Hi Michael, The problem is that in the GS the field length for the time is 8 yet they only write out 4 characters and leave the remaining 4 blanks. In order to get around this the company I am at had to modify the standard to change the length to 4.
The nuances I was referring to were in Seeburger, not X12. I've been running EDI systems and programs for companies so 17 years now, so the issues I come across are with the translation software anomolis, trading partners who are a pain in the ass, and consultants who think they know more than anyone else ;) Jon ----- Original Message ---- From: Michael Mattias/LS <[EMAIL PROTECTED]> To: [email protected] Sent: Wednesday, November 15, 2006 6:18:37 PM Subject: Re: [EDI-L] Seeburger Anomolies? 11/15/06 >I am new to using Seeburger's translation software, but I am finding >some odd things in the translator's standards for X12. It looks like >the standards for enveloping in version 4010 and higher aren't >formatted correctly. They seem to be writing out 8 characters in the GS >time element. Eight (8) character GS time is a perfectly valid option in ANSI 4 (valid group times in 003040+ : 4, 6 or 8 characters) >Also, has anyone run into differences between a detail level SAC >segment's definition vs a summary level SAC segment's definition? No, an SAC segment is an SAC segment is an SAC segment, regardless of in which transaction set or what position within a transaction set it appears. (ANSI standard. Valid charge/allowance codes may vary in private implementations) . >I am wondering if these are here on purpose Well, the time thing probably IS 'on purpose.' Differences in editing between "header" and "detail" SAC segments probably are not 'on purpose,' unless the editor is in fact performing an edit to comply with a private implementation. >Just wondering if there are any other little nuances to look out for! Oh, there's lots of nuances in ANSI EDI. You don't even hardly have to look very hard for them. However, ANSI ASC X12 is ANSI ASC X12 and all translator/editor products should edit the same data the same way. That's not to say they all DO edit the same way, only that they SHOULD get the same results. Michael C. Mattias Tal Systems Inc. Racine WI [EMAIL PROTECTED] .com http://www.talsyste ms.com [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/
