Business Process Procedures - SAP Service …sapidp/... · Web viewBusiness purpose Procedure Technical/System Prerequisites for Transactional Apps The prerequisite for using the

SAP Fiori Apps for the SAP ERP Application PP

SAP SEDietmar-Hopp-Allee 1669190 WalldorfGermany

How to implement defined Fiori apps on top of the SAP Best Practices Baseline packages.

Based on the example of US Baseline V3.607

How-to Guide: V1.00


Copyright

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

© SAP SE Page 2 of 28

http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.



Contents

SAP Fiori Apps for ERP Baseline – Application PP...................................................................6

1 Purpose of SAP Fiori..........................................................................................................6

2 Overview Matrix for PP Fiori Apps......................................................................................7

3 Ready-to-Activate / Fully-Activated Version.....................................................................11

4 Technical/System Prerequisites for Transactional Apps...................................................11

5 Transactional PP Apps.....................................................................................................12

5.1 General Configuration.................................................................................................12

5.2 Required SAP Notes...................................................................................................12

5.3 Technical Data............................................................................................................12

5.3.1 Back-End Components.........................................................................................12

5.3.2 Front-End Components: UI5 Application...............................................................13

5.3.3 Front-End Server: SAP Fiori Launchpad Components.........................................13

5.3.4 Technical Requirements.......................................................................................14

5.3.5 Configuration and App Implementation for Baseline Processes...........................14

5.3.6 Assign User Roles in the Back-End System.........................................................14

5.3.7 Activation of Gateway Service in the SAP Gateway Server with Transaction.......15

5.4 Material Requirements Planning.................................................................................17

5.4.1 Business Purpose for Material Requirements Planning........................................17

5.4.2 Monitor Material Shortages...................................................................................17

5.4.3 Manage Material Shortages..................................................................................19

5.4.4 Monitor External Requirements............................................................................20

5.4.5 Manage External Requirements...........................................................................21

5.4.6 Supported Scope Items........................................................................................22

5.5 Production Order Handling.........................................................................................23

5.5.1 Business Purpose for Production Order Handling................................................23

5.5.2 Production Order Release....................................................................................23

5.5.3 Confirm Production Operations.............................................................................24

5.5.4 Confirm Production Orders...................................................................................25

5.5.5 Supported Scope Items........................................................................................26

6 Technical/System Prerequisites for SAP Smart Business Apps.......................................26

7 Technical/System Prerequisites for Fact Sheets..............................................................27

8 Fact Sheets for PP...........................................................................................................27

8.1 Fact Sheet for Production Order.................................................................................27

8.1.1 Description............................................................................................................27



8.1.2 Navigation Targets................................................................................................27

8.1.3 Transactions.........................................................................................................27

8.1.4 Technical Requirements.......................................................................................27

8.1.5 Technical Data......................................................................................................28



SAP Fiori Apps for ERP Baseline – Application PP

1 Purpose of SAP FioriSAP Fiori is a collection of apps that represent the new SAP user experience. SAP Fiori apps have a consistent design language and make use of a common technical infrastructure. They provide a consistent end-to-end user experience and can be used across all device types without creating additional implementation effort.

Organized by user role, the SAP Fiori launchpad is the central entry hub to all Fiori apps where users access apps via tiles. The launchpad has services for navigation, personalization, single sign-on, and search. The launchpad and the tiles are flexible and can be adapted to your needs. You can use the search in the SAP Fiori launchpad to perform a cross-entity search through core SAP Business Suite applications. The search uses the SAP NetWeaver Embedded Search technology on a SAP HANA database. New SAP HANA-enabled search models are delivered for core business objects.

The Fiori apps focus on critical and common activities and are designed around how people work:

Role-based: Fiori apps decompose complex applications into a task-based experience with one central entry point for each user.

Responsive: Fiori apps adapt to all sizes, devices, versions, and channels to provide a common user experience across all channels.

Simple: Fiori apps follow the 1-1-3 experience (1 user, 1 scenario, 3 screens). They know and provide the right context and meaningful data integration.

Coherent user experience with apps that speak the same design language. This implies coherence for common activities as well as coherence for your brand.

Instant value with a low barrier to adoption, enabling customers to adapt and users to personalize.

Interactive on desktop, tablet, and mobile platforms

All UIs are built using state-of-the-art technology such as HTML5 and SAP UI5 mobile. Fiori apps allow you to access the most recent version of your back-end data via OData services. Through previously defined roles and authorizations, you can specify which apps and which data a user is allowed to access.

