SAP RSAR_ISOURCE_TD_DELETE Function Module for Delete an InfoSource for transaction data
RSAR_ISOURCE_TD_DELETE is a standard rsar isource td 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 Delete an InfoSource for transaction data 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 isource td delete FM, simply by entering the name RSAR_ISOURCE_TD_DELETE 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_ISOURCE_TD_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 'RSAR_ISOURCE_TD_DELETE'"Delete an InfoSource for transaction data.
EXPORTING
I_ISOURCE = "InfoSource Name
* I_OBJVERS = RS_C_OBJVERS-ACTIVE "
* I_MODE = RS_C_FALSE "X: Delete without prompt
* I_NO_TRANSPORT = "No Transport Connection
EXCEPTIONS
CANCELLED = 1 UNKNOWN_ISOURCE = 2 NOT_ALLOWED = 3 OBJECT_LOCKED = 4 UNREACHABLE = 5 UNAUTHORIZED = 6 ABORTED = 7
IMPORTING Parameters details for RSAR_ISOURCE_TD_DELETE
I_ISOURCE - InfoSource Name
Data type: RSA_ISOURCEOptional: No
Call by Reference: No ( called with pass by value option)
I_OBJVERS -
Data type: RS_OBJVERSDefault: RS_C_OBJVERS-ACTIVE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MODE - X: Delete without prompt
Data type: RS_FLAGDefault: RS_C_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_NO_TRANSPORT - No Transport Connection
Data type: RS_BOOLOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CANCELLED - Abort by user input
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UNKNOWN_ISOURCE - InfoSource does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_ALLOWED - You may not delete
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_LOCKED - The InfoSource is locked
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UNREACHABLE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UNAUTHORIZED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ABORTED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSAR_ISOURCE_TD_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_cancelled | TYPE STRING, " | |||
| lv_i_isource | TYPE RSA_ISOURCE, " | |||
| lv_i_objvers | TYPE RS_OBJVERS, " RS_C_OBJVERS-ACTIVE | |||
| lv_unknown_isource | TYPE RS_OBJVERS, " | |||
| lv_i_mode | TYPE RS_FLAG, " RS_C_FALSE | |||
| lv_not_allowed | TYPE RS_FLAG, " | |||
| lv_object_locked | TYPE RS_FLAG, " | |||
| lv_i_no_transport | TYPE RS_BOOL, " | |||
| lv_unreachable | TYPE RS_BOOL, " | |||
| lv_unauthorized | TYPE RS_BOOL, " | |||
| lv_aborted | TYPE RS_BOOL. " |
|   CALL FUNCTION 'RSAR_ISOURCE_TD_DELETE' "Delete an InfoSource for transaction data |
| EXPORTING | ||
| I_ISOURCE | = lv_i_isource | |
| I_OBJVERS | = lv_i_objvers | |
| I_MODE | = lv_i_mode | |
| I_NO_TRANSPORT | = lv_i_no_transport | |
| EXCEPTIONS | ||
| CANCELLED = 1 | ||
| UNKNOWN_ISOURCE = 2 | ||
| NOT_ALLOWED = 3 | ||
| OBJECT_LOCKED = 4 | ||
| UNREACHABLE = 5 | ||
| UNAUTHORIZED = 6 | ||
| ABORTED = 7 | ||
| . " RSAR_ISOURCE_TD_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM RSAR_ISOURCE_TD_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) | = RS_C_OBJVERS-ACTIVE. | |||
| DATA(ld_i_mode) | = RS_C_FALSE. | |||
Search for further information about these or an SAP related objects