Owning Depot: Difference between revisions
(Initial Creation) |
(Updated) |
||
| Line 1: | Line 1: | ||
Owning Depot is defined as the depot that is responsible for planning a trip, and is used by access control to determine whether a planner should see an orders or trips for planning.. | Owning Depot is defined as the depot that is responsible for planning a trip, and is used by access control to determine whether a planner should see an orders or trips for planning.. | ||
This logic depends on the creation of the following data: | This logic depends on the creation of the following data: | ||
| Line 6: | Line 5: | ||
* Create planning regions through postcode. | * Create planning regions through postcode. | ||
* Use [[Static Data]] Region Depot to link a planning region to a depot. | * Use [[Static Data]] Region Depot to link a planning region to a depot. | ||
* Set up planning regions by postal region i.e. L | * Set up planning regions by postal region i.e. "L" could be assigned to a region "GBLIV" or "GBNW". | ||
Locations created are automatically assigned to the planning region based on the postcode. | Locations created are automatically assigned to the planning region based on the postcode. | ||
If you | The postcode is extracted according to the rules applied against the [[Countries]]. So, for GB, the postal region is extracted. For example, for a location with an address "L24 1XZ", the postal region "L" is extracted, and for postcode "NG6 8UZ", the postal region is "NG" (Nottingham). | ||
If you want to change this automatic assignment, this can be done in the CTMS [[Locations]] screen - change the planning region in the screen against the location and tick "Retain Planning Region" before saving - the new region will be saved and the system will not automatically reset it. | |||
Users can then be assigned a default depot and planning region. | Users can then be assigned a default depot and planning region through [[Access Control]]. | ||
When a user has an assigned planning region, most screens will automatically filter the data shown in the screens to show only the data matching the planning region, for example, the [[Planning]] screen, when showing orders in the unscheduled order well. | |||
Revision as of 08:55, 5 September 2024
Owning Depot is defined as the depot that is responsible for planning a trip, and is used by access control to determine whether a planner should see an orders or trips for planning..
This logic depends on the creation of the following data:
- Create planning regions through postcode.
- Use Static Data Region Depot to link a planning region to a depot.
- Set up planning regions by postal region i.e. "L" could be assigned to a region "GBLIV" or "GBNW".
Locations created are automatically assigned to the planning region based on the postcode.
The postcode is extracted according to the rules applied against the Countries. So, for GB, the postal region is extracted. For example, for a location with an address "L24 1XZ", the postal region "L" is extracted, and for postcode "NG6 8UZ", the postal region is "NG" (Nottingham).
If you want to change this automatic assignment, this can be done in the CTMS Locations screen - change the planning region in the screen against the location and tick "Retain Planning Region" before saving - the new region will be saved and the system will not automatically reset it.
Users can then be assigned a default depot and planning region through Access Control.
When a user has an assigned planning region, most screens will automatically filter the data shown in the screens to show only the data matching the planning region, for example, the Planning screen, when showing orders in the unscheduled order well.
