"Follow the same methodology as described, in detail, in the ALE configuration guide, when implementing EDI. It is a full grown project in its own right, treat it as such. We have compiled a few documents that assist us when we tackle EDI projects, browse through them and use them to assist your preparation for an EDI implementation."

Planning is an important first step to take in any EDI implementation.  First of all an understanding of the following should be gained:

• EDI;

•  application (SAP);

•  requirements of trading partners;

•  requirements of EDI standards being used; and

•  the EDI mapping tool that will be used.

The following is a list of things that should be considered during the planning phase of an EDI implementation:

• identify EDI goals/requirements;

•  identify EDI organizational structures (EDI coordinator and steering committee);

•  train people involved in EDI;

•  select and list trading partners;

•  determine public standard versions and transaction to be used with trading partner;

• confirm envelope selection and contents for each trading partner;

•  confirm communication requirements for each trading partner;

•  analyze application (SAP);

•  consider audit and security requirements; and

•  analyze future requirements.

Documents

• Mapping template - What should you be looking for when designing a scenario between 2 parties?

• OSS Note - How to implement EDI.

• Interface design - The purpose of this document is to outline the technical design of the EDI interface from SAP to the EDI subsystem.

• Interface design specification - The purpose of the document is to describe the functional technical design and the physical technical design of the EDI architecture.