SAP ALE

Setting up ALE is the first step in implementing CUA. Fortunately, as
an SAP Web Application Server (Web AS) administrator, the transaction
SALE will lead you through the steps necessary to implement ALE. This
is a three-part process. The first part of this process involves defining a
logical system. Next, you will assign clients to the logical systems. Finally,
you define target systems for RFCs. In the following sections, you will
learn about each of these steps.

From transaction SALE, follow:Modelling and Implementing Business
Processes → Predefined ALE Business Processes → Cross-Application
Business Processes → Central User Administration → ALE Mandatory
Activities for Central User Administration.

You assign the logical system names to the client
definitions in the corresponding systems in transaction SCC4.

Communications between the central system and the sub-systems use the
network with an Remote Function Call (RFC). Youmaintain the technical
definition of the link in transaction SM59.

The RFC link names must
be the same as the names of the logical systems.

You then activate the Central User Administration with transaction SCUA.

Note: If you have 10 clients that will participate in CUA,
you must define 10 logical systems. SAP suggests the
following naming convention: <SID>CLNT###. Thisway, the
logical system name DEVCLNT101 clearly provides a unique
label/identifier for client 101 in SAP system DEV.

If you periodically refresh one system with a copy
from another (heterogeneous system copy), such as copying
your PRD production system back to your QAS testing system,
you must adapt your procedure to include renaming the
logical systems in QAS. Logical system names must be unique!
OSS Notes for CUA and Client Copies
OSS Note Number OSS Topic
399917 CUA: Moving of a CUA via Client or
System Copy
197728 Deleting the CUA completely or
cleaning up data
191449 CUA: Central User Administration
191207 CC-TOPIC: Client Copy and Central
User Administration
4. Choose Save.
16

An RFC destination is always created from the client in
which you are logged on to. For example, to define an RFC
link from client 101 to client 500, you must be logged on to
client 101. Central user administration RFC links must always
be two-way. To define the RFC link completely, you must also
log on to client 500 and define client 101 as an RFC destination.

When you install Central User Administration in a productive
environment, the existing users of the system infrastructuremust be copied
to the central system. This procedure is called migration. The migration
process enables you to compare and adjust the user identifications that
were copied from the sub-systems.