CTMS 11.0 ER024-029: Difference between revisions
(Created page with "<!-- MEDIA LANDSCAPE YES --> {{#vardefine:System|CTMS}} {{ERHeader |SystemVersion=CTMS 11.0 |ERNumber=ER024-029 }} {{ERTableHeader}} {{ERTableRow |DATA_ADM_SYSTEM_PARAM_342923....") |
No edit summary |
||
Line 11: | Line 11: | ||
|Data Script | |Data Script | ||
|1.1 | |1.1 | ||
| | |342923 | ||
| | |HP-AM7K8G | ||
| | |2 | ||
| | |A new EDI process will need to be setup to process the POD_INFO files to be transferred to DHL Link. | ||
| | |||
The FTP Server will need to be setup unless the existing flow for TRIPXML files can be used: this directory structure is used for LOAD, CITD and Electronic Manifest files. | |||
A new system parameter OMS_CREATE_POD will need to be configured for the appropriate customers of the orders to generate the POD_INFO files. | |||
The POD_INFO files will be triggered when the delivered quantity of an order line is changed and the order line has not been zero packed. | |||
The delivered quantity will be compared to the despatched, packed or ordered quantity of the order line to assess the status of the order as SUCCESS, FAILED, PART DELIVERED or PART UNDELIVERED. Note that a status of PRE DELIVERY will be used should a control record be generated and then the delivered quantity be removed. | |||
A POD_INFO file will be generated for each order and it will contain its current trip and debrief information with a vertical bar as a fixed delimiter. | |||
Note that if multiple signatories have been recorded, e.g. the order has been delivered at different times, these signatories will be listed together. | |||
The EDI process will use the following report values: | |||
1. | |||
Title: Process Name | |||
Name: P_PROCESS_NAME | |||
Value: POD_INFO | |||
2. | |||
Title: Package Name | |||
Name: PROCESS | |||
Value: DP_CSV_POD.P_PROCESS_CSV_POD | |||
See FS-342923 for further information. | |||
|Hiren Patel | |||
}} | }} | ||
{{ERTableRow | {{ERTableRow |
Revision as of 13:17, 15 June 2017
EMERGENCY RELEASE - CTMS 11.0
RELNOTE ER024-029
Module | Program Name | Ver | Call/Iss | Client Ref | Pr'ty | Remarks | Reporter |
DATA_ADM_SYSTEM_PARAM_342923.sql | Data Script | 1.1 | 342923 | HP-AM7K8G | 2 | A new EDI process will need to be setup to process the POD_INFO files to be transferred to DHL Link.
The FTP Server will need to be setup unless the existing flow for TRIPXML files can be used: this directory structure is used for LOAD, CITD and Electronic Manifest files. A new system parameter OMS_CREATE_POD will need to be configured for the appropriate customers of the orders to generate the POD_INFO files. The POD_INFO files will be triggered when the delivered quantity of an order line is changed and the order line has not been zero packed. The delivered quantity will be compared to the despatched, packed or ordered quantity of the order line to assess the status of the order as SUCCESS, FAILED, PART DELIVERED or PART UNDELIVERED. Note that a status of PRE DELIVERY will be used should a control record be generated and then the delivered quantity be removed. A POD_INFO file will be generated for each order and it will contain its current trip and debrief information with a vertical bar as a fixed delimiter. Note that if multiple signatories have been recorded, e.g. the order has been delivered at different times, these signatories will be listed together. The EDI process will use the following report values: 1. Title: Process Name Name: P_PROCESS_NAME Value: POD_INFO 2. Title: Package Name Name: PROCESS Value: DP_CSV_POD.P_PROCESS_CSV_POD See FS-342923 for further information. |
Hiren Patel |
DATA_ADM_SYSTEM_PARAM_CONFIG_342923.sql | Data Script | 1.1 | " | " | " | " | " |
DATA_DP_CSV_POD_342923.sql | Data Script | 1.1 | " | " | " | " | " |
DP_CSV_POD.sql | Database Package | 1.2 | " | " | " | " | " |
TRG_SOL_XML.sql | Trigger | 5.42 | " | " | " | " | " |