App Implementation: Freight Order VisibilityBefore you can start to implement the app, ensure that your system landscape has been set up to enable SAP Fiori and that this system landscape already includes the front-end components and back-end components for your app:
SAP Fiori System Landscape Options | |
|---|---|
Configuration of Front-End Server | |
Back-End Components Delivered with (Product Version Stack) | SAP Event Management 9.2 SPS 2 |
Front-End Components Delivered with (Product Version Stack) | SAP Fiori 1.0 for SAP Event Management SPS 1 |
Note
The app offers the possibility to upload documents. For security reasons, we strongly recommend that you install an appropriate virus scanner in your SAP Fiori system landscape and define sufficiently restrictive scan profiles to prevent the upload of malicious content.
For more information on virus scanning and scan profiles for SAP Fiori apps, see Virus Scanning.
Ensure that the front-end component of the app is in place on your front-end server. It is automatically installed with the UI add-on.
Front-End Server: Front-End Component of App (Software Component) |
|
For more information about the installation of SAP Fiori products, see Downloading and Installing Product Versions.
For the Freight Order Visibility
app, the following SAP Notes must be implemented:
Back-End/Front-End Server | SAP Note Number | Description |
|---|---|---|
Front-End Server | Implementation recommendations for SAP Fiori 1.0 for SAP Event Management |
The following sections list tasks that have to be performed to implement the Freight Order Visibility
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 library at https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/index.html?appId=F0762
.
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 | fo_visibility |
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: 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. |
Before implementing the app, you must ensure the following:
ODT40 Scenario must be configured correctly in SAP Backend
To be able to implement the app, you must perform the following configuration tasks:
n/a
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.