SAP ABAP IMG Activity SIMG_OLQU-O (Setting Up Clients)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ QI (Package) QM IMG and area menu
IMG Activity
ID SIMG_OLQU-O Setting Up Clients  
Transaction Code S_ALR_87003779   IMG Activity: SIMG_OLQU-O 
Created on 19981222    
Customizing Attributes SIMG_OLQU-O   Setting up clients 
Customizing Activity SIMG_OLQU-O   Setting Up Clients 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_OLQU-O    

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:

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

Business Attributes
ASAP Roadmap ID 202   Establish Company Structure 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_OLQU-O 0 HLA0009540 Quality Management 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
IMGDUMMY D - Dummy object QCCC OLQU-O1 QM Transfer All Standard Settings 
IMGDUMMY D - Dummy object QCCP OLQU-O2 Transfer QM Standard Settings for Quality Planning 
IMGDUMMY D - Dummy object QCCY OLQU-O3 Transfer QM Tolerance Key 
IMGDUMMY D - Dummy object QCCS OLQU-O4 Transfer QM Sampling Schemes 
IMGDUMMY D - Dummy object QCCK OLQU-O5 Transfer QM Standard Examples for Catalogs 
IMGDUMMY D - Dummy object QCCW OLQU-O6 Transfer QM Standard Settings for Quality Inspection 
IMGDUMMY D - Dummy object QCCZ OLQU-O7 Transfer QM Standard Settings for Quality Certificate 
IMGDUMMY D - Dummy object QCCM Transfer QM Standard Settings for the Q-Notification 
IMGDUMMY D - Dummy object QCCU OLQU-O10 Transfer Standard QM Basic Settings & Environment Settings 
IMGDUMMY D - Dummy object QCCT OLQU-11 Transfer QM Standard Texts 
IMGDUMMY D - Dummy object QCCF OLQU-O12 Transfer QM Forms (? See Text!) 
IMGDUMMY D - Dummy object QCCN OLQU-O13 Transfer QM Number Ranges for QM Objects 
History
Last changed by/on SAP  19991209 
SAP Release Created in