Overview

Before an R/3 system can call 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 into the system where SLL-LEG 1.0 has been installed.

The various settings you need to make in the R/3 system 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.
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

The Cockpit for Legal Services in the Feeder System (transaction /SAPSLL/MENU_LEGALR3) is a single screen from which you can access all of the necessary programs and functions for establishing and regulating communication between the Feeder System and the Legal Services System.

Fig. 1: “Legal Services” Cockpit

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

The

• Transfer to Legal Services and
• Basic Settings

group boxes are the focus of the following sections. 

When you click Basic Settings, you access a transaction where you can maintain settings for change pointer management and system communication (via ALE).

Fig. 2: “Legal Services” Cockpit: Basic Settings

Note:
You must maintain these settings regardless of the services you wish to use.

Basic Settings

You must define basic settings for the following:

• System communication (via ALE)
• Change Pointers

System Communication

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

• Define Logical System
• Assign Logical System
• Maintain RFC Destinations for RFC Calls
• Maintain RFC Destinations for Method Calls
• Maintain ALE Distribution Model

Define Logical System

Here, you should define the logical system of your own Feeder System (if you have not already done so) and the logical system of the Legal Services 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 Feeder System runs in client 900 of system JDL, you would now assign logical system JDLCLNT900 to client 900.

Maintain RFC Destinations for RFC Calls

You now establish a technical connection between your Feeder System and the Legal Services 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 Legal Services System).
You also have to specify the IP address of the Legal Services System as well as the RFC user, client and password to be used for logging on to the Legal Services System with RFC calls.
Note:
You must first of all create this RFC user in the Legal Services System.
Example:
The name of your Legal Service System’s logical system is JDVCLNT100, so you must specify the RFC destination ‘JDVCLNT100’, the connection type ‘3’, the IP address, and the RFC user ’USERRFC’ with the appropriate password in client 100.

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 Legal Services System’s logical system.
Example:
If your Legal Service System’s logical system is JDVCLNT100 and the RFC destination you defined is also JDVCLNT100, you would assign the following:

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

Maintain ALE Distribution Model

Finally, you need to set up the ALE Distribution Model. First of all, use the Create Model View function to create a new distribution model.

Fig. 5: Maintain Distribution Model: Add New Model

Example:
You create a new distribution model called ’SLL-LEG’.

Next, use the Add BAPI function to assign object/interface CustomsDocumentIF and its method (SynchronizeIfR3) to the logical system of the Feeder System (sender system) and to the logical system of the Legal Services System (receiver system) for your new distribution model. 
Example:
Within distribution model ’SLL-LEG’, you assign object/interface CustomsDocumentIF and method SynchronizeIfR3 to the sender system JDLCLNT900 (Feeder System) and the receiver system JDVCLNT100 (Legal Services System). 

Fig. 6: Maintain Distribution Model: Add New Model: Add BAPI

Change Pointers

Essential information from the

• Customer master
• Vendor master, and
• Material master

has to be transferred from the Feeder System to the Legal Services System. Information about new and changed master data records also has to be passed on to the Legal Services System. 
These changes are recorded using ALE change pointers, and then transferred asynchronously to the Legal Services System.

Activate Change Pointers Globally

First of all, you need to generally activate the change pointers.

Fig. 7: Activate Change Pointers Generally

Activate Change Pointers for Message Types

Next, you activate the change pointers for specific message types:

Fig. 8: Activate Change Pointers for Message Types

Transferring Documents to Legal Services

Before you can call the Legal Control – Export, Legal Control – Import or Sanctioned Party List Screening services, you have to transfer the document data to the Legal Services System.
Customs documents are then created in the Legal Services System. The services are executed on the basis of these documents.

Customizing

In the Feeder System, you must specify which documents are to be transferred to the Legal Services System. These documents are identified by document type.

 
Fig. 9: Control: Call Legal Services: Overview
You can specify whether the documents assigned to a specific document type at an application level should be transferred.

The application level refers to the processing level of the documents. The following levels are possible:

• SD0A – Dispatch / Export: Sales Order Document
• SD0B – Dispatch / Export: Outbound Delivery
• SD0C – Dispatch / Export: Customer Invoice Document
• MM0A – Receipt / Import: Purchase Order Document
• MM0B – Receipt / Import: Inbound Delivery
• MM0C – Receipt / Import: Goods Receipt Document (Materials Docum.)

Furthermore, you can specify whether the system should issue an error message if a document is created in the Feeder System but its document type is not maintained here.
Example:
A sales document (document type ‘OR’) is created in the Feeder System. This document type has not yet been defined in the Feeder System. You have specified that the system should issue an error message if a document is created at application level SD0A but the document type in question has not yet been defined. 

Fig. 10: Control: Call Legal Services: Document types

Additionally, you can specify whether a pop-up status message should be issued in the Feeder system when you save a document and it is going to be blocked due to a “Not OK” result for one or more of the services called in the Legal Services System.
Example:
The pop-up ‘Document blocked due to Legal Control – Export’ is displayed.
Note:
Currently, only documents for document levels SD0A, SD0B and MM0A can be transferred to the Legal Services System.

Only documents with document types where the ‘Transfer Legal Services’ field is flagged are transferred to the Legal Services System.
The system issues a pop-up status message only for documents with document types where the ‘Dialog Legal Services’ field is flagged.