About multisite activation readiness
Important
This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.
Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
The upgrade readiness check performs a series of configuration analysis tests to identify issues that could potentially affect data upgrade. These checks include verification that the multisite configuration is setup correctly. This includes verifying that the site and warehouse hierarchies are specified.
Important
The upgrade readiness tests will not complete until the site structure is configured.
The following tables list and describe the conditions and requirements for multisite activation that the readiness check tests for. These tests ensure that the activation process is completed without errors.
Description |
Conditions |
Requirement |
Site and warehouse relations |
None |
A site is assigned to all warehouses. |
Site and warehouse relations |
None |
Warehouses only refer to quarantine warehouses that are located on the same site. |
Site and work center relations |
None |
All work centers are linked to a site. |
Site and production unit relations |
None |
All production units are linked to a site. |
Site and production unit relations |
None |
Production units only refer to picking warehouses or storage warehouses that are located at the same site. |
Site and production unit relations |
None |
All work centers that are associated with a production unit are linked to the same site as the production unit. |
Physical inventory dimension group setup |
|
For each item that uses this dimension group, all transactions are related to the same site. Otherwise, some sites may have with negative inventory values. |
Financial inventory dimension group setup |
|
For each item that uses this dimension group, all transactions are related to the same site. Otherwise, the cost may change. |
Financial inventory dimension group setup |
None |
Activation will not result in cross-site markings. |
Deleted warehouses |
None |
Closed inventory transactions do not refer to a warehouse that has been deleted. InventDim records cannot refer to a deleted warehouse. Note If this check fails, the validation displays a list of any deleted warehouses. You will have to re-create these warehouses, assign them to a site, and then re-run the upgrade readiness check. After the upgrade is complete, you can delete the warehouses again, because no transactions are created for these warehouses during the activation process. |
Inventory dimensions in virtual companies |
One or more virtual companies exist. |
Tables that contain InventDimId fields are not 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 is set to not specified. |
Site and task group relations |
None |
All work centers in a task group belong to the same site. This site must be the same site that is defined on the task group. |
Site and task group relations |
None |
All task groups are assigned only to work centers located on the same site. |
Site and bill of materials relations |
None |
All warehouses that are defined in the bill of materials are associated with the same site. Master planning assumes 0 (zero) days for picking. |
Site and bill of materials relations |
None |
If a site is defined in the BOM version, all warehouses that are defined in the BOM belong to that same site. |
Site and route relations |
None |
All work centers that are defined in a route belong to the same site. |
Site and route relations |
None |
A task group that is assigned to a route contains only work centers that are assigned to the same site as the work centers that are defined in the route. |
Site and route relations |
None |
All work centers that are defined in a route version belong to the same site. |
Site and route relations |
None |
For each route version that is assigned to a site, all work centers that are defined in the route belong to the same site. |
Shipment setup |
A warehouse is not defined on the shipment |
Multisite cannot be activated. You must either complete or cancel the shipment before you upgrade. |
Shipment template setup |
A warehouse is not defined on the shipment template |
Multisite cannot be activated. You must add a warehouse to the shipment template before you upgrade. |
Fallback warehouse |
None |
A fallback warehouse is selected on the Other tab in the Company information form. |
Inventory dimensions |
None |
Inventory dimension combinations do not include both the site dimension and the warehouse dimension. Note This check will fail when there is a defect in the application. To recover, you must manually clean up the Inventory Dimension table. |
Additional readiness checks
The following table describes additional readiness checks that the validation performs.
Description |
Conditions |
Requirement |
Site and production order relations |
None |
Open production orders do not span multiple sites. Note If this check fails, the validation displays a list of the production orders that span multiple sites. You must end these production orders before upgrading. |
Empty intercompany inventory dimensions |
None |
The intercompany inventory dimensions table is empty. This table is used only for temporary storage of data. |
Empty intercompany inventory summary |
None |
The intercompany on-hand inventory table is empty. This table is used only to store data temporarily. |
Empty quarantine orders |
None |
All quarantine orders are associated with a warehouse. |
Empty inventory summary delta |
None |
The on-hand inventory changes table is empty. This table is used only to store data temporarily. |
Empty inventory summary delta dimension |
None |
The on-hand inventory checks table is empty. This table is used only to store data temporarily. |
Inventory transaction ID on the same site |
None |
All open inventory transactions with the same inventory transaction ID, or Lot ID, are associated with the same site. Note If this check fails, the validation displays a list of the lot IDs for which inventory transactions will be split across multiple sites. You must close these inventory transactions by financially updating the parent transaction before proceeding with the upgrade. |
Empty transfer journal lines |
None |
A warehouse is assigned to all transfer journal lines. |
Empty inventory transfer lines |
None |
A warehouse is assigned to all inventory transfer lines. |
Empty warehouse management orders |
None |
A warehouse is assigned to all warehouse management orders. |
Empty warehouse management order transactions |
None |
A warehouse is assigned to all warehouse management order transactions |