# JD Edwards EnterpriseOne Package Build and Deployment Checklist > Source: https://netray.co/tools/jde-package-build-and-deployment-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Step-by-step checklist for building and deploying JDE packages: pre-build checks, build, deployment, verification and rollback. ## Category oracle ## Erp Oracle JD Edwards EnterpriseOne ## Audience - JDE CNC administrator - JDE developer - Release manager ## Tool **Kind:** checklist **Groups:** #### Before the build **Items:** **Text:** Change requests approved and objects checked in through Object Management Workbench **Critical:** true Objects promoted to the correct path code and transfer activity rules followed Developers confirm no objects are still checked out **Text:** Build window agreed with users and batch schedule reviewed **Critical:** true Disk space on the deployment server and build target confirmed **Text:** Latest backup of central objects and specs taken **Critical:** true #### Define and build the package **Items:** Package type chosen: full, update or partial, with reason recorded Package assembly lists the correct objects and the right path code Build definition parameters checked, including compile options and server list **Text:** Package build run and build log reviewed for errors and warnings **Critical:** true **Text:** Business function compile errors resolved before deployment **Critical:** true #### Deploy **Items:** **Text:** Package deployed to enterprise and logic servers in a planned order **Critical:** true Web servers refreshed or restarted as required by the object types changed Fat client or workstation deployment scheduled if it is still used Server cache cleared as required and processes restarted in a controlled way Deployment location and package name recorded in the change log #### Verify **Items:** **Text:** Smoke tests run for changed applications, UBEs and business functions **Critical:** true Version and processing option settings confirmed in the target path code Key batch jobs rerun in test and output compared Users in the test group sign off Server logs checked for new errors after deployment #### Rollback and close out **Items:** **Text:** Previous package kept and tested as a rollback target **Critical:** true Rollback steps and time limit written before go live Change records closed and OMW project status updated Lessons learned captured for the next build **Scoring Note:** Do not start the build until every critical item in the first group is complete. ## Content **Intro:** In JD Edwards EnterpriseOne, custom objects and Oracle updates reach users through packages. A repeatable package build and deployment routine reduces surprises. This checklist covers the full cycle from object promotion to rollback. **Sections:** #### How to use the checklist **Body:** Copy the list per release or project and tick items as they are done. Critical items should be completed in order. Exporting to PDF or Excel gives you evidence of what was done and by whom, which helps in audits and when something regresses after a release. #### Choosing the package type **Body:** A full package rebuilds all objects of a path code and is used for new environments, tools release upgrades or after major updates. An update package contains only objects you name and is the usual routine choice. A partial package is built from a selected subset and suits specific deliveries. Use the smallest package that meets the need but plan full builds regularly to keep the specs consistent. #### Path codes and promotion **Body:** Objects move along path codes, for example development, prototype, pristine and production. Promotion in Object Management Workbench updates central objects, and packages carry them to servers. Keep the sequence disciplined: building a production package from objects that never passed test is the most common source of regressions. **Bullets:** - Check the package build log for each object type - Remember business functions need compiling on each server platform - Keep ESU and ASU applications separate from custom changes #### Common mistakes **Body:** Deploying during a batch window, skipping the rollback test, building without checking for checked-out objects, and ignoring compile warnings that become runtime failures. Also failing to refresh web caches after UI changes, so some users see old screens. **Cta:** If your release process is slow because of manual comparison work, we can help with automated object comparison and change summaries over your JDE modifications. **Faq:** #### What is the difference between a full and update package? **Answer:** A full package rebuilds every object for a path code and refreshes the specs. An update package carries only the objects you select. Full builds are heavier but remove accumulated inconsistencies, so schedule them periodically. #### Do I need a package for UBE version changes? **Answer:** New or modified versions are also objects and normally need to be in a package to reach the servers, unless you use features that read from central objects. Follow the rule your CNC team set for each path code. #### How long does a package build take? **Answer:** It depends on the number of objects, hardware and compile settings. An update package may take minutes to an hour, a full package several hours. Measure your own builds and plan windows with margin. #### What should I do if a deployment fails? **Answer:** Stop, read the build and server logs, and use the rollback package if users are affected. Fix the cause in a lower path code, rebuild and redeploy. Record the failure in the change record. ## Search terms jde package build checklist, jd edwards package deployment steps, jde update package, jde full package build, jde omw promotion checklist, jd edwards deploy package to enterprise server --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json