JD Edwards: new vs. legacy pricing models

28 jun '16 - : Andrei Agavriloaiei & Gabriel Dragoi - share: LinkedIN Mail
jd-edwards-new-vs-legacy-pricing-models

There’s a subtle difference between legacy pricing models for JD Edwards and the models used by Oracle today. This difference often accounts for licensing issues with a big impact. 

The legacy Suite or Solution based pricing models involve a group of application modules/systems bundled into a suite or solution (as the pricing model name suggests). In addition to this, there is a number of Named, Moderate, Inquiry and Concurrent user licenses which can be used for the users authorized to access all modules irrespective of the actual modules/systems they need.

To stay in compliance with your licenses in such a scenario, organizations have to:

  • Only deploy the modules included in the suite or solution they purchased;
  • Ensure authorized users don’t exceed the number of owned licenses;
  • Add security restrictions on the actions (add or change) performed by Moderate and Inquiry users.

The current pricing models used by Oracle offer more flexibility. Application User licenses are authorized for a specific module while Custom Suite Users are authorized for multiple modules within a suite. Because of this, it is important to keep a tight control over who has access to what. In technical terms, this translates into adding security restrictions on entire applications (run).

End-users often think that the current Custom Application Suite model works in the same way as legacy models. In reality, this is not the case, and you need to take specific actions to adjust your EnterpriseOne or World installation to the correct model. Make sure that only the owned modules are deployed, create the correct number of user accounts, filter the menu to grant access to relevant components only and add application security restrictions for current pricing models and action security restrictions for legacy models.

In our next article, we will talk about "Program to Price list Module Mapping". More information can also be found in our latest white paper “JD Edwards – License Compliance Risks.” Our new white paper format is mobile friendly, so you can easily read it on your tablet or mobile phone.

Download Our Free White Paper: 
JD Edwards - License Compliance Risks

B-lay helps organizations effectively use and manage their software assets with practical solutions and services. We love helping you avoid costs, so contact us for support on your JD Edwards license issues!

Oracle Database and hardware infrastructure

The required number of licenses for Oracle’s Database programs are (almost) at all times related to the hardware infrastructure on which the software is installed. Incorrect interpretation or understanding of whether the software is deemed to be installed and how the installed software should be licensed in a certain specific hardware infrastructure is by far the number 1 license compliance issue. 

Oracle Database and hardware infrastructure

Download

Fill out this form to download our free whitepaper

Please make sure you've filled out the form correctly.

B-lay will use any of the data provided above in accordance with our privacy policy