
Meet your instructor, a professional with more than 40 years in consumption and integration, and learn migration tools, REST API, and data services for SAP OData and Salesforce API.
Learn how OData provides a robust rest api for SAP backends, enabling platform-independent data access and cross-system integration with json responses across browsers, mobile apps, and Salesforce.
Master create, read, update, and delete operations in SAP OData services and REST API workflows, handling single and multiple records, validations, and basic design considerations for front-end and back-end integration.
Learn to use SAP gateway service builder (segw) to model entities and associations, generate runtime artifacts, implement create, read, update, delete methods, and register and test services.
Explore creating a project with SAP OData services by modeling data in a custom table, mapping fields, and performing read and create operations across frontend and backend systems.
Create data models for entity types in SAP OData services by manual entries, importing structures, or using internal types, then define fields and properties and generate service objects.
Learn how to register a service in SAP OData, create a data model, and manage local data objects across multiple backend systems, configuring the default host and port for testing.
Implement the get entity method by reading the key parameter from the frontend, handling single or multiple key fields, and retrieving the corresponding record using the input values.
Learn how to implement get entity set in SAP OData services, retrieving single records by primary keys or multiple records, with table outputs, a signature button, and important parameters.
Implement create method to accept and map incoming data to a local entity, validate fields, and insert a new record into the database, with CSRF-protected post requests.
Implement the update method to modify an existing record sourced from the frontend within SAP OData services and the Salesforce API.
Implement the delete method by selecting a single record via its primary key, deleting in the grid, and verifying the record disappears after refresh in the SAP OData service workflow.
learn how to use SAP OData query parameters in OData services to refine rest api calls, including $filter, $select, $count, and $expand, with examples of entities and related data.
Learn to implement the $filter parameter in SAP OData services by building date-range options, time formats, and select options, then test the service for correct results.
Explore two options for implementing the $filter method in SAP OData services, comparing performance and complexity when filtering by date ranges and/or multiple conditions, and when to use class-based filtering.
Learn to use the $inlinecount option in SAP OData REST services to retrieve total record counts and display them with data when consuming Salesforce API.
learn to use the $orderby option in SAP OData services to sort by key and multiple fields in ascending or descending order, including a static utility method.
Explore paging in OData by using $top and $skip to limit records per page and fetch the next set, enabling efficient front-end reporting.
Learn to test the get method of SAP OData REST services using Postman, configuring the API URL with the server IP and port, supplying credentials, and interpreting JSON responses.
Learn how to test a post operation from Postman against SAP OData services and Salesforce API, including building the request body, managing CSRF tokens, and validating the 201 created response.
Learn to implement exception handling and display meaningful messages in SAP integration by using message controls, assertions, and REST-based interfaces to surface clear errors across systems.
Learn to integrate an odata service with Excel by connecting, selecting a data set, loading data into a worksheet, and enabling auto refresh for up-to-date records.
Learn to define associations and navigation properties between principal and dependent entities, retrieving header and line item details in a single call.
Implement association and navigation in SAP OData services by coding logic to fetch related entities, handle missing values, and expand data sets for Rest API and Salesforce API integration.
Explore association and navigation in SAP OData services, part 3, implementing get expanded entityset and expanded navigation properties for REST API and Salesforce API integration.
Implement the expanded entity in SAP OData services, defining pilot entities, exposing single funding source details, and building the grid with header and line items, integrating data into the database.
Define a deep structure using local and global extensions, then implement the deep entity with an expanded entity. Deploy and test data flow from backend SAP OData to the frontend.
OData ( open data protocol ) service is a web protocol and one of the common way for communicating with sap backend system with SAP UI5/Fiori or any other third party software's as front end, which works on HTTP(s), e.g salesforce, SAP C4C, CRM, or any other software's , portal.
OData is use to expose the SAP data with any other customer software’s which works on HTTP(S) as well it is use for updating the data into SAP system using ABAP.
Using Odata help us to access sap data from anywhere and from any device. With odata concept, client and server component can be developed independently . It is based on the REST architecture.
Prior to odata developer were using different SAP connectors like java connector , .net, php based connectors to established and communication channel between SAP and other software's. Because of the flexibility of odata service as we can consume it from any application which works on web Odata becomes a preferred way of communication over other methods like, IDOC, REST API, RFC/BAPI etc.
Advantages of OData :
•Odata light in weight
•It is very easy and relatively fast to access data
•We can get output in xml and json
•We can perform all web based methods like, GET, PUT, POST, DELETE and Query.
•Odata known for its stateless functionality, it means for every request from frontend system it gives the response , and server does not save any data. It treats every OData call as a new call.
•We can develop and test OData in sap OData gateway frame work, before giving it to front end developer.
•Due to advantage of complete framework in SAP for odata , compare to normal rest api development with which we do using resource handler class, the coding part is less in Odata
Rest API - Create Sales order with Rest API
Consume Salesforce API in SAP