| Delete and archiveTo save disk space and system performance, regularly delete or
archive, or delete and archive actual warehousing order data, inventory
transaction data, and history data. Delete and archive history data In the following sessions, you can delete or archive, or
delete and archive history data: - Delete/Archive Warehousing Orders (whinh2255m000)
- Delete/Archive Shipment Notice History (whinh3251m000)
- Delete/Archive Receipt History (whinh3260m000)
- Delete/Archive Load/Container/Shipment History (whinh4251m000)
- Delete/Archive Cycle Counting Order History (whinh5250m000)
- Delete/Archive Adjustment Order History (whinh5270m000)
- Delete/Archive Inventory Transactions (whinr1200m000)
- Delete/Archive Inventory Transactions by Item and Warehouse (whinr1210m000)
- Delete/Archive Issues by Period (whinr1220m000)
- Delete/Archive Issue by Period and Warehouse (whinr1230m000)
- Archive/Delete Packaging Item Transactions (whinr1215m000)
- Delete/Archive Handling Unit Version History (whwmd5231m000)
In the following sessions, to keep the last transaction of
the objects that you delete, select the Keep Last Transaction check box: - Delete/Archive Warehousing Orders (whinh2255m000)
- Delete/Archive Shipment Notice History (whinh3251m000)
- Delete/Archive Receipt History (whinh3260m000)
- Delete/Archive Load/Container/Shipment History (whinh4251m000)
This way, the most recent transaction stays in the live
company while the older data is deleted or archived. To access the archiving sessions, use the appropriate menu of the
history sessions. Note For more information, refer to User's Guide for
Archiving (U9352* US). Delete live data In addition to history data, you can also delete live
records for the following objects: - Warehousing orders
- Handling units
- Inbound and outbound advice
- Confirmed shipments
- Adjustment orders and related data
- Cycle counting order and related data
You can access the deletion sessions from the appropriate menu on the
sessions of these objects. Performance aspects - Effect on CPU: Yes
- Effect on database growth: Yes
| |