Understand the basics of SAP Netweaver Gateway Understand OData Channel API basic concept Know the types of SAP Business Content that we can expose as Gateway Services Know the Development Environment’s that SAP developed Gateway plug-ins for Objectives
Agenda Overview Service Modeling Summary
Agenda Overview of Netweaver Gateway Service Modeling Summary
SAP NetWeaver Gateway Devices Enterprise Software Web SRM SCM ERP PLM CRM SAP Business Suite SAP NetWeaver Gateway Open Any Device, Any Experience, Any Platform People Optimized for user interaction scenarios Stateless Non-disruptive, any SAP Business Suite version Developers Simple APIs, no SAP knowledge required Standards Based on the OData protocol (Atom) REST Social Experiences
SAP NetWeaver Gateway Architecture Gateway Core Technology OData with SAP Annotations Network Standards Data Source Providers Tools SAP NetWeaver SAP NetWeaver Gateway Service Adaptation Supportability Monitoring Security SAP Business Suite [ERP,CRM,SRM…] BAPI / RFC Dynpro Data Conn. IDEs Plug-ins Events / Worflow Metadata Repository Consumer Consumer Consumer Generators BOR/SCR/ RFC Custom Dev OData Channel API
Transaction Code is ‘SEGW’ for SAP NETWEAVER SERVICE BUILDER. Using this transaction we create our own OData services with help of RFC BAPI’s also.
SAP NetWeaver Gateway Tools Gateway Core Technology OData with SAP Annotations Network Standards Tools SAP NetWeaver SAP NetWeaver Gateway Service Adaptation REST Supportability Monitoring Security SAP Business Suite [ERP,CRM,SRM…] Data Source Providers BAPI RFC WS Data Conn. IDEs Plug-ins Events Metadata Repository Consumer Consumer Consumer Generators BOR/SCR/ RFC Custom Dev. Tools BOR Generator SCR Generator Generate new Gateway objects from existing BAPIs, RFCs or Dynpros Build custom Gateway object RFC Generator Custom Dev. Benefits Capabilities Does not require coding Well-suited for non-ABAP developers Enables rapid prototyping Create new Gateway objects from existing BOR Objects , RFMs & ABAP Dynpro screens Supports multiple object aggregation Supports adaptation based on client application requirements Generate structures based on underlying data source Support CRUD operations + QUERY Operation Simplification of Service Interface so that no SAP skills required
CRUD Operation with help of OData service
OData + SAP Extensions OData Atom Publishing Protocol Atom Syndication Format What is OData? Based on industry standards – http://www.odata.org REST-based architecture Uses the standard GET, PUT, POST & DELETE HTTP Verbs for CRUD operations Stateless apps. OData APIs Offer database like access to business data – “ODBC for the Web” No knowledge of SAP structures required: Supports object navigation Dynamic binding takes place at run time Gateway Core Technology OData with SAP Annotations REST Service Adaptation Metadata Repository Service Adaptation Supportability Monitoring Security HTTP XML
IDE Plug-Ins [optional] IDE Plug-in tools IDEs Plug-ins Benefits Capabilities Developers require no SAP Knowledge Applicable to client developers In their native [IDE] environment Increase productivity Simplify SAP service consumption IDE plug-In available for Visual Studio, xCode & Eclipse Provide ease of consumption thru search and exploration capabilities on Gateway services Enable proxy generation of Gateway services Application starter kit Support all CRUD operations on Gateway services Push support for xCode , Visual Studio Provide out-of-box security and supportability capability
Agenda Company Profile Overview Overview of Netweaver Gateway Service Modeling Summary
Remote Function Modules Remote Function Modules (RFMs) are based on Function Modules that are enabled for being called Remotely Based on the Remote Function Call (RFC) Protocol All BAPIs are RFC enabled Easy to create RFC enabled Function Modules
Gateway Services Based on RFMs or BOR Objects Overview Gateway Data Models can be created based on RFMs or BOR Objects. Gateway Objects are created in the ABAP Development Workbench – transaction SEGW Once you create the object you can create entity sets or check the checkbox to create entity sets. Once done click on ‘Generate’: Data provider class and Model provider class.
Gateway Service Mapping Tool The Mapping Tool allows you to do the following: Select Data Model operation type being mapped. Flatten structures Rename attributes Simplify the interface Assign constant values to import attributes Assign attributes as key values Change Mapping Route – used to flatten structures, rename attributes, and assign attributes. Set Constant Value – used to assign a constant value an input attribute
OData Service Documents – The Consumption Starting Point After an Entity Data Model has been turned into an OData Service, the Gateway system will provide you with a URL to access this service. When this URL is requested, the Gateway service will respond by sending you the Service Document. The Service Document is a high-level description of the resources exposed by the OData service.
In order to consume an OData service, you should retrieve the metadata that describes the service. This is done by adding the suffix $metadata to the Service Document URL. E.G. http ://primus.sapdemo.com:8000/sap /[...]/ $metadata
Agenda Overview Service Modeling Summary
SAP Netweaver Gateway OData basic concept Expose as Gateway Services Summary
Bibliography Scn.sap.com Help.sap.com Youtube : Ethic Coder abaper.weebly.com OData and SAP NetWeaver Gateway book by Fischer, Drees , Bonnen , Heinz and Vishal Sikka