App Implementation: Approve Purchase ContractsBefore 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 |
|---|---|
Configuration of Front-End Server | |
Back-End Product Versions Supporting the App (Minimum Product Version Stack) |
|
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 |
| 8 |
Front-end server | Front-end component |
| 8 |
For the Approve Purchase Contracts
app, the following SAP Notes must be implemented:
Back-End/Front-End Server | SAP Note Number | Description |
|---|---|---|
Both | Central note for |
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=F0400
.
Component | Technical Name |
|---|---|
OData Service (Version Number) |
|
For more information about activating OData services, see Front-End Server: Activate OData Services.
Component | Technical Name |
|---|---|
| SAP UI5 Application |
|
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).
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.
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.
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 |
|---|---|---|
| OData service authorization is included in the example role
In addition, this role contains authorizations to display the related business data. End of the note. | OData service authorization must be assigned. |
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 .
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:
Specify the workflow tasks that are relevant for approving purchase contracts. You do this in Customizing for Materials Management
under . For more information, see the documentation available in Customizing.
Users of the Approve Purchase Contracts
app can create the following notes:
Approval notes
Forwarding notes
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.
Approval Notes
If text type "K18
" does not yet exist, you must create it in Customizing for Materials Management under . 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
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.
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.