> > >
Use this batch job to resolve dimension inconsistencies on closed inventory transactions (transactions that have been financially updated), that may occur as a result of running the multisite activation process. This batch job is intended only for cleaning up transactions that were closed before the multisite activation. It is not intended for periodic usage.
Inconsistent dimensions may occur when a warehouse is not specified on a source transaction, but a warehouse is specified on the corresponding inventory transaction. During the multisite activation process, all open InventDim records are updated to include a site dimension. An open source transaction that lacks a warehouse is updated with the site that is specified on the corresponding inventory transaction.
However, for performance reasons, the multisite activation process does not update closed inventory transactions. In the case of a closed source transaction that lacks a warehouse, the multisite activation process updates the transaction with the default site. However, the corresponding inventory transaction is updated with the site that is associated with the warehouse that is specified on the inventory transaction. The result may be an inconsistency where a source transaction is associated with one site, and the corresponding inventory transaction is associated with a different site.
You can use the batch job to resolve site inconsistencies on select closed source transactions by updating them with the site that is associated with the most recent inventory transaction. The update makes the site that is referenced on the source transaction consistent with the site on the associated inventory transactions.
You can set up the batch job to process these transactions at a convenient time, such as evenings or weekends. This allows a customer to activate the multisite functionality, resume business operations quickly, and process historical data at a later time.
Do not run this batch job on transactions that are created after you have activated the multisite functionality. If the warehouse that is specified as the default warehouse during the multisite activation process is used on any transactions that are generated after the multisite activation, the warehouse information on those transactions will be lost.
Preconditions for running this batch job are:
The LogisticsAdvanced configuration key is enabled.
The multisite functionality is activated.
Run the Multisite activation - dimension inconsistency clean up job
Click > > > .
The and fields are populated by default with the default site and warehouse values that are saved in the database.
Enter the date range to apply to the job.
The check box is selected by default. When the check box is selected, the batch job updates any source transactions that were originally updated with the default warehouse during the multisite activation process, by clearing the warehouse.
Click OKto resolve the site inconsistencies on any closed source transactions, and their corresponding inventory transactions, that fall within the specified date range.