Ansicht
Dokumentation

RSDRI_ODSO_UPDATE_RFC - Modifies Data Records in a Transactional ODS Object (RFC Version)

ABAP Short Reference   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Functionality

This function module receives the technical name of the DataStore object as a return parameter. Data is transferred in the generic table with the new/changed records.

A check is carried out to see whether the DataStore object is a DataStore object for direct writing. Then the data is converted from the 250-byte format to the structure of the DataStore object and inserted in the object. The number of data records inserted is returned (e_numrows). In the event of errors during this process, the relevant exception is returned.

Example

Notes

You must use the parameter I_RFCDATA_UC for data transfer, especially when packed data formats are used in the DataStore object (INT4, Float, ...), because of the fact that conversion errors may occur during the internal table transfer.

You must load the data into a table with the same structure of the DataStore object first. Then the data must be exported in the following way:

EXPORT rsdri = TO DATA BUFFER

rsdri is a constant that MUST be used. The objects in parenthesis are, on the one hand, the table that is filled with the data, and on the other hand, the XString variable to which the data is transferred.

When you want to change data in a DataStore object, you must transfer the values of all InfoObjects in the DataStore object structure, not only the data that has changed. Thus, each record in the DataStore object, uniquely identifiable by a primary key, is replaced by a new data record.

Table I_T_DATA has a flat, 250-byte long structure. Data is stored in the DATA field. If the structure of the DataStore object table is longer than 250 bytes, additional rows are required. The first row of the CONTINUATION field should be blank and all additional rows should be marked with an X.

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 that the structure of the data matches the structure of the DataStore object table 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. For example, you might implement no lock (except at database level) for quick changes to a small number of records but implement a lock for lengthy changes involving a large number of records.

Further technical notes:

The RFC-enabled function module RSDRI_ODSO_UPDATE_RFC uses the local function module RSDRD_SEL_UPDATE.

For remote calls, you should use the function module RSDRI_ODSO_UPDATE_RFC. For local calls, you should use the function module RSDRD_SEL_UPDATE, so that data conversions are saved before and after the call and also to improve performance.

Further information

Parameters

E_NUMROWS
I_AUTHORITY_CHECK
I_ODSOBJECT
I_RFCDATA_UC
I_TRIGGER_SMARTMERGE
I_T_DATA

Exceptions

ACTIVE_TABLE_NAME_NOT_FOUND
ARRAY_UPDATE_FAILED
DATA_TARGET_NOT_ODS
INTERNAL_ERROR
ODS_TYPE_NOT_TRANSACTIONAL
RECORD_KEY_DOES_NOT_EXIST

Function Group

RSDRI_ODSO

CPI1466 during Backup   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 3961 Date: 20240523 Time: 145301     sap01-206 ( 81 ms )