SPIRITTOData

OData
Your ERP, finally scriptable

SPIRITT connects to any OData V2 service, learns its entity sets and rules, then works the records directly: querying, creating, updating and deleting them. It turns SAP Gateway, S/4HANA and other OData V2 back ends into synced data, portals and automations you never had to hand-build.

SPIRITT Workspace input reading Connect me to OData, with the OData icon in a compact app tile.

What you can do with OData.

  • It learns your service first

    SPIRITT reads every entity set, key, field, relationship and write rule before it touches a record.

  • Full read and write

    Filtered queries, single-record reads, partial updates with change protection, deletes and multi-level inserts like an order with its lines.

  • Systems on top of it

    Syncs, portals, data quality sweeps and warehouse loads, built and run by SPIRITT on your schedule.

Get started in three steps.

01

Open your workspace

Start a workspace for the ERP, finance or operations system you want to automate.

A workspace connected to structured data
02

Connect your OData service

Add the HTTPS service URL and the username and password for a service account.

SPIRITT Workspace input reading Connect me to OData, with the OData icon in a compact app tile.
03

Point it at an outcome

Describe the sync, portal or cleanup you want. SPIRITT maps the entities and builds it.

Data, charts, and recurring workflow arrows

Put your ERP data in motion

Questions

OData, with SPIRITT.

01Which systems can SPIRITT reach through OData?+
Any OData V2 service over HTTPS: SAP Gateway and S/4HANA services, plus other ERP and business systems that expose OData V2.
02What can it do with the records?+
List entity sets, read their schemas, run filtered and sorted queries, fetch single records, create records, update fields and delete records where the service permits it.
03Can it create an order with its line items?+
Yes. SPIRITT can create a record together with new related records in one insert, such as an order header and its lines, where the service schema supports it.
04How does it avoid overwriting other edits?+
Updates and deletes accept the record's version tag, so a change fails cleanly if someone else edited the record first. Updates only touch the fields you change.
05How does it know what each service allows?+
It reads the service metadata first: keys, field types, relationships and which entity sets accept create, update or delete. Every action follows those rules.
06What do I need to connect?+
The HTTPS URL of your OData V2 service and the username and password of an account with the permissions your workflows need.
Buy from builders who use what they sellBuilt usingSPIRITT