RTVN 22.0 Release Notes - Dashboard - Portal

One NetworkRelease Notes

Published 02/12/2019

Copyright Notice

© 2019 by One Network Enterprises, Inc. All rights reserved.

Printed in the United States of America, 2019.

No part of this document may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission of One Network Enterprises.

Release Notes – RTVN 22.0 Release Notes

Table of Contents – 3

1 Table of Contents

1 Table of Contents 32 System and Network Changes 132.1 Network Changes 14

2.2 System Requirements 15

2.3 Backward Incompatibilities 162.3.1 Manufacturing 16

2.3.2 Logistics 16

3 Enhancements and New Features 173.1 Command Center 183.1.1 Command Center UI/UX Enhancements 18

User Interface / User Experience Enhancements 18

3.1.2 Partner Onboarding 19

3.1.3 Temporary Role Assignments 19

3.2 Integration 203.2.1 Implement Standard 219 EDI X12 Interface for Logistics Service Request 20

3.2.2 Implement Standard 858 EDI X12 Interface for Shipment Information 20

3.2.3 Implement Standard Outbound DESADV - Dispatch Advice Message for EDIFact 21

3.2.4 Support for EDI Message Queue on Shipper Network for Carrier EDI Messages 21

3.3 Logistics & Transportation Management 223.3.1 Execution 22

Ability to View Tender Plan Historical Data 22

Carrier Allocation by TEU 23

Enhanced Bill of Lading Format 24

Latitude/Longitude for All Tracking Events 26

Mouse Wheel Scroll for Tracking Events 26

Payable Cost at Shipment Level 27

Planner Workspace Enhancements 28

Premium Freight Workflow 28

Re-calculation of Shipment Leg Dates During Parent Shipment Update 29

Service-Level Filter Added to Routing Guide 30

Site Contact Information for Shipment Details 30

Intrastate Authority Permit Required 31



Sorting by Pickup Date on Carrier Shipment Screens 31

Update Allowed Response Time in Groups by Carrier or Multiple Loads 32

3.3.2 Financials 33

Carrier PRO Number on Claims Status Listing Screens 33

Currency Conversion Rate Field on Invoice Detail Screen 34

Invoice Currency Derivation Enhancement 35

Invoicing Policies UI for Value Add Contracts 36

Searchable Invoice Reference Numbers 37

Truck Utilization Report 38

3.3.3 Global Trade 39

Controlling Site for Milestone Derivation Rules 39

Enhanced Online Analytics for Global Trade-related Metrics 40

Late Serialization 42

Lock Landed Cost for Global Shipments while In Transit 42

Redesigned Container View 42

3.3.4 Market Maker 43

3.3.5 Scheduling 43

Additional Fields on VASP Appointment Outbound Interface 43

Capacity Utilization Summary Updates 44

Ability to Schedule Controlled with Non-Controlled Shipments 45

Delivery Appointment Warning Enhancement 45

CSV Interfaces for Scheduling Policies 46

Enhanced Scheduling Alert 47

Shift-level Rules 47

Template for Creating Recurring Standing Blocks 48

Dock Door Group Order in Calendars 48

Updated Site-level Projected Capacity Views 49

3.3.6 Visibility 50

Ability to View Shipment-specific Details for Stops on Map 50

Auto-Complete and Picker for All Carrier Filters 50

Automatic Closure of Holds Based on Milestones 51

Check for Case-sensitive Shipment Numbers 52

Deactivation of Milestone Processes 53

Dimension and Hazmat Info on Shipment and Movement PDFs 54

Enhanced UI for Transportation Admin 55

Filter by Multiple Equipment Type on Transportation Reports 56



Incoterms Fields on Search Shipment Reports 57

Mandatory Vehicle/Equipment Number 57

Missing Attachment Alert Subscription 58

Reason Code Section on Cancel and Delete Functions 59

Problems Link Support 60

Reason Code and Comments when Confirming Load to Carrier 62

Report Subscriptions for Logistics Reports 63

Restrict Future Dates for Pickup and Delivery Tracking Events 63

Search Movements Report Upgrade 64

Shipment Window Validation 65

Shipment Events as Part of Lead-Time References 66

Shipment State Filter for Shipment Not Delivered Alert 67

Shipment State Summary Report and Portlet Filters 67

Shipment Template Publication 68

Sorting for Shipment Type Field 69

Supplier Permissions Enhancements 69

Support for Off-network Drivers 71

Tender Plan Screen Enhancements 71

UI Enhancements for TMS 72

Warning Message for Changes on Shipment Leg 73

3.4 Manufacturing 753.4.1 Constrained Demand Translation Enhancements 75

Constrained Demand Translation Engine Demand Scenario Support 75

Item Allocation Ordered by Customer Priority 77

Constrained Demand Translation Support for Component Effective Dates 77

3.4.2 Updated Search Where Used Report 78

3.4.3 Dynamic Product Group Type Name on Raw Material Forecasts by Commodity Code TLVs 79

3.4.4 MRP Engine Execution for Specific Finished Goods 79

3.4.5 Production Planning Menu Reorganization 80

3.5 Master Data Management 823.5.1 Additional Filter Details at VC Level for Particular Organization or Enterprise 82

3.5.2 Approval Matrix Enhancements 82

3.5.3 Dynamic Enumeration for Item Category 83

3.5.4 Item Description Enhancements for BOMs 83

3.5.5 Precedence Field Added to Item Substitution Screens 84



3.5.6 Product Group Type Picker for Location Product Association Screen 85

3.5.7 Support for GS1 and Item Catalog 86

3.6 ONE Blockchain™ 883.6.1 Chain of Custody 88

Compliance and Exceptions 88

3.7 ONE Social Apps 90

3.8 Optimization 913.8.1 Replenishment 91

Aggregated Orders Forecast Enhancements 91

Improved Support for UOM Conversion 92

RPL API Data for Selected Time Zone 93

3.8.2 Demand Planning 93

Alerts for Severe Trend Deviation 93

Complete Support for Traffic Site Group-level Forecasts 94

Product Mix Scenarios for Foot Traffic 95

Forecast Review by Site 95

Simplified DP Alert Engine Configuration 96

Site-Seasonality Association Templates 97

Site Group Filters on Search Traffic Forecast 98

Weekly Data for Search Store POS 99

3.8.3 Inventory Planning 100

Multi-Tier Inventory Planning 100

3.8.4 Demand Translation 101

Demand Translation by PLU Item 101

3.9 Order Management 1033.9.1 Contracts 103

Procurement Contract Enhancements 103

Management Organization for Procurement Contracts 104

3.9.2 Requisition 104

Creating and Managing Requisitions 104

Requisition Features 109

3.9.3 Order 111

Tracking Events on Orders and Order Lines Regarding Holds 111

On-Hand Visibility during Order Creation and Processing 112

Disable Change Request Collaboration 113



Emergency and Expedite Options for Orders 115

Expedite Action for Purchase Orders 115

Links Tab for Associated Requisitions 116

Partially-Shipped Lines on Purchase Order Search 116

Ship to Country and Ship from Country on Purchase Order Reports and Portlets 117

Updated Date Fields for Collaboration 119

Automatically Populate Vendor Item Price Based on Item Mapping 119

Audit Trail on Packing Requirements Screen 120

Assign To Filter on Order Hold Report 121

Return Order Program Information Updated 121

Enhanced Bulk Update Operations 122

Redesigned RFQ Explorer 123

3.9.4 ASN & Shipments 124

Equipment Type for ASN Creation 124

Over-shipping Tolerance Validator 124

Visibility for Existing ASNs 126

3.9.5 Procurement Invoice 127

Manual Invoice Creation Option 127

3.9.6 UI Changes for Order Screens 127

3.9.7 Vendor Performance 128

Vendor Performance Overrides 128

3.9.8 Analytics 129

Analytics Details Report Enhanced to Support Totals 129

3.10 Platform 1313.10.1 Dynamic Transformations for EDI Messages 131

3.10.2 Mobile App for Packing and Receiving 131

3.10.3 Organization Hierarchy with Permissions 132

3.10.4 Support for Org-level Enumerations 133

3.11 S&OP 1343.11.1 Sandbox Plant Capacity Management Admin UI 134

3.11.2 Support for Capacity Type on Capacity Management UIs 134

3.12 SCPT 1363.12.1 Incoterms Fields on Search Shipment Lines Report 136

3.12.2 Multiple Sites with Different Time Zones on TLVs 136

3.13 Warehouse Management 138



3.13.1 Additional Filters for WMS Reports and Portlets 138

3.13.2 Auto-move Packing List to Ready To Ship State Once Related Pick List is Closed 139

3.13.3 Available Inventory for Expired Lot 140

3.13.4 Batch No Field on WMS Reports 141

3.13.5 Bill of Materials Reconfiguration 142

3.13.6 Enhancements to Shipment Fact Report 143

3.13.7 Expiration Date on Packing List 144

3.13.8 Expiry Date Filter for WMS Reports 145

3.13.9 Inventory Aging Report – Alert Subscription and Portlet 146

3.13.10 Lot Expiry Date on Cycle Count Line 147

3.13.11 Lot Instance Inventory Tracking 148

3.13.12 Multiple BOMs for the Same Serial-controlled Item 148

3.13.13 Multiple Stocking UOMs 149

3.13.14 Notification Alert on Cycle Count 150

3.13.15 Printing Pick Lists as PDFs 150

3.13.16 Reason Reject Code for Rejected Quantity 151

3.13.17 Ship From Site/Ship From Address/Ext Ship From Site on Packing List 152

3.13.18 UI Enhancements for WMS 153

3.13.19 Usage Rule for Items on Receipts and Pick Lists 153

4 Bug Fixes 1554.1 Logistics Bug Fixes 1564.1.1 Array Exception for Batch Confirm Action – PDS-12167 156

4.1.2 Auto-approval Missing Hold due to Currency Mismatch – PDS-12410 156

4.1.3 Blank Reports – PDS-12052 156

4.1.4 BOL/AWB Number not Set on Shipment After Processing EDI 301 – PDS-11228 / LS-35648 157

4.1.5 Broken Filters on Planner Report – PDS-12762 157

4.1.6 Broken Validation for Pickup and Delivery Dates – PDS-11954 157

4.1.7 Cancel Movement and Execution Windows Showing Different Enumerations – PDS-12602 157

4.1.8 Creation Date and Event Date in Different Formats in Shipment Tracking Event Outbound – PDS-11920 158

4.1.9 Customer can Deactivate and Update Enterprise on Partnership Entry – LN-45574 / PDS-11938 158

4.1.10 Deactivated Partner Profile Still Found SaveToConfirmed Via Integration – PDS-13282 158



4.1.11 Enterprise Slice/Data Warehouse DB not Seeing Partner Organizations - LN-46855 158

4.1.12 Fuel Index Rate Showing Two Decimal Places — PDS-14406 159

4.1.13 Movement Link Persists on Canceled Invoice Lines – PDS-11831 159

4.1.14 Multiple Operating Cost link Appearing when Currency and Operating Costs are the Same – PDS-14198 159

4.1.15 Newly Created Favorites not Working – PDS-12607 160

4.1.16 Picker and AutoComplete not Supported on Origin Site and Destination Site Screens – PDS-13962 160

4.1.17 Outbound Shipment Message Not Generated – PDS-12379 160

4.1.18 Out Of Memory Issue – PDS-14464 160

4.1.19 Permissions-restricted Roles Allowed to Perform Actions – LN-46174 / PDS-12911 161

4.1.20 Spot Bid Rejected Alert to All Carriers – PDS-13399 161

4.1.21 Remove Trailing or Leading Space from Site or Partner Site Name – PDS-13178 161

4.1.22 Required Field not Marked in Accessorial Pop-up – LN-46114 / PDS-12763 161

4.1.23 Route Showing Expired Rates for a Carrier – LN-45527 162

4.1.24 Shipment and Movement State Mismatch on Movement Upload – PDS-13992 162

4.1.25 Shipments in Continuous Move Disappearing – PDS-13876 162

4.1.26 Site Scheduling Policies Report not Showing all Settings – LN-45565 / PDS-11965 162

4.1.27 System is Allowing Parent Shipment to Close when Legs are not Closed – PDS-12573 163

4.1.28 System Should Not Allow To Create Shipment With Leading or Trailing Space – PDS-14364 163

4.1.29 Tender Plan History Missing Timestamp and Changed By User Details – PDS-12278 163

4.1.30 Unable to Open Parent Shipment in Closed State – PDS-14102 163

4.1.31 Unable to Resize Calendar on the Appointment Scheduling Screen – LN-46241/ PDS-12964 164

4.2 Order Management (OMS) Bug Fixes 1654.2.1 Add Order Pop-up does not Disappear once the Order Line is Added – PDS-14285 165

4.2.2 Applying Holds to Orders – PDS-11848 165

4.2.3 Deployment Order in New State Although Error is Set – PDS-14208 165

4.2.4 Document Disappearing and Reappearing – PDS-12309 165

4.2.5 Event Category Filter Disabled – PDS-12297 166

4.2.6 Order Hold Report Cannot be Saved as Favorite – PDS-12149 166

4.2.7 Order Update Alert not Working via Integration Action – PDS-11799 166

4.2.8 Ship To Site not Properly Verified on Purchase Order Synch Inbound – PDS-11306 167

4.2.9 Unable to Update Purchase Orders in New State on Inbound – PDS-13963 167



4.2.10 URL in New Note Alert Does not Direct User to the Order – PDS-10545 167

4.3 Optimization Bug Fixes 1684.3.1 Duplicate Item Policy in RPL – PDS-12433 168

4.3.2 IP Results Issues – PDS-14390 168

4.3.3 Load Builder Engine Query not Checking Active Flag of AVL – PDS-10330 168

4.3.4 Potential Lost Sales Report Cannot Select Multiple Stores – PDS-12404 168

4.4 Platform (PLT) Bug Fixes 1694.4.1 CSV Header and Content Displayed in the Incorrect Language - PLT-16370 169

4.4.2 Enhance Computation Measure on Date Difference - PLT-16308 169

4.4.3 EPT-level Permission by Policy - PLT-17025 169

4.4.4 Jasper Command Center Reports Not Showing the Corresponding Parent Folder Names – PLT-16929 169

4.4.5 New SFTP Destination Should Use JSCH - PLT-17216 170

4.4.6 Receiving Calendar Headers - PLT-17036 170

4.4.7 Support Async Export of Reports - PLT-16409 170

4.5 SCPT Bug Fixes 1714.5.1 Categories in New Report Subscription and New Integration Subscription not in Sync –

PDS-12308 171

4.5.2 Error Generating Return Order from Receipt Screen – PDS-12389 171

4.5.3 Outbound Shipment Summary Portlet Performance Issues – PDS-14652 171

4.6 Supply Chain Core Bug Fixes 1734.6.1 Administer Roles Organization Spelling – SCC-4083 173

4.6.2 Alerts not Working – SCC-4049 173

4.6.3 Change Partner Carrier for Static Routes – SCC-4176 173

4.6.4 Duplicate Route Error Message Inconsistency – SCC-4187 173

4.6.5 New Alert Subscription Page not Loading for Transportation Manager Role – SCC-4036 174

4.7 Warehouse Management Bug Fixes 1754.7.1 Alert for Percentage Rejected Quantity Tolerance not Getting Generated –

PDS-14124 175

4.7.2 Alert Notification Does not Contain Message Details – PDS-14068 175

4.7.3 Error in Requisition Activity and Distribution Report – PDS-14123 175

4.7.4 Error on Closing Partial Receipt – PDS-14512 176

4.7.5 Expiry Date Populated on PDF but not on Picklist Detail Screen – PDS-13998 176

4.7.6 Inventory Operation in Packed State – PDS-12659 176



4.7.7 Picker Report for Customer Partner Showing Partnerships of Other Organizations – PDS-13997 176

4.7.8 Pick List and Receipt Reports Order No Filter not Working – PDS-13498 177

4.7.9 Receipt Reject Alert Filters Showing Data from All Instances – PDS-14262 177

4.7.10 Receipt Rejected Quantity Report and Alert not working for the Order more than 2 Lines — PDS-14321 177

4.7.11 Requires Buffers for Component After Delete Load – PDS-12039 177

