jkcedi, True. Years ago we used the GEIS 'pass through envelope' to receive proprietary data from a specific TP. The payload was simply non-EDI formatted file (probably 80 characters) wrapped with ISA/IEA, and both parties knew about it. Don't know if GXS still offers it.
Mike Rudolph -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of jkcedi Sent: Thursday, November 08, 2007 11:02 AM To: edieileen; Mike Rawlins Cc: [email protected] Subject: Re: [EDI-L] XML embedded in EDIFACT Speaking generally, I have heard of putting enveloping around non-EDI data for transmission/routing purposes, to trick some systems into allowing the data through. But this should be an exception, and should never be done without the explicit agreement between partners. ----- Original Message ----- From: Mike Rawlins To: edieileen Cc: [email protected] Sent: Thursday, November 08, 2007 10:19 AM Subject: Re: [EDI-L] XML embedded in EDIFACT Never seen anything like it for a CONTRL, 997, or 999. I suspect that either something got messed up on the sender's end, or else they are clueless. ----------------------------------------- Michael C. Rawlins, Rawlins EC Consulting www.rawlinsecconsulting.com edieileen wrote: > One of our customers received and EDIFACT CONTRL transaction with > XML embedded in it. Has anyone ever seen this before? > > Thanks, > > Eileen > > > The transaction looks like this: > > UNB+UNOA:2+XXX+XXX:XX+071106:1033+2000117'UNH+0001+CONTRL:2:2:UN'UCI+ > 000000005+XXX+XXX+4'UCM+Please look at the UCM Segments for your > Error Details'UCM+ > <HeaderInfo> > <SenderInfo> > <SenderId>MNP</SenderId> > <SenderControlNbr>000000005</SenderControlNbr> > <SenderApplDocId>62191</SenderApplDocId> > <ShipFromId>88123</ShipFromId> > <ShipToId>72401</ShipToId> > </SenderInfo> > <ReceiverInfo> > <ReceiverId>0935HRB2002201</ReceiverId> > </ReceiverInfo> > <MsgInfo> > <MsgType>DESADV</MsgType> > <DateTimeStamp>11-06-2007T11:34:22</DateTimeStamp> > </MsgInfo> > </HeaderInfo> > <ErrorDetails> > <ErrorCode>7181</ErrorCode> > <TypeofError> MISSING ELEMENT</TypeofError> > <LocationOfBadData>Segment: NAD; CdListRspAgencyCd > Element</LocationOfBadData> > <LineNumber>12</LineNumber> > <BadData>NAD</BadData> > </ErrorDetails> > 'UNT+5+0001'UNZ+1+2000117' > > > > ... > 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 > > > > > [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 ... 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/
