Retiring JD Edwards World means preserving agreed historical records and usable access before removing the source application dependency. For this scenario, prioritise ledger types, job costs and property-related documents. 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 JD Edwards World "read-only" really 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.

  • IBM i hardware and its software stack. A machine, an operating system release, maintenance contracts and backups, all kept up for a system nobody posts to.
  • RPG and World skills. The people who can navigate the menus, fix a broken query or explain a DREAM Writer version are retiring, and contractors who know World are scarce and expensive.
  • Licences and support for JD Edwards World and the tools around it.
  • Security and patching on a platform that holds supplier bank details, payroll history and tenant data, often with emulator access that's hard to control.
  • Audit-access workarounds. Auditors get printouts, spool files or screenshots of green screens, with little trace of who saw what.

Turning off the IBM i removes all of these. How much you save depends on your contracts and hardware, so we won't put a number on it.

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 JD Edwards World

ArchiveHub keeps World's data model as World built it: F-numbered files, business units, object/subsidiary accounts, ledger types, document types and pay items. Field names keep their native form and come with descriptions, so a query on GLRCND or a document type RC still works the way it used to.

  • General accounting: F0911 Account Ledger with every G/L transaction, F0902 Account Balances by ledger type (AA actual, BA budget, JA job budget and PA open commitments), F0901 Account Master, F0006 Business Unit Master for companies, departments, communities, lots (jobs) and buildings, and F0011 Batch Control Records.
  • Accounts payable: F0411 A/P Ledger voucher pay items, F0413 and F0414 for payment headers and paid pay items, and F0401 Supplier Master.
  • Accounts receivable: F0311 A/R Ledger with invoices, unapplied receipts and receipt application records, and F0301 Customer Master.
  • Address book and setup: F0101 Address Book Master and F0116 Address by Date, F0005 User Defined Codes, F0010 Company Constants, F0014 Payment Terms, F0030 Bank Transit Master and F4008 Tax Rate/Area.
  • Subcontracts and work orders: F4301 and F4311 for order type OS subcontracts, and F4801 Work Order Master.
  • Real estate management: F1501 Tenant/Lease Master, F1502 Recurring Billings Master, F1507 Unit Master and F1511 Tenant/Lease Billings Detail.
  • Fixed assets, payroll and tax: F1201 Asset Master and F1202 Asset Account Balances, F060116 Employee Master, F06156 Paycheck History, F0618 Timecard / Payroll Transaction History, and F0018 Sales/Use/VAT Tax Detail.

World stores dates as CYYDDD Julian numbers. ArchiveHub shows them as calendar dates and keeps the original values available. The quarter-end A/P and A/R aging tables are rebuilt from F0411/F0414 and F0311, the way World ages them, and are labelled as archive-derived, not native World files.

Explore the demonstration

Account Ledger Inquiry list in ArchiveHub Account Ledger Inquiry: F0911 lines by business unit, object and subsidiary, with document type, G/L date and amount. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Account Ledger Inquiry detail page in ArchiveHub Account Ledger Inquiry detail: a single F0911 line with its batch, document and account context. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

A/P Aging list in ArchiveHub A/P Aging: open supplier pay items by aging bucket as of a quarter end, with retainage shown apart. 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.

General Ledger

  • Account Ledger Inquiry: reference workflow: Account Ledger Inquiry (P09200) and General Journal Review over the Account Ledger file F0911
  • Trial Balance: reference workflow: the Trial Balance Report / Trial Balance by Object from Account Balances F0902 (ledger AA), with closed years rolled forward by the Annual Close
  • Chart of Accounts: reference workflow: Accounts by Business Unit / Account Master (P0901, F0901), with job cost accounts by lot
  • Business Units: reference workflow: the Business Unit Master (P0006, F0006): companies, departments, communities (projects), lots (jobs) and buildings
  • Batch Review: reference workflow: General Journal Review / Batch Review by batch type (Batch Control Records F0011)
  • Budget vs Actual: reference workflow: Budget Comparison / Account Balances by budget ledger BA against actual ledger AA (F0902)
  • Integrity Reports: reference workflow: A/R to G/L Integrity (P037001), A/P to G/L Integrity (P047001) and Asset to G/L Integrity: subledger activity against the control accounts by period

Accounts Payable

  • Supplier Master: reference workflow: Supplier Master Information (P01054): Address Book F0101 and Supplier Master F0401
  • Supplier Ledger Inquiry: reference workflow: Supplier Ledger Inquiry (P042002) / Voucher Entry (P0411): A/P Ledger F0411 pay items
  • Payment Inquiry: reference workflow: Payment Inquiry / the Automatic Payments Check Register (F0413 payment header, F0414 payment detail)
  • A/P Aging: reference workflow: A/P Aging / the Open A/P Summary Report as of quarter end (rebuilt from F0411 and F0414; retainage shown apart)

