261850: Difference between revisions
(New page: ==261850 PA-7NVD2L Change Consolidation Trigger== {| class="prettytable" | <div align="right">'''Version :'''</div> | <center>'''1.0'''</center> |} '''Copyright OBS Logistics © 2009''' ...) |
Middletong (talk | contribs) No edit summary |
||
| Line 9: | Line 9: | ||
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 | ||
= Funcional Overview = | |||
== Client Requirement == | == Client Requirement == | ||
| Line 44: | Line 48: | ||
{| | {| Border="1" | ||
| '''System Parameter''' | | '''System Parameter''' | ||
| '''Trip Status - ‘ACCEPTED’''' | | '''Trip Status - ‘ACCEPTED’''' | ||
| Line 84: | Line 88: | ||
* [[TRIPSUM]] | * [[TRIPSUM]] | ||
=References= | |||
{| | {| Border="1" | ||
| <center>'''Ref No'''</center> | | <center>'''Ref No'''</center> | ||
| <center>'''Document Title & ID'''</center> | | <center>'''Document Title & ID'''</center> | ||
| Line 101: | Line 105: | ||
|} | |} | ||
=Document History= | |||
{| | {| Border="1" | ||
| <center>'''Version'''</center> | | <center>'''Version'''</center> | ||
| <center>'''Date'''</center> | | <center>'''Date'''</center> | ||
| Line 148: | Line 152: | ||
|} | |} | ||
=Authorised By= | |||
{| | {| Border="1" | ||
| '''''Matt Crisford''''' | | '''''Matt Crisford''''' | ||
| Development Manager | | Development Manager | ||
Latest revision as of 16:02, 21 September 2009
261850 PA-7NVD2L Change Consolidation Trigger
Version :
|
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
Funcional Overview
Client Requirement
Currently quantity consolidation by Customer or Customer Group is triggered by a trip being taken to an ‘ACCEPTED’ status - change this to being activated at ‘PLANNED’ status. Any orders added or deleted from a trip would require the Trip to be revalidated to recalculate the Trip revenue.
Solution
The consolidation by customer or customer group is handled by a procedure called process shipment within the package TRM. This procedure is currently only called when the trip is at status ‘ACCEPTED’.
A system registry parameter will be added to control the functionality. The registry will determine which statuses will trigger the consolidation. The options for the registry will be ‘PLANNED’, ‘ACCEPTED’ or ‘BOTH’. If no value is set for the registry parameter then the consolidation will trigger at status ‘ACCEPTED’ as per existing functionality.
The trip will be revalidated whenever an order is added or deleted and this will then recalculate the trip revenue.
Set-up
Data
A new system parameter called ‘TRM_STATUS_FOR_CONSOLIDATION’ will be required and should be set to the trip status required for the new functionality to be operative:
Functional Description
Change to ‘TRM’ package
The function ‘PROCESS_SHIPMENT’ in the ‘TRM’ package will be called in the ‘TRIPSUM’ form via the function ‘VALIDATE_TRIP’ in the ‘TRM’ package via the function ‘SET_TRIP_STATUS’ in the ‘TRM’ package.
If the trip status is updated at present to be one of the following then the function ‘PROCESS_SHIPMENT’ will not be run:
- PLANNED
- DELETED
- REJECTED
- CANCELLED
- ABANDONED
- SEMI_FIXED
Therefore, the function ‘VALIDATE_TRIP’ will need to include or exclude the trip status ‘ACCEPTED’ or ‘PLANNED’ based on the setting of the new system parameter ‘TRM_STATUS_FOR_CONSOLIDATION’.
The processing for the trip status may be summarised as follows:
| System Parameter | Trip Status - ‘ACCEPTED’ | Trip Status – ‘PLANNED’ |
| ACCEPTED | INCLUDED | EXCLUDED |
| PLANNED | EXCLUDED | INCLUDED |
| BOTH | INCLUDED | INCLUDED |
| NULL | INCLUDED | EXCLUDED |
If the new system parameter has not been setup then the existing functionality will be retained so that ‘PLANNED’ is excluded from processing.
The new system parameter will not affect the exclusion of the trip status, as listed above, except for ‘PLANNED’.
The function ‘SET_TRIP_STATUS’ may be called by the following forms:
References
| EST-261850 PA-7NVD2L Change Consolidation Trigger v1.0.doc |
Document History
| Initial version | ||||
| Reviewed and Issued | ||||
Authorised By
| Matt Crisford | Development Manager | |
| Suk Sandhu | TMSCC MTS Product Manager |
