1. How To Build OData Services from any
Business Suite Data – Fast!
Jeff Gebo, Chris Whealy
September 2012

2. SAP NetWeaver Gateway Service Builder (SEGW)
One-Stop-Shop for all GW OData Service Developers
Ÿ Developer productivity (low TCD) for
Little or no ABAP skills
ABAP Developer, Technical Consultant
and Business Process Expert
Ÿ The SAP NetWeaver Gateway Service
Builder is a one stop shop tool that
Technical covers the entire development lifecycle
Consultant of a Gateway Service
/ BPX
Ÿ Generation of model definition
Ÿ Generation of service implementation
from existing business functionality
Ÿ Integration and projection for important
data sources like GenIL, SPI and BW
Ÿ EDMX-Model import
Strong ABAP skills
Ÿ Extensibility/Reuse of Gateway
Services
Professional
ABAP
Developer
© 2012 SAP AG. All rights reserved. 2

3. SAP NetWeaver Gateway
Service Builder
Gateway’s Design-Time Environment
Build and manage services from one location
OData modelling environment
Ÿ Define entity types, entity sets, associations etc.
Project-based Service Development
Ÿ Consolidates all service design and runtime
objects
For both experienced and less-experienced
developers
Ÿ Take advantage of existing data sources and
automatic content generation or…
Ÿ Define a new service completely from scratch
© 2012 SAP AG. All rights reserved. 3

