Table of Contents

Search

  1. Preface
  2. Introduction to Services Integration Framework
  3. Setting Up the SIF SDK
  4. Request and Response Objects
  5. Transactions and Exception Handling
  6. ORS-Specific SIF API
  7. Asynchronous SIF Requests
  8. ORS-Specific JMS Event Messages
  9. Using Security Access Manager
  10. Using Dynamic Data Masking
  11. SIF API Reference
  12. Troubleshooting
  13. Appendix A: Identifiers
  14. Appendix B: Frequently Asked Questions

Services Integration Framework Guide

Services Integration Framework Guide

ExecuteBatchDelete

ExecuteBatchDelete

The ExecuteBatchDelete API calls the Delete batch job.

Request Parameters

The ExecuteBatchDelete request contains the following parameters:
TableName
Specifies the base object table name. Required.
SourceTableName
Specifies the name of the table that contains the list of cross-reference records to delete. Required.
Cascading
Determines if the batch delete is cascading. Set to
true
to run a cascading batch delete. Optional.
RecalculateBVT
Determines if the BVT is recalculated. Set to
true
to recalculate BVT after a batch delete. Optional.
OverrideHistory
Determines if the MDM Hub records the activity performed by the batch delete in the history tables. Set to
true
to record the history of deleted records in the history table. Set to
false
to ignore the value of PurgeHistory and write the last state of the data into the history tables when the record is deleted. Optional.
PurgeHistory
Determines if the MDM Hub deletes all non-merge history records related to deleted cross-reference record. You cannot retrieve the deleted history records. Set to
true
to delete the history records. Set to
false
to retain the history records. Optional.
If you set OverrideHistory to
true
and PurgeHistory to
true
, the batch delete removes all traces of the deleted records from the history tables.

Response Fields

The ExecuteBatchDelete API returns the following fields:
InteractionId
Contains the interaction ID.
Message
Contains a message regarding the status of the request.
RetCode
Contains the return code.

Usage Example

The following example runs the Delete batch job on a base object table:
SiperianClient sipClient = SiperianClient.newSiperianClient(new File( context.getTestPTTStartDir() + "siperian-client.properties" ) ); ExecuteBatchDeleteRequest req = new ExecuteBatchDeleteRequest(); req.setTableName(jobContext.getTableName()); // Base object table name req.setSourceTableName(jobContext.getSourceTableName()); // The table that contains a list of cross-reference records to delete ExecuteBatchDeleteResponse executed = (ExecuteBatchDeleteResponse) sipClient.process( req ); String errMessage = executed.getMessage(); int rc = executed.getRetCode();

0 COMMENTS

We’d like to hear from you!