No it isn't.  You are correct and PO301 is mandatory by standard.  More 
importantly, there is a good reason that it is mandatory.  It tells you the 
reason the PO3 segment is being used.

That doesn't mean your customer is going to see the light and make a change on 
his side... but he should never have set his system to disregard a mandatory 
element.

The puzzling thing is why it matters to him.  If he doesn't want to map the 
data that comes in that element, he *can* just ignore it.  But to be format 
compliant, there still needs to be at least an empty element in the X12 you 
send to him.  So I don't understand why he cares if there is actually data in 
it or not.



From: [email protected] [mailto:[email protected]] On Behalf Of Gerardo 
Santillana
Sent: Friday, May 10, 2013 9:07 AM
To: [email protected]
Subject: [EDI-L] 855 Mandatory element not needed



Hi

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?

Thanks

Gerry

[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