SAP RSA1_OLTPSOURCE_DELETE Function Module for









RSA1_OLTPSOURCE_DELETE is a standard rsa1 oltpsource delete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 rsa1 oltpsource delete FM, simply by entering the name RSA1_OLTPSOURCE_DELETE into the relevant SAP transaction such as SE37 or SE38.

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



Function RSA1_OLTPSOURCE_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 'RSA1_OLTPSOURCE_DELETE'"
EXPORTING
I_OLTPSOURCE = "
* I_OBJVERS = 'A' "
* I_DEVCLASS = "
* I_REQUEST = "
* I_NO_TRANS = ' ' "
* I_NO_AUTHORITY = RSAOT_C_FLAG-ON "

IMPORTING
E_REQUEST = "
E_DEVCLASS = "
E_T_MESSAGES = "

EXCEPTIONS
TRANSPORT_ERROR = 1 FAILED = 2 NO_PERMISSION = 3 ERROR_OCCURED = 4
.



IMPORTING Parameters details for RSA1_OLTPSOURCE_DELETE

I_OLTPSOURCE -

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

I_OBJVERS -

Data type: RSAOT_OBJVERS
Default: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_DEVCLASS -

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

I_REQUEST -

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

I_NO_TRANS -

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

I_NO_AUTHORITY -

Data type: RSAOT_FLAG
Default: RSAOT_C_FLAG-ON
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for RSA1_OLTPSOURCE_DELETE

E_REQUEST -

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

E_DEVCLASS -

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

E_T_MESSAGES -

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

EXCEPTIONS details

TRANSPORT_ERROR -

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

FAILED -

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

NO_PERMISSION -

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

ERROR_OCCURED -

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

Copy and paste ABAP code example for RSA1_OLTPSOURCE_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_e_request  TYPE RSAOT_REQUEST, "   
lv_i_oltpsource  TYPE RSAOT_OLTPSOURCE, "   
lv_transport_error  TYPE RSAOT_OLTPSOURCE, "   
lv_failed  TYPE RSAOT_OLTPSOURCE, "   
lv_i_objvers  TYPE RSAOT_OBJVERS, "   'A'
lv_e_devclass  TYPE RSAOT_DEVC, "   
lv_i_devclass  TYPE RSAOT_DEVC, "   
lv_e_t_messages  TYPE RSAOT_T_MESSAGES, "   
lv_no_permission  TYPE RSAOT_T_MESSAGES, "   
lv_i_request  TYPE RSAOT_REQUEST, "   
lv_error_occured  TYPE RSAOT_REQUEST, "   
lv_i_no_trans  TYPE RSAOT_FLAG, "   ' '
lv_i_no_authority  TYPE RSAOT_FLAG. "   RSAOT_C_FLAG-ON

  CALL FUNCTION 'RSA1_OLTPSOURCE_DELETE'  "
    EXPORTING
         I_OLTPSOURCE = lv_i_oltpsource
         I_OBJVERS = lv_i_objvers
         I_DEVCLASS = lv_i_devclass
         I_REQUEST = lv_i_request
         I_NO_TRANS = lv_i_no_trans
         I_NO_AUTHORITY = lv_i_no_authority
    IMPORTING
         E_REQUEST = lv_e_request
         E_DEVCLASS = lv_e_devclass
         E_T_MESSAGES = lv_e_t_messages
    EXCEPTIONS
        TRANSPORT_ERROR = 1
        FAILED = 2
        NO_PERMISSION = 3
        ERROR_OCCURED = 4
. " RSA1_OLTPSOURCE_DELETE




ABAP code using 7.40 inline data declarations to call FM RSA1_OLTPSOURCE_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_objvers) = 'A'.
 
 
 
 
 
 
 
DATA(ld_i_no_trans) = ' '.
 
DATA(ld_i_no_authority) = RSAOT_C_FLAG-ON.
 


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!