Show TOC
Setting Up
Clients
In this section, 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 R/3 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 with these
transactions!
- Entries that already exist in the target
client are not overwritten.
- 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' transaction SE01). To copy this data into subsequent
target systems or target clients, you only need to transport the request with
its copied data entries.
- The system only executes these transactions,
if you have authorization in the client to create transport requests, and if
the transport system is set correctly in this client.
There are the following transactions for
copying basic settings:
- QCCC All standard settings
- 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.
- 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:
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 note number 52390 in the note
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 note 61049 in note database
We recommend that you maintain master data in the target system, instead of
transporing it.
- Transporting SAPscript objects
See note 3355 in note database