SPRO

[Former Member]

Hi

Pl tell me the use of following in SPRO

QM-> Basic settings ->Settings up clients -> QM Transfer all standard settings, transfer QM standard settings for quality planning, transfer QM tolerances keys,Transfer QM sampling schemes,etc.There are about 10 transfer fields.

from where are these settings trasferred and to some server or else to where ,pl tell me the usage of these fields. Is the transfer to all plants or to a single plant only. How does the change gets effected if we click these field.

Pranav

[Former Member · Accepted solution]

Hi Shyamal

Great guidance.

thank you very much. Very useful for a person like me needs lot of guidance.

in my query

"QM-> Basic settings ->Settings up clients -> QM Transfer all standard settings, transfer QM standard settings for quality planning, transfer QM tolerances keys,Transfer QM sampling schemes,etc.There are about 10 transfer fields".

the client is not appearing when clicking any of these fields. how to actually go step by step in this transfer. is this transfer of the standard settings necesary or already will be there. if we dont do this transfer will it be problem to run QM.

Also tell about MARA table , is this where we enter "Client " . I heard about 200 client,300 client , 900 client,etc. is this what refers client.

thanks

Pranav.

[Former Member · Accepted solution]

Hi Pranav,

Kindly refer this Help Document,,,

Setting Up Clients

In this IMG activity, you provide the clients in the test system with the standard settings available in the QM component. You can then use these basic settings to maintain the master data required for your business transactions and to test the functions in the QM component.

This function is particularly useful, if you:

Have other SAP application components active in a client and you want to implement the QM functions retrospectively.

Want to update or add to the system settings in the current client after changing a release.

Requirements

You have set up the client according to the general instructions.

Activities

If you did not set up the client as an exact copy of client 000, you can use the transactions listed below to copy the basic data and default settings for the QM component in client 000 of the standard system to other clients.

Caution:

No cancellations are possible for these transactions!

Entries that already exist in the target client are not overwritten.

The automatic import protection in the target client is adhered to.

If the automatic correction recording is active, the system draws up a transport request in the target client that contains all copied entries (you can process category 'Copy Transport' in transaction SE01).

The system only executes the transaction if you have the authorization to create transport requests in the current client and the transport system is set up correctly in this client.

To copy this data into subsequent target systems or target clients, you only need to transport the request with its copied data entries.

Caution It is important to note that existing data can be deleted and/or changed when you execute a transport into another system (not the same as transports that originate in client 000). Therefore, you should never transport this request into a production system.

The following transactions can be used copying basic settings:

QCCC All standard settings

With catalogs

With standard texts

Without number ranges

Without sampling systems

Without tolerance keys

Without forms

QCCP Standard settings for quality planning

QCCW Standard settings for quality inspections

QCCZ Standard settings for quality certificates

QCCM Standard settings for quality notifications With notification-related catalogs

QCCU Standard settings for the QM environment

QCCK Catalog entries; examples

QCCT (standard texts QM_*)

You must copy the standard texts used in the forms into the current client, since there is no automatic default to client 000 for these texts. There is, however, a default defined for the language in table T002C in the client.

QCCF (forms QM_*)

You do not need to copy forms into the current client, since the system automatically defaults to client 000, if the required form does not exist in the current client.

QCCS Sampling systems according to ISO 2859 and ISO 3951

QCCY Tolerance keys according to ISO 0286

QCCN (number ranges Q*)

The application programs can only be run, if the number ranges are available in the current client.

The number ranges in the standard system are set up in such a way that you can copy them for most applications, using transaction QCCN without having to change them. However, if you automatically copy number ranges from client 000 using transaction QCCN, this leads to inconsistencies, if number ranges already exist in the current client that overlap with those in the standard system. This is also why the copying of number ranges is not included in transaction QCCC. Therefore, you must first check whether non-standard number ranges have been set up in the current client and if this is the case, you must manually maintain the number ranges for:

Inspection characteristics and Inspection methods

Control charts

Inspection plans and reference operation sets

Inspection lots

Physical samples and physical-sample drawing

Condition records for certificate profile determination

Characteristic confirmation numbers

Quality notifications

You must pay particular attention both when grouping notification types and assigning these groups to the number ranges manually and when copying from the standard client. See text reference and SAP Note number 52390 in the notes database.

Technical note: to improve the response times, the standard system is set up so that it stores a certain number interval when numbers are allocated internally. The numbers contained in the buffer are lost when the application program is terminated. You can define the scope of the number range buffers using transaction SNRO.

Further notes

Update instead of Insert: If you want to overwrite the existing settings in the current client with the standard settings from client 000, (instead of supplementing them) you can use the method mentioned in the transactions above. These transactions process prepared command files with the help of transaction SM29. To carry out an update instead of an insert, use the transaction SCC1 (in place of SM29) or the report RSCLCCOP together with the command files stored in the transactions mentioned above. The system, however, does not record this process in a transport request, as in transaction SM29. You can display the copy's log with transaction SCC3 or report RSCCPROT.

