Logistics Execution v2 PDF

Logistics Execution (LE)
PDF download from SAP Help Portal:

http://help.sap.com/saphelp_fiorierpx2_100/helpdata/en/45/01535205d05364e10000000a423f68/content.htm
Created on February 10, 2016
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
Page 2 of 17
1 Logistics Execution (LE)

1.1 Track Shipments
With the transactional app Track Shipments , you can provide precise shipment information to your customers quickly and easily from your desktop or mobile
device.
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.
System Landscape Requirements

The app consists of front-end components (such as the user interfaces) and back-end components (such as the OData service). The back-end and the frontend components are delivered with one product and have to be installed in a system landscape that is enabled for SAP Fiori.
Product Version Containing Back-End and
Front-End Components of the App
Back-End Product Versions Supporting the
App (Minimum Product Version Stack)
SAP Fiori System Landscape Options
SAP Fiori principal apps 1.0 for SAP ERP SPS 6
SAP ERP 6.0 SPS 15 or higher

SAP enhancement package 2 of SAP ERP 6.0 SPS 5 or higher
SAP enhancement package 7 of SAP ERP 6.0 SPS02 or higher
Setup of SAP Fiori System Landscape with ABAP Environment
Based on SAP enhancement package 7 of SAP ERP 6.0 also possible:
Setup of SAP Fiori System Landscape with SAP HANA Database
Setup of SAP Fiori System Landscape with SAP HANA XS
Component for Customer Incidents

UI5 Track Shipments (LE-FIO).
More Information
App History: Track Shipments
App Implementation: Track Shipments
App Extensibility: Track Shipments
1.1.1 App History: Track Shipments

Note
Starting with the initial delivery date, the app is delivered with each support package stack of the respective SAP Fiori product. This document only lists
support package stacks in which the app has been enhanced or changed. If the app was not changed in a particular support package stack, then this
support package stack is not mentioned in this document.
The Track Shipments app has been enhanced as follows:
SAP Fiori principal apps for SAP ERP 1.0 SPS 5 (Delivery Date 01/2015)
New/Enhanced Key Features
PUBLIC
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
New/Enhanced Extensibility Options
No changes
No new or enhanced key features
New/Changed Implementation Details
No new or changed implementation details
The UI controller hook extHookOnDetailDataReceived can be used to change or

check detail data.
SAP Note for Technical Changes
2013352
No new or enhanced key features
New/Changed Implementation Details
OData Services are enabled to provide extensibility
ListDetail
Additional information for a shipment can be displayed on the shipment list
ShipmentDetail
Additional information for a shipment can be displayed
SAP Note for Technical Changes
1979388
1972124
Initial delivery.
1.1.2 App Implementation: Track Shipments

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 and backend components for your app are already available in this system landscape:
Setup of SAP Fiori System Landscape with ABAP Environment

Based on SAP enhancement package 7 of SAP ERP 6.0 also possible:
Configuration of Front-End Server
Configuration of SAP Fiori Infrastructure
Back-End Product Versions Supporting the

App (Minimum Product Version Stack)
Product Version Containing Back-End and

Front-End Components of the App
SAP ERP 6.0 SPS 15 or higher

SAP Fiori principal apps 1.0 for SAP ERP SPS 6
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
Technical Name of Software

Component
Support Package Level
Back-end server
Back-end component
SRA019 1.0
Front-end server
Front-end component
UIX01EAP 100
Required SAP Notes

For the Track Shipments app, the following SAP Note must be implemented:
PUBLIC
Page 4 of 17
Back-End Server
SAP Note Number
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
Front-End Server: Activate OData Services

Component
Technical Name
OData Service (Version Number)
SRA019_SHIPMENT_TRACKING_SRV (1)
For more information about activating OData services, see Front-End Server: Activate OData Services.
Front-End Server: Activate SAP UI5 Application

Component
Technical Name
SAP UI5 Application
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: Enable App for Access in SAP Fiori Launchpad

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.
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.
Back-End Server: Delivered Authorization Role

