Training Client

Are there any data standards ( master and transactional) to ensure the Training client has all the necessary data to allow participants to be actively involved in training. I am thinking of taking a 3 months Transactional data cut from Production and perform some data quality standards review before the Training client is available for use. Are there any criteria for setting up a good training client. Any articles are welcome.
Thanks

Hi,
I suppose you can use the SAP IDES server, for training purpose as it has all the relevant data across industries, instead of creating a client with production data.
Regards,
Varadharajan M

Similar Messages

Loading data from SRM training client

Hello all,
I want to create another source system in BW to image a training client in SRM. i.e. to say having SQCLNT100 as my QA and SQCLNT200 as my training client.
What is the best practice? should I mix the data from the two source systems in one warehouse model, or do I create separate model for each of the source systems?
Regards.

Hello BW,
Can anybody help me out with the above problem?
Thanx

New Training Client - how to build?

We have a training client (3 yrs old) with training exercises, training users etc.
We need to build a new training client based on the config. of our live system but minus the live data.
We will then need to get the exercises etc. back onto new client.
What is the best way to go about this.
thanks.
Marie

This sounds like a client copy minus the Application data.
In a client copy you cannot move part of the Application data, so I suggest you copy the client using only the Configuration and User Master Records. The Profile SAP_UCUS would work for this.

How to train client to update muse

How does one enable client to update a muse website? Thx!

They have two options:
1 - Use In-browser editing for minor updates
2 - Use Muse for bigger updates
If you can provide a bit more information about your situation we might be able to give a more precise answer.

How to refresh training system/client

Hi Experts,
I have a ECC6.0 IDES which is used for training purposes.Now the database(/oracle file system) is approaching 100%.
Can anyone let me know how can I refresh the system ( by scheduling any background job? not sure).
Actually the client 001 is to be refreshed.Because training runs on 001 client.
Thanks and Regards,
Moulinath Ray

if you use 001 as the trainig client, then you alter the data in this client, so you cannot use it as a master client.
The 8xx clients are preconfigured IDES-clients and i wouldn't use them as training clients.
You should configure a client (e.g. 001) according to your needs and then create a new client. You can logon to this new client with user/pw sap*/pass (if the profile parameter login/no_automatic_user_sapstar is set correctly, if not adjust and activate the profile and restart your system). Then you can do a client copy from 001 to the new client. When the training is done, just copy 001 again to the new client, so the trainers have a fresh training client.
If you want to remove the client you can use tcode SCC5. I wouldn't delete the data on database level
Edited by: Ulf Brinkmeier on Feb 3, 2009 1:01 PM

Use of client dependent tables

Hi Gurus,
I have read many threads on difference between client dependent and independent data/objects etc.
But, someone tell me please, wheat exactly the 'Use or Advantage' of client dependent tables/data.
Thanks in advance.
V

