Owning Depot - Revision history

Anw: Categorisation

2025-05-06T14:40:42Z

Categorisation

← Older revision		Revision as of 16:40, 6 May 2025
Line 20:		Line 20:

	When a user has an assigned depot, most screens will automatically filter the data shown in the screens to show only the data matching the planning region or default depot. For example, the [[Planning]] screen will only show orders in the unscheduled order well from the planning regions owned by your depot, and trips from, to or through that owning depot configured against the user using the screen.		When a user has an assigned depot, most screens will automatically filter the data shown in the screens to show only the data matching the planning region or default depot. For example, the [[Planning]] screen will only show orders in the unscheduled order well from the planning regions owned by your depot, and trips from, to or through that owning depot configured against the user using the screen.

			<noinclude>[[Category:FAQ]]</noinclude>

Anw: Updated

2024-09-05T07:17:22Z

Updated

← Older revision		Revision as of 09:17, 5 September 2024
Line 16:		Line 16:


	Users can then be assigned a default depot ~~and planning region~~ through [[Access Control]].		Users can then be assigned a default depot through [[Access Control]]. Your user can be based at a single depot (set through the BASED_AT user parameter), or your user can have access to all depots (set through the ALL_DEPOTS user parameter).


	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 or default depot. For example, the [[Planning]] screen will only show orders in the unscheduled order well from ~~that~~ planning ~~region~~, and trips from, to or through that owning depot configured against the user using the screen.		When a user has an assigned depot, most screens will automatically filter the data shown in the screens to show only the data matching the planning region or default depot. For example, the [[Planning]] screen will only show orders in the unscheduled order well from the planning regions owned by your depot, and trips from, to or through that owning depot configured against the user using the screen.

Anw: Minor correction

2024-09-05T06:58:46Z

Minor correction

← Older revision		Revision as of 08:58, 5 September 2024
Line 19:		Line 19:


	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.		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 or default depot. For example, the [[Planning]] screen will only show orders in the unscheduled order well from that planning region, and trips from, to or through that owning depot configured against the user using the screen.

Anw: Minor formatting change

2024-09-05T06:56:25Z

Minor formatting change

← Older revision		Revision as of 08:56, 5 September 2024
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:

Anw: Updated

2024-09-05T06:55:32Z

Updated

← Older revision		Revision as of 08:55, 5 September 2024
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 ~~belongs~~ to "GBLIV"		* 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 ~~wants~~ to change this, ~~they change~~ in the CTMS Locations screen and tick "Retain Planning Region" before saving~~, so~~ system ~~doesn't~~ automatically reset it.		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]].


	~~The~~ screens will ~~then~~ filter the ~~orders'~~ planning ~~regions~~, ~~based on their locations~~		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.

Anw: Initial Creation

2024-05-17T10:27:30Z

Initial Creation

New page

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 belongs to "GBLIV"

Locations created are automatically assigned to the planning region based on the postcode.

If you wants to change this, they change in the CTMS Locations screen and tick "Retain Planning Region" before saving, so system doesn't automatically reset it.

Users can then be assigned a default depot and planning region.

The screens will then filter the orders' planning regions, based on their locations