SAP Fiori principal apps for SAP ERP 1.0 SPS00 (Delivery Date 01/2014) (2022)

Initial delivery.

1.7.2 App Implementation: Approve Requisitions

PUBLIC Page 34 of 138

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 SP15 or higher

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-End Components of the App

SAP Fiori principal apps for SAP ERP 1.0 SPS03

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 GBAPP 002 600 06

Front-end server Front-end component UIX01EAP 100 03

Required SAP Notes

For Approve Requisitions , the following SAP Notes must be available:

Back-End/Front-End Server SAP Note Number Description

Both 1937868 Central note for Approve Requisitions . 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 Requisitions 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_prapproval (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_PR_APV

For more information about how to activate the UI5 application (ICF service), see Front-End Server: Activate ICF Services of UI5 Application.

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 Purchase Requisition

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 and Back-End Server: Assign Role with OData Service Authorization to Users

To grant access to OData services to specific users, 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 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 Number) Back-End Server: Delivered Authorization Role (PFCG Role)

Front-End Server: Authorization Role

gbapp_prapproval (1) SAP_MM_PR_APV_APP Use an existing role or create a new one

For more information about authorization roles and assigned OData services, see Front-End Server: Assign Role with OData Service Authorization t and Back-End Server: Assign Role with OData Service Authorization to.

Configuration Tasks

To enable the Approve Requisitions 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 Requisition Release Procedure Procedure with Classification .

You have configured the approval workflow for approving purchase requisitions.

When customizing the release strategy, you have indicated whether or not you want to enable overall approval of purchase requisitions or whether you only want to enable approval of requisition items.To enable overall approval, you must enable overall release for the affected document type. You do this in Customizing for Materials Management under Purchasing Purchase Requisition Define Document Types by selecting the OvRel checkbox for the document type, for example for document type NB .

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 requisitions. You do this in Customizing for Materials Management under Purchasing Purchase Requisition Approve Requisitions App Specify Workflow Task IDs for Approve Requisitions App . Note the following:

To enable overall approval of purchase requisitions, specify the workflow task ID that corresponds to overall release of object type BUS2105.

To enable approval of purchase requisition items, specify the workflow task ID that corresponds to the release of object type BUS2009.

For more information, see the documentation available in Customizing.

Storage of Notes

Users of the Approve Requisitions 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 Requisitions app are stored at item level of the purchase requisition. The program logic assumes that text type "B08" can be used for storing the note in the database.

Forwarding Notes

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

Required Activities

Approval and Rejection Notes

If text type "B08" does not yet exist, you must create it in Customizing for Materials Management under Purchasing Purchase Requisition Texts for Purchase Requisitions Define Text Types . You have to enter the Sequential Number "08".

