Overview

Before the system where SLL-LEG 1.0 has been installed can provide legal services such as

• Legal Control – Export (LCE)
• Legal Control – Import (LCI), and
• Sanctioned Party List Screening (SPL),

Specific master data records (customer, vendor and material master records) and document data (sales orders and outbound deliveries in SD and purchase orders in MM) have to be transferred from the R/3 system where the logistics processes are managed.

The various settings you need to make in the system where SLL-LEG 1.0 has been installed are described in the following sections:

• ALE Communication
• Customizing

Note:
Throughout this document, the system where SLL-LEG 1.0 has been installed is referred to as the Legal Services System. This is your GTS system. Throughout this document, the R/3 system where logistics processes (SD and MM documents) are maintained is referred to as the Feeder System.

"Legal Services" Cockpit

Fig. 1: “Legal Services” Cockpit

To access the area menu where you can define control settings for system communication with one or more Feeder Systems, click Sys. Communication.

Fig. 2: “System Communication” Cockpit

The settings you make here enable the Legal Services System to receive data from and send status results to the Feeder System.

The

• System Connection and
• Logical System Group

  group boxes are the focus of the following sections. 

System Connection

Before the Legal Services System can communicate with your Feeder System, you must make a range of ALE settings:

• Define Logical System
• Assign Logical System
• Define Target Systems for RFCs
• Maintain RFC Destinations for Method Calls

Define Logical System

Here, you should define the logical system of your own Legal Services System (if you have not already done so) and the logical system of the Feeder System.
The standard naming convention for this is <system name>CLNT<client number>.
Example:
If your Feeder System runs in client 900 of the system called JDL, and the Legal Services System runs in system JDV, client 100, you would define the logical systems for these as follows: 

• JDLCLNT900 Feeder System
• JDVCLNT100 Legal Services System

Assign Logical System

Next, you assign the logical system of your Feeder System to its own separate client.
Example:
If your Legal Services System runs in client 100 of system JDV, you would now assign logical system JDVCLNT100 to client 100.

Define Target Systems for RFCs

You now establish a technical connection between the Legal Services System and your Feeder System.

Fig. 3: Maintain RFC Destinations: R/3 Connections

First of all, you create a new R/3 connection (connection type ‘3’ – R/3 connection).
Standard naming convention: the name of the RFC destination is the name of the target logical system (in this case, the logical system of the Feeder System).
You also have to specify the IP address of the Feeder System as well as the RFC user, client and password to be used for logging on to the Feeder System with RFC calls.
Note:
You must first of all create this RFC user in the Feeder System.
Example:
The name of your Feeder System’s logical system is JDLCLNT900, so you must specify the RFC destination ‘JDLCLNT900’, the connection type ‘3’, the IP address, and the RFC user ’USERRFC’ with the appropriate password in client 900.

Fig. 4: Maintain RFC Destinations: R/3 Connections – Detailed Screen
Note:
You can use the Remote Logon and Test Connection functions to check and test the connection.

Maintain RFC Destinations for Method Calls

You now need to define the standard connection for calling methods. You do this by assigning the RFC destination defined in 2.1.3. as the standard BAPI destination for the Feeder System’s logical system.
Example:
If your Feeder System’s logical system is JDLCLNT900 and the RFC destination you defined is also JDLCLNT900, you would assign the following:

JDVCLNT100                                                 Legal Services System
            > JDLCLNT900                                Feeder System
                        > Standard RFC Destination for BAPI Calls
                                    >JDLCLNT900        Feeder System
 

Logical System Group

If you want to connect several Feeder Systems to the Legal Services System, you can group the Feeder Systems together into logical system groups. This is only possible if certain requirements are met (see section 3.2).

You must make the following settings:

• Definition
• Logical System Assignment

Definition

This is where you define logical system groups that can be used to group together logical systems with (partly) matching characteristics.

Fig. 5: Logical System Group: Definition

Important:
This is a cross-client table!

Logical System Assignment

Next, you assign specific logical systems to a logical system group.

Fig. 6: Logical System Group: Logical System Assignment

Note:
If you want to group together several logical systems into a logical system group, you must ensure that the following requirement is met:
Each master data record must be unique across all Feeder Systems.
In other words, the material numbers, customer numbers and vendor numbers that you assign must all be unique across all systems. This means that if your master data is maintained centrally (using a specially designated master data server, for example), all of the systems involved can be grouped together into a single logical system group.
Note:
Even if you only want to connect one Feeder System to the Legal Services System, you must still define a logical system group for this single Feeder System!

Important:
This is a cross-client table!