This transaction uses the YFS_EXECUTION_EXCEPTION_AUDIT table to find the audits that can be purged, and then deletes them.
The following are the attributes for this time-triggered transaction:
Attribute | Value |
---|---|
Base Transaction ID | EXECEXECPAUDITPURGE |
Base Document Type | General |
Base Process Type | TASK_EXECUTION |
Abstract Transaction | No |
APIs Called | None |
User Exits Called | None |
The following are the criteria parameters for this transaction:
Parameter | Description |
---|---|
Action | Required. Triggers the transaction. If left blank, it defaults to Get, the only valid value. |
Number of Records To Buffer | Optional. Number of records to retrieve and process at one time. If left blank or specified as 0 (zero), it defaults to 5000. |
Live | Optional.
Mode in which to run. Defaults to N.
|
PurgeCode | Required. Cannot be modified. Used for internal calculations, such as determining retention days. Corresponds with the PurgeCode used in the Business Rules purge criteria. |
OrganizationCode | Optional. Organization for which the Execution Exception purge needs to be run. |
AgentCriteriaGroup | Optional. Used to classify nodes. This value can be accepted
by WMS time-triggered transactions that only perform their tasks on
nodes with a matching node transactional velocity value.
Valid values are LOW, HIGH, and any additional values defined by the Hub from Sterling Application Platform > System Administration > Agent Criteria Groups. |
ColonyID | Required in a multischema deployment where the YFS_EXECUTION_EXCEPTION_AUDIT table may exist in multiple schemas. Runs the agent for the colony. |
The following statistics are tracked for this transaction:
Statistic Name | Description |
---|---|
NumExceptionAuditsPurged | Number of Execution Exception Audits purged. |
For a transaction, the Pending Job Count is the number of records that can be purged from the YFS_EXECUTION_EXCEPTION_AUDIT table.
None.
YFS_EXECUTION_EXCEPTION_AUDIT