4.7.12 Requisition Activity and Distribution Report Showing Null Records for BOH Fields – PDS-14122 178

4.7.13 Reverse Inventory Adjustment on Cycle Count – PDS-11796 178

4.7.14 RTVN 9901 MRP Engine Failed Due to 50k Record Error – PDS-14289 178

4.7.15 Sequence Numbers not in Order in Printed Picklist PDF – PDS-14039 179

4.7.16 Text on PDF is too Small – PDS-14007 179

4.7.17 Unable to Add EPT-level Callback – PDS-12472 179

4.7.18 Unable to Close Receipt Due to Outbound Generation Error – PDS-13461 179

4.7.19 UOM Filter Not Present for Requisition Activity and Distribution Report – PDS-14115 180

4.7.20 Upcoming Cycle Count Notification Error – PDS-14334 180

4.7.21 Users Unable to Create Putaway Lists – PDS-13966 180

5 Revision History 181




System and Network Changes – 13

2 System and Network Changes



2.1 Network ChangesThe 22.0 release includes the following network changes:

• ONE is phasing out its FTP service on a customer-by-customer basis with the goal of moving all FTP users to SFTP by Q2 of 2019.• ONE is beginning to enforce relative path file access in SFTP and FTP accounts with a goal of completing the change by Q2 of 2019. ONE initiated the implementation of this change on a customer-by-customer basis during the 21.0 UAT period.



2.2 System RequirementsOne Network Enterprises (ONE) requires that clients meet the following minimum system requirements to achieve desired system performance:Hardware:

• Machine CPU/Memory: Core 2 Duo 2 GHz Processor with 2 GB of RAM or equivalent machine (with no other application running at the same time)

• Graphics: Video card capable of displaying 65,536 colors (16 bit) at 1024 by 768 resolution

Database Requirements for Data Warehouse:

• For Oracle Databases: compatible with Oracle 12c• For Maria Databases: compatible with MariaDB 10.0

Software:

• Operating System: Microsoft Windows Vista, 7, 8 or 10• Supported Browsers:

• IE 11• Chrome (Verified on version 71.0.3578.98)

• Plug-in: Adobe Flash Player 7.0 or later version

General:

• Valid email account• Broadband Internet Connection



2.3 Backward Incompatibilities

2.3.1 Manufacturing• The Inbound Interface MFG.ItemIn is deprecated and is not supported in versions after 21.0.

2.3.2 Logistics• The field called MCNumber located on the TMS.OrgProfile model has been changed from

BOOLEAN to STRING.

• GroupName Field• The field GroupName on model TMS.RoutePoolPoint has been changed from STRING

to STRING_ENUMERATION. • Field GroupName in Inbound Interface TMS.RoutePoolPointInbound version 2.0

changed datatype from STRING to STRING_ENUMERATION.

• Model TMS.SiteConcConstraint has been removed in this release.


Enhancements and New Features – 17

3 Enhancements and New Features



3.1 Command Center

3.1.1 Command Center UI/UX EnhancementsThis release introduces several user interface and user experience enhancements to Command Center. These enhancements include general improvements to the appearance of Command Center as well as additional features designed to improve the Command Center user experience.

User Interface / User Experience Enhancements

• Improved Accessibility - The change of hyperlink color from red to blue made all themes more accessible to visually impaired users.

• Updated Header Bar Icons - The header bar appearance is refreshed and includes restyled icons. These icons continue to deliver the same functionality as in previous versions. (shown below)

• User Help Access - The access point for the online help documents is relocated to the standard Command Center menu bar. (shown below)

• In-Page Tabs - The appearance of in-page tabs is updated to improve the overall usability of system screens which have in-page tabs. (shown below)

• Updated Button Appearance - The buttons are now styled to match the rest of Command Center and have improved visibility.

• Accordions - On tabs where there are multiple content areas contained in accordions (show/hide), we have restyled the appearance of the accordions to match the general Command Center styles and themes.

• Upload Page - The upload page for uploading CSV files has been updated in all locations where uploading screens appear.

Analytics Impact None

Integration Impact None

Related Functionality

None



Usage and Configuration

Search the online help for Command Center for more information about Command Center.

3.1.2 Partner OnboardingHistorically, customers worked with the NOC to onboard one or more Organizations and to establish partnership once they onboard. The Partner Onboarding feature simplifies the onboarding process. With this feature, customers can search for partners in ONE, establish partnerships with organizations already in ONE, and invite organizations to join ONE if they have not already joined. Customers have complete visibility of the created partner invitations and their corresponding status. A mutual partnership is created between two Organizations once the invited Organization agrees to the partnership.




None


See the "Partner Onboarding" Quick Guide for more information.

3.1.3 Temporary Role AssignmentsOften, an organization will need to assign a role to a user on a temporary basis. For example, this may happen when the primary user is not available for some time (e.g., leave of absence). With this enhancement, the system provides a way for the primary user, or a local administrator, to temporarily assign a role to another user. These role assignments have an effective date range and expire after the effective end date. The updated user cannot log in with the temporary role before or after the effective date. The temporary role assignment can be revoked before the effective end date by either the user who assigned the role in the first place or the enterprise admin.




None


See the "Temporary Role Assignments" section of the 22.0 New Feature Usage and Configuration Guide for more information.



3.2 Integration

3.2.1 Implement Standard 219 EDI X12 Interface for Logistics Service Request

With this enhancement, a new standard 219 EDI X12 inbound interface for Logistics Service Request has been implemented. Logistics Service Request supports the following:

• Load• UnLoad• Requested Ship Date / Pick Up Date• Delivered By This Date• Scheduled Pick Up Time• Earliest Requested Pick Up Date• Latest Requested Pick Up Time• Ship To• Ship From




None


None

3.2.2 Implement Standard 858 EDI X12 Interface for Shipment Information

With this enhancement, a new standard 858 EDI X12 inbound interface for Shipment Information has been implemented. The shipment interface provides the following information:

• Transaction Details• General Shipment Information• Reference Identification• Address Information• Geographic Location




None




None

3.2.3 Implement Standard Outbound DESADV - Dispatch Advice Message for EDIFact

This update implements a new outbound interface for the DESADV EDIFact format. This outbound interface applies to shipment model. By using this interface, customers can subscribe to and receive a DESADV EDIFact file when a shipment is in the "Awaiting" state. One Network then sends the DESADV EDIFact file to the customer.




None


Contact the NOC for more information.

3.2.4 Support for EDI Message Queue on Shipper Network for Carrier EDI Messages

This software release gives shipper network users visibility of carrier EDI messages done on the Global Logistics Gateway (GLG) via the EdiMessageQueue report within the instance. This feature allows users to view these messages within the instance, rather than having to connect to GLG separately just to view the status of carrier EDI transactions.




None


None



3.3 Logistics & Transportation Management

3.3.1 Execution

Ability to View Tender Plan Historical Data

Users now can view historical tender plan data by clicking a link on a tender plan details page. When clicked, the link opens a report which shows all previous tender plans and tender details.

The TP History page (seen in the screenshot below) shows sequence, cost, route, and state details.






None


See the "Viewing Tender Plan History" section of the 22.0 New Feature Usage and Configuration Guide for more information.

Carrier Allocation by TEU

This release includes a new flag in the header section on the Rotational Assignment UI for Carrier Groups to reveal if commitments are measured in TEUs (Twenty-foot Equivalent Units) which is used to manage container capacities. When this flag is enabled, the system computes commitment in terms of TEUs for container moves for a movement, instead of per movement.

For example, one 20 ft. container = 1 TEU, and one 40 ft. container = 2 TEUs. A movement using these two containers has a commitment of 3 TEUs instead of 1.



1 mailto:[email protected]




None


See the "Creating New Rotational Assignment" section in the 22.0 New Feature Usage and Configuration Guide for more information.

Enhanced Bill of Lading Format

The Bill of Lading (BOL) format is updated in this release. The new format supersedes the previous format and is available on the Documents tab of the Shipment screen. The new BOL, like the previous format, is available as a PDF which can be downloaded or emailed.

Customers are able to use the previous BOL format if desired. If the previous version is desired, please contact the NOC at [email protected] to request the change.

mailto:[email protected]

mailto:[email protected]






None





Latitude/Longitude for All Tracking Events

Carriers can provide latitude and longitude information for all types of shipment tracking events (i.e., "Delayed," "Arrived," or "Update Current Position"). The system is enhanced to record latitude and longitude data on all events. Latitude and longitude data can be entered on the Tracking Events pop-up window in the User Interface (UI) as well as Latitude and Longitude fields in EDI messages.


Integration Impact EDI messages can relay latitude and longitude data for all tracking events.


None


None

Mouse Wheel Scroll for Tracking Events

With this enhancement, users can utilize the mouse wheel to scroll through a list of tracking events that is longer than the viewing window. This feature adds to the scroll up/scroll down buttons on the side of the window and makes viewing all tracking events for a shipment or a movement much easier.






None


None

Payable Cost at Shipment Level

The Manual Allocation UI supports shipment cost value, which is automatically derived based on the percentage provided. The customer can manually populate the LTL (Less Than Truck Load) Cost field on the Shipment Detail UI, which represent the ad-hoc cost to execute the shipment. As part of Tender Plan Generation, for any carrier pass-in tenders (a tender where a carrier exists on a route, but there is no contract for that carrier), the cost is defined based on the sum of shipment LTL cost on all shipments in that movement. For movements in the "Awaiting" or "Tendered" state, whenever the movement cost is updated, the shipment LTL Cost is automatically adjusted based on cost percentage.




None


See the "Creating a Shipment" section in the Online Help for more information.



Planner Workspace Enhancements

The Planner Workspace Report is updated to include new fields and a filter. The Client and Spacesfields are added to the report in order to display more information for the planner user. Additionally, the report can be filtered by client to reduce the number of search results.




None


See the "Viewing Planner Workspace" section in the Online Help for more information.

Premium Freight Workflow

The new Premium Freight Workflow supports organizational control of premium freight costs through a structured approval workflow. The workflow begins when a shipper creates a premium freight load and assigns the load to a premium freight service level triggering higher costs exceeding approval thresholds.

Automatic approval for the load is based on the total freight cost; if the cost is above the auto-approval threshold, the load moves to an approval phase. The level of approval needed depends on the cost, as more expensive freight loads require higher levels of approval. Once proper approval has been received, the load moves to the "Confirmed" state and follows the standard workflow for transportation and visibility.






None


See the "Configuring Premium Freight Workflow" section in the 22.0 New Feature Usage and Configuration Guide for more information.

Re-calculation of Shipment Leg Dates During Parent Shipment Update

This update changes shipment screens to include new functionality for computing delivery dates. When a user adds a Pick-Up Date, the Compute Delivery Date button becomes available in the header section of the parent shipment. This button allows the system to run a computation and produce an estimated Delivery Date. Additionally, Shipment Leg dates are updated and populated according to the calculation.




None


None



Service-Level Filter Added to Routing Guide

With this update, the Service Level filter appears on Routing Guide screens. This optional filter helps users filter routing guide transit time options for carrier contracts.




None


See the "Using Filters" section in the Online Help for more information.

Site Contact Information for Shipment Details

The Shipment Details screen is updated with this release. Pickup contact information is now automatically populated using Site shipping contact information in the system. Additionally, Delivery contact information is derived directly from Site receiving contact information. If pickup or delivery information is not available from Site information, then it is taken from Site contacts.




None




None

Intrastate Authority Permit Required

This update to Carrier Profiling includes a parameter called Intrastate Authority Permit Required. This requirement is necessary for shipments moving across states that require a permit of authority. Using the Carrier Profiling UI, users can set the validation, which shows an error message when planning an intrastate shipment. Additionally, a flag entitled "Skip Carrier Profile Validation" is available on the Carrier Partners UI. This flag overrides validations set for carrier profiles.




None


See the "Adding Carrier Partners" section in the Online Help for more information.

Sorting by Pickup Date on Carrier Shipment Screens

With this update, carrier users can sort all shipment reports and screens by pickup date. Users can sort the Pickup column in ascending or descending order by selecting the Pickup option from theAdvanced Sorting menu.






None


See step 9 in the "Report Layout Configuration" section of the Online Help for more information on advanced sorting.

Update Allowed Response Time in Groups by Carrier or Multiple Loads

With this update, Tendering Policies are updated to include the ability to change the default Allowed Response Time based on the carrier. The Carrier field is available on the Create Tendering Policies UI. Additionally, Tender Plan generation now checks for policies that contain both a carrier and site first. If a policy that contains a value for both fields is not found, then the system then checks for policies based on the carrier only. If there is still no valid policy, then the system will check for policies based on the site as a last attempt.






None


None

3.3.2 Financials

Carrier PRO Number on Claims Status Listing Screens

Before this release, the system displayed the carrier Pro Number on Claims detail screens, but not on status listing screens. This update provides a PRO Number column on each status listing screen (e.g., New, Open, etc.) when searching claims. The screenshot below contains an example of the column.






None


None

Currency Conversion Rate Field on Invoice Detail Screen

Users can view currency conversion information for invoices. The Preferred Conversion Rate field for Invoice Lines explains the conversion factor and details if a currency conversion occurred.






None


See the "Searching Invoices" section in the Online Help for more information.

Invoice Currency Derivation Enhancement

With this enhancement, when a movement has a tender and carrier contract which use the same Unit of Measure (UOM), the system uses that rate currency on the invoice. If the rates on the tender and carrier contracts use different UOMs, the system uses the Base Rate UOM listed on the carrier contract. This policy is enabled using the Use Base Rate As Pref UOM flag at the carrier contract level.






None


None

Invoicing Policies UI for Value Add Contracts

With this release, a UI for Invoicing Policies is available for Value Add Contracts. Users can enter local and global policies for invoice generation and invoicing events. This screen is accessed from the Contract Mgmt menu, and policies can be created for all active Value Added Service Providers.






None


See the "Managing Global Invoicing Policies" section in the 22.0 New Feature Usage and Configuration Guide for more information.

Searchable Invoice Reference Numbers

In some instances, carriers have different invoice numbers than those generated by the One Network system. With this enhancement, carrier users can enter and search for their reference invoice numbers on Invoice screens. The Reference Invoice Number field is available on the header section of invoices and is also available as a filter when searching invoices.






None


None

Truck Utilization Report

The Truck Utilization Report allows users to see the utilization percentage of a truck on a specific movement. The report displays both the quantity (space) utilization as well as weight utilization. Users can search by movement number for a specific movement and can refine the report using a delivery date range and the status of the movement. The % Quantity Utilization and % Weight Utilization are calculated based on the equipment type settings of the equipment selected for a movement.



2 https://techdocs.elogex.com/display/OHD/.Managing+Equipment+Settings+v21.03 https://techdocs.elogex.com/display/19FG/.Viewing+Truck+Utilization+Report+v22.0




Search for "Managing Equipment Settings2" in the Online Help for additional information on Equipment Settings.


See "Viewing Truck Utilization Report3" section in the 22.0 New Feature Usage and Configuration Guide for more information.

3.3.3 Global Trade

Controlling Site for Milestone Derivation Rules

With this update, the Controlling Site field is available on the Milestone Derivation Rules screen. Entering a controlling site on this screen allows the system to automatically derive the milestone process by taking into consideration the controlling site defined on milestone derivation rule. The milestone process template is derived based on the best match for the controlling site on the shipment header.

Milestone derivation rules can be ranked using the up and down arrows on the left-hand side of the screen. If a match is not available under milestone derivation rules, then the system does not populate this field on the shipment header.

https://techdocs.elogex.com/display/OHD/.Managing+Equipment+Settings+v21.0

https://techdocs.elogex.com/display/OHD/.Managing+Equipment+Settings+v21.0

https://techdocs.elogex.com/display/19FG/.Viewing+Truck+Utilization+Report+v22.0

https://techdocs.elogex.com/display/19FG/.Viewing+Truck+Utilization+Report+v22.0






None


None

Enhanced Online Analytics for Global Trade-related Metrics

Global trade-related fields are now available on the Network Analysis Report. The following fields are available:

• Detention Time in Days• Detention Cost• Item Name• Total Landed Cost • Demurrage Time in Days • Demurrage Cost• No of Containers • TEUs



