249771: Difference between revisions
Middletong (talk | contribs) |
Middletong (talk | contribs) No edit summary |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
= | = 261673-MA-7PCNBY Add Fields to CN Warehouse Extract= | ||
Copyright OBS Logistics © | Copyright OBS Logistics © 2009 | ||
The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied | The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied | ||
= | = Functional Overview = | ||
== Client Requirement == | == Client Requirement == | ||
Amend the code referenced in the Trip Manipulation, Trip Planning and Trip Summary forms so that the Owning Depot is applied to a trip based on the following: | Amend the code referenced in the Trip Manipulation, Trip Planning and Trip Summary forms so that the Owning Depot is applied to a trip based on the following: | ||
8When a Carrier is applied to a Trip the Owning Depot should be the Hub Location assigned to that Carrier (in resource maintenance), this is regardless of whether Start and End at Hub is enforced. | |||
*If a Trip is created and saved with a Carrier that does not have a Hub Location (i.e. Haulier) the Owning Depot should default to the first RDC stop on the Trip, regardless of whether this is PK or DL. | |||
*If there are no stops on the Trip associated with an RDC location the user should not be able to save the Trip without manually assigning an Owning Depot, this should be reflected in a message which I believe is currently in place: "Changes cannot be saved as Owning Depot is NULL". | |||
As part of this development the functionality currently used to prompt a user to enter a carrier when creating a Trip should be added to the Apply via x-dock locations function. In addition to this the code should be amended to prevent a Trip being saved without a Carrier having been applied (Fixed Routes will need to be checked as part of this to ensure it will follow the correct rule). | As part of this development the functionality currently used to prompt a user to enter a carrier when creating a Trip should be added to the Apply via x-dock locations function. In addition to this the code should be amended to prevent a Trip being saved without a Carrier having been applied (Fixed Routes will need to be checked as part of this to ensure it will follow the correct rule). | ||
== Solution == | == Solution == | ||
The existing code, in Trip Manipulation, Trip Planning and Trip Summary forms, will be changed so that the owning deport is applied to the trip based on the rules below. | The existing code, in Trip Manipulation, Trip Planning and Trip Summary forms, will be changed so that the owning deport is applied to the trip based on the rules below. | ||
*When a Carrier is applied to a Trip the Owning Depot will be defaulted to the Hub Location assigned to that Carrier (from table RES_CARRIER column HUB_LOCATION), this is regardless of whether start and End at Hub is enforced. | |||
*If a Trip is created and saved with a Carrier that does not have a Hub Location (i.e. Haulier) the Owning Depot will default to the first RDC stop on the Trip, regardless of whether this is PK or DL. | |||
*If there are no stops on the Trip associated with an RDC location then the message "Changes cannot be saved as Owning Depot is NULL" will be displayed and the user will not be able to save the Trip without manually assigning an Owning Depot. | |||
A new field will be added to the Apply x-dock pop-up window to accommodate the carrier. The User will be forced to enter a carrier before the trip can be saved. | A new field will be added to the Apply x-dock pop-up window to accommodate the carrier. The User will be forced to enter a carrier before the trip can be saved. | ||
== Scope == | == Scope == | ||
This change will be applied to system version 10.6. | This change will be applied to system version 10.6. | ||
= | = Functional Description = | ||
== Owning Depot. == | == Owning Depot. == | ||
The owning depot will be taken from one of three places. The first place that will be used is the Hub location that has been assigned to the carrier. This is stored on the REC_CARRIER table, column HUB_LOCATION. This value will be used regardless of whether the start and end hub has been enforced. | The owning depot will be taken from one of three places. The first place that will be used is the Hub location that has been assigned to the carrier. This is stored on the REC_CARRIER table, column HUB_LOCATION. This value will be used regardless of whether the start and end hub has been enforced. | ||
[[Image:249771_1.png]] | |||
| Line 54: | Line 46: | ||
[[Image:249771_2.png]] | |||
| Line 61: | Line 52: | ||
[[Image:249771_3.PNG]] | |||
| Line 86: | Line 77: | ||
|} | |} | ||
= Document History = | |||
{| Border="1" | {| Border="1" | ||
| <center>'''Version'''</center> | | <center>'''Version'''</center> | ||
| Line 135: | Line 122: | ||
|} | |} | ||
= Authorised By = | |||
{| Border="1" | {| Border="1" | ||
Latest revision as of 17:43, 13 October 2009
261673-MA-7PCNBY Add Fields to CN Warehouse Extract
Copyright OBS Logistics © 2009
The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied
Functional Overview
Client Requirement
Amend the code referenced in the Trip Manipulation, Trip Planning and Trip Summary forms so that the Owning Depot is applied to a trip based on the following:
8When a Carrier is applied to a Trip the Owning Depot should be the Hub Location assigned to that Carrier (in resource maintenance), this is regardless of whether Start and End at Hub is enforced.
- If a Trip is created and saved with a Carrier that does not have a Hub Location (i.e. Haulier) the Owning Depot should default to the first RDC stop on the Trip, regardless of whether this is PK or DL.
- If there are no stops on the Trip associated with an RDC location the user should not be able to save the Trip without manually assigning an Owning Depot, this should be reflected in a message which I believe is currently in place: "Changes cannot be saved as Owning Depot is NULL".
As part of this development the functionality currently used to prompt a user to enter a carrier when creating a Trip should be added to the Apply via x-dock locations function. In addition to this the code should be amended to prevent a Trip being saved without a Carrier having been applied (Fixed Routes will need to be checked as part of this to ensure it will follow the correct rule).
Solution
The existing code, in Trip Manipulation, Trip Planning and Trip Summary forms, will be changed so that the owning deport is applied to the trip based on the rules below.
- When a Carrier is applied to a Trip the Owning Depot will be defaulted to the Hub Location assigned to that Carrier (from table RES_CARRIER column HUB_LOCATION), this is regardless of whether start and End at Hub is enforced.
- If a Trip is created and saved with a Carrier that does not have a Hub Location (i.e. Haulier) the Owning Depot will default to the first RDC stop on the Trip, regardless of whether this is PK or DL.
- If there are no stops on the Trip associated with an RDC location then the message "Changes cannot be saved as Owning Depot is NULL" will be displayed and the user will not be able to save the Trip without manually assigning an Owning Depot.
A new field will be added to the Apply x-dock pop-up window to accommodate the carrier. The User will be forced to enter a carrier before the trip can be saved.
Scope
This change will be applied to system version 10.6.
Functional Description
Owning Depot.
The owning depot will be taken from one of three places. The first place that will be used is the Hub location that has been assigned to the carrier. This is stored on the REC_CARRIER table, column HUB_LOCATION. This value will be used regardless of whether the start and end hub has been enforced.
If the Carrier on the trip does not have a hub assigned, the owning depot will be set to the first RDC stop on the TRIP.
Finally if the carrier does not have a hub assigned and there is no Stops associated with an RDC, a message will be displayed prompting the user to assign a depot manually. The user will not be able to save the trip until an owning depot is assigned.
An owning depot field will be added to the Trip Summary screen to allow the users to manually enter the owning depot if required. The Trip Manipulation and planning screens already have an owning depot field.
When creating a X-dock trip the user will be able to add a carrier to the trip(s). A new field will be added to the X-dock pop up screen to allow the carrier to be entered. If a carrier is entered the owning depot will default as detailed above. If no carrier is entered the owning depot will default to the first RDC stop on the trip. If the owning depot is still NULL no changes will be allowed to the trip until the owning depot is manually entered by the user.
As part of this change the fixed routes screen will be changed to follow the same rules mentioned, above.
When generating trips from fixed routes, the owning depot of the trip will be defined based on the rules:-
If carrier has a hub location this will be used.
If the carrier does not have a hub location, the owning depot will be the first RDC stop on the trip
If there is no RDC stop on the trip the owning depot will be the Depot the user has entered, and if this is null the user will be required to enter a depot manually.
References
| EST-249771 AS-765E9J Fix to Owning Depot Issue v1.doc |
Document History
| Initial version | ||||
| Initial Review | ||||
| Review | ||||
| Review and Issue | ||||
| Review (Fixed Routed Process) |
Authorised By
| Dave Meir | Development Manager |
|
| Suk Sandhu | TMSCC MTS Product Manager |