HI,
The use of client dependent tables is that if data in one table of a particular client is updated then that data wont be seen in any other clent it provides a security to the data we retrict users with their authorizations in differen clients
When you log on to an SAP System, you log on to a particular client of this system. Any activities you carry out in the system are always carried out in one client. When you plan your SAP system landscape, you must consider which clients you need for which activities.
By assigning activities to be performed in a client, you give each client a particular role. This section describes the most important client roles.
Since you need to adapt the SAP software for your own business needs, each SAP system landscape requires a client where Customizing settings, and possibly ABAP Workbench developments, can be made. This client is known as the Customizing and development client, or Customizing client for short. The abbreviation CUST is used for this client.
Before you can use the Customizing settings and Workbench developments productively, you need to test them extensively for errors. Any faulty settings can seriously disrupt productive operations, and at worst, lead to the loss of productive data. The integrated nature of the various SAP applications means that there are many dependencies between the different Customizing settings. Even an experienced Customizing developer may not discover these dependencies immediately. The correctness of the settings can only be guaranteed with extensive testing. The client where these tests are made is the Quality Assurance Client, QTST for short.
A separate client is required for productive use of the SAP System. So that this client can be used without disruption, it is essential that no Customizing settings or Workbench developments are made here, and also that no tests are carried out. This client is known as the Production Client, PROD for short.
These three clients, CUST, QTST and PROD, are the central clients that exist in every system landscape. Standard system landscapes have precisely one client for each of these client roles.
We recommend that you make all your Customizing settings in a single Customizing client, and then use the CTS to transport them to the other clients.
We also recommend that you do not make any Customizing settings or Workbench developments in the quality assurance or production clients. You can make sure of this by making appropriate client settings.
In addition to the central clients, you can also set up other clients for other tasks. However, you must remember that each extra client takes up additional system resources (main memory and database space). They also need to be administrated. For example, you need to set up and administrate access authorization for the users, and also distribute any changes to other clients with the CTS. You must weigh up the advantages and disadvantages of setting up other clients.
Examples of other client roles are:
Development test client (TEST): Developers can use this client to test their Customizing settings and Workbench developments, before they release their change requests. In this client the developers can create test application data for realistic tests. If they discover errors, they can remove them in the Customizing client. A development test client is always set up in the same SAP System as the Customizing client. This means that any changes that are made to cross-client data in the Customizing client are also immediately visible in the development test client. Changes to client-specific data are copied from the Customizing client to the development test client using a special client copy function. The client copy function uses the unreleased change requests from the Customizing client to do this. The development test client is set so that you cannot make changes to Customizing data and Repository objects.
Prototype or sandbox client (SAND): You can use this client to test any client-specific Customizing settings if you are not sure whether you want to use them in this form. Any settings that you want to keep are then entered in the Customizing client. To prevent conflicts between the prototype client settings and real settings in the Customizing client, you cannot make changes to cross-client Customizing data and Repository objects in the prototype client. The CTS does not record changes made to client-specific Customizing data, and does not transport them from the prototype client. You can make sure of this by making appropriate client settings.
Training client (TRNG): To prepare end users for new functions that are to be transported into the production client, you can set up a training client. The users can use the new functions in this client with specially created application data. This client is set so that you cannot make changes to Customizing data and Repository objects.'''
plzz reward if this information is usefull to u plaa dont forget to reward

Transfer master data from a project from one client to another client

Hi all,
I have a training client and a production client. The project master data has been created (Tcode CJ01) in training client with multiple levels and WBS. Is there a way to transfer the master data from the training client to another client so there will be no need to create the same project in another client?
Thanks.

Refer note for 37899 batch input option.
Though this pertains to older versions with few changes to code it might be suitble to the version you are working on.
Regards
Sreenivas

Client Delete and Logical System and CUA

I'm getting ready to do some client clean up in prep for an upgrade from ECC 5 to ECC 6 soon.
Currently we have a 3 system landscape: DV1 QA1 PR1
Clients on these systems are as follows: (not including 000, 001, 066)
PR1:100 - the production client
QA1:100 - Integration Master - not used except for RFC connections for Solution Manager
QA1:110 - Cycle 1 testing - not used
QA1:120 - Cycle 2 testing - not used
QA1:200 - Old training master client - not used
QA1:201 - Old training client - not used
QA1:710 - no longer being used for testing
QA1:720 - client used for system and integration testing
DV1:100 - Configuration - not used
DV1:110 - ABAP development
DV1:120 - Configuration
DV1:700 - Template for test - not used
DV1:710 - Test with prod data
Most have a logical system defined for the client.
I am going to delete those I've underlined above as they are no longer used.
Some of these are setup in the CUA system.
All are showing up in Solution Manager SMSY system landscape.
My plan is to backup the system database first!
Then:
1) Delete the client(s) (SCC5) one by one
2) Remove the client from CUA (SCUA)
3) Remove the logical name (SALE)
What I am unsure about is the order of the process. Should the CUA and ALE modifications come before actually deleting the client?
Does this sound like a reasonable plan to clean up our client landscape?
Thanks in advance for your suggestions and help.
Laurie McGinley

Dear Laurie,
Order should be like below:
1) Remove the client from CUA (SCUA)
2) Delete the client(s) (SCC5) one by one
3) Remove the logical name (SALE)
More over you should delete these clients from Solution Manager also inorder not to have error message when you go to solution Manager for doing anything on that system.
Please revert back for any queries.
Regards
Shailesh Mamidwar

Single file to multiple IDOC's (on Multiple R3 Clients):

Hi,
We have a complex Landscape with multiple (4) businesses (multiple R3) instances and most common R3 --> DEV 4 instances with 5 clients each, QAS 4 instances with 2 clients each with some additional clients, PRD 4 instances with a client each and Training 4 instances with 2 clients each in the Landscape along with BW systems.
We are trying to implement standard MDM - XI - R3 distribution scenario. Only difference being MDM Production will be the Master distribution client and have to be distributing to all the R3 clients. For those who doesn't know SAP MDM - is Master Data Management Engine and within this scenario the output from MDM is standard XML IDOC file.
To achieve this syndication is being planned as MDM production to distribute files to 4 businesses to 4 file share folders. These files will be picked up by XI production and will be distributing(Creating IDOCs) on multiple receivers (R3 --> DEV, QAS and PRD) clients of the respective instances.
The one to one scenario is very simple to build MDM XML file from file adapter to R3 IDOC of IDOC adapter, but for our business it becomes one file to multiple R3 clients (IDOCs) on multiple R3 instances;
My question is: Is there an easy way to configure single file to mutiple R3 client IDOC receivers scenario? Also there might be additions and deletions of the R3 clients based on business requirements. Is there any proposed or already implemented procedure to achieve this complex distribution?
We have planned on trying to define a business system for each R3 client (DEV/QAS/PRD) and to have the integration directories configuration built for all the 47 clients that the data needs to be distributed. With IDOC Adapter is this the only way to go? Also, in future if there are additions or deletions of clients it becomes maintenance intensive and there won't be a quick way to stop the distribution?
Your time and input is appreciated.
Thanks and Regards,
-Raj.

Michal,
Thanks for your answer and FAQ.
I think I am confusing everyone with my long messages!
We already have XI DEV, XI QAS, XI PRD.
But business requirement for the global harmonization MDM scenario is that MDM PRD should be able to distribute the XML files (IDOC fields in GLMAST01 - IDOC format) to all the DEV, QAS and PRD (R3) systems in the landscape. For this distribution XI is used as the integration partner (File adapter picks up the XML file from MDM file share location and IDOC adapter creates an IDOC on the respective R3).
For this specific scenario though XI-DEV and XI-QAS systems are present they are available only for testing phase. After the scenario is moved into production, XI-PRD should be able to pick up the XML file from MDM and distribute it to all the DEV, QAS, PRD R3 systems.
Same file needs to be distributed to 20 DEV clients across 4 DEV instances, 27 QAS clients across 4 QAS instances and 12 PRD/TRN(training clients).
Yes, as you said in your answer earlier deleting a client from the distribution is removing the client from the receiver determination (and removal of corresponding Interface determination, sender agreement and receiver agreement).
Addition of a client for distribution is adding the client (business system) in receiver determination (and addition of of corresponding Interface determination, sender agreement and receiver agreement).
Do I have to maintain all the 59 (Clients from different systems) sets of config within the ID and all the systems in SLD of XI - DEV/QAS/PRD? Even if I do so, Is this the right way to go, defining all the DEV/QAS/PRD clients within all the SLD's of XI - DEV/QAS/PRD?
I am not finding an easy way to architect this.
I appreciate your time and patience.
Thanks and regards,
Rajani Kanth Yalamanchili.

Client Roles in a Three System Landscape

I initially post this Question in other forum:
Hi all,
We have a three system landscape. In the Development client, we have the Customizing Client, the Sandbox Cliet and a Training client. I have some questions about this configuration:
Acording to System and Client Settings - System Administration Assistant (BC-RRR) - SAP Library, Training client must be in Quality Assurance System, and it must be created by client copy from client QTST (it gets the transports from Custimizing). In this Training System we must create users for all our key-users to training. We must not create any user for key-users in sandbox client (this client is for the DEV team). is that ok?
What are the downsides of having out TRAINING client in the Development System?
Now, a consultant is asking me to open some modifications in the TRAINING client: He needs to load Exchange rates (OB08) in that client, but he is getting "Client is not modifiable". They are asking me to create users for key-users in the sandbox client and the training client.
I need to know if they are using the system in the right way. I dont want the system to become a mess.
I been reading this notes: SAP Note 356483. I don´t know what this means: "Now the corresponding Customizing object is no longer subject to the transport connection and is excluded from the changeability check. The change is active in all clients of the system. You can also change the Customizing object in a locked client (independent of the client role). However, now it is also no longer possible to manually transport entries of the view or table."
Aditional notes:
SAP Note 78329, sap kb 356483
Thanks for your help!
One person answere me this:
Hi
You should create your question in the appropriate area :
Software Logistics
The drawback of having training client in dev system is that it could be negatively impacted by ongoing changes performed in that system (custom program that are changed, not working...)
Some specific customizing changes can be set as current setting and thus can be modified without needing to open customizing but only if the client is set as productive.
There is also a way do deactivate modification recording of objects (aka deactivating the transport connection) but, if you apply this change for this activity/object, you won't be able any more to record change into transport orders
Regards
356483 - Customizing: Current settings in the test system
77430 - Customizing: Current settings

Hi Andres
I do not really now the exact impact, it might prevent some business data from being mass processed or overwritten...
I did had to deactivate the transport connection on specific objects/activities for some customers.
It depends on the frequency of that activity. I don't like to open the client to modification as you can sometime forget to close it back, and sometime also it gave the opportunity to other consultants to make changes that would create inconsistency among envt in the whole landscape.
At least activating the recording of changes could help in tracking the source of modifications
RZ10 => rec/client=ALL
STMS => RECCLIENT=ALL
Regards

Client Definition Question

I asked this question in another forum here, got some helpful feedback and a recommendation to post the question here as it might be more fitting for some in this group.
In getting ready to teach a class, I've been putting together my set of SAP terms and getting ready to explain them to the class. I've been cross referencing the SAP Glossary and other sources to try to give as correct a definition as possible. In looking at these, one element I've been wondering about is the SAP definition of a client within SAP ERP.
The SAP glossary defines client as "In commercial, organizational, and technical terms, a self-contained unit in an SAP system with separate master records and its own set of tables." I find the last phrase in that definition (which I've italicized) to be puzzling. In an instance where multiple clients are sharing the same underlying database, each client does not have its own set of tables. To my knowledge that's not a required element of a client. (That's why the mandt field is so common in tables.)
So...why is that phrase a part of the definition and what is SAP intending it to mean? Is a distinction being drawn here between logical segregation of content (vs. actual segregation)? Or is there something here that I'm just not understanding?
As an example of what I'm talking about, if we have one instance of SAP ERP that has multiple activie clients, and If we were to take table T001 which contains company code information mapped to a particular client, wouldn't all the clients in that instance be sharing that same table?
I realize that logically if one uses transaction SE16 to view the table from within SAP ERP, only the information for the client one is working within is shown. My thinking had been that if one were to look at this table directly in the DBMS, the table would show all of the clients active within this instance. So in that sense each client is using the same set of tables with logical segregation of data based on the MANDT field. (i.e. if I had 3 clients running on one SAP instance tied to an Oracle backend, the backend would not have 3 totally independent databases for each client.)
Am I missing something here, or is the definition of client a bit misleading?

Hi Tony,
Pity that your question did not get a reply in more than two weeks.
I am happy to say that I have never come across the "its own set of tables" statement. Whoever wrote that is either ignorant or a victim of a very bad mistranslation. A client is a logical "subdivision" of the data stored in a SAP database. I'm not old enough to confirm this, but when I started at SAP I was told that the client concept came from the time when several companies shared a single database on some large central mainframe and obviously could not be allowed to see each other's business data. Today the use of a client is different, e.g. it provides for separation between customizing and sandbox clients in a development system, or between say test and training clients in a QA system.
Technically all clients share the same set of tables. A "client-dependent" table has the characteristic that its first field (and the leading field of its primary key) is always the client number. The "client-dependent" attribute is maintained in the SAP dictionary. When an ABAP program contains a statement like "SELECT * FROM TAB" and TAB is client-dependent, the DB interface in the kernel will automatically convert this to "SELECT * FROM TAB WHERE MANDT = "<client>". An SQL trace (ST05) of a simple business transaction will reveal this behaviour immediately.
Not all tables are client-dependent, some are cross-client, i.e. their data is visible to and shared by all clients in the system. As a rule, all master/transaction tables are client-dependent, while system tables containing instance-specific rather than business-specific data (e.g. the list of printers) are cross-client. Customizing tables are mostly client-dependent but some are cross-client (I'm a technical consultant so I can't really tell you why that is).
You are perfectly correct that if you look at a table at database level rather than through SE16, you would see records for all clients residing in the same table. Incidentally the same can be achieved in ABAP by adding the CLIENT SPECIFIED option to the SELECT statement but the code of business transactions must of course do no such thing.
Also, the client concept is not specific to Oracle so the advice to post the question on the SAP/Oracle forum seems a little misleading. SAP implements the client concept regardless of the underlying database.
Hope this clarifies things,
Mark

SCC4- Client Role ? in Client Setting

Hell Friends,
I need some information on Client's Role Setting in SAP system in SCC4.
Which role need to be assigned to each client based on the requirement/purpose in a SAP System ?
Here, i am giving brief information on the Clients created in our SAP System Landscape.
SAP ECC DEV System
          100 - Golden Master Client
          110 - Unit Testing Client
          120 - ABAP Development Client
          190 - Sand Box Client
SAP ECC QAS System
          200 - Integration Testing Client
          220 - Training Client
SAP ECC PRD System
          300 - Production Client
          310 - Pre- Production Client
Now, my question is which role is assigned to which Client in "Client Role" setting under SCC4, based on the Purpose of the respected client. ?
I am waiting for your valuable response.
Regards
Bhavik G. Shroff

Hi Presu,
Thank you very much for your valuable response. This inforamtion is useful for the Client Setting in SAP System.
But, I also want specific information for this setting in SCC4.
Client Role:
                   C Customizing
                   D Demo
                   E Traning/Education
                   P Production
                   S SAP Reference
                   T Test
Based on my client List, which Client Role need to be assigned to Which Client ,according to their Purpose ?
Regads
Bhavik G. Shroff
Edited by: Bhavik G. Shroff on Jul 11, 2009 12:44 PM

Role of copy profiles in client copy.

Hi All,
Can anybody give the idea regarding the role & importance of copy profiles in Cilent copy..
Regards
Srinivas K

Hi,
The client copy profile is the one which decides the kind of data that is going to get copied to the new client.
So choosing a profile depends on the kind of activity or the purpose for which the new client is been created. Ex :Training client ,testing etc.
For this we need to know the requirment clearly for what the requster is going to use the client accordingly choose the right profile to copy the client.
If we have good undersatnding of end users work then Basis persons can come up with a profile to be used in a client copy.
So classification of data plays important role in choosing a copy profile.Like Application data,Customizing data,User master data etc.
And also client depedent or independent data...
And for more details you can go through the above link provided by Deepu.
As far I know we can not copy the application data alone as it dependents on the customizing .
So we need to copy both of them together if we need application data.
Secondly we have be more careful if we are opting for a cross client customizing as this is going to impact not only the target client but also other clients in the system.

Add development abap client

Hello,
We have development client and also abap development client are different one.
We have already development, qa, production, training clients defined in solman landscape.
How to add abap development client in solman.
Thanks.
Anirudh,

Anirudh,
you can create a new system role in SMSY and display it in your projects system landscape.
Just select a logical component, click on the system soles button, add a new one, and give it a system type (i.e. Source Systems). Then assign the system:client to the new role. Sometimes this is done if you have two QA boxes as well.
regards,
Jason

Client in sap

hi ,
1. what is client in sap.
i. explain the client no: which we see on the initial screen of logon page.

Hi Baleeq,
SAP Clients are part of the defining technical structure of the SAP System. Each client contains its own master records and set of tables.
When you log on to an SAP System, you log on to a particular client of this system. Any activities you carry out in the system are always carried out in one client. When you plan your SAP system landscape, you must consider which clients you need for which activities.
By assigning activities to be performed in a client, you give each client a particular role. This section describes the most important client roles.
Since you need to adapt the SAP software for your own business needs, each SAP system landscape requires a client where Customizing settings, and possibly ABAP Workbench developments, can be made. This client is known as the Customizing and development client, or Customizing client for short. The abbreviation CUST is used for this client.
Before you can use the Customizing settings and Workbench developments productively, you need to test them extensively for errors. Any faulty settings can seriously disrupt productive operations, and at worst, lead to the loss of productive data. The integrated nature of the various SAP applications means that there are many dependencies between the different Customizing settings. Even an experienced Customizing developer may not discover these dependencies immediately. The correctness of the settings can only be guaranteed with extensive testing. The client where these tests are made is the Quality Assurance Client, QTST for short.
A separate client is required for productive use of the SAP System. So that this client can be used without disruption, it is essential that no Customizing settings or Workbench developments are made here, and also that no tests are carried out. This client is known as the Production Client, PROD for short.
These three clients, CUST, QTST and PROD, are the central clients that exist in every system landscape. Standard system landscapes have precisely one client for each of these client roles.
SAP recommends that you make all your Customizing settings in a single Customizing client, and then use the CTS to transport them to the other clients.
SAP also recommends that you do not make any Customizing settings or Workbench developments in the quality assurance or production clients. You can make sure of this by making appropriate client settings.
In addition to the central clients, you can also set up other clients for other tasks. However, you must remember that each extra client takes up additional system resources (main memory and database space). They also need to be administrated. For example, you need to set up and administrate access authorization for the users, and also distribute any changes to other clients with the CTS. You must weigh up the advantages and disadvantages of setting up other clients.
Examples of other client roles are:
Development test client (TEST): Developers can use this client to test their Customizing settings and Workbench developments, before they release their change requests. In this client the developers can create test application data for realistic tests. If they discover errors, they can remove them in the Customizing client. A development test client is always set up in the same SAP System as the Customizing client. This means that any changes that are made to cross-client data in the Customizing client are also immediately visible in the development test client. Changes to client-specific data are copied from the Customizing client to the development test client using a special client copy function. The client copy function uses the unreleased change requests from the Customizing client to do this. The development test client is set so that you cannot make changes to Customizing data and Repository objects.
Prototype or sandbox client (SAND): You can use this client to test any client-specific Customizing settings if you are not sure whether you want to use them in this form. Any settings that you want to keep are then entered in the Customizing client. To prevent conflicts between the prototype client settings and real settings in the Customizing client, you cannot make changes to cross-client Customizing data and Repository objects in the prototype client. The CTS does not record changes made to client-specific Customizing data, and does not transport them from the prototype client. You can make sure of this by making appropriate client settings.
Training client (TRNG): To prepare end users for new functions that are to be transported into the production client, you can set up a training client. The users can use the new functions in this client with specially created application data. This client is set so that you cannot make changes to Customizing data and Repository objects.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Training Client

Similar Messages

Maybe you are looking for