EDI Configuration in SAP - AFS 6.

0
Version

Applies to:
SAP AFS 6.0 Version. For more information, visit the Enterprise Resource Planning homepage.

Summary
In this article I have mentioned an important configuration of EDI and Idoc in SAP-AFS. I have mentioned
the description, implication and necessary customization of Idoc generation of SAP-AFS.

Author: Indraneel Mukherjee

Company: CapGemini India
Created on: 16 December 2008

Author Bio
I have taken a great interest in the contribution of SDN and since not much research and material is available
on site in SAP-AFS hence I have decided to contribute it based on my experience and skill.
Currently I am working for Capgemini,India and I have experience in various organizations like Reliance,
Infocomm, Accenture, IBM, etc.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

© 2009 SAP AG 1
 EDI Configuration in SAP - AFS 6.0 Version

Table of Contents
Configuration of System for EDI .........................................................................................................................3
1) Create and assign logical system to client .................................................................................................3
2) Activating SAP Workflow: ...........................................................................................................................4
3) Setting up an Idoc Administrator.................................................................................................................7
4) Define a file port:.........................................................................................................................................7
Related Content..................................................................................................................................................8
Disclaimer and Liability Notice............................................................................................................................9

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

© 2009 SAP AG 2
 EDI Configuration in SAP - AFS 6.0 Version

Configuration of System for EDI

Before the system is ready and enabled for EDI, certain configuration needs to be maintained in the system.
Following are the basic steps for EDI configuration:
1) Create and assign logical system to client
2) Activate the SAP workflow
3) Set up an Idoc Administrator
4) Define port and user specific parameters
Let us discuss the above parameters in details:

1) Create and assign logical system to client

Basically every client has a system landscape and to which logical system should be assigned to it.Thus
no two client can have same logical system name.To create a logical system the navigation path is:

Assign logical system to client (navigation path is already shown above)

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

© 2009 SAP AG 3
 EDI Configuration in SAP - AFS 6.0 Version

2) Activating SAP Workflow:

Basically for EDI monitoring SAP workflow must be maintained and activated.Following are the settings
that needs to be maintained:
i) Use Tcode-SWU3 as shown below:

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

© 2009 SAP AG 4
 EDI Configuration in SAP - AFS 6.0 Version

ii) Select automatic workflow customizing as shown below:

iii)After the above process entire message log appears in verifying workflow log as shown below:

Basically, when you choose Perform Automatic Workflow Customizing, only those activities that currently
have the status error are executed automatically or else there will be no execution. Its also important to
maintain prefix number under workflow development environment . Standard objects (workflow tasks,
standard tasks, and so on) are identified with an eight-digit number. The last five digits of this number are
assigned automatically by the system. The prefix number is used for the first three digits of this number.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

© 2009 SAP AG 5
 EDI Configuration in SAP - AFS 6.0 Version

iv) Test for RFC destination:

We need to activate the workflow because the EDI error handling and notification procedure makes
extensive use of workflow.It is a good strategy to make use of workflow for error handling and notification
handling.
v) Activating event receiver linkage: Enter T-Code-OYEB and press yes to activate the event linkage.

The inbound processing of IDoc uses the workflow functionality to pass the EDI data to the appropriate
application. Activating the event linkage creates the link needed for the inbound EDI process to inform
workflow to take the EDI data and process it in the application.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

© 2009 SAP AG 6
 EDI Configuration in SAP - AFS 6.0 Version

3) Setting up an Idoc Administrator

This functionality is required to intimate the concerned person when an EDI error occurs i.e the system
identifies whom to contact by using this functionality. It can be specified for partner profile and message
combination. Additionally, make sure that there is at least one administrator defined. Otherwise, the
notification will go to the inbox of all SAP users since the work-item is considered as a general task. Use
Tcode- OYEA we have to enter object type and user ID as shown below:

The IDoc administrator has been directly assigned to a specific user in this context. We recommend that the
IDoc Administrator be assigned to a position in an existing organizational structure. Such an assignment
allows for greater flexibility within the system to handle personnel.

4) Define a file port:

A port definition helps to define the directories and filenames the system uses to generate to and/or retrieve
from the EDI IDoc file.Port can be defined using Tcode-WE21.
Here we need to define port type as FILE as shown below:

The version of an IDoc type or segment is developed in a correction level. The latest version remains the
current version in all subsequent correction levels. When a new version is developed, it then becomes the
current version. All versions are retained in the system, hence reductions from current versions to former
versions are possible at any time. This allows the IDoc interface to serve the interface with any subsystem in
a compatible mode even after upgrades. Remote Function Call (RFC) is the R/3 functionality that allows the
translator to communicate with the R/3 System and vice versa. The SERVER_EXEC is a preconfigured
destination provided by SAP for the customer. The directory and shell script defined in the command file
parameter is necessary for outbound EDI if the R/3 System is to start—or trigger—the external system
(translator) using RFC.

i) Define user specific parameters: It is a good idea to set up user-specific parameters as they provide the
default values. Some examples of user parameters are as follows: Test port for the file interface. For
example, the paths for Test inbound modified outbound file are derived from this description

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

© 2009 SAP AG 7
 EDI Configuration in SAP - AFS 6.0 Version

Related Content
• Forums –SAP-EDI and Idoc – configuration
• For more information, visit the Enterprise Resource Planning homepage.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

© 2009 SAP AG 8
 EDI Configuration in SAP - AFS 6.0 Version

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not
supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.
SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document,
and anyone using these methods does so at his/her own risk.
SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or
code sample, including any liability resulting from incompatibility between the content within this document and the materials and
services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this
document.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

© 2009 SAP AG 9