Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components
Close Print View
Configuring: Configuration Needed in SAP R/3 to Send and Receive IDocs
 

Classic Java CAPS

Configuring JMS Clients

Configuring Java CAPS for SSL Support

Configuring Java CAPS Business Processes

Configuring Environment Components for the Sun Business Process Manager

Configuring Sun Master Indexes (Repository)

Configuring Java CAPS Project Components for Application Adapters

Configuring Java CAPS Project Components for Communication Adapters

Configuring Java CAPS Project Components for Database Adapters

Configuring Java CAPS Project Components for Web Server Adapters

Configuring Java CAPS Environment Components for Application Adapters

Configuring Java CAPS Environment Components for Communications Adapters

Configuring Java CAPS Environment Components for Database Adapters

Configuring Java CAPS Environment Components for Web Server Adapters

Configuring JDBC/ODBC Drivers

Configuring SAP R/3 for the SAP BAPI Adapter

Configuring SAP R/3 for the SAP BAPI Adapter

Creating the RFC Destination for the Adapter

Configuration Needed in SAP R/3 to Send and Receive IDocs

Configuring the Distribution Model

Configuring Communications

Configuring Secure Network Communications for SAP

Configuring Siebel EAI Workflows

Importing an SNA Custom Handshake Class

Configuring WebLogic for Asynchronous Communication

Configuring Master Index (Repository) Connectivity and Environments

Related Topics for Sun Adapter for Batch/FTP

Java EE Based Components

Broadcasting Master Index Updates to External Systems

Configuring Sun Master Indexes

Configuration Needed in SAP R/3 to Send and Receive IDocs

For the SAP BAPI Adapter to interact successfully with the SAP R/3 system, you must configure the SAP R/3 system as described in this chapter.

The SAP R/3 screen captures in this chapter correspond to SAP GUI version 6.2, and SAP R/3 version 4.0. They are included to illustrate the general nature of the procedures, and contain only example values. Refer to the documentation supplied with your SAP R/3 system to determine the exact procedures.

Figure 7 Distribution Model Hierarchy
Distribution Model

Following this high-level setup, you need to define Communications parameters in SAP R/3 to specify the correct routing of IDocs (either inbound to or outbound from SAP R/3). The hierarchy of this Communication system is shown in the following figure.

Figure 8 Communications Hierarchy
Communications Model

The RFC Destination defines the entity to which Remote Function Calls (RFCs) can be made; it is the same as the Logical System in the Distribution Model. The Communications Port defines a channel for communication of IDocs. The Partner Profile acts as an identifier for the eGate system, and provides a communications gateway by incorporating elements of the ALE interface.