ER CTMS 047-105: Difference between revisions
(Created page with "<!-- MEDIA LANDSCAPE YES --> {{#vardefine:System|CTMS}} {{#vardefine:SystemVers|12.0}} {{#vardefine:ERPatch|047}} {{#vardefine:ERNumber|105}} {{ERHeader |SystemVersion={{#var:System}} {{#var:SystemVers}} |ERNumber=ER {{#var:System}} {{#var:ERPatch}}-{{#var:ERNumber}} }} {| class="wikitable" border="1" width="100%" |- bgcolor="silver" !Module !! Program Name !! Ver !! Call/Iss !! Client Ref !! Pr'ty !! Remarks |- |AT_SCH_ORD_REFERENCE_620885.sql |Database Script |1.1 |...") |
(No difference)
|
Revision as of 12:23, 18 June 2025
EMERGENCY RELEASE - CTMS 12.0
RELNOTE ER CTMS 047-105
| Module | Program Name | Ver | Call/Iss | Client Ref | Pr'ty | Remarks |
|---|---|---|---|---|---|---|
| AT_SCH_ORD_REFERENCE_620885.sql | Database Script | 1.1 | 620885 | 669852-55 | 1 | The new system parameter that is called 'TIMI_EXTRACT' can be set to 'Y' so that data will be extracted for a file to send to the TIMI system.
New import decodes will need to be created for 'TIMI_TRACKING_REASON' which will be used to map the reason codes that are used for the items for the events in Calidus to the tracking codes that are used in TIMI. For example, reason code 'SC' will indicate that an item has been collected, and reason code 'SU' will indicate that an item has been unloaded. These reason codes will be decoded with a tracking reason of 'LOAD' and 'UNLOAD' respectively and the location of the scan will then be used to derive the tracking code for TIMI. For example, reason code 'SC' will be converted to tracking code '2100' if the item is not scanned at a depot, and reason code 'SU' will be converted to tracking code '2210' if the item is scanned at a depot. EDI parameters can be set for the EDI process which may exist for a customer and/or a cost centre, or neither a customer nor a cost centre: FTP_PROTOCOL = SFTP (to use a secure connection to transfer the files to TIMI) TIMI_EXTRACT = Y (to identify that the TIMI process exists) INCLUDE_2100 = Y (to include the 2100 tracking events if they are appropriate) INCLUDE_4100 = Y (to include the 4100 tracking events if they are appropriate) A branched version 1.11.1.1 of DP_FLEXIPOD will be released to the 19c databases which will use APOD. |
| DATA_ADM_SYSTEM_PARAM_620885.sql | Database Script | 1.1 | " | " | " | " |
| DATA_IMP_DECODE_620885.sql | Database Script | 1.1 | " | " | " | " |
| TI_SCH_ORD_STATUS.sql | Database Trigger | 1.33 | " | " | " | " |
| TRG_SCH_HAULAGE_FLX.sql | Database Trigger | 1.6 | " | " | " | " |
| TRG_SCH_ORD_ITEMS_REASONS_SCAN.sql | Database Trigger | 5.9 | " | " | " | " |
| TRG_SCH_ORD_REFERNCE_AI.sql | Database Trigger | 1.10 | " | " | " | " |
| TRG_SOI_XML.sql | Database Trigger | 5.28 | " | " | " | " |
| DP_CSV6.sql | Exports Package | 1.47 | " | " | " | " |
| DP_FLEXIPOD.sql | Flexipod Package | 1.11 | " | " | " | " |
| New Parameters | |||
|---|---|---|---|
| Parameter Name | Config Level | Setting Value | Result |
| TIMI_EXTRACT | SYSTEM | N | Data will not be extracted for a file to send to the TIMI system. |
| TIMI_EXTRACT | SYSTEM | Y | Data will be extracted for a file to send to the TIMI system. |
