GLOBAL CUSTOMER SUPPORT POLICY REGARDING Oracle Product Lifecycle Analytics (OPLA) CUSTOMIZATIONS
(Doc ID 1606731.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Product Lifecycle Analytics - Version 3.3.0 to 3.5.0 [Release 3.3.0 to 3.5.0]
Information in this document applies to any platform.
This policy statement is necessary due to the complexity of the customizations that can be implemented within various Oracle Products. Oracle Product Lifecycle Analytics (OPLA) allows you to customize and extend the out-of-the-box solutions by providing configuration and customization capabilities. Customers can also modify Oracle Data Integrator (ODI) ETL scenarios per their needs, and have the flexibility to add tables/columns even to the MDS schema. The flexibility of the customization comes with significant responsibility- the complete ownership of your work.
Global Customer Support is available to assist in the troubleshooting and diagnosing of problems that customers experience during the implementation and use of the out-of-the-box OPLA product. Support is not responsible for assisting/troubleshooting the following areas of customization:
NOTE: Customization Service Requests cannot be granted a severity higher than 3 which allows Oracle Support Services time to address non-custom issues with clients.
Modifying the Configurator:
OPLA product provides a set of defined columns and user-defined columns in MDS schema tables. An OPLA Configurator client provided with the application allows the customer to map these defined/user-defined columns to Agile attributes, so ETL task can load data from Agile PLM database. Defined columns from MDS schema are pre-wired to metrics or dimensions in subject areas within the BI Model (RPD). User-defined columns are NOT pre-wired in the BI Model and this is as-designed. The customer needs to customize the RPD model to wire these into the subject area. It is expected that anyone customizing the RPD model has experience with data warehousing models OBIEE and ODI.
Custom ETL scenarios:
ETL Customization Guidelines
- Load additional dimension attributes from other system
- Load additional facts from non-Agile sources which qualify with the OPLA dimensions
- Extending OPLA use-cases which are not supported or configurable to Agile source
- Extending OPLA to customer-specific time dimensions needs
- Avoid any changes to the out-of-the-box projects
- Bringing in additional dimension attributes or external data
- Create custom project
- Include the interfaces and procedures for customizing the ETL
- Create a package and call ANALYTICS_ETL scenario before custom ETL scenario
- Better to run out-of-the-box ETL before running the custom ETL
These are the guidelines on ETL customization to put you on the correct path. But neither Oracle Support nor Oracle Development support any issues arising from these customizations.
Debugging custom code or sample code:
Oracle Support does not cater to the customer’s custom or sample code. Oracle Support will only validate the out-of-the-box code. All customizations must work outside of applications in order for the customization to work, as Support does not debug custom codes.
Materialized views on MDS schema:
Customers can create Materialized views on the MDS schema for their specific needs on an independent basis. Any issues arising from these customizations will be the customer’s responsibility to test and validate it, as Oracle Support will only test the out-of-the-box schema under in-house against customer source DB to validate the issue. Once it is proven that the out-of-the-box schema has no issue, then customer needs to unplug all Materialized views from MDS schema and add one Materialized view at time to find all affected (corrupted) Materialized views.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document