(PFCG Role)
Front-End Server: Assignment to Authorization Role
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
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.
1.1.3 App Extensibility: Track Shipments

You can extend Track Shipments according to your business needs for different aspects. For this purpose, the following extensibility options are available:
View
Extension Point
Use
ObjectListItemTemplate.fragment.xml
ListDetail
Customer Extension Point shipmentListDetail: Here

additional info for a shipment can be displayed on the
shipment list
ShipmentDetail
S3.view.xml
Customer Extension Point shipmentDetail: Here

additional information for a shipment can be displayed
Add Customer Field

To add a customer field to Track Shipments , the following extensibility entities are available on the different software layers. You have to extend each of
these entities according to your specific business needs:
UI
Back End/ABAP
Optional
View
Extension Point
Design Time: Gateway

Entity
ObjectListItemTempla
ListDetail
SRA019_SHIPMENT_TRAC
Design Time: Extension

Include (in DDIC
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
Business Add-Ins (BAdIs)

The following BAdIs are available for extensibility purposes:
BD_SRA019_FREIGHT_CHARGE
You can use this BAdI to retrieve the freight charge for a given shipment. It is called when the user executes the OData service to retrieve the header
details for the Track Shipments application.
BD_SRA019_IMG_RETRIEVER
You can use this BAdI to retrieve the images for partners. It is called when the user executes the OData service to retrieve the partner image for the
Track Shipments application.
BD_SRA019_USR_TO_CUSTOMER
You can use this BAdI to implement a method for associating employees to customers.
SRA019_SHIPMENT_TRA_DPC
You can use this BAdI to change the shipment data that is retrieved from the back-end system and displayed on the user interface of the Track
Shipments app.
SRA019_SHIPMENT_TRA_MPC
You can use this BAdI to enhance the entities (the OData model) of the SRA019_SHIPMENT_TRACKING SAP NetWeaver Gateway service of the Track
Shipments app. This allows you to add your own fields.
These BAdIs are available in Customizing for Logistics Execution under
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
Allows you to add fields for contacts
SRA019_S_CUSTOMER
SRA019_S_CUSTOMER_INCL
Allows you to add fields for customers
SRA019_S_ITEM_DETAIL
SRA019_S_ITEM_INCL
Allows you to add fields for the item detail
PUBLIC
Page 6 of 17
SRA019_S_LIST
SRA019_S_LIST_INCL
Allows you to add fields for the shipment list entries
SRA019_S_SHIPMENT_PARTNER
SRA019_S_PARTNER_INCL
Allows you to add fields for the partner data
SRA019_S_PO_DETAIL
SRA019_S_PO_DETAIL_INCL
Allows you to add fields for the PO detail
SRA019_S_SHIP_DETAIL
SRA019_S_SHIP_DETAIL_INCL
Allows you to add fields for the shipment detail
For more information about extension includes, see Extension Includes.
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
Allows you to check and change the shipment detail

data.
For more information about UI controller hooks, see UI Controller Hooks.
More Information
For a general description of the extensibility options and procedures of Fiori apps, see Extensibility.
1.2 Outbound Delivery

This fact sheet displays contextual information about the outbound delivery. You can navigate to its related business objects and you can access related
transactions in operational systems.
With Outbound Delivery , you can access the most important details of an outbound delivery quickly and easily. For example, you can easily review the
number of packages, their weight and volume, and the items delivered. This information can be used for planning or execution purposes such as loading,
picking, and packing. You can also quickly check the current status of a delivery and advise the customer when the goods will arrive at the customer side.
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
Transactions in the ABAP Back End

You can access the following transactions in your ABAP back-end system, for example:
PUBLIC
Page 7 of 17
Display Outbound Delivery (VL03N)
Note
From mobile devices or tablets, you cannot access SAP GUI transactions or Web Dynpro transactions through the SAP Fiori launchpad.

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)


Fiori UI for Shipping (LE-FIO)
More Information
App History: Outbound Delivery
App Implementation: Outbound Delivery
1.2.1 App History: Outbound Delivery

