Ansicht
Dokumentation

RSDRI_ODSO_MODIFY_RFC - Modifies entries in a transactional ODS cube (RFC version)

CL_GUI_FRONTEND_SERVICES - Frontend Services   BAL_S_LOG - Application Log: Log header data  
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 either transferred in the generic table (i_t_data) or using the XSTRING parameter (i_rfcdata_uc). A check is carried out to see whether the DataStore object is a DataStore object for direct writing. Then, the data records transferred are converted to the structure of the DataStore object, and the data is inserted into 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 data transfer with the parameter I_RFCDATA_UC especially if you are dealing with packed data formats 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 structure of the DataStore object first. The data must then 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.

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 each additional row should be flagged with 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 modification of a small number of records but implement a lock for lengthy modifications involving a large number of records.

Further technical notes:

The RFC-enabled function module RSDRI_ODSO_MODIFY_RFC uses the local function module RSDRD_SEL_MODIFY.

For remote calls, you should use the function module RSDRI_ODSO_MODIFY_RFC. For local calls, you should use the function module RSDRD_SEL_MODIFY, 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_MODIFY_FAILED
DATA_TARGET_NOT_ODS
INTERNAL_ERROR
ODS_TYPE_NOT_TRANSACTIONAL
RECORD_KEY_ALREADY_EXISTS

Function Group

RSDRI_ODSO

BAL_S_LOG - Application Log: Log header data   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 3982 Date: 20240523 Time: 123318     sap01-206 ( 77 ms )