X12 856 Ship Notice/Manifest
This standard provides the standardized format and establishes the data contents of a ship notice/manifest transaction set. A ship notice/manifest lists the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information.
The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment.
- ~ Segment
- * Element
- > Component
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.
- SH
- Ship Notice/Manifest (856)
Code identifying party sending transmission. Codes agreed to by trading partners.
Code identifying party receiving transmission. Codes agreed to by trading partners.
Date sender generated a functional group of transaction sets.
Time (HHMM) when the sender generated a functional group of transaction sets (local time at sender's location).
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. Positions 1-3, version number; positions 4-6, release and subrelease level of version; positions 7-12, industry or trade association identifier (optionally assigned by user).
- 002040CHRY
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) is intended for use by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the invoice transaction set).
- 856
- X12.10 Ship Notice/Manifest
Beginning Segment for Ship Notice
To transmit identifying numbers, dates and other basic data relating to the transaction set
Example: BSN001234568811041200
Code identifying purpose of transaction set.
- 00
- Original
- 01
- Cancellation
- 19
- Seller initiated change
A unique control number assigned by the original shipper to identify a specific shipment.
A unique supplier-assigned Shipment Identification (SID) number that is not repeated within a one year period.
Date (YYMMDD).
- BSN03 is the date the shipment transaction set is created.
Date/Time Reference
To specify pertinent dates and times
Code specifying type of date or time, or both date and time.
- At least one of DTM02 or DTM03 must be present.
- 011
- Shipped
Local date and time shipment leaves the supplier premises.
Time expressed in 24-hour clock time (HHMM, time range: 0000 though 2359).
Code identifying the time.
- 01
- GMT + 1 hour
Non England European Locations
- 02
- GMT + 2 hours
Non England European Locations
- 03
- GMT + 3 hours
Non England European Locations
- 04
- GMT + 4 hours
Non England European Locations
- 05
- GMT + 5 hours
Outside of North America
- 06
- GMT + 6 hours
Outside of North America
- 07
- GMT + 7 hours
Outside of North America
- 08
- GMT + 8 hours
Outside of North America
- 09
- GMT + 9 hours
Outside of North America
- 10
- GMT + 10 hours
Outside of North America
- 11
- GMT + 11 hours
Outside of North America
- 12
- GMT + 12 hours
Outside of North America
- 13
- GMT - 12 hours
Outside of North America
- 14
- GMT - 11 hours
Outside of North America
- 15
- GMT - 10 hours
Outside of North America
- 16
- GMT - 9 hours
Outside of North America
- 17
- GMT - 8 hours
Outside of North America
- 18
- GMT - 7 hours
Outside of North America
- 19
- GMT - 6 hours
Outside of North America
- 20
- GMT - 5 hours (Eastern Time)
South American Locations
- 21
- GMT - 4 hours (Atlantic Time)
South American Locations
- 22
- GMT - 3 hours
South American Locations
- 23
- GMT - 2 hours
Outside of North America
- 24
- GMT - 1 hour
Outside of North America
- CD
- Central Daylight Time
Daylight Savings Time
- CT
- Central Time
- ED
- Eastern Daylight Time
Daylight Savings Time
- ET
- Eastern Time
- GM
- Greenwich Mean Time
England
- MD
- Mountain Daylight Time
Daylight Savings Time
- MT
- Mountain Time
- PD
- Pacific Daylight Time
Daylight Savings Time
- PT
- Pacific Time
Detail
Example: HL~1~~S
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments.
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure.
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment, and would be incremented by one in each subsequent HL segment within the transaction.
Code defining the characteristic of a level in a hierarchical structure.
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order or item level information.
- S
- Shipment
Code indicating whether if there are hierarchical child data segments subordinate to the level being described.
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Measurements Actual Net Weight
To specify physical measurements, including dimensions, tolerances, weights and counts.
Example: MEAPDN28000LB
Code specifying the application of physical measurement cited.
- PD
- Physical Dimensions (Product Ordered)
Code identifying the type of measurement.
- N
- Actual Net Weight
The value of the measurement.
- Either MEA03 or MEA05 or MEA06 or MEA08 is required.
- If either MEA03, MEA05 or MEA06 is used, MEA04 is required.
Gross weight and net weight must be whole numbers. No decimals are allowed.
Measurements Gross Weight
To specify physical measurements, including dimensions, tolerances, weights and counts.
Example: MEAPDG34250LB
Code specifying the application of physical measurement cited.
- PD
- Physical Dimensions (Product Ordered)
Code identifying the type of measurement.
- G
- Gross Weight
The value of the measurement.
- Either MEA03 or MEA05 or MEA06 or MEA08 is required.
- If either MEA03, MEA05 or MEA06 is used, MEA04 is required.
Gross weight and net weight must be whole numbers. No decimals are allowed.
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight and quantity.
The TD1 segment should match what is on the Bill of Lading. In case of mixed loads use 'MIX90' in TD101 and the total number of containers (returnable and non-returnable) in TD102 (e.g., 1 pallet + 2 boxes = 3 containers).
Examples:
TD1PLT712
TD1MIX903
TD1COL522
Code identifying the type of packaging. Part 1. Packaging form. Part 2. Packaging Material.
- If TD101 is present, then TD102 is required.
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier, sequence of routing and to provide transit time information
When multiple carriers are to be employed in the movement of material, specify the originating carrier (the carrier leaving the supplier's dock). The SCAC code for the originating (routed) carrier is provided in the Supplier/Carrier Routing Instructions (853).
If making a rail shipment other than through a consolidator, identify the railroad carrying the shipment.
The mode of 'PC' (Private Carrier) is only to be utilized when transportation service is provided by the supplier using their own equipment and the supplier does not submit a Freight Bill for payment of said service. If 'PC' is used and the supplier does not have an assigned SCAC code, the supplier should insert the first four alphabetic characters of their company name. This is the only exception allowed with regard to the entry of SCAC codes.
If the supplier submits Freight Bills to FCA US for payment of supplier-provided transportation, use the mode and SCAC codes found on the Supplier/Carrier Routing Instructions (853). If the supplier does not have an SRI, they should call their FCA US Logistics as soon as possible.
SCAC codes CXUA, EWCF, ROEE AND XPEN and transportation modes 'A', 'AC' and 'AE' require a valid AETC number. SCAC code 'XZZZ' is now invalid and will be flagged as an error.
For expedited truck shipments (transportation mode 'E'), the SCAC in TD503 must be the actual trailer SCAC. For air expedited shipments (transportation mode 'AE'), the SCAC in TD503 must be the actual routed carrier SCAC. For air charter expedited shipments (transportation mode 'AC'), the SCAC in TD503 must be the SCAC of the carrier selected by FCA US Logistics.
Examples:
TD5B2UPACM (Trailer Load)
TD5B2CETRLT~~~PPCP1122 (Less than Trailer Load--Consolidation)B
TD52GTWR (Rail)B
TD52EAFCAE (Air Express)B
TD52UCCILT2551-10 (MMMA)
Code describing the relationship of a carrier to a specific shipment movement.
- At least one of TD502, TD504, or TD505 must be present.
- B
- Origin/Delivery Carrier (Any Mode)
Code designating the system/method of code structure used for Identification Code (67).
- When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement: use TD502 to identify the party responsible for defining the routing sequence; use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
- If TD502 is present, then TD503 is required.
- 2
- Standard Carrier Alpha Code (Motor) (SCAC)
Code identifying a party.
- If TD507 is present, then TD508 is required.
For TD502. Use carrier's SCAC code from Supplier/Carrier Routing Instructions (853).
For Mexico northbound and intra-Mexico moves: use conveyance carrier's SCAC.
Code specifying the method of transportation for the shipment.
- If TD510 is present, then TD511 is required.
- A
- Air
- AC
- Air Charter
- AE
- Air Express
- D
- Parcel Post
- DD
- Dedicated Delivery Service
- E
- Expedited Truck
- GG
- Geographic Shipping/Receiving
- GR
- Geographic Receiving
- GS
- Geographic Shipping
- I
- Common Irregular Carrier
- L
- Contract Carrier
- LT
- Less Than Trailer Load (LTL)
- M
- Motor (Common Carrier)
- O
- Containerized Ocean
- PC
- Private Carrier
- PD
- Parcel Delivery
- R
- Rail
- RC
- Rail, Less Than Carload
- RR
- Roadrailer
- VE
- Vessel, Ocean
- X
- Intermodal (Piggyback)
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity.
Used for shipments to MMMA only to supply the Routing Code from the Unit Contract Carriers. Not used for any other carriers for MMMA.
Code identifying type of location.
- PP
- Pool Point
For consolidation shipments. Not used for MMMA.
Carrier Details (Equipment)
To specify transportation details relating to the equipment used by the carrier.
Examples:
TD3TL~~154268 (Trailer)RR
TD3CR12345678 (Rail)
Code identifying type of equipment used for shipment.
- If TD302 is present, then TD303 is required.
Prefix or alphabetic part of an equipment unit's identifying number.
- If TD304 is present, then TD305, and TD306 are required.
For Mexico northbound and intra-Mexico moves: use carrier's SCAC code from Supplier/Carrier Routing Instructions (853).
Reference Numbers
To specify identifying numbers.
Although the standard allows up to 30 characters in reference numbers, FCA US processes only the first 16. Sending more than 16 characters in Bill of Lading numbers, Packing Slip numbers or Freight Bill numbers may result in ASNs being rejected as duplicates if the first 16 characters match a previously used reference number.
One REF segment is required at the Shipment level for the Bill of Lading number when shipping by surface carrier or Airbill number when shipping by air. Do not use more than 16 characters for Bill of Lading or Airbill number.
If multiple parts with multiple packing slips are involved in a shipment to a single destination, only one Bill of Lading Number should be utilized to identify that material at the Shipment level. The Commodity Procurement Program requires the Bill of Lading only at the Shipment Level.
A Master Bill of Lading is required when your Supplier Routing Instructions (SRI) indicates a shipment through a Pool Point, Crossdock or Border Crossing OR for transportation mode Geographic Receiving ('GR'). If the transportation mode is Geographic Shipping and Receiving ('GG') or Geographic Shipping ('GS'), a master bill of lading is not required even though the shipment is routed through a pool point.
The Master Bill of Lading number must be in a REF segment at the Shipment level. Detail Bill of Lading numbers are also required and must appear in REF segments at the Order level.
One to four additional REF segments at the Shipment level for trailer or railcar seal numbers, if present. Do not use more than 8 characters for each seal number.
One additional REF segment at the Shipment level for the Freight Bill number, if available. Do not use more than 16 characters for Freight Bill number.
One REF segment is required at the Shipment level for Packing Slip (Shipper) if only one Packing Slip applies to the entire shipment.
If there is more than one Packing Slip for a shipment, the REF segment is required at the Order level for each part number. Do not use more than 16 characters for the Packing Slip.
A Packing Slip Number cannot be duplicated within a twelve-month period.
A Bill of Lading Number cannot be duplicated within a twelve-month period
All cancellations (BSN01 = '01'), whether for line items or the entire ASN, require at least the following REF segments:
One at the Shipment level with the Bill of Lading number from the original ASN.
One at the Shipment level if only one Packing Slip applies to the entire shipment. If there is more than one Packing Slip for a shipment, a REF segment is required at the Order level for each part number.
Examples:
REFBM7374288
REFAW01DTW123456
REFPK34911
REFSN12345678
REFMB12345
REFFRA2113N
REFCNAA17284588 (MMMA)
Code qualifying the Reference Number.
- AO
- Appointment Number
- AW
- Air Waybill Number
- BM
- Bill of Lading Number
- CN
- Carrier's Reference Number (PRO/Invoice)
Carrier's Reference Number (PRO/Invoice) for MMMA shipments through carriers other than Unit (UCCI).
- FR
- Freight Bill Number
- MB
- Master Bill of Lading
- PK
- Packing List Number
- SN
- Seal Number
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
The same Bill of Lading and Packing Slip number cannot be reused during the same twelve month period. The FCA US system will reject these as duplicates.
Name
To identify a party by type of organization, name and code
Up to four N1 segments are used at the Shipment level. If all parts on the shipment are going to a single destination put all four N1 segments in the Shipment level. If the shipment is going to multiple destinations, the Ship To (ST) and Ultimate Destination (MA) N1 segments are put in the Order level with the appropriate part shown in the LIN segment.
The 'SU' and 'SF' are always at the Shipment level. The 'ST' and 'MA' could be at the Shipment level if shipping all items to one location or at the Order level if shipping to multiple locations.
Use 'SU' for the FCA US assigned supplier code for which the Material Release (830) was issued. Use 'SF' for the actual Ship From Location, even if the same as the 'SU'. Use 'ST' for the actual Ship To location specified on the Material Release. Use 'MA' for the FCA US receiving plant code of the ultimate destination, even if the same as the 'ST'.
These codes should echo the codes in the N1 segments in the heading and detail areas of the Material Release (830). If the codes are not correct on the Release, contact your buyer.
The entry of location codes with suffixes should be without any spaces between the five numerics and the alpha suffixes. For instance, the code '12345 A' should be entered as '12345A'.
Mopar Supplier Ship Direct and the Commodity Procurement Program will use an N1 segment with the 'BT' (Bill-To) qualifier in the Shipment level instead of the 'MA' (Ultimate Destination) qualifier in the Shipment or Order levels.
In support of the Container Management System, if the shipment being defined is containers only and being shipped to non-FCA US locations, an iteration of the N1 segment should be used with a qualifier of 'BT' and a value of '08989' in N104. Please refer to Example 25.
If the shipment of containers is being shipped to a FCA US location, omit the N1 segment with the 'BT' qualifier.
Examples:
N1SU~~9274724AB
N1SF~~9274724BB
N1ST~~9204025
N1MA~~9204025
N1BT~~9203103 (Mopar Supplier Ship Direct)
N1BT~~9206000 (Commodity Procurement Program - Steel)
N1BT~~9207020 (Commodity Procurement Program - Resin)
N1BT~~9208989 (Container Management)
N1SU~~9104006 (Customer EDI only)
N1SF~~9105406 (Customer EDI only)
N1ST~~9112345 (Customer EDI only)
Code identifying an organizational entity or a physical location.
- At least one of N102 or N103 must be present.
- BT
- Party to be Billed For Other Than Freight(Bill To)
Used for Mopar Supplier Ship Direct, Commodity Procurement Program, Container Management System only.
- MA
- Party for whom Item is Ultimately Intended
FCA US Plant
- SF
- Ship From
- ST
- Ship To
- SU
- Supplier/Manufacturer
Code designating the system/method of code structure used for Identification Code (67).
- 91
- Assigned by Seller or Seller's Agent
- 92
- Assigned by Buyer
Code identifying a party.
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
If N101 = 'SU', use: the FCA US assigned supplier code of the released supplier.
For Customer EDI only: '04006' = FCA US.
If N101 = 'SF', use the FCA US assigned supplier code of the actual Ship From location.
For Customer EDI only: the FCA US assigned code for FCA US plant locations.
If N101 = 'ST', use the FCA US assigned receiving plant code or the supplier code of the actual Ship To location.
For Customer EDI only: the FCA US assigned customer code.
If N101 = 'MA', use the FCA US assigned ultimate destination receiving plant code.
If N101 = 'BT':
'03103' for Mopar Supplier Ship Direct
'06000' for Steel Procurement Program
'06200' for FCA US Stamping
'07020' for Resin Procurement Program
'08989' for Container Management System
'05200' for Pay As Built
'02000' for Precious Metals
Reference Numbers
To specify identifying numbers.
Used in conjunction with the Ultimate Receiving ('MA') location in the N1 loop to identify FCA US receiving plant dock code as shown on the FCA US Material Release.
Example: REFDKCD3
Code qualifying the Reference Number.
- DK
- Dock Number
Excess Transportation Detail
To specify information relating to premium transportation.
To identify the causes, responsibility, and authorization number for a shipment that requires premium transportation. Used when FCA US gives authorization to use other than normal routing.
Examples:
ETDZZSAESR123456 (For Supplier Responsible AETC)
ETDZZZAECR123456 (For Carrier Responsible AETC)
ETDZZAAECE123456 (For FCA US Plant Responsible AETC)
Code identifying the reason for shipment via premium transportation rather than the normal mode of transportation.
- The value given in ETD03 qualifies the authorization number given in EDT04.
- If either ETD03 or ETD04 is present, then the other is required.
- ZZ
- Mutually Defined
Code identifying the organization responsible for paying the premium transportation costs.
- A
- Customer Plant (Receiving Location)
- S
- Supplier Authority
- Z
- Mutually Defined
Used for carrier responsibility.
Code qualifying the Reference Number.
- AE
- Authorization for Expense (AFE) Number
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
FCA US assigned Authorization for Excess Transportation Charges (AETC) number must start with:
'CE' for FCA US Expense
'SR' for Supplier Responsible
'CR' for Carrier Responsible
Must be unique within the current model year.
The Container level is used only for the Mopar Global Core Return System.
Example: HL21~CN
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments.
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure.
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment, and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to.
- HL02 identifies the Hierarchical ID Number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure.
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order or item level information.
Code indicating whether if there are hierarchical child data segments subordinate to the level being described.
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Item Identification
To specify basic item identification data.
The LIN segment is used to identify the bin or container number the parts are shipped in.
Example: LIN~~UF~B9842-9983
Alphanumeric characters assigned for differentiation within a transaction set.
- LIN01 is the line item identification
- If LIN04 is present, then LIN05 is required.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- LIN02 through LIN31 provide for fifteen (15) different product/service ID's for each item. For Example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU.
- If LIN06 is present, then LIN07 is required.
- UF
- User-defined Shipping Container Identifier
Example: HL32~O
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments.
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure.
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment, and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to.
- HL02 identifies the Hierarchical ID Number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure.
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order or item level information.
- O
- Order
Code indicating whether if there are hierarchical child data segments subordinate to the level being described.
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
Item Identification
To specify basic item identification data.
There should be one LIN segment in each Order level. The LIN segment is used to identify the buyer's number or returnable container part number and to cross-reference parts to returnable containers.
If a returnable container is used, the Container Part number is required in the LIN segment for the released part, as well as in an additional LIN segment in its own Order level.
Clarification on the specification of part number:
When FCA US issues the ASN:
- BP = Customer part number
- VP = FCA US part number
When FCA US receives the ASN:
- BP = FCA US part number
- VP = Supplier part number
Examples:
LINBPBP05761192AAEC~REL (Part Number only)
LIN05761192AAECRELRC0000CC10 (Part Number with Returnable Container)0000CC10 (Returnable Container Part Number)
LIN~~RC
LINBPBP03486285AAVP~ALY185B (Acustar Electronics Part Number)
LIN02802752AAEC2VO24901 (Primary Metals)02802752AA
LIN~~BPVO24901 (Commodity Procurement Program)
LIN~~BP~M04799198V (MMMA)
Mopar Consignee only:
LINVPVP05761192AAEC~REL (Part Number only)
LIN05761192AAECRELRC~0000CC10 (Part Number with Returnable Container)
Global Core Return only:
LIN~~BP~U5761192 (Part Number only)
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- LIN02 through LIN31 provide for fifteen (15) different product/service ID's for each item. For Example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU.
- If LIN06 is present, then LIN07 is required.
- BP
- Buyer's Part Number
The FCA US released part number found on the Material Release.
- RC
- Returnable Container No.
- VP
- Vendor's (Seller's) Part Number
For Mopar Consignee only.
Identifying number for a product or service.
- If LIN08 is present, then LIN09 is required.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- If LIN10 is present, then LIN11 is required.
- EC
- Engineering Change Level
Engineering Change Level required for production parts.
Primary Metals use: 'EC' = Engineering Control (Metal Specification Suffix).
- VO
- Vendor's Order Number
Primary Metals and Commodity Procurement Program use: Vendor (Mill) Order.
- VP
- Vendor's (Seller's) Part Number
For Huntsville Electronics use.
Identifying number for a product or service.
- If LIN12 is present, then LIN13 is required.
FCA US requires 1 to 3 characters for Engineering Change Level (check with your Engineering dept.).
Vendor Part Number may be up to 30 characters.
Primary Metals use:
Metal Specification Suffix requires 1 character.
Primary Metals and Commodity Procurement Program use:
Vendor (Mill) Order Number requires 5 characters.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- If LIN14 is present, then LIN15 is required.
- RC
- Returnable Container No.
Used only if LIN02 is 'BP' or 'VP' (Mopar Consignee only) and part is shipped in returnable container.
(A separate LIN segment in another Order level for returnable container tracking is also required.)
- VO
- Vendor's Order Number
Item Detail (Shipment)
To specify line item detail relative to shipment
Used to show quantity being shipped, unit of measure, and YTD cum shipped (adjusted for receiving discrepancies and returned material). Required at the Item level for Primary Metals and Commodity Procurement Program. Required at the Item Level for Containers. Required at the Order level for all other materials.
Examples:
SN13294942300EA90097
SN124 (Primary Metals and Commodity Procurement - Order level)UN (Service & Parts-Dealer Direct)
SN1~~2
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set.
Quantity shipped for the released part or returnable container part number referenced in the associated LIN segment.
Primary Metals, Commodity Procurement Program, use: Theoretical and Actual Pounds Shipped.
Code identifying the basic unit of measurement.
- SN103 defines the unit of measurement for both SN102 and SN104.
Purchased parts unit of measure as shown on the FCA US Material Release.
- 01
- Actual Pounds
- CW
- Hundred Pounds (CWT)
For Commodity Procurement Only
- EA
- Each
For Commodity Procurement Only
- FT
- Foot
For Commodity Procurement Only
- HF
- Hundred Feet
For Commodity Procurement Only
- KG
- Kilogram
For Commodity Procurement Only
- PC
- Piece
For Commodity Procurement Only
- UN
- Unit
Number of units shipped to date.
Cumulative net quantity to Date shipped for the current model year, including the quantity in SN102.
Not used by Primary Metals, Service & Parts-Dealer Direct, Commodity Procurement Program, Global Core Return System and Container Management System.
Quantity ordered.
Mopar Supplier Ship Direct only.
Purchase Order Reference
To provide reference to a specific purchase order
Used to show FCA US Purchase Order number and amendments.
Examples:
PRFPR517243AA00145447~~~~~VS800001 (Mopar Supplier Ship Direct)
PRF
Identifying number for Purchase Order assigned by the orderer/purchaser.
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction.
Primary Metals use: Steel Release Number.
Product/Item Description
To describe a product or process in coded or free-form format
Used by Mopar Supplier Ship Direct only to specify vehicle identification number, mileage and in-service date.
Example: PID~F~~~~1P3XP48KXNN137402 045405 92167
Code indicating the format of a description.
- When PID01 is ``F'', PID04 is not used.
Reference Numbers
To specify identifying numbers.
Although the standard allows up to 30 characters in reference numbers, FCA US processes only the first 16. Sending more than 16 characters in Bill of Lading numbers, Packing Slip numbers or Freight Bill numbers may result in ASNs being rejected as duplicates if the first 16 characters match a previously used reference number.
When parts on a single trailer are destined for multiple destinations and will pass through a consolidation center, OR where the transportation mode is Geographic Receiving, a Master Bill of Lading must be created. The Master Bill of Lading number must be in a REF segment at the Shipment level. Detail Bill of Lading numbers are also required and must appear in REF segments at the Order level.
If there is more than one Packing Slip for a shipment, the REF segment is required at the Order level for each part number. Do not use more than 16 characters for the Packing Slip.
A Packing Slip Number cannot be duplicated within a twelve month period.
A Bill of Lading Number cannot be duplicated within a twelve month period
All cancellations (BSN01 = '01'), whether for line items or the entire ASN, require at least the following REF segments:
One at the Shipment level with the Bill of Lading number from the original ASN.
One at the Shipment level if only one Packing Slip applies to the entire shipment. If there is more than one Packing Slip for a shipment, a REF segment is required at the Order level for each part number.
For Global Core Return System, two REF segments shall be used. The first shall have a qualifier of 'BM' in REF01 for the core return control number. The second shall have a qualifier of '8X' to convey the claim type: warranty ('W') or Mopar ('M') .
Examples:
REFBM7374288
REFPK34911
REFSV12345678 CG (Mopar Shipper, Space, Service Level)
Code qualifying the Reference Number.
- 8X
- Transaction Category or Type
- BM
- Bill of Lading Number
For Memphis Core Center only.
- LI
- Line Item Identifier (Seller's)
- MY
- Model year number
- PK
- Packing List Number
- RE
- Release Number
RAN for MMMA
- SV
- Service Charge Number
For Mopar SSD only.
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
If REF01 = '8X', the Claim Type for Global Core Return System.
If REF01 = 'LI', the line item number from the Material Release (for Memphis Core Center only).
If REF01 = 'SV', the Mopar Shipper number and parcel shipping service level code.
If shipping mode is LTL, provide Mopar Shipper number only. (for Mopar SSD only).
NOTE: The same Bill of Lading and Packing Slip number cannot be reused during the same twelve month period. The FCA US system will reject these as duplicates.
Name
To identify a party by type of organization, name and code
Two N1 segments are used at the Order level for a particular part number if the shipment is going to multiple destinations. The Ship To and Ultimate Destination N1 segments are put in the Order Level with the appropriate part shown in the LIN segment.
Use 'MA' for the FCA US receiving plant code of the ultimate destination, even if same as 'ST'.
These codes should echo the codes in the N1 segments in the heading and detail areas of the Material Release (830). If the codes are not correct on the Release, contact your buyer.
Example: N1MA~~9204025
Code identifying an organizational entity or a physical location.
- At least one of N102 or N103 must be present.
- MA
- Party for whom Item is Ultimately Intended
FCA US Plant
Code designating the system/method of code structure used for Identification Code (67).
- 92
- Assigned by Buyer
Code identifying a party.
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Use the FCA US assigned ultimate destination receiving plant code.
Reference Numbers
To specify identifying numbers.
Used in conjunction with the Ultimate Receiving ('MA') location in the N1 loop to identify FCA US receiving plant dock code as shown on the FCA US Material Release.
Example: REFDKCD3
Code qualifying the Reference Number.
- DK
- Dock Number
Name
To identify a party by type of organization, name and code
Two N1 segments are used at the Order level for a particular part number if the shipment is going to multiple destinations. The Ship To and Ultimate Destination N1 segments are put in the Order Level with the appropriate part shown in the LIN segment.
Use 'ST' for the actual Ship To location specified on the Material Release.
These codes should echo the codes in the N1 segments in the heading and detail areas of the Material Release (830). If the codes are not correct on the Release, contact your buyer.
Example: N1ST~~9274724AB
Code identifying an organizational entity or a physical location.
- At least one of N102 or N103 must be present.
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67).
- 92
- Assigned by Buyer
Code identifying a party.
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Use the FCA US assigned receiving plant code or the supplier code of the actual Ship To location.
Allowance, Charge or Service
To specify allowances, charges or services
To specify allowances or charges for ERS productive material only. This segment is used in the Order level to bill for charges associated with clauses or supplier-paid transportation for a specific part number. All charges must be related to a provision in the FCA US Purchase Order. Either ITA05 or ITA14 is required.
FCA US allows up to three ITA segments per Order level. If more than three occurrences are needed, contact Corporate Accounts Payable for instructions.
To bill FCA US for supplier-paid transportation, the value 'E' must be in the transportation code of the FCA US Purchase Order.
The Allowance or Charge Total Amount element (ITA07) is in the N2 format which calls for numeric data with 2 implied decimal points. If the charge or allowance is $100.00, the amount would be transmitted as '10000' (the decimal point is not transmitted).
Examples:
ITAC~~~06023A~~54321~~~~~~CLAUSE (PO clause)
ITA~C~~~06~~~3500~~~~~~~TTB (transportation)
Code which indicates an allowance or charge for the service specified.
Code indicating method of handling for an allowance or charge.
- 04
- Credit Customer Account
If ITA01 = 'A', use '04'.
- 06
- Charge to be Paid by Customer
If ITA01 = 'C', use '06'.
The number assigned by a vendor referencing an allowance, promotion, deal or charge.
If the additional charge is based on a clause in the FCA US Purchase Order, use the clause number. For other charges, do not use.
Total dollar amount for the allowance or charge.
- If ITA07 is present with either ITA06 or ITA08, then ITA07 takes precedence.
A free-form description to clarify the related data elements and their content.
For FCA US Clause Code (ITA05), enter 'CLAUSE'.
Example: HL32~O
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments.
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure.
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment, and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to.
- HL02 identifies the Hierarchical ID Number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure.
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order or item level information.
- O
- Order
Code indicating whether if there are hierarchical child data segments subordinate to the level being described.
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Item Identification
To specify basic item identification data.
There should be one LIN segment in each Order level. The LIN segment is used to identify the buyer's number or returnable container part number and to cross-reference parts to returnable containers.
If a returnable container is used, the Container Part number is required in the LIN segment for the released part, as well as in an additional LIN segment in its own Order level.
Clarification on the specification of part number:
When FCA US issues the ASN:
- BP = Customer part number
- VP = FCA US part number
When FCA US receives the ASN:
- BP = FCA US part number
- VP = Supplier part number
Examples:
LINBPBP05761192AAEC~REL (Part Number only)
LIN05761192AAECRELRC0000CC10 (Part Number with Returnable Container)0000CC10 (Returnable Container Part Number)
LIN~~RC
LINBPBP03486285AAVP~ALY185B (Acustar Electronics Part Number)
LIN02802752AAEC2VO24901 (Primary Metals)02802752AA
LIN~~BPVO24901 (Commodity Procurement Program)
LIN~~BP~M04799198V (MMMA)
Mopar Consignee only:
LINVPVP05761192AAEC~REL (Part Number only)
LIN05761192AAECRELRC~0000CC10 (Part Number with Returnable Container)
Global Core Return only:
LIN~~BP~U5761192 (Part Number only)
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- LIN02 through LIN31 provide for fifteen (15) different product/service ID's for each item. For Example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU.
- If LIN06 is present, then LIN07 is required.
- BP
- Buyer's Part Number
The FCA US released part number found on the Material Release.
- RC
- Returnable Container No.
- VP
- Vendor's (Seller's) Part Number
For Mopar Consignee only.
Identifying number for a product or service.
- If LIN08 is present, then LIN09 is required.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- If LIN10 is present, then LIN11 is required.
- EC
- Engineering Change Level
Engineering Change Level required for production parts.
Primary Metals use: 'EC' = Engineering Control (Metal Specification Suffix).
- VO
- Vendor's Order Number
Primary Metals and Commodity Procurement Program use: Vendor (Mill) Order.
- VP
- Vendor's (Seller's) Part Number
For Huntsville Electronics use.
Identifying number for a product or service.
- If LIN12 is present, then LIN13 is required.
FCA US requires 1 to 3 characters for Engineering Change Level (check with your Engineering dept.).
Vendor Part Number may be up to 30 characters.
Primary Metals use:
Metal Specification Suffix requires 1 character.
Primary Metals and Commodity Procurement Program use:
Vendor (Mill) Order Number requires 5 characters.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- If LIN14 is present, then LIN15 is required.
- RC
- Returnable Container No.
Used only if LIN02 is 'BP' or 'VP' (Mopar Consignee only) and part is shipped in returnable container.
(A separate LIN segment in another Order level for returnable container tracking is also required.)
- VO
- Vendor's Order Number
Item Detail (Shipment)
To specify line item detail relative to shipment
Used to show quantity being shipped, unit of measure, and YTD cum shipped (adjusted for receiving discrepancies and returned material). Required at the Item level for Primary Metals and Commodity Procurement Program. Required at the Item Level for Containers. Required at the Order level for all other materials.
Examples:
SN13294942300EA90097
SN124 (Primary Metals and Commodity Procurement - Order level)UN (Service & Parts-Dealer Direct)
SN1~~2
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set.
Quantity shipped for the released part or returnable container part number referenced in the associated LIN segment.
Primary Metals, Commodity Procurement Program, use: Theoretical and Actual Pounds Shipped.
Code identifying the basic unit of measurement.
- SN103 defines the unit of measurement for both SN102 and SN104.
Purchased parts unit of measure as shown on the FCA US Material Release.
- 01
- Actual Pounds
- 24
- Theoretical Pounds
- CW
- Hundred Pounds (CWT)
For Commodity Procurement Only
- EA
- Each
For Commodity Procurement Only
- FT
- Foot
For Commodity Procurement Only
- HF
- Hundred Feet
For Commodity Procurement Only
- KG
- Kilogram
For Commodity Procurement Only
- PC
- Piece
For Commodity Procurement Only
- TO
- Troy Ounce
- UN
- Unit
Number of units shipped to date.
Cumulative net quantity to Date shipped for the current model year, including the quantity in SN102.
Not used by Primary Metals, Service & Parts-Dealer Direct, Commodity Procurement Program, Global Core Return System and Container Management System.
Quantity ordered.
Mopar Supplier Ship Direct only.
Purchase Order Reference
To provide reference to a specific purchase order
Used to show FCA US Purchase Order number and amendments.
Examples:
PRFPR517243AA00145447~~~~~VS800001 (Mopar Supplier Ship Direct)
PRF
Identifying number for Purchase Order assigned by the orderer/purchaser.
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction.
Primary Metals use: Steel Release Number.
Product/Item Description
To describe a product or process in coded or free-form format
Used by Mopar Supplier Ship Direct only to specify vehicle identification number, mileage and in-service date.
Example: PID~F~~~~1P3XP48KXNN137402 045405 92167
Code indicating the format of a description.
- When PID01 is ``F'', PID04 is not used.
Reference Numbers
To specify identifying numbers.
Although the standard allows up to 30 characters in reference numbers, FCA US processes only the first 16. Sending more than 16 characters in Bill of Lading numbers, Packing Slip numbers or Freight Bill numbers may result in ASNs being rejected as duplicates if the first 16 characters match a previously used reference number.
When parts on a single trailer are destined for multiple destinations and will pass through a consolidation center, OR where the transportation mode is Geographic Receiving, a Master Bill of Lading must be created. The Master Bill of Lading number must be in a REF segment at the Shipment level. Detail Bill of Lading numbers are also required and must appear in REF segments at the Order level.
If there is more than one Packing Slip for a shipment, the REF segment is required at the Order level for each part number. Do not use more than 16 characters for the Packing Slip.
A Packing Slip Number cannot be duplicated within a twelve month period.
A Bill of Lading Number cannot be duplicated within a twelve month period
All cancellations (BSN01 = '01'), whether for line items or the entire ASN, require at least the following REF segments:
One at the Shipment level with the Bill of Lading number from the original ASN.
One at the Shipment level if only one Packing Slip applies to the entire shipment. If there is more than one Packing Slip for a shipment, a REF segment is required at the Order level for each part number.
For Global Core Return System, two REF segments shall be used. The first shall have a qualifier of 'BM' in REF01 for the core return control number. The second shall have a qualifier of '8X' to convey the claim type: warranty ('W') or Mopar ('M') .
Examples:
REFBM7374288
REFPK34911
REFSV12345678 CG (Mopar Shipper, Space, Service Level)
Code qualifying the Reference Number.
- 8X
- Transaction Category or Type
- BM
- Bill of Lading Number
- LI
- Line Item Identifier (Seller's)
For Memphis Core Center only.
- MY
- Model year number
- PK
- Packing List Number
- RE
- Release Number
RAN for MMMA
- SV
- Service Charge Number
For Mopar SSD only.
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
If REF01 = '8X', the Claim Type for Global Core Return System.
If REF01 = 'LI', the line item number from the Material Release (for Memphis Core Center only).
If REF01 = 'SV', the Mopar Shipper number and parcel shipping service level code.
If shipping mode is LTL, provide Mopar Shipper number only. (for Mopar SSD only).
NOTE: The same Bill of Lading and Packing Slip number cannot be reused during the same twelve month period. The FCA US system will reject these as duplicates.
Name
To identify a party by type of organization, name and code
Two N1 segments are used at the Order level for a particular part number if the shipment is going to multiple destinations. The Ship To and Ultimate Destination N1 segments are put in the Order Level with the appropriate part shown in the LIN segment.
Use 'MA' for the FCA US receiving plant code of the ultimate destination, even if same as 'ST'.
These codes should echo the codes in the N1 segments in the heading and detail areas of the Material Release (830). If the codes are not correct on the Release, contact your buyer.
Example: N1MA~~9204025
Code identifying an organizational entity or a physical location.
- At least one of N102 or N103 must be present.
- MA
- Party for whom Item is Ultimately Intended
FCA US Plant
Code designating the system/method of code structure used for Identification Code (67).
- 92
- Assigned by Buyer
Code identifying a party.
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Use the FCA US assigned ultimate destination receiving plant code.
Reference Numbers
To specify identifying numbers.
Used in conjunction with the Ultimate Receiving ('MA') location in the N1 loop to identify FCA US receiving plant dock code as shown on the FCA US Material Release.
Example: REFDKCD3
Code qualifying the Reference Number.
- DK
- Dock Number
Name
To identify a party by type of organization, name and code
Two N1 segments are used at the Order level for a particular part number if the shipment is going to multiple destinations. The Ship To and Ultimate Destination N1 segments are put in the Order Level with the appropriate part shown in the LIN segment.
Use 'ST' for the actual Ship To location specified on the Material Release.
These codes should echo the codes in the N1 segments in the heading and detail areas of the Material Release (830). If the codes are not correct on the Release, contact your buyer.
Example: N1ST~~9274724AB
Code identifying an organizational entity or a physical location.
- At least one of N102 or N103 must be present.
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67).
- 92
- Assigned by Buyer
Code identifying a party.
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Use the FCA US assigned receiving plant code or the supplier code of the actual Ship To location.
Allowance, Charge or Service
To specify allowances, charges or services
To specify allowances or charges for ERS productive material only. This segment is used in the Order level to bill for charges associated with clauses or supplier-paid transportation for a specific part number. All charges must be related to a provision in the FCA US Purchase Order. Either ITA05 or ITA14 is required.
FCA US allows up to three ITA segments per Order level. If more than three occurrences are needed, contact Corporate Accounts Payable for instructions.
To bill FCA US for supplier-paid transportation, the value 'E' must be in the transportation code of the FCA US Purchase Order.
The Allowance or Charge Total Amount element (ITA07) is in the N2 format which calls for numeric data with 2 implied decimal points. If the charge or allowance is $100.00, the amount would be transmitted as '10000' (the decimal point is not transmitted).
Examples:
ITAC~~~06023A~~54321~~~~~~CLAUSE (PO clause)
ITA~C~~~06~~~3500~~~~~~~TTB (transportation)
Code which indicates an allowance or charge for the service specified.
Code indicating method of handling for an allowance or charge.
- 04
- Credit Customer Account
If ITA01 = 'A', use '04'.
- 06
- Charge to be Paid by Customer
If ITA01 = 'C', use '06'.
The number assigned by a vendor referencing an allowance, promotion, deal or charge.
If the additional charge is based on a clause in the FCA US Purchase Order, use the clause number. For other charges, do not use.
Total dollar amount for the allowance or charge.
- If ITA07 is present with either ITA06 or ITA08, then ITA07 takes precedence.
A free-form description to clarify the related data elements and their content.
For FCA US Clause Code (ITA05), enter 'CLAUSE'.
The Item level is only used for Primary Metals and Commodity Procurement Program.
Example: HL43~I
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments.
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure.
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment, and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to.
- HL02 identifies the Hierarchical ID Number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure.
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order or item level information.
- I
- Item
Code indicating whether if there are hierarchical child data segments subordinate to the level being described.
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
Item Detail (Shipment)
To specify line item detail relative to shipment
Used to show quantity being shipped, unit of measure, and YTD cum shipped (adjusted for receiving discrepancies and returned material). Required at the Item level for Primary Metals and the Commodity Procurement Program. Required at the Order level for all other materials.
Example: SN1~~1~CX
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set.
For Primary Metals and Steel Procurement Program use: Number of coils shipped.
For Resin Procurement Program: Number of lots shipped.
Measurements
To specify physical measurements, including dimensions, tolerances, weights and counts.
Primary Metals uses MEA segments at the Item level for actual weight and theoretical weight of material shipped. On a shipment for an item sold on a theoretical weight basis, two MEAs will be sent: one for the actual pounds and one for the theoretical pounds. On a shipment for an item sold on an actual weight basis, only one occurrence of the MEA will be sent for the actual pounds shipped.
The Commodity Procurement Program uses MEA segments at the Item level for actual weight and theoretical weight of material shipped. For Steel Procurement, both actual and theoretical weights are required. For Resin Procurement, only actual weight is required.
Weight must be whole numbers. No decimal are allowed.
Examples:
MEAPDWT3050001
MEAPDWT3050024
Code specifying the application of physical measurement cited.
- PD
- Physical Dimensions (Product Ordered)
Code identifying the type of measurement.
- WT
- Weight
The value of the measurement.
- Either MEA03 or MEA05 or MEA06 or MEA08 is required.
- If either MEA03, MEA05 or MEA06 is used, MEA04 is required.
Weight must be whole numbers. No decimal are allowed.
Code identifying the basic unit of measurement.
'01' and '24' are for Primary Metals and Commodity Procurement use. Rest of the codes are for Commodity Procurment only.
- 01
- Actual Pounds
- 24
- Theoretical Pounds
- CW
- Hundred Pounds (CWT)
- EA
- Each
- FT
- Foot
- HF
- Hundred Feet
- KG
- Kilogram
- PC
- Piece
Reference Numbers
To specify identifying numbers.
Although the standard allows up to 30 characters in reference numbers, FCA US processes only the first 16. Sending more than 16 characters in Shipper's Identification (SID) numbers, Bill of Lading numbers, Packing Slip numbers or Freight Bill numbers may result in ASNs' being rejected as duplicates if the first 16 characters match a previously used reference number.
The REF segment(s) is required at the Item level for Primary Metals and Commodity Procurement Program.
Examples:
REFHC611X035
REFLS015465138751875
REFLTA5320
Code qualifying the Reference Number.
- HC
- Heat Code
Primary Metals and Steel Procurement use.
For Resin Procurement
- LS
- Bar-Coded Serial Number
Primary Metals and Steel Procurement use.
For Resin Procurement
- LT
- Lot Number
For Resin Procurement
The Tare level is only used for Service & Parts Division when a container is controlled by a Master or Mixed Load Bar-coded Label.
Example: HL21~T
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments.
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure.
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment, and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to.
- HL02 identifies the Hierarchical ID Number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure.
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order or item level information.
- T
- Shipping Tare
Code indicating whether if there are hierarchical child data segments subordinate to the level being described.
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Reference Numbers
To specify identifying numbers.
The Mixed Load/Master Label Serial Number cannot be duplicated within a twelve-month period.
Examples:
REFLSG00006312
REFLSM00001234
Code qualifying the Reference Number.
- LS
- Bar-Coded Serial Number
Example: HL32~O
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments.
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure.
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment, and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to.
- HL02 identifies the Hierarchical ID Number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure.
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order or item level information.
- O
- Order
Code indicating whether if there are hierarchical child data segments subordinate to the level being described.
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
Item Identification
To specify basic item identification data.
There should be one LIN segment in each Order level. The LIN segment is used to identify the buyer's number or returnable container part number and to cross-reference parts to returnable containers.
If a returnable container is used, the Container Part number is required in the LIN segment for the released part, as well as in an additional LIN segment in its own Order level.
Clarification on the specification of part number:
When FCA US issues the ASN:
- BP = Customer part number
- VP = FCA US part number
When FCA US receives the ASN:
- BP = FCA US part number
- VP = Supplier part number
Examples:
LINBPBP05761192AAEC~REL (Part Number only)
LIN05761192AAECRELRC0000CC10 (Part Number with Returnable Container)0000CC10 (Returnable Container Part Number)
LIN~~RC
LINBPBP03486285AAVP~ALY185B (Acustar Electronics Part Number)
LIN02802752AAEC2VO24901 (Primary Metals)02802752AA
LIN~~BPVO24901 (Commodity Procurement Program)
LIN~~BP~M04799198V (MMMA)
Mopar Consignee only:
LINVPVP05761192AAEC~REL (Part Number only)
LIN05761192AAECRELRC~0000CC10 (Part Number with Returnable Container)
Global Core Return only:
LIN~~BP~U5761192 (Part Number only)
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- LIN02 through LIN31 provide for fifteen (15) different product/service ID's for each item. For Example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU.
- If LIN06 is present, then LIN07 is required.
- BP
- Buyer's Part Number
The FCA US released part number found on the Material Release.
- RC
- Returnable Container No.
- VP
- Vendor's (Seller's) Part Number
For Mopar Consignee only.
Identifying number for a product or service.
- If LIN08 is present, then LIN09 is required.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- If LIN10 is present, then LIN11 is required.
- EC
- Engineering Change Level
Engineering Change Level required for production parts.
Primary Metals use: 'EC' = Engineering Control (Metal Specification Suffix).
- VO
- Vendor's Order Number
Primary Metals and Commodity Procurement Program use: Vendor (Mill) Order.
- VP
- Vendor's (Seller's) Part Number
For Huntsville Electronics use.
Identifying number for a product or service.
- If LIN12 is present, then LIN13 is required.
FCA US requires 1 to 3 characters for Engineering Change Level (check with your Engineering dept.).
Vendor Part Number may be up to 30 characters.
Primary Metals use:
Metal Specification Suffix requires 1 character.
Primary Metals and Commodity Procurement Program use:
Vendor (Mill) Order Number requires 5 characters.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- If LIN14 is present, then LIN15 is required.
- RC
- Returnable Container No.
Used only if LIN02 is 'BP' or 'VP' (Mopar Consignee only) and part is shipped in returnable container.
(A separate LIN segment in another Order level for returnable container tracking is also required.)
- VO
- Vendor's Order Number
Item Detail (Shipment)
To specify line item detail relative to shipment
Used to show quantity being shipped, unit of measure, and YTD cum shipped (adjusted for receiving discrepancies and returned material). Required at the Item level for Primary Metals and Commodity Procurement Program. Required at the Item Level for Containers. Required at the Order level for all other materials.
Examples:
SN13294942300EA90097
SN124 (Primary Metals and Commodity Procurement - Order level)UN (Service & Parts-Dealer Direct)
SN1~~2
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set.
Quantity shipped for the released part or returnable container part number referenced in the associated LIN segment.
Primary Metals, Commodity Procurement Program, use: Theoretical and Actual Pounds Shipped.
Code identifying the basic unit of measurement.
- SN103 defines the unit of measurement for both SN102 and SN104.
Purchased parts unit of measure as shown on the FCA US Material Release.
- 01
- Actual Pounds
- CW
- Hundred Pounds (CWT)
For Commodity Procurement Only
- EA
- Each
For Commodity Procurement Only
- FT
- Foot
For Commodity Procurement Only
- HF
- Hundred Feet
For Commodity Procurement Only
- KG
- Kilogram
For Commodity Procurement Only
- PC
- Piece
For Commodity Procurement Only
- UN
- Unit
Number of units shipped to date.
Cumulative net quantity to Date shipped for the current model year, including the quantity in SN102.
Not used by Primary Metals, Service & Parts-Dealer Direct, Commodity Procurement Program, Global Core Return System and Container Management System.
Quantity ordered.
Mopar Supplier Ship Direct only.
Purchase Order Reference
To provide reference to a specific purchase order
Used to show FCA US Purchase Order number and amendments.
Examples:
PRFPR517243AA00145447~~~~~VS800001 (Mopar Supplier Ship Direct)
PRF
Identifying number for Purchase Order assigned by the orderer/purchaser.
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction.
Primary Metals use: Steel Release Number.
Product/Item Description
To describe a product or process in coded or free-form format
Used by Mopar Supplier Ship Direct only to specify vehicle identification number, mileage and in-service date.
Example: PID~F~~~~1P3XP48KXNN137402 045405 92167
Code indicating the format of a description.
- When PID01 is ``F'', PID04 is not used.
Reference Numbers
To specify identifying numbers.
Although the standard allows up to 30 characters in reference numbers, FCA US processes only the first 16. Sending more than 16 characters in Bill of Lading numbers, Packing Slip numbers or Freight Bill numbers may result in ASNs being rejected as duplicates if the first 16 characters match a previously used reference number.
When parts on a single trailer are destined for multiple destinations and will pass through a consolidation center, OR where the transportation mode is Geographic Receiving, a Master Bill of Lading must be created. The Master Bill of Lading number must be in a REF segment at the Shipment level. Detail Bill of Lading numbers are also required and must appear in REF segments at the Order level.
If there is more than one Packing Slip for a shipment, the REF segment is required at the Order level for each part number. Do not use more than 16 characters for the Packing Slip.
A Packing Slip Number cannot be duplicated within a twelve month period.
A Bill of Lading Number cannot be duplicated within a twelve month period
All cancellations (BSN01 = '01'), whether for line items or the entire ASN, require at least the following REF segments:
One at the Shipment level with the Bill of Lading number from the original ASN.
One at the Shipment level if only one Packing Slip applies to the entire shipment. If there is more than one Packing Slip for a shipment, a REF segment is required at the Order level for each part number.
For Global Core Return System, two REF segments shall be used. The first shall have a qualifier of 'BM' in REF01 for the core return control number. The second shall have a qualifier of '8X' to convey the claim type: warranty ('W') or Mopar ('M') .
Examples:
REFBM7374288
REFPK34911
REFSV12345678 CG (Mopar Shipper, Space, Service Level)
Code qualifying the Reference Number.
- 8X
- Transaction Category or Type
- BM
- Bill of Lading Number
For Memphis Core Center only.
- LI
- Line Item Identifier (Seller's)
- MY
- Model year number
- PK
- Packing List Number
- RE
- Release Number
RAN for MMMA
- SV
- Service Charge Number
For Mopar SSD only.
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
If REF01 = '8X', the Claim Type for Global Core Return System.
If REF01 = 'LI', the line item number from the Material Release (for Memphis Core Center only).
If REF01 = 'SV', the Mopar Shipper number and parcel shipping service level code.
If shipping mode is LTL, provide Mopar Shipper number only. (for Mopar SSD only).
NOTE: The same Bill of Lading and Packing Slip number cannot be reused during the same twelve month period. The FCA US system will reject these as duplicates.
Name
To identify a party by type of organization, name and code
Two N1 segments are used at the Order level for a particular part number if the shipment is going to multiple destinations. The Ship To and Ultimate Destination N1 segments are put in the Order Level with the appropriate part shown in the LIN segment.
Use 'MA' for the FCA US receiving plant code of the ultimate destination, even if same as 'ST'.
These codes should echo the codes in the N1 segments in the heading and detail areas of the Material Release (830). If the codes are not correct on the Release, contact your buyer.
Example: N1MA~~9204025
Code identifying an organizational entity or a physical location.
- At least one of N102 or N103 must be present.
- MA
- Party for whom Item is Ultimately Intended
FCA US Plant
Code designating the system/method of code structure used for Identification Code (67).
- 92
- Assigned by Buyer
Code identifying a party.
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Use the FCA US assigned ultimate destination receiving plant code.
Reference Numbers
To specify identifying numbers.
Used in conjunction with the Ultimate Receiving ('MA') location in the N1 loop to identify FCA US receiving plant dock code as shown on the FCA US Material Release.
Example: REFDKCD3
Code qualifying the Reference Number.
- DK
- Dock Number
Name
To identify a party by type of organization, name and code
Two N1 segments are used at the Order level for a particular part number if the shipment is going to multiple destinations. The Ship To and Ultimate Destination N1 segments are put in the Order Level with the appropriate part shown in the LIN segment.
Use 'ST' for the actual Ship To location specified on the Material Release.
These codes should echo the codes in the N1 segments in the heading and detail areas of the Material Release (830). If the codes are not correct on the Release, contact your buyer.
Example: N1ST~~9274724AB
Code identifying an organizational entity or a physical location.
- At least one of N102 or N103 must be present.
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67).
- 92
- Assigned by Buyer
Code identifying a party.
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Use the FCA US assigned receiving plant code or the supplier code of the actual Ship To location.
Allowance, Charge or Service
To specify allowances, charges or services
To specify allowances or charges for ERS productive material only. This segment is used in the Order level to bill for charges associated with clauses or supplier-paid transportation for a specific part number. All charges must be related to a provision in the FCA US Purchase Order. Either ITA05 or ITA14 is required.
FCA US allows up to three ITA segments per Order level. If more than three occurrences are needed, contact Corporate Accounts Payable for instructions.
To bill FCA US for supplier-paid transportation, the value 'E' must be in the transportation code of the FCA US Purchase Order.
The Allowance or Charge Total Amount element (ITA07) is in the N2 format which calls for numeric data with 2 implied decimal points. If the charge or allowance is $100.00, the amount would be transmitted as '10000' (the decimal point is not transmitted).
Examples:
ITAC~~~06023A~~54321~~~~~~CLAUSE (PO clause)
ITA~C~~~06~~~3500~~~~~~~TTB (transportation)
Code which indicates an allowance or charge for the service specified.
Code indicating method of handling for an allowance or charge.
- 04
- Credit Customer Account
If ITA01 = 'A', use '04'.
- 06
- Charge to be Paid by Customer
If ITA01 = 'C', use '06'.
The number assigned by a vendor referencing an allowance, promotion, deal or charge.
If the additional charge is based on a clause in the FCA US Purchase Order, use the clause number. For other charges, do not use.
Total dollar amount for the allowance or charge.
- If ITA07 is present with either ITA06 or ITA08, then ITA07 takes precedence.
A free-form description to clarify the related data elements and their content.
For FCA US Clause Code (ITA05), enter 'CLAUSE'.
Summary
Transaction Totals
To transmit a hash total for a specific element in the transaction set
- Number of line items (CTT01) is the accumulation of the number of HL segments. If used, hash total (CTT02) is the sum of the value of units shipped (SN102) for each SN1 segment.
Example: CTT~4
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).
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.
Cancellation and Retransmission of a Line Item
GS*SH*SENDERGS*RECEIVERGS*240810*213751*000000001*X*002040CHRY~
ST*856*0009~
BSN*01*1388*090923*1510~
DTM*011*090923*1500*ET~
HL*1**S~
MEA*PD*G*1200*LB~
MEA*PD*N*1050*LB~
TD1*CTN25*6~
TD5*B*2*CETR*LT~
TD3*TL**2834~
REF*BM*3137~
REF*PK*428355~
N1*SU**92*41241AA~
N1*SF**92*91444AB~
N1*ST**92*04025~
N1*MA**92*04025~
HL*2*1*O~
LIN**BP*0B237MB5AA*EC*REL~
SN1**100*EA*3400~
PRF*BB284144GA~
CTT*2~
SE*21*0009~
ST*856*00091~
BSN*00*1389*090923*1510~
DTM*011*090923*1500*ET~
HL*1**S~
MEA*PD*G*1200*LB~
MEA*PD*N*1050*LB~
TD1*CTN25*6~
TD5*B*2*CETR*LT~
TD3*TL**2834~
REF*BM*3137~
REF*PK*428355~
N1*SU**92*41241AA~
N1*SF**92*91444AB~
N1*ST**92*04025~
N1*MA**92*04025~
HL*2*1*O~
LIN**BP*0B237MB5AA*EC*REL~
SN1**50*EA*3350~
PRF*BB284144GA~
CTT*2~
SE*21*00091~
GE*2*000000001~
IEA*1*000000001~
Sample 1
GS~SH~61994~04000~240116~1903~76330~X~002040CHRY*
ST~856~76328*
BSN~00~0007434439~240116~1903*
DTM~011~240116~1903~ET*
HL~1~~S*
MEA~PD~G~13~LB*
MEA~PD~N~10.4~LB*
TD1~CTN25~1*
TD5~B~2~UPSG~M*
TD3~TL~~12345*
REF~BM~000000191361314*
REF~MB~1Z5212W00300939477*
REF~PK~0349979800*
N1~ST~~92~60779*
N1~SU~~92~61994*
N1~SF~~92~61994*
N1~BT~~92~03103*
HL~2~1~O*
LIN~~BP~123220RR*
SN1~~1~EA~1~~EA*
PRF~20216265~~~~~26352362*
PID~F~~~~LIGHT BAR TEX BLACK 07-11*
CTT~2*
SE~23~76328*
GE~1~76330*
IEA~1~000076329*
Sample 10
GS*SH*SENDERGS*RECEIVERGS*240810*222131*000000001*X*002040CHRY~
ST*856*0002~
BSN*00*28345*090912*0931~
DTM*011*090912*0931*ET~
HL*1**S~
MEA*PD*G*7880*LB~
MEA*PD*N*6240*LB~
TD1*MIX90*4~
TD5*B*2*CETR*LT***PP*01123~
TD3*TL**4381~
REF*MB*48335~
N1*SU**92*11282AA~
N1*SF**92*11282EE~
HL*2*1*O~
LIN**BP*05286221AA*EC*REL*RC*0000CC10~
SN1**450*EA*2680~
PRF*FR218721BX~
REF*BM*48336~
REF*PK*81336~
N1*ST**92*04015~
N1*MA**92*04015~
HL*3*1*O~
LIN**BP*03245554AA*EC*F*RC*0000CC3A~
SN1**220*EA*8370~
PRF*ME218895XA~
REF*BM*48337~
REF*PK*81337~
N1*ST**92*04012~
N1*MA**92*04012~
REF*DK*AUX~
HL*4*1*O~
LIN**BP*00133671AA*EC*REL*RC*0CC00090~
SN1**650*EA*14500~
PRF*EB432228F~
REF*BM*48337~
REF*PK*81337~
N1*ST**92*04012~
N1*MA**92*04012~
REF*DK*MAIN~
HL*5*1*O~
LIN**BP*04282338AA*EC*B*RC*0000CC3A~
SN1**300*EA*2140~
PRF*RR289341X~
REF*BM*48338~
REF*PK*81338~
N1*ST**92*04070~
N1*MA**92*04070~
HL*6*1*O~
LIN**RC*0000CC10~
SN1**1*EA*81~
REF*BM*48336~
REF*PK*81336~
N1*ST**92*04015~
N1*MA**92*04015~
HL*7*1*O~
LIN**RC*0000CC3A~
SN1**1*EA*97~
REF*BM*48337~
REF*PK*81337~
N1*ST**92*04012~
N1*MA**92*04012~
REF*DK*AUX~
HL*8*1*O~
LIN**RC*0CC00090~
SN1**1*EA*44~
REF*BM*48337~
REF*PK*81337~
N1*ST**92*04012~
N1*MA**92*04012~
REF*DK*MAIN~
HL*9*1*O~
LIN**RC*0000CC3A~
SN1**1*EA*16~
REF*BM*48338~
REF*PK*81338~
N1*ST**92*04070~
N1*MA**92*04070~
CTT*9~
SE*78*0002~
ST*856*0028~
BSN*00*22833*140221*1200~
DTM*011*140221*1200*ET~
HL*1**S~
MEA*PD*G*1400*LB~
MEA*PD*N*1200*LB~
TD1*CTN71*1~
TD5*B*2*JTRC*LT~
TD3*TL**8451~
REF*BM*9890067~
REF*PK*9890067~
N1*SF**92*54547~
N1*ST**92*58179B~
HL*2*1*O~
LIN**BP*UF0480964A~
SN1**75*EA~
REF*LI*001~
CTT*2~
SE*19*0028~
ST*856*0029~
BSN*00*654982*141118*1200~
DTM*011*141118*1200*ET~
HL*1**S~
MEA*PD*G*3000*LB~
MEA*PD*N*3000*LB~
TD1*MIX90*550~
TD5*B*2*LSLG*LT~
TD3*TL**10555888~
REF*BM*654982~
REF*PK*654982~
N1*SU**92*99999~
N1*SF**92*99999~
N1*ST**92*06203~
N1*MA**92*06203~
HL*2*1*O~
LIN**RC*CT121509~
SN1**500*EA*1250~
PRF*A999444AA~
HL*3*1*O~
LIN**RC*CP4845SP~
SN1**20*EA*300~
PRF*A999444AA~
HL*4*1*O~
LIN**RC*CP4845VL~
SN1**20*EA*250~
PRF*A999444AA~
CTT*4~
SE*29*0029~
GE*3*000000001~
IEA*1*000000001~
Sample 11
GS*SH*SENDERGS*RECEIVERGS*240810*223007*000000001*X*002040CHRY~
ST*856*0003~
BSN*00*28179*090914*1600~
DTM*011*090914*1600*CT~
HL*1**S~
MEA*PD*G*22520*LB~
MEA*PD*N*20335*LB~
TD1*MIX90*16~
TD5*B*2*YFSY*M~
TD3*TL**8733~
REF*BM*432278~
REF*PK*891141~
REF*SN*00003781~
N1*SU**92*78445AA~
N1*SF**92*78445RR~
N1*ST**92*09103~
N1*MA**92*09103~
HL*2*1*O~
LIN**BP*0B244MA6AA*EC*REL~
SN1**600*EA*3680~
PRF*FR218721BX~
HL*3*1*O~
LIN**BP*0B245MA6AA*EC*F~
SN1**600*EA*3570~
PRF*ME218895XA~
HL*4*1*O~
LIN**BP*04831231AA*EC*REL~
SN1**900*EA*22340~
PRF*EB432228F~
HL*5*1*O~
LIN**BP*05122234AA*EC*B*RC*0000CC3A~
SN1**200*EA*6163~
PRF*RR289341X~
HL*6*1*O~
LIN**BP*00133671AA*EC*REL*RC*0CC00090~
SN1**400*EA*21230~
PRF*AL218681R~
HL*7*1*O~
LIN**RC*0000CC3A~
SN1**2*EA*43~
HL*8*1*O~
LIN**RC*0CC00090~
SN1**1*EA*61~
CTT*8~
SE*44*0003~
ST*856*0030~
BSN*00*17282933*141215*1900~
DTM*011*141215*1900*ET~
HL*1**S~
MEA*PD*G*6307*LB~
MEA*PD*N*5165*LB~
TD1*RCK52*13~
TD5*B*2*MAEU*AE***PP*00187~
TD3*AF*UX*738~
REF*BM*17231311~
REF*PK*17231311~
N1*SU**92*52743~
N1*SF**92*52743A~
N1*ST**92*04015C~
N1*MA**92*04015~
ETD*ZZ*S*AE*SR23498R~
HL*2*1*O~
LIN**BP*05162008AA*EC*REL*RC*0CS08193~
SN1**78*EA*8894~
PRF*O8427111~
HL*3*1*O~
LIN**RC*0CS08193~
SN1**50*EA*1520~
CTT*3~
SE*25*0030~
ST*856*0000001~
BSN*00*CY2846853151340*081110*1335~
DTM*011*081110*1335*ET~
HL*1**S~
MEA*PD*G*385*LB~
MEA*PD*N*160*LB~
TD1*MIX90*2~
TD5*B*2*XEXL*GG***PP*00190~
TD3*TL**535555~
REF*BM*CY284685~
N1*SU**92*12345I~
N1*SF**92*12345I~
N1*ST**92*02452~
N1*MA**92*02452~
REF*DK*SD~
HL*2*1*O~
LIN**RC*00000EXP~
SN1**1*EA*31193~
REF*PK*CY284685~
HL*3*1*O~
LIN**BP*55077776AA*EC*A*RC*00000EXP~
SN1**40*EA*40~
PRF*O6524146G~
REF*PK*CY284685~
ITA*C***06*092**2010******CLAUSE~
HL*4*1*O~
LIN**RC*00000EXP~
SN1**2*EA*30185~
REF*PK*CY284686~
HL*5*1*O~
LIN**BP*55077775AB*EC*A*RC*00000EXP~
SN1**40*EA*40~
PRF*O6524146G~
REF*PK*CY284686~
ITA*C***06*092**5725******CLAUSE~
HL*6*1*O~
LIN**RC*00000EXP~
SN1**4*EA*30185~
REF*PK*CY284687~
HL*7*1*O~
LIN**BP*55077774AB*EC*A*RC*00000EXP~
SN1**40*EA*40~
PRF*O6524146G~
REF*PK*CY284687~
ITA*C***06*092**4725******CLAUSE~
HL*8*1*O~
LIN**RC*0CC00098~
SN1**1*EA*31271~
REF*PK*CY284688~
HL*9*1*O~
LIN**RC*0CC00091~
SN1**12*EA*33455~
REF*PK*CY284688~
HL*10*1*O~
LIN**BP*55077776AA*EC*A*RC*0CC00098~
SN1**40*EA*80~
PRF*O6524146G~
REF*PK*CY284688~
HL*11*1*O~
LIN**BP*55077775AB*EC*A*RC*0CC00091~
SN1**40*EA*80~
PRF*O6524146G~
REF*PK*CY284688~
HL*12*1*O~
LIN**BP*55077774AB*EC*A*RC*0CC00091~
SN1**40*EA*800~
PRF*O6524146G~
REF*PK*CY284688~
CTT*12~
SE*70*0000001~
GE*3*000000001~
IEA*1*000000001~
Sample 2
GS*SH*SENDERGS*RECEIVERGS*240810*214956*000000001*X*002040CHRY~
ST*856*0006~
BSN*00*2829334*091007*1900~
DTM*011*091007*1900*ET~
HL*1**S~
MEA*PD*G*675*LB~
MEA*PD*N*550*LB~
TD1*CTN25*3~
TD5*B*2*EAFC*AE~
TD3*TL**1821~
REF*BM*4322185~
REF*PK*58773~
N1*SU**92*48999AB~
N1*SF**92*48999CD~
N1*ST**92*04015~
N1*MA**92*04015~
ETD*ZZ*A*AE*CE23451R~
HL*2*1*O~
LIN**BP*06344287AA*EC*X*RC*00000EXP~
SN1**600*EA*8894~
PRF*PR382241AC~
HL*3*1*O~
LIN**BP*05322188AA*EC*REL*RC*00000EXP~
SN1**300*EA*5681~
PRF*PR2899311A~
HL*4*1*O~
LIN**RC*0000CC3A~
SN1**50*EA*1520~
CTT*4~
SE*29*0006~
ST*856*0012~
BSN*00*123456*081126*1424~
DTM*011*081126*1424*ET~
HL*1**S~
MEA*PD*G*65*LB~
MEA*PD*N*58*LB~
TD1*CTN25*3~
TD5*B*2*JTRC*LT~
TD3*TL**104569~
REF*BM*87654322~
REF*PK*87654322~
N1*SU**92*55101~
N1*SF**92*55101~
N1*ST**92*23031~
N1*BT**92*03103~
HL*2*1*O~
LIN**BP*56002329AA~
SN1**12*UN*12*12*UN~
PRF*00145447*****VS80001~
PID*F****1P3XP48KXNN137402 045405 92167N/L~
HL*3*1*O~
LIN**BP*56002330AA~
SN1**12*UN*12*12*UN~
PRF*00145447*****VS80001~
PID*F****1P3XP48KXTC012345 083960 93055N/L~
REF*SV*12345678 CG~
CTT*3~
SE*28*0012~
ST*856*0013~
BSN*19*123456*081126*1424~
DTM*011*081126*1424*ET~
HL*1**S~
REF*BM*87654322~
REF*PK*87654322~
N1*SU**92*55101~
N1*SF**92*55101~
N1*ST**92*02452~
N1*MA**92*02452~
HL*2*1*O~
LIN**BP*56002329AA~
SN1**0*EA*3350~
CTT*2~
SE*15*0013~
GE*3*000000001~
IEA*1*000000001~
Sample 3
GS*SH*SENDERGS*RECEIVERGS*240810*215258*000000001*X*002040CHRY~
ST*856*0010~
BSN*00*2833*090911*1200~
DTM*011*090911*1200*ET~
HL*1**S~
MEA*PD*G*1400*LB~
MEA*PD*N*1200*LB~
TD1*CTN71*1~
TD5*B*2*JTRC*LT~
TD3*TL**8451~
REF*BM*890067~
REF*PK*890067~
N1*SU**92*42332AA~
N1*SF**92*42332AF~
N1*ST**92*03118~
N1*MA**92*03118~
HL*2*1*T~
REF*LS*G13558~
HL*3*2*O~
LIN**BP*05761192AA*EC*X~
SN1**75*EA*220~
PRF*PR517243AA~
HL*4*2*O~
LIN**BP*04004819AA*EC*REL~
SN1**100*EA*340~
PRF*PR519943AA~
HL*5*2*O~
LIN**BP*05421281AA*EC*REL~
SN1**40*EA*95~
PRF*PR518321FE*****VS80001~
HL*6*2*O~
LIN**BP*04322989AA*EC*F~
SN1**30*EA*420~
PRF*PR517885XA~
CTT*6~
SE*35*0010~
ST*856*0014~
BSN*00*123456*120916*1432~
DTM*011*120916*1412*ET~
HL*1**S~
MEA*PD*G*60720*LB~
MEA*PD*N*60000*LB~
TD1*COL52*2~
TD5*B*2*RDWY*M~
TD3*TL**792~
REF*BM*726109069~
REF*PK*726109069~
N1*SU**92*93111~
N1*SF**92*74352~
N1*ST**92*42775A~
N1*BT**92*06000~
HL*2*1*O~
LIN**BP*02802752AA*VO*24901~
SN1**59350*24~
PRF*O8444001D~
HL*3*2*I~
SN1**1*CX~
MEA*PD*WT*29500*01~
MEA*PD*WT*29180*24~
REF*LS*S07309038~
HL*4*2*I~
SN1**1*CX~
MEA*PD*WT*30500*01~
MEA*PD*WT*30170*24~
REF*LS*S07309039~
CTT*4~
SE*31*0014~
ST*856*0015~
BSN*00*1387*111130*0900~
DTM*011*111130*0900*ET~
HL*1**S~
MEA*PD*G*1200*LB~
MEA*PD*N*1050*LB~
TD1*CTN25*2~
TD5*B*2*JTRC*LT*2110-11~
TD3*TL**2834~
REF*BM*3137~
REF*PK*428355~
N1*SU**92*41241AA~
N1*SF**92*41241AA~
N1*ST**92*04506~
N1*MA**92*04506~
HL*2*1*O~
LIN**BP*M04877215V~
SN1**100*EA*3400~
PRF*O8444001D~
REF*MY*3~
REF*RE*AB12345~
HL*3*1*O~
LIN**BP*M04877216V~
SN1**100*EA*3329~
PRF*O9177815A~
REF*MY*3~
REF*RE*AB12345~
CTT*3~
SE*29*0015~
GE*3*000000001~
IEA*1*000000001~
Sample 4
GS*SH*SENDERGS*RECEIVERGS*240810*215845*000000001*X*002040CHRY~
ST*856*0008~
BSN*00*1387*090923*1500~
DTM*011*090923*1500*ET~
HL*1**S~
MEA*PD*G*1200*LB~
MEA*PD*N*1050*LB~
TD1*CTN25*6~
TD5*B*2*CETR*LT~
TD3*TL**2834~
REF*BM*3137~
REF*PK*428355~
N1*SU**92*41241AA~
N1*SF**92*41241FF~
N1*ST**92*91444AB~
N1*MA**92*04025~
HL*2*1*O~
LIN**BP*0B237MB5AA*EC*REL~
SN1**100*EA*3400~
PRF*BB284144GA~
HL*3*1*O~
LIN**BP*0B237MX9AA*EC*G~
SN1**100*EA*3329~
PRF*BB284145GA~
HL*4*1*O~
LIN**BP*0B237MM4AA*EC*REL~
SN1**100*EA*3400~
PRF*BB284146GA~
CTT*4~
SE*29*0008~
ST*856*0016~
BSN*00*12345678*130303*1200~
DTM*011*130303*1200*ET~
HL*1**S~
MEA*PD*G*2600*LB~
MEA*PD*N*2100*LB~
TD1*BIN52*2~
TD5*B*2*JTRC*LT~
TD3*TL**104569~
REF*BM*12345678~
REF*PK*87654321~
N1*SU**92*42332AB~
N1*SF**92*42332AF~
N1*ST**92*04025~
N1*MA**92*04025~
REF*DK*MAIN~
HL*2*1*O~
LIN**BP*05761192AA*EC*REL*RC*0000CC3A~
SN1**525*EA*2318~
PRF*PR517243AA~
ITA*C***06***3500*******TTB~
ITA*C***06*092A**8500******CLAUSE~
HL*3*1*O~
LIN**BP*04004819AA*EC*REL*RC*0000CC3A~
SN1**600*EA*40145~
PRF*PR519943AA~
ITA*C***06*092A**13000******CLAUSE~
HL*4*1*O~
LIN**RC*0000CC3A~
SN1**2*EA*122~
CTT*4~
SE*32*0016~
ST*856*0017~
BSN*00*123456*120916*1432~
DTM*011*120916*1412*ET~
HL*1**S~
MEA*PD*G*1400*LB~
MEA*PD*N*1200*LB~
MEA*PD*G*60720*LB~
MEA*PD*N*60000*LB~
TD1*CNT90*2~
TD5*B*2*RDWY*M~
TD3*TL**792~
REF*BM*726109069~
REF*PK*726109069~
N1*SU**92*35052~
N1*SF**92*35052~
N1*ST**92*91535~
N1*BT**92*07020~
HL*2*1*O~
LIN**BP*04490184AA*VO*24901~
SN1**59350*24~
PRF*Q934600167~
HL*3*2*I~
SN1**1*LO~
MEA*PD*WT*29500*01~
MEA*PD*WT*29180*24~
REF*LT*53287C4~
HL*4*2*I~
SN1**1*LO~
MEA*PD*WT*30500*01~
MEA*PD*WT*30170*24~
REF*LT*53148B4~
CTT*4~
SE*33*0017~
GE*3*000000001~
IEA*1*000000001~
Sample 5
GS*SH*SENDERGS*RECEIVERGS*240810*220138*000000001*X*002040CHRY~
ST*856*0007~
BSN*00*193314*090922*1200~
DTM*011*090922*1200*ET~
HL*1**S~
MEA*PD*G*1200*LB~
MEA*PD*N*1050*LB~
TD1*BIN79*1~
TD5*B*2*CETR*LT~
TD3*TL**104569~
REF*BM*193314~
REF*PK*193314~
N1*SU**92*41241AA~
N1*SF**92*41241FF~
N1*ST**92*91444AB~
N1*MA**92*04025~
HL*2*1*O~
LIN**BP*04221835AA*EC*REL*RC*0000CC10~
SN1**300*EA*6800~
PRF*BB284144GA~
HL*3*1*O~
LIN**RC*0000CC10~
SN1**1*EA*35~
CTT*3~
SE*24*0007~
ST*856*0018~
BSN*00*12345678*130303*1200~
DTM*011*130303*1200*ET~
HL*1**S~
MEA*PD*G*2600*LB~
MEA*PD*N*2100*LB~
TD1*BIN52*2~
TD5*B*2*CETR*LT***PP*01112~
TD3*TL**104569~
REF*MB*0000066666~
REF*PK*87654321~
N1*SU**92*44444D~
N1*SF**92*44444D~
N1*ST**92*09106~
N1*MA**92*09106~
REF*DK*MAIN~
HL*2*1*O~
LIN**BP*05761192AA*EC*REL*RC*0000CC3A~
SN1**525*EA*2318~
PRF*PR517243AA~
HL*3*1*O~
LIN**RC*0000CC3A~
SN1**2*EA*122~
CTT*3~
SE*25*0018~
ST*856*0019~
BSN*00*12345678*130603*1200~
DTM*011*130603*1200*ET~
HL*1**S~
MEA*PD*G*2600*LB~
MEA*PD*N*2100*LB~
TD1*BIN52*2~
TD5*B*2*JTRC*LT~
TD3*TL**104569~
REF*BM*12345678~
REF*PK*87654321~
N1*SU**92*04006~
N1*SF**92*05406~
N1*ST**92*12345~
REF*DK*MAIN~
HL*2*1*O~
LIN**VP*05357477AA*EC*REL*RC*0000CC3A~
SN1**351*EA*3360~
PRF*00677642~
HL*3*1*O~
LIN**RC*0000CC3A~
SN1**2*EA*122~
CTT*3~
SE*24*0019~
GE*3*000000001~
IEA*1*000000001~
Sample 6
GS*SH*SENDERGS*RECEIVERGS*240810*220555*000000001*X*002040CHRY~
ST*856*0011~
BSN*00*123456*090316*1432~
DTM*011*090316*1412*ET~
HL*1**S~
MEA*PD*G*68240*LB~
MEA*PD*N*67500*LB~
TD1*MIX52*3~
TD5*B*2*RDWY*M~
TD3*TL**792~
REF*BM*726109069~
REF*PK*726109069~
REF*SN*0~
REF*AO*900505327~
N1*BT**92*06200~
N1*SU**92*93111~
N1*SF**92*74352~
N1*ST**92*06203~
N1*MA**92*06203~
HL*2*1*O~
LIN**BP*02802752AA*EC*2*VO*24901~
SN1**59350*24~
PRF*08444001D*34562~
HL*3*2*I~
SN1**1*CX~
MEA*PD*WT*29500*01~
MEA*PD*WT*29180*24~
REF*HC*657406~
REF*LS*S07309038~
HL*4*2*I~
SN1**1*CX~
MEA*PD*WT*30500*01~
MEA*PD*WT*30170*24~
REF*HC*657406~
REF*LS*S07309039~
HL*5*1*O~
LIN**BP*01234567AA*EC*5*VO*27368~
SN1**8150*01~
PRF*08782074*34781~
HL*6*5*I~
SN1**582*EA~
MEA*PD*WT*8150*01~
REF*HC*372154~
REF*LS*S07309067~
CTT*6~
SE*45*0011~
ST*856*0020~
BSN*00*123456*120916*1432~
DTM*011*120916*1412*ET~
HL*1**S~
MEA*PD*G*60720*KG~
MEA*PD*N*60000*KG~
TD1*CNT90*2~
TD5*B*2*RDWY*M~
TD3*TL**792~
REF*BM*726109069~
REF*PK*726109069~
N1*SU**92*35052~
N1*SF**92*35052~
N1*ST**92*91535~
N1*BT**92*07020~
HL*2*1*O~
LIN**BP*04490184AA*VO*24901~
SN1**60000*KG~
PRF*Q934600167~
HL*3*2*I~
SN1**1*LO~
MEA*PD*WT*29500*KG~
REF*LT*53287C4~
HL*4*2*I~
SN1**1*LO~
MEA*PD*WT*30500*KG~
REF*LT*53148B4~
CTT*4~
SE*29*0020~
ST*856*0021~
BSN*00*123456*120916*1432~
DTM*011*120916*1412*ET~
HL*1**S~
MEA*PD*G*60720*LB~
MEA*PD*N*60000*LB~
TD1*BAL90*2~
TD5*B*2*RDWY*M~
TD3*TL**792~
REF*BM*726109069~
REF*PK*726109069~
N1*SU**92*93111~
N1*SF**92*74352~
N1*ST**92*42775A~
N1*BT**92*06000~
HL*2*1*O~
LIN**BP*02802752AA*VO*24901~
SN1**3500*FT~
PRF*G964800123~
HL*3*2*I~
SN1**2000*FT~
REF*LS*S07309038~
HL*4*2*I~
SN1**1500*FT~
REF*LS*S07309039~
CTT*4~
SE*27*0021~
GE*3*000000001~
IEA*1*000000001~
Sample 7
GS*SH*SENDERGS*RECEIVERGS*240810*220848*000000001*X*002040CHRY~
ST*856*0004~
BSN*00*7322*090918*0700~
DTM*011*090918*0700*ET~
HL*1**S~
MEA*PD*G*45220*LB~
MEA*PD*N*40165*LB~
TD1*RCK52*12~
TD5*B*2*CR*R~
TD3*RR*GTW*104569~
REF*BM*8911124~
REF*PK*84667~
REF*SN*88271011~
REF*SN*88271012~
REF*SN*88271013~
REF*SN*88271014~
N1*SU**92*18398AA~
N1*SF**92*18398BB~
N1*ST**92*02452~
N1*MA**92*02452~
HL*2*1*O~
LIN**BP*04401461AA*EC*AC*RC*000CS132~
SN1**120*EA*4140~
PRF*PR382241AC~
HL*3*1*O~
LIN**BP*04401727AA*EC*REL*RC*000CS132~
SN1**180*EA*6229~
PRF*PR289931A~
HL*4*1*O~
LIN**BP*04401728AA*EC*G*RC*000CS132~
SN1**420*EA*9314~
PRF*PR517243G~
HL*5*1*O~
LIN**RC*000CS132~
SN1**12*EA*137~
CTT*5~
SE*36*0004~
ST*856*0022~
BSN*00*123456*120916*1432~
DTM*011*120916*1412*ET~
HL*1**S~
MEA*PD*G*60720*LB~
MEA*PD*N*60000*LB~
TD1*SKD90*2~
TD5*B*2*RDWY*M~
TD3*TL**792~
REF*BM*726109069~
REF*PK*726109069~
N1*SU**92*93111~
N1*SF**92*74352~
N1*ST**92*42775A~
N1*BT**92*06000~
HL*2*1*O~
LIN**BP*02802752AA*VO*24901~
SN1**175*PC~
PRF*G964800123~
HL*3*2*I~
SN1**100*PC~
REF*LS*S07309040~
HL*4*2*I~
SN1**75*PC~
REF*LS*S07309041~
CTT*4~
SE*27*0022~
ST*856*0023~
BSN*00*2829334*120527*1900~
DTM*011*120527*1900*ET~
HL*1**S~
MEA*PD*G*675*LB~
MEA*PD*N*550*LB~
TD1*CTN25*3~
TD5*B*2*SCNN*M~
TD3*TL**839405~
REF*BM*334322185~
REF*PK*3358773~
N1*SU**92*48999AB~
N1*SF**92*48999CD~
N1*ST**92*04015~
N1*MA**92*04015~
ETD*ZZ*Z*AE*CR2344R~
HL*2*1*O~
LIN**BP*06344287AA*EC*X~
SN1**600*EA*8894~
PRF*PR382241AC~
HL*3*1*O~
LIN**BP*05322188AA*EC*REL~
SN1**300*EA*5681~
PRF*PR2899311A~
CTT*3~
SE*26*0023~
GE*3*000000001~
IEA*1*000000001~
Sample 8
GS*SH*SENDERGS*RECEIVERGS*240810*221445*000000001*X*002040CHRY~
ST*856*0005~
BSN*00*28345*090912*0931~
DTM*011*090912*0931*ET~
HL*1**S~
MEA*PD*G*7880*LB~
MEA*PD*N*6240*LB~
TD1*MIX90*2~
TD5*B*2*CETR*GR~
TD3*TL**4381~
REF*MB*MB95053~
N1*SU**92*11282AA~
N1*SF**92*11282EE~
HL*2*1*O~
LIN**BP*05286221AA*EC*REL*RC*0000CC10~
SN1**450*EA*2680~
PRF*FR218721BX~
REF*BM*48336~
REF*PK*81336~
N1*ST**92*04025~
N1*MA**92*04025~
HL*3*1*O~
LIN**RC*0000CC10~
SN1**1*EA*22~
REF*BM*48336~
REF*PK*81336~
N1*ST**92*04025~
N1*MA**92*04025~
HL*4*1*O~
LIN**BP*03245554AA*EC*F*RC*0000CC3A~
SN1**220*EA*8370~
PRF*ME218895XA~
REF*BM*48337~
REF*PK*81337~
HL*5*1*O~
LIN**RC*0000CC3A~
SN1**1*EA*37~
REF*BM*48337~
REF*PK*81337~
N1*ST**92*04012~
N1*MA**92*04012~
REF*DK*AUX~
CTT*5~
SE*43*0005~
ST*856*0024~
BSN*00*S51-010342*120908*1900~
DTM*011*120908*1848*ET~
HL*1**S~
MEA*PD*G*4297*LB~
MEA*PD*N*4157*LB~
TD1*BOX25*2~
TD5*B*2*EXEL*M~
TD3*TL**60783~
REF*BM*0300038~
REF*PK*0300038~
N1*SU**92*43677~
N1*SF**92*03150~
N1*ST**92*43677~
N1*MA**92*43677~
HL*2*1*CN~
LIN**UF*B9842-9983~
HL*3*2*O~
LIN**BP*U4567869~
SN1**6*EA~
REF*BM*C106299171~
REF*8X*W~
HL*4*2*O~
LIN**BP*U4567870~
SN1**6*EA~
REF*BM*C106299172~
REF*8X*W~
HL*5*1*CN~
LIN**UF*B9842-9984~
HL*6*5*O~
LIN**BP*U4567888~
SN1**10*EA~
REF*BM*C106541149~
REF*8X*W~
CTT*5~
SE*36*0024~
ST*856*0025~
BSN*00*12345678*121116*1200~
DTM*011*121116*1200*ET~
HL*1**S~
MEA*PD*G*650*LB~
MEA*PD*N*580*LB~
TD1*MIX90*540~
TD5*B*2*LSLG*LT~
TD3*TL**104569~
REF*BM*12345678~
REF*PK*87654321~
N1*SU**92*99999~
N1*SF**92*99999~
N1*ST**92*42332AF~
N1*MA**92*42332AF~
N1*BT**92*08989~
HL*2*1*O~
LIN**RC*CT121509~
SN1**500*EA~
PRF*P517243AA~
HL*3*1*O~
LIN**RC*CP4845SP~
SN1**20*EA~
PRF*P517243AA~
HL*4*1*O~
LIN**RC*CP4845VL~
SN1**20*EA~
PRF*P517243AA~
CTT*4~
SE*30*0025~
GE*3*000000001~
IEA*1*000000001~
Sample 9
GS*SH*SENDERGS*RECEIVERGS*240810*221823*000000001*X*002040CHRY~
ST*856*0001~
BSN*00*12345678*090911*1200~
DTM*011*090911*1200*ET~
HL*1**S~
MEA*PD*G*2600*LB~
MEA*PD*N*2100*LB~
TD1*BIN52*2~
TD5*B*2*JTRC*LT~
TD3*TL**104569~
REF*BM*12345678~
REF*PK*87654321~
N1*SU**92*42332AB~
N1*SF**92*42332AF~
N1*ST**92*04025~
N1*MA**92*04025~
REF*DK*MAIN~
HL*2*1*O~
LIN**BP*05761192AA*EC*REL*RC*0000CC3A~
SN1**525*EA*2318~
PRF*PR517243AA~
HL*3*1*O~
LIN**BP*04004819AA*EC*REL*RC*0000CC3A~
SN1**600*EA*40145~
PRF*PR519943AA~
HL*4*1*O~
LIN**RC*0000CC3A~
SN1**2*EA*122~
CTT*4~
SE*29*0001~
ST*856*0026~
BSN*00*12346666*130114*1200~
DTM*011*130114*1200*ET~
HL*1**S~
MEA*PD*G*60720*LB~
MEA*PD*N*60000*LB~
TD1*SKD90*2~
TD5*B*2*RDWY*M~
TD3*TL**799~
REF*BM*726109888~
REF*PK*726109888~
N1*SU**92*43052~
N1*SF**92*43052~
N1*ST**92*04088~
N1*MA**92*04088~
N1*BT**92*05200~
HL*2*1*O~
LIN**BP*0XA46TL2AC~
SN1**175*PC~
CTT*2~
SE*21*0026~
ST*856*0027~
BSN*00*12347777*140624*1200~
DTM*011*140624*1200*ET~
HL*1**S~
MEA*PD*G*40720*LB~
MEA*PD*N*40000*LB~
TD1*SKD90*5~
TD5*B*2*CETR*LT~
TD3*TL**73849~
REF*BM*72837456~
REF*PK*72837456~
N1*SU**92*52938~
N1*SF**92*52938~
N1*ST**92*47959~
N1*MA**92*95042~
N1*BT**92*02000~
HL*2*1*O~
LIN**BP*0000006244~
SN1**593833.31*TO~
PRF*G398476388~
CTT*2~
SE*22*0027~
GE*3*000000001~
IEA*1*000000001~
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.