App Implementation: Approve

Purchase Orders
System Landscape Requirements
Before you start to implement the app, ensure that your system landscape has been set up to enable
SAP Fiori. This also implies that the front-end and back-end components for your app are already
available in this system landscape:
SAP Fiori System Landscape Options

Setup of SAP Fiori System Landscape with ABAP

Environment
Based on SAP enhancement package 7 of SAP ERP
6.0 also possible:

Setup of SAP Fiori System Landscape with

SAP HANA Database

Setup of SAP Fiori System Landscape with

SAP HANA XS

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions Supporting the App

SAP ERP 6.0 SP15 or higher

(Minimum Product Version Stack)

SAP enhancement package 2 of SAP ERP

6.0 SPS05 or higher

SAP enhancement package 3 of SAP ERP

6.0 SPS05 or higher

SAP enhancement package 4 of SAP ERP

6.0 SPS05 or higher

SAP enhancement package 5 of SAP ERP

6.0 SPS03 or higher

SAP enhancement package 6 of SAP ERP

6.0 SPS01 or higher

SAP enhancement package 7 of SAP ERP

6.0 SPS02 or higher

Product Version Containing Back-End and Front-

SAP Fiori principal apps for SAP ERP 1.0 SPS04

End Components of the App

For more information on the installation of the back-end and front-end components of the app, see
Installation of Back-End Components and Installation of Front-End Components.
For the app, the following software components must be available in your system landscape. These
components are contained in the product SAP Fiori principal apps for SAP ERP:
Back-End/Front-End

Back-End/Front-End

Technical Name of Software

Support Package

Server

Component

Component

Level

Back-end server

Back-end component

GBAPP 002 600

07

Front-end server

Front-end component

UIX01EAP 100

04

Required SAP Notes

For the Approve Purchase Orders app, the following SAP Notes must be implemented:
Back-End/Front-End SAP Note
Server

Number

Both

1937715

Description

Central note for Approve Purchase Orders. All other important notes for
this app are referenced from the central note.

Implementation Tasks
The following sections list tasks that have to be performed to implement the Approve Purchase
Orders app. The tables contain the app-specific data required for these tasks:
Front-End Server: Activate OData Services
Component

Technical Name

OData Service (Version Number)

gbapp_poapproval (1)

For more information about activating OData services, see Front-End Server: Activate OData
Services.
Front-End Server: Activate UI5 Application
Component

Technical Name

UI5 Application

MM_PO_APV

For more information about how to activate the ICF service, see Front-End Server: Activate ICF
Services of SAPUI5 Application (for transactional apps) or Activate ICF Service of BSP
Application (fact sheets).
Front-End Server: Enable App for Access in SAP Fiori Launchpad
There are several steps to be performed to enable the app for access in the SAP Fiori launchpad. You
require the listed data to perform these steps.
For more information about the steps to be performed, see Setup of Catalogs, Groups, and Roles
in the SAP Fiori Launchpad.
Component

Technical Name

Semantic Object

PurchaseOrder

Business Role

SAP_MM_BCR_Buyer_X1

Business Catalog

SAP_MM_BC_Buyer_X1

Business Catalog Group

SAP_MM_BCG_Buyer_X1

Technical Role

SAP_MM_TCR_T_X1

Technical Catalog

SAP_MM_TC_T_X1

LPD_CUST Role

UIX01MM

LPD_CUST Instance

TRANSACTIONAL

Front-End Server and Back-End Server: Assign Roles with OData Service Authorization to
Users
To grant specific users access to OData services, you have to assign roles (including OData service
authorization for the app) to your users. You have to 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 adjust this role according to your needs.
On the front-end server, you can 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

Back-End Server: Delivered

Number)

Authorization Role (PFCG

Front-End Server: Authorization Role

Role)

gbapp_poapproval

SAP_MM_PO_APV_APP

You can assign the OData service authorization to

a business role, for example the delivered

(1)

business role SAP_MM_BCR_Buyer_X1.

You must assign OData service authorizations for the app to your users.
Caution
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.
End of the caution.
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. For more
information, see Back-End Server: Assign OData Service Authorization to Users.
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. For more
information, see Front-End Server: Assign OData Service Authorization to Users.

Configuration Tasks
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

Purchasing Purchase Order

Release Procedure for Purchase Orders .

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

Purchasing Purchase Order Approve Purchase Orders App

Specify Workflow Task IDs for Approve Purchase Orders App . 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

Purchasing Purchase Order Texts for Purchase Orders Define

Text Types for Header Texts . 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

Purchasing

Purchase Order Approve Purchase Orders App BAdI: Change Data of Approve Purchase
Orders App .
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.