ANSI X12 - DELJIT - 862 - V4010 - O - v1.0 - 20090225
ANSI X12 - DELJIT - 862 - V4010 - O - v1.0 - 20090225
ANSI X12 - DELJIT - 862 - V4010 - O - v1.0 - 20090225
0 ANSI X12_DELJIT_862_V4010_O
Data Elements
Data elements and data segments can be classified differently in different transaction sets:
M Mandatory
O Optional
X Conditional – depends on contents of other field or condition All
data
elements are assigned minimum required and maximum permissible character lengths specified in the data element
dictionary. If a data element is transmitted, it must meet minimum/maximum length requirements, regardless of the
element’s content.
Each data element has a defined data type specified in the data element dictionary. Data types include:
ID Identification
Nn Numeric without decimal point, positive if there is not minus
R Explicit
AN Alphanumeric
DT Date
TM Time
For transmission purposes, numeric (Nn) and decimal (R) fields are assumed to be positive unless a leading minus
sign indicating a negative value is transmitted. A plus sign is never transmitted. When transmitted, the minus sign (-)
and the decimal point (data type [R]), are not counted as part of the data element’s length.
The decimal point for numeric (Nn) data types is implicitly located within the data element according to the
specified data type, but is not transmitted with the data. For example, data type N3 implies three decimal
places.
The decimal point for decimal (R) data types is explicitly located within the data element. There is no limit
on the number of fractional digits, as long as the total number of digits does not exceed the maximum
length specified.
If a data element is not transmitted, its default value cannot be assumed (e.g.,a numeric data element not
transmitted cannot be assumed to have a value of zero {0}).
Numeric and decimal data should be transmitted with only significant zeros. Alphanumeric data elements
should be transmitted with no leading or trailing blanks.
Conditional relationships within a data segment are noted and explained in the specification
Table 2: Detail
Pos. Seg. Req. Loop Notes and
Name Max. Use
No. ID Repeat Comments
LOOP ID - LIN 10000
010 LIN Item Identification M 1
020 UIT Unit Detail M 1
050 REF Reference Identification O 12
Table 3: Summary
Pos. Seg. Req. Loop Notes and
Name Max. Use
No. ID Repeat Comments
010 CTT Transaction Totals O 1
020 SE Transaction Set Trailer M 1
This code indicates the version, release and subrelease of the EDI standard
being used, including the GS and GE segments. Positions 1-3 are the version
number; positions 4-6 are the release and subrelease, level of the version
004010 Draft Standard
Segment: N1 Name
Position: 050
Loop: N1
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
Syntax Notes: 1. At least one of N102 or N104 is required
2. If either N103 or N104 is present, then the other is required
Semantic Notes:
Comments: 1. 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.
2. This N1 loop in the header area can be used to identify the shipping schedule issuer, the
supplier, and the ship-to and ship-from locations.
Example: N1*SF*ABC*92*N021~
Segment: N1 Name
Position: 050
Loop: N1
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
Syntax Notes: 1. At least one of N102 or N104 is required
2. If either N103 or N104 is present, then the other is required
Semantic Notes:
Comments: 1. 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.
2. This N1 loop in the header area can be used to identify the shipping schedule issuer, the
supplier, and the ship-to and ship-from locations.
Example: N1*ST*Kia Car Assembly*6*P001~
FST*310*P*D*20090325~ …
FST*420*P*D*20090326~
FST*310*P*D*20090329~
Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.
Alternative Proxies: