Business Data Maintenance - Revision history

Anw: Added details of MCS Scanning changes

2025-09-16T10:41:23Z

Added details of MCS Scanning changes

← Older revision		Revision as of 12:41, 16 September 2025
Line 31:		Line 31:
	These codes can be used to record why a user has opted to perform a certain action, an example of this is when a user Reverses TI's they can enter the reason for the reversal. This table is now used to maintain non conformance codes for collections and deliveries.		These codes can be used to record why a user has opted to perform a certain action, an example of this is when a user Reverses TI's they can enter the reason for the reversal. This table is now used to maintain non conformance codes for collections and deliveries.

			If using Quarantine processing, you may set the action of new reason codes to "QUAR". This indicates that the reason code will add the item to quarantine, which may then be handled through the the [[Quarantine Maintenance]] screen.

	== Order Reason Codes ==		== Order Reason Codes ==

Anw: Split into separate pages

2025-06-27T09:32:09Z

Split into separate pages

← Older revision		Revision as of 11:32, 27 June 2025
Line 225:		Line 225:

	== Shift Patterns ==		== Shift Patterns ==
	~~You can maintain shift patterns here.~~		{{:Shift Patterns}}

	~~<center>[[Image~~:~~bdm_shift_patterns.jpg\|600px]]</center>~~

	~~Shift patterns must be unique and are applied to a particular depot.~~

	~~You can search for shifts for a depot, or see all.~~

	~~To create a new shift press the '''New''' button. You can only create new shifts for the depots you are associated with.~~

	~~To edit a shift press the '''Edit''' button. Only the days of the week and the times can be edited~~

	~~You can enter:~~
	* Depot
	* Shift Code - Unique to the shift pattern.
	* Shift Start - time
	* Shift End - time
	* Mon-Fri - checkboxes to which days of the week this shift applies.

	~~To delete a shift press the '''Delete''' button. Validation exists to ensure that you cannot delete a shift that has drivers associated with it.~~


	~~You can assign shifts to drivers using the Resources maintenance screen, or you can generate shifts for multiple drivers in this screen using the '''Generate Shifts''' button.~~

	~~<center>[[Image:bdm_generate_shifts.jpg\|600px]]</center>~~

	~~You will be prompted to enter a shift for the depot from a lookup, as well as a from and to date.~~
	~~You can then select all of the drivers to whom you wish to apply this shift and click '''Generate Shifts'''.~~

	~~<center>[[Image:bdm_generate_shifts_2.jpg\|600px]]</center>~~

	~~Validation exists to check that a driver is not already on a shift. If this occurs a message appears for each driver that cannot be allocated to the shift. All other drivers will be allocated.~~

	Further validation exists to check that one of the days between the first and last days entered corresponds to a day that the shift is associated with. If this occurs a warning message is shown as below:

	~~<center>[[Image:bdm_generate_shifts_3.jpg]]</center>~~

	~~Pressing the '''OK''' button will proceed to generate the shifts. Pressing the '''Cancel''' button will abandon the shift creation.~~


	~~You can see all users assigned to a particular shift by pressing '''Display Shifts'''.~~

	~~<center>[[Image:bdm_display_shifts.jpg\|600px]]</center>~~

	From this screen it is possible to change the search criteria to only bring back particular records. You can search on the driver, driver name, shift code and the from and to dates. Press the '''Refresh''' button to only bring back the records you are interested in. Press the '''Clear Search Criteria''' to bring back all records.

	~~On this screen you have the following buttons~~
	* '''New''' – this allows you to create a single record for a single driver.
	* '''Edit''' – this allows you to edit a single record. Only the from and to dates can be changed.
	* '''Delete''' – this allows you to delete a single or multiple records.
	* '''Save''' – this saves any changes you have made.
	* '''Close''' – closes the screen and returns to the shift patterns screen.


	~~You can also import~~ Shift Patterns ~~and assign shifts to drivers through [[Imports]]:~~
	* [[Imports_Details#SHIFT_PATT\|SHIFT_PATT]]
	* [[Imports_Details#DRIVER_SHIFT\|DRIVER_SHIFT]]

Anw: Patch 48 SCR-CTMS-03557646-18 Paragon interface

2025-04-14T12:00:51Z

Patch 48 SCR-CTMS-03557646-18 Paragon interface

← Older revision		Revision as of 14:00, 14 April 2025
Line 342:		Line 342:

	== Paragon Keys ==		== Paragon Keys ==
	This tab allows you to maintain Paragon Run Keys. This is required when using the Paragon Routing and Scheduling system through an API.		This tab allows you to maintain Paragon Run Keys.
			{{Note}} This is required when and specific to using the Paragon Routing and Scheduling system through an API.

			<center>[[Image:bdm_par_keys.png\|800px]]</center>


	<noinclude>		<noinclude>

Anw: Merged from training document

2024-06-10T10:43:45Z

Merged from training document

← Older revision		Revision as of 12:43, 10 June 2024
Line 140:		Line 140:
	* Routing Code		* Routing Code
	* Cost Centre		* Cost Centre


			{{Note}} When using Zones in the standard journeys for contracts, the system would have to look through all zones created on the system for other purposes like scheduling engine. Rather than consider zones that have not been defined for Finance, you may set up zones based on the areas for charging and click the "Rating" flag - the contracts function only looks at these zones.

Anw: Merged from training document

2024-06-05T09:57:45Z

Merged from training document

← Older revision		Revision as of 11:57, 5 June 2024
Line 54:		Line 54:

	<center>[[Image:bdm_order_status.jpg\|600px]]</center>		<center>[[Image:bdm_order_status.jpg\|600px]]</center>

			The CSTM checkbox is ticked if orders of the status can be sent to MTM.

			The CBR checkbox is ticked if orders of the status can be rebooked.


Line 238:		Line 242:

	To delete a shift press the '''Delete''' button. Validation exists to ensure that you cannot delete a shift that has drivers associated with it.		To delete a shift press the '''Delete''' button. Validation exists to ensure that you cannot delete a shift that has drivers associated with it.


	You can assign shifts to drivers using the Resources maintenance screen, or you can generate shifts for multiple drivers in this screen using the '''Generate Shifts''' button.		You can assign shifts to drivers using the Resources maintenance screen, or you can generate shifts for multiple drivers in this screen using the '''Generate Shifts''' button.
Line 249:		Line 254:

	Validation exists to check that a driver is not already on a shift. If this occurs a message appears for each driver that cannot be allocated to the shift. All other drivers will be allocated.		Validation exists to check that a driver is not already on a shift. If this occurs a message appears for each driver that cannot be allocated to the shift. All other drivers will be allocated.

	Further validation exists to check that one of the days between the first and last days entered corresponds to a day that the shift is associated with. If this occurs a warning message is shown as below:		Further validation exists to check that one of the days between the first and last days entered corresponds to a day that the shift is associated with. If this occurs a warning message is shown as below:

Line 277:		Line 283:
	== Team Details ==		== Team Details ==
	{{Note}} This is specific to session collection functionality.		{{Note}} This is specific to session collection functionality.

			<center>[[Image:bdm_team_details.jpg\|600px]]</center>

	Team master data will be created to link a team to a home depot for creating collection orders. The Team data including attributes to control the type of session that each team operates, whether the end session collection is required from transport, which depot the mid-session and end session collections should be delivered to and an optional validation period in minutes that that will control the planning for cold, normal and hot weather conditions.		Team master data will be created to link a team to a home depot for creating collection orders. The Team data including attributes to control the type of session that each team operates, whether the end session collection is required from transport, which depot the mid-session and end session collections should be delivered to and an optional validation period in minutes that that will control the planning for cold, normal and hot weather conditions.

Anw: Added cross-reference to associated imports

2024-06-04T09:20:17Z

Added cross-reference to associated imports

← Older revision		Revision as of 11:20, 4 June 2024
Line 268:		Line 268:
	* '''Save''' – this saves any changes you have made.		* '''Save''' – this saves any changes you have made.
	* '''Close''' – closes the screen and returns to the shift patterns screen.		* '''Close''' – closes the screen and returns to the shift patterns screen.


			You can also import Shift Patterns and assign shifts to drivers through [[Imports]]:
			* [[Imports_Details#SHIFT_PATT\|SHIFT_PATT]]
			* [[Imports_Details#DRIVER_SHIFT\|DRIVER_SHIFT]]

Anw: Added cross-reference to associated imports

2024-06-04T09:18:30Z

Added cross-reference to associated imports

← Older revision		Revision as of 11:18, 4 June 2024
Line 136:		Line 136:
	* Routing Code		* Routing Code
	* Cost Centre		* Cost Centre


			Location Zones may also be imported through [[Imports]]:
			* [[Imports_Details#LOC_ZONES\|LOC_ZONES]]

Anw: Minor correction

2024-05-17T13:46:41Z

Minor correction

Show changes

Anw: Minor formatting change

2024-05-17T13:37:39Z

Minor formatting change

← Older revision		Revision as of 15:37, 17 May 2024
Line 118:		Line 118:
	You can use this to maintain zones in the system.		You can use this to maintain zones in the system.

	Zones may be used by various areas of the system (e.g. fixed routes) to determine where the location is grouped ~~toegther~~, and therefore how to route to it from another location.		<center>[[Image:bdm_location_zones.png\|600px]]</center>

			Zones may be used by various areas of the system (e.g. fixed routes) to determine where the location is grouped together, and therefore how to route to it from another location.

	A zone can be maintained here with the following information:		A zone can be maintained here with the following information:
Line 135:		Line 137:
	* To Range		* To Range
	* Inactive		* Inactive
	* Inc/Exc - ~~include~~ or ~~exclude~~ the ~~range from~~ the zone.		* Inc/Exc - this flag indicates if the type of zone is being included or excluded from the location zone to enable greater flexibility to specify the delivery locations that are valid for the particular location zone.
	* Customer		* Customer
	* Routing Code		* Routing Code

Anw: Categorisation

2024-05-14T09:39:27Z

Categorisation

← Older revision		Revision as of 11:39, 14 May 2024
Line 327:		Line 327:
	This tab allows you to maintain Paragon Run Keys. This is required when using the Paragon Routing and Scheduling system through an API.		This tab allows you to maintain Paragon Run Keys. This is required when using the Paragon Routing and Scheduling system through an API.

			<noinclude>
	[[Category:Maintenance\|140]]		[[Category:Maintenance\|140]]
	[[Category:C-TMS Modules\|D-140]]		[[Category:C-TMS Modules\|D-140]]
	[[Category:C-TMS User Guide\|BD-140]]		[[Category:C-TMS User Guide\|BD-140]]
			</noinclude>