Transport to Other Clients or Systems:

Customizing tables

All Customzing tables in the QM component have an automatic transport link.

Transporting master data of QM component

See SAP Note 61049 in notes database

We recommend that you maintain master data in the target system, instead of transporing it.

Transporting SAPscript objects

See SAP Note 3355 in notes database

So, advisably you should select the option "QM Transfer All Standard Settings" while transferring the setting inter client.

I heard about 200 client,300 client , 900 client,etc. is this what refers client.

Yes, your understanding is correct.

All these client scenario is designed to incorporate the new development / add-ons / amended-changed-updated configurations w/o interrupting the live server's function and it's data base.

E.g. if there is a roll out process need to put live for a new Plant. Then all the relevant configuration is set in the Golden Master Client (That used to be known as 100), then transported to the Development Client (As per your example let us assume it's 200, where the entire set up is self examined by the analyst / configuration team).

Once it's passes through, it is transported to the Quality Client (As per your example let us assume it's 300, where the End user or the live user's do testing the new set up).

Once it's passes through then finally the tested Ok development it transported to the Live Client / Server / System, (As per your example let us assume it's 900)

I hope it may have cleared your understanding more. What I would advice you is spent a time with your Basis guy to make your understanding Cristal Clear.

Regards,

Shyamal

Kindly refer this Help Document,,,

Setting Up Clients

In this IMG activity, you provide the clients in the test system with the standard settings available in the QM component. You can then use these basic settings to maintain the master data required for your business transactions and to test the functions in the QM component.

This function is particularly useful, if you:

Have other SAP application components active in a client and you want to implement the QM functions retrospectively.

Want to update or add to the system settings in the current client after changing a release.

Requirements

You have set up the client according to the general instructions.

Activities

If you did not set up the client as an exact copy of client 000, you can use the transactions listed below to copy the basic data and default settings for the QM component in client 000 of the standard system to other clients.

Caution:

No cancellations are possible for these transactions!

Entries that already exist in the target client are not overwritten.

The automatic import protection in the target client is adhered to.

If the automatic correction recording is active, the system draws up a transport request in the target client that contains all copied entries (you can process category 'Copy Transport' in transaction SE01).

The system only executes the transaction if you have the authorization to create transport requests in the current client and the transport system is set up correctly in this client.

To copy this data into subsequent target systems or target clients, you only need to transport the request with its copied data entries.

Caution It is important to note that existing data can be deleted and/or changed when you execute a transport into another system (not the same as transports that originate in client 000). Therefore, you should never transport this request into a production system.

The following transactions can be used copying basic settings:

QCCC All standard settings

With catalogs

With standard texts

Without number ranges

Without sampling systems

Without tolerance keys

Without forms

QCCP Standard settings for quality planning

QCCW Standard settings for quality inspections

QCCZ Standard settings for quality certificates

QCCM Standard settings for quality notifications With notification-related catalogs

QCCU Standard settings for the QM environment

QCCK Catalog entries; examples

QCCT (standard texts QM_*)

You must copy the standard texts used in the forms into the current client, since there is no automatic default to client 000 for these texts. There is, however, a default defined for the language in table T002C in the client.

QCCF (forms QM_*)

You do not need to copy forms into the current client, since the system automatically defaults to client 000, if the required form does not exist in the current client.

QCCS Sampling systems according to ISO 2859 and ISO 3951

QCCY Tolerance keys according to ISO 0286

QCCN (number ranges Q*)

The application programs can only be run, if the number ranges are available in the current client.

The number ranges in the standard system are set up in such a way that you can copy them for most applications, using transaction QCCN without having to change them. However, if you automatically copy number ranges from client 000 using transaction QCCN, this leads to inconsistencies, if number ranges already exist in the current client that overlap with those in the standard system. This is also why the copying of number ranges is not included in transaction QCCC. Therefore, you must first check whether non-standard number ranges have been set up in the current client and if this is the case, you must manually maintain the number ranges for:

Inspection characteristics and Inspection methods

Control charts

Inspection plans and reference operation sets

Inspection lots

Physical samples and physical-sample drawing

Condition records for certificate profile determination

Characteristic confirmation numbers

Quality notifications

You must pay particular attention both when grouping notification types and assigning these groups to the number ranges manually and when copying from the standard client. See text reference and SAP Note number 52390 in the notes database.

Technical note: to improve the response times, the standard system is set up so that it stores a certain number interval when numbers are allocated internally. The numbers contained in the buffer are lost when the application program is terminated. You can define the scope of the number range buffers using transaction SNRO.

Further notes

Update instead of Insert: If you want to overwrite the existing settings in the current client with the standard settings from client 000, (instead of supplementing them) you can use the method mentioned in the transactions above. These transactions process prepared command files with the help of transaction SM29. To carry out an update instead of an insert, use the transaction SCC1 (in place of SM29) or the report RSCLCCOP together with the command files stored in the transactions mentioned above. The system, however, does not record this process in a transport request, as in transaction SM29. You can display the copy's log with transaction SCC3 or report RSCCPROT.