Additionally, clicking the Total Shipments count on the report opens a list of shipment details and an audit trail for all applicable shipments in the selected state.




None


None



Late Serialization

In some cases, a manufacturing facility cannot apply serialization immediately to some products, which later enter the supply chain. Therefore, occasions arise that require users to apply serialization to the product at a point downstream from the original point of manufacturing and packaging. This process is called Late Serialization. With this release, late serialization can be applied to a Singleton, or at the Singleton Line level in the system.




None


See "Applying Late Serialization" section in the 22.0 New Feature Usage and Configuration Guide for more information.

Lock Landed Cost for Global Shipments while In Transit

With this enhancement, users are not allowed to add or update landed cost information once a global shipment reaches the "In Transit" state. Updating landed cost information after the shipment is in transit could potentially cause the cost to rise above the price threshold, creating holds and shipment problems. For any global shipment in the "In Transit" state or further, the Total Landed Cost tab on the shipment UI shows inactive buttons for the Delete, Add, and Upload options, and submitting a CSV file with changed landed costs causes an error message to appear on the Landed Cost CSV Upload screen.




None


None

Redesigned Container View

This update includes a redesigned Container View. The top portion of the screen shows a summary of containers per State. The lower portion of the screen shows container numbers with related information, including booking information, current location, reference numbers, and links. Users can click on a container number to view container information as well as book the container to a shipment, if necessary. Clicking the small arrow to the left of the movement number shows an expanded list of associated sub-movements. Additionally, the Links column now shows full words as links, instead of single letters, and "More..." if the word links are unable to fit in the current cell width.






None


See the "Working with Containers" section in the Online Help for more information.

3.3.4 Market Maker

3.3.5 Scheduling

Additional Fields on VASP Appointment Outbound Interface

With this update, the following fields are available on Value Added Service Provider (VASP) Appointment Outbound messages:

• Shipment Estimated Pickup Date• Shipment Estimated Delivery Date• Shipment Commodity Code• Shipment Equipment Type• Site Address• Site Organization• Pickup Location• Pickup Appointment Date/Time• Pickup Actual Date/Time



• Commodity • Equipment Type

Users can utilize these additional fields when viewing VASP appointment requests.




None


None

Capacity Utilization Summary Updates

This update allows users to find unscheduled Standing Block capacity for a given date when creating appointments. Users can view Standing Blocks Unscheduled whose CapacityUOMmatches the UOM they are working with on the Scheduling Summary. A column called "Standing Block Unscheduled" appears on the UI and lists the available unscheduled standing blocks by capacity type.




None


None



Ability to Schedule Controlled with Non-Controlled Shipments

A new policy called "Schedule Controlled With Non-Controlled Shipments" is available on the Basic Policies tab of the customer-level Scheduling Policies screen. When enabled, this policy allows users to schedule both controlled and non-controlled shipments at the same time.




None


See the "Ability to Schedule Controlled and Non-Controlled Shipments" section of the 22.0 New Feature Usage and Configuration Guide for more information.

Delivery Appointment Warning Enhancement

Viewing multiple warnings without having to scroll helps prevent delivery appointment issues at the site level by allowing users to see more possible warnings at once. This enhancement allows users to see more than two Appointment Warnings at a time on the delivery appointment creation screen.




Integration Impact

None


None


None

CSV Interfaces for Scheduling Policies

Before this release, CSVs were created to capture data stored for scheduling policies at the Dock Door Group level. With this enhancement, CSVs are updated to capture recurrence data (e.g., work shifts at the dock door group level and work hours at the dock door level) as well as all Org-level and Site-level policies.




None


None



Enhanced Scheduling Alert

This release includes a new alert type called Appointment Scheduled Alert which is added to the Shipment alert subscriptions. The Appointment Scheduled Alert type allows users to receive a notification when an appointment is scheduled for a shipment.




None


See the "Create an Alert for Scheduled Appointments" section of the 22.0 New Feature Usage and Configuration Guide for more information.

Shift-level Rules

This update includes the ability to set reservation frequency and concurrency rules at the Shiftlevel. Users have the ability to configure fixed capacity limits on each work shift based on Load Type. This is useful in planning jobs where work shifts have different capacities for load types during different days and times of the week. The Scheduling Engine can enforce these Load Type-based capacity limits in addition to the Capacity UOM-based limits already enforced at the shift level. If either of these limits would be exceeded when attempting to schedule, the system shows a warning message indicating the Shift Capacity Constraint cannot be met.






None


None

Template for Creating Recurring Standing Blocks

This release includes an update to the Add Standing Block feature. Users have the ability to create a repeating template by selecting multiple days of the week for standing blocks. Blocks are created for selected days that fit inside the Effective Date parameters. Selected days are highlighted in grey. An example of multiple selected days is shown in the screenshot below.




None


See the "Creating Standing Blocks" section in the 22.0 New Feature Usage and Configuration Guide for more information.

Dock Door Group Order in Calendars

This enhancement to the Scheduling Policies allows users to specify the order in which users see the docks doors when viewing the calendar. For example, users may want to have busier doors listed first, although they might have names that are not in sequence or alphabetical order.






None


See the "Configuring Dock Door Group Order in Calendars" section in the 22.0 New Feature Usage and Configuration Guide for more information.

Updated Site-level Projected Capacity Views

Before this update, the Projected Capacity Views (PCVs) only supported cases and pallets as units of measure (UOM). The system was not able to offer appointment candidates if the shipment quantity UOM was not in cases or pallets. With this enhancement, Site-level PCVs are updated to compute the corresponding Capacity Units of Measure (UOMs) which are enforced according to the active Organization-level Scheduling Policy.




None


None



3.3.6 Visibility

Ability to View Shipment-specific Details for Stops on Map

With this enhancement, the following shipment information is added to site marker pop-ups on the Map screen (found on the Load tab when searching a specific movement):

• Shipment - the shipment number(s) involved at the stop• Operation - describes the operation performed on the shipment(s) at the stop

The following screenshot gives an example of the shipment data available when clicking on a stop on the map.




None


See the "Viewing Shipment-specific Details for Stops on the Map" section in the 22.0 New Feature Usage and Configuration Guide for more information.

Auto-Complete and Picker for All Carrier Filters

The system now features auto-complete and picker capability for the Carrier filter in Transaction Reports, Routing Guides, and shipment search screens. This allows users to easily select a carrier in the system when entering information on these screens.






None


None

Automatic Closure of Holds Based on Milestones

With this update, the system now supports automatic closure of shipment holds based on milestones. This functionality is policy-driven, and users can select Hold Policies when creating a milestone for a shipment. Holds related to the policy are closed upon milestone completion. Both standard and multi-modal shipments are supported for this feature.






None


See the "Custom Holds Based on Custom Milestones" section in the 22.0 New Feature Usage and Configuration Guide for more information.

Check for Case-sensitive Shipment Numbers

This enhancement adds a Transportation Policy called "Ignore Case For Shipment No" to the system. When a shipment is created or updated (and the policy is enabled), the system will ignore upper and lower case letters in validating shipment number uniqueness. If disabled, the system checks to verify that no shipment exists with the same alphanumeric digits. If a shipment already exists, regardless of case, an error message appears.






None


See the "Managing Transportation Policies" section of the Online Help for more information.

Deactivation of Milestone Processes

With this update, users can deactivate milestone processes in the UI. Milestone processes can be deactivated by removing the checkmark from the Active box on the Milestone Config Summaryscreen as well as the Milestone Config Detail screen. Deactivating milestone processes also disables all related milestone types; however, reactivating milestone process do not reactivate other milestone types, as they must be reactivated separately.






None


None

Dimension and Hazmat Info on Shipment and Movement PDFs

This update includes enhancements to Shipment and Movement PDF printouts. The Hazmat Infoand Dimensions columns are added in the information sections of printed documents. An example PDF document is shown below.






None


None

Enhanced UI for Transportation Admin

With this update, the Transportation Admin role can enable and disable features for a Shipper enterprise. Options include setting the starting day of the week, allowed services, and system and network features available to the selected enterprise.






None


See the "Enhanced UI for Transportation Admin" section in the 22.0 New Feature Usage and Configuration Guide for more information.

Filter by Multiple Equipment Type on Transportation Reports

Prior to this update, users could only filter shipment searches by a single equipment type. This enhancement allows users to search for multiple equipment types in all transportation reports, as well as the global search report. The Equipment filter allows you to select all equipment types you wish to see (Equal), or exclude equipment types you do not wish to see (Not Equal).




None


None



Incoterms Fields on Search Shipment Reports

With this update, the Inco Term and Inco Terms Location fields are added to the Search Shipment reports (Draft, Awaiting, Confirmed, etc). The screenshot below shows the columns on the report.




None


None

Mandatory Vehicle/Equipment Number

This release includes a new policy setting named Mandate Equipment For Carrier To Pickup. This policy setting, located on the Transportation Policy screen, allows an enterprise to require carriers to supply a vehicle/equipment number when picking up a shipment or movement. With the policy enabled, if a carrier does not supply a vehicle or equipment number, the system displays an error message and prevents the carrier from saving the pickup event.






None


See the "Managing Transportation Policies" section in the 22.0 Online Help for more information.

Missing Attachment Alert Subscription

This new alert subscription notifies users of a missing attachment for carrier or client Invoices. When a carrier or client creates an invoice - either manually or through EDI - and no PDF file is attached to the invoice, an alert is triggered and sent to subscribed users. The alert also applies to system-generated invoices when Auto-Submit is disabled. The alert does not trigger for re-submitted invoices.






None


See the "Missing Attachment Alert Subscription" section in the 22.0 New Feature Usage and Configuration Guide for more information.

Reason Code Section on Cancel and Delete Functions

This update includes the addition of reason code and comments fields for canceled movements and deleted shipments. Users can select a reason code and add a comment when executing the Confirm, Cancel And Confirm, or Delete functions. The Reason Code and Reason Code Comments fields are also added to the Shipment History and Movement History UIs, as seen in the screenshot below.






None


See the "Confirming a Movement Cancellation" and "Deleting Shipments" sections of the Online Help for more information.

Problems Link Support

With this update, users can click a Problems link on Shipment Report and Container View pages to view any problems associated with the shipment or container(s). The following screenshot shows the location of the Problems link for a shipment.



The Problems screen lists problems by ID number and shows problem type, priority information, and dates. This screen allows users to immediately address problems with shipments and work towards a quick resolution.




None




None

Reason Code and Comments when Confirming Load to Carrier

With this enhancement, users can set a reason code policy that requires a Reason Code and Comment when confirming a load to a carrier. The policy can be set to require these fields for the pop-up windows associated with the following actions performed in the UI:

• Save to Confirmed• Cancel• Tender Accept• Conditionally Accept• Copy Shipment• Accept Bid -> Market Maker

The following screenshot shows the Confirmation Reason and Confirmation Comments fields on the Save To Confirmed pop-up window.




None


See the "Configuring Reason Code Policies" section of the 22.0 New Feature Usage and Configuration Guide for more information



Report Subscriptions for Logistics Reports

Report Subscriptions are available for all Logistics Reports. The "Integration Subscriptions" option, located in the Tools menu, allows users to perform the following actions in the system:

• Define an interface group for Logistics report subscriptions• Define an outbound interface based on the following reports:

• Movement Shipment Report• Appointment Requests• Invoice Report




None


See the "Working with Report Subscriptions" section of the 22.0 New Feature Usage and Configuration Guide for more information.

Restrict Future Dates for Pickup and Delivery Tracking Events

This enhancement to Transportation Policies restricts a user's ability to create a Pickup or Delivery Tracking Event so that users cannot enter a date occurring in the future. Preventing this scenario is crucial for maintaining accurate Carrier scores in the Carrier Scorecarding feature.

With this policy enabled, the restriction applies to the creation of pickup and delivery tracking events whether they are created from the UI, using Integration, or via EDI messages. When a user



enters an invalid date for an event, the system generates an error message. The system validates the entered dates, comparing them to the system time instead of the local time.




None


See "Restricting Future Dates for Pickup and Delivery Tracking Events" in the 22.0 Feature Guide for more information.

Search Movements Report Upgrade

With this release, the Search Movements report screen uses a new UI framework for better usability. The default Filters screen is set up to easily filter movements, as many common filter options are available and easily manipulated.






None


None

Shipment Window Validation

Users are now able to set a policy to ensure that Early Pickup and Delivery dates/times cannot be the same as Late Pickup and Delivery dates/times, as it is not logical to have these times be the same. If a user enters the same dates and times for these fields on a shipment, an error message appears. This validation works for both manually-created and electronically-created shipments. This validation is set using the Transportation Policy entitled Validate Shipment Windows, as seen in the screenshot below.






None


See the "Working with Transportation Policies" section in the Online Help for more information.

Shipment Events as Part of Lead-Time References

With this enhancement, Lead Time References, as well as Milestones, can be created based upon a Shipment Event Reference. Lead time references are created based upon specific shipment event types and event dates. The Shipment Milestone computation code is enhanced to support tracking events created from lead time references. Additionally, the estimated completion date of the milestone is calculated based upon the event date of shipment event when "Lead Time Reference" is selected for milestone processes.




None


See the "Adding Lead Time References to Shipment Events" section in the 22.0 New Feature Usage and Configuration Guide for more information.



Shipment State Filter for Shipment Not Delivered Alert

This update adds a shipment State filter to the Shipment Not Delivered alert. This field helps users further filter Shipment Not Delivered Alerts by reducing the number of alerts sent by the system. You can see the location of the State field in the screenshot below.




None


None

Shipment State Summary Report and Portlet Filters

With this release, the Shipment State Summary Report and Portlet are updated to include filters. The default filters are Ship From Site, Ship To Site, and Show States With Zero Count. This enhancement makes this portlet and report functionality consistent with other reports and portlets across the RTVN platform.






None


See the "Using Filters in the Shipment State Summary Report" section in the 22.0 New Feature Usage and Configuration Guide for more information.

Shipment Template Publication

With this update, users can publish a shipment template for a specific user group or role type. This makes shipment creation more uniform for a group of users or a specific role. Additionally, if a user updates a shipment template, he will be able to republish it so that all updates to the template appear for others as well.




None


See the "Publishing Shipment Templates" section in the 22.0 New Feature Usage and Configuration Guide for more information.



Sorting for Shipment Type Field

With this update, the "Shipment Type" field can be sorted. The field can be sorted by using ascending, descending or advanced sorting methods.




None


None

Supplier Permissions Enhancements

With this update, users can define Supplier Permissions for a particular site. A Supplier Permission button is available on the Site Details page, which opens a pop-up window which allows users to select supplier partners who can access that site. When permissions are granted for a site, that site is visible for the selected supplier(s) on the Shipment Details page's Site picker.



Site Picker Screen:




Users can upload supplier site permissions by accessing Tools -> Upload -> Supplier Site Permissions and using the standard CSV uploading process.


See the "Supplier Permissions UI" section in the 22.0 New Feature Usage and Configuration Guide for more information.



Support for Off-network Drivers

This release includes updates to recording off-network drivers for movements. A new text field called Offnetwork Driver Name is available in the header section of the Movement Details UI to store information about a driver who is not part of your network. Any resource assigned to the movement on the Resource tab overrides the off-network driver value. The screenshot below shows the location of the new field on the movement screen.




None


None

Tender Plan Screen Enhancements

This enhancement adds a Distance field in the header section of tender plan screens to help users when adding a spot carrier or making adjustments to an existing tender plan for hubs whose rates are typically based on distance. This distance shown on the tender plan is the same distance listed in the Distance column of the Awaiting screen and is retrieved from the movement details.






None


None

UI Enhancements for TMS

In this release, many TMS screens underwent visual changes to enhance the user experience. Most of the visual enhancements consist of a change in common icons, screen icons, calendars, and flags on the UI. None of these enhancements impact existing workflows or functionalities. These enhancements are part of a global Command Center Enhancement.

The Search Shipment screen observes a change under the Links column. Earlier, the Links column has initials of the actions such as History, Tracking, and Tender Plan. Since this release, the Link column contains additional options such as Tender, Charges, Chain of Custody, Receipts.






See the "Command Center UI/UX Enhancements" section in these release notes for more information on specific UI/UX changes.


None

Warning Message for Changes on Shipment Leg

