Configuring Quality Management in Discrete Manufacturing (1E1)

You use this configuration item to define inspection point field combinations to record results for inspection points. An inspection point is an identifiable record of inspection results that is assigned to an inspection operation. Hence, inspection points allow you to execute several inspections and to record multiple sets of characteristic results for an operation, for example, during production or at goods receipt.

For several inspections during production, you can define that an inspection should take place every five minutes or for every container. To achieve this, you configure a freely-defined inspection point.

1. Define an inspection point field combination by entering an identifier (three characters long) and a short text. The identifier must start with 9 or with a letter (A to Z).
2. For an identifier, configure different inspection point fields with individual keywords and an individual sequence. There are two text and number fields of variable length that you can freely define. In addition, the inspection point data record can contain a date and time field.

You assign the defined identifier for the inspection point field combination to the inspection plan header.

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.

1. 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).
   Note

   You are only allowed to use each inspection type for one inspection lot origin.
2. Define the contents of the controlling fields for each inspection type. For more information, see the field help.

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.

1. Determine which control parameters are relevant for the individual inspection types and which of these parameters can be predefined uniformly for each inspection type.
2. Define the default values for each inspection type.

   Store only those default values that you will always use when you maintain the material master.

3. Maintain the table of default values.
4. 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 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 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 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 skipped
    Note

    For skip lots, an automatic usage decision is made for consistency reasons.

You use this configuration item to assign orders to order types. You have to assign every order to an order type. The order category (40, process order) is a fixed setting and cannot be changed. The order categories are predefined in the SAP system and characterize the technical properties of the orders. The order category defines, for example, the transactions you can use to process an order.

The order type defines the following:

• Order residence time

  You define how long completed orders remain in the SAP system before they are archived.

• Status management

  An order can run through several statuses*. The status controls which business-related operations* are permitted with an order.

• Number assignment

  ou have to assign a number range to each order type. If you create a new order type by copying an existing one, you can either keep the number range assignment or choose a different one.

Note

In addition to the general order parameters at client level, there are also parameters at plant level, which you can process in the configuration step under Shop Floor Control → Master Data for Process Manufacturing → Define Order-Type-Dependent Parameters.

Order types are preset in the standard delivery of the SAP system.

1. Classify the orders with regard to their defining characteristics (for example, order category or number range).

2. For each order category, define whether you want to use status management.

3. If necessary, define your own order types. To do so, copy an existing order type and adjust the data as necessary.

You use this configuration item to define the parameters that are valid for each order type and plant.

The parameters are split up as follows:

Here, you define the data that influences master data selection or order master data maintenance. The screen contains the following indicators:

• The production version defines if the production version is selected automatically or manually.
• The recipe selection ID defines the priorities according to which the recipe is selected.
• You can activate the entry tool for operations to help you when you create operations.

• General
  • Substitute MRP controller/substitute production supervisor. These are proposed when you create process orders if an MRP controller or production supervisor are not specified in the material master, or if there is no reference to material.
  • Reservation/Purch.Req. specifies whether certain order objects (operations, components) are relevant to MRP.
  • Collective requisition enables collective purchase requisition per order for externally processed operations or non-stock items.
• Bill of Material
  • Application defines how the BOM alternatives are selected.
  • Batch Determination
  • Search procedure defines how batch determination is to take place.
• Quality Inspection

  Inspection type defines how a quality inspection is to be carried out.

• Status Change Documents
  • Here, you define whether you want change documents to be written if a status change occurs. You also define the level at which the change documents are written:
  • A status change document documents the following:
    • Which status has been changed
    • Who changed the status
    • Whether the status has been activated or deactivated
    • In which transaction the status change has been carried out
  • In the process order*, you can define the status at the following levels:
    • Order header
    • Operation
    • Material component
• Status change documents can thus be defined independently of each other, at each of these four levels.
  Note

  If you have defined these parameters such that status change documents are written for a particular order level, the SAP System only writes a status change document for a status change from this point in time if the order (or operation/component) has been created since the status change documents have been activated.
• Documentation of Goods Movements

  You can specify that goods movements are to be documented with reference to an order.

• Cost Accounting

  Here, you define the parameters relevant for cost accounting, such as costing variants for planned and actual costs and a results analysis key.

• Distribution Role

  Default (distribution) role defines an automatically generated distribution role for CO settlement.

You use this configuration item to create production scheduling profiles for specific plants.

In a production scheduling profile, you can:

• Specify that certain business transactions or processes are to be carried out in parallel in a production or process order:
  • Order release at the time the order is created
  • Generation of document link from the material master when the order is created
  • Generation of document link from a BOM when the order is created
  • Scheduling upon order release
  • Generation of document link from the material master upon order release
  • Generation of document link from a BOM upon order release
• Specify whether only partial quantities are to be confirmed at the time of an availability check
• Specify that an automatic goods receipt is to take place
• Specify that in the case of the confirmation:
  • No short quantities are to be updated
  • No excess quantities are to be updated
  • Neither short nor excess quantities are to be updated
  • An adjustment of the operation and component quantities to the actual values is to take place
• Make various specifications in the area of batch management:
  • Automatic batch creation when an order is opened
  • Branching to batch classification when a batch is changed
  • Extended batch classification via Customer Function Call
  • Generation of a batch split record in the production order for each batch that is found
• Specify settings regarding transport:
  • Specify that only transport requirements are to be created if transport requirements can be generated for all the components of the operation
  • Specify that either the committed quantities or the required quantities are to be taken into account when transport requirements are generated
  • Specify that the creation of transport requirements is to take place automatically
• Specify which order type is to be suggested depending on the business process
• You can assign a production scheduling profile to a:
  • Material (Work Scheduling screen in material master)
  • Production supervisor

Note

• The assignment to a material takes higher priority.
• The production scheduling profile is adopted in the production or process order at the time the order is opened.

1. Create the necessary production scheduling profiles.
2. Assign the profiles to the appropriate materials or production supervisors.

You use this configuration item to define the production supervisors for your plants. In addition, you can assign a control profile to each production supervisor. By assigning production supervisors to materials within the application, you can define responsibilities for a material within production activity control.

1. Create your production supervisors.
2. If necessary, assign profiles to your production supervisors.

In this configuration item, you can define task list usages to assign routing to various work areas. You can create several task lists with various usages for the production of a material. In work orders, you can assign order types* to usages. The system uses the usage in an order for automatic task list selection.

You can specify that a routing is to be used only for Plant Maintenance or for goods receipt.

Define task list usages.

You use this configuration item to define a collection of default values for task list headers and operations.

You can minimize the maintenance of task list data as follows:

• Data from the material master is proposed
• Data from the work center can be referenced or copied
• Data from the profile is proposed

You can enter a profile in routing maintenance. The values from this profile are proposed when you create a new routing or routing object, such as a header or an operation. This data can either be saved or overwritten.

The profile contains default values for the status or for the operation increment.

Note

The values you maintained in the material master or the work center will be proposed before any values from the profile.

1. Determine the default values that can reduce the amount of maintenance work in your company.
2. If necessary, define several profiles.
3. Maintain the default values for routing maintenance.