CENTRAL USER ADMINISTRATION

Situations Leading to Central User Administration (CUA)

Complex system landscapes. Manual Maintenance of

user information in all the available systems.

Tedious Administrative task

Complex administrative job may lead to Security problems

9/4/2012

Central User Administration using ALE

Users can be administrated in a central system. Central user administration reduces the maintenance and synchronization issues faced by authorization administrators. Automatic distribution of users to the child systems. Local administration still possible.

9/4/2012

Concept Of Central User Administration

9/4/2012

SYSTEM

SETUP

Setting up ALE user for all clients. Creating Logical Systems. Assigning Logical Systems to Clients. Define Target systems for RFC calls. Creating Distribution model in the central system. Generating Partner profiles in central system. Distributing Model views.

9/4/2012

 Generating Partner profiles in client system. Assigning the Central User Administration distribution Model. User distribution field selection Testing Central User Administration. Migrating Existing Users to Central System (SCUG) Testing Migrated Data in Central System. Log display for Central User Administration

9/4/2012

Configuration
Central Client
CLIENT 800 User Master Record

LS800(Logical System)

SAP SYSTEM

LS810(Logical System) User Master CLIENT 810 Record

7

Child Client

9/4/2012

Setting up ALE User for Central System(SU01)

9/4/2012

9/4/2012

10

9/4/2012

11

9/4/2012

Setting up ALE User for Client System(SU01)

12

9/4/2012

13

9/4/2012

14

9/4/2012

15

9/4/2012

Creating Logical Systems(BD54)

16

9/4/2012

17

9/4/2012

18

9/4/2012

Assigning Logical Systems to the Clients (SCC4)

19

9/4/2012

20

9/4/2012

Define Target Systems for RFCS Calls for Central System(SM59)

21

9/4/2012

22

9/4/2012

23

9/4/2012

RFC Connection Test

24

9/4/2012

Define Target System for RFCS Calls for Client System(SM59)

25

9/4/2012

26

9/4/2012

27

9/4/2012

RFC Connection Test

28

9/4/2012

Creating Distribution Model in Central System(BD64)

29

9/4/2012

30

9/4/2012

Adding BAPIs(BD64)

31

9/4/2012

32

9/4/2012

33

9/4/2012

New Distributed Model

34

9/4/2012

Generating Partner Profiles in Central System(BD64).

35

9/4/2012

36

9/4/2012

37

9/4/2012

Distribute Model Views.

38

9/4/2012

39

9/4/2012

Model View Distribution Logs

40

9/4/2012

Generate Partner profiles in Client System ( BD64).

41

9/4/2012

Assigning the Central User Administration distribution Model (SCUA).

42

9/4/2012

43

9/4/2012

Display Logs

44

9/4/2012

Display System Landscape in Client System (SCUA)

45

9/4/2012

46

9/4/2012

Defining Attributes for Field Maintenance (SCUM)

47

9/4/2012

Testing Central User Administration Create User in Central System (SU01)

48

9/4/2012

49

9/4/2012

Data Transfer

50

9/4/2012

51

9/4/2012

Log on to Client System for Testing

52

9/4/2012

53

9/4/2012

Migrating Existing Users to Central System (SCUG)

54

9/4/2012

55

9/4/2012

Testing Migrated Data in Central System(SU01)

56

9/4/2012

57

9/4/2012

Displaying Log For CUA (SCUL).

58

9/4/2012

59

9/4/2012

Removal Central User Administration

Log on central system and run RSDELCUA to delete one of the child system Delete message types clone and user clone for the selected child system Delete the complete partner model Execute BD64 and in change mode delete the methods for deleted child and save it Log in to every child system to be deleted. Run RSDELCUA report Once this is done complete partner profile can be deleted. Need not to delete RFC connections
60

9/4/2012

Log on central system and run RSDELCUA

61

9/4/2012

62

9/4/2012

63

9/4/2012

Reorganize CUA Tables

64

9/4/2012

65

9/4/2012

Execute BD 64 and Delete the Methods and Model in Central system.

66

9/4/2012

Log on Client system and run RSDELCUA

67

9/4/2012

68

9/4/2012

69

9/4/2012

Advantage of Central User Administration

Maintain user mater records centrally in one system

Make administrative job easy. Less possibility of user data inconsistency. Time Saving.

70

9/4/2012

71

9/4/2012