BMC Analytics For BSM 7.6.04 Reference Guide

BMC Analytics for Business Service Management 7.6.
04
Reference Guide
April 2011
www.bmc.com
Contacting BMC Software

You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information
about the company, its products, corporate offices, special events, and career opportunities.
United States and Canada

Address
BMC SOFTWARE INC

2101 CITYWEST BLVD
HOUSTON TX 77042-2827
USA
Telephone
713 918 8800 or

800 841 2031
Fax
(01) 713 918 8000
Fax
713 918 8000
Outside United States and Canada

Telephone
(01) 713 918 8800
If you have comments or suggestions about this documentation, contact Information Design and Development by email at
doc_feedback@bmc.com.
Copyright 2003 - 2011 BMC Software, Inc.

BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent
and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and
logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the
property of their respective owners.
IT Infrastructure Library is a registered trademark of the Office of Government Commerce and is used here by BMC Software, Inc.,
under license from and with the permission of OGC.
ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the
U.S. Patent and Trademark Office, and is used here by BMC Software, Inc., under license from and with the permission of OGC.
UNIX is the registered trademark of The Open Group in the US and other countries.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
SAP and BusinessObjects are trademarks or registered trademarks of SAP AG in Germany and in several other countries.
BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this information is
subject to the terms and conditions of the applicable End User License Agreement for the product and the proprietary and restricted
rights notices included in this documentation.
Restricted rights legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF
THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to
restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and
DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC Software, Inc., 2101 CityWest Blvd., Houston, TX
77042-2827, USA. Any contract notices should be sent to this address.
Customer Support
You can obtain technical support by using the Support page on the BMC Software website or by contacting Customer
Support by telephone or email. To expedite your inquiry, please see Before Contacting BMC Software.
Support website
You can obtain technical support from BMC Software 24 hours a day, 7 days a week at
http://www.bmc.com/support_home. From this website, you can:
Read overviews about support services and programs that BMC Software offers.
Find the most current information about BMC Software products.
Search a database for problems similar to yours and possible solutions.
Order or download product documentation.
Report a problem or ask a question.
Subscribe to receive email notices when new product versions are released.
Find worldwide BMC Software support center locations and contact information, including email addresses, fax
numbers, and telephone numbers.
Support by telephone or email

In the United States and Canada, if you need technical support and do not have access to the Web, call 800 537 1813 or
send an email message to customer_support@bmc.com. (In the Subject line, enter
SupID:<yourSupportContractID>, such as SupID:12345.) Outside the United States and Canada, contact
your local support center for assistance.
Before contacting BMC Software

Have the following information available so that Customer Support can begin working on your issue immediately:
Product information
Product name
Product version (release number)
License number and password (trial or permanent)
Operating system and environment information
Machine type
Operating system type, version, and service pack
System hardware configuration
Serial numbers
Related software (database, application, and communication) including type, version, and service pack or
maintenance level
Sequence of events leading to the problem
Commands and options that you used
Messages received (and the time and date that you received them)
Product error messages
Messages from the operating system, such as file system full
Messages from related software
License key and password information

If you have a question about your license key or password, contact Customer Support through one of the following
methods:
E-mail customer_support@bmc.com. (In the Subject line, enter SupID:<yourSupportContractID>,

such as SupID:12345.)
In the United States and Canada, call 800 537 1813. Outside the United States and Canada, contact your local support
center for assistance.
Submit a new issue at http://www.bmc.com/support_home.
Contents
Chapter 1
Universe characteristics and related information
About the ITSM Universe and installed objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

ITSM universe characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Fields for reporting on multitenancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Stored procedures, functions, and tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Using business service models in BMC Analytics for BSM . . . . . . . . . . . . . . . . . . 13
About the ProactiveNet universe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Stored procedures, functions, and tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
ANA_EVENT_OP_HISTORY_VIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
About the ImpactPortal universe. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Stored procedure, table, and view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
About the PortalCDE universe. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Stored procedures, functions, and tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Fiscal calendar data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
ANA:Fiscal_Calendar form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
ANA_FISCAL_CALENDAR view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Date conversion functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
FN_ADJUSTED_DATE function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
FN_GET_EPOCH_DATE function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Timezone table and supported timezones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
ANA_TIMEZONE_INFO table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Timezone support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Chapter 2
Universe and report customization templates
41
Universe customization templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Report customizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 1: Report Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 2: Data Selection/Grouping/Sorting/Parameters . . . . . . . . . . . . . . . . . . .
New and Changed parameter description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 3: Report Presentation Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chart Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Field Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Variable additions and Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
42
43
44
44
44
45
45
45
46
Chapter 3
47
Report conditions and default views
Report conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Default views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Contents
BMC Software, Inc., Confidential
BMC Analytics for BSM default views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Cloud Lifecycle Management default views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Event Management default views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
CMDB default views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Change Management default views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Service Request Management default views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Asset Management default views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Service Level Management default views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Service Desk default views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Configuration Drift Management default views. . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Index
61
Reference Guide
Chapter
Universe
characteristics and
related information
This appendix contains the following topics:
About the ITSM Universe and installed objects (page 4)

About the ProactiveNet universe (page 18)
About the ImpactPortal universe (page 25)
About the PortalCDE universe (page 26)
Fiscal calendar data (page 28)
Date conversion functions (page 30)
Timezone table and supported timezones (page 32)
Chapter 1 Universe characteristics and related information

BMC Analytics for BSM 7.6.04
About the ITSM Universe and installed objects

This section contains information about the ITSM universe and about the objects
that are installed by BMC Analytics for BSM for reporting on the BMC Remedy IT
Service Management applications, BMC Atrium CMDB, and BMC Cloud Lifecycle
Management.
ITSM universe characteristics

Table 1-1 contains the characteristics of the ITSM universe.
Table 1-1: Characteristics of the ITSM universe
Name
Value
Description
Name
ITSM
Name of the universe
Description
BMC Analytics for BSM 7.6.04 universe for

reporting on BMC Remedy ITSM
Description of the universe
Connection
ITSM
Name of the connection used to

connect to the BMC Remedy AR
System database
Classes and Objects
See Self Help Document ID KA345616 in the

BMC Knowledge Base for a complete list of
classes and objects.
Description of the formulas for the

classes and objects in the universe.
See Self Help Document ID:
KA345616 in the BMC Knowledge
Base for a complete list of classes
and objects.
Reference Guide

Name
Value
Description
Statistics
SAP BusinessObjects XI R 3.1 SP3 and BMC

Remedy AR System Server version 7.1:
Universe metrics
438 classes
4166 objects
815 conditions
539 tables
298 alias
808 joins
0 contexts
27 hierarchies
SAP BusinessObjects XI R2 SP5 and BMC
Remedy AR System Server version 7.1:
434 classes
4098 objects
815 conditions
524 tables
296 alias
802 joins
0 contexts
27 hierarchies
SAP BusinessObjects XI R3.1 SP3 and BMC
Remedy AR System Server version 7.5 and 7.6:
558 classes
5459 objects
951 conditions
713 tables
481 alias
1189 joins
0 contexts
27 hierarchies
SAP BusinessObjects XI R2 SP5 and BMC
Remedy AR System Server version 7.5 and 7.6:
482 classes
4699 objects
848 conditions
621 tables
359 alias
966 joins
0 contexts
27 hierarchies


Name
Value
Description
Controls
Limit size of long text objects to: 4000 characters Limits the amount of data and the
time used to retrieve the data
Limit execution time to: 10 minutes
Warn if Cost Estimate Exceeds 300 seconds
Multiple SQL Statements for each Context: true These are the settings used by
Multiple SQL Statements for each Measure: false BusinessObjects to generate SQL
queries. Based on the specified
Allow Use of Union,Intersect and Minus
values, you can restrict the types of
Operators: true
operations that the SQL generation
Cartesian Products: warn
engine can do.
Allow Selection of Multiple Contexts: false
SQL Query
Allow Use of Subqueries: true

Allow Complex Operands in Query Panel: true
Fields for reporting on multitenancy

BMC Analytics for BSM uses the data stored in the BMC Remedy ITSM application
form fields that are listed in this topic.
For more information about multitenancy in the ITSM universe, see BMC Analytics
for Business Service Management Installation and Administration Guide.
Table 1-2:
Application
Version
Application view
Asset
Management
7.0.x, 7.5.x,
7.6x
BMC_CORE_BMC_B
ASEELEMENT
Incident
Management
7.0.x
HPD_HELP_DESK
Fields
Company 1
Incident
Management
7.5.x, 7.6.x
HPD_HELP_DESK
Problem
7.0.x
Management
PBM_PROBLEM_IN
VESTIGATION
Database column name

1
Company
Contact_Company
Direct_Contact_Compa
ny
Company
Contact_Company
ny
Company
Assigned Support
Company
Owner Support
Company
Company
Contact_Company
Reference Guide
Contact_Company
ny
Company
Contact_Company
ny
Company
Assigned_Support_Co
mpany
Owner_Support_Comp
any
Company
Contact_Company
Table 1-2:
Application
Version
Problem
7.5.x and
Management 7.6.x
Application view
PBM_PROBLEM_IN
VESTIGATION
Fields
Company
Contact_Company
Problem Manager
Assignment Support
Company
Manager Assignment
Support Company
Problem
7.0.x
Management
(Known
Error)
PBM_KNOWN_ER
ROR
Company
7.5.x and
Problem
Management 7.6.x
(Known
Error)
PBM_KNOWN_ER
ROR
Problem
7.0.x
Management
(Solution
Database)
PBM_SOLUTION_
DATABASE
Problem
7.5.x and
Management 7.6.x
(Solution
Database)
Company
Contact_Company
Support_Company_Pbl
m_Mgr
Assigned_Support_Co
mpany
Company
Company
Problem Manager
Assignment Support
Company
Company
Support_Company_Pbl
m_Mgr
Company
Company
PBM_SOLUTION_
DATABASE
Company
Solution Assignment
Support Company
Company
Assigned_Support_Co
mpany
Change
7.0.x
Management
CHG_INFRASTRU
CTURE_CHANGE
Location Company
Change
7.5.x and
Management 7.6.x
CHG_INFRASTRU
CTURE_CHANGE
Location Company
Change Manager
Support Company
Change Assignee
Support Company
Change Implementer
Support Company
Change
7.0.x
Management
(Release
Management
)
not applicable
not applicable
Change
7.5.x and
Management 7.6.x
(Release
Management
)
RMS_Release
Location_Company
Release Manager
Support Company
Location_company
Location_company
Company3
ASCPY
ChgImpCpy
not applicable
Location_Company
Company3

Table 1-2:
Application
Version
Application view
Service
2.0.x and
Request
2.2.x
Management
SRM_REQUEST
Service Level 7.1.x, 7.5.x,

Management and 7.6.x
SLM_Contract
Fields
Location_Company
Customer_Company
Location_Company
Customer_Company
SharedServicesGroups SharedServicesGroup
s
1.
Though BMC Remedy Asset Management also uses the field CMDBRowLevelSecurity in its
multitenancy implementation, BMC Analytics for BSM does not use the field in its multitenancy
implementation.
Stored procedures, functions, and tables

This section lists and describes the stored procedures, functions, and tables that are
installed by BMC Analytics for BSM. The objects that are installed vary according
to whether your BMC Remedy AR System Server uses an Oracle database or a
Microsoft SQL Server database.
Oracle stored procedures, functions, packages, tables,

and views
Category
Name
Description
Function
FN_ADJUSTED_DA
TE
Invoked as required by IT Service Management

class and object formulas. The script that inserts
the function is
FN_ADJUSTED_DATE_ORA.SQL.
BMC Analytics for BSM uses these converted
dates for reporting and trending metrics. The
function supports Daylight Saving Time for
multiple time zones. For more information, see
the BMC Analytics for Business Service
Management Reference Guide.
Package
PKG_BSM_RELATIO Populates the

