JD Edwards Glossary

JD Edwards EnterpriseOne (E1)

Oracle's tier-one ERP platform for mid-market and large enterprises, providing integrated financial, distribution, manufacturing, and human capital management modules. Runs on multiple databases (Oracle DB, SQL Server) and application servers.

JD Edwards World

The legacy AS/400-based predecessor to EnterpriseOne. Still in active production at hundreds of organizations worldwide, particularly in manufacturing and distribution. Requires specialized RPG and COBOL expertise for maintenance and customization.

Tools Release

JD Edwards' application development framework version. Tools Releases (e.g., 9.2.8, 9.2.9) deliver platform updates including security patches, UI enhancements, and new development capabilities. Regular Tools Release adoption is critical for maintaining vendor support and security compliance.

ESU (Electronic Software Update)

Oracle's patching mechanism for JD Edwards. ESUs deliver bug fixes, security patches, and minor enhancements. ESU deployment requires testing, validation, and careful change management to avoid regression in customized environments.

CNC (Configurable Network Computing)

The JD Edwards middleware and deployment architecture that manages package builds, server configurations, and application deployment. CNC administration is a specialized discipline requiring deep knowledge of the JDE technology stack.

UDO (User Defined Object)

End-user-configurable components in JD Edwards including watchlists, personal forms, and one-view reports. UDOs enable business user customization without developer intervention but require governance to prevent configuration sprawl.

Orchestrator

JD Edwards' low-code automation platform for building cross-application integrations, automated workflows, and IoT connections. Orchestrations execute business logic across JDE modules and external systems without custom code deployment.

Object Management Workbench (OMW)

The JD Edwards change management tool that tracks all object modifications through the development lifecycle — from check-out through development, testing, and production deployment. OMW enforces change control governance across the JDE environment.

Package Build & Deployment

The process of compiling JD Edwards application changes into deployable packages and promoting them across environments (development → testing → production). Package management is a CNC function that requires coordination between development, QA, and operations.

Data Dictionary

The centralized repository of all data item definitions in JD Edwards. Every field, column, and data element is defined in the Data Dictionary with its type, size, validation rules, and display properties. Changes to Data Dictionary items cascade across all objects that reference them.

Business Functions

Reusable C-language components in JD Edwards that encapsulate business logic. Business functions are called by applications, reports, and integrations to execute calculations, validations, and data operations. Custom business functions require specialized development and testing.

Table Conversions (TC)

JD Edwards batch processing programs used for mass data manipulation — imports, exports, transformations, and migrations. TCs are commonly used during implementations, upgrades, and data remediation projects.

Named Event Rules (NER)

JD Edwards' visual programming language for implementing business logic without C-code compilation. NERs are attached to application events and execute when triggered by user actions or system processes.

JDE to S/4HANA Migration

The platform transition from JD Edwards to SAP S/4HANA. This migration involves data mapping between fundamentally different data models, business process re-engineering, integration redesign, and parallel operation during transition. Typical timelines range from 18–36 months depending on complexity.

JDE to Oracle Fusion Migration

The platform transition from JD Edwards to Oracle Fusion Cloud. While remaining within the Oracle ecosystem, this migration involves moving from an on-premise, highly customizable platform to a cloud-native, configuration-driven SaaS model with different architectural assumptions.

Dual-Stack Operation

Running JD Edwards alongside a target platform (SAP, Fusion) during migration. Dual-stack periods require maintaining operational support for both systems simultaneously, doubling the operational demand on the IT team during the transition window.

Sunsetting

The planned decommissioning of a JD Edwards environment after migration to a successor platform. Sunsetting requires data archival, integration cutover, user transition, and regulatory compliance for historical data retention — a process that typically extends 6–12 months beyond go-live.

Customization Inventory

A comprehensive audit of all modifications made to a JD Edwards environment — custom objects, modified objects, custom reports, business functions, integrations, and workarounds. The customization inventory determines migration complexity and is the single most important input to accurate migration planning.