The purpose of this document is to give the user all necessary information around the SAP Fiori apps for PP to be able to run them on top of the SAP Best Practices MM processes.



2 Overview Matrix for PP Fiori AppsThe following matrix shows the existing Fiori roles available within the MM application and the assigned Fiori apps.



Fiori Role Fiori App Short Description Mapping to Scope Item(Baseline Scope Item) IDs

Fiori Application Type

SAP HANA Mandatory

Material Requirements Planner - Buy Scenarios Only

Monitor Material Shortages

You can monitor material shortages in a selected area of responsibility. You can specify a shortage definition and a time horizon to determine which materials you want to check. You can specify a shortage definition and a time horizon to determine which materials you want to check.

Make-to-Stock Production - Discrete Industry (MTS)* (145)

Transactional No

Manage Material Shortages

You can check the coverage of your materials based on the settings you made in the Monitor Material Shortages app. To help you solve your shortages, the system proposes different solutions. You can simulate the solution to preview its effects and you can apply the solution that best solves your issue.


Transactional No

Monitor External Requirements

You can monitor the uncovered requirements originating from sales orders and stock transport orders in a selected area of responsibility. You can specify a shortage definition and a time horizon to determine which uncovered external requirements you want to check.


Transactional No

Manage External Requirements

You can check your uncovered and delayed items based on the settings you made in the Monitor External Requirements app. To help you cover your external requirements, the system proposes different solutions. You can simulate the solution to preview its effects and you can apply the solution that best solves your issue.


Transactional No

SAP Production Planning & Control

Confirm Production Orders

A production worker can perform partial or final confirmations for production orders through a simplified and intuitive UI. The app provides fast order input and simplified order confirmation procedures that are available for desktop, tablet, and mobile.


Transactional No

Confirm Production Operations

Production workers can view and confirm order operations released to their work centers. They can search for the next order operation that they want to confirm by its number or confirmation number. They can use various sorting and filtering options that speed up and simplify the search for an order operation that they want to confirm. Production workers can


Transactional No





SAP HANA Mandatory

partially or finally confirm a production order operation anytime and from any place using various mobile devices.

Production Supervisor

Release Production Orders

Production supervisors can release production orders using a highly intuitive and user-friendly application. The browser based application supports desktop, tablet and mobile devices.


Transactional No

Production Order

This fact sheet displays contextual information about the Production Order. You can navigate to its related entities and you can access related transactions in operational systems.


Fact sheet No

Planned Order This fact sheet displays contextual information about the Planned Order. You can navigate to its related entities and you can access related transactions in operational systems, or you can navigate to related transactional applications.


Fact sheet No

Process Order This fact sheet displays contextual information about the process order. You can navigate to its related entities and you can access related transactions in operational systems, or you can navigate to related transactional applications.

Make-to-Stock Production – Process Industry (146)

Fact sheet No

Resource This fact sheet displays contextual information about the resource. You can navigate to its related entities and you can access related transactions in operational systems, or you can navigate to related transactional applications.



Fact sheet No

Work Center This fact sheet displays contextual information about the work center. You can navigate to its related entities and you can access related transactions in operational systems, or you can

Make-to-Stock Production - Discrete Industry

Fact sheet No





SAP HANA Mandatory

navigate to related transactional applications. (MTS)* (145)




* For Wave 2, the MRP Fiori apps are capable to manage external procurements such as purchase orders or purchase requisitions. All scope items using procured materials (raw or semi-finished) can use these Fiori Apps.

Procurement without QM (130)

Stock Transfer with Delivery (MRP run requires 130) (134)

Make-to-Stock Production – Discrete Industry (MTS) (145)


3 Ready-to-Activate / Fully-Activated VersionFor the Ready-to-Activate version, the complete content described in this document is relevant.

For the Ready-to-Demo version, you can skip all the chapters which treat configuration topics. The following subchapters are relevant for each Fiori application:

Description

Key Features

Business purpose

Procedure

4 Technical/System Prerequisites for Transactional Apps

The prerequisite for using the SAP Fiori transactional apps is implementing the relevant application independent parts provided by the SAP Fiori apps rapid-deployment solution. This version of SAP Fiori apps rapid-deployment solution includes new SAP Fiori apps and enables the implementation of SAP NetWeaver Gateway, SAP UI5 and any of the SAP Fiori transactional apps. In general, it is necessary to set up the SAP Fiori system landscape.

