Support - Tesla EDI Inbound Guide
Order Template
For each dealership an order will be created each day, this is a placeholder which will be added to by the import process. This is existing fixed schedules functionality which has not been modified for Tesla.
System parameters
ALLOW_MULTIPLE_ADD_REFS should be set to Y for the appropriate cost centre.
Dealership Decodes
The delivery locations in the inbound files are the Tesla dealership locations not CTMS locations and as such must be decoded, scripts have been created and released during the normal release process to create these decodes
Du Type Decodes
The du types in the inbound files are the Tesla du types not du types and as such must be decoded, scripts have been created and released during the normal release process to create these decodes
Inbound Files
An example inbound file is included below
EDI Tables
Two new tables have been created to hold the details of the Inbound files
- TESLA_EDI_ORDER_HEADER
- TESLA_EDI_ORDER_DETAILS
Each table has an associated sequence, and the detail is linked to the header by the header ID.
Inbound EDI
A new EDI flow will be present for the DHLAA cost centre and the Tesla customer. The import processes will be completed within the DP_TESLA_EDI package using the IMPORT_ORDERS procedure.
File Format
The test files provide simply have numeric a file name, so the file pattern is not specified on the EDI flow. An example file is included above.
EDI Parameters
The following Parameters are required
EDI Report Values
The following Report values are required
Order Processing
An order will exist on the correct schedule for each dealership in the inbound file the delivery date can be found in the “deliveryStartDateTime” tag and the dealership in the “referenceField7” tag
The correct CTMS dealership location will then be found using the decode
A skeleton order will exist in CTMS which will have been created by an existing process note the schedule and delivery location agree with your inbound file, if no order is found on the schedule for the dealership an error will be raised and the order will not be processed.
The product type is not contained in the inbound file so therefore must exist as a default parameter on the EDI flow. If no default is present an error will be raised and the order will not process.
The Du type must also exist as an EDI parameter on the flow. An attempt will be made to decode the passed in palletSize value which contains a du type which has been mapped so in this example
Maps to
If no mapping is found the EDI default will be used. If no default is present an error will be raised and the order will not process.
Once the correct order has been located and the product and DU type validated. The order will be updated with the details in the inbound file.
If the DU type doesn’t exist on the current order a new line will be created for that DU type, the placeholder line will be removed at this point if no items exist with the same du type.
Note the weight and volume on the line these are taken directly from the inbound pallet section and should not be manipulated.
Order items will have been created
Item contents will have been created
Additional References will have been created to indicate the Consolidated order reference, MH Order references(s) and Tesla references(s)
Each reference should only be stored once and the values are found as follows
Consolidated Order – “aggregatedOrderNumber” tag, only 1 per order will be stored
MH(Manhattan) Order ref – “OrderNumber” tag
Tesla Reference – “referenceField4” of the line section
Interface Errors
A new Tesla Orders tab page has been added to the interface errors screen which will contain the success/failure stats of each or the file imports and allow the user to reprocess any failed records after the issue has been corrected. This process will use the same package functionality as the inbound orders.
Specifications
P:\Development\CTMS\DHL\543347 SCR - Tesla Order Interface
P:\Development\CTMS\DHL\613005 SCR - Changes to the Tesla Order Interface
P:\Development\CTMS\DHL\632041 - Changes to Tesla order interface for Aggregated order number