Accounts Receivable

  • Customer Master: reference workflow: Customer Master Information (P01053): Address Book F0101 and Customer Master F0301 (homebuyers and tenants)
  • Customer Ledger Inquiry: reference workflow: Customer Ledger Inquiry (P032002) and Tenant A/R Ledger Inquiry: A/R Ledger F0311 invoices and unapplied receipts
  • Receipts Journal: reference workflow: the Receipts Journal / receipt inquiry: A/R Ledger F0311 receipt records (matching document type RC)
  • A/R Aging: reference workflow: A/R Aging / tenant and homebuyer aging as of quarter end (rebuilt from F0311 invoices and receipt records)

Job Cost

  • Job Status Inquiry: reference workflow: Job Status Inquiry (P512000): budget (JA), actual (AA), open commitments (PA) and projected final by job and cost code (F0902)

Homebuilding

  • Lot Status & Closings: reference workflow: homebuilder lot status: the job business unit (F0006 type JB) with job dates, job cost, sale and gross margin from the Account Ledger

Subcontracts

  • Subcontract Inquiry: reference workflow: Subcontract Management Contract Status / Contract Analysis (F4301, F4311 order type OS), with progress payments and retainage
  • Retainage Ledger: reference workflow: the retainage report: subcontract retainage pay items held on the A/P Ledger (F0411, G/L offset RETN) by contract and job

Real Estate Mgmt

  • Lease Master: reference workflow: Lease Information / the Lease Master Listing (Tenant/Lease Master F1501), with recurring billings (F1502) and billing history (F1511)
  • Tenant Rent Roll: reference workflow: the tenant rent roll from the Recurring Billings Master (F1502): rent, CAM and real estate tax schedules by lease, unit and effective period
  • Tenant Billings: reference workflow: Tenant/Lease Billings Detail (F1511) from Recurring Billing generation and late fees, with the invoice status in the A/R Ledger (F0311)
  • Unit Master & Occupancy: reference workflow: the Unit Master (F1507), with occupancy at the archive date from the Tenant/Lease Master

Work Orders

  • Work Orders: reference workflow: the Work Order Master (F4801): homeowner warranty and tenant maintenance orders with vendor costs by subledger (F0911 subledger type W)

Fixed Assets

  • Asset Master: reference workflow: Asset Master Information (P1201, F1201), with net book value from Asset Account Balances (F1202)
  • Asset Balances: reference workflow: Asset Account Balances / Depreciation Inquiry (F1202): cost and accumulated depreciation by asset and fiscal year

Cash Management

  • Bank Reconciliation: reference workflow: Manual Bank Account Reconciliation (P09131): cash account ledger lines with the reconciled code (F0911 GLRCND)

Payroll & HR

  • Employee Master: reference workflow: Employee Master Information (P060116, F060116)
  • Paycheck History: reference workflow: the Payroll Register / Paycheck History Inquiry (F06156, prefix YU), with timecard detail (F0618)
  • Payroll Journal Reconciliation: reference workflow: Payroll Register totals (F06156) against the payroll journal entries in F0911 by home business unit and period

Tax

  • Tax Detail: reference workflow: the Sales/Use/VAT Tax Report over the Taxes file F0018

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.

ArchiveHub keeps archived documents linked to their records: vouchers, subcontracts, home sales, leases, and the supplier, asset and employee records. When a homeowner warranty claim or a subcontractor dispute comes up, the signed paperwork is attached to the record it belongs to. Nobody needs to search a file share or a box in storage.

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 World file, with native field descriptions and suggested joins (for example F0411 to F0414 to F0413, or F4311 to F0411).
  • Retention rules with approved purge, so records leave the archive on schedule and never without sign-off.
  • Legal hold on a job, lease, supplier or fiscal year when litigation or an audit is under way.
  • 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 World files come off the IBM i with native file and field names, keys and Julian dates intact.
  2. Validate. Record counts are compared file by file. The trial balance from F0902 must agree with World's, and A/R, A/P and fixed assets must tie to the G/L as World's own integrity reports would show them. Job cost balances by ledger type are checked too.
  3. Parallel read access. Accounting, property management and job cost users work in ArchiveHub while World is still available, and confirm that the answers match.
  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.

The green screens can go

Your World history is decades of careful bookkeeping, and it deserves a better home than an ageing IBM i you only keep for lookups. Move it into ArchiveHub, keep the reports, and turn the machine off.

Questions about JD Edwards World retirement

Does World retirement automatically remove IBM i costs?

No. Other applications may share the platform, and contractual costs may continue. Assess the application, infrastructure and archive operating costs separately before approving a savings estimate.

What should be preserved for historical job or property questions?

Scope the relevant jobs, ledger types, transaction keys and available contracts or supporting documents. Test representative disputes or audit questions against that agreed scope.

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 JD Edwards World 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 JD Edwards World-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 JD Edwards World retirement engagement

ArchiveHub offers a fixed-price engagement for JD Edwards World 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 JD Edwards World retirement requirements with ArchiveHub

JD Edwards World is a trademark of its respective owner. ArchiveHub is not affiliated with or endorsed by Oracle Corporation.