291361 - Revision history

Admin: /* Order Confirmation Report */

2012-05-10T15:47:08Z

Order Confirmation Report

← Older revision		Revision as of 17:47, 10 May 2012
Line 292:		Line 292:
	\|-		\|-
	\| style="border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| DELIVERY_DATE_TIME		\| style="border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| DELIVERY_DATE_TIME
	\| style="border:0.018cm solid #000000;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| SCH_ORD.EARLY_DEL\|\|SCH_ORD.LATE_DEL		\| style="border:0.018cm solid #000000;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| SCH_ORD.EARLY_DEL SCH_ORD.LATE_DEL

	\|-		\|-

Admin: /* Order Confirmation Report */

2012-05-10T15:46:29Z

Order Confirmation Report

Admin: /* Order Confirmation Report */

2012-05-10T15:44:39Z

Order Confirmation Report

← Older revision		Revision as of 17:44, 10 May 2012
Line 220:		Line 220:
	\|-		\|-
	\| style="border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| COLLECTION_CONTACT		\| style="border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| COLLECTION_CONTACT
	\| style="border:0.018cm solid #000000;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| GEO_CONTACT.FORENAME\|\| GEO_CONTACT.SURNAME		\| style="border:0.018cm solid #000000;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| GEO_CONTACT.FORENAME GEO_CONTACT.SURNAME

	\|-		\|-

Admin: /* Order Confirmation Report */

2012-05-10T15:43:50Z

Order Confirmation Report

