Cleaning Up Inventory Records
Explanation
This activity is used to remove location records created for inventory parts
that have a zero quantity on-hand and are not frozen. This activity is performed
prior to generating a count report. Records pertaining to receive inventory
part and issue inventory part transactions will be deleted through this operation.
This is useful, for example, when the part becomes obsolete or the warehouse
no longer exists.
Location records for both serialized or configurable parts will be deleted
through this operation. You can specify the number of days prior to today's
date (i.e., system date) and the site for which the records should be removed.
The last transaction date for the location of the inventory part is used to
determine if a cleanup should be performed.
You can either perform a cleanup of inventory directly, or schedule the task
as a background job.
Note:
- Inventory locations are not removed by using the cleanup of inventory
routine.
- You can include multiple projects by using wildcard characters. If you
enter the wildcard character (%) in the Project ID field, all records
will be included regardless of whether they are in project or standard inventory.
- To remove the records created for the parts with serial numbers, enable
the Serial Numbers Only option. To remove the records created for
the parts with configurations, enable the Configurations Only option.
To remove the records created for the parts with a handling unit ID, enable
Handling Units Only option. Enable all three options to remove the
location records for the parts containing both serial numbers, configurations
and handling units.
Prerequisites
N/A
System Effects
- All records with an on-hand quantity of zero and a last transaction
date prior to the number of days specified in the Days Before Current
Date field, are removed from the Inventory Part
In Stock, Receive Inventory Part and
the Issue Inventory Part pages.
- If you have scheduled the task as a background job, the task will be
automatically performed based on defined selection criteria.There will be
one background job per site if there are multiple sites [i.e., if you run
the task with the wildcard character (%)].