SAP BAPI_RE_CN_ADVPAY_EXT_CHANGE Function Module for Change AP Legacy Data Transfer (Real Estate Contract)









BAPI_RE_CN_ADVPAY_EXT_CHANGE is a standard bapi re cn advpay ext change 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 AP Legacy Data Transfer (Real Estate Contract) 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 re cn advpay ext change FM, simply by entering the name BAPI_RE_CN_ADVPAY_EXT_CHANGE into the relevant SAP transaction such as SE37 or SE38.

Function Group: RERA_BAPI_ADVPAY_EXT
Program Name: SAPLRERA_BAPI_ADVPAY_EXT
Main Program: SAPLRERA_BAPI_ADVPAY_EXT
Appliation area:
Release date: 19-Aug-2005
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_RE_CN_ADVPAY_EXT_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_RE_CN_ADVPAY_EXT_CHANGE'"Change AP Legacy Data Transfer (Real Estate Contract)
EXPORTING
COMPCODE = "Company Code
CONTRACTNUMBER = "Number of Real Estate Contract
* TEST_RUN = ' ' "Simulation Indicator

TABLES
* ADVPAY_EXT = "AP - Legacy Data Transfer
RETURN = "Return Parameter(s)
.



IMPORTING Parameters details for BAPI_RE_CN_ADVPAY_EXT_CHANGE

COMPCODE - Company Code

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

CONTRACTNUMBER - Number of Real Estate Contract

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

TEST_RUN - Simulation Indicator

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

TABLES Parameters details for BAPI_RE_CN_ADVPAY_EXT_CHANGE

ADVPAY_EXT - AP - Legacy Data Transfer

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

RETURN - Return Parameter(s)

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

Copy and paste ABAP code example for BAPI_RE_CN_ADVPAY_EXT_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_compcode  TYPE BAPI_RE_CONTRACT_KEY-COMP_CODE, "   
lt_advpay_ext  TYPE STANDARD TABLE OF BAPI_RE_ADVPAY_EXT_DATC, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_contractnumber  TYPE BAPI_RE_CONTRACT_KEY-CONTRACT_NUMBER, "   
lv_test_run  TYPE BAPI_RE_ADDITIONAL_FIELDS-TESTRUN. "   SPACE

  CALL FUNCTION 'BAPI_RE_CN_ADVPAY_EXT_CHANGE'  "Change AP Legacy Data Transfer (Real Estate Contract)
    EXPORTING
         COMPCODE = lv_compcode
         CONTRACTNUMBER = lv_contractnumber
         TEST_RUN = lv_test_run
    TABLES
         ADVPAY_EXT = lt_advpay_ext
         RETURN = lt_return
. " BAPI_RE_CN_ADVPAY_EXT_CHANGE




ABAP code using 7.40 inline data declarations to call FM BAPI_RE_CN_ADVPAY_EXT_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 COMP_CODE FROM BAPI_RE_CONTRACT_KEY INTO @DATA(ld_compcode).
 
 
 
"SELECT single CONTRACT_NUMBER FROM BAPI_RE_CONTRACT_KEY INTO @DATA(ld_contractnumber).
 
"SELECT single TESTRUN FROM BAPI_RE_ADDITIONAL_FIELDS INTO @DATA(ld_test_run).
DATA(ld_test_run) = ' '.
 


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!