Retiring Oracle EBS means preserving agreed historical records and usable access before removing the source application dependency. For this scenario, prioritise journal-to-subledger relationships, supplier invoices and accounting context. Compare required reports and documents with source evidence, test permissions and obtain business acceptance before scheduling shutdown.

This guide covers the retirement questions, a mock-data ArchiveHub demonstration and the validation work needed to define a project scope.

What keeping EBS around actually costs

Cost categories are a discovery checklist, not a guaranteed savings calculation. Verify support status, deployment, shared infrastructure and contract terms for the actual installation.

An inquiry-only EBS instance can retain significant operating costs. Assess the following against the actual configuration and contracts:

  • Oracle Database licences and support, usually on processor metrics sized for a production workload that no longer exists.
  • DBA and Apps DBA effort: patching, cloning, AutoConfig, the concurrent managers, the Forms and WebLogic tiers, and the backups.
  • An ageing technology stack. Operating systems, Java and browser plugins move on; the old instance either keeps being upgraded or becomes a security exception.
  • Audit access workarounds. Auditors need responsibilities created, read-only menus built, and someone who still knows how to navigate Account Analysis or drill from a GL journal to Subledger Accounting.
  • People. The functional consultants who understand the Accounting Flexfield, multi-org and SLA are expensive, and fewer of them want to keep an old release alive.

Scope, versions and evidence

This is an illustrative workflow, not a customer case study. Confirm the source release, deployment, modules, customisations and extraction permissions before using the mappings below. Tables and report labels describe the demonstration catalogue; native-report equivalence has not been independently certified. Use agreed source reports and representative records for acceptance testing.

An archive is not a replacement for every operational feature of the retired ERP. Document required historical tasks, excluded functions and any archive-derived calculations.

Historical data to scope for Oracle EBS

The archive preserves the agreed EBS tables, keys and business relationships. Familiar field names help experienced users, but archived workflows and calculations must still be demonstrated and accepted.

General Ledger. GL_JE_BATCHES, GL_JE_HEADERS and GL_JE_LINES carry every journal, GL_BALANCES every period balance per ledger, account and currency. GL_CODE_COMBINATIONS and FND_FLEX_VALUES_VL keep the Accounting Flexfield readable, GL_LEDGERS and GL_PERIODS the ledger and calendar context, and GL_BUDGETS, GL_BUDGET_VERSIONS and GL_BUDGET_INTERIM the budgets.

Subledger Accounting. XLA_TRANSACTION_ENTITIES, XLA_EVENTS, XLA_AE_HEADERS and XLA_AE_LINES, joined to the GL through GL_IMPORT_REFERENCES. The drill from a journal line back to the invoice, receipt or asset transaction that created it survives the move.

Payables and Receivables. AP_INVOICES_ALL, AP_INVOICE_LINES_ALL, AP_INVOICE_DISTRIBUTIONS_ALL, AP_PAYMENT_SCHEDULES_ALL, AP_CHECKS_ALL and AP_INVOICE_PAYMENTS_ALL; RA_CUSTOMER_TRX_ALL with its lines and RA_CUST_TRX_LINE_GL_DIST_ALL distributions, AR_PAYMENT_SCHEDULES_ALL, AR_CASH_RECEIPTS_ALL and AR_RECEIVABLE_APPLICATIONS_ALL.

Trading Community Architecture. HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_PARTY_SITES, HZ_LOCATIONS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL and the customer profiles, plus AP_SUPPLIERS and AP_SUPPLIER_SITES_ALL.

Assets, Projects, HRMS and Payroll. FA_ADDITIONS_B, FA_BOOKS, FA_DEPRN_SUMMARY, FA_DEPRN_DETAIL and FA_DISTRIBUTION_HISTORY; PA_PROJECTS_ALL, PA_TASKS, PA_EXPENDITURE_ITEMS_ALL and PA_COST_DISTRIBUTION_LINES_ALL; the date-tracked PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F, PAY_PAYROLL_ACTIONS, PAY_ASSIGNMENT_ACTIONS, PAY_RUN_RESULTS, PAY_RUN_RESULT_VALUES and PAY_COSTS.

Supply chain. PO_HEADERS_ALL down to PO_DISTRIBUTIONS_ALL, RCV_SHIPMENT_HEADERS and RCV_TRANSACTIONS, OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL, MTL_SYSTEM_ITEMS_B and CST_ITEM_COSTS.

