SAP ABAP IMG Activity SIMG_CFMENUOLIAQS41 (Define Code Groups for Catalog Types)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM-CIC (Application Component) Interaction Center WinClient
     ⤷ INSC (Package) Application Development R/3 Plant Maintenance Customizing
IMG Activity
ID SIMG_CFMENUOLIAQS41 Define Code Groups for Catalog Types  
Transaction Code S_ALR_87000929   IMG Activity: SIMG_CFMENUOLIAQS41 
Created on 19981222    
Customizing Attributes SIMG_CFMENUOLIAQS41   Define Code Groups for Catalog Types 
Customizing Activity SIMG_CFMENUOLIAQS41   Define Code Groups for Catalog Types 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUOLIAQS41    

In this step you can maintain catalogs in the languages allowed.

SAP Recommendation

When creating the code groups, you should consider that generic specifications for code groups are possible to define the individual catalog profiles. We therefore recommend using common identification codes for similar code groups or for code groups that might possibly be displayed together in the selection.

The standard catalog types are:

  • Catalog 2 - Task catalog
  • Catalog 5 - Defect cause catalog
  • Catalog A - Activities
  • Catalog B - Object parts
  • Catalog C - Damage screens

Note

When maintaining the code groups, bear in mind the following possible entries for the catalog type:

  • Code group '*' All code groups for the catalog type can be selected
  • Code group 'xx*' All code groups for this generic entry
  • Code group 'xxx' Only catalog type 'xxx' can be selected
  • Code group ' ' If no code group is maintained, then the catalog type, for example, cause of damage, will be suppressed in the notifications.

Special note on the display of the code group texts.

When maintaining the individual code groups, you can provide each code group with a text.

In the next step, you will enter what are called group codes for each code group. The code represents a specification within a code group.

Example

You define a code group 'Color'.

You then create the individual colors red, blue, and so on, as group codes.

If you want to see the text 'red' supplemented by the name of the code group in the display on the screen, you must enter an '&' after the word 'color' when maintaining the code group description.

The text 'color red' is then displayed on the screen when the color 'red' has been selected.

If the character '&' has not been entered, the text 'red' will be displayed on its own.

The position of character '&' determines the length of the code group description when it is transferred to the group code display.

Note

Please note that the output length of the composite text is restricted. As a result, there is the danger that the entire length of the composite text may exceed the output length in the mask and that information may therefore be lost.

Transport of catalogs and long texts for catalogs

A transport can be compiled manually and then transported. The following steps must be performed:

  1. Creation of a transport order using SE09. Use Goto -> Object list to switch to the object list and to change mode, then use Edit -> New entries.
  2. The following entries must be made for each catalog type. The warning of table class A can be ignored. For each entry, use F2 to go to the key fields and enter the specified key using Edit -> New entries:
    1. R3TR TABU QPGR (F2) -> key xxxy* (xxx=client, y=catalog type)
    2. R3TR TABU QPGT (F2) -> key xxxy*
    3. R3TR TABU QPCD (F2) -> key xxxy*
    4. R3TR TABU QPCT (F2) -> key xxxy*
  3. If long texts have been created for code groups or codes, and these should also be transported, the following tasks must be performed:
    1. The following entry must be made in the transport order:
      R3TR TEXT QKATALOG,xxxy*,*,*
    2. The program RSTXR3TR must run in EXPORT mode for this transport order.
  4. The transport will then be performed. In the target system/client, program RSTXR3TR in IMPORT mode will be started.
  5. In table TTXCP, the entries QKATALOG,QPGT and QKATALOG,QPCT must be made and program RCTXTCPY executed.

Note:

If you want to make the transport within an SAP system (between two clients), use the client copy function via the Customizing menu. The transport order number serves as the profile for the objects to be selected. With this function, the transport order must not be released or exported.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
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_CFMENUOLIAQS41 0 HLA0006647 Maintenance Notifications 
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 QS41 QS41 Maintain Code Group Index 
History
Last changed by/on SAP  19991022 
SAP Release Created in