HFM User's Guide 11.1.2.3
HFM User's Guide 11.1.2.3
User's Guide
Release 11.1.2.3
Documentation Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Chapter 1. About Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Financial Management Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Performance Management Architect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
EPM Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Financial Management Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Scenario Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Year Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Period Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Entity Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Value Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Account Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Intercompany Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
View Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Custom Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
User-Defined Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Chapter 2. Basic Financial Management Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Starting Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Starting Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Starting Financial Management with SiteMinder . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Opening Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Closing Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Setting User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Specifying a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Specifying Default Language for Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Specifying Number Formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Specifying File Extract Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Using Document Manager as the Default Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Setting User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Enabling Multibyte Language Date and Time Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Using Financial Management Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Exiting Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Using Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Setting Point of View Bar Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Selecting Members for the Point of View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Selecting Multiple Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Contents
iii
iv
Contents
Contents
vi
Contents
Contents
vii
viii
Contents
Contents
ix
Contents
Contents
xi
xii
Contents
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
13
14
Documentation Accessibility
In This Chapter
Financial Management Features..........................................................................15
Architecture.................................................................................................16
Performance Management Architect .....................................................................16
EPM Workspace ............................................................................................16
Financial Management Dimensions ......................................................................16
User-Defined Elements ....................................................................................19
15
Pre-built starter kit applications for specific requirements such as Sustainability Reporting,
IFRS, Japan Statutory Reporting
Architecture
Financial Management is designed to operate as a multitier system.
l
The client can be used to create and maintain application profile information and metadata.
On the Web server tier, you access the Web-enabled portions of Financial Management.
The middle tier contains the domain intelligence and connections to the relational database.
The data tier contains the relational database and all Financial Management data and
metadata.
EPM Workspace
Financial Management is available within Oracle Hyperion Enterprise Performance
Management Workspace. For information on tasks performed in EPM Workspace, such as
preferences or features in the Navigate, Favorites, Manage, or Tools menu, see the Oracle
Hyperion Enterprise Performance Management Workspace User's Guide and online help.
16
Dimension members are arranged in hierarchies. Upper-level members are called parent
members, and a member immediately below a parent member is referred to as its child. All
members below a parent are referred to as descendants. The bottom-level hierarchy members
of the hierarchy are called base-level members.
Data is typically entered into base-level members of dimensions and not into parent members.
Values for parent-level members are aggregated from the children of the parent-level members.
In some cases, data for base-level members is calculated.
The following sections describe the system-defined dimensions. For information on setting
dimension attributes, see the Oracle Hyperion Enterprise Performance Management Architect
Administrator's Guide if you are using Oracle Hyperion EPM Architect, or the Oracle Hyperion
Financial Management Administrator's Guide if you are using Financial Management Classic
application administration.
Scenario Dimension
The Scenario dimension represents a set of data, such as Actual, Budget, or Forecast. For example,
the Actual scenario can contain data from a general ledger, reflecting past and current business
operations. The Budget scenario can contain data that reflects the targeted business operations.
The Forecast scenario typically contains data that corresponds to predictions for upcoming
periods. A Legal scenario can contain data calculated according to legal GAAP format and rules.
You can define any number of scenarios for an application and define attributes for Scenario
dimension members, such as the default frequency, the default view, and zero data settings.
Year Dimension
The Year dimension represents the fiscal or calendar year for data. An application can contain
data for more than one year. You specify a year range when you create the application and select
a year from the Year dimension to process data.
Period Dimension
The Period dimension represents time periods, such as quarters and months. It contains time
periods and frequencies by displaying the time periods in a hierarchy. For example, if the Actual
scenario maintains data on a monthly basis, generally 12 periods of data are available for this
scenario in a year. Financial Management supports years, months, and weeks for the period
dimension.
Entity Dimension
The Entity dimension represents the organizational structure of the company, such as the
management and legal reporting structures. Entities can represent divisions, subsidiaries, plants,
regions, countries, legal entities, business units, departments, or any organizational unit. You
can define any number of entities.
17
The Entity dimension is the consolidation dimension of the system. Hierarchies in the Entity
dimension reflect various consolidated views of the data. Various hierarchies can correspond to
geographic consolidation, legal consolidation, or consolidation by activity. All relationships
among individual member components that exist in an organization are stored and maintained
in this dimension. Entities in an organization can be categorized as dependent, base, or parent
entities. Dependent entities are owned by other entities in the organization. Base entities are at
the bottom of the organization structure and do not own other entities. Parent entities contain
one or more dependents that report directly to them.
You define attributes for Entity dimension members, such as the default currency and security
class, and to specify whether the entity allows adjustments and stores intercompany detail.
Value Dimension
The Value dimension represents the different types of values stored in your application, and can
include the input currency, parent currency, adjustments, and consolidation detail such as
proportion, elimination, and contribution detail. For example, the Entity Currency member
stores the value for an entity in its local currency. The Parent Currency member stores the value
for an entity translated to the currency of the parent entity. The Value dimension is useful for
providing an audit trail of the transactions applied to data.
Account Dimension
The Account dimension represents a hierarchy of natural accounts. Accounts store financial
data for entities and scenarios in an application. Each account has a type, such as Revenue or
Expense, that defines its accounting behavior.
You define attributes for Account dimension members, such as the account type, the number
of decimal places to display, and whether the account is a calculated, consolidated, or
intercompany partner account.
Intercompany Dimension
The Intercompany dimension represents all intercompany balances that exist for an account.
This is a reserved dimension that is used in combination with the Account dimension and any
custom dimension. Financial Management can track and eliminate intercompany transaction
details across accounts and entities. You can also run Intercompany Matching reports to view
intercompany transactions.
View Dimension
The View dimension represents various modes of calendar intelligence; such as, Periodic, Yearto-Date, and Quarter-to-Date frequencies. If you set the view to Periodic, the values for each
month are displayed. If you set the view to Year-to-Date or Quarter-to-Date, the cumulative
values for the year or quarter are displayed.
18
Custom Dimensions
Custom dimensions are dimensions associated with accounts. These dimensions enable you to
specify additional details associated with accounts, such as products, markets, channels, balance
sheet movement, or types of elimination. For example, custom dimensions could include
Product Line, Region, Channel, or Customers. A Custom dimension for products associated
with Sales and COGS accounts enables you to track sales and cost detail by product.
User-Defined Elements
Many elements in Financial Management are user-defined. For example, when you create a
journal, you specify a label and description.
User-defined elements, the minimum and maximum length for each element, and additional
restrictions are listed below. The table groups the elements by the modules in which they are
found.
Table 1
Max.
length
Restrictions
Language
20
None
Period label
80
Element
Application Profile
View label
10
View description
40
Period description
40
10
Create Application
Application label
Note: Application labels are not case-sensitive. For example, App1 and APP1 are
considered the same application label.
Application
description
255
User-Defined Elements
19
Element
Min. length
Max.
length
80
Restrictions
Metadata Manager
Member label
Must be unique. The label can contain up to 80 characters including spaces, but
cannot start with a space.
Cannot include these characters:
l
Asterisk ( * )
At sign ( @ )
Comma ( , )
Curly brackets ( { } )
Forward slash ( / )
Minus sign ( - )
Number sign ( # )
Period ( . )
Plus sign ( + )
Semicolon ( ; )
40
Alias label
80
80
Security
Security class
20
Asterisk ( * )
At sign ( @ )
Comma ( , )
Curly brackets ( { } )
Minus sign ( - )
Number sign ( # )
Period ( . )
Plus sign ( + )
Semicolon ( ; )
Slash mark ( / )
Element
Min. length
Max.
length
Restrictions
20
Journals
Journal label
Asterisk ( * )
At sign ( @ )
Comma ( , )
Curly brackets ( { } )
Forward slash ( / )
Minus sign ( - )
Number sign ( # )
Period ( . )
Plus sign ( + )
Semicolon ( ; )
Journal description
255
None
Journal group
30
None
50
None
Must be one of these characters and cannot be used in the file or in the file name:
Load/Extract
Delimiter character
Ampersand (&)
At sign ( @ )
Backslash (\)
Carat ( ^ )
Colon ( : )
Comma ( , )
Dollar sign ( $ )
Line ( | )
Percent sign ( % )
Question mark ( ? )
Semicolon ( ; )
Tilde ( ~ )
Note: You must use the same delimiter character throughout the file. Using different
delimiter characters within the same file causes an error when you load the file.
Data grids
Cell description
1900
None
80
None
User-Defined Elements
21
Element
Min. length
Max.
length
Restrictions
Annotation
255
None
Decimal character
Backslash ( \ )
Forward slash ( / )
Minus sign ( - )
Plus sign ( + )
Documents
Document names
(including folder
and report names)
16
Asterisk ( * )
At sign ( @ )
Backslash ( \ )
Colon ( : )
Comma ( , )
Curly brackets ( { } )
Forward slash ( / )
Line ( | )
Number sign ( # )
Plus sign ( + )
Question mark ( ? )
Semicolon ( ; )
Note: Document names also cannot contain trailing or leading white space.
22
In This Chapter
Starting Financial Management ..........................................................................23
Opening Applications ......................................................................................24
Closing Applications .......................................................................................24
Setting User Preferences ..................................................................................24
Enabling Multibyte Language Date and Time Formats .................................................26
Using Financial Management Help .......................................................................27
Exiting Financial Management ............................................................................27
Using Financial Management .............................................................................27
Ensure that the Web server is started and the Web application server is running in the Services panel.
In your browser, enter the URL for the EPM Workspace Log On page.
Note: The default EPM Workspace URL is http://localhost:port/workspace, where
localhost is the name of the BI+ server and port is the TCP port on which the
application server is listening. For Apache Tomcat, the default port for EPM
Workspace is 19000.
23
In EPM Workspace, select Navigate, then Applications, then Consolidation and select an application.
Opening Applications
An application is a set of dimensions and dimension members that meet a set of analytical or
reporting requirements. For example, you can have an application to report on tax data and a
separate application for sales analysis.
In Financial Management, all data is processed within applications. You can open and work with
multiple applications at one time.
Note: To access an application, you must be assigned as a user of the application.
To open an application, select Navigate, then Applications, then Consolidation, and then select
an application.
Closing Applications
You can close the current application in which you are working, or if you have multiple
applications open, close them all simultaneously.
Click the X on the top of the tab in which the application is open.
24
When you make any change in a user preference, you must log off and log back in for the change
to take effect.
See these procedures:
l
Specifying a Cluster
You can specify an Financial Management application as your startup application. From the
General Preferences in EPM Workspace, you can select an Application, and when you log off
and log back into EPM Workspace, the Financial Management application that you selected
opens automatically.
The server cluster that is displayed is based on the cluster that was used at logon. You can select
a different cluster.
25
From the Workspace, select File, then Preferences, and then Consolidation.
and the cluster based on the Web Server and cluster that you used at logon.
Optional: To change the server cluster, from the dropdown list, select a cluster.
From Default Language for Descriptions, select the language to use for descriptions.
Note: The languages are listed in alphabetical order.
For Thousands Separator Character, enter one character to use to separate thousands.
Optional: To set the application to open with Document Manager, select Use Document Manager as
the default page.
The preferences are saved to the database for the current application.
Tip: To reset the settings to the default values, click Reset.
10 Click OK.
11 Log off, and log on again for the changes to take effect.
26
Note: The system language files should be installed on both the browser machine and the Web
From the Control Panel, select Regional and Language Options and select the Languages tab.
In the Supplemental Language support section, make sure these options are selected:
Install files for complex script and right-to-left languages (including Thai)
If the required type is not checked, select it and click Apply. The system files will be installed. You may
then need to reboot your machine.
To log off from a Financial Management Web page, select File, and then Log Off , or click
Log Off from the top menu and click Yes to confirm that you want to log off. The system
returns you to the Logon dialog box, so that you can log on again if necessary.
27
throughout the application session. When you exit the application, the point of view is saved
and can be used the next time that you open the application.
You can set options for displaying dimensions in the POV bar. You can display dimension long
names (such as Scenario or Year), dimension short names (such as S for Scenario or Y for Year),
or select not to display dimension names. You can display dimension labels, descriptions, and
icons, and wrap the POV. You can show, hide, or reorder dimensions.
When you select these POV bar options in one module, they are saved and applied to other
modules: Show Dimension long names, Show Dimension short names, Do not show Dimension
names, Show Label, Show Description, Show Dimension icons, and Wrap POV. For example,
if you select to show dimension long names in data grids, the POV displays dimension long
names when you open a journal. If you close and reopen the application, the settings persist.
Open an application.
From the Point of View bar, click the POV options icon at the right side of the bar and select options:
l
Show Label
Show Description
Wrap POV
POV Details, view the dimension member names and descriptions, and click OK.
Reorder Dimensions, select dimensions, use the up and down arrows to change the
dimension order, and click OK.
28
Open an application, and from the Point of View bar, click a dimension.
From the Member Selection dialog box, select a member from the dimension list, and click the Add
Selection right arrow to move it to the selected members list.
Tip: To remove members from the selected members list, select one or more members and
click the Remove Selection left arrow, or select the Down arrow and Remove All.
Optional: To filter the list, click the Filter down arrow and select a top member.
Tip: To reset the list and view all members, click Reset.
Optional: To move a selected member up or down in the selected members list, highlight the member
and click the Up or Down arrows.
29
Optional: To expand or collapse the dimension members, from the Selector Options down arrow, select
Expand All, or Collapse All.
From the Member Selection dialog box, use one of these methods:
l
Select members and click the Add Selection right arrow to move them to the selected
members list
Click the Add Selection down arrow and select a list to move to the selected members
list.
Tip: To remove members from the selected members list, select one or more members and
click the Remove Selection left arrow, or select the Down arrow and Remove All.
Optional: To filter the list, click the Filter down arrow and select a top member.
Tip: To reset the list and view all members, click Reset.
Optional: To move a selected member up or down in the selected members list, highlight the member
and click the Up or Down arrows.
30
Optional: To expand or collapse the dimension members, from the Selector Options down arrow, select
Expand All, or Collapse All.
From the Member Selection page, click the Favorite Members tab.
click the Remove Selection left arrow, or select the Down arrow and Remove All.
Click the Shuttle Right arrow to move the selected members to the Favorite Members tab and click
OK.
From the Member Selector, right-click on a member in the left pane, then select Member
Properties.
From the Member Selector, right-click on a member in the Selected Members tab, then select
Member Properties.
31
From the Member Selector, right-click on a member in the Favorite Members tab, then
select Member Properties.
From a data form, data grid, journal, or Process Management page, right-click on a member,
then select Member Properties.
Click OK.
Optional: From the Member Selection dialog box, click Enable/disable filter selection on the text for
the search criteria.
32
Click Find Down to display the next dimension member that contains the search criteria you entered.
Continue until you find the appropriate dimension member, or click Find Up to view a previous member.
When you find and select a member, click Shuttle Right to move it to the selected members list.
Click OK.
Displaying Columns
You can specify which columns to display on Financial Management pages. You can also expand
or collapse, and reorder columns.
Selecting Columns
You can specify which columns to display on a page, or display all available columns. For
example, on the Manage Journals page, you can select to display any or all of these columns:
Label, Description, Short Description, Status, Group, Type, Balance Type, Created By, Created
On, Approved By, Date Approved, Posted By, Date Posted, Entity, Parent, and Security.
To select columns:
1
From the menu at the top of the page, select View, and then Columns.
Select the columns to display, or to display all columns, click Show All.
Reordering Columns
You can reorder the columns on a page.
To reorder columns:
1
From the menu at the top of the page, select View, and then Reorder Columns.
From the Visible Columns list, select one or more columns and use the Up and Down arrows to move
them up or down in the column display order.
Click OK.
Using Filters
You can use filters to define and view a subset of tasks or documents to which you have security
access. For example, on the Manage Journals page, you can filter the list of journals by Entity,
Group, Label, Description, Journal Types, Balance Types, or Status.
You can expand, collapse, or resize the Filters pane to show or hide filter criteria.
33
To filter data:
1
, next to a category.
Tip: To remove filter criteria and display all items, click the Reset Filter button
Managing Documents
The Document Manager provides a central location from which you can manage documents in
applications. From the Document Manager, you can work with task lists, data grids, data forms,
system reports, links, related content, and custom documents.
From the Document Manager, you can perform these document tasks:
l
Create
Open
Edit
Load
Extract
Add to Favorites
Delete
Create folders
You can create public documents that can be shared with other users, or private documents,
which are displayed in the Documents list of the user who created them.
You can integrate external documents such as custom documents, related content, and links
into applications.
34
You can filter the list of documents using criteria such as Document Type, Document File Type,
or Document Category. Document Category is only available to users with Administrative
security rights. If the Show Other Users' Private Documents option is selected, the
administrator can see other users' documents in the Manage Documents page, but not in the
Filters pane.
You can expand, collapse, or resize the Documents pane on the left to display the list of
documents.
To access the Document Manager, select Navigate, then Applications, and then
Consolidation, and open an application. If the Document Manager is not displayed by default,
select Consolidation, and then Documents.
Opening Documents
From the Manage Documents page, you can open one or multiple documents using any of these
methods:
To open documents:
l
Select a document from the Manage Documents list and click Open Selected Document.
Select a document from the Manage Documents list and select Actions, and then Open.
From the Manage Documents list, double-click a document name to open it.
From the Documents pane on the left, double-click a document name to open it.
From the Documents pane on the left, select a document, right-click and select Open.
Saving Documents
When you save a document, by default the system uses the Root folder. You can change the
location in which to save the document, and specify whether it should be a private document.
Private documents are only displayed in the Documents list of the user who created them.
To save a document:
1
Optional: Select a security class for the document or use the Default security class.
35
Click Save.
From the Document Manager, click New, and then Folder, or select Actions, then New, and then
Folder.
From Security Class, select the security class to assign to the folder, or use the Default security class.
Note: Users of this folder must have access rights to the specified security class. This option
is only available if you have ALL access to at least one security class.
For Content Type, select the type of documents for the folder.
Tip: If the folder will be used for all documents, select All.
Click Create.
36
To view document folders, select Consolidation and then Documents and view the document
folders in the list.
To expand or collapse the Documents list, click the plus (+) or minus (-) signs next to folders,
or right-click and select Expand All Below, Collapse, or Collapse All Below.
Loading Documents
You can load these types of documents:
l
Data forms
Data grids
Task lists
Reports
Links
Related Content
Custom documents
When the Path is selected in the Default section of the Load Documents page, the system displays
a list of folders that exist in the system to which you can load documents. You can browse to
select a folder from which to load documents.
When you change the default load options, the options are updated for all the rows unless you
have a file selected. If you select the Override Security Class option for a specific row, the security
class for that row is not updated when you change the default security class. You can change the
current document path in the default load section or each row independently.
Note: You cannot load a custom document in Override mode with the same name as an already
loaded document with a security access to which you do not have access.
When the load process is complete, a link displays for the log so that you can view any errors.
To load documents
1
Select Consolidation, then Load, and then Documents, or from the Document Manager toolbar, click
Load Documents.
From the Document Type list, select the type of documents to load.
For Security Class, select a document security class or use the Default security class.
Optional: To override the security class specified in the file being loaded, select Override Security
Class, then select the security class from Security Class.
For File Name, enter the document file name or click Browse to locate the file.
37
The system adds rows that you can use to load additional documents.
Tip: To delete rows, select the rows and click Delete.
Click Load.
From the Document Manager, click New, then Link, or select Actions, then New, and then Link.
To display the page within the current page, select Tasklist opens link within same page.
Note: If you do not select this option, the page opens in a separate browser window.
Optional: Select Prompt user before opening link so that the system prompts you with a confirmation
dialog box before opening the page.
Optional: Select Include Single Sign On information in page request so that the single sign-on
information is posted back to the page.
To save the link, click Save, enter the information, and click Save.
Copy the link text from the dialog and use it to create a bookmark in the browser.
Use this bookmark to open Oracle Hyperion Enterprise Performance Management Workspace and view
the document. You will be prompted to log on before the document is opened.
38
Set up a link to the related content resource server. There is one repository for all Related
Content documents, which is accessed through one URL.
Configure external authentication. If you are not using external authentication, the Related
Content tab is not displayed in Manage Documents.
See the Oracle Enterprise Performance Management System Installation and Configuration
Guide.
Make sure that your administrator has enabled external authentication and that a link is established to
the related content resource server.
From Documents, select New, then Related Content, or Actions, then New, then Related Content.
Note: If external authentication is not enabled, the Related Content tab is not displayed.
For Resource Document, enter the name of the document or click Browse to locate the file.
From Open As, select the format in which to open the document.
39
From Document Manager, click New, and then Task List, or select Actions, then New, and then Task
List.
40
Folder
Task List
Custom Documents
Data Form
Data Grid
Link
Related Content
Reports
Tasks
Optional: To reorder items in a task list, highlight the item to move, and click the Move Task List Item
arrows to move the item up, down, to the top, or to the bottom.
Tip: To remove items from a task list, select the item and click Delete or Delete All.
or greater than signs (< >), single or double quotation marks (', ),
From Security Class, select a security class, or use the Default security class.
Optional: Select Private if you do not want to display this task list to other users.
Optional: To reorder items, highlight the item to move, and click the Move Task List Item arrows to move
the item up, down, to the top, or to the bottom.
41
Click Delete.
Managing Favorites
You can add documents that you use frequently to your list of Favorites. You can view the list
of documents marked as favorites, quickly access them from the Favorites section, or remove
items as favorites.
You can expand, collapse, or resize the Favorites pane to show or hide more Favorites.
Any changes that you make to the Favorites list are saved when you log out of the application.
See these procedures:
l
Adding Favorites
You can add items that you use frequently, such as data forms, data grids, or reports, to the
Favorites section.
After you add favorites, you can view and access them from the Favorites section.
To add favorites:
1
Removing Favorites
You can remove items that you no longer need from your list of Favorites.
42
Managing Data
3
In This Chapter
Creating and loading a data file is an alternative to manually entering data in a data grid. You
create data files in an ASCII format supporting multibyte character sets (MBCS) or a file encoded
with the Unicode format. By default, data files use the DAT file extension. A data file contains
sections that map the file data to dimensions, and can contain these sections:
l
Column Order
View
Data
Description
Sample data files are installed with Financial Management and are located in the
FinancialManagement\SampleApps directory.
43
Table 2
File Section
Description
Column
Order
Specifies the order in which dimension members are displayed. The following syntax specifies the default column order:
!Column_Order = Scenario, Year, Period, View, Entity, Value, Account, ICP, Custom
The default dimension sequence is optional. You can change the column order to meet your needs, and you can specify
multiple Column Order sections in a data file. Each subsequent Column Order section overrides the previously defined
section.
Note: Column order impacts load performance. To maintain optimal performance, first list the Scenario, Year, Entity, and
Period dimensions.
If you do not specify the Scenario, Year, or Period dimensions in the column order sequence, it is assumed that they are
specified in a separate section of the data file. If you do not include the ICP or Custom dimensions in the sequence, they
are assumed to be ICP None, and None respectively.
View
Specifies the default view for all data following it. You can specify multiple View sections in the data file; each section must
start with a valid View dimension. Each subsequent View section overrides the previously defined section. If you do not
specify a View section, the view must be specified in the point of view.
Data
Specifies numeric amounts for valid input cells. If accounts do not accept line item detail, you must load data into them.
The syntax for this section is as follows:
<Scenario>; <Year>; <Period>; <View>;_ <Entity>; <Value>; <Account>; <ICP>;_
<Custom>; <Data>
Note: Zeros are stored as data. Loading zeros into an application is not recommended because zeros can increase the
size of the database and impact performance.
You can specify several Data sections throughout the data file. If you place the Data section before the first Column Order
section, the default column order is used.
Ownership data is used to calculate the ultimate ownership and consolidation percentages for the dependents of the
selected parent.
Ownership information is managed within the ICP dimension by way of a member list called System that is automatically
generated by the system.
For percent consolidation data, you must know an entity members parent in the hierarchy. The parent is required for percent
consolidation data but is ignored in all other circumstances.
Line Item
Detail
You load line item detail to accounts that support line item detail and are valid dimension combinations. A line item is
represented by a delimited pair that consists of a description and a value. You can specify several Line Item Detail sections
throughout the data file. The following syntax specifies a sample point of view, line item detail, and line item value:
!Line_Item_Detail
Actual; 2012; January; Periodic;_ Connecticut; USD; Salaries; [ICP None];_ Golfballs;
Customer2; [None]; Increases;_ John Doe; 5000
You must load line item detail to one period. You cannot load it to a range of periods. The scenarios default view (YTD or
Periodic) determines how the line item detail is loaded.
The line item detail description cannot be blank, but you can leave the line item detail value blank. Descriptions do not
need to be unique. If you do not enter a description and value pair after the point of view settings, an error occurs and you
are prompted to enter a description for the line item detail.
Note: Use only double quotation marks ( ) in line item detail. Single quotation marks ( ) are not supported.
44
Managing Data
File Section
Description
Description
Dimension Groupings
The group dimension section sets the point of view for the load data that is contained in the data
section. For the Period dimension, you can specify one or a range of periods. You must define
one member only for all other dimensions that are specified in the group dimension section.
For example, you could use the following section to specify a range of periods from January to
March:
!Period = January...March
You can specify groupings for dimensions as many times as necessary throughout the data file.
However, they must agree with the respective column order sequence. Each subsequent
occurrence of a grouping overrides the previous grouping.
Note: You can use any of the valid characters as long as the character is not used in the file name
or in any other way in the file. For example, if you are using the ampersand ( & ) in an
entity member name, you cannot use the ampersand as the delimiter character. You must
use the same delimiter character throughout the file. Using different delimiter characters
within the same file causes an error when you load the file.
!Column_Order = Scenario, Year, Period, View, Entity, Value, Account, ICP, Flows,
Market, Region, CostCenter
!DATA
Budget data for six months.
Budget; 2012; July; Periodic; Connecticut; USD; Sales;_
[ICP None]; Flows; Market; Region; CostCenter; 1200000
Budget; 2012; August; Periodic; Connecticut; USD; Sales;_
[ICP None]; Flows; Market; Region]; CostCenter; 1100000
45
Load Methods
These options are available for loading a data file into an application. You select one of these
options for each load process.
l
Merge
Replace
Replace by Security
Accumulate
Merge
Select the Merge option to overwrite the data in the application with the data in the load file.
For each unique point of view that exists in the data file and in the application, the value in the
data file overwrites the data in the application.
Note: If the data load file includes multiple values in the file for the same point of view, the
Replace
Select the Replace option to replace the data in the application with the data in the load file. For
each unique combination of Scenario, Year, Period, Entity, and Value in the data file, the Replace
option clears all account values from the application, then loads the value from the data file.
46
Managing Data
Note: If you have multiple values in the file for the same unique combination of dimensions,
the system loads only the value for the last entry.
If you select the Accumulate Within File option in conjunction with the Replace option, the
system clears the value from the application, adds all values for the same point of view in the
data file, and loads the total.
You can achieve the same result as using the Replace option with the Accumulate Within File
option by using the Database Management module. You can organize the data in the file into
groups based on Scenario, Year, Entity, Value, and Period.
Use the Clear Data tab in the Database Management module to clear each unique combination
of these dimensions, selecting all accounts including system accounts. Enter the data manually
in a data grid, or load or copy the data into the application using the Merge or Accumulate load
options. When you perform the Clear operation for a period in a subcube, data, cell text, and
line item detail are cleared, but cell attachments are not cleared.
Note: You may need to create several small files to load a data file using the Replace mode,
especially if the data is very large or if the file contains ownership data. An error message
is displayed if the file is too large when you try to load it.
Replace by Security
Select the Replace by Security option to perform a data load in Replace mode in which only the
members to which you have access are loaded. This option enables you to perform a data load
in Replace mode even if you do not have access to all accounts. When you perform the Clear
operation for a period in a subcube, only the cells to which you have access are cleared. Data,
cell text, and line item detail are cleared, but cell attachments are not cleared.
Accumulate
Select the Accumulate option to accumulate the data in the application with the data in the load
file. For each unique point of view in the data file, the value from the load file is added to the
value in the application.
Note: Data for system accounts is not accumulated.
Load Methods
47
Load Example
The following example shows how the load options work. Suppose the following data exists in
the application for the Sales and Purchases accounts:
...Sales;... 15
...Purchases;... 10
The following table displays the effect that load mode selections have on data loaded into an
application:
Table 3
Mode
Load Data
Load Mode
Sales
Purchases
Sales
Purchases
Merge
NODATA
10
75
10
Replace or
NODATA
NODATA
75
NODATA
Replace by
Security
48
Managing Data
Mode
Load Data
Load Mode
Sales
Purchases
Sales
Purchases
Accumulate
90
10
N/A
N/A
Loading Data
You can load data using a text file that contains sections that map the file data to dimensions.
When you load multiple data files, they are loaded in sequential order. You should not run
reports, books, or batches while data is being loaded.
Specify the name of the data file to load, and make sure that you set up a directory for the log
file. The log file stores information about the load process; for example, syntax errors and invalid
records.
Oracle recommends that you add Financial Management to the exceptions for your Web popup blocker. When you perform some tasks such as loading data, a status window pops up showing
the task status. If you have a pop-up blocker enabled on your computer, the status window is
not displayed.
To load data:
1
Optional: From Default Load Options, select File Contains Ownership Data if the load file contains
ownership data, such as shares owned.
Caution!
If ownership data is included in the file, you must select this option, or an error
occurs when you load the file.
Optional: Select File Contains Process Management Data if the load file contains data for assignment
of process management submission groups to submission phases.
Optional: Select Accumulate within File to add multiple values for the same cells in the load file before
loading them into the application.
From Delimiter Character, select the default character used to separate the data in the file. These
characters are valid delimiters: , ~ @ # $ % ^ & | : ; ? \
Note: You can use any of the valid characters if that character is not used in the file name
or in any other way in the file. For example, if you use the ampersand ( & ) in an entity
member name, you cannot use the ampersand as the delimiter character.
Loading Data
49
Replace by Security to replace data to which you have access, depending on your security
rights
Accumulate to add data to data in the application
See Load Methods on page 46.
For File Name, enter a file name, or click Browse to locate the file.
Note: By default, data files use the DAT file extension. The load process accepts other file
extensions such as TXT or CSV, however, Oracle recommends that you use the DAT
file extension.
Optional: To override the default load options, select Override, and select different load options for the
file.
Select an action:
l
50
Managing Data
From the Progress page, click Stop Task for the data load.
From the Running Tasks page, select the Data Load task from the Tasks filter, and click
Stop Tasks, or select Actions, and then Stop Tasks.
All data for January (including Phase 2 assignments) is cleared, and the final result is as follows:
Scenario=Actual;Period=January
Actual;January;1;7,8,9
In Merge mode, the new group/phase assignments for the period override the assignments for
the same groups, but keep the assignments for other groups. If an error is detected for a period,
all new assignments for that period are ignored.
After you load a submission group file to an application, users using the application are notified
that the system has changed and that they must log off from the application and log back on.
The load format is as follows:
!SUBMISSION PHASE
<scenario>;<period>;<phase#>;<group assignment>
51
Actual;January;1;ALL
Actual;February;1;1,3,5
Actual;February;2;2,4,6-15
Actual;March;1;1,2,35,7,9
Actual;March;2;8,10-13,15
Actual;March;3;14
Display Name (for cell context menu) and URL (to drill to)
Extracting Data
Use the procedure in this section to extract data as flat files.
Note: You can also extract data to a database. To extract data to a database, you must be assigned
the Administrator security role, and have a previously configured database and universal
data link (UDL) file. See the Extracting Data to a Database section in the Oracle Hyperion
Financial Management Administrator's Guide.
You can extract base-level input data and some types of calculated data from an application.
When you extract data, it is saved to an ASCII file. By default, data files use the .DAT file
extension. After you extract data to a data file, you can view and modify it in a text editor.
When you extract data, you must specify a member for the Scenario and Year dimensions. You
can specify one or more members for the Period, Entity, and Account dimensions.
You can also extract these types of calculated data:
l
52
Base accounts and custom dimension members that are calculated by rules
Parent accounts that intersect with their respective CustomTop member and ICPTop
member. If the CustomTop metadata attribute is blank or ALL, the [None] member is used.
Only valid data intersections are extracted. For each unique point of view, data is presented
in a data line in the file. Group headings are not created.
When you select options for extracting data, you can save the selections as a template. The
template stores the current Type, Extract Format, Point of View, and selected options. When
you select a saved template, the extract options are populated with the default values.
Make sure that you set up a directory for log files and extracted files. The log file stores
information about the process, such as the start and end time of the extract and the number of
extracted records.
Extracting Data
53
SalesIC;CHINA;[None];AllCustom2;[None];[None];100000
If you saved POV dimensions in a template, from Template, select the template. The
Point of View and extract options are populated with the default values from the
template.
If you are not using a template, select the POV dimension members to export.
Calculated Data
Derived Data
Cell Text
54
None
Optional: For Extracted File Prefix, enter a prefix, or use the application name default prefix.
Managing Data
10 Click Extract.
11 From the download box, select Save.
12 Enter a name for the extracted file and make sure that the location for the file is in the directory that
you set up.
Note: By default, data files use the DAT file extension.
13 Click Save.
Copying Data
You can copy data from a specific scenario, year, period, or list of periods to a specific destination
(provided that the destination is not locked). The frequency of the source periods must equal
the frequency of the destination periods. If you copy a list of periods, the number of source
periods must equal the number of destination periods. The source and destination scenarios
must also have the same default frequency. To update values, you must reconsolidate after you
copy the data.
For the Value dimension, you can copy values only from the Entity Currency member, or you
can include system and exchange rate accounts.
You can define a factor by which copied data values are multiplied. Source amounts are
multiplied by the factor before data is copied to the destination. For example, you can increase
data values in one scenario before you copy them to another scenario, such as increasing all
Actual 2011 data values by 15% when you copy them to Forecast 2012. The multiplication factor
that you define is not applied to system accounts.
You must also consider any business rules you created and loaded that may affect the account
data; for example, a rule that can be used to calculate an account in one period but not in another
period.
You can specify how data is copied into an application. You can select to merge, replace, or
accumulate the data. For all Mode options, copy and load data options are the same. See Load
Methods on page 46.
You also specify a log file, which stores information about the copy process, for example, the
start and end times for the copy process and access violations.
To copy data:
1
For Source, select a Scenario, Year, and a Period or range of Periods from which to copy data.
For Destination, select a Scenario, Year, and the same number of Periods to which to copy data.
For Copy Members, select the Account and Entity members from which to copy data.
Copying Data
55
Entity Currency Data to copy the data in the Entity Currency member of the Value
dimension
Rates and System Data to copy data from system and exchange rate accounts
10 Optional: To store the copy information in a log file, select Enable Detailed Logging.
11 Optional: For Multiplier, enter a factor by which to multiply the data that you are copying, such as 1.0.
Note: The factor that you specify is not applied to system accounts.
12 Click Copy.
13 Optional: To view a log of the copy process, click View Log.
metadata.
These rules apply to copying line item detail:
l
56
If the source scenario has line item detail and the destination scenario can accept line item
detail, all details and the corresponding total are copied to the destination scenario.
If the source scenario has line item detail and the destination scenario cannot accept line
item detail, only the total is copied from the source scenario to the destination scenario. No
line item detail is copied to the destination scenario.
If the source scenario does not have line item detail and the destination scenario cannot
accept line item detail, no detail is copied.
If the source scenario does not have line item detail and the destination scenario accepts line
item detail, the total amount is copied from the source to the first line item detail data in
the destination scenario with the description equal to the label of the scenario.
If the source and destination scenario views are the same, Periodic to Periodic or YTD to
YTD, all details and the corresponding total are copied to the destination scenario. The
amount reflects the default view defined for the scenario.
Managing Data
If the source and destination scenario views are not the same, Periodic to YTD or YTD to
Periodic, the line item detail in the destination scenario may not match the total after the
copy operation. Line item detail in the destination scenario only matches the total when you
view the data in the nondefault view of the scenario.
If both the source and destination support intercompany transactions, the system copies
the source amount to the destination. It also copies the corresponding intercompany
transaction details to the destination cell.
If the source supports intercompany transactions but the destination does not, the system
does not copy the transaction.
If the source does not support intercompany transactions but the destination does, the
system does not copy the transaction.
If the destination contains intercompany details, the system does not copy the transaction.
Clearing Data
You can clear data for selected entities and accounts for a specific scenario, year, period, or list
of periods. When you clear data, base and parent entities are cleared. However, only base-level
accounts are cleared. You cannot clear any cells that contain posted intercompany transactions.
Note: You must select only unlocked cells when you clear data, or the clear process does not
complete successfully.
To clear invalid records from the database, you must be an administrator. See the Oracle Hyperion
Financial Management Administrator's Guide.
To clear data:
1
From Source, select a Scenario and Year, and select the Period, Account, and Entity dimension members
to clear.
Entity Currency Data to clear the data in the Entity Currency member of the Value
dimension
Clearing Data
57
Rates and System Data to clear data from system and exchange rate accounts
Optional: To store the clear information in a log file, select Enable Detailed Logging.
Click Clear.
58
Managing Data
4
In This Chapter
59
From the Document Manager, click New, and then Data Grid, or select Actions, then New, and then
Data Grid.
Set the grid rows and columns. See Setting Data Grid Rows and Columns on page 61.
Set the grid display options. See Setting Grid Display Options on page 62.
To open data grids, from the Document Manager, select a data grid and click Open Selected
Document, or select Actions, and then Open.
Calculation Process
Translating Data
Consolidating Data
Locking Data
60
These topics describe the tasks that you can perform for data grids:
l
From the Document Manager, click New, and then Data Grid, or select Actions, then New, and then
Data Grid.
To select the row and column dimensions to display on the grid, drag the dimensions from the top POV
to the rows and columns as needed.
Click the dimensions on the rows, columns, or POV to select members or a member list.
Optional: Select the POV options button to select and change POV options.
Optional: Select the Column options button next to a column, or Row options button next to a row to
select and change column or row options.
Optional: To change the order of row or column dimensions, select the Down arrow next to the Column
options or Row options button, and select Reorder Dimensions. Select the dimensions and use the
arrow keys to change the order, and click OK.
Optional: To view the data grid, click Grid Viewer, or select Actions, and then Grid Viewer.
Tip: To return to the Grid Designer, click Grid Designer, or select Actions, and then Grid
Designer.
Working with Data Grids
61
From Scale, select a scale value, or use the default scale defined for the currency assigned to the entity.
62
Enter a Columns Per Page value, or use the default value of 128.
Enter a Rows Per Page value, or use the default value of 1024.
If the Grid Designer is not displayed, from the toolbar, click Grid Designer, or select
Actions, and then Grid Designer.
Enter dimension names in a comma-separated list in the order in which you want them
to display on the POV bar.
Tip: To view more dimensions without scrolling, click the More... icon at the top left
For Do not display in POV, enter any dimension names that you do not want to display in the POV.
Tip: To view more dimensions without scrolling, click the More... icon at the top left of the
text box.
For Retrieve from User POV, enter dimension names for which you want to use the members from the
background POV.
Tip: To view more dimensions without scrolling, click the More... icon at the top left of the
text box.
63
From Security Class, select the security class for the folder or use the Default security class.
Click Save to overwrite the current grid, or Save As to save the current grid as a new grid.
From the Document Manager, click New, and then Folder, or select Actions, and then New, and then
Folder.
64
From Security Class, select the security class for the folder or use the Default security class.
Note: Users of this folder must have access rights to the specified security class.
Click Create.
From the Document Manager, select the data grid to extract, and click Extract Documents, or select
Actions, and then Extract Documents.
From the download box, click Save, enter a file name, and click Save.
Select Consolidation, then Load, and then Documents, or from the Document Manager, click Load
Documents.
Follow the instructions for loading documents. See Loading Documents on page 37
65
Repeat the steps until you have entered or edited all the necessary data.
66
After entering the data in the parent-level members, you must submit the data to distribute it
among the base periods and to save it to the database.
For blank base periods, when you input data at the summary level, the data is distributed evenly
across the periods. If the base periods contain data, the data is distributed proportionally. For
example, if the months of January, February, and March list 3, 3, and 4 as the existing data, and
you enter 100 in the Quarter1 member, the system distributes 30, 30, and 40 to January, February,
and March, respectively.
Repeat steps 1 through 3 until you have entered or edited all the data.
From a data grid, select a cell or block of cells that contains the data to use for other cells.
available. If only some of the selected cells in the range are editable, the system pastes
the values to those cells only.
Clearing Data
You can clear the values from one cell or from a range of cells. The system clears the selected
input cells only. Cells that are read-only are not cleared.
67
Cell Color
Indication
Light yellow
Data in the cells has been modified but has not yet been saved.
The input status is OK, but the status of the adjustment is not OK (CH, CN or TRN). If the status is CN for node level
adjustments, you must run Force Calculate Contribution to clear up the adjustment member status.
Dark yellow
Impacted (displayed for Process Control and Calculation Status). Indicates that the underlying data has changed. You
should run translation or consolidation.
White
Input - this is an input cell. You can manually enter or edit data.
Orange
Invalid - the cell point of view is an invalid combination of dimension members. You cannot enter data in invalid cells.
Beige
Locked - the cell is locked, and you cannot modify the cell data.
Green
OK - Data has not changed since the last calculation, translation, or consolidation process.
Light green
Light green
ProRata - You may enter data at a summary-level time period and distribute it across base-level time periods based on
existing data.
Dark green
Blue indicator
Cell Text - the cell contains one or more cell text descriptions.
Red indicator
Green indicator
Is Drillable - Data was loaded from a source system and you can drill through from the cell to the source.
You cannot perform any actions on cells in invalid dimension intersections. Invalid dimension
intersections do not accept data entry because the top parents detail members are not used, or
restrictions are set for those dimensions. You can set up restrictions for dimensions when you
set up members in the metadata file. For example, if you set up the Sales account in the metadata
file to accept data entry by customer, the intersection of Sales and None for the Custom
dimension is an invalid intersection for data entry.
To determine the data status, you must check both the calculation status and the process level
of the data. See Viewing Calculation Status on page 69 and Viewing Process Level on page
70.
68
Refreshing Data
You can refresh the data that is displayed in data grids and display the data that is saved in the
database. This enables you to make changes to the data and restore the original data. When you
refresh data, you are prompted to save any changes that you made to the data. You can select
whether to save the changes to the database or restore the data that is saved in the database.
Note: When multiple users are updating data values in the same cells, there is no indication to
users that cell data has been overwritten. If multiple users enter data in the same cell
simultaneously, the database stores the data from the last user who saved data.
Reloading rules
69
Table 5
Calculation Statuses
Status
Description
OK
None of the data for the specified Scenario, Year, Period, Entity, and Value dimensions has changed.
OK ND
OK - No Data. The calculation was run, but calculations were not run for no data.
OK SC
OK - System Changed. A change has occurred that may affect the data for the specified Scenario, Year, Period, Entity, and
Value dimensions. For example, a new rules file, metadata file, or member list file has been loaded, or the currency rate has
changed. The data itself, such as a value of 10,000 has not changed. Rather, some change has taken place, perhaps in a
dimension member attribute. For example, the number of decimals associated with the account was set to two, requiring the
value to be changed to 10,000.00.
CH
Needs Calculation. At least one data cell for the specified Scenario, Year, Period, Entity, and Value dimensions changed, or
metadata parameters or rules have changed. As a result, because calculation was not run, other data cells in this dimension
may not be current. For base-level entities, you may have entered the data cell through data entry or by a data file load. For
any entity, the data cell may have been entered by a journal posting.
CH ND
Needs Calculation - No Data. This indicates the first time that calculation will be performed on the cell.
TR
Needs Translation. The selected Value dimension member is not the entitys default currency, and its translated values may
not be current.
TR ND
Needs Translation - No Data. This indicates the first time that translation will be performed on the cell.
CN
Needs Consolidation. The data for the specified Scenario, Year, Period, Entity, and Value dimensions may not be current
because any of the following items changed:
l
CN ND
Needs Consolidation - No Data. The parent has no data, but data for a child entity changed. This indicates the first time that
consolidation will be performed on the cell.
Locked
The data for the specified Scenario, Year, Period, Entity, and Value dimensions has been locked by an administrator. The data
can no longer be modified manually or through calculations.
Note: You can use the Allocation function to modify data in a locked destination POV.
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.
70
example, whether data needs to be promoted to the next review level, submitted, or approved.
See Process Levels on page 207.
71
To view adjustments:
1
Select the cell for the adjustment member for which to view the history.
The Cell Text dialog box includes the POV information and a grid for cell text. If no text
exists for the cell, the system displays a blank grid.
The system adds a row with the first available cell text as the cell text label.
72
Either accept the label or select one of the other previously loaded labels from the drop-down list.
The cell text labels in the drop-down list are displayed in alphabetical order. You cannot use
the same label twice in the same grid.
Tip: To quickly find a cell text label from a long list, enter one or more letters of the label.
For example, if you enter R, the system quickly advances to the first cell text label starting
with R (Rating in this example). You can then use the up and down arrows to find the
correct label.
On the row next to the [Default] system member label in the Cell Text column, enter the cell text.
Optional: To add cell text rows, click Add, select a Cell Text Label, and enter text.
Click Submit Data to save the data, or Reset Data to refresh the database
Optional: To display the entire cell text in read-only mode, click the Expand button. To return to the
editable cell text box, click the Collapse button.
Optional: To edit cell text in a separate, larger text box, click the Edit button.
Click OK.
73
To include one document attachment for the cell, click the cell with the [Default] cell
text label.
To include multiple document attachments for the cell text label entry, click the icon to
the right of each cell text row to open the Document Attachment dialog, then attach the
document to that cell text row.
From your list of custom documents, select one or more documents to associate with the cell, and click
Attach.
Click OK.
The attachment is displayed in the Attachments section of the Cell Text dialog box.
Tip: To detach a document from a cell, select the document to detach, and click Detach.
Enter line items, and press Enter or select a different cell to see the change.
74
Tip: To clear line item detail, enter zero as the value to clear the amount.
Click Close.
Click OK.
Task
Data Grid
Data Forms
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
No
Yes
75
To run allocations:
1
From a data grid, select the cell for which to run or force equity pickup calculations.
76
Locking Data
You can lock an entity for a period or periods if you do not want users to be able to modify that
data. When data is locked, you cannot change the data for that scenario, year, entity, parent,
value, and period. To lock data, you must be assigned the Lock Data security role.
When you lock data, you only need to select the top parent entity, because the system locks
recursively across the Entity and Value dimensions starting at the base entities. For each entity,
Value members are locked in this order: Entity Currency, None, Parent Currency, Contribution
Total.
You can lock data for a period only if these conditions are met:
l
The entitys calculation status must be OK. See Viewing Calculation Status on page 69.
If process management is enabled for the scenario, the entity must have a process level of
Published. If Process Management is enabled and the cell status is NODATA, you must
promote the process unit before it can be locked. See Process Levels on page 207.
If the entity is a parent, all of its children must also be locked. If you select the top parent,
the system locks all of its children.
The Validation account for the entity currency and entity currency adjustments must be
zero.
To lock data:
1
Unlocking Data
To unlock data, you must be assigned the Unlock Data security role.
To unlock data:
1
From a data grid, select the cell for which to unlock data.
When you unlock data, you only need to select the top parent entity, because the system unlocks
recursively across the Entity and Value dimensions. If you need to unlock specific children under
a parent entity instead of unlocking all the children, an administrator can disable recursive
unlocking using the UseRecursiveUnlock registry setting. See the Oracle Hyperion Financial
Management Administrator's Guide.
Locking Data
77
must have set up your consolidation rules file to store these transactions. The Nature parameter
of the HS.Con function determines whether consolidation transactions are stored. See the Oracle
Hyperion Financial Management Administrator's Guide.
In addition, you must have View or All security access to the destination point of view. The
destination point of view corresponds to the destination cell impacted by the transaction. The
source point of view corresponds to the cell from which the consolidation was run. If you select
a parent member of the Custom dimension or ICP dimension, the system generates all of the
corresponding audit transaction details for all base members of the selected parent.
When you select to view transactions, they open in a new Web browser window. You can then
print the transactions.
From a data grid, select a cell for which to view consolidation transactions.
78
From a data grid, select the cell for which to view entity transaction detail.
79
from the data subcube. The amounts for each transaction detail are stored in the Debit or Credit
column, depending on the sign of the data cell.
The Remarks column contains additional information about the amount. Depending on the
Value dimension, you can have several possible remark comments such as whether the amount
is Input, Calculated, or Derived, or uses the Nature parameter for auditing transactions. It can
also contain information about prior records. One of the main purposes of the Entity Detail
Transaction Report is to show all of the transaction records that made up the amount stored in
the database. Prior LID, Journals, and Transactions remarks indicate that the amount stored in
the database could be from line item details, journal adjustments, consolidation eliminations,
as well as derived data from prior periods.
Table 7
Value Dimension
Remark
Entity Currency
Input
Calculated
Prior LID
Derived
Calculated
Group Label
Prior Journals
Derived
Nature
Prior Transactions
Derived
Adjustments
Proportion/Elimination
From a data grid, select the cell for which to view entity transaction detail.
Select View, then Rows, and then select rows to display, or select Show All.
Select View, then Columns, and then select columns to display, or select Show All.
Optional: To show or hide columns, select View, then Columns, then Manage Columns, and use the
arrow keys to move columns to the Hidden or Visible column lists.
Optional: To reorder columns, select View, then Reorder Columns, use the Up and Down arrows to
reorder the columns and click OK.
80
81
To print reports:
1
From a data grid, select an input cell that has a drillable indicator.
Right-click and select Drill Through to launch a new page with the Point of View for the selected cell,
from which you can drill through to the source data.
82
Note: If you drill through to FDM, the information opens in a new browser window. If you
Information
Start
Promote
Reject
Sign Off
Submit
Approve
Publish
These options are also available from the Process Control module. See Chapter 12, Using
Process Management.
Select a cell in a data grid that is set up for Process Management, right-click and select
Manage Process.
To use the Process Control module, select Consolidation, then Data, and then Process
Control.
83
84
Consolidating Data
5
In This Chapter
Consolidation Process
Consolidation is the process of gathering data from dependent entities and aggregating the data
to parent entities. After you enter or load data into base-level entities, calculate and adjust data,
you run a consolidation for a selected Scenario and Period to aggregate the data throughout the
organization. As data consolidates, the system performs the necessary currency translation and
intercompany eliminations, and equity adjustments or minority ownership calculations if
needed.
Financial Management provides a default consolidation method. To enable statutory
consolidations, you can customize the consolidation process. When you create an application,
you can set the Consolidation Rules attribute. By default, when this setting is not enabled, the
system performs the default consolidation and eliminations. When this setting is enabled, the
system performs consolidation according to the rules written in the Sub Consolidate() routine,
as defined by the administrator. See the Oracle Hyperion Financial Management Administrator's
Guide.
You launch the consolidation process from data grids. Launching consolidation runs the
consolidation rules for the specified scenario, year, period, entity, and value. As part of that
process, consolidation is run for all descendent entities and all prior time periods within the
same year. The consolidation process runs all Calculate functions for each affected entity and
value. The translation process is run as required to convert data from the child entity currency
to the parent entity currency. If the child and parent entity use the same currency, the translation
process is not run.
After you select the parent entity into which the dependent entities consolidate, processes that
are required run automatically.
Consolidation Process
85
The system runs calculation rules for all descendants of the entity.
If the data for the child entity and the data for the parent entity are in different currencies,
the system translates data 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.
You can enter adjustments to data through journals.
The consolidation process begins. If the parent's ownership of the child is less than 100%,
the ownership percentage is applied. The system generates proportion and elimination
detail, and creates contribution data. You can make further adjustments to contribution
data through journals.
At the entity level of the consolidation process, you enter data in input accounts and enter
adjustments through journals in the entity currency. The system runs calculation rules at the
entity level, resulting in adjusted data for the entity.
Following are examples of the consolidation process.
The first example shows the process when the entity currency and the parent currency are
different.
86
Consolidating Data
The following example shows the process when the entity currency and the parent currency are
the same.
Consolidation Process
87
Translation Process
Currency translation converts account data from one currency to another. The data in the local
currency of the dependent entity is translated to the currency of the parent using the local
currency exchange rate.
You can enter currency rates by entity for base entities. If you enter currency rates by entity,
during translation, the system uses the current entity for the direct translation rate. For example,
if the entity currency rate is Euro, and the parent currency rate is USD, the system uses
Rate.Euro.USD in the entity that is being translated. If you do not enter currency rates by entity,
the system derives the direct rate from the indirect rate in the current entity. For example, it
reverses the amount stored in Rate.USD.Euro to obtain Euro/USD.
If the currency rate is not found in the current entity, the system uses the direct rate in the None
entity. If the rate is not found, the system derives the direct rate from the indirect rate in the
88
Consolidating Data
None entity. For example, the system reverses the amount stored in Rate.USD.Euro to obtain
Euro/USD. See the Oracle Hyperion Financial Management Administrator's Guide.
After the translation rule is run, the translated currency dimension is stored. You can make
adjustments to the translated amounts in each currency through journals.
The total of these two levels (Translated and Adjusted data) represents the starting point of the
consolidation process. The translation process does not take place if the entity and the parent
have the same default currency. In this case, the system moves directly to the consolidation
process.
As a dependent entity's values roll up into its parent during consolidation, the system can store
consolidation detail, such as Proportion and Elimination detail. Proportion detail contains the
balances resulting from the execution of consolidation rules. It also reflects the results of the
percent consolidation on the base values. Elimination detail contains any eliminating balances
that result during consolidation based on elimination rules.
The system derives as aggregation the contribution (before adjustment) values. It is still possible
to adjust this data through journals. The system runs calculation rules for adjustments to
contribution after you post the journals.
The total of the contribution data (before adjustments) plus the adjustments represents the
contribution of the base entity to its parent. The system adds the contribution to the
contributions of the other immediate dependents of the parent to obtain the parent consolidated
data. The intermediate contribution level aggregations are not stored during calculation.
However, the parent consolidated data is stored by the system.
Calculation Process
When you calculate data, the system runs calculation rules for the scenario, year, period, entity,
and value that you specify. For example, you can calculate the current months opening balances
by using the prior months closing balances.
Calculation rules for all prior time periods within the same year are also run if they have not
been run previously. Because calculation rules do not consolidate source entities or run
translation, the status (for example, needs translation or consolidation) is not removed from
the cell. Even if the input accounts are not current, calculation uses that data to derive calculated
accounts.
89
You translate currency rates in the From Currency dimension to the currency in the To Currency
dimension.
You enter currency rates in data grids using these point of view grid settings:
l
Table 8
Dimension
Description
Scenario
Year
Period
View
YTD
Entity
Value
Entity Currency
Account
Intercompany Partner
ICP None
From Currency
Source currency
Select the Currencies system member list.
To Currency
Destination currency
Select the Currencies system member list.
90
Consolidating Data
You enter consolidation percentages using this point of view and entering data at the parent
entity cell.
Table 9
Dimension
Description
Scenario
Year
Period
View
YTD
Entity
Parent Entity
Value
None
Account
PCON
ICP
Child Entity
Custom
None
Calculating Data
You can calculate data from data grids or from the Process Control module.
When you calculate data, calculation rules run for the selected scenario, year, period, entity, and
value. In addition, all prior time periods within the same year that were not previously calculated
are calculated. For example, if you calculate data for June, data that was not previously calculated
for January through May is calculated.
You can calculate contribution values rather than parent values. Contribution values are values
added to a parent by a dependent entity. When you select contribution values, this populates
the Value dimension members of the current entity without rolling the contribution total up to
the parent entity. You can also force calculation to run to generate contribution values.
The Calculate option is available only for cells for which data has changed since the cells were
last calculated. You can use the Force Calculate option to calculate cells for which data has not
changed. For example, a cells uses a formula that calculates the current period value based on
the previous period value. If the value for the previous period changes, you can use Force
Calculate to recalculate the current period value.
After you calculate data, the Calculate Data menu option is disabled. If you load or enter new
data or metadata, the Calculate Data menu item is reenabled. If the Calculate Data option is not
enabled, you can use the Force Calculate option to calculate data.
To calculate data:
1
91
To force calculation to run for all selected cells, select Force Calculate.
To force calculation to run for all selected contribution values, select Force Calculate
Contribution.
Translating Data
Currency translation converts account data from one currency to another. You can translate
data from the entity's input currency to any other currency that has been defined in the
application, either during the consolidation process or separately. When you consolidate data,
currency translation occurs if the parent entity has a different default currency than the child
entities. Data in the Entity Currency Total member of the child is translated to the parent's
currency, and the result is stored in the child currency member. You may need to translate to
currencies other than the parent currency. The Value dimension contains members for all
application currencies.
Launching translation runs the default translation rules for the specified scenario, year, period,
entity, and value. As a part of the process, translation rules for all prior time periods within the
same year are also run, if translation for those periods is required (TR status). Because translation
rules do not cause dependent entities to be consolidated, they do not remove the status that
indicates that a cell needs consolidation (CN status). Even if the data for the entity's default
currency is not current, translation uses that data to derive the input accounts for the specified
currency (Value dimension). Subsequently, the translation rules automatically launch the
calculation process so that the calculated accounts are populated for the specified currency.
After you have entered currency rates for the application, you can translate the currency for an
entity to any application currency in the Value dimension.
You translate data and view translation status from data grids or from the Process Control panel.
See Viewing Calculation Status on page 69.
After you translate data, the Translate Data menu command is disabled. If you load new data,
the Translate Data menu option is reenabled. If the Translate Data menu option is not enabled
but you need to run the translation process, you can use the Force Translate menu command.
To translate data:
1
92
Consolidating Data
Note: Translation is run for all cells in the current scenario, year, period, entity, and
value.
l
To force translation to run for all selected cells, select Force Translate.
Consolidation Options
Consolidation is the process of gathering data from dependent entities and aggregating the data
to parent entities. Launching consolidation runs the consolidation process for the specified
scenario, year, period, entity, and value. As a part of that process, consolidation for all descendant
entities and all prior time periods within the same year is run, if it has not been run previously.
The consolidation process runs all calculation rules functions for each affected entity and value,
and the translation process runs as necessary to convert from child entities to parent entities.
The consolidation process does not run translation rules for currencies that are not used in the
process of deriving parent entity data from its children.
These options are available for consolidating data: Consolidate (Impacted), Consolidate All with
Data, and Consolidate All.
Consolidation Options
93
Process units with a status of OK or OK SC on the current period are recalculated, retranslated,
and reconsolidated.
If the selected parent has a status of CN or CN ND in the prior period, consolidation runs for
all periods from the first period in the current year where the parent is impacted until the current
period.
Consolidate All
The Consolidate All option is available for any parent entity, regardless of its status. When you
select this option for a parent entity, the system performs calculations for every process unit
within the consolidation path of the selected parent, regardless of its status. It consolidates all
entities whether they contain data or not. This option is useful when an update from prior periods
is required, or when an entity with no data needs to be populated using allocations. This option
should be used sparingly because the system does not omit entities with no data, which can have
a significant impact on consolidation performance.
Process units with a status of NODATA on the current period are calculated, translated, and
consolidated.
Process units with a status of OK or OK SC on the current period are recalculated, translated,
and reconsolidated.
If the selected parent has a status of CN or CN ND in the prior period, consolidation runs for
all periods from the first period in the current year where the parent is impacted until the current
period.
Consolidating Data
You can run consolidation from data grids or the Process Control pane, or you can use the Task
Automation functionality to automate the process. You can access the consolidation options
from the shortcut menu of any parent entity in a data grid. When you select a parent to
consolidate, 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, the data for the prior period is
also consolidated.
To use the Consolidate option, you must be assigned the Consolidate security role. To use
Consolidate All, you must be assigned the Consolidate All security role. To use Consolidate All
with Data, you must be assigned the Consolidate All with Data security role.
When the consolidation process is complete, the status of each successfully consolidated entity
changes to OK.
Note: If the consolidation process is running for the selected entity, the system displays a warning
94
Consolidating Data
To consolidate data:
1
value.
l
To consolidate all selected entities that contain data, select Consolidate All with Data.
Open a data grid and select a cell for which to run consolidation.
Right-click and select Consolidate, Consolidate All, or Consolidate All with Data.
From the Consolidation Progress page, view the progress for the task that is running.
From the Running Tasks page, select the Consolidation task from the Tasks filter and
click View to view the progress.
Consolidating Data
95
any tasks that you started. Administrators can cancel running tasks by any user to free resources.
See the Oracle Hyperion Financial Management Administrator's Guide.
From the Consolidation Progress page, click Cancel for the consolidation to cancel.
From the Running Tasks page, select the Consolidation task from the Tasks filter, and click
Stop Task.
Consolidation Status
You can view the consolidation status from data grids. The consolidation status of a base level
or parent entity can change as a result of several actions:
l
Reloading rules
96
Consolidating Data
6
In This Chapter
97
You can only enter data on forms for which you have security rights. You can open, view, enter
or edit data, and save data in data forms. Only an administrator with Manage Data Forms security
rights can create, load, and delete forms. See the Oracle Hyperion Financial Management
Administrator's Guide.
From an open form, you can launch and work with the form in Oracle Hyperion Smart View
for Office. For information on using Smart View, see the Oracle Hyperion Smart View for Office
User's Guide.
See these topics:
l
Click Open Selected Document, or select Actions, and then Open, or double-click the form.
Function
New
Save
(disabled in an open form)
Save As
(disabled in an open form)
Open Form
(disabled in an open form)
98
Toolbar Button
Function
Toolbar Button
Designer
Script
Submit Data
Refresh
Calculate
Force Calculate
Suppress Rows
Suppress Columns
Suppress Lines
Cell Text
Instructions
Print
Open in Smart View
From the Document Manager, open a data form. See Opening Data Forms on page 98.
99
made changes to the user POV, they are not reflected in Oracle Hyperion Smart View for
Office.
You can work with the form in Microsoft Excel, save the form, and make changes offline while
not connected to Financial Management. When you connect to Financial Management, you can
send the modified values to Financial Management.
Click Open in Smart View, or select Actions, and then Smart View.
Double-click an input cell to enter data. Input cells are displayed as white cells.
Note: To clear a cell, you can delete its contents, enter NODATA, or right-click and select
Clear.
automatically refreshed after the consolidation process. When the consolidation process
is complete, from the data form, click Refresh to refresh the data in the form. If you choose
to refresh the data in a data form while consolidation is running, you must manually close
the Running Task page.
Table 11
Menu Command
Description
Cell Text
View cell text. See Viewing Cell Text in Data Forms on page 103.
Intercompany
Transactions
View intercompany transactions. See Drilling Through to Intercompany Transactions on page 111.
Linked Form
Cell Information
Force Calculate
For base entity, force calculation to run. See Calculating Data on page 91.
Force Calculate
Contribution
For base entity, force calculate contribution to run. See Calculating Data on page 91.
Consolidate
For parent entity, consolidate entities. See Consolidate (Impacted Consolidation) on page 93.
Calculate
Contribution
For parent entity, calculate contribution. See Calculating Data on page 91.
For parent entity, consolidate every dependent entity within the consolidation path of the selected parent that
contains data, regardless of its status. See Consolidate All with Data on page 93.
Consolidate All
For parent entity, perform calculations for every process unit within the consolidation path of the selected parent,
regardless of its status. See Consolidate All on page 94.
Translate
Translate selected cells. See Translating Data on page 92. (only available if translation is available).
Force Translate
Force translation to run. See Translating Data on page 92. (only available if translation is available).
Lock
Unlock
Manage Process
View process unit status. See Viewing the Process Control Summary on page 215.
Allocate
For base entity, allocate data from a source account to a destination account. See Running Data Allocations on
page 76.
Menu Command
Description
Source Transactions
View source transactions. See Viewing Source and Destination Transactions on page 77.
Destination
Transactions
View destination transactions. See Viewing Source and Destination Transactions on page 77.
Entity Details
View entity details. See Running Entity Detail Reports on page 78.
Cell History
Run EPU
Run the Equity Pickup process. See Calculating Equity Pickup Adjustments on page 131.
Force EPU
Force the Equity Pickup process to run. See Calculating Equity Pickup Adjustments on page 131.
Execute
Run on-demand rules. See Running On-Demand Rules in Data Forms on page 108.
Drill
Drill through to source data through FDM or through ERPI. Only available if you loaded drillable regions for FDM or
ERPI. See Drilling Through to Source Data on page 111.
After you add cell text, a blue triangle is displayed to indicate that there is text associated with
the cell.
Note: You cannot enter text for a cell that is calculated by the form.
If the administrator has set up the form with a cell text column, enter the cell text in the
column.
The Cell Text dialog box includes the POV information and a grid for cell text. If no text
exists for the cell, the system displays a blank grid.
The system adds a row with the [Default] system member as the cell text label.
Either accept the [Default] label or select one of the other previously loaded labels from
the drop-down list.
On the row next to the [Default] system member label in the Cell Text column, enter
the cell text.
The cell text labels in the drop-down list are displayed in alphabetical order. You cannot use
the same label twice in the same grid.
Tip: To quickly find a cell text label from a long list, enter one or more letters of the label.
For example, if you enter R, the system quickly advances to the first cell text label starting
with R (Rating in this example). You can then use the up and down arrows to find the
correct label.
Optional: To add cell text rows, click Add Row, select a Cell Text Label, and enter text.
If the administrator has set up the form with a cell text column, view the cell text in the
column.
Note: The cell point of view is displayed for informational purpose only.
Click OK.
If the administrator has set up the form with a cell text column, edit the cell text in the
column, or click Cell Text to add more text.
The Cell Text dialog box includes the POV information and a grid for cell text. If no text
already exists for the cell, the system displays a blank grid.
The system adds a row with the [Default] system member as the cell text label.
Either accept the [Default] label or select one of the other previously loaded labels from
the drop-down list.
On the row next to the [Default] system member label in the Cell Text column, enter
the cell text.
The cell text labels in the drop-down list are displayed in alphabetical order. You cannot use
the same label twice in the same grid.
Tip: To quickly find a cell text label from a long list, enter one or more letters of the label.
For example, if you enter R, the system quickly advances to the first cell text label starting
with R (Rating in this example). You can then use the up and down arrows to find the
correct label.
Optional: To add cell text rows, click Add Row, select a Cell Text Label, and enter text.
Tip: To delete a row, click Delete Row.
Click Attach.
To include one document attachment for the cell, click the cell with the [Default] cell
text label.
To include multiple document attachments for the cell text label entry, click the icon to
the right of each cell text row to open the Document Attachment dialog, then attach the
document to that cell text row.
From your list of custom documents, select one or more documents to associate with the cell, and click
Attach.
Click OK.
Tip: To detach a document from a cell, select the document to detach, and click Detach.
to delete a row of line item detail. You can also click Clear Row to clear the line item
detail from a row.
triangle at the top of the cell. Cells that contain both cell text and line item detail are
indicated by blue and red triangles at the top of the cell.
From the Document Manager, open a data form and make sure the administrator has set it to display
line item detail for all input periods.
Click Save, close the line item detail page and click Refresh to refresh the data.
From Member Selection, select the dimension member to change and click OK.
Select the cell for which to calculate data and save the data.
Click Calculate.
Click Force Calculate to force calculation to run for each scenario, year, period, value,
parent, entity defined in the grid, regardless of status.
Note: You must submit the data before you calculate.
From the toolbar, click the Execute button and select the rule to run.
Note: This process runs the rule on all valid POVs on the form that are not locked.
Right-click on a cell and from the context menu, select Execute, and then select the rule
to run.
Note: This process runs the rule for only the POVs of the selected cells.
The Execute toolbar button and right-click menu option are not available if the
administrator has not specified any on-demand rules for the form.
Right-click on the cell and select Cell Information to verify the calculation status.
security role. If you are not assigned this role, only the Invalid cells suppression option is
available.
To suppress data:
1
To suppress rows, on the toolbar, click Suppress Rows, and select None, or one or more
of these options: NoData, Zero, or Invalid.
To suppress columns, on the toolbar, click Suppress Columns and select None, or one
or more of these options: NoData, Zero, or Invalid.
To suppress rows and columns, on the toolbar, click Suppress Lines and select None,
or one or more of these options: NoData, Zero, or Invalid.
Tip: Another method of selecting suppression options is to place your cursor over a row
or column header, and right-click to change the row or column. To change both
row and column options, place your cursor in the space at the top left of the form
where the rows and columns intersect, right-click and select an option.
From the Document Manager, open the form into which to enter data.
To add dimension members to the form, in the leftmost header cell of the form, click Add Member,
.
Select the members for which to enter data and click Add.
Tip: To select multiple members, hold Ctrl and select members. Use Add All and Remove
Click OK.
If the administrator has set up the form with a cell text column, enter the cell text in the
column.
Optional: To calculate or force calculate the selected cells, click Calculate and Force Calculate,
respectively.
Note: You must submit the data before you calculate.
The form is automatically refreshed and updated with the newly added entries.
From a data form, select an input cell that has a drillable indicator.
Right-click and select Drill Through to launch a new page with the Point of View for the selected cell,
from which you can drill through to the source data.
Drilling Through to Intercompany Transactions 111
Note: If you drill through to FDM, the information opens in a new browser window. If you
Managing Ownership
7
In This Chapter
Managing Ownership
You can manage ownership and control of an organization by recording the shares of stock that
the entities in the organization own in one another. You can record two types of shares for an
organization: regular shares and voting shares. The system uses regular shares to calculate
ownership, and voting shares to calculate control.
The Manage Ownership grid displays a list of entities according to hierarchy. You can define the
ownership of a parent entity in child entities by assigning system accounts for partial entity
ownership, such as Percent Ownership (POWN system account) and Percent Consolidation
(PCON system account). You can enter share values and specify consolidation methods for the
entities. See Entering Ownership Information on page 115.
You can calculate ownership percentages based on share ownership. See Calculating
Ownership on page 118.
If you assign a holding company to a parent entity, the system first uses the share values to
calculate the ownership and control percentages. It then uses those percentages to propose the
consolidation percentage and method for the entities below that parent.
The following figure shows a sample ownership grid. The rows display the list of child entities
based on the entity that you are using as the parent entity in the point of view. The columns
display system accounts for which you can enter values.
Figure 1
Optional: To display the entity description, from Display Options, select Show Entity Description.
Optional: To show only active entities, from Display Options, select Show Active Only.
Note: This option is available only if the application is set up for Organization by Period. If
Optional: To select the columns to display, select View and select the columns, or select Show All.
Click OK.
System Account
Possible Values
POWN - Percent ownership based on the entitys shares that are owned
by other entities
PCTRL - Percent control based on the entitys voting shares that are
owned by other entities
Note: If the PCON, POWN, PCTRL, and DOWN system accounts do not contain values for
partial ownership, the value is displayed as 100. If you do not enter values for the Consol
1,2, or 3 methods, the method is displayed as zero (0).
Select the scenario, year, period, and entity dimension members from the Point of View for which to
enter ownership information.
Optional: To display the entity currency, select View, then Columns, and select Entity Currency.
From the grid, select entities for which to enter values and take one or more of these actions:
l
For Active, select Yes or No to specify whether the consolidation status of the child into
its parent is active.
To save the changes to the database and refresh the grid, click Submit, or select Actions, and then
Submit.
Tip: To reset the data to the values in the database without saving changes, click Reset, or
If the data type of the source and destination cells does not match (for example, Yes or No
versus a number).
If the value of the source cell is out of valid range for the value of the destination cell (for
example, the source value is -100, and the destination cell is a Consol1 value which has a
range of 0 to 255).
From the Manage Ownership grid, select the cell that contains the value that you want to apply, and
click Copy , or select Actions, then Copy, or right-click and select Copy.
Select the cells to which you want to apply the value, and click Paste, or select Actions, and then
Paste, or right-click and select Paste.
The system applies the current value to all the selected entities.
To save the current values to the database and refresh the data, click Submit, or select Actions, and
then Submit.
Tip: To reset the data to the values that were last saved in the database, click Reset, or select
Percent Ownership
Percent ownership (POWN) represents the percentage of an entitys non-voting shares that other
entities own, directly or indirectly. The system calculates the percentage owned based on the
share values stored in the Shares%Owned account. The calculation result is stored in the parent
in the POWN system account using the ICP dimension. For example, if the calculation returns
90% for Entity A, the system stores 90 in the parent entitys POWN account, ICP=A.
Percent Control
Percent control (PCTRL) represents the percentage of an entity based on voting shares that other
entities own, directly or indirectly. The system calculates the percentage that the selected parents
holding company controls of each dependent, based on the share values stored in the Voting
%Owned account. The calculation result is stored in the parent in the PCTRL system account
using the ICP dimension. For example, if the calculation returns 80% for Entity A, the system
stores 80 in the parent entitys PCTRL account, ICP=A.
For example, if Entity 002 has a value of 80 in the Shares%Owned account, ICP=holding (the
holding company owns 80% of Entity 002), the system stores 80 in the DOWN account , ICP=A
for Entity=Group1.
Percent Consolidation
Percent consolidation (PCON) is the percentage of an entitys values that consolidate to its
parent. The system uses the methods defined in the Consolidation Method metadata table to
determine the percent consolidation to apply for each entity. If there is no consolidation method
assigned to the entity, or the method assigned to the entity does not match a method marked
UsedByCalcRoutine, the system uses the percent consolidation corresponding to the percent
control.
For example, if the Method account Custom1=Global, ICP=001 has a value of 1, and the percent
consolidation in the consolidation method table corresponding to the Global method is 100%,
the system stores 100 in the PCON account, ICP=001.
Consolidation Method
Consolidation method is the set of rules that determine how to consolidate data from an entity
to its parent. The system proposes this method based on the percent control and the
consolidation methods in the Consolidation Method metadata table that have the
UsedbyCalcRoutine attribute. For each entity for which percent control is calculated, the
system assigns the consolidation method corresponding to the percent control for the
consolidation method specified in the table. For example, if the percent control calculated for
Entity A is 75%, and the consolidation method assigns the GLOBAL method when percent
control is from 50% to 100%, the system stores 1 in the parent entitys Method account,
Custom1=GLOBAL, ICP=A.
The exception to this rule is the holding company for the parent. For the holding company, the
system does not use percent control to determine the consolidation method. Instead, it assigns
the consolidation method that has the IsHoldingMethod attribute.
Calculating Ownership
You use the Calculate Ownership option to calculate values for ownership percentages based on
entity shares. You can calculate ownership for multiple parent entities and for multiple periods
for a specific scenario and year. You can run calculation procedures together or separately.
For the Calculate Ownership option to be available, you must assign a holding company to the
parent entity. When you define entity members for the application, you specify the
HoldingCompany attribute for the entity. See the Oracle Hyperion Financial Management
Administrator's Guide.
To calculate ownership:
1
From the POV, select the parent entity for which to calculate ownership.
Note: The parent entity that the calculation process uses is the Entity on the point of view.
For example, if the POV entity is Region.Europe, the calculation runs for Europe, not
Region.
From the right pane, select one or more Calculate Ownership options:
l
To calculate ownership for the current entity only, select Current Entity.
To calculate ownership for the current entity and all parent entities below it, select
Descendants.
To calculate ownership for all entities, select All Entities.
From Periods, select the periods for which to calculate ownership, or select All.
Click Calculate.
8
In This Chapter
H owns 80% of A.
The EPU adjustment impacts both assets and equity in the holding company.
Investments in A: 700 (Debit)
Equity: 700 (Credit)
H owns 80% of A.
A owns 30% of B
Adjustment in A
The EPU calculation path starts with EPU adjustment in A:
l
A owns 30% of B
Investments in A: 80 (Debit)
Equity: 80 (Credit)
After the EPU adjustment is posted in A, and the value of A's equity is adjusted to reflect the
current value of its investment in B, the EPU adjustment related to the investment of H in A can
be calculated.
In this case, the formula to calculate the EPU adjustment is as follows:
Adjustment amount = (Percentage of ownership * Equity of entity owned after EPU
adjustment) Investment at historical cost
l
H owns 80% of A
Example 4: Cross-Ownership
In cases of cross-ownership or circular ownership, EPU adjustments must be calculated
iteratively or through an equation.
Owner Entity, which is the entity that owns a share of the subsidiary
Entity pairs with circular ownership are indicated by a green icon in the Level column.
For each pair, the table also displays the level number corresponding to the order in which they
are processed by the EPU calculation, the percentage of ownership for EPU processing, and
calculation status.
The default point of view contains the default members for the current Scenario, Year, and Period
dimensions. You can change the Point of View.
Optional: To change the default Point of View, click Scenario, Year, and Period, and select dimension
members.
Select row and column options. See Modifying the Display of the Manage Equity Pickup Table on page
130.
Description
Level
Numbers that identify the order in which each entity pair is processed during EPU calculation
Entity pairs with circular ownership are indicated by a circular icon.
Owner
Owned
% EPU
Status
You can display labels, descriptions, or both labels and descriptions, and you can sort each
column in ascending or descending order.
You can filter rows using this criteria: Owner, Owned, %EPU, Circular Ownership, Status, or
Level. The %EPU amounts are positive amounts between 0 and 100, with decimals. You can
include all entity pairs, exclude pairs with circular ownership, or display only pairs with circular
ownership.
From Display Options, for Column Display, select Label, Description, or Both.
f.
For Status, select to display calculations with a status of OK, Impacted, or Both.
g. For Level, select the level range that you want to display.
To calculate EPU:
1
From the Manage Equity Pickup page, click Run EPU or Force EPU, or select Actions, and
then Run EPU, or Actions, and then Force EPU.
From a data grid, data form, or Process Control, right-click and select Run EPU or Force
EPU.
Click Refresh.
Click Full Report or Filtered Report, or select Actions, and then Full Report, or Actions, and then
Filtered Report.
For Report Format, select an option: HFM-Format, PDF, RTF, HTML, XLS, or XLSX.
Click OK.
occurs only if the Owner entity does not own the next pair and if new data was posted to
the Owner entity.
At the end of the calculation process, both the calculation and Equity Pickup status of the entities
should be OK, unless another process changed the entities in the meantime.
Reporting on Financial
Management Data
9
In This Chapter
Creating Reports
You create a report using one of these methods:
l
For details on each report option, see the Defining Reports chapter in the Oracle Hyperion
Financial Management Administrator's Guide.
Opening Reports
You can view the list of available reports by report type or file type, and sort the list by report
name or the date and time last modified. You can open reports from the Manage Documents
list, task lists, or Favorites.
To open reports:
1
From the Filters pane, click the Filter button next to Document Type, and select the report type to open.
BI Publisher report templates offer these report print options: PDF, RTF, HTML, XML, and
XSLX. You can customize these templates in Microsoft Word. For example, by default, the report
displays up to 30 columns. You can customize the template to display more columns. To
customize the templates, you must install and configure Microsoft Office Word and Oracle BI
Publisher Desktop. You can then use BI Publisher to customize templates and update reports.
Note: If you want to retain a customized template when you upgrade or uninstall Financial
Open a report.
HFM-Format
RTF
HTML
XLS
XLSX
If necessary for the report, select Override POV, and click OK.
Editing Reports
You can edit reports that you previously created.
To edit reports:
1
Saving Reports
When you save a report, you can specify a destination folder and security and privacy options.
If you previously saved the report, from the Save As dialog box, you can specify a different
location, security, or privacy options.
The report name can contain a maximum of 20 characters. Do not use double quotation marks
() or an equal sign (=) in the report name.
To save a report:
1
Click Save or Save As, and enter the information for the report.
Click Save.
Printing Reports
You can print reports that you created and saved on the local client computer or the server.
When you select Print, the report is generated based on the report selections.
When you print a report, you can choose to override some or all options available to the report
type. For example, for an Intercompany Matching report, you could select a different partner
entity for the report. If you do not select to override any options, the system uses the option
setting from the report definition. The last overridden option is preserved in a session, so if you
rerun the same or another report, the system displays one or more overridden options from the
time you last printed the report.
To print reports:
1
Click OK.
Click Print.
Deleting Reports
You can delete reports that you no longer need. To delete a report from the server, you must
have All access to the reports security class. Before you delete a report folder, you must first
delete any reports that it contains.
10
Processing Intercompany
Transactions
In This Chapter
Intercompany Transaction Module Features........................................................... 141
Intercompany Transaction Security Roles.............................................................. 142
Sample Intercompany Transactions Task Flow ........................................................ 143
Intercompany Transaction Load Files .................................................................. 144
Loading Intercompany Transactions.................................................................... 147
Extracting Intercompany Transaction Files............................................................. 148
About Managing Intercompany Transactions.......................................................... 148
Creating Intercompany Transactions ................................................................... 149
Viewing Intercompany Transactions .................................................................... 152
Editing Intercompany Transactions ..................................................................... 155
Duplicating Intercompany Transactions................................................................ 155
Assigning Reason Codes to Intercompany Transactions ............................................. 156
Matching Intercompany Transactions .................................................................. 156
Unmatching Intercompany Transactions ............................................................... 166
Posting Intercompany Transactions .................................................................... 167
Unposting Intercompany Transactions ................................................................. 169
Viewing Intercompany Transaction Progress........................................................... 170
Deleting Intercompany Transactions ................................................................... 170
Reporting on Intercompany Transactions .............................................................. 171
Running Intercompany Transaction Reports ........................................................... 171
Running Matching Reports .............................................................................. 174
Drilling Through to Transaction Details................................................................. 178
Email Alerts for Intercompany Transactions ........................................................... 178
Intercompany Sales/Purchases
Intercompany Receivables/Payables
Intercompany Loans/Bonds
The Intercompany Transactions module provides an efficient way to identify, report, and
reconcile intercompany account differences. You can enter, match, post, and verify
intercompany transactions. With the ability to view transaction detail at any time, you can
reconcile intercompany account differences frequently, and thus minimize their impact on the
closing cycle. You can also analyze differences due to real errors in transaction currency or
differences due to exchange rates.
With the Intercompany Transactions module, you can perform these business processes:
l
Match transactions in the transaction currency, and in the reporting or parent currency.
Post transactions.
View an entity partners intercompany transaction details with the entity at any time.
Analyze differences due to real errors in transaction currency or differences due to exchange
rates.
Lock entities and close periods to prevent unauthorized input.
For intercompany administrative tasks, see the Oracle Hyperion Financial Management
Administrator's Guide.
Create transactions.
Edit transactions.
Delete transactions.
To perform matching tasks for transactions, you must be assigned one or more of these security
roles for that task:
l
Task
Description
The administrator defines reason codes in the application to be used for the intercompany matching process.
Users can select from this list when processing intercompany transactions.
Before you can perform any action on intercompany transactions, the administrator must open the transaction
periods. During this process, the administrator also defines the Match/Validate Before Posting requirement
and the matching tolerance to be used for the matching process.
Load transactions
You can load transactions into the system from external ASCII files. You can also enter transactions manually.
Manage transactions
You can view the list of transactions, change the entity and partner selections, and select other filtering criteria
to view transactions.
Edit transaction
You can make changes to a transaction, such as adding comments to the transaction.
You can run a transaction report to view a list of transactions based on the filter criteria.
Before performing the matching process, you can run the matching report to see which transactions are to be
matched.
Auto-match by
transaction ID
You can match transactions using the transaction ID or the reference ID. The system updates the transactions
with a matched status and matched code. You can also save the matching settings to a matching template
to be used later.
Task
Description
This is another option to view the matching transactions report where the transactions are matched based on
the accounts instead of a transaction or invoice.
Auto-match by account
This option is useful to match transactions when the application does not have an exact match of transaction
ID and detail. To avoid a possible mismatch, you can perform auto-matching by ID first, then auto-matching
by account.
After you perform the auto-match process, you might find some transactions that should be matched even
though they do not fit the matching criteria for the process. You can select certain transactions and manually
match the transactions. The matching process updates the matched status and assigns a matched code.
Perform unmatch of
transactions
During the matching process, you might need to unmatch certain groups of transactions manually. When you
select a transaction, the system displays the group of transactions that have the same matched code. You
can then unmatch all transactions within the same matched group.
Post transactions
After all transactions have been matched and you are ready to post the transactions to the system, you can
select the transactions to post.
After you post transactions, you can create a transaction report to view the status of each transaction. This
report contains information on the posting status, and posting user, date and time. This can be used as a
summary report so that you can quickly view the posting information.
Lock entities
The administrator can lock entities to prevent users from adding new transactions or making changes to specific
entities. When the entity is locked, no more matching can done for that entity, and no additional transactions
can be posted for the entity.
After you post transactions and the intercompany accounts reflect the account balance of these transactions,
you can run the Intercompany Matching System Report to view the matching at the account level for individual
transactions.
Drill through to
transaction details from
data grids or data forms
When you are in a data grid or data form, you can view the corresponding intercompany transactions. You
cannot modify transactions from data grids or forms.
Close period
At the end of the closing cycle after you finish processing intercompany transactions, the Intercompany
Administrator closes the period to prevent additional modifications to the transactions for the period. If the
Match/Validate Before Post option is selected for the period, all matched transactions or mismatched
transactions with a reason code must be posted before the period can be closed. When you close a period,
the period is locked for future transactions, however, you can continue to view transactions or run reports on
transactions from the period.
Reason Code table: This section is loaded only if you have Intercompany Transaction
Administrator security role access; otherwise, this section is ignored during the load.
IC Transaction section: This section is used most frequently and is loaded if you have
Intercompany Transaction User security role access.
During the load process, the system also does not load the posting or matching status from the
load file.
Keyword
Description
Intercompany Detail
Column_Order
Thousand_Separator
(Optional). Indicates the delimiter used in the amount to separate the thousands. If this is not specified, the system
uses the regional settings for the numeric value defined in the application server.
Decimal
(Optional). Indicates the character to be used for the decimal amount. If this is not specified, the system uses the
regional settings for the numeric value defined in the application server.
You can use any of the valid characters if that character is not used in the file name or in any
other way in the file. For example, if you use the ampersand ( & ) in an entity member name,
you cannot use the ampersand as the delimiter character. You must use the same delimiter
character throughout the file. Using different delimiter characters within the same file causes an
error when you load the file.
Note: If you are using an Oracle database, the system converts the transaction ID, sub ID,
reference ID, and reason code to upper case during the load process. For example, the
system converts the t123 Transaction ID to T123 during the file load.
Example:
!SCENARIO=Actual
!YEAR=2012
!PERIOD=January
!DECIMAL=.
!THOUSAND_SEPARATOR=,
INTERCOMPANY DETAIL
!
Column_Order=Entity;Partner;Account;Flows;Market;Region;CostCenter;TransID;SubID;Date;Tr
ansCurr;TransAmt;EntCurrAmt;Rate;RefID;Comment1;Comment2
China;France;ICPay;Flows;Market;Region;CostCenter;DE124;08/10/06;EUR;2000;
8000;Ref123;Text1234;Text9995
China;France;ICPurch;Flows;Market;Region;CostCenter;BX3212;08/12/06;EUR;2500;
10000; ;Text2345;Text8984
China;Germany;ICRef;Flows;Market;Region;CostCenter;AC4345;08/15/06;EUR;1700;
6970;ABC12;Text2323;Text9232
...
Load Methods
When you load intercompany transactions, you can select to merge or replace the transactions.
Merge
Select this option to update the records with the new changes and create any new records. The
system does not update any information in records with a Matched or Posted status. The load
log file contains information about any transactions that were not loaded. The Merge mode does
not delete any records in the database.
Table 15
Record 1
N/A
Record 1
Record 2 - Matched
New Record 2
Record 3
N/A
Record 3
Record 4 - Posted
New Record 4
Record 5
New Record 5
New Record 5
N/A
New Record 6
New Record 6
Replace
The Replace mode replaces all the transactions in the database for the specified scenario, year,
period, entity with the transactions specified in the load file. In the Replace mode, the system
first clears all records for the entity for the scenario, year, period. If the system encounters any
intercompany transactions for the entity that have a status of Posted or Matched, it does not
clear those transactions; it skips them and continues with the load process. After clearing all
applicable transactions for the entity, the system replaces all transactions for the entity with the
records from the load file.
146 Processing Intercompany Transactions
Table 16
Record 1
N/A
N/A
Record 2 - Matched
New Record 2
Record 3
N/A
N/A
Record 4 - Posted
New Record 4
Record 5
New Record 5
New Record 5
N/A
New Record 6
New Record 6
From Default Load Options, for Delimiter, select the character to use as the delimiter during the load
process.
For File Name, enter the transaction file to load, or click Browse to navigate to and open the file.
Optional: To load additional files, click Add and select to add 1, 5, or 10 rows.
Click Load.
The scan and load status for each file is displayed in a new page.
From the Point of View bar, select the scenario, year, and period.
Enter the names of the Entity and Partner dimension members, or click Browse to find the Entity and
Partner members.
Matched
Unmatched
Mismatched
Posted
Unposted
From Reason codes, select a reason code, or leave the default option of All.
From Transaction Currency, select a transaction currency for which to extract transactions, or leave the
default option of All.
For Transaction Match Code, enter a match code value, or use the percent sign (%) as a wildcard.
Optional: To extract a list of reason codes defined in your application, select Include list of Reason
Codes.
Click Extract.
10 From the confirmation prompt that the extract was successful, click OK.
11 Click the Download link and select Save.
12 Enter a name for the extracted file and make sure that the location for the file is in the directory that
you set up.
Note: By default, transaction files use the TRN file extension.
13 Click Save.
You can enter intercompany transactions for accounts that have been set up by the administrator
as intercompany accounts. Entities that conduct intercompany transactions with each other are
known as intercompany partners. The administrator identifies the entities that can be
intercompany partners.
The intercompany period must be open before you can enter any intercompany transactions.
After the period is opened, you can manually enter transactions in the application. To create
transactions, you must be assigned the Intercompany Transaction User security role.
The transaction should contain information for only one transaction as related to the entity in
the point of view. The transaction ID and sub ID are used as the key to the transaction detail
record.
Table 17
Transaction Detail
Transaction
Detail
Description
Scenario
Year
Period
Transaction ID
This ID is required. You must enter an ID for the transaction, with a maximum of 40 characters. When combined with
the Sub ID, this ID becomes a unique identifier for the entity/partner/account/C1/C2 within the scenario/year/period
combination.
Transaction
Detail
Transaction Sub
ID
Description
(Optional). You can enter a sub-ID for the transaction, with a maximum of 40 characters. This is useful if you need to
handle one-to-many or many-to-many transactions between two entities. For example, if one transaction in the
originating entitys book corresponds to multiple transactions in the partners book, you can use the Transaction ID for
the common reference and use the Sub ID for the multiple transactions.
Another use for the sub ID is when there is an adjustment needed to adjust the transaction in the Entity Currency instead
of posting a journal adjustment in the Entity Curr Adjs. In this case, you can create a dummy transaction and use the
same Transaction ID from the original invoice, but use the Sub ID to identify as an adjustment by entering ADJ1 in the
sub ID to show that it is an adjustment instead of a real invoice.
Reference ID
(Optional). You can enter a reference ID to store any reference information for the transaction. For example, the entity
might have its own set of invoice numbering that is different from the entity that issued the invoice. You can enter
additional information in this Reference ID text box for information purposes only.
You can also use the reference ID for the partners transaction ID. You can enter the entitys reference ID for the
Transaction ID and enter the corresponding invoice number from the partner entity in this text box.
Transaction
Date
Entity
The entity must be a valid ICP base entity, not a parent entity.
Partner Entity
The partner entity must be a valid ICP entity for the account.
Account
The account must be a valid ICP account and the cell must support transactions as specified in the Rules file. See the
Rules section of the Oracle Hyperion Financial Management Administrator's Guide.
Custom
The custom member must be a valid custom member for the account.
Transaction
Amount
This is the invoice amount in the currency of the transaction. This is required only if the entity currency is not entered.
Transaction
Currency
This is the currency used for the Invoice transaction. It must be a valid currency defined in the application.
Conversion Rate
This is the rate used to convert the transaction currency amount to the local reporting currency amount for the transaction.
During the calculation of the local currency amount, if the operator is Divide, the system uses this formula: Local currency
= transaction currency/rate. If the operator is Multiply, the system uses this formula: Local currency = transaction
currency * rate.
See the Oracle Hyperion Financial Management Administrator's Guide.
Operator
The Multiply or Divide operator depends on the local currency of the transaction. You must first define the Multiply or
Divide operation for a specific currency in the currency table of the application. The default value for the operator is
Divide. See the Oracle Hyperion Financial Management Administrator's Guide.
Entity Currency
Amount
This is the invoice amount in the local entity currency. The currency must be a valid currency defined in the application.
Comment 1
(Optional). You can enter comments for the transaction. You can enter a maximum of 256 characters.
This is required if the transaction amount is not entered. Otherwise, the system can recalculate this information if you
enter the transaction amount and the conversion rate.
Transaction
Detail
Description
Comment 2
(Optional). You can enter additional comments for the transaction. You can enter a maximum of 256 characters.
You can use Comment 2 to enter comments related to the partners transaction. For example, Entity A might enter
comments in Comment 1 related to the transaction. Later, Entity A might run a matching report or view the partners
transaction and realize that there are discrepancies with the partners amount. Entity A can then enter the additional
comments in Comment 2 to state anything related to the information in the partners record. This information is then
part of the transaction and can be included in the matching report for informational or audit trail purposes.
Note that while Comment can be used for partner information, only the entity can enter the information. The partner
entity cannot enter information in the entitys record.
Reason Code
(Optional). The reason code must be a valid one defined by the administrator. The main purpose of the reason code
is to indicate why a transaction has a Mismatched status; for example, because of a missing invoice from the partner
entity, or an incorrect amount entered by the partner. If the transaction has a Matched status, you do not need to assign
a reason code for the transaction. You cannot assign a reason code to a transaction with an Unmatched status.
From the Point of View bar, select a scenario, year, and base period.
From the Edit Intercompany Transaction pane menu bar, select New.
From the New Intercompany Transaction pane, for Transaction ID, enter the transaction or invoice
number.
Optional: For Transaction Sub ID, enter a sub identification for the transaction or invoice.
Optional: For Reference ID, enter reference information for the transaction.
Optional: For Transaction Date, enter a valid date, or click the pop-up calendar to select a date.
For Partner, enter a partner entity or click Pick Members to select a member.
13 For Conversion Rate, enter the rate used to convert the transaction currency amount to the local reporting
currency amount.
Note: If you leave this text box empty and enter the entity currency amount, the system
14 For Entity Currency Amount, enter the invoice amount in the local entity currency, and enter the currency
of the reporting entity.
15 Optional: For Comment 1 and Comment 2, enter comments for the transaction.
Note: You can enter a maximum of 256 characters.
16 To save the transaction, from the top of the Edit Transactions window, click Save, or select Actions and
then Save.
Tip: To reset rows to their default settings, from the top of the Edit Transactions window,
In addition to the transaction detail that you entered, the transactions list displays systemgenerated information about the transaction that cannot be changed manually. For example, it
displays the matching status, posting status, match code, user ID of the last user to modify the
152 Processing Intercompany Transactions
transaction, and the date and time the transaction was last modified. Matched transactions are
indicated by double green boxes, and posted transactions are indicated by a green flag in the
Status column. Mismatched transactions are indicated by a red triangle.
Select View, then Columns, and select the columns, or select Show All.
Optional: To show or hide columns, select View, then Columns, then Manage Columns, and use the
arrow keys to move columns to the Hidden or Visible column lists, and then click OK.
Optional: To reorder columns, select View, then Reorder Columns, and use the arrow keys to reorder
the columns.
Optional: To change the column sort order, click the header icons and select an option:
l
Ascending
Descending
No Sort
To display the dimension label, corresponding description, or both, expand Display Options in the right
pane, then from Dimension Options, select a dimension, and select Label, Description, or Both.
Tip: To reset the settings to the last saved state, click Reset Settings.
filtering with testgroup might return different results than filtering with TestGroup.
a. For Entity, either use the default entity, enter an entity, or click Browse and select a
member.
b. For Partner, either use the default partner entity, enter a partner entity, or click
Browse and select a member.
c. If you select to display Entity Transactions, for Entity Account and Customs, enter an
account, or click Browse and select an account.
d. If you select to display Partner Transactions, for Partner Account and Customs, enter a
partner account, or click Browse and select an account.
e. Optional: Filter rows by ID, or leave blank to display all:
f.
Transaction ID
Transaction Sub ID
Reference ID
Reason Code
Match Code
Transaction Currency
From Include, select one or more options: Matched, Unmatched, Mismatched, Posted, or Unposted.
Expand Display Options, and from Scale Factor, select a value or use the Default value.
From Decimal Override, select a value between 0 and 6, or use the Default value.
For Dimension Options, for the dimensions, select to display Label, Description, or Both.
From the Point of View bar, select a scenario, year, and base period.
To save the changes, from the top of the Edit Intercompany Transactions pane, click Save, or select
Actions and then Save.
From the New Intercompany Transaction pane menu bar, click Duplicate.
To save the changes, from the top of the New Intercompany Transactions pane, click Save, or select
Actions and then Save.
From the list of intercompany transactions, select the transaction or transactions to which to assign a
reason code.
Note: You can assign a reason code only to transactions with the Mismatched status.
Click Set Reason Code, or select Actions, and then Set Reason Code.
From the Reason Code list, select a reason code, and then click OK.
Auto-Match Process
The auto-match process performs the matching only on transactions with a status of Unmatched
or Mismatched. These transactions must also be unposted transactions. When you select the
auto-match process, you can select whether to match transactions by account, or by ID.
You can filter the list to match only transactions with a specific transaction currency.
Transactions that have been previously matched are excluded from the matching process because
a match code has been assigned to those transactions.
After you include transactions in the matching process, the match status of the transactions
becomes Matched or Mismatched. Any mismatched transactions can be included again in the
auto-match process.
When you auto-match intercompany transactions, a progress bar is displayed with the progress
percentage, status, and last update time. You can also view the progress from the Running Tasks
module.
Auto-Match
Performing the auto-match process using the Transaction ID is the most common and accurate
method of matching intercompany transactions. The system performs the auto-match process
by Transaction ID using the current filter selected for Entity/Partner/Transaction ID/
Transaction Currency. If you filter for Reference ID and perform an auto-match, transactions
are matched based on Entity/Partner/Reference ID/ Transaction Currency in the current filter.
You cannot filter both Transaction ID and Reference ID at the same time and perform an automatch
If you want to use a different method of matching, you select the Auto-Match Template option.
See Using Auto-Match Templates on page 161.
You can specify an ID or use wildcards. If the ID is left blank, the system matches all transactions
for the entity and partner.
When matching transactions using the transaction ID or reference ID, the system always uses
the transaction currency. There is no need to specify a tolerance amount because the transactions
are considered Matched only if the amounts match without error. The system assigns a separate
match code to each group of transactions.
If you have transactions with different currencies but the same transaction ID or reference ID,
during the auto-match process, the transactions are matched by currency group. If all the
transactions in all the currency groups are matched, the system assigns one match code to all
the transactions.
Table 18
Transaction ID
Entity
Partner
Currency
T123
EUR
T123
EUR
T123
USD
T123
USD
In this example, if the transactions in EUR are matched and the transactions in USD are matched,
the system assigns one match code for all four transactions. If the transactions in EUR match
but the transactions in USD are not matched, the system considers all of the transactions
Mismatched.
The following table shows the rules for matching transactions using IDs:
Table 19
Matching Process
Entitys Transactions
Partners
Transactions
Match using
Transaction ID
Transaction ID
Transaction ID
Match using
Reference ID
Transaction ID
Reference ID
Reference ID
Transaction ID
Reference ID
Reference ID
Comments
Asset
Liability
Balance
Balance Recurring
Profit/Loss group
l
Revenue
Expense
Flow
For each group of transactions, the system assigns a match status and separate match code. For
example, the Balance Sheet group of transactions could have a Matched status and be assigned
a match code, but the Profit/Loss group of transactions could have a Mismatched status.
Example
In the following example, the intercompany transactions all have the same transaction ID 123:
Entity
Partner
Account
Amount
Account Type
Recltic
100
Asset
Sales
110
Revenue
Payltic
100
Liability
Cog
100
Expense
The system subdivides the transactions into the BS and PL groups as follows:
BS Group
A, B, Recltic, 100, Asset
B, A, Payltic, 100, Liability
Subgroup status: Matched. The system assigned a match code to this group.
PL Group
A, B, Sales, 110, Revenue
B, A, COG, 100, Expense
Subgroup status: Mismatched. No match code is assigned to this group.
Auto-Match by Account
In addition to performing the matching process using the transaction ID, you can match the
transactions based on specific accounts and matching accounts. The system performs the
matching process for the entity and partner that you specify. The transactions to be matched are
grouped by transaction currency during the matching process and are assigned a separate match
code for each currency group.
For each transaction included in the matching process, the system first translates the transaction
currency amount to the application currency, based on the default translation rules set up for
the application. The translated amount is added to the total difference amount. The system
Matching Intercompany Transactions 159
performs the translation for each transaction in the auto-match process and the difference
amount is calculated.
Note: The conversion rate used in translation is the rate that is stored in the Rate account for
To auto-match transactions without using a template, click Auto Match, or select Actions, then Auto
Match, and then select Auto Match.
From the confirmation prompt that you are about to auto-match based on the current filter settings,
click Yes, or click No and change the settings.
Click Refresh to display an updated intercompany transactions list and verify the Matched status.
To auto-match transactions using a template, click Auto Match, or select Actions, then Auto Match,
and then select Auto Match Template.
From the Manage Intercompany tab, click Refresh to display an updated intercompany transactions
list and verify the Matched status.
Click Auto Match or select Actions, and then Auto Match, and then select Auto Match Template.
Select an action:
l
To run the auto-match process using an existing template, from Template, select a
template, and then click Match, or select Actions, and then Match.
To create an auto-match template, continue with the next steps.
From the Point of View bar, select a scenario, year, and base period.
Enter the names of the Entity and Partner dimension members, or click Browse to find the Entity and
Partner members.
Select an option:
l
If you selected Match By ID, select Transaction ID or Reference ID, and enter an ID or use
a wildcard.
If you selected Match By Account, click Add and select the account dimension members
or custom members, and in the Matching Accounts section, click Add and select the
matching account dimension members or custom members.
Tip: To remove accounts or matching accounts, click Delete or Delete All.
Select an action:
To perform the matching process without saving the selection, click Match, or select
Actions, and then Match.
To save the settings as a template, click Save, or select Actions, and then Save.
During the manual match process, the system subdivides all the intercompany transactions with
the same transaction or reference ID into separate groups based on their account type. The entire
group of transactions within the manual match process must be matched before the transactions
can be assigned a Matched status and a match code.
If both subgroups are matched, the system assigns all of the transactions the Matched status and
assigns them one match code. If only one subgroup is matched, but the other is not, all of the
transactions are considered mismatched.
The transactions are grouped by their Balance Sheet or Profit/Loss account type as follows:
Balance Sheet group
l
Asset
Liability
Balance
Balance Recurring
Profit/Loss group
l
Revenue
Expense
Flow
Example
In the following example, the intercompany transactions all have the same transaction ID 123:
Entity
Partner
Account
Amount
Account Type
Recltic
100
Asset
Sales
110
Revenue
Payltic
100
Liability
Cog
100
Expense
The system subdivides the transactions into the BS and PL groups as follows:
BS Group
A, B, Recltic, 100, Asset
B, A, Payltic, 100, Liability
Subgroup status: Matched.
PL Group
A, B, Sales, 110, Revenue
B, A, COG, 100, Expense
Subgroup status: Mismatched.
Matching Intercompany Transactions 163
The result is that because only one subgroup is matched and the other is not, the system considers
all transactions mismatched, and assigns all transactions in this manual match process a
Mismatched status and no match code.
From the transactions list, select the transactions that you want to match.
Matching Status
Intercompany transactions can have one of these matching statuses: Unmatched, Matched, or
Mismatched. The matching status is updated by the system and cannot be changed manually.
When you create or load a transaction, it has a default status of Unmatched. If the transaction
is included in the auto-match process, the transaction is updated to Matched or Mismatched
status. The Mismatched status means that the matching process has been done for the transaction
but it was not matched, or was not within the matching tolerance level as defined for the
application. You can resolve this by rerunning the auto-match process or by manually matching.
See Auto-Matching Intercompany Transactions on page 160 and Manually Matching
Transactions with Tolerance Amount on page 162.
Changes from Unmatched to Matched or Mismatched
During the auto-match or manual process, unmatched transactions can be changed to Matched
or Mismatched status.
Changes from Mismatched to Unmatched
If a transaction has gone through the auto-match process and has a status of Mismatched, any
changes to the transaction (with the exception of the comments and reason code) change the
status to Unmatched. This applies to both manual entry and loading transactions.
Changes from Matched to Unmatched
Since the system does not allow changes to matched transactions except for comments and
reason code, you cannot change the matched status by manual entry or loading transactions.
However, you can perform the Unmatch process manually, and the Matched status can be
changed to Unmatched status.
Match Code
When you create a transaction, it has a status of Unmatched and a default of blank for the Match
Code. After you perform the matching process, the system changes the matching status to
Matched and generates a match code. It is for display only and you cannot change it manually.
The same match code applies to all the matching transactions in a group. For example, if you
match the following transactions, the same code applies to all the transactions in this group. If
there are reversed transactions, the system considers them a separate group and assigns them a
separate match code.
During the match by ID process, the system subdivides all the intercompany transactions with
the same transaction or reference ID into separate groups based on their account type. It then
assigns a separate match code and match status to each group of transactions with the same ID.
When the system generates the match code during the matching process, it uses one of these
prefixes to distinguish the different types of matching processes:
l
Entity
Partner
Account
Tran ID
Tran Amt
Match Status
Match Code
ICRec1
XY234
100
Matched
A11
ICRec2
XY235
300
Matched
A11
ICPay1
XY234
100
Matched
A11
ICPay2
XY235
300
Matched
A11
For the Match by Account process, you can select the option to group by transaction currency.
If one group of transactions has a different transaction currency than another group, the system
generates separate match codes for the different groups.
When the unmatch process is complete, the matching status for the transactions changes to
Unmatched and the match code becomes blank.
For example, suppose a group of transactions that include T123, T124, T125, T126 were matched
and assigned the same Match Code of A122. If you want to make changes to transaction T125,
you need to select T125 to unmatch. When you select T125, the system displays all the
transactions within the Match group for your review. After you confirm the selection, the
unmatch process unmatches all the transactions in this match group.
Click Unmatch Selected or Unmatch All, or select Actions, and then Unmatch Selected, or Unmatch
All.
From the Unmatch tab, review the transactions to be unmatched and click Unmatch.
When the unmatch process is completed, the match status for these transactions is
Unmatched and the match code changes to blank.
Select an action:
l
From the Result tab, verify the posting result and click OK.
On the Manage Intercompany transactions list, posted transactions are indicated by a green
flag in the Status column.
Posting Process
During the posting process, the system accumulates the transactions related to a particular
account cell and accumulates the amount to the account balance. For example, if you have two
transactions with a total of 100 for the ICRec account, the system applies the total amount of
100 to the ICRec account balance. If this is the first transaction, the ICRec account has a balance
of 100. If you later post four transactions to this account for a total amount of 300, after posting,
the ICRec account has a balance of 400, because the system adds the amount to the account
balance.
The system posts transactions to the Entity Currency Value dimension. If the account is a Balance
type, the system posts the amount as YTD view regardless of the default view of the scenario.
From Manage Intercompany Transactions, select the point of view, and review the Status
column for posted transactions.
From Manage Intercompany Transactions, select the point of view, and sort by Post status.
See Displaying Transaction Columns on page 153.
From a data grid, drill down to view the transactions. See Drilling Through to Intercompany
Transactions on page 82.
From a data form, drill down to view the transactions. See Drilling Through to
Intercompany Transactions on page 111.
Select an action:
l
From the Result tab, verify the posting result and click OK.
From the list of transactions, select the transaction, and select a task.
From the Manage Intercompany Transactions page, view the progress bar for the task
that is running.
From the Running Tasks page, select the task to view the progress.
Select an action:
l
To delete the transactions that meet the filter criteria, click Delete All, or select Actions,
and then Delete All.
Note: When you select Delete All, some transactions might not be deleted, based on their
When you run a report, a progress bar is displayed with the progress percentage, status, and last
update time. You can also view the progress from the Running Tasks module. See Viewing
Intercompany Transaction Progress on page 170.
grouping capability. This is not the matching report for reconciliation purposes. See
Running Matching Reports on page 174.
Select Consolidation, then Intercompany, then Reports. Click New, Reports, then IC
Transactions.
Select Consolidation, then Intercompany, then Manage. From the Reports menu, select IC
Transactions.
Select Consolidation, then Documents. Click New, then Reports, then IC Transactions.
To print or preview the report, click Print/Preview, or select Actions and then Print/Preview.
To save the report, click Save, or select Actions, and then Save.
Tip: To reset the selected options back to default values without saving your changes, click
From the confirmation prompt that the report was saved successfully, click OK.
Entity
Partner
Account
ICRec1
ICRec2
ICPay1
ICRec1
ICRec2
Table 22
Entity
Partner
Account
ICRec1
ICRec2
ICPay1
ICRec1
ICRec2
From Display Options, select View, then Columns, and select the columns, or select Show All.
Tip: To reorder columns, or show or hide them, click Manage Columns and select the
To sort the column, select Ascending, Descending, or select Actions, and then
Ascending or Descending.
To select no sorting, with the column selected and set to Ascending or Descending, click
either Ascending or Descending to display No Sort.
To repeat the information in every row, click Repeat, or select Actions, and then
Repeat.
To display the subtotal for the amounts, click Totals, or select Actions, and then Totals.
Transaction ID
Transaction Sub ID
Reference ID
Reason Code
Match Code
Transaction Currency
From Include, select one or more options: Matched, Unmatched, Mismatched, Posted, or Unposted.
Optional: To display only the subtotal row instead of all transaction details, select Suppress Details.
Suppressing Details
If you want the Matching Report to display only the subtotal amount, you can select to suppress
the intercompany details. When you select this option, the report displays only the total
difference for each entity/partner section. If there is a discrepancy and you need to view each
intercompany transaction, you can regenerate the report and show intercompany details.
Select Consolidation, then Intercompany, then Reports. Click New, Reports, then
Intercompany Match by Account.
Select Consolidation, then Intercompany, then Manage. From the Reports menu, select
Intercompany Match by Account.
Select Consolidation, then Documents. Click New, then Reports, then Intercompany Match
by Account.
From Security Class, select a security class for the report, or use the Default security class.
From the Point of View, select a scenario, year, and base period.
For Partner, enter a partner entity or click Browse to select a partner entity.
11 Optional: From Scale Factor and Decimal Override, select values for the amounts displayed for the
transactions.
12 From the Report Columns section, select columns to display on the report.
13 From Accounts, click Add and select the account dimension members or custom members, and in the
Matching Accounts section, click Add and select the matching account dimension members or custom
members.
Details
15 From Include During Processing, select one or more Match or Post statuses:
l
Matched
Unmatched
Mismatched
Posted
Unposted
18 To save the report, click Save, or select Actions, and then Save.
Tip: To reset the selected options back to default values without saving your changes, click
19 From the confirmation prompt that the report was saved successfully, click OK.
Select Consolidation, then Intercompany, then Reports. Click New, Reports, then
Intercompany Match by ID.
Select Consolidation, then Intercompany, then Manage. From the Reports menu, select
Intercompany Match by ID.
Select Consolidation, then Documents. Click New, then Reports, then Intercompany Match
by ID.
From Security Class, select a security class for the report, or use the Default security class.
From the Point of View, select a scenario, year, and base period.
For Partner, enter a partner entity or click Browse to select a partner entity.
11 Optional: From Scale Factor and Decimal Override, select values for the amounts displayed for the
transactions.
12 From the Report Columns section, select columns to display on the report.
13 From Match By, select an option and enter the IDs:
l
Details
15 From Include During Processing, select one or more Match or Post statuses:
l
Matched
Unmatched
Mismatched
Posted
Unposted
18 To save the report, click Save, or select Actions, and then Save.
Tip: To reset the selected options back to default values without saving your changes, click
19 From the confirmation prompt that the report was saved successfully, click OK.
Drill through from an Intercompany Matching Report (account balance level). See Drilling
Through to Intercompany Transactions on page 138.
Drill through from data grids. See Drilling Through to Intercompany Transactions on
page 82.
Drill through from Data Forms. See Drilling Through to Intercompany Transactions on
page 111.
you send an alert to a user, you must ensure that the user has security rights to receive
intercompany transaction alerts.
You can generate email alerts from the Intercompany Transactions Monitor page and
Intercompany Transactions Manage page.
To use email alerts, see Chapter 13, Using Email Alerts.
11
Using Journals
In This Chapter
About Journals ........................................................................................... 181
Journal Security Roles ................................................................................... 182
Using Journal Templates ................................................................................ 182
Managing Journal Periods............................................................................... 187
Processing Journals...................................................................................... 188
Creating Journals......................................................................................... 188
Scanning Journals ....................................................................................... 192
Journal Status ............................................................................................ 192
Managing Journal Groups ............................................................................... 193
Viewing Journal Lists..................................................................................... 194
Editing Journals .......................................................................................... 194
Selecting Dimension Members for Journal Detail ..................................................... 195
Copying and Pasting Journal Cells ..................................................................... 196
Submitting Journals...................................................................................... 196
Unsubmitting Journals ................................................................................... 196
Approving Journals....................................................................................... 197
Rejecting Journals........................................................................................ 197
Posting Journals.......................................................................................... 197
Unposting Journals....................................................................................... 198
Reviewing Journals....................................................................................... 199
Journal Validation ....................................................................................... 199
Viewing Automated Consolidation Journals ........................................................... 200
Creating Journal Reports ................................................................................ 201
Deleting Journals......................................................................................... 204
About Journals
During a financial period, you may need to adjust data after it is entered or loaded into baselevel entities. Journals provide an audit trail of changes made in the application and indicate
which users made adjustments and which accounts, entities, and time periods are affected.
With journals, you can:
l
Create recurring journals that are repeated for a number of future periods
Create auto-reversing journals that generate reversing entries in the next time period
After creating a journal, you submit it to your supervisor for approval before posting it to the
database.
Manage Templates
Create Journals
Generate Recurring
Read Journals
Approve Journals
Post Journals
Standard templates, which contain accounts and entities for adjustments that you enter
frequently. See Creating Standard Journal Templates on page 183.
Recurring templates, which contain complete information for identical journal entries that
occur for more than one period. See Creating Recurring Templates on page 184.
Journal templates are independent of the scenario and year. You select a scenario and year when
you create a journal based on the template. However, you must select a Value dimension member
for Recurring templates.
To access templates, you must be assigned the Manage Templates security role.
See these procedures:
l
Balanced - In a balanced journal, the total debits and credits for the journal must balance
before you can post the journal.
Balanced by Entity - In a balanced by entity journal, the total debits and credits must balance
for each entity included in the journal entry.
Unbalanced - In an unbalanced journal, the total debits and credits do not need to balance
before you can post the journal.
To set the Point of View, click a dimension name and from Member Selection, select dimension
members.
From Security Class, select a security class. or use the Default security class.
For Account, double-click in the row and from Member Selection, select an account and click OK.
10 Optional: To move the dimensions from the POV to the table rows, click Move dimensions to Table.
Tip: To move the dimensions selected for rows to the POV, click in the row and click Move
dimensions to POV.
Delete Row.
13 Optional: To scan the template and verify that journal entries are valid, click Scan.
14 To save the template, click Save.
Tip: To restore the last saved version of the template, click Reset.
To change the Point of View, click a dimension name and from Member Selection, select dimension
members.
From Security Class, select a security class or use the Default security class.
For Account, double-click in the row and from Member Selection, select an account and click OK.
10 Optional: To move the dimensions from the POV to the table rows, click Move dimensions to Table.
Tip: To move the dimensions selected for rows to the POV, click in the row and click Move
dimensions to POV.
Delete Row.
13 Optional: To scan the template and verify that journal entries are valid, click Scan.
14 To save the template, click Save.
Tip: To restore the last saved version of the template, click Reset.
To view template lists, select Consolidation, then Journals, and then Templates.
sensitive. For example, filtering with testgroup might return different results than
filtering with TestGroup.
From the Filters pane, enter filter criteria for Group, Label, or Description.
For Balance Types, click the Filter button, select balance types, and click OK.
Select View, then Columns, and select the columns to display, or select Show All.
To reorder columns, select View, then Reorder Columns, and use the arrow keys to reorder the columns.
Optional: To change the column sort order, click the header icons and select an option:
l
Sort Ascending
Sort Descending
No Sort
To add rows for more entries, click Add Rows. Rows are added to the bottom of the template.
Optional: To preview the template, view the Preview details at the bottom of the Journal Templates page.
To view the template in a larger format on a separate page, click Detach.
Click Print.
From the list of templates, select the template to delete and click Delete, or select Actions, and then
Delete.
security role.
Viewing Periods
You can filter the list of journal periods by selecting a scenario and year and by selecting the
period status; for example, Opened, Closed, or Unopened.
To view periods:
1
From Scenario and Year, select a scenario and year for which to view periods.
By default, all periods have an initial status of Unopened. You can open and close periods at any
time, but you cannot change an opened period to unopened.
You cannot close a period if there are unposted auto-reversals in the period. If you close a period
that contains approved journals, a warning message is displayed.
For Scenario and Year, select members of the periods that you want to open.
To open the selected periods, click Open, or select Actions, and then Open.
To close the selected periods, click Close, or select Actions, and then Close.
Processing Journals
After you set up journals, you can enter journal information and process journals. See these
procedures:
l
Creating Journals
You use journals to enter adjustments to account balances and maintain an audit trail of changes
to your data. You create journals by entering a journal label and description, balance type, point
of view, and adjustment amounts. You can also enter a security class for the journals, and a
journal group that you can use to filter and sort journals. After you create a journal, its status is
Working.
Before you create a journal, check the point of view to be sure that the scenario, year, period,
and value are the ones to which you want to enter adjustments. See Opening and Closing
Periods on page 187.
You can drag and drop the Entity, ICP, and all Custom dimensions between the journal grid
and the POV. If all dimensions in the journal detail lines are the same, the dimension is moved
to the POV header information. If they are not the same, they remain in the journal details. The
Account dimension remains on the detail line, and all other dimensions remain in the header.
If you are creating a journal for a single entity, you can use the entity dimension from the POV
header without dragging it to the journal rows.
When you enter journal data, you can scan the journal and verify that the entries are valid. In
this way, you can make any necessary changes before you post the journal. See Scanning
Journals on page 192.
To change the Point of View, click a dimension name and from Member Selection, select dimension
members.
- */ # {} ; , @
From Security Class, select a security class or use the Default security class.
10 For Account, select an account by using one of these methods and then click OK:
l
11 Optional: To move the dimensions from the POV to the table rows, click Move dimensions to Table.
Tip: To move the dimensions selected for rows to the POV, click in the row and click Move
dimensions to POV.
Delete Row.
14 Optional: Scan the journal and verify that the entries are valid. Save the journal and click Scan. See
Scanning Journals on page 192.
To change the Point of View, click a dimension name and from Member Selection, select dimension
members.
Note: The label can contain a maximum of 20 characters. Do not use these characters: . +
- */ # {} ; , @
From Security Class, select a security class or use the Default security class.
10 For Account, select an account by using one of these methods and then click OK:
l
11 Optional: To move the dimensions from the POV to the table rows, click Move dimensions to Table.
Tip: To move the dimensions selected for rows to the POV, click in the row and click Move
dimensions to POV.
Delete Row.
14 Optional: Scan the journal and verify that the entries are valid. Save the journal and click Scan. See
Scanning Journals on page 192.
to the journal. To modify the template, you must have All access to the security class assigned
to the template.
Click Generate.
Select a scenario, year, and period for which to generate the journal, and click OK.
Scanning Journals
After you enter journal data, you can scan the journal to verify that all entries are valid. The scan
process enables you to identify errors and make any necessary changes before you post the
journal.
When you run a scan, if the journal contains errors, a separate window displays the scan results
by row number. If all of the entries are valid, no message is displayed.
To scan journals:
1
Click Scan.
Journal Status
The journal status indicates the current state of the journal. The status of a journal changes when
you create, submit, approve, reject, or post the journal.
Table 23
Journal Statuses
Status
Description
Working
Journal is created. It has been saved, but it can be incomplete. For example, it might need to have a label or single entity
assigned.
Submitted
Approved
Rejected
Posted
The journal actions that are available depend on the journal status. For example, if the journal
has a status of Approved, the only actions available are Reject or Post.
Click Create.
Select one or more journal groups to delete and click Delete Selected, or select Actions,
and then Delete Selected.
To delete all journal groups, click Delete All, or select Actions, and then Delete All.
From the journal list, click View, then Columns, and then select the columns to display, or select Show
All.
Optional: To show or hide columns, select View, then Columns, then Manage Columns, and use the
arrow keys to move columns to the Hidden or Visible column lists.
Optional: To change the column sort order, click the header icons and select an option:
l
Sort Ascending
Sort Descending
No Sort
Editing Journals
You can edit a journal that you previously created. For example, you can change the description
of a journal, add adjustments, or change the balance type.
You can edit only Working, Submitted, and Rejected journals. You cannot edit Approved or
Posted journals. You must have All security access to the security class for a journal to edit the
journal. See the Oracle Hyperion Financial Management Administrator's Guide.
To edit journals:
1
To change the Point of View, click a dimension name and from Member Selection, select dimension
members.
From the list of journals, select a journal with a status of Working, Submitted, or Rejected.
Click Edit, or select Actions and then Edit, or double-click a journal row.
Optional: To scan the journal and verify that the entries are valid, click Scan.
Value Dimension
[Adjs Ent]
[Parent Adjs]
[Contrib Adjs]
ST Template
[Adjs Ent]
Rec Template EC
[Adjs Ent]
Rec Template PC
Rec Template PA
Rec Template CA
You can select the journal detail when the journal status is Working, Submitted, or Rejected.
You cannot make changes to the journal detail when the journal status is Approved or Posted.
To change the Point of View, click a dimension name and from Member Selection, select a member for
the scenario, year, period, and value.
Click OK.
Tip: To select dimension members from an open journal, click Pick Members, or from a
journal row, right-click and select Pick Members, select the members, and click OK.
To copy the information in a row and store it on the clipboard, click Copy Row, or select Actions, and
then Copy Row.
To paste the information from the clipboard to the selected row, click Paste Row, or select Actions, and
then Paste Row.
Submitting Journals
After creating journals and entering journal data, you must submit them to your supervisor for
approval before posting them to the database. You can submit a journal when you create it, or
submit it later by selecting it from the list of available journals.
You can submit journals one at a time or in batches. After you submit a journal, the status
changes to Submitted. A reviewer then approves or rejects the journal, and if it is approved, you
can post it.
To submit journals:
1
From the list of journals, select the Working or Rejected journal to submit.
Unsubmitting Journals
You can unsubmit a journal that you previously submitted. When you unsubmit a journal, the
status reverts from Submitted to Working.
To unsubmit journals:
1
Approving Journals
After you submit a journal, you can approve it for posting. You can approve a journal from the
Edit Journal tab after you create and submit it, or you can approve it later by selecting it from
the journals list.
You can approve journals one at a time or in batches. After you approve a journal, the status
changes to Approved and the journal cannot be edited.
To approve journals:
1
Rejecting Journals
After a journal is submitted for approval, or approved, you can reject it. You can reject journals
one at a time or in batches. After you reject a journal, the status changes to Rejected.
To reject journals:
1
Posting Journals
You can post a journal after it is approved. You can post a journal after you submit and approve
it, or you can post it later by selecting it from the list of available journals.
The scenario view to which a journal is posted depends on the setting for the Scenario attribute
ZeroViewForAdj. If this attribute is set to Periodic, the journal is posted to the Periodic value.
If this attribute is set to YTD, the journal is posted to the YTD value.
You can post journals one at a time or in batches. You must have the journal period open before
you can post, and you must have All access to the security classes of every entity for the detail
lines.
Your ability to post a journal also depends on the process level of the data in the journal. For
example, if you have a process management security role of Reviewer 2 and the data that the
journal affects is at Process Level 6, you cannot post the journal. See Process Levels on page
207.
When you post adjustments from a journal, the adjustment values are stored in the specified
adjustment member. These four Value dimension members are valid for posting journals: Entity
Currency Adjustments, Parent Currency Adjustments, Parent Adjustments, and Contribution
Adjustments.
You can post a journal to a specific parent and child combination (node) by using one of these
Value dimensions:
l
Contribution Adjs - Applied to the contribution when determining the contribution total.
Note: Node adjustments are posted in the currency of the parent.
If more than one journal is posted to the Entity Currency Adjs member for the same account,
the results are cumulative. The total from the current journal is added to or subtracted to from
the existing total in Entity Currency Adjs.
When you post a journal, the system recalculates the account balances so that the database reflects
the adjustments. The journal status changes to Posted, and you can view the adjustment in a
data grid.
Note: Do not delete or rename a posted journal, as this will result in unresolved data for the
To post journals:
1
Unposting Journals
You can unpost a journal after it is posted. For example, suppose you post several journals with
adjustments to an entity, and you receive new data for that entity. You can unpost the journals,
load the new data, and post the journals again.
When you unpost a journal, the journal status changes to Rejected. When you unpost an autoreversal journal, the journal status changes back to Approved.
To unpost journals:
1
Reviewing Journals
You can review journals that have been created, edited, submitted, unsubmitted, approved,
rejected, or posted. You can review journals before they are posted, or after they are posted and
before you run a journal report.
To review journals:
1
Journal Validation
When you submit, approve, or post a journal, the system validates the journal. The system checks
for these conditions:
l
The period must be a base period for the scenarios base frequency.
The journal must have the appropriate status for the action to be performed.
The entity and the parent must be valid dimensions. For regular journals, the entity must
allow adjustments. If you are posting a journal to Parent Currency Adjs, you must enter a
valid parent. The entity must be a child of the specified parent for the journal entity.
If you are posting a journal to a node, the parent must allow adjustments for child entities.
The entity must be a child of the specified parent.
Node journals must have valid parent-entity combinations. The system also checks for the
Organization by Period application setting when you attempt to post node journals. The
entity must be active for the parent for the period in which you are posting.
The account must be valid. It must be an Asset, Liability, Revenue, Expense, Balance, Flow,
or Balance Recurring account. The account must be a base account and cannot be designated
as calculated in metadata. It cannot be calculated through a roll-up process; the account
cannot have children.
All other dimensions must be valid. The ICP dimension cannot be ICP Top, ICP Entities,
or blank, but you can select ICP None. If an ICP is specified, the account must be set up as
an ICP account.
The Custom dimensions cannot be designated as calculated in metadata and cannot be
calculated through a roll-up process; the Custom dimensions cannot have children.
For a balanced journal, the total debits must equal the total credits. For a balanced- by-entity
regular journal, the total debits must equal the total credits for each entity. For a balancedby-entity node journal, the total debits must equal the total credits for each node and the
parent and children entities must have the same currency. If the Value dimension is Entity
Currency, the parent entities in the journal can have different currencies, but they must have
the same currency as their children entities.
l
The subcube of dimensions containing the line item cell cannot be locked.
consolidation journals. You can only open and view journals, run reports, and extract
journals.
To run a journal report on automated consolidation journals, see Creating Journal Reports
on page 201. To print a report, see Printing Journal Reports on page 203.
Select the Scenario, Year, and Period for the consolidation data that you want to view.
For the Value member, select [Proportion] or [Elimination], and then click OK.
The system displays a list of journals generated during the consolidation process.
of View and to the journal security class. You must also have the Read Journals or
Journals Administrator security role.
Click New, then Reports, and then Journal, or select Actions, then New, then Reports, and then
Journal.
From the Point of View, select a Scenario, Year, Period, and Value for the report.
Note: To run a journal report for automated consolidation journals, you must select
From the journal report, click View, then Columns, and then select the columns to display, or select
Show All.
Optional: To show or hide columns, select View, then Columns, then Manage Columns, and use the
arrow keys to move columns to the Hidden or Visible column lists.
Optional: To reorder columns, select View, then Reorder Columns, use the Up and Down arrows to
reorder the columns and click OK.
Optional: To change the column sort order, click the header icons and select an option:
l
Ascending
Descending
No Sort
Optional: To repeat the information in every row, click Repeat or select Actions, and then Repeat.
Optional: To display the subtotal for the amounts, click Totals, or select Actions, and then Totals.
Tip: To restore the columns to their default settings, click Restore Defaults.
sensitive. For example, filtering with testgroup might return different results than
filtering with TestGroup.
To filter by entity, enter an entity name or click Browse and select an entity.
To filter by group, label, or description, enter text or use the percent sign (%) as a wildcard.
To filter by status, select one or more options: Working, Submitted, Approved, Rejected, or Posted, or
select Show All.
To filter by type, select one or more options: Regular, Auto-reversing, Auto-reversed, or select Show
All.
To filter by balance type, select one or more options: Balanced, Unbalanced, or Balanced by Entity,
or select Show All.
Tip: To restore the list to its default status, click Restore Defaults.
Click Save or Save As, enter the report information and click Save.
Click Print/Preview.
the columns or format. For instructions on selecting options for reports, see Printing
Journal Reports on page 203.
Click Print.
Deleting Journals
You can delete unposted journals that you no longer need. You cannot delete Approved or Posted
journals, because that would result in unresolved data for the adjustment values that the journal
had created.
To delete journals:
1
From the journals list, select the journal to delete, and click Delete, or select Actions, and then
Delete.
12
In This Chapter
About Process Management ............................................................................ 205
Starting Process Management .......................................................................... 208
Using Process Control ................................................................................... 209
Promoting Process Units ................................................................................ 222
Submitting Process Units................................................................................ 223
Approving Process Units................................................................................. 224
Rejecting Process Units ................................................................................. 225
Signing Off on a Process Unit .......................................................................... 225
Publishing Process Units ............................................................................... 226
Locking and Unlocking Process Units .................................................................. 227
Viewing Process Review History......................................................................... 228
Email Alerts for Process Control ........................................................................ 228
Process Management Validation ...................................................................... 229
Process Management and Consolidation.............................................................. 230
When you select a 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 is not available when you select a quarter, such as Q1. If you select multiple
cells and your selection includes a data cell in which Process Management is not supported, the
Process Management option is not available.
If Process Management is enabled for a scenario, the system performs validation checks 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. See Process Management Validation on
page 229.
Read - you can only view data for the process unit.
Promote - you can view data and also promote an entity even if you do not have All
access.
All - you have complete access to the process unit, including the ability to view and to
modify data.
Table 25
Security Role
Description
Reviewer 1
through 9
You can promote a process unit to the next level or reject it. See Process Levels on page 207.
Reviewer 10
You can reject a process unit, but you cannot promote it because a next level is not available. To move the process
unit to the Submitted level for final approval, you must be a Submitter.
Submitter
You 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, a Submitter can omit many levels of review and go to
the last process level (Submitted) before final approval.
Review
Supervisor
You have access rights to start a process unit that allows input to the entitys data, and you can approve and publish
the data.
To promote or reject a process unit, you may also need the Reviewer 1-10 role, depending on the process level. See
Process Levels on page 207.
Process Levels
Process units pass through a number of process levels during the review cycle. The possible
process levels are shown in Table 26 with a description of each level and the access rights that
are required.
Table 26
Process Levels
Level
Description
Not Started
The Review Supervisor has not started the process unit, and only the Supervisor can enter data. Only the Supervisor who
has All access rights to the entity can change the process unit level to First Pass.
First Pass
Process unit has been started and is in the initial stage for data to be entered by users with the proper access rights.
Any user with Read or Promote access to the entity can view the entitys data. Any user with All access to the entity can
modify the entitys data. No security role is checked when the process unit is in the First Pass level.
Review Levels
1 through 10
Process unit is at the designated review level. To view data, a user needs access rights of Read, Promote, or All, and a
security role of less than or equal to the process level of the data. To modify data or change the status, a user needs
access rights of All and a security role equal to the process level of the data.
Submitted
Process unit has been submitted and is ready for final approval. To view data, a user needs access rights of Read,
Promote, or All, and any security role. To modify data or change the status, a user needs access rights of All and the
Review Supervisor security role.
Submitted level is the common final process level before a process unit can be approved. If you have the Submitter
security role, you have the option to skip levels of review and promote the process unit directly to the Submitted level.
Approved
Process unit has been approved. To view data, a user needs access rights of Read, Promote, or All, and any security
role. To modify data or change the status, a user needs access rights of All and the Review Supervisor security role.
Published
Process unit has been published for public access. To view data, a user needs access rights of Read, Promote, or All,
and any security role. To modify data or change the status, a user needs access rights of All and the Review Supervisor
security role.
Not Supported
Note: The ability to modify data also includes the ability to post journals.
After a Review Supervisor starts a process unit, its process level changes to First Pass.
You can start Process Management from a data grid or from the Process Control module. When
you start a process unit from the Process Control module, you can select a data view and filter
and sorting options. See Using Process Control on page 209.
From the POV bar, click a dimension name and from Member Selection, select dimension members for
the Scenario, Year, and Period.
Optional: To change the top member for the entity list, from Member Selection, select an entity.
Local
Translation
Contribution
Optional: Select the options for the grid, views, and columns.
Optional: If you are using the Tree view, select Apply Action to Selected Entity Only or Apply Action to
Selected Entity and Descendants.
10 Click OK.
From a data grid, select the cell for which to start Process Management.
Click OK.
currency rate information. In addition, you can generate and receive email alerts about process
management status.
To access the Process Control module, select Consolidation, then Data, and then Process
Control.
Local View
When the Local Data View is selected, the Calculation Status (Calc Status) column is based on
the Entity Currency Total member (Entity Curr Total) of the Value dimension. The Journal
Status column (ECA Status) is based on the Entity Currency Adjustment member (Entity Curr
Adjs) of the Value dimension.
Translation View
When the Translation Data View is selected, the Calculation Status (Calc Status) column is based
on the Parent Currency Total member (Parent Curr Total) of the Value dimension. The Journal
Status column (PCA Status) is based on the Parent Currency Adjustment member (Parent Curr
Adjs) of the Value dimension.
Consolidation View
When the Consolidation Data View is selected, the Calculation Status (Calc Status) column is
based on the Contribution Total member (Contribution Total) of the Value dimension. The
Journal Status columns (PA and CA Status) are based on the Parent Adjustment (Parent Adjs)
and Contribution Adjustment (Contribution Adjs) members of the Value dimension.
From the POV bar, click a dimension name and from Member Selection, select dimension members for
the Scenario, Year, and Period.
Optional: To change the top member for the entity list, from Member Selection, select an entity.
Local
Translation
Contribution
Optional: Select the options for the grid, views, and columns.
To select multiple rows, from the Process Control page, use these options:
l
To select contiguous rows, highlight a row and drag to select additional rows.
To select noncontiguous rows, highlight a row, press and hold Ctrl, and select additional
rows.
To select all rows, click the top left cell corner of the grid.
Review Level, for example, Started, First Pass, Review Level 1, Approved. See Process Levels
on page 207.
Pass/Fail status, which displays whether the process unit is ready for promotion to the next
level. See Viewing the Pass or Fail Status on page 216.
Validation status, which displays the validation status for the entity based on the amount
stored in the Validation account for the entity. See Viewing Validation Account Detail on
page 217.
Calculation status, for example, OK, NODATA, CH. See Viewing Calculation Status on
page 218.
Journal status, which displays a red or green flag for the status of journals for the entity, such
as Entity Currency Adjustments, Parent Currency Adjustments, Parent Adjustments, or
Contribution Adjustments. See Viewing Journal Status on page 219.
The Process Control page also uses cell colors to indicate additional information about the data.
See Using Data Cell Colors to Determine Status on page 68.
Style
You can display entities in a flat list or as a Tree hierarchy format. You can only use a Tree view
if you select the Hierarchy system member list. All other member lists are displayed as a flat list.
When the entities are displayed in a Tree view, you can expand and collapse the hierarchy using
the plus (+) and minus (-) signs next to the entity. When changing the process level in a Tree
view, you can choose to apply the action to the current selected entity only or to the selected
entity and its descendants. Using the entity and descendants option allows you to perform an
action without having to manually expand the entire organization.
When the list is displayed in a Tree view, row sorting or filtering is unavailable.
Entity View
You can view entity information using the entity label, description, or both. The default setting
is to display the label.
Filters
When you use a list view, row sorting and filtering are available. For example, you can filter rows
based on the review level and display all rows above or below a specific review level, such as all
levels above First Pass. You can sort rows by review levels in descending or ascending order.
You can filter rows by validation status, such as Pass Only or Fail Only. You can also filter rows
by calculation status, such as OK, CN, or TR. See Viewing Calculation Status on page 69.
After you set sorting and filtering options, the settings are displayed in tool tips for the columns
on the Process Control page.
Period View
You can view one period or all periods. When you choose all periods, you can view status for
only one submission phase at a time, and you must choose to view either the Process Review
Level or Calculation Status. The selected information is displayed across the columns for all the
periods in the scenario.
Submission Phases
If your application contains submission phases, 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.
Page Size
Depending on the entity list selection, it is possible to display many entities for Process Control.
To minimize the performance issue with a large number of entities, you can select the number
of entities to display on the page.
From the Process Control page, Display Options, Grid Settings, select a Data View:
l
Local
Translation
Contribution
For Rows Per Page, enter the number of rows or use the default value of 1024.
For Review Level Columns, select one or more options: Review Level, Pass/Fail, or Validation.
For Status Columns, select one or more options: Calc Status or Journal Status.
Function
Rates
Toolbar Button
Description
Link to a predefined data grid with Rate data.
Note: The grid label for the predefined Web grid must be named Rates.
Ownership
Management
Refresh
Manage Process
Start, promote, submit, approve, reject, sign off, and publish a process unit.
Consolidate
Consolidate, consolidate all, consolidate all with data, calculate contribution, or force
calculate contribution of data.
Calculate
Translate
From Process Control, select the Scenario, Year, Period, and top member Entity process unit for which
to view a summary.
On the right pane, expand Review Level Summary or Calculation Status Summary.
Data View
Value Dimension
Local Data
Translate Data
Consolidation Data
Contribution Total
If the calculation status is OK, OK SC, or NODATA and if the Validation account amount is
equal to zero or NODATA, the Pass/Fail column displays a Pass check mark indicating that the
unit is ready for promotion.
If the process unit fails, the Pass/Fail column displays an X. In this case, 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.
When the system checks for Pass/Fail status, it checks for derived data in the current period. A
period can contain derived data if the Validation account is a Flow account and if the
ZeroViewforNonAdj metadata attribute is set to Periodic for the scenario. A unit with a
calculation status of NODATA passes only if there is no data in prior periods. If a unit has a
calculation status of NODATA but data exists in the prior period, the process unit displays a Fail
status. For example, if you have no data in January, the calculation status for January is NODATA
with a status of Pass. If you have data in January but no data in February, the status is Fail because
February has derived data from January.
See Viewing Validation Account Detail on page 217.
To view the Pass/Fail status, from Process Control, select the entities for which to show
status.
The Pass/Fail status is displayed in the Pass/Fail column.
Calculation status
Depending on the Data View option that you selected for the process unit, the system displays
different data values.
l
If the Data View is Local Data, the system displays Entity Curr Total, Entity Curr Adjs and
Entity Currency
If the Data View is Translate Data, the system displays Parent Curr Total, Parent Curr Adjs
and Parent Currency.
If the Data View is Consolidation Data, the system displays Proportion, Elimination,
Contribution Adjs and Contribution Total.
The Raw Data option displays the data in units. The Formatted Data option displays data in the
scaled value based on the scale of the currency assigned to the entity.
For example, suppose the Entity dimension member, WestSales, displays an X in the Validation
column. To view more information, you can click the X in the column. The following figure
shows the Validation account detail for the WestSales account.
Figure 3
In the example, there are two validation accounts: Surplus and ICMatch. The Surplus account
contains a balance, causing West Sales to fail validation. WestSales is not ready for promotion
because the Validation account does not equal zero. It cannot be promoted until the Surplus
account has been balanced.
From Process Control, select the entities for which to show validation detail.
For the selected entity, double-click its icon in the Validation column.
Tip: You can also click the icon for the entity in the Pass/Fail column.
To view calculation status, from Process Control, select the entity top member for which to
show calculation status.
The calculation status is displayed in the Calc Status column.
From Process Control, select the entity top member for which to show journal status.
The journal status is displayed in the ECA, PCA, PA, or CA Status column.
Optional: If the column displays a red flag indicating unposted journals for a process unit, click the flag
to open the Journals module and view the unposted journals.
To view rates:
1
From Process Control, select the process control unit for which to view rates.
The system opens the Rates data grid that you previously defined. If you do not have a Rates
data grid, an error message is displayed.
From Process Control, select the process control unit for which to view ownership management
information.
The system opens the Ownership Management grid that you previously defined. If you do not
have an Ownership Management grid, an error message is displayed.
From Process Control, select the process unit for which to attach a document.
From your list of custom documents, select one or more documents to associate with the process unit,
and click Attach.
Note: You cannot attach private documents.
The document is associated with the scenario, year, period, and entity combination and the
process level.
From Process Control, select the process unit for which to calculate data.
Click Calculate
From Process Control, select the process unit for which to translate data.
From Process Control, select the process unit for which to consolidate or calculate contribution.
From Process Control, select the process unit for which to run or force equity pickup calculations.
security roles. Any user who has All access to the entity can modify the data.
The process unit must have a calculation status of OK, OK SC, or NODATA, and a zero balance
in the validation account before you can promote it.
When you promote the 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 immediate children.
If your application uses phased submissions, when you select a cell, the system determines the
submission phase that applies to the cell. There can only be one review status for each submission
phase, so when you promote the cell, you promote all the cells for that submission phase. When
you promote multiple cells in the data grid, the system determines all submission phases that
apply to those cells and promotes the phases at the same time, depending on the review level
dependency rules.
After you promote a process unit, its process level changes to the next process level. You can
promote a process unit up through Review Level 10, which is the last process level. When a
process unit has a status of Review Level 10, you can submit it for approval. See Submitting
Process Units on page 223.
Note: If you receive javascript errors during the promotion process, you might need to increase
the timeout setting for the Oracle Hyperion Reporting and Analysis proxy server. See the
Oracle Enterprise Performance Management System Installation and Configuration Guide.
From Promotion Level, select a review level to which to promote the process unit.
Optional: If you use the Tree view, select Apply Action to Selected Entity Only or Apply Action to Selected
Entity and Descendants.
Click Promote.
From a data grid, select the cell for the process unit to promote.
For Promotion Level, select the review level for the process unit.
Click OK.
Optional: If you use the Tree view, select Apply Action to Selected Entity Only or Apply Action to Selected
Entity and Descendants.
Click Submit.
Click OK.
Optional: If you use the Tree view, select Apply Action to Selected Entity Only or Apply Action to Selected
Entity and Descendants.
Click OK.
Click Approve.
Click Reject.
Optional: If you use the Tree view, select Selected Entity Only or Selected Entity and Descendants.
Click OK.
Optional: If you use the Tree view, select Apply Action to Selected Entity Only or Apply Action to Selected
Entity and Descendants.
Click OK.
security roles. Any user who has Read or All access to the entity can view the entitys data,
but it is available only for viewing.
Set the rows and columns. See Selecting Entities for Process Control on page 212.
Optional: If you use the Tree view, select Apply Action to Selected Entity Only or Apply Action to Selected
Entity and Descendants.
Click Publish.
Click OK.
To lock data:
1
From a data grid, select the cells for which to lock data.
To unlock data:
1
From a data grid, select the cells for which to unlock data.
From a data grid, select the process unit for which to view information.
It checks the process level of direct descendants to ensure that you are not promoting an
entity to a level that is higher than the lowest level of all of the entitys dependents.
If you are using a different currency for the entity, the system checks the process level for
the entitys input currency to ensure that a current translation is being used.
If you are using a node component, the system checks the currency process unit that applies
to the parents input currency to ensure that the node values are correct.
The system also performs validation checks for child entities with 0% consolidation (unowned
entities). Before you can promote the parent entity, you must promote the unowned entities to
a specific level; for example, the lowest level of all of the child entities.
It checks the process level of the immediate parents to ensure that you are not rejecting an
entity to a level that is lower than all of the entitys parents.
If the Value dimension equals the input currency for an entity, the system checks the input
currency for all of the parents. If the parents input currency is the same as the entitys input
currency, the system checks the node process unit. If the parents input currency is different,
the system checks the process level of the parents currency at the entity level.
If the Value dimension uses a currency other than the input currency for an entity, the system
checks the level of the node process unit.
If the Value dimension indicates that you are using a node process unit, the system checks
the process level for the parents input currency process unit.
13
In This Chapter
About Email Alerts ....................................................................................... 231
Generating Alerts for Intercompany Transactions ..................................................... 232
Generating Alerts for Process Control .................................................................. 233
The security class assigned to the scenario and entity for the alert must support email alerts.
See the Oracle Hyperion Financial Management Administrator's Guide.
Users must be assigned a security role to receive email alerts. See the Oracle Enterprise
Performance Management System User Security Administration Guide
The SMTP mail server must be configured. See the Oracle Enterprise Performance
Management System Installation and Configuration Guide.
From the list of entities, select the entities for which to send an alert.
The comment is used for all the alerts that are generated.
Click Send.
Security access rights of All, Read, or Promote to the data cell for the transaction
Security class attribute of SupportAlert=Y for both the scenario and entity
When you receive an email alert for intercompany transactions, it displays the module from
which the alert was generated; for example, Intercompany Transactions. It also displays the point
of view used in the transaction for which the alert was generated.
The comment that was used when generating the alert is displayed for all users. However, the
specific information in the alert varies depending on your security role and the security class
assigned to the transaction.
For security reasons, no data is displayed in email alerts. The email serves to alert you of a change
in status, or that you must perform an action about the item in the alert.
When a process review action is performed in a data grid or the Process Control module, the
system automatically generates email alerts to the appropriate users for the action, according to
the scenario setting and security rights set up by the administrator. For example, when a process
unit is promoted to the next level, only the users with appropriate access rights to the process
unit at that review level can receive the alerts.
The system sends email alerts to the users at the prior level before the process control action,
and to the users at the current level after the action. For example, User 1 and User 2 both have
Reviewer 4 role access, and User 3 and 4 have Reviewer 5 role access. When the process unit is
at Level 4 and is promoted to Level 5, User 1 and 2 receive email alerts because they are at Level
4 before the promote action. Users 3 and 4 receive email alerts because they are at Level 5, which
is the current level after the promote action.
When the alert is generated, the user who performed the action receives a confirmation email.
The confirmation email contains the action performed, the process units affected by the action,
and the names of the users receiving the email alerts for each process unit.
Enable security access for email alerts for the process unit and for the appropriate users for the action.
Optional: To add a comment, from Process Control, select a process unit and enter a comment in
Comments.
As a result of the review action, an alert is generated to the appropriate users. The comment
is used for all the alerts that are generated.
The email content contains the following information regarding the action performed and the
process unit:
Action: review action performed
Comment: additional comments to be included in the email
Process unit information: list of entities in the review action
Entity label - Entity description, Period, Year, Scenario, Review Level
prior to action, Review Level after the action
The process for sending process control alerts is different from that of intercompany
transactions, where you can enter comments when you send the alert. Since the system generates
process control alerts, it enables you to include additional comments in the content, and then
includes the comments when generating the alerts. The additional comments are included in all
the alerts generated from one review action. Therefore, all users in a specific distribution list
receive the same comment information.
When you receive an email alert for process management, it displays the module from which
the alert was generated; for example, Process Control. It also displays the point of view used in
the process unit for which the alert was generated.
The comment that was used when generating the alert is displayed for all users.
For security reasons, no data is displayed in email alerts. The email serves to alert you of a change
in status, or that you must perform an action about the item in the alert.
14
Automating Tasks
In This Chapter
Overview .................................................................................................. 237
Financial Management Tasks Available for Automation.............................................. 237
Prerequisites for Task Automation...................................................................... 238
Managing Taskflows ..................................................................................... 238
Viewing Taskflows ........................................................................................ 239
Creating Taskflows ....................................................................................... 239
Editing Taskflows ......................................................................................... 248
Deleting Taskflows ...................................................................................... 248
Copying Taskflows ....................................................................................... 248
Running Taskflows Manually for Testing ............................................................... 249
Controlling Access to Taskflows ........................................................................ 249
Scheduling Taskflows .................................................................................... 250
Viewing Taskflow Status ................................................................................. 250
Overview
Task Automation provides a method for linking a series of tasks into a taskflow. You can use
task automation to automate tasks that you commonly perform using Financial Management.
When you work with Financial Management, you routinely perform tasks such as loading data,
running calculations and translations, consolidating parent entities, and extracting data. You
can create, manage, and maintain taskflows to schedule critical tasks to be run as required.
See these procedures:
l
Allocate
Calculate
Overview 237
Calculate Contribution
Translate
Consolidate
Load Journals
Extract Journals
Load Data
Process Journals
You must be assigned one of these Oracle Hyperion Shared Services roles to perform taskflow
operations:
m
Note: Both of these roles are global user roles. Users assigned these roles can either modify
or run taskflows for any application and product. See the Oracle Enterprise
Performance Management System User Security Administration Guide.
Managing Taskflows
A taskflow is a sequence of tasks that you can create in task automation. For example, you can
create a taskflow to load, calculate, and consolidate data. You can create, edit, save, copy, and
delete a taskflow, view a list of available taskflows, assign access to a taskflow, run a taskflow
manually for testing, and schedule a taskflow to run automatically.
You can enable logging capability for taskflows. See the Oracle Enterprise Performance
Management System Installation and Configuration Troubleshooting Guide.
See these procedures:
l
Viewing Taskflows
You store and manage taskflows in Shared Services. The Taskflow Listing Summary shows the
available taskflows by application, the user who created the taskflow, and a description.
To view taskflows:
1
Select Administration, and then Taskflows, and then Manage, or expand Taskflows from the left side
navigation pane and select Manage.
Note: When viewing tasks in a taskflow, users can only view those tasks to which they have
access.
Creating Taskflows
You create a taskflow to link a series of tasks and specify the time to run them. When you create
a taskflow, you assign it a name and description. Then you add task stages and links between
tasks. Stages define specific tasks, such as data loads. Links specify how the system should proceed
after completion of the step.
To create taskflows:
1
Select Administration, and then Taskflows, and then Manage, or expand Taskflows from the left side
navigation pane and select Manage.
Click Submit.
The taskflow editor is displayed, where you can add stages and links.
Adding Stages
A stage describes a step in a taskflow. Each stage has an action, such as load data. These actions
have parameters for which values are supplied at runtime.
You define a stage using these three tabs:
l
General: Defines the stage name, description and user ID of the user responsible for
completing the stage. The user can be an initiator, which is the owner of the first stage in
the taskflow, or another user for the other stages.
Processing: Defines the action to be performed when the stage is run and any required
parameters.
Starting Event: Defines the event that initiates the taskflow, and the scheduled times for the
event to occur. The scheduled time is based on the time of the application server, not on the
time of the local user's computer. You can schedule the taskflow to run according to a
schedule such as weekly, monthly, at the first of the month, or so on. This tab is displayed
only for the first stage in the taskflow. It displays the scheduled event (taskflow start time),
or is disabled (for the manual start of a taskflow run by the Run Now option).
To add stages:
1
A new stage is displayed in the left pane, and stage details are displayed in the right pane. If
stages exist in the taskflow, the new stage is created at the end of the taskflow.
Figure 4
b. Optional: For Description, enter a taskflow description; for example, Load a monthly
data file.
c. From Run As, select UserName, and enter a username and password for the user who
launches the taskflow.
Note: Stage 1 requires that you enter a username and password. When you create future
stages, you can select to run as the Initiator, which tells the system to use the user
ID and password that was defined in Stage 1.
c. From Type for each parameter, select Picklist, Text Box, or URL, depending on the action,
and enter values for the parameter.
For example, for the LoadData action, the Mode option contains a picklist from which
you can select Merge, Accumulate, or Replace.
To edit the Point of View, click Edit, then select members for the Point of View.
For the data file and log file names and paths, you must manually enter the information
in a text box. The taskflow is run from the server, so you must make sure that the file
names and paths are valid and can be accessed from the server running the task.
Therefore, you should not enter a path such as c:\file.dat that references your own
hard drive. You must identify the computer name and share directory for the file using
Universal Naming Convention (UNC); for example, \\HFMServer\share\path
\file.dat.
Figure 5
Select the Starting Event tab, select Scheduled Event and enter this information:
b. For Start Date, enter the scheduled date for the task to be run, or click the pop-up
calendar and select a date.
c. From Start Time, select the scheduled time for the task to be run.
Note: The scheduled time is based on the time of the application server, which is
identified on the Server Date line, not on the time of the local user's computer.
d. For a recurring task, select Recurrence, and from Recurrence Pattern, select the task
frequency.
e. Select an option for the task end date and time:
No End Date
Optional: To add a stage, click Add Stage and complete the stage information for General and
Processing.
Note: The Starting Event tab is available only for the first stage. However you can schedule
Table 29
Action
Parameter
Name
Type
Possible Values
Purpose
Allocate
POV
URL
Point of View
Calculate
POV
URL
Point of View
Calculate
Force
Picklist
True
False
Calculate
Contribution
POV
URL
Point of View
Calculate
Contribution
Force
Picklist
True
False
Translate
POV
URL
Point of View
Translate
Force
Picklist
True
False
Consolidate
POV
URL
Point of View
Consolidate
Type
Picklist
Impacted
All
Load Journals
Journals File
Textbox
Load Journals
Log File
Textbox
Load Journals
Delimiter
Textbox
Extract Journals
Journals File
Textbox
Extract Journals
Log File
Textbox
Extract Journals
Delimiter
Textbox
Action
Extract Journals
Extract Journals
Extract Journals
Parameter
Name
Extract
Templates
Extract Recurring
Templates
Extract Journals
Type
Possible Values
Picklist
True
False
True
False
True
False
Picklist
Picklist
Purpose
Indicates whether to extract journal templates
Extract Journals
POV
URL
Point of View
Load Data
Data File
Textbox
Load Data
Log File
Textbox
Load Data
Delimiter
Textbox
Load Data
Mode
Picklist
Load Data
Load Data
Accumulate
Within File
Contains
Ownership Data
Picklist
Picklist
Merge
Replace By Security
Replace
Accumulate
True
False
True
False
Extract Data
(Deprecated)
Data File
Textbox
Extract Data
Log File
Textbox
Extract Data
Delimiter
Textbox
Extract Data
View
Picklist
Year to date
Periodic
Scenario Default
Extract Data
POV
URL
Point of View
Extract Data
Calculated
Picklist
True
False
Action
Execute Journal
Action
Parameter
Name
Type
Possible Values
Journal Action
Picklist
Submit
Approve
Post
Unpost
Unsubmit
Reject
Delete
Purpose
Indicates the type of action to perform for the
journal. See Processing Journals on page
188.
Execute Journal
Action
POV
URL
Point of View
Execute Journal
Action
Journal Label
Textbox
Extract Data to
Database
DSN
Textbox
Extract Data to
Database
Table Prefix
Textbox
Extract Data to
Database
Push Type
Picklist
Standard
Metadata Only
Essbase
Data Warehouse
True
False
True
False
True
False
None
Extract Data to
Database
Extract Data to
Database
Extract Data to
Database
Extract Data to
Database
Extract Data to
Database
Extract Data to
Database
Extract Type
Exclude Dynamic
Accounts
Calculated Data
Derived Data
POV
Picklist
Picklist
Picklist
Picklist
Picklist
URL
Point of View
Action
Parameter
Name
Type
Possible Values
Purpose
Data File
Textbox
Log File
Textbox
Extract Type
Picklist
True
False
True
False
True
False
None
True
False
True
False
Exclude Dynamic
Accounts
Calculated Data
Derived Data
Cell Text
Picklist
Picklist
Picklist
Picklist
Picklist
Phased
Submission
Group Data
Picklist
POV
URL
Point of View
Process Management
POV
URL
Process Management
Comment
Textbox
Comment text
Process Management
Action
Picklist
Start
Promote
Reject
Sign Off
Submit
Approve
Publish
None
Review level 1 to 10
Process Management
Promote to State
Picklist
Adding Links
A link is the point during the execution of the taskflow at which the activity in one stage is
completed, and the taskflow ends or control passes to another stage, which starts. A link can be
unconditional, where the completion of one stage always leads to the start of another, or
conditional, where the sequence of operation depends on one or more link conditions.
A link specifies the action for the system to take next. Every stage needs a link. In general, most
stages have two links: success and failure. You can specify that, if the first stage is successful, the
system should proceed to the second stage (Receiving stage). You can also specify the action to
be performed if problems occur in the first stage and it does not successfully complete.
For example, you can set a success link so that if the first stage of LoadData is successful, the
system should proceed to the Receiving stage of Consolidation. You can set a failure link so that
if failure occurs or any problems are encountered in the LoadData stage, the system should
proceed to the Receiving stage of End, which ends the process and terminates the taskflow.
The last stage in the taskflow must have a final link with End as the target to complete the
taskflow.
You can specify conditions for a link. For example, you can add a condition for a load data task
such as LoadData_Result= =Success.
You must enter two equal signs (= =) after the variable, and place single quotation marks (')
around the condition that you are evaluating. The value can be True or False.
To add links:
1
Select Condition tab if applicable, and from Variable, select a variable, for example, LoadData_Result.
Tip: To delete a condition, click Delete.
Click Add.
Note: Ensure that the last stage in the taskflow has a link with an End target.
Editing Taskflows
After you create a taskflow, you can edit the taskflow description, and create, edit, or delete
taskflow variables. You can also add or delete a stage or a link.
To edit taskflows:
1
Select Administration, and then Taskflows, and then Manage, or expand Taskflows from the left side
navigation pane and select Manage.
From the Taskflow Listing Summary page, select the taskflow to edit and click Edit.
To add a stage, click Add Stage. See Adding Stages on page 240.
To add a link, click Add Link. See Adding Links on page 247.
To delete a stage, you must first delete all conditions from the link of the stage to be
deleted. Save the taskflow, and then click Delete.
Note: If you delete a stage, all links associated with it are also deleted.
Deleting Taskflows
You can delete a taskflow that you no longer need.
To delete taskflows:
1
Select Administration, and then Taskflows, and then Manage, or expand Taskflows from the left side
navigation pane and select Manage.
From the Taskflow Listing Summary page, select the taskflow to delete, and click Delete.
Copying Taskflows
After you define a taskflow for an application, you can copy it to a different application.
To copy taskflows:
1
Select Administration, and then Taskflows, and then Manage, or expand Taskflows from the left side
navigation pane and select Manage.
From the Taskflow Listing Summary page, select the taskflow to copy and click Save As.
Click Submit.
Shared Services adds a copy of the taskflow with a new name to the Taskflow Listing
Summary.
Select Administration, and then Taskflows, and then Manage, or expand Taskflows from the left side
navigation pane and select Manage.
From the Taskflow Listing Summary page, select the taskflow to run and click Run Now.
Manage
Execute
Select Administration, and then Taskflows, and then Manage, or expand Taskflows from the left side
navigation pane and select Manage.
From the list of taskflows, select a taskflow and click Access Control.
Select the appropriate base roles for Manage Permission Role and Execute Permission Role.
For example, select the Manage Financials TF role for the Manage Permission Role and
Execute Financials TF for the Execute Permission Role.
Click Save.
Scheduling Taskflows
You can schedule a taskflow to run automatically without creating or editing a taskflow. Schedule
Taskflow enables you to define the taskflow start time and the scheduled times for the event to
occur, based on the application server time, not the local users computer.
To schedule a taskflow:
1
Select Administration, and then Taskflows, and then Manage, or expand Taskflows from the left side
navigation pane and select Manage.
From the list of taskflows, select a taskflow and click Schedule Taskflow.
line.
d. For a recurring task, select Recurrence, and from Recurrence Pattern, select the task
frequency.
e. Select an option for the task end date and time:
No End Date
Click Save.
taskflows by status or application, or by the date or range of dates on which the taskflow was
initiated.
You can drill down on individual taskflows to view details of the taskflow. The Taskflow
Participant Summary page displays the status for each stage of the taskflow and the time that
each stage was completed. You can see the stages that were completed successfully and the stages
that failed. This information can be used to troubleshoot the task automation.
Select Administration, and then Taskflows, and then Status, or expand Taskflows from the left side
navigation pane and select Status.
Optional: To search for a taskflow, select the filter criteria, and click Search.
Figure 7
Element
Description
Status
Active
Done
Stopped
All
Application
Taskflow
Taskflow name
Element
Description
Initiated between
(optional)
Enter or select by clicking the date or range of dates in which the taskflow was initiated
Search
Click to display in the Taskflow Listing area a list of taskflows that meet the search criteria that you specify
Taskflow Listing
Displays taskflows that meet the search criteria that you specify, such as:
l
ID
Application*
Taskflow*
Initiator*
Status*
Description
*Indicates data that is sortable. You may sort taskflows by Application, Taskflow, Initiator, Started, or by Status by
clicking on the column header.
Stop
Delete
Delete All
Refresh
From the Taskflow Status Summary page, you can also stop an active taskflow, view a taskflow
participant summary, or view taskflow participant details:
l
Select Administration, and then Taskflows, and then Manage, or expand Taskflows from the left side
navigation pane and select Manage.
Optional: To filter the list, select search criteria for the taskflow, and click Search.
Select Administration, and then Taskflows, and then Status, or expand Taskflows from the left side
navigation pane and select Status.
Select the search criteria for the taskflows, and click Search.
To view all of the taskflows in theShared Services taskflow management system, select
(Status) All and click Search.
In the Taskflow Listing area, find the taskflow for which to view the participant summary and click the
taskflow ID.
Element
Description
Taskflow Summary
Summary information for the selected taskflow (items appear in the order of completion):
l
ID
Application
Taskflow
Initiator
Started
Status
Description
Participant
Stage participant name. Participants are selectable. Click a participant to view details about a taskflow
participant.
Stage Name
Stage name
Element
Description
Status
Stage status:
l
Active
Done
Stopped
All
Success Variable
Status Message
Completed
Select Administration, and then Taskflows, and then Status, or expand Taskflows from the left side
navigation pane and select Status.
Select the search criteria for the taskflows, and click Search.
To view all the taskflows in theShared Services taskflow management system, select (Status)
All and click Search.
In Taskflow Listing, find the taskflow for which to view the participant summary and click the taskflow
ID.
Oracle Hyperion Shared Services displays the Taskflow Participant Details page and sorts
the participant events chronologically.
Glossary
value flows over time and its sign behavior. Account type
options can include expense, income, asset, liability, and
equity.
total credits.
application.
asset account An account type that stores values that
outline.
consolidation The process of aggregating data from
Glossary 255
the organization.
descendant Any member below a parent in the database
256 Glossary
year-to-date values.
generation A layer in a hierarchical tree structure that defines
its parent.
Glossary 257
all accounts for periods specified in the data load file and
loads values from the data load file. If an account is not
specified in the load file, its values for the specified periods
are cleared.
review level A Process Management review status indicator
258 Glossary
Index
A
Account dimension, 18
Accumulate data load option, 47
Accumulate within File data load option, 47
active entities, 32
Active status, 115
adjustments
entering, 188
viewing in data grids, 71
alerting, 231
allocations, 76
Approved journal status, 192
approving process units, 224
auto-reversing journals, 190
B
balanced journals, 183
C
Calculate Ownership option, 117
calculating data, 91
calculation status, 62
cell adjustments in grids, 71
cell colors in grids, 68
cell descriptions, 72
cell history, 76
cell information, 71
cell text, 73
clearing data, 57
Consolidate All option, 94
Consolidate All with Data option, 93
Consolidate option, 93
consolidation
canceling, 95
effects on process management, 230
entering percentages, 90
options, 93
procedure, 94
process overview, 85
viewing progress, 95
viewing statuses, 69
consolidation method
calculations, 118
selecting, 115
contribution values, 91
copying data, 55
copying line item detail, 56
currency rates, 89
Custom dimension, 19
custom documents, 39
D
data
calculating, 91
clearing, 57
clearing from grids, 67
copying, 55
displaying , 62
editing, 66
entering, 66
extracting, 52
loading, 49
translating, 92
data file
column order, 44
creating, 43
grouping by dimension, 45
line item detail, 44
script example, 45
view, 44
Data Forms
adding members, 110
calculating data, 108
changing point of view, 107
Index 259
E
elimination detail, 89
Entity Detail Report, 78
Entity dimension, 17
equity pickup (EPU)
calculating, 131
calculation process, 132
cascading ownership, 124
cross-ownership, 127
260 Index
description, 121
direct ownership, 122
direct ownership with translation, 123
examples, 122
managing, 129
printing reports, 132
Extract Data options, 53
extracting data, 52
F
Favorites
adding, 42
managing, 42
removing, 42
FDM, accessing from data grids, 82
Financial Management
architecture, 16
dimensions, 16
help, 27
starting, 23
H
help in Financial Management, 27
I
Intercompany dimension, 18
Intercompany Reports print override options, 138
intercompany transactions
auto-match template, 161
auto-matching, 160
copying, 57
creating, 149
deleting, 170
duplicating, 155
editing, 155
extracting, 148
load files, 144
loading, 147
manually matching, 162
match code, 165
matching status, 165
posting, 167
receiving alerts, 233
sample workflow, 143
security roles for, 142
sending alerts, 232
unmatching, 166
unposting, 169
viewing, 152
invalid characters in labels and descriptions, 19
locking
data, 77
process units, 227
logging on, 23
journal groups
creating, 193
deleting, 193
journal templates
creating recurring, 184
creating standard, 183
deleting, 187
editing, 186
viewing lists of, 185
journals
approving, 197
closing periods, 187
copying and pasting cells, 196
creating, 188
creating auto-reversing, 190
deleting, 204
editing, 194
managing journal groups, 193
opening periods, 187
posting, 197
reviewing, 199
security roles, 182
status, 192
submitting, 196
unposting, 198
unsubmitting, 196
using recurring templates, 191
validating, 199
viewing lists of, 194
Manage Ownership
Calculate Ownership option, 118
changing point of view, 114
entering information, 115
overview, 113
setting display options, 114
member selection, 28
Merge data option, 46
Method account, 115
L
label requirements, 19
limitations for characters, 19
line item detail
adding, 74
viewing, 75
linked Data Forms, 107
loading data
procedure, 49
viewing load progress, 50
N
naming restrictions, 19
O
on-demand rules in data forms, 108
override options for Intercompany reports, 138
ownership management
Calculate Ownership option, 118
calculating values for, 117
changing point of view, 114
copying values, 116
entering values for, 115
setting display options, 114
system accounts, 115
P
percent consolidation
calculation, 118
entering percentages, 90
Percent Consolidation (PCON) account, 115
Percent Control (PCTRL) account, 115
percent control calculation, 117
Percent Ownership (POWN) account, 115
percent ownership calculation, 117
Period dimension, 17
periods
closing, 187
managing for journals, 187
opening, 187
Index 261
point of view
changing in Data Forms, 107
in Ownership Management, 114
saving Favorite members, 31
selecting members, 28
setting, 28
viewing active entities only, 32
viewing member properties, 31
Posted journal status, 192
posting journals, 197
preferences, setting user, 24
printing reports, 138
process control
attaching documents, 220
calculating data from, 221
calculation status summary, 215
consolidating data from, 221
data view, 211
main page, 209
options, 213
Pass/Fail status, 216
receiving alerts, 235
review level summary, 215
running equity pickup, 221
sending alerts, 233
toolbar, 215
translating data from, 221
validation detail, 217
viewing calculation status, 218
viewing journal status, 219
viewing rate data, 219
process history, viewing, 228
process levels
description, 207
displaying, 62
viewing, 70
process management
approving, 224
enabling, 205
levels, 207
locking and unlocking data, 227
overview, 205
promoting, 222
publishing, 226
rejecting, 225
security roles for, 206
signing off on, 225
262 Index
starting, 208
submitting, 223
validation, 229
viewing history, 228
process unit sign-off, 225
promoting process units, 222
proportion detail, 89
publishing process units, 226
R
rate data from process control, 219
recurring journal templates, 191
Rejected journal status, 192
rejecting
journals, 197
process units, 225
Replace by Security load option, 47
Replace data load option, 46
reports
deleting, 139
formatting, 136
opening, 136, 137
printing, 138
saving, 138
viewing intercompany transactions, 138
requirements for user-defined elements, 19
S
scale value, 62
Scenario dimension, 17
security roles
for journals, 182
for process management, 206
signing off on process units, 225
SiteMinder security, 24
standard journal templates, 183
Submitted journal status, 192
submitting
journals, 196
process units, 223
summary-level time periods, 66
suppressing data in Data Forms, 109
T
task automation
overview, 237
prerequisites, 238
task lists
creating, 40
deleting, 42
editing, 41
taskflows
adding links, 247
copying, 248
creating, 239
creating stages, 240
deleting, 248
editing, 248
managing, 238
parameters for Financial Management, 242
participant details, 254
running manually, 249
scheduling, 250
stopping, 252
viewing, 239
viewing status, 250
templates
creating recurring journal templates, 184
creating standard journal, 183
deleting journal templates, 187
editing journal templates, 186
using recurring journal templates, 191
transactions
consolidation, 77
intercompany, 82
translating data, 92
translation
entering currency rates, 89
process, 88
running logic, 92
W
Working journal status, 192
Y
Year dimension, 17
Z
zero values
in Data Forms, 109
in data grids, 62
U
unbalanced journals, 183
unlocking
data, 77
process units, 227
unsubmitting journals, 196
user preferences, 24
user-defined element requirements, 19
V
validation
Index 263
264 Index