PATCH C-TMS P040
CTMS
Release Notes
CALIDUS TMS
7th Oct 2021 - 1.0
Reference: P040
Contents
- 1 SUMMARY INTRODUCTION
- 2 DEVELOPMENT
- 3 SUPPORT INCIDENTS
- 4 BUGS
- 4.1 Log Number: 01637325
- 4.2 Log Number: 01736613
- 4.3 Log Number: 01721147
- 4.4 Log Number: 00224027
- 4.5 Log Number: 00217837
- 4.6 Log Number: 00224886
- 4.7 Log Number: 01753120
- 4.8 Log Number: 01753917
- 4.9 Log Number: 01743791
- 4.10 Log Number: 01784859
- 4.11 Log Number: 01784924
- 4.12 Log Number: 00233712
- 4.13 Log Number: 01742219
- 4.14 Log Number: 01794295
- 4.15 Log Number: 01778011
- 4.16 Log Number: 01801142
- 4.17 Log Number: 01793592
- 4.18 Log Number: 01810707
- 5 MODULES DELIVERED
- 6 ADDITIONAL CHANGES
SUMMARY INTRODUCTION
INTRODUCTION
The main aim of this document is to provide CALIDUS TMS users with the level of detail required to accurately test all software included in the patch. The document also contains set-up and configuration details to enable the user to configure the system correctly for the new functionality to work.
GLOSSARY OF TERMS
Term | Meaning |
---|---|
C-TMS | Transport Management System |
C-WMS | Warehouse Management System |
CR | Change Request |
C-WCS | Warehouse Control System |
C-ePOD | Electronic Proof of Delivery |
C-MCS | Mobile Control System |
C-TTM | Track and Trace Management |
EDI | Electronic Data Interchange |
TID | Testing Issue Development, or Log |
TESTING PROCESS
TIDs AND RESOLUTION
If there are any areas of the functionality that are not acceptable or do not meet the requirement specified in the Change Request then these should be expressed by raising a TID.
FINAL 'END TO END' TESTING
Prior to release to a production database, a full 'End to End' test is required on the test system by all sites using the database. Once this is signed off, a release date can be arranged.
AUTHORISATION
Authorisation from nominated release personnel only will be required when requesting a release to a production environment
DEVELOPMENT
Log Number: 01746708
Summary of Call | Carrier Rules when manually adding a second order to a trip |
Detail of Fix | Carrier rules where not called by the function, amendment to include them. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 01738129
Summary of Call | Cut Offs Extract |
Detail of Fix | New extract to report on orders where the delivery date has been amended due to cut off times |
Set-up and Configuration | No set-up/configuration required |
Log Number: 01743547
Summary of Call | Portal Rebrand |
Detail of Fix | A new logo called MNX_LOGO_WIDE will be available to configure for the labels and reports for system parameters LABAL_LOGO_FILE and LOGO_FILE.
The Zebra printer labels will display the same MNX logo for the SCHEDULED and UNSCHEDULED formats for the orders. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 00226252
Summary of Call | Portal Rebrand |
Detail of Fix | The reports TRIP_SHEET_POD_POC and LFS_DESPATCH_NOTE will refer to the system parameters LOGO_PATH and LOGO_FILE to print the new MNX logos.
The footer logo has been removed from the Proof of Collection/Delivery pages in the TRIP_SHEET_POD_POC report. The text will be black in the Proof of Collection/Delivery pages in the TRIP_SHEET_POD_POC report. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 01748137
Summary of Call | Changes to the Polarspeed label |
Detail of Fix | Format changes configured by customer to display different information in external ref. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 01777963
Summary of Call | Decode Amendment |
Detail of Fix | Changes to control which orders are validated for master locations |
Set-up and Configuration | No set-up/configuration required |
Log Number: 01778186
Summary of Call | Microlise - Development |
Detail of Fix | The system parameters 'MIC_REDUCED_EVENTS' and 'MIC_3PL_TRIP_HOURS' will be used to reduce the number of messages that are sent to Microlise.
Trip status changed to 'ACCEPTED' An order is added or removed from a trip The delivery windows change on an order
The duration of the trip must then not exceed the specified number of hours to trigger the event. The number of hours for the trip will only apply to 'ACCEPTED' trip when reduced events are being assessed. |
Set-up and Configuration |
New Parameters | |||
---|---|---|---|
Parameter Name | Config Level | Setting Value | Result |
MIC_REDUCED_EVENTS | SYSTEM | N | Microlise will continue to receive all triggered events. |
MIC_REDUCED_EVENTS | SYSTEM | Y | Microlise will receive a reduced number of defined events. |
MIC_3PL_TRIP_HOURS | SYSTEM | NULL | Microlise will continue to receive all triggered events. |
MIC_3PL_TRIP_HOURS | SYSTEM | NUMBER | The number of elapsed hours that Microlise requires a trip not to exceed for the reduced number of events. |
Log Number: 01727371
Summary of Call | Pass Actual Distance Through |
Detail of Fix | The database scripts will be run during the release process.
The 'Paragon Trip Detail' import can be configured to include a new field called 'ACTUAL_DISTANCE' to store the actual total distance for a radial trip. The 'Planning' screen displays the 'Actual Total Dist' as well as the 'Total Dist'. The new system parameter called 'MIC_ACTUAL_DISTANCE' can be set to 'Y' for the actual total distance from Paragon, provided that it is greater than zero, to be sent to Microlise as the 'TRIP_DISTANCE' in preference to the calculated total distance. |
Set-up and Configuration |
New Parameters | |||
---|---|---|---|
Parameter Name | Config Level | Setting Value | Result |
MIC_ACTUAL_DISTANCE | SYSTEM | N | The calculated distance will continue to be sent to Microlise as the 'TRIP_DISTANCE'. |
MIC_ACTUAL_DISTANCE | SYSTEM | Y | The actual distance from Paragon, provided that it is greater than zero, in preference to the calculated distance will be sent to Microlise as the 'TRIP_DISTANCE'. |
Log Number: 01805293
Summary of Call | Case Addition of Country Code into Ouput xml from CTMS |
Detail of Fix | The EFX messages for the trips and their orders can include the country code for the load and delivery drop locations of the orders.
This change will apply to the EFX messages at the 'trip' and 'order' type levels of data but it will not apply to the 'cancel' and 'debrief' messages. The XML tag will be 'COUNTRYCODE' and it will be included after the 'NAME' and 'POSTCODE' tags in the 'LOCATION' sections. A new system parameter called 'EFX_XML_INC_COUNTRYCODE' can be set to 'Y' for the cost centre of the trip to include this new XML tag in the files for EFX. |
Set-up and Configuration |
New Parameters | |||
---|---|---|---|
Parameter Name | Config Level | Setting Value | Result |
EFX_XML_INC_COUNTRYCODE | COST_CENTRE (NRCC) | N | The outbound EFX message will not include a value for the 'COUNTRYCODE' for the load and drop locations. |
EFX_XML_INC_COUNTRYCODE | COST_CENTRE (NRCC) | Y | The outbound EFX message will include a value for the 'COUNTRYCODE' for the load and drop locations. |
SUPPORT INCIDENTS
Log Number: 00218431
Summary of Call | Include reason type and cost centre in MCS for LATE receipts |
Detail of Fix | The goods receipt process will assess the reason code provided for when it has an 'at fault' code of 'LATE' to update the received items as late items.
The reason codes will be assessed at the 'ITEM_NON_CON' level with the system parameter 'ORD_REASON_CODE_FILTER' to identify the 'at fault' code. This system parameter can have values of 'COST_CENTRE', 'CUST_GROUP' or 'BOTH' with 'BOTH' being the default value. For example, the cost centre of the trip in receipt can be assessed. A reason code for the cost centre or a generic reason code of '+' can apply when the system parameter is 'COST_CENTRE' or 'BOTH'. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 00226975
Summary of Call | Zebra label production is a problem for some printers |
Detail of Fix | The SCHEDULED and UNSCHEDULED Zebra label formats have been changed to include a different method to display the MNX logo. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 00230920
Summary of Call | C-TMS Orders Wide screen |
Detail of Fix | The checkboxes are aligned sequentially and the fast_order_entry layout is being retained. The Deliver_Until field is also set to proper alignment. So that, it shouldn't move to Order Type for fast order entry. Fixed some issues in the ORDERS_WIDE form to make sure that, it is Consistent all over. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 00236029
Summary of Call | Unable to upload POL_MONDAY_21 location zones |
Detail of Fix | The customer of a location zone is optional.
Validation will be performed only when a customer is provided for the location zone. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 00235961
Summary of Call | Inbound NIG orders being rejected |
Detail of Fix | The EDI parameters to validate and match master locations for the inbound orders will have a fixed default value of N.
This will ensure that the locations will not need to be decoded for any NIG orders. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 00235970
Summary of Call | Order delivery date recalculated |
Detail of Fix | The customer cut-off times will be assessed only for order creation events in the XML order files.
Order amendments, packing and despatching events will not recalculate the order time windows based on these cut-off times. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 01798886
Summary of Call | INC40466720 - Rebooking option is not working |
Detail of Fix | The unscheduling of an order from a trip stop has been changed to assess any trip items for the order on the stop when MCS is active and there are actual order items on a pallet rather than on shipping LPNs from an initial DSPD message.
An order can then be rebooked without having to be depalletised first. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 00237483
Summary of Call | UAT Separate configurable layouts for the main version of ORDERS_WIDE |
Detail of Fix | Separated Configurable layouts between ORDERS and ORDERS_WIDE forms to make them independent.
Enlarged Loaded and Unloaded fields in ORDERS form. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 00246043
Summary of Call | Manually order time window derivation |
Detail of Fix | The fast order time windows for the manually entered orders will use the same logic as the Portal and EDI orders when deriving the next depot in the assessment. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 01807529
Summary of Call | Collection details missing the Order Items activity descriptions |
Detail of Fix | The reason code will be stored for the item for orders that are collected or delivered.
Ad hoc collections will also create a reason code for the item. The assessment will be for the item, pallet or transport unit. A reason code of SL will be used for ad hoc collections. |
Set-up and Configuration | No set-up/configuration required |
BUGS
Log Number: 01637325
Summary of Call | Locations Database - removal of commas |
Detail of Fix | A new EDI parameter called 'DECODE_ADDRESS_CHARS' for XML orders can be created with a value 'Y' to replace values for the address information (name, lines 1-3, town and county) as specified in a new import decode called 'ADDRESS_CHARS'.
A new import decode called 'ADDRESS_CHARS' can be created to replace specific characters in the location addresses that are received in the XML order files. The target value will replace the source value if it occurs in the address, e.g. a space to replace a comma. The target value can contain text to indicate that a space or a null value will be used: 'SPACE' for a space or 'NULL' for a null value. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 01736613
Summary of Call | MCS, Scheduling Engine and Contacts |
Detail of Fix | Fixes following UAT |
Set-up and Configuration | No set-up/configuration required |
Log Number: 01721147
Summary of Call | Planned ETA incorrect |
Detail of Fix | The trip stops times will be set to the advised times for the route from Logix/PTV.
The times could become unfixed if the SU stop calculated its initial time window based on the order and that time window was after the advised time window for stop 2. The times for stop 1 are now set to the advised time windows earlier in the process to prevent this recalculation of the subsequent trip stop times. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 00224027
Summary of Call | Amendments to EDI1214 |
Detail of Fix | Amendments to the file format and the processing of files |
Set-up and Configuration | No set-up/configuration required |
Log Number: 00217837
Summary of Call | Microlise trigger for DELETED trips |
Detail of Fix | The Microlise trigger for DELETED trips is not required when the trip was previously only PLANNED. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 00224886
Summary of Call | Order error in ORDERS_WIDE with fast order entry function |
Detail of Fix | The ORDERS_WIDE screen will have the Delivery Type field disabled for the fast order entry functionality. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 01753120
Summary of Call | LOTS issues - CTMS & TTM |
Detail of Fix | 1. A new system parameter for cost centres exists called LOTS_DEL_CUST_SIGNATORY.
Description: 'Controls if DEL messages for LOTS require an actual signatory - Y to hold messages' Used in the ORDER_HEADER_CONFIRM section in the LOTS files. And to only send a DEL message when an actual signatory is obtained from EPOD (except when the file is triggered at COMPLETED status). The signed by from the trip stop will not be included when an actual signatory is not received. DEL messages will remain on hold until an actual signatory is received or the trip is completed. The DEL control records will be updated as processed with the text 'Missing signatory, no DEL file created' for the filename. 2. The VLI/VUI messages will remain on hold until a scan for the vehicle is received. If a DEL message is sent for the order these VLI/VUI will then not be sent and their control records will be updated as processed with the text 'Scan not received, DEL message created' for the filename. 3. The TRP messages will check that a control record has not been created or a trip that has subsequently been DELETED without first sending a TRP message. The TRP control records will be updated as processed with the text 'Deleted Control Record' for the filename. 4. The DRIVER_NAME section does not include a space if a driver is not assigned. 5. The STOP_CONTACT_NAME section does not include a space if a contact is not assigned. |
Set-up and Configuration |
New Parameters | |||
---|---|---|---|
Parameter Name | Config Level | Setting Value | Result |
LOTS_DEL_CUST_SIGNATORY | COST_CENTRE | Y | The DEL message will require an actual signatory for the delivery location of the order before it can be sent. |
LOTS_DEL_CUST_SIGNATORY | COST_CENTRE | N | The DEL message will not require an actual signatory for the delivery location of the order before it can be sent. |
LOTS_FTP_PUT_DIRECTORY | SYSTEM | POPULATED | The LOTS file will be placed temporarily in this directory with a suffix of 'TMP'. |
LOTS_FTP_PUT_DIRECTORY | SYSTEM | NULL | The LOTS file will not be placed temporarily in this directory. |
LOTS_FTP_DESTINATION_DIRECTORY | SYSTEM | POPULATED | The LOTS file will be placed in this directory with a suffix of 'XML'. |
LOTS_FTP_DESTINATION_DIRECTORY | SYSTEM | NULL | The LOTS file will be placed in this directory. |
Log Number: 01753917
Summary of Call | Locations > International Customer drop down |
Detail of Fix | Applied the user parameters to the International customer drop-down list. The list will refer to cust_group and customer user parameters. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 01743791
Summary of Call | XML Order Upload |
Detail of Fix | The EDI parameter STORE_ITEM_DU_TYPE can be set to Y to ensure that the DU type of the stock item in the EDI order file is used for the order item when it is created.
If this EDI parameter is not set to Y, the DU type of the stock items for the orders that are being created will not default to the DU type of the first line of a previously processed order that is being amended in the same polling session. Other EDI parameters are available to control which DU type is used for the order items when the EDI parameter STORE_ITEM_DU_TYPE is not set to Y. Operations that are provided with a DU type for a stock item should set the EDI parameter STORE_ITEM_DU_TYPE to Y to ensure that the DU type of the stock item in the EDI order file is used. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 01784859
Summary of Call | Interface change |
Detail of Fix | Ensure COL & DEL addresses are treated the same |
Set-up and Configuration | No set-up/configuration required |
Log Number: 01784924
Summary of Call | Order details Screens not accessible when searching via order search |
Detail of Fix | Transport_Unit_ID and Transport_Unit_Type are now visible in Orders screen (Configure Layout). Resolved the minimum width error. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 00233712
Summary of Call | EDI Orders |
Detail of Fix | New locations for EDI orders will have the advised delivery address. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 01742219
Summary of Call | EDI Order Upload |
Detail of Fix | An EDI order that failed to upload and be created due to data that failed validation can be corrected and reprocessed in the 'Interface Errors - Error Correction' screen.
The order will be created with the advised lines, and any items with their contents. Each order that is processed will refer to the parameters that are set for its original EDI process. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 01794295
Summary of Call | Scheduling engine errors |
Detail of Fix | The network scheduling engine will update orders that fail to fully schedule as auto-processed to prevent their being resubmitted for scheduling at a later date.
Any orders that encounter a locked record will be available for resubmitting once they have been rolled back and unscheduled. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 01778011
Summary of Call | Orders are having multiple lines with the same DU type |
Detail of Fix | The messages to Microlise will not send any duplicate detail-level order lines to avoid generating an error in Microlise when the message is processed.
Duplicate detail-level order lines will be assessed for: - Product Type - DU Type - Quantity - Packed Quantity - Packed RPE - Despatched Quantity - Delivered Quantity - RPE - Despatched RPE - Weight - Actual Weight - Volume - Actual Volume - SAP Order Line Number Only the last instance of these duplicated order lines will be sent to Microlise. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 01801142
Summary of Call | Order Windows |
Detail of Fix | The time windows are calculated with reference to the cut-off times for the schedule rules and the standard routes.
The local airport will be found for the current controlling depot during the assessment of the order's locations to assess standard routing. Auditing has been included for the assessment. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 01793592
Summary of Call | INVITRMEL barcode scanning issues |
Detail of Fix | The layouts of the customer labels have changed to accommodate longer item identifiers for the barcodes.
Some customers can now have item identifiers up to 16 digits. |
Set-up and Configuration | No set-up/configuration required |
Log Number: 01810707
Summary of Call | Payments - VAT consolidation |
Detail of Fix | The order costs will be updated for the payments when the order data is saved.
The cost, revenue and any applicable VAT will be updated and displayed in the Orders and Orders Wide screens. The new system parameter ACC_INC_ALL_ORDER_COST_PAYMENTS can be configured by cost centre of the order to include all payments for the costs and not just internal payments when validating the order. When system parameter ACC_INC_ALL_ORDER_COST_PAYMENTS is Y all order cost payments will be included in the order cost and VAT calculations. When system parameter ACC_INC_ALL_ORDER_COST_PAYMENTS is N only internal order cost payments will be included in the order cost and VAT calculations. |
Set-up and Configuration |
New Parameters | |||
---|---|---|---|
Parameter Name | Config Level | Setting Value | Result |
ACC_INC_ALL_ORDER_COST_PAYMENTS | COST_CENTRE | Y | Includes all payments for the order costs when validating the order. |
ACC_INC_ALL_ORDER_COST_PAYMENTS | COST_CENTRE | N | Includes all internal payments for the order costs when validating the order. |
MODULES DELIVERED
Module Name | Version No | Description | Log Number |
---|---|---|---|
INT_XML_IN.sql | 5.220 | Order Import Package | 01637325 |
CONTRACT.fmx | 2.73 | Contracts Form | 01736613 |
DATA_ADM_SYSTEM_PARAM_01736613.sql | 1.2 | Data Script | 01736613 |
DP_MCS_SCANNING.sql | 5.68 | MCS Scanning Package | 01736613 |
DP_NOKIA_LOC_PLAT.sql | 1.35 | Nokia Location Platform Interface | 01736613 |
DP_SCHEDULING_ENGINE.sql | 5.173 | Scheduling Package | 01736613 |
DP_MCS_SCANNING.sql | 5.69 | MCS Scanning Package | 00218431 |
DP_LOGIX.sql | 1.11 | Package for LOGIX Interfaces | 01721147 |
DP_EDI1214.sql | 5.5 | DB Package | 00224027 |
TRG_SCH_TRIP_XML_INT.sql | 5.33 | Trigger | 00217837 |
DP_SCHEDULING_ENGINE.sql | 5.174 | Scheduling Package | 01746708 |
OMS.sql | 5.244 | Order package | 01738129 |
DP_CSV6.sql | 1.42 | CSV Extract package | 01738129 |
CT_SCH_ORD_AFTER_CUT_OFF.sql | 1.1 | Data Script | 01738129 |
DATA_REP_REPORT_01738129.sql | 1.2 | Data Script | 01738129 |
DATA_REP_REPORT_PARAM_01738129.sql | 1.1 | Data Script | 01738129 |
DATA_RES_LABEL_FORMATS_01743547.sql | 1.1 | Data Script | 01743547 |
LFS_DESPATCH_NOTE.rep | 1.2 | Despatch Note | 00226252 |
LFS_TRIP_SHEET_POD_POC.rep | 1.7 | Trip Sum POD/POC Report | 00226252 |
DATA_RES_LABEL_FORMATS_00226975.sql | 1.1 | Data Script | 00226975 |
DP_CARRIER.sql | 1.94 | Carrier Management | 01748137 |
DATA_ADM_SYSTEM_PARAM_01748137.sql | 1.2 | Data Script | 01748137 |
DATA_ADM_SYSTEM_PARAM_CONFIG_01748137.sql | 1.1 | Data Script | 01748137 |
ORDERS_WIDE.fmx | 1.36 | Orders Screen | 00224886 |
DATA_ADM_SYSTEM_PARAM_01753120.sql | 1.1 | Data Script | 01753120 |
DATA_ADM_SYSTEM_PARAM_CONFIG_01753120.sql | 1.1 | Data Script | 01753120 |
INT_XML_OUT2.sql | 5.319 | Outbound XML Package | 01753120 |
LOCATION.fmx | 2.195 | Location Maintenance | 01753917 |
INT_XML_IN.sql | 5.221 | Order Import Package | 01743791 |
INT_XML_IN.sql | 5.222 | Order Import Package | 01777963 |
ORDERS_WIDE.fmx | 1.38 | Orders Screen | 00230920 |
INT_XML_IN.sql | 5.223 | Order Import Package | 01784859 |
ORDERS.fmx | 2.442 | Order Screen | 01784924 |
DATA_ADM_MSEL_FORM_PARAM_01784924.sql | 1.2 | Data Script | 01784924 |
INT_XML_IN.sql | 5.224 | Order Import Package | 00233712 |
DP_IMP_2.sql | 1.79 | Import Package | 00236029 |
INT_XML_IN.sql | 5.225 | Order Import Package | 01742219 |
INT_ERR_ORD.fmx | 2.8 | Interface error correction | 01742219 |
INT_XML_IN.sql | 5.226 | Order Import Package | 00235961 |
INT_XML_IN.sql | 5.227 | Order Import Package | 00235970 |
CUST_COST.fmx | 2.138 | Customer Maintenance form | 00235970 |
DATA_ADM_SYSTEM_PARAM_01778186.sql | 1.1 | Data Script | 01778186 |
TRG_SHA_XML.sql | 5.27 | Trigger | 01778186 |
TRG_STS_XML.sql | 5.22 | Trigger | 01778186 |
TRG_SOL_XML.sql | 5.46 | Trigger | 01778186 |
TRG_SCH_ORD_EARLY_DEL.sql | 1.3 | Trigger | 01778186 |
TRG_SCH_TRIP_XML_INT.sql | 5.34 | Trigger | 01778186 |
TRG_SOI_XML.sql | 5.22 | Trigger | 01778186 |
DP_SCHEDULING_ENGINE.sql | 5.175 | Scheduling Package | 01794295 |
DP_INT_XML_MIC2.sql | 1.34 | CTMS to MIC Interface | 01778011 |
INT_XML_MIC.sql | 5.154 | MIC interface | 01778011 |
OMS.sql | 5.245 | Order package | 01801142 |
TRM.sql | 5.203 | Trip manipulation package | 01798886 |
ORDERS.fmx | 2.443 | Order Screen | 01798886 |
ORDERS_WIDE.fmx | 1.39 | Orders Screen | 01798886 |
DATA_ADM_MSEL_FORM_PARAM_237483.sql | 1.1 | Data Script | 00237483 |
ORDERS_WIDE.fmx | 1.40 | Orders Screen | 00237483 |
ORDERS.fmx | 2.444 | Order Screen | 00237483 |
AT_PAR_TRIP_DTL_01727371.sql | 1.1 | Data Script | 01727371 |
DATA_ADM_SYSTEM_PARAM_01727371.sql | 1.1 | Data Script | 01727371 |
DATA_IMP_FIELD_01727371.sql | 1.1 | Data Script | 01727371 |
IMP.sql | 5.204 | CSV Imports Package | 01727371 |
INT_XML_MIC.sql | 5.155 | MIC interface | 01727371 |
PAR.sql | 5.113 | Paragon Interface | 01727371 |
PLANNING.fmx | 1.119 | Planning Screen | 01727371 |
DATA_ADM_SYSTEM_PARAM_01805293.sql | 1.1 | Data Script | 01805293 |
DATA_ADM_SYSTEM_PARAM_CONFIG_01805293.sql | 1.1 | Data Script | 01805293 |
INT_XML_EFX.sql | 5.19 | EFX XML Package | 01805293 |
LFS_LABEL.rep | 1.23 | Label Report | 01793592 |
LFS_LABEL_MULTI.rep | 1.11 | Label Report | 01793592 |
DATA_RES_LABEL_FORMATS_01793592.sql | 1.1 | Data Script | 01793592 |
OMS.sql | 5.246 | Order package | 00246043 |
DP_EPOD_WEB_SERVICE.sql | 1.134 | EPOD Web Service | 01807529 |
DATA_ADM_SYSTEM_PARAM_01810707.sql | 1.1 | Data Script | 01810707 |
DATA_ADM_SYSTEM_PARAM_CONFIG_01810707.sql | 1.1 | Data Script | 01810707 |
ACC.sql | 5.83 | Accounts package | 01810707 |
OMS.sql | 5.247 | Order package | 01810707 |
ORDERS.fmx | 2.445 | Order Screen | 01810707 |
ORDERS_WIDE.fmx | 1.41 | Orders Screen | 01810707 |
ADDITIONAL CHANGES
WCS
There are no WCS changes required.
EPOD/T2A
There are no ePOD/T2A changes required.
MCS
There are no MCS changes required.
PORTAL/TTM
There are no Portal changes required.
EDI
There are no EDI changes required.