This update provides a warning message when users attempt to update the details of a shipment leg. If the dates, consignee, or shipper for the shipment leg do not match with the parent shipment and other related shipment legs, a warning message appears when attempting to save the changes.






None


None



3.4 Manufacturing

3.4.1 Constrained Demand Translation Enhancements• Constrained Demand Translation Engine Demand Scenario Support (see page 75)• Item Allocation Ordered by Customer Priority (see page 77)• Constrained Demand Translation Support for Component Effective Dates (see page 77)

Constrained Demand Translation Engine Demand Scenario Support

This release adds a new filter to specify the Engine Demand Scenario for the Constrained Demand Translation Engine. The TLVs display the results from the most recent scenario run.






None




None

Item Allocation Ordered by Customer Priority

This enhancement to the Constrained Demand Translation (CDT) Engine allows item allocation to be based on customer priority. Users can set the Customer Priority value (1-100, 100 being the highest priority) for each customer, and the CDT engine allocates items based on the defined customer priority.




None


See the "Setting Customer Priority" section of the 22.0 Feature Guide for instructions on defining customer priority.

Constrained Demand Translation Support for Component Effective Dates

CDT Engine now supports effective dates on BOM Components. Users can model the switching of components or changing component quantity for a specific Bill Of Materials.






None


None

3.4.2 Updated Search Where Used ReportThis update includes additional fields to the Search Where Used report. The following fields are available on the report:

• Item• Component Item Description• Quantity• Quantity UOM

These fields help users better understand where and how BOM (Bill of Materials) components are being used.




None




None

3.4.3 Dynamic Product Group Type Name on Raw Material Forecasts by Commodity Code TLVs

This enhancement updates the Raw Material Forecasts by Commodity Code Timeline View (TLV) screen so that the Product Group Name field is a dynamic field, meaning users can select different values for this field based on product Levels and Groups selected on the TLV. This change is beneficial to some companies that need to pick data based on different hierarchies.




None


None

3.4.4 MRP Engine Execution for Specific Finished GoodsWith this enhancement, the Material Requirement Planning (MRP) engine can be run for a specific finished goods item and can recompute demand translation for the impacted components. The engine finds the raw material items associated with the finished goods item selected and recomputes the requirements for those raw items. A filter called Finished Goods Item is available when running the engine.






None


See the "Working with the Demand Translation Engine" section in the 22.0 New Feature Usage and Configuration Guide for more information.

3.4.5 Production Planning Menu ReorganizationThis release updates the organization of the Production Planning Menu to improve the user experience. The menu items are grouped by functionality to improve the user experience: Engine, Timeline Views, Prod Order Fcst, Production Orders.

Engine

• Production Planning Engine• Mps Engine TLV• Mps Production Plan TLV

Timeline Views

• MultiBuffer BOM Hierarchy TLV• MultiBuffer Constrained Item TLV• Resource Group Aggregated POH TLV• Resource Group Detail TLV• Resource Capacity Review• Supply Planning Brand Owner Workbench



Prod Order Fcst

• Production Order Forecast Report• Upload Prod Order Fcst

Production Orders

• Production Order Report• Create Production Order• Production Work Order Summary• Search Production Work Orders• Create Production Work Order




None


None



3.5 Master Data Management

3.5.1 Additional Filter Details at VC Level for Particular Organization or Enterprise

With this update, the Search Location screen for VC admin users is updated to show Enterpriseand Organization details when selecting a Site filter. These details help users to filter information further when searching locations in the system. The screenshot below shows the Site pop-up window on the Search Location screen.




None


None

3.5.2 Approval Matrix EnhancementsThis release includes the following updates to the Approval Matrix UI:

• Role and User columns for an approval matrix entry are editable from both the Approval Matrix screen as well as the Detail screen.

• The Model Level Name column is now non-editable.• The Details, Organization, Role, and User columns contain hyperlinks to related information.






None


None

3.5.3 Dynamic Enumeration for Item CategoryWith this enhancement, the Item Category field on Comma-separated Value (CSV) files is set to a dynamic enumeration field, rather than free-form text. This field is now displayed as a drop-down selection on the UI after a successful CSV upload.




None


None

3.5.4 Item Description Enhancements for BOMsThis update includes the automatic population of the Item Description field on Bills of Materials (BOMs). When a user selects an item with a description while creating a BOM, the system



automatically adds the item description on the current BOM line. This is useful in expediting the BOM creating process for all users.




None


None

3.5.5 Precedence Field Added to Item Substitution ScreensThis release adds a new field called Precedence to the Item Substitution Detail Screen, the New Item Substitution Screen, and the Item Substitution Report. This field is a user-defined, numerical parameter, which is defined on the New Item Substitution screen.






None


None

3.5.6 Product Group Type Picker for Location Product Association ScreenThis update adds the picker functionality to the Product Group Type filter on the Location Product Association Hierarchy screen. Users can now select a product group type from a list in a pop-up window rather than having to type an exact value into this filter. The screenshot below shows the location of the picker icon on the Location Product Association Hierarchy screen.






None


None

3.5.7 Support for GS1 and Item CatalogThis release includes support for the following GS1/Item Catalog-related elements:

• Multi-value support for strings, string enumeration, and all number types.• A guided configuration for attribute configuration fields instead of plain text. For example,

for string enumeration, there is a drop-down box with available enumerations.• Schema selection policies.• Hierarchical application.• Ability to upload schema metadata and actual values via the inbound interface from the UI.• Ability to use a partner's schema if the schema is marked as public.

A sample process for this feature would be similar to the following procedure:

1. Create a product hierarchy.2. Associate items with the product hierarchy.3. Create attribute schema(s).4. Associate product hierarchy levels, item product group-level associations, and items with the

schema(s). 5. Set attribute values.

UIs have been enhanced for admin users to deal with attributes and values for master data management. An example is shown in the screenshot below.




Integration Impact Inbound integration has been updated to include support for this feature.


None





3.6 ONE Blockchain™

3.6.1 Chain of Custody

Compliance and Exceptions

The Chain of Custody feature can track items across multiple movements and sites, where there is potential for various kinds of exceptions, such as a shipment scanned at an unknown location, or a faulty temperature reading from a sensor on a truck. Additionally, at the point of handovers (pick up or delivery), both parties may have some alternate compliance rules, such as damaged barcodes on a package or broken seals, inspected as part of the handover, with any violations captured.

The system is updated to capture this compliance and exception data based on handover checks enforced at the point of pickup and delivery. All such exceptions from violations are computed and captured as part of the Exceptions tab on the Chain of Custody UI so that users can view and act upon them appropriately.




Chain of Custody




None



3.7 ONE Social AppsFollow the link below to view the latest updates for ONE Social Apps, including Chat and Blipper.https://esg.onenetwork.com/appHistory

https://esg.onenetwork.com/appHistory



3.8 Optimization

3.8.1 Replenishment

Aggregated Orders Forecast Enhancements

This release includes an enhanced Aggregated Orders Forecast (AOF) feature. AOF is a quantity of demand for an item at a site over a specified time range, but is represented by net demand (i.e., after inbound orders and current on hand are accounted for). This configuration enables the system to generate dependent demand for a distribution center (DC) without requiring store orders or interfering with possible independent demand from the DC stored in a Demand Forecast. Consequently, this allows for hyper-scale functionality by dramatically cutting down the volume of required data while running Demand Planning at the DC level. This model is implemented for Retail Advanced Replenishment, and users can view a report of aggregated order forecasts in the system.


Integration Impact An inbound interface is now available for AOF.


None


See the "Searching Aggregated Order Forecasts" section of the 22.0 New Feature Usage and Configuration Guide for more information.



Improved Support for UOM Conversion

In this release, improvements to UOM (Unit of Measure) conversion provide a common ground for defining conversion ratios between two different UOMs. Users have the flexibility to specify the quantities of supply and demand regarding UOM.

For example, if a customer wants to order items from a vendor, the customer stores the items in crates and Vendor is storing the items in a box. So, the Replenishment engine uses the new UOM conversion feature to get the required conversion ratios to convert box items into crates. The customer or vendor should share the information related to an agreed upon conversion factor, which is used by the engine.

The earlier implementation of UOM was restricted to a very few units only (Case/Pallet/Pound etc.). Also, the enumerations used internally were of different types, so converting between them was difficult, and no standard behavior was established to define the conversion factors.

To support this enhancement, a new field, Order UOM, is added to the UI. Users can specify the unit of measurement for ordering the items. The new field is added to Buffer, Buffer Lane, Item, and Store Buffer screens.




None


None



RPL API Data for Selected Time Zone

Replenishment Timeline Views (TLVs) are enhanced to support a single time zone view for multiple sites. The system now uses the current buffer's start time, which is based on one single time zone, rather than the subnet's start time for calculating data measures when showing a Projected Inventory View (PIV). This feature reduces confusion for users planning replenishment strategies for sites across time zones.




None


None

3.8.2 Demand Planning

Alerts for Severe Trend Deviation

This release introduces a new alert that analyzes trend deviations at an Item level. The alert identifies items that have significant deviation between future and past forecast for a specified number of weeks. The Buyer SCA dashboard contains a new portlet called Forecast Trend Deviation, which allows users to monitor the trend deviations. Users can apply various filters to obtain the required report.






None


None

Complete Support for Traffic Site Group-level Forecasts

With this update, the Demand Planning engine can now forecast foot traffic at the Site Grouplevel. Visibility for Site Group-level data is enhanced in the following Foot Traffic UIs:

• Geo Forecast Book• Geo Forecast and History Review• Search Traffic Forecast

The screenshot below shows the Site Group Level filter on the Geo Forecast Book screen. Note that "Site" is still an option for foot traffic; this update allows users to choose either level when forecasting for foot traffic.




None




See the "Working with Foot Traffic" section of the Online Help for more information.

Product Mix Scenarios for Foot Traffic

This update includes PMIX (Product Mix) Scenario support for foot traffic. Users can create PMIX scenarios, save them, and export the data to a spreadsheet, as desired. Scenarios are created by inputting a forecasted item, traffic percentage, site/site group, and a date range, along with a related BOM (Bill of Materials) as desired. The system then calculates an item forecast and a BOM forecast (if applicable) for the selected items per store. The information obtained from this report is helpful in predicting the amount of product needed to cover the expected foot traffic. The following screenshot shows the New Scenario screen, which is used to create a PMIX scenario.




None


See the "Working with Foot Traffic Scenarios" section in the 22.0 New Feature Usage and Configuration Guide for more information.

Forecast Review by Site

This update includes the addition of the Forecast Review by Site UI. With this screen, users can break down forecast reviews at the Site level. The report shows Items per Site Name, along with corresponding data measures. The screenshot below shows an example of this UI.






None


See the "Forecast Review by Site" section of the 22.0 New Feature Usage and Configuration Guide for more information.

Simplified DP Alert Engine Configuration

This release includes an update to Alert Engine Configuration. The Alert Config Detail screen is available, and users can enter simple subnet type and threshold details for alert configuration. All saved configurations appear on the Search Alert Config screen.






None


See the "Configuring the Demand Planning Alert Engine" section of the 22.0 New Feature Usage and Configuration Guide for more information.

Site-Seasonality Association Templates

This update introduces a UI used for Site-Seasonality Association. Users can apply seasonality templates to sites with Activation and Deactivation dates, similar to the way items are modeled for seasonality (e.g., Christmas products). The Search Site Seasonality Association menu option is added to the Seasonality group under the Demand Planning menu.






None


See the "Creating and Searching Site-Seasonality Association Templates" section in the 22.0 New Feature Usage and Configuration Guide for more information.

Site Group Filters on Search Traffic Forecast

The Search Traffic Forecast screen (found under the Demand Planning -> Foot Traffic menu option) is updated with this release. The Site Group Type and Site Group Level filters are now available and can be utilized when filtering the report. These optional fields help to further filter search results for foot traffic forecasts in regards to specific sites.






None


See the "Searching Traffic Forecasts" section in the 22.0 New Feature Usage and Configuration Guide for more information.

Weekly Data for Search Store POS

The Search Store POS screen is updated to include a Data Bucketization filter. Users can now select either Daily or Weekly data bucketization for viewing the report.






None


See the "Searching Store Point-of-Sale Data" section of the 22.0 New Feature Usage and Configuration Guide for more information.

3.8.3 Inventory Planning

Multi-Tier Inventory Planning

Multi-Tier Inventory Planning optimizes service levels of locations simultaneously across multiple tiers in a supply network so that the total cost of safety stock is minimized. Any given user’s network is composed of locations that are internal to the user, as well as locations that are external to the user. Multi-Tier Inventory Planning uses a dynamic safety stock formula to calculate the total cost of safety stock in a network, given the service level values that each of the locations is providing to its downstream connections. With this enhancement, users can analyze and change the amount of safety stock that is held in inventory in multiple locations.

The Multi-Tier Inventory Engine is available to analyze items and calculate a safety stock. Associated reports are available after a successful engine run.






None


See the "Working with Multi-Tier Inventory Planning" section of the 22.0 New Feature Usage and Configuration Guide for more information.

3.8.4 Demand Translation

Demand Translation by PLU Item

With this update to the Demand Translation engine, two new filters are available. Users can select a Site Group level and type, or Finished Goods Items. If the user selects a Site Group level and type, the engine calculates all finished goods and raw materials for a given site. However, if the user selects one or more finished goods item(s), the engine calculates raw material requirements for that item and all related raw materials only. This feature supports hierarchical Unit of Measure (UOM) conversion. The screenshot below shows the location of the filters when running the engine.






None


See the "Working with the Demand Translation Engine" section of the Online Help for more information.



3.9 Order Management

3.9.1 Contracts

Procurement Contract Enhancements

This release adds the following Procurement Contracts enhancements:

• Hold Support: Procurement Contracts support blocking as well as non-blocking holds. Holds are supported at the contract, or at the contract term level.

• Contract Management Org Support: Users can now define a contract management organization that is different from the buying organization to manage the contracts on behalf of the buyer.

• Contract Date Parameters: Contracts can have a start date that is in the past. The contract is considered valid as long as the contract end date is in the future.


Integration Impact Integration interfaces support a Start Date that is in the past.


None


See the "Working with Procurement Contracts" section in the 22.0 New Feature Usage and Configuration Guide for more information.



Management Organization for Procurement Contracts

With this update to Procurement Contracts, buyer users are able to select the Managing Organization while creating a contract. The Management Org field is added to the contract header. After creation, the selected managing organization is able to manage the contract on behalf of the buyer. The managing org is considered a 3PL Partner to the buying or creation organization.




None


None

3.9.2 Requisition

Creating and Managing Requisitions

The Line Type field is a new field available on Purchase Requisition lines. This mandatory field shows the default value of "Product," and can be edited by the requesting user until the requisition reaches the "Awaiting Approval" state. The following line type options are available:

• Product

Item Line Type



• Service• Kit

Generic/Specific Item Support :

Three fields are available for items on requisition lines: Ext Item, Generic Item, and Item. The Generic Item field shows all generic items based on the selected line type. If a user selects a generic item, the Item field shows all the specific items related to it. If the user does not provide a Generic Item, the Item field displays all the items based on the line type.

Requisition lines can be approved individually by users. The Approve Line action is available for requisition lines on Purchase Requisition detail screens. Requisitions that have some approved lines and some non-approved lines move to the "Partially Approved" state. This state supports the following actions:

• Revise• Approve• Convert To Order/RFQ

Users can revise specific fields on "Approved" and "Partially Approved" requisitions using the Revise action. The following fields are available for revision:

• Quantity• Fund• Fund Line• Target Price

If a user revises any of the above fields, the line must go through the approval process again, and the state shall change back to "Awaiting Approval."

Requisition Management Org Field

Requisitions now support the Requisition Management Org (RMO) field, which is automatically populated based on the buffer/item info. Users can change the RMO when the requisition is created; the defaulting logic applies only if the Requisition Management Org field is not manually populated. The RMO can manage the requisition on behalf of the requesting org.

Contract Information

A new column called Contract Info is available on the Requisition Line grid. Users can utilize this feature to find existing contract information which is related to each requisition line. Additionally, the Populate Contract Info button is available on requisition details screens after the user saves a requisition. Clicking this button forces the Contract Info column to be populated with available contracts which are in the "Open" and "Conditionally Open" states, and shows the contract number if only a single contract is available. If multiple contracts are available for the given combination of Ship To Site, Item, Request Delivery Date, and Vendor, a contract number for one contract and a