If your company already uses text type "B08" for a different purpose, you can use the BAdI Extend Runtime of Gateway Service for Approve Requisitions App (GBAPP_APV_PR_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 Requisition Approve Requisitions App BAdI: Change Data of Approve Requisitions App . Forwarding Notes

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

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.

PUBLIC Page 36 of 138

1.7.3 App Extensibility: Approve Requisitions

You can extend the Approve Requisitions app for different aspects. For this purpose, the following extensibility options are available:

Add fields to master list

You can add your own fields to each item in the master list.

Add fields to the purchase requisition item overview (if you use the overall approval of purchase requisitions)

You can add your own Fields to the purchase requisition item overview; this screen is available if you use the overall approval of purchase requisitions.

Add fields to the purchase requisition item details view (if you use overall approval) Add fields to the purchase requisition item details view (if you use item-based approval) Add fields to the service line details view

Add fields to the service limit details view

Add Fields to Master List

To add customer fields to each item in the master list, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs:

UI Back End/ABAP

View Extension Point Design Time: Name of Entity

Set

Add Fields to Item Overview

To add customer fields to the header area and to the Information area of the purchase requisition item overview, the following extensibility entities are available on the different software layers. You have to extend each of these entities according to your specific business needs:

UI Back End/ABAP

View Extension Point Design Time: Name of Entity

Set

FAQs

What are the 3 types of SAP Fiori apps? ›

SAP Fiori has three app types, each distinguished by their focus and infrastructure requirements: Transactional apps. Fact sheets. Analytical apps.

On which SAP back end product can you install SAP Fiori principal apps? ›

The apps can be implemented based on one of the following SAP products in the back-end system: 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.

Where can I find SAP Fiori apps? ›

How to Find all the SAP Fiori Catalogs that are created for a Particular Transaction Code in SAP S/4 HANA?
  1. Go to SE16–>SUI_TM_MM_APP.
  2. Select APP_TYPE as T and Provide TCODE for which you are searching FIORI Catalogs for. In this case it is ME22N.. Execute.
  3. Below is the List.
Jul 9, 2020

What is the latest version of SAP Fiori? ›

Fiori 3 is the latest version, released in 2018.

What does the SAP Fiori Rule 1 1 3 mean? ›

SAP advocate a design principle known as 1-1-3 (“one one three”). This means each screen should be designed with a single user (or role) in mind, a single task that this user wants to accomplish, and a maximum of three levels of navigation to perform this task.

How many SAP Fiori apps are there? ›

SAP Fiori provides 300+ role-based applications like HR, Manufacturing, finance, etc.

What is SAP Fiori used for? ›

What is SAP Fiori? SAP Fiori is the user interface or user experience (UX) that supplements and can replace the SAP GUI. This streamlined application uses tiles to encapsulate standard tasks, such as approving purchase requisitions, viewing sales orders, and approving timesheets.

How can I access Fiori app from SAP GUI? ›

If you're in your normal SAP GUI screen, you can navigate directly to your Fiori launchpad (if you have it activated) in SAP S/4HANA by using transaction n/ui2/flp – note that the “/n” at the start of the transaction is essential.

How do I know if my Fiori app is activated? ›

Use the Task Manager transaction for SAP Fiori content activation task list run to activate all required Fiori apps based on select SAP Fiori Business roles and their artifacts like OData services, SICF nodes, business roles and it will even create a test user for us.

Why is SAP called Fiori? ›

SAP Fiori gets its name from the Italian word for flower. We know that flowers are nice to look at, are shaped with nature's intelligent design, and are delightful to behold.

How do I know my Fiori version? ›

Find the SAP Fiori Client version within the Fiori client
  1. Open SAP Fiori Client.
  2. Double tap on the toolbar of the Fiori client application.
  3. A menu bar get open in the bottom of screen now scroll it to left you will see a settings button.
  4. Now scroll down for settings and you will see the version.

What version of Fiori does SAP s4 Hana 1809 use? ›

2667191– SAP FIORI FOR SAP S/4HANA 1809: Release Information Note. 2482461– SAP FIORI FOR SAP S/4HANA 1709: Release Information Note.

What are SAP Fiori apps? ›

What is SAP Fiori? SAP Fiori is a design system that enables you to create business apps with a consumer-grade user experience, turning casual users into SAP experts with simple screens that run on any device.

What is the difference between Fiori and UI5? ›

The difference is that Fiori is a design concept, and SAPUI5 is a library framework. You can still build custom UI5 Apps that do not adhere to the SAP Fiori design guielines, but they are called custom UI5 Apps.

What are the main principles of SAP Fiori? ›

The design philosophy of SAP Fiori is based on five core principles. SAP Fiori user experience is role-based, adaptive, simple, coherent, and delightful.

You might also like

Latest Posts

Article information

Author: Dan Stracke

Last Updated: 07/25/2022

Views: 6311

Rating: 4.2 / 5 (63 voted)

Reviews: 94% of readers found this page helpful

Author information

Name: Dan Stracke

Birthday: 1992-08-25

Address: 2253 Brown Springs, East Alla, OH 38634-0309

Phone: +398735162064

Job: Investor Government Associate

Hobby: Shopping, LARPing, Scrapbooking, Surfing, Slacklining, Dance, Glassblowing

Introduction: My name is Dan Stracke, I am a homely, gleaming, glamorous, inquisitive, homely, gorgeous, light person who loves writing and wants to share my knowledge and understanding with you.