Agentic AI Capability

Forty and more kinds of source, one way of registering them.

Your supply chain data sits in ERPs, planning suites, warehouse and transport systems, service tools, lakes, databases, files and web services.

YOUR SOURCE SYSTEMSONE WAY OF REGISTERING THEMWHAT USES THE RESULTSAP S/4HANA · ECCorders · stock · materialsOracle Fusion ·E-Business Suiteorders · items · suppliersPlanning suitesforecasts · planned ordersWarehouse · transportstock · tasks · shipmentsCRM · servicemanagementcustomers · casesLakes · warehouses ·fileshistory · drops · streamsChatLima questionsin plain languageAgents and rulesthe facts for every runSmartAppsapproval screensBI tools and APIsthe same meaning everywhereBack to the ERPwrite-back, confirmed01One connector list40+ kinds of source, eachwith its settings02One connectionaddress, service account,read rights03One descriptionnames, types, keys, counts,sample04One query engineread in place and joinacross sourcesone description · one owner · one access rule for every data set
Many kinds of source, one registration path, one description per data set. The dashed line back to the ERP is the write-back that the owning system confirms.
40+
kinds of source system with a ready connector
product
40+
source systems connected across production estates today
production
3
ways a source is read: in place, a governed copy, or a drop or stream
product
5
systems registered in one morning in the showcase estate
showcase estate
Where this sits

Stage 1 of six: register

Step by step

What a connector does between your question and your system

One translation layer per kind of system; everything above it works the same way.

WHAT ASKS THE QUESTIONChatLimaa question in plainlanguageAn agenta rule that needsfactsA SmartAppan approval screenBI tool or APIthe same meaningLIMA DATA FABRICFederated query engineone question, a query persource, joinedRegistered data setdescription, owner, access ruleConnectorspeaks the system’s owninterfaceTHE INTERFACE THE SYSTEM SUPPORTSReleasedservices andviewsSAPREST resourcesOracle FusionSQLdatabases,warehouses, lakesFiles andstreamsdrops and eventsYOUR SOURCE SYSTEMSSAP S/4HANA ·ECCOracle Fusion ·EBSPlanning ·warehouse ·portalLake · files ·servicesAsked onceOne question or one rule reaches severalsystems, in the words of the ontology.Translated onceThe connector turns that into the calls thesystem understands, under the connection’srights.Supported interfacesEach vendor publishes what may be read and how;Juno uses those published routes.Rows stay putThe rows stay in the system that owns them, andthe answer carries the time it was read.
A connector carries two things: how to reach the system, and how that system describes what it holds. Everything above it stays the same whichever source answers.

Each kind of system publishes its own way in. SAP publishes released services and views for integration. Oracle Fusion publishes REST resources. A warehouse system publishes REST calls; a lake answers SQL; a supplier portal drops a file. A connector holds the settings for one of those kinds.

When a data set is registered, the connector asks the system what it holds and hands the description to the data fabric. When a question arrives, the federated query engine plans the work, sends a query to each source that holds part of the answer, and joins the results in the middle.

The layers above the connector stay the same. ChatLima, an agent, a SmartApp and a BI tool all ask in the words of the ontology, so a question about open purchase order lines reads the same whether the lines sit in SAP, in Oracle or in both.

The layer below stays the vendor’s. Juno uses the routes each vendor publishes and supports, so an upgrade of the source system keeps working. Write-back follows the same principle, through the interface the owning system supports.

The catalogue

What can be registered, and how each kind is read

Nine categories cover the estates we meet; the general connectors take care of the rest.

CategoryExamplesWhat Juno readsHow it is read
ERPSAP S/4HANA · SAP ECC · Oracle Fusion · Oracle E-Business SuitePurchase orders and lines, sales orders, deliveries, stock, materials, suppliers, planned ordersReleased services and views; tables where your team allows it
Planning suitesDemand, supply and inventory planning systemsForecasts, planned orders, exception messages, safety stock and inventory targetsREST resources and published extracts
Warehouse and transportWarehouse management, transport management, carrier portalsStock by location, tasks, handling units, shipments, deliveriesREST resources, files
CRM and serviceSalesforce · ServiceNowCustomers, orders, cases, incidents and the tasks raised against themREST over the system’s own object model
Lakes and cloud warehousesCloud data warehouses and lakehousesHistory at scale, harmonised extracts, measures prepared by your data teamSQL through the warehouse’s own query service
DatabasesPostgreSQL · Oracle · SQL Server · MariaDB · MySQLAny table or view the service account may readSQL
FilesCSV, Excel, XML and JSON on a share, in object storage or over SFTPSupplier confirmations, price lists, uploads from the businessA drop on a schedule, or a direct upload
Streams and eventsMessage brokers and event topicsMovements, confirmations and status changes as they happenSubscribe and land as a data set
Web servicesSupplier portals, marketplaces, internal servicesWhatever the service publishes, with its own authenticationREST, called on a schedule or on demand

