SAP BBP_ITEMLIST_CHECK Function Module for
BBP_ITEMLIST_CHECK is a standard bbp itemlist check 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 itemlist check FM, simply by entering the name BBP_ITEMLIST_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_PDIAD
Program Name: SAPLBBP_PDIAD
Main Program: SAPLBBP_PDIAD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_ITEMLIST_CHECK 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_ITEMLIST_CHECK'".
EXPORTING
I_P_GUID = "
I_OBJECT_TYPE = "
I_COM = "
* IT_ATTACH = "
* IV_CHECK_ALL_ITEMS = "
* IV_UPDATE_FROM_CHANGE_VERSION = "
IMPORTING
P_CHECK_IND = "
TABLES
* I_ITMADM = "
* I_SDLN = "
* I_TOL = "
* I_WEIGHT = "
* I_DEP = "
* I_ITMIGP = "
* I_ITMPSET = "
* I_ITMBEI = "
* I_ITMISB = "
* I_ACCOUNT = "
* I_PARTNER = "
* I_CONFIRM = "
* I_ORGDATA = "
IMPORTING Parameters details for BBP_ITEMLIST_CHECK
I_P_GUID -
Data type: CRMD_ORDERADM_H-GUIDOptional: 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_ITM_ICOMOptional: No
Call by Reference: Yes
IT_ATTACH -
Data type: BBPT_PDS_ATT_TOptional: Yes
Call by Reference: Yes
IV_CHECK_ALL_ITEMS -
Data type: XFELDOptional: Yes
Call by Reference: Yes
IV_UPDATE_FROM_CHANGE_VERSION -
Data type: XFELDOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BBP_ITEMLIST_CHECK
P_CHECK_IND -
Data type: BBP_CHECK_INDOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BBP_ITEMLIST_CHECK
I_ITMADM -
Data type: BBP_PDS_ITMADMOptional: Yes
Call by Reference: No ( called with pass by value option)
I_SDLN -
Data type: BBP_PDS_SDLNOptional: Yes
Call by Reference: Yes
I_TOL -
Data type: BBP_PDS_TOLOptional: Yes
Call by Reference: Yes
I_WEIGHT -
Data type: BBP_PDS_WEIGHTOptional: Yes
Call by Reference: Yes
I_DEP -
Data type: BBP_PDS_DEPOptional: Yes
Call by Reference: Yes
I_ITMIGP -
Data type: BBP_PDIGPOptional: Yes
Call by Reference: Yes
I_ITMPSET -
Data type: BBP_PDPSETOptional: Yes
Call by Reference: Yes
I_ITMBEI -
Data type: BBP_PDBEIOptional: Yes
Call by Reference: Yes
I_ITMISB -
Data type: BBP_PDISBOptional: Yes
Call by Reference: Yes
I_ACCOUNT -
Data type: BBP_PDACCOptional: Yes
Call by Reference: Yes
I_PARTNER -
Data type: BBP_PDS_PARTNEROptional: Yes
Call by Reference: Yes
I_CONFIRM -
Data type: BBP_PDS_CONOptional: Yes
Call by Reference: Yes
I_ORGDATA -
Data type: BBP_PDS_ORGOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BBP_ITEMLIST_CHECK 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: | ||||
| lt_i_itmadm | TYPE STANDARD TABLE OF BBP_PDS_ITMADM, " | |||
| lv_i_p_guid | TYPE CRMD_ORDERADM_H-GUID, " | |||
| lv_p_check_ind | TYPE BBP_CHECK_IND, " | |||
| lt_i_sdln | TYPE STANDARD TABLE OF BBP_PDS_SDLN, " | |||
| lt_i_tol | TYPE STANDARD TABLE OF BBP_PDS_TOL, " | |||
| lt_i_weight | TYPE STANDARD TABLE OF BBP_PDS_WEIGHT, " | |||
| lt_i_dep | TYPE STANDARD TABLE OF BBP_PDS_DEP, " | |||
| lt_i_itmigp | TYPE STANDARD TABLE OF BBP_PDIGP, " | |||
| lv_i_object_type | TYPE CRMD_ORDERADM_H-OBJECT_TYPE, " | |||
| lv_i_com | TYPE BBP_PDS_ITM_ICOM, " | |||
| lt_i_itmpset | TYPE STANDARD TABLE OF BBP_PDPSET, " | |||
| lt_i_itmbei | TYPE STANDARD TABLE OF BBP_PDBEI, " | |||
| lv_it_attach | TYPE BBPT_PDS_ATT_T, " | |||
| lt_i_itmisb | TYPE STANDARD TABLE OF BBP_PDISB, " | |||
| lv_iv_check_all_items | TYPE XFELD, " | |||
| lt_i_account | TYPE STANDARD TABLE OF BBP_PDACC, " | |||
| lv_iv_update_from_change_version | TYPE XFELD, " | |||
| lt_i_partner | TYPE STANDARD TABLE OF BBP_PDS_PARTNER, " | |||
| lt_i_confirm | TYPE STANDARD TABLE OF BBP_PDS_CON, " | |||
| lt_i_orgdata | TYPE STANDARD TABLE OF BBP_PDS_ORG. " |
|   CALL FUNCTION 'BBP_ITEMLIST_CHECK' " |
| EXPORTING | ||
| I_P_GUID | = lv_i_p_guid | |
| I_OBJECT_TYPE | = lv_i_object_type | |
| I_COM | = lv_i_com | |
| IT_ATTACH | = lv_it_attach | |
| IV_CHECK_ALL_ITEMS | = lv_iv_check_all_items | |
| IV_UPDATE_FROM_CHANGE_VERSION | = lv_iv_update_from_change_version | |
| IMPORTING | ||
| P_CHECK_IND | = lv_p_check_ind | |
| TABLES | ||
| I_ITMADM | = lt_i_itmadm | |
| I_SDLN | = lt_i_sdln | |
| I_TOL | = lt_i_tol | |
| I_WEIGHT | = lt_i_weight | |
| I_DEP | = lt_i_dep | |
| I_ITMIGP | = lt_i_itmigp | |
| I_ITMPSET | = lt_i_itmpset | |
| I_ITMBEI | = lt_i_itmbei | |
| I_ITMISB | = lt_i_itmisb | |
| I_ACCOUNT | = lt_i_account | |
| I_PARTNER | = lt_i_partner | |
| I_CONFIRM | = lt_i_confirm | |
| I_ORGDATA | = lt_i_orgdata | |
| . " BBP_ITEMLIST_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM BBP_ITEMLIST_CHECK
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