Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Repository and cross-client customizing objects

Former Member
0 Likes
6,526

Hi,

I'm new to SAP so sorry if this sounds stupid.

I would like to know what "repository and cross-client customizing objects" do in SAP. On T000, you can check whether a client allows changes on the "repository and cross-client customizing objects".

What is the implication if changes are allowed? Thanks!

Dan

1 ACCEPTED SOLUTION
Read only

Wolfgang_Janzen
Product and Topic Expert
Product and Topic Expert
2,582

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.

Cheers, Wolfgang

5 REPLIES 5
Read only

Wolfgang_Janzen
Product and Topic Expert
Product and Topic Expert
2,583

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.

Cheers, Wolfgang

Read only

0 Likes
2,582

Thanks Janzen. It's very useful.

Read only

0 Likes
2,582

If you want to see an example of a potential implication from "leaving the system open", take a look at how the function module TR_SYS_PARAMS is used in the include LSUTLU01.

Read only

Former Member
0 Likes
2,582

When you try to maintain T000 from tcode SCC4 etc... then a popup appears which explains it:

Message no. TB 113

Diagnosis

You are in the process of maintaining a cross-client table. You are using the standard table maintenance screen here, which is frequently used to maintain client-specific customizing entries. This message serves to warn you that each change you make will have an effect on all other clients in the system!

System Response

You have the apporpriate authorization for cross-client maintenance.

Procedure

Take a second thought about the effect of your changes. Due to logical dependencies between client-specific customizing and applications data on the one hand and cross-client customizing data on the other hand, changing or deleting cross-client data could result in inconsistencies.
Therefore such changes should be carefully planned and coordinated, taking all the clients in the system into consideration.

Read only

Former Member
0 Likes
2,582

When you try to maintain T000 from tcode SCC4 etc... then a popup appears which explains it:

Message no. TB 113

Diagnosis

You are in the process of maintaining a cross-client
table. You are using the standard table maintenance
screen here, which is frequently used to maintain 
client-specific customizing entries. This message 
serves to warn you that each change you make will 
have an effect on all other clients in the system!

System Response

You have the apporpriate authorization for 
cross-client maintenance.

Procedure

Take a second thought about the effect of your changes.
Due to logical dependencies between client-specific
customizing and applications data on the one hand and
cross-client customizing data on the other hand, 
changing or deleting cross-client data could result 
in inconsistencies.
Therefore such changes should be carefully planned 
and coordinated, taking all the clients in the 
system into consideration.