1 Introduction

In order to support enterprise reporting and analysis needs, accurate operational data encompassing millions of product records must be made available for use within analytics applications. This data must be organized and formatted in meaningful ways to support different query modes and ensure that business users derive the right information for decision making.

Typically, Extract-Transform-Load (ETL) processes are used to reorganize source data before loading it into the target system. Field-level data mappings need to be carried out to resolve any differences in the field names.

1.1 About this Guide

This document is intended for data warehouse administrators who are familiar with Agile Product Lifecycle Management (Agile PLM) and Agile PLM for Process.

1.1.1 Acronyms Used in This Document

The table below lists the acronyms used in this document.

Acronym	Expansion
BI	Business Intelligence
CAPA	Corrective and Preventive Action
CRM	Customer Relationship Management
DM	Data Mart
ECO	Engineering Change Order
ECR	Engineering Change Request
ETL	Extract-Transform-Load
FS	Fact Staging
MCO	Manufacturing Change Order
MDS	Multi-Dimensional Schema
NCR	Non-Conformance Report
OBIEE	Oracle Business Intelligence Enterprise Edition
ODI	Oracle Data Integrator
ODM	Operational Data Mart
OPLA	Oracle Product Lifecycle Analytics
PLM	Product Lifecycle Management
PLM BI	Product Lifecycle Management Business Intelligence
PLM DM	Product Lifecycle Management Data Mart
PPM	Product Portfolio Management
PQM	Product Quality Management
PR	Problem Report
SCM	Supply Chain Management
SS	Stop Ship

1.1.2 Related Documentation

The documents that you may need to reference during the data mapping process, mainly the Oracle Product Lifecycle Analytics (OPLA) product installation documentation and the database schema documentation, are available on Oracle Technology Network (http://www.oracle.com/technology/documentation/agile.html).

• Oracle Product Lifecycle Analytics Setup Guide - Describes the installation and deployment of BI product components.

• Oracle Product Lifecycle Analytics Data Reference Manual - Describes the entities of the published model of the MDS schema.

• Oracle Product Lifecycle Analytics User Guide - OPLA helps you to analyze business data, assess business impact, make timely decisions, and conduct trend analysis.

1.2 Overview of Agile Product Lifecycle Management Data Mapping

The Oracle Product Lifecycle Analytics (OPLA) application queries data for reports and dashboards from the Multi-Dimensional Schema (MDS) database. The MDS database schema contains a set of tables and columns to support PLM business reporting and analytics requirements. The data for this MDS schema is sourced from Agile Product Lifecycle Management (Agile PLM).

You define fields in Agile PLM according to your business process requirements. The Oracle Product Lifecycle Analytics application retrieves accurate field data for analysis only if the data in the MDS fields and the data in the Agile PLM fields are synchronized. Additionally, you should map the source custom-defined fields (Page Two and Page Three) of Agile PLM business objects.

Data type mapping is available in all three models - PC, PQM, and PPM.

Note For more information on Oracle Product Lifecycle Analytics architecture, see the Oracle Product Lifecycle Analytics Installation and Setup Guide.

1.3 Overview of Agile PLM for Process Extensibility

Oracle Product Lifecycle Analytics (OPLA) solution framework for Agile PLM for Process source allows you to customize and extend the out-of-the-box solution by providing configuration and customization capabilities.

Data flows from Agile PLM for Process to the presentation layer within OPLA happens in the following order:

1. Source to Staging

2. Staging to Multi-Dimensional Schema (MDS)

3. MDS to the presentation layer of the OBIEE repository

1.4 The Agile PLM OPLA Configurator

The OPLA Configurator tool allows you to map attributes from the Agile PLM application to fields in the data layer of the Oracle Product Lifecycle Analytics application. With an easy-to-use graphical interface, the OPLA Configurator simplifies the process of mapping fields from Agile PLM to the tables and columns in the MDS database schema. These saved field-level mappings are used by the ETL process to load data into the target MDS database schema.

Note: When you open an object in the Agile PLM Web Client or Java Client, you see a tabbed window with fields. In Agile PLM these fields are called attributes. For complete information on Agile PLM attributes, refer to the Agile Administrator Guide.

Important: The OPLA Configurator tool is used only for Agile PLM application data mapping.