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 Material Replenishment with Kanban – In-House Production (4B3)

Objectives

After completing this lesson, you will be able to:

Define process steps and business roles for material replenishment with kanban – in-house production (4B3)
Identify business roles for material replenishment with kanban – in-house production (4B3)

Process Steps for Material Replenishment with Kanban – In-House Production (4B3)

Applicable Process Steps

Process Steps	Description
Create Planned Independent Requirements	Planned Independent Requirements (PIRs) are used to perform demand management functions. A planned independent requirement contains one planned quantity and one date, or a number of planned independent requirements schedule lines, that is, splitting one planned quantity according to dates.
Material Requirements Planning	The purpose of material requirements planning is to tailor available capacities and receipts on time to suit requirements quantities. You can use MRP or consumption-based planning for this purpose.
Adjust Planning in Planning Table	The planning table is used to plan the production of materials on production lines. After planning is complete, the planned orders are fixed.
Set Available Kanban to EMPTY	Setting a Kanban container to EMPTY triggers replenishment of the material.
Change the Kanban to FULL	Setting an empty Kanban to FULL triggers a repetitive manufacturing backflush where the goods receipt is posted. The backlush receives the amount that is required to "fill" the Kanban, and consumes the components specified in the Bill of Material to produce the received amount.
Check Dependent Requirements of Material	In this step, you check whether planned orders exist for a material.
Set Available Kanban to EMPTY	When setting the container to EMPTY, the system automatically creates and directly releases a production order with order type YPK1. With this strategy, one production order will be created for one empty Kanban container.
Pick Components for Production Order	When a production order is released, you have to pick components for the order, then post the goods movements.
Confirm Production Operation	The confirmation document contains the processing status of orders, operations, sub-operations, and individual capacities that you review before making the final confirmation.
Repetitive Manufacturing Backflush	A backflush is an accounting method that records the costs associated with producing the good only after it has been produced, completed, or sold. This step executes multiple activities in a single step, such as finished product goods receipt, backflush of component materials, posting of costs to cost collector and creation of material and journal entries.
Post Processing List of Error Records	If errors occur during backflushing (for example, material movements missing for previous backflush oeprations), you can create a list of components that have to be post-processed.
Review Manufacturing Object Pages	You can make corrections to resolve errors that have occurred during the backflush here, in the Reprocess Goods Movements app.

Business Roles for Material Replenishment with Kanban – In-House Production (4B3)

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.

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