Computer Generated Solutions
/
943 Warehouse Stock Transfer Shipment Advice
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Computer Generated Solutions. Contact Computer Generated Solutions for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Computer Generated Solutions logo

X12 943 943 Warehouse Stock Transfer Shipment Advice

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Warehouse Stock Transfer Shipment Advice Transaction Set (943) for use within the context of an Electronic Data Interchange (EDI) environment.
The transaction set can be used by a depositor or an agent of the depositor to advise the recipient that a transfer shipment has been made. This transaction set provides a receiving location with detail information concerning product being shipped to that location.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
  • Sample Transaction Set (Non-prepack)
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/computer-generated-solutions/943-warehouse-stock-transfer-shipment-advice/01HJP377VWB1P47119CM9K07SM
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
W06
020
Warehouse Shipment Identification
Max use 1
Required
0100 Loop Consignee
0100 Loop Ship From
N9
090
Reference Identification Shipment Bill of Lading Number
Max use 1
Optional
N9
090
Reference Identification Vessel Number
Max use 10
Optional
G62
110
Date/Time
Max use 5
Required
NTE
120
Note/Special Instruction
Max use 20
Optional
W27
130
Carrier Detail
Max use 1
Required
W10
150
Warehouse Additional Carrier Information
Max use 1
Optional
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

U
U.S. EDI Community of ASC X12, TDCC, and UCS
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

This version number covers the interchange control segments

00401
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

>
Component Element Separator

Functional Group Header

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

AR
Warehouse Stock Transfer Shipment Advice (943)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

GS-04
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

GS-05
337
Time
Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

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
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

004010
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

Heading

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

Code uniquely identifying a Transaction Set

  • The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
943
Warehouse Stock Transfer Shipment Advice
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

W06
020
Heading > W06

Warehouse Shipment Identification

RequiredMax use 1

To provide identifying numbers, dates, and other basic data for this transaction set

Example
W06-01
514
Reporting Code
Required
Identifier (ID)

Code specifying the basis used when reporting shipment information

N
Original
W06-02
285
Depositor Order Number
Optional
String (AN)
Min 1Max 22

Identifying number for warehouse shipping order assigned by the depositor

Usage notes

Container ID (or BC Shipment ID if no container ID available)

W06-03
373
Date
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • W0603 is the actual date on which shipment was made.
Usage notes

Transmission Date

W06-04
145
Shipment Identification Number
Optional
String (AN)
Min 1Max 30

Identification number assigned to the shipment by the shipper that uniquely identifies the shipment from origin to ultimate destination and is not subject to modification; (Does not contain blanks or special characters)

Usage notes

Manufacturer/factor Assigned Shipment ID Number

W06-05
531
Agent Shipment ID Number
Optional
String (AN)
Min 1Max 12

Identification number assigned to the shipment by the agent (Number does not contain blank or punctuation characters)

Usage notes

BC assigned shipment identification number.

0100 Loop Consignee
OptionalMax 1
Variants (all may be used)
0100 Loop Ship From0100 Loop Ship To
N1
040
Heading > 0100 Loop Consignee > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Usage notes

At least 2 N1 segment/loop will be sent per transaction set to denote the ship from and ship to locations (N101 = ‘SF’ and ‘ST’). In addition, an extra N1 segment will be sent to denote the consignee for this shipment (N101 = ‘CN’).

Example
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

CN
Consignee
N1-02
93
Name
Optional
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Optional
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

  • 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.
Usage notes

This is the location code as defined by N101. For N101 = ‘CN’, N104 = Sender Assigned Ship To Customer ID.

0100 Loop Consignee end
0100 Loop Ship From
RequiredMax >1
Variants (all may be used)
0100 Loop Consignee0100 Loop Ship To
N1
040
Heading > 0100 Loop Ship From > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Usage notes

At least 2 N1 segment/loop will be sent per transaction set to denote the ship from and ship to locations (N101 = ‘SF’ and ‘ST’). In addition, an extra N1 segment will be sent to denote the consignee for this shipment (N101 = ‘CN’).

Example
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

SF
Ship From
N1-02
93
Name
Optional
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Optional
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

  • 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.
