Integrating with Oracle JDE EnterpriseOne
Overview
Oracle JDE is a comprehensive suite of Enterprise Resource Planning (ERP) software applications. It is widely used by medium to large enterprises to manage business processes across various departments.
The Greenhouse Gas (GHG) Protocol (and other similar protocols) defines three categories of activities that result in emissions:
- Scope 1: Direct Emissions
These are GHG emissions from sources that are owned or controlled by the company. They occur directly from operations or assets the company operates, such as fuel combustion in company-owned boilers, furnaces, or vehicles, emissions from chemical production in owned process equipment, and fugitive emissions from refrigerants or leaks in industrial equipment. - Scope 2: Indirect Emissions from Energy
These are indirect emissions from the generation of purchased electricity, steam, heating, and cooling consumed by the company, such as electricity used to power office buildings, factories, or data centers, purchased district heating or chilled water systems, steam bought from a utility provider. - Scope 3: Other Indirect Emissions
These are all other indirect emissions that occur in the value chain of the reporting company, both upstream and downstream, such as business travel (e.g., flights, hotels), purchased goods and services (e.g., raw materials), transportation and distribution (e.g., freight from suppliers) and waste generated in operations.
The SINAI Data Import API is used to ingest large amounts of business activity data into the SINAI platform in an automated, ongoing basis. Using your system of choice, your IT team exposes the relevant data and our API imports it automatically on a periodic basis. This data is then transformed into greenhouse gas (GHG) emissions, which can be used for sustainability analysis and to develop a decarbonization roadmap.
Sourcing of relevant data from JDE datasets
While every JDE implementation is slightly different, these are the typical tables from which business activity data can be sourced for different GHG emissions categories:
| Scope | GHG category (per GHG Protocol) | Typical activity data in JDE | Key JDE E1 tables you would query |
|---|---|---|---|
| 1 – Direct | Stationary combustion (on‑site boilers, generators) | • Fuel purchase vouchers, PO receipts • Equipment BOM/work‑order fuel issues | F4301 Purchase Order Header, F4311 PO Detail, F0411 AP Ledger, F0911 GL, F4101/F4102 fuel item masters, F4801 Work‑Order Master, F1201 Asset Master |
| Mobile combustion (owned vehicles, forklifts) | • Fleet fuel POs/Vouchers • Equipment usage meters • Vehicle depreciation | F4301, F4311, F0411, F0911, F1310/F13100 Equipment Meters, F1201/F1202 Assets | |
| Fugitive (refrigerants, SF₆) | • Inventory issues of refrigerant gas • Maintenance work orders | F4101 item master (refrigerant SKU), F4111 Item Ledger, F4801 WO Master | |
| Process emissions (chemical processing) | • Work‑orders & routings • Production cost ledger | F4801, F3102 Production Cost, F3002 Bill of Material | |
| 2 – Indirect (energy) | Purchased electricity, steam, heating & cooling | • Utility service POs/vouchers • GL postings by cost centre | F4301, F4311, F0411, F0911 |
| 3 – Value‑chain (15 categories) | 1. Purchased goods & services | • PO headers & lines • Supplier master • AP vouchers | F4301, F4311, F0411, F0101 Supplier AB |
| 2. Capital goods | • Capital asset acquisitions • Fixed‑asset register | F1201 Asset Master, F1202 Balances, F4301/4311, F0411 | |
| 3. Fuel‑ & energy‑related activities (upstream) | • Fuel invoices for generators, fleet, etc. | F4311, F0411, F0911 | |
| 4. Up‑stream transportation & distribution | • Inbound freight costs • Shipment loads | F4960 Load Header, F4961 Load Legs, F4941 Shipment Routing, F4311 freight lines | |
| 5. Waste generated in operations | • Vendor invoices for waste haulage • Work‑order disposal tasks | F0411, F0911, F4801 | |
| 6. Business travel | • Employee expense reports • Corporate card feed | F20111 Expense Report Header, F20112 Expense Report Detail, F09E150 Card Txns | |
| 7. Employee commuting | • Payroll/HR commute allowances • Mileage reimbursements | F060116 Employee Master, F20112 mileage lines, Payroll time‑entry tables | |
| 8. Up‑stream leased assets | • Real‑estate & equipment lease master data | F1501B/F1511B Lease Master & Billing, F1201 assets | |
| 9. Down‑stream transportation & distribution | • Outbound shipments • Billable freight charges | F4201 Sales Order Header, F4211 Detail, F4960/4961 freight, F42119 history | |
| 10. Processing of sold products | • Manufacturing work orders linked to customer • Product routings & BOM | F4801, F3002, F3102 | |
| 11. Use of sold products | • Warranty/service claims • Installed‑base records | F4211 (service doc types), F4801 service WO | |
| 12. End‑of‑life treatment of sold products | • Return‑material authorisations • Scrap adjustments | F4211 (RMA), F4111 item ledger | |
| 13. Down‑stream leased assets | • Lease billings to customers | F1511B Tenant/Lease Billing | |
| 14. Franchises | • Franchise fee GL entries • Contract billing | F5211 Contract Billing Detail, F0911 | |
| 15. Investments | • Equity/loan GL accounts • Subsidiary ledgers | F0911, F0902 balances |
Preparing the datasets
The SINAI Data Import API supports importing tabular datasets from a large array of common enterprise technologies (see supported platforms for details).
While the specific configuration to prepare and export the relevant datasets depends on your JDE platform deployment, your overall IT ecosystem and security guidelines, these are a few options available:
Query / Scheduling tech inside JDE | Export landing zone & matching Fivetran connector | Ease of configuration | Security model | Operational complexity | |
|---|---|---|---|---|---|
1 | Universal Batch Engine (UBE) custom report (RDA or BI Publisher) • Scheduled via EnterpriseOne Batch Scheduler/WSJ | UBE set to Output to CSV or eText file → dropped in print queue path or network/SFTP share → SINAI Data Import API (via SFTP connector) | Moderate: requires report design & version; but no extra tools once set up | Same JDE row security governs the data; SFTP share secured with key‑pair or safelisted IPs | Very stable. Some file cleanup and version management required. |
2 | Orchestrator Studio (Data Request + Groovy step) • Orchestrator Scheduler | CSV/JSON → SFTP folder → SINAI Data Import API (via SFTP connector) | Low‑code, wizard‑driven; nothing to install | Inherits row/column security; SFTP key‑pair or tunnel | One orchestration per view; minor script upkeep |
3 | ReportsNow DAS (designer + “Scheduled Task”) | CSV/XLSX to S3 or SFTP → SINAI Data Import API (via S3/SFTP) | Drag‑and‑drop; power users can own | Uses JDE ODBC security; IAM or SSH keys | Extra Windows service; license cost but rich monitoring |
4 | Oracle materialized views + | Oracle Database SINAI Data Import API pulls the m‑view directly from the Oracle database | One‑time DDL; nothing to code | Direct DB auth (TLS 1.2, SSH tunnel) | DBA skills needed |
We will take it from there
Once a connection is configured, the import process is fully automated. The SINAI Data Import API automatically detects when new datasets are published, imports them and computes the corresponding GHG emissions. Learn more at Automated data flow.
Updated 3 months ago