SAP BBP_PDLIM_UPDATE Function Module for
BBP_PDLIM_UPDATE is a standard bbp pdlim update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for bbp pdlim update FM, simply by entering the name BBP_PDLIM_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_PDLIM
Program Name: SAPLBBP_PDLIM
Main Program: SAPLBBP_PDLIM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_PDLIM_UPDATE pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'BBP_PDLIM_UPDATE'".
EXPORTING
I_P_GUID = "
I_P_KIND = "
I_OBJECT_TYPE = "
I_COM = "
* IV_PARK_OR_SAVE = "
* IV_CHANGE_VERSION = "
IMPORTING
E_COM = "
CHANGING
E_CHANGED = "
TABLES
I_LIMIT = "
IMPORTING Parameters details for BBP_PDLIM_UPDATE
I_P_GUID -
Data type: CRMD_ORDERADM_H-GUIDOptional: No
Call by Reference: Yes
I_P_KIND -
Data type: CRMT_OBJECT_KINDOptional: No
Call by Reference: Yes
I_OBJECT_TYPE -
Data type: CRMD_ORDERADM_H-OBJECT_TYPEOptional: No
Call by Reference: Yes
I_COM -
Data type: BBP_PDS_LIM_ICOMOptional: No
Call by Reference: Yes
IV_PARK_OR_SAVE -
Data type: XFELDOptional: Yes
Call by Reference: Yes
IV_CHANGE_VERSION -
Data type: XFELDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BBP_PDLIM_UPDATE
E_COM -
Data type: BBP_PDS_LIM_ECOMOptional: No
Call by Reference: Yes
CHANGING Parameters details for BBP_PDLIM_UPDATE
E_CHANGED -
Data type: XFELDOptional: No
Call by Reference: Yes
TABLES Parameters details for BBP_PDLIM_UPDATE
I_LIMIT -
Data type: BBP_PDS_LIMITOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_PDLIM_UPDATE Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_e_com | TYPE BBP_PDS_LIM_ECOM, " | |||
| lt_i_limit | TYPE STANDARD TABLE OF BBP_PDS_LIMIT, " | |||
| lv_i_p_guid | TYPE CRMD_ORDERADM_H-GUID, " | |||
| lv_e_changed | TYPE XFELD, " | |||
| lv_i_p_kind | TYPE CRMT_OBJECT_KIND, " | |||
| lv_i_object_type | TYPE CRMD_ORDERADM_H-OBJECT_TYPE, " | |||
| lv_i_com | TYPE BBP_PDS_LIM_ICOM, " | |||
| lv_iv_park_or_save | TYPE XFELD, " | |||
| lv_iv_change_version | TYPE XFELD. " |
|   CALL FUNCTION 'BBP_PDLIM_UPDATE' " |
| EXPORTING | ||
| I_P_GUID | = lv_i_p_guid | |
| I_P_KIND | = lv_i_p_kind | |
| I_OBJECT_TYPE | = lv_i_object_type | |
| I_COM | = lv_i_com | |
| IV_PARK_OR_SAVE | = lv_iv_park_or_save | |
| IV_CHANGE_VERSION | = lv_iv_change_version | |
| IMPORTING | ||
| E_COM | = lv_e_com | |
| CHANGING | ||
| E_CHANGED | = lv_e_changed | |
| TABLES | ||
| I_LIMIT | = lt_i_limit | |
| . " BBP_PDLIM_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM BBP_PDLIM_UPDATE
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single GUID FROM CRMD_ORDERADM_H INTO @DATA(ld_i_p_guid). | ||||
| "SELECT single OBJECT_TYPE FROM CRMD_ORDERADM_H INTO @DATA(ld_i_object_type). | ||||
Search for further information about these or an SAP related objects