Understanding Process Steps and Business Roles for Enabling Manufacturing Subsidiary to Handle Assembly for Headquarters (2WL)

After completing this lesson, you will be able to:

After completing this lesson, you will be able to:

  • Define process steps and business roles for enabling manufacturing subsidiary to handle assembly for headquarters (2WL)
  • Identify business roles for enabling manufacturing subsidiary to handle assembly for headquarters (2WL)

Process Steps for Enabling Manufacturing Subsidiary to Handle Assembly for Headquarters (2WL)

Applicable Process Steps

Process StepDescription
Display Sales Order and Order Confirmation (Optional)In this activity, you see newly created sales order and order confirmation in SAP S/4HANA supplier system. A sales order is automatically created from PO and an order confirmation is automatically sent to the buyer system.The subcontracting purchase order is created in the opposite system (buyer) and sent to the SAP S/4HANA system (subsidiary as supplier side). For more information, see the Create Purchase Order test procedure in the Subcontracting (BMY) test script.
Material Requirements PlanningIn this step, you start the MRP run for the sales order created previously.
Monitor Material CoverageOnce the MRP has been performed, you can display the semifinished good (SG35) with in the stock and requirements list in the App Monitor Material Coverage Net / Individual Segments.Requirements planning has been carried out.
Convert Purchase Requisition to Purchase OrderThis activity creates a purchase order for consumables. This activity is only required if you do not convert an existing purchase requisition as described in Assign Purchase Requisition / Create Subcontract Order.
Approve Purchase Order (Optional)All the purchase orders that require release by an authorized person are listed and must be approved. Only POs with a value higher than 500.00 USD can be released in this transaction. POs with a value under this amount are not required to be released.
Goods Issue from HeadquarterIn this activity, goods issue is posted in the headquarter and communicated to subsidiary.
Post Goods ReceiptIn this step, you post the goods receipt for the material against the subcontracting PO.Goods issue against the subcontracting purchase order must have been created in the headquarter system (buyer side).
Convert Planned Order to Production OrderIn this step, planned order is converted into production order.
Release Production OrderIn this step, you release the production order.The production order created by the MRP controller is assigned a release date in accordance with the scheduling margin key.
Material Staging into Production Storage LocationIn this activity, you stage materials for production. If there is sufficient stock available on the production storage location, no line items are generated.
Pick Components for ProductionThe released production order is now ready for picking. Only those materials that are not in the service stock at the assembly aisle are to be picked. For picking, the operator selects the specific picking list that can be called up directly with the production order number. The operator has a series of further selection options to allow for optimal worklist selection.Ensure sufficient material is present in stock.
Confirm Assembly ActivitiesThis process shows the processing status of orders, different operations, and individual capacities. It is an instrument for controlling orders. This scope item uses time event confirmation.
Post Goods Receipt for Production OrderThe purpose of this activity is to post the goods receipt for the production order.
Create DeliveryIn this activity, you create the outbound delivery for the sales order.
Execute PickingThe picking process involves taking goods from a storage location and staging the right quantity in a picking area, where goods that are prepared for shipping.
Post Goods Issue for DeliveryIn this step, you post the goods issue for the delivery.
Send Advance Shipping NotificationThe advance shipping notification is automatically sent to the Buyer system. The goods issue must be available in the SAP S/4HANA system (supplier side)
Post Goods Receipt at Headquarter

In this step, you post the goods receipt for the material against the inbound delivery at Headquarter.

Create Billing Document

In this activity, you create billing document against the outbound delivery.

Goods receipt against the Inbound delivery should be created in opposite system (buyer). As the billing document creation in the SAP S/4HANA system (subsidiary as supplier side) triggers a supplier invoice to the opposite system which requires goods receipt.
Send InvoiceIn this activity, Supplier Invoice is automatically sent to Headquarter.
Review Supplier Invoice at Headquarter (Optional)In this procedure, a supplier invoice is displayed at Headquarter. These test steps are processed only when the corresponding supplier system sends an invoice.

Business Roles for Enabling Manufacturing Subsidiary to Handle Assembly for Headquarters (2WL)

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, 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:

  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.
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