# JD Edwards Data Dictionary Item Request Template

> Source: https://netray.co/tools/jde-data-dictionary-item-request-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A form for requesting a new or changed data dictionary item: alias, type, size, row and column descriptions, edit rules and where it will be used.

## Category

oracle

## Erp

Oracle JD Edwards EnterpriseOne

## Audience

- JDE developer
- JDE functional consultant
- Data architect

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company name

**Key:** company

**Type:** text

**Default:** Acme Precision Ltd

#### Request type

**Key:** request_type

**Type:** select

**Options:**

- New data item
- Change to existing item
- Retire data item

**Default:** New data item

#### Data item alias

**Key:** alias

**Type:** text

**Default:** XCUSTRF

#### Data type

**Key:** item_type

**Type:** select

**Options:**

- String
- Character
- Numeric
- Math numeric
- Date (Julian)
- General

**Default:** String

#### Size / decimals

**Key:** size

**Type:** text

**Default:** 30 characters

#### Row description

**Key:** row_desc

**Type:** text

**Default:** Customer Reference

#### Column title

**Key:** col_desc

**Type:** text

**Default:** Cust|Ref

#### Glossary

**Key:** glossary

**Type:** textarea

**Default:** Free-form customer reference printed on the pick slip and carried to the invoice. Not validated against any table.

#### Edit rule and UDC

**Key:** edit_rule

**Type:** textarea

**Default:** No edit rule. No user defined code table. Blank allowed.

#### Tables and objects using the item

**Key:** used_in

**Type:** textarea

**Default:** Custom column in sales order detail extension table, form P4210 exit, R42520 version XJDE0001

#### Requestor

**Key:** requestor

**Type:** text

**Default:** S. Khan

**Blocks:**

#### Data Dictionary Item Request

**Body:** Company: {{company}}
Requestor: {{requestor}}
Request type: {{request_type}}

#### Item definition

**Table:**

**Columns:**

- Attribute
- Value

**Rows:**

**0:** Data item alias

**1:** {{alias}}

**0:** Data type

**1:** {{item_type}}

**0:** Size / decimals

**1:** {{size}}

**0:** Row description

**1:** {{row_desc}}

**0:** Column title

**1:** {{col_desc}}

#### Glossary

**Body:** {{glossary}}

#### Edit rules and user defined codes

**Body:** {{edit_rule}}

#### Where it will be used

**Body:** {{used_in}}

#### Review questions

**Table:**

**Columns:**

- Question
- Answer

**Rows:**

**0:** Does an existing data item already meet the need?

**0:** Does the alias follow the site custom naming standard?

**0:** Is the item name unique across systems and tables?

**0:** Will interfaces or reports expose this field?

**0:** Is a table change or index change needed?

#### Approvals

**Signatures:**

- Requestor
- Data architect
- CNC administrator
- Functional lead

**Notes:** Starting point only. Use the data item master application (P92001) to create the item, and follow your own custom naming standards. Check that the alias does not collide with a standard Oracle item or a future release.

## Content

**Intro:** In JD Edwards almost everything starts in the data dictionary: field length, description, edits and help text all live there. A short request form stops duplicate items and badly sized fields from reaching your tables.

**Sections:**

#### How to use the template

**Body:** Complete the request type, alias, data type and size, then write the row description, column title and glossary. Describe the edit rule, any user defined code table, and where the item will be used. Export the form, circulate it for review and keep it with the object change record. Use the review table to challenge whether a standard item can do the job.

**Bullets:**

- Search for an existing item first.
- Follow a custom prefix to avoid clashes.
- Write the glossary for a user who never met the developer.

#### Why size and type matter

**Body:** A data item's size and type flow into every table column, form control and report that uses it. Making a field too short can truncate data, and increasing it later means regenerating table specifications and often changing the database. Choose size from business reality, such as the longest customer reference you actually receive, plus a margin, and confirm with the DBA.

#### Naming and ownership

**Body:** Custom items need a consistent naming convention that cannot collide with Oracle's own items in a future release. Many sites use a reserved prefix for customer-created aliases. Whatever you pick, document it and enforce it in the review. Also record who owns the definition so someone can answer later why a field exists.

#### Common mistakes

**Body:** Reusing a standard data item for a different meaning is a classic one. Others are leaving the glossary blank, forgetting that interfaces and reports share the item, and skipping the review of an edit rule that blocks existing data. Treat the form as a thinking tool, not paperwork.

**Cta:** If you maintain many custom data items and tables, Netray can help document them and map where they are used across objects and interfaces.

**Faq:**

#### Where do I create a data item in EnterpriseOne?

**Answer:** The data item master application, P92001, is used to add and change data items. Access is usually restricted to developers or administrators, so the request form feeds that team.

#### Should I reuse a standard data item?

**Answer:** Only if it truly means the same thing. Reusing an item for a different purpose confuses users and reports, and a future standard change can break it. Create a custom item with a clear name when the meaning is different.

#### Can I change the size of an existing item later?

**Answer:** It is possible, but it ripples into tables, specifications, interfaces and stored data, and may need regeneration and database changes. Settle the size in the request, with a margin.

#### Does this form apply to user defined codes?

**Answer:** Partly. The data item defines the field, and a UDC table gives it allowed values. Record the UDC product code and type in the edit rule box and log changes in the UDC worksheet.

## Search terms

jde data dictionary item form, jd edwards new data item, jde p92001 data item master, jde custom field request, jde data dictionary naming standard, jde user defined code data item, jde add column to table request

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