SAP RSAOS_OLTPSOURCE_MAP_DELETE Function Module for Deleting a OltpSource









RSAOS_OLTPSOURCE_MAP_DELETE is a standard rsaos oltpsource map delete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Deleting a OltpSource 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 map delete FM, simply by entering the name RSAOS_OLTPSOURCE_MAP_DELETE 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_MAP_DELETE 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_MAP_DELETE'"Deleting a OltpSource
EXPORTING
I_OLTPSOURCE = "OLTP Source
I_LOGSYS = "Source System
I_OBJVERS = "Object Version
* I_NO_DEL_MAPPING = RS_C_TRUE "an existing mapping can be kept
* I_NO_DEL_FIELD_IOBJ_MAP = RS_C_TRUE "Do not delete field mapping
* I_NO_DEL_SEGMENT_MAP = RS_C_TRUE "Do not delete segment mapping
* I_NO_DEL_IPAK = RS_C_FALSE "Do not delete Infopackages
* I_NO_TRANSPORT = RS_C_FALSE "# # # # No transport connection
* I_NO_AUTHORITY = RS_C_FALSE "# # # # No check of authority

IMPORTING
E_T_MESSAGES = "

EXCEPTIONS
NOT_EXIST = 1 LOCKED = 2 TRANSPORT_ERROR = 3
.



IMPORTING Parameters details for RSAOS_OLTPSOURCE_MAP_DELETE

I_OLTPSOURCE - OLTP Source

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

I_LOGSYS - Source System

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

I_OBJVERS - Object Version

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

I_NO_DEL_MAPPING - an existing mapping can be kept

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

I_NO_DEL_FIELD_IOBJ_MAP - Do not delete field mapping

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

I_NO_DEL_SEGMENT_MAP - Do not delete segment mapping

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

I_NO_DEL_IPAK - Do not delete Infopackages

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

I_NO_TRANSPORT - # # # # No transport connection

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

I_NO_AUTHORITY - # # # # No check of authority

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

EXPORTING Parameters details for RSAOS_OLTPSOURCE_MAP_DELETE

E_T_MESSAGES -

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

EXCEPTIONS details

NOT_EXIST - OltpSource does not exist

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

LOCKED -

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

TRANSPORT_ERROR -

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

Copy and paste ABAP code example for RSAOS_OLTPSOURCE_MAP_DELETE 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_not_exist  TYPE STRING, "   
lv_e_t_messages  TYPE RSAOS_T_MESSAGES, "   
lv_i_oltpsource  TYPE RSOLTPSOURCER, "   
lv_locked  TYPE RSOLTPSOURCER, "   
lv_i_logsys  TYPE RSSLOGSYS, "   
lv_i_objvers  TYPE RSOBJVERS, "   
lv_transport_error  TYPE RSOBJVERS, "   
lv_i_no_del_mapping  TYPE RS_BOOL, "   RS_C_TRUE
lv_i_no_del_field_iobj_map  TYPE RS_BOOL, "   RS_C_TRUE
lv_i_no_del_segment_map  TYPE RS_BOOL, "   RS_C_TRUE
lv_i_no_del_ipak  TYPE RS_BOOL, "   RS_C_FALSE
lv_i_no_transport  TYPE RS_BOOL, "   RS_C_FALSE
lv_i_no_authority  TYPE RS_BOOL. "   RS_C_FALSE

  CALL FUNCTION 'RSAOS_OLTPSOURCE_MAP_DELETE'  "Deleting a OltpSource
    EXPORTING
         I_OLTPSOURCE = lv_i_oltpsource
         I_LOGSYS = lv_i_logsys
         I_OBJVERS = lv_i_objvers
         I_NO_DEL_MAPPING = lv_i_no_del_mapping
         I_NO_DEL_FIELD_IOBJ_MAP = lv_i_no_del_field_iobj_map
         I_NO_DEL_SEGMENT_MAP = lv_i_no_del_segment_map
         I_NO_DEL_IPAK = lv_i_no_del_ipak
         I_NO_TRANSPORT = lv_i_no_transport
         I_NO_AUTHORITY = lv_i_no_authority
    IMPORTING
         E_T_MESSAGES = lv_e_t_messages
    EXCEPTIONS
        NOT_EXIST = 1
        LOCKED = 2
        TRANSPORT_ERROR = 3
. " RSAOS_OLTPSOURCE_MAP_DELETE




ABAP code using 7.40 inline data declarations to call FM RSAOS_OLTPSOURCE_MAP_DELETE

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_no_del_mapping) = RS_C_TRUE.
 
DATA(ld_i_no_del_field_iobj_map) = RS_C_TRUE.
 
DATA(ld_i_no_del_segment_map) = RS_C_TRUE.
 
DATA(ld_i_no_del_ipak) = RS_C_FALSE.
 
DATA(ld_i_no_transport) = RS_C_FALSE.
 
DATA(ld_i_no_authority) = RS_C_FALSE.
 


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!