It seems that we all have our war stories when it comes to standards and the
relationship we maintain with customers and vendors.

I had a heck of a time with K-mart years ago dealing with their invoice
because of a number that had to appear in the heading.  Even though each
invoice reflected one shipment, the total number of invoices had to match
the required number of items ordered before K-mart would pay any of them.
That number in the heading was the key.  And there were charge backs levied
if these invoices weren't sent within a certain period after the shipments
were made.  

 

K-mart, like several other customers, liked to use these invoices as ASNs as
well so they didn't have to collect both from us.  I probably spent a day
every week on the phone with them discussing either missing invoices (that
we had sent but they could not find in their ERP system) or late
shipments/invoices in order to avoid their charge backs.

 

I was never so happy as when they went bankrupt and all this went away.  My
900-lb gorilla was gone.

 

Sincerely,

 

Jason McMahon

8079 Village Drive

Cincinnati, OH  45242-4315

 <mailto:[email protected]> [email protected]

http://gutausse.weebly.com/articles.html

 <http://gutausse.blogspot.com/> http://gutausse.blogspot.com

 <http://www.linkedin.com/pub/jason-mcmahon/11/743/51b>
http://www.linkedin.com/pub/jason-mcmahon/11/743/51b

  _____  

size=2 width="100%" align=center tabindex=-1> 

From: [email protected] [mailto:[email protected]] On Behalf Of Matt
Brown
Sent: Monday, March 05, 2012 11:53 AM
To: [email protected]; [email protected]
Subject: RE: [EDI-L] Deviating from X12 Standards

 

  

In addition to the 900-lb gorilla comments (or "tail" vs. "dog" or
"customer" vs. "supplier") with which I concur, I have to agree with Chris
that we try to keep BOTH sides of the transaction in the loop (regardless of
which one is our actual customer) so that they both understand the "rules of
engagement."

Sometimes, after months (years) of sending the same e-mails about the same
issues with ZERO response even when we BEG for "advice," if the recipient is
OK with it, we'll just shut off compliance for a specific
Element/Segment/Loop. 

On some (usually inbound X12) issues--especially when there is what seems
like an "arbitrary" limit to the number of Loop/Segment occurrences (e.g.,
"3", "54", "99", "100000")--as long as the recipient can handle the number
of occurrences, we'll either raise the upper limit or just make it
unlimited.

Matt
________________________________
Matthew Brown
eBusiness Analyst
EasyLink Services International Corporation
Phone: 917-524-0594
Fax: 212-999-7375
[email protected] <mailto:mbrown%40easylink.com> 
www.easylink.com

This message, together with any attachments, may contain information that is
confidential or legally privileged. If you are not the intended recipient,
you are not permitted to disseminate, distribute, or copy this message or
any attachment. If you have received this message in error, please notify
the original sender by return e-mail and delete this message, along with any
attachments from your computer.

-----Original Message-----
From: [email protected] <mailto:EDI-L%40yahoogroups.com>
[mailto:[email protected] <mailto:EDI-L%40yahoogroups.com> ] On Behalf
Of Ron Katz
Sent: Sunday, March 04, 2012 3:40 PM
To: [email protected] <mailto:EDI-L%40yahoogroups.com> 
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] <mailto:ron.katz%40entrack.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





[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