You can set up Dashboards and Analyses, for Unifier Cost Sheet data, in Oracle Business Intelligence Enterprise (OBIE) analyses and select the Cost Sheet column data that you want to use for analyses.
This section explains the following topics:
- Data Mapping - Columns
- Data Mapping - Cost Attributes
When you open a Cost Sheet record in the Analytics node, the Analytics - Cost Sheet Setup window opens with the following tabs:
- Data Mapping - Columns
- Data Mapping - Cost Attributes
The following explains each tab and their respective fields.
Data Mapping - Columns
The Data Mapping - Columns tab is divided in two sections:
- System-defined columns: Listed on top of the window.
- User-defined Columns: Listed under User Define Columns section of the window.
The system-defined columns of the Data Mapping - Columns tab allows you to map the Cost Sheet Analytic fields to a corresponding Cost Sheet Data Source defined in Unifier.
In addition to the system-defined Cost Sheet columns, you can add additional user-defined columns (total of 20). The User Defined Columns section, in Data Mapping - Columns tab of the Cost Sheet Setup, displays the additional 10 columns (User Defined Columns from 11 to 20).
The top section of Data Mapping - Columns tab (system-defined columns) has the following columns:
- Name
- Data Source
The following explains each column.
Name
Lists a series of predefined fields which correspond to the fields used in OBI.
Note: Since the fields under Name are grouped logically, the order displayed are according to the list of fields that need mapping for Cost Sheet.
This is a list of predefined fields:
- Estimate
- Original Budget
- Pending Budget Revisions
- Approved Budget Revisions
- Revised Budget
- Contracts
- Purchase Orders
- Original Commitments
- Forecast
- Pending Change Orders
- Pending PO Amendments
- Pending Commitment Changes
- Approved Change Orders
- Approved PO Amendments
- Approved Commitment Changes
- Revised Commitments
- Pending Payment Applications
- Pending Invoices
- Pending Spends
- Approved Payment Applications
- Approved Invoices
- Approved Spends
- Actuals Received
- Journal Entries
- Risks & Issues
- Forecast Adjustments
- Budget Variance
- Remaining Budget
- Budget Percent
- Commitment Percent
Data Source
Lists the corresponding data source to each field that is listed in the Name column. The values in the Data Source fields:
- Are divided into two sources (Single Sources and the Logical Sources).
- Are sorted in alphabetic order.
- Exist in the Cost Sheet for all CBS type Shells.
The lower section of Data Mapping - Columns tab (under the User Defined Columns section) has the following columns:
- Name
- Data Source
- Label
The following explains each column.
Name
This is a list of predefined columns:
- User Defined Column 1
- ...
- User Defined Column 20
The Analytic field name can be the same as the Data Source name. For example, you can map a User Defined Curve to data source named, "Initial Baseline."
Data Source
- The P6 data sources are included under the Single Sources, and the element is included within the parenthesis of the P6 Data Source. For example,
Current Baseline (Planned Cost). - In addition to the predefined list displayed, you can add up to 10 additional mappings for the Cost Sheet data sources.
- You can pick the same data source for multiple fields.
Label
- Labels are required for the User Defined Columns. A red-color asterisk (*/star symbol) appears for the columns that have been mapped to a data source.
Note: Asterisk (*/star symbol) does not appear for a column that has not been mapped to a data source.
- For existing mappings of user-defined Cost Sheet columns, the labels are populated based on the data source name.
- Labels support non-ISO characters (UTF-8 characters).
- If there are no labels, then the data source names will be sent to OBIEE.
Note: Custom String translation is not applied.
- When you select a data source for the first time, the label is populated based on the data source name. You can modify the label according to your business need.
- The maximum characters allowed in the label field is 50, same as the Cost Sheet Data Source Name.
Note: The system does not perform Label Uniqueness test.
Data Mapping - Cost Attributes
The Data Mapping - Cost Attributes tab contains user-defined Attributes, listed under the User Defined Attributes section.
To add a new field, click Add to open the Add User Defined Attribute window. Enter name, source, and label in the following fields:
- Name
- Data Source
- Label
The Data Type field is read-only and set as "String" by default. The value in the Data Type field determines if the selected field is a Dimension object or a Fact object in Analytics. If the Data Type field is "String," then the field is a Dimension object in Analytics.
Note: Only the "String" type field is supported for Cost Code Attributes data mapping in Analytics.
You can add up to 20 String type Data Elements (DEs) from the Cost Code Attributes Detail Form as User Defined Attributes.
The Name field is a required field and lists User Defined String Field 1 through 20.
- If a name has been selected, for example, User Defined String Field 1, then the list does not include User Defined String Field 1 and starts with User Defined String Field 2.
- If an existing name has been deleted, the name will appear in the list.
The Data Source field lists Data Elements (DEs) in the Cost Code Attributes Detail Form.
Only DEs with the "String" type Data Definitions (DDs) are displayed in the Data Source field. The "String" type DDs in the list are:
- Text Box
- Multiple Text Lines
- Pull-Down Menu
- Radio Buttons
- Multi-select Input
The DDs in the Data Source field include the DEs. For example, Description (uuu_cost_description). If a DE that has already been added is deleted from the deployed design, then the DE name will be seen, only.
Unifier populates the Label field based on the DE that has been selected in the Data Source drop-down list. The Label field is a required and editable field, and it will accept non-ISO characters (UTF-8), to support internationalization.
The maximum allowed length is the same as the DE label, and Unifier does not check for label name uniqueness.