Table of Contents

Search

  1. Abstract
  2. Supported Versions
  3. Writing Custom Scripts to Run Batch Jobs

Writing Custom Scripts to Execute Batch Jobs

Writing Custom Scripts to Execute Batch Jobs

Parameters

Parameters

Parameter
Description
IN_BO_TABLE_NAME
Name of the table that contains the list of base objects to delete.
IN_XREF_LIST_TO_BE_DELETED
Name of the table that contains the list of XREFs to delete.
IN_RECALCULATE_BVT_IND
If set to 1, recalculates BVT following base object and/or XREF delete.
IN_ALLOW_CASCADE_DELETE_IND
If set to 1, specifies that when records in the parent object are deleted, Hub Delete also removes the affected records in the child base object. Hub Delete checks each child base object table for related data that should be deleted given the removal of the parent base object record.
IN_CASCADE_CHILD_SYSTEM_XREF
This parameter is not supported. Leave the value for this parameter as the default, which is 0, when executing the procedure.
IN_OVERRIDE_HISTORY_IND
If set to 1, Hub Delete does not write to history tables when deleting. If you set IN_OVERRIDE_HISTORY_IND=1 and set IN_PURGE_HISTORY_IND=1, then Hub Delete removes the deleted records from the history tables.
IN_PURGE_HISTORY_IND
If set to 1, Hub Delete will remove all history records related to deleted XREF records that are not related to merge history. You cannot retrieve the deleted XREF record if required.
If set to 0, Hub Delete will retain all history records related to deleted XREF records that are not related to merge history. You can retrieve the deleted XREF record if required.
Default is 0.
IN_USER_NAME
Name of the HUB user who executes Batch Delete. The default value is
admin
.
IN_ALLOW_COMMIT_IND
If set to 1, Hub Delete commits or rolls back all changes. If set to 0, Hub Delete does not commit or roll back changes; user must explicitly commit or roll back changes.

0 COMMENTS

We’d like to hear from you!