Show TOC

App Implementation: Manage Change RequestsLocate this document in the navigation structure

System Landscape 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:

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)

  • SAP enhancement package 8 for SAP ERP 6.0 (01 (01/2016))
  • SAP enhancement package 7 for SAP ERP 6.0 (11 (01/2016))
Each SAP Fiori app consists of front-end components and back-end components:
  • 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.

The front-end and back-end components of the app are delivered with the following SAP product versions as part of the listed software components. The required software components for the app are contained in the listed product instances:

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) )
  • UI for Central App NW740
  • UI for Central App NW731
  • UI for Central App UI 2.0

UIEAAP01 100 (0009 )

Back-End Components

  • SAP enhancement package 8 for SAP ERP 6.0 (01 (01/2016))
  • SAP enhancement package 7 for SAP ERP 6.0 (11 (01/2016))
  • Central Applications
  • Master Data Governance

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.

Required SAP Notes

On the back-end server, the following SAP notes must be implemented for this app:

SAP Note Number

Description

1955289 Information published on SAP site

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

1955289 Information published on SAP site

Release Information Note for SAP Fiori Apps for Material Requirements Planning

Implementation Tasks

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=F0670

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

Note

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.

Make the assignment on the back-end server and on the front-end server :
  • 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.

  • SAP_PP_CHANGEREQ_DT_APP

Note

In addition, this role contains authorizations to display the related business data.

OData service authorization must be assigned.

Prerequisites for Implementation

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.

  • Change requests are created when working with the MRP apps for managing material coverage and uncovered requirements. You have therefore installed and configured at least one combination of apps for monitoring and managing material coverage, external requirements, or internal requirements, depending on your business needs.

    For more information about implementing these apps, see the following app-specific implementation documentation:

  • 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 Change Requests 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:

    • 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

    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

Configuration Tasks

To be able to implement the app, you must perform the following configuration tasks in the back-end system:

  • You have ensured that your local e-mail client allows UTF-8 support for the mailto: protocol.

For composing a standard email in the Manage Change Request app, the following texts are provided:

  • PP_MRP_CR_EMAIL_SUBJECT (subject)

  • PP_MRP_CR_EMAIL_BODY1 (salutation and first part of body)

  • PP_MRP_CR_EMAIL_TABITEM (purchase order item)

  • PP_MRP_CR_EMAIL_TABSCH (schedule line)

  • PP_MRP_CR_EMAIL_TABSCH_MULTI (schedule lines)

  • PP_MRP_CR_EMAIL_BODY2 (second part of body, complimentary close, and sender’s name)

Note

The application can only send the prepared email to your email client if the text is not longer than the maximum length permitted by your browser for the mailto URL.

If you want to change the standard email texts, start transaction SE61 (Documentation) in your ABAP back-end system, copy the relevant dialog text to transaction SO10 (Standard Texts), and make your changes. You can also create your own texts directly in transaction SO10.

The standard email texts are available in all 16 SAP Fiori languages. The system determines which language to use for the email as follows:

  1. The system chooses the language that has been entered for the contact person in the vendor master. The system determines the contact person according to the logic described in the App Implementation documentation for the managing apps. For example, see App Implementation: Manage Material Coverage under Configuration Tasks.

  2. If there is no language entry in the vendor master for the contact person, the system uses the logon language.

  3. If you have created your own email texts and they are not available in the language entered for the contact person, the system uses the logon language, if available, or English.

More Information

For more information about app implementation, see http://help.sap.com/fiori_implementation Start of the navigation path App Implementation Information for SAP Fiori End of the navigation path.