test

Sun B2B Suite ASC X12 OTD Library User's Guide

Sample for Identifying Segment IDs Using Local Codes

This is an example of a customized definition of a X12 transaction set 814 of v4010. The .SETS section of the SEF file is:


.SETS
814=^[ST,M][BGN*8,M][.CUR]{:>1+5[.FA1]+1[FA2,M,>1]}{:>1+4[N1*12@192]+10[.N2,
,2][N3*5,,2][N4*23][.PER*1,,>1][.REF,,>1][.DTM,,>1]}{:>1-60[N1*5@58]+10[.N2,
,2][.N3,,2][.N4][.PER,,>1][.REF,,>1][.DTM,,>1]}{:>1-60[N1*5@151]+10[.N2,,2][
.N3,,2][.N4][.PER,,>1][.REF,,>1][.DTM,,>1]}{:>1-60[N1*13@51]+10[.N2,,2][.N3,
,2][.N4][.PER,,>1][.REF,,>1][.DTM,,>1]}^{:>1[LIN*4@176][ASI*1@14][REF*9@172,
,>1]+0[REF*9,,>1][REF*10@200,,>1][.REF*10@181,,>1][REF*12@177,,>1][REF*12@18
2,,>1][REF*10@178,,>1]+10[DTM*6@76,,>1][.CUR@17][.AMT*1@82,,>1]+0[.AMT*1@81,
,>1][.AMT*1@80,,>1][.AMT*1@79,,>1][.AMT*1@18,,>1]+10[.PM]{:>1+5[.FA1]+1[FA2,
M,>1]}{:>1+4[NM1*3]+10[.N2,,2][.N3,,2][.N4][.PER,,>1][REF*14@87,,>1]+0[REF*1
4@86,,>1][REF*10@93,,>1][REF*10@88,,>1][REF*10@92,,>1][REF*10@169,,>1][REF*1
5@179,,>1][REF*16@89,,>1]+10[DTM*10@28,,>1]}}[SE,M]

The same definition may also be viewed in a third—party application such as EDISIM 5.0 (see figure Figure A–1). Multiple N1 segments as well as REF segments are customized so that they are adjacent to each other in a tandem fashion. Local codes for these adjacent segments must be used for parsing a message. Therefore, the Segment IDs Using Local Codes field must have a N1,REF value (a list of segment IDs separated by commas).

Figure A–1 X12 Transaction Set 814 of v4010

X12 Transaction Set 814 of v4010