I have heard of all kinds of stange things trading partners do to the standard 
to get what they want. As long as no one is using the same map/model standard 
so you won't affect other TP's then I usually just change the standard 
model/map to allow for what they want. Depends if you are a good salesman or 
not to sell them on the fact that they should make a change on their end to 
handle the universally standard format instead of changing it to what they want.


Hoff Professional Consulting
President/Director of IT
Phone- 519-348-0895 
Fax - 425-732-1861 
Cell - 519-276-0489 
E-mail - [email protected]


________________________________
From: Ron Katz <[email protected]>
To: [email protected] 
Sent: Sunday, March 4, 2012 3:39 PM
Subject: [EDI-L] Deviating from X12 Standards


  
Hello Group
We have a customer that insists on receiving the SAC-05 element with the
explicit decimal as opposed to the implied decimal type N2 defined in the
standards.
Has anyone heard of this type of exception being used that defies the
standards.
Any thoughts are appreciated.

Ron Katz
ENTRACK Inc.
401-334-2463
[email protected]




[Non-text portions of this message have been removed]




[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/

Reply via email to