Picklist purge
This purge picks up all picklists that have been existing for a period greater than the retention days specified in the criteria parameters and those that do not have any shipments.
Any enterprise using the Console must schedule purge transactions.
You can use purge codes pseudo-logic to analyze purges. If the following conditions are met, a picklist is picked up for purge:
- The picklist should exist for more than the specified retention period.
- The picklist should not be associated with any shipment.
All shipments associated with the picklists should have been purged before running this purge agent.
Attributes
The following are the attributes for this time-triggered transaction:
Attribute | Value |
---|---|
Base Transaction ID | PICKLISTPRG |
Base Document Type | Order |
Base Process Type | Order Delivery |
Abstract Transaction | No |
APIs Called | None |
User Exits Called | YFSBeforePurgeUE |
Criteria parameters
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. 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 sharded deployment where the YFS_PICK_LIST table may exist in multiple schemas. Runs the agent for the colony. |
Statistics tracked
The following statistics are tracked for this transaction:
Statistic Name | Description |
---|---|
NumPickListsPurged | Number of picklists purged. |
Pending job count
For this transaction, the pending job count is the number of records that can be purged from the YFS_PICK_LIST table.
Events raised
None.
Tables purged
YFS_PICK_LIST