Show TOC

App Implementation: Approve Purchase OrdersLocate 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:

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)
  • EHP2 FOR SAP ERP 6.0 - SPS 05 (02/2009)
  • EHP3 FOR SAP ERP 6.0 - SPS 05 (08/2009)
  • EHP4 FOR SAP ERP 6.0 - SPS 05 (11/2009)
  • EHP4 FOR SAP ERP 6.0 / NW7.01 - SPS 05 (11/2009)
  • EHP5 FOR SAP ERP 6.0 - SPS 03 (12/2010)
  • EHP6 FOR SAP ERP 6.0 - SPS 01 (11/2011)
  • SAP ERP 6.0 - SPS 15 (02/2009)
  • EHP7 FOR SAP ERP 6.0 - SPS 01 (08/2013)
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 principal apps 1.0 for SAP ERP ( 08 (10/2015) )
  • Central App UI NW731
  • Central App UI NW740

UIX01EAP 100 (0008 )

Back-End Components

SAP Fiori principal apps 1.0 for SAP ERP (08 (10/2015))

  • Central App INT
  • Central App INT NW740

GBAPP002 600 (0010 )

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

1937715 Information published on SAP site

Installation Information for Approve Purchase Orders (MM)

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

SAP Note Number

Description

1937715 Information published on SAP site

Installation Information for Approve Purchase Orders (MM)

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

Front-End Server : Activate OData Services

Component

Technical Name

OData Service (Version Number)

GBAPP_POAPPROVAL (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

 MM_PO_APV

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

GBAPP_POAPPROVAL (001 )

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

  • SAP_MM_PO_APV_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:

To enable the Approve Purchase Orders app, the following prerequisites must be met in Customizing:

  • You use the release strategy in Purchasing (MM-PUR). You have made the corresponding settings in Customizing for Materials Management under Start of the navigation path Purchasing Next navigation step Purchase Order Next navigation step Release Procedure for Purchase Orders End of the navigation path.

  • You have configured the approval workflow for approving purchase orders.

  • To create work items which can be approved using the app, you have set up a connection between the release strategy and SAP Business Workflow.

In addition, you must perform the following configuration tasks:

Workflow

Specify the workflow tasks that are relevant for approving purchase orders. You do this in Customizing for Materials Management under Start of the navigation path Purchasing Next navigation step Purchase Order Next navigation step Approve Purchase Orders App Next navigation step Specify Workflow Task IDs for Approve Purchase Orders App End of the navigation path. For more information, see the documentation available in Customizing.

Storage of Notes

Users of the Approve Purchase Orders app can create the following notes:

  • Approval and rejection notes

  • Forwarding notes

System Behavior

  • Approval and Rejection Notes

    Approval and rejection notes created in the Approve Purchase Orders app are stored at header level of the purchase order. The program logic assumes that text type "F18" can be used for storing the note in the database.

  • Forwarding Notes

    Forwarding notes created in the Approve Purchase Orders app are stored with the work item of SAP Business Workflow.

Required Activities

  • Approval and Rejection Notes

    If text type "F18" does not yet exist, you must create it in Customizing for Materials Management under Start of the navigation path Purchasing  Next navigation step Purchase Order Next navigation step  Texts for Purchase Orders Next navigation step  Define Text Types for Header Texts End of the navigation path. You have to enter the Sequential Number "18".

    If your company already uses text type "F18" for a different purpose, you can use the BAdI Extend Runtime of Gateway Service for Approve Purchase Orders App (GBAPP_APV_PO_RDP), method SET_ATTRIBUTES, to use a different text type to store the notes. This BAdI is available in Customizing for Materials Management under Start of the navigation path Purchasing  Next navigation step Purchase Order Next navigation step  Approve Purchase Orders App Next navigation step  BAdI: Change Data of Approve Purchase Orders App End of the navigation path.

  • Forwarding Notes

    You do not need to create a text type. The note is saved with the workflow work item, not with the purchase order.

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.