JD Edwards User Defined Code Change Log Worksheet
User defined codes drive dropdowns, validations and business rules across JD Edwards. Because they live in control tables, one environment can drift away from another quietly. A simple change log shows what exists where.
| Product code | UDC type | Code value | Description | Action | DV | PY | PD | Requested by | Reason | |
|---|---|---|---|---|---|---|---|---|---|---|
Example codes are illustrative. User defined codes are maintained per environment in the control tables, so changes made in one environment do not appear in another until you repeat or migrate them. Use your own product codes and types.
Compare JDE control data across environments
Optional: ask how UDC and control table differences could be reported automatically.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
Add a row for every UDC value you add, change or retire. Record the product code, UDC type, code value, description and the reason. Then mark the status in each environment as you apply it. Export to Excel for a review meeting, or filter by pending production changes before a go-live.
- One row per code value.
- Mark N/A when an environment does not need it.
- Review pending items before each promotion.
Why UDCs drift between environments
UDC values are stored in the control tables, accessed through the User Defined Codes application P0004A, and the underlying tables are F0004 for types and F0005 for values. Because they are data rather than objects, promoting an OMW project does not carry them across. Teams must migrate them with a data tool or re-enter them, and a missed value shows up as an invalid code or a failed validation in production.
Impact of a change
Retiring or renaming a code can affect reports, data selection, processing options, order activity rules and interfaces that hard-code the value. Before marking a retire row as done, search objects and integrations for the value and check whether transactions still use it. Prefer a retire date and description change over deleting when history matters.
Common mistakes
Changing a UDC directly in production without recording it, so the next refresh wipes the change. Adding codes in one environment only. Using a code description to hold business meaning that other systems parse. Keep the log, and make the log part of your promotion checklist.
Frequently Asked Questions
Does an OMW promotion move UDC values?
No. UDC values are data in the control tables, not objects. Plan a separate step to copy them, using your data migration tooling or manual entry, and record it in this log.
Which tables hold user defined codes?
Types are held in F0004 and the code values in F0005, with language variants in related tables. The User Defined Codes application P0004A is the normal way to maintain them.
Should I delete a retired code?
Often it is safer to keep it and mark it inactive or change its description, because historical transactions may still reference it. Check usage first and follow your data retention rules.
What if production and test differ?
Compare the two by exporting each UDC type and diffing the results, then decide which is right. After a refresh from production, the test environment will match production again and local test-only values will be lost.
If UDC and control table drift keeps surprising your go-lives, Netray can discuss a read-only comparison of control data between your JDE environments.
Related Tools
JD Edwards Data Dictionary Item Request Template
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.
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 Environment Refresh Runbook Template
A fill-in runbook for refreshing a JDE test or development environment from production: scope, data sources, pre-checks, steps, validation and sign-off.
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.
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 UBE Runtime Log Worksheet
- JD Edwards Go-Live Cutover Plan Worksheet
- JD Edwards Batch Window Runtime Calculator