App Implementation: Track Purchase Order

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 (Minimum Product Version Stack)	SAP ERP 6.0 SPS 15 or higher SAP enhancement package 2 of SAP ERP 6.0 SPS 5 or higher SAP enhancement package 3 of SAP ERP 6.0 SPS 5 or higher SAP enhancement package 4 of SAP ERP 6.0 SPS 5 or higher SAP enhancement package 5 of SAP ERP 6.0 SPS 3 or higher SAP enhancement package 6 of SAP ERP 6.0 SPS 1 or higher SAP enhancement package 7 of SAP ERP 6.0 SPS 2 or higher
Product Version Containing Back-End and Front-End Components of the App	SAP Fiori principal apps 1.0 for SAP ERP SPS 8

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 Server	Back-End/Front-End Component	Technical Name of Software Component	Support Package Level
Back-end server	Back-end component of app	SRA020 1.0	8
Front-end server	Front-end component	UIX01EAP 100	8

Required SAP Notes

For Track Purchase Order, the following SAP Notes must be implemented:

Back-End/Front-End Server	SAP Note Number	Description
Both	1940542	Central note for Track Purchase Order. 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 Track Purchase Order 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=F0403.

Front-End Server: Activate OData Services

Component	Technical Name
OData Service (Version Number)	sra020_po_tracking_srv (1)

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

Front-End Server: Activate SAP UI5 Application

Component	Technical Name
SAP UI5 Application	MM_PURORD_TPO

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

The SAP Fiori launchpad is the entry point to SAP Fiori apps. In the launchpad, the user can see and access those Fiori apps that have been assigned by an administrator to the catalog designed for this user's role.

The administrator makes these assignments in the launchpad designer. For more information, see Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad.

SAP delivers technical catalogs for groups of SAP Fiori apps as repositories to create your own catalogs in the launchpad designer. Along with these catalogs, more technical content is delivered for each SAP Fiori app. You can find the delivered technical content for each SAP Fiori app in the SAP Fiori apps reference library.

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.

Caution 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 Add Start Authorizations for OData Services to Role on Front-End and Front-End Server: Assign Roles to Users.

OData Service (Version Number)	Back-End Server: Delivered Authorization Role (PFCG Role)	Front-End Server: Assignment to Authorization Role
sra020_po_tracking_srv (1)	OData service authorization is included in the example role SAP_MM_PURORD_TPO_APP. Note In addition, this role contains authorizations to display the related business data. End of the note.	OData service authorization must be assigned.

Prerequisites for Implementation

Before implementing the Track Purchase Order app, you must ensure that the business users who will use the app have the authorizations required for tracking purchase orders in the SAP GUI.

More Information

For general information about the user management concept in a SAP Fiori environment, see Users in ABAP Front-End System and Users in ABAP Back-End System.