Analytics Log (Business Process) Setup

You can set up Dashboards and Analyses, for Unifier Business Processes, in Oracle Business Intelligence Enterprise (OBIE) analyses and select the Business Process data that you want to use for analyses.

When you open a Business Process in the Analytics node, you will see the Analytics - Business Process Setup window with the following tabs:

Business Processes tab
Custom Fields tab
Data Mapping tab

Business Processes tab

Select Business Processes for Analytics

The Business Processes tab allows you to select the Business Process that you want to use in Analytics.

Use the Add or Remove buttons to add or remove the Business Processes for Analytics. To add a new Business Process for use in Analytics:

Click Add to open the Select Business Processes for Analytics window that lists all the company-level, Shell-level, and Project-level Business Processes, in alphabetical order.
Note: This list includes Active and Inactive Business Processes.
Select one Business Process, or select as many as you need, and click OK to add the Business Process to the log.
Note: After you added the Business Process, that Business Process will no longer be available in the Select Business Processes for Analytics list.

You can remove a Business Process that is published for Analytics. To remove a Business Process for use in Analytics, select the Business Process from the Select Business Processes for Analytics list and click Remove. You can delete multiple Business Processes from the list. You can add a removed Business Process for Analytics reporting. Click Add if you want to add a removed Business Process to the list.

If a Company Administrator inactivates a Business Process that has been used for Analytics, then this Business Process continues to remain in the Business Processes tab. If you remove a Business Process from the Business Processes tab, data that exists in Analytics, for the removed Business process, remains as is; however, the new data will not be published.

To save space, you can decide not to track the history of facts and dimensions, on a Business Process.

In the Analytics - Business Processes Setup window (Business Processes tab) you can select a business process and mark to not track the history of the business process data elements (Track History of Data Elements? column). By default, all BPs in this tab are selected to have their history tracked. After your initial selection in the Track History of Data Elements? column for a BP, if you open the Analytics - Business Processes Setup window and go to the Business Processes tab and deselect the track history option for a BP, then Unifier will notify you that the BP will no longer maintain the historical data in Analytics.

For a BP with track history option selected, all data mapping changes for the elements of the BP will be recorded as errors in the historical data in Analytics.

Note: The Track History of Data Elements? column values will be included in the Configuration Package during export or import.

Custom Fields tab

The Custom Fields tab is available after you add your Business Processes in the Business Processes tab. The Custom Fields tab has two sections:

Main Form Elements
Line Item Elements

You can specify values in each field to set the number of user-defined fields for Data Mapping. The default values displayed are based on the existing user-defined fields limit that is currently set in Unifier.

The total number of Main Form custom fields cannot exceed 900. Similarly the total number of Line Item custom fields cannot exceed 900.

When entering values in the fields:

Use numeric values.
Do not use decimal points.
Use numbers greater than the default values.
Note: The number of fields specified are bundled as a part of configuration package, if the component has been tagged.

Data Mapping tab

The Data Mapping tab allows you to map the predefined Analytic Business Process fields to a corresponding Data Element (DE) in the Business Process.

Notes:

The Data Mapping tab is available after you have added a Business Process, in the Business Processes tab, and clicked Apply or OK.
The Data Mapping is done per DE and not per Business Process. All Business Processes added in the Business Processes list tab are included and you do not need to select a specific Business Process for mapping.
The fields from both Upper and Detail forms can be mapped in the Data Mapping tab, and you can change mapping of the fields.
The workflow data (Steps and tasks), related to any Workflow BP, is also sent to Analytics.
The DE of type Rich Text is not available to be mapped to the UDFs from Analytics.

The Data Mapping tab displays the following information:

Name
Source
Data Source
User Defined Attributes
- Name
- Data Type
- Source
- Data Source
- Label
  Note: In addition to the system defined fields for Analytics, you can define additional custom fields for Analytics in the User Defined Attribute section.

Name

The Name column is pre-populated and displays the following names:

Specification Section
Vendor ID
Contract Type
Reason
Unit of Measure
Spend Category
Quantity
Unit Cost

The names above represent the fields used in OBI. These are read-only fields and you cannot modify them.

All the "Main Form" fields are listed first and are sorted alphabetically within the source.

All the "Line Item" fields are listed after the Main form fields and are sorted alphabetically within the source.

Source

The Source column displays the location of the Data Element (DE) seen in the Data Source. For Business Processes, the DEs can either be from the "Main Form" or the "Line Item."

Data Source

The Data Source column contains a consolidated list of all DEs for all of the selected Business Processes in the Business Processes tab. In addition:

