--- title: "Summer '25 Load Status" slug: "summer-25-load-status" tags: ["EDI", "Load Status Update"] updated: 2025-09-03T16:08:08Z published: 2025-11-04T19:06:30Z canonical: "documents.revenova.com/summer-25-load-status" --- > ## Documentation Index > Fetch the complete documentation index at: https://documents.revenova.com/llms.txt > Use this file to discover all available pages before exploring further. # Summer '25 Load Status ## Overview EDI 214 and 322 transactions contain Load status information including appointments and exceptions. See the EDI Specification Guide for payload examples. ## EDI 214 ### Inbound Load stop status updates match on the Stop Number first, and then the City, State, and Country. If no Stop Number is provided, matching is based on the Stop Account and must match the City. The State and Country must also match, if present. **Time Zones** The TMS accepts time zones as an optional element when received from inbound EDI 214 transactions. Time zone information is managed as described below. The Time Zone is set for Stop Level Events such as arrivals, departures, and appointment times in the following scenarios. - The Stop Location record in the TMS has a time zone. - The time zone is set to the Stop location. - If the time zone indicated on the EDI 214 is different from the Stop location time zone, the time on the 214 is translated into the Stop location time zone. - If the Stop Location does not have a time zone. - The time from the EDI 214 is accepted. - In Transit X6 Load tracking updates are processed as Load events. If a time zone is received on an X6 214 update, the time zone is converted to GMT. - If an EDI 214 transaction does not contain a time zone, the time from the transaction is translated into the Stop location's time zone. Time zones follow the following hierarchy. | | Event | | --- | --- | | | **↓** | | | Stop | | | **↓** | | | Location | | | **↓** | | | User | | | **↓** | | | GMT | Time Zones are sent in outbound 214 transactions in Local Time (LT). **Geolocations** Latitude and Longitude coordinates are an optional element that may be received by the TMS in EDI 214 transactions. Geolocation coordinates are stored on the Load in the **Last Reported Geolocation** field. City/State combinations are not matched to the geolocation coordinates. ### Outbound Outbound EDI 214 transactions are processed as Platform Events. The TMS makes the *SendLoadStatusMessages* API call to send all queued 214 transactions to the Trading Partner VAN and/or Trading Partner(s) as X6 transactions. No EDI 997 is returned to the TMS. > [!NOTE] > The TMS sends Load stop information including those with the same location for multiple stops on a single Load. EDI 214 transactions are sent when a Load meets the following criteria. 1. The first Stop does not have a **Last Reported City** value. 2. The **Load Status** is not one of the following. - Delivered - Completed - Cancelled - Declined - Expired 3. The **Expected Delivery Date** does not have a value OR the last Stop **Expected Ship Date** is more than 10 days in the past. 4. The Load’s **EDI Provider** matches the Revenova customer **EDI Provider**. 5. The Load’s **EDI Status** is set to one of the following. - Accepted - Updated by Customer - Update Pending from Customer 6. The Transportation Profile **Location Update Send Frequency** field is set to one of the picklist values (not null). - 15 minutes - 30 minutes - 1 hour - 2 hours - 4 hours - 12 hours - 24 hours 7. The Load meets the time elapsed set by the **Location Update Send Frequency** on the Transportation Profile. The TMS sends an updated EDI 214 transaction when there are changes to the following fields. - Appointment Time(s) - Arrival Date - Departure Date - Carrier Status set to *Loading* or *Unloading* **Stop Number** Outbound EDI 214 transactions include the Stop Number in the currentLocation element. Load Stops are searched and the first Stop not in a *Departed* status determines the current Stop Number sent in the transaction. See the EDI Specification Guide for more element information. **Event Code** The **Event Code** field is displayed on the Load EDI related list. Event Codes are received on inbound EDI 214 transactions. Multiple Event Codes may be as part of outbound EDI 214 transactions. See the EDI Specification Guide for a list of Event Codes. #### **Bulk EDI 214 Send** Send or re-send EDI 214 status transactions in bulk. Check the appropriate Loads from the Load list view and select EDI Status from the drop-down. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EDI Load Status - Load List View - 2.png) Send EDI 214 transactions by clicking the Send button from the Bulk EDI 214 Send Visualforce page shown below. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EDI Load Status - 3.png) #### **EDI 214 Tracking Modal Send** Send 214 Status Update transactions from the Customer Banner LWC. While the Load is in transit, navigate to the Customer Banner LWC. Select the tracking button on the banner. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EDI Load Status - Customer Banner.png) The Load Tracking Administration modal renders. Choose the **Send EDI 214 Update Now** button. ![](https://cdn.document360.io/b89abf73-101a-4754-a781-084aef8f68dd/Images/Documentation/EDI Load Status - Tracking Modal.png) ## EDI 322 Outbound Load Status updates are sent as EDI 214 transactions. ### Inbound Inbound EDI 322 transactions contain movement events and CLM car location messages. - Inbound EDI 322 Load Status Message transactions are matched based on the shipmentId to the TMS **Load Number**. - The Event Code received in the transaction determines the Stop information that is updated. See the Event Codes table below for specific logic. - If the EDI transaction contains a **Waybill Number**, **Booking Number**, or **Seal Number** these values are saved to the Load. - Any existing values in these fields are overwritten with the values from the EDI 322 transaction. **Stop Matching** The information received in the EDI 322 transaction is used to identify/match the current Load Stop based on the following criteria. | TMS Stop Field | EDI 322 Event Payload Element | Logic | | --- | --- | --- | | Number | stopNumber | Matched value is the current Stop. | | Location | location (latitude and longitude) | 1. A Location is created and compared to each Account latitude and longitude. 1. The difference is calculated for each Account. 2. The closest Account is compared to Location field of any Stop. 3. Matched Account is the current Stop. | | Location | status eventCity and eventState | 1. Each Account City and State is checked (case-insensitive). 2. Account City and State is compared to status eventCity and eventState of any Stop. 3. Matched Account is the current Stop. | - Some scenarios have no matches based on the Stop Number, Lat/Lon, or City/State. - The first Stop without a **Departure Date** has not yet departed. - This stop is the current Stop. - If still no match is found, all other Stops have **Departure Date** fields populated. - The last Stop on the Load is the current Stop. ### Event Codes | Code | Name | Stop Information/Notes | | --- | --- | --- | | AD | EDI Delivery Appointment Scheduled | | | AG | Estimated Delivery | - **Stop Status** is *En Route.* - Previous Stops set as *Departed*. - Stop **Carrier Status Comments** are updated. - Stop **Carrier ETA Date** is the eventDate (LT). - Stop **Carrier ETA Time** is the eventTime (LT). | | AL | EDI Loaded on Rail | - **Stop Status** is *Arrived.* - Stop **Arrival Date** is the eventDate (LT). - Stop **Arrival Time** is the eventTime (LT). | | AR | Rail Arrival at Destination Ramp | - **Stop Status** is *Arrived.* - Stop **Arrival Date** is the eventDate (LT). - Stop **Arrival Time** is the eventTime (LT). *The same AR code is listed twice for Rail Arrival at destination ramp and EDI Rail Arrival.* | | B | EDI Bad Order | *Shipment was on a piece of equipment that failed.* | | CB | Chassis Tie | | | CC | Chassis Untie | | | D1 | Completed Unloading at Delivery Location | - **Stop Status** is *Departed.* - Previous Stops set as *Departed.* - Stop **Departure Date** is the eventDate (LT). - Stop **Departure Time** is the eventTime (LT). | | G | EDI Repaired Released | | | I1 | Intermodal In-Gate | - **Stop Status** is *En Route.* - Previous Stops set as *Departed*. - Stop **Carrier Status Comments** are updated. *The same EDIInGate (I) and Intermodal In-Gate (I1) codes are listed twice.* | | J | EDI Delivered to Connecting | - **Stop Status** is *Departed.* - Stop **Departure Date** is the eventDate (LT). - Stop **Departure Time** is the eventTime (LT). *Shipment delivered to an interline Carrier.* | | L | EDI Loading On Spot | | | NF | EDI Free Time to Expire | *The date and time of the NF event is the last free day.* | | NT | Container Ready for Pickup From Rail Yard | - **Stop Status** is *En Route.* - Previous Stops set as *Departed*. - Stop **Carrier Status Comments** are updated. | | OA | Intermodal Out-Gate | - **Stop Status** is *En Route.* - Previous Stops set as *Departed*. - Stop **Carrier Status Comments** are updated. | | P | EDI Departed Terminal Location | - **Stop Status** is *Departed.* - Stop **Departure Date** is the eventDate (LT). - Stop **Departure Time** is the eventTime (LT). | | R | EDI Received from Prior Carrier | *Shipment is received from an interline Carrier.* | | RA | Waypoint Arrival | - **Stop Status** is *En Route.* - Previous Stops set as *Departed*. - Stop **Carrier Status Comments** are updated. | | RD | Waypoint Departure | - **Stop Status** is *En Route.* - Previous Stops set as *Departed*. - Stop **Carrier Status Comments** are updated. | | RL | Rail Departure from Origin Intermodal Ramp | - **Stop Status** is *Departed.* - Stop **Departure Date** is the eventDate (LT). - Stop **Departure Time** is the eventTime (LT). | | RN | EDI Renotification | *Notify Party at destination is re-notified.* | | S | EDI Spotted at Customer | | | S1 | Train Spotted at Consignee Location | - **Stop Status** is *Arrived.* - Previous Stops set as *Departed*. - Stop **Arrival Date** is the eventDate (LT). - Stop **Arrival Time** is the eventTime (LT). | | T | EDI ITM In | | | TA | Waybilled | | | TM | EDI ITM Out | | | UR | Equipment Grounding | - **Stop Status** is *En Route.* - Previous Stops set as *Departed*. - Stop **Carrier Status Comments** are updated. | | VA | EDI Vessel Arrival | | | VD | EDI Vessel Departure | | | W | EDI Waybill Created | | | X1 | Arrived at Delivery Location | - **Stop Status** is *Arrived.* - Previous Stops set as *Departed*. - Stop **Arrival Date** is the eventDate (LT). - Stop **Arrival Time** is the eventTime (LT). | | XA | EDI Released Loaded by Customer | - Stop **Carrier Status Comments** are updated. | | Z | EDI unloading on Spot | - **Stop Status** is *Arrived.* - Stop **Arrival Date** is the eventDate (LT). - Stop **Arrival Time** is the eventTime (LT). |