App Implementation: Approve Requests

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)

n/a (n/a)

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 for request approvals 1.0 ( 05 (04/2015) )	Approve Requests UI NW731 Approve Requests UI NW740 Approve Requests INT Approve Requests INT NW740	UIX01CA1 100 (0005 )
Back-End Components	n/a (n/a)	n/a	IW_PGW 100 (0005 )

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
1931160	Release Information Note for SAP Fiori Approve Requests

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

SAP Note Number	Description
1931160 2103156	Release Information Note for SAP Fiori Approve Requests Launching Fiori apps in standalone mode

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

Front-End Server : Activate OData Services

Component	Technical Name
OData Service (Version Number)	/IWPGW/TASKPROCESSING (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	CA_ALL_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
/IWPGW/TASKPROCESSING (001 )	In addition, this role contains authorizations to display the related business data. n/a Note In addition, this role contains authorizations to display the related business data.	OData service authorization must be assigned.

OData Service (Version Number)

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

Front-End Server : Assignment to Authorization Role

/IWPGW/TASKPROCESSING (001 )

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

n/a

Note

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

OData service authorization must be assigned.

Prerequisites for Implementation

Before implementing the app, you must ensure the following:

Make sure that you have at least one business workflow in the back-end system(s) that defines the task types to be used for Approve Requests. Ensure that all the authorizations required for the workflows are maintained.
Make sure that the required SAP Notes are implemented.
Configure the connections between the Gateway system and your back-end system(s) from which you want to retrieve the work items.

For more information, see SAP Help Portal at http://help.sap.com Technology SAP Gateway SAP NetWeaver Gateway 2.0 Configuration and Deployment Information Configuration Guide SAP NetWeaver Gateway Configuration Guide OData Channel Configuration Connection Settings on the SAP NetWeaver Gateway Hub System Connection Settings: SAP NetWeaver Gateway to SAP Systems .
Activate the Task Gateway Service in Customizing for SAP NetWeaver under Gateway OData Channel Administration General Settings Activate and Maintain Services .

For more information, see section To activate the service at http://help.sap.com Technology SAP Gateway SAP NetWeaver Gateway 2.0 Configuration and Deployment Information Configuration Guide SAP NetWeaver Gateway Configuration Guide Configuration Settings for SAP NetWeaver Gateway Supported Scena Configuration Settings for OData Channel Scenarios Configuring the Task Gateway Service .
Assign the software version to the service in Customizing for SAP NetWeaver under Gateway OData Channel Administration General Settings Assign Data Provider to Data Model activity .

For more information, see section To assign the software version to the service at http://help.sap.com Technology SAP Gateway SAP NetWeaver Gateway 2.0 Configuration and Deployment Information Configuration Guide SAP NetWeaver Gateway Configuration Guide Configuration Settings for SAP NetWeaver Gateway Supported Scena Configuration Settings for OData Channel Scenarios Configuring the Task Gateway Service .
If you run on SAP NetWeaver lower than 7.4, assign the back-end system aliases for the Task Processing Service (/IWPGW/TASKPROCESSING) in Customizing for SAP NetWeaver under Gateway  OData Channel Development with IW_BEP  Registration  Assign SAP System Aliases to OData Service .

If you run on SAP NetWeaver 7.4, define system aliases for the Task Processing Service in Customizing for SAP NetWeaver under Gateway  OData Channel  Administration  General Settings  Assign SAP System Aliases to OData Service .

For more information, see SAP Help Portal at http://help.sap.com Technology  SAP Gateway  SAP NetWeaver Gateway 2.0  Development Information  Developers Guide  SAP NetWeaver Gateway Developer Guide  OData Channel  Basic Features  Service Life-Cycle  Activate and Maintain Services .

Configuration Tasks

To be able to implement the app, you must perform the following configuration tasks in the back-end system:

Configuring a Task and Decisions

Enter and define a task and those decision options from your workflow task that you want to display in the Approve Requests application.

Note

This section is only relevant if you are implementing the Approve Requests application for your SAP Business Workflow.

Follow the steps below in the back-end system where you maintain your workflow template.

In Customizing for SAP NetWeaver, choose Gateway Service Enablement Content Workflow Settings Maintain Task Names and Decision Options .
Fill in the Step Name table as described below and save your entries:
- Workflow ID: Enter the ID of your workflow template.
- Step ID: Enter the task step from your workflow template.
- Icon MIME Repository Path: Leave this field blank.
- Step Description: Enter the task name.
Select the entry in the Step Name table and choose Decision Keys in the navigation panel.
Add and define your decision options in the Decision Keys table as described below and save your entries:
- Key: Enter the decision key.
  
  Decision keys are numeric and sequential and correspond to the position of decision options in the Workflow Builder. Enter the first decision option with key 1, the second decision option with key 2, and so on.
- Icon Mime Repository Path: Leave this field blank.
- Decision Text: Define the label of the decision option.
  
  This name is displayed on the application screen as a button label. The proposed length of the decision text is maximum 14 characters. Decision texts longer than 14 characters will not fit to the device screen.
- Comment On: If you want to make it mandatory for the user to add a comment when executing a decision, select this checkbox.
- Nature: Here you have the following options:
  - Select POSITIVE for the approve type decision option.
    
    The decision option is displayed either as a green pushbutton or in a gray popover (depending on the space available) on the detail screen of the application.
  - Select NEGATIVE for the reject type decision option.
    
    The decision option is displayed either as a red pushbutton or in a gray popover (depending on the space available) on the detail screen of the application.
  - Leave the field empty for multiple decision options.
    
    The decision options are displayed either as gray pushbuttons or in a gray popover (depending on the space available) on the detail screen of the application.

Note

If the step type for the workflow task is not User Decision, implement BAdI /IWWRK/BADI_WF_BEFORE_UPD_IB.

Defining the Workflow Scenario

Define your workflow scenario by completing the following steps in your Gateway system: add a scenario, assign the consumer type, assign roles, and define tasks.

Add a workflow scenario.
1. In Customizing for SAP NetWeaver, choose Gateway Service Enablement Content Task Gateway Service Scenario Definition .
2. Choose New Entries.
3. Fill in the Scenario Decision table as described below and save your entries:
  - Scenario Identifier: Define a scenario ID.
  - Scenario Display Name: Define a name for your scenario.
  - Scenario Order: Not relevant for Approve Requests.
  - Technical Service Name: Enter /IWPGW/TASKPROCESSING.
  - Version: Enter 1.
  - EntitySet External Name: Enter Task.
  - Property External Name: Enter TaskDefinitionID.
  - Default Sort by Property: Define how you want to sort the work items on the list screen of the application. If you do not set this parameter, the default value is CreatedOn.
    
    Note
    You can use all the properties of the task collection here.
    
    To display a list of all the possible properties, see SAP Help Portal at http://help.sap.com Technology SAP Gateway SAP NetWeaver Gateway 2.0 Content Information Content Guide SAP NetWeaver Gateway Content Guide SAP NetWeaver Gateway Supported OData Channel Scenarios Task Gateway Task Gateway Administrator Task Gateway Service Task Gateway Service Version 1 Task Collection .
    
    The property you have selected is added to the list of possible sorting properties on the detail screen of the application.
    
    Note
    You can also define the sorting principles on the UI of the application. You can choose from a list of properties.
  - Mass Action: Not relevant for Approve Requests.
  - Class for Scenario Count: Leave it empty
    
    Note
    If the scenario is not part of the Business Workflow engine, and you want to see the number of tasks pending for this scenario, enter the name of the class that implements the /IWWRK/IF_TGW_SCENARIO interface in the back-end system.
  - Quick Act.: Select the Quick Act. checkbox to enable quick approval of workflow items by swiping on the screen.
    
    This field is only relevant if you use a touch screen device.
Assign the consumer type to the scenario.
1. Select the row containing your approval scenario and choose table Assign Consumer Type to Scenario in the navigation panel.
2. Choose New Entries.
3. In the Task Gateway Consumer Type field, select TABLET.
4. Save your entries.
Assign a role to the consumer type and the scenario (optional).

Now you can assign an approval scenario to a number of roles, that is, the scenario will only be available to users who are assigned to at least one of the relevant PFCG roles.
1. Select the row for TABLET (for all devices), and choose Assign Role to Consumer Type and Scenario in the navigation panel.
2. Choose New Entries.
3. In the Role column, select the role you want to use.
4. Save your entries.
Define tasks for your scenario.

Note
You can define several tasks for your scenario. Make sure that you follow the steps below for each task.
1. Choose Scenario Definition in the navigation panel, and select the row containing your approval scenario.
2. Choose Task Definition for Scenario in the navigation panel.
3. Choose New Entries.
4. Enter the task type ID for your approval workflow.
  Note
  You can find your task type ID in the back-end system as described below:
  1. Start the Workflow Builder.
  2. Search for the workflow definition you would like to enable.
  3. Open the approval step.
  4. Go to Control tab, and check the Task field.
5. In the SAP System Alias field, enter the source system alias for the task type.
  
  Note
  Make sure that the Task Gateway Service is connected to the selected system aliases.
6. Save your entries.

Configuring the SAP Fiori Launchpad

To enable Approve Requests, create a tile for each workflow scenario as described below.

Note

Make sure that role SAP_FND_TCR_T_X1 is assigned to your user.

Start the launchpad designer in your NetWeaver Gateway system with the following URL: http://<server>:<port>/sap/bc/ui5_ui5/sap/ARSRVC_UPB_ADMN/main.html.
Select the SAP FND Transactional Applications (SAP_FND_TC_T_X1) catalog.
Add a new tile.
Choose the App Launcher - Dynamic tile.
Select the newly created tile, and fill in the following fields as described below:
- Title: Enter the name of your workflow scenario, for example, Capital Expenditure Approval.
- Icon: Use any of the available icons.
- Service URL: Enter /sap/opu/odata/IWPGW/TASKPROCESSING;mo/ScenarioCollection?$filter=key eq '<your scenario identifier>'.
- Semantic Object: Enter WorkflowTask.
- Action: Enter approveRequests.
- Parameters: Enter scenarioId=<your scenario identifier>.
Choose Save.

For more information, see .

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 .