The performs a series of configuration analysis tests to verify that the multisite configuration (the site and warehouse hierarchies) are correctly configured.
The following tests are a subset of the activation readiness analysis tests. These tests are performed during the multisite activation to ensure that the activation process can be completed without errors. These tests are also performed when you run the report.
Description |
Conditions |
Requirement |
||
Site/warehouse relations |
None |
All warehouses must be linked to a site. |
||
Site/warehouse relations |
None |
No warehouse refers to a quarantine warehouse on another site. |
||
Site/work center relations |
None |
All work centers must be linked to a site. |
||
Site/production unit relations |
None |
All production units must be linked to a site. |
||
Site/production unit relations |
None |
No production unit refers to a picking warehouse or a storage warehouse on another site. |
||
Site/production unit relations |
None |
All work centers that are associated with a production unit must be linked to the same site as the production unit. |
||
Physical inventory dimension group setup |
|
For each item that uses this dimension group, all transactions must be related to the same site. Otherwise, some sites may end up with negative inventory. |
||
Financial inventory dimension group setup |
|
For each item that uses this dimension group, all transactions must be related to the same site. Otherwise, the cost may change. |
||
Financial inventory dimension group setup |
None |
The activation must not result in cross-site markings. |
||
Deleted warehouses |
None |
Closed inventory transactions, which refer to a warehouse that has been deleted, must not exist. No InventDim records can refer to a deleted warehouse.
|
||
Inventory dimensions in virtual companies |
One or more virtual companies exist. |
No tables containing fields of type InventDimId must be shared across companies. |
||
Intercompany configuration |
Intercompany endpoints are defined. |
For all intercompany action policies, the value mapping of the handling warehouse that is defined in the document configuration must be set to not specified. |
||
Site/task group relations |
None |
All work centers in a task group must belong to the same site. This site must be the same site that is defined on the task group. |
||
Site/task group relations |
None |
A task group that is assigned to a work center must not contain work centers from sites that differ from the site that the work center is assigned to. |
||
Site/bill of materials relations |
None |
All warehouses that are defined in the BOM must be associated with the same site, because master planning assumes 0 (zero) days for picking. |
||
Site/bill of materials relations |
None |
If a site is defined in the BOM version, all warehouses that are defined in the BOM must belong to that same site. |
||
Site/route relations |
None |
All work centers that are defined in a route must belong to the same site. |
||
Site/route relations |
None |
A task group that is assigned to a route can only contain work centers that are assigned to the same site as the work centers that are defined in the route. |
||
Site/route relations |
None |
All work centers that are defined in a route version must belong to the same site. |
||
Site/route relations |
None |
For each route version that is assigned to a site, all work centers that are defined in the route must belong to the same site. |
||
Shipment setup |
A warehouse is not defined on the shipment |
Multisite activation is not possible. The wizard informs the user to either complete or cancel the shipment before multisite functionality can be activated. |
||
Shipment template setup |
A warehouse is not defined on the shipment template |
Multisite activation is not possible. The wizard informs the user to add a warehouse to the shipment template before multisite functionality can be activated. |
||
Fallback warehouse |
None |
A fallback warehouse must be selected on the tab in the form. |
||
Inventory dimensions |
None |
No inventory dimension combination must exist where both the site dimension and the warehouse dimension are populated (not blank).
|
The following additional tests are performed during the multisite activation process and when you run the report.
Description |
Conditions |
Requirement |
||
Site/production order relations |
None |
Open production orders must not span multiple sites.
|
||
Empty intercompany inventory dimensions |
None |
The intercompany inventory dimensions table must be empty, as this table is only used for temporary storage of data. |
||
Empty intercompany inventory summary |
None |
The intercompany on-hand inventory table must be empty, as this table is only used for temporary storage of data. |
||
Empty quarantine orders |
None |
All quarantine orders must be associated with a warehouse. |
||
Empty inventory summary delta |
None |
The on-hand inventory changes table must be empty, as this table is only used for temporary storage of data. |
||
Empty inventory summary delta dimension |
None |
The on-hand inventory checks table must be empty, as this table is only used for temporary storage of data. |
||
Inventory transaction ID on the same site |
None |
All open inventory transactions with the same inventory transaction ID (Lot ID) must be associated with the same site.
|
||
Empty transfer journal lines |
None |
A warehouse must be assigned to all transfer journal lines. |
||
Empty inventory transfer lines |
None |
A warehouse must be assigned to all inventory transfer lines. |
||
Empty warehouse management orders |
None |
A warehouse must be assigned to all warehouse management orders. |
||
Empty warehouse management order transactions |
None |
A warehouse must be assigned to all warehouse management order transactions |
Unless otherwise noted, the Microsoft Dynamics AX business logic and the requirement that all users must be logged off the system during the multisite activation will ensure that the additional tests that are listed above do not fail.
Note |
---|
If any of these checks fail, it is an indication that the system is still in use, or that there is a problem with the current implementation of Microsoft Dynamics AX. |