JD Edwards World DREAM Writer Version Documentation Template
In JD Edwards World, a report or inquiry is usually run through a DREAM Writer version. The version holds the processing options, data selection and sequencing that make one run different from another. This template turns that hidden setup into a document you can review, hand over or use in a migration inventory.
Fill in
The program the version belongs to.
JDE World DREAM Writer Version Documentation Template
DREAM Writer Version Documentation
Company: Acme Precision Ltd Program: P4210 Version: ZJDE0001 Description: Open sales orders by customer, branch plant 30 Environment: PRODDTA / PRODCTL Business owner: Customer service manager Documented by: A. Kumar Date: 2026-10-20
Business purpose
Used each morning by customer service to review open sales orders and promised dates for branch plant 30.
Processing options
Tab 1: Default order type = SO Tab 2: Print detail lines = 1 Tab 3: Currency mode = Domestic
Data selection
Branch plant EQ 30 Status code last EQ 520 Order date GE prior month start
Data sequencing
1. Customer number 2. Promised date 3. Order number
Scheduling and output
Run schedule: Daily at 06:00 on job queue QBATCH Output and distribution: Printer outq SALESPRT, PDF emailed to customer service group
Review log
| Date | Reviewer | Finding | Action |
|---|---|---|---|
Approvals
Copy processing option values from the version's processing option screens and data selection from the selection screen rather than typing from memory. Keep one document per version. Record any customization to the base program separately.
Optional help building a version inventory
If you have hundreds of versions to document, we can discuss reading the setup and summarizing it for review.
Optional. The tool and every export work without this. No spam.
How to use the template
Fill in one form per DREAM Writer version you care about. Start with the program ID and version name, then copy the processing option values, the data selection rules and the sequencing from the version screens. Add the business purpose in a sentence a non-technical manager could read, and the run schedule and output distribution so that the operational dependency is visible. Export the result to PDF or Word and store it with your change records or your migration inventory.
Why versions matter in World
Many World installations contain hundreds of versions created over decades, copied from base versions and slightly changed. The program source is often unchanged, so the behavior sits in the version setup. If the people who created them leave, nobody knows which versions drive month-end, which feed outside spreadsheets and which are dead. Documenting the version captures the logic that a source code review alone would miss.
- Processing options change how a program behaves
- Data selection defines which records are included
- Data sequencing defines order and break levels
- Job queue and output define where the result goes
Using the output in a migration or audit
Once you have versions documented, rank them by use. Check job logs, schedules and user interviews to find which ones are active, then decide for each one whether to replace it with standard functionality in the target system, rebuild it, or retire it. In audits, the same documentation shows who owns a report and what rules it applies. A common mistake is documenting every version equally. Start with those run on a schedule and those used for financial close.
Frequently Asked Questions
What is DREAM Writer in JD Edwards World?
DREAM Writer is the World facility for running programs with saved settings called versions. A version stores processing options, data selection and sequencing, so the same program can produce many different reports without changing code.
Where do I find processing options for a version?
In World, processing options are reached from the version list for the program, typically by a function key or menu option on the versions screen. The exact path depends on your release and menu setup, so check your own screens.
Do I need to document every version?
No. Focus on active versions: scheduled jobs, month-end and financial reports, and anything feeding outside systems. Retire or archive unused versions after confirming with the business owner.
Can this help with a move to E1 or another ERP?
Yes. Documented versions become requirements for the new system, and show which reports can be replaced by standard ones. It also reduces dependence on the individuals who remember the setup.
If your version inventory is large, Netray can discuss ways to extract and summarize version setup into a reviewable list. The template works fully on its own.
Related Tools
JDE World to E1 Migration Readiness Assessment
Ten questions that show how complicated a JD Edwards World to E1 (or other ERP) move will be, based on customization, data, interfaces and people.
OracleJD Edwards World Key File Reference Table
A searchable lookup of widely used JD Edwards World files with the module, purpose and key field prefix, useful for queries, reports and migration mapping.
ERP Migration & SelectionAS/400 Green Screen Modernization Assessment
Find out whether your IBM i green screen applications should be left alone, wrapped with a web or API layer, or replaced, based on 10 practical questions.
Developer ToolsIBM i (DB2 for i) SQL Data Extraction Script Generator
Generate DB2 for i SQL to inspect a file, count rows, and extract records with Julian date filters for JD Edwards World or other IBM i data.
More Oracle tools
See all- JD Edwards World to EnterpriseOne Data Conversion Mapping Worksheet
- JD Edwards World Custom Program and Modification Inventory Worksheet
- IBM i Power Hosting Cost Comparison Calculator
- JD Edwards World Custom Object Conversion Effort Calculator
- IBM i Batch Window Capacity Calculator
- AS/400 Disk Storage Growth Forecast Calculator
- IBM i Restore Time and RTO Calculator
- AS/400 Skills Succession Risk Assessment
- IBM i System Values Reference
New to JD Edwards World? Start with the JD Edwards World guide and toolkit.
Keep exploring
Free tools
- JD Edwards World Custom Object Conversion Effort CalculatorTurn your count of custom RPG programs, DREAM Writer reports, screens and interfaces into build and test hours, cost and elapsed time.
- JD Edwards World Private AI Layer Blueprint GeneratorFill in your JD Edwards World version, database, hosting and users to get a shareable architecture plan for a private, on-prem AI assistant.
- JD Edwards World AI Assistant Sizing and Value CalculatorEstimate peak load, GPUs, index size, hours saved and payback for an on-prem AI assistant on JD Edwards World.
ERP fixes and how-tos
- How to set data selection and processing options in JD EdwardsHow data selection and processing options actually work on a JD Edwards version, how they differ, and how to set them up correctly for a report or batch program.
- How to Add a Private AI Layer to JD Edwards World on IBM iAdd AI to JD Edwards World without moving data: DB2 for i access, journal-based replication, rebuilt row security, local GPUs and approved batch write-back.
- JD Edwards API Documentation: AIS REST, Orchestrator, BSSV and Connector OptionsJD Edwards integration options explained: AIS REST, Orchestrator, business services (BSSV), Z-files and third-party connectors such as Concur, with trade-offs.
Runs with your ERP
- RF-SMART Manufacturing Data Collection for JD Edwards WorldShop floor barcode data collection for JD Edwards World with RF-SMART: what it reports, how it connects, setup steps, pitfalls and a private AI layer on top.
- Vertex Tax Connectors with JD Edwards EnterpriseOneHow Vertex calculates sales, use and VAT tax for JD Edwards EnterpriseOne and World, plus Oracle EBS and Cloud ERP: integration model, flows, setup, pitfalls.
- RF-SMART and JD Edwards EnterpriseOne: Barcode Scanning and Mobile WMSHow RF-SMART connects barcode scanning to JD Edwards EnterpriseOne and World: integration method, data flows, setup steps, pitfalls and where private AI helps.
AI on your ERP
- AI for JD Edwards World on IBM i, without a EnterpriseOne migrationAdd AI to JD Edwards World on IBM i without replatforming: read the physical files safely, ground an LLM on your data, and keep control on the box you already run.
- AI for JD Edwards Inventory Management and Shop Floor ManufacturingAI on JD Edwards EnterpriseOne inventory and manufacturing: item ledger, work orders, MRP messages and cost variances, answered in plain English on your own servers.
Integrations
- How to add WhatsApp to JD Edwards World on IBM iHow to connect WhatsApp Business to JD Edwards World on IBM i: data queues, DB2 for i triggers, template messages, supplier replies and approvals back into World.
- How to add AI agents to JD Edwards World on IBM iHow to add AI agents to JD Edwards World on IBM i: a read-first tool layer over DB2 for i, human approval before any write, and a fully on-prem model option.