SAP BAPI_RECEIVABLE_CHANGE_MLT Function Module for Change BAPI for receivable









BAPI_RECEIVABLE_CHANGE_MLT is a standard bapi receivable change mlt SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change BAPI for receivable 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 bapi receivable change mlt FM, simply by entering the name BAPI_RECEIVABLE_CHANGE_MLT into the relevant SAP transaction such as SE37 or SE38.

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



Function BAPI_RECEIVABLE_CHANGE_MLT 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_RECEIVABLE_CHANGE_MLT'"Change BAPI for receivable
  EXPORTING
*  GENERATE_LINKS = 'X' "Indicates that CAG_RBL links to be generated automatically
*  TESTRUN =  "Switch to Simulation Session for Write BAPIs
*  PROCESSEXTENSION =  "Flag: Execute Customer Extensions (BAdIs) in BAPI

TABLES
   HEADER =  "Receivable header structure
*  POSITIONS =  "Receivable Position for MAPI Change
*  BUSINESSPARTNERS =  "Receivables Business Partners for Change BAPI
*  CHANGEDRECEIVABLES =  "Semantic Key for CMS_RBL
*  FAILEDRECEIVABLES =  "Semantic Key for CMS_RBL
*  EXTENSIONIN =  "Ref. structure for BAPI parameter ExtensionIn/ExtensionOut
*  RETURN =  "Return Parameter
.



IMPORTING Parameters details for BAPI_RECEIVABLE_CHANGE_MLT

GENERATE_LINKS - Indicates that CAG_RBL links to be generated automatically

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

TESTRUN - Switch to Simulation Session for Write BAPIs

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

PROCESSEXTENSION - Flag: Execute Customer Extensions (BAdIs) in BAPI

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

TABLES Parameters details for BAPI_RECEIVABLE_CHANGE_MLT

HEADER - Receivable header structure

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

POSITIONS - Receivable Position for MAPI Change

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

BUSINESSPARTNERS - Receivables Business Partners for Change BAPI

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

CHANGEDRECEIVABLES - Semantic Key for CMS_RBL

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

FAILEDRECEIVABLES - Semantic Key for CMS_RBL

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

EXTENSIONIN - Ref. structure for BAPI parameter ExtensionIn/ExtensionOut

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

RETURN - Return Parameter

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

Copy and paste ABAP code example for BAPI_RECEIVABLE_CHANGE_MLT 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_header  TYPE STANDARD TABLE OF BAPICMS_STR_RBL_HDR_CHG, "   
lv_generate_links  TYPE BAPICMS_STR_RBL-GENERATE_LINKS, "   'X'
lv_testrun  TYPE BAPI_CMS_STR_CENTRAL-TESTRUN, "   
lt_positions  TYPE STANDARD TABLE OF BAPICMS_STR_RBL_POS_CHG, "   
lt_businesspartners  TYPE STANDARD TABLE OF BAPICMS_STR_RBL_BP_CHG, "   
lv_processextension  TYPE BAPI_CMS_STR_CENTRAL-PROCESSEXTENSION, "   
lt_changedreceivables  TYPE STANDARD TABLE OF BAPICMS_STR_RBL_SKY, "   
lt_failedreceivables  TYPE STANDARD TABLE OF BAPICMS_STR_FAIL_RBL_SKY, "   
lt_extensionin  TYPE STANDARD TABLE OF BAPIPAREX, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2. "   

  CALL FUNCTION 'BAPI_RECEIVABLE_CHANGE_MLT'  "Change BAPI for receivable
    EXPORTING
         GENERATE_LINKS = lv_generate_links
         TESTRUN = lv_testrun
         PROCESSEXTENSION = lv_processextension
    TABLES
         HEADER = lt_header
         POSITIONS = lt_positions
         BUSINESSPARTNERS = lt_businesspartners
         CHANGEDRECEIVABLES = lt_changedreceivables
         FAILEDRECEIVABLES = lt_failedreceivables
         EXTENSIONIN = lt_extensionin
         RETURN = lt_return
. " BAPI_RECEIVABLE_CHANGE_MLT




ABAP code using 7.40 inline data declarations to call FM BAPI_RECEIVABLE_CHANGE_MLT

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 GENERATE_LINKS FROM BAPICMS_STR_RBL INTO @DATA(ld_generate_links).
DATA(ld_generate_links) = 'X'.
 
"SELECT single TESTRUN FROM BAPI_CMS_STR_CENTRAL INTO @DATA(ld_testrun).
 
 
 
"SELECT single PROCESSEXTENSION FROM BAPI_CMS_STR_CENTRAL INTO @DATA(ld_processextension).
 
 
 
 
 


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!