Beruflich Dokumente
Kultur Dokumente
D84382
Edition 3.0
D63786GC30
November 2013
Student Guide - Volume II
Manage Applications
Oracle Hyperion Financial
Management 11.1.2: Create &
Technical Contributors other intellectual property laws. You may copy and print this document solely for your
and Reviewers own use in an Oracle training course. The document may not be modified or altered
in any way. Except where your use constitutes "fair use" under copyright law, you
Ron Reiley may not use, share, download, upload, copy, print, display, perform, reproduce,
Yuen Man Boronski publish, license, post, transmit, or distribute this document in whole or in part without
the express authorization of Oracle.
The information contained in this document is subject to change without notice. If you
Graphic Editor find any problems in the document, please report them in writing to: Oracle University,
Seema Bopaiah 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not
warranted to be error-free.
Malavika Jinka
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names
may be trademarks of their respective owners.
Contents
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
1 Introduction
Course Objectives 1-2
Course Agenda: Day 1 1-3
Course Agenda: Day 2 1-4
Course Agenda: Day 3 1-5
iii
Dimensions 2-7
Financial Management Data Dimensions 2-8
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
3 Managing Dimensions
Objectives 3-2
Dimension Library 3-3
Applications 3-4
Shared Library 3-5
Creating Dimensions 3-6
Creating Associations Between Dimensions 3-8
Configuring Custom Dimensions 3-11
Setting Up Languages 3-13
Setting Up Enhanced Cell Text 3-15
Organizing Shared Library by Using Folders 3-16
Filtering Shared Library 3-17
Managing Dimensions in Classic Applications 3-18
Summary 3-20
Quiz 3-21
Practice 3: Overview 3-25
iv
4 Managing Dimension Members
Objectives 4-2
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
5 Loading Metadata
Objectives 5-2
Metadata Load Files: Overview 5-3
Formatting Metadata Load Files for Performance Management Architect 5-4
Setting Up Dimensions 5-5
Dimensions Section 5-6
Members Sections 5-7
Managing Languages 5-9
Hierarchy Sections 5-10
DimensionAssociations Section 5-12
Creating ADS Files with the Performance Management File Generator 5-13
Loading Metadata Process 5-14
Merge and Reorder Options 5-15
Creating Import Profiles 5-17
Defining Load Options 5-18
Mapping Dimensions 5-19
Mapping Properties 5-20
Running Import Profiles 5-21
Viewing Job Status 5-22
v
Loading Metadata from Interface Tables 5-23
Loading Metadata from Oracle Hyperion Data Relationship Management 5-24
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Summary 5-25
Quiz 5-26
Practice 5: Overview 5-30
6 Creating Applications
Objectives 6-2
Applications and Performance Management Architect 6-3
Local and Shared Dimensions 6-4
Creating Applications by Using the Application Wizard 6-6
vi
Quiz 7-18
Practice 7: Overview 7-22
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
vii
10 Deploying Applications
Objectives 10-2
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
viii
12 Entering Data by Using Data Grids
Objectives 12-2
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
ix
Extracting Member Lists 13-20
Summary 13-21
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Quiz 13-22
Practice 13: Overview 13-26
x
16 Assigning Access to Data and Documents
Objectives 16-2
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
xi
18 Creating and Managing Task Lists
Objectives 18-2
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
xii
Creating Journals from Recurring Templates 20-16
Creating Auto-Reversing Journals 20-17
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
21 Translating Data
Objectives 21-2
Data Translation: Overview 21-3
Default Translation Process 21-4
Data Grids and Data Forms for Exchange Rates 21-5
Translating Financial Data in Data Grids 21-7
Checking Translation Status 21-8
Summary 21-10
Quiz 21-11
Practice 21: Overview 21-15
22 Running Consolidations
Objectives 22-2
Financial Management Business Process 22-3
Consolidation: Overview 22-4
Consolidation Process 22-5
Consolidation and the Value Dimension 22-6
Checking Calculation Status 22-7
Consolidation of Children by Percentages 22-9
Ownership Management 22-10
Assigning Ownership by Period 22-11
Calculating Ownership Using Shares 22-13
Managing Equity Pickup by Using the Equity Pickup Task 22-15
Consolidating Data 22-16
Setting Data Process Control Display Options 22-19
xiii
Viewing Status for All Periods 22-20
Summary 22-21
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Quiz 22-22
Practice 22: Overview 22-26
xiv
Adding Filters to Source Dimensions 24-9
Inserting Mapping Tables 24-11
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
xv
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Sales Interco
Salaries
Interest Expense
Member lists can reduce the time that you spend browsing member hierarchies in data grids
and data forms. For the example in the slide, if Total Revenue, Total Costs, and
Administration Expenses are used frequently in the point of view for the Account dimension,
your administrator can create a member list named Profit. You can then select members from
the list, instead of browsing through the hierarchy of the Account dimension.
You can also use member lists in rules and in Financial Reporting and Web Analysis. For
example, you can write a rule that calculates all members of a member list, or run a report for
all members of a member list.
Two types of member lists are used in Financial Management:
• System-defined member lists
• User-defined member lists
Income
Before Taxes
Children of Base
Gross Margin parent member list
member list
Total Revenue
Sales
Sales Sales
Sales Interco
Admin Expense
After an application is created and metadata is loaded, the system generates system-defined
member lists.
System-defined member lists group members according to common properties, such as all
children of a specified parent or all base members of a specified dimension.
For the example in the slide, Sales and SalesInterco are shown as children of Total Revenue,
and Sales, SalesInterco, Salaries, Interest Charges, and Administration Expense are shown
as base members in a hierarchy.
Interest Expense
Admin Expense
• Create member lists in a text file that you load into your
application.
• Include definitions for all user-defined member lists in a
single file.
Sub EnumMemberLists()
Dim aEntityLists(2)
You can use a text editor, such as Microsoft Notepad, to create member list files.
Member list creation process:
1. Identify the number of lists for the dimension and the name and number ID for each list.
2. Following Microsoft Visual Basic script syntax, add members to each static and dynamic
list.
The example in the slide shows the following syntax for creating two Entity member lists and
one Account member list:
Sub EnumMemberLists ()
Dim aEntityLists(2)
Dim aAccountLists(1)
If HS.Dimension = “Entity” Then
Sub EnumMemberLists()
Dim aEntityLists(2)
Dim aAccountLists(1)
If HS.Dimension = "Entity" Then
Each member list file must include an EnumMemberLists subroutine to specify which
dimensions have member lists, the number of lists for each dimension, and the name of each
member list.
The following table describes the syntax shown in the slide:
Syntax Description
aElementLists(n) = “ListName” Specifies the name and numeric ID for each list.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Sub EnumMembersInList()
If HS.Dimension = "Account" Then
If Hs.MemberListID=1 Then
You use the EnumMembersInList subroutine to add members to a list. For a static member
list, you list all members of the list in the script.
For all dimensions except Entity, you use the HS.AddMemberToList statement, in which you
must specify a member. For the Entity dimension, you use the Hs.AddEntityToList statement,
in which you must specify a member and its parent.
Syntax Description
Sample Script
The following member list script creates two Entity member lists and one Account member
list:
Sub EnumMemberLists()
Dim aEntityLists(2)
Dim aAccountLists(1)
If HS.Dimension = "Entity" Then
aEntityLists(1) = "UnitedStates"
aEntityLists(2) = "Europe"
HS.SetMemberLists aEntityLists
ElseIf HS.Dimension = "Account" Then
aAccountLists(1) = "ProfitAndLoss"
HS.SetMemberLists aAccountLists
End If
End Sub
Sub EnumMembersInList()
If HS.Dimension = "Entity" Then
If HS.MemberListID=1 Then
HS.AddEntityToList "Europe","ITA_Top"
HS.AddEntityToList "Europe","FRA_Top"
HS.AddEntityToList "Europe","UK_Top"
End If
ElseIf HS.Dimension = "Account" Then
If HS.MemberListID=1 Then
HS.AddMemberToList "Sales"
HS.AddMemberToList "SalesInterco"
For Dynamic member lists, instead of listing all members of the member list, you enter rules to
select members that meet specified criteria. Criteria are member properties such as currency
or account type. The list is generated dynamically each time it is accessed by a user.
For the example in the slide, the list of entities is received into an array. For each entity in the
array, the value of the DefaultCurrency property is compared with the preferred value of
USD. If the value is equal to USD, the entity is added to the list. Then the next entity in the
array is processed.
Ali=HS.Account.List("","")
For i=Lbound(ALi) to Ubound(ALi)
If (StrComp(HS.Account.AccountType(ALi(i)),"asset",vbTextCompare)=0) Then
The example in the slide shows the following syntax for creating a dynamic member list in the
Account dimension for all accounts of the Asset account type:
Ali=HS.Account. List(““,””)
For i=Lbound(ALi) to Ubound(ALi)
If (StrComp(HS.Account.AccountType(ALi(i)),”asset”,vbTextCompare)=0)
Then HS.AddMembertoList ALi(i)
End If
Next
You use dynamic POV member lists in the rows or columns of data grids and data forms.
They allow you to change the rows or columns displayed for a dimension based on the
currently selected members of the Entity, Period, Year, or Scenario dimension in the POV.
You can base the member list on more than one POV dimension, for example, on the current
combination of Scenario and Period.
In the slide example, the LinesOfBusiness dimension contains hardware and software
products. Entities in Connecticut do business only in software; entities in all other states do
business in both hardware and software. A dynamic POV member list is used in the row
section of the data form. When the user selects an entity in Connecticut in the POV, the
member list displays rows for software products only; when the user selects an entity in any
other state, the form displays rows for both hardware and software products .
• The member list name must have the suffix (@POV), for
example: LOB by State(@POV).
• Use the HS.MemberList<Dimension> function to retrieve
the current POV member; for example,
HS.MemberListYear.
• The valid POV dimensions you can reference in dynamic
After creating a member list script file, you load it into your application. You load member lists
using the Load Application Elements task. Before loading the file, you can scan to verify that it
is formatted correctly. When you modify the file, you must reload it into the application.
Tip: If you click the Scan button, the syntax is checked; the members that are retrieved are
not checked.
To load member lists:
1. Select Consolidation, then Load, and then Application Elements.
The Load Application Elements task is displayed.
2. In the Member Lists section, click Browse to select the member list that you want to
load.
3. Optional: On the Load Members Lists, click Scan to check the syntax of the member
list.
4. Click Load to load the member list.
5. Click Log to verify that the member list is loaded successfully.
You extract member lists in the Extract Application Elements task. Extracted member lists are
saved as ASCII files. By default, member lists have the file extension LST.
To extract member lists:
1. Select Consolidation, then Extract, and then Application Elements.
The Extract Application Elements task is displayed.
2. In the Member Lists section, click Extract.
A Download button is displayed in the Member Lists section.
3. Click Download.
The File Download dialog box is displayed.
4. Click Save.
The Save As dialog box is displayed.
5. Browse to a location where you want to save the file, and click Save.
Answer: d
Answer: a
Answer: b
Answer: b
Manager
Calculation Manager
You use Calculation Manager to design, validate, and deploy calculations that enable you to
solve business problems. The user interface provides a graphical design environment that
enables you to build complex calculations easily.
Calculation Manager enables you to break rules into individual rule components that can be
shared between applications. For example, you can create a formula to calculate “days sales
outstanding,” and then reuse the formula in all applications that require this calculation.
Rules created in Calculation Manager are stored in the Calculation Manager database. The
rules are validated against the dimension metadata in Performance Management Architect
and the deployed Financial Management application. To activate the rules in your Financial
Management applications, you deploy the rules from Calculation Manager to your Financial
Management application server. You can deploy Calculation Manager rules to both Financial
Management applications built in Performance Management architect and to Classic
Administration applications.
Calculation Manager
FINAPP_CalcMgr.rle
Rules for Financial Management application use Microsoft Visual Basic Script (VB Script)
syntax, enhanced with special functions for Financial Management. Calculation Manager
provides a graphical interface that enables you to create Financial Management rules without
requiring knowledge of VB Script syntax. You create graphical rules in Calculation Man ager,
and when you deploy the rules to your Financial Management applications, Calculation
Manager automatically converts the graphical rules to a VB Script file, and then loads the file
into the application. In the slide example, rules are deployed from Calculation Manager to a
Financial Management application named FinApp.
Note: You are not required to use Calculation Manager to create Financial Management
rules. If you are knowledgeable of VB Script, you can create VB Script files in a text editor or
other scripting tool and load the script file directly into your Financial Management application
using the Load Application Elements task.
The rules for each Financial Management application are organized into eleven rule types.
For each rule type, you create a rule set. You can create more than one rule set for each type,
but you can deploy only one rule set for each type to the application.
You execute the rules for a rule type by performing actions within Financial Management. For
the example in the slide, when you select Calculate from the shortcut menu of a data grid, the
rules for the Calculate rule type are executed.
Calculate Set account values based on formulas. You can run Calculate rules from data grids,
data forms, and the Process Control task. Calculate rules are executed automatically
when you consolidate an entity.
Dynamic Create formulas for accounts with the Dynamic account type. Dynamic accounts
accurately calculate YTD and Periodic values that are not calculated correctly by the
aggregation of base member values.
Dynamic rules are valid only for dynamic accounts, and are executed automatically
when you open data grids and data forms that contain accounts with the account type
Dynamic.
Consolidate Perform customized consolidation and elimination calculations. You run Consolidate
rules from data grids and the Process Control task.
Equity Pick Up Perform customized ownership calculations for entities. You run Equity Pick Up rules
from data grids or the Manage Equity Pick Up task.
Allocate Set allocate data from a source to multiple destinations. You run Allocate rules from
data grids or data forms.
Input Configure parent members to allow data entry. Input rules are executed when you
open an application.
No Input Configure members to prevent data entry. No Input rules are executed when you open
an application.
Transaction Configure accounts to allow posting of data from the Intercompany Transaction
module. Transaction rules are executed when you open an application.
Generic Reuse rules in rule sets for more than one rule type. For example, you create a rule for
rounding that you use in your Calculate and Translate rule sets. You must add Generic
rules to a rule set for one or more of the other rule types in order to deploy them in a
Financial Management application. You can nest generic rule sets within rules sets for
any rule type.
Global Use Generic rules to set global values that you can use in all calculation types. These
rules run before all other rule types. For example, you could create a rule that defines
variables for names of your exchange rate accounts and then reuse the variables as
needed in rules for other calculation types.
Loop
component
Condition
Formula
component
component
A rule is a Calculation Manager object that consists of calculations grouped into components.
You design a rule by dragging components from the Rule Palette to the flow chart. Each
component performs a separate task.
Condition Components
A condition component comprises conditional statements (If...Then statements) that are either
true or false. You insert other rule components within the scope of the condition component. If
the condition is true, Calculation Manager executes the components within the scope of the
condition component. If the condition is false, the components within the condition are
skipped.
You use condition components to limit the members for which a rule is executed. For
example, if a calculation is valid only for the Forecast scenario, you can create a condition to
test whether the current scenario in the point of view is Forecast.
For the example in the slide, the loop and formula components are within the scope of the
condition component. They are executed only if the condition specified for the condition
component evaluates to true.
Condition Functions
Formula components are the primary components of a rule. You use them to assign values to
accounts or to clear account values.
The formula component comprises calculation statements that assign values to accounts
based on your defined formula. To create the calculation statements, you add rows to grids in
the formula component.
Each calculation statement in the grid consists of a destination expression and a source
expression. The destination expression is displayed on the left of the equal sign, and the
source expression is displayed on the right. You use dimension keywords to identify the
dimensions for the members included in the expressions. Dimension keywords for standard
dimensions consist of the first letter of the dimension followed by a pound sign (#). For
example, A#Sales identifies the Sales member of the account dimension. Dimension
keywords for custom dimensions consist of the dimension alias or short name followed by a
pound sign. For example, Flows#ClosingBalance identifies the ClosingBalance member of
the Flows dimension.
Oracle Hyperion Financial Management 11.1.2: Create & Manage Applications 14 - <#>
Data is retrieved from the dimension members specified in the source expression and written
to the members specified in the destination expression.
• You can specify members from the account, custom, and ICP dimensions in the
destination expressions.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
• You can specify members from any dimension in the source expression.
• You can use standard math operators to perform calculations on the source data before
it is written to the destination. For example, you increase the source data values by 10%
before writing the values to the destination.
• You can also add condition statements to grids. The calculation statements in the grid
are executed only if the condition evaluates to true.
The example in the slide shows a formula component with two grids:
• In the first row of the first grid, the destination is the Surplus member of the Account
dimension. The source expression retrieves values for the TotalLiabEquity and
You create rules for the rule types required by your application. When you add components to
a rule, you can create components for the rule or you can reuse components. For example,
you create a formula component for Rule1 named Balances that retrieves opening balances
for accounts. When you create Rule 2, you can reuse the Balances component.
Note: You cannot reuse loop or condition components. However, you can copy and paste
loop or condition components between rules.
Oracle Hyperion Financial Management 11.1.2: Create & Manage Applications 14 - <#>
To create rules:
1. Log on to Workspace.
2. In Performance Management Architect, select Navigate, then Administer, and then
Calculation Manager.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
The Rule Designer allows you to edit rules in script view. Changes you make to calculation
manager objects in script view are preserved when you return to the graphical view.
Note: Changes you make to the shared components in the rule in script view are not saved
when you return to the graphical view.
To edit rules in script view:
1. In Calculation Manager, open a rule.
- The rule designer is displayed.
2. If you have made change to the rule, save your changes.
3. Select Edit, and then Script.
- The rule is displayed in the script editor.
4. Edit the script for the rule components as needed.
5. Select Edit, and then Graphical.
6. Click Save to save you changes.
Oracle Hyperion Financial Management 11.1.2: Create & Manage Applications 14 - <#>
Creating Rule Sets
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Before you can deploy the rules for a rule type, you must create a rule set and add the rules to
it. The order that you place the rules in the rule set determines their order of execution.
You can include one rule set inside another rule set. For the example in the slide, you create
a rule set named SalesAndPrice for all sales-related rules. You include the SalesAndPrice
rule set within another rule set named CalcRules, which contains all rules for the Calculate
rules type.
To create rule sets:
1. In Calculation Manager, expand Consolidation.
2. Expand an application.
3. Expand the rule type for the rule set that you want to create.
Formula
components
Script
components
You validate rules to verify that the syntax does not contain errors and that all dimension
members referenced in the rules exist in the application. You can validate an entire rule set,
an individual rule, or an individual formula or script component. You cannot deploy rules to
Financial Management applications until all validation errors are corrected.
To validate rules:
1. In Calculation Manager, expand Consolidation.
2. Expand an application.
3. Right-click a rule set, rule, formula component, or script component, and select
Validate.
- The Information dialog box displays any validation errors.
4. Click OK.
Oracle Hyperion Financial Management 11.1.2: Create & Manage Applications 14 - <#>
Deploying Rules
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
You cannot execute rules within Financial Management applications until you deploy the rules
from Calculation Manager to the application.
Deployment Guidelines
• You can deploy only one rule set from each rule type. However, the rule set can have
other rule sets nested within it.
• You do not need to deploy rules sets for all rule types. For example, you can deploy only
a rule set for the Calculate rule type.
• When you deploy rules, all existing rule sets in the application are erased and replaced
with the rules sets that you deploy.
To deploy rules to an application:
1. In Calculation Manager, select View, and then Deployment View.
2. Expand Consolidation.
Import
You can import Calculation Manager objects from or export them to XML files. You can import
and export individual Calculation Manager objects or an entire application. If you import or
export an entire application, all rules, rules sets, rule components, and variables for the
application are in a single XML file.
When you export Calculation Manager objects from an application to an XML file, the
application name is included in the file. When you import the file, the Calculation Manager
objects are imported into the application named in the file. You can override the target
application at the time of import.
To import Calculation Manager objects:
1. In Calculation Manager, select File, and then Import.
- The Import dialog box is displayed.
2. Click Browse and select an XML file.
3. Optional: Click Update Details to modify the target application.
Note: If you do not modify the target application, the Calculation Manager objects are
imported into the same application from which they were exported.
Oracle Hyperion Financial Management 11.1.2: Create & Manage Applications 14 - <#>
4. Select one of the following import options:
- Select Override Existing Objects to replace Calculation Manager objects that
have the same name as objects in the XML file.
- Select Skip Existing Objects to skip objects in the XML file that exist in
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Calculation Manager.
- Select Error out for duplicates to halt the import process if duplicate object
names are in Calculation Manager and the XML file.
5. Click Import.
- A dialog box displays an import results log.
6. Optional: Click Save to save the import results log to a file.
7. Click OK.
To export individual Calculation Manager objects:
Sub Translate
'Calculate change due to exchange rates
HS.Trans "Flows#Rate","Flows#Opening","A#EopRate"
HS.Trans "Flows#Move","Flows#P_L","A#EopRate",A#A
End Sub
Prior to version 11.1.1 of Financial Management, you were required to create rules by using
VB Script. Rules for all calculation types were included in a single script-based rules file (RLE)
that you loaded into Financial Management. You can import RLE files into Calculation
Manager either as script components or as Calculation Manager objects.
Importing RLE Files as Script Components
When you import RLE files, for each SUB procedure of a valid calculation type in the RLE file,
a rule set containing one business rule and one script component is created. The example in
the slide shows the SUB TRANSLATE procedure of an RLE file and the following Translate
type objects that are created in Calculation Manager:
• A script component named Translate_Component that contains all script from the
procedure
• A rule named Translate_Rule that includes Translate_Component as a component
Oracle Hyperion Financial Management 11.1.2: Create & Manage Applications 14 - <#>
• A rule set named Translate_Ruleset that includes Translate_Rule as a member
Importing Script-Based Files as Calculation Manager Objects
You can migrate RLE files to Calculation Manager objects. To determine how to split groups
of VB script calculation statements into Calculation Manager components, the comment lines
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
in the VB script file are used. Three component-splitting options are provided:
• Separate component: A separate formula component is created for the calculation
statements following each comment line.
• Multiblock component: A single formula component is created, with separate grids for
the calculation statements following each comment line.
• Single-block component: All calculation statements are added to a single formula
component in a single grid, regardless of comment lines.
To import script-based rules files:
Answer: a
Oracle Hyperion Financial Management 11.1.2: Create & Manage Applications 14 - <#>
Quiz
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Answer: a
All except one are Calculation Manager views. Identify the odd
one.
a. System
b. Custom
c. Application
d. List
Answer: c
All except one are rule types. Identify the odd one.
a. Dynamic
b. Input
c. Transactions
d. Output
Answer: d
and Groups
Provisioning Users
Financial Management provides security at four levels: task, artifact, data security, and user
authentication.
Security Guidelines
• Users must provide a valid ID and password to log on to the system.
• Users can launch only tasks to which they have access. For example, users can be
given the ability to create journals but not to post journals.
• Users can open only documents and objects to which they have access. Securable
documents and objects include data grids, data forms, journals, workspaces, and
system reports.
• Users can view and modify data, and filter metadata within selection lists only for
dimension members to which they have access.
• You can specify the tasks that users and groups are
authorized to perform.
• Other tasks are removed from the menus to present a
customized user interface.
• Task security is assigned through security roles.
Task security determines the tasks that a user can access within an application. You assign
task security by assigning one or more security roles to a user. Each role is associated with a
set of tasks. For the example in the slide, a journal administrator can access more tasks than
a journal user and remove other tasks from menus to present a customized user interface.
The online Help lists the available security roles.
Artifacts are objects such as data grids, task lists, and journals. Artifact security is assigned
through security classes. Security classes are a grouping mechanism for assigning security
access to sets of related members, documents, or other objects.
For the example in the slide, for salary accounts, you assign the SalaryRelated security class
to data grids and forms. You then assign the SalaryRelated security class to Payroll
department users and no access to other users. Then the salary account data grids and forms
are available only to Payroll department users.
You can set up data security to protect data and prevent unauthorized users from changing
data. For example, you can restrict access to certain data elements in an application.
For the example in the slide, different security classes are assigned different access levels.
East Region is assigned the access level “All,” West Region is assigned the access level
“Metadata,” United Kingdom is assigned the access level “Read,” and Singapore is assigned
the access level “None.”
You use security roles to limit the tasks that users can perform in an application.
• For each security role, you set access to Yes or No.
• You can assign roles by user and by group.
• If you provision a group, you do not need to provision the users within the group.
The following are five special roles:
• Application Administrator: Grants access to all tasks and data in a Financial
Management application
• Provisioning Manager: Enables you to assign security roles and security class access
to users in a Financial Management application
• Financial Management Manager: Grants access to the Performance Management
Architect and Calculation Manager tasks required for Financial Management
administrators. It includes the Financial Management Administrator, Financial
Management Application Creator, and Financial Management Calculation Manager
Administrator roles.
• Default: Within an application, enables users and groups to perform default tasks in
each module, for example, define application profiles, open data grids, create reports,
manage metadata, load data, and extract member lists
Extract
Application level
Manage Reports
Financial Management security roles address the six areas listed in the slide. Refer to the
Oracle Enterprise Performance Management System User Security Administration Guide for
explanations of the Financial Management security roles.
Shared Services User Management Console provides a centralized location from which you
manage security for your Financial Management applications.
User Management Console provides a list of users and groups from your authentication
provider. You provision users and groups by assigning them security roles in an application. If
security roles are assigned to a user both individually and through one or more groups, the
user receives both the individual and group role assignments.
A user who, within an application, is assigned the Provisioning Manager role can assign
security roles.
To assign security roles:
1. Log on to Workspace.
2. Select Navigate, then Administer, and then User Management to display User
Management Console.
7. From the Available Roles list, select an application and a role, and then click the
right-arrow button.
The role is added to the Selected Roles list.
8. Repeat step 7 to add other roles.
9. Click Save.
Answer: b
Answer: a
Answer: a
East Sales US
(Member Attribute) Europe
Australia
SecurityClass = US
Before setting up security for users and groups, you should ensure that your security-related
application settings are configured correctly.
The following application settings, which you set in Performance Management Architect, enable
dimension security. You set each setting to Yes or No:
• Use Security For Accounts
• Use Security For Entities
• Use Security For Scenarios
• UseSecurityForICP
• Use Security For <Custom Dimension Name>
For the example in the slide, the security-related application settings for the Entity, Account, and
Scenario dimensions are set to Yes.
check node data based on the entity’s access. Select Parent to check node data based on
the parent’s access.
All/All All/None
Read/All Read/None
Sales All
Costs Read
Florida All
France None
You assign users access rights to members indirectly through a security class. For example,
assume that the security class for the Sales and Net Profit members is Revenue Accounts. If you
assign a user Read access to the Revenue Accounts security class, the user receives Read
access to the Sales and Net Profit members.
Data cells represent intersections of dimension members. Users may be assigned multiple levels
of access for the multiple members of a data cell. In this case, to determine the user’s access to
the cell, the most restrictive access right is applied.
For the example in the slide, at the intersection of Costs and Florida, the user has Read access to
the Costs member and All access to the Florida member. Therefore, the user has Read access to
the cell. Similarly, at the intersection of Costs and France, the user has Read access to the Costs
member and None access to the France member. Therefore, the user has no access to the cell.
If metadata filtering is enabled for an application, user access rights also control member filtering.
Users see only the members of the Scenario, Entity, ICP, Account, and custom dimensions to
which they have access. Metadata filtering applies to member selection lists and to the rows and
columns of data grids and data forms.
Every Financial Management document is assigned a security class. The users’ access to a
document is determined by their access level to the security class. Document access levels are
described in the following table:
Document Description
Access
Read • Users can open the document, and can also save a private grid.
Metadata • For data forms and data grids, based on their access rights to the row and column
Promote members, users can modify data.
• For journals, data is read-only.
• Users cannot modify the document. For example, they cannot add rows or columns
to a data grid.
All • Users can open, modify, and save the document. Users must have the Manage
Data Entry Forms role to save data forms.
Dimension
association
Security classes define user and group access rights to application elements. As previously
discussed, you create security classes in Performance Management Architect by adding a
dimension of the security class type.
After creating a dimension for security classes, you associate the security class dimension with
the Security Class properties of the dimensions for which security is enabled.
A system-generated security class called [Default] is created as part of an application, and has the
following properties:
• It cannot be deleted or modified by users.
• Access rights can be assigned to the security class [Default].
• Any member without a security class (where security class = <blank>) is treated as if it has
the security class [Default].
Within applications, after you provision users and groups and create security classes, you can
specify the type of access that each user and group has to each security class.
You can assign users one of five access types: None, Metadata, Read, Promote, and All.
By default, the access assignment table displays all user and groups in the rows and all security
classes in the columns. You can filter the display to show only selected user, groups, and security
classes. You can use the Pivot Table feature to toggle between two views for the assign access
table. For example, if users and groups are on the rows and security classes are on the columns
and you click Pivot Table, then the users and groups move to the columns and the security
classes move to the rows.
When you grant users access to a security class, you can enable email alerts. Email alerts can be
used for intercompany reporting and also to inform the users of process unit status changes for
entities and scenarios that use the security class. To receive email alerts, a user must have All or
Promote access to the security class. By default, email alerts are disabled.
For applications created by using classic administration, you can create and delete security
classes in the assign access table. For applications created by using Enterprise Performance
Management Architect, you must create and delete security classes by using the Security Class
dimension in your application.
You can run security reports to review security that you set up for the application. You can select
from these options:
• Classes by User – Displays the security classes assigned to each user.
• Roles by User – Displays the security roles assigned to each user.
• Users by Group – Displays the users assign to each security group.
To run security reports:
1. In Workspace, select Navigate, then Administer, and then Shared Services Console.
2. Expand the Application Groups folder, and then expand the application group for your
application.
3. Right-click the application and select Assign Access Control.
4. Click Security Reports.
5. Perform one of the following actions:
- Select Access Rights, and then select Classes By User or Roles By User, or both.
- Select Users By Group.
6. Select a report format and template.
You can configure security auditing to track provisioning and Lifecycle Management activities at
the global, project, and application levels.
Global-level auditing enables you to audit security and artifacts handled by Shared Services.
Project- and application-level auditing enable you to audit security activities related to a specific
project or application performed through Shared Services.
Note: Project and application security activities that are performed outside Shared Services—for
example, assigning calculation scripts in Essbase—cannot be audited. Also, assignment of
security classes to artifacts cannot be audited.
You can run audit reports and view them to track changes made to the security data over a period
of time.
Note: Auditing must be configured before you can generate audit reports.
To run audit reports:
1. Log on to Shared Services.
2. Select Administration, then Audit Reports, and then Security Reports to display audit
information related to the security tasks for which auditing is configured.
3. Select the user and date range for which the report is to be generated.
4. Click View Report.
6. Optional: Click Export to export the report to a CSV file, which can be opened in Microsoft
Excel.
By default, the security report file is named auditsecurityreport.txt.
7. Click Close.
In addition to using Shared Services to provision users and groups and assign access, you can
use it to load security information from a text file.
!USERS_AND_GROUPS
FINAPPS\AdminGroup
FINAPPS\ChrisW
FINAPPS\PatM
!ROLE_ACCESS
Administrator;FINAPPS\trnadmin
Load System; FINAPPS\AdminGroup
!SECURITY_CLASS_ACCESS
System;FINAPPS\AdminGroup;All;Y
System;FINAPPS\ChrisW;Read;Y
Europe;FINAPPS\ChrisW;All;Y
The section includes the security class, the Microsoft Windows domain name for the user or
group, the user or group name, the access right, and Y or N for the email alert right. A backslash
separates the security class from the Microsoft Windows domain name. The following are a few
examples:
class;Domain\User;rights;alerts
class;Domain\Group;rights;alerts
Security information load files can be in an ASCII format, supporting multibyte character sets
(MBCS), or in a Unicode format, using little-endian byte ordering. The default file name extension
for security information load files is SEC.
When you load a security information file, you can clear existing application security information
(before beginning the load).
You can extract security information to a file. You select a delimiter for the file and the security
elements that you want to include.
Valid delimiter characters: , ~ @ # $ % & ^ | : ; ? \
To extract security:
1. Select Consolidation, then Extract, and then Application Elements.
The Extract Application Elements task is displayed.
2. In the Filters area in the Security section, select the security elements to extract.
3. In the Delimiter list in the Security section, select the delimiter to use in the security file.
4. Click Extract.
A Download button is displayed in the Security section.
5. Click Download.
The File Download dialog box is displayed.
6. Click Save.
The Save As dialog box is displayed.
7. Browse to a location where you want to save the file, and click Save.
Answer: d
Answer: a
Answer: a
All except one are access types that you can assign to a
security class. Identify the odd one.
a. Read
b. Write
c. Metadata
d. None
Answer: b
Formatting
Custom formula
column
Data forms are templates, with predefined row and columns, that users can use to input and
view specified data elements. Users cannot add rows and columns to or remove rows and
columns from data forms.
In data forms, users can change point of view selections only for the dimensions that you
specify when you set up the form. For example, you can set up the point of view for a form so
that users can select the period but not the scenario and entity for which they want to enter
data.
You can define links from one form to another to enable users to drill through to view data in
the linked form.
If you use Financial Data Quality Management (FDM) to load data into an application, users
can drill from data forms to FDM to view the source data. The process of drilling down is
similar to the one used in data grids.
New Form
Open Form
View Script
Submit Data
Refresh
Cell Text
Instructions
Reset
Disable/enable single-click
In data forms, you can right-click a data cell and use the shortcut menu commands. The
commands are similar to the data grid menu commands. The availability of menu commands
depends on the cell status and your security rights.
Note: When you perform consolidation actions in data forms, you must click Refresh to
refresh the data in the form.
Force Calculate
Calculate Execute
On Demand
Rules
Data Forms provide three calculation methods. The Calculate and Force Calculate options
execute all rules of the calculate type defined for the application. The Execute option enables
users to select an individual On Demand rule to run. On Demand rules are useful when you
want to run only a subset of calculations to quickly see the results in the data form. For
example, when you are working in a data form that has been set up to run a specific On
Demand rule, you can enter data, and then run the On Demand rule to quickly see the results
of the calculation.
Note: You cannot use On Demand rules if you are creating and deploying the rules by using
Calculation Manager. On Demand rules are valid only in VB script rule files that are loaded
into your application from the Load Application Elements task.
When you run rules by using the Calculate, Force Calculate, or Execute toolbar options, they
are run for the currently selected POV, and for all row and column members on the form. For
example, if entity members are on the columns, they are run for all the entity members on the
form. If rules are run by using the Calculate, Force Calculate, or Execute option from the
shortcut (context) menu, the rules are run for the currently selected members only.
By default, a new data form includes one column with the Scenario dimension and one row
with the Period dimension. You use the Form Designer to add and remove rows and columns,
and to move dimensions between the rows, the columns, and the POV. For example, you can
move the Year dimension from the POV to a column to view Years in columns.
Unlike data grids, data forms enable you to specify formatting, custom headings, and other
display options for individual rows and columns. For example, you create a row for the
California member and format it in bold, 10 pt text. You create additional rows for the children
of the California member and format them in plain, 8 pt text.
If you use a member list in a row or column, when the form is displayed, it includes rows for
each member in the member list.
• Drag the dimension from the POV to the desired row or column.
To reorder dimensions in a row or column:
1. In the row or column that you want to reorder, click the Options list and select
Reorder Dimensions.
2. Use the arrow buttons to reorder the dimensions.
3. Click OK.
To remove dimensions from rows or columns:
• Right-click the dimension and select Remove Dimension.
Options that you set for individual rows or columns override the defaults for the form. The
following table describes the options that are available for rows and columns:
Option Description
Cust Header Style Enter formatting keywords for the row heading or
column heading.
No Suppress Turn off suppression for the specified row. Thus,
regardless of the suppression options that are set for
the form, the row is displayed.
Decimal Places Specify the number of decimal places. Valid values are
0 through 9.
Cell Text Specify the cell text label to use for cell text rows or
columns.
Calc Expression Contains the formula for the row or column (available
only if Calculated Row/Column is selected).
The following table describes the options that are available only for rows:
Option Description
Add Member For forms that suppress NoData cells, this enables
users to enter data for suppressed members. The
option adds an icon that users can click to select
members and enter data. You specify the dimension
and member list from which users can select.
The following example adds an icon that enables users
to select members from the Markets member list of the
Custom1 dimension:
C1{Markets}
You can use style properties to apply formatting to forms. Each style property consists of a
property name, a colon, and a value. The value can be one or more words, separated by
spaces as in the following example:
color:red; text-align:right
The Style option is interpreted by the browser, not by Financial Management. Therefore, it is
limited only by what the browser supports. The Style option uses the standards supported by
the World Wide Web Consortium (W3C). For information about style standards, see the
website at http://www.w3.org/TR/REC-CSS2.
By default, formatting assigned to rows overrides formatting assigned to columns. For
example, if column 2 is italic and row 5 is bold, the cell at the intersection of column 2 and row
5 is displayed in bold.
You can combine styles at row and column intersections by including, for a row, a semicolon
as the first character in the Style text box or Cust Header Style text box. For the example in
the slide, because the first character in the Style text box for the Total Sales row is a
semicolon, the cell at the intersection of Total Sales and Quarter 1 is displayed in bold italic.
For rows and columns, you can use the following keywords to select a period relative to the
current POV:
• CUR
• FIRST
• LAST
• NEXT
• PRIOR
You can also specify a numeric offset. For example, if the current period is March, CUR -2
selects January.
keyword.
3. Optional: In the Numbers list, select an offset number.
4. Click the keyword you selected.
The keyword and offset are added to the Member Selection List.
5. Click OK.
You can use the Scalc function to create, in columns or rows, custom formulas that use
standard mathematical operators. The specified calculations are performed in the client’s web
browser. The slide example subtracts column 2 from column 1.
You can use the Scalc function to specify more complicated calculations in rows, columns, or
cells. The specified calculations are performed in the application server. You can use the
following types of items:
• References to dimension members. The following example references the Purchases
and OtherCosts of Account dimension members:
SCalc(((A#Purchases)-(A#OtherCosts))*100)
• Cell references, using the syntax Cell(rowIndex,columnIndex). The following
example refers to the cell in the fourth row of the second column: SCalc(Cell(4,2)).
• Row references, using the syntax Row(rowIndex). The following example divides row
4 by row 2: SCalc(Row(4)/Row(2)).
Note: For rows or columns that contain member lists, the calculation is performed on the total
for the members of the list.
You can set up columns and rows for input of cell text, thereby enabling users to enter text
annotations directly in the data form, instead of in the Cell Text dialog box.
For the example in the slide, column 5 displays cell text for the Quarter1 member. The
[Default] cell text label is selected. The reference to the Quarter1 member, in the column
definition for column 5, connects the text entered in the cells for column 5 to the Quarter1
member.
To set up text rows and columns:
1. Select a row or column.
2. Expand Row Options or Columns Options.
3. In the Cell Text list, select a cell text label.
The default settings do not override the settings for individual rows and columns.
To set up column and row defaults:
1. In the Form Details section, set the grid, print, and suppression options for columns and
rows.
2. Under Display Options, select from the following options:
- Select Single Period to view, in the line-item entry window, only the period for the
selected cell.
- Select Calculate by Row to change the default calculation order (columns first) to
rows first. For some calculations, for correct results, rows may need to be
calculated first.
- In the Show list, select whether to show member labels or descriptions, or both.
You can use the Headings section of the Form Designer to specify heading defaults for each
dimension. In the example in the slide, the Headers section of the Form Designer specifies
that the Entity dimension should display both the member label and description in bold.
To set heading defaults:
1. On the Headers tab, in the Show drop-down list, select Label or Description to display
member labels or descriptions for dimension headings, or Both to display both.
2. In the Style box, enter style keywords.
3. In the Length box, specify the maximum length for row headings.
4. Optional: Perform one or both of the following actions:
- Select Fixed, if you want the maximum and minimum length to be the same.
- In the Other column, enter valid data form scripts for header options that are not
provided by Form Builder.
You can add rules defined as On Demand rules to data forms. The rules you add to the On
Demand section of the form display when users select the Execute menu on the toolbar or
from the context menu.
To add On Demand rules:
1. Expand the Form Details section of the settings pane.
2. Click the On Demand rules button.
3. Select one or more rules to include with the form.
4. Click OK.
You can view and modify data form scripts. For more information about the syntax for data
form scripts, see the Oracle Hyperion Financial Management Administrator’s Guide.
To view the script for a data form:
• On the data form toolbar, click Script .
Before entering data in a data form, you can select any point of
view for the form.
a. True
b. False
Answer: b
Answer: b
Answer: a
Answer: c
Monthly Close
Task List
Enter Journals
0100101100
0100101100
010010110
01001011
Consolidate
0100101100
010010110
01001011
Report
A task list contains items and tasks that you use frequently (for example, data forms, data
grids, and reports). You access task lists from the Task List section of the documents pane.
You can also access task lists through Excel and Outlook. By setting up task lists, you can
complete your workflow without navigating among forms, grids, and report modules.
For the example in the slide, the Monthly Close task list consists of the following tasks: enter
journals, review, consolidate, report.
To organize the documents of a task list, you can add folders. Users can then expand folders
and select one or more documents. For the example in the slide, the US Forms folder is
nested inside the MonthlyClose task list.
If your workflow involves many tasks, you can nest task lists. Nesting task lists makes
navigation easier for end users. For the example in the slide, the “Journal tasks” task list is
nested inside the MonthlyClose task list.
You can create private or public task lists. Private task lists can be accessed only by the users
who create them. To limit access to a list, you can assign a security class to the list. For
example, you can assign the Admin security class to a task list that you want to limit to
administrators.
To create task lists:
1. Select Consolidation, and then select Documents.
The Documents tab is displayed.
2. Select Actions, then New, and then Task List.
The new task list is displayed.
3. Add items to the task list. (See the following section “Adding Items to Task Lists.”)
In Financial Management, when you create a related content document, the document serves
as a link to a resource in another product. For example, you can add a report from Financial
Reporting to a task list or you can launch the report from the Documents tab.
To add related content:
1. Select Consolidation, and then Documents.
The Documents tab is displayed.
2. Select Actions, then New, and then Related Content.
The Related Content tab is displayed.
3. Click Browse .
The Select Resource Document dialog box is displayed.
4. Select the document that you want to make available as related content.
5. Click OK.
6. Click Save.
The Save Document dialog box is displayed.
7. Enter a name and description for the document.
8. In the Security Class list, select a security class.
9. Click Save.
Before you can add a link to a task list, you must create the link.
• When you create a link, you can specify whether it should be displayed on the same
page or in a separate window.
• For links to web pages that are time-consuming to open, you may want to specify that
the system prompt the user before opening the web page.
• You can choose to pass single sign-on information to the URL being accessed. The
Custom Link option includes that application name as well.
• The link can be launched from the Documents tab as well as from task lists.
To add links:
1. In the Documents tab, select Actions, then New, and then Link.
The Define Link dialog box is displayed.
2. In the URL field, enter the link address.
3. Specify how you want the link to open and display.
4. Click Save.
5. Enter the name and description of the link, and select a security class.
6. Click OK.
Answer: b
Answer: a
All except one can be added to a task list. Identify the odd one.
a. Journal reports
b. Data grids
c. Data forms
d. Excel spreadsheets
Answer: d
Answer: a
3
East Sales
Sale Customer
Administration Marketing
Plant1 2 West Sales East
1 East
2
East Sales 1
USA
RentalRevenue: 0
RentalExpense: 0
California Connecticut
RentalRevenue: 1500 RentalRevenue: 0
Elimination of intercompany balances occurs during data consolidation. During the elimination
process, differences between intercompany account balances are posted to a plug account.
For the example in the slide, East Sales leased equipment worth USD $1,500 from Plant1. When
data is consolidated, the intercompany account balances for the RentalExpense and
RentalRevenue intercompany accounts are eliminated at the first common parent, the USA entity.
Because balances for intercompany partners may not agree, you need accounts that, upon
consolidation, record the differences between pairs of intercompany account balances. In
Financial Management, these storage accounts are called plug accounts.
Note: You use plug accounts to track eliminations. If you do not use a plug account, you can still
track intercompany data, but the data will not be eliminated during consolidation.
The example in the slide shows a USD $500 Sales intercompany balance against a USD $600
Purchases intercompany balance. When the consolidation is performed, the USD $100 difference
is placed in the intercompany difference plug account (IntercoDiffPL).
Intercompany eliminations are stored in the Value dimension. Because Value dimension members
are displayed in data grids and reports, you can easily audit intercompany eliminations.
For the Entity Currency members that are associated with intercompany balance accounts,
reversing entries are created in Elimination members. The reversals result in the following:
• Zero balances are consolidated to the first common parent of the Entity Currency member
that is associated with the parent account
• The differences between the eliminated balances are posted to the Entity Currency member
of the plug account
For the example in the slide, CA01 and CA03 have intercompany account balances in the
SalesInterco and PurchasesInterco accounts. The Elimination member provides reversing entries
for the account balances. Therefore, the Entity Currency members for the SalesInterco and
PurchasesInterco accounts for the parent CA_Top have zero balances. The balances eliminated
from SalesInterco and PurchasesInterco are posted to the IntercoDiffPL plug account. CA_TOP
displays a balance of 100 for IntercoDiffPL, which is the difference between the eliminations
posted from the intercompany accounts.
Specifies whether
Specifies a security
class for the entity
for the ICP
dimension
You must set the Is ICP property for all entities that act as intercompany partners and have
intercompany data.
The Security As Partner property assigns the security class to be used for an entity when the
entity acts as an intercompany partner in the ICP dimension. For example, you may want users in
Europe to be able to enter intercompany transactions between European entities and United
States entities, but not be able to modify data for United States entities. To achieve this objective,
you make the following security assignments:
• For United States entities, you assign USA for the Security Class property and Intercompany
for the Security As Partner property.
• You give users in Europe read-only access to the USA security class and read/write access
to the Intercompany security class. Thus, you enable users in Europe to enter data for United
States entities only when the entities are selected in the ICP dimension.
For instructions on setting member properties, see the lesson titled “Managing Dimensions.”
Plug account
To use accounts in intercompany transaction processing, you must set two member properties:
• Is ICP: To flag the account as an intercompany account
• Plug Account: To store differences between intercompany balances
For instructions on configuring accounts, see the lesson titled “Configuring Accounts and Custom
Dimensions.”
Entities to match
Intercompany matching reports help you track intercompany transactions for analysis and auditing
purposes. After consolidating data, you can run intercompany matching reports, which provide
details on intercompany account balances that were eliminated.
When creating intercompany reports, you can select intercompany entities and their partners, as
well as intercompany accounts.
• Entity and Partner are the entities for which you want to match intercompany transactions.
• Accounts and Matching Accounts are the intercompany accounts for which you want to
match transactions.
• If you select a plug account, all accounts for which the selected account is the plug account
are included in the report.
You can also select one or more of the following report options:
• Suppress Matches: Suppress transactions for which the entity and partner amounts are
less than the amount set in Matching Tolerance.
• Matching Tolerance: To see only the out-of-balance transactions that exceed the value that
you specify, enter a value or use the default value of 0.
partners.
• Suppress Details: Suppress intercompany detail and print only the total difference for each
entity-partner section.
• Group By: Specify a custom dimension by which to group the transactions.
• Suppress Customs: Suppress custom dimensions.
• Scale Factor: Select a scale factor or use the default value of 0. For example, if you enter a
scale factor of 3, the report amount is displayed in thousands. If the scale factor is 0, the
report amount is displayed in units.
• Decimal Override: Select a decimal setting, to override the setting defined in the account, or
You can access intercompany matching reports from the Documents task. When you run a report,
you can override the default report settings. For example, you can select a different partner entity.
The date, time, and user are displayed as header information.
Tip: You can preview intercompany reports during the design process by clicking Print/Preview on
the Intercompany Report tab.
To run intercompany matching reports:
1. In the Documents task, double-click an intercompany report.
The Override dialog box for the report is displayed.
2. Optional: Select a POV.
3. Optional: Select an entity and a partner.
4. In the Report Format list, select a format.
Note: You can select PDF, RTF, HTML, or XLS format.
5. In the Select Template list, select a report template.
6. Click OK.
The Running Tasks tab is displayed.
7. Click Intercompany Matching Report .
The report is displayed.
Oracle BI Publisher (BI Publisher) is a reporting solution from Oracle that enables you to create
and format reports.
You can use BI Publisher report templates to format intercompany reports. The templates offer
report print options, including PDF, RTF, HTML, or XLS. Additionally, you can modify these
templates in Microsoft Word.
To format intercompany reports with BI Publisher:
1. Open Microsoft Word.
2. Navigate to your Server Working folder\Report Style Sheet\Templates\Intercompany
folder in your Financial Management directory, and open the intercompany report template.
3. Make format changes to the template.
4. Navigate to your Server Working folder\Report Style Sheets\Sample XML\Intercompany in
your Financial Management directory, and open the ICP.XML file.
5. Preview your changes.
Note: You can preview your changes in PDF, RTF, HTML, or XLS.
6. In the template directory, save the modified template with a new name.
Note: If you have more than one Financial Management server, you must save the
modified template in the template directory of each server.
7. In the application, select a report format, select the modified template, and click OK.
The Intercompany Transaction module enables you to track and reconcile intercompany
transaction details at the invoice level across accounts and custom dimensions.
Note: Use of the Intercompany Transactions module is optional.
With the ability to view the details of intercompany invoices at any time, you can reconcile
intercompany account differences frequently, and thus minimize the impact of such
differences on the closing cycle. You can also analyze differences due to real errors in
transaction currency or differences due to exchange rates. You perform the following tasks
by using the Intercompany Transactions module:
• Import intercompany invoices for entities. You can also manually enter invoices.
• Match transactions between entities at the invoice level, in both the transaction currency and
the reporting or parent currency.
• After matching and reconciliation, post summarized totals to your Financial Management
intercompany accounts.
For more information about managing intercompany transactions by using the
Intercompany Transactions module, see the Oracle Hyperion Financial Management
Administrator’s Guide.
Oracle Hyperion Financial Management 11.1.2: Create & Manage Applications 19 - <#>
Summary
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Answer: b
Answer: a
Answer: c
Adjusted
Account Journal
Account
Balance Adjustments
Balance
Financial Management journals provide an audit trail of changes made in an application. Journals
tell you which users made adjustments and which accounts, entities, and time periods are
affected. All adjustments through journals must be reviewed and approved before you can post
them.
With journals, you can:
• Create double-sided journal entries by using debits and credits
• Balance entries, or you can permit single-sided, out-of-balance entries
• Create recurring journals that are repeated for several future periods
• Create auto-reversing journals that generate reversing entries in the next time period
• Use the journal approval process to provide accountability
After creating a journal, you submit it to your supervisor for approval before posting it to the
Financial Management database.
You can view automated consolidation transactions as automated consolidation journals. You can
extract the journals to external files, and print them through journal reports. This option is available
only on the web.
Automated consolidated journals are automatically created during consolidation and facilitate
reporting on the consolidation process. Automated consolidation journals generated from the
consolidation process are displayed in the [Elimination] or [Proportion] Value dimension and
provide a user-friendly way to report the amount in the child entity that is rolled up into the parent
entity during consolidation.
Note
• To generate automated consolidation journals, you must use consolidation rules, and specify
the Nature value. For more information, see the Oracle Hyperion Financial Management,
Fusion Edition 11.1.2.3 Administrator's Guide.
• You cannot edit, scan, submit, approve, reject, post, unpost, or delete the automated
consolidation journals. You can only open and view journals, run reports, and extract
journals.
- For the Value member, select [Proportion] or [Elimination], and then click OK.
A list of journals generated during the consolidation process is displayed.
2. Click a journal to view the transactions.
Note: You can view transactions based on your security rights to the members in the POV
and to the journal security class. You must also have the Read Journals or Journal
Administrator security role.
The Value dimension plays an important role in journal processing. When you load data from a file
or use a data form or grid to enter data, the values are stored in the Entity Currency member of the
Value dimension. When you post adjustments from a journal, the adjustment values are stored in
the specified adjustment member.
Financial Management stores the adjusted data by combining the values in the Entity Currency
and Entity Currency Adjs members and storing the result in the Entity Currency Total member.
The adjusted value is used during the consolidation process.
Journal A:
<Entity Currency> 500 –100
<Entity Currency Adjs> –75
If more than one journal is posted to an adjustment member for the same account, the results are
cumulative. The total from the current journal is added to or subtracted from the existing total in
the adjustment member.
For the example in the slide, Journal A posts –100 to Entity Currency Adjs, and Journal B posts 25
to Entity Currency Adjs. The total in Entity Currency Adjs is –75.
If entities roll up to more than one parent, you can use the Parent Adjs member to create parent
adjustments. Parent adjustments enable you to apply an adjustment for a child to a selected
parent, rather than to all parents. For the example in the slide, if WestSales is a child of both
SalesServices and California, parent adjustments made to WestSales will affect only
SalesServices or California.
Note: Parent adjustments are available only for parent entities for which the
AllowAdjFromChildren application setting is selected (On).
You can use the Contribution Adjs member to adjust the amount a child contributes to a parent
after percent ownership and eliminations have been applied.
To create parent and contribution adjustments:
1. Select Consolidation, then Journals, and then Manage.
2. In the journal point of view, select the Parent Adjs member or the Contribution Adjs member.
3. Start a new journal.
4. In the journal POV, select the child/parent combination to adjust.
For each scenario, you must open time periods before you can post journal entries to them. By
default, all periods in Financial Management have an initial status of Unopened. You can open
and close periods at any time, but you cannot change an opened period to unopened.
Note: You must have the Administrator or Journals Administrator security role to manage periods.
To open periods:
1. Select Consolidation, then Journals, and then Periods.
The Journal Periods task is displayed.
2. Select the scenario and year of the periods that you want to open.
3. In the Period section, select the periods that you want to open.
4. Click Open .
In Financial Management, you use the Manage Journals task to create journals and to enter
information into the journals. You enter journal information by using journal templates or by
creating blank journals.
You can create journal groups to help classify journals by type:
• Reclasses
• Entry corrections
• Reversals
• Accruals
• Minority interest accounting entries
• Elimination of adjusting entries
• Allocations
• Overhead
Note: You must have the Administrator or Journals Administrator security role to create journal
groups.
You can create a journal template to post adjustments that have common information, such as
entities or accounts. For example, you create a template that includes the Short Term Assets and
Long Term Assets accounts, for reclassifying assets. You use this template to create journals for
reclassifying assets for different periods.
Template Types
You can create two types of journal templates:
• Standard templates: Contain accounts and entities for adjustments that you enter
frequently
• Recurring templates: Contain complete information for identical journal entities that occur
for more than one period
Standard journal templates are independent of scenario, year, and adjustment member (for
example, Parent Adjs). You select these when you create a journal based on a template.
Recurring templates are independent of scenario and year, but not adjustment member. You must
select an adjustment member when you create recurring templates.
example in the slide, a template is created for reclassifying sales from domestic to export;
therefore, the Destinations dimension, which contains the domestic and export members, has
been moved from the POV to the rows.
To create journal templates:
1. Select Consolidation, then Journals, and then Templates.
2. Click New.
3. Perform one of these actions:
- To create a standard template, select Standard Template.
- To create a recurring template, select Recurring Template.
Type Description
Balanced by Entity Total debits and credits for each entity must
balance.
Before creating journals, you must set the POV based on your requirements. You set the POV in
the Manage Journals task. The POV determines the members for the Scenario, Year, Period, and
Value dimensions. You can select from the following adjustment members in the Value dimension:
• Entity Curr Adjs
• Parent Curr Adjs
• Parent Adjs
• Contribution Adjs
To set the POV:
1. Select Consolidation, then Journals, and then Manage Journals.
2. In the point of view, select members for the Scenario, Year, Period, and Value dimensions.
You can start with a blank journal or you can create the journal from a template.
To create journals:
1. Select Consolidation, then Journals, and then Manage Journals.
The Manage Journals task is displayed.
2. Click New.
3. Perform one of these actions:
- To create a blank journal, select Journal.
- To create a journal based on a template, select Journal from Template.
4. In the Label text box, enter a journal label.
5. Optional: In the Group list, select a group to assign to the journal.
Type Description
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Balanced by Entity Total debits and credits for each entity must
balance.
You can use a recurring template to create journals automatically. When you generate a journal
from a recurring template, you receive a confirmation message that the journal has been
generated. The status of the journal is Approved. To create a journal using a recurring template,
you must be assigned the Generate Recurring security role. If you have the Journal Administrator
role, you automatically receive the Generate Recurring role.
To create journals by using recurring templates:
1. Select Consolidation, then Journals, and then Templates.
2. Open a recurring template from which to create a journal.
3. Click Generate.
4. Select a scenario, year, and period for which to generate the journal, and click OK.
Auto-reversing journals affect two periods of data. You post an auto-reversing journal to adjust
values in one period; the system automatically creates a journal that reverses those adjustments
for the next period. The journal created in the following period has the Approved status. You can
then post this approved journal for the reversal to take effect.
When you unpost an auto-reversing journal, the status of the journal reverts to Approved, and the
system-generated, auto-reversing journal in the next period is deleted. You cannot unpost an
auto-reversing journal after its auto-reversal is posted.
For example, you can create and post an auto-reversing journal in January that adjusts the Sales
accounts for EastSales. The system creates a journal that reverses those adjustments for
February.
To create auto-reversing journals:
• Create a journal by using the procedure described in the section “Creating Journals” earlier in
this lesson. However, in the Type list, select Auto-reversing instead of Regular.
1 2 Status: Submitted
Status: OR
Status:
Journal Status:
Approved Rejected
Posted
If Approved, user can
4 post the journal.
After creating journals and entering journal data, users must submit the journals to a supervisor for
approval before they can post them to the Financial Management database.
1. Users review and submit journals one at a time or in batches.
2. The status of the journal changes from Working to Submitted.
3. A reviewer (a user with the Approve Journal security role) approves or rejects the journal.
4. If the journal is approved, the user can post it (the user must have the Post Journals security
role).
Guidelines
• You cannot submit journals of the type Balanced unless the total debits equal the total
credits.
• You cannot submit journals of the type “Balanced by Entity” unless the total debits equal the
total credits for each entity.
• If you have the Journal Administrant security role, and the period is opened, you can post a
journal with a Submitted, Working, or Rejected status.
• You can unpost a posted journal. Reversing journal entries are created in the database, and
the status of the journal changes to Rejected.
After reviewing and posting the journal adjustments, you can view them in a data grid or in the
Entity Details report.
You can use a data grid to view the adjustments made to the accounts for an entity. For example,
you can change the Value dimension in the grid POV to view the values in the Entity Currency
Adjs, Entity Currency, and Entity Currency Total members.
The adjustment members (Entity Curr Adjs, Parent Curr Adjs, Parent Adjs, Contribution Adjs)
show the cumulative total posted from all journals to the cell. You can use the Cell Adjustments
feature to view the individual journal postings to the cell.
To view adjusted data in data grids:
1. Open a data grid.
2. Right-click a cell for an adjustment member, and select Cell Adjustments.
You can use the Entity Details report to view details of the entire consolidation path for a specific
cell, including the journal entries that were generated in the journal posting process.
To view adjustments in the Entity Details report:
1. In the data grid, select a valid intersection.
2. Right-click the valid intersection cell, and select Entity Details.
Note: In an entity report for a Parent entity, the data shows only the totals from its children.
Define
Filter
columns.
journals.
You can create and format journal reports to check the status of journals and to review journal
adjustments. To design a report, you select columns, set up column attributes, and set up filters.
To create journal reports:
1. Select Consolidation, then Journals, and then Reports.
The Journal Report task is displayed.
2. Select Actions, then New, then Reports, and then Journal.
The Journal: New Report tab is displayed.
3. Select the POV for the report.
4. Set up columns, column attributes, and filters.
5. Click Save.
By default, a journal includes the following columns: Label, Description, Entity, and Account. You
can remove columns, add additional columns (for example, for custom dimensions or journal
status), and reorder columns.
You can sort columns in ascending or descending order, add subtotals, and show or suppress
repeat heading information. For Account, Entity, or custom dimension columns, you can display
member names, descriptions, or both.
In the example in the slide, the journal report is sorted in ascending order by the Entity column.
The Entity column displays the member description. The Account column displays both the
member label and descriptions.
You can use the Row Filters pane to limit the journals that are included in the report. For example,
you can include only posted journals or only journals that belong to a specified journals group.
When you run journal reports, you can override the POV that was saved with the report.
To run journal reports:
1. Select Consolidation, then Journals, and then Reports.
The Journal Report task is displayed.
2. Select a report.
3. Select Actions, and then Print.
The Report Override Options dialog box is displayed.
4. Optional: Override the saved POV for the report:
a. Select Override POV.
b. Select a POV for the report.
5. In the Report Format list, select a format.
Note: You can select HFM_FORMAT, PDF, RTF, HTML, or XLS format.
6. In the Stylesheet list, select a stylesheet.
7. Click OK.
The Running Tasks tab is displayed.
8. Click Journal Reports .
Answer: b
Answer: d
Answer: b
Answer: b
Translating Data
EUR
GBP
Currency translation converts account data from one currency to another. When you
consolidate data, currency translation occurs if the parent entity has a different default
currency than the child entities. Data in the Entity Curr Total member of the child is translated
to the parent’s currency, and the result is stored in the corresponding child currency member.
For example, if UK has a default currency of GBP and its parent, Europe, has a default
currency of EUR, data in the Entity Currency Total member of UK is translated to EUR and is
written to the Parent Currency member for UK. This is summed with any parent currency
journal adjustments in the Parent Curr Adjs member for UK to Parent Curr Total. The data in
the Parent Curr Total member of UK is then consolidated to the Entity Currency member of
Europe.
You may need to translate to currencies other than the parent currency. The Value dimension
contains members for all application currencies.
UK April
The example in the slide shows the following steps of the translation process during
consolidation:
1. The Currency property of the child being consolidated is compared with the Currency
property of the parent. If the currencies are different, translation is initiated.
2. The exchange rate account and translation method are selected based on the account type:
- For Revenue and Expense accounts, the rate account specified by the Default
Rate For Flow setting is used. If PVA For Flow is enabled, the PVA method is
selected; otherwise, the VAR method is selected.
- For Asset and Liability accounts, the rate account specified by the Default Rate
For Balance setting is used. If PVA For Balance is enabled, the PVA method is
selected; otherwise, the VAR method is selected.
3. The value in the Entity Currency Total member is translated by using the selected rate
account and translation method. The result is stored in the Value dimension currency
member that corresponds to the parent’s default currency.
4. The translated value is consolidated to the Entity Currency member of the parent.
Default Rate For Flow, Default Rate For Balance, Use PVA For Flow, and Use PVA For
Balance are application-wide settings that apply to all accounts. You can use custom
translation rules to override these settings. For example, you create a custom translation rule
to use a historical rate for some balance sheet accounts but not for others.
Oracle Hyperion Financial Management 11.1.2: Create & Manage Applications 21 - 4
Data Grids and Data Forms for Exchange Rates
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
“To” custom
dimension
‘From” custom
dimension
You maintain currency rates by loading or manually inputting data to the currency members of
the custom dimensions that you designated as the “From” and “To” dimensions when you
created custom dimensions. The “From” and “To” custom dimensions contain system-defined
currency members that you can access by using the [Currencies] member list. You must input
currency rates to accounts that have the Currencyrate account type.
You enter currency rates by defining a data grid or data form by using the guidelines in the
following table:
Dimension Description
View YTD
Entity [None]
Value [None]
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
After entering the exchange rates, you can translate the currency for an entity to any
application currency in the Value dimension. If the Value dimension is not on the grid rows or
columns, the destination currency is specified in the point of view.
To translate data in data grids:
1. Select Consolidation, and then Documents.
2. Open a data grid.
3. Right-click the cell for the currency, and select Translate.
Currency is GBP.
When a current value member in the point of view is a currency other than the local currency
of the member, the calculation status indicates whether data needs to be translated.
To check the translation status:
1. In the application, select Consolidation, and then Documents.
2. Open a data grid.
3. In the Cell area of the Grid Display Options pane, in the Show list, select Calculation
Status.
Status Description
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Answer: a
Answer: a
Answer: b
Answer: d
Running Consolidations
Translate and
Data consolidation is one step of the business process for large (or public) companies. For the
example in the slide, consolidation is typically performed after data is collected, calculated, and
adjusted for base-level entities.
You use the consolidation features in Financial Management to consolidate financial data for
reporting and analysis.
NetProfit
Connecticut 20000
Consolidated data
for the Connecticut
entity
Administration East 6000
Development 4000
EastSales 5000
Consolidation is the process of gathering data from descendants and aggregating the data to
parent entities. Consolidation applies only to the Entity dimension. After entering or loading data
into base-level entities, you run a consolidation for a selected scenario and period to aggregate
the data throughout the organization.
The example shown in the slide displays the consolidated data for the NetProfit account of the
Connecticut entity. During consolidation, the data values from the base-level entities
(Administration East, Marketing East, Development, and EastSales) are rolled up to the
parent-level entity, Connecticut.
• Run calculations.
• Perform currency translations.
• Apply ownership percentages.
• Eliminate intercompany balances.
Connecticut
California
When you consolidate an entity, processes that are required for the descendants of the entity run
automatically.
• Calculation rules are run for all descendants of the entity for the period being consolidated
and for all prior periods.
• If the data for the child entity and the data for the parent entity are in different currencies, the
data is translated based on the exchange rate. For the child entity, the translated value is
stored in the Parent Currency member of the Value dimension. The translated value in
Parent Currency is rolled up to the parent.
• If the parent’s ownership of the child is less than 100%, the ownership percentage is applied.
Intercompany transactions between entities are eliminated at their first common parent.
[Contribution Total]
[Proportion] [Elimination]
[Parent Total]
During the consolidation process, the value in the Entity Currency member of the child members
may be transformed before being aggregated to the parent. The Value dimension stores data for
the intermediary steps in the transformation. You can display Value dimension members on data
grids and reports. This information provides an audit trail that you can use to determine how the
value that each entity contributed to the parent was derived.
For the example in the slide, the Contribution Adjs, Proportion, Elimination, Parent Adjs, Parent
Currency, Parent Curr Adjs, and Entity Currency Adjs value dimension members store data.
Note the following points about the consolidation process:
• Proportion detail is generated when consolidation rules are executed. The Proportion
member also stores the results of the consolidation percentage that is applied to the base
values.
• Based on elimination rules, elimination detail contains eliminating balances that result during
consolidation.
• Contribution Total is the contribution of the base entity to its parent. This amount is added to
the other immediate dependent contributions of the parent to obtain the parent consolidated
data. Intermediate contribution-level aggregations are not stored during calculation.
Financial Management maintains the calculation status for every Scenario, Year, Period, Entity,
Parent, and Value combination. The calculation status indicates whether data needs to be
calculated, translated, or consolidated.
You can view the calculation status from the Data Process Control task or from a data grid.
To check calculation status:
1. In the application, select Consolidation, then Data, and then Process Control.
2. Select members from the Scenario, Year, and Period dimensions.
3. Select an entity and relationship (for example, UnitedStates with the Descendants
relationship to view status for the UnitedStates and its descendants).
Status Description
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
OK None of the data for the specified Scenario, Year, Period, Entity,
and Value dimensions changed.
OK SC OK, System Changed. A change may affect the data for the
specified Scenario, Year, Period, Entity, and Value dimensions.
For example, a new rules file or metadata file was loaded. The
data itself, such as a value of 10,000, has not changed. For a
dimension member attribute, the number of decimal places
associated with the account was set to two, and requires the
value to be changed to 10,000.00.
NoData No data exists for the specified Scenario, Year, Period, Entity,
and Value dimensions.
NoAccess The user does not have rights for the specified dimension
member.
Geographical
100% 100%
80% 50%
By default, parents consolidate their children 100%. However, the application administrator can
specify a consolidation percentage in the PCON column of the Manage Ownership task. The
consolidation percentage determines what percentage of a child entity is consolidated to the
parent entity.
For the example in the slide, 100% of CA_TOP is consolidated into United States, but only 80% of
CA01 is consolidated into CA_TOP. Similarly,100% of Europe is consolidated into Geographical,
but only 90% of ITA_TOP is consolidated into Europe and 50% of ITA02 is consolidated into
ITA_TOP.
You use the Manage Ownership task to manage consolidation information for your child entities:
• Consolidation percentage
• Active status
• Calculate ownership and assign consolidation methods
For the example in the slide, California is the parent entity in the POV. The rows list child entities
of the California entity. The PCON column specifies the percentage of the child that gets
consolidated to the parent.
You can assign ownership by period if you selected Organization by Period in the application
settings. Organization by Period enables you to preserve historical organization structures and
have them coexist in an application with the current organization structure. Organizational
changes may be due to acquisitions, disposals, mergers, or reorganizations.
You assign ownership by period to an entity by selecting whether the status of a child is active or
inactive in the Active system account. The Active account is used as the flag that determines
whether an entity is active or inactive. You can assign values to the Active account in the Manage
Ownership task.
An active status is used to:
• Consolidate a child entity to its parent entity. Inactive entities are not consolidated.
• Affect the data of a parent with an active child. An inactive child does not affect the parent
data.
• Determine Process Management validation. An inactive child is ignored.
• Determine how journal validation rules are followed. No parent adjustments or contribution
adjustments can be posted to inactive children.
SharesOwned /SharesOutstanding
VotingOwned /VotingOutstanding
The Manage Ownership task enables you to automatically calculate a holding company’s percent
ownership and percent control of its subsidiaries based on its stock holdings. Additionally, if you
have defined consolidation methods, the ownership calculation can automatically assign the
consolidation percentage to each subsidiary based on the holding company’s percent control.
Note: The holding company entity and the subsidiary entities must be children of the same parent,
and the holding company entity must be assigned to the subsidiary entities by using the Holding
Company property in the Entity dimension metadata.
The following describes the process for calculating ownership based on shares:
1. In a data grid, or through a data load file, enter share information in the provided system
accounts:
• For each entity, enter the total shares outstanding and the total voting shares outstanding
in the SharesOutstanding and VotingOustanding system accounts.
• For the holding company entity, enter the total shares owned and total voting shares
owned of each subsidiary entity in the SharesOwned and VotingOwned system accounts.
• For each of the subsidiary entities, enter the shares that they own of each other and of the
holding company in the SharesOwned and VotingOwned system accounts. This allows
you to capture indirect ownership of subsidiaries by the holding company. For example,
Entity A, the holding company, owns shares of Entity B, and Entity B owns shares of entity
C. Consequently, Entity A owns a percentage of Entity C indirectly through its ownership
stake in Entity B.
Oracle Hyperion Financial Management 11.1.2: Create & Manage Applications 22 - 13
2. In the Manage Ownership task, select the parent of the holding company and use the
Calculate option on the Calculate Ownership panel to calculate the holding company’s
ownership of its subsidiaries. The ownership calculation populates the following columns in the
Manage Ownership table based on the share information:
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
• DOWN (Direct Ownership) is the holding companies direct ownership percentage of the
subsidiary entity based on shares of stock owned (SharesOwned/SharesOutstanding).
• PCTRL (Percent Control) is the holding companies percentage control of the subsidiary
entity based on the percentage of voting shares owned. (VotingOwned/VotingOutstanding)
• POWN (Percentage Ownership) is the holding companies total ownership of the
subsidiary. This is the total of DOWN plus any indirect ownership percentages derived
from its subsidiaries.
• Method (Consolidation Method): If consolidation methods are configured, a method is
automatically selected for each entity based on the value in PCTRL. The consolidation
SharesOwned/SharesOutstanding
If your application calculates entity ownership based on stock holdings, you can use the Equity
Pickup task, in conjunction with equity pickup rules, to revalue investments. The Equity Pickup
task calculates ownership percentages between pairs of entities based on the values entered in
the SharesOutstanding and SharesOwned system accounts. You can reference these
percentages by using functions in Equity Pickup rules.
For example, for June, you enter 100,000 in the SharesOutstanding system account for the
Monterey entity, and 50,000 in the SharesOwned account of the San Diego entity for Monterey. In
the row of the Equity Pickup table for San Diego as Owner and Monterey as Owned, the %EPU
column displays 5.
In this VB Script example, the PEPU function retrieves San Diego’s ownership percentage of
Monterey for the current year, scenario, and period from the Equity Pickup table. Monterey's
NetIncome account is multiplied by the ownership percentage to calculate the
IncomeFromSubsidiary account.
Hs.Exp "A#IncomeFromSubsidiary.I#Monterey = E#Monterey.V#USD.A#NetIncome
* “ & HS.PEPU( , “SanDiego”, “Monterey”)
Consolidation options
You run consolidations from the Consolidate options list on the Data Process Control task and
data grids. You can use the Task Automation functionality to automate the process. When a
parent is consolidated, all descendants of the parent are also consolidated.
If you consolidate data for a period and the data for prior periods has not been consolidated yet,
the data for the prior periods is consolidated as well.
The following table describes the three options for consolidating data:
Option Description
Oracle Hyperion Financial Management 11.1.2: Create & Manage Applications 22 - <#>
Option Description
Consolidate All Available for any parent entity, regardless of its status.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
options:
• Translate
• Force Translate
To consolidate data:
1. Select an entity.
2. On the toolbar, click Consolidate and perform one of the following actions:
- Select Consolidate.
- Select Consolidate All.
- Select Consolidate All with Data.
3. Confirm that the consolidation process is completed successfully.
You can display entities in a flat list or as a tree hierarchy. You can view entity information by
using the entity label, the description, or both. The default setting is to display the label. You can
show or hide columns, such as Review Level and Journal Status.
Note: To display entities by using the Tree option, you must use the {Hierarchy} member list when
selecting the parent entity.
To set process control panel options:
1. Select Consolidation, then Data, and then Process Control.
The Process Control page is displayed.
2. In the Display Options pane, select the display options.
You can view either a single period or all periods. When you choose all periods, you must choose
to view either the Process Review Level or Calculation Status, and you must select a single review
phase.
To view status for all periods:
1. Select Consolidation, then Data, and then Process Control.
The Data Process Control task is displayed.
2. In the Period View section of the Display Options pane, select All.
3. In the Display list in the Column Settings area, select Calc Status or Review Level.
4. Click OK.
When you consolidate an entity, calculation rules are run for all
descendants of the entity only for the period being
consolidated.
a. True
b. False
Answer: b
Answer: a, b, c
Answer: a
Answer: a
Process Management
Process management is the management of the review and approval of financial data. You can
use process management to submit budget plans and have them approved efficiently, and to
transfer ownership of data. In a centralized environment, you can also use process management
to provide review control and to ensure data privacy.
If process management is enabled for a scenario, validation checks are performed for each
process unit as the data moves from one level to the next. Validation checks are defined by the
administrator to ensure that accounts are in balance.
Example
• Scenario Actual
• Year 2012
• Period January
• Entity West Sales
• Value USD
For the purpose of review, data is organized into process units. A process unit is the combination
of data for specific Scenario, Year, Period, Entity, and Value dimensions. In the Value dimension,
you can select Local, Translated, or Contribution data.
For the example in the slide, the process unit is a combination of data for Actual, 2012, January,
WestSales, and USD.
During the review cycle, users perform actions, such as promote, submit, approve, reject, and
publish, on process units.
First Pass
Submitted
Approved
Published
Process units pass through several process states during the review cycle. The following table
describes the process states:
Task Description
Not Started The review supervisor has not started the process unit, and
only the supervisor can enter data.
First Pass The process unit is started and is in the initial stage for data
to be entered by users with proper access rights.
Review Level 1–10 The process unit is at the designated review level.
Submitted The process unit was submitted and is ready for final
approval.
Approved The process unit was approved.
Security roles:
• Determine the review actions that users can perform
• Aid compliance with Sarbanes-Oxley, especially,
requirements imposed by Section 404
The actions that users can perform are determined by their assigned security roles. The following
table describes the actions permitted for each security role:
Reviewers 1 Can promote a process unit to the next level or reject it. When a
through 9 reviewer promotes a unit to the next level, data for that unit becomes
read-only for users at the current level.
Reviewer 10 Can reject a process unit, but cannot promote it because a next level is
not available. To move a process unit to the Submitted level for final
approval, Reviewer 10 must be a Submitter.
Submitter Can move the process unit to the final stage of the review process so
that it is ready for approval. Although the default action is to promote
the process unit to the next level, the Submitter can omit many levels of
review and go to the last process level (Submitted) before final
approval.
Review Supervisor Has access rights to start a process unit that allows input to the entity’s
data; can also approve and publish the data
Reviewer 2
Before you can use the Process Management option, you must enable scenarios in the Dimension
Library. The system performs validation checks for each process unit as the data moves from one
level to the next.
When you select a single cell, process management is available only for the input frequency of the
scenario. For example, if the input frequency is months, process management is available when
you select January, but it is not available when you select a quarter, such as Q1. In addition, if you
select multiple cells and your selection includes a data cell in which process management is not
supported, the option is not available.
For instructions on enabling scenarios in the Dimension Library, see the lesson titled “Setting Up
Entities, Calendars, and Scenarios.”
For instructions on configuring validation account settings, see the lesson titled “Configuring
Application Settings.”
Because process unit data could be related to hundreds of accounts, reviewers and approvers
may have difficulty in effectively analyzing the data. With submission phases, you can divide a
process unit into submission groups defined by account, custom, and ICP dimensions. You then
assign submission phases to the submission groups and place the groups in hierarchical order to
publish in process management.
For example, in the Actual scenario, you submit the Balance Sheet and Profit/Loss accounts for
review in Phase 1, and supplemental data in Phase 2. In the Budget scenario, you submit
Intercompany data in Phase 1, Balance sheet and Profit/Loss accounts in Phase 2, and
supplemental data in Phase 3. With the process unit divided, smaller chunks of data are
published, giving reviewers and approvers tighter quality control.
Submission Group Guidelines
• The maximum number of submission groups is 99.
• Submission groups can vary by account, custom, and ICP dimensions.
• You cannot assign the same group to multiple phases in the same period. For example, you
cannot assign Groups 2 through 5 to Phase 1, and Groups 3 and 8 to Phase 2, because
Group 3 cannot be assigned to Phases 1 and 2 in the same period.
• During the review process, you can promote each submission group in the process unit
rather than the entire process unit.
• Groups not assigned to a submission phase are not considered part of the review process.
• Base accounts do not inherit submission groups from parent accounts.
• Parent accounts do not assume submission groups from their children.
• A blank submission group defaults to Submission Group 1.
Submission Phase Guidelines
• The maximum number of submission phases allowed in the review process is 9.
Validation Account
Submission Phases
By default, the setting for submission phases is turned off, and the administrator must enable
phased submissions in the application settings by selecting the Use Submission Phase option.
The administrator must then define which dimensions (Account, custom dimensions, and ICP
Members) will be enabled for process management. At a minimum, you must enable at least one
dimension.
You assign validation accounts to submission phases to ensure that the value equals zero before
a process unit is promoted to the next review level. Financial Management application settings
include one validation account for each of the nine submission phases.
Note: If a validation account is not set for a submission phase, validation is not needed for that
phase. You can use the same validation account across multiple submission phases.
For instructions on configuring application settings, see the lesson titled “Configuring Application
Settings.”
For each application, the administrator must decide which dimension members to include in a
submission group.
In the metadata, you set the following attribute for submission groups:
Submission Group=0 to 99 or <blank>
Note
• The default is blank. A <blank> value defaults to the value of 1.
• If you set the submission group to zero, the account is not included in the review process.
• You can specify the submission groups for [ICP None] and [ICP Entities]. The submission
group value assigned to [ICP Entities] applies to all ICP entities in the [ICP Entities] subtree.
To easily work with dimension members, you should categorize them into appropriate
groups. For example, you can define Cash accounts and Investment accounts for Submission
Group 1.
HistData 0 0
Cash 1
Invest 1
ICRec 2
ICPay 2
Liability 3
[None] 1
Golf Balls 5
Tennis Balls 6
Soccer Balls 7
Note: For the dimensions that support phased submission (Account, ICP, and custom
dimensions), you should include every member for the dimension in a submission
group (0 through 99).
For instructions on setting submission groups, see the lesson titled “Managing Dimension
Members.”
Administrators can assign submission groups to each submission phase. Assignments are by
scenario. If a group is not assigned to a submission phase, process management is not applied to
the dimension members within that group.
You can display and manage submission phases by using the Submission Phases task. This task
appears if you enable the Use Submission Phase application setting. You must also be assigned
to the Administrator or Review Supervisor security role.
You can have up to 99 submission groups. You can enter ALL to indicate all groups. The default
for Submission Phase 1 is ALL to indicate all groups.
Note: All groups belong to Submission Phase 1 until you change their assignment.
To access the Submission Phases task:
1. Select Consolidation, then Data, and then Submission Phases.
2. Select a scenario.
3. Perform any of the following tasks:
- Enter one or more groups for a submission phase, and use a comma as a separator for
multiple group assignments (for example, 1, 5, 6, 9, 10).
- Specify a range of groups. For example, to assign groups 1, 2, 3, 4, 5, 7, and 8 to a
submission phase, specify 1-5, 7-8.
4. Click Save.
Access rights for process units can be None, Read, Promote, or All. The following table describes
the access rights:
Access Description
You view the status for process units in the Data Process Control panel. If you enabled
submission phases, the review level for each process unit is stored by the submission phase.
To view process unit status:
1. Select Consolidation, then Data, and then Process Control.
2. Select a POV.
3. In the Data View list, select Local, Translation, or Contribution.
You can select the submission phases for which you want to view status. You can also select the
review and status information for which you want to include columns.
To view status for multiple submission phases:
1. Select Consolidation, then Data, and then Process Control.
The Data Process Control task is displayed.
2. In the Phases Displayed area under the Columns Setting section of the Display options
pane, select the phases to display.
3. In the Review Level Columns and Status Columns area of the Columns Setting section of
the Display options pane, select the status information to display.
Process units can be promoted only if their calculation status is OK, OK SC, or NODATA and the
validation account amount is equal to zero. The Pass/Fail column displays a check mark or an X
to show whether the conditions are met. If the calculation status is OK, OK SC, or NODATA and
the validation account amount is equal to zero, a check mark is displayed in the Pass/Fail column,
indicating that the unit is ready for promotion. If the process unit fails, an X is displayed in the
Pass/Fail column.
If the process unit fails, you must perform the calculation in the current period to ensure that the
data is valid for promotion. After calculation, if the validation account is equal to zero, the
calculation status is updated to OK and the status of the column changes to Pass.
In the journal status column, a green flag indicates that there are no unposted journals. A red flag
indicates that unposted journals must be posted for the entity. However, unposted journals do not
*****************************************************************
Validation accounts are used as a balancing mechanism. You use rules to customize validations
in process management.
For the example in the slide, a validation rule runs only at the legal entity level, which is a
customer-defined level. The user-defined field #1 member attribute is populated with LEGAL to
define and identify the legal entities.
If you are using phased submissions, you can have separate validation accounts for each
submission phase. Financial Management application settings include additional validation
accounts that you can use for each submission phase.
The Validation and Pass/Fail columns are linked to the Validation dialog box so that you can view
additional details about calculation status and validation account information. The Validation
dialog box displays the validation account and its children with balances. The system displays the
following information:
• Calculation status for Entity Currency, Entity Curr Adjs, and Entity Curr Total
• Validation account amount for Entity Currency, Entity Curr Adjs, and Entity Curr Total
To view validation account details:
• Click the check mark or an “x” in the Validation or the Pass/Fail column.
You use the Manage Process commands to move process units through the review cycle.
Process units must have a calculation status of OK, OK SC, or NODATA and a zero balance in
the validation account before you can promote them. Process units with unposted journals can be
promoted.
When you promote parent entity data to the next process level, validation checks are performed to
verify that the child entities are at the level to which you are trying to promote the parent. A parent
can be promoted only to a level that is less than or equal to the lowest level of its children.
To move process units through the review cycle:
1. Select Consolidation, then Data, and then Process Control.
The Data Process Control task is displayed.
2. Select the units and, on the Data Process Control toolbar, click Manage Process, and select
Promote.
submission phase must be less than or equal to the review level of the lower-numbered phases in
that process unit.
For example, you divide Income, Balance Sheet, and Supplemental accounts into three
submission groups. The groups for Income and Balance Sheet accounts are assigned to Phase 1
and the group for Supplemental accounts is assigned to Phase 2.
If the Phase 1 accounts, Balance Sheet and Income, are at Review Level 4, you cannot promote
Phase 2 accounts, Supplemental, to a review level greater than 4. In the same way, you cannot
reject a submission group if it violates the submission phase rule.
The following table describes the commands in the Manage Process menu:
Start Brings data to First Pass. Cells on data entry forms and grids display
NOACCESS until the Review Supervisor starts the process unit.
Promote Promotes process units for all review levels. After a process unit is
promoted for review, data can be viewed only by a user with the
appropriate review-level security role. For example, if the process unit
is promoted to Review Level 2, only a user with the security roles of
Review Level 2 or higher can view the data.
Approve Approves process units. A process unit must have a status of OK, OK
SC, or NODATA to be approved.
Publish Publishes process units after they are approved. When process units
are published, the data is available for viewing by all users with
security access to the data in the process unit.
Sign Off Signs off on process units from Review Level 1 or higher. When a
process unit is signed off, its status does not change.
Reject Rejects process units and demotes them to their previous review level
Available
review levels
When you select Promote from the Manage Process menu, the Promote dialog box is displayed.
You use the Promotion Level list to select the review level. If the entity is a parent, you can also
promote its descendants.
To select review levels:
1. On the Process Control toolbar, click Manage Process, and select Promote.
2. In the Promotion Level list, select a review level.
3. In the Apply Action To list, perform one of the following actions:
- Select Selected Entity Only.
- Select Selected Entity and Descendants.
4. Click OK.
Users at review
level 4
If email alerting is enabled for the process unit scenario, process management triggers email
alerts based on a change of status for the process unit. Alerts are sent for the following actions:
First Pass, Review Levels 1 through 10, Submitted, Approved, and Published. Alerts are not
generated when the process unit is at the Not Started level or for the Sign Off action.
The system automatically generates email alerts to the appropriate users for the action, according
to the review-level assignments. The system sends email alerts to both the users at the level
before the process control action and to the users at the current level after the action.
For example, User A and User B have Reviewer 4 role access, and Users C and D have Reviewer
5 role access. When the process unit is at Level 4 and is promoted to Level 5, Users A and B
receive email alerts because they are at Level 4 before the promote action. Users C and D receive
email alerts because they are at Level 5, which is the current level after the promote action.
• An SMTP mail server must be specified on the Web Server tab of the EPM System
Configurator.
• The alerting process uses the email addresses that are stored in your external authentication
files. To receive email alerts, users must be on either LDAP or Microsoft Active Directory.
• The Supports Process Management-A attribute, which is set in the Metadata Manager, must
be enabled for the process unit scenario.
• The user must have the “Receive Email Alerts from Process Management” role.
• The user must have email alert access to the security class for the process unit entity and
scenario.
The Process Flow History window displays process history by date and time, user, action taken,
process level, and comments. The information cannot be changed or deleted. It is automatically
updated as units are processed by individual users.
To view review history:
1. Select Consolidation, then Data, and then Process Control.
The Data Process Control task is displayed.
2. Select a top member, and select a member list.
3. Right-click an entity, and select Process History.
You can promote, submit, approve, publish, and lock a process unit from a data grid.
Criteria for phased submissions in data grids:
• If a cell is selected in a data grid and Process Management is selected, the system
determines the submission phase that applies to the cell.
• You can have one review status for each submission phase. When cells are promoted, you
promote all cells for that submission phase.
To manage process units in data grids:
1. In a data grid, right-click one or more cells.
2. Select Manage Process.
The Manage Process dialog box is displayed.
3. Under the Action list, select to start, promote, reject, sign off, submit, approve, or publish the
units.
Lock data.
After data for a process unit has been submitted and approved, you can publish it. Only
administrators and review supervisors can modify published data. Optionally, you can lock data.
Locked data cannot be modified by Administrators or Review Supervisors. You must be assigned
the Lock Data security role to lock data.
Note: You can also lock and unlock data for scenarios that do not support Process Management.
You can lock data only if the following conditions are met:
• The calculation status for the entity is OK.
• All prior periods are locked.
• The validation account for the Entity Currency and Entity Currency Adjs members of the
Value dimension is zero.
• If the current scenario is enabled for Process Management, the process unit status is
Published.
Answer: c
Answer: a
Answer: b
Answer: a
Migrating Applications
Synchronizing Data and
0100101100
010010110
01001011
You use data synchronization to transfer data automatically from a source application to a
destination application. Data synchronization provides filters for selecting specific data
needed for other applications. You can schedule data synchronization to run during off-peak
business hours, and you can view data flows between applications after the data is
synchronized.
Note: Data Synchronization is available only for EPMA applications.
For example, you want to transfer data from one application, NA Consol (the source
application), to another, Sales Report (the destination application). NA Consol is the master
application where all the data is stored for consolidations. It contains both balance sheet and
income statement data. Sales Report meets sales reporting needs.
The sales revenue data needed to generate these reports resides in the Net Income hierarchy
in the Account dimension of the NA Consol application. You use data synchronization to
transfer the data from the Net Income hierarchy of the NA Consol application to the Net
Income hierarchy of the Sales Report application.
For the data synchronization to transfer data for a dimension, the dimension member names
in the source and destination applications must match.
If the member names do not match, you must create a mapping table. For example, you could
map data from the Sales member in the source application to the Revenue member in the
target application.
After creating a mapping table, you can insert it into data synchronizations.
To create mapping tables:
1. Select Navigate, then Administer, and then Data Synchronization to display the Data
Synchronizer page.
2. Select File, then New, and then Mapping Table to display Mapping Table Designer.
3. Select the source application, the destination application, and the dimension for which
you want to map data.
4. Click Next.
5. Perform the following actions to set up the mapping for the member:
a. In the source dimension, select the member.
b. In the destination dimension, select the member to which the source dimension
should be mapped.
10. Enter the name and description of the mapping, and click Finish.
Insert Validate
Mapping
Table
You use the New Synchronization Wizard to create data synchronizations. The following is a
high-level overview of the wizard steps:
1. Specify the source type, data source, and destination application.
2. Map source dimensions to destination dimensions.
3. Optional: Create filters for source dimensions.
4. Optional: Insert mapping tables.
5. Save the synchronization.
For each dimension in the source, you specify a matching dimension in the destination
application. For example, you map the ICP dimension in the source to the ICP dimension in
the destination application.
To map dimensions:
• Drag to draw a line from the source dimension to the destination dimension.
A link is displayed as a line connecting the source dimension to the destination
dimension.
By default, data for all dimension members of each dimension is transferred when you
synchronize data. You create filters so that only member data needed in the destination
application is transferred from the source.
For instance, the USSales application needs to receive data from the Reports application.
However, USSales needs data only from the WestSales entity in the Reports application. For
the example in the slide, by applying a filter to the Entity dimension in the Reports application,
you transfer only the data for WestSales.
After you define a filter, you can save it to be reused in other synchronizations.
To create filters:
1. On the Dimension Mapping page, right-click a source dimension and select Add Filter
Criteria to display the Filter Criteria dialog box.
2. In the Filter drop-down list, select one of the following filter criteria:
- Select Equal to filter only the dimension name in the selector field.
- Select Like to filter by pattern matches of partial dimension names.
Tip: Click Save As to save the filter for use in other synchronizations.
5. Click OK.
Note: After the filter is applied to the dimension, a filter icon is inserted next to the
dimension name on the Dimension Mapping page.
To add a saved filter to a source dimension:
1. On the Dimension Mapping page, right-click a source dimension and select Insert Filter
Definition.
The Insert Filter Definition dialog box is displayed.
The last step before validating data synchronizations is to insert mapping tables for those
applications whose dimension member names differ.
Data synchronization tables display two types of lines that link from the source to the
destination:
• A dashed line represents an inserted mapping table.
• A solid line represents linked dimension members without inserted mapping tables.
To insert mapping tables:
1. On the Data Synchronization toolbar, click Insert Mapping Table.
2. From the list of mapped tables, select the mapped table and click OK.
Save
After creating filters and inserting mapping tables, you save the data synchronization.
To save data synchronizations:
1. On the Data Synchronization toolbar, click Save.
The Save Data Synchronization page is displayed.
2. Enter the name and description of the synchronization, and click OK.
3. Select Navigate, then Administer, and then Data Synchronization.
4. On the toolbar, click Refresh.
The synchronization is displayed on the Data Synchronizer task.
When you validate synchronizations, the data is retrieved from the source application and
transformed according to mapping rules. Because the data is not written to the destination
application, you can quickly identify issues and fix them.
To validate data synchronizations:
1. In Workspace, select Navigate, then Administer, and then Data Synchronization.
The Data Synchronizer task is displayed.
2. Right-click a synchronization, and select Validate.
The Data Sync Validation Options dialog box is displayed.
3. Optional: Define a calculation to perform on the data.
a. In the Operator text box, enter a standard mathematical operator.
b. In the Value text box, enter a numeric value.
4. Select data load options.
5. Click OK.
When you execute synchronizations, the data is retrieved from the source application,
transformed according to mapping rules, and pushed to the destination application. You can
specify a calculation to apply to the data being transferred. For example, if you are
transferring data from Actual to Budget, you could specify that the values should be increased
by 10%.
To execute synchronizations:
1. In Workspace, select Navigate, then Administer, and then Data Synchronization.
The Data Synchronizer task is displayed.
2. Right-click a synchronization, and select Validate.
The Data Sync Execution Options dialog box is displayed.
3. Optional: Define a calculation to perform on the data.
a. In the Operator box, enter a standard mathematical operator.
b. In the Value box, enter a numeric value.
4. Click OK.
After setting up data synchronizations between applications, you can view the applications
graphically to show data flow from the source application to the destination application or from
the destination application to the source application.
• The Source Applications label is displayed in a rectangular box whose right side points
toward the destination application.
• The Destination Applications label is displayed in a similar box, only the arrow on the left
points toward the destination application.
To view data flows:
1. Select Navigate, then Administer, and then Application Library.
2. Right-click an application, and select Data Flow.
After you successfully deploy a Financial Management application in an environment, you can
use Lifecycle Management to migrate the application, repository, or individual artifacts across
product environments and operating systems. Migration is the process of copying all or part of
an application instance from one operating environment to another. For example, you can
migrate an application from development to testing or from testing to production. Artifacts are
individual application or repository items (for example, data grids and data forms, rules, and
journal templates). In addition to migrating the Financial Management application, you can
migrate the Performance Management Architect, Calculation Manager, and Shared Services
artifacts related to your application.
To migrate artifacts:
1. From the Shared Services Console, export the artifacts to a set of migration files. The
migration files are automatically saved in a zip archive file format.
2. Use FTP (or another method) to transfer the zip file to the import/export folder of the
destination environment. (The default location of this folder is
c:\oracle\middleware\user_projects\epmsystem1\import_export.)
3. From the Shared Services Console, import all artifacts or a selected subset of artifacts
into the destination environment.
You can export artifacts created for your application in Performance Management Architect to
files. You can export the local and shared dimensions, application settings, and import
profiles.
To export Performance Management Architect artifacts:
1. From Workspace, select Administer, and then Shared Services Console.
2. Expand Applications Groups, then expand Foundation.
3. Select EPM Architect.
An artifact list for the application is displayed.
4. Select the artifacts to export, or click Select All to export all artifacts.
5. Click Export.
6. In the File System Folder field, enter the name of the folder in which to save the
migration zip file.
7. Click OK.
The Migration Status Report is displayed.
8. Click Refresh and verify that the status is Complete.
You can export Shared Services users, groups, and security role assignments.
Note: Security class assignments are exported from the artifact list of the Financial
Management application, not from Shared Services.
To export user, group, and security role assignments:
1. From Workspace, select Administer, and then Shared Services Console.
2. Expand Applications Groups, then expand Foundation.
3. Select Shared Services. An artifact list is displayed.
4. Expand Native Directory and select the artifacts to export, or click Select All to export
all artifacts.
5. Click Export.
6. In the File System Folder field, enter the name of the folder in which to save the
migration zip file.
7. Click OK. The Migration Status Report is displayed.
8. Click Refresh and verify that the status is Complete.
You can import the entire artifact archive (zip file) or a selected
subset.
Before you import artifacts, you copy the zip file for the artifacts to the import/export folder in
the destination environment. You do not need to extract the contents of the zip file. Zip files
copied to the import/export folder are displayed as icons under the File System folder in
Shared Service Console.
To import all artifacts in the zip file:
1. From Workspace, select Administer, and then Shared Services Console.
2. Expand the File System folder.
3. Right-click the icon for the zip file that you want to import and select Import.
4. At the confirmation prompt, click OK.
The Migration Status Report is displayed.
5. Click Refresh and verify that the status is Complete.
To import selected artifacts from the zip file:
1. From Workspace, select Administer, and then Shared Services Console.
2. Expand the File System folder.
3. Expand the zip file, and then click the icon that displays beneath it.
4. Select the artifacts to import, or click Select All to import all artifacts.
You can export individual artifacts to the file system, edit them,
and import them after editing.
You can export or import individual artifacts to or from the local file system without creating a
zip file. When you export artifacts, they are saved as XML files. You can edit the XML file
before you import it.
To export individual artifacts:
1. From Workspace, select Administer, and then Shared Services Console.
2. Expand Application Groups.
3. Select an application.
An artifact list for the application is displayed.
4. Expand an application area to display the individual artifacts.
5. Right-click an artifact and select Export for Edit.
6. In the File Download dialog box, click Save.
7. Specify the location on the local file system and click Save.
To import individual artifacts:
1. From Workspace, select Administer, and then Shared Services Console.
2. Expand Application Groups, and then expand the application group to which your
Financial Management application is assigned.
Answer: b
Answer: b
One of the following is not a data source type. Identify the odd
one.
a. Hyperion application
b. Hyperion data interface area
c. External source (for example, flat file exported from
general ledger)
Answer: d
Answer: b
Smart View provides the framework to integrate Microsoft Office products with Financial
Management, Planning, Financial Reporting, and Web Analysis information.
With Smart View, you can take advantage of Microsoft Office features such as smart tags and
dynamic data points. To view imported data in Office, all users in an organization must have
Smart View installed on their computers.
• Server-side provider
• Client component
You connect to data sources and access Smart View functionality through ribbon commands
and the Smart View panel.
The Smart View ribbon, which contains commands for common Smart View operations, is
displayed on the Smart View tab and is always present. When you enter ad hoc analysis, the
HFM Ad Hoc tab is also displayed. When you open a Financial Management form in Smart
View, the HFM Ad Hoc tab is replaced by the HFM tab.
From the Smart View panel, you can manage data source connections, access data and task
lists, open Financial Management forms, and create reports.
Name Description
Functions Displays Function Builder or POV Manager, where you can create
and manage functions
Refresh Refreshes data on the current worksheet or all worksheets
Submit Data Saves and submits worksheet data to the data source
Options Displays the Options dialog box, where you can set end-user display
preferences, display options, and cell styles
Help Opens Smart View online Help
Sheet Info Displays general and connection information for the worksheet
You use the Smart View panel to manage data source connections. A connection is a
communication line between users and the data source; the data source can be connected to
or disconnected from the provider server.
You can add, delete, and modify connections for each Excel instance. These connections
have no relationship to worksheets. You can establish multiple connections for each Excel
instance.
Data connections are of two types:
• Shared connections are created by administrators, stored in a central location, and
available to multiple users through the Shared Connections panel.
• Private connections are created by users by saving the shared connections locally or by
entering a URL to a provider that was not configured for shared connections.
Use the Options dialog box to specify the following Smart View options:
• Member options control how dimension members are displayed in forms, including
instructions for setting the defaults for member name display, indentation, zooming, and
ancestor position.
• Data options control how data cells are displayed, including how certain Financial
Management row data is suppressed and how missing or invalid data is displayed on
data form.
• Advanced options control the global options for mouse operations, mode, undo and
redo operations, most recently used connections, and Smart View function refresh. They
can also control administrative tasks, including log messaging, shared connections URL,
and UI specifications.
• Formatting options control how numbers are formatted in forms.
• Cell Styles modify default styles in Smart View by changing cell styles to different fonts,
background colors, or border colors. You can also link cells to more than one style, and
you can specify the order in which styles are applied to such cells.
• Extensions options check for upgrades to extensions and enable logging.
After you connect to your Financial Management data source and application, you can use
Ad Hoc Analysis to view and analyze your data.
To open Ad Hoc Analysis, right-click the application and select “Ad hoc analysis.” The HFM
Ad Hoc ribbon is displayed with a default grid layout specific to the Financial Management
data source. When working with data, you can use the default grid, or you can update the
columns and rows with other dimension members. To update the columns and rows, select
Member Selection in the Analysis section of the ribbon.
The default ad hoc grid displays accounts in the rows and periods in the columns. The
remaining dimensions default to the first member of the dimension.
By default, cells are formatted with the same color scheme as data grids in the web client. For
example, cells with modified data are yellow, and invalid cells are orange. You can customize
cell formatting in the Options dialog box, which you access from the Smart View ribbon.
You can drill into (also known as zoom in and zoom out) various levels of data in the grid by
expanding the members. For example, if you want to view data for a specific quarter or month
rather than for the whole year, you can drill into the [Year] member to see more detailed data.
When you drill into a member, it is expanded based on the options specified in the Options
dialog box. If you drill into all levels, the grid displays all descendants of the selected member.
For the example in the slide, UnitedStates.California was expanded (Zoom In) to display its
children: California.1000, California.Plant1, California.WestSales, and California.WestAdmin.
To drill into dimension hierarchies:
1. Select a member.
2. On the HFM Ad Hoc ribbon, click Zoom In or Zoom Out to expand to the next level or to
collapse the current level.
Tip: You can also double-click a dimension member to expand to the next level, to all levels,
or directly to the bottom level.
To pivot dimensions, you can use standard drag-and-drop, or select Pivot in the Ad Hoc
ribbon.
When you pivot between rows and columns, the selected dimension is moved to the
outermost row or column on the opposite axis. In the screenshot, selecting Actual, and then
Pivot on the HFM Ad Hoc ribbon, moves the dimension to the columns.
You can also pivot a dimension from a grid to the POV.
The grid must have at least one dimension on rows and one dimension on columns. Before
removing a dimension from a grid, you must pivot the replacement dimension onto the grid.
To pivot dimensions:
• From the POV to the grid, right-click the member drop-down list and drag it to the grid.
• From the grid to the POV, right-click the member name and drag it to the POV.
• From rows to columns, select a member, and on the HFM Ad Hoc ribbon, click Pivot.
You can use the POV toolbar to change the POV settings for a grid.
In a worksheet, if you want to save changes that you made to the POV settings, refresh the
worksheet before you save it.
To change the point of view:
1. Click the dimension drop-down list and select the member. If the member is not shown,
perform steps 2 through 4.
2. Click the ellipsis (the three dots) to open the Member Selection dialog box.
3. Select (add) the desired members for all dimensions and click OK.
4. Repeat step 1 to change the member.
To change members, or change members in a grid, use the Member Selection dialog box.
To change members:
1. On the HFM Ad Hoc ribbon, click Member Selection to display the Member Selection
dialog box.
2. From the Dimension drop-down list, select a dimension.
3. Optional: Perform one of the following actions to set up filtering:
- From the Filters drop-down list, select a filter.
- For advanced filtering, select a member but do not select its check box, and then
select a filter from the Filter drop-down list. The highlighted member is used as the
filter parameter. For example, if you highlight Quarter1 and select Children from
the Filter List drop-down list, only the children of Quarter1 are displayed.
4. Perform one or both of the following actions:
- Enter a member name in the member name box, and click Find Next to find a
specific member.
- Select one or more members, and click Add to add the members to the Selection
list.
7. Click OK.
If a worksheet cell contains cell text, you can view it in a grid. Cells that contain text are
indicated by dark blue borders.
The example in the slide displays an explanation for the higher salary expense, for the
California entity. The explanation is that expenses are higher due to new hires.
To display cell text:
• Select a cell, and on the HFM Ad Hoc ribbon, click Cell Comments.
Free-form worksheets enable you to quickly create ad hoc analysis by entering member
labels on the worksheet. This free-form mode is especially useful when you are familiar with
the dimensions and members in the application. When you construct an analysis, Smart View
queries the connected data source, interprets the member names that you entered, and
creates a view based on the location of the labels.
Note: After you have an active connection, double-clicking a worksheet displays the default
view.
The layout for free-form entry requires you to enter the member labels for the row dimensions
to the left and one row below the member labels for the column dimensions. When you select
Refresh from the HFM Ad Hoc ribbon, the data is retrieved from the database.
The following are some guidelines for creating free-form worksheets:
• You cannot place members from the same dimension on both the rows and the
columns.
• You must precede all member names that consist of numbers with a single quotation
mark.
• You can apply cell styles in free-form mode.
• You must have an active connection in your worksheet before you can view data.
You can add Excel formulas and formatting to data cells. For example, you can add a formula
that calculates the values for the Budget column based on the values of the Actual column
plus a percentage. Or you can format data cells to display a currency symbol or to display
negative numbers in red. When you submit data, the values calculated by formulas are saved
to the database.
Formulas are automatically preserved, even when you perform the following actions:
• Refresh the ad hoc grid.
• Zoom in or zoom out (referential formulas are updated with their new relative positions).
• Use the Keep Only or Remove Only function.
Formulas are not preserved if you change the grid by any of the following actions:
• Pivot data (for example, by selecting Pivot to POV or Pivot to Column)
• Clear the grid
Rows and columns that you insert in the grid are preserved. For example, you can insert a
column for rates and enter salary rates. In the Salaries row, you can calculate salary
increases by adding an Excel formula to reference the values in the rates column.
To preserve formatting of data cells, you must apply the Preserve Format option to the cells.
Formatting applied to cells other than data cells is not preserved. For example, formatting
applied to row and column heading cells is not preserved.
FDM EE
General Ledgers
E-Business
Suite
E-Business Data .
Data Data
Suite
Adapter Smart
When you load data into Financial Management from an ERP System (Oracle E-Business
Suite General Ledger or PeopleSoft General Ledger) with Financial Data Quality
Management Enterprise Edition (FDM EE), you can drill through the Financial Management
application to view detailed data.
When you drill through FDM EE, a landing page displays general ledger accounts and the
hyperlinked balances that were used to populate the cells in the Financial Management
application. When you click a hyperlinked data value, you can drill through to the ERP source
system and view the associated journal entries for the selected general ledger account.
For more information about configuring Financial Management in FDM EE, see the Oracle®
Hyperion Financial Data Quality Management Enterprise Edition 11.1.2.3 Administrator’s
Guide.
Oracle Hyperion Financial Management 11.1.2: Create & Manage Applications 25 - <#>
To drill through to FDM EE:
1. In Smart View, select a cell that is configured for drill-through.
2. On the HFM Ad Hoc ribbon, click Drill-Through to display a list of reports that are
associated with the cell.
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
GBP
You can use the Calculate and Consolidate options on the HFM Ad Hoc ribbon to calculate,
translate, and consolidate data in Smart View. These features work the same way in Smart
View as they do in Financial Management. You can also view calculation or process
management status. In Smart View, use the Refresh option to ensure that you are looking at
the latest data.
To view the calculation or process management status:
1. On the Smart View ribbon, click Options to display the Options dialog box.
2. In the left panel, select Data Options. In the Mode section, click the Cell Display
drop-down list and select Calculation Status or Process Management.
3. Click OK.
4. If a grid or form is open, click Refresh.
You can adjust values in cells by increasing or decreasing numeric values or percentages.
You can adjust data for multiple cells at one time if all writable cells are at the same level. For
example, you cannot adjust data for March and Q1 in the same operation (assuming March
and Q1 are both writable).
You cannot adjust data values under the following circumstances:
• For a read-only or null member
• If a dimension member has a #Missing or #NoAccess value
To adjust data values:
1. Open a data form or grid, and select a data cell.
2. On the HFM ribbon, click Adjust.
The Adjust Data dialog box is displayed.
Submit data
back to
You must have the Load Excel Data security role to submit data to Financial Management.
The screenshot shows updated headcount data for May through December that is ready to be
submitted, or saved to the FM application.
To submit data:
1. Open a data form or grid in Smart View.
2. Change the data.
3. On the HFM ribbon, click Submit Data.
Form POV
From the Smart View panel, you can open data grids and forms that were created in the
Financial Management Web client. The Add Line Item Detail functionality is not supported in
grids and forms that are opened in Smart View.
When you open a data form, the point of view defined for the form is displayed along the top
of the worksheet. You can select dimension members for the dimensions that are designated
as Selectable in the data form definition.
Opening a data grid creates an ad hoc analysis that uses the rows, columns. and POV
defined for the grid as the default member selection.
To open data grids and data forms:
1. In Smart View, select an empty worksheet.
2. In the Smart View panel, expand Root.
3. Double-click the grid or form that you want to open.
The data grid or form is displayed in the worksheet.
You can also open linked forms from a form opened in Smart View. For rows that contain
links to forms, the cell text is displayed in red.
3. Perform the same range of functions as you would in the web client, such as calculating
data, adding cell text, and submitting data.
4. Click Close.
Oracle Hyperion Financial Management 11.1.2: Create & Manage Applications 25 - <#>
Quiz
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Answer: b
Answer: a
Answer: b
Answer: b