ER CTMS 034-017: Difference between revisions
No edit summary |
m (Text replacement - "[[Category:{{#var:System}} ER]]↵</noinclude>" to "[[Category:{{#var:System}} ER]]Category:ER CTMS 034 </noinclude>") |
||
| Line 97: | Line 97: | ||
<noinclude> | <noinclude> | ||
[[Category:{{#var:System}} ER]] | [[Category:{{#var:System}} ER]][[Category:ER CTMS 034]] | ||
</noinclude> | </noinclude> | ||
Latest revision as of 14:47, 14 July 2025
EMERGENCY RELEASE - CTMS 11.0
RELNOTE ER034-017
| Module | Program Name | Ver | Call/Iss | Client Ref | Pr'ty | Remarks |
|---|---|---|---|---|---|---|
| TRG_SCH_ORD_XML_INT.sql | Trigger | 5.18 | 358670 | WREQ0031943 | 3 | New version 2.43 of TripOrder.xsd will need to be installed by for the EDI files for interfacing with ConnectedView.
The EDI processes for ConnectedView should exist with triggers, parameters and report processes without a location or a customer but for a cost centre. ORD: Flow Type: ORD_XML_OUT
Parameters: ALLOW_MULTI_CUSTOMER = Y INCLUDE_ORDER_STATUS = Y SEND_HEADER_UPDATES = Y SEND_LINE_ITEMS = Y The order message will be sent for the despatching source depot for the creation and amendment of the orders at the depot. PACK: Flow Type: ORD_XML_OUT Parameters: PACK_EVENT = Y SEND_LINE_ITEMS = Y The pack message will be sent for the despatching source depot for the packing of the orders at the depot. POCPOD: Flow Type: TRIP_XML Parameters: ALLOW_MULTI_CUSTOMER = Y INCLUDE_ITEM_DELIVER = Y INCLUDE_NONCON_CODES = Y INCLUDE_REASON_CODES = Y INCLUDE_REASON_TYPE = Y INCLUDE_SIGNATURE = Y PODS_POCS = Y SEND_LINE_ITEMS = Y The POC messages will be sent for the loading at the source location for the collection orders. The POD messages will be sent for the unloading at the delivery location for the delivery orders. This trip may be for a depot that may be an outbase for the van fleet. The EDI processes also should exist for the LOAD, CITD and electronic manifest messages. The load message will be sent for the despatching source depot. The CITD message will be sent for the despatching source depot. An electronic manifest message will be sent for the despatching delivery depot for the parcel carrier. This depot may be an outbase for the van fleet. These EDI parameters can be configured to match the mapping of the files by any external processing for transfer to the source systems for the orders and carriers. New version 2.43 of TripOrder.xsd will be required for the messages for ConnectedView to be mapped. This version contains the ORDER_STATUS element at the end of the ORDER_HEADER segment. |
| INT_XML_OUT2.sql | Outbound EDI Package | 5.295 | " | " | " | " |
 Warning: | An EDI change is required with this release. New version 2.43 of TripOrder.xsd will need to be installed for the EDI files for messages for the new ConnectedView interface |
