SIEMENS PLM SOFTWARE

TcRA OOTB
Guidelines

BI Practice

8/27/2018

Unrestricted
 OOTB Guidelines

Contents

1. Naming Convention………………………………………………………………………………………………………………….. 3
1.1 Category Name…………………………………………………………………………………………………………………… 3
1.2 Report and Cube naming convention…………………………………………………………………………………. 3
2. Guidelines for TcRA Cube Creation…………………………………………………………………………………………… 4
2.1 Guidelines for Level/Node Name……………………………………………………………………………………….. 4
2.2 Mandatory columns for Report development…………………………………………………………………….. 4
1. Non-Hierarchical cube………………………………………………………………………………………………………. 4
2. For Hierarchical cube………………………………………………………………………………………………………… 4
2.3 Other TC Attributes/Columns Naming Convention……………………………………………………………… 5

Unrestricted 2
Business Intelligence & Reporting and Analytics Implementation
 OOTB Guidelines

This document will help TcRA Reports developer and others by

 Improving MLV/Cube readability

 Ease for future MLV modification
 Understand the Mapping/Traversal

1. Naming Convention

1.1 Category Name

 When you are dealing with a large number of TcRA Reports, you can segregate it
using Categories based upon business need.
 User can use the Category option from the BuildNPlay ribbon to create it.
 You can then use these categories to save Cubes, Reports, and Portals.
Example: - You can create the 'YFAI' category to save all the YFAI reports under it.
You can then create two sub-categories 'ASP' and 'LIMS' categories to segregate the
YFAI Reports further, based on the Specific Module.

1.2 Report and Cube naming convention

 User should define the Report name that self-describe the Report purpose
Example: - BOM Report, Change Report, Customer Part Search Report, Test Audit
Report, etc.

 Underlying Cube name should also matches with Report name.

Example: - BOM_Report_Cube, Change_Report_Cube etc.

Unrestricted 3
Business Intelligence & Reporting and Analytics Implementation
 OOTB Guidelines

2. Guidelines for TcRA Cube Creation

2.1 Guidelines for Level/Node Name

 Level names can be written as “<Source Name>_Node”

For example:- for item level :- “Item_Node”

2.2 Mandatory columns for Report development

1. Non-Hierarchical cube
 For Non-Hierarchical cube, first two columns are Mandatory columns
Mandatory columns: - id, label

2. For Hierarchical cube

 For Hierarchical cube, first five columns are Mandatory columns
Mandatory columns: - id, label, parented, hier, lev

Unrestricted 4
Business Intelligence & Reporting and Analytics Implementation
 OOTB Guidelines

2.3 Other TC Attributes/Columns Naming Convention

For 6th, 7th, 8th columns onwards, user should give proper name to column Header that
will clearly define the corresponding mapped TC attribute.

 Predicate attributes Names – Names must start with “Predicate” as initial.

For example: - “Predicate_object_type”. Add these columns after report attributes

Filter attributes – Column Names must start with “Filter” as initial.

For example: - Filter_Item_No

 Filter columns should be added at the end for User ease.

Unrestricted 5
Business Intelligence & Reporting and Analytics Implementation