Transport to Other Clients or Systems:

Customizing tables

All Customzing tables in the QM component have an automatic transport link.

Transporting master data of QM component

See SAP Note 61049 in notes database

We recommend that you maintain master data in the target system, instead of transporing it.

Transporting SAPscript objects

See SAP Note 3355 in notes database

So, advisably you should select the option "QM Transfer All Standard Settings" while transferring the setting inter client.

I heard about 200 client,300 client , 900 client,etc. is this what refers client.

Yes, your understanding is correct.

All these client scenario is designed to incorporate the new development / add-ons / amended-changed-updated configurations w/o interrupting the live server's function and it's data base.

E.g. if there is a roll out process need to put live for a new Plant. Then all the relevant configuration is set in the Golden Master Client (That used to be known as 100), then transported to the Development Client (As per your example let us assume it's 200, where the entire set up is self examined by the analyst / configuration team).

Once it's passes through, it is transported to the Quality Client (As per your example let us assume it's 300, where the End user or the live user's do testing the new set up).

Once it's passes through then finally the tested Ok development it transported to the Live Client / Server / System, (As per your example let us assume it's 900)

I hope it may have cleared your understanding more. What I would advice you is spent a time with your Basis guy to make your understanding Cristal Clear.

Regards,

Shyamal

Edited by: Shyamal Joshi on Aug 19, 2009 10:09 AM

I am not able to understand why this post is getting displayed such stufffffff. I think something may crashed to my Java here. Deeply regretted for the same.

[Former Member]

Hi Shyamal

Thanks for the great effort and guidance taken. Shall come back if in need of clarificatons.

thanks

Pranav

[Former Member]

Hi Sujit, thanks

By "Client" do you mean plant. The words "client" "server" confusing ,what is difference. So is client 000 the default client.

Can u tell steps by which these standard settings be transferred with one example. will you elaborate the steps with one transfer example like Transfer of Qm Tolerance keys,etc.

Why cant this standard settin done individually without clkicking these 10 fields.

Pranav

[Former Member]

Hi Pranav,

As per best of my understanding

A client is simply the first field of every data record in tables that are not overall system-related. It is a way to have different groupings of data within one database. Originally multiple companies ran SAP from one system and database in a time sharing fashion. The 'client' was the company they were doing business with. They added more companies and they became more clients in the system. The design created to separate one company's information from another a dded a 'client' or mandt field to each client-related data table. Behind the scenes any data access additionally specifies the client number that the user logged into.

Using the MARA table (general material data) as an example, the first data field is mandt followed by material number and other material fields. If you logged into client 300 and in an ABAP program did a database query like select * from mara SAP in the background is actually querying the database as select * from mara where mandt = 300.

Clients can be used for separating data for multiple companies or multiple divisions or just created for testing a process or data load. Clients can be created, copied and deleted.

And as per STD Defination by SAP the Client is Application Components (SAP)

In commercial, organizational, and technical terms, a self-contained unit in an SAP system with separate master records and its own set of tables.

Pls go through these links, I think it will help you to understand the enterprise structure in more detail.

[Link - 1|http://www.scribd.com/doc/6493244/SAP-R3-SD-Overview-Enterprise-Structure]

[SAP Enterprise Structure|http://www.sapstudymaterials.com/2007/12/mm-001-sap-enterprise-structure.html]

[These are the steps to copy client in SAP|http://www.sap-img.com/bc049.htm]

[Above all this document will surely help you to understand the SAP Enterprise structure in SAP|http://www.google.co.in/url?sa=t&source=web&ct=res&cd=3&url=http%3A%2F%2Firis.tennessee.edu%2FBlueprint%2FFinancial%2FEnterprise%2520Structure%2520%26%2520Master%2520Data.doc&ei=QDGKSpKoGJOMkAXH9Zgl&usg=AFQjCNGATCyFxGrLnq9SiqLz4Qq-1bp1dg&sig2=7Qgms73Z7YCwpBM9kg6Y_w]

Regards,

Shyamal

[Former Member]

Hi

QM-> Basic settings ->Settings up clients -> QM Transfer all standard settings, transfer QM standard settings for quality planning, transfer QM tolerances keys,Transfer QM sampling schemes,etc.There are about 10 transfer fields.

from where are these settings trasferred and to some server or else to where ,pl tell me the usage of these fields

This is trnsfer of master data (SAP defualt master data) from defualt client to client which you want.server remains same.

Also

If you did not set up the client as an exact copy of client 000, you can use the transactions listed below to copy the basic data and default settings for the QM component in client 000 of the standard system to other clients.

All 10 fields are nothing but the master data's

You must copy them to your client.

Regards

Sujit