Enhanced configuration migration safeguards and lock code handling
Configuration migration helps users move setup data across facilities and companies without manually recreating configuration records. This enhancement helps customers protect destination setup, maintain 3PL company rules, and keep lock code facility details accurate during configuration import and copy flows.
Automatic Backup of Destination Configuration During Configuration Migration
WMS creates a backup of the destination facility or company configuration before users import or copy configuration data. This helps customers preserve the destination setup before changes are applied through newly introduced button Import Config Pack or Copy Config to Eligible Facility/Company in the Configuration Pack Screen (ConfigPackView).
WMS creates the backup only when matching configuration records exist in the destination facility or company. The backup includes the destination configuration records for the entity being imported or copied. The backup file is stored on the backend file server and is recorded in the log files. If customers need the backup file, they must raise a Service Request.
If the backup fails because of a server or processing error, WMS stops the import or copy action and displays an error. If no matching destination records exist, WMS continues the import or copy action.
Restrict Lock Code Migration to Child Companies
Configuration migration helps users move setup across facilities and companies with less manual effort. In 3PL environments, lock codes must remain controlled at the parent company level so customers can apply inventory hold rules consistently and avoid creating lock code setup in child companies where it is not allowed.
WMS validates lock code records during configuration import and copy actions. When users import or copy lock code configuration to a child company, WMS prevents the action and displays an error. This validation applies to:
- Config Tool: Import Configuration
- Config Tool: Copy Configuration to Eligible Facility / Company
- Configuration Pack: Import Config Pack
- Configuration Pack: Copy Config Pack to Eligible Facility / Company
If a configuration pack includes lock codes as related records, WMS checks the parent company setup before continuing. WMS allows the action only when the lock code exists in the parent company, or when the user has access to create the lock code in the parent company. If the required parent company access or facility assignment is missing, WMS stops the import or copy action and displays an error.
| Scenario | Behavior |
|---|---|
| User imports or copies Lock Code configuration directly to a child company | WMS prevents the action and displays: Lock codes cannot be created for client companies. |
| Configuration pack includes Lock Code as a root entity and the destination is a child company | WMS prevents the import or copy action. |
| Configuration pack includes Lock Code as a related entity and the lock code exists in the parent company | WMS continues the import or copy action. |
| Configuration pack includes Lock Code as a related entity, but the user does not have parent company access | WMS stops the action and displays an error. |
| Lock Code has a facility value, but the destination facility is not assigned to the parent company | WMS stops the action and displays an error. |
| User imports or copies other configuration entities to a child company | WMS continues the action when no lock code restriction applies. |
Apply the Correct Facility to Lock Codes During Configuration Migration
Configuration migration helps users copy lock code setup across facilities and companies. This enhancement keeps global and facility-specific lock codes accurate in the destination, so inventory lock rules continue to work correctly after import or copy actions.
WMS checks whether each lock code is global or facility-specific during Config Tool or Configuration Pack import and copy actions. Global lock codes remain global in the destination. Facility-specific lock codes use the selected destination facility. WMS also honors existing lock code uniqueness and facility update validations.
- If source lock code is global, WMS keeps the lock code global in the destination.
- Source lock code is facility-specific, WMS creates or updates the lock code using the selected destination facility.
- Lock code already exists; WMS applies existing uniqueness and facility update validations.
Steps to enable and configure
To apply automatic Backup of Destination Configuration During Configuration Migration:
- Go to the Configuration Pack module.
- Select Import Config, Copy Config to Eligible Facility / Company, Import Config Pack, or Copy Config Pack to Eligible Facility / Company.
- Select the required source file, configuration pack, destination facility, or destination company.
- Submit the action.
WMS backs up eligible destination configuration records before applying the import or copy changes. WMS validates lock code records when the migration includes lock code configuration. Review any error message displayed by WMS and correct the setup or access issue before retrying.