Leah,

Where in my post did I say that ignoring standards is not "real world"?
Where in my does it say that it does not actually occur or happen?

My point is that if somebody is abusing the standard they should be called
out on it. Also, my response was to Alexander Luss's post saying this is
"perfectly good" - do you think that marking PO301 (Change Reason Code) as
Optional when it's clearly marked as mandatory, do you think it's
"perfectly good"?

I had a full time EDI job for over 4 years now (going to college in
evenings), first I worked for Direct EDI and now I work for Beacon. Yes, I
do not have decades of experience like some on this list.
Since you opened the topic of experience, in my role working for
third-party EDI providers, I have been fortunate to see mapping specs and
actually do mapping for dozens of retail hubs and most of them follow the
standard. My point is that in my short years of experience I have done a
large variety of mapping. By the way I have also been involved in helping
out with ERP integration into SAP (idocs), Sage Products (MAS 500) and
QuickBooks. So I know that there is a gap between the EDI standard and the
business applications.

Happy Friday :) and Happy Mother's day to all mothers out there!!!

Sergey Sudakov
EDI Project Manager
Beacon EDI, Inc
[email protected]
4445 Eastgate Mall
Suite 200
San Diego, CA 92121
800-334-6127 x2
https://beaconedi.com/
EDI Blog: https://beaconedi.com/edi-blog



On Fri, May 10, 2013 at 8:17 AM, Leah Halpin <[email protected]> wrote:

> Hi Sergey,
> Welcome to what we here on this list like to call the "real" world.  The
> TP is most likely NOT ignoring anything.  They, apparently, either don't
> need this information or have another way of getting it.  You are taking
> this way too seriously, but I see from linked in that you've not been doing
> this very long, so perhaps your experience in this type of "abuse" is
> limited.   As you gain experience you will see that EDI is limited by the
> ERPs/backend systems it serves.  Some systems cannot or do not
> want/need/provide the information that other systems are happy to
> provide/need/get.  This is why all of us here in the real world have jobs,
> so calm down, have an adult beverage of your choice and welcome the weekend!
>
> Happy Friday and Happy Mother's Day to all whom it applies (not you MCM).
>
> Leah
>
>
>   ------------------------------
>  *From:* Sergey Sudakov <[email protected]>
> *To:* Alexander Luss <[email protected]>
> *Cc:* Gerardo Santillana <[email protected]>; "[email protected]"
> <[email protected]>
> *Sent:* Friday, May 10, 2013 10:50 AM
> *Subject:* Re: [EDI-L] 855 Mandatory element not needed
>
>
>  Alexander,
>
> I disagree, it is not perfectly good. They do not mutually agree, one of
> them disagrees. Also in this case it is actually really bad because it is
> leaving out business information on why a line item is changing.
>
> By ignoring the X12 standard, they are ignoring 3 decades of standards
> development and hard work that was put into place it.
>
> What the customer is doing is called standards abuse. If everybody had the
> same thought process the standards development process would be useless.
>
> Gerry's customer is ignorant of the values that come with standards
> development. Three times a year at X12 meetings, leaders from various
> industries get together and decide what is the best way to do a Purchase
> Order or a PO Change or Health Care Claim.
>
> It's a 4 day long meeting where people work really hard all day long.
> Ignoring 30 years of that is not perfectly good, it should be at least
> considered. I am sure if Gerry's TP really understood the best practices
> that the standard has to offer.
>
> If it were not for the late 1970s and early 1980s pioneers of taking EDI
> standards seriously there would be a real lack of standards.
>
> http://x12.org/ now has a feature where you can make a change request
> online. If Gerry's TP thinks the data element should be optional they can
> post there.
>
> Thanks,
>
> Sergey Sudakov
> EDI Project Manager
> Beacon EDI, Inc
> [email protected]
> 4445 Eastgate Mall
> Suite 200
> San Diego, CA 92121
> 800-334-6127 x2
> https://beaconedi.com/
> EDI Blog: https://beaconedi.com/edi-blog
>
> On Fri, May 10, 2013 at 7:37 AM, Alexander Luss <[email protected]
> >wrote:
>
> > Gerry,
> >
> > X12 standard is not law that one can be prosecuted for breaking. It
> doesn't
> > have a moral side either. Anything that you and your TP can mutually
> agree
> > upon is perfectly good, valid, correct and legit.
> >
> >
> > *Thank you,
> > Alex Luss
> > ________
> > *
> >
> >
> > On Fri, May 10, 2013 at 9:07 AM, Gerardo Santillana
> > <[email protected]>wrote:
> >
> > > **
> > >
> > >
> > > 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
> >
> >
> >
> >
>
> [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