Tell us what you think

We want to create the best possible experience for our learners. Your feedback helps us to improve the experience for everyone.

SAP Learning Journey

Understanding Process Steps and Business Roles for Nonconformance Management (2QN)

Objectives

After completing this lesson, you will be able to:

Define process steps for nonconformance management (2QN)
Identify business roles for nonconformance management (2QN)

Process Steps for Nonconformance Management (2QN)

Applicable Process Steps

Process Steps	Description
Record Defect	In this step, you can continue processing of a defect in a quality notification (notification type Q3 – Internal Problem Notification) in order to enable a more comprehensive processing of the defect. You can also define immediate, corrective, and preventive actions and assign one or more root causes to the defect in the quality notification.It is currently only possible to continue the defect in a quality notification if no tasks have been assigned to the defect yet.
Process Defect	There are two options for processing and completing a defect: via notifications (N) or via eight disciplines of problem solving (8D) In the Process Defect via Quality Notification (N) step, the quality engineer further processes the defect. He can add additional information to the defect or complete missing fields. Furthermore, he assigns a quality task to the defect and enters a responsible task processor. The eight disciplines (8D) model is a problem solving approach. Its purpose is to identify, correct, and eliminate recurring problems. In this step, the quality engineer is guided through the 8 process steps of the 8D model.
Processor Receives the Notification (N)	This process step shows you how to receive a notification of a task assigned to you in the My Inbox – All Items (F0862) app.
Execute Quality Task and Document Outcome (N)	In this step, the task processor opens the task and documents the task’s outcome in the processor notes.
Process Defect via Eight Disciplines of Problem Solving (8D)	The eight disciplines (8D) model is a problem solving approach. Its purpose is to identify, correct, and eliminate recurring problems. In this step, the quality engineer is guided through the 8 process steps of the 8D model.
Complete Defect Processing	In this step, the quality engineer reviews the outcome of the quality task and completes the defect.
Record Defect Using CoPilot (Optional)	In this step, you can record the defect using the SAP CoPilot digital assistant.
Assign Defect to Quality Notification (Optional)	In this step, you can continue processing of a defect in a quality notification (notification type Q3 - Internal Problem Notification) in order to enable a more comprehensive processing of the defect.It is currently only possible to continue the defect in a quality notification if no tasks have been assigned to the defect yet.
Analyze Defects (Optional)	In this step, the quality engineer can analyze defects that have been captured in the system.
Overview Page for Quality Engineer (Optional)	The Quality Engineer Overview shows the most important information and tasks related to inspection management that are relevant for you on a single page. The information displays on set of cards.
Create Inspection Lot	This process describes the handling of inspection lots that were created manually. If required, the quality technician creates additional, manual inspection lots for the available inspection origins in order to perform additional quality inspections. After inspection results have been captured, the quality engineer makes a usage decision to close the manual inspection process. In this step, the quality technician manually creates an inspection lot. An inspection plan is assigned and the sample size is calculated automatically.
Record Inspection Results	The quality engineer records inspection results.
Make Usage Decision	The inspection is done and the inspection result is recorded. You must decide whether or not to accept the assembly depending on the inspection result. If you do not want to use the Quality Engineer Overview, you can open the Manage Usage Decisions (F2345) app directly.

Identify Business Roles for Nonconformance Management (2QN)

Click on the available pictogram to display according information and the relevant piece of the hierarchy.

Access to business applications is controlled by role-based authorization management. You assign Business Roles to Business Users, and the roles provide access to business tasks. Business Users are defined as employees, contractors, or other individuals that need access to the SAP S/4HANA Cloud, public edition system.

How to find Business Roles for a scope item

Navigate to https://rapid.sap.com/bp/#/BP_CLD_ENTPR.
Select your country localization from the Version drop-down list.
In the Solution Scope section, expand the relevant scope item group.
Select a scope item.
Download the test script.
Navigate to the Roles section of the test script.

A Business Role is assigned to a Business User to grant permission to access applications in SAP S/4HANA Cloud, public edition.

One or more Business Catalogs have been assigned to a Business Role. Business Catalogs include access to one or more applications, dashboards, or displays of data.

Administrators can control visibility to the data granted through the catalog by applying General Restrictions to Business Catalogs. By maintaining access restrictions, you can define the subset of all existing business objects a user can view (read) or edit (write) when working with a particular business role.

The Business Catalog defines which access categories are available (Value Help, Read, Write), and for which fields restriction values can be maintained. The fields vary per catalog, as they are based on the fields within the apps in the catalog. The Business Role aggregates restrictions for all Business Catalogs.

Administrators define a restriction based on a supported field (for example, company code, country, controlling area, and so on). Supported restriction fields vary per Business Catalog, as they are based on the fields within the apps in the catalog. You can restrict data access for the Value Help, Read, and Write separately. Read access always includes Value Help access, and Write access always includes Read access.

How to identify the Business Catalog(s) mapped to a Business Role and the Fiori application(s) mapped to a Business Catalog:

Log into the SAP S/4HANA Cloud, public edition system.
Select the Manage Business Roles application from the Launchpad.
Select a Business Role.
Select the Assigned Business Catalogs tab to view the standard Business Catalogs assigned to the standard Business Role.
Select a Business Catalog.
Select the Catalog Description tab to view the Functional Description, Authorization Criteria, and Associated Catalogs information.
Select the Applications tab to view the Fiori apps mapped to the Business Catalog.

Note

Please do not edit SAP Standard Business Roles directly. To customize Business Roles, always make a copy of the SAP Standard Business Role or use the option Create From Template in the Maintain Business Roles application.

To apply General Restrictions, an Administrator should first make a copy of the SAP Standard Business Role, or create a new role based on the SAP Standard Business Role Template. For example, if you need to restrict access in the Accounts Payable Accountant Business Role for some users to only Company Code 1710 (United States), and for some users to only Company Code 1010 (Germany), you will create two new Business Roles based on the SAP Standard Accounts Payable Accountant role. You should name the roles accordingly (for example, Accounts Payable Accountant_1710). In the first business role, you will edit the role and maintain the restriction value(s) for the entire Business Role (that is, define the Company Code field = 1710). Then, you may edit the individual business catalogs within the role and define the access category (that is, Value Help, Read, Write) as Restricted. When you create a new Business Role, the Read access is set to Unrestricted and Write access is set to No Access by default. When an access category is Restricted, you must select a specific field value (for example, Company Code = 1710) or grant unrestricted access. If you leave fields empty within a business catalog, a user will be assigned No Access to the field in the business catalog's granted apps.

Next lesson