Preserve operating-unit identifiers such as ORG_ID where present, and validate ledger, organisation and shared-data relationships for the selected tables. Every column keeps its Oracle name and a plain-English description, which means the ad-hoc query builder speaks the same language as your old SQL scripts.

Just as important, the joins between modules are kept. A Payables invoice still leads to its XLA accounting event, its subledger journal entry and the GL_JE_LINES row it was transferred into; a receipt in AR_CASH_RECEIPTS_ALL still shows the transactions it was applied to; a depreciation run in FA_DEPRN_SUMMARY still ties to the reserve account in GL_BALANCES. That chain is what an auditor actually walks, and it must be deliberately reconstructed and validated. CSV can retain keys, but files alone do not provide a navigable business workflow.

Explore the demonstration

Account Analysis list in ArchiveHub Account Analysis: GL journal lines by account combination, with source, category and period, as in the EBS report. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Account Analysis detail page Account Analysis detail: a single journal line with its batch, header and subledger context. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Invoice Aging Report in ArchiveHub Invoice Aging Report: open Payables invoices by supplier, aged into buckets at the archive cut-off. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Explore the report reference catalogue

These mappings identify intended business workflows, not certified one-for-one equivalents. Confirm availability, source coverage, filters, currencies, dates and calculations for the selected release and implementation.

Finance

  • Account Analysis: reference workflow: General Ledger Account Analysis (journal lines by account).
  • 1099 Payments Report: reference workflow: the Payables 1099 Payments Report (US service suppliers).
  • Invoice Aging Report: reference workflow: the Payables Invoice Aging Report (open invoices at the archive cut-off).
  • Payables to Ledger Reconciliation: reference workflow: the Payables to Ledger Reconciliation Report.
  • Invoice Inquiry (Payables): reference workflow: Payables Invoice Inquiry.
  • Payment Register: reference workflow: the Payables Payment Register / Payments Inquiry.
  • Aging - 4 Buckets: reference workflow: the Receivables Aging - 4 Buckets Report (open items at the archive cut-off).
  • AR to GL Reconciliation: reference workflow: the Receivables AR to GL Reconciliation Report.
  • Receipt Register: reference workflow: the Receivables Receipt Register / Receipts Summary.
  • Transactions Inquiry (Receivables): reference workflow: Receivables Transactions Inquiry.
  • Budget vs Actual Inquiry: reference workflow: GL Account Inquiry, Budget vs Actual (GL_BUDGET_VERSIONS).
  • GL Reconciliation Report: reference workflow: the Cash Management GL Reconciliation Report (bank to GL cash).
  • Bank Statements: reference workflow: Cash Management Bank Statements Inquiry.
  • Journal Inquiry: reference workflow: General Ledger Journal Inquiry.
  • Subledger Journal Entries: reference workflow: the Subledger Accounting Subledger Journal Entries Inquiry (XLA_AE_HEADERS).
  • Tax Reconciliation: reference workflow: the Receivables Tax Reconciliation Report (output tax reconciled to the GL tax account).
  • Trial Balance: reference workflow: the General Ledger Trial Balance (GL_BALANCES).

Assets

  • Asset Inquiry: reference workflow: the Asset Workbench / View Financial Information.
  • Journal Entry Reserve Ledger: reference workflow: the Journal Entry Reserve Ledger Report.
  • Cost and Reserve Summary: reference workflow: the Cost Summary and Reserve Summary Reports (roll-forward to GL).

HR & Payroll

  • Employee Inquiry: reference workflow: HRMS People and Assignment Inquiry (Employee Summary, Terminations).
  • Costing Summary to GL: reference workflow: the Payroll Costing Summary Report reconciled to General Ledger.
  • Payroll Register: reference workflow: the Payroll Register Report / Statement of Earnings.

Projects

  • Expenditure Inquiry: reference workflow: Projects Expenditure Inquiry (Expenditure Items).
  • Project Status Inquiry: reference workflow: Project Status Inquiry (capital projects).

Purchasing

  • Purchase Order Summary: reference workflow: the Purchasing Purchase Order Summary.
  • Supplier Inquiry: reference workflow: Supplier Management Supplier Inquiry.

Sales

  • Customer Inquiry: reference workflow: Trading Community Customer Inquiry.
  • Sales Orders: reference workflow: Order Management Sales Orders.

