Difference between revisions of "Locations"
From Commander4j Wiki
(Created page with "File:Location_Admin.jpg <br> You will need to define at least one location within the database before using the application in production. A location is identified by a si...") |
|||
| (11 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | [[File:Location_Admin. | + | [[File:Location_Admin.png|800px|thumb|left|Location Admin]] |
| + | <br> | ||
<br> | <br> | ||
You will need to define at least one location within the database before using the application in production. A location is identified by a single name. However you can associate a number of attributes to the location which will be included in messages to external applications. The messages generated by Commander are partly controlled by the Interface Admin screen, and partly by the settings for the locations involved in any given transaction.<br><br> | You will need to define at least one location within the database before using the application in production. A location is identified by a single name. However you can associate a number of attributes to the location which will be included in messages to external applications. The messages generated by Commander are partly controlled by the Interface Admin screen, and partly by the settings for the locations involved in any given transaction.<br><br> | ||
A location can be whatever you want, a site, a factory, a warehouse, a rack, a bay, a shelf. Just try and construct some meaningful and logical structure for your Location Id keys.<br>The default location for Pallets created by Commander is determined by the Location Id of the [[Process Orders|Process Order]] referenced during the [[Production Declaration]] transaction..<br><br> | A location can be whatever you want, a site, a factory, a warehouse, a rack, a bay, a shelf. Just try and construct some meaningful and logical structure for your Location Id keys.<br>The default location for Pallets created by Commander is determined by the Location Id of the [[Process Orders|Process Order]] referenced during the [[Production Declaration]] transaction..<br><br> | ||
| − | [[File: | + | [[File:Location Edit.png|400px|thumb|left|Location Edit]] |
{| border="1" | {| border="1" | ||
| Line 54: | Line 55: | ||
! scope="row" | Message Status Change | ! scope="row" | Message Status Change | ||
|| Select if you want to generate a message when a pallet status is amended. | || Select if you want to generate a message when a pallet status is amended. | ||
| + | |- | ||
| + | ! scope="row" | Message Journey Ref | ||
| + | || Select if you want to force the user to select a [[Journey Reference]] number when despatching product. | ||
|- | |- | ||
! scope="row" | Permit Pallet Status | ! scope="row" | Permit Pallet Status | ||
Latest revision as of 15:06, 21 December 2023
You will need to define at least one location within the database before using the application in production. A location is identified by a single name. However you can associate a number of attributes to the location which will be included in messages to external applications. The messages generated by Commander are partly controlled by the Interface Admin screen, and partly by the settings for the locations involved in any given transaction.
A location can be whatever you want, a site, a factory, a warehouse, a rack, a bay, a shelf. Just try and construct some meaningful and logical structure for your Location Id keys.
The default location for Pallets created by Commander is determined by the Location Id of the Process Order referenced during the Production Declaration transaction..
| Field | Description |
|---|---|
| Location Id | Unique Identification for Location - (20 characters) |
| Plant | Optional Plant / Site Identification - is included in messaging. |
| Warehouse | Optional Warehouse Identification - is included in messaging. |
| GLN | Optional Global Location Number (GLN) - is included in messaging. |
| Description | Description of this location. |
| Location | Optional - Sub Location Id - is included in messaging. |
| Type | Optional - Type- is included in messaging. |
| Section | Optional - Section - is included in messaging. |
| Bin | Optional - Bin- is included in messaging. |
| Equipment Tracking Id | Optional - used in conjunction with Equipment Type within Materials for Pallet Tracking. |
| Message Despatch Confirm | Select if you want to generate a message when a despatch is confirmed. |
| Message Equipment Tracking | Select if you want to generate a message when a despatch is confirmed. |
| Message Despatch Pre Advice | Select if you want to generate a message when a despatch is confirmed. |
| Message Production Confirm | Select if you want to generate a message when a pallet is confirmed. |
| Message Status Change | Select if you want to generate a message when a pallet status is amended. |
| Message Journey Ref | Select if you want to force the user to select a Journey Reference number when despatching product. |
| Permit Pallet Status | Select those values which are permitted in this location - validation when adding pallets to despatch. Use keyboard shortcuts CTRL / SHIFT etc to select multiple values etc. |
| Permit Batch Status | Select those values which are permitted in this location - validation when adding pallets to despatch. Use keyboard shortcuts CTRL / SHIFT etc to select multiple values etc. |
