Data Panda brings your JD Edwards EnterpriseOne or World 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.
JD Edwards started in 1977 in Denver, founded by Jack Thompson, Dan Gregory and Ed McVaney. The product grew on the IBM AS/400 as JD Edwards World and went green-field in the mid-1990s with OneWorld, later renamed EnterpriseOne. PeopleSoft acquired the company in 2003 for around 1.7 billion dollar, and Oracle then acquired PeopleSoft in 2005 for around 10.3 billion dollar. Oracle kept investing in the line: JD Edwards EnterpriseOne is still the modernised flagship and JD Edwards World is still maintained for the AS/400 installed base.
The customers are large manufacturers, EPC contractors, real-estate operators and distributors who run JDE on-prem or in Oracle Cloud Infrastructure and rarely re-platform. The data surface is famously deep: F4101 item master, F4102 item branch, F4211 sales order detail, F0101 address book, F0411 AP ledger, F0911 general ledger transactions, F4311 purchase orders, F3111 work-order parts list, plus the dozens of F-tables behind manufacturing, project costing and real estate. Two decades of CNC customisations, table conversions and Tools Release upgrades sit on top. In a warehouse, JDE becomes the backbone the CRM, the PIM and the project tools line up against, instead of OneView Reporting versus a Cognos workbook versus a controller's spreadsheet.
One consolidated view across every JDE company, business unit and ledger type, not five OneView outputs and a Cognos workbook that disagree.
Keep JDE in sync with the CRM, the PIM and the project tools, without another middleware bolted on top.
Use twenty years of JDE history for forecasting and anomaly detection that runs on the warehouse, not on the production database.
Internal tools on JDE data for people who should not be paying for an EnterpriseOne user licence.
A list of concrete reports, automations and AI features we have built on JD Edwards (JDE) data. Pick the one that matches your situation.
Are our JDE companies and business units closing on the same numbers?
Trial balance, intercompany position and FX translation per company and business unit on one view, reconciled against the group consolidation. Flags the company whose result is carrying a trend that disappears into the group number before the audit spots it, instead of waiting for the controller who runs the slowest OneView output.
Where is the item master drifting across branch plants?
F4101 attributes and F4102 item-branch records compared across branch plants, the PIM and the ecom channels. Surfaces SKUs where cost, UOM, lot control or category code differs by branch, so picking errors and a wandering consolidated COGS stop looking like a mystery.
How does a CRM opportunity become posted revenue in JDE?
Salesforce or Dynamics opportunity tracked to a JDE F4211 sales order line, shipment, F03B11 invoice and cleared payment posted to F0911. Elapsed days at each hop reveal where the commercial-to-operational handoff stalls, per rep, item and company.
Group P&L, intercompany elimination and working capital across every JDE company and business unit, without the Excel merge on the fifth. Close stops waiting on the controller whose OneView Reporting batch took all night.
Pipeline-to-order-to-invoice timing per rep, item and company, tied back to the CRM. Forecast accuracy is checked against F0911 posted revenue, not against CRM stage optimism.
Manufacturing throughput, project commitments, supplier reliability and inventory turns across every branch plant and company. Planning runs on the group view, not on one planner's saved JDE inquiry.
Closed-won Salesforce opportunities drop into JDE as F4211 sales order lines in the right company and branch plant, with customer mapped to F0101 address book and items to F4101. Invoice status from F03B11 and payment from F0911 flow back to the opportunity, so enterprise sales and group finance read the same cycle.
Groups carving out a business unit or migrating one region from JDE to Dynamics 365 F&O end up running both for years. We line up F0911 against MainAccounts, F0101 against CustomersV3 and F4101 against ReleasedProductsV2, so the group result and the item master agree across both ERPs while the carve-out plays out.
Akeneo PIM attributes, variants and enrichment state flow into JDE as F4101 master records and F4102 item-branch records with units, category codes and costing in the right place. Item-master drift between PIM, JDE branch plants and the ecom channels gets caught before it shows up as a picking error or distorted COGS.
HubSpot deals that reach closed-won create a JDE quote or F4211 sales order in the right company, with customer mapped to F0101 and item to F4101. Invoice and cash status flow back to HubSpot, so marketing reports ROI against posted JDE revenue, not against a forecast number that never clears.
You keep the reporting tool you already have. We connect it to the warehouse where your JD Edwards (JDE) data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
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.
Yes. EnterpriseOne is the modernised line on Oracle Database or SQL Server, accessed through the AIS REST services or by reading the underlying database. JD Edwards World runs on the IBM AS/400 (now IBM i) against DB2, and we read its physical files through the same warehouse pipeline. Both produce the same F-table model in the warehouse, so reporting does not have to know which side a row came from.
Custom tables, custom columns on standard tables and category-code repurposing all come across as first-class fields. Because the warehouse model documents what each field means at extract time, reports keep working when an applications release or a Tools Release upgrade renames or refactors something underneath. The upgrade conversation stops being held hostage by a dashboard nobody wants to break.
Every company, business unit, ledger type and category code on F0911, F4211 and F4101 comes through as a first-class column. Reporting can stay per business unit for local controllers, roll up by company or region, or consolidate to group with FX translated at the rates JDE itself used.
We review your JD Edwards (JDE) setup and the systems around it. Together we pick the first thing worth building.