Understanding and Managing Licensing Options in Oracle E-Business Suite

Understanding and Managing Licensing Options in Oracle E-Business Suite

To Bottom

---

This knowledge document describes the licensing options for Oracle E-Business Suite applications products. The most current version of this document can be obtained in My Oracle Support Knowledge Document 1639705.1. There is a change log at the end of this document. In This Document This document is divided into the following sections: Section 1: Licensing Options Section 2: Activating Oracle E-Business Suite Products Section 3: Product Dependencies Section 4: Product Families and Product Activation Section 5: Unlicensing a Product Section 1: Licensing Options Oracle E-Business Suite applications products can be activated from Rapid Install or from License Manager within Oracle Applications Manager. From Rapid Install, applications products can be activated for the following license models: License E-Business Suite (Suite Licensing) License Component Applications (Component Licensing) From License Manager, applications products can be activated as follows: License E-Business Suite License Component Application License Applications Product 1.1 License E-Business Suite This option is used to register a predefined set of Oracle E-Business Suite applications products. This licensing model allows wide access to applications functionality and will automatically register all applications products included in Oracle E-Business Suite. The applications products that are preselected are licensed automatically as a part of the suite. The ones that are not checked are usually not part of the Oracle E-Business Suite price bundle and must be registered separately as add-on products. 1.2 License Component Applications This option is used to register applications products by component applications. You should choose this option if your licensing agreement is for individual applications component products. These products are licensed based on the number of authorized users or on the number of business transactions processed. All individual applications products are listed on this screen. 1.3 License Applications Products This option is only available through License Manager in Oracle Applications Manager, and allows you to register individual Oracle E-Business Suite applications products. This option is generally used for off-cycle products (those that are released between release update packs) or for products not explicitly included in the product family groupings. License Manager does not set up license agreements or determine pricing, but performs the registration procedure that makes new components accessible to all Oracle E-Business Suite utilities. License Manager simply applies the logic defined by the Oracle Pricing guidelines. Contact your sales representative if you have any questions about the most appropriate licensing options for your organization. Section 2: Activating Oracle E-Business Suite Products Rapid Install lays down the files for all Oracle E-Business Suite applications products regardless of their license status. However, the products must be marked as licensed so they can be identified as active components of Oracle E-Business Suite. This information is stored in the STATUS column in the FND_PRODUCT_INSTALLATIONS table. You can check the status by running the following query with the APPS account in SQL*Plus: set pages 20000; col application_id for 9999; col application_name for A50; col status for A1; col application_short_name for A10; select fa.application_id, fa.application_short_name, fpi.status, fatl.application_name from fnd_product_installations fpi, fnd_application fa, fnd_application_tl fatl where ( fa.application_id = fpi.application_id and fa.application_id = fatl.application_id and fatl.language = 'US' ) order by fa.application_short_name; The possible values for STATUS are: I - Installed N - Not Installed S - Shared There is both a functional and technical impact in Oracle E-Business Suite when activating applications products in the FND_PRODUCT_INSTALLATIONS table. From the technical perspective, an Installed flag marks products for inclusion in patching and other tasks that will be performed to update and maintain the system after the initial installation. From a functional point of view, the behavior of some products and how they interact with each other may change depending on their status in this table. Note: As a best practice and to avoid any functional issues, always perform a full backup of your Oracle E-Business Suite database before activating any product. Section 3: Product Dependencies When processing a product, Rapid Install and License Manager automatically calculate the dependencies with other products and set all dependent products to Shared or Fully Installed if needed. The product dependencies are constructed by using the following files: RapidWiz.ini adlicmgr.ini applprod.txt 3.1 RapidWiz.ini and adlicmgr.ini Used by Rapid Install, RapidWiz.ini is located under /startCD/Disk1/rapidwiz. The counterpart of RapidWiz.ini, adlicmgr.ini is used by the License Manager component of Oracle Applications Manager. This file is located under $AD_TOP/resource in Release 11i, and under $AD_TOP/admin/template in Release 12.x. The files differ only in that RapidWiz.ini contains additional information for the exclusive use of Rapid Install. The [Product Groupings] section in these files includes the list of the application IDs for the products that will be activated when selecting each family. For example: Financials={101,140,200,222,240,260,600,8400,8401,8450,8901,231,673} The above application IDs correspond to the following Oracle E-Business Suite applications: GL,OFA,AP,AR,PN,CE,AX,IGI,PSB,PSA,FV,BNE,IBY Note: The application IDs and corresponding application short names can be obtained from the APPLICATION_ID and APPLICATION_SHORT_NAME columns in the FND_APPLICATION table. 3.2 applprod.txt This file is located under $APPL_TOP/admin, and contains all the dependency information between Oracle E-Business Suite applications products. This file dictates which other dependent products will be set as Fully Installed or Shared when selecting a particular product. The following example shows the dependencies for Oracle Payables in bold italics. # ################################################## # Payables # ################################################## # # application id, abbreviation, shortname, prefix 200 ap SQLAP APP # multiple product installations for msob, "controlled release", shared only # optional fourth field is "stub product". default is No Yes No No No # multilingual, has NLADD.sql Yes Yes # install oracle id, default ORACLE username, default ORACLE password 200 AP AP # concurrent conflict set id (logical database id) 0 # minimum version you can upgrade from, for shared and for fully-installed 8.0.57 8.0.57 # shared products; this lists fnd and some subset of: fnd ax ak az gl inv po fa ar ont as per pay mfg bom eng wip pa dt xla ce qa crp mrp ff # product libraries needed for "make -f .mk all" fnd alr inv bom crp eng mrp wip po gl ar pay ff dt ap fa # when install this product, set these other products to install ax ak az # requires that these other products are fully installed or installing ax ak az # Section 4: Product Families and Product Activation When you perform a new installation, you will first select a product family, which in turn will ultimately activate products that are included in that particular family. When you choose the License E-Business Suite option, License Manager will look at the following entry in adlicmgr.ini: [Suite Products] Suite Families={Basic,Marketing & Sales Intelligence,Supply Chain & Order Management Intelligence,Procurement Intelligence,Service Intelligence,Projects intelligence,Financials Intelligence,Balanced Scorecard,Enterprise Planning and Budgeting,Profitability Manager,Marketing,TeleSales,Field Sales,Order Management,Inventory Management,Purchasing,Discrete Manufacturing,Process Manufacturing,TeleService,Service Contracts,Project Costing,Project Billing,Financials,Human Resources} When you choose the License Component Application option, License Manager will look at the following entry in adlicmgr.ini: [Product Families] All Families={All,Intelligence,Marketing & Sales,Channel Revenue Management,Order Management,Logistics,Supply Chain Planning,Procurement,Manufacturing,Asset Lifecycle Management,Service,Projects,Product Lifecycle Management,Financial,Human Resources,Learning Management,Master Data Management - Customer Hub for B2B,Master Data Management - Customer Hub for B2C,Master Data Management - Site Hub,Master Data Management - Administrative & Development,Master Data Management - Product Information Management,Master Data Management - Vertical Product Hub,Product Hub Options,Interaction Center Technology,Financial Services,Communications/Utilities,Public Sector/University,High Tech,Aerospace Defense and Transportation} When you select a product family, for example "Service Contracts", License Manager will search for the entry Service Contracts={515,870,542} to obtain the initial list of application IDs. With that list, License Manager will look at entries in applprod.txt that correspond to those application IDs and will create the dependency tree for the rest of the products that need to be activated. In other words, License Manager will fully activate the three products included in Service Contracts (515, 870 and 542), searching inapplprod.txt for all their dependent products and setting them to Shared or Fully Installed accordingly. This will occur for each product that is fully activated. From the dependent list, License Manager will set all the products from the Shared list to Shared and all the products from the Fully Installed list to Fully Installed. Shared products will not fully activate other products. Only fully activated products will cause License Manager to look at all the dependencies that need to be Shared or Fully Installed. Section 5: Unlicensing a Product Unlicensing a product is not supported. Some applications will behave differently if some modules are fully activated or shared. Changing a product from Fully Installed to Shared or Not Installed may cause result in unpredictable behavior, especially if you continue to use Oracle E-Business Suite after the product was activated. Note: Oracle strongly recommends that you never use SQL*Plus, database triggers, or any other tool to manually modify Oracle E-Business Suite data unless otherwise instructed by Oracle Development. If you inadvertently activate a product, you have two options: Restore a full backup of the Oracle E-Business Suite database from before you activated the offending product. This is our preferred and supported recommendation to assure data consistency, since there is a functional impact on Oracle E-Business Suite: any transactions executed as a result of incorrectly activating a product would result in an unpredictable state within the product dependencies. Export and import the FND_PRODUCT_INSTALLATIONS table with the state from before you activated the offending product. Although this is the only table used by License Manager, this option is only feasible if no Oracle E-Business products at all were used after the offending product was incorrectly activated. If you are not certain whether Oracle E-Business Suite was used, we recommend you seek assistance from the relevant product support team to determine if there could be any adverse functional impact.