The Outbound Delivery fact sheet has been enhanced as follows:
SAP Fiori for SAP ERP 1.0 SPS 04 (Delivery Date 10/2014)
No changes.
No changes.
No changes.
No changes.
Initial delivery.
1.2.2 App Implementation: Outbound Delivery

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:

PUBLIC
Page 8 of 17
Version Stack)
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.
Required SAP Notes

For Outbound Delivery , the following SAP Notes must be available:
SAP Note Number
Description
Front-End Server
1936350
FIORI Cest BON: Minor UI adjustments of Delivery

Factsheets
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.
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
Oriented View Search and Operational Analytics
Embedded Search Setting Up Embedded Search Creating Connectors .
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
Search Software Component (= Component in ESH_COCKPIT): Subnode
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

Component
Technical Name
CB_OUTBOUND_DELIVERY_SRV (1)
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.
PUBLIC
Page 9 of 17

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.
Front-End Server: Authorization Role
(PFCG Role)
CB_OUTBOUND_DELIVERY_SRV (1)
SAP_LE_OUTBOUNDDELIVERY_APP
You can assign the OData service authorization to a

business role, for example the delivered business role
(SAP_LE_BCR_TranspSpecialist_X1).
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
Authorization Role (PFCG Role)
UI5 Application for annotation files
CBESH_ANF_LE
Annotation file (BSP)
CB_OUTBOUND_DELIVERY_SRV_ANNO.xml
More Information
System.
1.3 Inbound Delivery

This fact sheet displays contextual information about the inbound delivery. You can navigate to its related business objects and you can access related
With Inbound Delivery , you can access the most important details of an inbound delivery quickly and easily. For example, you can review the number of
packages in an inbound delivery as well as their weight and volume, and the items to be received. This information can be used for planning or execution
purposes such as unloading or putaway. You can also check the current status of a delivery quickly and see when the goods are planned to be on stock for
further processing.
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
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
Net Weight
Number of Packages
Navigation Targets
Note
Linked apps have to be already available in your system landscape or you have to implement them along with this app.
Fact Sheets
Supplier
Goods Receipt
Purchase Order
Material Master

Display Returns Delivery (VL31N)

Version Stack)
Version Stack)


More Information
App History: Inbound Delivery
App Implementation: Inbound Delivery
1.3.1 App History: Inbound Delivery

The Inbound Delivery fact sheet has been enhanced as follows:
No changes.
PUBLIC
Page 11 of 17
No changes.
No changes.
No changes.
Initial delivery.
1.3.2 App Implementation: Inbound Delivery


Version Stack)
Version Stack)
Front-End Server: Front-End Component of App (Software Component)
LE-SHP
Required SAP Notes

For Inbound Delivery , the following SAP Notes must be available:
SAP Note Number
Description
Front-End Server
1936350

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

Technology
Function-
Note
Example:
PUBLIC
Page 12 of 17
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

Component
Technical Name
CB_INBOUND_DELIVERY_SRV (1)

Component
Technical Name
UI5 Application
CBESH_ANF_LE

Component
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
to your needs.
(PFCG Role)
CB_INBOUND_DELIVERY_SRV (1)
SAP_LE_INBOUNDDELIVERY_APP
Note


PUBLIC
Page 13 of 17
Extensibility
Component
CBESH_ANF_LE
CB_INBOUND_DELIVERY_SRV_ANNO.xml
More Information
System.
1.4 Returns Delivery

This fact sheet displays contextual information about the returns delivery. You can navigate to its related business objects and you can access related
With Returns Delivery , you can access the most important details of a returns delivery quickly and easily. For example, you can review the number of
packages in an inbound delivery as well as their weight and volume, and the items to be received. This information can be used for planning or execution
purposes such as unloading or putaway. You can also quickly check the status of a delivery that must be returned and effectively handle the customer
complaint.
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
Net Weight
Number of Packages
Navigation Targets
Note
Linked apps have to be already available in your system landscape or you have to implement them along with this app.
Fact Sheets
Customer
Goods Receipt
Material Master
Credit Memo

