This purge removes import table 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 conditions are met, the YFS_IMPORT table is picked up for 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 | IMPORTTBLPRG |
Base Document Type | General |
Base Process Type | General |
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:
|
BatchDelete | Required. The method by which all records are deleted from
the table. 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. |
CollectPendingJobs | If this parameter is set to "N", the agent does not collect information on the pending jobs for this monitor. This pending job information is used for monitoring the monitor in the System Management Console. |
ColonyID | Required in a multi schema deployment where the YFS_IMPORT table may exist in multiple schemas. Runs the agent for the colony. |
The following statistics are tracked for this transaction:
Statistic Name | Description |
---|---|
NumImportsPurged | Number of import tables purged. |
For this transaction the pending job count is the number of records that can be purged from the YFS_Import table.
None.
YFS_IMPORT