X12 3060 Enveloping Segments Example - BISAC X12 Version 3060
Back to EDI Cookbook Table of Contents

ISA Example
In this example the underscore '_' character is used instead of a blank space to clarify the exact length of the ISA data elements. 
Sample Segment Data
Data Elements Data Element Descriptions
ISA*00*__________*00*__________*ZZ*1135309________*ZZ*2002450________*
980319* 1430*U*00200*000000001*0*P*>~
  • ISA01 

      
  • ISA02 
     
  • ISA03 
     
  • ISA04 
  • ISA05 
      
     
  • ISA06 
  • ISA07 
     
     
  • ISA08 
  • ISA09 
     
  • ISA10 
  • ISA11 
  • ISA12 
     
  • ISA13 
     
     
     
  • ISA14 
  • ISA15 
      
  • ISA16 
      
  • 00 indicates that no authorization information is
    present; e.g. no meaningful information appears in
    ISA02 
  • Authorization Information. This field is usually left
    blank. 
  • 00 indicates that no security information is present;
    e.g.no meaningful information appears in ISA04 
  • Security Information. This field is usually left blank. 
  • ZZ indicates mutually defined. For the book industry
    this indicates that the sender ID in ISA06 is the
    sender’s Standard Address Number (SAN) #. 
  • 1135309 
  • ZZ indicates mutually defined. For the book industry
    this indicates that the receiver ID in ISA08 is the
    sender’s Standard Address Number (SAN) #. 
  • 2002450 
  • Date the interchange is created. Format is
    ‘YYMMDD’. 
  • Time the interchange is created. ormat is ‘HHMM’. 
  • ‘U’ indicates US EDI community of ASC X12. 
  • ‘00200’ is the version number for the interchange
    envelope only. 
  • This number must be unique by trading partner.
    Since this number an be used for auditability it is
    recommended that it be a continuously incremented
    sequential number. 
  • ‘0’ indicates that no acknowledgment is requested. 
  • ‘P’ indicates that the data is Production Data.
    (‘T’ would indicate that the data is Test Data.) 
  • ‘>’ is the sub-element separator. This field is
    reserved for future expansion.
GS Example
Sample Segment Data
Data Elements Data Element Descriptions
GS*PO*1135309*2002450*980319*1435*200*X*003060~
  • GS01 
     
     
  • GS02 
     
  • GS03 
     
  • GS04 
  • GS05 
  • GS06 
     
     
  • GS07 
  • GS08 
     
  • The functional identifier code ‘PO’ is for the Purchase Order. 
    (For other document types please refer to the ‘BISAC X12 
    Implementation Guidelines for EDI - version 3.6). 
  • 113509. This is the Sender’s SAN. It should be identical to
    ISA06. 
  • 2002450. This is the Receiver’s SAN. It should be identical to
    ISA08. 
  • Date the group is created. Format is ‘YYMMDD’. 
  • Time the group is created. Format is ‘HHMM’. 
  • This number must be unique by trading partner. Since this number
    can be used for acknowledgment reconciliation it is recommended
    that it be a continuously incremented sequential number. 
  • X indicates the Accredited Standards Committee X12. 
  • ‘003060’ indicates the version of the documents contained in this
    group. 
GE Example
Sample Segment Data
Data Elements Data Element Descriptions
GE*10*200~
  • GE01 
     
  • GE02 
     
  • This is the total count of ‘ST’ segments within the function group;
    e.g. the number of Purchase Orders in this group. 
  • ‘200’ is the group control number. It is the same as the control number
    in GS06. 
IEA Example
Sample Segment Data
Data Elements Data Element Descriptions
IEA*1*000000001~
  • IEA01 
     
  • IEA02 
     
  • This is the total count of ‘GS’ segments within the interchange;
    e.g. the number of functional groups in this interchange. 
  • ‘000000001’ is the interchange control number. It is the same as the 
    control number in ISA13. 

  Back to EDI Cookbook Table of Contents