This purge removes order status audit data from the system. This reduces the load on frequently accessed tables.
You can use purge codes pseudo-logic to analyze purges. If the following condition is met, an order status audit is picked up for history purge:
Any enterprise using the Console must schedule purge transactions.
This transaction needs to be run after negotiation is completed.
The following are the attributes for this time-triggered transaction:
Attribute | Value |
---|---|
Base Transaction ID | STATUSAUDITPRG |
Base Document Type | Order |
Base Process Type | Order Fulfillment |
Abstract Transaction | No |
APIs Called | None |
User Exits Called | YFSBeforePurgeUE |
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. |
EnterpriseCode | Optional. Enterprise for which the Order Status Audit Purge needs to be run. If not passed, then all enterprises are monitored. |
Live | Optional. Mode in which to run. Valid values are:
|
PurgeCode | Required. Cannot be modified. Used for internal calculations, such as determining retention days. Corresponds with the PurgeCode used in Business Rules Purge Criteria. |
ColonyID | Required in a multi schema deployment where the YFS_STATUS_AUDIT Table may exist in multiple schemas. Runs the agent for the colony. |
The following statistics are tracked for this transaction:
Statistic Name | Description |
---|---|
NumStatusAuditsPurged | Number of status audits purged. |
Pending Job Count
For this transaction, the pending job count is the number of records that can be purged from the YFS_Status_Audit table.
None.
YFS_STATUS_AUDIT