Display Returns Delivery (VL03N)
Note
From mobile devices or tablets, you cannot access SAP GUI transactions or Web Dynpro transactions through the SAP Fiori launchpad.

PUBLIC
Page 14 of 17
Version Stack)
Version Stack)


More Information
App History: Returns Delivery
App Implementation: Returns Delivery
1.4.1 App History: Returns Delivery

The Returns Delivery fact sheet has been enhanced as follows:
No changes.
No changes.
No changes.
No changes.
Initial delivery.
1.4.2 App Implementation: Returns Delivery


Version Stack)
Version Stack)
Front-End Server: Front-End Component of Fact Sheet (Software Component)
LE-SHP
PUBLIC
Page 15 of 17
Required SAP Notes

For Returns Delivery , the following SAP Notes must be available:
SAP Note Number
Description
Front-End Server
1936350

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

Technology
Function-
Note
Example:
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

Component
Technical Name
CB_RETURNS_DELIVERY_SRV (1)

Component
Technical Name
UI5 Application
CBESH_ANF_LE

Component
Technical Name
PUBLIC
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
to your needs.

(PFCG Role)
CB_RETURNS_DELIVERY_SRV (1)
SAP_LE_RETURNSDELIVERY_APP

Note

Extensibility
Component
CBESH_ANF_LE
CB_INBOUND_DELIVERY_SRV_ANNO.xml
More Information
System.
PUBLIC
Page 17 of 17

Logistics Execution v2 PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Logistics Execution v2 PDF

Загружено:

Авторское право:

Доступные форматы

Logistics Execution (LE)

PDF download from SAP Help Portal:

1 Logistics Execution (LE)

System Landscape Requirements

SAP Fiori System Landscape Options

SAP Fiori principal apps 1.0 for SAP ERP SPS 6

SAP ERP 6.0 SPS 15 or higher

Component for Customer Incidents

1.1.1 App History: Track Shipments

New/Enhanced Extensibility Options

No new or enhanced key features

New/Changed Implementation Details

No new or changed implementation details

New/Enhanced Extensibility Options

The UI controller hook extHookOnDetailDataReceived can be used to change or

SAP Note for Technical Changes

No new or enhanced key features

New/Changed Implementation Details

OData Services are enabled to provide extensibility

New/Enhanced Extensibility Options

SAP Note for Technical Changes

1.1.2 App Implementation: Track Shipments

Setup of SAP Fiori System Landscape with ABAP Environment

Configuration of Front-End Server

Configuration of SAP Fiori Infrastructure

Back-End Product Versions Supporting the

Product Version Containing Back-End and

SAP ERP 6.0 SPS 15 or higher

Technical Name of Software

Support Package Level

Required SAP Notes

SAP Note Number

Front-End Server: Activate OData Services

OData Service (Version Number)

Front-End Server: Activate SAP UI5 Application

SAP UI5 Application

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

Back-End Server: Delivered Authorization Role

Front-End Server: Assignment to Authorization Role

1.1.3 App Extensibility: Track Shipments

Customer Extension Point shipmentListDetail: Here

Customer Extension Point shipmentDetail: Here

Add Customer Field

Design Time: Gateway

Design Time: Extension

Business Add-Ins (BAdIs)

Allows you to add fields for contacts

Allows you to add fields for customers

Allows you to add fields for the item detail

Allows you to add fields for the shipment list entries

Allows you to add fields for the partner data

Allows you to add fields for the PO detail

Allows you to add fields for the shipment detail

For more information about extension includes, see Extension Includes.

Allows you to check and change the shipment detail

For more information about UI controller hooks, see UI Controller Hooks.

1.2 Outbound Delivery

Transactions in the ABAP Back End

Display Outbound Delivery (VL03N)

System Landscape Requirements

Setup of SAP Fiori System Landscape with SAP HANA Database

Component for Customer Incidents

1.2.1 App History: Outbound Delivery