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 Integration of SAP Manufacturing Execution to Production Operation (2JN)

Objectives

After completing this lesson, you will be able to:

Define process steps for integration of SAP Manufacturing Execution to production operation (2JN)
Identify business roles for integration of SAP Manufacturing Execution to production operation (2JN)

Process Steps for Integration of SAP Manufacturing Execution to Production Operation (2JN)

Applicable Process Steps

Process Step	Description
Maintain 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, such as one planned quantity split over time according to dates. 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.
Carry Out Material Requirements Planning at Plant Level	The aim of material requirements planning is to tailor available capacities and receipts on time to suit requirement quantities. You can use MRP or consumption-based planning for this purpose.
Evaluate Stock/Requirements Situation	After you’ve carried out the requirements planning, you want to display the stock/requirements situation for the finished good in the stock/requirements list.
Carry Out Conversion to Production Orders for Final Assembly	The daily MRP run creates planned orders for goods that are to be produced internally. When the planned opening date is reached, the planned orders are converted to production orders for both semifinished and finished goods.
Review Material Availability Status for Production Orders	In this step, you review the material availability status for production orders.Prerequisite: The production orders for subassembly and final assembly have been created.
Stage Materials for Final Assembly	In this activity, you stage materials for production. If there’s sufficient stock available in the production storage location, no line items are generated.
Release Production Order for Final Assembly	A release at order operation level results in the order and all its operations being released. The order and the operations receive the REL status (released).Prerequisite: The production order created by the MRP controller has been assigned a release date in accordance with the scheduling margin key.
Check Production Order Transfer	Upon release of the production order for the subassembly in SAP S/4HANA (status REL), the order is transferred to the SAP Manufacturing Execution system. For this solution, the automated transfer process (DRF) will be used.
Assign Routing	In this step, you assign the shop floor specific routing.
Release Shop Order	In SAP Manufacturing Execution, the shop order release activity releases the shop order and creates the SFCs that have either been assigned to that order in SAP S/4HANA or will be created by SAP Manufacturing Execution. The shop order has the Releasable status and the SFCs have the New status. You can edit selected attributes of the shop order such as the release quantity, scheduled start and end dates, and planned work center (line).
Open Line Monitor	In this activity, you open the line monitor to control the production line and to check the machine status before starting a new SFC.
Start OPC Server	In this activity, you start the OPC server that is sending and receiving tag information from SAP Manufacturing Execution via SAP Plant Connectivity. The activity instructions are done for a Kepware demo OPC server but can be done with any OPC server supporting the data access protocol and having simulation capabilities.
Log On to the Server Where the SAP Plant Connectivity Is Running	In this activity, you start the SAP Plant Connectivity agent instances to enable the connection between the machines and the SAP Manufacturing Execution system.
Simulate Production Process	In this activity, you simulate the production process.
Simulate Production Process Manually	In this activity, you simulate the production process manually,
Post Rejected SFC to Scrap	In this step, you post an SFC that was rejected as a result of the camera check to scrap.
Review Production Order	After the release or confirmation of finished goods orders has been completed, the production supervisor could display and check the order with the Manage Production Orders (F2336) app for the finished good. The finished good material is managed with serial numbers. The system generates a serial number for each finished good when the production order is released.
Check Serial Numbers	In this step, you check the generated serial numbers for finished goods.
Preview Goods Receipt Slip and Label	In this step, you preview the material document.
Review Scrap Report	In this activity, you review the scrap report.

Business Roles for Integration of SAP Manufacturing Execution to Production Operation (2JN)

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