X12 315 Status Details (Ocean)
This Draft Standard for Trial Use contains the format and establishes the data contents of the Status Details (Ocean) Transaction Set (315) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide all the information necessary to report status or event details for selected shipments or containers. It is intended to accommodate the details for one status or event associated with many shipments or containers, as well as more than one status or event for one shipment or container.
- ~ Segment
- * Element
- > Component
- None included
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer
- U
- U.S. EDI Community of ASC X12, TDCC, and UCS
This version number covers the interchange control segments
- 00401
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator
- >
- Component Element Separator
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- QO
- Ocean Shipment Status Information (313, 315)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Assigned number originated and maintained by the sender
Code used in conjunction with Data Element 480 to identify the issuer of the standard
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
- 004010
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 315
- Status Details (Ocean)
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Inquiry or Reply
To transmit identifying numbers, dates, and other basic data relating to the transaction set
Example: B4*AE20020401*2235MSCU123456L4310DEHAMUN*7
Code indicating the status of a shipment
- AE
- Loaded on Vessel
- AL
- Loaded on Rail
- AO
- Loaded on Barge
- AR
- Rail Arrival at Destination Intermodal Ramp
- CR
- Carrier Release
- I
- In-Gate
- OA
- Out-Gate
- RL
- Rail Departure from Origin Intermodal Ramp
- UO
- Unloaded from Barge
- UR
- Unloaded from a Rail Car
- UV
- Unloaded From Vessel
Date expressed as CCYYMMDD
- B404 is the date of last reported status of cargo.
Date of event, (must provide century).
Prefix or alphabetic part of an equipment unit's identifying number
Mandatory for carrier own containers only.
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
Container number.
Code identifying equipment type
Has to be Valid Container ISO Code.
Code which identifies a specific location
ISO Location code. City Name in case B412 is ‘CI’.
Code identifying type of location
- CI
- City
- UN
- United Nations Location Code (UNLOCODE)
Number which designates the check digit applied to a piece of equipment
Mandatory for carrier own containers only.
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Example: N9BNCarrier Booking Number
Code qualifying the Reference Identification
- 4F
- Carrier-assigned Shipper Number
- ACC
- Status
- BM
- Bill of Lading Number
- BN
- Booking Number
- CA
- Cost Allocation Reference
- CT
- Contract Number
- LS
- Bar-Coded Serial Number
- P8
- Pickup Reference Number
- QJ
- Return Material Authorization Number
- REF
- Leasing Company Reference
- SN
- Seal Number
- SNC
- Customs Seal Number
- SNL
- Customer Seal Number
- SNM
- Carrier Seal Number
- SNN
- No Seal Number
- SNS
- Shipper Seal Number
- SNT
- Terminal Seal Number
- SNV
- State Non-Resident Violator Compact
- SO
- Shipper's Order (Invoice Number)
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
When used with N901 ACC it should contain:
NEWunique number - to report first creation
UPDATEsame unique number from NEW reporting – to report updated
DELETE*same unique number from NEW reporting – to report cancellation
Free-form descriptive text
Examples:
N9ACCNEW123456~
N9ACCUPDATE123456~
N9ACCDELETE*123456~
Status Details (Ocean)
To transmit identifying information relative to identification of vessel, transportation dates, lading quantity, weight, and cube
Example: Q29017020DK***43WLVESSEL NAME
Code identifying vessel
Lloyd's code, Call Sign.
Code identifying the country
- Q202 is the code identifying the country in which the ship (vessel) is registered.
Identifying designator for the particular flight or voyage on which the cargo travels
Code specifying vessel code source
- C
- Ship's Radio Call Signal
- L
- Lloyd's Register of Shipping
Name of ship as documented in "Lloyd's Register of Ships"
Port or Terminal
Contractual or operational port or point relevant to the movement of the cargo
At least one instance of the R4 loop is mandatory.
Sample 1:
R4LUNDEHAMHAMBURG
Sample 2:
R4RCIFRXXXMONTOIR*FR
Sample 3:
Terminal/Depot Code R45UNBEANRANTWERP**S913
Code defining function performed at the port or terminal with respect to a shipment
- 5
- Activity Location (Operational)
Place at which the activity being reported is occurring.
- D
- Port of Discharge (Operational)
Port at which cargo is unloaded from vessel.
- E
- Place of Delivery (Contractual)
Place at which cargo leaves its care and custody of carrier.
- L
- Port of Loading (Operational)
Port at which cargo is loaded on vessel.
- M
- Destination (Operational)
Place at which carrier actually turns cargo to consignee or his agent.
Should provide the destination of the inland move and not the final destination of the unit (i.e. next event location).
- R
- Place of Receipt (Contractual)
Place at which cargo enters the care and custody of carrier.
- S
- Return Pool (Operational)
Place at which equipment is returned.
Unit restitution location i.e. place where unit is returned empty or full after being stripped or stuffed by client.
- T
- Transshipment Port (Contractual)
Place at which cargo is transferred to another carrier.
Code identifying type of location
- CI
- City
- UN
- United Nations Location Code (UNLOCODE)
Code which identifies a specific location
UNLOCODE,.
POL and POD must be ISO Codes, In case Delivery and/or receipt are not ISO Locations XXX NOTATION AS IN DTX MAY BE USED AND R403
SHOULD MENTION “CI” NOT “UN”.
Free-form name for the place at which an offshore carrier originates or terminates (by transshipment or otherwise) its actual ocean carriage of property
City Name or Port Location.
Date/Time Reference
To specify pertinent dates and times
Represents the Date and Time of the Port Activity.
Example: DTM13920020401*0800
Code specifying type of date or time, or both date and time
- 139
- Estimated Arrival Date
- 140
- Actual Arrival Date
- 369
- Estimated Departure Date
- 370
- Actual Departure Date
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.