https://calidusassist.adcservices.apteancloud.com/calidus-assist/MTS/index.php?action=history&feed=atom&title=276276
276276 - Revision history
2026-05-09T01:01:46Z
Revision history for this page on the wiki
MediaWiki 1.39.8
https://calidusassist.adcservices.apteancloud.com/calidus-assist/MTS/index.php?title=276276&diff=2708&oldid=prev
Middletong: New page: =276276 - AS-84PBMN/ Dunelm SAP Order EDI Flow= Copyright OBS Logistics © 2011 The information contained herein is the property of OBS Logistics and is supplied without liability for er...
2011-02-11T12:16:58Z
<p>New page: =276276 - AS-84PBMN/ Dunelm SAP Order EDI Flow= Copyright OBS Logistics © 2011 The information contained herein is the property of OBS Logistics and is supplied without liability for er...</p>
<p><b>New page</b></p><div>=276276 - AS-84PBMN/ Dunelm SAP Order EDI Flow=<br />
<br />
Copyright OBS Logistics © 2011<br />
<br />
The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied<br />
<br />
<br />
=FUNCTIONAL OVERVIEW=<br />
<br />
==Client Requirement==<br />
Create a new integration flow to allow order header information from SAP R3 to be uploaded into Calidus TMS.<br />
<br />
Upload orders from SAP, validate versus static data and for mandatory fields, hold any errors in interface errors for review and resolution.<br />
<br />
<br />
==Solution==<br />
Dunelm will provide order files in XML format. These files will be transmitted or uploaded to ESI probably by ftp but the method and communication transport to be agreed. ESI will validate and transform the SAP XML message into the OBS XML Trip Order Schema. The ESI output files will be pushed via ftp to the C-TMS platform at OBS data centre in Runcorn.<br />
<br />
C-TMS will recognise new files as they are created in the designated /in folder. The files will be validated, any errors saved and reported in the C-TMS interface errors form, and where clean, loaded as order headers with C-TMS.<br />
<br />
==Scope==<br />
This change will be applied to C-TMS system version 10.6. <br />
<br />
<br />
=FUNCTIONAL DESCRIPTION=<br />
<br />
==Pre-requisites==<br />
Message flow<br />
<br />
[[Image:276276_1.png]]<br />
<br />
[[Image:276276_2.png]]<br />
<br />
[[Image:276276_3.png]]<br />
<br />
Note the output files are made unique using date time and a generated 3 digit sequence number. <br />
<br />
==Data & Mapping==<br />
Note that the input status is per order while the output status is per file. ESI will need to create an output file for each group of <status> in the input file. Alternatively, can SAP send separate files of N (new), A (amend) and C (cancel)?<br />
<br />
[[Image:276276_4.png]]<br />
<br />
*note that the default collection and delivery window dates/times need to be confirmed by the business.<br />
<br />
<br />
<br />
<br />
=REFERENCES=<br />
<br />
Not Available<br />
<br />
=DOCUMENT HISTORY=<br />
<br />
{| Border="1" <br />
| <center>'''Version'''</center><br />
| <center>'''Date'''</center><br />
| <center>'''Status'''</center><br />
| <center>'''Reason'''</center><br />
| <center>'''Initials'''</center><br />
<br />
|-<br />
| <center>0.1</center><br />
| <center>03/05/10</center><br />
| <center>Draft</center><br />
| Initial version<br />
| <center>DJM</center><br />
<br />
|-<br />
| <center>0.2</center><br />
| <center>06/05/10</center><br />
| <center>Draft</center><br />
| Correct filenaming and include updated XSD<br />
| <center>DJM</center><br />
|}<br />
<br />
<br />
=AUTHORISED BY=<br />
<br />
<br />
<br />
{| Border="1" <br />
| '''''Matt Crisford'''''<br />
| C-TMS Development Manager<br />
| <br />
<br />
|-<br />
| '''''Dave Meir'''''<br />
| C-TMS Product Manager<br />
| <br />
<br />
|}</div>
Middletong