fiori odata extensibility

7/18/2019 Fiori Odata Extensibility

http://slidepdf.com/reader/full/fiori-odata-extensibility 1/11

SAP FioriOData Extensibility



© 2013 SAP AG. All rights reserved. 2Ramp-Up Knowledge Transfer Customer

Objectives

At the end of this module, you will be able to:

Understand the different content layers in the context of extensibility;

Understand the oData Extensibility concept;

Create a custom oData project using the Redefinition approach.




Extensibility Considerations

SAP Fiori applications can be extended by enhancing one or multiple content layers,

depending of the extension requirements and the application type. In this section, we

will focus on the Gateway layer.

Content Layer

When an Extension is Required

Relevance

Business Suite The back-end logic and content required for

the application enhancement does not exist inthe Business Suite.

Relevant for transactional apps.

Gateway

The back-end logic and content required for

the app extension exists in the Business Suite

layer, but is not exposed in the app's Gateway

service.

Relevant for transactional and analytical apps.

HANA

The back-end content required for the app

extension exists in the HANA models, but is

not exposed in the app's OData service.

Relevant for analytical apps.

UI

The back-end logic and content required for

the app extension exists in the Gateway layer,

but is not exposed in the app's UI.

Relevant for transactional and analytical apps.

Search Model

The back-end logic is not exposed in the

application’s Gateway service.

Relevant for factsheets.




Required Skills

The following ABAP transactions will need to be used when extending the Gateway

Content Layer of a Fiori application:

• SEGW – Gateway Service Builder

• SE11 – ABAP Dictionary Maintenance

• SE80 – Object Navigator

Content Layer

ABAP

Business

Suite

SAP

NetWeaver

Gateway

HANA Native

Development

SAPUI5

OData Protocol

HTML5,

JavaScript

Fiori specific

UI

Development

Business Suite

X

X

Gateway X X

HANA

X

UI

X

X

X

Search Model X X




Odata Extensibility Taskflow

SE11 – ABAP Dictionary Maintenance

SEGW – Gateway Service Builder

SE80 – Object Navigator

Add fields into the Extension

include structure

Create a new oData project byredefining the out-of-the-box

oData project

Code in the extended Runtime

and Model Classes

This approach allows to achieve modification-free extension of Fiori applications.




OData Extensibility Concept

SAP delivered

oData projectCustom

oData project

RedefinesBy redefining the out-of-the-box

oData Service in a custom project,

it will be possible to expose

additional content, such as:

• Custom Properties to existing

Entities;

• Custom Entities;• HTTP methods for custom

Entities.


http://slidepdf.com/reader/full/fiori-odata-extensibility 7/11© 2013 SAP AG. All rights reserved. 7Ramp-Up Knowledge Transfer Customer

Redefining an oData ServiceOn Backend (Where IW_BEP is Deployed)

The out-of-the-box oData project is used as the starting point of the extension

project.

In SEGW, create a new

extension project…

And redefine itsoData service



Redefining an oData ServiceOn Backend (Where IW_BEP is Deployed)

SAP Technical Service Name is

required during the redefinition.

Select the additional Entities/Propertiesto be exposed and finalize the process.



Redefining an oData ServiceOn Gateway (Where IW_FND is Deployed)

The newly created custom oData Service needs to be registered in Gateway

(/IWFND/MAINT_SERVICE).

Once done, it can be tested using the Gateway Client tool to confirm the added

custom Entities/Properties are successfully retrieved.



Objectives

You should now be able to:

Understand the different content layers in the context of extensibility;

Understand the oData Extensibility concept;

Create a custom oData project using the Redefinition approach.



© 2013 SAP AG. 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 AG.

The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

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.

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

Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

http://www.sap.com/corporate-en/legal/copyright/index.epx




fiori odata extensibility

Documents