ER CTMS 041-059: Difference between revisions
From Calidus HUB
No edit summary |
No edit summary |
||
| Line 21: | Line 21: | ||
The 'CARRIER_POD' type of import will include new columns of data to extract from the file for the format that is being used: | The 'CARRIER_POD' type of import will include new columns of data to extract from the file for the format that is being used: | ||
POD_NAME | |||
TRIP_ID | |||
REASON_TEXT | |||
The 'DELIVERED' field should be 'FIXED' to 'Y' to enable only the 'Delivered' events to be processed in the message. | The 'DELIVERED' field should be 'FIXED' to 'Y' to enable only the 'Delivered' events to be processed in the message. | ||
Revision as of 16:14, 31 May 2022
EMERGENCY RELEASE - CTMS 11.0
RELNOTE ER041-059
| Module | Program Name | Ver | Call/Iss | Client Ref | Pr'ty | Remarks |
|---|---|---|---|---|---|---|
| DATA_IMP_FIELD_02023242.sql | Database Script | 1.1 | 02023242 | - | 3 | The creation of a tracking reference is audited when a label is printed for the order, and the deletion of a tracking reference is audited for the order.
The 'CARRIER_POD' type of import will include new columns of data to extract from the file for the format that is being used: POD_NAME TRIP_ID REASON_TEXT The 'DELIVERED' field should be 'FIXED' to 'Y' to enable only the 'Delivered' events to be processed in the message. The 'LFE POD' message contains validation of the size and type of the data. The delivered tracking reference must exist for the advised order reference. The order lines will be updated as delivered as they have been packed and despatched. The orders will be updated with information about the signatory and the reason code for the delivery. |
| TRG_SCH_ORD_TRACKING.sql | Database Trigger | 1.2 | " | " | " | " |
| DP_LFE_POD.sql | LFE POD Database Package | 5.5 | " | " | " | " |
