Entering content frame

Procedure documentation Configuring ALE and qRFC Connections for Third-Party Business Locate the document in its SAP Library structure

Use

This section contains all the steps necessary to set up an Application Link Enabling (ALE) and a queued Remote Function Call (qRFC ) connection for third-party business in the system landscape (1 SAP APO, 2 SAP R/3). In this scenario the SAP APO system is connected to the sales and supplying systems.

Procedure

  1. Define the logical systems in the sales system, the supplying system, and the SAP APO system.

    2. In Customizing for Basis, choose Application Link Enabling (ALE) ® Sending and Receiving Systems ® Logical Systems ® Define Logical System.

    Example: Logical systems

    Logical System

    Description

    R3VCLNT001

    Sales system

    R3LCLNT001

    Supplying system

    APOCLNT001

    SAP APO system
  2. Assign the relevant logical system to the client you are using. Do this in the sales system, the supplying system, and the SAP APO system.

    3. In Customizing for Basis, choose Application Link Enabling (ALE) ® Sending and Receiving Systems ® Logical Systems ® Assign Client to Logical System.

  3. Define the target systems for RFC calls.

    4. In Customizing for Basis, choose Application Link Enabling (ALE) ® Sending and Receiving Systems ® Systems in Network ® Define Target Systems for RFC Calls. Choose R/3 Connections.

    This graphic is explained in the accompanying text

    In the Log On subscreen, enter a new user (such as ALEREMOTE) that you have previously created in the target system. To create the user in the target system, from the SAP Easy Access screen, choose Tools ® Administration ® User Maintenance ® Users.

  4. Specify the RFC destinations for RFC method calls.

    5. In Customizing for Basis, choose Application Link Enabling (ALE) ® Sending and Receiving Systems ® Systems in Network ® Synchronous Processing ® Determine RFC Destinations for Method Calls.

    Example: RFC destinations for method calls

    SAP R/3 Sales System

    SAP R/3 Supplying System

    SAP APO System

    Logical system: R3LCLNT001

    Assignment:

    Standard RFC destination for BAPI calls (R3LCLNT001)

    Standard RFC destination for dialog calls (R3LCLNT001)

    Logical system: R3VCLNT001

    Assignment:

    Standard RFC destination for BAPI calls (R3VCLNT001)

    Standard RFC destination for dialog calls (R3VCLNT001)

    Logical system: R3VCLNT001

    Assignment:

    Standard RFC destination for dialog calls (R3VCLNT001)

    Logical system: R3LCLNT001

    Assignment:

    Standard RFC destination for dialog calls (R3LCLNT001)
  5. Create a central system (for example, the sales system) for distribution.

    6. In this system, create a distribution model to specify which messages are sent to a logical system. To do this, in Customizing for Basis choose Application Link Enabling (ALE) ® Modeling and Implementing Business Processes ® Maintain Distribution Model and Distribute Views.

    Create the distribution model with the following message types:

    Example: Distribution model

    Sender

    Receiver

    Message Type

    Client 001 (R3VCLNT001)

    Client 001 (R3LCLNT001)

    ORDCHG PO/order change

    ORDERS PO/order

    Client 001 (R3LCLNT001)

    Client 001 (R3VCLNT001)

    DESADV Delivery: Shipping notification

    INVOIC Invoice/billing document

    ORDRSP PO confirmation/order confirmation

    When you create the distribution model, you can also work with a data filter. For more information, see the documentation for the IMG activity Maintain Distribution Model and Distribute Views.

    Distribute the model from the central system to the other systems (for example, from the sales system to the supplying system). To do this, from the Change distribution model screen choose Edit ® Distribute model view. The receiver of the model view is, for example, the supplying system (R3LCLNT001). Here the system creates a copy of the distribution model.

  6. Make the following settings in the sales system.
    1. Create the partner profile. To do this, in Customizing for Basis choose Application Link Enabling (ALE) ® Modeling and Implementing Business Processes ® Maintain Distribution Model and Distribute Views. Choose Distribution Model ® Switch Processing Mode. In the distribution model, select the client in the sales system and choose Environment ® Generate Partner Profiles.

      2. For the partner system (supplying system, in the example R3LCLNT001), the system automatically creates the message type SYNCH (ALE: dummy message type for determining the RFC destinations) and a port (for example, A000000015).

      For further information, see Structure linkDefining Partners.

    2. Check the partner profile with the supplying system.

