Locations: Difference between revisions
Created page with " [[file:Location_Admin.png|600px] Locations within Commander4j allow you to record where a Pallet (SSCC) is located. Each location record consists of a short human friendly name for the location and a number of optional fields which can be used to attach additional information. On the location properties screen you will also see a number of check box's next to transaction/message flags. These flags determine if certain messages are generated as a result of transactions..." |
No edit summary |
||
| Line 1: | Line 1: | ||
[[file:Location_Admin.png|600px] | [[file:Location_Admin.png|600px]] | ||
Locations within Commander4j allow you to record where a Pallet (SSCC) is located. Each location record consists of a short human friendly name for the location and a number of optional fields which can be used to attach additional information. | Locations within Commander4j allow you to record where a Pallet (SSCC) is located. Each location record consists of a short human friendly name for the location and a number of optional fields which can be used to attach additional information. | ||
Revision as of 12:49, 19 August 2024
Locations within Commander4j allow you to record where a Pallet (SSCC) is located. Each location record consists of a short human friendly name for the location and a number of optional fields which can be used to attach additional information.
On the location properties screen you will also see a number of check box's next to transaction/message flags. These flags determine if certain messages are generated as a result of transactions within the application. These messages are typically used to update external systems.
Against each location there are some Batch and Pallet status indicators which determine if a SSCC can be moved into this location.