Show TOC

App Implementation: Report Quality IssueLocate this document in the navigation structure

Implementation information for SAP Fiori app.

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:

Database SAP Fiori System Landscape Setup Prerequisites

ABAP environment

Setup of SAP Fiori System Landscape for SAP Business Suite with ABAP Environment

Installation Requirements (Transactional Apps)

HANA database

Setup of SAP Fiori System Landscape for SAP Business Suite with SAP HANA Database

Installation Requirements (Fact Sheets)

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

UIEAAP01 100 (0009 )

Back-End Components

SAP enhancement package 7 for SAP ERP 6.0 (11 (01/2016))

Central Applications

EA-APPL 617 (0011 )

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

1931282 Information published on SAP site

General Information: QM

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

SAP Note Number

Description

1931282 Information published on SAP site

General Information: QM

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

Front-End Server : Activate OData Services

Component

Technical Name

OData Service (Version Number)

QM_NOTIF_SRV (0001 )

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

 UI_QM_CREATE

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

QM_NOTIF_SRV (0001 )

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

  • SAP_QM_REPORTQUALITYISSUE_APP

Note

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

OData service authorization must be assigned.
Configuration Tasks

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

The configuration of the Report Quality Issue app is controlled by Customizing activities that are available under Start of the navigation path Quality Management Next navigation step Fiori Apps for Quality Management End of the navigation path. By default, the Customizing activities are delivered with predefined settings. However, you can check the settings in client 000 and adapt them as appropriate for your business case.

To enable Report Quality Issue, you must perform the following configuration tasks:

  • Configure the Assigned To field as optional.

    1. Start Customizing and open the activity: Start of the navigation path Quality Management Next navigation step Quality Notifications Next navigation step Notification Creation Next navigation step Partners Next navigation step Define Partner Determination Procedures Next navigation step Define Partner Determination Procedure End of the navigation path.

    2. Select the Quality Management radio button and choose Change Partner.

    3. Select the Q3 Internal ProbMessage partner determination procedure and then choose Functions in Determination Procedure.

    4. For the Coordinator (user) entry, deselect the check box in the Partner Mandatory column.

    If you do not perform the configuration above, the Assigned To field remains mandatory and you cannot report a quality issue without filling it out. However, technically this field is not required for the reporting of a quality issue and therefore it is not available during the initial quality issue reporting.

  • Assign a user as the person responsible.

    Before you use Personnel number (PE) as the partner type, make sure you have maintained HR master data. To maintain HR master data, proceed as follows:

    1. Call up transaction PA30 (Maintain HR Master Data).

    2. Enter your personnel number. In the Direct selection group box, specify the following:

      • Infotype: Commnication

      • Subtype: 0001(System user name)

    3. Choose Create.

    4. Specify your start and end date and the System ID – username to access Fiori app.

    5. Save your changes.

    To enable this function, proceed as follows:

    1. Go to Customizing Overview of Notification Type under Start of the navigation path Quality Management Next navigation step Quality Notifications End of the navigation path.

    2. Choose a notification type and double-click the Partner Functions, Approval folder in the Dialog Structure.

    3. In the Person responsible field, choose a partner function, and save your changes.

    4. Go to Customizing Define Partner Determination Procedures under Start of the navigation path Quality Management Next navigation step Quality Notifications Next navigation step Notification Creation Next navigation step Partners End of the navigation path.

    5. Choose the partner function you have assigned as the person responsible, and specify the corresponding partner type.

    Note that we only support two partner types: Personnel number (PE) and User name (US).

  • Enable the attachment of images in quality issues.

    1. Start Customizing and open the activity: Start of the navigation path Cross-Application Components Next navigation step Document Management Next navigation step Control Data Next navigation step Define Document Types End of the navigation path.

    2. Choose the DOC document type and make sure that the following radio buttons are selected:

      • Revision Level Assignment

      • Version Assignment

      • Archiving Authorization

      • Make sure that the Default Application field is set to JPG.

    3. Open the Define object links folder and make sure that a link to the object QMQEL exists.

Note

The settings that you make at application level are stored in the cache of your Web browser. For this reason, if you want to discard these settings and revert to the default settings that come from Customizing, you should delete your browsing history and clear the cache of your Web browser.

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.