SAP BBP_API_CTR_CRT_CHG Function Module for









BBP_API_CTR_CRT_CHG is a standard bbp api ctr crt chg 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 ctr crt chg FM, simply by entering the name BBP_API_CTR_CRT_CHG 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_CTR_CRT_CHG 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_CTR_CRT_CHG'"
EXPORTING
* IV_SIMULATION = "
* IT_ORGDATA = "
* IT_LONGTEXT = "
* IT_CONDITIONS = "
* IT_TOL = "
* IV_USER_ID = "
* IV_TYPE = "
* IV_BLOCKED = "
* IV_LANGUAGE = "
IS_HEADER = "
* IT_ITEM = "
* IT_ATTACH = "
* IT_PARTNER = "

IMPORTING
ES_HEADER = "

TABLES
* ET_STATUS = "
* ET_MESSAGES = "
.



IMPORTING Parameters details for BBP_API_CTR_CRT_CHG

IV_SIMULATION -

Data type: XFELD
Optional: Yes
Call by Reference: Yes

IT_ORGDATA -

Data type: BBPT_PDEXT_ORG
Optional: Yes
Call by Reference: Yes

IT_LONGTEXT -

Data type: BBPT_PDEXT_LONGTEXT
Optional: Yes
Call by Reference: Yes

IT_CONDITIONS -

Data type: BBPT_PDEXT_CND_D
Optional: Yes
Call by Reference: Yes

IT_TOL -

Data type: BBPT_PDEXT_TOL
Optional: Yes
Call by Reference: Yes

IV_USER_ID -

Data type: SY-UNAME
Optional: Yes
Call by Reference: Yes

IV_TYPE -

Data type: CHAR4
Optional: Yes
Call by Reference: Yes

IV_BLOCKED -

Data type: CHAR1
Optional: Yes
Call by Reference: Yes

IV_LANGUAGE -

Data type: SY-LANGU
Optional: Yes
Call by Reference: Yes

IS_HEADER -

Data type: BBPS_PDEXT_CTR_HEADER_IC
Optional: No
Call by Reference: Yes

IT_ITEM -

Data type: BBPT_PDEXT_CTR_ITEM_ICU
Optional: Yes
Call by Reference: Yes

IT_ATTACH -

Data type: BBPT_PDEXT_ATTACH
Optional: Yes
Call by Reference: Yes

IT_PARTNER -

Data type: BBPT_PDEXT_PARTNER
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for BBP_API_CTR_CRT_CHG

ES_HEADER -

Data type: BBPS_PDEXT_CTR_HEADER_D
Optional: No
Call by Reference: Yes

TABLES Parameters details for BBP_API_CTR_CRT_CHG

ET_STATUS -

Data type: BBP_PDS_STATUS
Optional: Yes
Call by Reference: Yes

ET_MESSAGES -

Data type: BBP_PDS_MESSAGES
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for BBP_API_CTR_CRT_CHG 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_es_header  TYPE BBPS_PDEXT_CTR_HEADER_D, "   
lt_et_status  TYPE STANDARD TABLE OF BBP_PDS_STATUS, "   
lv_iv_simulation  TYPE XFELD, "   
lv_it_orgdata  TYPE BBPT_PDEXT_ORG, "   
lv_it_longtext  TYPE BBPT_PDEXT_LONGTEXT, "   
lv_it_conditions  TYPE BBPT_PDEXT_CND_D, "   
lv_it_tol  TYPE BBPT_PDEXT_TOL, "   
lv_iv_user_id  TYPE SY-UNAME, "   
lt_et_messages  TYPE STANDARD TABLE OF BBP_PDS_MESSAGES, "   
lv_iv_type  TYPE CHAR4, "   
lv_iv_blocked  TYPE CHAR1, "   
lv_iv_language  TYPE SY-LANGU, "   
lv_is_header  TYPE BBPS_PDEXT_CTR_HEADER_IC, "   
lv_it_item  TYPE BBPT_PDEXT_CTR_ITEM_ICU, "   
lv_it_attach  TYPE BBPT_PDEXT_ATTACH, "   
lv_it_partner  TYPE BBPT_PDEXT_PARTNER. "   

  CALL FUNCTION 'BBP_API_CTR_CRT_CHG'  "
    EXPORTING
         IV_SIMULATION = lv_iv_simulation
         IT_ORGDATA = lv_it_orgdata
         IT_LONGTEXT = lv_it_longtext
         IT_CONDITIONS = lv_it_conditions
         IT_TOL = lv_it_tol
         IV_USER_ID = lv_iv_user_id
         IV_TYPE = lv_iv_type
         IV_BLOCKED = lv_iv_blocked
         IV_LANGUAGE = lv_iv_language
         IS_HEADER = lv_is_header
         IT_ITEM = lv_it_item
         IT_ATTACH = lv_it_attach
         IT_PARTNER = lv_it_partner
    IMPORTING
         ES_HEADER = lv_es_header
    TABLES
         ET_STATUS = lt_et_status
         ET_MESSAGES = lt_et_messages
. " BBP_API_CTR_CRT_CHG




ABAP code using 7.40 inline data declarations to call FM BBP_API_CTR_CRT_CHG

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 UNAME FROM SY INTO @DATA(ld_iv_user_id).
 
 
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_iv_language).
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!