Page History
...
Before the import process, all definitions are backed up and saved to the folder that contains the import file. See Preparing the settings import files on page 102.
The import settings command uses the following format:
...
Each dialog box requires its own import file. You can create this file either manually or by running the export settings command. See Export Settings command on page 100.
About the locations/locations-full settings import file
...
| Element | Description |
|---|---|
| Group name | The name of the group. May not exceed 20 characters. |
| Group technology | The technology code of the group. To find a valid code, see Table 7- 5 on page 103. |
| Group entity | The entity code of the corresponding technology. To find a valid code, see see Table 7- 5 on page 103. |
| Identifier name | The identifier text associated with the group. Full string and % wildcard characters allowed. |
| Group proxy_alias | The alias name of the warehouse system the Group is assigned to. '*' indicates all warehouse systems. |
The following table shows how the different grouping technologies can be mapped to entities.
Table 5 Mapping grouping technologies to entitiesAnchor Table5 Table5
...
| Element | Description |
|---|---|
| SLA name | The name of the SLA. May not exceed 20 characters. |
| SLA technology | The technology code of the SLA. To find a valid code, see Table 7-7 on page 104. |
| SLA entity | The entity code of the corresponding technology. To find a valid code, see see Table 7- 7 on page 104. |
| SLA Type | Either service time (S) or response time (R). To find the corresponding type for each technology, see see Table 7- 7 on page 104. |
| SLA proxy_alias | The alias name of the warehouse system the SLA is assigned to. '*' indicates all warehouse systems. |
The following table shows how the different SLA technologies can be mapped to entities.
Table 7 Mapping SLA technologies to entitiesAnchor Table7 Table7
...