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

Function BBP_BC_PO_CREATE 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_BC_PO_CREATE'".
EXPORTING
I_PO_HEADER = "
* I_PO_HEADER_CUST = "
* I_TRFC_CALL = ' ' "
IMPORTING
E_PO_HEADER = "
E_PO_HEADER_CUST = "
TABLES
* I_PO_ITEMS = "
* E_PO_ITEMS = "
* E_PO_ITEMS_CUST = "
* E_PO_ACCASS = "
* E_PO_ACCASS_CUST = "
* E_PO_PARTNER = "
* E_PO_ORGDATA = "
* E_PO_LIMIT = "
* E_PO_TEXT = "
* E_PO_STATUS = "
* E_PO_ATTACH = "
* I_PO_ITEMS_CUST = "
RETURN = "
* I_PO_ACCASS = "
* I_PO_ACCASS_CUST = "
* I_PO_PARTNER = "
* I_PO_TEXT = "
* I_PO_ATTACH = "
* I_PO_ORGDATA = "
* I_PO_LIMIT = "
IMPORTING Parameters details for BBP_BC_PO_CREATE
I_PO_HEADER -
Data type: BAPI_PO_HEADER_COptional: No
Call by Reference: No ( called with pass by value option)
I_PO_HEADER_CUST -
Data type: BAPI_PO_HEADER_CUST_COptional: Yes
Call by Reference: No ( called with pass by value option)
I_TRFC_CALL -
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BBP_BC_PO_CREATE
E_PO_HEADER -
Data type: BAPI_PO_HEADER_DOptional: No
Call by Reference: No ( called with pass by value option)
E_PO_HEADER_CUST -
Data type: BAPI_PO_HEADER_CUST_DOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BBP_BC_PO_CREATE
I_PO_ITEMS -
Data type: BAPI_PO_ITEM_COptional: Yes
Call by Reference: Yes
E_PO_ITEMS -
Data type: BAPI_PO_ITEM_DOptional: Yes
Call by Reference: Yes
E_PO_ITEMS_CUST -
Data type: BAPI_PO_ITEM_CUST_DOptional: Yes
Call by Reference: Yes
E_PO_ACCASS -
Data type: BAPI_ACC_DOptional: Yes
Call by Reference: Yes
E_PO_ACCASS_CUST -
Data type: BAPI_ACC_CUST_DOptional: Yes
Call by Reference: Yes
E_PO_PARTNER -
Data type: BAPI_BUP_DOptional: Yes
Call by Reference: Yes
E_PO_ORGDATA -
Data type: BAPI_ORG_DOptional: Yes
Call by Reference: Yes
E_PO_LIMIT -
Data type: BAPI_LIMIT_DOptional: Yes
Call by Reference: Yes
E_PO_TEXT -
Data type: BAPI_TEXT_IOptional: Yes
Call by Reference: Yes
E_PO_STATUS -
Data type: BAPI_BBP_STATUSOptional: Yes
Call by Reference: Yes
E_PO_ATTACH -
Data type: BAPI_ATT_DOptional: Yes
Call by Reference: Yes
I_PO_ITEMS_CUST -
Data type: BAPI_PO_ITEM_CUST_COptional: Yes
Call by Reference: Yes
RETURN -
Data type: BAPIRET2Optional: No
Call by Reference: Yes
I_PO_ACCASS -
Data type: BAPI_ACC_COptional: Yes
Call by Reference: Yes
I_PO_ACCASS_CUST -
Data type: BAPI_ACC_CUST_COptional: Yes
Call by Reference: Yes
I_PO_PARTNER -
Data type: BAPI_BUP_COptional: Yes
Call by Reference: Yes
I_PO_TEXT -
Data type: BAPI_TEXT_IOptional: Yes
Call by Reference: Yes
I_PO_ATTACH -
Data type: BAPI_ATT_COptional: Yes
Call by Reference: Yes
I_PO_ORGDATA -
Data type: BAPI_ORG_COptional: Yes
Call by Reference: Yes
I_PO_LIMIT -
Data type: BAPI_LIMIT_COptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BBP_BC_PO_CREATE 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_po_items | TYPE STANDARD TABLE OF BAPI_PO_ITEM_C, " | |||
| lv_e_po_header | TYPE BAPI_PO_HEADER_D, " | |||
| lv_i_po_header | TYPE BAPI_PO_HEADER_C, " | |||
| lt_e_po_items | TYPE STANDARD TABLE OF BAPI_PO_ITEM_D, " | |||
| lt_e_po_items_cust | TYPE STANDARD TABLE OF BAPI_PO_ITEM_CUST_D, " | |||
| lt_e_po_accass | TYPE STANDARD TABLE OF BAPI_ACC_D, " | |||
| lt_e_po_accass_cust | TYPE STANDARD TABLE OF BAPI_ACC_CUST_D, " | |||
| lt_e_po_partner | TYPE STANDARD TABLE OF BAPI_BUP_D, " | |||
| lt_e_po_orgdata | TYPE STANDARD TABLE OF BAPI_ORG_D, " | |||
| lt_e_po_limit | TYPE STANDARD TABLE OF BAPI_LIMIT_D, " | |||
| lt_e_po_text | TYPE STANDARD TABLE OF BAPI_TEXT_I, " | |||
| lt_e_po_status | TYPE STANDARD TABLE OF BAPI_BBP_STATUS, " | |||
| lt_e_po_attach | TYPE STANDARD TABLE OF BAPI_ATT_D, " | |||
| lt_i_po_items_cust | TYPE STANDARD TABLE OF BAPI_PO_ITEM_CUST_C, " | |||
| lv_e_po_header_cust | TYPE BAPI_PO_HEADER_CUST_D, " | |||
| lv_i_po_header_cust | TYPE BAPI_PO_HEADER_CUST_C, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lt_i_po_accass | TYPE STANDARD TABLE OF BAPI_ACC_C, " | |||
| lv_i_trfc_call | TYPE XFELD, " SPACE | |||
| lt_i_po_accass_cust | TYPE STANDARD TABLE OF BAPI_ACC_CUST_C, " | |||
| lt_i_po_partner | TYPE STANDARD TABLE OF BAPI_BUP_C, " | |||
| lt_i_po_text | TYPE STANDARD TABLE OF BAPI_TEXT_I, " | |||
| lt_i_po_attach | TYPE STANDARD TABLE OF BAPI_ATT_C, " | |||
| lt_i_po_orgdata | TYPE STANDARD TABLE OF BAPI_ORG_C, " | |||
| lt_i_po_limit | TYPE STANDARD TABLE OF BAPI_LIMIT_C. " |
|   CALL FUNCTION 'BBP_BC_PO_CREATE' " |
| EXPORTING | ||
| I_PO_HEADER | = lv_i_po_header | |
| I_PO_HEADER_CUST | = lv_i_po_header_cust | |
| I_TRFC_CALL | = lv_i_trfc_call | |
| IMPORTING | ||
| E_PO_HEADER | = lv_e_po_header | |
| E_PO_HEADER_CUST | = lv_e_po_header_cust | |
| TABLES | ||
| I_PO_ITEMS | = lt_i_po_items | |
| E_PO_ITEMS | = lt_e_po_items | |
| E_PO_ITEMS_CUST | = lt_e_po_items_cust | |
| E_PO_ACCASS | = lt_e_po_accass | |
| E_PO_ACCASS_CUST | = lt_e_po_accass_cust | |
| E_PO_PARTNER | = lt_e_po_partner | |
| E_PO_ORGDATA | = lt_e_po_orgdata | |
| E_PO_LIMIT | = lt_e_po_limit | |
| E_PO_TEXT | = lt_e_po_text | |
| E_PO_STATUS | = lt_e_po_status | |
| E_PO_ATTACH | = lt_e_po_attach | |
| I_PO_ITEMS_CUST | = lt_i_po_items_cust | |
| RETURN | = lt_return | |
| I_PO_ACCASS | = lt_i_po_accass | |
| I_PO_ACCASS_CUST | = lt_i_po_accass_cust | |
| I_PO_PARTNER | = lt_i_po_partner | |
| I_PO_TEXT | = lt_i_po_text | |
| I_PO_ATTACH | = lt_i_po_attach | |
| I_PO_ORGDATA | = lt_i_po_orgdata | |
| I_PO_LIMIT | = lt_i_po_limit | |
| . " BBP_BC_PO_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM BBP_BC_PO_CREATE
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.| DATA(ld_i_trfc_call) | = ' '. | |||
Search for further information about these or an SAP related objects