App Implementation: Pick Outbound Delivery

System Landscape Requirements

For information about the system requirements, see the S/4HANA UI Technology guide at http://help.sap.com/s4hana_op_1610.

Required SAP Notes

For this app, the following SAP Notes must be implemented:

Back-End / Front-End Server	SAP Note	Description
Not applicable	Not applicable	Not applicable

Implementation Tasks

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

You can also 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=F0868.

Front-End Server: Activate OData Services

Component	Technical Name
OData Service	LE_SHP_DELIVERY_PICK

For more information about activating OData services, see section Front-End Server: Activate OData Services in the S/4HANA UI Technology guide.

Front-End Server: Activate SAP UI5 Application

Component	Technical Name
SAP UI5 Application	LE_SHP_PICK

For more information about how to activate the ICF service, see section Front-End Server: Activate ICF Services of SAPUI5 Application in the S/4HANA UI Technology guide.

Front-End Server: Enable App for Access in SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to apps. In the launchpad, the user can see and access those 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 section Setup of Catalogs, Groups, and Roles in the SAP Fiori Launchpad in the S/4HANA UI Technology guide.

SAP delivers technical catalogs for groups of 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 app to your users.

Caution 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.

End of the caution.

Make the assignment on the back-end server and on the front-end server:

On the back-end server, you have to assign the OData service authorization to a PFCG role. For more information, see section Back-End Server: Assign OData Service Authorization to Users in the S/4HANA UI Technology guide.
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 sections Create PFCG Role on Front-End and Assign Launchpad Catalogs and Groups and Front-End Server: Assign Roles to Users in the S/4HANA UI Technology guide.

OData Service (Version Number)	Back-End Server: Authorization Role (PFCG Role)	Front-End Server: Assignment to Authorization Role
LE_SHP_DELIVERY_PICK	You can use the example business catalog SAP_LE_BC_OBDLV_PROC, Logistic Execution - Outbound Deliveries or your custom catalog to create the back-end PFCG role.	Use an existing role or create a new one.

More Information

Note that the role SAP_BR_SHIPPING_SPECIALIST gives a user the authorization to use this app. However, authorization is also required for the actions that are performed by this app. In this case, you also have to assign the authorization object V_LIKP_VST to the user in the backend.