DENORMALIZE_BSM_RELATIONSHIPS
NSHIPS
table. The following scripts are run to install the
package:
PKG_BSM_RELATIONSHIPS_SPEC_ORA.S
QL
PKG_BSM_RELATIONSHIPS_BODY_ORA.s
ql
Reference Guide
Category
Name
Description
Stored
procedure
POPULATE_FISCAL
_CALENDAR
Populates the ANA_FISCAL_CALENDAR

view. This stored procedure is invoked by AR
Workflow on the ANA:Fiscal Calendar Form
when the form is updated in BMC Remedy Mid
Tier. The script that inserts the stored
procedure is
PC_POPULATE_FISCAL_CALENDAR_ORA.
SQL
Stored
procedure
(Package
body)
ANA_POPULATE_T
IMEZONE_DST
The procedure queries ANA_TZ_DST_VIEW

and inserts data into the TABLE
ANA_TZ_DSTTIME.
Stored
procedure
(Package
specificatio
ns)
PKG_ANA_TZ_DST
The procedure queries ANA_TZ_DST_VIEW

and inserts data into the TABLE
ANA_TZ_DSTTIME
Table
DENORMALIZE_BS
M_REL
ATIONSHIPS
A database procedure reads the business

service models and the relationships in BMC
Atrium CMDB and populates the business
service model relationships in the
table. The table must be created before the
procedure is executed. The script
ANA_DENORMALIZE_BSM_RELATIONSHI
PS_DDL_ORA.SQL is run to install the table.
For more information, see BMC Analytics for
Business Service Management Installation and
Administration Guide.
Table
ANA_TIMEZONE_I
NFO
Lists the timezones used in the reports and the

related information. This table is created by the
following scripts:
ANA_TIMEZONE_INFO_DDL_ORA.SQL
ANA_TIMEZONE_INFO_DML_ORA.SQL
For more information about the supported

timezones, see BMC Analytics for Business
Service Management Reference Guide.
Table
ANA_REPORT_LOC
ALE
Stores the user-specified locale settings for the

reports. This table is created by the following
scripts:
Table
ANA_REPORT_STRI
NG
ANA_REPORT_LOCALE_DDL_ORA.SQL
ANA_REPORT_LOCALE_DML_ORA.SQL
Stores the text that appears on the reports. This

table is created by the following script:
ANA_REPORT_STRING_DDL_ORA.SQL

Category
Name
Description
Table
ANA_REPORT_TRA
NSLATION
Stores the report definition settings for the

reports in various languages. This table is
created by the following scripts:
ANA_REPORT_TRANSLATION_DDL_ORA
.SQL
ANA_REPORT_TRANSLATION_EN_DML_
ORA.SQL (English)
ANA_REPORT_TRANSLATION_JA_DML_
ORA.SQL (Japanese)
(This script will not get executed, but it will be

stored in the installation directory.)
Table
ANA_TZ_DSTTIME
Stores the precalculated data for the DST start

time and end time of the preferred time region,
which is used for converting Epoch time to the
preferred time in the date conversion function.
This table requires the
ANA_TIMEZONE_INFO table, which is also
created during installation and contains the
timezone code.
View
ANA_TZ_DST_VIE
W
This view is used to populate the table

ANA_TZ_DSTTIME. The view query reads the
data from table ANA_TIMEZONE_INFO and
precalculates the DST start time and end time.
This view requires the
ANA_TIMEZONE_INFO table, also created
during installation, that stores the timezone
region code.
View
10
ANA_FISCAL_CAL
ENDAR
Used by the Populate_Fiscal_Calendar

procedure, invoked by workflow on the
ANA:Fiscal Calendar form.
Reference Guide
Microsoft SQL Server stored procedures, functions,

packages, tables, and views
Category
Name
Description
Function
FN_ADJUSTED_DA
TE
Invoked as required by IT Service

Management class and object formulas. The
scripts that insert the function are:
FN_ADJUSTED_DATE_MSSQL.SQL
DROP_FN_ADJUSTED_DATE_MSSQL.S
QL
BMC Analytics for BSM uses these converted

dates for reporting and trending metrics. The
function supports Daylight Saving Time for
multiple timezones. For more information,
see Supported timezones for BMC Remedy
AR System server data source on page 35.
Stored
Procedure
ANA_POPULATE_T
IMEZONE_DST
Populates the table ANA_TZ_DSTTIME.

This procedure reads the data from table
ANA_TIMEZONE_INFO and precalculates
the DST start time and end time for the
preferred time region, which is used for
converting Epoch time to the preferred time
in the date conversion function. This stored
procedure requires the
ANA_TIMEZONE_INFO table, which stores
the time region code.
Stored
Procedure
PC_POPULATE_FIS
CAL_CALENDAR

view. This stored procedure is invoked by
AR Workflow on the ANA:Fiscal Calendar
Form when updated in BMC Remedy AR
System. The script that inserts the stored
procedure is
PC_POPULATE_FISCAL_CALENDAR_MS
SQL.SQL
Stored
Procedure
PC_DENORMALIZE
_BSM_RELATIONS
HIPS

Atrium CMDB from the
BMC_CORE_BMC_BASERELATIONSHIP
table and populates the
table. The scripts that install the stored
procedure are
DROP_PC_DENORMALIZE_BSM_RELA
TIONSHIPS_MSSQL.SQL
PC_DENORMALIZE_BSM_RELATIONS
HIPS_MSSQL.SQL

11
Category
Name
Description
Stored
Procedure
PC_BSM_RELATIO
NSHIPS_TRAVERSA
L
A database procedure called from

PC_DENORMALIZE_BSM_RELATIONSHI
PS that traverses one business service at a
time in a recursive mode. The scripts that are
run to install the procedure are
Table
ANA_TZ_DSTTIME
DROP_PC_BSM_RELATIONSHIPS_TRAV
ERSAL_MSSQL.SQL
PC_BSM_RELATIONSHIPS_TRAVERSAL
_MSSQL.SQL
Stores the precalculated data for the DST

start time and end time of the preferred time
region; used for converting Epoch time to the
preferred time in the date conversion
function.
This table requires the
ANA_TIMEZONE_INFO table, which is
also created during installation and contains
the timezone code.
Table
ANA_TIMEZONE_I
NFO
Lists the timezones used in the reports and

the related information. This table is created
by the following scripts:
DROP_TABLE_ANA_TIMEZONE_INFO_
MSSQL.SQL
ANA_TIMEZONE_INFO_DDL_MSSQL.S
QL
ANA_TIMEZONE_INFO_DML_MSSQL.S
QL
For more information about the supported

timezones, see Supported timezones for
BMC Remedy AR System server data
source on page 35.
Table
DENORMALIZE_BS
M_RELATIONSHIPS

Atrium CMDB from the
table and populates the
table. The table must be created before the
procedure is executed. The following scripts
are run to install the table:
12
DROP_TABLE_DENORMALIZE_BSM_RE
LATIONSHIPS_MSSQL.SQL
ANA_DENORMALIZE_BSM_RELATION
SHIPS_DDL_MSSQL.SQL
Reference Guide
Category
Name
Description
Table
ANA_REPORT_LOC
ALE
Stores the user-specified locale settings for

the reports. This table is created by the
following scripts:
Table
ANA_REPORT_STRI
NG
Stores the text that appears on the reports.

This table is created by the following scripts:
Table
ANA_REPORT_TRA
NSLATION
DROP_TABLE_ANA_REPORT_STRING_
MSSQL.SQL
ANA_REPORT_STRING_DDL_MSSQL.S
QL
Stores the report definition settings for the

reports in various languages. This table is
created by the following scripts:
View
DROP_TABLE_ANA_REPORT_LOCALE_
MSSQL.SQL
ANA_REPORT_LOCALE_DDL_MSSQL.S
QL
ANA_REPORT_LOCALE_DML_MSSQL.S
QL
DROP_TABLE_ANA_REPORT_TRANSL
ATION_MSSQL.SQL
ANA_REPORT_TRANSLATION_DDL_M
SSQL.SQL
ANA_REPORT_TRANSLATION_EN_DM
L_MSSQL.SQL (English)
ANA_REPORT_TRANSLATION_JA_DM
L_MSSQL.SQL (Japanese)
ANA_Fiscal_Calenda Used by the Populate_Fiscal_Calendar

r
procedure, invoked by workflow on the
ANA:Fiscal Calendar form.
Using business service models in BMC Analytics for BSM

Because the BMC _CORE_BMC_BASERELATIONSHIP table used by BMC
Atrium CMDB to store CI relationship date is not suitable for the reporting
requirements of BMC Analytics for BSM, a new table is created that prepares the
operational data for use in the reports.
The procedure, installed by BMC Analytics for BSM, retrieves BMC Business
Service Class CI data from the BMC _CORE_BMC_BASERELATIONSHIP table
and recursively traverses the table following the relationships that identify a
service model, then stores the CI, Relationship and other denormalized data in the
DENORMALIZE_BSM_RELATIONSHIPS table
In BMC Atrium CMDB, the relationships that are created directly are dependency
relationships, and the relationships that come from the import of Service Models
from BMC SIM are impact relationships. The current solution only works for the
dependency relationships that are created in BMC Atrium CMDB. The BMC SIM
relationship is a future enhancement.
13
The following BMC_BaseRelationship types are supported:
BMC_Component
BMC_Dependency
BMC_MemberOfCollection
The following table shows the detailed structure of the

DENORMALIZE_BSM_RELATIONSHIPS table.
Table 1-3: DENORMALIZE_BSM_RELATIONSHIPS table
14
Column Name
Type
Description
NODEID
VARCHAR2(38 BYTE)
The reconciliation id of the CI in the business service

model that is representing the current row
LEVELNUMBER
NUMBER
This will be the distance in terms of number of hops,

at which the current CI is from the top of the tree.
NODEORDER
NUMBER
The asset type and would typically have values like

"BMC_COMPUTERSYSTEM",
"BMC_BUSINESSSERVICE" etc.
RELATIONSHIPN
AME
VARCHAR2(254 BYTE)
The name of the relationship like "member of", "hosts",

"hosted by" that the current CI forms with the CI at the
next level.
UPARENT
VARCHAR2(254 BYTE)
The reconciliation id of The Business Service CI at the

root of the business service model.
REQUESTID
VARCHAR2(38 BYTE)
The request ID of the row which belongs to the CI in

the baserelationship table.
INSTANCEID
VARCHAR2(38 BYTE)
The Instance ID of the row which belongs to the CI in

the baserelationship table.
UPARENTNAME
VARCHAR2(254 BYTE)
The name of the business service at the root of the

business service model.
IPARENT
VARCHAR2(38 BYTE)
The reconciliationid of the CI which is the immediate

parent of the current CI for which this row belongs.
IPARENTNAME
VARCHAR2(254 BYTE)
The name of the CI which is the immediate parent of

the CI which the current row represents.
RELATIONSHIP
VARCHAR2(4000 BYTE)
The name of the relationship (dependency,

component etc) for the current node.
NODENAME
VARCHAR2(254BYTE)
The name of the current node
NODEDISPLAY
VARCHAR2(4000 BYTE)
The name of the current node along with the display

offset for the purpose of reporting.
DATASETID
VARCHAR2(254BYTE)
The datasetid of the CI from the base relationship table

which the CI represents.
Reference Guide
Populating the DENORMALIZE_BSM_RELATIONSHIPS

table
This table is populated by the PC_DENORMALIZE_BSM_RELATIONSHIPS
procedure. For information about running this procedure to populate the table, see
the BMC Analytics for Business Service Management Installation and Administration
Guide.
Business service models in the ITSM universe

