EST 05697238 LFS UPS API Changes

From Calidus HUB
Revision as of 16:23, 17 September 2025 by Anw (talk | contribs) (Minor correction)
Aptean Logo.png
STATEMENT OF WORK
CHANGE REQUEST ESTIMATE
ClientLFSProjectAUSite.
Client Reference.Aptean Reference05697238Estimate Version0.01
Prepared ByA N WalkerEstimate Date17/09/2025
Invoice Reference-Priority-
Customer.System Version12.48


Client Request
Option 1
  • UPS GSA application maintains a set of shipment number ranges (i.e. Con Note Numbers) that are assigned by our carrier
  • GSA assigns shipment numbers as each WMS order is processed
  • GSA then generates a carrier compliant label that includes this Shipment number
  • GSA interfaces the shipment data including the Shipment Number to the carrier
  • Goods are handed over when truck picks up and can be tracked based on this shipment number
  • Milestones are returned with the shipment number being the primary key

Option 2

  • GSA processes a WMS order
  • GSA then calls an API with the carrier and passes through the shipment details
  • The response to the API call passes back critical information from the carrier which includes the shipment number along with any routing data that will be critical for the label generation
  • GSA then generates a carrier compliant label that includes this Shipment number that was returned in the API response
  • Goods are handed over when truck picks up and can be tracked based on this shipment number
  • Milestones are returned with the shipment number being the primary key


Aptean Solution
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 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 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.
  • Item Labels
    • Add carrier reference to item label


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 or reports or exports other than those listed.


Cost Details
Activity Hours Rate per hour ($) Cost ($ Exc. GST)
Requirements 15.00 220.00 $3,300.00
Change Request Evaluation 7.50 220.00 $1,650.00
Functional Specification 23.50 220.00 $5,170.00
Technical Specification 0.00 220.00 $0.00
Development 58.50 220.00 $12,870.00
Testing and Release 22.25 220.00 $4,895.00
Implementation 3.75 220.00 $825.00
Project Management 26.00 220.00 $5,720.00
 
TOTAL 156.50   $34,430.00


Copyright © Aptean 2025.
This estimate has an expiry date of 30 days from the specified Estimate Date.
The information contained herein is supplied without liability for errors or omissions.