SAP RSAR_INFOSOURCE_MAINTAIN Function Module for Editing of InfoSource
RSAR_INFOSOURCE_MAINTAIN is a standard rsar infosource maintain SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Editing of InfoSource 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 infosource maintain FM, simply by entering the name RSAR_INFOSOURCE_MAINTAIN into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSAC
Program Name: SAPLRSAC
Main Program: SAPLRSAC
Appliation area: B
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSAR_INFOSOURCE_MAINTAIN 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_INFOSOURCE_MAINTAIN'"Editing of InfoSource.
EXPORTING
* I_ISOURCE = "InfoSource
* I_ISOSTYPE = "BW Infosource type (transaction data/basic characteristic)
* I_LOGSYS = "Source System
* I_TRANSTRU = "Transfer structure between source system and BW
* I_OLTPSOURCE = "OLTP Source
* I_ISTYPE = "Type of requested data
* I_MODUS = '3' "Processing mode
* I_1STSCR = ' ' "Definition for which screen is displayed in the IS dialog
* I_R_NAVIGATOR = "Access to AWB Navigator
EXCEPTIONS
INTERNAL_ERROR = 1 LOCKING_ERROR = 2
IMPORTING Parameters details for RSAR_INFOSOURCE_MAINTAIN
I_ISOURCE - InfoSource
Data type: RSISOURCEOptional: Yes
Call by Reference: Yes
I_ISOSTYPE - BW Infosource type (transaction data/basic characteristic)
Data type: RSISOSTYPEOptional: Yes
Call by Reference: Yes
I_LOGSYS - Source System
Data type: RSSLOGSYSOptional: Yes
Call by Reference: Yes
I_TRANSTRU - Transfer structure between source system and BW
Data type: RSTRANSTRUOptional: Yes
Call by Reference: Yes
I_OLTPSOURCE - OLTP Source
Data type: RSOLTPSOURCEROptional: Yes
Call by Reference: Yes
I_ISTYPE - Type of requested data
Data type: RSREQUTYPEOptional: Yes
Call by Reference: Yes
I_MODUS - Processing mode
Data type: RS_MODUSDefault: '3'
Optional: No
Call by Reference: Yes
I_1STSCR - Definition for which screen is displayed in the IS dialog
Data type: RSIS1STSCRDefault: ' '
Optional: Yes
Call by Reference: Yes
I_R_NAVIGATOR - Access to AWB Navigator
Data type: IF_RSAWBN_NAVIGATOROptional: Yes
Call by Reference: Yes
EXCEPTIONS details
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LOCKING_ERROR - Locking Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RSAR_INFOSOURCE_MAINTAIN 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_isource | TYPE RSISOURCE, " | |||
| lv_internal_error | TYPE RSISOURCE, " | |||
| lv_i_isostype | TYPE RSISOSTYPE, " | |||
| lv_locking_error | TYPE RSISOSTYPE, " | |||
| lv_i_logsys | TYPE RSSLOGSYS, " | |||
| lv_i_transtru | TYPE RSTRANSTRU, " | |||
| lv_i_oltpsource | TYPE RSOLTPSOURCER, " | |||
| lv_i_istype | TYPE RSREQUTYPE, " | |||
| lv_i_modus | TYPE RS_MODUS, " '3' | |||
| lv_i_1stscr | TYPE RSIS1STSCR, " ' ' | |||
| lv_i_r_navigator | TYPE IF_RSAWBN_NAVIGATOR. " |
|   CALL FUNCTION 'RSAR_INFOSOURCE_MAINTAIN' "Editing of InfoSource |
| EXPORTING | ||
| I_ISOURCE | = lv_i_isource | |
| I_ISOSTYPE | = lv_i_isostype | |
| I_LOGSYS | = lv_i_logsys | |
| I_TRANSTRU | = lv_i_transtru | |
| I_OLTPSOURCE | = lv_i_oltpsource | |
| I_ISTYPE | = lv_i_istype | |
| I_MODUS | = lv_i_modus | |
| I_1STSCR | = lv_i_1stscr | |
| I_R_NAVIGATOR | = lv_i_r_navigator | |
| EXCEPTIONS | ||
| INTERNAL_ERROR = 1 | ||
| LOCKING_ERROR = 2 | ||
| . " RSAR_INFOSOURCE_MAINTAIN | ||
ABAP code using 7.40 inline data declarations to call FM RSAR_INFOSOURCE_MAINTAIN
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.| DATA(ld_i_modus) | = '3'. | |||
| DATA(ld_i_1stscr) | = ' '. | |||
Search for further information about these or an SAP related objects