Usage notes

This is the location code as defined by N101. For N101 = ’SF’, N104 = Sender Assigned Ship From Location Code.

0100 Loop Ship From end
0100 Loop Ship To
RequiredMax 1
Variants (all may be used)
0100 Loop Consignee0100 Loop Ship From
N1
040
Heading > 0100 Loop Ship To > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Usage notes

At least 2 N1 segment/loop will be sent per transaction set to denote the ship from and ship to locations (N101 = ‘SF’ and ‘ST’). In addition, an extra N1 segment will be sent to denote the consignee for this shipment (N101 = ‘CN’).

Example
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

ST
Ship To
N1-02
93
Name
Optional
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Optional
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

  • 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.
Usage notes

This is the location code as defined by N101. For N101 = ‘ST’, N104 = Warehouse ID (assigned by our system).

0100 Loop Ship To end
N9
090
Heading > N9

Reference Identification Shipment Bill of Lading Number

OptionalMax use 1

To transmit identifying information as specified by the Reference Identification Qualifier

Usage notes

Reference numbers will be transmitted based on previous agreements between seller and shipping facility. Items transmitted must be utilized either in print or as part of picking/shipping process.

Example
N9-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

BM
Shipment Bill of Lading Number
N9-02
127
Reference Identification
Required
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

The Vessel Number the shipment is coming under or the shipment bill of
lading number depending on qualifier.

N9
090
Heading > N9

Reference Identification Vessel Number

OptionalMax use 10

To transmit identifying information as specified by the Reference Identification Qualifier

Usage notes

Reference numbers will be transmitted based on previous agreements between seller and shipping facility. Items transmitted must be utilized either in print or as part of picking/shipping process.

Example
N9-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

WU
Vessel Number
N9-02
127
Reference Identification
Required
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

The Vessel Number the shipment is coming under or the shipment bill of
lading number depending on qualifier.

G62
110
Heading > G62

Date/Time

RequiredMax use 5

To specify pertinent dates and times

Usage notes

One G62 segment will be sent to denote the estimate delivery (ETA) date.

Additional dates may be sent at a future time. Please make sure that you’re system can handle additional shipment requirement dates.

Example
G62-01
432
Date Qualifier
Required
Identifier (ID)

Code specifying type of date

17
Estimated Delivery Date
G62-02
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes

ETA Date

NTE
120
Heading > NTE

Note/Special Instruction

OptionalMax use 20

To transmit information in a free-form format, if necessary, for comment or special instruction

Usage notes

Use to relay free-form notes or messages.

Example
NTE-01
363
Note Reference Code
Optional
Identifier (ID)
Min 3Max 3

Code identifying the functional area or purpose for which the note applies

Usage notes

Codes:
WHI Warehouse Instructions
{Other} Any other previously agreed upon code

NTE-02
352
Description
Required
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

Usage notes

Free form notes/messages.

W27
130
Heading > W27

Carrier Detail

RequiredMax use 1

To specify details of the transportation equipment and carrier routing details

Usage notes

This segment will be used to transmit the transportation method/type and SCAC codes associated with this shipment.

Example
At least one of Standard Carrier Alpha Code (W27-02) or Routing (W27-03) is required
W27-01
91
Transportation Method/Type Code
Required
Identifier (ID)

Code specifying the method or type of transportation for the shipment

M
Motor (Common Carrier)
T
Best Way (Shipping Facility Option)
W27-02
140
Standard Carrier Alpha Code
Optional
Identifier (ID)
Min 2Max 4

Standard Carrier Alpha Code

  • W2702 is required when W2701 equals "B", "E", "H", "I", "K", "L", "M", "P" or "T".
Usage notes

The Standard Alpha Carrier Code of the preferred shipping facility.

W27-03
387
Routing
Optional
String (AN)
Min 1Max 35

Free-form description of the routing or requested routing for shipment, or the originating carrier's identity

Usage notes

Free-form description of the routing or requested routing for shipment, or the BC Shipper Code.

W10
150
Heading > W10

Warehouse Additional Carrier Information

OptionalMax use 1

