Catalog
In this subsection, you set up the terminology catalogs.
Catalogs provide a means of making sure you use the terminology
consistently. The QM component uses a two-level hierarchy consisting of
code groups and
codes for its catalogs. The terminology is encoded mnemonically
at the client level. The codes are made up of four characters, which in turn
are assigned to eight-character code groups. These codes can also be assigned
to eight-character
selected
sets at plant level.
To organize the catalogs, you must define:
- The use and description of each catalog
- Mnemonic keys for codes, code groups and selected sets
- Guidelines for creating short texts
- Guidelines for using and creating other catalog contents
Standard settings
In the standard system, catalogs 1 through 9 and A through E are defined for use. Use catalog types P through Z to define your own supplementary catalogs.
Activities
1. Organize
special catalogs
Special catalogs 1,
2, 3 and 9 have functions that differ from the remaining
catalogs.
a) Catalog
1:
You need this
special catalog to record inspection results; in it you define the value range
for qualitative inspection characteristics.
Refer to the
section
Inspection characteristics , to determine whether this
characteristic type is used in your organization. Organize catalog 1 according to its intended use for the inspection characteristics.
characteristic type is used in your organization. Organize catalog 1 according to its intended use for the inspection characteristics.
You can only access
characteristic attributes using selected sets. You must therefore create
selected sets at the plant level, in which you group the codes together under
general categories.
In the selected
sets, you must specify a
defect class for the characteristic attributes that represent a
rejection.
Determine what
additional information, if any, should be stored for the characteristic
attribute in the selected set. You can enter texts for tasks and effects on an
additional data screen.
b) Catalog 2:
Tasks
You need this
special catalog for the quality notifications. You can define automatic 
follow-up actions for tasks.
follow-up actions for tasks.c) Catalog 3:
Usage decisions
You need this
special catalog for
inspection lot completion. You can only access the usage
decisions using selected sets. You must maintain the following additional
control fields for each code contained in a selected set:
inspection lot completion. You can only access the usage
decisions using selected sets. You must maintain the following additional
control fields for each code contained in a selected set:- Valuation of the inspection lot
d) Catalog 9:
Defect types
You use this special
catalog to record defects in quality notifications. In this catalog, you must
define a defect class for each code contained in a code group.
2. Organize
general catalogs
When you record
characteristic results, you can also record the entries from several catalogs
or selected sets in addition to the characteristic values, provided they have
been stored in the inspection characteristic.
Determine which
catalogs will be useful for this purpose and which catalogs will require
selected sets at the plant level. Define the
catalog types in the subordinate menu item with the same
name.
Furthermore, you can
use certain catalogs to record data for the quality notifications and defect
records. Refer to the chapter Quality Notification,
Master Data for additional information.
Master Data for additional information.3. Maintain
catalog master records
Maintain the master
records for the catalogs you previously defined, in the following
sequence:
a) Code group,
code (at client level)
b) Selected set
(at plant level)
Once you have maintained the catalogs, set the status of the code groups and selected sets to 'Released'.
When the codes, code groups and selected sets are first used, the system gives them a usage indicator that prevents these objects from being deleted (either by mistake, or intentionally!). Since the usage indicators cannot be reset once they have been created, and codes cannot be deleted once they have been used, you should exercise caution when releasing catalogs, code groups and selected sets in a productive system.
Once you have maintained the catalogs, set the status of the code groups and selected sets to 'Released'.
When the codes, code groups and selected sets are first used, the system gives them a usage indicator that prevents these objects from being deleted (either by mistake, or intentionally!). Since the usage indicators cannot be reset once they have been created, and codes cannot be deleted once they have been used, you should exercise caution when releasing catalogs, code groups and selected sets in a productive system.
Additional Information
You can maintain the catalog master records in the languages in which the catalog types have been documented.
- To find codes in extensive catalogs quickly, you must use mnemonic keys for code groups, codes and selected sets. Define the structure of these keys carefully!
- When you search for a code, code group or a
selected set generically using the entry * and using the F-4 Help function,
the system displays the catalogs that fulfill the selection criteria in a
hierarchical list on a screen.
You can search generically with the special characters '+' and '*'
Example
If you enter +A* in the code field, the system searches for
codes whose keys have the letter A as their second letter.
- When you display created catalog entries in
transaction data (such as, inspection results and quality notifications), the
description for the code is displayed, but not for the code group. If you use
the special character & in the code group text, the
system displays a combination of both code and code group texts for the code.
The code text is displayed in place of the special character with the code
group text.
Example
Code group
description: Defect & assembly
Code description: Transistor
Display: Defect transistor assembly
Code description: Transistor
Display: Defect transistor assembly