The overall solution will be as follows:
- UPS send in an additional sub-reference on the order using the standard CTMS Interface format provided - proposed as CARRIER_REFERENCE.
 Note: This is not validated unique, but as this is generated by UPS and sent to us electronically, this will be acceptable.
- CTMS stores that as an additional order reference, visible in and searchable in the CTMS orders screens.
- CTMS passes that to Portal TTM as Order Reference 1 (additional order reference).
- The Portal TTM Trip/Order Enquiry screen is configured to search by Order Reference 1 (named appropriately such as "Carrier Reference" in the system).
- Portal TTM is configured to display that on the results table shown from a query.
- This will be displayed after the existing PO Reference.
- Portal TTM is configured to display that on the details of the order when you drill down into it.
- Note: This is just for the Trip/Order Enquiry screen - the following screens do not use the new reference: Order Visibility, Airport, Arrivals.
- Portal Gateway - the carrier reference will be sent to the end customer for tracking purposes, and they will be able to view the details of the order through this link.
- Portal Gateway - the parameter entry page will allow the user to select by which reference they want to find the consignment, from a drop-down list of available references
- B – Booking Ref.
- S – External Ref.
- T – OMS Ref.
- P – PO Ref.
- 1/2/3/4/5 – Order Ref 1/2/3/4/5.
- The new additional reference will be passed out on the existing ORD_XML messages.
Development Required:
- UPS – pass in CARRIER_REFERENCE sub-reference
- No CTMS dev expected on this, but this must be considered a requirement of the final deliverable.
- CTMS
- Pass defined (parameterized) CARRIER_REFERENCE to TTM in Reference1.
- Portal
- Enquiry results: Add Order Reference 1 to configurable items to display.
- Gateway
- Add drop-down list of selectable reference to use to find the order.
- ORS Reports
- Add Carrier Reference to selectable/reportable criteria. List below
- EX_ORDHEAD
- EX_ORDITM
- EX_ORDLINE
- UNSCHED
- SCHED_ORD2
- SCHED_ORDS
- Update existing user ORS reports that are based off these ORS types.
Scope:
- Only the interfaces, screens and fields specified will be changed - any other screens, interfaces and fields remain unaffected, specifically but not limited to:
- Other Portal TTM enquiry screens.
- Portal TMS screens.
- Any ORS reports other than those listed.
- Any imports other than those listed.
- Any labels, reports or exports other than those listed.
|
