# JD Edwards World DREAM Writer Version Documentation Template

> Source: https://netray.co/tools/jde-world-dream-writer-documentation-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Document a DREAM Writer program version, its processing options, data selection, sequencing and output in a form that survives staff changes and migration projects.

## Category

oracle

## Erp

Oracle JD Edwards World

## Audience

- JDE World developer
- Business analyst
- JDE World administrator

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company

**Key:** company

**Type:** text

**Default:** Acme Precision Ltd

#### Program ID

**Key:** program

**Type:** text

**Default:** P4210

**Help:** The program the version belongs to.

#### Version name

**Key:** version

**Type:** text

**Default:** ZJDE0001

#### Version description

**Key:** title

**Type:** text

**Default:** Open sales orders by customer, branch plant 30

#### Environment or library

**Key:** env

**Type:** text

**Default:** PRODDTA / PRODCTL

#### Business owner

**Key:** owner

**Type:** text

**Default:** Customer service manager

#### Documented by

**Key:** author

**Type:** text

**Default:** A. Kumar

#### Date

**Key:** date

**Type:** date

**Default:** 2026-10-20

#### Business purpose

**Key:** purpose

**Type:** textarea

**Default:** Used each morning by customer service to review open sales orders and promised dates for branch plant 30.

#### Processing options

**Key:** po

**Type:** textarea

**Default:** Tab 1: Default order type = SO
Tab 2: Print detail lines = 1
Tab 3: Currency mode = Domestic

#### Data selection

**Key:** selection

**Type:** textarea

**Default:** Branch plant EQ 30
Status code last EQ 520
Order date GE prior month start

#### Data sequencing

**Key:** sequence

**Type:** textarea

**Default:** 1. Customer number
2. Promised date
3. Order number

#### Run schedule and job queue

**Key:** schedule

**Type:** text

**Default:** Daily at 06:00 on job queue QBATCH

#### Output and distribution

**Key:** output

**Type:** text

**Default:** Printer outq SALESPRT, PDF emailed to customer service group

**Blocks:**

#### DREAM Writer Version Documentation

**Body:** Company: {{company}}
Program: {{program}}
Version: {{version}}
Description: {{title}}
Environment: {{env}}
Business owner: {{owner}}
Documented by: {{author}}
Date: {{date}}

#### Business purpose

**Body:** {{purpose}}

#### Processing options

**Body:** {{po}}

#### Data selection

**Body:** {{selection}}

#### Data sequencing

**Body:** {{sequence}}

#### Scheduling and output

**Body:** Run schedule: {{schedule}}
Output and distribution: {{output}}

#### Review log

**Table:**

**Columns:**

- Date
- Reviewer
- Finding
- Action

**Rows:**

#### Approvals

**Signatures:**

- Prepared by
- Business owner
- IT approver

**Notes:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How to use the template

**Body:** 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

**Body:** 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.

**Bullets:**

- 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

**Body:** 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.

**Cta:** 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.

**Faq:**

#### What is DREAM Writer in JD Edwards World?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

jde world dream writer documentation, dream writer version template, jd edwards world processing options, jde world report documentation, dream writer data selection, jde world technical specification template, jde world version inventory, world software dream writer

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json