Data Panda brings your SAP S/4HANA data together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your team uses every day.
SAP S/4HANA is SAP's current ERP, built on the SAP HANA in-memory database and sold as a Public Cloud edition, a Private Cloud edition and an on-premise installation. It covers finance and controlling, sales, procurement, inventory, production planning, plant maintenance and project management, with local versions for the tax and reporting rules of more than 1,000 country and industry combinations. In finance, the Universal Journal stores every G/L, controlling, asset and material ledger posting as one line item in table ACDOCA, so the general ledger, cost centres and profit centres are read from one table, with no reconciliation between modules.
S/4HANA exposes its data through released OData APIs for company codes, G/L accounts, journal entry items, business partners, sales orders, outbound deliveries, billing documents, purchase orders, supplier invoices, material documents, cost centres, production orders and enterprise projects. Custom CDS views can be published as extra APIs. We use those interfaces to load the accounting line items, the sales and purchasing flow and the master data into your warehouse, where they sit beside your CRM, your webshop and the reporting tools your teams already use.
One view across every company code, ledger and currency, built on ACDOCA line items instead of exported trial balances.
Keep S/4HANA in step with the CRM, the webshop and the expense tool without another point-to-point interface.
Forecasting and anomaly detection that runs on the warehouse copy, not on the production system.
Small internal tools on S/4HANA data for the colleagues who will never open the Fiori launchpad.
A list of concrete reports, automations and AI features we have built on SAP S/4HANA data. Pick the one that matches your situation.
Do our company codes close on the same numbers as the group report?
Every company code's trial balance comes straight from ACDOCA line items, with ledger, profit centre and currency kept. The warehouse rebuilds the group total from those lines, so a difference between a local close and the consolidated figure points to a specific company code and posting period instead of a spreadsheet version.
Which customers are slow to pay, and did sales know when they quoted?
Open items and cleared payments per business partner, matched to the sales orders and billing documents behind them. The same view shows the CRM opportunity that started the deal, so credit exposure and payment behaviour are visible per account before the next quote goes out.
Where does the order-to-cash cycle lose days?
Sales order date, outbound delivery date, billing document date and clearing date on one timeline per sales organisation, plant and customer. The step that stretches the cycle shows up per team rather than as one average lead time.
Group result, intercompany matching and working capital across every company code, read from the Universal Journal instead of from exported trial balances. Close questions get answered per posting line, not per spreadsheet tab.
Pipeline in the CRM matched to sales orders, deliveries and billing documents in S/4HANA. Forecast accuracy is checked against invoiced revenue per sales organisation, and credit exposure is visible before the quote.
Inventory per plant, production order output and supplier lead times beside the purchasing and sales flow. Planning runs on the group view rather than on one plant's saved report in Fiori.
Closed-won Salesforce opportunities become sales orders in S/4HANA, with the account matched to the right business partner and company code. Delivery status, billing document and cleared payment flow back to the opportunity, so sales and finance read the same order.
Dynamics 365 Sales accounts, contacts and opportunities are matched to S/4HANA business partners, sales orders and billing documents. Customer names in the CRM and customer numbers in SAP stop drifting apart, and account managers see open orders and payment status without an SAP login.
Shopify orders land in S/4HANA as sales orders in the company code and plant that serve that market, with material numbers and tax codes set. Refunds post as credit memos. Webshop revenue ends up in the same ledger as the rest of the group, with no monthly summary import.
Approved Concur expense reports and travel invoices post as journal entries in S/4HANA, with the employee's cost centre or WBS element already assigned. Controllers see travel spend per cost centre in the same report as the rest of the period, and project leads see it on their project.
Groups that run S/4HANA at headquarters and Exact Online in smaller Benelux entities get both ledgers in one warehouse with a mapped chart of accounts. The consolidated P&L covers every entity, and intercompany balances between the two systems are matched before close instead of in an exchanged spreadsheet.
Power BI reads the warehouse model built on ACDOCA, sales documents and material documents rather than querying S/4HANA directly. Reports stay fast during close, one measure definition serves every company code, and the finance and sales dashboards use the same margin number.
Blocked sales orders, overdue purchase orders and journal entries above a threshold trigger a message in the Teams channel of the team that owns them. The person who can fix the issue hears about it the same day, without a daily check of a Fiori worklist.
You keep the reporting tool you already have. We connect it to the warehouse where your SAP S/4HANA data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys. Read our DPA
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
Through the released OData APIs that SAP publishes on the SAP Business Accelerator Hub, such as API_JOURNALENTRYITEMBASIC_SRV for Universal Journal line items, API_SALES_ORDER_SRV, API_BILLING_DOCUMENT_SRV, API_PURCHASEORDER_PROCESS_SRV, API_MATERIAL_DOCUMENT_SRV, API_BUSINESS_PARTNER and API_COSTCENTER_SRV. Where a standard API does not cover a field you need, a custom CDS view published as an OData service closes the gap.
The released OData APIs and custom CDS views work in all three. The difference sits in what else is available: Private Cloud and on-premise systems also allow classic ABAP developments, which some groups use to build their own extraction for very large tables like ACDOCA. Public Cloud limits extraction to the released APIs and to CDS views you publish yourself, so we plan the load around those.
Key user custom fields can be exposed in the released APIs and in custom CDS views, and we carry them across as ordinary columns. Classic Z-fields on on-premise and Private Cloud systems come through a custom CDS view. Either way the field keeps its name in the warehouse, so a report built on it does not break at the next SAP upgrade.
We review your SAP S/4HANA setup and the systems around it. Together we pick the first thing worth building.