Professional Documents
Culture Documents
The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help
Portal.
Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.
2016 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP
SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are
provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP
Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in
Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
Table of content
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 1 of 17
Table of content
1 Logistics Execution (LE)
1.1 Track Shipments
1.1.1 App History: Track Shipments
1.1.2 App Implementation: Track Shipments
1.1.3 App Extensibility: Track Shipments
1.2 Outbound Delivery
1.2.1 App History: Outbound Delivery
1.2.2 App Implementation: Outbound Delivery
1.3 Inbound Delivery
1.3.1 App History: Inbound Delivery
1.3.2 App Implementation: Inbound Delivery
1.4 Returns Delivery
1.4.1 App History: Returns Delivery
1.4.2 App Implementation: Returns Delivery
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 2 of 17
Key Features
Browse a list of shipments to a customer assigned to the sales representative.
See the estimated shipment date and current status at a glance.
Filter shipments by status (shipped, scheduled, overdue), or search for all shipments to a specific customer.
Display details for a shipment (incl. shipment date, carrier, freight charges, item details, contacts).
Click the tracking number for shipped items to go directly to the carriers tracking Web site.
In addition, the app supports the following technical features and options:
If the long material number has been activated in your back-end system, it is automatically displayed in the Material field in this SAP Fiori app. For
more information, see Long Material Number in SAP Fiori Apps.
More Information
App History: Track Shipments
App Implementation: Track Shipments
App Extensibility: Track Shipments
SAP Fiori principal apps for SAP ERP 1.0 SPS 5 (Delivery Date 01/2015)
New/Enhanced Key Features
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
The app is now enabled to display the long material number instead of the
standard material number. For more information, see Long Material Number
in SAP Fiori Apps
Page 3 of 17
No changes
SAP Fiori principal apps for SAP ERP 1.0 SPS 3 (Delivery Date 07/2014)
New/Enhanced Key Features
2013352
SAP Fiori principal apps for SAP ERP 1.0 SPS 2 (Delivery Date 05/2014)
New/Enhanced Key Features
ListDetail
Additional information for a shipment can be displayed on the shipment list
ShipmentDetail
Additional information for a shipment can be displayed
1979388
1972124
SAP Fiori principal apps for SAP ERP 1.0 SPS 0 (Delivery Date 11/2013)
Initial delivery.
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
Back-end server
Back-end component
SRA019 1.0
Front-end server
Front-end component
UIX01EAP 100
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 4 of 17
Back-End/Front-End Server
Back-End Server
Description
Employee Assignment to Sold-to Party
1931055
Implementation Tasks
The following sections list tasks that have to be performed to implement the Track Shipments 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=F0405
Technical Name
SRA019_SHIPMENT_TRACKING_SRV (1)
For more information about activating OData services, see Front-End Server: Activate OData Services.
Technical Name
LE_SHIP_MON
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).
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
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)
SRA019_SHIPMENT_TRACKING_SRV (1)
OData service authorization is included in the example OData service authorization must be assigned.
role SAP_LE_SHIP_MON_APP
Note
In addition, this role contains authorizations to
display the related business data.
Configuration Tasks
To enable Track Shipments , you must perform the following configuration tasks:
Define URL for Carriers
In this Customizing activity, you define the URL for the carrier (vendor). It is used to provide a hyperlink from the tracking number. This Customizing
activity is available in Customizing for Logistics Execution under
Transportation Track Shipments .
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 5 of 17
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.
Extension Point
Use
ObjectListItemTemplate.fragment.xml
ListDetail
ShipmentDetail
S3.view.xml
Back End/ABAP
Optional
View
Extension Point
ObjectListItemTempla
ListDetail
SRA019_SHIPMENT_TRAC
BAdI/method to be
implemented
Runtime: Superclass/
Method to Be Redefined
Structure)
te.fragment.xml
BAdI:
Superclass:
KING_SRV/
SRA019_SHIPMENT_TRA_
CL_SRA019_SHIPMENT_TR
ShipmentList
DPC
A_DPC_EXT
Method:
Method:
IF_SRA019_SHIPMENT_T
SHIPMENTLISTSET_GET_E
RA_DPC~
NTITYSET
SRA019_S_LIST_INCL
CHANGE_SHIPMENT_LIST
_APT
S3.view.xml
ShipmentDetail
SRA019_SHIPMENT_TRAC
SRA019_S_SHIP_DETAIL
BAdI:
Superclass:
KING_SRV/
_INCL
SRA019_SHIPMENT_TRA_
CL_SRA019_SHIPMENT_TR
DPC
A_DPC_EXT
Method:
Method:
IF_SRA019_SHIPMENT_T
SHIPMENTDETAILSE_GET_
RA_DPC~
ENTITY
ShipmentDetail
CHANGE_SHIPMENT_DETA
ILS_API
Transportation
Track Shipments
Extension Includes
In addition to the extension includes described above, the following extension includes are available:
DDIC
Extension Include
Use
SRA019_S_LIST
SRA019_S_CONTACT_INCL
SRA019_S_CUSTOMER
SRA019_S_CUSTOMER_INCL
SRA019_S_ITEM_DETAIL
SRA019_S_ITEM_INCL
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 6 of 17
SRA019_S_LIST
SRA019_S_LIST_INCL
SRA019_S_SHIPMENT_PARTNER
SRA019_S_PARTNER_INCL
SRA019_S_PO_DETAIL
SRA019_S_PO_DETAIL_INCL
SRA019_S_SHIP_DETAIL
SRA019_S_SHIP_DETAIL_INCL
UI Controller Hooks
To plug in and execute custom code, the following hooks are available in the controller code:
Controller
Hook
Use
S3.controller.js
extHookOnDetailDataReceived
More Information
For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.
Key Features
Display the most important facts about an outbound delivery such as the ship-to and sold-to party and the status.
Preview the items in the outbound delivery.
Click the tile to see more information such as the delivery quantity and the weight.
Display more information about the parties involved in the outbound delivery.
View the logistic supply chain document flow.
Key Facts
Gross Weight
The total gross weight of a delivery
Net Weight
The total net weight of a delivery
Number of Packages
The number of packages contained in a delivery
Navigation Targets
Navigation targets are linked apps or back-end transactions that can be directly accessed from the fact sheet.
Note
These linked apps have to be already available in your system landscape or you have to implement them along with this app.
Fact Sheets
You can navigate to the following fact sheets, for example:
Customer
Goods Issue
Sales Order
Material Master
Billing Document
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 7 of 17
Note
From mobile devices or tablets, you cannot access SAP GUI transactions or Web Dynpro transactions through the SAP Fiori launchpad.
More Information
App History: Outbound Delivery
App Implementation: Outbound Delivery
SAP Fiori for SAP ERP 1.0 SPS 04 (Delivery Date 10/2014)
No changes.
SAP Fiori for SAP ERP 1.0 SPS 03 (Delivery Date 07/2014)
No changes.
SAP Fiori for SAP ERP 1.0 SPS 02 (Delivery Date 05/2014)
No changes.
SAP Fiori for SAP ERP 1.0 SPS 01 (Delivery Date 02/2014)
No changes.
SAP Fiori for SAP ERP 1.0 SPS 00 (Delivery Date 11/2013)
Initial delivery.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 8 of 17
Back-End Components Delivered with (Product SAP enhancement package 7 for SAP ERP 6.0 SPS 06
Version Stack)
Front-End Components Delivered with (Product SAP Fiori for SAP ERP 1.0 SPS04
Version Stack)
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 App (Software Component)
LE-SHP
For more information about the installation of SAP Fiori products, see Downloading and Installing Product Versions.
Description
Front-End Server
1936350
Implementation Tasks
The following sections list tasks that have to be performed to implement the Outbound Delivery fact sheet. The tables contain the app-specific data required
for these tasks.
Function-
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.
Create connectors based on the following search models:
Search Model
GOODS_ISSUE_H
SAPAPPLH: MM-IM
PURCHASE_ORDER_H
SAPAPPLH: MM-PUR
OUTBOUND_DELIVERY_H
SAPAPPLH: LE-SHP
SALES_ORDER_H
SAPAPPLH: SD-SLS
MATERIAL_H
SAPAPPLH: MM-IM
CUSTOMER_H
SAPAPPLH: SD-MD
Technical Name
CB_OUTBOUND_DELIVERY_SRV (1)
For more information about activating OData services, see Front-End Server: Activate OData Services.
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.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 9 of 17
Technical Name
Semantic Object
Business Role
SAP_LE_BCR_SHIPPINGSPECIALIST
Business Catalog
SAP_LE_BC_SHIPPINGSPECIALIST
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)
(PFCG Role)
CB_OUTBOUND_DELIVERY_SRV (1)
SAP_LE_OUTBOUNDDELIVERY_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.
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
CBESH_ANF_LE
CB_OUTBOUND_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.
Key Features
See the most important details of the inbound delivery such as the vendor party and delivery date.
Preview the inbound delivery items.
Access further information about the delivery such as the quantity and the weight.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 10 of 17
Display more information about the business partner, such as the address.
View the document flow involved in the logistic supply chain.
Navigate to the purchase order from the item detail.
Key Facts
Gross Weight
The total gross weight of a delivery
Net Weight
The total net weight of a delivery
Number of Packages
The number of packages contained in a delivery
Navigation Targets
Navigation targets are linked apps or back-end transactions that can be directly accessed from the fact sheet.
Note
Linked apps have to be already available in your system landscape or you have to implement them along with this app.
Fact Sheets
You can navigate to the following fact sheets, for example:
Supplier
Goods Receipt
Purchase Order
Material Master
More Information
App History: Inbound Delivery
App Implementation: Inbound Delivery
SAP Fiori for SAP ERP 1.0 SPS 04 (Delivery Date 10/2014)
No changes.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 11 of 17
SAP Fiori for SAP ERP 1.0 SPS 03 (Delivery Date 07/2014)
No changes.
SAP Fiori for SAP ERP 1.0 SPS 02 (Delivery Date 05/2014)
No changes.
SAP Fiori for SAP ERP 1.0 SPS 01 (Delivery Date 02/2014)
No changes.
SAP Fiori for SAP ERP 1.0 SPS 00 (Delivery Date 11/2013)
Initial delivery.
Back-End Components Delivered with (Product SAP enhancement package 7 for SAP ERP 6.0 SPS 06
Version Stack)
Front-End Components Delivered with (Product SAP Fiori for SAP ERP 1.0 SPS04
Version Stack)
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 App (Software Component)
LE-SHP
For more information about the installation of SAP Fiori products, see Downloading and Installing Product Versions.
Description
Front-End Server
1936350
Implementation Tasks
The following sections list tasks that have to be performed to implement the Inbound Delivery fact sheet. The tables contain the app-specific data required for
these tasks.
Function-
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:
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 12 of 17
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.
Create connectors based on the following search models:
Search Model
GOODS_RECEIPT_H
SAPAPPLH: MM-IM
PURCHASE_ORDER_H
SAPAPPLH: MM-PUR
INBOUND_DELIVERY_H
SAPAPPLH: LE-SHP
VENDOR_H
SAPAPPLH: MM-PUR
MATERIAL_H
SAPAPPLH: MM-IM
CUSTOMER_H
SAPAPPLH: SD-MD
Technical Name
CB_INBOUND_DELIVERY_SRV (1)
For more information about activating OData services, see Front-End Server: Activate OData Services.
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.
Technical Name
Semantic Object
Business Role
SAP_LE_BCR_GOODSRECEIPTSPEC
Business Catalog
SAP_LE_BC_GOODSRECEIPTSPEC
SAP_LE_BCG_GOODSRECEIPTSPEC
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)
(PFCG Role)
CB_INBOUND_DELIVERY_SRV (1)
SAP_LE_INBOUNDDELIVERY_APP
Note
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.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 13 of 17
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
CBESH_ANF_LE
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.
Key Features
Display the most important facts about a returns delivery such as the returning party and status.
Preview the items in the returns delivery.
Click the tile to display further information such as the delivery quantity and the weight.
View the returns process document flow.
Key Facts
Gross Weight
The total gross weight of a delivery
Net Weight
The total net weight of a delivery
Number of Packages
The number of packages contained in a delivery
Navigation Targets
Navigation targets are linked apps or back-end transactions that can be directly accessed from the fact sheet.
Note
Linked apps have to be already available in your system landscape or you have to implement them along with this app.
Fact Sheets
You can navigate to the following fact sheets, for example:
Customer
Goods Receipt
Material Master
Credit Memo
Note
From mobile devices or tablets, you cannot access SAP GUI transactions or Web Dynpro transactions through the SAP Fiori launchpad.
Page 14 of 17
The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end components
and the front-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori.
Back-End Components Delivered with (Product SAP enhancement package 7 for SAP ERP 6.0 SPS 06
Version Stack)
Front-End Components Delivered with (Product SAP Fiori for SAP ERP 1.0 SPS04
Version Stack)
SAP Fiori System Landscape Options
More Information
App History: Returns Delivery
App Implementation: Returns Delivery
SAP Fiori for SAP ERP 1.0 SPS 04 (Delivery Date 10/2014)
No changes.
SAP Fiori for SAP ERP 1.0 SPS 03 (Delivery Date 07/2014)
No changes.
SAP Fiori for SAP ERP 1.0 SPS 02 (Delivery Date 05/2014)
No changes.
SAP Fiori for SAP ERP 1.0 SPS 01 (Delivery Date 02/2014)
No changes.
SAP Fiori for SAP ERP 1.0 SPS 00 (Delivery Date 11/2013)
Initial delivery.
Back-End Components Delivered with (Product SAP enhancement package 7 for SAP ERP 6.0 SPS 06
Version Stack)
Front-End Components Delivered with (Product SAP Fiori for SAP ERP 1.0 SPS04
Version Stack)
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
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 15 of 17
For more information about the installation of SAP Fiori products, see Downloading and Installing Product Versions.
Description
Front-End Server
1936350
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.
Function-
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.
Create connectors based on the following search models:
Search Model
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
Technical Name
CB_RETURNS_DELIVERY_SRV (1)
For more information about activating OData services, see Front-End Server: Activate OData Services.
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.
Technical Name
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 16 of 17
Semantic Object
Business Role
SAP_LE_BCR_SHIPPINGSPECIALIST
Business Catalog
SAP_LE_BC_SHIPPINGSPECIALIST
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)
CB_RETURNS_DELIVERY_SRV (1)
SAP_LE_RETURNSDELIVERY_APP
Note
(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
CBESH_ANF_LE
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.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 17 of 17