Items on the requisition line are filtered depending on the selected line type.

Individual Line Approval

Field Revision on Approval



count of remaining contracts is shown. Users can open contracts by clicking on the Contract No link.

Additionally, the Populate BOH button on requisition detail screens can be used to populate current Buffer On-hand (BOH) info based on the Ship To Site. If Program information is provided on the buffer for the site, then only that value is used. If that information is not found, it is not populated, and Location information is checked next. If no Location information is found, then the system checks Site information to populate the buffer BOH.

Authorization Support

This update includes Authorization support for requisitions. The authorization flow is activated when you configure the validation policy. The Authorization tab on requisition details screens shows all active and pending authorizations, assigned user, and status. When a purchase requisition requires authorization, a hold is created by the system. The hold is visible from the Holds tab on the requisition detail screen.

Inventory Information



Links for Associated Orders

This update includes a Links tab on requisition details screens. The tab contains two sub-panels that show linked orders and Requests for Quotation (RFQs). The Orders panel shows all orders created from requisition lines. The RFQ panel shows all the RFQs created from requisition lines.

Purchase Order Release for Lines with Contracts

This update allows for Purchase Order (PO) Releases to be created for requisition lines. Users can select the Convert To Order action on requisition details screens. Requisition lines which have contracts available for them are converted to PO Releases, and lines that do not have available



contracts are converted to Purchase Orders. Lines having contracts available are grouped based on contract terms for creating the PO Release. Different PO Releases are created for lines containing different contract terms. If multiple contracts are available for a single requisition line, contract sourcing is used to decide the contract to be used for creating the PO release.

Re-opening of Lines upon Cancellation of Order

This update allows for requisition lines from the "Closed" state back to the "Approved" state if the order created for it is either deleted or canceled. The requisition header state changes accordingly. Requisition lines are re-opened for following actions performed on its related order :

• Delete• Cancel• Delete Line• Cancel Line

See the Integration Impact section in the table below for more information.

The system now supports UI upload capability for requisitions. The Upload Requisitions menu item is available for buyer users. This option is not available for vendors. The location of the menu item is seen in the screenshot below.


Integration Enhancements

UI Uploads



Integration Impact The Purchase Requisition (PR) process supports the following actions for integration:

• Create• Revise• Cancel• Cancel Line


None


See the "Requisition Enhancements" section in the 22.0 New Feature Usage and Configuration Guide for more information.

Requisition Features

Additional Costs

This update includes the ability to view Additional Costs on requisitions. Additional Costs are generic so that they can be applied to multiple models. An Additional Costs link on the requisition header shows the total of additional costs related to the requisition.

The Additional Costs for Requisition pop-up window allows the user to add costs by type and apply them to the entire requisition, per line, or via an even distribution.



Documents Support

This update includes documents support at the Purchase Requisition line and header levels to make it easier for customer users to control document permissions and categorization. The following changes are implemented in this release:

• Added the documents icon and label at the requisition line level.• The New Document tab will be added on the requisition details screen at the header level.• Unless the transaction is saved, users are not able to save the documents.• Document Type and Document Type Permission are pre-requisites to uploading documents.• Existing attachments are migrated to the Documents tab under the "Attachments" category.



Holds Support

Purchase requisitions now support blocking and non-blocking holds. Holds are supported for the entire requisition as a whole, as well as for each line on the requisition.

My Items Support

This updated includes My Items support for purchase requisitions. The New Requisition screen now has an Add Line(s) button that opens a pop-up window where users can search for My Items and add them to the requisition. The Add Line(s) pop-up window is shown below, with the My Items picker field visible.




None


See the "Requisition Enhancements" section of the 22.0 New Feature Usage and Configuration Guide for more information.

3.9.3 Order

Tracking Events on Orders and Order Lines Regarding Holds

This update improves visibility, tracking, and warning messages for users when an order/order line hold action is applied. Prior to this release, there was no tracking event notification when orders or



order lines were put on hold, released, or closed. The table below explains the tracking events shown per hold action.

Hold Action Tracking Event Shown

Create Hold Created

Assign Hold Assigned

Close Hold Released

Re-open Hold Reopened

Override Hold Overridden




None


See the "Hold Tracking Events" section of the 22.0 New Feature Usage and Configuration Guide for more information.

On-Hand Visibility during Order Creation and Processing

This release includes a Populate Current BOH button which is available on the Order Details UI and can be used by both buyer and vendor users to populate current on-hand data for the selected item(s). The Buffer On Hand field under the Order Lines section shows the updated information. When using this feature, buyers can see buyer-side on-hand stock, and vendors can see vendor-side on-hand stock.






None


See the "Populating Current Buffer On Hand" section in the 22.0 New Feature Usage and Configuration Guide for more information.

Disable Change Request Collaboration

This enhancement allows users to set up the system to automatically approve and acknowledge orders while enabling or disabling change request actions. Rather than initiating a lengthy change request process, the system can now keep orders in the Open state and allow for changes to be made, if desired. This enhancement applies to both Purchase Orders and Deployment Orders.

Users can configure Buyer Auto-Approval Policies to one of the following options:

• Accept To New - Orders are set for auto-approval and move from the Draft state to the New state.

• Accept To Open & Allow Change - Any change from the Vendor is auto-accepted, and the order moves to the Open state. The Buyer Change Request (BCR) action is available for buyer users.

• Accept To Open & Disallow Change - Any change from the Vendor is auto-accepted, and the order moves to the Open state. The Buyer Change Request (BCR) action is not available for buyer users.

• Accept To New-Open & Allow Change - Orders are set for auto-approval and move from the Draft state to the New state. Any change from the Vendor is auto-accepted, and the order



moves to the Open state. The Buyer Change Request (BCR) action is available for buyer users.

• Accept To New-Open & Disallow Change - Orders are set for auto-approval and move from the Draft state to the New state. Any change from the Vendor is auto-accepted, and the order moves to the Open state. The Buyer Change Request (BCR) action is not available for buyer users.

Users can set the Vendor Auto-Acknowledgment mode to one of the following options:

• Accept To Open - Renaming of "Fully Accepted." The order is automatically accepted and moves to the Open state.

• Accept To Open & Allow Change - Any change from the Buyer is auto-accepted, and the order moves to the Open state. The Vendor Change Request (VCR) action is available for vendor users.

• Accept To Open & Disallow Change - Any change from the Buyer is auto-accepted, and the order moves to the Open state. The Vendor Change Request (VCR) action is not available for vendor users.

The site-level policies for these options are available under order tabs on the Search Policiesscreen. The policies are called ConsigneeOrderAcceptance and ShipperOrderAcceptance.


Integration Impact Integration actions for BCR and VCR are updated to include the options mentioned above.


None


See the "Disable Change Request Collaboration" section in the 22.0 New Feature Usage and Configuration Guide for more information.



Emergency and Expedite Options for Orders

There are occasions where orders need to be rushed in order to fill a hole in supply or inflated demand. This update includes the Is Expedite and Is Emergency flags on order headers. Checking these boxes denotes that the order needs to be shipped quickly, or that it is an emergency order. Additionally, these flags are available as filters when searching for orders, so vendor users are able to find orders that are of high importance. These fields are applicable to Purchase Orders, Deployment Orders, Return Orders, and Sales Orders.


Integration Impact Integration now supports these flags.


Alert Subscriptions can be made for these flags. See the "Creating Alert Subscriptions" section of the Online Help for more information about creating alerts.


None

Expedite Action for Purchase Orders

With this update, the Purchase Order UI supports the Expedite action. This action is available only to Buyer Supply Chain roles for any order that is not in the Draft, Closed, Cancelled, or Deleted state. Selecting the Expedite action sets the "Needs Expedite" flag, located on the order screen, to "true," as well as creating a Purchase Order Needs Expediting problem on the Problem Workbench.






None


See the "Expediting Purchase Orders" section in the 22.0 New Feature Usage and Configuration Guide for more information.

Links Tab for Associated Requisitions

This update includes a Links tab on the Order Details screens. The tab contains two new sub-panel that show linked requisitions and Requests for Quotation (RFQs). The Requisitions panel shows all requisitions associated with an order. The RFQ panel shows all the RFQs created from requisition lines.




None


None

Partially-Shipped Lines on Purchase Order Search

When searching purchase orders or viewing purchase order portlets, Order Lines Shipped Shortnow include orders which are partially shipped, including the Open, Partially Shipped and In Fulfillment states. This helps users locate more partially-shipped orders easily in the system. The Purchase Order Lines Shipped Short screen is shown below.






None


See the "Viewing Order Exception Reports" section in the Online Help for more information.

Ship to Country and Ship from Country on Purchase Order Reports and Portlets

Two new filters are added to Purchase Order reports and portlets with this release. Ship From Country and Ship To Country are available when filtering these reports and portlets. Entering values in these fields helps users further filter results when searching purchase order-related information in the system.

The following reports and portlets are affected by this update:

Search Reports Exception Reports Portlets

Multi Order Type Schedule Dashboard

Purchase Order Missing ASN Report Purchase Order Schedule Summary

Order Schedule Dashboard Purchase Order Lines Promised Short Report

Purchase Order Summary

Order-Shipment Schedule Dashboard

Purchase Order Lines Shipped Short Report

Purchase Orders Awaiting Approval

Search POs Unreceived Purchase Order Report My New Purchase Orders

Search PO Schedules Late Purchase Orders Report Order Lines Promised Short

PO State Summary Purchase Order Waiting for Shipment Report

Purchase Order Schedules Promised Late

PO Schedule Summary Order Lines Missing ASN

Search Backordered Schedules Orders Waiting For Shipping

Order Hold Report (all from Order Mgmt Menu)

Order Lines Shipped Short

Deployment Order Schedule Dashboard

Projected Late Deliveries

Search DOs Inbound Intransit Purchase Orders



Search Reports Exception Reports Portlets

Search DO Schedules Inbound Purchase Order Summary

DO State Summary

Search SOs

Search SO Schedules

SO State Summary

Search Returns

Returns Schedule Summary

Purchase Order Analytics Report

Deployment Order Analytics Report

As an example, the screenshot below shows the Purchase Order Summary portlet with the Filtersmenu displayed.






None


See the "Purchase Orders" section of the Online Help for more information on searching and viewing purchase orders, order reports, and portlets.

Updated Date Fields for Collaboration

This update includes changes to date-related fields for collaborative orders. The following fields are updated:

Inco Date - Defines what entity owns the order by date.

Minimum Item Expiry Date – Defines the earliest expiration date for an item. Users can request items with the specified expiry date for collaborative orders. Also, buyers can negotiate items with expiry dates.

Buyer and seller users can collaborate and make change requests for these fields. The collaboration process for these dates is active only if the OMS.EnhancedOrderFieldsForCollaboration policy value is set to “IncoDate,MinExpiryDate".


Integration Impact New fields for delivery schedules are as follows:

• Request Inco Date• Promise Inco Date• Request min expiry Date• Promise min expiry Date


None


See the "Updated Date Fields for Collaboration" section in the 22.0 New Feature Usage and Configuration Guide for more information.

Automatically Populate Vendor Item Price Based on Item Mapping

This update allows for the Vendor Item Price of a Spot Purchase Order to be populated automatically, based on a mapped item price (if available in the system). The policy called "Configured Collaborative Fields” (found under the Enhanced Order tab on the Search Policiesscreen) must be set to "UnitPrice" in the system. When the policy is enabled, users do not have to enter prices manually on Spot POs.



4 https://techdocs.elogex.com/display/OHD/.Policies+OMS+v22.0


Integration Impact This policy is supported by Integration.


None


See the "Supply Chain Administration Policies4" section of the Online Help for more information on searching and editing system policies.

Audit Trail on Packing Requirements Screen

Prior to this enhancement, users could edit the Packing Requirements for an order on the Update Order UI, but could not view an audit trail of the changes made. This release implements an Audit Trail option on the Packing Requirements pop-up window. Users can view packing requirement change values, as well as the date and user that made the changes.

https://techdocs.elogex.com/display/OHD/.Policies+OMS+v22.0

https://techdocs.elogex.com/display/OHD/.Policies+OMS+v22.0






None


See the "Viewing an Audit Trail" section of the 22.0 New Feature Usage and Configuration Guide for more information.

Assign To Filter on Order Hold Report

The Assign To filter on the Order Hold Report is updated to allow users to search for First and Lastnames in addition to usernames. This functionality provides for a broader range of names to show up when using the filter on the report.




None


None

Return Order Program Information Updated

With this update, the system is enhanced to propagate Program information to the return order from the underlying purchase order. This enhancement applies to the Generate Return Orderaction from Purchase Orders Details screens as well as the Select Source Order action on the New Return screen.






None


None

Enhanced Bulk Update Operations

This enhancement is an extension of the Bulk Update feature. Users are now able to increase or reduce request quantities on the Bulk Update pop-up window on the Order Schedule Dashboard. This change allows users to update multiple orders in one click. The Request Delivery Date and Request Ship Date fields allow users to select orders for certain dates. Request Quantities can be either Increased or Reduced by a percentage entered by the user (note that only one of these actions can be performed at a time, as increasing and reducing at the same time is illogical). Users can also check the Round Off Request Quantity box, which causes newly-calculated values to round to the closest two decimal points per respective record. By default, this box is checked on the UI when performing the bulk update operation.

Analytics Impact

None

Integration Impact

None


None




See the "Bulk Update" section of the 22.0 New Feature Usage and Configuration Guide for more information.

Redesigned RFQ Explorer

This release includes updates to the Request for Quotation (RFQ) explorer. The UI is enhanced to provide a better-looking, simplified workflow for the user to create and work with RFQs. The top portion of the screen shows the total number of RFQs, plus a breakdown of RFQs by status. Users can click any RFQ link to view more details about the RFQ. The lower portion of the screen lists RFQ by request number. The following items are also included with this update:

• RFQs do not mandate the requested price range.• Users can set ranking factors for RFQ bids. For example, the best-priced product can be

combined with acceptable remaining shelf life and short lead times.• Comments and documents can be attached.• Holds can be added to RFQ contracts.• Item substitution availability.• Editable Service Type field.

The following screenshot shows the new UI.




None


See the "Redesigned RFQ Explorer" section in the 22.0 New Feature Usage and Configuration Guide for more information.



3.9.4 ASN & Shipments

Equipment Type for ASN Creation

With this enhancement, users are able to select the Equipment type while creating an ASN. The Equipment field is available in the header section of Order and ASN screens. This field helps buyer and vendor users better collaborate on shipment methods; vendors can approve or reject orders based on the desired equipment type. If no equipment selection is made, the Trans Modevalue is used.


Integration Impact The Equipment column is available for inbound files related to POs, DOs, SOs, and ASNs.


None


See the "Selecting Equipment Type for ASNs" section in the 22.0 New Feature Usage and Configuration Guide for more information.

Over-shipping Tolerance Validator

This release introduces an Over-shipping Tolerance Validator to ensure that a superfluous amount of an item is not shipped for an order. The purpose of this feature, called PureOvershippingToleranceValidator (Pure OSTV), is to behave like the original OvershippingToleranceValidator (OVST), but to add an additional check. This extra check is to ensure that a new shipment is created using only the over-shipping tolerance value (pure over



shipping). It should enforce the same over-shipping rules that are present for the normal over-shipping validator.

Some examples:

Order Request Quantity = 100Tolerance = 10%Both fail because the ASN quantity (120) is over the Quantity + tolerance (110).

Name PSQ OSTV Result Pure OSTV Result

ASN1 120 Fail Fail

Both fail ASN3 (120 total) because it exceeds the Quantity + tolerance (110). ASN2 is passed by Pure OSTV because it includes some of the original Request Quantity (non-over-shipping amount).


ASN1 55 Pass Pass

ASN2 55 Pass Pass

ASN3 10 Fail Fail

ASN3 is passed by original OSTV because 10 over shipping is allowed. The Pure OSTV fails this because the full request QTY is already consumed by ASN1 + 2. ASN3 is only shipping an over-shipping amount (pure over shipping), so it fails.


