New Oracle Pricing Models vs. Legacy JD Edwards Pricing Models
Pricing models are critical when choosing enterprise resource planning (ERP) software. How a software vendor charges for its products can make a big difference to your bottom line, particularly in large organizations where licensing can become complex.
If you’re considering a move to Oracle’s pricing models from JD Edwards, it’s essential to understand the differences between the two and how each may affect your business.
Working with Legacy JD Edwards Pricing Models
The legacy Suite or Solution-based pricing models for JD Edwards involve bundling a group of application modules or systems into a suite or solution, as the name suggests.
These pricing models include several user licenses, such as Named, Moderate, Inquiry, and/or Concurrent. Still, these can allow authorized users to access all modules, regardless of whether they need them.
To remain compliant with your licenses under the JD Edwards model, your organization must take specific steps, including:
- Deploying only the modules included in the purchased suite or solution.
- Ensuring authorized users don’t exceed the number of owned licenses.
- Adding security restrictions on actions performed by Moderate and Inquiry users.
Working with the New Oracle Pricing Models
In contrast, current Pricing Models for Oracle offer more flexibility. Application User licenses are authorized for a specific module, while Custom Suite Users are allowed for multiple modules within a suite.
It’s important to control who has access to what under this model. This means adding security restrictions on entire applications to ensure compliance.
It’s worth noting that end-users often assume the current Custom Application Suite model works in the same way as legacy models, but that’s not the case. You must take specific actions to adjust your EnterpriseOne or World installation to the correct model.
Ensuring Your Compliance with Oracle’s Pricing Models
To ensure compliance with Oracle’s pricing models, there are several steps you need to take.
- Ensure that only the modules you own are deployed.
- Create the correct number of user accounts and filter the menu to grant access only to relevant components.
- Add application security restrictions for current pricing models and action security restrictions for legacy models.
If you’re considering a move to Oracle’s pricing models from JD Edwards, it’s essential to understand the differences between the two. Oracle’s current pricing models offer more flexibility, but that doesn’t mean they’re simpler.
To remain compliant and avoid licensing issues, you must take specific actions to adjust your EnterpriseOne or World installation to the correct model.
By taking these steps, you can ensure you’re getting the most out of your ERP software while complying with licensing requirements.