Edi brain dump

I spent a lot of time on the phone learning a bunch of stuff so I'm going to try to capture some of it.
First problem that was encountered was REF*IL*UNK~ >>>> Invalid ITN PO Number
This happened because the flat files when we transfered over to the new machine were than stale. It was resolved by a careful checking and merging of these files EFSBEKPO,EFSBEKPROD,EFSFSAPO,EFSFSAPROD,EFSSYSCOPO, EFSSYSCOPROD

PROD.DAT has product cross-ref data

PO.DAT has Purchase Order Cross Ref data

they're columns of data

The next prob was getting some unkown trading partners. This was caused becuase we upgraded from get2connect.net to inovisworks.net and in doing so it thought they were new partners.

In a nutshell, most TP's (trading partners) are very minimalist

they only send what's needed to complete an order

and they almost never require verification or validation

EFS is different, since they're brokering their EDI services, they need to be able to not only separate their TP's, but manage the "leveraging" they are doing.

So they require some validation/verification.

One way they do this is thru having a separate EFS Document Control #

It acts like a PO, so for each PO we get, it comes with a Control#. They then require we tie our SO# to this so that when we report back any order acknowledgement (855) or Invoicing (810/880) that they can sort them out.