ASN1 50 Pass Pass

ASN2 50 Pass Pass

ASN3 10 Pass Fail




None


None



Visibility for Existing ASNs

In previous releases, users were creating new ASNs without realizing that a confirmed ASN already existed for an order. This enhancement shows existing ASNs to users in the Select or Create ASNpop-up. The option to create ASNs is still available, should the user choose to create a new ASN for the order.

The following screens are affected by this enhancement:

• Order Editor screen• Order Search screens• Schedule Search screens• Order Schedule Dashboard




None


None



3.9.5 Procurement Invoice

Manual Invoice Creation Option

With this update, even when the Auto Create Invoice policy flag is set to "True" for orders, users can still create manual invoices as necessary. This is helpful in scenarios where users need to create an invoice for a specific requirement manually. All manually-created invoices are automatically placed on hold upon creation and must be approved by an admin user.




None


See the "Managing Invoicing Policies" section of the Online Help for more information about setting invoicing policies.

3.9.6 UI Changes for Order ScreensThis update includes design changes to all Order screens. Several tabs on order creation and details screens are updated to allow for improved visibility and navigation. Additionally, new icons are available in the system to more closely match color schemes and improve usability. Below is a list of changed common icons and page icons:

• Common Icons - Template, Order Navigator, Manage Field Visibility, Collapse Section, Expand Section, Save, Submit, Add Line(s), Edit Address, Add SAC Code, Refresh, Export CSV (see below for a comparison between the new icons and the retired icons.)

• Page Icons - Generate Order Number, Populate Request Delivery Date, Manage Tabs, Add Line, Get Totals, Equipment Builder, Notes, Add Tracking Event

• Audit History Icon - The appearance of the Audit Icon is enhanced to match the updated Command Center theme. See Command Center section for more information

Desc. Diff. with Prev.Version

Audit Info

Packing Req.

Print Quality Inspeciton Report

Calculate Values

Pull In Forecast

Scale Up

Equip.

Builder

Old Icon

New Icon






None


None

3.9.7 Vendor Performance

Vendor Performance Overrides

In some cases, vendors are not able to meet delivery or shipment dates due to reasons outside of their control (e.g., hazardous weather conditions). This update allows buyers to override shipment or delivery dates on the Order Analytics Details screen. In addition to delivery dates, users can enter the following details from the Order Analytics Details screen:

1. Override Agreed Quantity2. Override Reason Code3. Override Comment

Buyer users can then reload vendor performance data by running an engine from the order analytics report screens. A dynamic filter on the Order Analytics Detail screen can filter all performance records that have an override value as well as any reason code.






None


See the "Overriding Vendor Performance Reports" section in the 22.0 New Feature Usage and Configuration Guide for more information.

3.9.8 Analytics

Analytics Details Report Enhanced to Support Totals

With this update, Order Analytics Detail screens are enhanced to include a total at the end of the report. The Total line shows the sum of all data on the report per column. This line helps users understand the grand totals of many different data measures without having to add the totals manually.






None


None



3.10 Platform

3.10.1 Dynamic Transformations for EDI MessagesThis update includes the addition of a dynamic pre-inbound or post-outbound transformation scheme for any EDI message so that existing system interfaces can be reused. A UI is available so that users can create, edit, and delete transformation schemes. This new framework is plugged into the Platform module and is executed when an EDI message arrives at and is triggered by ONE.


Integration Impact Integration messages now transform based on scripts or classes implemented on the Edi Message Transforms UI.


None



3.10.2 Mobile App for Packing and ReceivingThis release includes a Mobile Application for Packing and Receiving (MAPR) as a companion app for the One Network RTVN application. The app can be used for packing, receiving, and compliance operations in the system.

• The Pack operation is used to scan shipments, packing cartons, and shipment line items to create a packing list. This list is sent to the server and added to the shipment. Any shipper role can be given access to this operation.



• The Shipment Handover Compliance operation is used by the carrier to inspect a shipment before taking possession and ensure that it complies with the shipment hand-off checklist. Any carrier role can be given access to this operation.

• The Receive operation is used to scan received shipments, check shipment items against packing lists, and create receipts. Any buyer role can be given access to this operation.

• The Receiving Handover Compliance operation is used by the buyer to inspect a shipment before taking possession and ensure that it complies with the receiving handover checklist. Any buyer role can be given access to this operation.

The home screen for the application is shown below.




None


Contact the NOC for more information about the MAPR application.

3.10.3 Organization Hierarchy with PermissionsSome customers have a discernible and complex hierarchy of organizations, such as an organization that has several child organizations, who in turn have their own child organizations. Each organization at a higher level can potentially have roles with read/write permissions on any of their child entities. Platform now supports this type of Hierarchical Org permission as a first-class concept in its permissibility framework. These permissions also support multiple organizations at the same hierarchy level (e.g., a Reporting hierarchy, a Financial hierarchy, etc.).






None


None

3.10.4 Support for Org-level EnumerationsThis release includes support for organization-level enumerations. For example, the shipment equipment enumeration should vary by organization, as European-based organizations utilize different equipment than North American-based organizations. Support for this feature includes the following:

1. A new interface for loading org-level dynamic enumeration values is available.2. Existing Dynamic Enumerations UIs now support org-level enumeration values as a

backward compatible.3. A new web action is available for creating enumerations in the system.




None


None



3.11 S&OP

3.11.1 Sandbox Plant Capacity Management Admin UIThis release includes a sandbox Capacity Management UI. The Manage Plan Production Capacity TLV is a timeline view screen that allows capacity manager users to adjust the capacity of plants in their enterprise so that plans can be made using the new capacities. Users can edit Override Capacity and Plant Recurring Capacity for each Total Plant Capacity for a resource.




None


See the "Managing Plant Capacity" section of the 22.0 New Feature Usage and Configuration Guide for more information.

3.11.2 Support for Capacity Type on Capacity Management UIsWith this release, Capacity Type is available as a filter and data measure for all Capacity Management UIs. Users can choose between Operational Capacity (recurring + override capacity) and Contracted Capacity as a reference for comparing capacity against demand. The table below explains the difference between operational and contracted capacities for different data measures.



Data Measure Operational Capacity Contracted Capacity Equivalent

Weekday Sum (Recurring + Override) from Monday through Friday

Contracted Capacity

6-day Sum (Recurring + Override) from Monday through Saturday

Contracted Capacity + Flex Limit Upper Bound

7-day Sum (Recurring + Override) from Monday through Sunday

Contracted Capacity + Flex Limit Upper Bound




None


None



3.12 SCPT

3.12.1 Incoterms Fields on Search Shipment Lines ReportThis enhancement adds the Inco Term and Inco Terms Location fields to the Search Shipment Lines report. The screenshot below shows the columns on the report.




None


None

3.12.2 Multiple Sites with Different Time Zones on TLVsWith this update, Timeline Views (TLVs) now support multiple sites with different time zones on a single TLV screen. Each site's data is in its time zone, rather than a common timezone for the whole TLV. This helps avoid confusion when dealing with sites in different time zones.




None




None



3.13 Warehouse Management

3.13.1 Additional Filters for WMS Reports and PortletsThis update adds filters for Product Group Level and Site Group Level to some Warehouse Management reports and portlets. These fields help users further filter search results when running searches for group data. The screenshot below provides an example of the filters for an Inventory Analysis report.

The following reports and portlets are affected by this change:

• Issue Inventory• Pick Lists• Receipts• Packing Lists• Putaway Lists• Inventory Move Order• Inventory discrepancy• Cycle Count• Move Plans• Location Inventory• LPNs• Inventory Operations• Inventory Aging• Aggregate Inventory Report• Warehouse Workload Details• Warehouse Capacity Summary• Issue Inventory Summary• Inventory Analysis Report



• Inventory Status Report• Consumption Analysis Report• Singleton -> Singletons (WMS report)• Inventory Pins• Component Usage Report• Kits• Inventory By Person Report• Buffer BOH Adjustment Report• Search Logical Inventory Policy• Add Site Group Level filter to Warehouse Explorer (right-hand tab) and following reports:

• Inventory Aging• Inventory Analysis Report• Consumption Analysis Report• Singleton -> Singletons (WMS report)

• Kits• Inventory By Person Report• Buffer BOH Adjustment Report• Search Logical Inventory Policy




None


None

3.13.2 Auto-move Packing List to Ready To Ship State Once Related Pick List is Closed

With this update, when the "Auto Ready To Ship" packing policy is on, the system now automatically moves packing lists to the "Ready To Ship" state after the related pick list is closed, and the packing list is in the "Awaiting" state. This update removes the necessity for users to manually advance shipment states based on checking the status of the pick list. The enterprise admin can set this policy on the Packing tab of the Search Policies UI.






None


None

3.13.3 Available Inventory for Expired LotWith this update, a policy is available that can automatically move inventory from the "Available" to "Expired" state when the expiration date of the inventory has passed. The Auto Update Inventory Status When Expired policy can be set by the user on the Search Policies UI. When this policy is set, the system will not suggest expired inventory to be picked for orders. The location of the policy on the Lot tab is seen in the screenshot below.






None


See the "Searching Policies" section of the Online Help for more information on searching and editing policies.

3.13.4 Batch No Field on WMS ReportsWith this update, the Batch No field and filter is available following reports:

• Issue Inventory• Pick Lists• Receipts• Packing Lists• Putaway Lists• Inventory Move Order• Inventory Discrepancy• Cycle Count• Move Plans• Location Inventory• Inventory Operations

• Inventory Aging• Aggregate Inventory Report• Issue Inventory Summary• Issue Analysis Report• Consumption Analysis Report• Component Usage Report• Kits• Lots• Inventory By Person Report

This field helps users understand which batch certain inventory attributes belong to.






None


None

3.13.5 Bill of Materials ReconfigurationSingletons or kits are compiled based on a user-selected bill of materials. Bills of Materials (BOMs) can be modified at the user's discretion at any time - a process called reconfiguration. With this update, the system provides the following capabilities:

• Users can define a set of Serial Numbers or Lot Numbers with exact Lot Instances and a select a target BOM to reconfigure.

• The system automatically removes items that are not a part of the new BOM.• The system automatically adds items to the current assembly/kit to comply with the target

BOM.






None


See the "Bill of Materials Reconfiguration" section of the 22.0 New Feature Usage and Configuration Guide for more information.

3.13.6 Enhancements to Shipment Fact ReportThis release introduces two new fields to the Shipment Fact report in the Warehouse Management system. The newly added fields are Penalties Cost and Penalties Cost UOM. Penalties are part of a Site Accessorial Cost measure on the Shipment Fact. It applies to the Carrier Partner and Supplier Partner. Every site has a compliance check with the shipment. Any shipment that violates the compliance check incurs a penalty. The Shipment Fact report shows the penalty cost and the UOM (Unit of measurement) associated with the penalty.






None


See the "Penalties in Shipment Fact Report" section in the 22.0 New Feature Usage and Configuration Guide for more information.

3.13.7 Expiration Date on Packing ListThis update includes enhancements to printed packing lists. The Expiry Date field, which is available when viewing packing list details in the UI, is now populated when printing a packing list as a PDF. An example PDF is shown below.






None


See the "Searching Packing Lists" section of the Online Help for more information about viewing and printing packing lists.

3.13.8 Expiry Date Filter for WMS ReportsWith this update, the Expiry Date filter is available on the following WMS report screens:

• Inventory Summary Report• Inventory Aging Report• Warehouse On Hand Report

Additionally, the Expiry Date field is available on the following screens:

• Issue inventory• Pick Lists• Packing Lists• Receipts• Putaway Lists• Inventory Move Orders• Cycle Counts• Inventory Discrepancies



This field helps users acquire information about the expiration of inventory in their systems.




None


None

3.13.9 Inventory Aging Report – Alert Subscription and PortletThis update improves inventory visibility with the Item Expire Soon Summary portlet and report. This report shows a summary of items located at specific sites which are expiring within a specified time frame or a particular date.

The following fields are available on the portlet:

• Item• Item Description• Organization• Site• Site Description• Generic Item• Generic Item Description• Qty• Qty UOM

Additionally, an Alert Subscription for items expiring soon is available for subscription. Users can set up a notification, based on items expiring within a specific time frame.






None


See the "Configuring an Inventory Aging Alert Subscription" section of the 22.0 New Feature Usage and Configuration Guide for more information.

3.13.10 Lot Expiry Date on Cycle Count LineWith this update, the Lot Expiry Date field is available on cycle count line details right after the Lotfield. Additionally, the Lot Expiry Date column now appears on the Inventory picker on the cycle count line. This read-only field is automatically populated using the expiration dates for selected lots.




None


None



3.13.11 Lot Instance Inventory TrackingThis update allows Lots to be split into Lot Instances and tracked as separate distinguishable inventory attributes. This release updates the Lot inventory management policy, allowing it to model Lot Instances as a singleton option; admin users can set this policy on the Inventory Management Policy screen. The Lot Split Inventory operation is available on the Location Inventory report. Users can cancel this inventory operation if any error is made.




None


See the "Lot Split Inventory" section of the 22.0 New Feature Usage and Configuration Guide for more information.

3.13.12 Multiple BOMs for the Same Serial-controlled ItemWith this enhancement, the system allows for multiple configurations for the same serial-controlled item. With this change, users can now select an item configuration (bill of materials) during the work order creation process. There are some cases where multiple configurations (expressed as bill-of-material entities) can exist for the same item (kit or assembly) within the same or overlapping date ranges. For example, a camera kit (with a specific SKU) can be configured differently depending on the context – requirements, location, etc. The camera kit can have additional or fewer items depending on the project requirements. Actual assembly and kitting processes must use the components according to the selected bill of materials. The following screenshot shows multiple BOMs for the same item; the first BOM created is marked as primary by default.



Analytics Impact

None

Integration Impact

None


None


See the "Creating BOMs" section in the Online Help for more information.

3.13.13 Multiple Stocking UOMsWith this update, users can provide the stocking unit of measure (UOM) on receipts that are different than the default value from the Buffer Stocking UOM. The system can now track UOMs as a user-distinguishable attribute, allowing the same inventory items to exist with multiple units of measure. This is useful for items that can come in packs of 6, 12, 20, and so on.




None




None

3.13.14 Notification Alert on Cycle CountWith this enhancement, users can subscribe to an Alert Subscription for Planned Date Changes to Cycle Counts. This alert can be set up in the same manner as all other alerts and notifies users of any planned date changes in regards to cycle counts. The screenshot below shows the Categoryand Alert Type fields set up for this specific alert.




None


See the "Creating an Alert Subscription" section in the Online Help for more information.

3.13.15 Printing Pick Lists as PDFsWith this update, Pick Lists can be printed as PDFs using a button on the Pick Lists UI. Users can then take printed pick lists into the warehouse to perform manual picking operations.






None


See the "Printing Pick Lists in PDF Format" section in the 22.0 New Feature Usage and Configuration Guide for more information.

3.13.16 Reason Reject Code for Rejected QuantityWith this enhancement, users can supply a Reason Reject Code when inputting a Reject Quantityon a receipt line. The Reason Reject Code is useful for determining why a line was rejected upon receipt so that the cause of errors can be more easily found. Additionally, Alert Subscriptions now support rejected quantities for receipts. Users can subscribe to these alerts to receive notifications about rejected inventory.






None


• See the "Creating Alert Subscriptions" section in the Online Help for more information about subscribing to alerts.

• Additionally, see the "Updating Receipts" section in the Online Help for more information about accepting receipts.

3.13.17 Ship From Site/Ship From Address/Ext Ship From Site on Packing List

With this update, the following fields are captured upon creation of a packing list:

• Ship From Site• Ship From Address• Ext Ship From Site

These fields are important in helping users understand where a packing list originated.




None




None

3.13.18 UI Enhancements for WMSVarious WMS screens include visual enhancements as part of this release. None of these enhancements impact existing workflows or functionalities. These enhancements are part of a global Command Center Enhancement.




See the "Command Center UI/UX Enhancements" section in these release notes for more information on specific UI/UX changes.


None

3.13.19 Usage Rule for Items on Receipts and Pick ListsWith this update, the Usage Rule column is available for Receipt lines and Pick List lines. This column displays the Warehouse Item Usage Rule (e.g., FIFO, FEFO, SLED, etc.) for individual items if there is not a specific Item Usage Rule for the site searched in the report.






