Configuration Import/Export
Configuration Import/Export (config) action button helps you to export and/or import (migrate or replicate) configurations from one environment (source) to another (target) in WMS, or company/facility specific configurations from one WMS Company/Facility to another.
Using this action button, you can export all or specific records via export configuration option and import those records to the target environment in the same screen via import configuration option. Importing configurations can create new records or update existing ones, but it does not delete existing records.
This configuration migration assists you in:
- Migrating customized configurations between environments within a single release.
- Extracting specific configurations and/or screens from a customer environment to QA to replicate issues.
- Duplicating the Parent Company's setups to create new facilities.
- Configuring new users who might require their default settings.
Pre-Requisites
To enable the “config” action button in the relevant screens, you need to add the group permission “ConfigImportExport / Import/Export Configuration”.
To add “ConfigImportExport / Import/Export Configuration” group permission, do the following:
- Go to Groups (GroupsView) UI.
- Select your group and click “Permissions” action button.
- In the group permissions list, enable the permission “ConfigImportExport / Import/Export Configuration”.
- Click Save.
Applicable Screens
The flexibility to migrate or replicate the UI configurations between facilities, companies, and environments is available in the following UIs or screens.
Module Name | UI/screen Name |
CCTriggerMgmtView | Cycle Count Trigger Management |
InventoryLockCodeView | Inventory Lock Codes |
LocationSizeTypeView | Location Size Types |
ObLpnTypeView | LPN Type |
OrderLockView | Order Lock |
PurchaseOrderTypeView | Purchase Order Type |
PutawayTypeView | Putaway Type |
ReasonCodeView | Reason Code |
ReplenishmentTypeView | Replenishment Type |
ReplenishmentZoneView | Replenishment Zone |
TaskTypeView | Task Type |
TaskZoneView | Task Zone |
TrailerTypeView | Trailer Types |
WorkOrderTypeView | Work Order Types |
LgfProgramDataView | Facility Parameters |
BarcodeTypeView | Barcode Type |
ScreenView | Screens |
CompanyParmView | Company Parameters |
EquipmentTypeView | Equipment Type |
ContactView | Contact |
OrdertypeView | Order Type |
CompanyReportTypeView | Company Report Type |
MheSystemView | MHE System / MHE Lane / MHE Msg Config / MHE Route Config |
VendorView | Vendor |
ShiptoCompanyView | Ship to Company |
ReplenishmentTypeZoneXrefView | Replenishment Type Zone Xref |
InputInterfaceConfigView | Input Interface Config |
VendorCharacteristicsView | Vendor Characteristics View |
LabelTemplateView | Label Template View |
BreaksView | Breaks View - WFM |
CostCentreView | Cost Centre |
WorkGroupView | Work Group |
GroupActivityView | Group Activity |
WFMWork_AreaView | Work Area |
TeamsView | Teams View - WFM |
BonusGroupView | Bonus Group View - WFM |
BonusBudgetView | Bonus Budget View - WFM |
MessageCodeView | Message Codes |
PutawayTypeCalcRuleView | Putaway Type Calc Rule |
MenuHdrView | Menus |
CubingRuleView | Cubing Rule |
CCAdjustmentApprovalRuleView | CC Adjustment Approval Rule |
TaskCreationView | Task Creation |
StaffingPlanView | Staffing Plan View - wfm |
WorkAreaActivityWFMView | Work Area Activity |
WmsTransactionView | Wms Transaction View - wfm |
ProdGoalVasView | Prod Goal Vas View - wfm |
ProdGoalLineGroupView | Prod Goal Line Group View - wfm |
SkuLineGroupView | Sku Line Group View - wfm |
ShiftsView | Shifts |
MaterialHandlingView | Material Handling |
ReplenishmentTemplateView | Replenishment Template View / Replenishment Rule |
ColumnOrderingView | Column Ordering |
WaveTemplateView | Wave Template / Wave Template > Wave Template Search / Wave Template Search > Dynamic Wave Search / Wave Template Search > Order Sequence Rule / Wave Template > Expiry Date Range / Wave Template > Allocation Mode |
InvHistoryActivityParamView | Inventory History Activity Parameters |
IbShipmentTypeView | IB Shipment Types |
VendorPerfCodeView | Vendor Performance Codes |
PutawayPriorityView | Putaway Priority |
OblpnPATypeActionView | Oblpn Putaway Type Action |
Export Configuration
You can export configurations for either selected rows or for entire screen. If the screen supports the “config” action button, then you can export the screen configuration.
To export the configuration, do the following:
- Go to your preferred UI or screen that supports config action button (applicable UIs or screens mentioned in the above list).
- Select the records to export.Note:
- If you are not selecting any records, the system exports all data available on the screen.
- Searching for a few rows and then exporting without selecting any record will still export all data (regardless of what was searched).
- On the right corner of the UI’s table, click “config” action button.
- In the drop-down options, click “export_configuration” option.
The system prompts to save the configuration file (.cfg file format) that needs to be downloaded in the local file system.
Note: You have to enable download permissions on your browser to download and save the export configuration file. - Select the folder location and click Save.
Import Configuration
You can import configurations to create new records or update existing records, but it does not delete existing records on the supported screen. If the screen supports the “config” action button, then you can export the screen configuration.
Importing configurations depends on the unique field names of the screens.
For example, assume that you have a task type description record “Internal Pick” on the source environment and on the target environment for Task Type UI.
If editing your source screen’s (Task Type) task type description to “Internal LPN Pick” and importing this configuration, the system will no longer find the “Internal Pick” task type description but creates a new “Internal LPN Pick” task type description record for the screen in the target environment.
The target environment for importing configurations can be:
- The same Facility/Company in the same environment. This is useful for restoring from a backup.
- A different Facility/Company but in the same environment. This is useful for replicating configurations done for one Facility in another Facility.
- The same Facility/Company in a different environment.
- A different Facility/Company in a different environment.
- The exported configuration file must be from an environment with a matching major release number (such as 23B or 23C).
- Currently, there is no support for automatic backup of the current configuration when an import is done. So, while importing configurations, it is always recommended to export configurations first for backup.
- The exported configuration file (.cfg file format) must be unedited manually.
To import the configuration, do the following:
- Go to the UI or screen that supports config action button (applicable UIs or screens mentioned in the above list).
- On the right corner of the UI’s table, click “config” action button.
- In the drop-down options, click “import_configuration” option.
- On the dialog box screen, click “Choose Files” button.
- Then, select the previously exported configuration file and click Upload.
Support Additional Tables in Purge Handling
The addition of new tables to our purge process delivers improved performance, helping optimize data retention and storage efficiency.
As part of the enhanced purge handling capabilities, we've introduced the option to purge records from the following tables according to a predefined schedule:
Table | Time frame to be purged |
---|---|
MHE_PICK_CONFIRMATION | 3 Months from current date. |
WMS_ACTIVITY | 3 Months from current date. |
INVENTORY_HISTORY | 5 years from the current date. |
AUDIT_HISTORY | 5 years from the current date. |
LPN_AUDIT_DTL | 5 years from the current date. |
PALLET_AUDIT_DTL | 5 years from the current date. |
OUTPUT_INTERFACE | 3 Months from current date. |
OUTPUT_INTERFACE_MSG_LOG | 3 Months from current date. |
LGFAPI_ARCHIVE | 3 Months from current date. |
STAGE_REPLENISHMENT_PICK | 3 Months from current date. |
SERIAL_NBR_HISTORY | 3 years from the current date. |
Serial Number History handles the history of Serial Number being linked, delinked, and shipped from LPNs.
NOTE: To avoid accidental loss of essential data during the purge, it's highly recommended to schedule regular API extractions or data exports for all critical information. This ensures a backup of historical data before it's removed by the automated purge processes.