287345
DHL C-TMS
Additional Trigger of TRP Message
FUNCTIONAL SPECIFICATION - 10.6
18/05/2011 - 1.0
Reference: FS 287345 NA-8F5HZ6
Functional Overview
Client Requirement
Currently a TRP message is only triggered when a Trip is moved from Planned to Accepted.
After this point, if planners make amendments to the order delivery date/time window but not move the trip between planned/accepted then the time Unilever are measuring us against does not match the actual time in C-TMS.
Can we add another trigger of the TRP message to trigger when the Trip is in an Accepted state and the order delivery date/time window is changed.
Solution
Once an order is scheduled on a trip, changes to that order do not trigger a ‘TRP’ message. The ‘TRP’ message will only be triggered by changes to the trip.
A new trigger will be added to the ‘SCH_ORD’ table that will fire when the order windows are changed, and the order is at a status of ‘SCHED_COLL’ or ‘SCHEDULED’ (i.e. scheduled on a trip).
The trigger will only fire for orders that have a customer and from location set up to produce EDI messages. The order’s customer and from location will be compared to records on table ‘EDI_PROCESS_HEADER’.
If a record is found then the trigger will write a record to the table ‘INT_XML_CONTROL’ containing the following information:
- External System– ‘EDI_PROCESS_HEADER.PROCESS_NAME’ where the customer and location match the order.
- Event Type– ‘TRP’ to indicate the type of message being sent.
- Trip Schedule– ‘SCH_TRIP.SCHED_NAME’ for the trip which the order is on.
- Trip ID– ‘SCH_TRIP.TRIP_ID’ for the trip which the order is on
- Trip Status– ‘SCH_TRIP.TRIP_STATUS’ for the trip which the order is on.
- Processed– ‘N’
The Trip for the Order will be a trip that visits the location ID for the EDI process and on which the Order is being loaded.
The record in ‘INT_XML_CONTROL’ will be processed by the existing job for the EDI flow.
N.B. the current ‘UNILEVER’ and ‘UNIICE’ outbound flows, along with the new Unilever Ireland flow are being moved to the generic outbound flow as part of RIO NA-8F5HA6. This estimate is based on the changes for RIO NA-8F5HA6 being applied and the flows using ‘EDI_PROCESS_HEADER’.
Scope
This change will be applied to system version 10.6.
Set-up
Pre-requisites
None
Menu Structure
‘Unchanged’
Data
‘Unchanged’
Functional Description
Current functionality is as follows:
Once an order is scheduled on a trip, changes to that order do not trigger a ‘TRP’ message. The ‘TRP’ message is triggered by changes (add/remove orders, changes to stop times) to the trip when the trips status is at a status specified in the trigger value set up in the EDI maintenance form.
Proposed new functionality:
A new trigger will be added to the ‘SCH_ORD’ table that will fire when the order delivery date and time windows are changed, and the order is at a status of ‘SCHED_COLL’ or ‘SCHEDULED’ (i.e. scheduled on a trip).
The columns on the ‘SCH_ORD’ table to check when updating will be ‘EARLY_DEL’ and ‘LATE_DEL’.
The trigger will be called ‘TRG_SCH_ORD_DEL_TRP’ and will only fire for orders that have a customer and ‘from’ location set up to produce EDI messages (i.e. records that exist on table ‘EDI_PROCESS_HEADER’) an additional check will be made on the EDI_TRIGGERS table to ensure that the new SO_DEL_DATE_CHANGE value is set to ‘Y’
If a record is found then the trigger will write a record to the table ‘INT_XML_CONTROL’ containing the following information:
| Column | Value |
| EXTERNAL_SYSTEM | Data from ‘EDI_PROCESS_HEADER.PROCESS_NAME’ where the customer and location match those of the order |
| EVENT_TYPE | ‘TRP’ |
| TRIP_SCHED | Data from ‘SCH_TRIP.SCHED_NAME’ for the trip on which the order is assigned |
| TRIP_ID | Data from ‘SCH_TRIP.TRIP_ID’ for the trip on which the order is assigned |
| TRIP_STATUS | Data from ‘SCH_TRIP.TRIP_STATUS’ for the trip on which the order is assigned |
| PROCESSED | ‘N’ |
The data will be stored in the ‘Edi’ tab page of the ‘Import’ screen and used to select the following data:
| Field | Column |
| Process Name | INT_XML_CONTROL.EXTERNAL_SYSTEM |
| Customer | SCH_ORD.CUSTOMER |
| Location | SCH_ORD.FROM_LOC |
The trip for the order will be a trip on which the order is being loaded at a specific location (i.e. has a haulage activity of ‘Load’ at a trip stop).
For example, the customer may be ‘UNIICE’ and the location may be ‘DHLUNGLO’, or the customer may be ‘UNILEVER’ and the location may be ‘DHLUNWTK’.
The record in ‘INT_XML_CONTROL’ will be processed by the existing database job generated when the EDI flow is started.
N.B. The current ‘UNILEVER’ and ‘UNIICE’ outbound flows, along with the new ‘Unilever Ireland’, flow should exist in the generic outbound flow as developed for RIO ‘NA-8F5HA6’ and this development must be installed first.
References
| EST-287345 NA-8F5HZ6 Additional Trigger of TRP Message v1.0.doc | |||
Glossary
| C-TMS | Calidus TMS |
Document History
| Initial version | ||||
| Reviewed and Issue | ||||
AUTHORISED BY
| Matt Crisford | Development Manager | |
| Peter Greer | TMSCC MTS Product Manager |
