Learn how read-only users differ from normal Oracle E-Business Application users

10 mar '15 - Tudor Stoenescu - share: LinkedIN Mail

Reading through the first pages of the Oracle E-Business Suite Applications Global Price List (PDF: for educational purposes only!), the metric “Application User” cannot be overlooked. This license type requires an organization to identify all individuals, authorized to use the E-Business Suite programs, regardless of whether they are actively using the software at a given time.

Often, organizations fail to actively keep track of the changing population. Not only should you track new users who need to access the software, but also remember to regularly perform data cleanups of all E-Business Suite users. Anyone who no longer needs to use the software should be end-dated: for example employees who have changed roles or left the organization. Bear in mind that anyone authorized to use E-Business Suite programs must be licensed. Any user data cleanup should include all instances, for example any test, development or acceptance environment. 
Here is why! During an E-Business Suite Financials pilot you may want to verify if the Purchasing module could provide added value as well. A selected number of people will get the responsibility, assigned within the system, to test the module. If your organization decides to start using the Purchasing functionality, licenses will be bought. But what if your organization decided the opposite? Did you end-date the responsibilities of all test users? Typically this does not happen which means that in an audit both tested applications and test users will be counted. So far this concise overview of the Application User metric.

Only at the bottom of the aforementioned Oracle E-Business Suite Applications Global Price List, the metric “Application Read-Only User” appears. This type concerns licenses per product for Financials, Purchasing, Project Costing, Service Contracts, Project Contracts, Sales Contracts, Discrete Manufacturing, or Process Manufacturing. When you look at corresponding prices, this license type may be very interesting but what does Read-Only in the Oracle E-Business Suite context actually mean? An Application Read-Only User is defined as an individual authorized to run only queries or reports against the application program for which the organization has also acquired non read-only licenses, regardless of whether the individual is actively using the programs at any given time.

Since read-only licenses provide fewer usage rights than the Application User licenses, they are cheaper. Do make sure, however, that all read-only responsibilities and corresponding users are clearly identified. If you fail to distinguish between different types of users, your organization will end up with all licenses being counted as “full use” Application User ones, which is a costly mistake. Individuals who are granted the right to both read-only and full use will be counted only once, as full Application Users, in a license review or license audit.

Do you want to learn more about Oracle's E-Business Suite? Then please join our free online expert session on March 20.


Expert session: Oracle E-Business Suite license metrics analyzed

B-lay experts Richard Spithoven & Tudor Stoenescu share their insights on complexities and differences in Oracle E-Business Suite license metrics.

Expert session: Oracle E-Business Suite license metrics analyzed


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