Show TOC

 App Implementation: Approve Purchase Contracts

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:

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

SRA001 1.0

8

Front-end server

Front-end component

UIX01EAP 100

8

Required SAP Notes

For the Approve Purchase Contracts app, the following SAP Notes must be implemented:

Back-End/Front-End Server

SAP Note Number

Description

Both

1937863Information published on SAP site

Central note for Approve Purchase Contracts. 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 Contracts 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=F0400Information published on SAP site.

Front-End Server: Activate OData Services

Component

Technical Name

OData Service (Version Number)

sra001_pcapproval (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_PC_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

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:

OData Service (Version Number)

Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Assignment to Authorization Role

sra001_pcapproval (1)

OData service authorization is included in the example role SAP_MM_PC_APV_APP.

Note Note

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

End of the note.

OData service authorization must be assigned.

Configuration Tasks

If you want to use the Approve Purchase Contracts 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 Contract Next navigation step Release Procedure for Contracts End of the navigation path.

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

  • 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 contracts. You do this in Customizing for Materials Management under Start of the navigation path Purchasing Next navigation step Contract Next navigation step Approve Purchase Contracts App Next navigation step Specify Workflow Task IDs for Approve Purchase Contracts App End of the navigation path. For more information, see the documentation available in Customizing.

Storage of Notes

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

  • Approval notes

  • Forwarding notes

System Behavior
  • Approval Notes

    Approval notes created in the Approve Purchase Contracts app are stored at header level of the purchase contract. The program logic assumes that text type "K18" can be used for storing the note in the database.

  • Forwarding Notes

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

Required Activities
  • Approval Notes

    If text type "K18" does not yet exist, you must create it in Customizing for Materials Management under Start of the navigation path Purchasing Next navigation step Contract Next navigation step Texts for Contracts 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 "K18" for a different purpose, you can use the BAdI Extend Runtime of Gateway Service for Approve Contracts App (SRA001_APC_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 Contract Next navigation step Approve Purchase Contracts App Next navigation step BAdI: Change Data of Approve Purchase Contracts 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 contract.

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.