None


None


Bug Fixes – 155

4 Bug FixesThis section contains all bug fixes implemented as part of the 22.0 release and are common to all of RTVN. Customer-specific bug fixes can be found in JIRA with a Fix Version of 22.0.


Bug Fixes – 156

4.1 Logistics Bug Fixes

4.1.1 Array Exception for Batch Confirm Action – PDS-12167

Problem: After executing the "Batch Confirmed" action on two shipments, the Success message was not displaying, and shipments were not moving to the confirmed state.

Cause: The action was failing due to an "Index: 0, Size: 0" error in the database.

Resolution: A database fix is applied, allowing the shipments to transition to the correct states.

4.1.2 Auto-approval Missing Hold due to Currency Mismatch – PDS-12410

Problem: Shipments with a total cost different than CAD (Canadian Dollars) should have been generating holds due to UOM mismatch; however, holds were not being applied, and invoices were being automatically approved.

Cause: This issue was caused by a logic error in the system.

Resolution: The code is updated to check for differentiation in UOM when dealing with CAD.

4.1.3 Blank Reports – PDS-12052

Problem: Some reports in the Reports tab were showing up blank and did not contain any data or information. The reports worked if the picker tool was used to select the Carrier filter, but did not work when auto-complete was used for that filter.

Cause: There was an issue with the auto-complete feature for the two reports. A third report was being made visible when it should not have been an option in the menu. Additionally, there were few reports which did not contain any data.

Resolution: Edited auto-complete function for the Carrier filter and visibility option for user-specific reports. Removed legacy reports.


Bug Fixes – 157

4.1.4 BOL/AWB Number not Set on Shipment After Processing EDI 301 – PDS-11228 / LS-35648

Problem: When generating a tender plan on a multi-modal shipment, the "BOL/AWB No" was not being set on the shipment after processing the EDI 301 message.

Cause: The system was not capturing the BOL/AWB number when processing the EDI message.

Resolution: The system has been updated to capture the correct information from the EDI message.

4.1.5 Broken Filters on Planner Report – PDS-12762

Problem: On the Planner Report, a wildcard search for Origin and Destination Cities and Origin and Destination Sites did not work; exact information was required in order to show results.

Cause: Support for wildcard searches was not available for OriginSite, DestinationSite, OriginCity, or DestinationCity.

Resolution: Wildcard support has been added for the filters listed above.

4.1.6 Broken Validation for Pickup and Delivery Dates – PDS-11954

Problem: When trying to derive the delivery date for a shipment based on the pickup date, the system was displaying an error message regarding a missing pickup date, even when the information was present.

Cause: The system was throwing an error because the Pickup Date was before the Delivery Date and transit time policy was not able to calculate the delivery date correctly.

Resolution: The system has been updated to calculate the transit time based on pickup date.

4.1.7 Cancel Movement and Execution Windows Showing Different Enumerations – PDS-12602

Problem: The Cancel Execution and Cancel Movement pop-up windows were showing different strings of text than the strings used in regular models.

Cause: A javascript error was causing different enumerations to appear.

Resolution: A javascript fix has been applied to the above-mentioned actions.


Bug Fixes – 158

4.1.8 Creation Date and Event Date in Different Formats in Shipment Tracking Event Outbound – PDS-11920

Problem: The date formats for Event Date and Creation Date were different in the TMS Shipment tracking event outbound interface.

Cause: The CSV template was set up incorrectly, so the dates were displayed in a different format.

Resolution: The template has been fixed to display both dates correctly.

4.1.9 Customer can Deactivate and Update Enterprise on Partnership Entry – LN-45574 / PDS-11938

Problem: When users attempted to add a partnership and searched for a company, the Enterprise link incorrectly took them to the General tab where options could be changed for the enterprise, and Deactivate button was available.

Cause: The Deactivate and Update buttons were appearing even though they did not perform any function on the UI.

Resolution: Users are now not allowed to save or deactivate partners when adding Partnerships as both buttons are not available.

4.1.10 Deactivated Partner Profile Still Found SaveToConfirmed Via Integration – PDS-13282

Problem: When the SaveToConfirmed was being sent to the system using Integration, the profile name found for the carrier was being applied, even if the carrier was not active.

Cause: The system was not checking whether or not a carrier was active.

Resolution: The system does not allow the confirmation of a movement to a specific carrier if the given carrier profile is inactive.

4.1.11 Enterprise Slice/Data Warehouse DB not Seeing Partner Organizations - LN-46855

Problem: New partner enterprises were sometimes not completely replicated into the enterprise slice.

Cause: This was an internal database issue.


Bug Fixes – 159

Resolution: The issue has been corrected internally.

4.1.12 Fuel Index Rate Showing Two Decimal Places — PDS-14406

Problem: When viewing the fuel index rates, the system was showing two decimals value places instead of three.

Cause: When the accessorial rate is re-calculated due to the moving index change, the description had the rate to store as 2-decimals.

Resolution: The system reads the accessorial rates, calculates them and constructs the cost description to the correct decimal value based on the data stored in the database.

4.1.13 Movement Link Persists on Canceled Invoice Lines – PDS-11831

Problem: When a carrier canceled an invoice line, the movement link on that line remained. This created an issue when the canceled line referenced the invalid move number.

Cause: Holds for multiple invoices were working incorrectly. Multiple holds were taking invoices into consideration which were in the canceled and rejected states.

Resolution: Removed movement reference for canceled invoice lines. Only the movement whose corresponding invoice line is approved is getting displayed on filter "Carrier Invoice Status= Approved" when applied.

4.1.14 Multiple Operating Cost link Appearing when Currency and Operating Costs are the Same – PDS-14198

Problem: The system is expected to display multiple links in the operating cost column when there is an operating cost present with multiple UOM. Otherwise, when the Currency and Operating Cost are the same UOM, the link should not appear.

Cause: An error in the system code was causing the link to appear when generating the same Currency on Cost and Operating Cost.

Resolution: The system is updated to show multiple links only if an operating cost is present with various UOMs.


Bug Fixes – 160

4.1.15 Newly Created Favorites not Working – PDS-12607

Problem: Multiple users were receiving an "Unsupported Operation" error message when trying to view newly-saved favorites that were recently created from a filtered shipment report screen.

Cause: The system was throwing a java error and trying to change immutable calendar values in system logs.

Resolution: The error has been corrected so that favorites are working correctly.

4.1.16 Picker and AutoComplete not Supported on Origin Site and Destination Site Screens – PDS-13962

Problem: Users were not able to select values for the Origin Site and Destination Site fields using the picker tool and auto-complete feature across all the shipment report screens.

Cause: The code was not designed to allow the Origin Site and Destination Site fields to use the picker and auto-complete functionality.

Resolution: The program code has been updated to use picker and auto-complete features on the Origin Site and Destination Site fields.

4.1.17 Outbound Shipment Message Not Generated – PDS-12379

Problem: Some users noticed that the system was not generating a shipment outbound message when creating and confirming a shipment.

Cause: A system error was occurring, preventing the system from generating the outbound file.

Resolution: The system error has been corrected; allowing for the generation of outbound messages for shipment confirmation.

4.1.18 Out Of Memory Issue – PDS-14464

Problem: Some users noticed an error due to the system being low on memory.

Cause: A listener in the system was taking up too much memory and causing errors to occur.

Resolution: The system now supports chunk-based processing of data to limit the memory use and improve performance.


Bug Fixes – 161

4.1.19 Permissions-restricted Roles Allowed to Perform Actions – LN-46174 / PDS-12911

Problem: Some user noticed that permission-restricted roles were allowing unauthorized actions to be carried out. This was happening with both existing roles and newly-created roles.

Cause: Multiple issues were causing this bug:

• Actions were executed and failed with the correct exception, but the system was showing a success message instead.

• Unauthorized buttons were not disabled on appointment screens.• Links to appointment screens were not hidden.

Resolution: The above errors have been corrected and implemented in the system.

4.1.20 Spot Bid Rejected Alert to All Carriers – PDS-13399

Problem: After accepting a spot bid for a tender, a rejection alert was being sent to all carriers, regardless of whether or not they submitted a bid.

Cause: A coding error was causing alerts to be generated for all carriers.

Resolution: The code has been fixed to only send rejection alerts to carriers who submitted bids.

4.1.21 Remove Trailing or Leading Space from Site or Partner Site Name – PDS-13178

Problem: Users were able to add spaces before or after a Site or Partner Site name, and the system would keep the spaces, causing issues when searching for sites.

Cause: The system was not set up to remove leading or trailing spaces from site names.

Resolution: The system has been updated to remove leading or trailing spaces from site names.

4.1.22 Required Field not Marked in Accessorial Pop-up – LN-46114 / PDS-12763

Problem: When adding an additional accessorial charge, the Select Partner field did show an asterisk next to it, meaning it was a required field.

Cause: A design error omitted the asterisk next to the Select Partner field.

Resolution: The system is updated to show an asterisk for the required field.


Bug Fixes – 162

4.1.23 Route Showing Expired Rates for a Carrier – LN-45527

Problem: When adding a carrier to a routing guide, an expired rate was pulling through into the routing guide.

Cause: The system was not designed to select the correct route when adding a carrier to a routing guide.

