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

Function BBP_API_IV_CRT 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_API_IV_CRT'".
EXPORTING
* I_TESTRUN = "
* I_INP_TYPE = "
* I_HEADER = "
* IT_ATTACH = "
* IT_ITEM_REL = "
IMPORTING
E_HEADER = "
ET_ATTACH = "
TABLES
* IT_ITEM = "
* ET_PARTNER = "
* ET_ORGDATA = "
* ET_LONGTEXT = "
* ET_FREIGHT = "
* ET_TAX = "
* ET_EXCHRATE = "
* ET_STATUS = "
* IT_ACCOUNT = "
* IT_PARTNER = "
* IT_LONGTEXT = "
* IT_FREIGHT = "
* IT_TAX = "
* IT_EXCHRATE = "
* ET_ITEM = "
* ET_ACCOUNT = "
IMPORTING Parameters details for BBP_API_IV_CRT
I_TESTRUN -
Data type: XFELDOptional: Yes
Call by Reference: Yes
I_INP_TYPE -
Data type: BBP_INP_TYPEOptional: Yes
Call by Reference: Yes
I_HEADER -
Data type: BBPS_PDEXT_INV_HEADER_ICOptional: Yes
Call by Reference: Yes
IT_ATTACH -
Data type: BBPT_PDEXT_ATTACHOptional: Yes
Call by Reference: Yes
IT_ITEM_REL -
Data type: BBPT_PDEXT_IVHUB_IRELOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BBP_API_IV_CRT
E_HEADER -
Data type: BBPS_PDEXT_INV_HEADER_DOptional: No
Call by Reference: Yes
ET_ATTACH -
Data type: BBPT_PDEXT_ATTACHOptional: No
Call by Reference: Yes
TABLES Parameters details for BBP_API_IV_CRT
IT_ITEM -
Data type: BBPS_PDEXT_INV_ITEM_ICUOptional: Yes
Call by Reference: Yes
ET_PARTNER -
Data type: BBPS_PDEXT_PARTNEROptional: Yes
Call by Reference: Yes
ET_ORGDATA -
Data type: BBPS_PDEXT_ORGOptional: Yes
Call by Reference: Yes
ET_LONGTEXT -
Data type: BBPS_PDEXT_LONGTEXTOptional: Yes
Call by Reference: Yes
ET_FREIGHT -
Data type: BBPS_PDEXT_FREIGHTOptional: Yes
Call by Reference: Yes
ET_TAX -
Data type: BBPS_PDEXT_TAXOptional: Yes
Call by Reference: Yes
ET_EXCHRATE -
Data type: BBPS_PDEXT_EXROptional: Yes
Call by Reference: Yes
ET_STATUS -
Data type: BBPS_PDEXT_STATUSOptional: Yes
Call by Reference: Yes
IT_ACCOUNT -
Data type: BBPS_PDEXT_ACCOptional: Yes
Call by Reference: Yes
IT_PARTNER -
Data type: BBPS_PDEXT_PARTNEROptional: Yes
Call by Reference: Yes
IT_LONGTEXT -
Data type: BBPS_PDEXT_LONGTEXTOptional: Yes
Call by Reference: Yes
IT_FREIGHT -
Data type: BBPS_PDEXT_FREIGHTOptional: Yes
Call by Reference: Yes
IT_TAX -
Data type: BBPS_PDEXT_TAXOptional: Yes
Call by Reference: Yes
IT_EXCHRATE -
Data type: BBPS_PDEXT_EXROptional: Yes
Call by Reference: Yes
ET_ITEM -
Data type: BBPS_PDEXT_INV_ITEM_DOptional: Yes
Call by Reference: Yes
ET_ACCOUNT -
Data type: BBPS_PDEXT_ACCOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BBP_API_IV_CRT 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_item | TYPE STANDARD TABLE OF BBPS_PDEXT_INV_ITEM_ICU, " | |||
| lv_e_header | TYPE BBPS_PDEXT_INV_HEADER_D, " | |||
| lv_i_testrun | TYPE XFELD, " | |||
| lt_et_partner | TYPE STANDARD TABLE OF BBPS_PDEXT_PARTNER, " | |||
| lt_et_orgdata | TYPE STANDARD TABLE OF BBPS_PDEXT_ORG, " | |||
| lt_et_longtext | TYPE STANDARD TABLE OF BBPS_PDEXT_LONGTEXT, " | |||
| lt_et_freight | TYPE STANDARD TABLE OF BBPS_PDEXT_FREIGHT, " | |||
| lt_et_tax | TYPE STANDARD TABLE OF BBPS_PDEXT_TAX, " | |||
| lt_et_exchrate | TYPE STANDARD TABLE OF BBPS_PDEXT_EXR, " | |||
| lt_et_status | TYPE STANDARD TABLE OF BBPS_PDEXT_STATUS, " | |||
| lv_et_attach | TYPE BBPT_PDEXT_ATTACH, " | |||
| lt_it_account | TYPE STANDARD TABLE OF BBPS_PDEXT_ACC, " | |||
| lv_i_inp_type | TYPE BBP_INP_TYPE, " | |||
| lv_i_header | TYPE BBPS_PDEXT_INV_HEADER_IC, " | |||
| lt_it_partner | TYPE STANDARD TABLE OF BBPS_PDEXT_PARTNER, " | |||
| lv_it_attach | TYPE BBPT_PDEXT_ATTACH, " | |||
| lt_it_longtext | TYPE STANDARD TABLE OF BBPS_PDEXT_LONGTEXT, " | |||
| lt_it_freight | TYPE STANDARD TABLE OF BBPS_PDEXT_FREIGHT, " | |||
| lv_it_item_rel | TYPE BBPT_PDEXT_IVHUB_IREL, " | |||
| lt_it_tax | TYPE STANDARD TABLE OF BBPS_PDEXT_TAX, " | |||
| lt_it_exchrate | TYPE STANDARD TABLE OF BBPS_PDEXT_EXR, " | |||
| lt_et_item | TYPE STANDARD TABLE OF BBPS_PDEXT_INV_ITEM_D, " | |||
| lt_et_account | TYPE STANDARD TABLE OF BBPS_PDEXT_ACC. " |
|   CALL FUNCTION 'BBP_API_IV_CRT' " |
| EXPORTING | ||
| I_TESTRUN | = lv_i_testrun | |
| I_INP_TYPE | = lv_i_inp_type | |
| I_HEADER | = lv_i_header | |
| IT_ATTACH | = lv_it_attach | |
| IT_ITEM_REL | = lv_it_item_rel | |
| IMPORTING | ||
| E_HEADER | = lv_e_header | |
| ET_ATTACH | = lv_et_attach | |
| TABLES | ||
| IT_ITEM | = lt_it_item | |
| ET_PARTNER | = lt_et_partner | |
| ET_ORGDATA | = lt_et_orgdata | |
| ET_LONGTEXT | = lt_et_longtext | |
| ET_FREIGHT | = lt_et_freight | |
| ET_TAX | = lt_et_tax | |
| ET_EXCHRATE | = lt_et_exchrate | |
| ET_STATUS | = lt_et_status | |
| IT_ACCOUNT | = lt_it_account | |
| IT_PARTNER | = lt_it_partner | |
| IT_LONGTEXT | = lt_it_longtext | |
| IT_FREIGHT | = lt_it_freight | |
| IT_TAX | = lt_it_tax | |
| IT_EXCHRATE | = lt_it_exchrate | |
| ET_ITEM | = lt_et_item | |
| ET_ACCOUNT | = lt_et_account | |
| . " BBP_API_IV_CRT | ||
ABAP code using 7.40 inline data declarations to call FM BBP_API_IV_CRT
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.Search for further information about these or an SAP related objects