App Implementation: Mark-to-Market Valuation
System Landscape Requirements
For more information about the installation of the front-end components, see Installation Requirements (Analytical Apps).
Tile Type for Launching App
The Mark-to-Market Valuation
analytical app is launched using a KPI tile.
This KPI requires an evaluation that specifies one or more input parameters. For more information see Configuration Settings: Mark-to-Market Valuation..
Required SAP Notes
For the Mark-to-Market Valuation
app, the following SAP Notes must be implemented:
Back-End/Front-End Server | SAP Note Number | Description |
|---|---|---|
SAP HANA DB | Lists the tables to be replicated |
Implementation Tasks
The following sections list tasks that have to be performed to implement the Mark-to-Market Valuation
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=F0688
.
HANA Server: Assign SAP HANA Roles to Users and Roles
SAP HANA Role | Needed for ... |
|---|---|
| Read access to KPI data (views and XS OData services) |
sap.hba.r.cmmeafs.roles::MarkToMarketKPI | SAP HANA Live for Commodity Management |
As a prerequisite for read-access to KPI definition, ensure you have assigned the generic role Smart Business Runtime Role
(sap.hba.r.sb.core.roles::SAP_SMART_BUSINESS_RUNTIME
) to all users or roles.
As a prerequisite for KPI modeling, ensure you have assigned the generic role Smart Business Administration Role
(sap.hba.r.sb.core.roles::SAP_SMART_BUSINESS_MODELER
) to specific users (e.g. key user, administrator).
For more information about SAP HANA roles, see Assigning Roles for Accessing SAP HANA Data.
You can find the data required to perform this step in the SAP Fiori apps reference library at https://www.sap.com/fiori-apps-library.
HANA Server: Generate and Assign Analytic Privileges to Users and Roles
You can find the KPI data required to perform these steps in the SAP Fiori apps reference library at https://www.sap.com/fiori-apps-library.
Needed for | How to generate? |
|---|---|
Access to KPI data (only views) | To be generated by the customer using |
Access to KPI definition in KPI catalog | To be assigned by the customer using SAP Smart Business modeler app |
(Note: If the authorization object T_RDB_CMM
is used, it should be replaced by FTR_COEX
.)
You can find the KPI data required to perform this step in the SAP Fiori apps reference library at https://www.sap.com/fiori-apps-library.
Needed for | How to generate? |
|---|---|
Access to business data (only views) | To be generated by the customer using |
Front-End Server: Activate SAP UI5 Application
SAP UI5 Application | Technical Name |
|---|---|
Generic Drill-Down Application |
|
For more information about how to activate the SAP UI5 application (ICF service), see Front-End Server: Activate ICF Services of SAP UI5 Application.
Front-End Server: Enable App for Access in SAP Fiori Launchpad
The SAP Fiori launchpad is the entry point to SAP Fiori apps. From a user perspective, it displays those SAP Fiori apps that have been assigned to the catalog designed for this user's role.
This presupposes that an administrator has made the necessary assignments in the launchpad designer to enable a user's access to the respective SAP Fiori apps in the SAP Fiori launchpad. 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 KPI 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: AuthorizationRole |
|---|---|---|
|
|
|