SAP Gateway and OData Inroduction

By

 SAP Gateway Introduction

The growth of the mobile device sector is driving the demand for new innovative applications for business and enterprise.

SAP Gateway is an innovative solution for simple and robust business enterprise mobile access.

SAP Gateway provides simple, secure, and controlled access to SAP data via an open standard, abstracting the specifics of the SAP Business Suite systems.

Key Challenges in Enterprise Computing for Business Consumers


The problem in the past was that for different consumers a developer had to build a specific integration scenario that used its own protocol. However, one-off applications specific to each device or platform were not transferable. For example, a solution built for browser-based applications could not be used for the integration of enterprise software. The solution is to use one protocol, the OData protocol.

The Solution: OData





SAP Gateway is a layer between the channels (devices, applications, etc.) and the SAP Business Suite systems—more specifically, SAP NetWeaver ABAP-based systems. This layer allows you
to mask the sometimes-complex processes and data structures in the SAP Business Suite systems and present them to the outside world in a simplified way. In addition, SAP Gateway unifies access to SAP Business Suite data and processes via the OData protocol and thus opens the SAP world to virtually any developer who understands OData. Knowledge of SAP specifics isn’t required.

OData was originally invented by Microsoft and shared through the open specification promise. It has become an industry standard; the latest version, version 4 is an OASIS standard, which is now driven by SAP, Microsoft, IBM, and a number of other companies. SAP Gateway is used by SAP Business Suite and SAP S/4HANA to publish OData services built on top of the ABAP application server. SAP Gateway enables the consumption of SAP Business Suite and SAP S/4HANA data for people-centric applications across multiple channels.

What is OData?
The most important point is that the OData service forms a kind of contract between the non-SAP side and the SAP side, helping to bring together developers on both sides.

OData Benefits
Based on Representational State Transfer (REST), OData provides compelling benefits for
SAP application development.

  • It is relatively lightweight and builds on the HTTP protocol allowing database-like access to data via the web.
  • The standard address representation or resource is the Uniform Resource Identifier (URI).
  • OData supports two formats for representing the resources it exposes; the XML-based AtomPub format and the JSON format.
SAP Gateway Architecture
SAP Gateway 2.0 is technically based on ABAP add-ons that are deployed to the SAP NetWeaver stack (7.0, 7.01, 7.02, and 7.31).

There are add-ons that provide the SAP Gateway Server functionality (GW_CORE and IW_FND) and there is an add-on (IW_BEP) that provides the SAP Gateway back-end functionality. The add-on IW_BEP is deployed on the SAP Business Suite back end because that is where the service development takes place.

With SAP NetWeaver 7.40, the software components of these add-ons are delivered as part of the SAP Basis in a single software component, SAP_GWFND. This means that the software components for the back-end functionality, as well as the software components for the SAP Gateway server functionality, are available on every system running on top of SAP NetWeaver 7.40.



Deployment Scenarios:
SAP Gateway is usually deployed in one of three ways: 
  1. Central hub deployment
    1. Development in Back End
    2. Development in the Hub
  2. Embedded deployment
  3. Using SAP Cloud Platform OData Provisioning.



Comments

Post a Comment

Popular posts from this blog

Exception handing in OData

By
Image
SAP provided below 2 Interfaces and 2 Classes to handle the exceptions in OData. /IWBEP/IF_MESSAGE_CONTAINER /IWBEP/IF_MGW_CONTEXT /IWBEP/CX_MGW_BUSI_EXCEPTION /IWBEP/CX_MGW_TECH_EXCEPTION     Example: DATA(lo_msg_container) = mo_context->get_message_container( ). SELECT SINGLE * FROM qals INTO @DATA(ls_qals) WHERE prueflos EQ @iv_prueflos.  IF sy-subrc NE 0. METOD 1: Just raise an exception but don't handle it (no parameters)          RAISE EXCEPTION TYPE /iwbep/cx_mgw_busi_exception.  The output will be as follows: Method 2: Using Message Container raising and handling the exceptions using the interface reference as importing parameter.       lo_msg_container->add_message_text_only(         EXPORTING           iv_msg_type = 'E'           iv_msg_text = |Inspection Lot { iv_prueflos } is invalid| ).       RAISE EXCEPTION TYPE /iwbep/cx_mgw_busi_exception         EXPORTING           message_container = lo_msg_container.     ENDIF. Method 3: BUSINESS_ERROR Raising and
Read more

ALV reort using CL_SALV_TABLE

By
Image
 REPORT ztest_pr.  TABLES: afko.  TYPES: BEGIN OF ty_final,           aufnr TYPE afko-aufnr,           matnr TYPE resb-matnr,           auart TYPE aufk-auart,           abjnr TYPE aufk-objnr,           aufpl TYPE afvc-aufpl,           aplzl TYPE afvc-aplzl,           vornr TYPE afvc-vornr,           arbid TYPE afvc-arbid,           steus TYPE afvc-steus,           objnr TYPE afvc-objnr,           stext TYPE bsvx-sttxt,         END OF ty_final.  DATA: lt_final TYPE TABLE OF ty_final,              ls_final TYPE ty_final.  DATA: lv_stext LIKE bsvx-sttxt.   SELECT-OPTIONS: s_aufnr FOR afko-aufnr. ******************************************************** * Class Definition ********************************************************  CLASS lc_salv DEFINITION.    PUBLIC SECTION.      METHODS: fetch_data,               create_salv_obj RAISING cx_static_check ,               display_toolbar,               set_layout,               set_column_attr RAISING cx_static_check,               event_handle_
Read more