To transmit shipping information and requirements

Usage notes

This segment will be used to transmit the Seal number related to this shipment if available.

Example
W10-04
225
Seal Number
Optional
String (AN)
Min 2Max 15

Unique number on seal used to close a shipment

Usage notes

Seal Number

Heading end

Detail

0200 Loop
RequiredMax >1
W04
020
Detail > 0200 Loop > W04

Item Detail Total

RequiredMax use 1

To designate those line items that were shipped

Usage notes

The seller’s style number and UPC or EAN will always be transmitted.

The W0402 element will identify whether the current UPC is a pre-pack UPC or a single size (open size/stock) UPC. If W0402 = ‘PK’ then the UPC is a pre-pack UPC. If W0402 = ‘EA’ then the UPC is a single size (open size/stock) UPC.

Regardless of whether W0402 is ‘EA’ or ‘PK’, the number of units shipped will ALWAYS be the total number of units. For a pre-pack this means this is NOT the total number of prepacks but rather the total number of units that would have been packed into all the pre-packs. The total number of prepacks and the number of units per pre-pack will be sent in the child W20 element (see W20 Segment below).

The W0415 value (the sender PO number) MUST be captured and sent back on the 944 when confirming actual receipts against this PO/UPC.

Example
W04-01
382
Number of Units Shipped
Required
Decimal number (R)
Min 1Max 10

Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set

Usage notes

This is the quantity of units shipped. For pre-packs this is the total number of units NOT the total number of pre-packs.

W04-02
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

EA
Each
PK
Pre-pack
W04-03
438
U.P.C. Case Code
Optional
String (AN)
Min 12Max 12

Code (Universal Product Code - U.P.C.) including two high order digits identifying the "system" (U.S. Grocery = 00, 06 or 07; U.S. Drug = 03); using the U.S. Grocery system, the next ten digits are: Manufacturer (5) Case Code (5)

Usage notes

If sent, this will be the UPC of the pre-pack that to which this component UPC belongs. This element will only be sent if this UPC is a component of a prepack.

W04-04
235
Product/Service ID Qualifier
Required
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

VN
BC Style Number
W04-05
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

Seller’s Style Number

W04-06
235
Product/Service ID Qualifier
Required
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

EN
European Article Number (EAN) (2-5-5-1)
UP
U.P.C. Consumer Package Code (1-5-5-1)
W04-07
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

Universal Product Code (UPC)
European Article Number (EAN)

W04-14
235
Product/Service ID Qualifier
Required
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

LT
PO Number
W04-15
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

The production PO number shipment is referencing.

G69
030
Detail > 0200 Loop > G69

Line Item Detail - Description

OptionalMax use 5

To describe an item in free-form format

Usage notes

Used to transmit detail level free form notes/messages.

Example
G69-01
369
Free-form Description
Required
String (AN)
Min 1Max 45

Free-form descriptive text

Usage notes

Product description or detail notes/messages.

N9
040
Detail > 0200 Loop > N9

Reference Identification

RequiredMax use 200

To transmit identifying information as specified by the Reference Identification Qualifier

Usage notes

This segment will be used to transmit additional item information. If the BC PO line number is sent it MUST be captured and returned on the corresponding 944.

Example
At least one of Reference Identification (N9-02) or Free-form Description (N9-03) is required
N9-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

97
BC Dimension Code
BL
BC Label Code
CO
Product Country of Origin
D5
BC Color Code
KZ
Ship Terms
LI
BC PO line number
LT
Contractor Lot Number
PE
Port of Exit
PR
Price (Product Cost per Unit)
SB
BC Size Bucket Code
SR
BC Size Range Code
SZ
BC Size Code
U11
BC PO Detail UDF 11
U12
BC PO Detail UDF 12
X11
BC PO Header UDF 11
X12
BC PO Header UDF 12
N9-02
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

Reference Identification
For N901=PR, this will be the amount.
For N901=KZ, this will be the BC shipment terms code.

N9-03
369
Free-form Description
Optional
String (AN)
Min 1Max 45

Free-form descriptive text

Usage notes