The list of values displayed upon clicking the Data Source drop-down will be those that have a matching data definition as the Name field. When you click, the Data Source drop-down list contains a list of values that have a matching Data Definition (DD) as the Name field.
The drop-down list, which requires the Upper form mapping, contains a consolidated list of all Upper form DEs. For example, if there are ten Upper forms from all the Business Processes, and each Upper form has 10 DEs, then the list of DEs displayed in the drop-down list will be a consolidated and unique list of DEs from all the Business Processes.
The drop-down list, which requires the Detail form mapping, contains a consolidated list of all Detail form DEs. For example, if there are twenty Detail forms, and each Detail form has 10 DEs, then the list of DEs displayed in the drop-down list will be a consolidated and unique list of DEs from the Detail forms of all the Business Processes.
The fields displayed in the Data Source drop-down list is a concatenation of DE Label and DE Name, and the DE Name is displayed within parentheses. For example, Department(contract_department)

User Defined Attributes

The User Defined Attributes section of the Data Mapping tab lists the following columns:

Name
Data Type
Source
Data Source
Label

The Label will be based on the selected DE label, but you can change it.

Use the Add, Modify, and Remove to add, modify, or remove user defined attributes.

To modify a user-defined attribute, select the attribute, click Modify, and modify the fields.

To remove a user-defined attribute, select the attribute, click Remove, and modify the fields.

To add a user-defined attribute, read the following information:

When you click Add, the Add User Defined Attribute window opens. This window allows you to select the following mandatory fields:

Data Type
Source
Name
Data Source
Label
Notes:
- A value for the mandatory Label field will be selected by the system.
- The Label field is populated based on the Data Element that you have selected from the Data Source drop-down list.
- The Label field is editable and required. You will receive an error message if you leave the Label field blank.
- If you notice that the value in the Label field has changed, it means that other fields have been updated at one point.
- Analytics displays the value, if the label is absent.
- Analytics displays the label, which has the Value/Label pair, in the case of Data Elements (DEs).

The Data Type that you select impacts the Name and the Data Source of the user-defined attribute. The Data Type field allows you to select the following attributes, only:

String (default)
Date
Numeric

For example, if you select String as your Data Type, you can:

Select from a predefined set of sources from Source drop-down list (Main Form or Line Item).
Add up to 30 names (User Defined String Fields 1 - 30) as the Name.
Select from a predefined set of data sources from Data Source drop-down list.
The content of the Label field will be selected by the system and according to your other selections.

Analytics Dimension and Fact

The Data Type that you select corresponds to the Analytics fields as follows:

If the Data Type that you select is String/Date, then your selection corresponds to a Dimension object in Analytics.
If the Data Type that you select is Numeric, then your selection corresponds to a Fact object in Analytics and is only available in the Primavera - Project User Defined.

Additional information

If the same DE exists in both Upper form and Detail form, then the DE is displayed for the Upper form fields, as well as the Line Item fields.
If you map a DE for one field, you can map the same DE to another field. You can choose the DEs, per your Company business needs, when setting up the mapping.
If you change the mapping of the fields, for the new records, then the next time the data is published to OBI, the values will be as per the updated fields. If you need to refresh, for all the records, then you need to click the check box option in the Schedule tab.
If you delete a DE mapped to an Analytic field, the Data Source field displays only the DE name.
If there are any un-mapped fields in the Data Mapping tab, the un-mapped fields appear in the DE list, based on the updated design.
If you delete a Business Process, and click Apply, the Data Source field displays only the DE name.
The allowed user-defined attributes is driven by the number that is set in the Custom Fields tab.
Pickers are available for String field mappings for both canned and user defined attributes and are as follows:
- BP Data Picker
- Shell Data Picker
- Space Data Picker
- User Data Picker
- BP Picker
- User Picker
- Shell Picker
- Space Picker
- BP Creator
- P6 Activity Picker

Summary Payment Application (SPA) SOV type BPs

You can perform data reporting in Analytics for Base Commit, Change Commit, and Payment Application Business Processes of SPA SOV type. The system sends the following Cost allocation Line Item details to Analytics:

Cost Code
Cost Name
Short Description
Quantity
Unit Price
Amount

If you need to transfer data from any field (at the Summary level) to Analytics, then you must map the field to a User Defined Field in Line Items of the Business Process. The system sends the mapped field to Analytics as a part of Cost allocation Line Item.

Note: Users can map any field that exists in the Detail form.

The values of the fields in the existing Cost allocation Line Items are retained for the fields that are common to both the Summary and Cost allocation Line Items. The following explains the details:

Cost Code
The value of the field in the Cost allocation Line Item is retained. The CBS Picker field does not exist in the Detail Form design.
Cost Name
The value of the field in the Cost allocation Line Item is retained. The bi_item field does not exist in the Detail Form design.
Short Description
The value of the field in the Cost allocation Line Item is retained.
Quantity
The value of the field in the Cost allocation Line Item is retained.
Unit Price
The value of the field in the Cost allocation Line Item is retained. The Unit price is auto-populated from the value of the field in the Detail Form and is a read-only field in the Cost allocation Line Item. The value of the field in the Cost allocation Line Item will match the value of the field in the Detail Form.
Amount
The value of the field in the Cost allocation Line Item is retained.