View source for EST 05695722 WREQ0130528 Ford Inbound Interface Changes

{{Template:EstimateNew
|Supimix_Client_Code=DHLT
|Supimix_Project_Code=AA
|Supimix_Site_Code=-
|Supimix_Client_Reference=WREQ0130528 
|Supimix_Number=05695722 
|The_version_of_the_document=0.01
|Your_Name=A N Walker
|Supimix_PO_Reference=-
|Supimix_Priority=-
|Date_(DD/MM/YY)=15/08/2025
|Clients_Customer=Ford
|System_Version_being_changed=12.48
|Client_Request=Ford are introducing a new SAP system and a new inbound interface format.

Copy of the Ford specification attached.

We will use DHL Link to translate the message to a more standard inbound format or use a one to one interface. The plan is to capture the same data as current

Please note that this request is linked to the outbound tracking request on WREQ0127859. We need to ensure we have all the information that we need for the tracking.

|OBS_Solution=The Ford Inbound Orders EDI process currently:
* Finds the order
* Stores the items and contents onto standard EDI tables
* Then processes them to update the order
**  Adds Items
**  Adds contents
**  Generates lines

The process does not currently update or store the individual shipment IDs for each order on each item.

The process will be modified to:
* Change the mapping of the header elements
* Store the order references as new order reference FORD_SHIPMENT_ID.
* Use an optional EDI parameter VERSION, to control whether this is using the old or new versions of the import file. 
An implementation script will be created to create the new parameters and references.

{{Note}} This process will support both versions of the EDI formats provided, but '''not''' at the same time, so the implementation must be a controlled swap-over.


The process will be modified to add a VERSION parameter. If this is explicitly set to "1", then the process will run the old import. Otherwise, this will run the new import specified here.

The fields used for the header information will be modified as follows:

* Old Format (v1)                     - New Format (v2)             
* Shipment (shipment_id attribute) - FreightOrderId          
* shipping_location             - InitialSourceLocation    
* carrier                      - CarrierID                
* truck_license_plate          - TruckLicensePlateID      
* seal_number                  - N/A                         
* shipping_date                - DateAndTime              
* shipto_location              - ArrivalLocation          
* N/A                          - LogisticalExecutionStatus

{{Note}} It is assumed that the data content is not changing, just the labels. If this is not the case, the estimate must be revisited.

{{Note}} It is assumed that the structure of the pallets information is not changing (as no format has been provided). If this is not the case, the estimate must be revisited.

The system must be configured to allow multiple order references.

The system parameter "ALLOW_MULTIPLE_ADD_REFS" should be set to "Y" for the appropriate cost centre.

Note that the DHL AA system is already configured for this, but should be checked for the cost centre (implementation task).

The process will be modified to store the order references from FreightOrderId as order references against the template order - there could be many. 

|Requirements_Days=0
|Estimation_Days=6
|Functional_Specification_Days=7.5
|Technical_Specification_Days=0
|Development_Days=37.5
|Testing_and_Release_Days=7.5
|Implementation_Days=0
|Project_Management_Days=12
|Year=2025
|Free_Of_Charge=N
|DiscountPerc=0
|DiscountText=
}}