270871 - Revision history

Middletong at 12:22, 1 March 2010

2010-03-01T12:22:20Z

← Older revision		Revision as of 14:22, 1 March 2010
Line 102:		Line 102:

	\|}		\|}

			Back to [[CONPRD Release - 24/02/2010]]

Middletong at 12:01, 1 March 2010

2010-03-01T12:01:01Z

← Older revision		Revision as of 14:01, 1 March 2010
Line 7:		Line 7:


	=~~Functional Overview~~=		=FUNCTIONAL OVERVIEW=

	==Client Requirement==		==Client Requirement==
Line 38:		Line 38:
	A field will be added to the select statement, SCH_ORD_AUDIT.ACTION_DATE where SCH_ORD_AUDIT.ORD_CHANGE =’POD Changed from N to Y’. To ensure that records which do not have a POD date are excluded, the table will be added to the cursor with an outer join and the ORD_CHANGE condition will include an outer join. The outer join will ensure that records are not excluded where the POD has not bee changed. In this instance , the action date field will be returned as a null value.		A field will be added to the select statement, SCH_ORD_AUDIT.ACTION_DATE where SCH_ORD_AUDIT.ORD_CHANGE =’POD Changed from N to Y’. To ensure that records which do not have a POD date are excluded, the table will be added to the cursor with an outer join and the ORD_CHANGE condition will include an outer join. The outer join will ensure that records are not excluded where the POD has not bee changed. In this instance , the action date field will be returned as a null value.

	=~~Functional Description~~=		=FUNCTIONAL DESCRIPTION=
	After making the amendments to the cursor which extracts the data, we must also add the new field POD Received Date to the extract. The field will be displayed at the end of the existing data.		After making the amendments to the cursor which extracts the data, we must also add the new field POD Received Date to the extract. The field will be displayed at the end of the existing data.

Line 46:		Line 46:


	= ~~References~~ =		= REFERENCES =

	{\| Border="1"		{\| Border="1"
Line 62:		Line 62:


	= ~~Document History~~ =		= DOCUMENT HISTORY =

	{\| Border="1"		{\| Border="1"
Line 87:		Line 87:


	= ~~Authorised By~~ =		= AUTHORISED BY =

Middletong: /* Functiona Overview */

2010-03-01T11:58:27Z

Functiona Overview

← Older revision		Revision as of 13:58, 1 March 2010
Line 7:		Line 7:


	=~~Functiona~~ Overview=		=Functional Overview=

	==Client Requirement==		==Client Requirement==
Line 28:		Line 28:

	==Scope==		==Scope==
	This change will be applied to system version 10.5.0 on CONTST and once approved CONPRD.		This change will be applied to system version 10.5.0 on CONTST and once approved CONPRD.

	=SET-UP=		=SET-UP=

Middletong at 11:58, 1 March 2010

2010-03-01T11:58:10Z

← Older revision		Revision as of 13:58, 1 March 2010
Line 10:		Line 10:

	==Client Requirement==		==Client Requirement==
			Changes to CTMS Report CN Trip and Order DetailAllan Butterworth/St Albans/UK/Exel
			Change Request Details:
			*Change the Report parameters so that the report only includes 'UNLOAD' activity name.
			*Include a column for POD Recieved Date and populate from Database


	==Solution==		==Solution==
			Amend the existing procedure CSV.WRITE_CN_TRIP_ORDER_DETAIL.
			The existing cursor C_TRIP_ORDER will be changed to include the following selection criteria

			SCH_HAULAGE.ACTIVITY_NAME = ‘Unload’

			To include POD_Received_Date , the cursor will also be updated to select ACTION_DATE from the order audit table SCH_ORD_AUDIT, where the ORD_CHANGE = 'POD changed from N to Y.' Using the audit table rather than the interface table means that POD_Received_Date will be populated when the POD has been manually applied and the extract will run quicker as OMS_REF is a primary key of the audit table.

			The procedure will be updated to display the new field in the extract, at the end of the existing information.


	==Scope==		==Scope==
			This change will be applied to system version 10.5.0 on CONTST and once approved CONPRD.

			=SET-UP=
	==Data==		==Data==
			The data selected by the cursor C_TRIP_ORDER will be amended.

			A condition will be added based on SCH_HAULAGE_ACTIVITY, where activity_name = ‘UNLOAD’.

			A field will be added to the select statement, SCH_ORD_AUDIT.ACTION_DATE where SCH_ORD_AUDIT.ORD_CHANGE =’POD Changed from N to Y’. To ensure that records which do not have a POD date are excluded, the table will be added to the cursor with an outer join and the ORD_CHANGE condition will include an outer join. The outer join will ensure that records are not excluded where the POD has not bee changed. In this instance , the action date field will be returned as a null value.

	=Functional Description=		=Functional Description=
			After making the amendments to the cursor which extracts the data, we must also add the new field POD Received Date to the extract. The field will be displayed at the end of the existing data.

			[[Image:270871_1.png]]

			If an audit record exists for the oms_ref with the required ORD_CHANGE of ‘POD changed from N to Y’, the new field will be populated with the ACTION_DATE value, otherwise the new field will be null.


	= References =		= References =
Line 30:		Line 56:
	\|-		\|-
	\| <center>1</center>		\| <center>1</center>
	\| EST~~-259410~~ PA-~~7MKDYG~~ CN ~~Loading Schedule Report~~ Changes v1.~~doc~~		\| EST 270871 PA-7X9EDF CN Trip and Order Detail Changes v1.0
	\| <center>1</center>		\| <center>1.0</center>
	\| <center>06/01/09</center>		\| <center>03/11/09</center>
	\|}		\|}

Line 46:		Line 72:

	\|-		\|-
	\| <center>1a</center>		\| <center>0.1</center>
	\| <center>12~~/01~~/09</center>		\| <center>30/12/09</center>
	\| <center>Draft</center>		\| <center>Draft</center>
	\| Initial version		\| Initial version
	\| <center>~~PDR~~</center>		\| <center>SW</center>

	\|-		\|-
	\| <center>1</center>		\| <center>1.0</center>
	\| <center>12~~/01~~/09</center>		\| <center>30/12/09</center>
	\| <center>Issue</center>		\| <center>Issue</center>
	\| Reviewed and Issued		\| Reviewed and Issued
	\| <center>~~MJC~~</center>		\| <center>SW</center>
	\|}		\|}

Middletong: New page: =270871 - PA-7X9EDF/ CN Trip and Order Detail Change= Copyright OBS Logistics © 2009 The information contained herein is the property of OBS Logistics and is supplied without liabilit...

2010-03-01T11:39:42Z

New page

=270871 - PA-7X9EDF/ CN Trip and Order Detail Change=

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

=Functiona Overview=

==Client Requirement==

==Solution==

==Scope==

==Data==

=Functional Description=

= References =

{| Border="1"
| <center>'''Ref No'''</center>
| <center>'''Document Title & ID'''</center>
| <center>'''Version'''</center>
| <center>'''Date'''</center>

|-
| <center>1</center>
| EST-259410 PA-7MKDYG CN Loading Schedule Report Changes v1.doc
| <center>1</center>
| <center>06/01/09</center>
|}

= Document History =

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>1a</center>
| <center>12/01/09</center>
| <center>Draft</center>
| Initial version
| <center>PDR</center>

|-
| <center>1</center>
| <center>12/01/09</center>
| <center>Issue</center>
| Reviewed and Issued
| <center>MJC</center>
|}

= Authorised By =

{| Border="1"
| '''''Matt Crisford'''''
| Development Manager
|

|-
| '''''Peter Greer'''''
| TMSCC MTS Product Manager
|

|}