Historical Reporting and Access After EBS Retirement

Historical access must support the questions users continue to ask. Finance may need to trace a GL balance to journal lines or an AP invoice, Procurement may need a purchase order and its approval history, and Audit may need transaction details with supporting evidence.

EBSArchive provides reports across General Ledger, Payables, Receivables, Cash Management, Fixed Assets, Projects, Purchasing, Inventory, Order Management, HR, and Payroll. Examples include GL Trial Balance, GL Detailed Journal Lines, AP Invoices, AR Transactions, Asset Register, Project Costs, Purchase Orders, Inventory Transactions, Sales Orders, Employee Assignments, and Payroll History. The complete coverage is available in the Oracle EBS Historical Report Catalog .

Reports preserve the business context around each record, including ledger, operating unit, organization, supplier, customer, employee, accounting period, status, audit columns, descriptive flexfields, and accounting flexfield segments. These values allow users to recognize and explain historical transactions using familiar EBS information.

Main reports provide the starting point, while subreports expose supporting detail. A user can begin with a trial balance, invoice, receipt, purchase order, asset, project, or sales order and drill into lines, distributions, payments, accounting, approvals, comments, and attachments.

This structure improves access to high-volume data because users first narrow the results by period, account, organization, supplier, customer, or transaction number before opening detailed records.

The reports use Oracle APEX interactive reporting features, including filtering, sorting, grouping, saved filters, and downloads.

Attachments preserve the evidence behind a transaction. The archive may need invoice images, journal and ledger support, expense receipts, AR receipt documents, purchase order files, requisition documents, contracts, calculations, approval notes, and correspondence. The report catalog includes attachment, comment, and web-link reports across several EBS modules.

EBS attachments stored in database tables can be opened from the related APEX report. MarkView invoices and other third-party documents can be moved to OCI Object Storage, with a mapping table connecting the EBS transaction identifier to the stored file URL.

Documents retained in SharePoint or another centralized document repository can appear in an APEX web-links report. Authorized users can then move directly from the archived transaction to the document in its existing repository.

High-volume reports need predictable response times. Detailed GL reporting may join journal headers, journal lines, code combinations, ledgers, periods, and reference tables across many years of data.

Pre-joined reporting tables created with CREATE TABLE AS SELECT can materialize these joins, descriptions, and flexfield segments before the report runs. Appropriate indexes then support faster searches because the major joins have already been resolved.

Large extracts should run outside the browser request. An asynchronous background job can use DBMS_CLOUD.EXPORT_DATA to write the result to OCI Object Storage, after which APEX provides a secure link for the user to download the file. This supports large audit and reconciliation extracts without slowing normal report pages.

Oracle APEX can use local authentication or enterprise single sign-on through OpenID Connect, OCI IAM federation, and the customer's identity provider. This allows archive access to follow existing sign-in and user-lifecycle policies.

Local or identity-provider groups can map to APEX authorization schemes for application, module, page, and report access. Finance, Procurement, HR, and Payroll users can therefore be restricted to the reports and documents appropriate to their roles.

This access model preserves the separation previously enforced through EBS responsibilities, operating units, business groups, and application roles.

Validation must prove that users can complete real historical inquiries without EBS. Report totals should match the corresponding EBS reports, subledgers should reconcile to General Ledger, and representative transactions should be tested across years, ledgers, operating units, organizations, and statuses. Testing should also cover drill-down paths, attachments, external links, authorization rules, report performance, and large downloads. Finance should trace a balance to its source, AP should follow an invoice through payment, Procurement should review a purchase order and approval history, and Audit should assemble evidence for a prior-period transaction.

The prebuilt report catalog provides a broad starting point, while discovery and business validation determine whether custom reports, schemas, flexfields, localizations, or document integrations are also required. A validated archive gives users secure reports, supporting documents, scalable downloads, and familiar inquiry paths after EBS is retired.