The solution includes a description of the general configuration steps required to manually set up the configuration within the system landscape and information about the software installation. We have three scenarios for Fiori: transactional apps, analytical apps and fact sheets. Each scenario has its specific systems or software that need to be installed. By reading through the referenced documents, you should be able to set up your own Fiori landscape based on your existing system environment.

The package delivers a description of the SAP Fiori related security configuration. When running your SAP Business Suite system, you must ensure that your data and processes support your business needs without allowing unauthorized access to critical information. This document provides the network safety related system components settings, and based on SAML2.0, SSO2 and X.509, a single point of Single Sign-on authentication configuration.

The SAP Fiori launchpad is the entry point to SAP Fiori apps on mobile or desktop devices and the Launchpad Designer is the standard tool for configuring the launchpad. The configuration



guide provides the information for the setup and also explains how to add the different types of apps to the launchpad.

For detailed information on the technical implementation of the above mentioned prerequisites, refer to the SAP Fiori Apps rapid-deployment solution on the SAP Service Marketplace (direct access to the page: http://service.sap.com/rds-fiori-apps).

5 Transactional PP Apps

5.1 General ConfigurationIn the following the necessary configuration steps for the activation and usage of the app are mentioned in a short checklist. Details are described in the relevant configuration guides for the SAP Fiori Apps rapid-deployment solution, SAP HANA Live rapid-deployment solution and SAP Fiori Infrastructure rapid-deployment solution.

5.2 Required SAP NotesFor Monitor Material Shortages, the following SAP Notes must be implemented:

Back-End/Front-End Server SAP Note Number Description

Back-end and front-end servers

1955289 Release Information Note for SAP Fiori Apps for Material Requirements Planning

1931275 Fiori-App: “Release Production Orders” corrections

1893788 Conversions in SAP NetWeaver Gateway Framework

5.3 Technical DataThe following tables list technical objects specific to the apps in the production environment.

5.3.1 Back-End ComponentsOData Service App Authorization Role (PFCG Role)

PP_MRP_COCKPIT_SRV (1) Monitor Material Shortages

SAP_PP_MATSHORT_MR_APP


SAP_PP_MATSHORT_DT_APP


SAP_PP_UNCOVSO_MR_APP


SAP_PP_UNCOVSO_DT_APP

PP_PRODORDER_RELEASE_SRV Release Production orders

SAP_PP_PRODORD_REL_APP

PP_PRODOPS_CONFIRM_SRV Confirm Production

SAP_PP_PROD_OPS_CONF_APP


https://service.sap.com/sap/support/notes/1893788

https://service.sap.com/sap/support/notes/1931275

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1955289&_NLANG=en&_NVERS=0

http://www.service.sap.com/rds-fiori-apps


OData Service App Authorization Role (PFCG Role)

Operations

PP_PRODORD_CONFIRM Confirm Production Orders

SAP_PP_PROD_ORD_CONF_APP

CB_PRODUCTION_ORDER_SRV (1)

Fact Sheet for Production Order

SAP_PP_TCR_T

5.3.2 Front-End Components: UI5 ApplicationComponent App Technical Name

UI5 Application Monitor Material Shortages

PP_MATSHORT_MR


PP_MATSHORT_DT


PP_UNCOVSO_MR


PP_UNCOVSO_DT

Release Production Orders

PP_PRODORD_REL


PP_PRODOPS_CNF


PP_PRODORD_CNF

5.3.3 Front-End Server: SAP Fiori Launchpad ComponentsApp Component Technical Name

MRP Business Role SAP_PP_BCR_MRPController

Business Catalog SAP_PP_BC_MRPController

Business Catalog Group SAP_PP_BCG_MRPController

Technical Role SAP_PP_TCR_T

Technical Catalog SAP_PP_TC_T

LPD_CUST Role UIAPPP01

LPD_CUST Instance TRANSACTIONAL

Production Order Business Role SAP_PP_BCR_Worker

Business Catalog SAP_PP_BC_Worker

Business Catalog Group SAP_PP_BCG_Worker



5.3.4 Technical RequirementsThe following software products must be available in your system landscape:

Back-end system (business data)

Required product release: SAP enhancement package 7 for SAP ERP 6.0 SP03

Required software components: SAP_APPL 617

UI add-on (front-end components)

Required product release: UI for EHP7 for SAP ERP 6.0

Required software components: UIEAAP01 SP01

The SAP HANA database is mandatory for working with SAP Fiori apps for MRP. All restrictions concerning the handling of materials on an SAP HANA database are also valid for the MRP apps. For more information about restrictions, see Restrictions.

Mobile devices with small displays are not supported by the MRP apps due to usability issues. Small displays require condensing the complex MRP data and relevant information to such a degree that it is no longer possible to work with the MRP apps efficiently. For more information, see SAP Note 1955289.

5.3.5 Configuration and App Implementation for Baseline Processes

Before implementing the apps, you must ensure the following:

You have configured the Material Requirements Planning component in the back-end system. For more information, see the Customizing Production → Material Requirements Planning.

You have installed and configured the app-specific configurations as described in the chapters below.

You have assigned the authorizations that are required for changing and creating requisitions or orders to the business users in the backend system.

You have configured the RFC connection SAP_ERP_PP with connection type H and chosen Trusted Relationship as the Logon Procedure. This RFC connection is used for navigating to the back-end system to view the stock/requirements list or change material data. If you use a different name for the RFC connection, you have to change the system alias for the entries Stock Requirements List and Change Material in transaction LPD_CUST for role UIAPPP01 and instance TRANSACTIONAL.

5.3.6 Assign User Roles in the Back-End SystemAssign the necessary backend role for the Monitor Material Shortages app in the ERP system to the user used for the launchpad logon.

Procedure 1. Access the activity using one of the following navigation options:


http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1955289&_NLANG=en&_NVERS=0


IMG Menu Tools → Administration → User Maintenance → Role Administration → Roles

Transaction Code PFCG

2. On the Role Maintenance screen, enter the role as mentioned in the table below, and then choose Change.

Fiori App Name Role Name

Monitor Material Shortages

SAP_PP_MATSHORT_MR_APP


SAP_PP_MATSHORT_DT_APP


SAP_PP_UNCOVSO_MR_APP


SAP_PP_UNCOVSO_DT_APP

Release Production orders

SAP_PP_PRODORD_REL_APP


SAP_PP_PROD_OPS_CONF_APP


SAP_PP_PROD_ORD_CONF_APP

Fact Sheet for Production Order

SAP_PP_TCR_T

3. On the Change Roles screen, make sure that there is a green light on the Authorization tab page.

4. Choose the User tab page, enter the User ID as backend user.

5. Save your entries.

5.3.7 Activation of Gateway Service in the SAP Gateway Server with Transaction

UseOData Channel implementations retrieve the data from an SAP business system, that is, a backend system.

Once a service has been defined in the backend system, the service must be registered or activated in the SAP NetWeaver Gateway system.

This is a generic step that you must only carry out once an SAP Fiori app shall be activated that is not yet part of this rapid-deployment solution. In this case, the name of the service must be known, and the service can be activated as stated below.



In case the apps are configured as part of this package, skip this step. The app-specific service to be activated will be mentioned in the app-specific configuration guide.

Procedure1. Access the activity using the following navigation options:

Transaction Code /IWFND/MAINT_SERVICE

IMG Menu SAP NetWeaver → Gateway→ OData Channel → Administration → General Settings → Activate and Maintain Services

2. Choose Add Service.

3. On the Add Service screen, enter the System Alias and choose Enter. A list of services is displayed.

Field Name Entry Value

System Alias <SYSTEM ALIAS of ERP>

4. Choose Get Services.

5. Choose the Technical Service Names.

Field Name Entry Value

Technical Service Name PP_MRP_COCKPIT_SRV (1)

PP_PRODORDER_RELEASE_SRV

PP_PRODOPS_CONFIRM_SRV

PP_PRODORD_CONFIRM

Only services that are not yet activated are displayed in this list. To find the Technical Service Name to be activated, perform a wild card search in the Technical Service Name field with the Service Name provided in the app-specific configuration guide in chapter Activation of Gateway Service in SAP NetWeaver Gateway.

Example: Search for *SRA007_BENEFITS_SRV *. The system searches for the Technical Service Name which may include additional namespace information but includes the External Service Name.

6. Enter the name of the package being used.

7. Select Standard Mode in the ICF Node section.

8. Select the Set current client as default client in ICF node.

9. Choose Continue (Enter). Assign your Workbench and Customizing Requests and confirm the displayed messages.

10. Confirm the information message that the metadata was loaded successfully.

11. Choose Back.

12. Select the record you have just created in the list.

13. Choose Gateway Client.

14. Choose Execute (F8).



The HTTP response is displayed and an XML file appears in the lower right corner. This indicates that the web service has been configured properly.

To run an SAP Fiori app, it is required that in addition to the above mentioned services, at least two app-specific services are activated per app. One service provides the required UI components and the other service establishes a connection to the backend and provides the required backend data. Which services are required in this case is described in detail in the app-specific configuration guides.

For web service calls, you must maintain authorization object S_SERVICE. You then assign the web service operations to a role in transaction PFCG.

Find more information, see Defining Operation-Specific Security Authorizations for Web Services in the SAP Help Portal.

In case an error message occurs indicating that the http request failed, check the following:

Does the trusted RFC connection work properly?

Check in the Trust Manager (transactions trust) if the SSL certificates are set up properly so the gateway system can communicate properly with the respective backend system.

5.4 Material Requirements Planning5.4.1 Business Purpose for Material Requirements PlanningIn Material Requirements Planning, one of the main tasks of an MRP controller is to monitor the material shortage situation and solve any issues in time. Another main task is to ensure that sufficient supplies have been planned to cover your external requirements — whether from sales orders or stock transfer orders, for example. The goal is to ensure that both customer and production demand are available on time and to avoid any disruptions due to missing parts. To enable the MRP controller to fulfil these goals, you can define a material shortage profile and material shortage definitions in the Customizing. These Customizing settings provide sets of rules that the system uses for calculating material shortages and uncovered demands (or uncovered external requirements). These rules define the scope of the shortage calculation meaning the supply and demand elements to be considered, the conditions that have to be met to be a relevant shortage, or the priority of the demand elements.

5.4.2 Monitor Material Shortages

5.4.2.1 Business Purpose for Monitor Material ShortagesWith the Monitor Material Shortages transactional app, you can monitor material shortages in a selected area of responsibility. You can specify a shortage definition and a time horizon to determine which materials you want to check.


http://help.sap.com/saphelp_nw73ehp1/helpdata/en/63/ed7746b6044288928b1382232ec10a/content.htm

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/63/ed7746b6044288928b1382232ec10a/content.htm


The Material Resource Planner calls the app to monitor the availability for purchased materials and react on possible underdeliveries for sales orders caused by missing input materials.

5.4.2.2 Key FeaturesWith the Monitor Material Shortages app, you can do the following:

Select an area of responsibility

Select a shortage definition and specify a time horizon to determine which materials you want to monitor

Narrow down the scope of the material list by using facet filters

View a material list according to the selected shortage definition as well as other selection criteria

Personalize the table by choosing which table columns are shown and how table entries are sorted

Display a chart showing the stock availability of a selected material over the next 21 days

Tailor the app to your needs and save the combination of shortage definition, time horizon, and filters as a variant

Save your personalized variants as tiles on your home page from which you can directly navigate to the Manage Material Shortages app

View details of the selected materials and check different solutions in the Manage Material Shortage app

5.4.2.3 Prerequisites for ConfigurationBefore implementing the app, you must ensure the following:

Default configuration settings are provided for this app in the Customizing for Production → Material Requirements Planning → Apps for Material Requirements Planning → General Settings. Check if the SAP standard configuration settings in the following Customizing activities meet your business requirements. If this is the case, no further changes are necessary.

Otherwise, you can tailor the following Customizing settings to your needs:

Define Supply and Demand Profiles:In this activity, you can create your own supply and demand profiles. Here, you organize your supply and demand elements into groups that you assign to the material shortage definitions in a later Customizing step. This filters the supply and demand elements to be used for the calculations.

Define Material Shortage Profiles:In this activity, you can create your own material shortage profile. The material shortage profile contains the individual material shortage definitions that you can select in the app in the Shortage Definition drop-down box. The shortage definition contains the specific set of rules for calculating the material shortage or uncovered demand.

Assign Material Shortage Profile to Users:In this activity, you can assign the material shortage profile to your users. This controls the material shortage definitions the user can choose from in the app. If you make no changes here, the system automatically uses the SAP standard material shortage profile for all users.



5.4.3 Manage Material Shortages

5.4.3.1 Business Purpose for Manage Material ShortagesWith the Manage Material Shortages transactional app, you can check the coverage of your materials based on the settings you made in the Monitor Material Shortages app. To help you solve your shortages, the system proposes different solutions. You can simulate the solution to preview its effects and you can apply the solution that best solves your issue.

5.4.3.2 Key FeaturesWith the Manage Material Shortages app, you can do the following:

View a list of your materials with shortages

View details of material shortages as a table or a chart

View additional MRP information

Navigate to the back-end system to view the stock/requirements list or change material data

Select a shortage to check the different solutions proposed by the system

Preview the effects of the proposed solutions as a table or a chart

Choose a solution to apply the changes


You have configured the Material Requirements Planning component in the back-end system. For more information, see Customizing for Production → Material Requirements Planning.

You have installed and configured the Monitor Material Shortages app. For more information, see App Implementation: Monitor Material Shortages.

You have assigned the authorizations that are required for changing and creating requisitions or orders to the business users, in the back-end system.

You have activated the Gateway service PP_MRP_COCKPIT_SRV 0001 (Version 1) in the Gateway system.

You have configured the RFC connection SAP_ERP_PP with connection type H and chosen Trusted Relationship as the Logon Procedure. This RFC connection is used for navigating to the back-end system to view the stock/requirements list or change material data. If you use a different name for the RFC connection, you have to change the system alias for the entries Stock Requirements List and Change Material in transaction LPD_CUST for role UIAPPP01 and instance TRANSACTIONAL.



5.4.4 Monitor External Requirements

5.4.4.1 Business Purpose for Monitor Material ShortagesWith Monitor External Requirements, you can monitor the uncovered requirements originating from sales orders and stock transport orders in a selected area of responsibility. You can specify a shortage definition and a time horizon to determine which uncovered external requirements you want to check.


Select an area of responsibility.

Select a shortage definition and specify a time horizon to determine the scope of the uncovered external requirements you want to check.

Narrow down the scope of the requirements list by using facet filters.

View a table of sales orders and stock transport orders according to the selected shortage definition as well as other selection criteria.

Personalize the table by choosing which table columns are shown and how table entries are sorted.

Tailor the app to your needs and save the combination of shortage definition, time horizon, and filters as a variant.

Save your personalized variants as tiles on your home page from which you can navigate directly to the Manage External Requirements app.

View details of selected materials and check different solutions on the Manage External Requirements app.


You have configured the Material Requirements Planning component in the back-end system. For more information, see Customizing Production → Material Requirements Planning.

You have assigned the authorizations that are required for displaying the Stock/Requirements List (transaction MD04) to the business users, in the back-end system.

Default configuration settings are provided for this app in the Customizing Production → Material Requirements Planning → Apps for Material Requirements Planning → General Settings. Check if the SAP standard configuration settings in the following Customizing activities meet your business requirements. If this is the case, no further changes are necessary.

Otherwise, you can tailor the following Customizing settings to your needs:

Define Supply and Demand Profiles:In this activity, you can create your own supply and demand profiles. Here, you organize your supply and demand elements into groups that you assign to the material shortage definitions in a later Customizing step. This filters the supply and demand elements to be used for the calculations.



Define Material Shortage Profiles:In this activity, you can create your own material shortage profile. The material shortage profile contains the individual material shortage definitions that you can select in the app in the Shortage Definition drop-down box. The shortage definition contains the specific set of rules for calculating the material shortage or uncovered demand.

Assign Material Shortage Profile to Users:In this activity, you can assign the material shortage profile to your users. This controls the material shortage definitions the user can choose from in the app. If you make no changes here, the system automatically uses the SAP standard material shortage profile for all users.

5.4.5 Manage External Requirements

5.4.5.1 Business Purpose for Monitor Material ShortagesWith Manage External Requirements, you can check your uncovered and delayed items based on the settings you made in the Monitor External Requirements app. To help you cover your external requirements, the system proposes different solutions. You can simulate the solution to preview its effects and you can apply the solution that best solves your issue.


View a list of your uncovered and late external requirements.

View details of external requirements as a table or as a chart.

View additional MRP information.

Navigate to the back-end system to view the stock/requirements list or change material data.

Select an uncovered item to check the different solutions proposed by the system.

Preview the effects of the proposed solutions as a table or a chart.

Choose a solution to apply the changes.


You have configured the Material Requirements Planning component in the back-end system. For more information, see the Customizing Production → Material Requirements Planning.

You have installed and configured the Monitor External Requirements app. For more information, see App Implementation: Monitor External Requirements.

You have assigned the authorizations that are required for changing and creating requisitions or orders to the business users, in the back-end system.

To implement the app, you must specify which contact person function is relevant for this app. You make this setting in the Customizing Production → Material Requirements Planning → Apps for Material Requirements Planning → General Settings → Specify Functions of Vendor



Contact Person. You can then view data for the contact person with the function you have specified when opening a solution card in the app.

5.4.6 Supported Scope ItemsThe transactional apps for Material Resource Planning can support the scope item Make-to-Stock Production (145). You can make use of the following materials.

Material Type RAW

Purchasing Org 1000

Purchasing Group 100

Vendor 300000

Plant 1000

MRP Controller 101

Material R13, R14, R16; R27

Material Type RAW

Purchasing Org 1000


Vendor 300000

Plant 1000

MRP Controller 101

Material R17

Material Type RAW

Purchasing Org 1000


Vendor 300001, 300005

MRP Controller 101

Plant 1000

Material R18

Material Type RAW

Purchasing Org 1000


Vendor 300000

MRP Controller 101



Material Type RAW

Plant 1000

Material R20, R122, R128

Material Type RAW

Purchasing Org 1000


Vendor 300001, 300003, R300008

MRP Controller 101

Plant 1000

Material R120

5.5 Production Order Handling5.5.1 Business Purpose for Production Order HandlingWith Release Production Orders, production supervisors can release production orders using a highly intuitive and user-friendly application. The browser based application supports desktop, tablet and mobile devices. The confirmation of the production can be similarly done by the shop floor worker either on header or operations level.

5.5.2 Production Order Release

5.5.2.1 Business Purpose for Production Order ReleaseWith Release Production Orders, production supervisors can release production orders using a highly intuitive and user-friendly application. The browser based application supports desktop, tablet and mobile devices. The confirmation of the production can be similarly done by the shop floor worker either on header or operations level.

5.5.2.2 Key FeaturesThe Production Order related apps have the following capabilities:

Provide an overview of production orders to be released based on individual variants

Give end-users immediate overview of missing parts

Detailed screen that provides end users with decision-critical information (date and time, system and user status, relevant work centers, missing part information for operations, and so on)

Search engine to identify and filter production orders

Provides the ability to perform the material availability check on one or more production orders

Navigation to the stock requirement list from the material description from the detail screen or from the missing parts overview screens



Columns in the overview table can be sorted in ascending or descending order

Availability check can be performed to find missing parts that is displayed with an alert box displaying the number of missing parts

5.5.2.3 Prerequisites for Configuration

Before implementing the app, you must ensure the following:

You have created one or several variants in the back-end using transaction Create Variant for Production Order Selection (RPSPOR1).

The variants must be assigned to a user in transaction Assign Variant for Production Order Selection to User (RPSPOR2).

5.5.3 Confirm Production Operations

5.5.3.1 Business Purpose for Confirm Production OperationsWith Confirm Production Operations, production workers can view and confirm order operations released to their work centers. They can search for the next order operation that they want to confirm by its number or confirmation number. They can use various sorting and filtering options that speed up and simplify the search for an order operation that they want to confirm. Production workers can partially or finally confirm a production order operation anytime and from any place using various mobile devices.

5.5.3.2 Key FeaturesThe Confirm Production Operations app has the following capabilities:

Displays order operation released to the user’s work center

Enables search for a production order operation by its number or confirmation number

Allows to partially or finally confirm an order operation

Provides access to goods movement information during confirmation

Allows to sort and filter the list of order operation by status and time frame

Also allows to sort and filter by operations defined as milestone in the SAP ERP back-end system

Provides graphical progress bar to view confirmed quantities

Runs on SAP HANA, as well as on any other database

Is a web-based application that can be easily enhanced using HTML5

Enables direct navigation to Material fact sheet

Offers an intuitive and user-friendly navigation




Personnel number is entered under Human Resources.

To do this, on the SAP Easy Access screen, choose Human Resources → Personnel Management → Administration → HR Master Data → Personnel Actions. You can also use transaction PA40 to create a personnel number.

SAP name is assigned to the personnel number.

To do this, on the SAP Easy Access screen, choose Human Resources → Personnel Management → Administration → HR Master Data → Maintain. In the Direct Selection section, in the Infotype field, enter 105, and in the STy field enter 0001 as the subtype.

Personnel number is assigned to work center under Logistics.

To do this, from the SAP Easy Access screen, choose Logistics → Production → Master Data → Work Centers. You can also use transaction CR01 to create a work center or transaction CR02 to change a work center.

After you have created or changed a work center, choose Basic Data HRMS to assign the personnel number to the work center.

Production orders exist and are released in SAP ERP.

5.5.4 Confirm Production Orders

5.5.4.1 Business Purpose for Monitor Material ShortagesWith the Confirm Production Orders, a production worker can perform partial or final confirmations for production orders through a simplified and intuitive UI. The app provides fast order input and simplified order confirmation procedures that are available for desktop, tablet, and mobile.

5.5.4.2 Key FeaturesThe Confirm Production Orders app has the following capabilities:

Search for a production order by its number

Display a list of orders based on the variant configured for the production order and assigned to the user in SAP ERP

Perform partial or final confirmation for a production order

Access goods movement information during confirmation

Provides graphical progress bar to view planned and confirmed quantities

Runs on SAP HANA as well as on any other database

Is a web-based application that can be easily enhanced using HTML5

Direct navigation to Material fact sheet

Offers an intuitive and user-friendly navigation




Production order variant is created in SAP ERP (transaction code RPWPORDC1)

Production order variant is assigned to the user (transaction code RPWPORDC2)

Production orders exist and are released in SAP ERP

5.5.5 Supported Scope ItemsThe transactional apps for Material Resource Planning can support the scope item Make-to-Stock Production (145). You can make use of the following materials.

Master / Org. Data Value Master / Org. Data Details

Material F126 Finished Good MTS

S21 Semi-finished Good Repetitive Manuf.

S22 Semi-finished Good Phantom

S23 Semi-finished Good Subcontracting

S25 Semi-finished Good Ext. Procurement

S124 Semi-finished Good Subassembly

Plant 1000 Plant 1 - Production Plant

Storage Location 1020 Production storage location

1030 Shipping Storage location

1050 Stores Storage location

6 Technical/System Prerequisites for SAP Smart Business Apps

The prerequisite for using the SAP Smart Business for Sales Order Fulfillment is implementing the SAP Fiori Design Infrastructure rapid-deployment solution. This solution enables SAP customers and partners to deploy, configure, and validate the landscape components required for the enablement of SAP Fiori designs on top of SAP Business Suite powered by SAP HANA. The solution delivers deployment and configuration guidelines which are relevant for all SAP Fiori apps or for a specific SAP Fiori archetype such as the SAP Smart Business apps. It focuses on SAP Fiori landscape, security and networking settings, launchpad setup, personalization topics, KPI framework setup, KPI Modeler and search models configuration.



7 Technical/System Prerequisites for Fact Sheets

SAP Fiori has three app types, each distinguished by their focus and infrastructure requirements. The below mentioned document is to describe generic enablement configuration activities for each App Type. The document also describes the configuration for fact sheets.

These fact sheets display contextual information about central objects used in your business operations. They are designed to be intuitive and harmonized fact sheets and allow navigation from one fact sheet to other related fact sheets. For example, you can navigate from master data like customer or material to related documents like sales order, delivery, billing document or vice versa.

Fact sheets run only on an SAP HANA database and require an ABAP stack.

8 Fact Sheets for PP

8.1 Fact Sheet for Production Order8.1.1 DescriptionThis fact sheet displays contextual information about the Production Order. You can navigate to related entities and access related transactions in operational systems.

8.1.2 Navigation TargetsYou can navigate to the following apps, for example:

Release Production Order

Confirm Production Order

Sales Order

Material

Customer

WBS Element

Work Center

8.1.3 TransactionsYou can access the following transactions, for example:

Display Production Order

Pegged Requirements Production Order

8.1.4 Technical RequirementsThe technical requirements are:

SAP enhancement package 7 for SAP ERP 6.0 SP02

UI for EHP7 for SAP ERP 6.0



8.1.5 Technical DataFront-End Components

Component Technical Name

UI5 Application BCSBN_PRODUCTIONORDER_ANNO.XML

Business Role SAP_PP_BCR_PRODSUPERVISOR

Business Catalog SAP_PP_BC_PRODUCTIONSUPERVISOR

Business Catalog Group -


Business Process Procedures - SAP Service …sapidp/... · Web viewBusiness purpose Procedure Technical/System Prerequisites for Transactional Apps The prerequisite for using the

Documents