Electronic Data Interchange (EDI) and Application Link Enabling (ALE) are used to exchange business

data between systems. The IDoc interface consists of the definition of a data structure, along with
processing logic for this data structure. The integration service Application Link Enabling (ALE) enables
the integration of business processes that have been developed across multiple SAP systems or external
systems. The data structure is the IDoc. The IDoc is the exchange format common to all the
communicating systems.

The Interface Adviser provides support for designing and implementing

permanent interfaces between SAP components and external components.
You can access the Interface Adviser in SAPNet.

The output or follow up processing of partner-dependent messages is automated via Message

Control. The application then calls the Message Control using the specified interfaces.

The RFC is an SAP interface protocol, which simplifies the programming of communication
processes between systems. The RFCs enable you to call and execute predefined functions in a
remote system, or in the same system. The RFCs manage the communication process, parameter
transfer, and error handling. In the J2EE Engine the RFC functions are implemented by the JCo
RFC Provider service, which is used for processing ABAP to Java requests. A feature is provided
for receiving calls from the SAP systems this is done by registering the J2EE Engine as a RFC
destination. Technically, the service is based on the JCo (SAP Java Connector).
The scenarios are intended to describe a work process as simply and as realistically as
possible. They are templates or starting points for the business processes you are setting
up, but do not necessarily represent your individual procedure. The EDI scenarios do not
cover conversion of the IDoc standard into an EDI standard (such as EDIFACT,
ODETTE, or ANSI X. 12). This conversion is performed by an external EDI subsystem.
You therefore remain in the IDoc standard when testing the scenario.

EDI business processes are usually modeled according to the following procedure:

Default settings and usage are described first on the sender side, then on the recipient side.

To use the Test Tool of the IDoc interface to test the processes in one system, you can
convert the outbound message (outbound IDoc) into an inbound message (inbound IDoc). To
do this, you need to swap the sender and recipient in the control record.

You can use the IDoc display to call and check the generated IDocs in the system.
1) The legacy system can, of course, be an R/3 system or R/2 system with industry
materials. During data transfer, the system converts the industry materials into retail
articles. However, this only applies in the case of different systems. To convert industry
materials into retail articles in the same system, you must use program RMMMMPOI.
2)

The following master data objects can be distributed: Change numbers (If a change number is
distributed using the message type ECMMAS, it contains: Change master record (in long text if
available), Alternative dates, Validity, Object types for change master record, Object
management records (in long text if available)), Article master record

User master record

Purchasing info record

Business process

Classification, class and characteristics

Conditions

Cost center

Cost center group

Cost element group

Cost element

Customer master record

Activity type

Activity master record

Activity type group

Vendor master record

Material master record

Unit of measure for cost center and cost element combination

Source list

Human Resources: HR Master Data, Organizational Data

Profit Center

G/L Account

Bill of material (materials and documents)

Activity price of cost center and cost element combination

Value Scale and Quota Scale

ALE business process library, EDI application scenarios.