‎2006 Jul 25 10:27 AM
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
‎2006 Jul 25 10:50 AM
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
‎2006 Jul 25 10:50 AM
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
‎2006 Jul 26 2:28 AM
‎2006 Jul 26 9:46 AM
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.
‎2006 Jul 25 12:58 PM
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.
‎2006 Jul 25 1:00 PM
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.