Extension of FIORI Factsheets

Author:

Ursula Knakal
Business Processes rliebers@kpmg.comConsultant
SAP Österreich GmbH
ursula.knakal@sap.com
BRF+ LEAN TRACE VISUALIZATION TOOL

TABLE OF CONTENT
1 GENERAL INDROCUTION ............................................................................................................... 3
2 ENHANCEMENT OF SEARCH MODEL .......................................................................................... 3
3 TEST TRANSFER FROM ODATA ................................................................................................... 5
4 EXTEND THE ANNOTATION FILE .................................................................................................. 7
5 ADAPT THE NAVIGATION ............................................................................................................... 7

2
BRF+ LEAN TRACE VISUALIZATION TOOL

1 GENERAL INDROCUTION
We want to extend the standard FIORI Factsheet for Sales Order with two Fields:
 Order related invoice status on header level
 Rejection reason on item level

2 ENHANCEMENT OF SEARCH MODEL

In order to get the new fields delivered by the ODATA service we need to extend the search model as described in the
following points:

1. Go to Administration Cockpit of Embedded Search via transaction ESH_COCKPIT and switch to Modeler
Mode.

2. Click on Software Components  maintain Software Components and create a new Software Component in
customer namespace.

3. Select your created Software Component in the List below and click Software Components  Include
Software Component.

4. Select the Software Component you want to enhance – in our case it is SAPAPPLH.

3
BRF+ LEAN TRACE VISUALIZATION TOOL

5. Navigate to the Search Model you want to enhance – in our case SALES_ORDER_H, mark the line and click on
edit.

6. Skip the first step in the roadmap and go directly to the second “Model Nodes”. Select the node you want to
extend. Select the fields you want additionally and make sure that “select for node” flag is checked.

7. Since this field is only a key but we want to display the corresponding texts on the factsheets navigate to the
next step in the roadmap “Node Relations”. Select the to be enhanced node in the table (in our case sd_vbuk)
and create a new association to node TVBST via createassociation.
a. Once you created the association give it a meaningful name in column “Association”

4
BRF+ LEAN TRACE VISUALIZATION TOOL

b. Now we have to create the mapping between the key field to the texts. To do so maintain the table
below like the following in case of FKSAK (order rel. invoice status):

8. Once we have finished this step navigate directly to roadmap step “Node Response”. Here we have to make
sure, that our additional fields will be added in the response attribute list of the corresponding nodes.
Please note that the majority of OData services only transfer data on Header and Item level!
a. Add your fields in the response attribute list.

9. Click Finish.

10. Switch back from Modeler mode to Administration Cockpit and click Actions  Update
a. Now the enhanced model as well as the existing ODATA service will be updated in the backend, this
may take a while.

3 TEST TRANSFER FROM ODATA

Once the update of the search connectors is complete, switch to your gateway system and go to transaction
/IWFND/MAINT_SERVICE. Filter the technical name on term *CB*SRV*. Select the corresponding service – in our case
Sales Order – and click on “Gateway-Client”.

Execute the Service with test data and check that the additional fields are delivered.

5
BRF+ LEAN TRACE VISUALIZATION TOOL

Trouble Shooting: If you don’t get the additional fields try executing transaction
/IWBEP/CACHE_CLEANUP in the Backend and transaction /IWFND/CACHE_CLEANUP in the gateway
system. You can also test the enhanced search model with transaction ESH_TEST_SEARCH.

6
BRF+ LEAN TRACE VISUALIZATION TOOL

4 EXTEND THE ANNOTATION FILE

1. Take the existing annotation file for the Fact Sheet you want to extend. In our case it is BSP Application
BSCBN_ANF_SDSLS and the annotation file BSCBN_SALES_ORDER_SRV_ANNO.xml
2. Copy the standard annotation file, create a new BSP application in customer namespace and a new XML page
with flow logic in which you copy the content of the standard annotation file.
3. Make your changes!

More information about the annotation file:

http://help.sap.com/fiori_bs2013/helpdata/en/00/674152c1bd141be10000000a445394/content.htm?frameset=/en/
b4/a64552bda1d171e10000000a44176d/frameset.htm

Be aware that the place where your new field is displayed is dependent on the priority you assign to it, e.g. if you have
a detailed view of Sales Oder items with 2 navigations down a field with priority “low” will be displayed on the last
view of the navigation.

5 ADAPT THE NAVIGATION

1. Go to transaction LPD_CUST and select the Launchpad role for the factsheet you extended.
2. Navigate to the details by double clicking on the Launchpad role and select the corresponding entry for the
factsheet

3. Click on “show advanced parameters” and adapt the Target Application Parameters accordingly

7
BRF+ LEAN TRACE VISUALIZATION TOOL

8
www.sap.com

©2011 SAP AG. All rights reserved.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign,
SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other
SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP AG
in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects,

Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and
other Business Objects products and services mentioned herein as
well as their respective logos are trademarks or registered trademarks
of Business Objects Software Ltd. Business Objects is an SAP
company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL

Anywhere, and other Sybase products and services mentioned herein
as well as their respective logos are trademarks or registered
trademarks of Sybase, Inc. Sybase is an SAP company.

All other product and service names mentioned are the trademarks of
their respective companies. Data contained in this document serves
informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials

are provided by SAP AG 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.