Kontakt

Ansicht
Dokumentation

RSDRI_ODSO_DELETE_RFC - Deletes Data Records in a Transactional ODS Object (RFC Version)

RSDRI_ODSO_DELETE_RFC - Deletes Data Records in a Transactional ODS Object (RFC Version)

Vendor Master (General Section)   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

This function module receives the technical name of the ODS object and possibly also some selection criteria (optional) as transfer parameters.

A check is carried out to see whether the DataStore object is a DataStore object for direct writing. After this, the relevant data records are deleted. The number of deleted data records is returned (e_numrows). In the event of errors during this process, the relevant exception is returned.

Example

Notes

I_ODSOBJECT must contain the technical name, not the description.

Table I_T_RANGE may only contain InfoObjects of the type Characteristic. It may not contain navigation attributes, display attributes, or key figures.

The following applies for table I_T_RANGE:

The conditions are formatted according to the usual ABAP select-option style.

The following values are valid in the SIGN field:

  • 'E' = Exclude
  • 'I' = Include

The following values are valid in the OPTION field:

  • 'EQ' = equal to
  • 'GE' = greater than or equal to
  • 'LE' = less than or equal to
  • 'GT' = greater than
  • 'LT' = less than
  • 'NE' = not equal to

Notee:

  • The operator 'CP' (contains pattern) is not supported.
  • Table I_T_RANGE must contain the technical name of the InfoObject in the IobjNm field for each entry, not one time only.
  • Conditions for the same InfoObject (regardless of their number and sequence in the table) are treated as OR operations. Conditions for different InfoObjects are treated as AND-bound. This means that each InfoObject has only one set of conditions.
  • 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 deletion of few records but implement a lock for lengthy deletion involving a large number of records.

Example

0CUSTOMER I EQ CUST-A
0CUSTOMER I EQ CUST-B
0MATERIAL I EQ MAT-1

The following conditions generate entries with:

0CUSTOMER = CUST-A oder CUST-B

and

0MATERIAL = MAT-1

Further technical notes:

The RFC-enabled function module RSDRI_ODSO_DELETE_RFC uses the local function module RSDRD_SEL_DELETION.

For remote calls, you should use the function module RSDRI_ODSO_DELETE_RFC. For local calls, you should use the function module RSDRD_SEL_DELETION, 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_DELETE_ALL
I_ODSOBJECT
I_TRIGGER_SMARTMERGE
I_T_RANGE
I_T_RANGE_EXT

Exceptions

CONFLICTING_DELETION_CRITERIA
DATA_TARGET_NOT_ODS
DELETE_FAILED
INTERNAL_ERROR
ODS_TYPE_NOT_TRANSACTIONAL

Function Group

RSDRI_ODSO

Addresses (Business Address Services)   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 4337 Date: 20240523 Time: 134208     sap01-206 ( 59 ms )