Contract Maintenance and Purging (contract_purge_job)
Module Name |
contract_purge_job |
Description |
Contract Maintenance and Purging |
Functional Area |
Contracts |
Module Type |
Admin - Ad hoc |
Module Technology |
Background Processing |
Catalog ID |
N/A |
Wrapper Script |
b8dwrap.ksh |
Design Overview
This background job is composed of two-step processing. It will have a threading assignment and a business logic processing.
Thread assignment program will filter eligible records from contract header table based on its purge criteria from system parameter settings. The Order History Months parameter will determine number of months a contract elapsed in the system comparing current date and contract's status date. Contracts are also considered for deletion when they remained in cancelled, worksheet, submitted, or complete status for a user-defined number of months without any orders and contacts marked for deletion. These records are chunked and Thread ID is assigned for each. They will be stored temporarily in a staging table.
The Business logic program will process all records from the staging table. Using bulk processing, this program will mark contracts that have reached their end date to completed (for types A and B) or review status (for types C and D). It will free up and clean the staging table afterwards. There is a STOP ON NEXT feature in bulk processing (through a loop) where Administrators can stop this batch with a flip of this indicator.
Key Tables Affected
Table 7-1 Key Tables Affected
Table | Select | Insert | Update | Delete |
---|---|---|---|---|
PURGE_CONFIG_OPTIONS |
Yes |
No |
No |
No |
RMS_BATCH_STATUS |
Yes |
No |
No |
No |
B8D_PROCESS_CONFIG |
Yes |
No |
No |
No |
JOB_AUDIT_LOGS |
No |
Yes |
No |
No |
B8D_CONTRACT_MAIN_PURGE_STG |
Yes |
Yes |
No |
Yes |
CONTRACT_HEADER |
Yes |
No |
Yes |
Yes |
CONTRACT_DETAIL |
No |
No |
No |
Yes |
CONTRACT_COST |
No |
No |
No |
Yes |
ORDHEAD |
Yes |
No |
No |
No |