Hi Jim, Could you please send an example of what you're describing? There are two ways TLE would go with this, either ignore it, viewing it as another "RFF loop" or it might think it was out of order or "unexpected" and fail the entire transaction. TLE does allow the addition of "non-standard" segments, so this is easily gotten around, either way. Other translators may not have this option.
Leah ________________________________ From: jimdivoky <[email protected]> To: [email protected] Sent: Thu, May 5, 2011 12:34:08 PM Subject: [EDI-L] Effect of adding a new segment Scenario: 800 pound gorilla sends an outbound message using established EDI standards like X12 and EDIFACT. They add a second REF/RFF segment within a repeating REF/RFF segment loop which currently contains one mandatory segment as specified in their IG. The recipient does not need to do anything with the new segment. Question: What percentage of the TPs receiving the message with the additional REF/RFF segment would not have to make any changes to their data structure and/or map? Thanks, Jim Divoky [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: [email protected] [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/