Sales & Purchasing

  • Item Inquiry: reference workflow: Inventory Item Inquiry (Master Items).
  • Uninvoiced Receipts Report: reference workflow: the Purchasing Uninvoiced Receipts Report (tying to the GL accrual account).

Source documents stay attached

Document types below illustrate the intended scope. Include source attachments and external repositories explicitly, and test retrieval and record linkage before decommissioning.

Archived records carry the documents that backed them. Payables invoices open with the scanned supplier invoice, Receivables transactions with the invoice that went to the customer, purchase orders with the printed PO. Bank statements, customer and supplier records, employee records, assets and projects also keep their attachments, subject to successful extraction, linkage and retrieval validation. Retire an external document repository only after confirming no remaining dependencies.

Beyond the reports

Confirm these capabilities, configuration requirements and limits during the demonstration and scope review; the report catalogue alone does not validate them.

  • Ad-hoc query builder over the configured archived tables, with Oracle column names, descriptions and suggested joins (for example GL_JE_LINES to GL_CODE_COMBINATIONS, or AP_INVOICES_ALL to AP_SUPPLIERS).
  • Retention rules and purge with approval, so data leaves only when policy says so and someone has signed off.
  • Legal hold on records that must not be purged.
  • Personal-data governance: agree the lawful retention, access and deletion requirements with the responsible privacy and records teams. Product features alone do not establish regulatory compliance.
  • Access controls: define and test permissions for the required companies, records and sensitive fields. Do not assume that system-level roles reproduce the original ERP permissions, particularly for payroll and HR data.
  • OData feeds to Excel, Power BI and SAP Analytics Cloud.

How the decommissioning project runs

  1. Extract the EBS tables with their native names, keys and descriptions.
  2. Validate row counts per table, then tie the numbers out: opening balances plus scoped posted journal movements to closing balances, matching ledger, currency, period and posting status, Payables and Receivables to their GL control accounts, Assets to the reserve and cost accounts, the trial balance to the last one the instance produced.
  3. Run in parallel. Finance, audit and tax users answer real questions in ArchiveHub while the instance is still available, and compare.
  4. Retire after acceptance. Obtain documented sign-off for data reconciliation, document retrieval, user access, retention and legal holds, recovery and remaining integrations. Retire only the approved components; shared infrastructure may still be needed. End or reduce subscriptions, licences and support only where the contract permits. Budget for archive operation and any residual costs.

Shut the instance down

If your EBS environment now exists mainly to be looked at, we can show you its General Ledger, Subledger Accounting and Payables history in ArchiveHub, in the terms your team already uses.

Questions about Oracle EBS retirement

What must survive an EBS journal-to-invoice drill-down?

Include the agreed journal, subledger accounting and source-transaction identifiers, together with lookup meanings and documents. Prove the relationship on representative transactions; copying journal lines alone does not prove the drill-down.

How should EBS balances be reconciled?

Compare opening balances, posted movements and closing balances for the same ledger, currency and period. Document adjustments, posting-status filters and excluded modules rather than comparing unscoped table totals.

What does this ArchiveHub demonstration prove?

The screenshots illustrate how selected records can be presented using mock data. They do not prove production completeness, customer outcomes or parity with every Oracle EBS report. Request a demonstration against your own approved scope and acceptance cases.

Related retirement resources

For the broader project approach, see Oracle ERP retirement planning. To evaluate how users will find transactions, follow relationships and retrieve documents, explore archived data reporting. These resources complement this Oracle EBS-specific scope rather than replace source-system validation.

Evidence and further reading

The report catalogue and screenshots originate from an internal mock-data demonstration. They are not vendor certification or customer implementation evidence.

Use Oracle application documentation to locate the documentation for the installed release. This is a documentation entry point, not verification of every table or report mapping in this article.

Fixed-price Oracle EBS retirement engagement

ArchiveHub offers a fixed-price engagement for Oracle EBS retirement and historical data access, based on an agreed scope, deliverables and acceptance criteria. Request a scoped proposal covering your source systems, data, documents, reporting and validation requirements. The proposal should specify included services, exclusions, ongoing platform or hosting charges, and how scope changes will be handled.

Discuss your Oracle EBS retirement requirements with ArchiveHub

Oracle E-Business Suite is a trademark of its respective owner. ArchiveHub is not affiliated with or endorsed by Oracle.