This transaction deletes the shipment statistics from the table older than the specified retention days.
This agent should be used whenever shipment statistics records need to be removed, such as after application server restart.
You can use purge codes pseudo-logic to analyze purges. If the following condition is met, the shipment statistics are picked up for purge:
The following are the attributes for this time-triggered transaction:
Attribute | Value |
---|---|
Base Transaction ID | PRG_SHIP_STATS |
Base Document Type | Order |
Base Process Type | Order Delivery |
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 Shipment Statistics 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_SHIPMENT_STATISTICS table may exist in multiple schemas. Runs the agent for the colony. |
The following are the statistics parameters for this transaction:
Parameter | Description |
---|---|
NumShipmentStatisticsPurged | Number of shipment statistics purged. |
For this transaction, the pending job count is the number of records that can be purged from the YFS_SHIPMENT_STATISTICS table.
None.
YFS_SHIPMENT_STATISTICS