SAP Function RSDRI_ODSO_MODIFY - Modifies Entries in a Transactional ODS Cube

Parameter Reference Type Length Default Optional Text
I_ODSOBJECT RSDODSOBJECT C 30 ODS Object
I_T_MODIFY STANDARD TABLE 0 Table of Records to Be Inserted/Modified

Parameter Reference Type Length Text
E_RECORDS I I 4 Number of Inserted/Modifed Records

Exception Text
ACTIVE_TABLE_NAME_NOT_FOUND Name of Active Table Not Found
ARRAY_MODIFY_FAILED Modification of Array Failed
DATA_TARGET_NOT_ODS Data Target Is Not an ODS Object
INTERNAL_ERROR Unexpected Error
ODS_TYPE_NOT_TRANSACTIONAL ODS Object Type Is Not "Transactional"
RECORD_KEY_ALREADY_EXISTS Key for at Least One Record Conflicts with a Unique Secondary Index

Functionality
This function module receives the technical name of the DataStore objectas a return parameter. Data is transferred in a table with the samestructure as the active table of the DataStore object.
A check is carried out to see whether the DataStore object is aDataStore object for direct writing. The number of data records insertedis returned (e_numrows). In the event of errors during this process, therelevant exception is returned.

Notes
Data is either accepted in full or rejected in full. For this reason,you must ensure that the data is correct and in particular ensure thatthe structure of the data matches the structure of the DataStore objecttable exactly. Incorrect data or structures may result in SQL errors,exceptions, or in data being transferred in the wrong format.

  • Since a DataStore object for direct writing is often supplied with new
    • data, lock management must be implemented in the calling object. Forexample, you might implement no lock (except at database level) forquick modifications of a small number of records but implement a lockfor lengthy modifications involving a large number of records.

    Further information

    Description
    Technical name of the DataStore object.