Resolution: While adding/updating Individual Carriers on the Route Details screen, per the system date, the most relevant route is used as the base rate (e.g., current route or nearest future route.

4.1.24 Shipment and Movement State Mismatch on Movement Upload – PDS-13992

Problem: Some users observed that, if a shipment was confirmed and movement was uploaded through the UI, the movement was assigned Tendered state by the system instead of a Confirmed state. So, the shipment and movement were in different states.

Cause: The program logic was causing the issue of a state mismatch.

Resolution: The program logic has been updated to resolve the state mismatch issue between a shipment and movement.

4.1.25 Shipments in Continuous Move Disappearing – PDS-13876

Problem: Some users observed that, if a shipment was put on the Continuous Move option, then it didn't appear in the search results.

Cause: The issue in the program code was causing the shipment to be omitted from search results.

Resolution: The program code has been updated to resolve the issue.

4.1.26 Site Scheduling Policies Report not Showing all Settings – LN-45565 / PDS-11965

Problem: Some users noticed that they were unable to view anything that confirmed that Combined Appointments were enabled, or anything for the auto-schedule policy, even though they were set up earlier.

Cause: The Site Scheduling Policies report had not been updated to search for and include changes made in the previous release.


Bug Fixes – 163

Resolution: Added policy information for support of Multi-Appointment and Combined Appointment scheduling. The system now also obtains Auto-scheduling policy information correctly.

4.1.27 System is Allowing Parent Shipment to Close when Legs are not Closed – PDS-12573

Problem: Some users noticed that parent shipments could be closed when only some associated legs were being closed. The parent shipment should have been closing only when all legs were closed.

Cause: A coding error was not checking for open shipment legs and not throwing an error message.

Resolution: The system has been updated to display a warning message when trying to close a shipment with active legs.

4.1.28 System Should Not Allow To Create Shipment With Leading or Trailing Space – PDS-14364

Problem: The system was not permitting users to update or create shipments due to trailing space issue.

Cause: The system was ignoring the leading spaces for shipments, so it was throwing an error trying to load shipment numbers without spaces.

Resolution: While creating the shipment, the shipment number's leading or trailing space is now no longer considered.

4.1.29 Tender Plan History Missing Timestamp and Changed By User Details – PDS-12278

Problem: Some users noticed that upon reviewing the Tender Plan History report, it was missing two critical components: Timestamp and Changed By user name.

Cause: The correct data table was not being searched for this report.

Resolution: The correct data table is now aligned with this report to show all critical components.

4.1.30 Unable to Open Parent Shipment in Closed State – PDS-14102

Problem: Some users noticed that the error message was showing when trying to reopen a parent shipment in the Closed state.


Bug Fixes – 164

Cause: The program code has an internal bug which was causing the error.

Resolution: The program code has been updated to allow users to reopen a parent shipment in the Closed state.

4.1.31 Unable to Resize Calendar on the Appointment Scheduling Screen – LN-46241/ PDS-12964

Problem: Some users noticed that they could not resize the calendar to full screen on the Appointment Scheduling screen.

Cause: The "maximize" button was not showing due to a small design error.

Resolution: The design error has been corrected to show the "maximize" button.


Bug Fixes – 165

4.2 Order Management (OMS) Bug Fixes

4.2.1 Add Order Pop-up does not Disappear once the Order Line is Added – PDS-14285

Problem: Add Order pop-up does not Disappear upon adding the Order Line.

Cause: There was an internal error in the code that caused the add order pop-up box to appear on the screen once the order line is added.

Resolution: The program code has been updated so that the add order pop-up box disappears once the order line is added.

4.2.2 Applying Holds to Orders – PDS-11848

Problem: Some users noticed that adding an hold to an order and updating was causing the hold to close.

Cause: A prior enhancement related to hold validation was causing the system to automatically close holds on manually-updated orders.

Resolution: Code in the system has been fixed in order to keep holds open when manually updating an order.

4.2.3 Deployment Order in New State Although Error is Set – PDS-14208

Problem: The system does not roll back the transaction if auto-promise or auto-approve fails for deployment order in the new state.

Cause: The system allowed the user to create Deployment Order with the same Ship TO and Ship From site through integration CSV files.

Resolution: The system has been updated to process only the related files, and if the files do not match, the system displays the appropriate error on the screen.

4.2.4 Document Disappearing and Reappearing – PDS-12309

Problem: When uploading a document with the same name under both the Notes and Attachments and Documents sections of a purchase order, the document was disappearing from the Documents tab and then reappearing on the Notes and Attachments tab.


Bug Fixes – 166

Cause: Attachments and Documents were running under the same model in the system, causing documents to only appear once on the UI, as dual documents were not allowed under the model.

Resolution: Users can now no longer enter the same file name on both tabs, as an error message appears prompting a new name for one of the documents.

4.2.5 Event Category Filter Disabled – PDS-12297

Problem: The Event Category filter was improperly disabled for the two reports:

• OMS.TrackingEventsReport• OMS.EnhancedOrdersEventTypesVisibility

Cause: The event category filter was inadvertently disabled on the UI for these reports.

Resolution: The reports have been modified to provide a functional event category filter.

4.2.6 Order Hold Report Cannot be Saved as Favorite – PDS-12149

Problem: Some users noticed that the Order Hold Report was not able to be saved when a Model name was added to the report.

Cause: A coding issue was causing the report to error on save when it contained a value for the Model name field.

Resolution: The code has been refactored to accept a Model name, and the report can now be saved and viewed as a favorite.

4.2.7 Order Update Alert not Working via Integration Action – PDS-11799

Problem: Some users noticed that an Order Update alert was not triggering from the OMS.CreateOrUpdateFromInteg action.

Cause: A code issue was preventing the OMS.CreateOrUpdateFromIntegaction from triggering the order update alert.

Resolution: The code has been updated so that the integration action also triggers the alert successfully.


Bug Fixes – 167

4.2.8 Ship To Site not Properly Verified on Purchase Order Synch Inbound – PDS-11306

Problem: The system displayed an error message while uploading "Ship To Site" Purchase Order inbound files.

Cause: The "ShipToSite" and "ShipFromSite" fields were not validated to their associated Enterprise/Organization fields due to an error in the coding.

Resolution: The system has been updated to refer to the proper associated Enterprise/Organization fields while creating orders using the inbound files.

4.2.9 Unable to Update Purchase Orders in New State on Inbound – PDS-13963

Problem: Purchase Order inbound files were failing with a Schedule error while trying to update the Ship From Site information on existing orders. Users would see an error message when submitting the inbound files.

Cause: The Ship From Site field was not aligned with the other fields to accept changes via inbound files, causing an error message to appear.

Resolution: The Ship From Site field processing has been updated to accept changes up to the Open state.

4.2.10 URL in New Note Alert Does not Direct User to the Order – PDS-10545

Problem: When the user received a new Note alert notification, when clicking on the order number link in the email, it did not direct the user to the order.

Cause: The callback that is responsible for the order link in the Note Added alert was providing a dead system inbox link.

Resolution: The callback has been fixed to properly link the alert to the order.


Bug Fixes – 168

4.3 Optimization Bug Fixes

4.3.1 Duplicate Item Policy in RPL – PDS-12433

Problem: When running the Order Aggregation Engine for the same item with a different program, it was trying to generate and combined two orders into one and was failing with a duplicate line reason error message.

Cause: The engine did not contain logic to address this particular situation.

Resolution: A new validator that supports the notion of checking for both unique item and program has been implemented so that the Order Aggregation engine can create orders successfully.

4.3.2 IP Results Issues – PDS-14390

Problem:

Cause: Explain the cause of the problem here.

Resolution: Explain the resolution of the problem here.

4.3.3 Load Builder Engine Query not Checking Active Flag of AVL – PDS-10330

Problem: When running the Load Builder Engine for Deployment Orders, the system was not checking to see if the selected AVLs were active or not.

Cause: There was no system check to confirm that AVLs were active when running the load builder.

Resolution: The "is_active" check has been added to the java query when selecting AVL lines.

4.3.4 Potential Lost Sales Report Cannot Select Multiple Stores – PDS-12404

Problem: Users were unable to select more than one store when using the Potential Lost Sales report. This led to a lengthy process when trying to compile data from multiple stores.

Cause: The report was not set up to accept site groups as a query.

Resolution: The Site Group filter is now available on the Potential Lost Sales report.


Bug Fixes – 169

4.4 Platform (PLT) Bug Fixes

4.4.1 CSV Header and Content Displayed in the Incorrect Language - PLT-16370

Problem: Downloaded CSVs were not rendering column headers or enumeration values in the user's preferred locale/language.

Cause: An oversight in the CSV export logic caused this issue.

Resolution: The code has been updated to allow column titles and enumeration values to reflect the user's selected locale/language.

4.4.2 Enhance Computation Measure on Date Difference - PLT-16308

Problem: Some users noticed that computed columns in Reports did not support numerical difference between two date and/or timestamp fields.

Cause: Computations for date and timestamp differences was not a supported feature.

Resolution: Two functions have been added to the system:

• date_to_millils (date) - Converts dates to milliseconds• millis_to_date (long) - Convert milliseconds to dates

4.4.3 EPT-level Permission by Policy - PLT-17025

Problem: A runtime error was encountered when evaluating a custom permission policy defined on a model in the EPT.

Cause: The logic which looks up custom permission policies was considering only module-level policies and was not using the EPT classloader.

Resolution: The EPT classloader is now consulted when evaluating custom permission policies.

4.4.4 Jasper Command Center Reports Not Showing the Corresponding Parent Folder Names – PLT-16929

Problem: Jasper reports were not correctly showing the corresponding parent folder names in Command Center.


Bug Fixes – 170

Cause: The Command Center UI was not designed to display the parent folder name properly for Jasper reports.

Resolution: The system has been updated to show the proper folder names.

4.4.5 New SFTP Destination Should Use JSCH - PLT-17216

Problem: When a user creates a new SFTP destination in their integration subscription, it should automatically set to use JSCH to take advantage of the latest SSH encryption protocols.

Cause: The system was not set up to us JSCH to handle these integration subscriptions.

Resolution: The Integration Subscription UI has been changed to always use the JSCH library, and integration documentation has been updated.

4.4.6 Receiving Calendar Headers - PLT-17036

Problem: The Calendar screen for Dock Door Groups was showing overlapping text on the Dry Door header tab.

Cause: The UI had a design error regarding dates that caused long strings of text to overlap.

Resolution: Dates and related labels have been edited so that they do not overlap on the UI.

4.4.7 Support Async Export of Reports - PLT-16409

Problem: Some users were experiencing a timeout when exporting shipment reports in the system.

Cause: The system was not set up to support asynchronous exports.

Resolution: The system has been enhanced to initiate all exports asynchronously – this allows the user to continue other work while the export runs, and get the result in an Exports page after the fact. (Exports which take only a few seconds are immediately available without leaving the current page.)


Bug Fixes – 171

4.5 SCPT Bug Fixes

4.5.1 Categories in New Report Subscription and New Integration Subscription not in Sync – PDS-12308

Problem: Users noticed that the category options were different when viewing the New Report Subscription screen and the New Integration Subscription screen.

Cause: The two screens were pulling category options from different locations.

Resolution: The system is now coded to pull the category options from the same source.

4.5.2 Error Generating Return Order from Receipt Screen – PDS-12389

Problem: When generating a return order from a completed receipt, users were encountering an error stating "Return Order Template Policy".

Cause: A hard-coded value was causing a javascript error which lead to this issue.

Resolution: The javascript has been edited to accept parameters instead of using a hard-coded value.

4.5.3 Outbound Shipment Summary Portlet Performance Issues – PDS-14652

Problem: Some users noticed an increase in portlet loading time or portlet loading timeout, resulting in reduced overall system performance.

Cause: Some users removed the Creation Date filter value for Inbound and Outbound Shipment Summary portlets because the Creation Date filter was not mandatory. This meant that a substantial number of records were loaded into the portlet, impacting the performance of the system.

Resolution: The Creation Date filter for Inbound and Outbound Shipments Summary portlets is now a mandatory filter.

Users with Buyer Supply Chain Planner and Vendor Supply Chain Planner-derived role types, who saved their preferences without the Creation Date filter will receive an error “Creation Date is required” for these portlets during dashboard loading. To resolve the error mentioned above, users must provide Creation Date filter values (these can be set as relative or static dates) and save preferences or reset the portlet so default date range will be applied starting from next dashboard loading.

NOTE:Resetting the portlet removes all filters from preferences, not just the Creation Date filter.


Bug Fixes – 172


Bug Fixes – 173

4.6 Supply Chain Core Bug Fixes

4.6.1 Administer Roles Organization Spelling – SCC-4083

Problem: The Administer Roles UI was showing a field name of "Organisation" instead of "Organization".

Cause: This was a spelling error in the UI design.

Resolution: The error has been corrected and the field correctly reads as "Organization".

4.6.2 Alerts not Working – SCC-4049

Problem: Some users noticed that Hold alerts were not being generated for shipments.

Cause: There were hard-coded values in the system that should have been generic so that the system could generate hold alerts properly.

Resolution: Commented and hard-coded strings were removed from the code so that the system can properly create hold alerts.

4.6.3 Change Partner Carrier for Static Routes – SCC-4176

Problem: Some users noticed that the system did not allow them to change the Partner Carrier for a Static Route once the Static Route was created.

Cause: The Copy functionality via the list view action did not allow users to change the carrier.

Resolution: Changes were made in the Copy Static Route view javascript file to allow modification of the carrier partner value.

4.6.4 Duplicate Route Error Message Inconsistency – SCC-4187

Problem: The system did not allow users to change the Partner Carrier for a Static Route once the Static Route was created.

Cause: An error occurred in the system where the route number was being considered a duplicate and throwing a system error that was not end-user friendly.

Resolution: The proper error message has been applied for the end user to address duplicate routes.


Bug Fixes – 174

4.6.5 New Alert Subscription Page not Loading for Transportation Manager Role – SCC-4036

Problem: When TransMgr roles were attempting to view the New Alert Subscription screen, it was not loading and showing the error message "The page you requested could not be loaded. This may be due to a temporary connectivity issue."

Cause: A javascript error was causing loading issues for this screen.

Resolution: A fix has been applied so that the screen loads correctly for this user and role type.


Bug Fixes – 175

4.7 Warehouse Management Bug Fixes

4.7.1 Alert for Percentage Rejected Quantity Tolerance not Getting Generated – PDS-14124

Problem: Some users noticed that alerts for Pct Rejected Quantity Tolerance were not being generated in the system.

Cause: The system logic contained some error in alert age tolerance.

Resolution: Logic has been updated so that alerts can be properly issued.

4.7.2 Alert Notification Does not Contain Message Details – PDS-14068

Problem: The alert notification messages were not showing any message details about the upcoming cycle count and cycle count subscription.

Cause: The Alert Inbox message and Email Notification should contain upcoming Cycle Count due date and information about the Cycle Count subscription. Due to issues in the program code, the messages were blank.

Resolution: The program code has been updated so that the alert notification contains the required information about cycle count.

4.7.3 Error in Requisition Activity and Distribution Report – PDS-14123

Problem: Some users noticed that the received quantity and distribution report related qty is not getting updated as expected,

Cause: Due to lack of time zone support in current buffer analytics, it's not possible to correctly assemble data for Requisition Activity and Distribution report.

Resolution: Added time zone support to the buffer analytics engine. The time zone -aware analytics will be implemented as a separate analytics engine, with its own fact model:SCPT.RequisitionActivity.

The report will be updated to point to the new fact model and will use DateTime computations in the context of respective site time zones.


Bug Fixes – 176

4.7.4 Error on Closing Partial Receipt – PDS-14512

Problem: Some users noticed that, when closing a partial receipt, a "failed to update" error message was being displayed.

Cause: Due to a missing permission, the system failed to write the surrounding database transaction files.

Resolution: Added the missing permission to the system in order to properly write database transaction files.

4.7.5 Expiry Date Populated on PDF but not on Picklist Detail Screen – PDS-13998

Problem: On the Picklist Detail screen, only Lot and Lot Expiry Date information was present; the Expiry Date field was blank. However, when printing to PDF, the Expiry Date was showing data as well.

Cause: The system was printing the expiry dates for lots and singletons related to a line, even though the pick line expiry information was not present.

Resolution: The system has been updated to not print expiry dates of singletons or lots if the pick line's expiry date is empty.

4.7.6 Inventory Operation in Packed State – PDS-12659

Problem: Users noticed that the Consume and Adjust actions were incorrectly available for inventory in the Packed state.

Cause: The system was not set up to limit the actions available for inventory in this state.

Resolution: The system has been enhanced to limit the actions available to packed inventory.

4.7.7 Picker Report for Customer Partner Showing Partnerships of Other Organizations – PDS-13997

Problem: Some users noticed that on the Reject Quantity Alert, the Picker report for customer partners was also showing partnerships of other organizations.

Cause: An SQL error was causing other partnerships to appear when running the report.

Resolution: The SQL has been fixed as to only show proper partnerships on the report.


Bug Fixes – 177

4.7.8 Pick List and Receipt Reports Order No Filter not Working – PDS-13498

Problem: When searching the Pick List/Receipt Lists Report on Order No, all data was showing instead of only the data related to the Order No that was populated in the filters.

Cause: A SQL error was causing shipments with a generated pick list/receipt linked to different orders to appear when users were running the report with a different order number filter.

Resolution: Included shipment data in the set filtered by the Order No filter in both reports.

4.7.9 Receipt Reject Alert Filters Showing Data from All Instances – PDS-14262

Problem: Receipt Reject alerts were showing data from all instances instead of user/role/org-specific data.

Cause: Some OMS changes were causing this error to occur.

Resolution: The issue has been resolved after integrating previous OMS changes.

4.7.10 Receipt Rejected Quantity Report and Alert not working for the Order more than 2 Lines — PDS-14321

Problem: The system failed to generate an alert for rejected quantity report for orders of more than 2 lines.

Cause: The system failed to allocate the alert due to: PersonalizedIssueCompTaskPerformer.

Resolution: Fixed mapping population for Development Support and Learning Support.

4.7.11 Requires Buffers for Component After Delete Load – PDS-12039

Problem: Some users noticed that warehouse assembly and kitting operations were failing.

Cause: The system logic required the components' buffers to find the component item. If a buffer was not present, the system identified the item as a work-in-progress item and didn’t use it as a component in multi-level bills of materials.


Bug Fixes – 178

Resolution: The Require Component Buffer For Kitting and Require Component Buffer For Assembly policies were introduced, and logic has been updated to require a component buffer only if they are turned on. If the corresponding policy is off, then a single-level bill of material is expected, and component buffer will not be required by the system.

4.7.12 Requisition Activity and Distribution Report Showing Null Records for BOH Fields – PDS-14122

Problem: The Requisition Activity and Distribution Report was showing null fields for the Opening BOH and Closing BOH fields.

Cause: The system logic contained some error. Due to this, the records for which the BOH was not calculated were also shown in the report, resulting in null values being displayed.

Resolution: Logic has been updated so that the records for which Opening And Closing BOH is calculated are shown in the report.

4.7.13 Reverse Inventory Adjustment on Cycle Count – PDS-11796

Problem: Some users were unable to reverse an inventory discrepancy/adjustment reflected on Inventory Operations that was created/applied from Cycle Count inventory.

Cause: The system was not designed to allow these operations to occur on cycle count UIs.

Resolution: The system now allows cancellation of adjustments regardless of inventory discrepancy linkage. Additionally, an Inventory Operation Cancel filter/retrieval and detail field has been added to inventory discrepancy.

4.7.14 RTVN 9901 MRP Engine Failed Due to 50k Record Error – PDS-14289

Problem: MRP Engine failed to perform due to 50K record error.

Cause: DataAccessService queries were not allowed to fetch more than 50K rows of data due to memory constraints. MRP Engine query exceeded the limit.

Resolution: The system is updated to add a condition and fetch only those items which are part of BOM, either as Raw Materials, Intermediate or FG items. The updated condition has reduced Items from 50K to 30K and increased Engine performance.


Bug Fixes – 179

4.7.15 Sequence Numbers not in Order in Printed Picklist PDF – PDS-14039

Problem: When printing a picklist to PDF, the sequence number of lines was not in numerical order.

Cause: The algorithm to enforce numerical values in order was not set up for PDF printing for picklists.

Resolution: Numerical value order logic was added to printed PDFs for picklists.

4.7.16 Text on PDF is too Small – PDS-14007

Problem: Some users noticed that exported PDF files were not readable as the font in the PDF implementation was too small to read.

Cause: The PDF was printed in the wrong media type - A2 instead of A4.

Resolution: Corrected the media type to be A4.

4.7.17 Unable to Add EPT-level Callback – PDS-12472

Problem: The Adjust Logical Inventory task performer was not using User or Enterprise Admin context, but instead was using Value chain Admin Context. EPT-level callbacks were not being invoked and could not verify buffers for EPT-level alert.

Cause: The system was not set up to process this task in the correct level context.

Resolution: The system has been updated to pass the user context identifier in grid task parameters instead of in the Value Chain Id. The previous parameter format is still supported.

4.7.18 Unable to Close Receipt Due to Outbound Generation Error – PDS-13461

Problem: While performing the Receipt close outbound operation, it is failing due to the exception:

REJECT_REASON_CODE"."OPERATION_TYPE": invalid identifier

Cause: An SQL was causing this issue to occur.

Resolution: The SQL has been fixed for this issue.


Bug Fixes – 180

4.7.19 UOM Filter Not Present for Requisition Activity and Distribution Report – PDS-14115

Problem: Some users noticed that there was no UOM filter present on the Requisition Activity and Distribution Report.

Cause: The filter was missing for this report.

Resolution: The filter has been added.

4.7.20 Upcoming Cycle Count Notification Error – PDS-14334

Problem: The system was unable to find resources for certain cycle count notifications.

Cause: When processing child-level alerts, only alerts on the first model in the child list were able to be correctly processed. If an alert was created for any other child model, a null pointer exception was thrown.

Resolution: The system has been updated to correctly process multiple alerts for cycle counts at multiple levels.

4.7.21 Users Unable to Create Putaway Lists – PDS-13966

Problem: While generating putaway lists from receipts in a Closed state that have at least one line quantity of 0, an error message was showing.

Cause: The system was throwing an exception when attempting to process lines with a 0 value.

Resolution: The system has been redesigned to skip 0 quantity receipt lines during putaway list generation.


Revision History – 181

5 Revision HistoryVersion Release Date Author Comments

0.1 09 Jun 2018 Tech Docs Commence Initial Draft

0.2 28 Dec 2018 Tech Docs • Publish Draft of Working Copy for IBUs

0.3 03 Feb 2019 Tech Docs • Add recent bug fixes through Jan 25, 2019.

• Add known remaining undocumented enhancements.

• Update System Requirements section.

• Update Backward Incompatibilities section.

• Update Minimum Requirements section.

• Copy-edit all content.

0.4 06 Feb 2019 Tech Docs Added content to the Network Changes section.

0.5 12 Feb 2019 Tech Docs Minor edits for clarity, style, and grammar.