4. Gateway Service Builder – Development Flow in Detail
OData
Service
Defini.on
in
SEGW
Data Model
Declara.ve
Import
Import
DDIC/
Definition
(MPC)
Data
Model
Defini.on
Model
Data
Model
RFC/BOR
Redefine
Defini.on*
(EDMX)
Interface*
Data
Source
Service
Include
(GenIL,
BOL,
enera.on
Service
G Gateway
SPI,
BW
Service*
Service Easy
Query,
Implementation Service
Implementa.on
FC/BOR
Code-­‐Based
Implementa.on*
Map
R MDX)
Code-­‐Based
Extensions*
mapping)
Opera.on*
(DPC) (Code
based
or
Service * Repeatable
Maintenance within
Service
Registra.on
one service
and
Hub
Ac.va.on
© 2012 SAP AG. All rights reserved. 4

5. Gateway Service Builder – Development Flow in Detail
OData
Service
Defini.on
in
SEGW
Data Model
Declara.ve
Import
Import
DDIC/
Definition Model
Data
Model
RFC/BOR
(MPC) Redefine
Defini.on*
(EDMX)
Interface*
Data
Source
Service
Include
(GenIL,
BOL,
Gateway
SPI,
BW
Service*
Service Easy
Query,
Code-­‐Based
Implementa.on*
Map
RFC/BOR
MDX)
Implementation
(DPC) Code-­‐Based
Extensions*
Opera.on*
Service * Repeatable
Maintenance within
Service
Registra.on
one service
and
Hub
Ac.va.on
© 2012 SAP AG. All rights reserved. 5

6. Service Builder
File Import
Import a Data Model
Jumpstart service modelling
Ÿ EDMX Modelling Tool
(e.g. OData Visualizer in MS Visual Studio)
Ÿ Modify properties as needed
Ÿ Generate model provider class and
stubs for data provider class
© 2012 SAP AG. All rights reserved. 6

7. Service Builder
Import Existing BOR/RFC Data Structure for Use in an OData Service
Import a Data Source
Re-use Existing BOR/RFC Interfaces
Ÿ Wizard walks you through it
Ÿ Modify properties as needed
© 2012 SAP AG. All rights reserved. 7

8. Service Builder
Generate an OData Service from an Existing BOR/RFC Object
Implementation Without Code
Map to Data Source
Ÿ Add constants
Ÿ Modify properties
Ÿ Drag-and-drop
© 2012 SAP AG. All rights reserved. 8

9. Service Builder
Associations
Relationships Between Entity Types
Use Service Builder to maintain associations
Enable navigation from one entity to another based
on association
Automatic generation of associations in model
provide class (MPC) and metadata
© 2012 SAP AG. All rights reserved. 9

10. Service Builder – Runtime Artefacts
NetWeaver System containing IW_BEP
Registered Service Registered Model
Name Name
Data Provider Model Provider
Base Class Base Class
External Service
Name Data Provider Model Provider
Class Class
Gateway Service
© 2012 SAP AG. All rights reserved. 10

11. Demo
© 2012 SAP AG. All rights reserved. 11

12. Use Case 1: RFC/BOR Generator
Import from data source:
1. Create an entity “Account” from BOR Object
Account
BP ID*
BP Role
Email
Phone
…
2. Service Implementation for Account
© 2012 SAP AG. All rights reserved. 12

13. Use Case 2: Composition
Import from data source: Existing SalesOrder Service:
1. Create an entity “Account” from BOR Object
SalesOrderHeader
0..N
SO ID *
Account Buyer ID
BP ID* …
1
BP Role
Email 1
Phone
…
SalesOrderItem
SO ID*
Item Position*
2. Service Implementation for Account 1..N Product ID
3. Composition with existing “Sales Order” service …
© 2012 SAP AG. All rights reserved. 13

14. Use Case 3: Redefine a Service
1. Create an OData Service from SPI PLM_MAT
2. Redefine interface/metadata
• Select only relevant nodes
• Change labels
• Change External Names
3. Overwrite/ Generate new service for adjusted interface
© 2012 SAP AG. All rights reserved. 14

15. Thank you
What’s new in Gateway SP5?
http://help.sap.com/saphelp_gateway20sp05/helpdata/en/10/2b9c8a863a451ebe6bd4358d9d6adb/
frameset.htm

16. Legal Disclaimer
The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the
permission of SAP. This presentation is not subject to your license agreement or any other service or subscription
agreement with SAP. SAP has no obligation to pursue any course of business outlined in this document or any
related presentation, or to develop or release any functionality mentioned therein. This document, or any related
presentation and SAP's strategy and possible future developments, products and or platforms directions and
functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The
information on this document is not a commitment, promise or legal obligation to deliver any material, code or
functionality. This document is provided without a warranty of any kind, either express or implied, including but not
limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This
document is for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility
for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly
negligent.
All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking
statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.
© 2012 SAP AG. All rights reserved. 16

17. © 2012 SAP AG. All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal
without the express permission of SAP AG. The information contained herein may be Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services
changed without prior notice. mentioned herein as well as their respective logos are trademarks or registered trademarks
of Business Objects Software Ltd. Business Objects is an SAP company.
Some software products marketed by SAP AG and its distributors contain proprietary
software components of other software vendors. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of Sybase, Inc. Sybase is an SAP company.
Corporation.
All other product and service names mentioned are the trademarks of their respective
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,
companies. Data contained in this document serves informational purposes only. National
System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/
product specifications may vary.
VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, The information in this document is proprietary to SAP. No part of this document may be
OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, reproduced, copied, or transmitted in any form or for any purpose without the express prior
RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent written permission of SAP AG.
Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of This document is a preliminary version and not subject to your license agreement or any
IBM Corporation. other agreement with SAP. This document contains only intended strategies, developments,
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. and functionalities of the SAP® product and is not intended to be binding upon SAP to any
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered particular course of business, product strategy, and/or development. Please note that this
document is subject to change and may be changed by SAP at any time without notice.
trademarks of Adobe Systems Incorporated in the United States and/or other countries.
SAP assumes no responsibility for errors or omissions in this document. SAP does not
Oracle is a registered trademark of Oracle Corporation.
warrant the accuracy or completeness of the information, text, graphics, links, or other items
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. contained within this material. This document is provided without a warranty of any kind,
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are either express or implied, including but not limited to the implied warranties of
trademarks or registered trademarks of Citrix Systems, Inc. merchantability, fitness for a particular purpose, or non-infringement.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World SAP shall have no liability for damages of any kind including without limitation direct, special,
Wide Web Consortium, Massachusetts Institute of Technology. indirect, or consequential damages that may result from the use of these materials. This
limitation shall not apply in cases of intent or gross negligence.
Java is a registered trademark of Sun Microsystems, Inc.
The statutory liability for personal injury and defective products is not affected. SAP has no
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for control over the information that you may access through the use of hot links contained in
technology invented and implemented by Netscape. these materials and does not endorse your use of third-party Web pages nor provide any
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, warranty whatsoever relating to third-party Web pages.
StreamWork, 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.
© 2012 SAP AG. All rights reserved. 17