>I need to send an 855 to a customer, according with his specs he does not want
>element PO301 in segment PO3, but this element is a
>standard mandatory >element.
> I can do it but, Is it correct to force the system not to send a mandatory
> element?
If you stay in the EDI field long enough you will see *plenty* of your
clients'/employers' partners specify documents which are not
standard-compliant.
I recommend to all my clients they adopt a policy something like "we will not
enter into any EDI trading agreements except those
which acknowledge both parties will send only documents which are syntax
compliant to the agreed standard; any documents received
which are not syntax-compliant will be acknowleged as 'rejected.' The sender
is expected to "correct and resend" as rejected
documents will not be processed beyond this edit. "
If you want to leave the legal stuff out, just drop a note to the partner and
politely point it out to him. I've yet to have any
partner not thank me for doing so and make changes.
FWIW, this is a really easy policy to implement if you are using a REAL
translator and not some piece of homegrown crap (of which
there is a lot more in use than you ever dreamed there was).
MCM
------------------------------------
...
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/
