Show TOC

Process documentationSetting Up Nonconformance Locate this document in the navigation structure

 

You can use this process to set up the Nonconformance feature.

Process

  1. In System Rule Maintenance, you change any NC-related rule as required for your shop floor. For more information, see Setting Up Visual Test and Repair.

    The following system rules define the overall guidelines by which the system operates:

    • Bypass Previous NC Routings on Return

    • Generate and Lookup Vertical Ref Numbers

    • Generate Horizontal Ref Numbers

    • Maximum Loop Count

    • NC Allows Non-BOM Component and Ref Des

    • NC Allows Undefined Component

    • NC Closure Required Default

    • NC Unassembled BOM Components

    • Use NC Groups for Production Clients

    For more information, see Nonconformance Rules.

  2. In Routing Maintenance, you proceed as follows:

    1. Create repair loops.

    2. Create disposition routings or set up function-based dispositioning.

      • You must define necessary routings for all needed nonconformance scenarios prior to using the NC functionality. Proper NC routing, disposition routing and any other special routings should be created and applied to the NC client, disposition group or operation (see Routing Maintenance).

      • In Disposition Group Maintenance, you define disposition groups and their functions.

        For example, you can define LOCAL_REWORK as a disposition group that identifies the processes and steps needed to support reworking a product defect at the location where the defect was discovered. Some disposition groups are included by default and may be used as a starting point to create similar disposition groups.

        For more information, see Nonconformance Disposition.

    3. Write scripts to automatically send nonconformed SFC numbers to a next step based on criteria (see Routing Scripts with Nonconformance Codes).

  3. In NC Client Maintenance, you do the following:

    • Define how NC Selection and Log NC (NC Data Entry) will be displayed

    • Define the behaviors and interactions for such integrated NC plug-ins, as NC Data Tree and NC charts, and for the Work Instruction plug-in

    • Define whether primary and secondary NC codes can be logged and specify the component routing.

    Several NC clients have been configured and applied to other PODs by default. These NC clients have been created to support standard Log NC business process scenarios for several manufacturing scenarios, including simple and complex manufacturing and assembly. These default NC clients can be used as is or as a starting point for creating new NC clients for similar Log NC needs. For more information, see NC Clients.

    Recommendation Recommendation

    We recommend that you use one of the existing clients to become familiar with the functions allowed.

    End of the recommendation.
  4. In Data Field Definition Maintenance, you define fields for NC category that you want to appear in the POD. In Data Field Assignment Maintenance, you group these data fields and associate them with a data type of NC category.

    • In Data Field Definition Maintenance, you define the fields to be used for Log NC Data Entry. For this, you can use the pre-loaded REF_DES, COMMENTS, COMMENTS_REQ, FAILURE_ID, INVENTORY_ID, COMPONENT fields or define other fields. The data fields that are specified in the system settings property Log NC must already be defined in Data Field Definition Maintenance.

      The REF_DES and COMPONENT data fields are among the fields that are predefined. If a new data field is needed, fill in at least the Data Field and Type fields on the Main tab page.

    • For the data fields to be utilized in Log NC, they must be assigned to an NC data type in Data Field Assignment Maintenance. If a new data type is needed, fill in at least the Category and Type data type fields on the Main tab page. Use the Insert <xxx> action links to add the needed data fields to the data type and save the data type.

    For more information, see Data Field Definition and Assignment.

  5. In Default Value Maintenance, you define the parameters and default values of NC codes for the NC Code (NC_CODE) table as follows:

    Column Title

    Default Value

    ASSIGN NC TO COMPONENT

    S

    CAN BE PRIMARY CODE

    true

    CLOSURE REQUIRED

    true

    COLLECT REQUIRED NC DATA ON NC

    O

    MAXIMUM NC LIMIT (SFC)

    0

    NC CATEGORY

    FAILURE

    NC DATA TYPE

    SIMPLE

    NC PRIORITY

    500

    STATUS

    301

    For more information, see NC Code and Child Tables.

  6. In NC Code Maintenance and NC Group Maintenance, you do the following:

    1. Group and create NC codes.

    2. Categorize each NC code as a Failure, Defect, or Repair (see NC Code).

    3. Assign NC data types to NC codes, if required.

      You assign NC data types, which contain fields mapped to Log NC Data Entry elements, to NC codes.

      Each NC code must have an associated data type. The data type identifies the data entry fields to be displayed in the NC Data Entry plug-in for the NC code.

      To specify the data type for an NC code, retrieve the NC code and enter the desired data type using the browse for the field on the Main tab page.

    4. Create primary and secondary NC codes according to the NC hierarchy you want to use on your floor (see Creating NC Code Hierarchy).

    5. Assign DPMO categories to NC codes, if required (see Setting Up DPMO).

    6. Set up activity hooks for NC codes (see Setting Up Activity Hooks).

    For more information, see NC Code Maintenance and NC Group Maintenance.

  7. You set up the POD for nonconformance (see Setting Up PODs for Nonconformance). If required, you set up the Fast Barcode Interface and how operators can close NC codes (see Configuring Fast Barcode Interface).

    A POD with at least the following plug-ins is needed in order to use Log NC:

    • NC Selection

    • NC Data Entry

    Optionally, you can also set up Model Viewer (see Setting Up Visual Test and Repair) and NC Tree. Note that you need to set up NC Tree to log defects and repairs.

    A default LOG_NC client is predefined in SAP ME. It is assigned to the Default Operation POD (OPERATION_DEF) which uses the 3 panel horizontal layout. If you need to set up a new Log NC client, you can configure it in NC Client Maintenance (see NC Client Maintenance).

  8. You set up Standalone NC Logging, if required (see Standalone NC Logging).

  9. You set up DPMO, if required (see DPMO).

  10. You create work instructions and attach them where necessary if work instructions are to be used with the NC client (see Setting Up Work Instructions).