For N901=PR, this will be the ISO currency code.
For N902=KZ, this will be the BC shipment terms description.

W20
050
Detail > 0200 Loop > W20

Line-Item Detail - Miscellaneous

OptionalMax use 2

To specify packing details of the items shipped

Usage notes

This segment will be sent ONLY for pre-packs to specify the total number of pre-packs and the total number of units per pre-pack.

Example
If either Size (W20-02) or Unit or Basis for Measurement Code (W20-03) is present, then the other is required
W20-01
356
Pack
Optional
Numeric (N0)
Min 1Max 6

The number of inner containers, or number of eaches if there are no inner containers, per outer container

Usage notes

The number of pre-packs.

W20-02
357
Size
Optional
Decimal number (R)
Min 1Max 8

Size of supplier units in pack

Usage notes

The number of total units per pre-pack.

W20-03
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

ZZ
Mutually Defined
0200 Loop end
Detail end

Summary

W03
010
Summary > W03

Total Shipment Information

RequiredMax use 1

To provide totals relating to the shipment

Usage notes

Total stock keeping units to be shipped.

Example
W03-01
382
Number of Units Shipped
Required
Decimal number (R)
Min 1Max 10

Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set

Usage notes

Total number of units shipped in transaction.

SE
020
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

EDI Samples

Sample Transaction Set (Non-prepack)

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231207*0318*U*00401*000000001*0*T*>~
GS*AR*SENDERGS*RECEIVERGS*20231207*031849*000000001*X*004010~
ST*943*1234~
W06*N*XSN4DS4100012*20070301*5152041-03444*10042 ~
N1*SF**92*CHND1~
N1*ST**92*WH1~
N1*CN**92*023~
N9*WU*PSU28848991000~
N9*BM*09300700004282991~
G62*17*20070320~
NTE*WHI*PRODUCT EXPECTED DURING AM, EXPECTED FOR IMMEDIATE RE-SHIPMENT, 940’S~
NTE*WHI*PREVIOUSLY SENT FOR PICK RANGE 14801-14920~
W27*M*RDWY~
W10****200014880~
W04*800*EA**VN*M11M9100P*UP*737411419014*******LT*P91003~
N9*LI*01~
N9*D5*BLU~
N9*SZ*6X~
N9*SZ*4~
N9*97*32~
N9*BL*FEDERATED~
N9*U12*XYZ~
W04*1200*EA**VN*M11M9100P*UP*737411419022*******LT*P91003~
G69*CHANGE HANG TAGS TO X422l~
N9*LI*01~
N9*D5*BRN~
N9*SZ*6P~
N9*SZ*4~
N9*97*32~
N9*BL*FEDERATED~
N9*U12*NNN~
W04*800*EA**VN*M11M9100P*UP*737411419022*******LT*P91003~
N9*LI*01~
N9*D5*BLK~
N9*SZ*8R~
N9*SZ*4~
N9*97*32~
N9*BL*FEDERATED~
N9*U12*RRR~
W03*2800~
SE*39*1234~
GE*1*000000001~
IEA*1*000000001~

Sample Transaction Set (Prepack)

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231207*0318*U*00401*000000001*0*T*>~
GS*AR*SENDERGS*RECEIVERGS*20231207*031854*000000001*X*004010~
ST*943*4444~
W06*N*XSN4DS4100012*20070301*5152041-03444*10042 ~
N1*SF**92*CHND1~
N1*ST**92*WH1~
N1*CN**92*023~
N9*WU*PSU28848991000~
N9*BM*09300700004282991~
G62*17*20070320~
W27*M*RDWY~
W10****200014880~
W04*900*PK**VN*M11M9100P*UP*737411419014*******LT*P91003~
N9*LI*01~
N9*SZ*PPK~
N9*97*K21~
N9*SR*SZA~
N9*SB*1~
W20*50*18*ZZ~
W04*1200*PK**VN*M11M9100X*UP*837411419014*******LT*P91003~
N9*LI*01~
N9*SZ*PPK~
N9*97*X19~
N9*SR*SZA~
N9*SB*1~
W20*100*12*ZZ~
W03*2100~
SE*26*4444~
GE*1*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.