SAP RSPLS_DSO_ARRAY_DELETE Function Module for Deletes data records in a Planning-DSO
RSPLS_DSO_ARRAY_DELETE is a standard rspls dso array 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 Deletes data records in a Planning-DSO 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 rspls dso array delete FM, simply by entering the name RSPLS_DSO_ARRAY_DELETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSPLS_DSO_API
Program Name: SAPLRSPLS_DSO_API
Main Program: SAPLRSPLSALV
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSPLS_DSO_ARRAY_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 'RSPLS_DSO_ARRAY_DELETE'"Deletes data records in a Planning-DSO.
EXPORTING
I_DSO_OBJECT = "DSO Object
I_T_DELETE = "Records to Be Deleted
* I_TRIGGER_SMARTMERGE = RS_C_TRUE "Start Smart Merge for HANADB
IMPORTING
E_RECORDS = "Number of deleted records
EXCEPTIONS
DATA_TARGET_NOT_DSO = 1 DSO_TYPE_NOT_PLANNING = 2 ACTIVE_TABLE_NAME_NOT_FOUND = 3 ACTIVE_VIEW_NAME_NOT_FOUND = 4 RECORD_KEY_DOES_NOT_EXIST = 5 ARRAY_DELETE_FAILED = 6 INTERNAL_ERROR = 7
IMPORTING Parameters details for RSPLS_DSO_ARRAY_DELETE
I_DSO_OBJECT - DSO Object
Data type: RSDODSOBJECTOptional: No
Call by Reference: Yes
I_T_DELETE - Records to Be Deleted
Data type: STANDARD TABLEOptional: No
Call by Reference: Yes
I_TRIGGER_SMARTMERGE - Start Smart Merge for HANADB
Data type: RS_BOOLDefault: RS_C_TRUE
Optional: No
Call by Reference: Yes
EXPORTING Parameters details for RSPLS_DSO_ARRAY_DELETE
E_RECORDS - Number of deleted records
Data type: IOptional: No
Call by Reference: Yes
EXCEPTIONS details
DATA_TARGET_NOT_DSO - Data target is no DSO-Object
Data type:Optional: No
Call by Reference: Yes
DSO_TYPE_NOT_PLANNING - DSO-Object type is no Planning-DSO
Data type:Optional: No
Call by Reference: Yes
ACTIVE_TABLE_NAME_NOT_FOUND - Name of Active Table Not Found
Data type:Optional: No
Call by Reference: Yes
ACTIVE_VIEW_NAME_NOT_FOUND - Name of Active View not found
Data type:Optional: No
Call by Reference: Yes
RECORD_KEY_DOES_NOT_EXIST - At Least One of the Records Has a Key That Does Not Yet Exist
Data type:Optional: No
Call by Reference: Yes
ARRAY_DELETE_FAILED - Array-Delete failed
Data type:Optional: No
Call by Reference: Yes
INTERNAL_ERROR - Unexpected error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RSPLS_DSO_ARRAY_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_records | TYPE I, " | |||
| lv_i_dso_object | TYPE RSDODSOBJECT, " | |||
| lv_data_target_not_dso | TYPE RSDODSOBJECT, " | |||
| lv_i_t_delete | TYPE STANDARD TABLE, " | |||
| lv_dso_type_not_planning | TYPE STANDARD TABLE, " | |||
| lv_i_trigger_smartmerge | TYPE RS_BOOL, " RS_C_TRUE | |||
| lv_active_table_name_not_found | TYPE RS_BOOL, " | |||
| lv_active_view_name_not_found | TYPE RS_BOOL, " | |||
| lv_record_key_does_not_exist | TYPE RS_BOOL, " | |||
| lv_array_delete_failed | TYPE RS_BOOL, " | |||
| lv_internal_error | TYPE RS_BOOL. " |
|   CALL FUNCTION 'RSPLS_DSO_ARRAY_DELETE' "Deletes data records in a Planning-DSO |
| EXPORTING | ||
| I_DSO_OBJECT | = lv_i_dso_object | |
| I_T_DELETE | = lv_i_t_delete | |
| I_TRIGGER_SMARTMERGE | = lv_i_trigger_smartmerge | |
| IMPORTING | ||
| E_RECORDS | = lv_e_records | |
| EXCEPTIONS | ||
| DATA_TARGET_NOT_DSO = 1 | ||
| DSO_TYPE_NOT_PLANNING = 2 | ||
| ACTIVE_TABLE_NAME_NOT_FOUND = 3 | ||
| ACTIVE_VIEW_NAME_NOT_FOUND = 4 | ||
| RECORD_KEY_DOES_NOT_EXIST = 5 | ||
| ARRAY_DELETE_FAILED = 6 | ||
| INTERNAL_ERROR = 7 | ||
| . " RSPLS_DSO_ARRAY_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM RSPLS_DSO_ARRAY_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_trigger_smartmerge) | = RS_C_TRUE. | |||
Search for further information about these or an SAP related objects