Understanding Process Steps and Business Roles for Make-to-Stock – Process Manufacturing Based on Process Order (BJ8)

Objectives
After completing this lesson, you will be able to:

After completing this lesson, you will be able to:

  • Define process steps for make-to-stock – process manufacturing based on process order (BJ8)
  • Identify business roles for make-to-stock – process manufacturing based on process order (BJ8)

Process Steps for Make-to-Stock – Process Manufacturing Based on Process Orders (BJ8)

Applicable Process Steps

Process StepDescription
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, one planned quantity split over time according to dates. This process step shows you how to create PIRs.

Note
Instead of creating a single requirement, sometimes a requirements plan that includes one or more planned independent requirements can be maintained for mass processing. In this case, the requirements are grouped and maintained under a requirement plan number.
Material Requirements PlanningThe aim of material requirements planning is to tailor available capacities and receipts on time to suit requirement quantities. This process step shows you how to use MRP or consumption-based planning.
Evaluate the Stock / Requirement SituationThis process step shows you how to monitor the material coverage situation for the finished material product after the requirements planning has been carried out.
Create Process OrderThis process step shows you how to create process orders. Because the order release is executed automatically, production can start immediately.
Review Process OrderThis process step shows you how to review created process orders.
Goods Issue via Pick List

The withdrawal of the raw materials is used for the process order. This withdrawal can be done by using the picking list or doing a manual goods issue.

Note that if the material is set for backflush (in material master or resource), the withdrawing is done automatically after you confirm the operation or the whole order. Backflushing should not be used for batch-managed components (to ensure that the physically picked and consumed batch is the same as the recorded batch).

Manual Goods Issue (instead of Picking List)This process step shows you how to perform a goods issue.
Monitor Order ProgressThis process step shows you how to generate a work list for process orders, components and operations, with user-specific selection and layout settings.
Confirm Production incl. Component BackflushThe confirmation documents include the processing status of order, operations, phases and individual capacities. It is an instrument to control the order. The time ticket confirmation allows recording either the default times for machine and labour usage, or actual times for major deviations. Backflushed materials will be posted automatically during respective phase confirmations. This process step shows you how to confirm production. You can post scrap quantities as an optional. If no major deviations occurred, only the last phase (milestone) must be confirmed. Using milestone confirmation, all prior phases are confirmed automatically.
Post Goods Receipt for Process OrderThe purpose of this activity is to post the goods receipt for the process order. You may post goods receipt for the total quantity, but usually already partial quantities of the products are required for further processing, such as consumption for further production or subsequent deliveries for sales orders.
Review Process Order ConfirmationThis process step shows you how to review confirmations for process orders.
Review Scrap ReportThis process step shows you how to review the scrap report.
Review Manufacturing Object PagesThis process step shows you how to review different object pages available for different roles in Manufacturing area.

Business Roles for Make-to-Stock – Process Manufacturing Based on Process Orders (BJ8)

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

  1. Navigate to https://rapid.sap.com/bp/#/BP_CLD_ENTPR.
  2. Select your country localization from the Version drop-down list.
  3. In the Solution Scope section, expand the relevant scope item group.
  4. Select a scope item.
  5. Download the test script.
  6. 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, etc.). 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:

  1. Log into the SAP S/4HANA Cloud, public edition system.
  2. Select the Manage Business Roles application from the Launchpad.
  3. Select a Business Role.
  4. Select the Assigned Business Catalogs tab to view the standard Business Catalogs assigned to the standard Business Role.
  5. Select a Business Catalog.
  6. Select the Catalog Description tab to view the Functional Description, Authorization Criteria, and Associated Catalogs information.
  7. 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.

Log in to track your progress & complete quizzes