The ITSM universe has all the data elements that are related to the business service
models exposed as part of the classes, objects and conditions. This will enable the
business user to perform ad hoc analysis on the business service models in tandem
with the data coming from other modules. Specifically, the business user will be
able to do cross-functional reporting from the business service model to BMC
Remedy Incident Manager, BMC Remedy Change Manager and other modules in
the ITSM universe.
The screenshots in the figures below show the details of where the related objects
and conditions exist in the universe. They primarily are hosted in the BMC Atrium
CMDB module under the class with the name Business Service Model.
Figure 1-1: Universe Logical Model:

15
Figure 1-2: Universe Objects for Business service model
16
Reference Guide
Figure 1-3: Universe conditions for Business service model
Reports based on Business Service Model

There are two predefined reports that are part of the BMC Analytics for BSM
product that report on the business service models. The reports follow.
C02 - Business Services Supported By a CI: This report provides the bottom up
analysis capability for the business service model. The user can enter/select a
list of CIs, and the report will display a list of all the business services that are
supported by each of the CIs.
C03 - Business Service Profile: This report provides the top down analysis
capability for the business service model. The user can enter/select a list of
business service models from a drop down and the report will decompose each
of them to the lowest level in terms of the CIs that are supporting it.

17
About the ProactiveNet universe

The following table summarizes the characteristics of the ProactiveNet universe.
Table 1-4: Characteristics of the ProactiveNet universe
Name
Value
Description
Name
ProactiveNet
Description
BMC Analytics for BSM universe 7.6.04

for reporting on BMC ProactiveNet 8.5
Description of the universe.
Connection
ProactiveNet
Name of the connection used to connect to

the BMC ProactiveNet Performance
Management server database
Classes and Objects
See Self Help Document ID: KA345616 in Description of the formulas for the classes
the BMC Knowledge Base for a complete and objects in the universe.
list of classes and objects.
Statistics
24 classes
Universe metrics.
421 objects
42 conditions
14 tables
12 alias
24 joins
0 contexts
0 hierarchies
18
Reference Guide
Name
Value
Description
Controls
Limit size of result set: 5000 rows
Limits the amount of data and the time

used to retrieve the data.
Limit size of long text objects to: 4000

characters
SQL Query
These are the settings used by

Allow use of union, intersect and minus BusinessObjects to generate SQL queries.
Based on the specified values, you can
operators: yes
restrict the types of operations that the SQL
Allow complex conditions in Query
generation engine can do.
Panel: yes
Allow use of subqueries: yes
Cartesian products: warn

Multiple paths
Generate several SQL statements for

each context: yes
Generate several SQL statements for
each measure: yes
Allow selection of multiple contexts: no
These are the settings used by SAP

BusinessObjects to generate SQL queries.

installed by BMC Analytics for BSM.
Category
Name
Description
Event
ANA_OP_HISTORY
_SYNC
Invokes the event operation history procedure

PC_PROCESS_EVENT_DATA daily.
Function
FN_ADJUSTED_DA
TE
A function that converts an epoch value into a

readable data and time format, according to
timezone information stored in the table
ANA_TIMEZONE_INFO..
Function
FN_GET_EPOCH_D
ATE
A function that converts an epoch value into a

readable data and time format, according to
timezone information stored in the table
ANA_TIMEZONE_INFO. Used to boost query
performance.
Procedure
PC_CLEANUP_OP_
HISTORY
Deletes any existing history tables and cleans

the partition and prune control tables.
Procedure
ANA_LASTRUN_C
NTL
Initially populates the table

ANA_LASTRUN_CNTL with a null value.
Procedure
PC_
EVENT_OP_HISTOR
Y_TRAVERSAL
Invoked by procedure
PC_PROCESS_EVENT_DATA; retrieves new
data from an event table; calls procedure
PC_POPULATE_EVENT_STATUS_HISTORY
to populate the related event operation history
table with the event data.

19
20
Category
Name
Description
Procedure
PC_POPULATE_EV
ENT_OP_HISTORY
Invoked by procedure
PC_EVENT_STATUS_HISTORY_TRAVERSA
L; populates the event operation history table
with new event data.
Procedure
PC_POPULATE_FIS
CAL_CALENDAR

table with dates according to the fiscal period.
Procedure
PC_PROCESS_EVEN
T_DATA
Main procedure that identifies updated event

data and calls additional procedures to update
the event operation history tables.
Procedure
PC_REFRESH_VIEW
_STRUCTURE
Recreates the view

ANA_EVENT_OP_HISTORY_VIEW to
incorporate newly created event operation
history tables. Invoked by procedure
PC_PROCESS_EVENT_DATA
Procedure
DROP_ANA_OBJEC
TS_SYBASE
Removes all the installed objects from the

database during an uninstallation.
Table
ANA_EVENT_OP_H
ISTORY
An event operation history table that

corresponds to each EG_EVENT table;
populated by the procedure
PC_POPULATE_EVENT_STATUS_HISTORY.
For more information about this table see the
<i>BMC Analytics for Business Service
Management Reference Guide
Table
ANA_FISCAL_CAL
ENDAR
A fiscal calendar table that is populated

depending upon the start year, start month,
and the duration of the fiscal calendar;
populated by procedure
PC_POPULATE_FISCAL_CALENDAR
Table
ANA_LASTRUN_C
NTL
Stores the Last Run date of the procedure

PC_PROCESS_EVENT_DATA in epoch
format; initially populated with a null value by
the procedure ANA_LASTRUN_CNTL.
Table
ANA_FIELD_ENUM
_VALUES
Stores all of the values for the enumerated BMC

Remedy AR System fields.
Table
ANA_TIMEZONE_I
NFO
Stores all of the timezones and Daylight Saving

Time (DST) values.
View
ANA_EVENT_OP_H
ISTORY_VIEW
Aggregates all of the

ANA_EVENT_OP_HISTORY tables.
Reference Guide
ANA_EVENT_OP_HISTORY_VIEW
The history table ANA_EVENT_OP_HISTORY_VIEW contains the operational
history of an event life cycle. Because the EG_EVENT tables used by BMC
ProactiveNet Performance Management to store operational history are not
suitable for the reporting requirements of BMC Analytics for BSM, a new table is
created that prepares the operational data for use in the reports. The procedures
installed by BMC Analytics for BSM retrieve comma-separated event data from the
MC_OPERATIONS column of the BMC ProactiveNet Performance Management
table (EG_EVENT), separate the data, then store it in the
ANA_EVENT_OP_HISTORY_VIEW table, along with the event ID, creation date
of the event, modification date of the event, and other data.
The following table shows the detailed structure of the
ANA_EVENT_OP_HISTORY_VIEW table.
Table 1-5: ANA_EVENT_OP_HISTORY_VIEW
Column name
Data type
Description
MC_UEID (primary key)
Varchar (64)
Event ID
OPERATION_SEQ_NUM
(primary key)
Integer
The sequence of operations

in descending order
EVENT_DATE_RECEPTION
Integer
Event create date
EVENT_DATE_MODIFICATION
Integer
Event modification date
OPERATION_DATE
Integer
The time at which an

operation was performed
on the event. This is a HEX
value converted to an
integer.
USER_NAME
Varchar (128)
User who changed the

event.
ARG1
Varchar (128)
Can contain any string as

defined by the user in the
BMC ProactiveNet
Performance Management
application.
OPERATION_STATE
Varchar (128)
Operation that was

performed on the event
ARG3
Varchar (128)
Can contain any string as

defined by the user in the
BMC ProactiveNet
Performance Management
application.
LAST_PROCESSED_DATE
Datetime
Date when the record in the

History Table was last
processed by the
procedures.

21
Populating the history table

The history table is populated by the main procedure
PC_PROCESS_EVENT_DATA_SYBASE.sql which runs nightly and is initiated by
the event ANA_EVENT_OP_HISTORY_SCHEDULE_SYBASE.sql. This
procedure performs the following steps:
Checks for newly created event tables, and creates a history table
ANA_EVENT_STATUS_HISTORY for each new event table.
Calls the procedure PC_EVENT_STATUS_HISTORY_TRAVERSAL to populate

the new history table
Checks for updated event tables.
Calls the procedure PC_EVENT_STATUS_HISTORY_TRAVERSAL to update

the history table for any event table that has been updated.
Updates the BMC ProactiveNet Performance Management Partition Control

table with the same entry that was included in the new history table.
Updates the BMC ProactiveNet Performance Management Prune Control table

with the same value that was included in the new history table.
Recreates the history view to include any new history tables.
Updates the Last Run value in the ANA_LASTRUN_CNTL table.
History procedure pseudocode