In Customizing for Basis, choose Application Link Enabling (ALE) ® Modeling and Implementing Business Processes ® Partner Profiles and Time of Processing ® Maintain Partner Profile Manually. Choose the partner type LS and the partner number of the supplying system.

Note

The message types ORDERS and ORDCHG are generated automatically with basic type ORDERS05. Create another inbound parameter using message type INVOIC, message variant MM, and transaction code INVL.
  1. Make the following settings in the supplying system:
    1. To do this, in Customizing for Basis choose Application Link Enabling (ALE) ® Modeling and Implementing Business Processes ® Maintain Distribution Model and Distribute Views.

      2. On the Change Distribution Model screen, choose Environment ® Generate Partner Profiles. For the partner system R3VCLNT001, the system automatically creates the message type SYNCH (ALE: dummy message type for determining the RFC destinations) and a port (for example, A000000015).

    2. Check the partner profile with the sales system.

In Customizing for Basis, choose Application Link Enabling (ALE) ® Modeling and Implementing Business Processes ® Partner Profiles and Time of Processing ® Maintain Partner Profile Manually. Choose the partner type LS and the partner number of the sales system.

Note

Check the inbound parameter with the message type ORDERS. It must have the process code ORDE. Change the parameter if necessary.
  1. Set up the SAP APO system as the target system in both SAP R/3 systems, in order to make a connection to the SAP APO system.

From the SAP Easy Access screen, choose Logistics ® Central Functions ® Supply Chain Planning Interface ® Core Interface Advanced Planner and Optimizer ® Settings ® Target Systems. Enter the logical system of the SAP APO system, and enter the operation mode (T Transactional events active (standard)).

For more information, see the SAP APO documentation under Supply Chain Management (SCM) Business Scenarios ® Integration of APO and R/3 ® APO Core Interface ® Setting Up the System Infrastructure and Data Transfer ® Settings in R/3 ® Set Target System.
  1. Maintain the SAP APO release in both R/3 systems. On the SAP Easy Access screen, choose Logistics ® Central Functions ® Supply Chain Planning Interface ® Core Interface Advanced Planner and Optimizer ® Settings ® APO Releases.

For more information, see the SAP APO documentation under Supply Chain Management (SCM) Business Scenarios ® Integration of APO and R/3 ® APO Core Interface ® Setting Up the System Infrastructure and Data Transfer ® Settings in R/3 ® Maintain APO Release.
  1. Make the following settings in the SAP APO system:
    1. Maintain a business system group.

      2. To do this, from Customizing for Advanced Planner and Optimizer (APO), choose Basis Settings ® Integration ® Business System Group ® Maintain Business System Group.

      In this scenario you maintain exactly one business system group. The master data must be unique in both SAP R/3 systems.

      The BSG typically represents a namespace for the master data. If two SAP R/3 systems are in the same business system group (BSG), then for example, material QIR001 in one of the systems in SAP APO represents that same product as material QIR001 from another system. The materials must therefore be unique in both SAP R/3 systems. Plants must only exist in one system.

      Note

      If the material or the plant is part of a condition for the rule-based ATP check, the material must represent the same product in both the sales and supplying system, or the plant must only exist in one system.

    2. Assign the logical systems to the business system group.

      3. To do this, from Customizing for Advanced Planner and Optimizer (APO), choose Basis Settings ® Integration ® Business System Group ® Assign Logical System and Queue Type.

    3. Enter the user exits for locations (ZXCIFUSERU06) and products (ZXCIFUSERU08) in an enhancement project (transaction CMOD) in SAP APO.

Note

Master data usually has the suffix @BSG, where BSG stands for the name of the business system group. Plants usually have the prefix PL.

For more information, see the SAP APO documentation under Supply Chain Management (SCM) Business Scenarios ® Integration of APO and R/3 ® APO Core Interface ® Setting Up the System Infrastructure and Data Transfer ® Settings in APO.

See also:

 

Structure linkALE Quick Start

Structure linkIDoc Interface: EDI Application Scenarios (BC-SRV-EDI)

Structure linkElectronic Data Interchange/IDoc Interface (SD-EDI)

Link to external website Technical Integration

 

 

 Leaving content frame