Michael, I see an MTX in the LDT loop, in the N9 loop as you suggest, in the SPI loop, in the N1 loop in the SPI loop, in the CB1 loop subordinate to the SPI loop, in the ADV loop, all at the header level. Nowhere do I see an MTX which is not subordinate to some other segment (within a loop). Of course, as you mention, no way to stop them sending this "non-standard" segment. Any chance the IG has an example or that you can get a sample file from them?
Good Luck, Leah ----- Original Message ---- From: Michael Mattias/LS <[EMAIL PROTECTED]> To: EDI-L <[email protected]> Sent: Saturday, February 9, 2008 11:47:43 AM Subject: [EDI-L] ANSI 004040 850, placement of segment MTX? I have a request to map an ANSI 004040 850 purchase order for one of my clients. The client's trading partner's proposed IG shows the header structure of his ANSI 004040 850 document as .... ST Transaction Set Header BEG Beginning Segment for Purchase Order REF Reference Identification (>1) MTX Text (>1) Loop ID - N1 (200 ) N1 Loop ID - P01 (100000) P01 Baseline Item DataM1 Loop ID - CTT ( 1 ) CTT Transaction TotalsO1 SE Transaction Set TrailerM1 My 004011 standard for 850 is the first in which the MTX segment appears in this transaction set; however, both in 004011 and in version 005010, segment MTX in the header of the 850 is shown in an N9 loop... i.e, an N9 Segment is required as a "loop starter" for any occurrences of segment MTX in this transaction set. (My standards disk for ANSI 4 only goes thru 004011, so I can't look this up myself) Since segment MTX requires N9 loop in both 004011 and in 005010, I think the above specification for 004040 should also show an N9 segment and loop requirement; that is, I think the trading partner is suggesting an 'ansi invalid' document. (Not that they don't do that, but it seems highly unlikely). Then again, he may have just missed this in his documentation and he intends to send MTX only in an N9 loop.. in which case I will let him know his doc is bad and could you please correct it so the next poor schmuck won't have to go thru the same angst this poor schmuck is suffering. Could someone with access to the ANSI 004040 standards please check on this for me and post response? Thanks a lot. Michael C. Mattias Tal Systems Inc. Racine WI [EMAIL PROTECTED] .com Michael C. Mattias Tal Systems Inc. Racine WI [EMAIL PROTECTED] .com <!-- #ygrp-mkp{ border:1px solid #d8d8d8;font-family:Arial;margin:14px 0px;padding:0px 14px;} #ygrp-mkp hr{ border:1px solid #d8d8d8;} #ygrp-mkp #hd{ color:#628c2a;font-size:85%;font-weight:bold;line-height:122%;margin:10px 0px;} #ygrp-mkp #ads{ margin-bottom:10px;} #ygrp-mkp .ad{ padding:0 0;} #ygrp-mkp .ad a{ color:#0000ff;text-decoration:none;} --> <!-- #ygrp-sponsor #ygrp-lc{ font-family:Arial;} #ygrp-sponsor #ygrp-lc #hd{ margin:10px 0px;font-weight:bold;font-size:78%;line-height:122%;} #ygrp-sponsor #ygrp-lc .ad{ margin-bottom:10px;padding:0 0;} --> <!-- #ygrp-mlmsg {font-size:13px;font-family:arial, helvetica, clean, sans-serif;} #ygrp-mlmsg table {font-size:inherit;font:100%;} #ygrp-mlmsg select, input, textarea {font:99% arial, helvetica, clean, sans-serif;} #ygrp-mlmsg pre, code {font:115% monospace;} #ygrp-mlmsg * {line-height:1.22em;} #ygrp-text{ font-family:Georgia; } #ygrp-text p{ margin:0 0 1em 0;} #ygrp-tpmsgs{ font-family:Arial; clear:both;} #ygrp-vitnav{ padding-top:10px;font-family:Verdana;font-size:77%;margin:0;} #ygrp-vitnav a{ padding:0 1px;} #ygrp-actbar{ clear:both;margin:25px 0;white-space:nowrap;color:#666;text-align:right;} #ygrp-actbar .left{ float:left;white-space:nowrap;} .bld{font-weight:bold;} #ygrp-grft{ font-family:Verdana;font-size:77%;padding:15px 0;} #ygrp-ft{ font-family:verdana;font-size:77%;border-top:1px solid #666; padding:5px 0; } #ygrp-mlmsg #logo{ padding-bottom:10px;} #ygrp-vital{ background-color:#e0ecee;margin-bottom:20px;padding:2px 0 8px 8px;} #ygrp-vital #vithd{ font-size:77%;font-family:Verdana;font-weight:bold;color:#333;text-transform:uppercase;} #ygrp-vital ul{ padding:0;margin:2px 0;} #ygrp-vital ul li{ list-style-type:none;clear:both;border:1px solid #e0ecee; } #ygrp-vital ul li .ct{ font-weight:bold;color:#ff7900;float:right;width:2em;text-align:right;padding-right:.5em;} #ygrp-vital ul li .cat{ font-weight:bold;} #ygrp-vital a{ text-decoration:none;} #ygrp-vital a:hover{ text-decoration:underline;} #ygrp-sponsor #hd{ color:#999;font-size:77%;} #ygrp-sponsor #ov{ padding:6px 13px;background-color:#e0ecee;margin-bottom:20px;} #ygrp-sponsor #ov ul{ padding:0 0 0 8px;margin:0;} #ygrp-sponsor #ov li{ list-style-type:square;padding:6px 0;font-size:77%;} #ygrp-sponsor #ov li a{ text-decoration:none;font-size:130%;} #ygrp-sponsor #nc{ background-color:#eee;margin-bottom:20px;padding:0 8px;} #ygrp-sponsor .ad{ padding:8px 0;} #ygrp-sponsor .ad #hd1{ font-family:Arial;font-weight:bold;color:#628c2a;font-size:100%;line-height:122%;} #ygrp-sponsor .ad a{ text-decoration:none;} #ygrp-sponsor .ad a:hover{ text-decoration:underline;} #ygrp-sponsor .ad p{ margin:0;} o{font-size:0;} .MsoNormal{ margin:0 0 0 0;} #ygrp-text tt{ font-size:120%;} blockquote{margin:0 0 0 4px;} .replbq{margin:4;} --> ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ [Non-text portions of this message have been removed] ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
