|Application Area||Application Subarea||Configuration Item Name||Configuration Item ID||Configuration Step||Configuration Approach||Category||Global, Country Dependent, or Localized|
|Quality Management||Quality Inspection||Inspection Lot Creation||500288||Maintain Inspection Types||Use Configuration Step in Configure Your Solution||Optional||Global|
|Quality Management||Quality Inspection||Inspection Lot Creation||500288||Maintain Inspection Lot Origins and Assign Inspection Types||Use Configuration Step in Configure Your Solution||Optional||Global|
|Quality Management||Quality Inspection||Inspection Lot Creation||500288||Define Default Values for Inspection Type||Use Configuration Step in Configure Your Solution||Optional||Global|
|Quality Management||Quality Inspection||Inspection Lot Completion||500268||Edit Selected Sets for Usage Decisions||Use Configuration Step in Configure Your Solution||Optional||Country Dependent|
|Quality Management||Quality Inspection||Inspection Lot Completion||500268||Edit Code Groups and Codes for Usage Decisions||Use Configuration Step in Configure Your Solution||Optional||Global|
|Quality Management||Basic Settings||Settings at Plant Level||500275||Maintain Settings at Plant Level||Use Configuration Step in Configure Your Solution||Optional||Country Dependent|
You use this configuration item to define the inspection types and the controls associated with the inspection type. The inspection type determines how an inspection is to be carried out. You are not allowed to change delivered inspection types, but you can create new entries.
- Define the eight-character keys and the short texts for each inspection type that you want to use. The key needs to start with 9 or a letter (A to Z).NoteYou are only allowed to use each inspection type for one inspection lot origin.
- Define the contents of the controlling fields for each inspection type. Check the field help for more information.
You use this configuration item to make settings for inspection lot origins and assign inspection types. The inspection lot origins are predefined in the system. You cannot define your own inspection lot origins. You can assign the inspection types you have created in the step before to an existing inspection lot origin. In addition, you must define which inspection type variants should exist for each origin. An example of an inspection type variant is a model inspection with a separate inspection type and associated task list usage.
- Maintain the inspection type variants for each inspection lot origin. You are allowed to create variants starting with the letters A to O, T to W, Z, or with the numbers 1 to 4.
- A variant 01 is predefined in the system. It must exist for each inspection lot origin as it will be used by the system as default if no other inspection type is set as the preferred inspection type in the material master.
You use this configuration item to define default values to a material's inspection setup. The default values you define in this step are used for new materials having this inspection type assigned. The values are relevant for the inspection setup that is defined in the Quality Management view of the material master. If you want to define different ways of inspection lot processing for individual materials or material groups you can change these inspection type default values in the material master.
Before you can maintain the default values, you must assign the inspection type to an inspection lot origin. This is because the fields for which you can store default values for an inspection type are dependent on the inspection lot origin.
For inspection processing purposes, the system allows you to store your own combination of control parameters for each material. Such a wide range of different processes, however, is generally not required or desired. You should therefore combine the materials into groups and define a standard profile for the controls for each material group in the material master. If these parameters are the same for all material groups for each inspection type, you can include them in the default values for the inspection type.
- Determine which control parameters are relevant for the individual inspection types and which of these parameters can be predefined uniformly for each inspection type.
- Define the default values for each inspection type.
Store only those default values that you will always use when you maintain the material master.
- Maintain the table of default values.
- Although some controls cannot be predefined uniformly in the system by means of default values for an inspection type for all materials, they could still be defined uniformly for comprehensive material groups. For such material groups, define the profiles using organizational measures and make sure the inspection planners use these profiles.
You use this configuration item to define the selected sets for usage decisions. In a selected set, you bundle those code groups and codes that are required or allowed for a specific purpose at plant level.
During inspection lot completion, it is only possible to access the usage decisions using selected sets. For each code contained in a selected set you make the following settings:
- Assign a valuation code and a quality score
- Define a proposal for the inventory posting or, if you are using quality management together with warehouse management, define a follow-up action to trigger stock postings.
In addition, you specify one of the codes within the selected set as the default code. This default code is used in processes where a code has to be determined by the system instead of being provided by the user.
You are not allowed to change delivered selected sets, but you can create and edit your own entries.
You use this configuration item to define code groups and codes for making usage decisions in order to standardize the usage decision options quality engineers have when completing an inspection lot. You define the code groups and codes at client level. Technically, code groups and codes for making usage decisions belong to catalog type 3. The combination of the catalog type, the code group, and the code uniquely identifies a usage decision in a coded format. Code groups are made up of eight characters and are used to summarize codes at client level according to various criteria. The codes are made up of four characters, which you use to mnemonically encode a usage decision (for example, A for Accepted and R for Rejected). You define a short text and optionally also a long text for each code.
You are not allowed to change delivered code groups and codes, but you can create and edit your own entries.
You use this configuration item to make plant-specific settings relating to quality management, for example, settings that are relevant for a specific inspection type such as the default settings for usage decisions. You can change and supplement several central controlling functions at plant level. These controlling functions relate to the planning and implementation of quality inspections; for technical reasons they are collated in one table. The functions you want to use for quality inspections determine which settings are relevant for your requirements.
In the Details screen for a plant, you can make settings relating to results recording that are mainly relevant for the hierarchical results recording worklist. For example, you can make settings for decimal places or for partial samples. In addition, you can make settings relating to results recording for inspection points, for example, specifying defaults for the valuation of inspection points. These settings are also relevant for the SAP Fiori app for results recording for inspection points.
In the subfolder Inspection Type-Specific Settings for Plant, you can define default settings for usage decisions:
- Default selected set for usage decisions
- You define the selected set relevant for an inspection type in the plant. The system only allows usage decisions that are included in this selected set.
- You can enter different usage decision selected sets for the inspection lot header and for partial lots.
- Settings for automatic usage decision
From the selected set you have assigned to the inspection type you can choose a combination of code group and code that will be used for an automatic usage decision in the following cases:
- When results were recorded and the valuation of all characteristics is Accepted
- When an inspection lot is skippedNoteFor skip lots, an automatic usage decision is made for consistency reasons.