Showing posts with label EDI Mapping. Show all posts
Showing posts with label EDI Mapping. Show all posts

Sunday, August 13, 2017

WHITEPAPER: Understanding the 10 EDI messages critical to deploying "Best in Class" Procure to Pay (PTP) SAP EDI

I have seen many, many EDI implementations in this space over the years and have yet to come by a single company that has adopted all of the good features available in SAP to bring real value in to the PTP process. In each part of the process, described below, I will highlight exactly what the purpose is for each EDI message or functionality and highlight the benefits for implementing it in the mentioned fashion.

Below, I list the PTP process for a typical replenishment PO where we procure stock via a Purchase Order (PO) to a supplier who delivers the product to our warehouse using one of our 3rd party carriers. The nuances around freight forwarding, drop ship and make to order scenarios are not covered here but are addressed using 90% of these same techniques as well.

Saturday, July 1, 2017

Everything EDI...

We would like to bring your attention to a portal that shares a lot of good information on Electronic Data Interchange (EDI), a technology that has long been thought of as "dying" but is actually growing in its adoption.
Check it out for free mapping templates, links to standards, recruiters, service companies and much more...

Monday, August 10, 2015

Mar-Kov provides Electronic Data Interchange (EDI) Functionality to the Process Manufacturing Industry

Mar-Kov Computer Systems has added EDI functionality to its standard suite including Manufacturing, Purchasing, Receiving, Sales, Shipping, Barcoding, Electronic Batch Recording (EBR), Lot Track/Trace, Recalls - See more at Global News Wire

Monday, May 18, 2015

Mapping a Customers EDI field in to and then out of SAP

Customers that transact Orders to you via an EDI X12 850 often need you to send certain, customer specific, fields back to them on subsequent documents. This is often a requirement at both the header and item levels of the order. A common example of a header field would be the department number. It makes sense for the customer to have the department number returned on subsequent documents but we don't have any use for that number in our SAP system other than to store the details and pass it to subsequent documents.