App Implementation: Manage External Requirements
In order to be able to implement this app, your system landscape has to be enabled for SAP Fiori. Depending on the database type serving as the basis in your system landscape, it has to be set up for SAP Fiori and has to meet the respective prerequisites:
| Database | SAP Fiori System Landscape Setup | Prerequisites |
|---|---|---|
ABAP environment |
Setup of SAP Fiori System Landscape for SAP Business Suite with ABAP Environment |
|
HANA database |
Setup of SAP Fiori System Landscape for SAP Business Suite with SAP HANA Database |
The SAP product version in the back-end system serving as the the basis for the app must be the following:
|
Required Back-End Product (Product Version Stack) |
|
-
The front-end components of the app consist of the user interfaces and content required for launching the app on the SAP Fiori launchpad. These components have to be installed on your front-end server.
-
The back-end components of the app mainly consist of the OData services required for the app. These components have to be installed in your back-end system.
|
App Component |
Required SAP Product Version (Support Package Stack) |
Available Instances Containing Software Component |
Software Component Required for App (Support Package) |
|---|---|---|---|
|
Front-End Components |
SAP Fiori 1.0 for SAP ERP ( 09 (01/2016) ) |
|
UIEAAP01 100 (0009 ) |
|
Back-End Components |
|
|
SAP_APPL 617 (0001 ) |
For more information about the installation of front-end components, see http://help.sap.com/fiori_implementation.
The app offers the possibility to upload documents. For security reasons, we strongly recommend that you install an appropriate virus scanner in your respective back-end system and define sufficiently restrictive scan profiles to prevent the upload of malicious content. For more information about virus scanning and scan profiles for SAP Fiori apps, see Virus Scanning.
On the back-end server, the following SAP notes must be implemented for this app:
|
SAP Note Number |
Description |
|---|---|
|
Release Information Note for SAP Fiori Apps for Material Requirements Planning |
On the front-end server, the following SAP notes must be implemented for this app:
|
SAP Note Number |
Description |
|---|---|
|
Release Information Note for SAP Fiori Apps for Material Requirements Planning |
The following sections list tasks that have to be performed to implement the required components of the app. The tables contain the app-specific data required for these tasks.
You can find the data required to perform these tasks in the SAP Fiori apps reference library at:
https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F0250Front-End Server : Activate OData Services
|
Component |
Technical Name |
|---|---|
|
OData Service (Version Number) |
PP_MRP_COCKPIT_SRV (001 ) |
For more information about how to activate the OData service, see Front-End Server: Activate OData Services .
Front-End Server: Activate SAP UI5 Application
|
Component |
Technical Name |
|---|---|
|
SAP UI5 Application |
PP_UNCOVSO_DT |
|
SAP UI5 Application for Reuse Library |
PP_MRP_REUSE |
For more information about how to activate the SAP UI5 application (ICF service), see Front-End Server: Activate ICF Services.
Enable App for Access in SAP Fiori Launchpad
To define the access of single users to this app in the SAP Fiori launchpad, technical content is delivered, such as catalogs and example roles.
You can find an overview of the delivered technical content for this SAP Fiori app in the SAP Fiori apps reference library.
For more information about how to procede with this content, see Enable App for Access in SAP Fiori Launchpad.
Front-End Server and Back-End Server: Assign OData Service Authorizations to Users
You must assign OData service authorizations for the app to your users.
Several authorization default values are connected to the OData service. To ensure that all these default values are assigned to a user, you have to follow the instructions given under the documentation links provided.
-
On the back-end server, a dedicated authorization role (PFCG role) for the OData service is delivered as an example. You can copy this role and adjust it to your needs.
-
On the front-end server , you must assign the OData service authorization to a new or existing role, such as a business role that has been adjusted according to your needs.
|
OData Service (Version Number) |
Back-End Server: Delivered Authorization Role (PFCG Role) |
Front-End Server : Assignment to Authorization Role |
|---|---|---|
|
PP_MRP_COCKPIT_SRV (001 ) |
In addition, this role contains authorizations to display the related business data.
Note
In addition, this role contains authorizations to display the related business data. |
OData service authorization must be assigned. |
Before implementing the app, you must ensure the following:
-
You have configured the Material Requirements Planning component in the back-end system. For more information, see Customizing for Production under 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 in the back-end system that are required for changing and creating requisitions or orders to the business users of the Manage External Requirements app.
You have made the necessary settings for the relevant application components in the back-end system so that the following back-end transactions can be accessed:
Stock/Requirements List (MD04)
Change Material Master (MM02)
Display Purchase Order (ME23N)
Display Purchase Requisition (ME53N)
Display Sales Order (VA03)
Display Production Order (CO03)
Display Process Order (COR3)
Display Planned Order (MD13)
You have installed and configured the following fact sheets:
You have assigned the authorizations in the back-end system that are required for using the linked transactions and the linked fact sheets to the business users of this app.
In transaction RFC Destinations (SM59), 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.
If you use a different name for the RFC connection, you have to change the system alias for the following entries in transaction Launchpad Customizing(LPD_CUST):
Role
Instance
Description
UIAPPP01
TRANSACTIONAL
Stock Requirements List
UIAPPP01
TRANSACTIONAL
Change Material
UIAPPP01
TRANSACTIONAL
Display Planned Order
UIAPPP01
TRANSACTIONAL
Display Process Order
UIAPPP01
TRANSACTIONAL
Display Production Order
UIAPPP01
TRANSACTIONAL
Display Sales Order
UIAPMM01
TRANSACTIONAL
Display Purchase Order
UIAPMM01
TRANSACTIONAL
Display Purchase Requisition
To be able to implement the app, you must perform the following configuration tasks in the back-end system:
To determine the contact person for solution cards and quickviews in the application, the system proceeds as follows:
First it checks if there is an entry for the contact person on the Partners tab page in the purchase order.
If not, it checks if there is an entry for the salesperson on the Communication tab page in the purchase order.
If not, it uses the contact person in the vendor master. If more than one contact person has been entered in the vendor master, the system checks the Customizing settings for Production under
Material Requirements Planning 
Apps for Material Requirements Planning General Settings Specify Contact Person Function 
so that it knows which contact person it should use. You must therefore have specified the contact person function that is relevant for the apps in this Customizing activity.
For more information about
app implementation, see http://help.sap.com/fiori_implementation
App Implementation Information for SAP Fiori .