| |
|
|
|
|
|
|
|
|
|
Segment: |
|
|
BSN Beginning Segment for
Ship Notice |
|
|
Position: |
|
|
020 |
|
|
Loop: |
|
|
Level: |
|
|
Heading |
|
|
Usage: |
|
|
Mandatory |
|
|
Max Use: |
|
|
1 |
|
|
Purpose: |
|
|
To transmit identifying numbers, dates, and other basic data
relating to the transaction set |
|
|
Syntax Notes: |
|
|
1 |
|
|
If BSN07 is present, then BSN06 is required. |
|
|
Semantic Notes: |
|
|
1 |
|
|
BSN03 is the date the shipment transaction set is created. |
|
|
|
|
|
2 |
|
|
BSN04 is the time the shipment transaction set is created. |
|
|
|
|
|
3 |
|
|
BSN06 is limited to shipment related codes. |
|
|
Comments: |
|
|
1 |
|
|
BSN06 and BSN07 differentiate the functionality of use for the
transaction set. |
|
|
Notes: |
|
|
|
|
|
Example: BSN*00*SHIP02931092*19990712*1615! |
|
Data Element Summary
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Ref. |
|
|
Data |
|
|
|
|
|
Des. |
|
|
Element |
|
|
Name |
|
|
Attributes |
|
|
M |
|
|
BSN01 |
|
|
353 |
|
|
Transaction Set Purpose Code |
|
|
M |
|
|
|
|
|
ID 2/2 |
|
|
|
|
|
Code identifying purpose of transaction set |
|
|
|
|
|
|
|
|
M |
|
|
BSN02 |
|
|
396 |
|
|
Shipment Identification |
|
|
M |
|
|
|
|
|
AN 2/30 |
|
|
|
|
|
A unique control number assigned by the original shipper to
identify a specific shipment |
|
|
M |
|
|
BSN03 |
|
|
373 |
|
|
Date |
|
|
M |
|
|
|
|
|
DT 8/8 |
|
|
|
|
|
Date expressed as CCYYMMDD |
|
|
M |
|
|
BSN04 |
|
|
337 |
|
|
Time |
|
|
M |
|
|
|
|
|
TM 4/8 |
|
|
|
|
|
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) |
|
| |
|
|
|
|
|
|
|
|
|
856I4010 (004010) |
|
|
|
|
|
February 18, 2000 |
|
|
|