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

Function RSAR_ASSIGN_LOGSYS 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_ASSIGN_LOGSYS'"Assignment of a source system to an InfoSource.
EXPORTING
I_ISOURCE = "InfoSource
I_LOGSYS = "Source System
I_ISOSTYPE = "BW Infosource type (transaction data/basic characteristic)
* I_NEWAWB = RS_C_FALSE "Flag for call awb
* I_OLTPSOURCE = "DataSource
* I_OSTYPE = "Type of OLTP Source that delivers master data
IMPORTING
E_SRCTYPE = "
E_TEXT = "
E_ICON = "
E_OLTPSOURCE = "Replicate Table for OLTP Sources in BW
E_ISTYPE = "Type of requested data
EXCEPTIONS
INVALID_LOGSYS = 1 ERR_BY_DATASRC = 2 ERR_IN_DIALOG = 3 ACTION_CANCELLED = 4
IMPORTING Parameters details for RSAR_ASSIGN_LOGSYS
I_ISOURCE - InfoSource
Data type: RSISOURCEOptional: No
Call by Reference: Yes
I_LOGSYS - Source System
Data type: RSSLOGSYSOptional: No
Call by Reference: Yes
I_ISOSTYPE - BW Infosource type (transaction data/basic characteristic)
Data type: RSISOSTYPEOptional: No
Call by Reference: Yes
I_NEWAWB - Flag for call awb
Data type: RS_BOOLDefault: RS_C_FALSE
Optional: Yes
Call by Reference: Yes
I_OLTPSOURCE - DataSource
Data type: ROOSOURCEROptional: Yes
Call by Reference: Yes
I_OSTYPE - Type of OLTP Source that delivers master data
Data type: RSOSTYPEOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RSAR_ASSIGN_LOGSYS
E_SRCTYPE -
Data type: RSA_SRCTYPEOptional: No
Call by Reference: Yes
E_TEXT -
Data type: RS_TXTLGOptional: No
Call by Reference: Yes
E_ICON -
Data type: RS_ICONOptional: No
Call by Reference: Yes
E_OLTPSOURCE - Replicate Table for OLTP Sources in BW
Data type: RSOLTPSOURCEOptional: No
Call by Reference: Yes
E_ISTYPE - Type of requested data
Data type: RSREQUTYPEOptional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID_LOGSYS -
Data type:Optional: No
Call by Reference: Yes
ERR_BY_DATASRC -
Data type:Optional: No
Call by Reference: Yes
ERR_IN_DIALOG -
Data type:Optional: No
Call by Reference: Yes
ACTION_CANCELLED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RSAR_ASSIGN_LOGSYS 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_e_srctype | TYPE RSA_SRCTYPE, " | |||
| lv_i_isource | TYPE RSISOURCE, " | |||
| lv_invalid_logsys | TYPE RSISOURCE, " | |||
| lv_e_text | TYPE RS_TXTLG, " | |||
| lv_i_logsys | TYPE RSSLOGSYS, " | |||
| lv_err_by_datasrc | TYPE RSSLOGSYS, " | |||
| lv_e_icon | TYPE RS_ICON, " | |||
| lv_i_isostype | TYPE RSISOSTYPE, " | |||
| lv_err_in_dialog | TYPE RSISOSTYPE, " | |||
| lv_i_newawb | TYPE RS_BOOL, " RS_C_FALSE | |||
| lv_e_oltpsource | TYPE RSOLTPSOURCE, " | |||
| lv_action_cancelled | TYPE RSOLTPSOURCE, " | |||
| lv_e_istype | TYPE RSREQUTYPE, " | |||
| lv_i_oltpsource | TYPE ROOSOURCER, " | |||
| lv_i_ostype | TYPE RSOSTYPE. " |
|   CALL FUNCTION 'RSAR_ASSIGN_LOGSYS' "Assignment of a source system to an InfoSource |
| EXPORTING | ||
| I_ISOURCE | = lv_i_isource | |
| I_LOGSYS | = lv_i_logsys | |
| I_ISOSTYPE | = lv_i_isostype | |
| I_NEWAWB | = lv_i_newawb | |
| I_OLTPSOURCE | = lv_i_oltpsource | |
| I_OSTYPE | = lv_i_ostype | |
| IMPORTING | ||
| E_SRCTYPE | = lv_e_srctype | |
| E_TEXT | = lv_e_text | |
| E_ICON | = lv_e_icon | |
| E_OLTPSOURCE | = lv_e_oltpsource | |
| E_ISTYPE | = lv_e_istype | |
| EXCEPTIONS | ||
| INVALID_LOGSYS = 1 | ||
| ERR_BY_DATASRC = 2 | ||
| ERR_IN_DIALOG = 3 | ||
| ACTION_CANCELLED = 4 | ||
| . " RSAR_ASSIGN_LOGSYS | ||
ABAP code using 7.40 inline data declarations to call FM RSAR_ASSIGN_LOGSYS
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_newawb) | = RS_C_FALSE. | |||
Search for further information about these or an SAP related objects