client configuration

[former_member97292]

For example, one landscape with various clients: 200 for DEV, 300 for QA. If I configure in client 100, do I then transport that configuration to clients 200 and 300?

What I am asking is does each client in a landscape have its own configuration? The clients would use the same software with different configurations, causing posting of transactions to be different in each client.

Thank you.

[Paul_Babier · Accepted solution]

Hello Perry,

If I am understanding you correctly, each client is customizable. Customizing to one client does not make those changes to another client. You can copy clients, and make further customizing to copied clients. Some customizations are client specific and others are cross-client ( meaning affecting all clients). So based on that, can you be more specific? Or does this help?

Regards,

Paul

[former_member97292]

Hi, Paul

When you say customizable, do you mean the configuration? If those are the same, then you understand my question. We're new to SAP and are increasing our understanding of SM daily. Slowly.

Your answer: each client in a landscape may have its own configuration. A transaction in client 200 can be configured to process/post differently than the same transaction in client 300, even though the two clients are in the same landscape. Also, I understand that some configurables are cross-client and affect all clients in a landscape. Correct?

Thank you. I appreciate your help.

Edited by: Perry DuBard on Feb 24, 2011 7:46 PM

[Paul_Babier]

Hello Perry,

First Clients are not unique to Solution Manager, but exist in all SAP systems.

Here is the definition, because it will help clarify for you.

Client

Definition

A commercially, organizationally, and technically self-contained unit within an SAP System. Clients have their own master records and set of tables.

The definition of the client organizational unit is obligatory.

Use

The client is the highest level in the SAP System hierarchy. Specifications that you make, or data that you enter at this level are valid for all company codes and for all other organizational structures. You therefore only need to make these specifications, or enter this data once. This ensures that the data is consistent.

Users must enter a client key when they log on to the SAP System. This defines the client in which they wish to work. All the entries you make are saved per client. Data processing and analysis is also carried out per client.

This means that you cannot include customer accounts from different clients in one dunning run.

Access authorization is assigned per client. You must create a user master record for each user in the client where he or she wishes to work.

The SAP System is delivered with the clients 000 and 001 - these clients already contain default settings. For more information, see Setting Up Clients in Customizing. These sections are automatically selected when you create your implementation projects (company IMG, project IMG).

Further to this clients 000 and 001 should typically be used as refernce clients and NOT working clients. This way you can have a Standard Default Client you use as a reference client for copying a new client.

And for the most part in the SAP world Customizing does mean configuration, but it can also mean customization as in custom code, so it can be more than configuration, and actually include customizations.

I hope this has answered your question now

Regards,

Paul

[Former Member]

hi

And you can control the customizaion in the client by the system wise,check here

[client control|http://help.sap.com/saphelp_nw04/helpdata/en/57/38dea84eb711d182bf0000e829fbfe/content.htm]

Jansi