| Oracle Product Lifecycle Analytics Configurator and Data Mapping Guide Release 3.5 E70277-01 |
|
 Previous |
 Next |
| Oracle Product Lifecycle Analytics Configurator and Data Mapping Guide Release 3.5 E70277-01 |
|
Previous |
Next |
Answers to some frequently asked questions are listed in this chapter.
Why are some PLM attributes not appearing in its attribute options list for mapping?
All attributes that are defined in the PLM database are not available for selection. Only those attributes that have corresponding mapping information defined in the Data Mart tables are displayed.
Can I map disabled attributes using the Configurator?
The Configurator does not support the mapping of disabled attributes. If a previously mapped attribute is subsequently disabled in PLM, the mapping is highlighted in red for your attention.
Why am I prompted to select a target dimension table only for certain attributes?
You can change the target dimension table only for list, multi-list, and user-defined attributes. For conforming dimension tables, you can only change the attribute name. In PPM module, you can change the target dimension table only for multi-list attributes.
Why do some of the dimension table names in the list appear in blue?
This indicates that the dimension table has already been mapped for the selected attribute.
Only a few PLM attributes are displayed for the predefined dimension table names. Why?
Some List IDs may already have been mapped to a predefined dimension table in another row or tab. In this case, only the attributes for the same List ID are displayed. A target dimension table can be mapped to only one List ID.
Can I start the Configurator before the ODM ETL process runs?
Yes, but Flex attributes will not be available for mapping.
Can I use the Configurator while the MDS ETL is running?
This is best avoided as it can interfere with the ETL process.
Why are some of my flex attributes not displayed in the OPLA Configurator?
Newly created flex attributes should have been entered in the new columns using the Agile JavaClient or WebClient in order to be picked up by the ODM ETL process. Unless this is done, these attributes will not appear in the OPLA Configurator.
Will my changes to Agile PLM configuration require any changes to existing mappings?
After you finish the initial mapping of PLM attributes, you will need to update the mappings whenever a mapped attribute is changed or disabled in Agile PLM.
When I upgrade to OPLA Configurator, what happens to the configurations done using MDS Configurator version 3.3.1.1?
See Upgrade Considerations section in Oracle Product Lifecycle Analytics (OPLA) Installation and Setup Guide.
In OPLA Configurator, if I need more mappable fields what should I do?
Use Options > Add user-defined fields menu to add more user-defined configurable fields. See Extending user-defined (Configurable) fields.
Can I extend the number of User-defined dimension tables using OPLA Configurator?
No. For information on adding user-defined dimension tables to MDS Schema using OPLA Configurator, refer section, Adding User-defined dimension tables to the Schema.
The OPLA Configurator supports only the extension of columns in Fact tables and creation of corresponding bridge tables (wherever applicable).
How do I get more elaborated logging messages in my log file?
OPLA Configurator uses Apache log4j libraries for logging messages. You can change log4j.properties file with different logging level (INFO, DEBUG, WARN, ERROR) to control the type of messages logged in the log file.
For more information see Apache log4j at http://logging.apache.org/log4j/1.2/manual.html.
When I upgrade from PLM BI 3.0 / 3.1 / 3.2 to OPLA 3.5, can I retain all configurations done using the 3.3.1.1 version of the MDS Configurator?
Yes. It is possible to retain all the configurations done using the 3.3.1.1 version of the MDS Configurator when you upgrade from PLM BI 3.0 to OPLA 3.5.
Why do we have domain value lookup in OPLA?
You can configure your own PPM subclasses in Agile PLM. These subclasses can be used as Program, Project, and Portfolio according to the needs in your organization. You need to map these configured subclasses into respective domains to obtain meaningful reports.
What happens if I do not configure domains?
If you do not configure domain values, the ETL run does not populate values in the Phase-Gate Fact Table. You will receive a WARNING email notification indicating that you have not configured Phase and Gate.
What are the mandatory domain values that need to be configured for PPM?
You need to configure the Program, Portfolio, Phase and Decision Gate domain values for PPM.
Why are the source attributes not showing up in the PPM subclasses configuration in MDS Configurator?
There are two answers to this question.
a. The staging ETL did not run successfully.
b. Before using PPM subclass configuration users should always configure the appropriate domains under Options--> ETL Configurations > Domain lookup tab.
Answers to some frequently asked questions are listed below:
Why are there no records returned when I create an Answer by selecting in Project Summary Subject Area's P4P Metrics Measures for any projects in "3 Year NPV" nor "Annualized Case Volume"?There are no pre-mapped results for these Measures.
Why are there no records returned when I create an Answer by selecting in Project Summary Subject Area's P4P Metrics Measures for any projects in "3 Year NPV (No Basis, No Phase, No Year)" nor "Annualized Case Volume (No Basis, No Phase, No Year)"?None of your NPD Projects use the expected pre-mapped Project Metric names of: THREE_YR_NPV_NOB_NOPH_NOFY nor ANNUALIZED_VOLUME_CASES_NOB_NOPH_NOFY. You can re-map these as needed.
Why are there no records returned when I add the P4P Metrics Dimension of Basis Name (and/or Category Name, Metric Phase Name, Fiscal Year) to my Project Summary Subject Area's Answer with P4P Metrics Measures for any projects in "3 Year NPV (No Basis, No Phase, No Year)" nor "Annualized Case Volume (No Basis, No Phase, No Year)"?These Dimensions are only useful with the "3 Year NPV" and "Annualized Case Volume" measures (note that there is no parenthetical qualifying of Basis or Phase or Fiscal Year in their names).