The full list with versions and settings lives in the connector list. Product.

SAP and Oracle

The two systems most of the questions land on

Juno reads through the routes each vendor publishes, so an upgrade of the source keeps the connection working.

SystemHow Juno reads itObjects your team will recogniseWhat to agree with your team
SAP S/4HANA · cloud editionsReleased OData services and the views published for integrationPurchase order and schedule line, supplier confirmation, planned order, production order, stock, business partnerWhich communication scenarios the service account holds
SAP S/4HANA private edition · SAP ECCThe same released services, plus direct reads of tables and views where your team allows themEKKO · EKPO · EKET · EKES · MARC · MARD · LFA1 · PLAFThe client, and whether direct table reads are allowed
Oracle Fusion CloudREST resources under the Fusion REST interface, plus the extracts your administrator publishespurchaseOrders · supplyPlans · itemsV2 · inventoryOnhandBalances · suppliersWhich roles the integration user holds
Oracle E-Business SuiteDirect reads of the application tables and views your database team exposesPO_HEADERS_ALL · PO_LINES_ALL · MTL_SYSTEM_ITEMSThe schema, and which views are opened
/sap/opu/odata4/sap/api_purchaseorder_2/SAP S/4HANA: the released purchase order service in OData V4. It succeeds the V2 service, which SAP deprecated with release 2308.
I_POSupplierConfirmationAPI01SAP S/4HANA: the released view behind supplier confirmations, which became a business object of its own with release 2111.
/fscmRestApi/resources/11.13.18.05/purchaseOrdersOracle Fusion: the purchase order REST resource. Drafts and change orders carry their own resources beside it.

Read paths shown for orientation; your estate decides which of them is switched on. Product · dated vendor documentation, checked 19 September 2026.

Three ways to read

In place, as a governed copy, or as a drop

The mode belongs to the data set, so one project can mix all three.

Read in placeJuno queries the rows in the system that holds them and joins across systems in the federated query engine. This is the default, and it is how an answer stays as current as the source.
A governed copy in your lakeWhere history at scale is needed, or a source answers slowly, the Lima Quanta lands a governed copy in your own lake on a schedule. Juno reads it there, under the same owner and the same access rules.
A drop or a streamFiles arrive on a schedule and events arrive as they happen. Both land as registered data sets with a description, an owner and an access rule, like any other source.

The mode is set per data set and can change later. Product.

The running example

Monday morning: five systems, four different routes in

Showcase estate.

The running example

The showcase estate holds SAP S/4HANA for the main business, Oracle Fusion for an acquired division, a planning suite, a supplier portal and a lake. Four routes in were needed before L. Tan could ask her question.

SAP answered through its released services and the purchasing views. Oracle Fusion answered through its REST resources once S. Iyer granted the integration user the purchasing roles. The planning suite gave a published extract of planned orders and exceptions. The supplier portal dropped a daily file of confirmed ship dates at 06:00. All four arrived in the same project, with one description each.

Next capability

Questions and agents on data that stays in place

How one question becomes a query per source, how the results are joined, and when a governed copy is the better choice.

Terms on this page
ConnectorThe settings and the code that reach one kind of source system and read what it holds.
Released serviceAn interface the system’s vendor publishes for integration and supports across upgrades.
REST resourceOne addressable object in a system’s web interface, such as a purchase order or an item.
Governed copyA scheduled copy of a source in your own lake, with its owner, its refresh and its access rule.
Read modeHow a data set is read: in place, as a governed copy, or as a drop or a stream.
Questions
Which SAP releases can you read?

SAP S/4HANA in its cloud and private editions, and SAP ECC. Cloud editions are read through released services and published views; the private edition and ECC add direct reads of tables and views where your team allows them.

Our system sits outside your list. What then?

Anything with a database, a REST interface, a file drop or a message topic can be registered through the general connectors. The named connectors add ready settings for systems we meet often.

Does Juno write to these systems as well?

Agents write through the interface the owning system supports, switched on per application after a confirmed test write. The system runs its own checks and its acknowledgement is kept with the action.

How much runs in production today?

More than 40 source systems are connected across production estates, with 60 GB under management and over 200 active business users.

In the platform

Where Juno sits among the four capabilities

Each one builds on the one before it.

One shared foundationCatalogLineageAccess policyWrite path

See Juno answer and act on your own data

Bring two systems and one decision your planners make every week. In the first week we register the data, confirm the mapping with your team, answer your questions in ChatLima and run the first agent at the level you choose.