The following is the general test cycle for implementing an EDI relationship with Quaker, a unit of PepsiCo Beverages & Foods. These steps should be followed in the order of appearance. There will be variances to this schedule depending upon several factors, including the trading partner’s current EDI activity, available resources, the transaction set being implemented, internal applications and the amount of testing required, just to name a few. This implementation schedule is a recommendation and thus should serve as a guide only. Each company will need to analyze their respective systems and strategic EDI goals to determine if alterations to this schedule are needed. If at anytime you are uncertain how this schedule applies to your implementation, please contact the EDI Team.

Quaker does not require a signed trading partner agreement for entering into an EDI relationship. There are several companies where this type of agreement is required. If your company requires a signed trading partner agreement, forward the agreement to the EC Business Team. Click here for EC Business team contact information.

Click here to download the appropriate EDI Implementation Guides. Quaker supports ANSI X-12 and UCS standards in versions 4010 and 4030. Use these Implementation Guides to build your translation for the transaction sets. If there are discrepancies between Quaker’s recommended mappings and the information required for your company’s application systems, contact the EDI Team to arrange a conference call to discuss the discrepancies.

This is when representatives from both companies agree that the segments, elements, and codes for the appropriate transaction sets are consistent. It is important that an agreement be reached on this issue before moving to the next level.

This is an internal operation performed by each respective company. This requires coding the finalized mappings into your company’s translator.

This step begins only after all the previous steps have been completed. This is the first opportunity to test both trading partners’ ability to communicate with each other. It is important that the technical representatives from both companies are in constant contact with each other before, during and after the "test transmission" step.

A parallel test is when both trading partners continue current business processes using traditional paper documents. EDI transactions are introduced to accompany the paper documents. It is advised that the receiving company compare the EDI information, at a micro level, against the traditional paper documentation. The idea is to ensure the completeness and accuracy of the EDI files before relying exclusively on the EDI documents for general business.

After completion of at least one business cycle in the parallel mode, both trading partners will agree that the EDI documents adhere to the same requirements of the traditional paper documentation. It is recommended to spend more time in parallel mode rather than move to production prematurely. Be cautious, however, about spending too much time in parallel mode because it is more expensive to send duplicate information via two media.

The final stage of implementation is to “turn off” the paper. After both trading partners feel confident that the EDI files contain complete, accurate, and timely information, it is no longer necessary to receive the paper documentation. It is at this stage that the companies have moved into full production. Be sure to monitor the EDI activity for a short while to ensure successful EDI production status.

The schedule provides:
three weeks for transaction mapping/coding
two weeks for test transmissions
four weeks for parallel testing, evaluation, and adjustments

The final production date is dependent on:
initial trading partner contact
the specific transaction sets
the number of transaction sets
experience level of trading partners with individual transaction sets