Table of Contents

Clean Up

Cleanup Setup in 3PL Dynamics

With every posted document, sent email, or aborted session, your database grows. That makes sense. However, not all data must be saved forever in your environment. For example, posted documents only have to be stored a couple of years and aborted scan sessions can be closed and deleted almost right away. That is where cleanup setups help you out.

With these setups, you can determine what data can be deleted after a certain period. In that way, you prevent your database from becoming unnecessarily big which could bring down your applications performance. But you also prevent error messages. As too many incorrectly closed scan sessions can cause errors in your process when your employees end up in an old session. Furthermore, EDI messages containing print documents in the DI Message Table can increase your database a lot, without you knowing. Therefore, delete these data periodically with the cleanup setup.

How To

  1. Access the cleanup setup.
  2. By default, there are several predefined settings. You can activate or change these (date filter or additional table filter). You can also add an additional rule. For example, to remove one-time addresses.
  3. Go to job queue entries
  4. Open a new job queue entry 'WMS Job Queue Task - Task 13' in order to automatically delete every night all the records that meet the criteria.
  5. Set the task to wait and schedule the cleanup action on a day/time when there are few or no transactions. For example, at night and only on Saturdays.
  • The function 'Calculate' gives the number of records which are going to be deleted
  • The function 'Cleanup All' delete the records
Tip
  • If the task has never been run before, the first time will take longer.

Explanation Cleanup Setup

These fields define the structure and properties of the "3PL Cleanup Setup" table, which is used for configuring cleanup operations in an application. Each field has a specific purpose and data type, allowing users to define and manage cleanup settings for different tables in the system.

Field Name Field Type Description
Table No. Integer Represents the number of the table. If a Table is not available in the Clean Up Setup please create a ticket to add the Table
Table Name Text[100] Represents the name of the table.
Table Caption Text[249] Represents the caption or description of the table.
Extra Table Filter TableFilter Represents an additional filter that can be applied to the table. It allows specifying additional conditions to narrow down the records to be processed during cleanup operations.
Type Option Represents the type of cleanup operation to be performed on the table. It is an option field with three possible values: "Delete", "Archive", and "Compress".
Field Number Integer Represents the number of the field within the table. Where the Date(Time) filter will be applied on.
Filter Field Text[80] Represents the name of the field used as a filter during cleanup operations.
Date Formula DateFormula Represents a formula used to calculate a date value during cleanup Operations.
Inactive Boolean Represents whether the cleanup setup is inactive or not. If set to true, the cleanup setup will not be executed during cleanup operations.
Last Executed DateTime Represents the date and time when the cleanup setup was last executed.
Total Records Deleted Integer Represents the total number of records deleted during the cleanup operation.
Records within filter Integer Represents the number of records within the specified filter criteria.

Type Explanation

Type Description Supported Tables
Delete Records are removed from the table. All
Archive Max. Archive Date is 3 Months. This option will transfer the records from the WMS Document Header to the WMS Posted Document Header (including Sub Tables) WMS Document Header
Compress Will remove the unused Set Entries - Report Usage
- WMS Specification Set Entry
- WMS Item Ledger Entry
- WMS Doc. Info Set Entry
- WMS Carrier Stack Set Entry
- WMS Carrier Set Entry
Tip

You can create multiple configurations per table. For example, for the DI Message table where you filter by SND-ZPL / SND-PDF and clean it daily, and the other message types once a month.