SAP 6.0 Document Exchange

The acquisition of Ariba by SAP is widely promoted as a purchasing portal. What is more important, but not as “hot,” is the combination with Crossgate for classical EDI (X12) exchange for low volume customers or vendors. (High volume users should be exchanged directly using AS2 or FTPS.)

For low volume customers or vendors, web portals are used. For example:

1. A vendor Purchase Order is posted.
2. The vendor then prints it the P.O. and fills the order.
3. To invoice for the product at the time of shipment, the vendor clicks on the P.O. to turn-it-around to an Invoice, then adds the invoice number, etc.

SAP ERP 6x users have the options of NetWeaver (higher development/no per message cost) or Ariba (low development/higher long-term cost). The NetWeaver path has a hidden short-cut that both speeds implementation and lowers cost.

Most “mom and pop” vendors use a portal from the array of EDI networks (IBM, GXS, True Commerce, SPS Commerce, DICentral, etc.). This means you can direct X12 and format other messages to their portal; at their expense. This reduces both your development time and the “help desk” cost inherent when they contact to learn, use, and correct mistakes on a NetWeaver portal.

DCS recommends high volume direct connection and low volume portal use for the most effective, reliable, secure, and economical document exchange with key customers and vendors. DCS can readily connect your IDoc/X12 to an EDI network or help you decide the best combination for saving money and connecting to all Trading Partners.

How did you automate document exchange with low volume Trading Partners? What tips and tricks can you offer your peers?