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

Parameter Reference Type Length Default Optional Text
I_DELETE_ALL BAPI6116XX-ALLINFOOBJECTS C 1 X Delete All Table Entries
I_ODSOBJECT BAPI6116-ODSOBJECT C 30 ODS Object

Parameter Reference Type Length Text
E_NUMROWS BAPI6116XX-NUMROWS I 4 Number of deleted records

Parameter Reference Length Optional Text
I_T_RANGE BAPI6116SLIO 123 X Selection Criteria for InfoObjects

Exception Text
CONFLICTING_DELETION_CRITERIA Conflict between "Delete All" and "Selection Criteria"
DATA_TARGET_NOT_ODS Data Target Is Not an ODS Object
DELETE_FAILED Deletion Has Failed
INTERNAL_ERROR Unexpected error
ODS_TYPE_NOT_TRANSACTIONAL ODS Object Type Is Not "Transactional"

Functionality
This function module receives the technical name of the ODS object andpossibly also some selection criteria (optional) as transfer parameters.
A check is carried out to see whether the DataStore object is aDataStore object for direct writing. After this, the relevant datarecords are deleted. The number of deleted data records is returned(e_numrows). In the event of errors during this process, the relevantexception is returned.

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 keyfigures.
The following applies for table I_T_RANGE:
The conditions are formatted according to the usual ABAP select-optionstyle.
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 fordifferent InfoObjects are treated as AND-bound. This means that eachInfoObject 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. Forexample, you might implement no lock (except at database level) forquick deletion of few records but implement a lock for lengthy deletioninvolving 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 localfunction module RSDRD_SEL_DELETION.
            For remote calls, you should use the function moduleRSDRI_ODSO_DELETE_RFC. For local calls, you should use the functionmodule RSDRD_SEL_DELETION, so that data conversions are saved before andafter the call and also to improve performance.

            Description
            Technical name of the DataStore object.