| Oracle® Retail Store Inventory Management Operations Guide Release 15.0 E65670-03 |
|
 Previous |
 Next |
| Oracle® Retail Store Inventory Management Operations Guide Release 15.0 E65670-03 |
|
Previous |
Next |
Data purging is based upon a data-retention schedule whereupon all data existing prior to the computed date are purged. The data within this timeframe must meet data integrity constraints as well as functional requirements.
SIM Data purging programs are meant to provide the basic implementation of logical selection of sets of data based on functional requirement and data retention periods. The data retention periods are defined in SIM system configuration table. Logical sets of data may exist in multiple tables.
With this assumption, SIM purge shell scripts execute the java EJB which calls the oracle PL/SQL stored procedures to delete the records. The purging logics are resides in PL/SQL storedprocedures, Customer may choose the their preferred purging strategy and implement their ownpurging implementation.
Relevant progress messages are logged with regard to purge batch program runtime information. The location of sim batch log and logging levels can be configured in log4j.xml file which is located in <sim_batch_location>/resources/conf/log4j.xml.
The user running the batch process must have write permission on the directory into which the sim batch log is written, or the batch process will not run. If it is not acceptable to give the batch user permission for the default log directory, log4j.xml must be configured to use a different directory.
|
Note: The purge PL/SQL programs may save the detailed exceptions into PURGE_ERROR_LOG table. DBA needs to purge the data periodically. |
The following section summarizes SIM's data Purge programs and includes both an overview of each purge program business functionality, and scheduling notes.
Table 5-1 Data Purge Program List and Dependencies
| Purge Name | Description | Dependencies |
|---|---|---|
|
PurgeAdHocStockCount |
Deletes AD HOC stock counts with a status of in progress which schedule date was X days in the past. |
No dependencies |
|
PurgeAll |
Deletes records from the SIM application that meet certain business criteria. |
No dependencies |
|
PurgeAudits |
This batch process deletes audits that have been held in the system for a number of system defined days. |
No dependencies |
|
PurgeBatchImpExp |
This batch process deletes batch import export records that have been held in the system for a number of system defined days. |
No dependencies |
|
PurgeClosedTransfers |
This batch deletes closed transfer documents and related shipments. |
No dependencies |
|
PurgeCompletedUINDetail |
This batch deletes completed UIN Detail records that have been held in the system for a number of system defined days. |
No dependencies |
|
PurgeDeletedUsers |
This batch program deletes users that have a status of deleted and have been held in the system for a number of system defined days. |
No dependencies |
|
PurgeDSDReceivings |
This batch process deletes the Direct Store Delivery receiving completed. canceled Direct Store Delivery receiving records, and their associated closed Purchase Order records. |
No dependencies |
|
PurgeFulfillmentOrders |
This batch deletes closed fulfillment order records. |
No dependencies |
|
PurgeInvalidUserRoles |
This batch program removes all expired or orphaned roles from the users in the system. |
No dependencies |
|
PurgeInventoryAdjustments |
This batch process deletes inventory adjustments that have been held in the system for a number of system defined days. |
No dependencies |
|
PurgeInventoryAdjustTemplate |
This batch deletes inventory adjustment templates that have been held in the system for a number of system defined days. |
No dependencies |
|
PurgeItem |
This batch program deletes the items that are in deleted status (D). |
No dependencies |
|
PurgeItemBaskets |
This batch process deletes item baskets. |
No dependencies |
|
PurgeItemHierarchy |
This batch deletes unused and deleted item hierarchies. |
No dependencies |
|
PurgeItemPrice |
This batch deletes expired or deleted item prices. |
No dependencies |
|
PurgeItemRequests |
This batch process deletes item requests that have been held in the system for a number of system defined days. |
No dependencies |
|
PurgeItemTickets |
This batch process deletes canceled item tickets that have been held in the system for a number of system defined days.. |
No dependencies |
|
PurgeLockings |
This batch process deletes lockings that have been held in the system for a number of system defined days. |
No dependencies |
|
PurgePriceChangesWorksheet |
This batch deletes completed/rejected price change work sheet records. |
No dependencies |
|
PurgePriceHistories |
This batch process deletes price histories. |
No dependencies |
|
PurgePurchaseOrders |
This batch process deletes closed purchase order records. |
No dependencies |
|
PurgeRelatedItems |
This batch will delete related items. |
No dependencies |
|
PurgeResolvedUINProblems |
This batch process deletes resolved item serial number problems. |
No dependencies |
|
PurgeSalesPosting |
This purges the sales, returns, void sales and void returns transaction from the staging table. |
No dependencies |
|
PurgeShelfReplenishment |
This batch deletes completed or canceled Shelf replenishment records. |
No dependencies |
|
PurgeStagedMessage |
This batch process removes processed integration staging records (MPS Staged Messages). |
No dependencies |
|
PurgeStockCounts |
This batch process deletes stock counts. |
No dependencies |
|
PurgeStockItemStockHistory |
This batch will delete store item stock history inventory movement records. |
No dependencies |
|
PurgeTemporaryUINDetail |
This batch process deletes temporary UIN detail records. |
No dependencies |
|
PurgeUINDetailHistories |
This batch process deletes UIN detail history records (UIN Audit information). |
No dependencies |
|
PurgeUserCache |
This batch program deletes expired user cache records. |
No dependencies |
|
PurgeUserPasswordHistory |
This batch program deletes user password history records. |
No dependencies |
|
PurgeVendorReturns |
This batch deletes closed or completed RTVs and related shipments. |
No dependencies |
Most SIM purge programs can be scheduled to run at any time (ad hoc) with no particular order, while some of purge programs may need to run in a particular order to provide optimal results. Table 5-2, "Purge Scheduling Notes" provides some scheduling recommendations:
Table 5-2 Purge Scheduling Notes
| Batch Name | Schedule Type | Successor Depends on Success of Predecessor | Notes |
|---|---|---|---|
|
DeactivateOldUsers�PurgeDeletedUsers�PurgeUserPasswordHistory�PurgeInvalidUserRoles�PurgeUserCache � |
Ad hoc |
Not required.�The successor batch runs regardless of success/failure of the predecessor batch. |
These batches should run on a continuous basis to ensure tight security and appropriate access to SIM. |
|
PurgeDSDReceivings�PurgePurchaseOrders�PurgeClosedTransfers�PurgeVendorReturnsPurgeFulfillmentOrders |
Ad hoc |
Not Required |
Run these purge batches in logical order to provide optimal results. |
|
PurgePriceChangesWorksheetPurgeItemPrice |
Daily |
Not Required |
These batch should run at least once per day to remove the expired item price from the transaction table to ensure to optimized price retrieving response time. |
|
PurgeItem |
Ad hoc |
Not Required |
This purge should run after all other purges. |
|
PurgeItemTicket |
Ad hoc |
Not Required |
It is recommended to purge the printed tickets regularly to optimize the overall daily ticket printing process. |
The following section summarizes SIM's purge processes and includes both an overview of each purge process business functionality, assumptions, and scheduling notes for each purge program.
PurgeAdHocStockCount batch does the following:
Deletes ad hoc stock counts with a status of in progress.
Any ad hoc stock count with a creation date/time stamp older than the Days to Hold In Progress Ad Hoc Counts parameter value will be deleted. For example, the default value is 1. If the batch program is run with the default value, the batch program would delete all in-progress counts more than 24 hours old.
This batch program deletes ad hoc stock counts with a status of in progress. Any ad hoc stock count with a creation date/time stamp older than the Days to Hold In Progress Ad Hoc Counts parameter value will be deleted. For example, the default value is 1. If the batch program is run with the default value, the batch program would delete all in-progress counts more than 24 hours old.
PurgeAll batch does the following:
Deletes records from the SIM application that meet certain business criteria (for example, records that are marked for deletion by the application user, records that linger in the system beyond certain number of days, and so on).
It is the wrapper batch which contains all purge batches which are listed in the purge list.
PurgeAll.sh <purge_date>
Where purge_date is optional, date format must be dd/MM/yyyy if purge_date is specified.
PurgeAudit batch does the following:
Deletes audit records. Any audit record with a create date/timestamp older than the Days To Hold Audit Records parameter value is deleted. For example, if the default value is 30 and the batch program is run with the default value, the batch program would delete all the audit records that are more than 30 days old.
PurgeAudits.sh <purge_date>
Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.
PurgeBatchImpExp batch does the following:
Deletes batch import export records.
Any import export record with an end date/timestamp older than the Days To Hold Completed Staging Records parameter value and with the Status value of 2 (COMPLETED) is deleted. For example, if the default value is 30 and the batch program is run with the default value, the batch program would delete all the records that are more than 30 days old and are in completed status.
PurgeBatchImpExp.sh <purge_date>��Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.�
PurgeClosedTransfers batch does the following:
Deletes all the closed transfer which are in either cancelled or completed status and shipments related to them.Any closed transfer with a update date older than the Days to Hold Transfer Documents parameter value will be deleted. For example, the default value is 30. If the batch program is run with the default value, the batch program would delete all closed transfers, transfer requests and related shipments which are closed and was last updated 30 days ago.
PurgeClosedTransfers.sh <purge_date>
Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.
Table 5-6 Key tables for PurgeClosedTransfers Batch
| Tables | Select | Insert | Update | Delete |
|---|---|---|---|---|
|
config_system |
Yes |
|||
|
tsf |
Yes |
Yes |
||
|
tsf_line_item |
Yes |
|||
|
tsf_ship |
Yes |
Yes |
||
|
tsf_ship_carton |
Yes |
|||
|
tsf_ship_line_item |
Yes |
Yes |
||
|
tsf_ship_line_item_uin |
Yes |
|||
|
tsf_ship_line_item_att |
Yes |
|||
|
shipment_bol |
Yes |
|||
|
tsf_delv |
Yes |
|||
|
tsf_delv_line_item |
Yes |
PurgeCompletedUINDetail batch does the following:
Deletes completed UIN Detail records. A completed UIN is any UIN with a status of Removed from Inventory, Missing, Sold, Shipped to Vendor, or Shipped to Warehouse.
Any UIN detail record with a complete status and update date at least X days in the past (where X is with system parameter DAYS_TO_HOLD_COMPLETED_UINS) will be deleted from ITEM_UIN and ITEM_UIN_PROBLEM table.
PurgeCompletedUINDetail.sh <purge_date>
Where purge_date is optional and the date format must be dd/MM/yyyy format if purge_date is specified.
PurgeDeletedUsers batch does the following: These users and all associated data are deleted from SECURITY_USER_ROLE, SECURITY_USER_STORE, SECURITY_USER_PASSWORD, and SECURITY_USER tables.
It finds users marked as deleted with an end date that is at least X days in the past (where X is the system parameter SECURITY_DAYS_TO_HOLD_DELETED_USERS).
These users and all associated data are deleted from database tables.
PurgeDeletedUsers.sh <purge_date>
Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.
PurgeDSDReceivings batch process does the following:
Deletes the Direct Store Delivery receivings.
Any DSD record which is in Closed/Cancelled status and which has a complete date older than Days to Hold Received Shipments is an eligible record for purge.
Before a DSD record is purged, checks are made to ensure that the purchase order associated with a particular DSD is also completed and is older than Days to Hold Purchase Orders.
In effect, a DSD record can be purged only if its associated PO records can be purged.
PurgeDSDReceivings.sh <purge_date>
Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.
Table 5-9 Key tables for PurgeDSDreceivings Batch
| Tables | Select | Insert | Update | Delete |
|---|---|---|---|---|
|
config_system |
Yes |
|||
|
purchase_order |
Yes |
Yes |
||
|
purchase_order_line_item |
Yes |
Yes |
||
|
dsd |
Yes |
Yes |
||
|
notes |
Yes |
Yes |
||
|
dsd_adjustment |
Yes |
Yes |
||
|
dsd_carton |
Yes |
Yes |
||
|
dsd_line_item |
Yes |
Yes |
||
|
dsd_line_item_uin |
Yes |
Yes |
||
|
dsd_line_item_att |
Yes |
Yes |
PurgeFulfillmentOrders Batch batch does the following:
Deletes all the fulfillment order records which are not in New or In Progress status and for which the update date has expired the purge_date by number of days more than Days to Hold Customer Order parameter value.
Additionally, only those fulfillment orders will be deleted for which customer order ID and fulfillment order ID combination does not exist for any Transfer, Return, Purchase Order, and Warehouse delivery transaction.
PurgeFulfillmentOrders.sh <purge_date>
Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.
Table 5-10 Key tables for PurgeFulfillmentOrders Batch
| Tables | Select | Insert | Update | Delete |
|---|---|---|---|---|
|
config_system |
Yes |
|||
|
tsf |
Yes |
|||
|
purchase_order |
Yes |
|||
|
tsf_delv_line_item |
Yes |
|||
|
ful_ord |
Yes |
Yes |
||
|
ful_ord_line_item |
Yes |
Yes |
||
|
ful_ord_dlv |
Yes |
Yes |
||
|
ful_ord_dlv_line_item |
Yes |
Yes |
||
|
ful_ord_dlv_line_item_uin |
Yes |
Yes |
||
|
ful_ord_dlv_line_item_att |
Yes |
Yes |
||
|
ful_ord_rv_pick |
Yes |
Yes |
||
|
ful_ord_rv_pick_line_item |
Yes |
Yes |
||
|
ful_ord_pick |
Yes |
Yes |
||
|
ful_ord_pick_line_item |
Yes |
Yes |
||
|
ful_ord_bin |
Yes |
Yes |
PurgeInvalidUserRoles batch program does the following:
Removes all expired user roles and orphaned user roles (roles that were deleted by removing a store) from the SIM system.
The batch process finds user role assignments that have an end date that is at least X days in the past (where X is specified by the system parameter SECURITY_DAYS_TO_HOLD_EXPIRED_USER_ROLES), and deletes these expired role assignments.
The users (excluding super users) with role assignments that have no matching store assignments (orphaned role assignments) are also deleted from SECURITY_USER_ROLE table.
PurgeInvalidUserRoles.sh <purge_date>
Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.
PurgeInventoryAdjustments batch process does the following:
Deletes inventory adjustments records with a create date/timestamp older than Days To Hold Completed Inventory Adjustments parameter value will be deleted. For example, the default value is 30. If the batch program is run with the default value, the batch program would delete all the inventory adjustment records, which are more than 30 days old.
PurgeInventoryAdjustments.sh <purge_date>
Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.
PurgeInventoryAdjustTemplate batch process does the following:
Deletes inventory adjustment template records for which the status is cancelled and the record (approve date) has satisfied the DAYS_TO_HOLD_CANCELLED_TEMPLATE value which is specified in CONFIG_SYSTEM table.
PurgeInventoryAdjustTemplate.sh <purge_date>��Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.�
This batch program deletes items with a status of Delete (D).
There are two segments in the PurgeItem Batch which do the following different tasks:
Validate if the Item should be deleted.
Delete item from all associated tables if validation check is passed.
Validate if the item should be deleted. The Validations include:
If SOH of item, item parent and item grandparent is 0.
If any transfers exist for item, item parent and item grandparent.
If any RTV exists for item, item parent and item grandparent.
If any Inventory adjustment exists for item, item parent and item grandparent and so on.
If any Item Basket exists for the item.
If any Product Group exists for the item.
If any Stock Count exists for the item.
If any Store Order exists for the item.
If any Item Request exists for the item.
If any Direct Store Delivery exists for the item.
If any Warehouse Delivery exists for the item.
Delete item from all associated table. If the validations checks are met, the records related to the item which is marked for the purge action are deleted.
Table 5-14 Key tables for PurgeItem Batch
| Tables | Select | Insert | Update | Delete |
|---|---|---|---|---|
|
item_componen |
Yes |
Yes |
||
|
Item |
Yes |
Yes |
||
|
store_item_stock |
Yes |
|||
|
purchase_order_line_item |
Yes |
|||
|
rtv_line_item |
Yes |
|||
|
stock_count_line_item |
Yes |
|||
|
tsf_line_item |
Yes |
|||
|
rtv_ship_line_item |
Yes |
|||
|
dsd_line_item |
Yes |
|||
|
dsd_adjustment |
Yes |
|||
|
stock_count_line_item_uin |
Yes |
|||
|
tsf_ship_line_item |
Yes |
|||
|
tsf_delv_line_item |
Yes |
|||
|
item_basket_line_item |
Yes |
|||
|
print_store_order_item |
Yes |
|||
|
item_ticket |
Yes |
|||
|
item_request_line_item |
Yes |
|||
|
ful_ord_line_item |
Yes |
|||
|
ful_ord_pick_line_item |
Yes |
|||
|
inv_adjust_line_item |
Yes |
|||
|
inv_adjust_template_item |
Yes |
|||
|
shelf_adjust_line_item |
Yes |
|||
|
shelf_replenish_line_item |
Yes |
|||
|
tsf_allocation |
Yes |
|||
|
item_uin |
Yes |
Yes |
||
|
store_item |
Yes |
Yes |
||
|
item_image |
Yes |
Yes |
||
|
store_sequence_item |
Yes |
Yes |
||
|
store_item_stock |
Yes |
Yes |
||
|
store_item_stock_nonsell |
Yes |
Yes |
||
|
supplier_item_manufacture |
Yes |
Yes |
||
|
warehouse_item |
Yes |
Yes |
||
|
partner_item |
Yes |
Yes |
||
|
supplier_item_uom |
Yes |
Yes |
||
|
supplier_item |
Yes |
Yes |
||
|
supplier_item_country |
Yes |
Yes |
||
|
supplier_item_country_dim |
Yes |
Yes |
||
|
item_ticket |
Yes |
Yes |
||
|
item_component |
Yes |
Yes |
||
|
item_price |
Yes |
Yes |
||
|
item_price_history |
Yes |
Yes |
||
|
store_uin_admin_item |
Yes |
Yes |
||
|
item_uda |
Yes |
Yes |
||
|
product_group_item |
Yes |
Yes |
||
|
related_item |
Yes |
Yes |
This batch process deletes item baskets. Any item basket record with a process date or timestamp older than batch date value is deleted.
PurgeItemPrice batch process does the following:
Purges records which were expired or were marked as deleted from ITEM_PRICE table based on the retention period. The retention period is specified by system configuration parameter DAYS_TO_HOLD_EXPIRED_ITEM_PRICE.
Following are the rules defining records to be purged:
Regular Price Change: Has status of completed or deleted, effective date was X number of days in the past (relative to the specified date if specified). At any given time, at least one completed latest regular price must be retained in ITEM_PRICE for a store item.
Promotion Change: Has status of completed or deleted, and end date is number of days in the past (relative to the specified date if specified).
Clearance Change: Has status of completed or deleted, and end date is number of days in the past (relative to the specified date if specified).
PurgeItemPrice.sh <date>
Where date is optional and the date format must be dd/MM/yyyy if date is specified.
If date is not provided, then the current time on the batch client is used.
PurgeItemHierarchy batch does the following:
Purges all Item Hierarchies that is in delete status. It also records from referencing tables such as STOCK_COUNT_ADHOC_CONFIG and ITEM_HIERARCHY_ATTRIB.
The batch process logs errors with executing the batch otherwise it returns a success code.
PurgeItemRequests batch does the following:
Deletes item requests which are in Cancelled/Completed status. Any item request record with a process date/timestamp older than DAYS_TO_HOLD_CANCELLED_ITEM_REQUESTS system configuration value will be deleted. For example, the default value is 30. If the batch program is run with the default value, the batch program would delete all the item request records, which are more than 30 days old.
PurgeItemRequests.sh <purge_date>
Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.
PurgeItemTickets batch does the following:
Deletes item tickets which were printed or canceled at least X days in the past (where X is the system parameter DAYS_TO_HOLD_ITEM_TICKETS).
It is recommended to purge the printed tickets regularly to optimize the overall daily ticket printing process.
PurgeItemTickets.sh <purge_date>
Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.
This batch process deletes lockings records from ACTIVITY_LOCK table. Any lock record with a lock date/timestamp older than Days to Hold Locking Records (DAYS_TO_HOLD__LOCKING_RECORDS) system configuration value will be deleted. For example, the default value is 30. If the batch program is run with the default value, the batch program would delete all the shelf replenishment records, which are more than 30 days old.
PurgeLockings.sh <purge_date>
Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.
This batch process deletes price change worksheet records from the staging table which are in Rejected/Completed status. Any price change record with an effective date/timestamp older than Days To Hold Price Changes parameter value will be deleted. For example, the default value is 30. If the batch program is run with the default value, the batch program would delete all the price change records, which are more than 30 days old.
PurgePriceChangeWorksheet.sh <purge_date>
Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.
This batch process deletes price histories. At least a minimum of 4 historical prices are maintained for an item/store. Days To Hold Price History will determine the number of days that price histories can be kept in the database.
PurgePriceHistories.sh <purge_date>
Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.
This batch process deletes closed purchase order records. The purchase order records which are in closed status and complete date is at least X days in the past (where X is system parameter DAYS_TO_HOLD_COMPLETED_PURCHASE_ORDERS) are deleted from the database.
PurgePurchaseOrders.sh<limit_size>
Where limit size is optional and the d default value is 1000.
This batch process deletes the related items for which the end date has expired for more than Days To Hold Related Items (DAYS_TO_HOLD_RELATED_ITEMS) system configuration value.
PurgeRelatedItems.sh <purge_date>��Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.�
PurgeResolvedUINProblems batch does the following:
Deletes resolved UIN exception records. UIN exception records with status of resolved and resolved date is at least X days in the past (where X is system parameter DAYS_TO_HOLD_RESOLVED_UIN_EXCEPTIONS) are deleted from ITEM_UIN_PROBLEM table.
purgeResolvedUINProblems.sh <purge_date>
Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.
This batch process deletes the Point-of-Service transaction from the Oracle Retail Xstore Point of Service transaction staging table. It reads the Days to Hold Sales Posting and Days to Hold Failed Sales configuration parameters and all the transactions which are present beyond the configuration parameter are deleted. It also purges the POS transaction logs for the request IDs that are in processed status.
PurgeSalesPosting.sh <purge_date>
Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.
This batch process deletes shelf replenishment lists which are in Completed/Cancelled state. Any shelf replenishment list record with a status date/timestamp older than Days To Hold Shelf Replenishment parameter value will be deleted. For example, the default value is 1. If the batch program is run with the default value, the batch program would delete all the pick list records, which are more than a day old.
In addition, the batch will also delete shelf adjustment lists which are in Complete state. Any shelf adjustment record with an update date/timestamp older than Days to Hold Shelf Adjustment Lists parameter value will be deleted.
PurgeShelfReplenishment.sh <purge_date>
Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.
This batch finds integration staging records that are marked as processed or deleted, and update date is at least X days in the past (where X is the system parameter DAYS_TO_HOLD_COMPLETED_STAGING_RECORDS), the batch process deletes these records from MPS_STAGED_MESSAGE table.
Rebuilding the indexes on the MPS_STAGED_MESSAGE table each day is recommended after batch process completes.
PurgeStagedMessageJob.sh <purge_date>
Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.
Table 5-28 Key tables for PurgeStagedMessage Batch
| Tables | Select | Insert | Update | Delete |
|---|---|---|---|---|
|
config_system |
Yes |
|||
|
mps_staged_message |
Yes |
Yes |
|
Note: The optional date is the point of reference the script should use. The script uses current date for the point of reference by default, but can be run from any reference point.Therefore, if purging records that are 10 days old, and running the script without the optional date, the process removes all records older than 10 days from the current date. If the optional date argument is specified, records 10 days older than the specified optional date are purged. |
This batch process deletes stock counts which are in Completed/Cancelled status. Any stock count with a schedule date/timestamp older than Days To Hold Completed Stock Counts parameter value will get deleted. For example, the default value is 30. If the batch program is run with the default value, the batch program would delete all the stock return records, which are more than 30 days old.
PurgeStockCounts.sh <purge_date>
Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.
This batch process deletes stock returns which are in Dispatched/Cancelled status. Any stock return record with a completed date/timestamp older than DAYS_TO_HOLD_RETURNS system configuration value will be deleted. For example, the default value is 30.If the batch program is run with the default value, the batch program would delete all the stock return records, which are more than 30 days old
This batch process deletes store item stock history records which have been kept for more than Days To Hold Transaction History which is specified by system configuration. For example, the default value is 30. If the batch program is run with the default value, the batch program would delete all the stock history records, which are more than 30 days old.
PurgeStoreItemStockHistory.sh <purge_date>��Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.�
This batch process deletes temporary UIN detail records. UIN detail records with no status and update date is at least X days in the past (where X is system parameter DAYS_TO_HOLD_TEMPORARY_UINS) are deleted from ITEM_UIN table.
PurgeTemporaryUINDetail.sh <purge_date>
Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.
This batch process deletes UIN detail history records (UIN Audit Information). UIN Audit information could be purged for a UIN while the UIN is still open within the system. Open UIN is any UIN that is in one of the following statuses:
In Stock
In Receiving
Reserved for Shipping
Unavailable
UIN history records with open status and an update date at least X days in the past (where X is system parameter DAYS_TO_HOLD_UIN_AUDIT_INFORMATION) are deleted from ITEM_UIN_HISTORY table.
purgeUINDetailHistories.sh <purge_date>
Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.
This batch program deletes cached users who have no security user role assignments.
PurgeUserCache.sh <purge_date>
Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.
If purge_date is not specified, the current GMT time is used.
This batch process finds users with more than X passwords (where X is the system parameter PASSWORD_NUMBER_OF_PREVIOUS_TO_DISALLOW), and deletes the oldest passwords that exceed this limit.
PurgeUserPasswordHistory.sh <purge_date>
Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.
Purge_date currently has no effect, reserved for future use.
This batch process deletes vendor returns which are in closed or completed status. Any vendor return record with a closed date/timestamp older than DAYS_TO_HOLD_RTV system configuration value will be deleted. For example, the default value is 30. If the batch program is run with the default value, the batch program would delete all the vendor return records, which are more than 30 days old.
PurgeVendorReturns.sh <purge_date>
Where purge_date is optional and the date format must be dd/MM/yyyy if purge_date is specified.
