2 Mapping the Agile Product Lifecycle Management Data

This chapter relates to Agile PLM for information on configuration (attribute mapping) related to Agile PLM for Process see Extending the Agile PLM for Process Data on page 43.

2.1 Data Mapping Process

The OPLA Configurator's configuration capabilities includes the mapping of Cover Page, Page Two, Page Three, and Flex attributes of supported Agile PLM classes, as follows:

MDS fact fields to Agile PLM source fields.
MDS dimension fields to Agile PLM source lists that are assigned to the Agile PLM fields.

Data accessed by the tool is located in the MDS and ODM database tables.

Important:

Any changes to the Data Dictionary definitions in the OPLA staging schema or MDS impacts the tool. Refer to the latest published model as documented in the OPLA Data Reference Manual.

The Oracle Product Lifecycle Analytics reports derive data from fixed target columns within the database tables. Using the OPLA Configurator, the data elements (in the fixed target columns) are mapped to the source columns. Data is derived from these source columns.

For these changes to take effect, you must perform the following actions in the order given:

Before you start mapping, at least one successful completion of a Stage ETL run.
After you finish mapping, at least one successful ETL run on MDS.

Note:

The OPLA Configurator is a mapping tool. Data is retrieved and updated through the ETL processes. If there are any configuration mapping changes, MDS ETL is automatically set to Full Load. When you change the PLM version, set MDS ETL to Full Load by using ETL Configurations > Runtime Options.

Note:

After enabling any module for staging, the ETL has to run in Full Load. To do this manually:

1. Connect to the ODM/Stage Schema.

2. Back up the ETL_RUN_INFO table.

3. Tuncate the ETL_RUN_INFO table.

2.2 What's Configurable in Agile PLM

The MDS has three field types:

Main fields (Not configurable) - These fields correspond to an object's Cover Page attributes in the Agile PLM application. Some Cover Page attributes, such as multi-text fields, are not relevant for analysis and are excluded from the MDS. Since these fields have a predefined meaning they are embedded in the OBIEE model and used to compute relevant predefined metrics.

These are exposed in the presentation layer of the model as measures and dimensions. Reports created using these measures and dimensions are embedded in the out-of-the-box role-based and functional dashboards.
Defined extensions (Configurable) - Defined extension fields in each fact or subject area capture important information about the subject area. They have predefined semantics and in Agile PLM are configurable to the Cover Page, Page Two, Page Three, and flex attributes. Out-of-the-box, they are not mapped to any Agile PLM attribute. These defined fields are mapped as dimensions and measures in the OBIEE model.
User-defined extensions (Configurable) - User-Defined extension fields in each fact or subject area are used to capture important information about the subject area. They have predefined semantics, and in Agile PLM are configurable to the Cover Page, Page Two, Page Three, and flex attributes. Out-of-the-box, they are not mapped to any Agile PLM attribute. If you want to use these fields you need to customize the model. Contact your Oracle PLA administrator for further information.

Figure 2-1 Agile PLM Mappings

The figure above illustrates the following:

How each type of MDS field is mapped from one layer to the next.
Shows the field that you can configure or customize.

Note:

Use the OBIEE Admin features for additional configuration and customization.

2.3 Mappings Supported in this Release

The table below shows the data sources for the target MDS tables. The Target Fact Table column lists the target MDS table name. The Classes column lists the attribute groups (from where the data is sourced).

Target Fact Table	Classes	Subclasses	Supported Source Attribute Groups
Core Fact Table	PR NCR CAPA Change Orders Change Requests Manufacturing Change Orders Stop Ship Deviations	Cover Page, Page Two attributes, Page Three attributes of subclasses Flex attributes
	Mfr Part Mfr	Cover Page attributes, Page Two attributes, Page Three attributes of subclasses Flex attributes
	Item Mfr part Item Product Performance	Item AML flex attributes Read through of dimensions configured on Item facts and Mfr Part facts
	Gate	Cover Page attributes, Page Two attributes, Page Three attributes of Gate subclasses configured as Gate domain Gate subclass Flex attributes Team tab P3 and Flex attributes
	Activity	Program Project Phase Portfolio	Cover Page attributes, Page Two attributes, Page Three attributes of Activity subclasses configured as different domain values Activity subclass Hex attributes Team tab P3 and Flex attributes For every supported domain (Program, Portfolio and Phase), you can map only the subclasses that are configured as domain attributes.
Affected Item Fact Table	PR NCR CAPA Audit, ECO ECR MCO SS Deviations	All Attributes configured on the Affected Item tab. Note Excludes Item read-through attributes.
Single Materialized view consisting of subclass	Audit CAPA NCR PR Change Order Engineering Change Request Manufacturing Change Stop Ship Deviations	Read through of dimensions configured on Item facts, subclass facts

2.3.1 PPM-Specific Mappings

The table below describes how the OPLA Configurator provides mapping ability to Agile PLM Product Portfolio Management (PPM) source data.

OPLA Configurator		MDS Target table
Configurator Subject Area	Mapping Description	Fact Table	Dimension Table
Portfolio	Oracle PLA Configurator provides the ability to map Cover Page/P2/P3/Flex attribute of any Activity subclass. Choose the attributes relevant to the Portfolio domain subclasses as configured in domain look up.	Portfolio fact: PPM_PORTFOLIO_F	Portfolio Dimensional attribute: PPM_PORTFOLIO_D
Program	OPLA Configurator provides the ability to map Cover Page /P2/P3/Flex attribute of any Activity subclass. Choose the attributes relevant to the Program domain subclasses as configured in domain look up.	Program fact: PPM_PROGRAM_F	Program Dimensional attribute: PPM_PROGRAM_D
Project	OPLA Configurator provides the ability to map Cover Page /P2/P3/Flex attribute of any Activity subclass. Choose the attributes relevant to Activities subclasses that are considered as Projects according to the Phase domain configured in domain value lookup.	Project Summary fact: PPM_PRJ_SUM_F	The Project dimensional attribute: PPM_PROJECT_D
Phase	OPLA Configurator provides the ability to map Cover Page /P2/P3/Flex attribute of any Activity subclass. Choose the attributes relevant to the Phase domain subclasses as configured in domain look up.	Phase Gate fact: PPM_PHASE_GATE_F	Phase dimensional attribute: PPM_PHASE_D
Activity	OPLA Configurator provides the ability to map Cover Page /P2/P3/Flex attribute of any Activity subclass. Also, the P3 and Flex attributes of Team tab.	Activity base fact: PPM_ACTIVITY_F	Activity dimensional attribute: PPM_ACTIVITY_D
Gate	OPLA Configurator provides the ability to map Cover Page /P2/P3/Flex attribute of any Gate subclass. Also, the P3 and Flex attributes of Team tab. Choose the attributes relevant to the Decision Gate domain subclasses as configured in domain look up or any Gate subclass if you are planning to bring it across to Detailed areas	Phase Gate fact: PPM_PHASE_GATE_F	Gate dimensional attribute: PPM_GATE_D

2.3.2 Supported Data Types

The table below lists the supported data type mappings.

Target: MDS Table/Column Type	Source: Agile PLM Attribute Type
Dimension	List Multi-list Cascade Single-select dynamic list Note Cascade lists are not supported for the PPM module in Oracle Product Lifecycle Analytics Release 3.3 and higher.
Bridge	Multi-list Multi-list cascade Multi-list dynamic
Date	Date
Number	Number
Float	Money
Text	Alphanumeric text
Money	Also known as Cost