SAP BBP_MAT_AVAIL_PLANTS_31I Function Module for NOTRANSL: EBP: ATP-Auskunft über mehrere Werke
BBP_MAT_AVAIL_PLANTS_31I is a standard bbp mat avail plants 31i SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: EBP: ATP-Auskunft über mehrere Werke processing and below is the pattern details for this FM, 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 mat avail plants 31i FM, simply by entering the name BBP_MAT_AVAIL_PLANTS_31I into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBPM
Program Name: SAPLBBPM
Main Program: SAPLBBPM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BBP_MAT_AVAIL_PLANTS_31I 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_MAT_AVAIL_PLANTS_31I'"NOTRANSL: EBP: ATP-Auskunft über mehrere Werke.
EXPORTING
IV_MATERIAL = "Material Number
IV_UNIT = "Unit of Measure for Display
* IV_CHECK_RULE = "Checking Rule for Availability Check
* IV_STGE_LOC = "Storage Location
* IV_BATCH = "Batch Number
* IV_CUSTOMER = "Customer Number
TABLES
IT_PLANTS = "EBP: Transfer Structure of Plants
* ET_AVAIL = "EBP: Export Parameter of Availability Check
* ET_WMDVSX = "EBP: Structure for Simulated Requiremt - ATP Info. Internet
* ET_WMDVEX = "EBP: Result of Availability Check - ATP Info. Internet
* ET_RETURN = "EBP: Return Parameter
IMPORTING Parameters details for BBP_MAT_AVAIL_PLANTS_31I
IV_MATERIAL - Material Number
Data type: BAPIMATVP-MATNROptional: No
Call by Reference: No ( called with pass by value option)
IV_UNIT - Unit of Measure for Display
Data type: BAPIADMM-UNITOptional: No
Call by Reference: No ( called with pass by value option)
IV_CHECK_RULE - Checking Rule for Availability Check
Data type: BAPIT441V-PRREGOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_STGE_LOC - Storage Location
Data type: BAPICM61V-LGORTOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_BATCH - Batch Number
Data type: BAPICM61V-CHARGOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_CUSTOMER - Customer Number
Data type: BAPIKNVVKY-CUSTOMEROptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BBP_MAT_AVAIL_PLANTS_31I
IT_PLANTS - EBP: Transfer Structure of Plants
Data type: BBP_PLANTOptional: No
Call by Reference: No ( called with pass by value option)
ET_AVAIL - EBP: Export Parameter of Availability Check
Data type: BBP_AVAILOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_WMDVSX - EBP: Structure for Simulated Requiremt - ATP Info. Internet
Data type: BBPWMDVSOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_WMDVEX - EBP: Result of Availability Check - ATP Info. Internet
Data type: BBPWMDVEOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_RETURN - EBP: Return Parameter
Data type: BBPRETOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BBP_MAT_AVAIL_PLANTS_31I 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_it_plants | TYPE STANDARD TABLE OF BBP_PLANT, " | |||
| lv_iv_material | TYPE BAPIMATVP-MATNR, " | |||
| lv_iv_unit | TYPE BAPIADMM-UNIT, " | |||
| lt_et_avail | TYPE STANDARD TABLE OF BBP_AVAIL, " | |||
| lt_et_wmdvsx | TYPE STANDARD TABLE OF BBPWMDVS, " | |||
| lv_iv_check_rule | TYPE BAPIT441V-PRREG, " | |||
| lt_et_wmdvex | TYPE STANDARD TABLE OF BBPWMDVE, " | |||
| lv_iv_stge_loc | TYPE BAPICM61V-LGORT, " | |||
| lv_iv_batch | TYPE BAPICM61V-CHARG, " | |||
| lt_et_return | TYPE STANDARD TABLE OF BBPRET, " | |||
| lv_iv_customer | TYPE BAPIKNVVKY-CUSTOMER. " |
|   CALL FUNCTION 'BBP_MAT_AVAIL_PLANTS_31I' "NOTRANSL: EBP: ATP-Auskunft über mehrere Werke |
| EXPORTING | ||
| IV_MATERIAL | = lv_iv_material | |
| IV_UNIT | = lv_iv_unit | |
| IV_CHECK_RULE | = lv_iv_check_rule | |
| IV_STGE_LOC | = lv_iv_stge_loc | |
| IV_BATCH | = lv_iv_batch | |
| IV_CUSTOMER | = lv_iv_customer | |
| TABLES | ||
| IT_PLANTS | = lt_it_plants | |
| ET_AVAIL | = lt_et_avail | |
| ET_WMDVSX | = lt_et_wmdvsx | |
| ET_WMDVEX | = lt_et_wmdvex | |
| ET_RETURN | = lt_et_return | |
| . " BBP_MAT_AVAIL_PLANTS_31I | ||
ABAP code using 7.40 inline data declarations to call FM BBP_MAT_AVAIL_PLANTS_31I
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 MATNR FROM BAPIMATVP INTO @DATA(ld_iv_material). | ||||
| "SELECT single UNIT FROM BAPIADMM INTO @DATA(ld_iv_unit). | ||||
| "SELECT single PRREG FROM BAPIT441V INTO @DATA(ld_iv_check_rule). | ||||
| "SELECT single LGORT FROM BAPICM61V INTO @DATA(ld_iv_stge_loc). | ||||
| "SELECT single CHARG FROM BAPICM61V INTO @DATA(ld_iv_batch). | ||||
| "SELECT single CUSTOMER FROM BAPIKNVVKY INTO @DATA(ld_iv_customer). | ||||
Search for further information about these or an SAP related objects