BSN Beginning Segment for Ship Notice

To transmit identifying numbers, dates, and other basic data relating to the transaction set

Position: BSN-01 · Element: 353 · Name: Transaction Set Purpose Code · Type: Identifier (ID) · Requirement: Mandatory · Min: 2 · Max: 2 · Repeat: -

Code identifying purpose of transaction set

Position: BSN-02 · Element: 396 · Name: Shipment Identification · Type: String (AN) · Requirement: Mandatory · Min: 2 · Max: 30 · Repeat: -

A unique control number assigned by the original shipper to identify a specific shipment

Position: BSN-03 · Element: 373 · Name: Date · Type: Date (DT) · Requirement: Mandatory · Min: 6 · Max: 6 · Repeat: -

Date (YYMMDD)

BSN03 is the date the shipment transaction set is created.

Position: BSN-04 · Element: 337 · Name: Time · Type: Time (TM) · Requirement: Mandatory · Min: 4 · Max: 8 · Repeat: -

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)

BSN04 is the time the shipment transaction set is created.

Position: BSN-05 · Element: 1005 · Name: Hierarchical Structure Code · Type: Identifier (ID) · Requirement: Optional · Min: 4 · Max: 4 · Repeat: -

Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set

Position: BSN-06 · Element: 640 · Name: Transaction Type Code · Type: Identifier (ID) · Requirement: Conditional · Min: 2 · Max: 2 · Repeat: -

Code specifying the type of transaction

BSN06 is limited to shipment related codes.

BSN06 and BSN07 differentiate the functionality of use for the transaction set.

Position: BSN-07 · Element: 641 · Name: Status Reason Code · Type: Identifier (ID) · Requirement: Optional · Min: 3 · Max: 3 · Repeat: -

Code indicating the status reason

C0706: If BSN-07 is present, then BSN-06 is required