This purge removes price list data from the system. This reduces the load on frequently accessed tables.
Any enterprise using the Console must schedule purge transactions.
You can use purge codes pseudo-logic to analyze purges. If the following condition is met, a price list is picked up for purge:
The following are the attributes for this time-triggered transaction:
Attribute | Value |
---|---|
Base Transaction ID | PRICELISTPRG |
Base Document Type | General |
Base Process Type | General |
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. |
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 a table may exist in multiple schemas. Runs the agent for the colony. |
The following statistics are tracked for this transaction:
Statistic Name | Description |
---|---|
NumPriceSetsPurged | Number of price sets purged. |
For this transaction, the pending job count is the number of records that can be purged from the YFS_Price_Set table.
None.
YFS_PRICE_SET table with VALID_TILL_DATE less than or equal to (CurrentDate - LeadDays)
YFS_PRICE_PROGRAM_DEFN
YFS_ITEM_PRICE_SET
YFS_ITEM_PRICE_SET_DTL