Overview
EDI Order Update Console
The EDI Order Update Console Lightning Web Component (LWC) provides the ability to monitor and manage EDI transactions for each load. Once activated, the EDI Order Update Console LWC is found on the Load page under the EDI tab.
To activate the EDI Order Update Console for a trading partner, go to their EDI Location record and check the Use EDI Order Update Console checkbox.
Both Auto-Accept Update 204 and Use EDI Order Update Console cannot be checked. One or the other must be selected. When Use EDI Order Update Console is selected, all EDI Update settings for that EDI Location are ignored.
Updates received from an EDI 204 transaction are made. Block 204 transaction updates in the EDI Order Update Console.
.png)
With Use EDI Order Update Console checked, any inbound update 204s that are received for this trading partner are saved as new EDI Transaction records to the Load record they are associated with. Loads receiving those updates have the EDI Status field set to Update Pending from Customer. The EDI Transaction saved to the Load is set to a Pending status, indicating that it needs to be processed with the EDI Order Update Console.
Access the console by clicking the hyperlink to the EDI Transaction record from the EDI Transactions related list on the Load page.
.png)
The console should render on the second tab of the page.
.png)
The console attempts to match the Stops and Line Items between the inbound update 204 and the existing TMS Load for comparison purposes. A load “fingerprint” is defined below.
There are five columns for each section.
Field Name: This is the name of the field on the object that is updated.
EDI Update Value: This is the value of the field that is present on the inbound 204 update.
Current Value: This is the value of the field that is present on the existing TMS Load.
Save As Value: This is the value that is saved as an update to the Load, Stop, Line Item, etc. when one of the Save buttons is clicked.
Undo/Redo: This is a column of undo and redo buttons. These allow for quick accept/decline of a specific field in the console.
By default, Save As Value is populated with the same value as the EDI Update Value. If that value is different from the Current Value, it is highlighted in yellow, indicating a difference between the inbound 204 update and the actual value on the Load in the TMS. Click the Undo button to sets the Save As Value back to the Current Value, removing the highlight. Click the Redo button to set the Save As Value to the EDI Update Value, which again is highlighted if there is a difference. Users may also type directly into the Save As Value field as needed.
Each section represents the different objects that make up the load. These sections are expandable/collapsible with a button on the right-hand side for ease of navigation.
There are four buttons across the top right and bottom of the console. They perform the following actions.
Accept & Save: Saves all updates to the Load, Stops, Line Items and Customer Quote as indicated in the "Save As Value" column. An EDI 990 Acceptance is sent, and the user is brought to the updated Load. The EDI Status field on the Load is set to Accept.
Decline & Save: Saves all updates to the Load, Stops, Line Items and Customer Quote as indicated in the "Save As Value" column. An EDI 990 Rejection is sent, and the user is brought to the updated Load. The EDI Status field on the Load is set to Decline.
Show Updates Only/Show All Values: Shows only the updates when the "Current Value" is different than the "Save As Value." Click the same button again to show all fields.
Reload Console Data: During processing, to refresh the data and start the processing over, click this button to re-load the console back to its original state.
Each section of fields has an Undo and Redo button at the top of the "Save As Value" column. These buttons Undo or Redo the updates of all fields in the section for faster processing.
When processing Stops, there are Up and Down arrows in the "EDI Update Value" column. These buttons quickly shift the Stops on the inbound EDI Update 204 for ease of ordering and processing stops.
The stop-matching logic attempts to align the stops according to the load "fingerprint." The load “fingerprint” is defined as:
Location Name + Location Shipping Street + Location Shipping City + Location State + Location Postal Code
The line Item-matching logic attempts to align the line items according to a “fingerprint.” The line item "fingerprint" is defined as:
Name + Description + Handling Units + Pickup Stop Number + Delivery Stop Number
When the user attempts to Accept or Decline and then Save Console data, several checks are performed to prevent users from mistakenly editing 204s with invalid data. Four important items to be aware of are:
Each saved stop must have:
Number
Location Name
Shipping Street
Shipping City
Shipping State/Province
Shipping Zip/Postal Code
Shipping Country
Appointment Required
Expected Date
To remove a stop, remove all of the fields from 1 above. All Stop Numbers must be numeric. A Stop Number may not be used more than once.
Each saved line item must have:
Item Number
Item Description
Weight
Weight Units
Pickup Stop Number
Delivery Stop Number.
To remove a line item, remove all the fields from 3 above. All Pickup and Delivery Stop Numbers must be numeric and must reference a Stop.
After editing and either accepting or declining the load tender, the user is brought to the Load detail page. The processed EDI Transaction now has a Success status, and the Transaction Payload After Console Update field on the EDI Transaction is populated with the XML as updated by the user with the console.
.png)