This purge deletes negotiation history data from the system. This reduces the load on frequently accessed tables. It purges data from the order negotiation history tables.
You can use purge codes pseudo-logic to analyze purges. If the following condition is met, a negotiation is picked up for history purge:
Any enterprise using the Console must schedule purge transactions.
The following are the attributes for this time-triggered transaction:
Attribute | Value |
---|---|
Base Transaction ID | NEGOTIATIONHISTPRG |
Base Document Type | Order |
Base Process Type | Order Negotiation |
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 Negotiation History 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 a table may exist in multiple schemas. Runs the agent for the colony. |
The following statistics are tracked for this transaction:
Statistic Name | Description |
---|---|
NumNegotiationHistoriesPurged | Number of negotiation histories purged. |
For this transaction, the pending job count is the number of records that can be purged from the YFS_Negotiation_Hdr_H table.
None.
YFS_AUDIT
YFS_NEGOTIATION_HDR_H
YFS_NEGOTIATION_LINE_H
YFS_RESPONSE_H
YFS_RESPONSE_HDR_H
YFS_RESPONSE_LINE_H
YFS_RESPONSE_LINE_DTL_H