SAP BAPI_CTRACBILLPRODUCT_CHANGE Function Module for









BAPI_CTRACBILLPRODUCT_CHANGE is a standard bapi ctracbillproduct change 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 bapi ctracbillproduct change FM, simply by entering the name BAPI_CTRACBILLPRODUCT_CHANGE into the relevant SAP transaction such as SE37 or SE38.

Function Group: FKK_VT_PRD_BAPI
Program Name: SAPLFKK_VT_PRD_BAPI
Main Program: SAPLFKK_VT_PRD_BAPI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_CTRACBILLPRODUCT_CHANGE 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 'BAPI_CTRACBILLPRODUCT_CHANGE'"
  EXPORTING
   PRODUCT =  "
*  PRODUCTDATA =  "
*  PRODUCTDATAX =  "
*  TESTRUN = ' ' "
*  WRITECHANGEDOCUMENTS = 'X' "

TABLES
*  PRODUCTTEXTDATA =  "
*  PRODUCTTEXTDATAX =  "
*  PRODUCTSALESORGDATA =  "
*  PRODUCTSALESORGDATAX =  "
*  EXTENSIONIN =  "
*  RETURN =  "
.



IMPORTING Parameters details for BAPI_CTRACBILLPRODUCT_CHANGE

PRODUCT -

Data type: BAPI_BILLPRD_PRD_CREATE-PRODUCT
Optional: No
Call by Reference: No ( called with pass by value option)

PRODUCTDATA -

Data type: BAPI_BILLPRD_PRD_CHANGE
Optional: Yes
Call by Reference: No ( called with pass by value option)

PRODUCTDATAX -

Data type: BAPI_BILLPRD_PRD_CHANGEX
Optional: Yes
Call by Reference: No ( called with pass by value option)

TESTRUN -

Data type: BAPI_BILLCONTR_CONTROL-TESTRUN
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

WRITECHANGEDOCUMENTS -

Data type: BAPI_BILLCONTR_CONTROL-WRITECHANGEDOCUMENTS
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BAPI_CTRACBILLPRODUCT_CHANGE

PRODUCTTEXTDATA -

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

PRODUCTTEXTDATAX -

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

PRODUCTSALESORGDATA -

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

PRODUCTSALESORGDATAX -

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

EXTENSIONIN -

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

RETURN -

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

Copy and paste ABAP code example for BAPI_CTRACBILLPRODUCT_CHANGE 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_product  TYPE BAPI_BILLPRD_PRD_CREATE-PRODUCT, "   
lt_producttextdata  TYPE STANDARD TABLE OF BAPI_BILLPRD_PRDT_CHANGE, "   
lv_productdata  TYPE BAPI_BILLPRD_PRD_CHANGE, "   
lt_producttextdatax  TYPE STANDARD TABLE OF BAPI_BILLPRD_PRDT_CHANGEX, "   
lv_productdatax  TYPE BAPI_BILLPRD_PRD_CHANGEX, "   
lt_productsalesorgdata  TYPE STANDARD TABLE OF BAPI_BILLPRD_PRDS_CHANGE, "   
lv_testrun  TYPE BAPI_BILLCONTR_CONTROL-TESTRUN, "   SPACE
lt_productsalesorgdatax  TYPE STANDARD TABLE OF BAPI_BILLPRD_PRDS_CHANGEX, "   
lt_extensionin  TYPE STANDARD TABLE OF BAPIPAREX, "   
lv_writechangedocuments  TYPE BAPI_BILLCONTR_CONTROL-WRITECHANGEDOCUMENTS, "   'X'
lt_return  TYPE STANDARD TABLE OF BAPIRET2. "   

  CALL FUNCTION 'BAPI_CTRACBILLPRODUCT_CHANGE'  "
    EXPORTING
         PRODUCT = lv_product
         PRODUCTDATA = lv_productdata
         PRODUCTDATAX = lv_productdatax
         TESTRUN = lv_testrun
         WRITECHANGEDOCUMENTS = lv_writechangedocuments
    TABLES
         PRODUCTTEXTDATA = lt_producttextdata
         PRODUCTTEXTDATAX = lt_producttextdatax
         PRODUCTSALESORGDATA = lt_productsalesorgdata
         PRODUCTSALESORGDATAX = lt_productsalesorgdatax
         EXTENSIONIN = lt_extensionin
         RETURN = lt_return
. " BAPI_CTRACBILLPRODUCT_CHANGE




ABAP code using 7.40 inline data declarations to call FM BAPI_CTRACBILLPRODUCT_CHANGE

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 PRODUCT FROM BAPI_BILLPRD_PRD_CREATE INTO @DATA(ld_product).
 
 
 
 
 
 
"SELECT single TESTRUN FROM BAPI_BILLCONTR_CONTROL INTO @DATA(ld_testrun).
DATA(ld_testrun) = ' '.
 
 
 
"SELECT single WRITECHANGEDOCUMENTS FROM BAPI_BILLCONTR_CONTROL INTO @DATA(ld_writechangedocuments).
DATA(ld_writechangedocuments) = 'X'.
 
 


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!