JD Edwards Object Promotion Request Template
Object Management Workbench makes it easy to move objects. It does not make the decision to move them. This template records why the change is needed, what is touched, how it was tested and how to back it out.
Fill in
JD Edwards Object Promotion Request Template
Object Promotion Request
Company: Acme Precision Ltd OMW project: CUST_PICKSLIP_FIX Request date: 2026-10-26 Requestor: S. Khan, developer Promote from: Development (DV) Promote to: Prototype (PY)
Reason for change
Pick slip does not print the lot number for lot controlled items. Business users need lot numbers on the shipping paperwork.
Objects included
R42520 version XJDE0001 (custom print layout) P4205 form change N4200050 business function change
Impact assessment
| Area | Impact (Yes / No) | Detail |
|---|---|---|
| Other objects that call these objects | ||
| Processing options or data selection changes | ||
| Table or index changes | ||
| Security or menu changes | ||
| Interfaces, EDI or integrations | ||
| Data dictionary or UDC changes |
Testing evidence
| Test | Environment | Tester | Result | Date |
|---|---|---|---|---|
| Unit test of changed object | ||||
| Regression of dependent objects | ||||
| User acceptance |
Deployment and rollback
Package or deployment plan: ______________________ Planned deployment window: ______________________
Rollback plan: Redeploy the previous package. Restore previous object versions from the last approved project in Object Management Workbench.
Approvals
A starting point for your own change control, not a vendor form. Adapt statuses and path codes to your OMW workflow. Keep evidence attached to the change record.
Speed up JDE change documentation
Optional: see how impact lists and change notes can be drafted from your object library.
Optional. The tool and every export work without this. No spam.
How to use the template
Fill the header, describe the reason in business terms, and list every object in the OMW project with its version. Export the document, complete the impact and testing tables, and collect the signatures before the project is moved to the next status. For production, attach it to the change ticket so auditors can trace who approved the change and when.
- List objects and versions, not just the project name.
- Record the package plan and the window.
- Keep the rollback plan specific.
Why the impact table matters
A change to a business function or table can affect many other objects and interfaces. A processing option change can alter behaviour without any code changing. The impact table forces someone to ask about callers, security, menus, integrations and data dictionary items before promotion, when it is cheap to fix. Where a question is truly unknown, write unknown and find out.
Rollback in practice
A rollback plan that says restore the old version is only useful if the old version is known. Record the previous project, the version of each object and whether a full or update package is needed to undo the change. Table specification changes are harder to reverse than object changes, so call them out and agree a database-level plan with the DBA.
Common mistakes
Teams promote a project to production without a package slot, then wait days for a build. They test only the changed object and miss dependent forms or reports. They forget to move processing option and data selection changes with the report. The template makes these questions visible.
Frequently Asked Questions
Is this template specific to one JDE release?
No. The structure works for EnterpriseOne releases that use Object Management Workbench and path codes. Adjust status names and the package process to match your tools release and environment layout.
Who should sign the request?
At minimum the developer, a functional lead who tested the business result, the CNC administrator who schedules the package, and the business owner. Add a change manager if you have a formal change board.
Does a small change need the full form?
Use your judgment. A tiny change to a non-critical report may need only the header, objects and testing lines. Anything touching posting, inventory or integrations deserves the full impact assessment.
How should I store the signed copy?
Attach the exported PDF or Word file to the change ticket or the OMW project documentation your team uses. Consistent storage matters more than the tool, since audits ask for the record later.
If your change process around OMW is slow, Netray can help automate impact checks and documentation from your object library and past projects.
Related Tools
JD 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 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 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.
OracleJD 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.
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 Next Numbers Capacity Worksheet
- JD Edwards Batch Window Runtime Calculator