JD Edwards Data Dictionary Item Request Template
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.
Fill in
JD Edwards Data Dictionary Item Request Template
Data Dictionary Item Request
Company: Acme Precision Ltd Requestor: S. Khan Request type: New data item
Item definition
| Attribute | Value |
|---|---|
| Data item alias | XCUSTRF |
| Data type | String |
| Size / decimals | 30 characters |
| Row description | Customer Reference |
| Column title | Cust|Ref |
Glossary
Free-form customer reference printed on the pick slip and carried to the invoice. Not validated against any table.
Edit rules and user defined codes
No edit rule. No user defined code table. Blank allowed.
Where it will be used
Custom column in sales order detail extension table, form P4210 exit, R42520 version XJDE0001
Review questions
| Question | Answer |
|---|---|
| Does an existing data item already meet the need? | |
| Does the alias follow the site custom naming standard? | |
| Is the item name unique across systems and tables? | |
| Will interfaces or reports expose this field? | |
| Is a table change or index change needed? |
Approvals
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.
Map where a JDE data item is used
Optional: discuss documenting custom data items and their use across objects automatically.
Optional. The tool and every export work without this. No spam.
How to use the template
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.
- 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
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
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
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.
Frequently Asked Questions
Where do I create a data item in EnterpriseOne?
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?
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?
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?
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.
If you maintain many custom data items and tables, Netray can help document them and map where they are used across objects and interfaces.
Related Tools
JD Edwards User Defined Code Change Log Worksheet
Track each UDC value you add, change or retire, which environments it has reached, who approved it and why.
OracleJD Edwards Object Promotion Request Template
A change request form for promoting JDE objects through OMW project statuses and path codes, with testing evidence, package plan and rollback.
OracleJD Edwards Next Numbers Capacity Worksheet
List the next number series you track, their current and ending values and annual volume, and see how many years of headroom remain.
OracleJD Edwards Go-Live Cutover Plan Worksheet
Plan each cutover task with an owner, start hour and duration, and see end times and total window length before the weekend arrives.
More Oracle tools
See all- JD Edwards Document Types Reference (OP, SO, OV, PV)
- JD Edwards UBE Job Scheduling Worksheet
- JD Edwards Table Reference (F4211, F4311, F0101, F4101, F4102)
- JD Edwards Tools Release Upgrade Checklist
- JD Edwards Orchestrator Design Template
- JD Edwards Security Workbench Worksheet
- JD Edwards Environment Refresh Runbook Template
- JD Edwards UBE Runtime Log Worksheet
- JD Edwards Batch Window Runtime Calculator