SAP S/4HANA Ballerina Connector

[niveathika]

Description: SAP is a German multinational software corporation that develops enterprise software to manage business operations and customer relations. SAP is particularly known for its ERP (Enterprise Resource Planning) software, which helps organizations integrate and streamline their business processes.

SAP offers a range of software products that cover various aspects of business operations, including finance, human resources, supply chain, manufacturing, and more. SAP's software is widely used by large enterprises and organizations around the world to improve efficiency, visibility, and decision-making.

The aim is straightforward: provide developers with an efficient, streamlined connection to SAP systems using Ballerina. This initiative simplifies integration, enhancing Ballerina's versatility for developers engaging with SAP's advanced solutions.

Our initial focus is on S/4HANA—an ERP suite running on the SAP HANA in-memory database, covering core functions like finance, supply chain, manufacturing, and procurement.

[niveathika]

As the first task we will start will SAP S/4HANA for Procurement Planning API package,

• [ ] How will the package management be for SAP connector. As per SAP documentation this is separate package. Should we have different modules for each package?
• [ ] SCIM API is it common to multiple pckages?
• [ ] Verification of the Open API spec https://api.sap.com/api/SCIMService/overview

[niveathika]

Proposed Design https://docs.google.com/document/d/1-C0MZ8jYEqpSVAGUisZiKnE6T4KmTncXu_sLNiQGja4/edit#heading=h.evbw5icr5p4f

[niveathika]

As per the review of the design doc these are the following pending tasks,

• [x] Support for CSRF token header from the sap client itself.
• [x] Nail down versioning of different SAP ODATA endpoints - We are having different connectors for different APIs
• [x] Look into unsupported constraints and ask for improvement