App Implementation: Returns Delivery

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 components 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 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 Components Delivered with (Product Version Stack)	SAP enhancement package 7 for SAP ERP 6.0 SPS 06
Front-End Components Delivered with (Product Version Stack)	SAP Fiori for SAP ERP 1.0 SPS04

Ensure that the software component of the fact sheet is in place on your front-end server. It is automatically installed with the UI-Add-On.

Front-End Server: Front-End Component of Fact Sheet (Software Component)

LE-SHP

For more information about the installation of SAP Fiori products, see Downloading and Installing Product Versions.

Required SAP Notes

For Returns Delivery, the following SAP Notes must be available:

Back-End/Front-End Server	SAP Note Number	Description
Front-End Server	1936350	FIORI C’est BON: Minor UI adjustments of Delivery Factsheets

Implementation Tasks

The following sections list tasks that have to be performed to implement the Returns Delivery fact sheet. The tables contain the app-specific data required for these tasks.

Back-End Server: Create Connectors

SAP Fiori fact sheets are based on search models. To be able to use a fact sheet, you must activate the underlying search models by creating connectors. Create connectors in transaction ESH_COCKPIT.

For more information, SAP Help Portal at http://help.sap.com under Technology SAP NetWeaver Platform <release> Application Help Function-Oriented View Search and Operational Analytics Embedded Search Setting Up Embedded Search Creating Connectors .

Note Note

Note the following system behavior:

Search software components build a stack: On top of the basis component, different layers can be installed.

Search models can be available in different components: In their original component, but also in higher layer components (extension components).

Once you create a search connector in an extension component, all search models from the original component are transferred into the extension component. You will therefore no longer find the search models in the original component, which is shown in the table below.

Example:

You have created a connector for a search model originating in search component SAPAPPLH. You have created the connector via component EAAPPLH, not via its original component SAPAPPLH. From that moment on, all search models originating in component SAPAPPLH can only be found under the EAAPPLH node in transaction ESH_COCKPIT.

End of the note.

Create connectors based on the following search models:

Search Model	Search Software Component (= Component in ESH_COCKPIT): Subnode
GOODS_ISSUE_H	`SAPAPPLH`: MM-IM
PURCHASE_ORDER_H	`SAPAPPLH`: MM-PUR
SALES_ORDER_H	`SAPAPPLH`: SD-SLS
RETURNS_DELIVERY_H	`SAPAPPLH`: LE-SHP
VENDOR_H	`SAPAPPLH`: MM-PUR
MATERIAL_H	`SAPAPPLH`: MM-IM
CUSTOMER_H	`SAPAPPLH`: SD-MD

Front-End Server: Activate OData Services

Component	Technical Name
OData Service (Version Number)	`CB_RETURNS_DELIVERY_SRV` (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	`CBESH_ANF_LE`

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 fact sheet 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	-
Business Role	`SAP_LE_BCR_SHIPPINGSPECIALIST`
Business Catalog	`SAP_LE_BC_SHIPPINGSPECIALIST`
Business Catalog Group	`SAP_LE_BCG_SHIPPINGSPECIALIST`
Technical Role	`SAP_LE_TCR_T`
Technical Catalog	`SAP_LE_TC_F`
`LPD_CUST` Role	`UIAPLE01`
`LPD_CUST` Instance	`FACTSHEETS` `TRANSACTIONAL`

Front-End Server and Back-End Server: Assign Roles with OData Service Authorization to Users

To grant specific users access to OData services, 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 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 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
`CB_RETURNS_DELIVERY_SRV` (1)	`SAP_LE_RETURNSDELIVERY_APP` Note In addition, this role contains authorizations to use the underlying search models of the fact sheet and to display the related business data. End of the note.	You can assign the OData service authorization to a business role, for example the delivered business role (`SAP_LE_BCR_TranspSpecialist_X1`).

For more information about OData service authorizations and roles containing them, see Back-End Server: Assign OData Service Authorization to Users and Front-End Server: Assign OData Service Authorization to Users.

Extensibility

For information about how to extend fact sheets, see UI Extensibility for Fact Sheets. To extend a fact sheet, you need to change the related annotation file. The following table contains the information you need to find the annotation file.

Component	Authorization Role (PFCG Role)
UI5 Application for annotation files	`CBESH_ANF_LE`
Annotation file (BSP)	`CB_INBOUND_DELIVERY_SRV_ANNO.xml`

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.