Scribd
Upload
1K views

What Is Client Specific & Cross Client Data

This document discusses the differences between client-specific and cross-client data in SAP systems. Client-specific data only affects one client, such as user master records and application data. Cross-client data is reflected across all clients, such as technical settings, system parameters, and repository objects that define the behavior of the entire system. Examples of cross-client customizing objects include measurement units, time zones, dates, currencies, and customizing table data that is shared across all clients.

Uploaded by

PILLINAGARAJU
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
1K views

What Is Client Specific & Cross Client Data

This document discusses the differences between client-specific and cross-client data in SAP systems. Client-specific data only affects one client, such as user master records and application data. Cross-client data is reflected across all clients, such as technical settings, system parameters, and repository objects that define the behavior of the entire system. Examples of cross-client customizing objects include measurement units, time zones, dates, currencies, and customizing table data that is shared across all clients.

Uploaded by

PILLINAGARAJU
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 10

http://vishalchaudharybasis.blogspot.in/2014/01/what-is-client-specific-cross-client.

html

What is Client Specific & Cross Client Data?

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Client Specific – Data is affecting only one client, such as User master and application data

User master data:


http://www.saponlinetutorials.com/user-master-record-sap/
@@@@@@@@@@@@@@@@@@@@@@@@@@@

User Master Record

The concept of user master records User master records defines the user accounts for enabling access to
the SAP system. The user master record is mainly used for user administrative and Authorization
management (Role Administration). Normally, the user master record contains the user id as well as a
wealth of other information which can be used by SAP system administrators in managing users
effectively.

For example, the user master record contains information which validates a user log on session. User
master record stores important information like users access rights to SAP, user's passwords, the
authorization profiles and so on. User master records can be accessed using the Transaction T Code
SU01. In t-code SU01, users can be displayed by user id or in case one does not know the user id, users
can be displayed using all possible entries.

You need authorizations to create or maintain user master records:

Authorization to create and/or maintain user master records and to assign a user group (Auth.object
S_USER_GRP).
Authorization for the authorization profiles you want to assign to users (Auth.object S_USER_PRO).

Authorization to create and maintain authorizations (object S_USER_AUTH).

Authorization to protect roles. You can use this authorization object to determine which roles may be
processed and which activities (Create, Display, Change and so on) are available for the role(s) (object
S_USER_AGR).

Authorization for transactions that you may assign to the role and for which you can assign
authorization at the start of the transaction in the Profile Generator (object S_USER_TCD).

Authorization to restrict the values which a system administrator can insert or change in a role in the
Profile generator (S_USER_VAL)

http://ilovesapsecurity.blogspot.in/2012/03/user-master-record.html

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

How to export user master and authorization profiles in SAP system?


This article answers following queries:

 How to export user master and authorization profiles in SAP system?


 Which tcode is used for user master export in SAP system?
 Which profile to be used to export user master in SAP system?

------------------------------------------------------------------------------------

SCC8 transaction can be used for export of user master and authorization profiles in SAP
system.

Please login to target system and go to SCC8 tcode. SAP_USER profile to be used to export
user master and authorizations in SAP system.

So, please select profile as SAP_USER and input the correct target system and target client
in which user master needs to be imported later.
After that click on “Schedule as Background Job” pushbutton.

It will result in below screen.

Select the

1) Source client which you would like to export


2) Select background server (optional). If it is not selected, load balancing will happen and
client export can happen on any available background server.
3) Please tick "immediately" checkbox (as shown below)
4) Please tick "No Printer Dialog" checkbox (as shown below)

and execute
It will result in below screen asking confirmation to continue.
Please click continue pushbutton to start the export of User Masters.
We should follow above process and export users from all clients that are available in SCC4.
User master export may not be required for clients 001 and 066 (as these are standard
clients).

Please make note of which Export contains which client’s user data so that you can import
them later again (as part of post refresh steps
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

User master list table

USR01 User master record (runtime data)

USR04 User master authorizations

USR05 User Master Parameter ID

USR10 User master authorization Profiles

USR11 User Master Texts for Profiles (USR10)

USR12 User master authorization values

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Application data

cross client customizing?

Well, roughly speaking "repository objects" are the programs and data structures and "cross-client
customizing" is typically referring to technical settings such as communication links, system parameters,
etc.

By allowing changes to "repository and cross-client customizing objects" you allow to modify the
behaviour of the entire (physical) system.

In contrast to that, customizing is normally client-specific allowing to run multiple "logical systems" on
one physical system.

For example: there is only one (physical) user management (subsystem) (=> repository objects) but is
operates client-specific (=> customizing); users are restricted to one specific client - a user "SMITH"
defined in client "001" is different from "SMITH" in client "002". However, password rules are defined
on the system level - effecting all clients / logical systems.
OR

Customizing which is reflected to other client's i.e

throughout the system is called as cross client customizing

Also called as client-independent data

Customization is of two types:

1)Client Specific

2)Cross Client:

Cross client customizing means the change which is meant

for all irrespective of client, throughout a system. All

SAP objects i.e the ABAP codes are cross client.

example for the cross clinet customising object is

measuments.time zine,date,and currency.all are common value

geographically

customizing the table's data which reflects all the clients...!

ie.., the data that is independent of clients is customized..!

This is client independent, sap object are used all the

clients exp ABAP work bench objects

You might also like