SAP RECA_API_EXT_DATA_CHG Function Module for









RECA_API_EXT_DATA_CHG is a standard reca api ext data 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 reca api ext data chg FM, simply by entering the name RECA_API_EXT_DATA_CHG into the relevant SAP transaction such as SE37 or SE38.

Function Group: RECA_API_EXT_DATA
Program Name: SAPLRECA_API_EXT_DATA
Main Program: SAPLRECA_API_EXT_DATA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RECA_API_EXT_DATA_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 'RECA_API_EXT_DATA_CHG'"
EXPORTING
IO_BUS_OBJECT = "
IT_EXT_DATA = "
IO_MSGLIST = "

IMPORTING
ET_EXT_DATA_REMAINING = "
.



IMPORTING Parameters details for RECA_API_EXT_DATA_CHG

IO_BUS_OBJECT -

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

IT_EXT_DATA -

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

IO_MSGLIST -

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

EXPORTING Parameters details for RECA_API_EXT_DATA_CHG

ET_EXT_DATA_REMAINING -

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

Copy and paste ABAP code example for RECA_API_EXT_DATA_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_io_bus_object  TYPE IF_RECA_BUS_OBJECT, "   
lv_et_ext_data_remaining  TYPE RE_T_EXT_DATA, "   
lv_it_ext_data  TYPE RE_T_EXT_DATA, "   
lv_io_msglist  TYPE IF_RECA_MESSAGE_LIST. "   

  CALL FUNCTION 'RECA_API_EXT_DATA_CHG'  "
    EXPORTING
         IO_BUS_OBJECT = lv_io_bus_object
         IT_EXT_DATA = lv_it_ext_data
         IO_MSGLIST = lv_io_msglist
    IMPORTING
         ET_EXT_DATA_REMAINING = lv_et_ext_data_remaining
. " RECA_API_EXT_DATA_CHG




ABAP code using 7.40 inline data declarations to call FM RECA_API_EXT_DATA_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.

 
 
 
 


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!