This section contains the pseudocode for the history procedure
PC_PROCESS_EVENT_DATA_SYBASE.sql.
BEGIN
IF LastRun_date IS NULL
LastRun_date := MIN(START_TIME) FROM PARTITION_CNTL WHERE
TABLENAME = 'EG_EVENT'
Create a History Table if 1 already does not exist
Determine whether any old history tables exist.
If not then capture all existing history-tables and update them
part_num:=MAX(PART_NUM) FROM PARTITION_CNTL WHERE TABLENAME =
ANA_EVENT_OP_HISTORY'
index := 0
WHILE index <= part_num
BEGIN
IF index = 0
Note: Generate an Event and History Table depending upon
Partition Number
BEGIN
history_table := 'ANA_EVENT_OP_HISTORY'
event_table := 'EG_EVENT'
END
ELSE
BEGIN
history_table := 'ANA_EVENT_OP_HISTORY_'||@index
event_table := 'EG_EVENT_'||@index
22
Reference Guide
END
EXECUTE('SELECT @Last_modification_date =
MAX(MC_DATE_MODIFICATION) FROM ' ||
event_table)
IF last_modification_date > LastRun_date
Note: Process old tables that have been updated
BEGIN
EXEC PC_EVENT_OP_HISTORY_TRAVERSAL @event_table, @history_table
END
INCREMENT index
END
Using MaxEnd_date := MAX(END_TIME) FROM PARTITION_CNTL WHERE
TABLENAME = 'EG_EVENT' find any newly created history tables.
While all history tables not created
BEGIN
EXECUTE ('CREATE TABLE DBA.' || @history_table || '
(
MC_UEID VARCHAR(64),
OPERATION_SEQ_NUM INTEGER,
EVENT_DATE_RECEPTION INTEGER,
EVENT_DATE_MODIFICATION INTEGER,
OPERATION_DATE INTEGER,
USER_NAME VARCHAR(128),
ARG1 VARCHAR(128),
OPERATION_STATE VARCHAR(128),
ARG3 VARCHAR(128),
LAST_PROCESSED_DATE DATETIME,
PRIMARY KEY CLUSTERED (MC_UEID, OPERATION_SEQ_NUM)
)')
EXECUTE ('SELECT tabletype = TABLETYPE,
s_time = START_TIME,
e_time = END_TIME,
c_time = CREATION_TIME
FROM PARTITION_CNTL WHERE TABLENAME = ''EG_EVENT''
AND PART_NUM = ' || @part_num)
Note: We need to copy values for Event Table from
Partition_CNTL and paste same values for the History Table. This
is needed for the Pruning engine to work correctly
Motypeid:= TABLE_ID FROM SYSTABLE WHERE
TABLE_NAME='ANA_EVENT_OP_HISTORY'
IF NOT EXISTS (SELECT * FROM PARTITION_CNTL WHERE TABLENAME =
'ANA_EVENT_OP_HISTORY' AND PART_NUM = @part_num)
BEGIN
INSERT INTO PARTITION_CNTL VALUES
(
motypeid,
tabletype,
'ANA_EVENT_OP_HISTORY',
part_num,
s_time,
e_time,
c_time,
23
s_trace
)
COMMIT
END
EXEC PC_EVENT_OP_HISTORY_TRAVERSAL @event_table,
@history_table
END
Update PRUNE_CNTL table with an entry for the History table if
not already exists.
SELECT timecolumn = TIMECOLUMN,
deltahours = DELTAHOURS,
minitimestamp = MINTIMESTAMP,
lastpruned = LASTPRUNED
FROM PRUNE_CNTL WHERE TABLENAME = 'EG_EVENT'
Note: We need to populate Prune_CNTL table with appropriate
values that is the
same data as of Event Table for the pruning
engine to work correctly
IF NOT EXISTS (SELECT * FROM PRUNE_CNTL WHERE TABLENAME =
'ANA_EVENT_OP_HISTORY')
BEGIN
INSERT INTO PRUNE_CNTL VALUES
(
'ANA_EVENT_OP_HISTORY',
timecolumn,
deltahours,
minitimestamp,
lastpruned
)
COMMIT
END
UPDATE ANA_LASTRUN_CNTL with Current Date value
Note: The view structure will not be consistent after creation of
additional history tables. We need to build the History View again
depending
part_num:=MAX(PART_NUM) FROM PARTITION_CNTL WHERE
TABLENAME='ANA_EVENT_OP_HISTORY'
Call PC_REFRESH_VIEW_STRUCTURE part_num
END
24
Reference Guide
About the ImpactPortal universe
About the ImpactPortal universe

Table 1-6 contains the characteristics of the ImpactPortal universe.
Table 1-6: Characteristics of the ImpactPortal universe
Name
Value
Description
Name
ImpactPortal
Description

for reporting on BMC Impact Portal
Connection
ImpactPortal

the BMC Impact Portal database
Classes and Objects
Statistics
Universe metrics.
51 classes
639 objects
126 conditions
21 tables
15 alias
33 joins
0 contexts
14 hierarchies
Controls

characters


SQL Query
Multiple SQL Statements for each

Context: true
Measure: true
Operators: true


Allow Selection of Multiple Contexts:
false
Allow Complex Operands in Query
Panel: true
Stored procedure, table, and view

This section contains information about the stored procedure, table, and view that
is installed by BMC Analytics for BSM.

25
Category
Name
Description
Stored
procedure
POPULATE_FISCAL
_CALENDAR

view. This stored procedure is invoked
through the command line interface following
the installation. The script that inserts the
stored procedure is
SQL.
Table
CDE_FISCAL_CALE
NDAR

and the duration of the fiscal calendar; this
table is populated by the procedure
View
ANA_FISCAL_CAL
ENDAR

procedure
About the PortalCDE universe

Table 1-7 contains the characteristics of the PortalCDE universe.
Table 1-7: Characteristics of the PortalCDE universe
Name
Value
Description
Name
PortalCDE
Description

for reporting on BMC Performance
Manager Portal
Connection
PortalCDE

the BMC Performance Manager Portal
database
Classes and Objects
Statistics
29 classes
Universe metrics.
127 objects
67 conditions
9 tables
2 alias
6 joins
0 contexts
0 hierarchies
26
Reference Guide
About the PortalCDE universe
Name
Value
Description
Controls

characters
SQL Query

Context: true
Measure: true
Operators: true


Allow Selection of Multiple Contexts:
false
Allow Complex Operands in Query
Panel: true

installed by BMC Analytics for BSM.
Category
Name
Description
Stored
procedure
POPULATE_FISCAL
_CALENDAR

view. This stored procedure is invoked
through the command line interface following
the installation. The script that inserts the
stored procedure is
SQL.
Table
CDE_FISCAL_CALE
NDAR

and the duration of the fiscal calendar; this
table is populated by the procedure
View
ANA_FISCAL_CAL
ENDAR

procedure

27
Fiscal calendar data

BMC Analytics for BSM provides a custom table called
ANA_FISCAL_CALENDAR that provides fiscal calendar data. The fiscal calendar
data consists of day, week, month, quarter, year, and their derived values (such as
running day, running week, and so on). The BMC Analytics for BSM fiscal
calendar year can start on the first day of any month and end one year from the
start date. For example, if you specify April 1, 2009 as the beginning of the fiscal
calendar, the end date occurs March 31, 2010.
If you report on BMC IT Service Management applications, the product also
provides a BMC Remedy AR System form called ANA:Fiscal_Calendar. This form
must be loaded into the BMC Remedy AR System database and then populated.
If you report on BMC ProactiveNet Performance Management, BMC Impact
Portal, or BMC Performance Manager Portal, the installation loads the table into
the BMC product database, but you must manually populate it by running the
procedure PC_POPULATE_FISCAL_CALENDAR following the installation. For
more information about running this procedure, see BMC Analytics for Business
Service Management Installation and Administration Guide.
ANA:Fiscal_Calendar form
This form must be loaded into the BMC Remedy AR System database using the
BMC Remedy Mid Tier. The ANA:Fiscal_Calendar form enables you to analyze
trends based on fiscal calendar data. To support trend analysis, each date object in
the BMC_CORE_BMC_BASEELEMENT table is joined with the corresponding
date value object in the ANA_FISCAL_CALENDAR view.
Following the installation of BMC Analytics for BSM, you use BMC Remedy Mid
Tier to specify the start month, start year, and number of years of the fiscal calendar
using the BMC Remedy AR System ANA:Fiscal_Calendar form. The workflow for
the ANA:Fiscal_Calendar uses the Populate_Fiscal_Calendar stored procedure to
load the ANA_FISCAL_CALENDAR table, and the results are displayed at the
bottom of the ANA:Fiscal_Calendar form.
ANA_FISCAL_CALENDAR view
Transaction dates (for example, Base_element_create_date) are stored in the BMC
Remedy AR System and BMC ProactiveNet Performance Management database
in UNIX Epoch Time (number of seconds since January 1, 1970). They are not
absolute dates, and there is a time component attached to each of them. When joins
are created with the ANA_FISCAL_CALENDAR view (which has absolute dates),
the fn_adusted_date() function is used to convert into the local Time Zone and
truncated to absolute dates to make trend analysis meaningful.
For example, the conversion formula used for a report showing the Purchase Date
dimension on a computer running Microsoft SQL Server is as follows:
dbo.fn_adjusted_date(AM_BMC_CORE_BMC_BASEELEMENT.PurchaseDate)
28
Reference Guide
Fiscal calendar data
The conversion formula used for a report showing the Purchase Date dimension
on a computer running Oracle is:
fn_adjusted_date(AM_BMC_CORE_BMC_BASEELEMENT.PurchaseD
ate)
The join definition used for Purchase Order.Date_Ordered on a computer running

Microsoft SQL Server is:
isnull(datediff(ss,'01-01-1970',CAST(CONVERT(VARCHAR(10),
dbo.fn_adjusted_date(AM_BMC_CORE_BMC_BASEELEMENT.PurchaseDate),
111) AS
DATETIME)),-99)=ASSET_AGE_CALENDAR.Date_Value
The join definition used for Purchase Order.Date_Ordered on a computer running

Oracle follows.
nvl((trunc(fn_adjusted_date(AM_BMC_CORE_BMC_BASEELEMENT.PURCHASEDA
TE)) - to_date('01-JAN-1970','DD-MON-YYYY'))*86400,-99) =
ASSET_AGE_CALENDAR.Date_Value
Table 1-8 shows the detailed structure of the ANA_FISCAL_CALENDAR view.

Each row in the view represents a date, and each column represents a separate
component of the date.
Table 1-8: ANA_FISCAL_CALENDAR view structure
Column name
Data type
Description
Assigned_to
Varchar
The name of the product.

Example: BMC Analytics
Create_date
Integer
Epoch value for the day on which the fiscal table was
created.
Example: 1252886400
Day_name
Varchar
Name of the corresponding week day

Example: Friday
Day_of_Year
Integer
Day of Fiscal Year
Epoch_value
Integer
Epoch value of the corresponding date

Example: 1199404800
Last_modified_by
Varchar
Modified user name

Month_of_Year
Integer
Month of Fiscal Year
Month_of_Quarter
Integer
Month of Quarter
Month_Name
Varchar
Name of Month
Example: January
Quarter_of_Year
Integer
Quarter of Fiscal Year
Quarter_Name
Varchar
Quarter of Fiscal Year Combined With Year

Example: 2005Q2
Modified_date
Integer
Day on which fiscal table was last modified

Example: 1252886400

29
Table 1-8: ANA_FISCAL_CALENDAR view structure

Column name
Data type
Description
Request_id (primary
key)
Varchar
The actual date value in string format yyyymmdd
Running_Day
Integer
Running day
Running_Week
Integer
Running week
Running_Month
Integer
Running month
Running_Quarter
Integer
Running quarter
Running_Year
Integer
Running year
Short_description
Varchar
The product name
Example: 20080104

Start_Month
Integer
Currently not in use
Status
Integer
Currently not in use
Submitter
Varchar
The name of the product.

Type_of_day
Varchar
Whether the day is a work day or a holiday

Example: Workday
Week_of_Year
Integer
Week of Fiscal Year
Week_Name
Varchar
Week of year combined with year

Example: Week 7 of 2005
YEAR
Integer range (1900 2100)
The year value for the corresponding day

Example: 2008
Date conversion functions

If you use BMC Analytics for BSM to report on BMC Remedy ITSM applications,
the function FN_ADJUSTED_DATE performs the task of converting database
EPOCH dates to human-readable date formats.
If you use BMC Analytics for BSM to report on BMC ProactiveNet Performance
Management, BMC Performance Manager Portal, and BMC Impact Manager, both
functions FN_GET_EPOCH_DATE and FN_ADJUSTED_DATE are used, based
on reporting needs. Both functions are used to boost performance while querying
for reports on high volume data.
FN_ADJUSTED_DATE function
All the date objects in the universe have a formula embedded which looks like the
following example for the reported_date from the HPD_HELP_DESK form:
Fn_adjusted_date(HPD_HELP_DESK.Reported_Date)
The fn_adjusted_date function performs the following tasks:
30
Converts the date from the UNIX Epoch format to a normal date format.
Reference Guide
Date conversion functions
Offsets the date from GMT for the time zone of the BMC Analytics for BSM
instance (as defined in the ANA_TIMEZONE_INFO table)
Returns the result in the date format instead of the Epoch format
The pseudo code for the function fn_adjusted_date follows. Note that the syntax
may vary if you are reporting on the BMC ProactiveNet Performance Management
database.
Function Name: fn_adjusted_date
Parameters: InputDate, number, date in the UNIX Epoch format
Pseudo Code:
FUNCTION Fn_Adjusted_date (Parameters: Input Date Number)
BEGIN Function
Input_GMT_datetime = Parameter input date converted to date format;
Input_Year = Fetch the Year value from the Input_GMT_datetime
IF REGION_FLAG is not set to 'Y' for any region in ANA_TIMEZONE_INFO
table
THEN OutPut_Date = Input_GMT_datetime (default to GMT format)
IF REGION_FLAG='Y',
Fetch DST Start time, DST End time, DST flag,Offset
from ANA_TIMEZONE_INFO table for a regioncode for which flag='Y'
Note: DST_Flag='Y' indicates that this region observes Daylight saving
time
IF DST_Flag='Y' THEN
-- IF Input Date falls into DST, add one hour to input gmt time and
offset value
IF Input_GMT_datetime between DST Start time and DST End time
THEN
OutPut_Date := Input_GMT_datetime + (offset
+ 1 hour);
-- Else add offset value to input gmt time
ELSE
OutPut_Date := Input_GMT_datetime + offset;
END IF;
ELSE -- IF DST_Flag='N'
OutPut_Date := Input_GMT_datetime + offset;
END IF;
END IF;
Return Output Date;
END Function;
FN_GET_EPOCH_DATE function
The FN_GET_EPOCH_DATE function performs the following tasks:
Converts the date from the normal date format to UNIX Epoch format.

31
Offsets the date from GMT for the time zone of the BMC Analytics for BSM
instance (as defined in the ANA_TIMEZONE_INFO table)
Returns the result in the date format instead of the Epoch format
Function Name: fn_get_epoch_date

Parameters: InputDate, DateTime, date in yyyy/mm/dd hh:mm:ss am format.
The pseudo code for the FN_GET_EPOCH_DATE function follows:
FUNCTION FN_GET_EPOCH_DATE (Parameters: Input Date DateTime)
BEGIN Function
Input_GMT_datetime = Parameter input date
Input_Year = Fetch the Year value from the Input_GMT_datetime
IF REGION_FLAG is not set to 'Y' for any region in
ANA_TIMEZONE_INFO table
THEN OutPut_Date = Input_GMT_datetime (default to GMT format)
IF REGION_FLAG='Y',
Fetch DST Start time, DST End time, DST flag,Offset
from ANA_TIMEZONE_INFO table for a regioncode for which flag='Y'
Note: DST_Flag='Y' indicates that this region observes Daylight
saving time
IF DST_Flag='Y' THEN
-- IF Input Date falls into DST, add one hour to input gmt time
and
offset value
IF Input_GMT_datetime between DST Start time and DST End time
THEN
OutPut_Date := Convert (Input_GMT_datetime) to Epoch + (offset+ 1
hour);
-- Else add offset value to input gmt time
ELSE
OutPut_Date := Convert( Input_GMT_datetime) to Epoch + offset;
END IF
ELSE -- IF DST_Flag='N'
OutPut_Date := Conver( Input_GMT_datetime) to Epoch + offset;
END IF;
END IF;
Return Output Date;
END Function;
Timezone table and supported timezones

This section contains information about the timezone table and the supported
timezones.
32
Reference Guide
ANA_TIMEZONE_INFO table
A custom table is maintained in the BMC product databases with the name
ANA_TIMEZONE_INFO. This table is created during the installation process of
BMC Analytics for BSM.
The ANA_TIMEZONE_INFO table is used by the function FN_ADJUSTED_DATE
to convert epoch time values to human-readable date and time values, depending
upon the preferred time zone selected by customer during installation. The table is
also used by the function FN_GET_EPOCH_DATE to convert a given date and
time value to epoch format.
During the installation, you select the preferred timezone for the reports, and the
REGION_FLAG for that timezone is set to Y for the selected timezone.
Column name
Data type
Description
TIMEZONE_LOC_
ID
NUMBER
Timezone ID
COUNTRY
VARCHAR2(50 BYTE)
Country Name
COUNTRY_CODE
VARCHAR2(50 BYTE)
Country Code
REGION
VARCHAR2(50 BYTE)
Specific Region in a Country based

on Timezone
REGION_CODE
VARCHAR2(50 BYTE)
Region Code
DST_FLAG
VARCHAR2(1 BYTE)
Flag indicates whether the region

observes DST 'Y' or not 'N'
REGION_FLAG
VARCHAR2(1 BYTE)
Set 'Y' for the region which client

interested in
START_YEAR
VARCHAR2(50 BYTE)
Daylight saving Time (DST)

Starting Year
START_MONTH_
LAST_DT
VARCHAR2(50 BYTE)
DST Starting Month Last Date(If

start month is April then 31-APRIL
etc)
START_WEEK_D
AY
VARCHAR2(50 BYTE)
DST Starting Week Day Name in a

week
START_WEEK
VARCHAR2(10 BYTE)
DST Starting Week Number (First/

Second/Third/Fourth/Last) in a
Month
END_YEAR
VARCHAR2(50 BYTE)
Daylight saving Time (DST) Ending

Year
END_MONTH_LA
ST_DT
VARCHAR2(50 BYTE)
DST Ending Month Last Date(If End

month is September then 30SEPTEMBER etc)
END_WEEK_DAY
VARCHAR2(50 BYTE)
DST Ending Week Day Name in a

week

33
34
Column name
Data type
Description
END_WEEK
VARCHAR2(10 BYTE)
DST Ending Week Number in a

Month
START_MONTH_
LAST_NUM
VARCHAR2(50 BYTE)
DST Starting Month Last Date

Number (31-04 for April etc)
START_WEEK_D
AY_NUM
NUMBER
DST Starting Week Day Number in

a week (01 for Sunday, 02 for
Monday etc)
START_WEEK_N
UM
NUMBER
DST Starting Week Number in a

month (01 for First
start_week_day_number etc)
END_MONTH_LA
ST_NUM
VARCHAR2(50 BYTE)
DST Starting Month Last Date

Number ( 30-09 for September etc)
END_WEEK_DAY
_NUM
NUMBER
DST Ending Week Day Number in a

week (01 for Sunday, 02 for Monday
etc)
END_WEEK_NU
M
NUMBER
DST Ending Week Number in a

month (02 for Second
start_week_day_number etc)
DST_START_TIME
VARCHAR2(20 BYTE)
When the DST Starts for this region
DST_END_TIME
VARCHAR2(20 BYTE)
When the DST Ends for this region
GMT_START_TIM
E
VARCHAR2(20 BYTE)
Equivalent GMT Start time for this

Region (DST_Start_Time +
GMT_TimeDifference)
FLOAT
(ProactiveNet
universe only)
GMT_SEC_DIFFER
ENCE
Contains the GMT adjustment

value in seconds. Example: -5.30
GMT adjustments will be -19800;
used by the function
FN_GET_EPOCH_DATE
GMT_END_TIME
VARCHAR2(20 BYTE)
Equivalent GMT End time for this

Region (DST_End_Time +
GMT_TimeDifference)
GMT_TIMEDIFFE
RENCE
VARCHAR2(10 BYTE)
Time difference(offset) from GMT

for this Region
GMT_HRS_Mins
NUMBER
Time difference(offset) in Number

from GMT for this Region
Reference Guide
Timezone support
The Populate_Fiscal_Calendar stored procedure that populates the
ANA_FISCAL_CALENDAR table supports multiple timezones. During the BMC
Analytics for BSM installation, you were prompted for the timezone that you
wanted to use in the reports. You can also change the timezone that is used at any
time. The region code for the timezone in use is stored in the
ANA_TIMEZONE_INFO table. See ANA_TIMEZONE_INFO table on page 33
for more information.
Table 1-9 contains a list of timezones that are supported by the
ANA_FISCAL_CALENDAR table if you report using BMC Remedy AR System
server. Table 1-10 on page 38 contains a list of timezones that are supported by the
ANA_FISCAL_CALENDAR table if you report using BMC ProactiveNet
Performance Manager.
Table 1-9: Supported timezones for BMC Remedy AR System server data source (Sheet 1 of 4)
Country
Region
GMT
Region Code
GMT time difference
GMT
+00.00
Africa/Casablanca
Morocco
WET
+00.00
Africa/Harare
Zimbabwe
CAT
+02.00
Africa/Johannesburg
South Africa
SAST
+02.00
Africa/Monrovia
Liberia
GMT
+00.00
Africa/Nairobi
Kenya
EAT
+03.00
America/Anchorage
United States of America
AKST
-09.00
America/Argentina/
Buenos_Aires
Argentina
ART
-03.00
America/Bogota
Colombia
COT
-05.00
America/Caracas
Venezuela
VET
-04.30
America/Chicago
CST
-06.00
America/Denver
MST
-07.00
America/Georgetown
Guyana
GYT
-04.00
America/Godthab
Greenland
WGT
-03.00
America/Halifax
Canada
AST
-04.00
America/Hermosillo
Mexico
MST
-07.00
America/Inuvik
Canada
MST
-07.00
America/La Paz
Bolivia
BOT
-04.00
America/Lima
Peru
PET
-05.00
America/Los_Angeles
PST
-08.00
America/Mazatlan
Mexico
MST
-07.00
America/Mexico_City
Mexico
CST
-06.00
America/Midway Islands United States of America
SST
-11.00
America/New_York
EST
-05.00
America/Noronha
Brazil
FNT
-02.00

35
Country
Region
Region Code
GMT time difference
America/Phoenix
MST
-07.00
America/Puerto Rico
Puerto Rico (San Juan)
AST
-04.00
America/Quito
Ecuador
ECT
-05.00
America/Rankin_Inlet
Canada
CST
-06.00
America/Regina
Canada
CST
-06.00
America/Santiago
Chile
CLT
-04.00
America/Sao_Paulo
Brazil
BRT
-03.00
America/St_Johns
Canada
NST
-03.30
America/Tijuana
Mexico
PST
-08.00
America/Toronto
Canada
EST
-05.00
America/Vancouver
Canada
PST
-08.00
Asia/AbuDhabi
UAE
GST
+04.00
Asia/Almaty
Kazakstan
ALMT
+06.00
Asia/Baghdad
Iraq
AST
+03.00
Asia/Bangkok
Thailand
ICT
+07.00
Asia/Colombo
Sri Lanka
IST
+05.30
Asia/Hanoi
Vietnam
ICT
+07.00
Asia/Hong_Kong
Hong Kong
HKT
+08.00
Asia/Irkutsk
Russia
IRKT
+08.00
Asia/Jakarta
Indonesia
WIB
+07.00
Asia/Jerusalem
Israel
IST
+02.00
Asia/Karachi
Pakistan
PKT
+05.00
Asia/Katmandu
Nepal
NPT
+05.45
Asia/Kolkata
INDIA
IST
+05.30
Asia/Krasnoyarsk
Russia
KRAT
+07.00
Asia/Kuala Lumpur
Malaysia
MYT
+08.00
Asia/Novosibirsk
Russia
NOVT
+06.00
Asia/Pyongyang
North Korea
KST
+09.00
Asia/Riyadh
Saudi Arab
AST
+03.00
Asia/Seoul
South Korea
KST
+09.00
Asia/Shanghai
CHINA
CST
+08.00
Asia/Singapore
Singapore
SGT
+08.00
Asia/Taipei
Taiwan
CST
+08.00
Asia/Tbilisi
Georgia
GET
+04.00
Asia/Tokyo
Japan
JST
+09.00
Asia/UlaanBataar
Mongolia
ULAT
+08.00
Asia/Yakutsk
Russia
YAKT
+09.00
Atlantic/Azores
Portugal
AZOT
-01.00
36
Reference Guide
Country
Region
Region Code
GMT time difference
Atlantic/Cape_Verde
Cape Verde
CVT
-01.00
Australia/Adelaide
Australia
CST
+09.30
Australia/Brisbane
Australia
EST
+10.00
Australia/
Canberra,Melbourne,Syd
ney
Australia
EST
+10.00
Australia/Darwin
Australia
ACST
+09.30
Australia/Hobart
Australia
EST
+10.00
Australia/Perth
Australia
WST
+08.00
Europe/Amsterdam
Netherlands
CET
+01.00
Europe/Baku
Azerbaijan
AZT
+04.00
Europe/Belgrade
Serbia
CET
+01.00
Europe/Berlin
Germany
CET
+01.00
Europe/Bern
Switzerland
CET
+01.00
Europe/Bratislava
Slovak Republic
CET
+01.00
Europe/Brussels
Belgium
CET
+01.00
Europe/Bucharest
Romania
EET
+02.00
Europe/Budapest
Hungary
CET
+01.00
Europe/Copenhagen
Denmark
CET
+01.00
Europe/Dublin
Ireland
IST
+00.00
Europe/Edinburgh
Scotland
BST
+00.00
Europe/Ekaterinburg/
Yekaterinburg
Russian Federation
YEKT
+05.00
Europe/Helsinki
Finland
EET
+02.00
Europe/Istanbul
Turkey
EET
+02.00
Europe/Kamchatka
Russian Federation
PETT
+11.00
Europe/Lisbon
Portugal
WET
00.00
Europe/Ljubljana
Slovenia
CET
+01.00
Europe/London
Britain (UK)
BST
-00.00
Europe/Madrid
Spain
CET
+01.00
Europe/Magadan
Russian Federation
MAGT
+11.00
Europe/Moscow
Russian Federation
MSK
+03.00
Europe/New Caledonia
France
NCT
+11.00
Europe/Novosibirsk
Russian Federation
NOVT
+06.00
Europe/Paris
France
CET
+01.00
Europe/Prague
Czech Republic
CET
+01.00
Europe/Riga
Latvia
EET
+02.00
Europe/Rome
Italy
CET
+01.00
Europe/Sarajevo
Bosnia and Herzegovina
CET
+01.00

37
Country
Region
Region Code
GMT time difference
Europe/Skopje
Macedonia
CET
+01.00
Europe/Sofija/Sofia
Bulgaria
EET
+02.00
Europe/St. Petersburgh/
Saint Petersburg
Russian Federation
MSK
+03.00
Europe/Stockholm
Sweden
CET
+01.00
Europe/Tallinn
Estonia
EET
+02.00
Europe/Tashkent
Uzbekistan
UZT
+05.00
Europe/Vienna
Austria
CET
+01.00
Europe/Vilnius
Lithuania
EET
+02.00
Europe/Vladivostok
Russian Federation
VLAT
+10.00
Europe/Volgograd
Russian Federation
MSK
+03.00
Europe/Warsaw
Poland
CET
+01.00
Europe/Yerevan
Armenia
AMT
+04.00
Europe/Zagreb
Croatia
CET
+01.00
Oceania/Solomon Islands Solomon Islands (Honiara)
SBT
+11.00
Pacific/
Auckland,Wellington
New Zealand
NZST
+12.00
Pacific/Fiji
Fiji
FJT
+12.00
Pacific/Guam
Guam
ChST
+10.00
Pacific/Honolulu
HST
-10.00
Pacific/Majuro
Majuro
MHT
+12.00
Pacific/Pago_Pago
Samoa
SST
-11.00
Pacific/Port_Moresby
Papua New Guinea
PGT
+10.00
Pacific/Samoa/Apia
Samoa
WST
-11.00
Pacific/Tongatapu
Tonga
TOT
+13.00
Table 1-10: Supported timezones for BMC ProactiveNet Performance Manager data source (Sheet 1 of 3)
Region
Country
Region code
GMT time difference
GMT
(null)
GMT
0.00
America/New_York
EST
-5.00
America/Chicago
CST
-6.00
America/Denver
MST
-7.00
America/Phoenix
MST
-7.00
America/Los_Angeles
PST
-8.00
America/Anchorage
AKST
-9.00
Pacific/Honolulu
HST
-10.00
America/St_Johns
Canada
NST
-3.30
America/Halifax
Canada
AST
-4.00
America/Toronto
Canada
EST
-5.00
38
Reference Guide
Region
Country
Region code
GMT time difference
America/Rankin_Inlet
Canada
CST
-6.00
America/Regina
Canada
CST
-6.00
America/Inuvik
Canada
MST
-7.00
America/Vancouver
Canada
PST
-8.00
America/Mexico_City
Mexico
CST
-6.00
America/Mazatlan
Mexico
MST
-7.00
America/Hermosillo
Mexico
MST
-7.00
America/Tijuana
Mexico
PST
-8.00
Asia/Shanghai
China
CST
8.00
Asia/Kolkata
India
IST
5.30
Asia/Tokyo
Japan
JST
9.00
Europe/London
Britain (UK)
BST
0.00
Europe/Paris
France
CET
1.00
Europe/Berlin
Germany
CET
1.00
Europe/Copenhagen
Denmark
CET
1.00
Europe/Belgrade
Serbia
CET
1.00
Europe/Sarajevo
Bosnia and Herzegovina
CET
1.00
Europe/Istanbul
Turkey
EET
2.00
Africa/Johannesburg
South Africa
SAST
2.00
Asia/Riyadh
Saudi Arab
AST
3.00
Africa/Nairobi
Kenya
EAT
3.00
Asia/AbuDhabi
UAE
GST
4.00
Asia/Katmandu
Nepal
NPT
5.45
Asia/Novosibirsk
Russia
NOVT
6.00
Asia/Krasnoyarsk
Russia
KRAT
7.00
Asia/Irkutsk
Russia
IRKT
8.00
Asia/Yakutsk
Russia
YAKT
9.00
Asia/Bangkok
Thailand
ICT
7.00
Asia/Hong_Kong
Hong Kong
HKT
8.00
Asia/Singapore
Singapore
SGT
8.00
America/Bogota
Colombia
COT
-5.00
Atlantic/Cape_Verde
Cape Verde
CVT
-1.00
Europe/Madrid
Spain
CET
1.00
Europe/Rome
Italy
CET
1.00
Europe/Stockholm
Sweden
CET
1.00
Europe/Warsaw
Poland
CET
1.00
America/Lima
Peru
PET
-5.00

39
Region
Country
Region code
GMT time difference
Asia/Seoul
South Korea
KST
9.00
Asia/Pyongyang
North Korea
KST
9.00
40
Reference Guide
Chapter
Universe and report customization

templates
This section contains procedures and best practices for customizing the ITSM
universe and reports, as well as templates for recording your customizations.
This section contains the following topics:
Universe customization templates on page 42

Report customizations on page 43
Variable additions and Changes on page 46
Chapter 2 Universe and report customization templates

41
Universe customization templates

Use the table in this section to record customizations that you make to any of the
universes. Compare the parameter values in the Old Value column with the values
in your environment and record the new value in the New Value column.
The table below provides the old value from the ITSM universe. You can create a
table for any of the installed universes, however, by recording the universe
parameters and appropriate values.
IMPORTANT
Adding new classes and objects to the universe is subject to the BMC Software
customization policy, available at http://www.bmc.com/support/customizationpolicy.html. If you modify the BMC Remedy AR System database structure by
adding, removing, or changing ITSM application forms, before you can use them,
you must import the universe by selecting File => Import using the
BusinessObjects Designer tool. You must then refresh the universe structure, by
selecting View => Refresh Structure in the BusinessObjects Designer tool. Any
time you modify the ITSM universe or reports, you should export the universe by
selecting File > Export using the SAP BusinessObjects Designer tool.
Table 2-11: Universe customization values
Parameter Name
Old Value
ANSI92
Yes
AUTO_UPDATE_QUERY
No
BLOB_COMPARISON
No
BOUNDARY_WEIGHT_TABLE
-1
COLUMNS_SORT
No
COMBINED_WITH_SYNCHRO
No
COMBINE_WITHOUT_PARENTHESIS
No
COMPARE_CONTEXTS_WITH_JOINS
Yes
CORE_ORDER_PRIORITY
No
CORRECT_AGGREGATED_CONDITIO
NS_IF_DRILL
No
CUMULATIVE_OBJECT_WHERE
No
DECIMAL_COMMA
No
DISTINCT_VALUES
DISTINCT
END_SQL
EVAL_WITHOUT_PARENTHESIS
No
FILTER_IN_FROM
No
FIRST_LOCAL_CLASS_PRIORITY
No
FORCE_SORTED_LOV
No
JOIN_BY_SQL
No
MAX_INLIST_VALUES
-1
42
Reference Guide
New Value
Report customizations
Parameter Name
Old Value
REPLACE_COMMA_BY_CONCAT
No
SHORTCUT_BEHAVIOR
Successive
THOROUGH_PARSE
No
UNICODE_STRINGS
No
Sql Name
Value
New Value
Multiple SQL Statements for each Context TRUE

Measure
FALSE

Operators
TRUE
Cartesian Products
Warn
Allow Selection of Multiple Contexts
FALSE
Allow Use of Subqueries
TRUE
Allow Complex Operands in Query Panel TRUE

Control Name
Value
Limit Execution Time Value
600
Limit Size of Long Text Object Value
4000
Limit Size of ResultSet Value
5000
Universe Details
Value
Universe Name
ITSM
Universe Full Path
C:\Documents and
Settings\satish.mallavolu\De
sktop\ITSM25Unv\ITSM.unv
Universe Connection
shared-conn
Universe Current Owner

Universe Creation Date
20/03/2007
Universe Modified Date
13/10/2008
Before performing any modifications to a report, create a backup of the original
report and store the backup in a designated backup folder. The following example
shows a suggested naming convention for the backup folder:
<original_Folder_name>_Backup<date>
Use the template provided in this section as a guide for recording modifications to
the BMC Analytics for BSM reports.
43
IMPORTANT
Any time you modify the ITSM universe or reports, you should export the
universe by selecting File > Export using the BusinessObjects Designer tool.
Section 1: Report Identification

Report Name
BSA
<Business Systems Analyst>
Business Justification
For Customization
Request Type
New Report? Modification? Scheduled? On-Demand?
Section 2: Data Selection/Grouping/Sorting/Parameters

New Objects Included in the
report
Objects Modified with old and
new formulae
Objects Deleted from the
report
Change in Sort Order
<Dimension 1>, <Dimension 2> .
Change in Grouping
<Dimension 1>
New/Modified Formulae
Other Description
New and Changed parameter description

Field Name
Field Type
Selection Type
Initial Values
Time Period to
Analyze
Integer
Entry
24
Multiple
Selection
* = All
<Dimension 1> Drop Down List
Data Source
This parameter will

be in hours
<Data source
1>
NOTE
All parameters should be used in an 'AND' fashion.
44
Reference Guide
Other Requirements
A blank parameter
in this field indicates
that it should not be
included in the
query/filter
Section 3: Report Presentation Changes

Format
PDF: __ (Y/N)
Cover Page
Company Logo (left-hand corner)
Excel: __ (Y/N)
Report title (centered)

Report Information - an overview of the report's content
Report Selection Criteria - an overview of the report's query
Contact Information - who to contact with data questions
Page Header
Report Title
"Jump to Top of Data" link
Page Footer
Last Run Date/Time

Page number
Group Header
Group Footer
Other special
requirements
The Chart will be presented after the Cover Page but before the actual data.
The Report will use all of the default colors of the Analytics tool except in the chart
which will follow colors as supplied
The Report will be presented in Landscape Page Format
Chart Requirements
Display
None?
Per Report?
Per Group? If Yes, describe

details:
Chart Titles
"First Call Resolution (" + Count of all Incidents in report + ")"
Chart Type with

Details
This report will utilize a bar chart

The X Axis will show the Initials of each Associate included in the report:
The Y Axis will indicate the number of incidents for each Associate
Drill Down:
When the Total in the report is clicked, the user will be taken to the first page of the data
area of the report
When any of the bars or initials are clicked, the user will be taken to the group in the
report of the selected Associate.
Please note that the Total bar should NOT be included
Field Description
Field Name on
Report
Field Name of Form Name /DB Table Field Name

View
Name
of DB
Incident ID+
Incident ID
HPD:Help Desk
Field Type Special Formatting or Other

& Length Notes
on Report
Incident_ID
HPD_Help_Desk
Priority
Priority
HPD:Help Desk
HPD_Help_Desk
Priority
Selection
60

45
Field Name on
Report
Field Name of Form Name /DB Table Field Name

View
Name
of DB
Field Type Special Formatting or Other

& Length Notes
on Report
Summary
Summary
Summary
Character
100
HPD_Help_Desk
Product
Name
Character
254
HPD:Help Desk
Status
Selection
HPD:Help Desk
HPD_Help_Desk
Product Name Product

Name
Status
Status
HPD:Help Desk
HPD_Help_Desk
Assigned
Group
Assigned
Group
HPD:Help Desk
Assignee ID
Assignee ID
60
HPD_Help_Desk
Assigned
Group
Character
254
HPD:Help Desk
Assignee
Selection
HPD_Help_Desk
Reported Date Reported
Date
HPD:Help Desk
HPD_Help_Desk
Product Name will be pulled

from Resolution Product
Classification if ticket is in a
'Resolved,' 'Closed,' or
'Cancelled' status otherwise
use Product Classification
69
Reported
_Date
Date
Variable additions and Changes

Field Name on
Data Provider
Field Name
of Form
Form Name /DB Table Field Name Field Type

Name
of DB
& Length
on Report
Incident ID+
Incident ID
HPD:Help Desk
Priority
Priority
Character
HPD_Help_Desk
Incident_I
D
HPD:Help Desk
Priority
Selection
HPD_Help_Desk
Summary
Summary
HPD:Help Desk
15
60
Summary
HPD_Help_Desk
Character
100
Product Name Product

Name
HPD:Help Desk
Product
Name
Character
HPD_Help_Desk
Status
HPD:Help Desk
Status
Selection
Status
HPD_Help_Desk
Assigned
Group
Assigned
Group
HPD:Help Desk
Assignee ID
Assignee ID
60
Character
HPD_Help_Desk
Assigned
Group
HPD:Help Desk
Assignee
Selection
HPD_Help_Desk
Reported Date Reported
Date
46
254
HPD:Help Desk
HPD_Help_Desk
254
69
Reported
_Date
Date
Reference Guide
Special Formatting or Other

Notes
Chapter
Report conditions and default views
Report conditions
This section contains the list of conditions for each report, by application. For a list
of all of the conditions available in the universes, see the Self Help Document ID
KA345616 in the BMC Knowledge Base.
For more information about report conditions and the procedure to add a
condition to a hyperlinked report, see BMC Analytics for Business Service
Management Installation and Administration Guide.
Chapter 3 Report conditions and default views

47
The following two tables contain the list of reports that contain predefined
conditions. The first table shows the predefined reports that have hyperlinks, the
report that is shown when the hyperlinks are traversed, and the conditions used to
filter the parameter information for the report shown. The second table contains a
list of tabbed reports that contain hyperlinks, and the conditions used to filter the
information from the Summary tab to the Details tab.
Table 3-1: Hyperlinked reports and preconfigured conditions
Application
Report with hyperlinks
Resulting report
Asset
Management
A01a - Software License A01b - Software

Compliance
Compliance Detail
Conditions
Asset
Management
Asset
Management
A01b - Software
Compliance Detail
A01c - Compliance
Summary for
Software Product
A05a - Inventory Profile A05b - Inventory

Profile - Drill-Down
View
Asset
Management
A06a - Asset Aging
A06b - Asset Aging Drill-Down View
Asset
Management
A08a - Asset
Relationship Analysis Selection of Asset
A08b - Asset
Relationship
Analysis
Product Categorization Tier 2

Product Model Version
Manufacturer Name
Software Product Compliance
Product Name
Number of Products
Product Name
Compliance Status
Contract ID
Manufacturer Name
Product Name
Dataset Name
Asset Aging Time Range
Manufacturer
Product
CI Name
CI ID
Tag Number
Change
Management
C01 - Forward Schedule C01 - Forward

of Changes (FSC)
Schedule of Changes
(FSC) - Detail
Change ID
Change
Management
C03 - Open Changes By C03 - Open Changes

Status
By Status - Detail
Status Value
Change
Management
C04 - Closed Changes

Summary
Reporting Period Start Date

Reporting Period End Date
Company
C04 - Closed Changes

Summary - Detail
Change
Management
48
C07 - Change Requests

That Errored Out
C07 - Change
Requests That
Errored Out -Detail
Reference Guide

Company
Report conditions

Application
Resulting report
Conditions
Change
Management
C08 - Change Lifecycle

and Process Efficiency
C08 - Change
Lifecycle and Process
Efficiency - Detail

Company
Status Value
Change
Management
C09 - Open Changes By C09 - Open Changes

Phase
By Phase - Detail
Company
Stage Value
Change
Management
C10 - Forward Schedule C10 - Forward

of Tasks
Schedule of Tasks Detail
Period
Change
Management
C13 - Change Lead Time C13 - Change Lead

Report
Time Report - Detail

Company
Timing Value
Change
Management
C15 - Change Backlog

Report
C15 - Change Backlog

Report - Detail
Status Value
CMDB
C01a - Discovery
Datasets Comparison
C01b - Discovery
Datasets Comparison
- Drill-Down View
Manufacturer Name
Product CategorizationTier 1
Product Name
Datasets
CMDB
C04a - Staleness
Analysis of Discovery
Data
C04b - Staleness
Data -Drill Down I
Days Last Refreshed
CMDB
C04b - Staleness
Data -Drill Down I
C04c - Staleness
Data -Drill Down II
Days Last Refreshed

Manufacturer Name
Product Name
Datasets
Configuration
Drift
Management
D01 - Compliance
Report
D01 - Compliance
Report - Detail
Configuration
Drift
Management
D04 - Drift Report for

Selected Business
Services
D04 - Drift Report for

Selected Business
Services - Detail
Configuration
Drift
Management
D07 - Unapproved
Drifts for Selected
Business Services
D07 - Unapproved
Drifts for Selected
Business Services Detail
Target Name
Drift Date-Time for Compliance Check
Target Name
Baseline Name
Business Service Name
Business Service Name value
Business Service Name
Business Service Name value

49

Application
Resulting report
Conditions
Event
Management
E01 - Mean Response

Time by Device
E01a - Mean
Response Time Detail by Device
Event
Management
E01 - Mean Response

Time by Device
E01a - Mean
Response Time Detail by Group
Event
Management
E01 - Mean Response

Time by Device
E01a - Mean
Response Time Detail by Location
Event
Management
E01 - Mean Response

Time by Device
E01a - Mean
Response Time Detail by Service
Event
Management
E01 - Mean Response

Time by Device
E01a - Mean
Response Time Detail by User
Event
Management
E02 - Mean Time to

Repair by Device
E02a - Device Details
Event
Management
E02 - Mean Time to

Repair by Group
E02a - Group Detail
Event
Management
E02 - Mean Time to

Repair by Location
E02a - Location Detail
Event
Management
E02 - Mean Time to

Repair by Service
E02a - Service Detail
Event
Management
E05 - Top 10 Transaction E05a - Top 10

Event Generators Transaction Event
Detail
Generators - Detail
E06 - Top 10 Event

Generators - Detail
Event
Management
E06a - Device Event

Detail
Service Level
Management
SL01b - SLA Comp-Cost SL01c - SLA CompBy Contract_Detail

Cost By
Contract_Service
Target Detail
50
Reference Guide
Device Name
Event Severity
Group Name
Event Severity
Location Name
Event Severity
Service Name
Event Severity
User Name
Event Severity
Device Name
Event Severity
Group Name
Event Severity
Location Name
Event Severity
Service Name
Event Severity
Transaction Name
Severity
Event Reception Date
Monitoring Type
Device
Severity
Event Reception Date
Agreement Name
Companies
Contract Names
Contract Status
Start Time
Stop Time
Review Period Frequency
Report conditions

Application
Resulting report
Service Level
Management
SL02a - SLA Comp-Cost SL02b - SLA CompBy Supplier_Summary Cost By

Supplier_Detail
Conditions
Service Level
Management
SL02b - SLA Comp-Cost SL02c - SLA CompBy Supplier_Detail

Cost By
Supplier_Service
Target Detail
Service Level
Management
SL03a - SLA Comp-Cost SL03b - SLA CompBy Customer_Summary Cost By

Customer_Detail
Service Level
Management
SL03b - SLA Comp-Cost SL03c - SLA CompBy Customer_Detail

Cost By
Customer_Service
Target Detail
Service Level
Management
SL01a - SLA Comp-Cost SL01b - SLA Compby Contract_Summary Cost By

Contract_Detail
Service Request
Management
S04 - Service Requests

by Service Category
S04 - Service Requests

by Service Category Detail

Agreement Name
Contract Status
Review Frequency
Supplier Name
Agreement Name
Contract Status
Supplier Name
Start Time
Stop Time
Agreement Name
Companies
Contract Name
Contract Status
Agreement Name
Companies
Contract Name
Contract Status
Start Time
Stop Time
Agreement Name
Companies
Contract Names
Contract Status
Service Request Navigation Category 1
Service Requested By Company

51

Application
Resulting report
Conditions
Service Request
Management
S06 - Aging Report for

Open Service Requests
S06 - Aging Report

for Open Service
Requests - Detail
Service Request
Management
S08 - Open Service

Requests by Status
S08 - Open Service

Requests by Status Detail
Assignee Group
Open Service Request Aging Day
Buckets
Service Requested By Company
Service Request Status
Default views
This section contains the list of default views by application. Use this list when you
create views to ensure that the view does not already exist in the universe. If the
view exists, use the existing view. If the view does not exist, create a new view and
insert it into the universe. Keep in mind that the form name is the same as the view
name.
When you use the BMC Analytics for BSM product with a replicated BMC Remedy
AR System server database, you can replicate only the view required for the ITSM
universe, and only the views for the BMC Remedy IT Service Management
applications you have installed.
The following section lists the views required for each application. The list below
contains the views that are required if you use SAP BusinessObjects Enterprise XI
R3.1 SP2 and BMC Remedy AR System Server version 7.5. If you use a different
SAP BusinessObjects Enterprise XI version or a different BMC Remedy AR System
Server version, see the Self Help Document ID KA345616 in the BMC Knowledge
Base for the list of default views relevant to other universe versions.
BMC Analytics for BSM default views

ANA_FISCAL_CALENDAR
ANA_REPORT_LOCALE
ANA_REPORT_STRING
ANA_REPORT_TRANSLATION
ANA_TIMEZONE_INFO
dbo.arschema
Cloud Lifecycle Management default views

BMC_CORE_BMC_ComputerSystem
BMC_CORE_BMC_Cluster
52
Reference Guide
Default views
BMC_CORE_BMC_ResourcePool
BMC_CORE_BMC_ConcreteCollection
BMC_CORE_BMC_HostedSystemCompo
BMC_CORE_BMC_Dependency
BMC_CORE_BMC_Component
BMC_CORE_BMC_MemberOfCollection
BMC_CORE_BMC_ElementLocation
BMC_BMC_CORE_HardwareSystemCom
BMC_CORE_BMC_Organization
BMC_CORE_BMC_PhysicalLocation
BMC_CORE_BMC_BaseElement
BMC_CLOUD_BMC_ResourceSet
BMC_CLOUD_BMC_FunctionalCompon
BMC_CORE_BMC_ServiceOfferingIn
BMC_CORE_BMC_ContractLine
BMC_CORE_BMC_ServiceOffering
Event Management default views

ANA_EVENT_OP_HISTORY_VIEW
EG_EVENT_VIEW
EXTENDED_EVENT_SLOTS_VIEW
INSTANCEINFO_CFG_VIEW
MO_META_VIEW
CMDB default views

AST_CMDB_ASSOCIATIONS
BMC_CORE_BMC_APPLICATIONSYSTEM
BMC_CORE_BMC_BASEELEMENT
BMC_CORE_BMC_BIOSELEMENT
BMC_CORE_BMC_COMPUTERSYSTEM
BMC_CORE_BMC_DISKDRIVE
BMC_CORE_BMC_HARDWARESYSTEMCOM
BMC_CORE_BMC_KEYBOARD

53
BMC_CORE_BMC_LOGICALSYSTEMCOMP
BMC_CORE_BMC_MAINFRAME
BMC_CORE_BMC_MONITOR
BMC_CORE_BMC_NTDOMAIN
BMC_CORE_BMC_OPERATINGSYSTEM
BMC_CORE_BMC_PATCH
BMC_CORE_BMC_PRINTER
BMC_CORE_BMC_PRODUCT
BMC_CORE_BMC_PROTOCOLENDPOINT
BMC_CORE_BMC_SYSTEMSOFTWARE
BMC_CORE_CONFIG_BMC_DATASET
FIELD_ENUM_VALUES
RE_Activity
RE_Activity_Group_Assoc
RE_Group
RE_JOB
RE_JOB_EVENTS
RE_JOB_RUNS
Change Management default views

AAS_Activity
AST_CI_UNAVAILABILITY_CI_JOIN
CFG_BROADCASTSPGASSOCIATION
CHG_ASSOCIATIONS
CHG_CHANGEAPDETAILSIGNATURE
CHG_Infra__Change_Effort_Log
CHG_INFRASTRUCTURE_CHANGE
CHG_WORKLOG
CTM_PEOPLE_ORGANIZATION
CTM_PEOPLE_PERMISSION_GROUPS
FIELD_ENUM_VALUES
H1199
54
Reference Guide
Default views
NOTE
The view name H1199 will vary according to your installation. To verify the name
of this view, use the query documented in the section Updating the
CHG_STATUS_HISTORY table in the BMC Analytics for Business Service
Management Installation and Administration Guide.
HPD_HELP_DESK
PBM_KNOWN_ERROR
PBM_PROBLEM_INVESTIGATION
PBM_SOLUTION_DATABASE
PDL_SOFTWARELIBRARYITEM
RMS_Associations
RMS_FINCostsOJoinManifestAssoc
RMS_Release
RMS_ReleaseAPDetailSignature
RMS_ReleaseManifestAssociation
RMS_Worklog
SLM_Measurement
TMS_RELATIONSHIPS
TMS_TASK
TMS_TASKGROUP
Service Request Management default views

BMC_CORE_BMC_BUSINESSSERVICE
CTM_PEOPLE
FIELD_ENUM_VALUES
HPD_HELP_DESK
SRD_SERVICEREQUESTDEFINITION
SRM_QUESTIONRESPONSE
SRM_REQUEST
SRM_REQUESTAPDETAILSIGNATURE
SRM_SURVEY
SRM_WORKINFO
55
WOI_WORKORDER
WOI_WORKINFO
TMS_WORKINFO
SLM_EventSchedule
SLM_Measurement
TMS_TASK
Asset Management default views

AST_ASSETMAINTENANCE
AST_ASSETSUPPORT
AST_ASSETLEASE
AST_ASSETPEOPLE
AST_ASSETSOFTWARE
AST_ASSETWARRANTY
AST_AUD_ASSETASSOCIATIONS
AST_CI_UNAVAILABILITY_CI_JOIN
AST_CMDB_ASSOCIATIONS
AST_Compliance_BasicQuestions
AST_CONFIGITEMSASSOCIATIONJOIN
AST_CONFIGURATION
AST_CONTRACTPDRELATIONSHIPJOIN
AST_IMPACTED_AREAS
AST_LicenseCertificates
AST_PURCHASELINEITEM
AST_PURCHASEORDER
AST_PURCHASEREQUISITION
AST_PURCHASEREQUISITIONLINEITE
AST_PURCHASERETURN
AST_WORKLOG
BMC_CORE_BMC_APPLICATIONSYSTEM
BMC_CORE_BMC_BASEELEMNT
BMC_CORE_BMC_BIOSELEMENT
BMC_CORE_BMC_COMPUTERSYSTEM
56
Reference Guide
Default views
BMC_CORE_BMC_DISKDRIVE
BMC_CORE_BMC_HARDWARESYSTEMCOM
BMC_CORE_BMC_KEYBOARD
BMC_CORE_BMC_LOGICALSYSTEMCOMP
BMC_CORE_BMC_MAINFRAME
BMC_CORE_BMC_MONITOR
BMC_CORE_BMC_NTDOMAIN
BMC_CORE_BMC_OPERATINGSYSTEM
BMC_CORE_BMC_PATCH
BMC_CORE_BMC_PRINTER
BMC_CORE_BMC_PRODUCT
BMC_CORE_BMC_PROTOCOLENDPOINT
BMC_CORE_BMC_SYSTEMSOFTWARE
CFG_BROADCAST
CHG_CHANGEINTERFACE
CTM_PEOPLE
CTR_Contract_Relationship
FIELD_ENUM_VALUES
FIN_COSTASSOCIATIONJOIN
FIN_COSTS
FIN_PAYMENTS
HDP_HELP_DESK
OBJSTR_CLASS
PBM_KNOWN_ERROR
PDL_PRODUCTDICTIONARY
RMS_Release
SHR_SCHEMANAMES
Service Level Management default views

AST_CI_UNAVAILABILITY

57
FIELD_ENUM_VALUES
HPD_HELP_DESK
SLM_ASSOCIATION
SLM_ASSOCIATION_REVIEWPERIOD
SLM_CONTRACT
SLM_EventSchedule
SLM_GOALSCHEDULE
SLM_Measurement
SLM_MileStone
SLM_PENALTYREWARDS
SLM_RuleActionComponent
SLM_SERVICETARGET
SLM_SLAASSOCIATION
SLM_SLACOMPLIANCE
SLM_SLADEFINITION
SLM_UDA_ASSOCIATION_ATTACHMENT
SRM_REQUEST
Service Desk default views

AST_CI_UNAVAILABILITY
AST_CI_Unavailability_CI_Join
CFG_BROADCAST
CFG_BROADCASTSPGASSOCIATION
CTM_PEOPLE
CTM_SUPPORT_GROUP
FIELD_ENUM_VALUES
58
Reference Guide
Default views
FIN_Association
FIN_COSTS
HPD_ASSOCIATIONS
HPD_HELP_DESK
HPD_HELP_DESK_ASSIGNMENT_LOG
HPD_HELPDESK_AUDITLOGSYSTEM
HPD_IMPACTED_AREAS
HPD_INCIDENTINTERFACE
HPD_WORKLOG
PBM_IMPACTED_AREAS
PBM_INVESTIGATION_ASSOCIATIONS
PBM_INVESTIGATION_EFFORT_LOG
PBM_INVESTIGATION_WORKLOG
PBM_KNOWN_ERROR
PBM_KNOWN_ERROR_ASSOCIATIONS
PBM_PROBLEM_AUDITLOGSYSTEM
PBM_SOLUTION_DB_ASSOCIATIONS
RMS_RELEASE
SLM_EventSchedule
SLM_Measurement
SRM_SURVEY
TMS_RELATIONSHIPS
TMS_TASK
TMS_TASKEFFORT
TMS_WORKINFO
Configuration Drift Management default views

BMC_CORE_BMC_BUSINESSSERVICE

59
DSM_BASELINEMGR_BASELINE
DSM_DRIFT_DRIFTCIATTRIBUTES
DSM_DRIFT_DRIFTCIBUSINESSSERVI
DSM_DRIFT_DRIFTDETAILS
DSM_DRIFT_DRIFTS
DSM_DRIFT_DRIFTTOCHANGECORRELA
DSM_DRIFT_DRIFTTOINCIDENTCORRE
DSM_JOBMGR_JOB
DSM_JOBMGR_JOB_RUNS
DSM_LIBRARY_TARGETS
FIELD_ENUM_VALUES
HPD_HELP_DESK
60
Reference Guide
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Index
A
populating 22
ANA Fiscal_Calendar 28
ANA Fiscal_Calendar form 28
ANA_EVENT_OP_HISTORY_VIEW 21
ANA_FISCAL_CALENDAR 28
structure 29
timezone support 35
ANA_FISCAL_CALENDAR view 28
ANA_TIMEZONE_INFO table 33
F
fiscal calendar 28
ImpactPortal universe 28
ITSM universe 28
PortalCDE universe 28
ProactiveNet universe 28
FN_ADJUSTED_DATE function 30
FN_GET_EPOCH_DATE function 31
BMC Analytics for BSM

views 52
BMC Software, contacting 2
business service model
in the ITSM universe 15
reports 17
using 13
business service models 13
history table 21
C
C02 - Business Services Supported by a CI 17
C03 - Business Service Profile 17
customer support 3
customizing
ITSM universe 42
reports 43
ImpactPortal universe
characteristics 25
fiscal calendar 28
installed database objects 25
ITSM universe
characteristics 4
fiscal calendar 28
Microsoft SQL Server installed database
objects 11
Oracle installed database objects 8
multitenancy fields 6
default views 52
DENORMALIZE_BSM_RELATIONSHIPS table
populating 15
structure 14
E
event history table
Portal CDE universe

PortalCDE universe
characteristics 26
fiscal calendar 28
Index
61
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
ProactiveNet universe
characteristics 18
fiscal calendar 28
product support 3
R
report views 52
S
support, customer 3
T
technical support 3
timezone support 35
U
universe characteristics
ImpactPortal 25
ITSM 4
PortalCDE 26
ProactiveNet 18
V
views 52
Asset Management 56
BMC Analytics for BSM 52
Change Management 54
CMDB 53
Configuration Drift Management 59
Event Management 53
Service Desk 58
Service Level Management 57
Service Request Management 55
62
Reference Guide
Third-party product terms

The following terms apply to third-party products that are included with or in a BMC Software product as described in the BMC
Software, Inc., License Agreement that is applicable to the BMC Software product.
*171237*
*171237*
*171237*
*171237*
*171237*

BMC Analytics For BSM 7.6.04 Reference Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BMC Analytics For BSM 7.6.04 Reference Guide

Uploaded by

Copyright:

Available Formats

BMC Analytics for Business Service Management 7.6.

Contacting BMC Software

United States and Canada

BMC SOFTWARE INC

713 918 8800 or

(01) 713 918 8000

713 918 8000

Outside United States and Canada

(01) 713 918 8800

Copyright 2003 - 2011 BMC Software, Inc.

Restricted rights legend

Support by telephone or email

Before contacting BMC Software

Operating system and environment information

Sequence of events leading to the problem

Commands and options that you used

License key and password information

E-mail customer_support@bmc.com. (In the Subject line, enter SupID:<yourSupportContractID>,

Submit a new issue at http://www.bmc.com/support_home.

Universe characteristics and related information

About the ITSM Universe and installed objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Universe and report customization templates

Universe customization templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Report conditions and default views

BMC Analytics for BSM default views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

This appendix contains the following topics:

About the ITSM Universe and installed objects (page 4)

Chapter 1 Universe characteristics and related information

BMC Analytics for BSM 7.6.04

About the ITSM Universe and installed objects

ITSM universe characteristics

Name of the universe

BMC Analytics for BSM 7.6.04 universe for

Description of the universe

Name of the connection used to

Classes and Objects

See Self Help Document ID KA345616 in the

Description of the formulas for the

About the ITSM Universe and installed objects

Table 1-1: Characteristics of the ITSM universe

SAP BusinessObjects XI R 3.1 SP3 and BMC

Chapter 1 Universe characteristics and related information

BMC Analytics for BSM 7.6.04

Table 1-1: Characteristics of the ITSM universe

Allow Use of Subqueries: true

Fields for reporting on multitenancy

Database column name

About the ITSM Universe and installed objects

Database column name

Chapter 1 Universe characteristics and related information

BMC Analytics for BSM 7.6.04

Service Level 7.1.x, 7.5.x,

Database column name

Stored procedures, functions, and tables

Oracle stored procedures, functions, packages, tables,

Invoked as required by IT Service Management

PKG_BSM_RELATIO Populates the

About the ITSM Universe and installed objects

Populates the ANA_FISCAL_CALENDAR

The procedure queries ANA_TZ_DST_VIEW

The procedure queries ANA_TZ_DST_VIEW

A database procedure reads the business

Lists the timezones used in the reports and the