SAP RSAOS_OLTPSOURCE_MAPPING_SAVE Function Module for saving the mappings OltpSource <-> InfoSource

Search SAP Function Modules

RSAOS_OLTPSOURCE_MAPPING_SAVE is a standard rsaos oltpsource mapping save SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for saving the mappings OltpSource <-> 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 rsaos oltpsource mapping save FM, simply by entering the name RSAOS_OLTPSOURCE_MAPPING_SAVE into the relevant SAP transaction such as SE37 or SE38.

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

Function RSAOS_OLTPSOURCE_MAPPING_SAVE 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 'RSAOS_OLTPSOURCE_MAPPING_SAVE'"saving the mappings OltpSource <-> InfoSource
  EXPORTING
*  I_S_ISOSMAP =  "Mapping between InfoSources and OLTP Sources
*  I_SEGMENT_AS_HEADER =  "Boolean
*  I_T_OSFIELDMAP =  "Feld <-> InfoObject Mapping of an OLTP Source
*  I_SEGID =  "Segment ID
*  I_SEGID_IS =  "Segment-ID of the InfoSource
*  I_TX_OSSEGMAP =  "Mapping for Segments of a DataSource
*  I_SAVE_IN_VERSION =  "Object version in which the OltpSource is to be saved (D = shadow)
*  I_SAVE_DESPITE_WARNING =  "
*  I_NO_TRANSPORT = RSAOS_C_FLAG-OFF "Boolean
*  I_NO_AUTHORITY =  "No authorization check

 IMPORTING
   E_T_MESSAGES =  "

EXCEPTIONS
   TRANSPORT_ERROR = 1    INCONSISTENT = 2    INTERNAL_ERROR = 3 

.

IMPORTING Parameters details for RSAOS_OLTPSOURCE_MAPPING_SAVE

I_S_ISOSMAP - Mapping between InfoSources and OLTP Sources

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

I_SEGMENT_AS_HEADER - Boolean

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

I_T_OSFIELDMAP - Feld <-> InfoObject Mapping of an OLTP Source

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

I_SEGID - Segment ID

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

I_SEGID_IS - Segment-ID of the InfoSource

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

I_TX_OSSEGMAP - Mapping for Segments of a DataSource

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

I_SAVE_IN_VERSION - Object version in which the OltpSource is to be saved (D = shadow)

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

I_SAVE_DESPITE_WARNING -

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

I_NO_TRANSPORT - Boolean

Data type: RS_BOOL
Default: RSAOS_C_FLAG-OFF
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_NO_AUTHORITY - No authorization check

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

EXPORTING Parameters details for RSAOS_OLTPSOURCE_MAPPING_SAVE

E_T_MESSAGES -

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

EXCEPTIONS details

TRANSPORT_ERROR -

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

INCONSISTENT -

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

INTERNAL_ERROR -

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

Copy and paste ABAP code example for RSAOS_OLTPSOURCE_MAPPING_SAVE 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.

ABAP code using 7.40 inline data declarations to call FM RSAOS_OLTPSOURCE_MAPPING_SAVE

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