SAP RSAR_UPDATE_CONTROL Function Module for Controls the saving of received IDOCS in the database









RSAR_UPDATE_CONTROL is a standard rsar update control SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Controls the saving of received IDOCS in the database 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 rsar update control FM, simply by entering the name RSAR_UPDATE_CONTROL into the relevant SAP transaction such as SE37 or SE38.

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



Function RSAR_UPDATE_CONTROL 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 'RSAR_UPDATE_CONTROL'"Controls the saving of received IDOCS in the database
EXPORTING
I_S_MINFO = "
I_IDOC_HEADER_DATAPAKID = "

CHANGING
C_T_IDOCSTATE = "
C_SUBRC = "

TABLES
I_T_COMSTRU = "
.



IMPORTING Parameters details for RSAR_UPDATE_CONTROL

I_S_MINFO -

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

I_IDOC_HEADER_DATAPAKID -

Data type: RSARR_S_RECEIVE_HEADER3-DATAPAKID
Optional: No
Call by Reference: Yes

CHANGING Parameters details for RSAR_UPDATE_CONTROL

C_T_IDOCSTATE -

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

C_SUBRC -

Data type: SY-SUBRC
Optional: No
Call by Reference: Yes

TABLES Parameters details for RSAR_UPDATE_CONTROL

I_T_COMSTRU -

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

Copy and paste ABAP code example for RSAR_UPDATE_CONTROL 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_i_s_minfo  TYPE RSSM_S_MINFO, "   
lt_i_t_comstru  TYPE STANDARD TABLE OF RSSM_S_MINFO, "   
lv_c_t_idocstate  TYPE RSARR_T_IDOCSTATE, "   
lv_c_subrc  TYPE SY-SUBRC, "   
lv_i_idoc_header_datapakid  TYPE RSARR_S_RECEIVE_HEADER3-DATAPAKID. "   

  CALL FUNCTION 'RSAR_UPDATE_CONTROL'  "Controls the saving of received IDOCS in the database
    EXPORTING
         I_S_MINFO = lv_i_s_minfo
         I_IDOC_HEADER_DATAPAKID = lv_i_idoc_header_datapakid
    CHANGING
         C_T_IDOCSTATE = lv_c_t_idocstate
         C_SUBRC = lv_c_subrc
    TABLES
         I_T_COMSTRU = lt_i_t_comstru
. " RSAR_UPDATE_CONTROL




ABAP code using 7.40 inline data declarations to call FM RSAR_UPDATE_CONTROL

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 SUBRC FROM SY INTO @DATA(ld_c_subrc).
 
"SELECT single DATAPAKID FROM RSARR_S_RECEIVE_HEADER3 INTO @DATA(ld_i_idoc_header_datapakid).
 


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!