← Older revision		Revision as of 17:43, 10 May 2012
Line 205:		Line 205:
	== Order Confirmation Report ==		== Order Confirmation Report ==
	A new report called ‘Order Confirmation’ report will be created in Oracle reports and will generate a PDF file. The report will include Order details and some trip details in the Processed Format.		A new report called ‘Order Confirmation’ report will be created in Oracle reports and will generate a PDF file. The report will include Order details and some trip details in the Processed Format.



	{\| style="border-spacing:0;"		{\| style="border-spacing:0;"

Admin: /* Order Events */

2012-05-10T15:43:36Z

Order Events

← Older revision		Revision as of 17:43, 10 May 2012
Line 145:		Line 145:
	== Order Events ==		== Order Events ==
	When an order is validated and set to Status UNSCHEDULED for the first time on the system, a record will be added to the MSG_EVENT table to generate an email to the requestor. In addition, whenever the order is scheduled and the trip is set to ACCEPTED, a record will also be added to the control table MSG_EVENT for each order on the trip with a requestor_email record. (NB this could be more than once)		When an order is validated and set to Status UNSCHEDULED for the first time on the system, a record will be added to the MSG_EVENT table to generate an email to the requestor. In addition, whenever the order is scheduled and the trip is set to ACCEPTED, a record will also be added to the control table MSG_EVENT for each order on the trip with a requestor_email record. (NB this could be more than once)


	~~''Developer Notes, the code to insert the record will be written in the TI_SCH_ORD_STATUS_TRIGGER, when the status changes from INVALID to UNSCHEDULED and in TIU_TRIP_STATUS trigger.''~~



	{\| style="border-spacing:0;"		{\| style="border-spacing:0;"
Line 207:		Line 202:

	A record will only be added to the MESSAGE_EVENT table if an order has been assigned a requestor_email record. If a trip is set back to PLANNED and the carrier is changed, another record will be added into the MESSAGE_EVENT table for the trip.		A record will only be added to the MESSAGE_EVENT table if an order has been assigned a requestor_email record. If a trip is set back to PLANNED and the carrier is changed, another record will be added into the MESSAGE_EVENT table for the trip.


	== Order Confirmation Report ==		== Order Confirmation Report ==

Admin: /* Solution */

2012-05-10T15:42:57Z

Solution

← Older revision		Revision as of 17:42, 10 May 2012
Line 18:		Line 18:
	== Solution ==		== Solution ==
	'''Additional References/Message Types:'''		'''Additional References/Message Types:'''


	The additional references functionality provided by the orders screen will be used to receive and store the requestor name and requestor email address. This data will be either manually entered or captured through the CSV order import facility or captured through the XML order EDI interface.		The additional references functionality provided by the orders screen will be used to receive and store the requestor name and requestor email address. This data will be either manually entered or captured through the CSV order import facility or captured through the XML order EDI interface.


	The requestor name and email address will be used to send an order received email as soon as the order is received into C-TMS, then later in the transport process, once the order is planned and a carrier assigned, a confirmation email is sent to the requestor. The order received and order confirmed emails will contain an attached PDF document formatted as shown below		The requestor name and email address will be used to send an order received email as soon as the order is received into C-TMS, then later in the transport process, once the order is planned and a carrier assigned, a confirmation email is sent to the requestor. The order received and order confirmed emails will contain an attached PDF document formatted as shown below


	[[Image:]][[Image:]]		[[Image:]][[Image:]]
Line 30:		Line 27:

	'''Order Capture:'''		'''Order Capture:'''


	The C-TMS order interface will be configured so that the requestor and email address can be uploaded into pre-defined additional reference fields. If more than one destination email address is required the reference field in the interface mapping will presented as a concatenation of the email addresses separated by “;” (semi-colon).		The C-TMS order interface will be configured so that the requestor and email address can be uploaded into pre-defined additional reference fields. If more than one destination email address is required the reference field in the interface mapping will presented as a concatenation of the email addresses separated by “;” (semi-colon).


	The CSV order import will be modified to allow the requestor and email address to be uploaded with each order.		The CSV order import will be modified to allow the requestor and email address to be uploaded with each order.


	If manually keyed, the additional reference for the requestor and email address can be keyed into the Add Refs Tab of the order detail screen.		If manually keyed, the additional reference for the requestor and email address can be keyed into the Add Refs Tab of the order detail screen.


	Note – The system parameter that holds the default sending email address will be set up to be the value ‘dhlroad@networkrail.co.uk’. Note this will need to be done at the cost centre level of system parameters.		Note – The system parameter that holds the default sending email address will be set up to be the value ‘dhlroad@networkrail.co.uk’. Note this will need to be done at the cost centre level of system parameters.


	Once the requestor email addresses have been captured and the order validated (UNSCHEDULED status) a message will be queued before a the existing C-TMS email process will activate on a five minute schedule to send any new emails.		Once the requestor email addresses have been captured and the order validated (UNSCHEDULED status) a message will be queued before a the existing C-TMS email process will activate on a five minute schedule to send any new emails.
Line 48:		Line 40:

	'''Email Attachments:'''		'''Email Attachments:'''


	An Oracle report will be developed to generate the two PDF documents that form the attachment to the emails. The output is very similar for both the received and confirmed outputs. The confirmed output in addition shows the details of the appointed carrier providing the transportation.		An Oracle report will be developed to generate the two PDF documents that form the attachment to the emails. The output is very similar for both the received and confirmed outputs. The confirmed output in addition shows the details of the appointed carrier providing the transportation.
Line 54:		Line 45:

	'''Email Processing:'''		'''Email Processing:'''


	A database job will run on C-TMS looking for NEW queued received and confirmed emails to send. As these are recognised, the existing process will identify queued records, generate the report output, attach to an appropriate email and send to the required recipient.		A database job will run on C-TMS looking for NEW queued received and confirmed emails to send. As these are recognised, the existing process will identify queued records, generate the report output, attach to an appropriate email and send to the required recipient.
Line 60:		Line 50:

	'''Carrier Brief:'''		'''Carrier Brief:'''


	Once an order has been planned and a carrier assigned to the trip and the trip status promoted to ACCEPTED, a carrier confirmation email will be sent to confirm this information. This action will only be performed for the order(s) on the trip that contain a requester email address in additional references.		Once an order has been planned and a carrier assigned to the trip and the trip status promoted to ACCEPTED, a carrier confirmation email will be sent to confirm this information. This action will only be performed for the order(s) on the trip that contain a requester email address in additional references.
Line 66:		Line 55:

	'''Other considerations:'''		'''Other considerations:'''


	It is assumed that if the carrier is changed and re-briefed, this will generate another carrier confirmation email to the requestor with the revised carrier information.		It is assumed that if the carrier is changed and re-briefed, this will generate another carrier confirmation email to the requestor with the revised carrier information.
Line 72:		Line 60:

	'''''Technical Notes:'''''		'''''Technical Notes:'''''


	(''A new message type of ‘ORD_CONF’ will be created to indentify orders which require requestor emails'').		(''A new message type of ‘ORD_CONF’ will be created to indentify orders which require requestor emails'').


	''(Insert into the MSG_EVENT table for the record with the new ORD_CONF type containing the OMS ref of the order. This information will then be processed by a database job which will complete the sending of the email'').		''(Insert into the MSG_EVENT table for the record with the new ORD_CONF type containing the OMS ref of the order. This information will then be processed by a database job which will complete the sending of the email'').


	''(A change will be required in the MSG_PROCESSING package to process the new ORD_CONF type message and run the Oracle report described. A change will then be required in the MSG_CONSTUCTOR package to obtain the email addresses and requestor names which have been captured as additional references against this order).''		''(A change will be required in the MSG_PROCESSING package to process the new ORD_CONF type message and run the Oracle report described. A change will then be required in the MSG_CONSTUCTOR package to obtain the email addresses and requestor names which have been captured as additional references against this order).''


	== Scope ==		== Scope ==

Admin: /* Client Requirement */

2012-05-10T15:41:35Z

Client Requirement

← Older revision		Revision as of 17:41, 10 May 2012
Line 3:		Line 3:
	== Client Requirement ==		== Client Requirement ==
	'''Change Request Summary:'''		'''Change Request Summary:'''


	Requestor Emails		Requestor Emails
Line 9:		Line 8:

	'''Change Request Details:'''		'''Change Request Details:'''


	Order requestor is automatically sent an email to confirm details of bookings as order is received into C-TMS. Once briefed, a follow-up email confirms the carrier appointed.		Order requestor is automatically sent an email to confirm details of bookings as order is received into C-TMS. Once briefed, a follow-up email confirms the carrier appointed.
Line 15:		Line 13:

	'''Benefits identified as a result of the change:'''		'''Benefits identified as a result of the change:'''


	Confirmation received by the requestor for any orders placed and then briefed to carrier.		Confirmation received by the requestor for any orders placed and then briefed to carrier.


	== Solution ==		== Solution ==

Admin: /* Order Confirmation Report */

2012-05-10T15:39:52Z

Order Confirmation Report

← Older revision		Revision as of 17:39, 10 May 2012
Line 448:		Line 448:
	The report will be automatically generated based on order events and will also be available to run from the reports screen. The user will be required to provide an OMS_REF. A new record will be added in the REP_REPORT and REP_REPORT_PARAMS tables to facilitate this.		The report will be automatically generated based on order events and will also be available to run from the reports screen. The user will be required to provide an OMS_REF. A new record will be added in the REP_REPORT and REP_REPORT_PARAMS tables to facilitate this.

			[[Image:291361_4.png]]
	~~<center>~~[[Image:]]~~</center>~~


	== Creating the Email ==		== Creating the Email ==

Admin: /* Requestor Details */

2012-05-10T15:37:34Z

Requestor Details

← Older revision		Revision as of 17:37, 10 May 2012
Line 157:		Line 157:


	[[Image:]]		[[Image:291361_2.png]]


Line 163:		Line 163:


	[[Image:]]		[[Image:291361_3.png]]


	== Order Events ==		== Order Events ==

Admin: /* Implementation Advice */

2012-05-10T13:47:21Z

Implementation Advice

← Older revision		Revision as of 15:47, 10 May 2012
Line 122:		Line 122:


	[[Image:]]		[[Image:291361_1.png]]


Line 151:		Line 151:

	\|}		\|}

	= Functional Description =		= Functional Description =
	== Requestor Details ==		== Requestor Details ==

← Older revision		Revision as of 17:46, 10 May 2012
Line 248:		Line 248:
	\|-		\|-
	\| style="border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| COLLECTION_DATE_TIME		\| style="border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| COLLECTION_DATE_TIME
	\| style="border:0.018cm solid #000000;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| SCH_ORD.EARLY_COLL\|\|SCH_ORD.LATE_COLL		\| style="border:0.018cm solid #000000;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| SCH_ORD.EARLY_COLL SCH_ORD.LATE_COLL

	\|-		\|-
Line 264:		Line 264:
	\|-		\|-
	\| style="border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| DELIVERY_CONTACT		\| style="border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| DELIVERY_CONTACT
	\| style="border:0.018cm solid #000000;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| GEO_CONTACT.FORENAME\|\| GEO_CONTACT.SURNAME		\| style="border:0.018cm solid #000000;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| GEO_CONTACT.FORENAME GEO_CONTACT.SURNAME

	\|-		\|-
Line 330:		Line 330:
	\|-		\|-
	\| style="border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| COLLECTION_CONTACT		\| style="border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| COLLECTION_CONTACT
	\| style="border:0.018cm solid #000000;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| GEO_CONTACT.FORENAME\|\| GEO_CONTACT.SURNAME		\| style="border:0.018cm solid #000000;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| GEO_CONTACT.FORENAME GEO_CONTACT.SURNAME

	\|-		\|-
Line 358:		Line 358:
	\|-		\|-
	\| style="border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| COLLECTION_DATE_TIME		\| style="border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| COLLECTION_DATE_TIME
	\| style="border:0.018cm solid #000000;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| SCH_ORD.EARLY_COLL\|\|SCH_ORD.LATE_COLL		\| style="border:0.018cm solid #000000;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| SCH_ORD.EARLY_COLL SCH_ORD.LATE_COLL

	\|-		\|-
Line 374:		Line 374:
	\|-		\|-
	\| style="border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| DELIVERY_CONTACT		\| style="border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| DELIVERY_CONTACT
	\| style="border:0.018cm solid #000000;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| GEO_CONTACT.FORENAME\|\| GEO_CONTACT.SURNAME		\| style="border:0.018cm solid #000000;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| GEO_CONTACT.FORENAME GEO_CONTACT.SURNAME

	\|-		\|-
Line 402:		Line 402:
	\|-		\|-
	\| style="border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| DELIVERY_DATE_TIME		\| style="border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| DELIVERY_DATE_TIME
	\| style="border:0.018cm solid #000000;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| SCH_ORD.EARLY_DEL\|\|SCH_ORD.LATE_DEL		\| style="border:0.018cm solid #000000;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| SCH_ORD.EARLY_DEL SCH_ORD.LATE_DEL

	\|-		\|-