RSPLS_DSO_UPDATE SAP Function module - Modifies data records in a Planning-DSO

RSPLS_DSO_UPDATE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name RSPLS_DSO_UPDATE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: RSPLS_DSO_API
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM RSPLS_DSO_UPDATE - RSPLS DSO UPDATE

CALL FUNCTION 'RSPLS_DSO_UPDATE' "Modifies data records in a Planning-DSO
  EXPORTING
    i_dso_object =              " rsdodsobject  DSO Object
    i_t_update =                " standard table  Table of Records to Be Changed
    i_trigger_smartmerge = RS_C_TRUE  " rs_bool  Start Smart Merge for HANADB
  IMPORTING
    e_records =                 " i             Number of Modified Records
  EXCEPTIONS
    DATA_TARGET_NOT_DSO = 1     "               Data target is no DSO-Object
    DSO_TYPE_NOT_PLANNING = 2   "               DSO-Object is no Planning-DSO
    ACTIVE_TABLE_NAME_NOT_FOUND = 3  "          Name of Active Table Not Found
    ACTIVE_VIEW_NAME_NOT_FOUND = 4  "           Name of active view not found
    RECORD_KEY_DOES_NOT_EXIST = 5  "            At Least One of the Data Records Has a Key That Already Exists
    ARRAY_UPDATE_FAILED = 6     "               Arry-Update failed
    INTERNAL_ERROR = 7          "               Unexpected error
    .  "  RSPLS_DSO_UPDATE

ABAP code example for Function Module RSPLS_DSO_UPDATE

The ABAP code below is a full code listing to execute function module RSPLS_DSO_UPDATE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_records  
 
 TYPE I
.


DATA(ld_i_dso_object) = 'Check type of data required'.

DATA(ld_i_t_update) = 'Check type of data required'.

DATA(ld_i_trigger_smartmerge) = 'Check type of data required'.
.

CALL FUNCTION 'RSPLS_DSO_UPDATE'
  EXPORTING
    i_dso_object =               ld_i_dso_object
    i_t_update =                 ld_i_t_update
    i_trigger_smartmerge =       ld_i_trigger_smartmerge
  IMPORTING
    e_records =                  ld_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_UPDATE_FAILED =        6
    INTERNAL_ERROR =             7
    .  "  RSPLS_DSO_UPDATE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 6. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 7. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_e_records
 
 TYPE I ,
ld_i_dso_object
 
 TYPE RSDODSOBJECT ,
ld_i_t_update
 
 TYPE STANDARD TABLE ,
ld_i_trigger_smartmerge
 
 TYPE RS_BOOL .


ld_i_dso_object = 'Check type of data required'.
ld_i_t_update = 'Check type of data required'.
ld_i_trigger_smartmerge = 'Check type of data required'.