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 Rework Processing – Work-in-Process (BJQ)

Objectives

After completing this lesson, you will be able to:

Define process steps for rework processing – work-in-process (BJQ)
Identify business roles for rework processing – work-in-process (BJQ)

Process Steps for Rework Processing – Work-in-Process (BJQ)

Applicable Process Steps

Process Step	Description
Confirm Rework Required for Defective Material	Some operations produce more defects due to operational or component defects. To simulate the process, some predefined operations are triggered automatically at the end of the planned required operation. These are also released automatically and are followed by production execution as normal production parts. In the following scope item, the assembly of the finished product is confirmed. During the next operation, defects are detected in the final acceptance. A rework process is triggered immediately, the rework activity is confirmed, and the additional material consumption is posted. To simulate the process, we assume that some defects were found by inspection during production. For this reason, the insertion of a rework operation within the same production order is initiated automatically.
Confirm Production Order at Rework Operation	This process step shows you how to confirm and settle the additional rework operation within the original production order. This causes production variances within controlling and price differences for the dedicated product.
Manage Production Operations	After the release / confirmation of finished goods orders is performed, this process step shows you how to display and review the order using the Manage Production Operations (F2335) app for the material.
Confirm Subsequent Operation Including Reworked Quantity	This process step shows you how to confirm the subsequent operations after rework operation confirmation executed, which could summarize the yield quantity from previous operation and rework operation.
Review Manufacturing Object Pages	This process step shows you how to review the different objects pages available for different roles in the area of manufacturing.
Delete Reference Operation Set from Routing	In this step you delete the reference operation set from the routing.

Business Roles for Rework Processing – Work-in-Process (BJQ)

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