Administering Financial Consolidation and Close · 2020-03-03 · Contents Documentation Accessibility Documentation Feedback 1 Financial Consolidation and Close Overview Overview

Oracle® CloudAdministering Financial Consolidation andClose

E93973-22

Oracle Cloud Administering Financial Consolidation and Close,

E93973-22

Copyright © 2016, 2020, Oracle and/or its affiliates.

Primary Author: EPM Information Development Team

This software and related documentation are provided under a license agreement containing restrictions onuse and disclosure and are protected by intellectual property laws. Except as expressly permitted in yourlicense agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify,license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means.Reverse engineering, disassembly, or decompilation of this software, unless required by law forinteroperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. Ifyou find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it onbehalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software,any programs embedded, installed or activated on delivered hardware, and modifications of such programs)and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government endusers are "commercial computer software" or “commercial computer software documentation” pursuant to theapplicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use,reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/oradaptation of i) Oracle programs (including any operating system, integrated software, any programsembedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oraclecomputer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in thelicense contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloudservices are defined by the applicable contract for such services. No other rights are granted to the U.S.Government.

This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications thatmay create a risk of personal injury. If you use this software or hardware in dangerous applications, then youshall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure itssafe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of thissoftware or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks oftheir respective owners.

Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks areused under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc,and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registeredtrademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products,and services from third parties. Oracle Corporation and its affiliates are not responsible for and expresslydisclaim all warranties of any kind with respect to third-party content, products, and services unless otherwiseset forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not beresponsible for any loss, costs, or damages incurred due to your access to or use of third-party content,products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Documentation Accessibility

Documentation Feedback

1 Financial Consolidation and Close Overview

Overview of the Home Page 1-1

Integrating with Other Services 1-3

2 Creating an Financial Consolidation and Close Application

Application Prerequisites 2-1

Workflow for Creating an Application 2-1

Creating an Application 2-1

Enabling Application Features 2-3

Application Feature Descriptions 2-4

Consolidation and Supplemental Data Features 2-8

Enabling Ownership Management in Applications 2-9

Migrating Net Income Data 2-15

Creating Extended Dimension Applications 2-17

3 Managing Security

Security Overview 3-1

Managing Artifact and Data Access 3-2

Assigning User Access to Artifacts 3-3

Assigning User Access to Data 3-3

Enabling or Disabling Security for Dimensions 3-4

Assigning Security to Dimension Members 3-4

Data Source Dimension Security 3-6

Managing Forms Security 3-6

Assigning Access to Forms and Folders 3-7

iii

Default Form Security 3-8

4 Managing Applications

Application Overview 4-1

Restrictions for Dimensions, Members, Aliases, and Forms 4-2

Managing Dimensions 4-5

Importing Metadata 4-6

Creating the Metadata Import File 4-6

Example: Entity Dimension Import File 4-6

Other Supported Delimiter Characters 4-7

Loading the Metadata Import File 4-9

Exporting Metadata 4-10

Validating Metadata 4-11

Metadata Validation Messages 4-12

Importing Data 4-17

Creating the Data Import File 4-17

Data Import File Format 4-17

Example: Data Import File - Periodic View 4-18

Example: Data Import File - YTD View 4-18

Example: Data Import File - YTD Input and Replace Mode 4-19

Example: Data Import File - Overrides 4-20

Example: Data Import File - Exchange Rates 4-20

Load Methods 4-21

Load Method Examples 4-22

Loading the Data Import File 4-24

Exporting Data 4-25

Viewing Data Import and Export Status 4-26

Importing Data Using Data Management 4-26

Exporting Data Using Data Management 4-27

Data Integrations 4-28

Copying Data 4-28

Clearing Data 4-30

Refreshing the Database 4-31

Restructuring Cubes 4-32

Removing an Application 4-34

Scheduling Maintenance 4-34

Using the Inbox/Outbox 4-34

Working with Activity Reports and Access Logs 4-35

iv

5 Managing Application and System Settings

Specifying Application Settings 5-1

Specifying a Default Alias Table, and Setting Member and Alias Display Options 5-5

Specifying Number Formatting Preferences 5-5

Defining User Variables 5-6

Customizing Your Application Appearance 5-7

Making Announcements 5-7

Specifying Artifact Labels 5-8

Working With the Artifact Labels Grid 5-8

Adding Languages and Defining Localized Artifact Labels 5-9

Exporting and Importing Artifact Labels for Editing 5-9

Reviewing Artifacts 5-10

6 Connecting Subscriptions in EPM Cloud

About Connecting EPM Cloud Subscriptions 6-1

Considerations When Migrating Cross-Subscription Connections 6-3

Creating, Editing, and Deleting Connections to Other EPM Cloud Subscriptions 6-3

Common Connection Errors and Resolutions 6-5

Navigating Across EPM Cloud Subscriptions 6-6

Customizing Navigation Flows to Access Other EPM Cloud Subscriptions 6-6

Grouping Cards from Other EPM Cloud Subscriptions into Clusters 6-7

Configuring Cards with Tabs from Multiple EPM Cloud Subscriptions 6-10

7 Designing Custom Navigation Flows

Understanding Navigation Flows 7-1

What Can Be Customized in the Application Interface? 7-1

Navigation Flow Customization Categories 7-2

Navigation Flow Permissions 7-2

Predefined Navigation Flows 7-2

Viewing and Working with Navigation Flows 7-3

Creating and Duplicating Navigation Flows 7-4

Editing a Navigation Flow 7-4

Activating and Deactivating Navigation Flows 7-5

Customizing Labels for Cards, Tabs, and Clusters 7-6

Customizing Icons for Cards and Vertical Tabs 7-7

Hiding and Unhiding Cards and Tabs 7-7

Changing the Display Order of Cards on the Home Page 7-8

Adding Cards 7-8

Adding Tabs to a Tabular Page 7-9

v

Removing Navigation Flows, Cards, and Tabs 7-10

Grouping Cards into Clusters 7-11

Reloading a Navigation Flow 7-12

Switching Navigation Flows at Runtime 7-13

Why Is My Referenced Card, Tab, or Cluster Not Visible? 7-14

8 Designing Infolets

About Infolets 8-1

Anatomy of an Infolet 8-3

Determining Infolet Content 8-6

Designing Forms for Infolets 8-7

Designing Charts for Infolets 8-7

Using the Infolets Designer 8-8

Creating Infolets 8-10

Working with Infolets 8-11

Customizing the Application Interface to Access Infolets 8-12

9 Designing Financial Dashboards

Designing Dashboards 9-1

About Your Dashboard's Layout 9-3

About the Gauge Chart Type 9-3

About the Tile Chart Type 9-5

Customizing Dashboard Colors 9-7

Setting Line Width in Line and Combination Charts 9-7

About Global and Local POVs 9-8

Dashboard POVs and Valid Intersections 9-10

10

Working with Dimensions

Dimensions Overview 10-1

Account 10-2

Period 10-2

Data Source 10-3

Consolidation 10-4

Currency 10-5

Entity 10-5

Intercompany 10-5

Movement 10-6

Scenario 10-8

Year 10-8

vi

View 10-8

Multi-GAAP 10-8

Viewing and Editing Dimensions 10-9

Working with Dimension Hierarchies 10-9

Expanding and Collapsing Dimension Hierarchies 10-10

Navigating Dimension Hierarchies 10-10

Finding Dimensions or Members 10-10

Sorting Members 10-11

Moving Members Within the Dimension Hierarchy 10-11

Viewing a Member’s Ancestors 10-12

Showing Member Usage 10-12

Adding Custom Dimensions 10-12

Aggregation Options 10-13

Data Storage Options 10-14

About Dynamic Calc 10-14

Store Data Storage 10-15

Shared Data Storage 10-15

Never Share Data Storage 10-15

Label Only Data Storage 10-15

Setting Dimension Properties 10-15

Setting Dimension Evaluation Order 10-16

Using Extended Dimensionality 10-17

Defining Accounts 10-18

Account Types 10-21

Time Balance Property 10-22

Summary of Account Types and Time Balance 10-22

Aggregation (Consolidation Operator) 10-23

Account Types and Variance Reporting 10-24

Saved Assumptions 10-25

Data Types and Exchange Rate Types 10-25

Defining Account Properties 10-25

Setting Account Attribute Values 10-28

Defining Entity Members 10-30

Intercompany Property for Entities 10-30

Base Currency 10-31

Creating Alternate Hierarchies 10-31

Financial Consolidation and Close Data Model Overview 10-33

Working with Members 10-34

Seeded Dimension Members 10-34

Built-in Calculations 10-46

Dynamic Members 10-49

vii

Adding or Editing Members 10-49

Deleting Members 10-52

Deleting Parent Members 10-53

Viewing Member Properties from Forms 10-53

Working with Shared Members 10-53

Creating Shared Members 10-54

Setting Up Currencies 10-55

Working with Multiple Currencies 10-56

Scaling 10-57

Number Formatting 10-57

Viewing Currency Usage 10-57

Creating Currencies 10-58

Editing Currencies 10-59

Deleting Currencies 10-60

Setting Up Scenarios 10-60

About Scenarios 10-60

Time Periods 10-60

Access Permissions 10-61

Creating Scenarios 10-61

Editing Scenarios 10-61

Deleting Scenarios 10-62

Copying Scenarios 10-62

Customizing Application Years 10-63

Adding Years to the Calendar 10-63

Editing Year Information 10-63

Working with Attributes 10-64

Understanding Attribute Data Types 10-64

Deleting Attributes 10-65

Working with Attribute Values 10-65

Creating Attribute Values 10-65

Assigning Attribute Values to Members 10-66

Modifying Attribute Values 10-67

Deleting Attribute Values 10-67

Working with User-Defined Attributes (UDAs) 10-68

Creating UDAs 10-68

Changing UDAs 10-68

Deleting UDAs 10-69

Working with Member Formulas 10-69

Viewing Details of Formula Verification 10-70

Working with Alias Tables 10-70

About Alias Tables 10-70

viii

Creating Alias Tables 10-70

Editing or Renaming Alias Tables 10-71

Deleting Alias Tables 10-71

Clearing Alias Tables 10-71

Copying Alias Tables 10-72

11

Editing Dimensions in the Simplified Dimension Editor

About Editing Dimensions in the Simplified Dimension Editor 11-1

Accessing the Simplified Dimension Editor 11-2

Working with the Simplified Dimension Editor Grid 11-2

Switching to Another Dimension 11-2

Customizing the Column Layout 11-2

Viewing Ancestors 11-3

Showing Member Usage in an Application 11-3

Focusing Your Editing 11-4

Finding Members 11-4

Sorting Members 11-4

Moving Members to Another Hierarchy 11-5

Working with Member Formulas 11-5

Copying Member Names from Microsoft Excel 11-6

Editing Dimension Properties in the Simplified Dimension Editor 11-6

Editing Member Properties in the Simplified Dimension Editor 11-8

Adding Members in the Simplified Dimension Editor 11-18

Editing Members in the Simplified Dimension Editor 11-18

Deleting Members in the Simplified Dimension Editor 11-19

Adding Shared Members in the Simplified Dimension Editor 11-20

12

Managing Jobs

Jobs Overview 12-1

Viewing Pending Jobs and Recent Activity 12-1

Scheduling Jobs 12-2

Editing and Deleting Jobs 12-4

13

Auditing Tasks and Data

Configuring Audit Tasks 13-1

Auditing Information Overview 13-1

Viewing Audit Details 13-2

ix

Viewing Task Manager Audit Details 13-4

14

Defining Valid Intersections

Understanding Valid Intersections 14-1

Valid Intersection Groups 14-1

Valid Intersection Rules 14-1

Anchor and Nonanchor Dimensions 14-2

Valid Intersection Examples 14-3

Example: Anchor and Nonanchor Dimensions 14-3

Example: Required Dimension 14-4

Example: Unselected Members are Valid 14-4

Example: Redundant or Overlapping Valid Intersection Rules Within theSame Valid Intersection Group 14-5

Example: Redundant or Overlapping Valid Intersection Rules in DifferentValid Intersection Groups 14-5

Redundancy or Overlap in Valid Intersection Rules 14-6

Shared Members and Valid Intersection Rules 14-6

Substitution Variables and Valid Intersection Rules 14-6

Evaluation Order 14-6

Creating Valid Intersections 14-7

Managing Valid Intersections 14-8

Viewing Valid Intersections 14-8

Changing the Valid Intersection Group Evaluation Order 14-8

Disabling and Enabling Valid Intersection Groups 14-9

Editing Details for a Valid Intersection Group 14-9

Duplicating Valid Intersection Groups 14-10

Deleting a Valid Intersection Group 14-10

Suppressing Invalid Data in Forms 14-10

Working with Valid Intersections in Forms 14-11

Managing Invalid Intersection Reports 14-12

Creating an Invalid Intersection Report 14-13

Editing an Invalid Intersection Report 14-13

Duplicating an Invalid Intersection Report 14-14

Running an Invalid Intersection Report 14-14

Deleting an Invalid Intersection Report 14-14

15

Managing Forms

Predefined Forms 15-1

Form Components 15-3

Point of View 15-4

x

Page Axis 15-4

Rows and Columns 15-4

Form Design Considerations 15-4

Forms and Access Permissions 15-4

Forms and Currencies 15-5

Forms and Versions 15-5

Forms and Attributes 15-5

Forms and Shared Members 15-5

Forms and Calculations 15-5

Creating Simple Forms 15-5

Setting Form Layout 15-6

Setting Form Grid Properties 15-8

Setting Form Dimension Properties 15-9

Setting Display Properties 15-10

Setting Printing Options 15-11

Including Data Validation Rules in Forms 15-12

Setting Form Precision and Other Options 15-14

Creating Asymmetric Rows and Columns 15-15

Adding Formula Rows and Columns 15-15

Defining Simple Form Page and Point of View 15-16

Creating Composite Forms 15-17

Setting Composite Form Layout 15-17

Adding Simple Forms to a Composite Form Layout 15-18

Rearranging Forms in the Layout 15-19

Editing Simple Forms from within a Composite Form 15-19

Deleting Simple Forms from a Composite Form 15-19

Setting Composite Form Section Properties 15-19

Setting Composite Form Point of View and Page Dimensions 15-21

Creating Master Composite Forms 15-21

Embedding Charts in Composite Forms 15-22

Working with Forms and Form Components 15-24

Opening Forms 15-24

Previewing Forms 15-24

Editing Forms 15-25

Editing Simple Forms 15-25

Editing Composite Forms 15-25

Moving, Deleting, and Renaming Forms 15-26

Working with Substitution Variables 15-26

About Substitution Variables 15-26

Creating and Assigning Values to Substitution Variables 15-27

Deleting Substitution Variables 15-27

xi

Working with User Variables 15-27

About User Variables 15-27

Managing User Variables 15-27

Creating User Variables 15-28

Deleting User Variables 15-28

Working with Smart Lists 15-29

Synchronizing Smart Lists in Reporting Applications 15-29

Adding or Changing Smart List Properties 15-30

Adding or Changing Smart List Entries 15-31

Previewing Smart Lists 15-32

Displaying #MISSING with Smart Lists 15-32

16

Managing Journals

Creating Journal Groups 16-1

Deleting Journal Groups 16-1

Managing Journal Periods 16-2

Setting Journal Options 16-2

Journal Referential Integrity 16-3

17

Consolidating Data

Consolidation Process 17-2

Data Flow 17-2

Consolidation Process Flow 17-5

Intercompany Eliminations 17-10

Consolidation Dimension 17-14

Translation Process 17-15

Translating Data 17-16

About Exchange Rates 17-18

Entering Exchange Rates 17-19

Entering Override Rates 17-20

Specifying Default Translation Settings 17-21

Consolidation and Translation Security Access 17-22

Calculation Status 17-23

Consolidating Data 17-25

Viewing Consolidation Progress 17-26

Running a Consolidation Report 17-27

Consolidation Examples 17-30

Example 1: Reconsolidating Data from a Form 17-30

Example 2: Consolidating Data from the Data Status Grid 17-31

xii

Example 3: Consolidating Data for Multiple Periods 17-31

Advanced Consolidation Overview 17-31

Consolidation Logic 17-32

Managing Consolidation Methods 17-32

Modifying Consolidation Methods 17-34

Adding Consolidation Methods 17-35

Importing and Exporting Consolidation Methods 17-36

Recomputing Ownership Data 17-38

Managing Ownership 17-38

Changing Manage Ownership Settings 17-39

Importing and Exporting Ownership Data 17-41

Ownership Settings Year to Year 17-43

Ownership Settings in Forms and Configurable Calculation Rules 17-44

Advanced Consolidation Rules 17-46

About Configurable Consolidation Rules 17-48

Managing Consolidation Rule-sets and Rules 17-52

Creating Consolidation Rule-sets 17-52

Creating Consolidation Rules 17-57

Consolidation Strings 17-61

Viewing Rule-Sets 17-62

Deploying and Undeploying Rule-Sets 17-63

Duplicating and Deleting Rule-Sets 17-64

Seeded Consolidation Rules 17-64

Investment Rule-Set 17-66

Investment PP Rule-Set 17-67

Owner's Equity (Subsidiary/Proportional) Rule-Set 17-68

Owner's Equity (Subsidiary/Proportional) PP Rule-Set 17-70

Owner's Equity (Equity) Rule-Set 17-73

Owner's Equity (Equity) PP Rule-Set 17-75

Owner's Equity (Holding) Rule-Set 17-76

Net Income (Subsidiary) Rule-Set 17-77

Net Income (Equity) Rule-Set 17-78

Seeded Consolidation Rule Examples 17-80

Seeded Consolidation Rules - Example (January) 17-80

Seeded Consolidation Rules - Example (February) 17-83

Seeded Consolidation Rules - Example (March) 17-91

18

Working with Rules

Consolidation and Translation Rules 18-1

Selecting Business Rules 18-2

xiii

Assigning Access to Rules 18-3

Working with Override Translation Rules 18-3

Creating Override Translation Rules 18-7

Deploying Override Translation Rules 18-8

Creating Rate Accounts for Translation Overrides 18-9

Editing User-Defined Rate Accounts 18-10

Deleting User-Defined Rate Accounts 18-11

Working with Configurable Calculations 18-11

Creating Configurable Calculations 18-12

Enabling Auto Create Blocks for Configurable Calculations 18-14

Configurable Calculation Rules 18-15

System Calculations 18-25

System Calculation Option for Custom Dimension Top Member 18-26

Opening Balance Carry Forward 18-27

Opening Balance Override Rules 18-28

Balance the Balance Sheet Calculation 18-30

Ratio Calculation 18-31

Working within Calculation Manager 18-32

Working with Essbase Calc Script 18-33

Supported Essbase Functions 18-40

Configurable Calculations Best Practices 18-47

Best Practices for Calculations in Extended Dimensionality Applications 18-58

Equity Pickup Overview 18-62

Enabling Equity Pickup 18-64

Equity Pickup Processing 18-71

Working with On-Demand Rules 18-75

Guidelines for On-Demand Rules 18-76

Creating On-Demand Rules 18-78

Adding On-Demand Rules to Data Forms 18-79

Importing and Exporting On Demand Rules 18-81

Launching On-Demand Rules 18-81

Calculation Status for On-Demand Rules 18-83

Renaming On-Demand Rules 18-84

Deleting On-Demand Rules 18-84

19

Managing Approval Unit Hierarchies

Creating Approval Unit Hierarchies 19-1

Setting Up the Approval Unit Hierarchy 19-2

Selecting Approval Unit Hierarchy Members 19-3

Assigning Approval Unit Owners and Reviewers 19-4

xiv

Assigning Approval Unit Hierarchies to Scenarios 19-5

Editing Approval Unit Hierarchies 19-6

Viewing Approval Unit Hierarchy Usage 19-7

Synchronizing Approval Unit Hierarchies 19-7

Deleting and Renaming Approval Unit Hierarchies 19-8

Exporting Approval Unit Hierarchies 19-9

Importing Approval Unit Hierarchies 19-9

20

Managing the Approval Process

Approval Process Overview 20-1

Enabling Approvals 20-1

Starting the Approval Process 20-2

Approval Unit Promotional Path 20-3

Creating Approval Unit Annotation Reports 20-4

Creating Approval Status Reports 20-4

Data Validation Rules 20-5

Locking and Unlocking Entities 20-6

21

Setting Up Task Manager

Task Manager Terms 21-1

Task Manager Overview 21-2

Sample Task Flows 21-3

Managing Task Manager System Settings 21-4

Managing Global Integration Tokens 21-4

Creating a Global Integration Token 21-5

Deleting a Token 21-6

Managing Task Manager Organizational Units 21-6

Adding Organizational Units 21-6

Importing Organizational Units 21-7

Selecting an Organizational Unit 21-8

Managing Holiday Rules for Tasks 21-8

Creating Holiday Rules 21-8

Applying a Holiday Rule to an Organizational Unit 21-9

Applying a Holiday Rule to a Schedule Template 21-9

Importing Holiday Dates 21-10

Editing Holiday Rules 21-10

Duplicating Holiday Rules 21-11

Deleting Holiday Rules 21-11

Changing Configuration Settings 21-11

xv

Allowing Comment Deletions 21-11

Allowing Task Deletions 21-12

Displaying Upcoming Tasks 21-12

Approver Levels 21-12

Enabling Email Notifications in Task Manager 21-13

Reopening Tasks 21-13

Specifying Task Display in Smart View 21-14

Setting the Task Attachment Size 21-14

Allowing Reassignment Request Approvals 21-15

Managing Task Manager Attributes 21-15

Defining Task Manager Attributes 21-16

Defining Calculation Attributes 21-17

Importing List Attributes 21-20

Editing Attributes 21-21

Duplicating Attributes 21-21

Deleting Attributes 21-21

Viewing Attributes 21-22

Searching for Attributes 21-22

Managing Alert Types 21-22

Creating Alert Types 21-23

Editing Alert Types 21-23

Viewing Alert Types 21-23

Searching for Alert Types 21-24

Deleting Alert Types 21-24

22

Managing Teams for Task Manager

Adding Teams and Members for Task Manager 22-1

Editing Teams and Members for Task Manager 22-2

Deleting Teams and Removing Members 22-2

Managing Backup Assignments 22-3

Requesting a Reassignment in Task Manager 22-3

23

Managing Task Types

Task Types 23-1

Creating Task Types 23-2

Setting Task Type Properties 23-2

Setting Task Type Parameters 23-3

Specifying Task Type Instructions 23-3

Specifying Task Type Questions 23-4

xvi

Assigning Task Type Attributes 23-6

Working With Task Type Rules 23-7

Viewing Task Type History 23-8

Editing Task Types 23-9

Viewing Task Types 23-9

Searching for Task Types 23-10

Importing Task Types 23-10

Exporting Task Types 23-11

Deleting Task Types 23-12

24

Managing Task Templates

Creating Task Templates 24-1

Setting Template Properties 24-2

Specifying Template Instructions 24-3

Assigning Viewers to Templates 24-4

Applying Template Attributes 24-5

Specifying Day Labels 24-5

Embedding Templates 24-6

Working With Template Rules 24-7

Viewing Template History 24-9

Opening Templates 24-9

Adding Tasks to Templates 24-10

Editing Templates 24-10

Importing Tasks into Templates 24-11

Task Import File Format 24-12

Exporting Tasks to Microsoft Excel 24-15

Reassigning Users in Templates 24-15

Creating Schedules from Templates 24-16

Manually Validating Templates 24-18

Viewing Task Manager Templates 24-19

Searching for Templates 24-19

Deleting Templates 24-20

25

Managing Tasks

Creating Tasks 25-1

Setting Task Properties 25-2

Setting Task Parameters 25-3

Specifying Task Instructions 25-4

Selecting the Workflow 25-5

xvii

Adding Task Questions 25-7

Setting Task Access 25-9

Setting Task Predecessors 25-10

Applying Task Attributes 25-11

Working With Task Rules 25-12

Viewing Task History 25-13

Working with the Task Dialog Box 25-14

Importing and Exporting Tasks 25-15

Editing Tasks 25-16

Adding Attachments 25-17

Sorting Tasks 25-17

Searching for Tasks 25-17

Moving Tasks 25-18

Cutting, Copying, and Pasting Tasks 25-18

Reopening Tasks 25-19

Submitting Tasks 25-19

Approving or Rejecting Tasks 25-19

Managing Task Reassignments 25-20

Aborting Tasks 25-20

Deleting Tasks 25-20

26

Managing Schedules

Manually Creating Schedules 26-1

Setting Schedule Properties 26-2

Adding Instructions to Schedules 26-3

Assigning Schedule Viewers 26-4

Applying Schedule Attributes 26-5

Adding Day Labels 26-5

Working With Schedule Rules 26-6

Setting Required Task Parameters 26-7

Opening Schedules 26-7

Editing Schedules 26-8

Adding Tasks to Schedules 26-8

Importing Tasks into Schedules 26-8

Updating Tasks in Schedules 26-10

Reassigning Users in Schedules 26-11

Setting Schedule Status 26-12

Viewing Schedule History 26-13

Validating Schedules 26-13

Locking Schedules 26-14

xviii

Viewing Schedules 26-14

Searching for Schedules 26-14

Deleting Schedules 26-15

27

Managing Task Manager Integrations

Creating Integrations 27-1

Setting Integration Properties 27-2

Setting Integration Parameters 27-3

Editing Integrations 27-3

Validating Integrations 27-4

Deleting Integrations 27-5

Managing Connections 27-5

Adding Connections 27-5

Editing Connections 27-6

Deleting Connections 27-6

Viewing Integrations 27-7

Searching for Integrations 27-7

Creating Custom Task Manager Integrations 27-8

Creating Custom Process Automation Integrations 27-8

Creating Custom Event Monitoring Integrations 27-12

28

Using Task Manager and Supplemental Data Manager Reports

Generating Custom Reports for Task Manager and Supplemental Data Manager 28-1

Creating a Task Manager Query 28-2

Creating a Supplemental Data Query 28-6

Creating a Template 28-9

Setting Up a Report Group 28-10

Creating a Report 28-11

Generating the Report 28-12

Using Task Manager Report Binders 28-13

Generating Report Binders 28-13

Viewing Report Binders 28-14

29

Managing Supplemental Data

Supplemental Data Process Overview 29-1

Managing Supplemental Data System Settings 29-3

Setting Email Notifications in Supplemental Data Manager 29-3

Setting Preferences for Supplemental Data 29-4

Setting Supplemental Data Governors 29-4

xix

Working with the Data Set Dashboard 29-5

Managing Dimension Attributes in Supplemental Data Manager 29-6

Adding Dimension Attributes 29-6

Editing Dimension Attributes 29-7

Deleting Dimension Attributes 29-7

Working with Data Sets 29-8

Creating Data Sets 29-8

Adding Data Set Attributes 29-9

Importing Data Set List Attributes 29-16

Viewing Data Set History 29-17

Deleting Data Set Attributes 29-17

Editing Data Sets 29-17

Copying Data Sets 29-18

Deleting Data Sets 29-18

Creating Supplemental Data Manager Form Templates 29-18

Specifying Form Template Instructions 29-19

Working with Supplemental Data Manager Form Sections 29-20

Form Template Sections: Columns Tab 29-21

Form Template Sections: Group By Tab 29-22

Form Template Sections: Mapping Tab 29-23

Form Template Sections: History Tab 29-24

Assigning the Workflow 29-24

Specifying Form Template Questions 29-25

Setting Form Template Access 29-26

Viewing Form Template History 29-27

Editing Form Templates 29-27

Duplicating Form Templates 29-27

Deleting Form Templates 29-28

Deploying a Form Template to a Data Collection Period 29-28

Un-Deploying a Form Template to a Data Collection Period 29-29

Re-opening Supplemental Data Forms 29-30

Validating Supplemental Data Total Against an Account Balance 29-30

Managing Data Collection Workflow 29-32

Working with Supplemental Data in Smart View 29-32

Using Currency Translation 29-34

Selecting Default Currency for Entity Members 29-35

Setting Up Currency Attributes for Translation 29-35

xx

30

Managing Supplemental Data Manager Teams

Adding Teams and Members for Supplemental Data Manager 30-1

Importing and Exporting Teams and Members for Supplemental Data Manager 30-2

Exporting Supplemental Data Manager Users 30-4

Editing Teams and Members for Supplemental Data Manager 30-4

Deleting Teams and Removing Members for Supplemental Data Manager 30-5

A Task Manager Integrations with EPM Cloud Services

Setting Up an Integration A-1

Uploading and Downloading Files Within EPM Services A-2

Pre-Built EPM Cloud Integrations A-3

End User Integrations for EPM Cloud A-16

B Task Manager Integrations with Cloud and On-PremisesApplications

End User Integrations for Oracle Fusion Cloud B-1

Event Monitoring Integration Tasks for Oracle Fusion General Ledger B-5

End User Integrations for On-Premises Applications B-5

Setting Up an Integration B-13

On-Premises Oracle E-Business Suite (EBS) Integration B-16

C Financial Consolidation and Close Best Practices

xxi


For information about Oracle's commitment to accessibility, visit the OracleAccessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic supportthrough My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trsif you are hearing impaired.


xxii

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs

Documentation Feedback

To provide feedback on this documentation, send email to [email protected],or, in an Oracle Help Center topic, click the Feedback button located beneath theTable of Contents (you may need to scroll down to see the button).

Follow EPM Information Development on these social media sites:

LinkedIn - http://www.linkedin.com/groups?gid=3127051&goback=.gmp_3127051

Twitter - http://twitter.com/hyperionepminfo

Facebook - http://www.facebook.com/pages/Hyperion-EPM-Info/102682103112642

YouTube - https://www.youtube.com/oracleepminthecloud

xxiii

http://www.linkedin.com/groups?gid=3127051&goback=.gmp_3127051

http://twitter.com/hyperionepminfo

http://www.facebook.com/pages/Hyperion-EPM-Info/102682103112642

https://www.youtube.com/oracleepminthecloud

1Financial Consolidation and CloseOverview

Financial Consolidation and Close is a subscription-based consolidation and reportingsolution built for and deployed on Oracle Cloud.

Financial Consolidation and Close is a subscription-based consolidation and reportingsolution built for and deployed on Oracle Cloud. It provides a simple and quickdeployment for users who want fast implementation with no hardware and minimal ITsupport. It provides a user-friendly and intuitive interface along with built-infunctionality for consolidation and close process tasks.

Note:

This guide is designed for administrators implementing and maintaining theFinancial Consolidation and Close application.

Financial Consolidation and Close provides these features:

• Simplified tablet user interface

• Native dashboarding and analysis

• Predefined dimensions for detailed analysis

• Flexible application configuration with pre-built forms and reports

• Currency translations and FX adjustment calculations

• Automated cash flow

• Dynamic out-of-box calculations with limited need for customization

• Simplified Consolidation dimension for easy audit

• Business process task management and workflow

• Supplemental schedule data management

Watch the following video for a feature overview:

Getting Started

Overview of the Home PageWhen you first access Financial Consolidation and Close, the Home page provideseasy access to features. Depending on your application features and security roleaccess, you may see all or only some of these features.

1-1

https://apexapps.oracle.com/pls/apex/f?p=44785:265:0:::265:P265_CONTENT_ID:13514

Table 1-1 Overview of the Home Page

Feature Description

Navigator menu Link to advanced settings and administrativetasks, including managing alias tables,dimensions, close tasks, supplemental data,and Data Management.

Home icon Return to the Home page

Announcements panel Displays general announcements from theService Administrator

Tasks summary panel Displays a summary of tasks assigned to youby status.You can access all the tasks that are Open,Late tasks that are currently overdue, tasksscheduled for Today, or tasks due in 7 days.Selecting any link opens the Tasks page.

Tour Links to a product overview video of FinancialConsolidation and Close.

Product Tour

Dashboards View metrics and work with data on CloseOverview, Compliance, and Financialsdashboards. Dashboards are displayed if youhave access to at least one of the dashboards.

Tasks View tasks, complete required taskprocedures, and submit tasks. If you are auser, you will only see your tasks.

Data Enter and review data through simple forms,composite forms, and ad hoc forms.

Chapter 1Overview of the Home Page

1-2

https://apexapps.oracle.com/pls/apex/f?p=44785:24:3489605642766::NO:24:P24_CONTENT_ID,P24_PREV_PAGE:13307,1

Table 1-1 (Cont.) Overview of the Home Page

Feature Description

Journals Create and manage journals, journal groupsand templates, and perform all journal actions.

Reports Create and run Intercompany, Journal, TaskManager, and Financial Reporting reports.

Approvals View approval unit status and performapproval unit actions such as submit, approveand reject data.

Rules Manage, assign permission for, and launchrules.

Application • Manage applications• Import and export data• Import and export metadata• Access the consolidation flow• Access Task Manager• Access Supplemental Data• View job status and activity• Schedule jobs• Specify the default translation settings• Manage valid intersections• Run invalid intersection reports• Configure features• Configure service options - manage email

notifications, synchronize users, andprocess supplemental data forms

• Manage periods• Specify application settings

Tools • Set up user variables• Customize your application appearance• Create announcements• Edit navigation flows in application

structure• Edit artifact labels• Set maintenance time• Create notifications• Configure and view audit information• Manage migration tasks• Access additional security options,

including Group Management andProvisioning, and view Provisioning andSecurity Audit reports

Academy Link to videos and documentation

Integrating with Other ServicesFinancial Consolidation and Close integrates with Financial Reporting Web Studio,EPM Automate, Data Management, Oracle Smart View for Office, Task Manager, andSupplemental Data Manager. These integrations make your consolidation andbusinesss processes more effective and efficient.

Chapter 1Integrating with Other Services

1-3

Watch the following video for information about other services:

Integrating with Other Services

Financial Reporting Web Studio

Use Financial Reporting Web Studio to build highly-formatted and book-qualityproduction and financial management reports. You access financial reports from theNavigator menu. You can make changes to a report and when you finish editing it, youcan run it from the Reports list on the Home screen. You can run reports in HTML orPDF format.

EPM Automate

EPM Automate is a command-line utility that Service Administrators can use toschedule jobs such as importing and exporting data and metadata from an application,or executing business rules. You access EPM Automate from the Navigator menu, andthen execute commands from a command prompt.

Data Management

You use Data Management to integrate data from an enterprise resource planningsource system to an enterprise performance management target system. You accessData Management through the Navigator menu. From the Setup tab, you create importformats, locations, and mappings, and establish your source and target systems. Fromthe Workflow tab, you execute data integrations.

Smart View

Use Smart View to integrate with Microsoft Office applications such as Excel, Word,and PowerPoint. You install it from the Download menu. If you want to edit yourdimensions in Smart View, you can also download the add-on for Administrators. Afteryou install Smart View, you can access your data directly in an Office application. Forexample, you can open data forms directly in Excel.

Task Manager

Use Task Manager to define your templates, schedules, and tasks. You can specifybasic properties about a template or task, such as the name and period, as well asinstructions, attributes, labels, and rules.

Supplemental Data Manager

Supplemental Data Manager enables you to ad a greater level of granularity to yourapplication. You can use it to set up your dimensions, data sets, and form templates.When you finish editing a form template, you can access the form from your Tasksmenu. You can also view supplemental data in Dashboards.

Chapter 1Integrating with Other Services

1-4


2Creating an Financial Consolidation andClose Application

An application is a set of related dimensions and dimension members that are used tomeet a set of consolidation and close process needs. Each application has its ownaccounts, entities, scenarios, and other data elements.

Application Prerequisites• After analyzing available historical data, you have created a set of requirements

and developed an application design that supports your requirements.

• Security components have been set up. See "Managing Users and Roles" in theGetting Started with Oracle Enterprise Performance Management Cloud forAdministrators guide.

• At least one user is granted the Service Administrator role of the service instance.

Workflow for Creating an ApplicationTable 2-1 Workflow to Create an Application

Task Description More Information

Create application structure Create an application. See Creating an Application.

Load metadata and refresh theapplication

Load dimensions and their membersinto the application from load files.

See Importing Metadata.

Load data Load data from a flat file. See Importing Data.

Set up forms folders and forms Create forms folders and forms andspecify who can access them. Usersuse forms to view or enterapplication data.

See Managing Forms.

Set up task lists and tasks Create task lists and tasks, andspecify who can access them.

See Managing Tasks.

Create reports Design and develop reports thatdisplay the data available in theapplication.

See the Building Reports topic inDesigning with Financial ReportingStudio for Oracle EnterprisePerformance Management Cloud.

Creating an ApplicationFinancial Consolidation and Close is a multi-dimensional consolidation application. Bydefault, the system provides a required set of pre-defined dimensions to store theconsolidation detail data. During application creation and configuration, you can selectadditional optional dimensions based on your application needs.

2-1

Before you create your application, you can click Take a quick tour to access usefulinformation about designing and getting started with the application.

To create an application, you must be the Service Administrator.

After you create an application, you cannot rename it. For example, you cannotrename your "xxx" Test application to "xxx" in Production. You must recreate andrebuild your application.

To create an application:

1. Log on to Financial Consolidation and Close as a Service Administrator.

2. Under Finance, click Start.

3. Click Financial Close.

4. Click New.

5. On the Create Application: General page, enter a Name for the application.

The Application name cannot contain these characters:

Ampersand (&), Apostrophe (‘), Asterisk (*), At sign (@), Backslash (\), Caret (^),Colon (:), Comma (,), Curly brackets ({}), Dollar sign ($), Double quotation marks("), "Equal sign (=), Exclamation mark (!), Forward slash (/), Greater than (>), Lessthan (<), Line (|), Minus sign (-), Number sign (#), Parentheses ( ), Percent sign(%), Period (.), Plus sign (+), Question mark (?), Semi-colon (;), Spaces, Squarebrackets ([]), or Tabs.

6. For Description, enter an application description.

7. Click Next.

8. On the Details page, select the calendar and currency options for the application.After you create an application, you cannot change or enable these options.

• Time Period - Number of Months: Select the number of months to include inthe year: 12 months or 13 months.

If you select 12 months, by default, the periods are January to December.You can always add an alias to the period name if you want it to be different.

If you select 13 months, select the period Distribution for each quarter. Thedefault distribution is 3-3-3-4. You can select a prefix, and the numbers 1 to 13will be added to the prefix, for example, P1 through P13.

• Start and end year: Select the period range for which you want to includedata in the application.

You can adjust the period range that you want for your application. You canalso add additional years to your application by creating additional members inthe Year dimension after the application is created.

• First month of fiscal year: From the drop-down, select the first month to usefor the fiscal year. For 12 months, the default is January. For 13 months, thedefault is P1.

• Optional: Create HYTD Members: By default, the application provides thefollowing views of data: Periodic, YTD, QTD. To also include Half Year to Date(HYTD) time periods, click Enable.

• Main Currency: From the drop-down, select the main currency for yourapplication. The system provides the standard ISO codes. The defaultcurrency is USD.

Chapter 2Creating an Application

2-2

• Multicurrency: Select this option if your application contains data for morethan one currency. If the Multicurrency option is not enabled, the Currencydimension is not created for the application.

9. Click Next to enable application features. See Application Feature Descriptions.

10. After you select the features that you want to enable, click Next, and from theReview page, review the selected application details.

11. To create the application, click Create, or to change any settings, click Back andmake changes.

When you click Create, the system creates the application shell and generates theapplicable dimensions and members for your application based on your selections.

12. From the Application Creation Status message, click OK.

Enabling Application FeaturesYou can enable features using two methods:

• During the application creation process, you use the Features tab in the CreateApplication Wizard.

• After you create an application, you can enable features at any time from theApplication Configuration page.

The Features page displays the features available to be enabled. After you create anapplication, it displays the features that you selected as part of application creation.

Note:

You cannot disable features after application creation.

Watch the following video for information on configuring features:

Configuring Applications

Enabling Features During Application Creation

1. In the Create Application Wizard, navigate to the Features tab.

2. Select the features that you want to enable, and click Next.

3. From the Review page, review the selected application details.

4. Select an option:

• To create the application, click Create.

• To change any settings, click Back and make changes in the previous screen.

5. From the Application Creation Status message, click OK.

Enabling Features from Application Configuration

1. On the Home page, click Application, and select Configuration.

Chapter 2Enabling Application Features

2-3


2. From the Configure screen, click Enable Features.

3. Select the features that you want to enable.

See Application Feature Descriptions.

4. Click Enable.

5. When the system displays a message that the functionality has been enabled,click OK.

After you enable a new feature in an existing application, you must reload thenavigation flow.

6. On the Home page, click the down arrow next to the user name.

7. On the Setting and Actions menu, click Reload Navigation Flow.

Application Feature DescriptionsFinancial Consolidation and Close provides a set of consolidation features thatincludes out-of-the-box translations, consolidation, eliminations and adjustments.

When you create an application, the system creates these dimensions:

• Year

• Period

• View

• Currency (Only if multi-currency is selected)

• Consolidation

• Scenario

• Entity

• Intercompany (Only if Intercompany is selected in Enable Features)

• Account

• Movements

• Data Source

Depending on the functionality required for your application, you can enable additionalfeatures, dimensions, and members that you need. For example, you can enablejournal adjustments or tracking of intercompany eliminations. After a feature isenabled, you cannot disable it.

You can select these features:

• Consolidation

If you do not enable the Consolidation module, the Balance Sheet Hierarchyoption and other consolidation-related features are not available. See Consolidation and Supplemental Data Features.

• Accounts Reporting

Balance Sheet Hierarchy: Select the Balance Sheet hierarchy that is mostsuitable for your application. You can also manually create additional hierarchiesin addition to the ones created by the system.


2-4

– Traditional Balance Sheet Approach—This option provides the accounthierarchy with Total Assets as a parent member and Total Liabilities andEquity as a separate parent member. The aggregation of these two parentmembers should be zero as Total Assets = Total Liabilities and Equity.

– Net Asset Approach—This option allows you to track your Net Assetsseparately within the Balance Sheet hierarchy as Net Assets = Total Assets -Total Liabilities.

– Basic—Available only for Extended Dimension applications. This optionprovides a simplified hierarchy of the minimum required set of Account andMovement dimension members based on the enabled features and aminimum set of seeded forms. Note that Indirect cash Flow is an optionalenablement when the Basic option is selected but not when either Traditionalor Net Assets are selected.

Include Ratio Calculations

Select the applicable ratio calculations that you want to include in your application.A separate Ratio hierarchy will be created in the Account dimension with thespecific ratio groups that you selected. Individual ratio accounts and thecorresponding calculations will be created as part of the application. You can addadditional ratio calculations to each group.

– Liquidity Ratio

* Current Ratio

* Quick Ratio

* Cash Ratio

– Asset Management Ratio

* Inventory Turnover

* Asset Turnover

* Days Sales in Receivables

* Days Sales In Inventory

– Profitability Ratio

* Gross Profit Margin

* Return on Sales

* Return on Equity

– Leverage Ratio

* Debt To Equity Ratio

* Debt Ratio

• Multi-GAAP Reporting

Select this option if you need to report your financial statements in both localGAAP and in IFRS or other GAAP. This option tracks the local GAAP data input aswell as any GAAP adjustments.

You can rename members to reflect the correct GAAP adjustment if needed. Youcan also include additional members and hierarchies for other GAAP adjustmentsif needed.


2-5

If the Multi-GAAP option is enabled, you can have one additional customdimension for your application.

If the Multi-GAAP option is not enabled, the system does not create the Multi-GAAP dimension, so you can add two custom dimensions for your application.

– Enter Adjustment—Select this option to enter GAAP adjustments manually.

– Calculate Adjustment—Select this option to allow the system to calculate theadjustment amount based on the Local GAAP and IFRS amount entered.

• Cumulative Translation Adjustment (CTA) Account

This option is only available for multi-currency applications.

The CTA account is used to store the Foreign Exchange (FX) calculation valuesfor historical accounts.

You can configure the application to include the CTA Account in the BalanceSheet or in Comprehensive Income. For more information, see the "CTA andCICTA Accounts" section in Seeded Dimension Members.

– Balance Sheet

– Comprehensive Income

After you enable either of these options, you cannot change them. You mustrecreate the application to change the option.

The system automatically uses the same option for Local GAAP. For example, ifyou select CTA (Balance Sheet), the system selects CTA (Balance Sheet) forLocal GAAP. If you select CTA (Comprehensive Income), the system selectsCICTA (Comprehensive Income) for Local GAAP.

• Intercompany Data

Select this option if your application includes intercompany data. If enabled, thesystem creates an Intercompany dimension containing system members. TheEntity dimension displays a property for members that specifies if the membershould be included in the Intercompany dimension. If the property is selected, amember with the same name is created in the Intercompany dimension.

If you do not enable the Intercompany Data option, the Intercompany Dimension isnot displayed in your application.

Track Intercompany Elimination— If you select the Intercompany Data option,you can additionally select this tracking option. This option enables you to trackyour intercompany elimination data separately by data source. If this option is notselected, then the total elimination value from all data sources is stored as onetotal in the application rather than by the data source detail.

Note:

Both of these options are required to use the Ownership Managementfeature.

• Journal Adjustments

Select this option if your application includes journal adjustment data. If you selectthis option, the Journals menu displays in the application for you to manage yourjournal entries. Journals can be manually entered or loaded. If JournalAdjustments is enabled, the system adds an additional member named Journal


2-6

Input in the Data Source dimension to track the adjustment amount separatelyfrom regular data input.

Journal Workflow— If Journal Adjustments are enabled, you can additionallyselect a workflow for the journal process. When Journal Workflow is enabled, alljournals must first be submitted for approval before they can be posted to thesystem.

If you do not enable Journals, the Journals menu does not display in theapplication, and there are no journal-related metadata or reports.

• Ownership Management

Select this option to manage Ownership Management data and consolidationmethods.

This option is only available if you also enable Intercompany Data and TrackIntercompany Elimination.

Note:

Before you enable Ownership Management for an existing application,you must review the migration considerations to avoid potential conflictswith new seeded members. See Enabling Ownership Management inApplications.

• Equity Pickup

Select this option to enable the Equity Pickup method of recording the value ofinvestments in subsidiaries.

• Indirect Cashflow

If you select the Basic Accounts Reporting option, select this option to add theIndirect Cashflow hierarchies into the Closing Balance hierarchy, and add theCash Flow hierarchies.

If you select the Traditional Balance Sheet Approach or Net Asset Approach forAccounts Reporting, this option is selected by default and cannot be deselected.

• Track Multi-Source Data Input

A Data Source system dimension is provided as part of the application. In the DataSource dimension, the Data Input member is created by default to track datamanually entered or loaded from a .csv file. If you have multiple sources of datainput and adjustments that you want to track, you can use this option. For eachselection, a corresponding member is added to the Data Source dimension.

Other Data—Select this option if you want to collect data from another source. Anadditional member named "Other Data" will be created in the Data Sourcedimension for tracking purposes.

• Custom Dimensions

Using Custom dimensions can provide a more detailed view of consolidated data.These dimensions enable you to specify additional details associated withaccounts, such as products, markets, channels, and so on. For example, Customdimensions could include Product Line, Region, Channel, or Customers.

Select this option to add Custom dimensions, then enter a name for thedimension.


2-7

You can add a maximum of four Custom dimensions to an application. If yourapplication is enabled with the Multi-GAAP reporting option, you can create threeCustom dimensions.

Note:

The ability to add four Custom dimensions is available in all newprovisioned environments.

Two Custom dimensions are available in environments provisionedbefore June 2019. If you want to use more than two Custom dimensionsin those environments, you must request the Extended Dimensionalityupdate from Oracle Support. After you apply the update, you must createa new application. You cannot modify the number of dimensions in anexisting application. When Extended Dimensionality is enabled, you cancreate four Custom dimensions. If the application is enabled with theMulti-GAAP reporting option, you can create three Custom Dimensions.

• Supplemental Data Collection

Select this option if you want to collect additional supplemental details fromSupplemental Data. When it is enabled, you can configure your data collectionworkflow using Supplemental Data Manager, and the approved data is stored in aseparate member of the Data Source dimension named "Supplemental Data" fortracking purposes. You can drill back to the source to view all the supportingdetails. If you do not enable Supplemental Data Collection, some supplementaldata-related features are not available. See Consolidation and Supplemental DataFeatures.

Consolidation and Supplemental Data FeaturesFinancial Consolidation and Close provides a centralized monitoring of all businessprocess tasks by defining your business process activities for the period. You canenable the Consolidation feature to calculate and aggregate data throughout theorganization. You can then calculate and adjust data, perform currency translation andrun consolidation rules. Additionally, when you enable the Supplemental Data feature,you can organize, update and manage supplemental transaction details for financialanalytics and disclosure.

When you create an application, by default, Task Manager, Consolidation, andSupplemental Data features are enabled.

Consolidation and Supplemental Data features are optional. You can enable themduring or after you create an application.

The Task Manager feature is always enabled and you cannot disable it.

To enable features, see Enabling Application Features.

Consolidation Features

The following features are only available if the Consolidation module is enabled. If it isnot enabled, you cannot access these features from either the Home page or theNavigator.

• Balance Sheet Hierarchy


2-8

• Financial Dashboards

• Journals

• Approvals

• Rules

• Valid Intersections

• Data Management Integration

• Action Menus

• Smart Lists

• Variables

• Financial Reporting Web Studio

• Workflow

Supplemental Data Features

The following features are only available if the Supplemental Data feature is enabled.If it is not enabled, you cannot access these features from either the Home page,Downloads page, or the Navigator.

• Create and Manage Supplemental Data

• Oracle Smart View for Office

• Smart View Add-on for Administrator

• Smart View Extension for Task and Supplemental Data Management

Enabling Ownership Management in ApplicationsWhen you create an application, you can enable the Ownership Management feature,which allows you to assign ownership percentages and consolidation methods. Youcan also enable the feature for an existing application.

For details on this feature, see Managing Ownership.

This section lists the requirements to enable Ownership Management, and themetadata changes that the system implements when it is enabled.

Note:

If you do not enable Ownership Management, there is no impact to yourexisting application.

Before you enable Ownership Management, review these sections:

• Ownership Management Requirements for New Applications

• Ownership Management Requirements for Existing Applications

• Intercompany Dimension Members

• Member and Alias Considerations

Chapter 2Enabling Ownership Management in Applications

2-9

• Ownership Management Metadata Changes

Ownership Management Requirements for New Applications

To select the Ownership Management option for a new application:

• You must enable the Intercompany Data and the Track IntercompanyElimination options.

If both are enabled, the Ownership Management option is available for selection.

• If you do not select Ownership Management during application creation, you canenable the feature later if both of these options are enabled.

Ownership Management Requirements for Existing Applications

To enable the Ownership Management option for an existing application:

• The Intercompany Data option must be enabled.

If you do not have the Intercompany dimension enabled, you must re-create theapplication in order to use the Ownership Management feature.

• The Track Intercompany Elimination option must be enabled.

You can enable this option in an existing application if the Intercompany dimensionis enabled. See Enabling Application Features.

After you enable a new feature in an existing application, you must reload thenavigation flow.

– On the Home page, click the down arrow next to the user name.

– On the Setting and Actions menu, click Reload Navigation Flow.

Intercompany Dimension Members

When you enable the Intercompany Data and Track Intercompany Eliminationoptions, the system creates these dimension members:

• Intercompany Dimension

• FCCS_Elimination member of Consolidation Dimension

• FCCS_Intercompany Elimination member of Data Source Dimension

Member and Alias Considerations

When you enable Ownership Management, the system adds new seeded Accountsand Movement members with aliases, to support the seeded consolidation rules. Thismay result in a "Duplicate Alias" error with the existing members in the application.

The following tables list the new Member Names and Aliases for the Account andMovement dimensions. For details all of the metadata changes, including theConsolidation and Data Source dimensions, see Ownership Management MetadataChanges.

Before you enable the Ownership Management feature, you must do the followingsteps:

• Review the lists of new seeded members. If you have already defined somemembers that serve the same purpose, you must delete them to avoid a conflictwith the new seeded members.


2-10

• Review your existing Accounts and Movement members to ensure that there is noconflict with the Alias for the new members.

Note that there will not be a conflict with names for the new members, as the newseeded members have a prefix of FCCS_xxx.

• If there is a conflict, you should modify your Alias PRIOR to enabling the feature.Otherwise, you will encounter errors during migration or when refreshing thedatabase.

• If you modify an Alias, you should also modify any existing artifacts in which it isreferenced.

• You should either remove duplicate members from the referenced artifacts, orupdate the artifacts to reference the proper member.

After enabling Ownership Management, if you encounter errors with members andAliases, check the Jobs console to see the details on which member Alias is in conflict.

Table 2-2 Account Dimension - New Members

Member Name Alias

FCCS_Dividends Receivable Dividends Receivable

FCCS_Investment in Equity Companies Investment in Equity Companies

FCCS Investment in Equity CompaniesInvestment

Investment in Equity Companies - Investment

FCCS_Investment in Equity Companies EquityPickup

Investment in Equity Companies - EquityPickup

FCCS_Investment Link Investment Link

FCCS_Intangible Assets Intangible Assets and Goodwill

FCCS_Goodwill Goodwill

FCCS_Goodwill Input Goodwill - Input

FCCS_Goodwill Offset Goodwill - Offset

FCCS_Minority Interest Minority Interest

FCCS_Owners Equity Owner's Equity

FCCS_Other Equity Other Equity

FCCS_Revaluation Reserves Revaluation Reserves

FCCS_Dividends Declared Dividends Declared

FCCS_Retained Earnings Current - PreOwnership Change

Retained Earnings Current - Pre OwnershipChange

FCCS_Owners Income Owner's Income

FCCS_Minority Interest Income Minority Interest Income

FCCS_Net Discontinued Operations Income Net Discontinued Operations Income

FCCS_Discontinued Operations Income Discontinued Operations Income

FCCS_Discontinued Operations Tax Discontinued Operations Tax

FCCS_Continuing Operations Income Continuing Operations Income

FCCS_Equity Company Income Equity Company Income

Table 2-3 Movement Dimension - New Members

Member Name Alias

FCCS_Mvmts_Acquisitions Acquisition of companies and businesses


2-11

Table 2-3 (Cont.) Movement Dimension - New Members

Member Name Alias

FCCS_Mvmts_Disposals Disposal of companies and businesses

Ownership Management Metadata Changes

When the Ownership Management option is enabled, the system implements thesechanges to metadata.

Account Hierarchy Changes

When Ownership Management is enabled, seeded system Accounts will be created tosupport consolidation rules.

In addition, the Data Storage property of the existing "FCCS_Percent Consol" memberis changed from "Store" to "Dynamic Calc". This account will be dynamically calculatedbased on the entered Ownership information.

The updated FCCS_Total Assets hierarchy is shown below with these additionalaccounts:

• FCCS_Dividends Receivable

• FCCS_Investment in Equity Companies

• FCCS_Investment in Equity Companies Investment

• FCCS_Investment in Equity Companies Equity Pickup

• FCCS_Investment Link

• FCCS_Intangible Assets

• FCCS_Goodwill

• FCCS_Goodwill Input

• FCCS_Goodwill Offset

The updated FCCS_Total Equity hierarchy is shown below with these additionalaccounts:

• FCCS_Minority Interest


2-12

• FCCS_Owners Equity

• FCCS_Other Equity

• FCCS_Revaluation Reserves

• FCCS_Dividends Declared

• FCCS_Retained Earnings Current - Pre-Ownership Change

• FCCS_Owners Income

• FCCS Minority Interest Income

• FCCS_Net Discontinued Operations Income

• FCCS_Discontinued Operations Income

• FCCS_Discontinued Operations Tax

• FCCS_Continuing Operations Income

• FCCS_Equity Company Income

The updated FCCS_Drivers hierarchy is shown below with these additional accounts:

• FCCS_Percent Elim

• FCCS_Consol Method

• FCCS_Control

• FCCS_Control Input

• FCCS_Consol Method Input

• FCCS_Percent Consol Input

• FCCS_Percent Ownership Input

• FCCS_Percent Min Input


2-13

• FCCS_Percent Consol Prior Input

• FCCS_Percent Consol Change Input

• FCCS_Percent Consol- Property changed to Dynamic Calc

• FCCS_Percent Consol Prior

• FCCS_Percent Consol Change

• FCCS_Percent Owners

• FCCS_Percent Min

Consolidation Dimension Changes

• The Data Storage property of the existing "FCCS_Proportion" member is changedfrom "Dynamic Calc" to "Store".

• The "FCCS_Proportion" member is no longer the parent member for "FCCS_EntityTotal". Instead, this member is now a sibling for "FCCS_Entity Total".

• The Data Storage property changes require a reconsolidation for all existing datawithin the application. The Calculation status is changed to Impacted for allentities. You must reconsolidate all existing data in your application so that theProportion amount will be calculated and stored in the Consolidation dimension.

Note:

If any periods are locked, you must unlock them and then reconsolidatethe data.

The FCCS_Contribution hierarchy is shown below with these additional members:

• FCCS_Proportion

• FCCS_Entity Elimination Adj

Movement Member Changes


2-14

These new seeded Movement members will be added to support consolidation rulesfor ownership management:

• FCCS_Mvmts_Acquisitions

• FCCS_Mvmts_Disposals

Data Source Member Changes

These new seeded Data Source members will be added:

• FCCS_Intercompany Eliminations is used for tracking Intercompany Eliminationsrequired for Ownership Management.

• FCCS_Source Entities hierarchy will be used for Ownership Management.

The FCCS_Total Data Source hierarchy is shown below with these additionalmembers:

• FCCS_Intercompany Eliminations

• FCCS_Source Entities hierarchy

• S_Parent Source

• S_Current Source

• S_Entity

• S_FCCS_Total Geography

Migrating Net Income DataWhen you create an application, by default, the system creates the Account dimensionwith a hierarchy of seeded members. In the Account dimension, the seeded NetIncome hierarchy is created under the Balance Sheet member "FCCS_RetainedEarnings Current".

If you upgrade an existing application, as part of the upgrade process, the system willmove the Net Income hierarchy members under FCCS_Retained Earnings Current.You must then run the Configuration task to migrate the Net Income data.

During upgrade, only the FCCS_Net Income hierarchy will be moved as a child ofFCCS_Retained Earnings Current. Any alternate income hierarchies that have beencreated will remain under the Income Statement Group.

Chapter 2Migrating Net Income Data

2-15

Note:

The upgrade action is a one-time action. This migration task will be presentfor a couple of maintenance cycles but will be removed. You are encouragedto run this migration as soon as possible.

As part of the upgrade process, all of the base level members under FCCS_NetIncome will be updated with the Exchange Rate property set to No Rate. You canchange them to Historical, Historical Amount Override, or Historical Rate Override asneeded. You can create additional members under FCCS_Retained Earnings Current.

The data storage property of the FCCS_Retained Earnings Current member ischanged from Store to DynamicCalc.

The Configuration task to migrate Net Income data migrates the Net Income data fromFCCS_No Movement to FCCS Mvmts_NetIncome and updates all the seeded artifactsimpacted by the data migration. When you run the task, the system follows thisprocess:

• Moves all Net Income data from FCCS_NoMovement toFCCS_Mvmts_NetIncome. All seeded artifacts with FCCS_No Movement memberin the definition will be replaced with FCCS_Mvmts_NetIncome.

• Migrates the journal data and updates impacted journals and journal templates.The system replaces FCCS_No Movement with FCCS_Mvmts_NetIncome for alljournals (seeded and user-created) where the Account is Net Income or any of itsdescendants and Movement is FCCS_No Movement.

• If Supplemental Data is enabled in the application, updates the impacted recordsdue to data migration.

• If you use Data Management, you must manually update any mappings or importfile for the new Movement member.

• Custom artifacts will not be updated. You must manually update any customforms, reports, or other artifacts.

Note:

After the migration task is run, Migration export will no longer be available forFinancial Consolidation and Close applications created in the 17.04 updateor new applications.In addition, any seeded members that you previously moved are reset totheir original position.

To migrate Net Income data:

1. On the Home page, click Application, and select Configuration.

2. Click Migrate Net Income Data.

3. Click Launch to start the data migration task.

4. After the task is completed, the status is changed to Completed on the Configurepage.

Chapter 2Migrating Net Income Data

2-16

This task can take a long time to complete based on the amount of data thatneeds to be migrated. You can view the status and job details in the Jobs console.

5. Make sure that the migration task completed successfully. If the task fails for somereason, you can re-run the task from the Configuration screen.

6. On the Home page, click Forms, then select the Data Status form. Review theform and then run consolidation for all impacted entities.

Note:

Running the Migration task will change the calculation status to Impactedso it should be run again only if the first run did not completesuccessfully.

7. If there are any locked periods, you must unlock the period and rerun theconsolidation for all impacted entities.

8. Verify the consolidation results.

9. If your application contains custom-created forms impacted due to the migration,you must modify those forms.

Troubleshooting Net Income Data Migration Errors

When you run the Configuration task to migrate the Net Income data, you may receiveerror messages about the migration process and application artifacts.

Review all custom forms, reports, and other artifacts and make required changes toaccommodate the migration changes. For application artifacts that are not seeded,such as Forms, Reports, and Dashboards, check if the articles are defined withreference to the FCCS_Income Statement member. If so, you must edit the definitionof the artifact and make changes to point to the new hierarchy.

Note:

You can highlight the dimension member, such as FCCS_Income Statementor FCCS No Movement and click on the Show Usage toolbar icon to seewhat forms are using the member.

Table 2-4 Examples of Error Messages

Error Message Action

Form X did not import. Modify the form to change the POV to point tothe new hierarchy.

Creating Extended Dimension ApplicationsFinancial Consolidation and Close supports the creation of up to a total of four Customdimensions (or three Custom dimensions and one Multi-GAAP dimension). Followingare the considerations that should be taken into account while creating applications inan Extended Dimensionality environment.

Chapter 2Creating Extended Dimension Applications

2-17

You create an Extended Dimension application and other related artifacts in the sameway that you create a non-Extended Dimension application. However, you must makesome changes for the below-listed dimensions when operating in an ExtendedDimension environment.

Custom Dimensions

• The default members that are created in Custom dimensions are exactly the sameas in a non-Extended Dimension application, except that the "Total Custom"member is now "Dynamic Calc" instead of "Never Share".

• Any new parent members that you create in these Custom dimensions must usethe Data Storage property of "Dynamic Calc". This is the only difference andchange from the non-Extended Dimension application, where Custom parentdimensions are created as "Never Share".

Multi-GAAP Dimension

• The default Multi-GAAP hierarchy that is created by the application now followsthe same paradigm as the Custom dimensions. The Data Storage property forParent members will be "Dynamic Calc".

• Any new Multi-GAAP hierarchy that you create should follow the same paradigm.

Intercompany Dimension

The FCCS_Intercompany Entities parent member is now created as a "Dynamic Calc"member. You do not need to make any changes to this dimension.

Creating an Extended Dimensionality Application Using Artifacts from ExistingApplications

Create a New Application

Create a new Extended Dimensionality application with the required features andCustom dimensions as your non-Extended Dimensionality application, and add theadditional Custom dimensions. See Application Feature Descriptions.

Note:

You must create a new application using the Application Wizard. You cannotuse a Migration snapshot to create the application.

During the creation of the Extended Dimension application, all of the CustomDimension attributes and properties that you select must match the non-ExtendedDimension application.

These include:

• Application Name

• Dimension Properties

To access the non-Extended Dimension application dimension properties, on theHome page, click the Navigator icon, then select Application, Configuration, andselect Enable Features.


2-18

Metadata

From the non-Extended Dimension application, export the metadata for each of thedimension that have user-defined members (Scenario, Entity, Account, Movement,Data Source, Multi-GAAP, Custom, and Currency). If you have not modified theScenario, Movement, Data Source, or Multi-GAAP dimensions, they do not need to beexported.

Exporting the Metadata

1. Select the dimensions to export. On the Home page, click the Navigator icon,then select Application, and then Overview.

2. Select the Dimension tab, and select Export, and then Create.


2-19

3. Select the required dimensions and select Export.

A zipped metadata file will start to download.

4. Download the file and unzip the files into the directory.

Editing the Dimensions

1. Open the Custom and Multi-GAAP files in either Microsoft Excel or a text editorand then do the following steps:

Change the Data Storage property of each parent member to "Dynamic Calc".Make sure to do this for both "Data Storage (Default)" and "Data Storage (Consol)"columns.

2. Open the Entity dimension file.

Delete the column "FCH_MCH_Entity" if it exists.

Importing the Metadata

Import the metadata using the files that you exported and edited.

1. On the Home page, click the Navigator icon, then select Application, and thenOverview.

2. Select the Dimension tab, then click Import and Create.

3. Select the appropriate file for each dimension and click Validate.


5. Select the Dimension tab, then click Import and Create.

6. Select the appropriate file for each dimension and click Import.

7. If you are using Intercompany Eliminations, you must load the Account dimensiona second time.

8. Refresh the database.

Import and Create new Custom Dimensions. Make sure all of the parent members are"Dynamic Calc".


2-20

Data

It is anticipated that you will want to reload your source data and include mappings inData Management to members in the new Custom dimensions. However, if you wantto use the existing data and manually modify the data to include the new Customdimensions, then you will need to export the data from the non-Extended dimensionapplication as follows.


2. From the Actions menu, select Export Data, and then Create.

Note:

Set Dynamic Member to Exclude.

3. Select the Rates cube and set the slice definition and the POV as follows:


2-21

4. Select the Consol cube and set the slice definition and POV for Consol as follows.

Note that Segments and Departments are Custom dimensions, and note that onlyData Input and Other Data have been selected to export. You will need to selectall members that have data under Total Input and Adjusted in the Data Sourcedimension. You will want to exclude Journal Input and insert your own Customdimensions. Select other members of other dimensions as necessary for yourdata.

5. For Override data, leave the cube set to Consol, and set the slice definition andPOV for Consol as follows:

• For Data Source: Include Journal Input if needed.

• The only other changes from the above financial data extract is the membersof the Consolidation and Currency dimension. Choose the override membersin the Consolidation dimension, and all of the Input currencies in the Currencydimension.


2-22

6. Edit the data. For all data in the Consol cube, modify the POV to include membersfrom the new Custom dimensions.

7. Import the data. On the Home page, click the Navigator icon, then selectApplication, and then Overview. From the Actions menu, select Import Data,then Create.

Journals

Journals will be treated like data. You can export them out of your existing application,but will need to modify them to include new Custom dimensions. However, it isanticipated that most journals will be recreated in the new Extended Dimensionapplication.

If Workflow for journals is enabled, you will need to change the status for a journal toWorking from Posted to import the journal, since an Administrator cannot importposted journals.

To export journals:

1. On the Home page, click Journals, then select Actions, and Export.


2-23

2. Set the POV as appropriate. Below is an example.

3. Modify the journals for the new Custom dimension members.

4. Import the journals.

5. Consolidate and translate as needed.

Other Artifacts

All other artifacts (forms, dashboards, reports, Smart View, valid intersections) willneed to be recreated in the Extended Dimension application.


2-24

3Managing Security

Related Topics

• Security Overview

• Managing Artifact and Data Access

• Managing Forms Security

Security OverviewFinancial Consolidation and Close implements several security layers to ensuresecurity. Infrastructure security components, which are implemented and managed byOracle, create a highly secure environment for the service. The service ensuressecurity with password-protected single sign-on, and role-based access to data andartifacts.

Setting up security requires these steps:

• Create users and assign them access to the application. See the Getting Startedwith Oracle Enterprise Performance Management Cloud for Administrators guide.

The Identity Domain Administrator creates the users and assigns them access tothe application.

• Assign users role access to the application. See the Getting Started with OracleEnterprise Performance Management Cloud for Administrators guide.

The Identity Domain Administrator assigns users role access to the application.

• Assign users access to artifacts. See Assigning User Access to Artifacts.

Users are assigned access to artifacts in the application. These artifacts includeforms, journals, task lists, and report. This access is given to users by the creatorsof the artifacts or by the Service Administrator.

• Assign users access to data. See Assigning User Access to Data.

Users are assigned access to artifacts in the application. These artifacts includeforms, journals, task lists, and report. This access is given to users by the creatorsof the artifacts or by the Service Administrator.

The Administrator assigns access to data through access to dimension members.Users are assigned either Modify, View, or None access to members of adimension.

Watch the following video for an introduction to security:

Understanding Security

3-1


Managing Artifact and Data AccessAs an administrator, you can configure security on these application elements:

• Forms

• Journals

• Task Lists

• Financial Reporting reports

• Dimensions

• Integrations

– Oracle Smart View for Office

– Migration

– Data Management

– Oracle Hyperion Financial Close Management

The following table shows the functionality for each role.

Table 3-1 Functionality by Role

Functionality Viewer User Power User ServiceAdministrator

View data throughForms

Yes Yes Yes Yes

View Data throughData Analysis tools(FR, Forms, SmartView, Journals, Adhoc Grids)

Yes Yes Yes Yes

Enter data throughForms

Yes Yes Yes

Enter data throughJournals

Yes Yes Yes

Load data throughFDMEE

Yes Yes

Submit data forapproval (journal anddata)

Yes Yes Yes

Drill through tosource system

Yes Yes Yes Yes

Consolidate data Yes Yes Yes

Create and maintainforms

Yes Yes

Create Smart ViewWorksheets

Yes Yes Yes

Create and start theapproval process forProcess Control unitsand journals

Yes Yes

Chapter 3Managing Artifact and Data Access

3-2

Table 3-1 (Cont.) Functionality by Role

Functionality Viewer User Power User ServiceAdministrator

Perform actions onProcess ControlApproval units andJournals

Yes Yes Yes

Perform all functionalactivities for theapplication (exceptcreate and assignuser roles)

Yes

DimensionManagement

Yes

Member FormulaManagement

Yes

Start and closeJournal periods

Yes

Assigning User Access to ArtifactsAs an administrator, you assign security to artifacts, including forms, journals, tasklists, and Financial Reporting reports. You can assign these access rights:

• Modify

• Read

• None

For example, to view a form, the only requirement is Read access. Modify rights givethe user the right to modify a form (Power User or Administrator only).

The default security access is None for any artifact.

Assigning User Access to DataSecurity access (None, Read, Write) are assigned to members of dimensions. As anadministrator, you define which dimensions have security.

By default, security is enabled for these dimensions.

• Scenario

• Entity

• Account

• Data Source

The default security access is None.

You can disable security for any of these dimensions, but security is mandatory for atleast one dimension. You can assign security at a parent level for all of itsdescendants, and you do not need to assign security to each dimension memberindependently.


3-3

Data level security is based on the intersection of the security access to eachdimension. The most restrictive security access is the one used by the system.

For example, security is assigned to Scenario and Entity. A user has the followingaccess to individual members of the dimensions:

Scenario

Actual - Write

Budget - Read

Entity

UK - Write

France - Write

With the above access, the user can enter and load data to Actual/UK, but has Readonly access to Budget/UK and Budget/France.

Enabling or Disabling Security for DimensionsYou can enable security for dimensions, including user-defined Custom dimensions. Ifyou do not set security on a dimension, all users can access the dimension members.

By default, the Account, Entity, Scenario, and View dimensions are enabled for accesspermissions. Optionally, you can assign access to Year and Periods.

You can assign security to dimension members for user and groups. You can assignsecurity at a member level or parent level.

To enable or disable security for a dimension:

1. Click the Navigator icon .

2. Under Create and Manage, click Dimensions.

3. From Dimensions, select a dimension and then click Edit.

4. From the Edit Dimension Properties page, select an option:

• To enable security, click Apply Security.

Note:

If you do not select this option, there is no security on the dimension,and users can access its members without restriction.

• To disable security, clear Apply Security.

5. Click Save.

Assigning Security to Dimension MembersBefore you can assign access to members of user-defined custom dimensions, youmust select the Apply Security check box on the dimension’s Property tab.

You can assign security to dimension members at a member level or at a parent level.


3-4

To assign security to dimension members:



3. Select a member.

4. Click Assign Access.

5. Click Add Access.

6. Select the users and groups to access the selected member.

Click Users to display all users; click Groups to display all groups.

7. From Type of Access, select an option:

• Read

• Write

• None

8. Optional: Select a member level:

For example, select Children to assign access to the children of the selectedmember.

• Member

• Children

• Children (inclusive)

• Descendants

• Descendants (inclusive)

9. Click Add.

10. Click Close.

To modify access:

1. Click Edit Access.

2. For the selected member, select the type of access for the displayed users orgroups.

3. Optional: Select a member level:

For example, select Children to assign access to the children of the selectedmember.

• Member

• Children

• Children (inclusive)

• Descendants

• Descendants (inclusive)

4. Click Set.

5. Click Close.

To remove access:


3-5

1. Select the users and groups for whom to remove access to the selected member.

2. Click Remove Access, and then click OK.

3. Click Close.

Data Source Dimension SecurityDuring application creation, these steps occur:

• The DataSourceDefaultAccess user group is automatically created in ApplicationManagement.

• The default security role assigned for the group is Viewer.

• The system enables security on the DataSource dimension.

• Access rights are automatically assigned.

Note:

The Administrator should ensure that all the users in the application are partof the DataSourceDefaultAccess user group, so that you do not need tomanually assign security on the Data Source dimension.

Table 3-2 Data Source Dimension Access Rights

Dimension Member Group Access Access Rights Relation

No Data Source DataSourceDefaultAccess Write Member

Total Data Source DataSourceDefaultAccess Write Descendant

Journal Input DataSourceDefaultAccess Read Member

SDM Input DataSourceDefaultAccess Read Member

FDMEE Input DataSourceDefaultAccess Read Member

System Types DataSourceDefaultAccess Write Descendant

Note:

You should not enter data directly in forms or Oracle Smart View for Office toJournals, Supplemental Data Manager (SDM), and FDMEE input members(for example, Journal Input, SDM Input and FDMEE Input). It isrecommended to enter data through Journals, Supplemental Data Manager,or FDMEE, respectively.

Managing Forms SecurityAs an administrator, you can assign user access to individual forms and form folders.You can assign access to individual users, or to user groups.

Forms

Chapter 3Managing Forms Security

3-6

• Users and Power Users can view or enter data only into forms to which they haveaccess (and can work only with members to which they have access)

• Service Administrators and Power Users can design forms.

• Power Users can access forms they created or to which a Service Administratorassigned them access.

• Service Administrators have Write access to all dimension members and to allforms.

Form Folders

• Users who are assigned access to a form folder can access the forms in thatfolder.

• When you assign access to a folder, all folders under it inherit that access.

• If you assign specific access (for example, None or Write) to a form folder, thataccess permission takes precedence over its parent folder’s access permissions.For example, if a user has Write access to Folder 1 that contains Folder 2 to whichthe user has None access, the user can open Folder 1, but does not see Folder 2.

• If a user has None access to a form folder called Folder 1 that contains a formcalled Form 1 to which the user has Write access, the user can see Folder 1 andForm 1.

Assigning Access to Forms and FoldersTo assign security to forms and form folders:


2. Under Create and Manage, click Forms.

3. Select the form or form folder and then click Assign Access.

You can assign access to only one form or folder at a time.

A screen displays all the users with access rights.

4. From the Users tab or Groups tab, select a user or group to assign access.

Click Users to display all user names; click Groups to display all groups.

5. Click Add Access.

6. From Type of Access, select an option:

• Read

• Write

• None

7. Click Add.

8. Click Close.

To change which users can use or change forms or folders:

1. Select the users or groups for which to change access, and click Edit Access.

2. For Type of Access, select the type of access that the users or groups have tothe form or folder.

3. Click Set.


3-7

4. Click Close.

To remove access from forms or folders:

1. Select the users or groups for which to remove access, and click RemoveAccess.

2. Click OK.

Default Form SecurityThese forms are provided by default when you create an application. By default, theService Administrator and Power User have Modify access rights to these forms. AUser or Viewer can launch the form, but cannot modify the form layout.

For information on managing forms, see Managing Forms.

Note:

The forms that are displayed by default may depend on the features that areselected for the application.

• Data Status

• Enter Exchange Rates - Multi Period

• Enter Exchange Rates - Single Period

• Exchange Rates

• Override Rates

• Percentage Consolidation


3-8

4Managing Applications

Related Topics

• Application Overview

• Restrictions for Dimensions, Members, Aliases, and Forms

• Managing Dimensions

• Importing Metadata

• Exporting Metadata

• Validating Metadata

• Metadata Validation Messages

• Importing Data

• Exporting Data

• Viewing Data Import and Export Status

• Importing Data Using Data Management

• Exporting Data Using Data Management

• Data Integrations

• Copying Data

• Clearing Data

• Refreshing the Database

• Restructuring Cubes

• Removing an Application

• Scheduling Maintenance

• Using the Inbox/Outbox

• Working with Activity Reports and Access Logs

Application OverviewAfter you create an application, you can view and manage it by accessing Applicationfrom the Home page.

To manage applications, you must be the Service Administrator.

The Application overview shows the application properties and application statistics,such as the number of tasks, forms, rules, and approval hierarchies in yourapplication.

It also lists the dimensions used by the application. To manage dimensions, see Managing Dimensions.

4-1

To view the Application overview, on the Home page, click Application and thenselect Overview.

Restrictions for Dimensions, Members, Aliases, and FormsWhen naming dimensions, members, and aliases, follow these rules:

• For dimensions, members, or aliases, use no more than 80 characters.

• Do not use HTML tags in member names, dimension names, aliases, anddescriptions.

• Do not use quotation marks, brackets, backslashes, or tabs. Brackets arepermitted but not recommended in block storage outlines. They cause errors whenconverting to aggregate storage outlines.

• To begin dimension or member names, do not use these characters:

– at signs

– backslashes

– brackets

– commas

– dashes, hyphens, or minus signs

– equal signs

– less than signs

– parentheses

– periods

– plus signs

– quotation marks

– underscores

– vertical bars

• Do not place spaces at the beginning or end of names. Such spaces are ignored.

• Do not use forward slashes in member names.

Chapter 4Restrictions for Dimensions, Members, Aliases, and Forms

4-2

• For time periods in custom calendars, do not use spaces in prefixes.

• Do not use these words as dimension or member names:

– Calculation script commands, operators, and keywords.

– Do not prefix an object name with any of the following: OEP_, OFS_, OCX_,OWP_, OPF_, FCCS_, TRCS_, ARCS_, OQP_, OGS_. For example, theprefix “FCCS_A” is invalid. However, you can use the acronyms within theobject name, for example, A_FCCS, BFCCS, or FCCSB.

– Function names and function arguments.

– Names of other dimensions and members (unless the member is shared).

– If Dynamic Time Series is enabled, do not use History, Year, Season, Period,Quarter, Month, Week, or Day.

– These words:

* ALL

* AND

* ASSIGN

* AVERAGE

* CALC

* CALCMBR

* COPYFORWARD

* CROSSDIM

* CURMBRNAME

* DIM

* DIMNAME

* DIV

* DYNAMIC

* EMPTYPARM

* EQ

* EQOP

* EXCEPT

* EXP

* EXPERROR

* FLOAT

* FUNCTION

* GE

* GEN

* GENRANGE

* GROUP

* GT


4-3

* ID

* IDERROR

* INTEGER

* LE

* LEVELRANGE

* LOCAL

* LOOPBLOCK

* LOOPPARMS

* LT

* MBR

* MBRNAME

* MBRONLY

* MINUS

* MISSING

* MUL

* MULOP

* NE

* NON

* NONINPUT

* NOT

* OR

* PAREN

* PARENPARM

* PERCENT

* PLUS

* RELOP

* SET

* SKIPBOTH

* SKIPMISSING

* SKIPNONE

* SKIPZERO

* STATUS

* TO

* TOLOCALRATE

* TOP

* TRAILMISSING

* TRAILSUM


4-4

* TYPE

* UMINUS

* UPPER

* VARORXMBR

* XMBRONLY

* $$UNIVERSE$$

* #MISSING

* #MI

Managing DimensionsDimensions categorize data values. These dimensions are provided with FinancialConsolidation and Close:

• Account

• Period

• Data Source

• Consolidation

• Currency (Only if Multi-currency was selected during application creation)

• Entity

• Intercompany (Only if Intercompany was selected during application creation)

• Movement

• Scenario

• Year

• View

You can create additional Custom dimensions. See Adding Custom Dimensions.

The Dimensions page lists dimensions in order of precedence. The order ofdimensions is critical for the structure and performance of an application anddetermines how data calculations will perform.

To manage dimensions:

1. On the Home page, click Application.

2. Click Overview, and then click the Dimensions tab.

3. Perform a task:

• Click the name of the dimension that you want to view or modify to open Edit

Dimension Properties .

• To import metadata, click Import. See Importing Metadata.

• To export metadata, click Export. See Exporting Metadata.

Chapter 4Managing Dimensions

4-5

Importing MetadataYou can import metadata from a file in a comma-delimited, tab-delimited, or otherformat. These artifacts are supported in imports:

• Dimensions

• Smart Lists

• Exchange rates

To import metadata, perform these tasks:

• Create an import file for each artifact that you want to import. See Creating theMetadata Import File

• Load the import file or files (you can import multiple dimension files at the sametime). See Loading the Metadata Import File.

Creating the Metadata Import FileBefore you begin loading, you must create an import file for each artifact that you wantto import (dimensions, smart lists, and exchange rate tables). The import file mustcontain a header record, and then below the header record, a list of metadata recordsthat you want to import or update. The file format can be .csv (comma-delimited),or .txt (tab-delimited or other delimiter characters).

The file consists of these sections:

1. A header record, the first line in the file:

• Lists the dimension and any member properties used by subsequent metadatarecords; the header record and subsequent records do not need to include allproperties; properties that are not included are inherited from thecorresponding parent’s default property value

• Is case-sensitive

• Can list properties in any order, as long as the subsequent metadata recordsare in the same order

• Can use comma or tab delimiters. Other delimiter characters can be used ifthey are supported and the same delimiter character is used throughout thefile. For a list of supported delimiter characters and exceptions, see OtherSupported Delimiter Characters.

2. After the header record, a list of metadata records that you want to import update.Each metadata record contains a delimited list (comma, tab, or other) of propertyvalues that matches the order designated in the header record. A metadata recordcan skip a property that is specified in the header record; in this case, the defaultproperty is assumed.

For an example import file, see Example: Entity Dimension Import File.

Example: Entity Dimension Import FileIn this example, the import file loads an Entity dimension with the required headerrecord and three data records. This example is comma-delimited. The header record

Chapter 4Importing Metadata

4-6

specifies the member to be imported (Entity), the parent member (Parent) into which toimport the member, and the Data Storage property to assign to the member.

Entity, Parent, Data Storage

e1, Entity

e2, ,

e1, e2, Shared

Using this import file would result in this outline, assuming that no other membersexist:

Entity

e1

e2

e1 (Shared)

The first data record (e1, Entity) imports Entity member e1 as a child under the rootmember Entity. Unspecified values assume the default. For example, if data storage isnot specified, it assumes the default value, Never Share. The next data record (e2, ,)imports Entity member e2 under the dimension root member because no parent isspecified, and sets data storage to Never Share. The last data record (e1, e2,Shared) imports a shared member of e1 under member e2, and sets the data storageto Shared.

Other Supported Delimiter CharactersIn addition to commas and tabs, Financial Consolidation and Close supports thesedelimiter characters in import and export files:

• tilde (~)

• grave accent (`)

• exclamation point (!)

• number sign (#)

• question mark (?)

• dollar sign ($)

• percent sign (%)

• caret (^)

• ampersand (&)

• asterisk (*)

• parentheses ( )

• hyphen-minus (-)

• plus (+)

• colon (:)

• semicolon (;)


4-7

• angle brackets (< >)

• backslash (\)

• forward slash (/)

• vertical bar ( | )

• apostrophe (‘)

• braces ({ })

• underscore (_)

• brackets ([ ])

• at sign (@)

• period (.)

Only one character is supported for use as a delimiter. For example, one vertical bar( | ) is supported, but two vertical bars (| |) are not supported.

Caution:

Not all of the characters listed can be used for all import and exportscenarios. Note the following exceptions.

Import and Export Metadata Delimiter Exceptions

Do not use these delimiter characters in metadata import and export files.

Table 4-1 Import and Export Metadata Delimiter Exceptions

Delimiter Character Reason for Exception

double quotation mark ("") Creates an empty file

plus (+)minus (-)

forward slash (/)

percent sign (%)

Causes an error if the metadata import filecontains consolidation properties that usethese characters

angle brackets (< >) Causes an error if the property uses the value<none>

Note:

Any character that conflicts with a character in a member name causes anerror.

Table 4-2 Import and Export Data Delimiter Exceptions


parentheses ( ) Causes an error if used in a data import file


4-8

Table 4-2 (Cont.) Import and Export Data Delimiter Exceptions


double quotation mark ("") Creates an empty file

hyphen-minus (-) Causes an error if used in a data import file

Loading the Metadata Import FileTo load the metadata import file:

1. Create an import file for each artifact (dimensions, smart lists, and exchange ratetables) that you want to import. See Creating the Metadata Import File.


3. Click Overview, then click the Dimensions tab, and then click Import.

4. On the Import Metadata page, click Create.

5. Select the location of the import file or files:

• Local—Loads the import file or files from a location on your computer. ForImport File, click Browse to select the import file on your computer for theartifact that you’re importing.

• Inbox—Loads the import file or files from the server. Enter the name of the filein Import File.

6. For File Type, select an option:

• Comma delimited

• Tab delimited

• Other. Enter the delimiter character that is used in the import file. For a list ofsupported delimiter characters and exceptions, see Other Supported DelimiterCharacters.

7. Select Clear Members to delete members not explicitly specified in the load filebefore performing the import.

Note the following guidelines:

• If Clear Members is not selected, the import process will only add or updateexisting members. You can first load the metadata file without selecting ClearMembers to make sure that the file loads successfully. Then, select ClearMembers and execute the import process again.

• Any member not specified is deleted from the outline after importing thedimension unless it is an ancestor of a member that was specified, or it is abase member of a shared member that was specified.

• If you add accounts manually in a metadata load file with the Exchange RateType as Amount Override or Rate Override, make sure the Clear Membersoption is not selected, so that the shared entries are created correctly underHistorical accounts.

8. Optional: If the selected location is Inbox, click Save as Job to save the importoperation as a job, which you can schedule to run immediately, or at a later time.


4-9

Saving an import operation as a job is useful to batch a load sequence; forexample, import metadata, then import data, and then run rules when the dataload is complete.

9. Optional: If the selected location is Local, click Validate to test whether theimport file format is correct.

10. Click Import to run the import operation.

11. If the import process is successful, the Refresh Database dialog box prompts youto refresh the database. To refresh, click OK.

You can view the import status in the Jobs console. See Viewing Pending Jobs andRecent Activity.

Exporting MetadataYou can export metadata to a file in a .csv (comma-delimited) or .txt (tab-delimited orother delimiter character) format. These artifacts are supported in the export process:

• Dimensions

• Smart Lists

• Exchange rates

The system creates an export file for each artifact (.csv or .txt, depending on the filetype), and all export files are consolidated into one zip file. You must extract the .csvor .txt files from the zip file if you want to use the files as import files (for example,when importing into another application).

When you export seeded members, these member properties are exported:

• Account

• Parent

• Data Storage

• Operation

The member level customizations for seeded members are not exported as part of themetadata export. You can export customizations from the Tools Migration page.

To export metadata to a file:


2. Click Overview, click the Dimensions tab, and then click Export.

3. On the Export Metadata page, click Create.

4. Select the target location of the export file:

• Local—Saves the export file to a location on your local computer.

• Outbox—Saves the export file to the server.

5. Select the artifact or artifacts to export.


• Comma delimited—Creates a comma-delimited .csv file for each artifact.

• Tab delimited—Creates a tab-delimited .txt file for each artifact.

Chapter 4Exporting Metadata

4-10

• Other—Creates a .txt file for each artifact. Enter the delimiter character thatyou want to use in the export file. For a list of supported delimiter charactersand exceptions, see Other Supported Delimiter Characters.

7. Optional: If the selected location is Outbox, click Save as Job to save the exportoperation as a job, which you can schedule to run immediately, or at a later time.

8. Click Export, and then specify where to save the export file.

Validating MetadataIncorrect or or inappropriate metadata properties can cause errors duringconsolidation and cause poor performance.

Examples of metadata property validation include the default and Consol cube datastorage properties, whether the Consolidation operator is valid, and whether a Parentmember is Dynamic Calc or Label Only, or has a member formula.

A Best Practice is to validate metadata by running an on-demand Metadata Validationreport, and by checking metadata in the Dimension Editor.

Note:

If you have problems with your application, be sure to validate metadata andcorrect all errors before contacting Oracle Support.

To ensure that your metadata is valid, you can run the Metadata Validation report atany time. If metadata errors occurs, the report displays the dimension name, themember name in [Parent].[Child] format, and the error description. After validating, youcan expand the messages on screen, or click Export to extract the error messages toa CSV file. You can use the Dimension Editor to correct all errors.

For example, if an error occurs that an Entity dimension member has a ConsolidationOperator of other than Ignore in the Dimension Editor, select the member and changethe Consolidation Operator property to Ignore.

To validate metadata from the Metadata Validator:


2. Click Overview, then from Actions, select Validate Metadata.

3. Click Run to validate the metadata.

The total number of errors is listed and the dimension name for each dimensionwith errors are displayed.

4. Expand the dimension name to display the errors. The results are displayed in[Parent].[Child] format with the error description. To review further details of thevarious errors, see Metadata Validation Messages.

5. To export the error messages, click Export and then specify where to save theexport file.

6. Navigate to the Dimension Editor to correct the metadata errors.

To view a list of valid member properties, see Editing Member Properties in theSimplified Dimension Editor.

Chapter 4Validating Metadata

4-11

7. Re-run the consolidation and check performance.

To validate metadata from the Simplified Dimension Editor for a single dimension:


2. Click the Dimensions tab.

3. Click the Edit Member Properties tab on the left.

4. Select a dimension and, click the Zoom in All Levels icon on the toolbar.

5. From the top Actions menu, select Validate Metadata definitions.

6. The system displays the validation errors in the currently selected dimension.

7. Fix the metadata errors.

To view a list of valid member properties, see Editing Member Properties in theSimplified Dimension Editor.

8. Re-run the consolidation and check performance.

Metadata Validation MessagesMetadata Validation checks are applied against specific relationships within metadatain order to warn against situations that can cause data integrity issues, performanceissues or other issues. It is recommended that all validation message are cleared toensure that metadata design problems are not the cause of other problems.

Primary Members Must Exist Before Shared Members

Primary members must exist before shared members ("above" the shared member inthe hierarchy) for the following dimensions:

• Scenario

• Period

• Account

• Intercompany

• Movement

• Data Source

• Multi-GAAP (if exists)

• User-created Custom dimensions

Example validation message:

Shared member should not exist before the primary member.

Resolution:

Move the shared member to a position below the primary member.

Level 0 Member Data Storage Types Must Be Valid

The Data Storage type must be valid for all level 0 members:

• Entity, Movement dimensions: Store, Never Share, or Shared

Chapter 4Metadata Validation Messages

4-12

• Account, Data Source, Multi-GAAP, User-created custom dimensions: Store,Never Share, Shared, or Dynamic Calc


The Data Storage should be Store Never Share, Shared or Dynamic Calc forLevel 0 members.

Resolution:

Change the Data Storage selection as described above.

Note:

Currently the Metadata Validator will display an error for any Level 0Dynamic Calc members of the Movement Dimension except for seededmembers.

In future releases, "Dynamic Calc" will be allowed except for FCCS_ClosingBalance hierarchy, as long as they have a valid Member Formula. As a firststep towards this change, Dynamic Calc is added to the list of valid DataStorage selection options for Level 0 Movement members in the SimplifiedDimension Editor (SUIDE).

Level 0 Members Should Not Be Dynamic Calc Without Formulas

Any valid level 0 Dynamic Calc member must have a valid Member Formula for thefollowing dimensions:




Level 0 members should not be Dynamic Calc without member formulas in Ratedata storage.

Level 0 members should not be Dynamic Calc without member formulas inConsol data storage.

Resolution:

Add a valid formula to the Dynamic Calc member, or change the Data Storageproperties to Store, Never Share or Shared. For Rate Cube accounts, check whetherthe account is needed in the Rates Cube. If it is not needed, then delete the accountfrom the Rates Cube using the Dimension Editor, or change "Rates Consol op" to "NotUsed for Cube" from the Simplified Dimension Editor.

Parent Members Should Not Have Member Formulas

Parent members should not have Member Formulas for the following dimensions:

• Entity

• Account

• Movement


4-13

• Data Source




Parent member should not have member formula.

Resolution:

Remove the Member Formula from the parent member.

Aggregation Operators for All Children of Dimension Names Must Be Ignore orNever

The aggregation operator should be Ignore or Never if a member is a child of adimension name.

• Entity dimension: Ignore for both Consol cube and for Rates cube

• Other dimensions: Ignore or Never for Consol cube and Ignore for Rates cube


The Consol Operator for all children of the dimension name should beIgnore.

The Consol Operator for all children of the dimension name should beIgnore or Never.

Resolution:

Change the aggregation operator as described above. Note that the aggregationoperators for seeded members should already be correct.

Account Type and Aggregation Operators Must Match

Within the balanced Balance Sheet in the Account dimension, the account types of theparent and child accounts must match with the appropriate aggregation operator. Thecombination of parent account type and child account type determines whether theaggregation operator should be Addition or Subtraction. Ensuring that the accounttypes and aggregation operator match will ensure that the balance sheet dataaggregates properly to a balanced Balance Sheet.

If the “normal sign” (that is, Debit or Credit) is the same for the parent account andchild account then the aggregation operator must be Addition. If the "normal sign" isdifferent for the parent account and child account, then the aggregation operator mustbe Subtraction.

Parent Account Type Child Account Type Aggregation Operator

Revenue (Credit) Revenue (Credit) Addition

Revenue Expense (Debit) Subtraction

Revenue Asset (Debit) Subtraction

Revenue Liability (Credit) Addition

Revenue Equity (Credit) Addition

Revenue Saved Assumption Addition

Expense (Debit) Revenue Subtraction


4-14

Parent Account Type Child Account Type Aggregation Operator

Expense Expense Addition

Expense Asset Addition

Expense Liability Subtraction

Expense Equity Subtraction

Expense Saved Assumption Addition

Asset (Debit) Revenue Subtraction

Asset Expense Addition

Asset Asset Addition

Asset Liability Subtraction

Asset Equity Subtraction

Asset Saved Assumption Addition

Liability (Credit) Revenue Addition

Liability Expense Subtraction

Liability Asset Subtraction

Liability Liability Addition

Liability Equity Addition

Liability Saved Assumption Addition

Equity (Credit) Revenue Addition

Equity Expense Subtraction

Equity Asset Subtraction

Equity Liability Addition

Equity Equity Addition

Equity Saved Assumption Addition

Saved Assumption Any type Addition


Account Consol Operator should be Addition based on parent and childaccount types.

Account Consol Operator should be Subtraction based on parent and childaccount types.

Resolution:

Change the Account Type of parent or child or change the aggregation operator.

Note that the seeded balance sheet hierarchy must reflect the following structure:

The seeded balance sheet "grouping" account (FCCS_Balance Sheet) must be thefirst member following the seeded system accounts and exchange rate accounts.

The first child of FCCS_Balance Sheet must be the seeded balanced Balance Sheettop member. Currently either:

FCCS_Total Balance Sheet-Net Asset Approach

Or


4-15

FCCS_Total Balance Sheet-Traditional Approach

The aggregation operator for these accounts can be Addition, Subtraction, orIgnore. Ignore is suggested (but not required) unless you intend to report from the"grouping" member.

The aggregation operator for any other children of the FCCS_Balance Sheet groupingshould ideally be Ignore but can be Addition or Subtraction if reporting from the"grouping" member is required.

Any descendants of the immediate children of FCCS_Balance Sheet must be"Addition" or "Subtraction" and must match the combination of the child and parentaccount types.

Note that this validation is applied to all hierarchies within the FCCS_Balance Sheetgrouping member (with the exception of the seeded Cash and Non-Cash hierarchy). Ifyou wish to create an alternative hierarchy that is not subject to this validation check,the hierarchy can be placed under the FCCS_Income Statement grouping account.

Parent Store or Never Share Members of a Custom Dimension Should Not BeUsed as a Shared Member

Parent members that are Store or Never Share data storage should not be used as aShared member in the custom hierarchy. Applicable to the following dimensions:




A Store or Never Share primary parent member should not be used as aShared member.

Resolution:

Remove the shared member from the alternative hierarchy, create a new parent in thealternative hierarchy and share the level 0 members under the new parent.

Intercompany Elimination Members and Total Eliminations Members Should NotBe Moved in the Hierarchy

The Intercompany Elimination member should not be moved out of the TotalEliminations hierarchy.

The Total Eliminations member should not be moved out of the Total Data Sourcehierarchy.


Intercompany Elimination member should not be moved outside of TotalEliminations.

Total Eliminations member should not be moved outside of Total DataSource.

Resolution:

Move the Intercompany Elimination or Total Eliminations members to the correctlocation in the hierarchy.


4-16

Importing DataAfter you import dimensions, you can populate data by importing data files.

To import data, you must be a Service Administrator or Power User.

You can load data using a text file with sections that map the file data to dimensions.When you load multiple data files, they are loaded in sequential order.

Note:

You should not run reports, books, or batches while data is being loaded.

To import data, perform these tasks:

• Create an import file for each artifact that you want to import. See Creating theData Import File.

• Load the import file or files (you can import multiple dimension files at the sametime). See Loading the Data Import File.

Creating the Data Import FileBefore you begin loading, you must create an import file for each artifact that you wantto import (data, smart lists, and exchange rate tables). The import file must contain aheader record, and then below the header record, a list of data records that you wantto import or update. The file format can be .csv (comma-delimited), or .txt (tab-delimited or other delimiter characters).

For examples of Data Import files, see Example: Data Import File - Periodic View, Example: Data Import File - YTD View, Example: Data Import File - Overrides, and Example: Data Import File - Exchange Rates.

Data Import File FormatThe file format consists of rows and columns. The first row consists of ColumnHeaders. The first Column Header is the Dimension name of the import dimension.After that, there can be members from one other dimension called the driverdimension. The next Column Heading is the Point-of-View, and the last ColumnHeading is Data Load Cube Name.

Each row contains the member of the Load dimension as the first column. The next setof columns is the data value for each of the driver members. The Point-of-View columnhas members of the remaining dimension to uniquely identify the cell to which data isbeing imported. The last column is the Cube name - either Consol or Rates.

Chapter 4Importing Data

4-17

Example: Data Import File - Periodic ViewYou can import periodic data in a monthly frequency. Suppose the following dataexists in the application for the Sales account:

Sales...Jan: 100, Feb: 150, Mar: 120

A data import file would have these rows. The first row is the required file ColumnHeaders:

Period, Sales, Point-of-View, Data Load Cube Name

Jan, 100, "FCCS_Entity Input, ENTITY CURRENCY, England, FCCS_Data Input, FCCS_No Intercompany, FCCS_No Movement, Actual, FY14, Periodic, FCCS_Local GAAP", Consol

Feb, 150, "FCCS_Entity Input, ENTITY CURRENCY, England, FCCS_Data Input, FCCS_No Intercompany, FCCS_No Movement, Actual, FY14, Periodic, FCCS_Local GAAP", Consol

Mar, 120, "FCCS_Entity Input, ENTITY CURRENCY, England, FCCS_Data Input, FCCS_No Intercompany, FCCS_No Movement, Actual, FY14, Periodic, FCCS_Local GAAP", Consol

Example: Data Import File - YTD ViewData can be loaded to Financial Consolidation and Close on a Year-to-date (YTD)basis. If data is loaded to the FCCS_YTD_Input View dimension member instead ofthe FCCS_Periodic member, then Financial Consolidation and Close will populate theperiodic member such that the YTD amount matches the input amount. In all periodsexcept the first period, the prior period YTD amount is subtracted from the YTD Inputamount and the result is written to the Periodic View. In the first period, the YTD Inputamount is written to the Periodic View. The YTD Input amount is then cleared. Notethat this population of the periodic amount is based on a YTD input amount and NOT aClosing Balance input amount (although for Income Statement accounts only, theseare the same).

Closing Balance includes the impact of Opening Balance while YTD excludes OpeningBalance and encompasses movements for the current year only, excluding OpeningBalance. For Closing Balance Input, see the section on the Closing Balance InputHierarchy in Seeded Dimension Members.

Also, note that if you load data on a Quarterly basis in the YTD View, if there areperiods with NoData status between the current period and a period where data wasentered, the in-between periods with NoData calc status are changed to Impacted atthe start of the consolidation process and changed to OK on completion. All of theancestor's status are changed to Impacted for those periods if their status was NoDataprior to consolidation.


4-18

Suppose the following data exists in the application for the Sales account:

Sales...Jan: 100, Feb: 250, Mar: 370

A data import file would have these rows. The first row is the required file ColumnHeaders:

Period, Sales, Point-of-View, Data Load Cube Name

Jan, 100, "FCCS_Entity Input, ENTITY CURRENCY, England, FCCS_Data Input, FCCS_No Intercompany, FCCS_No Movement, Actual, FY14, FCCS_YTD Input, FCCS_Local GAAP", Consol

Feb, 250, "FCCS_Entity Input, ENTITY CURRENCY, England, FCCS_Data Input, FCCS_No Intercompany, FCCS_No Movement, Actual, FY14, FCCS_YTD Input, FCCS_Local GAAP", Consol

Mar, 370, "FCCS_Entity Input, ENTITY CURRENCY, England, FCCS_Data Input, FCCS_No Intercompany, FCCS_No Movement, Actual, FY14, FCCS_YTD Input, FCCS_Local GAAP", Consol

Example: Data Import File - YTD Input and Replace ModeWhen you load data using the Replace mode, the combination of data for thatScenario, Year, Period, and Entity is cleared and replaced with the data in the load file.

When you load data to YTD_Input and use Replace mode for the load file, the systemloads the data from the load file and reverses the YTD values for the Flow accountsthat are not specified in the data load file.

For the first period of a year, there is no YTD data to reverse, so the system appliesthis method for Periods 2-12 or 2-13.

This feature is supported for Administrator, Power User and User data loads. If aPower User or User performs the data load, the system will reverse the YTD values forwhich the user has Write access.

This example shows a data load file to the YTD_Input member in Replace mode. Thefirst row is the required Column Headers:

Period, Sales, Point-of-View, Data Load, Cube Name

Feb, 100, "FCCS_Entity Input, ENTITY CURRENCY, England, FCCS_Data Input, FCCS_No Intercompany, FCCS_No Movement, Actual, FY14, FCCS_YTD_Input, FCCS_Local GAAP", Consol

Feb, 100, "FCCS_Entity Input, ENTITY CURRENCY, Ireland, FCCS_Data Input, FCCS_No Intercompany, FCCS_No Movement, Actual, FY14, FCCS_YTD_Input, FCCS_Local GAAP", Consol


4-19

Results:

The system reverses the YTD values for all the unspecified accounts (that is, allaccounts except Sales that have a value in Prior Periods) in the data load file.

Example: Data Import File - OverridesIf you are using a multi-currency application, you can load different override rates oramounts to different source members. You use the following system members, whichare automatically created for a multi-currency application in the Consolidationdimension:

• FCCS_Overrides

• FCCS_Rate Override

• FCCS_Amount Override

A data import file could have these different amounts:

Entity, Jan, Point-of-View, Data Load Cube Name

E03, 100,"Actual,FY14,FCCS_Periodic,USD,FCCS_Common Stock,FCCS_No Intercompany,FCCS_Mvmts_IssueOfStock,No Product, FCCS_Data Input,FCCS_Local GAAP, FCCS_Amount Override",Consol

E03, 200,"Actual,FY14,FCCS_Periodic,USD,FCCS_Common Stock,FCCS_No Intercompany,FCCS_Mvmts_IssueOfStock,No Product, FCCS_Managed Data,FCCS_Local GAAP, FCCS_Amount Override",Consol

E03, 300,"Actual,FY14,FCCS_Periodic,USD,FCCS_Common Stock,FCCS_No Intercompany,FCCS_Mvmts_IssueOfStock,No Product, FCCS_Other Data,FCCS_Local GAAP, FCCS_Amount Override",Consol

Example: Data Import File - Exchange RatesFor multiple-currency applications, you import rates to the Rates cube.


4-20

A data import file could have these rows. The first row is the required file ColumnHeaders:

Period, Average Rate, Ending Rate, Point of View, Data Load Cube Name

Jan, 1,1,"USD, FCCS_Global Assumptions, From_USD, Actual, FY16, FCCS_Periodic", Rates

Feb, 1,1,"USD, FCCS_Global Assumptions, From_USD, Actual, FY16, FCCS_Periodic", Rates

Mar, 1,1,"USD, FCCS_Global Assumptions, From_USD, Actual, FY16, FCCS_Periodic", Rates

Jan, 2,2,"USD, FCCS_Global Assumptions, From_CAD, Actual, FY16, FCCS_Periodic", Rates

Feb, 2,2,"USD, FCCS_Global Assumptions, From_CAD, Actual, FY16, FCCS_Periodic", Rates

Mar, 2,2,"USD, FCCS_Global Assumptions, From_CAD, Actual, FY16, FCCS_Periodic", Rates

Jan, 3,3,"USD, FCCS_Global Assumptions, From_AUD, Actual, FY16, FCCS_Periodic", Rates

Feb, 3,3,"USD, FCCS_Global Assumptions, From_AUD, Actual, FY16, FCCS_Periodic", Rates

Mar, 3,3,"USD, FCCS_Global Assumptions, From_AUD, Actual, FY16, FCCS_Periodic", Rates

Load MethodsThese options are available for loading a data file into an application.

• Merge—Use this option to overwrite the data in the application with the data in theload file. Each record in the data load file is imported into the cell, replacing the oldvalue, if any.

• Replace—Use this option to replace data in the application. In Replace mode,before the first record for a specific Scenario/Year/Period/Entity/Mapped DataSource is encountered, the entire combination of data for that Scenario, Year,Period, Entity, and Mapped Data Source is cleared, whether manually entered orpreviously loaded.


4-21

• Accumulation Type—Select one of these options to accumulate the data in theapplication with the data in the load file:

– None—Each record in the data import file replaces the existing value in thedatabase for the record.

– With Database—The data is added to the existing value of the cell.

– Within File—The system accumulates the cell values that are within the file.

Load Method ExamplesThe following examples show how the load options work. Suppose the following dataexists in the application:

Actual, FY15, Jan, California, Sales: 20,000

Actual, FY15, Jan, California, COGS, 10,000

Actual, FY15, Jan, California, Expenses: 5,000

A load file has the following data:

Entity, Sales, COGS, Point-of-View, Data Load Cube Name

California, 10000, 15000, ("Actual","FY15","Jan"), Consol

California, 25000, 5000, ("Actual","FY15","Jan"), Consol

These examples how the data after the import using these option combinations:

Merge, None

Actual, FY15, Jan, California, Sales : 25,000 (second record wins)

Actual, FY15, Jan, California, COGS : 5,000 (second record wins)

Actual, FY15, Jan, California, Expenses : 5,000


4-22

Replace, None

Actual, FY15, Jan, California, Sales : 25,000

Actual, FY15, Jan, California, COGS : 5,000

Actual, FY15, Jan, California, Expenses : #MI (Replace clears everything in SYPE combination)

Merge, With Database

Actual, FY15, Jan, California, Sales : 55,000 (Accumulate two records with existing value in database)



Replace, With Database



Actual, FY15, Jan, California, Expenses : #MI (Replace clears all the data before the import)

Merge, Within File





4-23

Replace, Within File



Actual, FY15, Jan, California, Expenses : #MI

Loading the Data Import FileAs a best practice, do not load zero values.

To import the data file:


2. Click Overview and from Actions, select Import Data.

3. Click Create.

4. Select the location of the data import file:

• Local—Imports the data import file from a location on your computer.

• Inbox—Imports the data import file from the server.


• Comma delimited

• Tab delimited

• Other—Enter the delimiter character that is used in the import file. For a list ofsupported delimiter characters and exceptions, see Other Supported DelimiterCharacters.

6. From Import Mode, select a mode:

• Merge - Overwrite data in the application. Each record of data is imported intothe cell, replacing the old data, if any.

• Replace - Replace data in the application. In Replace mode, before the firstrecord for a specific Scenario/Year/Period/Entity is encountered, the entirecombination of data for that Scenario, Year, Period, and Entity is cleared.

7. From Accumulation Type, select a type:

• None - Replace the existing value in the database for the record.

• With Database - Add the data to the existing value of the cell.

• Within File - Accumulate the cell values that are within the file.

8. Enter or select the source file:

• If you selected Local, click Browse to navigate to the file.

• If you selected Inbox, enter the name of the file in Source File.

9. From Date Format, select a format.


4-24

10. Optional: If the selected location is Inbox, click Save as Job to save the importoperation as a job, which you can schedule to run immediately, or at a later time.

11. Optional: If the selected location is Local, click Validate to test whether theimport file format is correct.

12. Click Import.

13. From the information message that the data was submitted successfully, click OK.

14. To view details about the import process, click Application, click Jobs, viewRecent Activity, and then click the link for the import to view the details.

Exporting DataYou export data from the Applications page.

As an alternative, you can export data using Data Management. Create a customapplication as the source using Financial Consolidation and Close, then export thedata and save the export file from within Data Management.

To export data:


2. Click Overview, and from Actions, select Export Data.

3. Click Create.

4. On the Export Data page, select the target location of the data export file:

• Local—Saves the data export file to a location on your local computer.

• Outbox—Saves the data export file to the server.

5. For Cube Type, select either Consol or Rates.


• Comma delimited—Creates a comma-delimited .csv file for each artifact.

• Tab delimited—Creates a tab-delimited .txt file for each artifact.

• Other—Creates a .txt file for each artifact. Enter the delimiter character thatyou want to use in the export file. For a list of supported delimiter charactersand exceptions, see Other Supported Delimiter Characters.

7. For Smart Lists, specify Export Labels or Export Names.

8. For Dynamic Members, select whether to Include or Exclude.

9. Select the slice of data to be exported.

The Account dimension, which is the only dense dimension in the system, must bein the Column.

10. Optional: If the selected location is Outbox, click Save as Job to save the exportoperation as a job, which you can schedule to run immediately or at a later time.

11. Click Export, and then specify where to save the data export file.

To reduce the size of data export file, if a form has an entire row of #missingvalues, the row will be omitted from the data export file.

Chapter 4Exporting Data

4-25

Viewing Data Import and Export StatusThe Import and Export Status page displays details of recent jobs.

To view the status of a data import and export:


2. Click Jobs.

3. From Recent Activity, click the name of the import or export job to view thedetails.

4. From Show, select an option:

• Errors

• Warnings

• Information

• All

Importing Data Using Data ManagementData Management enables you to integrate data from an external source system withFinancial Consolidation and Close. Data from your source system is exported to flatfiles or Microsoft Excel files. You map the data in your flat files to your FinancialConsolidation and Close dimension structure and then import the data to yourapplication. For example, you can define Period mappings to map source systemPeriod names and Keys to your application Periods and Years. Category mappingsmap source system data categories to your application data categories andfrequencies.

Before using Data Management to load data from an external system, administratorsperform these setup tasks:

• Define Import Formats to define the layout of the source data files. Specify how tomap columns or fields in your data source to your Financial Consolidation andClose data structure.

• Create Locations to associate with the data integration. Each location has its ownData Load Mappings and Data Load Rules.

• Define Data Load Mappings for each location, which map source system membernames for each dimension to the corresponding application member names.

• Create Data Load Rules, which specify a data file to load into a selected Categoryand Period. If you want to the Data Load Rule to run at a later time, you can selectfrom Schedule options such as Daily or Weekly.

The Setup process enables you to import the data to Data Staging tables so that youcan verify that your settings and member mappings are correct before loading intoyour application.

After you define Data Management mappings, you can update the mappings and DataLoad Rules as needed. For example, if new accounts or dimension members havebeen added for a Location, or if member names have changed, you can update themapping of source system member names to your application member names.

Chapter 4Viewing Data Import and Export Status

4-26

You can load data from Data Management if you have the Service Administrator orPower User role.

After the data import process is finished, you can open a data form to verify that thedata was loaded correctly. You can Drill Through from a cell in the data form to viewthe source data that was loaded into the cell.

To access Data Management:

1. Click the Navigator icon , and then under Integration, click Data Management.

2. Click the Setup tab, and follow the procedures in the Administering DataManagement for Oracle Enterprise Performance Management Cloud guide.

Watch the following videos for information on data integrations:

Setting Up Data Integrations, and Running and Updating Data Integrations.

Exporting Data Using Data ManagementYou can export data from your application for analysis or for import into other systems.You can extract data using Data Management, stage it in Staging Tables, and thenexport it to a delimited flat file.

You can export data from Data Management if you have the Service Administratorrole.

Service Administrators must first set up the data export by performing the Setup tasksin Data Management:

• Add a Custom Target Application. The data that you extract is stored in the TargetApplication before export to a flat file.

• Specify Application Details and Dimension Details for the extract process.

• Define Import Formats to map data from the Source system to the dimensions inyour Target application.

• Create Locations to link the import formats to Data Load rules.

• Define Data Mappings for each location, which map source system dimensionmember names for each dimension to the corresponding Target applicationnames.

• Create Data Load Rules to run the data extract process.

After you run the data export process, the Status column displays the current status.The data is staged in Data Management. You can download the data file from theProcess Details page and save the data file.

To access Data Management:

1. Click the Navigator icon , and then under Integration, click Data Management.

2. Click the Setup tab, and follow the procedures in the Administering DataManagement for Oracle Enterprise Performance Management Cloud guide.

Watch the following video for information on exporting data using Data Management:

Chapter 4Exporting Data Using Data Management

4-27



Extracting Data Using Data Management.

Data IntegrationsData Integration is the mechanism by which integration processes are performed inFinancial Consolidation and Close. You can define file-based and direct integrationsources, create mapping rules to translate source data into the required target format,and execute and manage the periodic data loading process. Common integrationtasks are done using an easy-to-navigate interface that supports and conforms to howyou work.

You can access Data Integration directly from Financial Consolidation and Close.From the Data Integration page, you can create an integration. You can also run anexisting integration to extract data from the source and load it to target based on anyfilter criteria.

See Administering Data Integration for Oracle Enterprise Performance ManagementCloud, and the "Customers Using Oracle Financial Consolidation and Close Cloud"section in Administering Data Management for Oracle Enterprise PerformanceManagement Cloud.

To access Data Integration, you must be a Service Administrator, Power User, orUser.

To access Data Integration:

1. On the Home page, select Applications, and then select Data Exchange.

The Data Integration page is displayed.

2. To search for an integration, click Search and search by Name, Location, Source,or Target.

3. To sort the list of integrations, specify a condition. Sort results can be listed inAscending order (A to Z) or Descending order (Z to A).

4. To create an integration, click Create Integration

, and use the Create Integration wizard to specify the integration details.

5. To edit an integration, double-click an integration from the list and edit integrationdetails as needed.

6. To run an integration, select an integration from the list and click Run

.

Copying DataYou can copy data from a source POV to a destination POV. You can copy specificScenario, Year, Period, and Entity dimension members to destination dimensionmembers. This enables you to perform a bulk copy of data along with the supportingdetails such as journals and Supplemental Data Manager details. You can copy datafrom multiple periods and entities and data source members. You cannot copy data toa locked entity.

Chapter 4Data Integrations

4-28


To copy data, you must be a Service Administrator with Write access to the data.

You can copy these types of data:

• Regular data (including journals)

• Rate data—exchange rate data

• Override data—for historical accounts

For Regular Data, you can specify whether to merge or replace the data. You caninclude journal detail in the copy process for Regular Data if you select the "JournalInput" Data Source member. When you copy data that includes posted journals, thesystem creates the journal in the destination POV and automatically posts the journal.

The following members in these dimensions are fixed and not available for selection inthe Copy process:

• View - Periodic

• Currency - Entity Currency

• Account - <all members>

• Movement - <all members>

• Multi-GAAP - <all members>

• Custom- <all members>

• ICP - <all members>

• Consolidation - Entity Input

After the Copy process, the Calculation Status for all destination entity data changes toImpacted. You must run consolidation to update the values.

The system does not include entities with NoData as part of the Copy process.

To copy data:

1. On the Home page, click Application

2. Click Overview, then from Actions, select Copy Data.

3. Select the items that you want to copy:

• Regular Data

• Override Data

• Rate Data

4. For Regular Data, from Copy Options, select an option:

This option is only available for Regular Data. Rate Data and Override Data arealways copied using Replace mode.

• Replace—All destination data cells are replaced by the source data cellvalues.

• Merge—The source data cell values are merged into the destination data cellvalues. Any existing destination data cells that are not part of the source copywill remain after the merge.

5. For Source, select a Scenario, Year, Period or range or periods, and one or moreEntity members from the Member Selector, and click OK.

Chapter 4Copying Data

4-29

If you copy a range of periods, the number of source periods must equal thenumber of destination periods. Only Input base members below "FCCS_Total DataSource" are available for selection.

If you copy Rate Data, you do not need to select any Entity members.

6. Optional: From Data Source, select one or more members from the MemberSelector, and click OK.

7. Optional: To copy Supplemental Detail, select one or more Supplemental DetailData Source members to copy, then from Supplemental Data Member, select abase Data Source member for the destination.

You cannot select a Data Source member for the destination that was alreadyselected as part of the copy process.

8. For Destination, select a Scenario, Year, Period or range of periods, and one ormore Entity members to which to copy data.

9. Click Run to submit the copy data task, and at the prompt, click Yes to continue.

The system displays a message that the copy data task is submitted. You canmonitor the task status from the Jobs console. From the Application page, clickJobs, and then click on the job for more details.

Clearing DataYou can clear data for selected entities from a specific Scenario, Year, and period orrange of periods. You cannot clear data for a locked entity.

To clear data, you must be a Service Administrator with Write access to the data.

You can clear these types of data:

• Regular data (including journals)

• Rate data—exchange rate data

• Override data—for historical accounts

To clear data with journal detail, select the "Journal Input" Data Source member. Thesystem unposts the journal and clears the data cell value. It does not delete thesupporting unposted journal. If you want to later remove the unposted journal, you cando so manually.

The following members in these dimensions are fixed and not available for selection inthe Clear process:

• View - Periodic

• Currency - Entity Currency

• Account - <all members>

• Movement - <all members>

• Multi-GAAP - <all members>

• Custom- <all members>

• ICP - <all members>

• Consolidation - Entity Input

Chapter 4Clearing Data

4-30

After the Clear process, the Calculation Status of the entities changes to Impacted.You must run consolidation to update the values. The status of a parent entity alsochanges to Impacted if you clear data of its children. The system does not includeentities with NoData as part of the Clear process.

To clear data:

1. On the Home page, click Application

2. Click Overview, then from Actions, select Clear Data.

3. Select the items that you want to clear:

• Regular Data

• Override Data

• Rate Data

4. For Target, select a Scenario, Year, Period or range or periods, and one or moreEntity members from the Member Selector, and click OK.

5. Optional: To clear Supplemental Detail, select a Data Source member.

6. Click Run to submit the clear data task, and at the prompt, click Yes to continue.

The system displays a message that the clear data task is submitted. You canmonitor the task status from the Jobs console. From the Application page, clickJobs, and then click on the job for more details.

Refreshing the DatabaseOn the Application page, you can refresh the application database, which is used tostore data in the application. Databases are structured according to dimensions,hierarchical members, attributes, and other data specified in an application.

You must refresh the application database whenever you change the applicationstructure. Changes made to an application aren’t reflected to users performing dataentry and approval tasks until you refresh the databases for the application. Forexample, when you modify properties of an Entity member, add a Scenario, or changeaccess permissions, these changes are stored in the relational database until yourefresh the application database.

Before refreshing the database, you can choose whether to enable all users or just thecurrent administrator to use the application in maintenance mode during the refreshprocess. You can also log off all users, and you can terminate any active applicationrequests. After the database refresh, you can enable users to use the application.

Caution:

Before you refresh, a best practice is to back up your outline file and exportdata from all databases.

To refresh the database:


2. Click Overview, then from Actions, select Refresh Database.

Chapter 4Refreshing the Database

4-31

3. On the Refresh Database page, click Create.

4. Make selections for before and after the database refresh:

• Before Refresh Database

– Enable use of the application for—Allows All users or Administrators(or the current logged-in administrator) to access the application inmaintenance mode during the refresh.

– Log off all users—Logs off all users before starting the refresh

– Kill all active requests—Terminates any active requests in theapplication before starting the refresh

• After Refresh Database

Enable use of the application for—Allows All users or Administrators touse the application after the refresh

5. Choose an option:

• To refresh the database now, click Refresh Database, review the confirmationmessage, and then click Refresh.

• To schedule a database refresh job, click Save as Job, name the job, andthen click Save.

Note:

If you schedule a recurring refresh database job, the refresh joboptions that you select are applicable each time the job is run. Toedit your selections, click the name of the job in the Jobs console,and then click Save.

Restructuring CubesYou can run the Restructure Cube job to perform a full restructure of a block storagecube to eliminate or reduce fragmentation. This will also remove empty blocks.

This feature is not applicable for an Aggregate Storage cube (ASO).

Note:

You should not run this job during the application maintenance time. Youalso should not launch a consolidation process while the Restructure Cubejob is running.

When you perform this operation:

• Users will be prompted to log out.

• You must manually set the application to Maintenance mode.

• After the Restructure Cube job is run, you must manually turn off Maintenancemode.

Chapter 4Restructuring Cubes

4-32

• Users will then be informed that the application is available.

Running the Restructure Cube Job

To restructure a cube:


2. Click Jobs.

3. Click Schedule Jobs.

4. Select Restructure Cube, then select Run Now, and click Next.

5. Select when to run the job:

• Run Now

• Schedule starting from, and then select the date, time, and time zone.

6. Enter a Name for the job.

7. For Recurrence pattern, select how often to run the job, and optionally, select anEnd Date.

8. Click Next to continue.

9. Select a Cube from the drop-down list, then click Next.

10. Review your selections and then click Finish.

The Restructure Job is submitted on the Jobs page. Make sure that the job iscompleted by periodically refreshing the page.

Determining When to Restructure a Cube

To determine when to restructure a cube:

1. On the Home page, click Application, and then click Consolidation.

2. From the Consolidation Process page, click a user-editable rule, for example, FinalCalculations.

A user-editable rule is indicated by the User icon. When you click a rule, itlaunches Calculation Manager in a separate tab in the browser.

3. In Calculation Manager, click the Database Properties toolbar button.

4. From Database Properties, expand the "Planning" folder, and the applicationname, and check if the application's databases are running. There should not be ared box for the database.

5. Click on Consol database and navigate to the Statistics tab.

6. Check the Average clustering ratio property.

• If the value is close to 1 (1 is the maximum), there is no need to restructure thecube.

• If the value is not close to 1, for example, 0.0132828, you should restructurethe cube.

Chapter 4Restructuring Cubes

4-33

Removing an ApplicationRemoving an application deletes it and all of its contents. Any scheduled jobs for theapplication will also be deleted. This action cannot be undone. As a best practice, youshould back up the application first.

To remove an application:


2. Click Overview, then from Actions, select Remove Application.

3. Review the confirmation message. To continue, click Yes.

Scheduling MaintenanceBy default, Financial Consolidation and Close automatically performs dailymaintenance starting at midnight local time. During the nightly maintenance window,the system performs backups, applies any patches, recycles the application, and soon. If you prefer, you can schedule daily maintenance to occur at another time.

During daily maintenance, the service automatically creates a backup snapshot of dataand artifacts. When daily maintenance executes, it replaces the prior backup snapshotwith a new backup snapshot. You should schedule the execution of the EPMAutomate Utility on a daily basis to download the backup snapshot to a local computer.

To schedule maintenance:

1. On the Home page, click Tools.

2. Click Daily Maintenance.

3. Select the local time zone and the time of day for maintenance.

4. Click Save.

Using the Inbox/OutboxThe Inbox/Outbox enables you to upload files to the server/inbox and download thefiles from the server to your local computer. It also enables you to view the files thatare in the Inbox/Outbox and then use the files to schedule import and export jobs. Youcan filter by name, refresh the listing, and upload files from the server.

To view files in the Inbox/Outbox:


2. Click Overview, then from Actions, select Inbox/Outbox Explorer.

3. Optional: To filter the list of files, click Filter, enter a name, and then click Apply.

4. Optional: To refresh the list of files, click Refresh.

To upload a file:

1. Click Upload.

2. In the Upload File box, click Browse to select a file.

3. Optional: Click Overwrite file.

Chapter 4Removing an Application

4-34

4. Click Upload File.

Working with Activity Reports and Access Logs

About Activity Reports

The Activity Report, which is automatically generated for each day, enables ServiceAdministrators to understand application usage. It also helps streamline applicationdesign by identifying calculation scripts and user requests that impact applicationperformance. Additionally, the report may be used to compare service usage andperformance to a prior report. Information contained in this report includes:

• The number of users who accessed the service

In addition to the average usage duration for the number of users on a specificday, the report provides the number of users who logged on each day over the lastweek, the last seven days, and the last 30 days.

• Percentage of UI requests that took more than 10 seconds to finish, and top 7requests that took the most time to complete

A UI request is a user action such as signing in, loading data, working with forms,and validating rules. The section on the top 30 worst performing user actionsidentifies the user, duration of the action, activity that the user was performing, andthe screen that the user was on.

• Top 15 user interface requests by execution

• Average service response time by hour and the number of users by usageduration

• Top 10 most active users and top least active users by duration

• Top 5 worst performing calculation script commands over 1 minute

• Top 10 calculation scripts by duration

This table identifies the business rules that took the longest time to run. Availableinformation includes the name of the calculation script, the number of times thescript was run, and the duration.

• Unsupported browser versions and the number of users who used them

• Browser versions that were used to access the service and the number of userswho used them

• Application design changes that occurred during the report period

This section provides an audit trail of application design changes, if any.Information includes application name, type and name of the modified designartifact, identity of the user who modified the artifact, and the time the changeswere made. Data changes are not reflected in this table.

• Oracle Smart View for Office versions being used and the number of users whouse them

• 10 most active Smart View users who not use the current version of Smart View

Chapter 4Working with Activity Reports and Access Logs

4-35

Note:

The Application Activity Report uses the administrator’s time zone, which isset in the Maintenance Window screen.

About Access Logs

You can download a Comma Separated Value (CSV) file that provides detailedinformation on the IP Addresses that accessed the service and their activities. Theaccess log is generated each day. Information contained in the access log includesdate and time, the resources that users accessed, duration of user activity, the IPaddresses from which users connected to the service, and the actions that usersperformed in the service.

Activity Report and Access Log Retention Policy

Oracle retains Activity Reports and Access Logs for the last 60 days only.Use the downloadfile command to download activity reports and access logs from theOutbox to a local computer if you need them for audit purposes. See CommandReference in Working with EPM Automate for Oracle Enterprise PerformanceManagement Cloud.

To view Activity Reports and to download Access Logs:

1. Access the service.

2. Click Application, then Overview, and then Activity Reports.

3. Perform an action:

• To open an activity report, click View under Activity Report in the row thatindicates the day for which you want to view the report.

• To download an access log, click Download under Access Log in the rowthat indicates the day for which you want to download the log.

Chapter 4Working with Activity Reports and Access Logs

4-36

5Managing Application and System Settings

Related Topics

• Specifying Application Settings

• Specifying a Default Alias Table, and Setting Member and Alias Display Options

• Specifying Number Formatting Preferences

• Defining User Variables

• Customizing Your Application Appearance

• Making Announcements

• Specifying Artifact Labels

• Working With the Artifact Labels Grid

• Adding Languages and Defining Localized Artifact Labels

• Exporting and Importing Artifact Labels for Editing

• Reviewing Artifacts

Specifying Application SettingsYou can control many aspects of the application and the system, such as:

• How to display thousands, decimals, and negative numbers in forms

• Approvals actions to be taken when you're out of the office

• Actions about which you want to be notified

• Display the full names of users rather than user IDs

Note:

Administrators specify defaults for the current application. However, userscan override these application defaults by setting preferences to controlmany aspects of the application, such as their profile photo and hownumbers display in the application.

To set user preferences, see "Setting Your Preferences" in Working withOracle Financial Consolidation and Close Cloud.

1. Click Application, and then click Settings.

2. Specify defaults for the following application settings:

• Alias Setting—For option descriptions, see Specifying a Default Alias Table,and Setting Member and Alias Display Options

5-1

• Number Formatting—For option descriptions, see Specifying NumberFormatting Preferences

• Approvals—Select whether to display aliases, show the approval units thatare not started, and show approval units as aliases in approvals notifications

• Notifications—Enable notifications for task lists, approvals, and job console

– Task Lists - select this option if you want an email notification when youneed to perform actions on a task list.

– Approvals - select this option if you want an email notification when youneed to perform actions on Approvals.

– Job Console - select this option if you want an email notification when ajob that you launch is completed or generates an error.

You can specify task notification types and frequency from User Preferencesunder Tools. See "Setting Up Email for Notifications" in Working withOracle Financial Consolidation and Close Cloud.

• Page—Set defaults for indenting members on a page and setting the numberof items on the page drop-down.

Note:

The Number of Items on the Page Drop-down option lets youshorten the member list so that the Search box can be more easilyseen. If the list is shortened to 10 members, for example, then youwon't need to scroll to see the Search box.

• Other Options—Set options for date format, attribute dimension date format,partial grid fetch size ,whether to suppress application management options inOracle Smart View for Office, whether to enable data loads for ad hoc read-only roles, and whether to enable Consolidation Rules Logging.

– Date Format—Select a date format, or select Automatically Detect touse your system's locale settings.

– Attribute Dimension Date Format—Select a date format for attributedimensions.

– Partial Grid Fetch Size—If large forms require significant time to open,select this option to open part of a form. Enter the number of rows andcolumns to open, separated by a comma (,).

– Suppress Application Management Options in Smart View—When anew application is created, all application management options aredisplayed by default to administrators in Smart View. You can choose tohide or display the application management options. If you select Yes,application options are not displayed in Smart View. If you select No,application options are displayed in Smart View.

– Enable consolidation rules logging—Select to enable logging forconsolidation rules.

3. Specify options for the following system settings:

Chapter 5Specifying Application Settings

5-2

• Display Users’ Full Names—If selected, the system displays the user's fullname (for example, Victoria Hennings). If cleared, the system displays theuser's ID (for example, VHennings).

• Include Shared Members in Cube Refresh

• Email Character Set, for example, UTF-8 or Regional Setting.

• Business Rules Notification—If set to Yes, notifies users or groups whenrules (which are enabled for notification in Calculation Manager) arecompleted or encounter errors. In Notify These Users, select the users orgroups to notify.

• Allow Drill Down on Shared Members in Ad Hoc Form—Yes enablesdrilling on shared members in an ad hoc grid. No disables drilling on sharedmembers in an ad hoc grid.

• Minimize Approval Process Emails—Reduces the number of emails a userreceives when using Approvals. The default is No.

If Yes is selected, only one email notification (for the approved parent entity) issent to the new owner of the approval unit. Separate email notifications aren’tsent for every child entity in the approval unit hierarchy. If No is selected,owners that are set at parent nodes will receive emails for the selected nodeas well as an email for each child node.

• Enable Use of the Application for—Determines whether users can accessthe application in administration mode, such as during backups. When youselect Administrators, if any nonadministrative users are logged on to theapplication, they are forced off the system and will not be able to log on. Torestore access to an application for all users, select All users.

• Assign Application Owner—Assign ownership of the application to anotheradministrator.

• Enable the Display of Substitution Variables—Set how substitutionvariables display in the Member Selection dialog box when users respond toruntime prompts in business rules. Display All displays all substitutionvariables. Display None displays no substitution variables. Enable Filteringdisplays only substitution variables that are valid for the runtime prompt.

• Smart View Suppression Behavior—Choose a suppression behavior inOracle Smart View for Office for cases where rows and columns containmissing data or zeroes.

– Legacy (default)—Suppresses rows, or columns, or both that contain NoData/Missing or Zero, but not both.

– Standard—Suppresses rows, or columns, or both that contain both NoData/Missing and Zero.

• Smart View Ad Hoc Behavior—Choose to enable enhanced ad hoc featuresand behaviors in Smart View.

– Native (default)—Does not enable enhanced ad hoc features.

– Standard—Enables enhanced ad hoc features.

The enhanced ad hoc features and behaviors are:

– In-grid POV—POV members are placed on the grid instead of in the POVtoolbar.


5-3

– Submit without refresh—Using the default Submit Data button in theSmart View ribbon, all cells in a grid are submitted, including all data cellsthat have been explicitly modified (made dirty) and those that were notmodified. For this operation, all data cells are marked dirty and submitted.Once the submit operation is complete, the entire grid will be refreshed.

– Free-form support—Supports empty columns and rows anywhere in a gridand changing the alias table. Additionally, supports member auto-refreshwhere deleted members are returned to the grid upon refresh.

– Multiple-grid ad hoc—Supports multiple ad hoc grids on the same Excelworksheet. With multiple-grid ad hoc, you can submit data from any gridon the sheet. Grids based on aggregate storage cubes and block storagecubes are supported on the same sheet. Each grid is independent; forexample, if required, you can change the alias table for only one grid onthe sheet.

• Export EPM Cloud Smart List textual data during daily maintenance forincremental data import—Choose whether to perform a complete exportduring the daily maintenance process or to create an application backup:

– Yes (default)—Performs a complete export, such that data, includingSmart List data, can be incrementally imported to an application (thisoption may lengthen the maintenance process duration)

– No—Creates an application backup during the maintenance process, suchthat data can be used as part of a full restoration.

• Link Accounts by Default—For block storage (input) cubes, select whetherto XREF linked account members by default.

– Yes (default)—XREFs will be created on account members, and theapplication will work the same way it has in earlier releases.

– No—XREFs will not be created for account members, which may improvethe application’s performance. With No selected, after Cube Refresh isrun, all existing XREFs on account members will be deleted, and non-source cubes will no longer show data from the source cube.

Note:

HSP_LINK and HSP_NOLINK UDAs on specific account membersoverride the XREF setting for those account members. For example,if this option is set to No and you use the @XREF function to look up adata value in another cube to calculate a value from the currentcube, you can add theHSP_LINK UDA to such members to create the@XREF function only for these specific members. If this option is set toYes, HSP_NOLINK works the same way it worked in earlier releasesand prevents XREFs from being created on specific members.

4. Click Save to save the application settings.


5-4

Specifying a Default Alias Table, and Setting Member andAlias Display Options

If you create alias tables with aliases for dimensions and members, you can select adefault alias table for the application. You can set preferences for which set of aliases(stored in an alias table) to use for displaying member and dimension names.

To select the application’s default alias table:


2. Click Settings.

3. From Alias Table, select a default alias table.

4. In Member Name/Alias Display, select the option that enables the type ofmember data to be displayed on the Member Selector throughout your application:

• Default—The data determined by the form, grid, or dimension settings

• Member name—Only member names

• Alias—Only member aliases, if defined

• Member name : Alias—Names followed by aliases, if defined

• Alias:Member name—Alias, if defined, followed by the names

5. Click Save.

Specifying Number Formatting PreferencesYou can specify number formats, such as how to display thousands, decimals, andnegative numbers in forms. Your selections apply to all currencies, in all forms that youhave access to in the current application.

You can set these options:

• The thousands separator (None, Comma, Dot, or Space)

• The decimal separator (Dot or Comma)

• The display of negative numbers (A Minus sign before the number (Prefixed), orafter the number (Suffixed), or the number surrounded by parentheses)

• The displayed color for negative numbers (Black or Red)

To change the format of displayed numbers:

1. On the Home page, click Application, and then click Settings.

2. From the Application Settings page, under Number Formatting, select formatoptions:

Chapter 5Specifying a Default Alias Table, and Setting Member and Alias Display Options

5-5

Option Example

Thousands Separator None: 1000

Comma: 1,000

Dot: 1.000

Space: 1 000

You can enter values with or without athousands separator.

Decimal Separator Dot: 1000.00

Comma: 1000,00

You can enter values with or without adecimal separator.

Negative Sign Prefixed Minus: -1000

Suffixed Minus: 1000-

Parentheses: (1000)

Negative Color Black: Negative numbers are black

Red: Negative numbers are red

3. Click Save.

Note:

Formatting selections take effect when you click outside the cell. If youselect a setting other than Use Application Defaults for the Thousandsseparator or the Decimal separator, you must change both separators.You cannot select the same option for the Thousands and Decimalseparators.

Defining User VariablesYou can set user variables to limit the number of members displayed on a form,helping users focus on certain members. For example, if you create a user variablecalled Division for the Entity dimension, users can select a member for their owndivision.

The User Variables page lists the user variables that are defined for the application,with their name and dimension members.

To set up user variables, see Working with User Variables.

To view user variables:

1. On the Home page, click Tools and then click User Variables.

2. Click the Member Selector next to the variable to change.

3. On Member Selection, select members, and then click Save.

Chapter 5Defining User Variables

5-6

Customizing Your Application AppearanceYou can use Appearance to customize the appearance of pages, to change thetheme, or for example, to add your company logo to the Home page.

Note:

To customize your application appearance, you must be a ServiceAdministrator.

To customize the appearance of your display:

1. On the Home page, click Tools, and then click Appearance.

2. Specify a logo or background image or select another theme.

Note the following:

• Both the logo and background image can be customized. Any logo imagesmaller than 125px wide and 25px high can fit without scaling. For large imagelogos, Oracle recommends you maintain a 5:1 ratio so the image is scaledwithout distortion.

The default size for the background image is 1024x768. You can use a largerbackground image, however the image is scaled to fit the resolution setting ofyour display and the image is centered horizontally. If you want yourbackground image to fit both a browser and a mobile device, Oraclerecommends that you size the image so that it fits your biggest screen (orhighest resolution device).

• The logo and background image files must be accessible by URL. Importingimage files is not supported.

3. Click Save.

4. To see your updates, sign out of the application, and then sign in again.

Making AnnouncementsAdministrators can create and send announcements to users about upcoming events,such as system maintenance. Announcements are displayed in the Announcementsarea on the application's Home page.

To create an announcement:

1. On the Home page, click Tools, and then click Announcements.

2. Click Create.

3. Enter the announcement information:

Subject - the purpose of the announcement

Start Date - when to send the announcement.

End Date - optional.

Chapter 5Customizing Your Application Appearance

5-7

Content. You may need to select an editing mode (rich text or source code)before entering text.

4. To save the announcement, click Save and Close.

Specifying Artifact LabelsThe Artifact Labels page on the Tools cluster enables administrators to customizeartifact labels (artifact names, descriptions, and so on) based on the user's browserlocale.

A few examples:

• If you create a form with a cryptic name that you don't want displayed to the user,you can define a meaningful name for the form that is displayed in the language ofthe user.

• If you want to create a useful instruction for an artifact that only displays in thelanguage of the user, for example:

"This formula calculates the number of regular employees away on a Leave ofAbsence."

Related Links

• Working With the Artifact Labels Grid

• Adding Languages and Defining Localized Artifact Labels

• Exporting and Importing Artifact Labels for Editing

Working With the Artifact Labels GridThe Artifact Labels page displays an Excel-style spreadsheet grid that is filtered byartifact and property type.

The row axis of the grid displays the artifacts and their properties.

The column axis of the grid displays the following columns:

• Artifact—The type of artifact (for example, Task List or Rule)

• Property—The artifact's property type (for example, Name, Description, and soon)

• Default—Displays the artifact labels that were defined when the artifact wascreated.

When a language is added, a new column displays to the right of the Default column.

To view and filter the Artifact Labels grid:

1. Click Tools, and then click Artifact Labels.

2. To filter:

a. Click , and then select the artifacts you want to work with. For someartifacts, you can further filter by property type.

b. Click Apply to close the Filter window and display the artifact grid filtered byartifact type and property type.

Chapter 5Specifying Artifact Labels

5-8

Adding Languages and Defining Localized Artifact LabelsAdministrators can add a language for a given artifact to the Artifact Labels grid froma list of supported languages. You can select only one language at a time. When youadd a language, a new column for that language is added to the grid to the right of theDefault column. The cells in the language-specific column are editable.

Tip:

Use this method to add labels directly in the artifact labels grid. This methodis ideal if you only need to add or update a few labels at a time. For bulkchanges or edits on artifact labels; for example, terminology changes thataffect multiple labels, use the export feature to edit in Excel, then import. See Exporting and Importing Artifact Labels for Editing.

To add a language:


2. Click , and then select the artifacts you want to work with. For some artifacts,you can further filter by property type.

3. Click Apply.

4. Click Add Language.

5. Select from the list of supported languages.

6. In the language-specific column, enter artifact labels into the editable cells for eachartifact property (Name, Description, and so on).

7. Click Save.

Note:

When you define a localized artifact label for the Default navigation flow (forexample, editing the name of an icon on the Home page), your update willautomatically propagate to all navigation flows. However, if you define alocalized artifact label for another navigation flow that isn't the Default flow,then that update will override the label coming from the Default flow.

Exporting and Importing Artifact Labels for EditingYou can export all the artifact labels in a specific language to edit them. The labels areexported in an Excel file format (XLSX). After you edit the labels, you can import themback into the application.

Chapter 5Adding Languages and Defining Localized Artifact Labels

5-9

Tip:

Use this method for bulk changes or edits on artifact labels by language; forexample, terminology changes that affect multiple labels. For updates toindividual artifact labels, you can edit them directly in the artifact grid.

To export and import artifact labels for editing:


2. Click , and then select the artifacts you want to work with. For some artifacts,you can further filter by property type.

3. Click Apply.

4. Click Actions.

• To export artifact labels:

a. Click Export.

b. Select the target environment of the export file:

– Local—Saves the export file to a location on your local computer.

– Outbox—Saves the export file to the server.

c. Choose a language.

d. Click Export.

• To import artifact labels:

a. Click Import.

b. Select the location of the import file:

– Local—Loads the import file from a location on your computer. ForSource File, click Browse to select the import file on your computerfor the artifact you're importing.

– Inbox—Loads the import file from the server. Enter the name of thefile in Source File.

c. Click Import.

Reviewing ArtifactsTo review the artifacts in your application:

1. Click Application, then Configure, and then select a business process.

2. From the Actions menu, select Review Modified Artifacts.

3. Click Filter to select different artifact types.

The system displays the predefined artifacts, and you can see if modificationshave been made to the artifacts.

Chapter 5Reviewing Artifacts

5-10

4. To undo customizations to predefined artifacts, select the artifacts, and then clickRestore.

Chapter 5Reviewing Artifacts

5-11

6Connecting Subscriptions in EPM Cloud

Related Topics

• About Connecting EPM Cloud Subscriptions

• Considerations When Migrating Cross-Subscription Connections

• Creating, Editing, and Deleting Connections to Other EPM Cloud Subscriptions

• Common Connection Errors and Resolutions

• Navigating Across EPM Cloud Subscriptions

• Customizing Navigation Flows to Access Other EPM Cloud Subscriptions

About Connecting EPM Cloud SubscriptionsOverview

Service Administrators can connect multiple EPM Cloud subscriptions of the followingtypes:

• Planning

• Financial Consolidation and Close

• Tax Reporting

• Profitability and Cost Management

• Account Reconciliation

• Narrative Reporting

• Oracle Strategic Workforce Planning Cloud

Once administrators set up the connections, users who have access across EPMCloud subscriptions can navigate across them from a single access point with onelogin. Also artifacts such as forms, dashboards, and so on, from across subscriptionscan be co-mingled within a cluster or within tabs on a card in navigation flows. Artifactsin the target subscription are accessible based on the user's role.

Watch this overview video to learn how to integrate EPM business process flows.

Overview Video

Watch this overview video to learn how to customize your EPM Cloud workflow.

Overview Video

6-1



Which EPM Cloud subscriptions can I connect?

The source subscription is the subscription from which you're creating the connection.The target subscription is the subscription to which you're connecting from the sourcesubscription.

You can connect these source subscriptions (these subscriptions can also be targetsubscriptions):

• Planning


• Tax Reporting

Source subscriptions can also connect to these target subscriptions (thesesubscriptions can't be source subscriptions):



• Narrative Reporting

• Strategic Workforce Planning

What are the ways I can connect to other EPM Cloud subscriptions?

• Toggle between the source subscription and the target subscription on the

Navigator menu. See Navigating Across EPM Cloud Subscriptions.

• Customize navigation flows in the source subscription to access clusters, cards,and artifacts in other target subscriptions from the Home page. See CustomizingNavigation Flows to Access Other EPM Cloud Subscriptions.

Considerations

• Only Service Administrators create cross-subscription connections.

Users click a navigation link to open the linked subscription. Access within thelinked subscription is determined by the predefined role and access permissions, ifany, assigned to the user.

• For cross-subscription navigation to be seamless, all subscription instances towhich cross-subscription navigation flows are setup must belong to the sameidentity domain.

Note:

If the target and source subscription instances are not on the sameidentity domain, then you'll not be able to establish a connection betweenthem.

• Service Administrators cannot configure cross-subscription connections usingcorporate SSO (identity provider) credentials.

Chapter 6About Connecting EPM Cloud Subscriptions

6-2

If your subscriptions are configured for SSO, ensure that identity domaincredentials are maintained for the Service Administrators who configure cross-subscription connections. See Enabling Sign In With Identity Domain Credentials.

• Migrating cross-subscription connections between test and productionenvironments can cause issues in certain use case scenarios. For moreinformation, see Considerations When Migrating Cross-Subscription Connections.

Considerations When Migrating Cross-SubscriptionConnections

Oracle recognizes that it's common practice for administrators to try out new features,such as connecting subscriptions, on test environments and then migrate to productionenvironments. However, in doing so, it could cause some issues after migration. We'lldescribe some use case scenarios that you need to be aware of.

In the following scenarios, assume you have subscriptions for Financial Consolidationand Close and Planning Modules.

Use Case Scenario 1: Test to Production

In this scenario, the administrator has defined a connection between the PlanningModules test instance and the Financial Consolidation and Close test instance. Theadministrator then uses this connection to build a navigation flow in the PlanningModules test environment that refers to a card in the Financial Consolidation andClose test environment. If the administrator chooses to export all artifacts in the testenvironment, the export will include connections and navigation flows, including theconnection to the Financial Consolidation and Close test instance.

When the administrator imports this snapshot into the Planning Modules productionenvironment, they will have an undesirable connection to the Financial Consolidationand Close test instance from the Planning Modules production environment.

When migrating connections from test environments to production environments, it'simportant to ensure that any connections that were defined in the test environment arechanged to point to the corresponding production instances.

Use Case Scenario 2: Production to Production or Test to Test

This scenario doesn't have any caveats.

Use Case Scenario 3: Production to Test

In this scenario, the administrator might be trying to replicate an issue on a testinstance. In this case it's important that the administrator remember to change anyconnections that point to a production instance to a test instance. Connections thatpoint to a production instance from a test environment could inadvertently tamper withproduction.

Creating, Editing, and Deleting Connections to Other EPMCloud Subscriptions

Before you can create connections to other EPM Cloud subscriptions, you mustensure you have access to the source and target subscriptions you're connecting. You

Chapter 6Considerations When Migrating Cross-Subscription Connections

6-3

must also have URLs for the other subscriptions you're connecting and login details foreach subscription such as user ID (Service Administrator) and password.

To create, edit, duplicate, and delete connections:

1. Login to the source subscription.

2. From the Home page, click Tools, and then click Connections.

3. Choose an action:

• To add a connection:

a. On the Manage Connections page, click Create.

b. Select the target subscription you want to add.

c. Enter the target subscription connection details:

– In URL, enter the URL of the target subscription instance; forexample, http(s)://your-target-host-url.com. This is the URLthat you normally use to sign in to the target subscription instance.

– In Connection Name enter name for this navigation link; for example,Consolidation Application.

– Enter an optional description for the link.

– Use Service Administrator and Password to specify the credentialsof a Service Administrator.

Note:

These credentials are used only to define and validate thenavigation link. When a user logs in, their own role andaccess will be applied to access the target subscription.

– The Domain field is automatically populated based on the URL youenter. If there is no domain in the URL, then the Domain field is leftblank.

d. Click Validate.

e. If the validation is successful, click Save and Close.

• To edit connections:

a. On the Manage Connections page, click the name of a connection.

b. Edit connection details.

c. Click Validate.

d. If the validation is successful, click Save and Close.

• To duplicate a connection:

a. On the Manage Connections page, in the Action column next to theconnection you want to duplicate, click .

b. Click Duplicate.

c. Enter a name for the duplicate connection, then click OK.

• To delete a connection:

Chapter 6Creating, Editing, and Deleting Connections to Other EPM Cloud Subscriptions

6-4

a. On the Manage Connections page, in the Action column next to theconnection you want to delete, click .

b. Click Delete.

When target subscriptions are connected to an EPM Cloud source subscription, they

are listed in the My Connections pane on the Navigator menu of the source

subscription. The My Connections pane on the Navigator menu is where youcan navigate across subscriptions. See Navigating Across EPM Cloud Subscriptions.

Common Connection Errors and ResolutionsKnown Errors and Resolutions

• The target connection does not belong to the same domain as the source. Ensurethat the target connection is in the same domain as the source.

• The product version of the target is different from that of the source. Beforecreating a connection, ensure that both the source and target product versions arethe same.

• The user name must have a Service Administrator role.

• The target connection must have an application. Create an application on thetarget and try again.

• The user name or password is invalid. Ensure the user is a Service Administrator.

– Ensure the user password used in the connection definition is not expired.

– Ensure the Domain field is not edited by the user. The domain is automaticallypopulated from the URL. If there is no domain in the URL, then the Domainfield is left blank.

• The URL provided is not for a service of type <selected provider type name>.

For example, the user has selected a provider type for Planning Modules, but hasprovided a service URL for Financial Consolidation and Close.

Unknown Errors and Resolutions

• The target you were trying to reach could not be found. Check the URL to ensurethat the path is correct.

– Ensure that the URL is valid.

– Ensure that the URL is not a Workspace URL (for example, http://<hostname>/workspace).

• Unable to establish a connection due to an unexpected error. For commonconnection errors and possible resolutions, see "Connecting Subscriptions in EPMCloud" in your Administering guide at Cloud Documentation.

– The target server is down.

– The target server is in maintenance mode.

– The target server is performing daily maintenance and will not be availableuntil the maintenance process is complete.

– The target server URL is not a trusted website and is denied access.

Chapter 6Common Connection Errors and Resolutions

6-5

https://docs.oracle.com/en/cloud/saas/index.html

Navigating Across EPM Cloud SubscriptionsOnce an administrator creates connections to other EPM Cloud subscriptions, the

connections are listed in the My Connections pane on the Navigator menu.

You can toggle between the subscriptions from this location. You must have access tothe other subscriptions in order to open them. Artifacts are accessible based on theuser's role.

To open another Oracle Enterprise Performance Management Cloud subscription:

1. From the Home page, click Navigator .

2. If subscriptions are connected and you have access to those subscriptions, you'llsee a list of connected subscriptions in the My Connections pane. Click asubscription to open it.

Note:

Click the icon to the right of the subscription name to open thesubscription in a new window.

Customizing Navigation Flows to Access Other EPM CloudSubscriptions

You can customize the application interface to access other EPM Cloud subscriptionsfrom the Home page of a source subscription. For example, you can add artifacts tothe Home page, such as forms or financial reports, from other EPM Cloudsubscriptions. You can group these artifacts (called cards) into clusters by customizingnavigation flows. Clusters and cards from target EPM Cloud subscriptions can bedirectly included in the navigation flows of source EPM Cloud subscriptions. You can

Chapter 6Navigating Across EPM Cloud Subscriptions

6-6

also use the Navigation Flow Designer to customize cards to have tabular pageswhere each tab is an artifact from a different subscription.

These two use cases describe in detail how to customize navigation flows to accessother EPM Cloud subscriptions:

• Grouping Cards from Other EPM Cloud Subscriptions into Clusters

• Configuring Cards with Tabs from Multiple EPM Cloud Subscriptions

To learn more about designing navigation flows, see "Designing Custom NavigationFlows" in your Administering guide.

Grouping Cards from Other EPM Cloud Subscriptions into ClustersYou can group cards from various EPM Cloud subscriptions into a cluster that isaccessible from the Home page of a source subscription. For example, you can createa cluster within Financial Consolidation and Close consisting of cards with pre-builtexternal reports from Narrative Reporting.

Cards from multiple subscriptions can also be included within the same cluster on asource environment. For example, a Tax Reporting user can launch a Journals iconfrom Financial Consolidation and Close without leaving Tax Reporting.

Chapter 6Customizing Navigation Flows to Access Other EPM Cloud Subscriptions

6-7

You create clusters and add cards to clusters by customizing navigation flows. Forgeneral information about navigation flows, see "Designing Custom Navigation Flows"in your Administering guide.

To create a cluster made up of cards from other EPM Cloud subscriptions:

1. Launch the Navigation Flow page and create a navigation flow or edit an existingnavigation flow:

Note:

To create a navigation flow, you must first select an existing navigationflow and make a copy of it. Then edit the duplicate navigation flow detailsand save them.

a. Click Tools, and then click Navigation Flows.

b. To create a navigation flow, select the navigation flow you want to duplicate,

then in the upper right-hand corner of the page, click , and then selectCreate Copy. Enter a name for the navigation flow, and then click OK.

Note:

New flows are marked Inactive until they are activated by theadministrator. To activate or deactivate a navigation flow, in theActive column, click Active or Inactive. Only one navigation flow ata time can be active.

c. To edit an existing navigation flow, click the name of the navigation flow youwant to edit.


6-8

Note:

Editing is only possible if the navigation flow is inactive. If thenavigation flow you want to edit is active, ensure you mark itInactive before editing.

2. Create a cluster or add an existing cluster:

a. If it isn't already open, from the Navigation Flow page, click the name of thenavigation flow in which you want to add a cluster.

b. To create a new cluster, click Add Cluster, enter or select the cluster details,and then choose an icon for the cluster.

c. If there is an existing cluster you want to add from another subscription, clickAdd Existing Card/Cluster, select the target subscription under MyConnections, and then choose the cluster you want to add to your navigationflow.

Note the following:

• Clusters can't be directly selected from Narrative Reporting andProfitability and Cost Management using the Add Existing Card/Clusteroption.

• Clusters that are added from another navigation flow or from anothersubscription will display the localized labels that were defined in thesource navigation flow. To update the cluster labels in your navigationflow, on the Home page, click Tools, and then click Artifact Labels. See"Specifying Artifact Labels" in your Administering guide.

3. Select the cards to include in the cluster:

a. From the Navigation Flow page, navigate to the card you want to add to thecluster. If the card is within another subscription, first select the subscriptionunder My Connections, and then navigate to the card in that subscription.

b. To the right of the card that you want to move, in the Order column, click .

c. Select the cluster, and then click OK.

The cards will appear in the listing as children of the cluster. Use the up and downarrows next to the cards to reorder the cards within the cluster, if needed.

4. Click Save and Close.

You must activate the navigation flow and reload it to view your design time changes.To reload a navigation flow, click the down arrow next to your user name. Then on theSetting and Actions menu, click Reload Navigation Flow.


6-9

If you can't see your referenced artifacts after activating and reloading the navigationflow, see Why Is My Referenced Card, Tab, or Cluster Not Visible?

Configuring Cards with Tabs from Multiple EPM Cloud SubscriptionsYou can also customize cards in navigation flows to have tabular pages where eachtab is an artifact from a different subscription. For example, an Planning Modules usercan click a Revenue icon which launches a card with horizontal tabs showing reportsfrom Narrative Reporting.

You create tabular cards by customizing navigation flows. For general informationabout navigation flows, see "Designing Custom Navigation Flows" in yourAdministering guide.

To configure a card made up of tabs and sub-tabs from other EPM Cloudsubscriptions:

1. Launch the Navigation Flow page and create a navigation flow or edit an existingnavigation flow:


6-10

Note:

To create a navigation flow, you must first select an existing navigationflow and make a copy of it. Then edit the duplicate navigation flow detailsand save them.

a. Click Tools, and then click Navigation Flows.

b. To create a navigation flow, select the navigation flow you want to duplicate,

then in the upper right-hand corner of the page, click , and then selectCreate Copy. Enter a name for the navigation flow, and then click OK.

Note:

New flows are marked Inactive until they are activated by theadministrator. To activate or deactivate a navigation flow, in theActive column, click Active or Inactive. Only one navigation flow ata time can be active.

c. To edit an existing navigation flow, click the name of the navigation flow youwant to edit.

2. Add a tabular card with artifacts from various target subscriptions:

a. If there is an existing card you want to add from another subscription, from theNavigation Flow page, click Add Existing Card/Cluster, select the targetsubscription under My Connections, and then choose the card you want toadd to your navigation flow.

Note the following:

• Cards can't be directly selected from Narrative Reporting and Profitabilityand Cost Management using the Add Existing Card/Cluster option.

• Cards that are added from another navigation flow or from anothersubscription will display the localized labels that were defined in thesource navigation flow. To update the card labels in your navigation flow,on the Home page, click Tools, and then click Artifact Labels. See"Specifying Artifact Labels" in your Administering guide.

b. To add a new tabular card to the navigation flow, from the Navigation Flowpage, click Add Card, and then select details for the card:

• Name—Enter a label for the card.

• Visible—Select whether the card is visible to users on the Home page.

• Cluster—If clusters exist, select a cluster for the card or select None.

• Icon—Select the icon that will be displayed for the card you're creating.Choose from the available icons provided in the icon library.

• Content—Select from the following options:

– Page Type—Select a multiple page (tabular) format.

– Orientation—Select Vertical or Horizontal.


6-11

3. Add tabs and sub tabs to the tabular card:

a. To add an existing tab, click Add Existing Tab.

b. To add a new tab, click Add New Tab, and then edit tab details.

c. Click Add New Sub Tab or Add Existing Sub Tab, and then edit sub tabdetails.

d. For Artifact, click to select an artifact in the Artifact Library; for example,if the artifact is a form, then select the specific form from the artifact listing.Available artifacts include forms, dashboards, and financial reports. To selectan artifact from another subscription, select the target subscription under MyConnections, and then choose the artifact you want to add to your tab.

e. Repeat adding tabs and sub tabs until the card is complete.


Note:

• For cards with multiple tabs or sub tabs, the last tab accessed by a userwill be retained the next time the user accesses the card in the samesession. If the user logs out and then logs back in, the default tab will bedisplayed.

• Tabs or sub tabs that are added from another navigation flow or fromanother subscription will display the localized labels that were defined inthe source navigation flow. To update the tab labels in your navigationflow, on the Home page, click Tools, and then click Artifact Labels. See"Specifying Artifact Labels" in your Administering guide.

You must reload the navigation flow to view your design time changes. To reload anavigation flow, click the down arrow next to your user name. Then on the Setting andActions menu, click Reload Navigation Flow.


6-12

If you can't see your referenced artifacts after reloading the navigation flow, see WhyIs My Referenced Card, Tab, or Cluster Not Visible?


6-13

7Designing Custom Navigation Flows

Customize the application interface using navigation flows. Navigation flows enabledesigners to control how roles or groups interact with the application.

Related Topics

• Understanding Navigation Flows

• Viewing and Working with Navigation Flows

Understanding Navigation FlowsNavigation flows give application designers control over how various roles, or groups,interact with the application. The Navigation Flow Designer enables you to customizethe application interface. For example, you can change the names of the cards andclusters that display on the Home page and the order in which they are displayed. Youcan hide cards, create new cards, and group cards into clusters. You can alsocustomize the vertical and horizontal tabs that display on a card.

Watch these videos to better understand navigation flows.

• Overview Video

• Tutorial Video

Watch this overview video to learn how to customize your EPM Cloud workflow.

Overview Video

Related Topics:

• What Can Be Customized in the Application Interface?

• Navigation Flow Customization Categories

• Navigation Flow Permissions

• Predefined Navigation Flows

• Viewing and Working with Navigation Flows

What Can Be Customized in the Application Interface?• Labels for cards or tabs

• Icons that are used for cards or tabs

• Hide and unhide cards and tabs

• Display order of cards and tabs

7-1




• Add new cards

• Add existing cards

• Add new horizontal or vertical tabs

• Remove navigation flows, cards, and tabs

• Group cards into clusters

• Add existing clusters

See Viewing and Working with Navigation Flows.

Navigation Flow Customization CategoriesNavigation flows are categorized as follows for customization:

1. Global—Navigation flows are seen by all users

2. Role—Navigation flows are seen only by users in a specific role; for example,Planner or Interactive User

3. Group—Navigation flows are seen only by users belonging to a specific group

Navigation flows can be defined at any of these levels. In cases where navigationflows exist at multiple levels, updates are applied in the order of highest (global) tolowest (groups).

For example, if you create a navigation flow that displays an icon on the Home pagenamed "My Tasks", and then another administrator duplicates the navigation flow,makes the following changes to the card, and then associates the navigation flow witha group:

• At the global level, they rename "My Tasks" to "Company Tasks"

• At the group level, for a group named Sales, they rename "My Tasks" to "SalesTasks"

Users who belong to the group called Sales will see the label "Sales Tasks" in thenavigation flow instead of "My Tasks," and all other users will see the label "CompanyTasks".

Navigation Flow PermissionsThe application offers three levels of permissions for navigation flows:

• Role-based—Permissions are granted to users or groups assigned to a specificrole; for example, a Planner will see different cards displayed on the Home pagethan an Administrator

• Artifact-based—Permissions are granted to users or groups who can see certainartifacts; for example, a Planner will see only the forms to which they have beenassigned permission

• Global—Permissions are granted to all users

Predefined Navigation FlowsThe application comes with one predefined navigation flow, called Default. The Defaultnavigation flow is read only; therefore, you can't make any modifications to it.

Chapter 7Understanding Navigation Flows

7-2

These are the operations you can and cannot perform on the Default navigation flow:

• Name—You can't modify the name.

• Delete—You can't delete the navigation flow.

• Edit—You can view the navigation flow details, but you can't change anything.

• Activate or Deactivate—You can activate or deactivate the navigation flow.

• Duplicate—You can make a copy of the navigation flow.

Viewing and Working with Navigation FlowsAdministrators can view a list of navigation flows, including the predefined navigationflow, within the Navigation Flow page.

The Navigation Flow page lists each navigation flow by name, indicates the role or thegroup that has access to the navigation flow (if assigned), and provides a descriptionof the navigation flow (if provided). The listing also indicates whether the navigationflow is active or not.

Caution:

There are naming restrictions for navigation flows, cards, clusters, tabs, andinfolets in navigation flows. You cannot use these special characters:

• ampersand ( & )

• less than sign ( < )

• greater than sign ( > )

• quotation mark ( " )

• backslash ( \ )

• plus sign ( + )

To view the navigation flow:

1. Click Tools, and then click Navigation Flows.

2. To work with a navigation flow, perform an action:

• To create and duplicate navigation flows, see Creating and DuplicatingNavigation Flows.

• To edit a navigation flow, see Editing a Navigation Flow.

• To activate or deactivate a navigation flow, see Activating and DeactivatingNavigation Flows.

• To rename cards and tabs, see Customizing Labels for Cards, Tabs, andClusters.

• To customize the graphics used for cards and tabs, see Customizing Icons forCards and Vertical Tabs.

• To hide and unhide cards and tabs, see Hiding and Unhiding Cards and Tabs.

Chapter 7Viewing and Working with Navigation Flows

7-3

• To change the display order of cards on the Home page, see Changing theDisplay Order of Cards on the Home Page.

• To add cards, see Adding Cards.

• To add tabs, see Adding Tabs to a Tabular Page.

• To remove navigation flows, cards, and tabs, see Removing Navigation Flows,Cards, and Tabs.

• To group cards into clusters, see Grouping Cards into Clusters.

• To see why remote artifacts might not be visible, see Why Is My ReferencedCard, Tab, or Cluster Not Visible?.

Creating and Duplicating Navigation FlowsTo create a navigation flow, you must first select an existing navigation flow and makea copy of it. Then edit the duplicate navigation flow details and save them.

To create and duplicate a navigation flow:

1. Open the Navigation Flow page. See Viewing and Working with NavigationFlows.

2. Select the navigation flow you want to copy, then in the upper right-hand corner of

the page, click , and then select Create Copy.

3. Enter a name for the navigation flow, and then click OK.

Note:

Ensure that you adhere to the navigation flow naming restrictionsoutlined in Viewing and Working with Navigation Flows.

4. Edit details for the navigation flow. See Editing a Navigation Flow.

Note:

New flows are marked Inactive until they are activated by theadministrator. To activate a navigation flow, see Activating andDeactivating Navigation Flows.

To reload a navigation flow to view design time changes, see Reloading a NavigationFlow.

Editing a Navigation FlowTo edit a navigation flow:


2. Click the name of the navigation flow you want to edit.


7-4

Note:

The predefined navigation flow isn't editable. However, you can create acopy of a predefined navigation flow and edit the copy. See PredefinedNavigation Flows.

3. Edit details of the navigation flow:

• Name—The name is editable if the navigation flow isn't a predefinednavigation flow.

Note:

Ensure that you adhere to the navigation flow naming restrictionsoutlined in Viewing and Working with Navigation Flows.

• Assign To—Click to assign the navigation flow to a group of users or to arole.

• Visible—Indicates whether a card in the navigation flow is visible on the Homepage to the users in the group.

• Order—The cards within the navigation flow are listed in the order in whichthey are displayed on the Home page, if visible. Selecting an up or down arrowoption repositions the cards in the listing and changes the display order of thecards on the Home page. Selecting the right arrow moves a card into a cluster.

• Remove—Removes a card or cluster from the navigation flow.

• Add Card—Adds a new card to the navigation flow. See Adding Cards.

• Add Cluster—Adds a new cluster to the navigation flow. See Grouping Cardsinto Clusters.

• Add Existing Card/Cluster—Adds an existing card or cluster to thenavigation flow.


Activating and Deactivating Navigation FlowsYou can create multiple navigation flows for each category (global, role, or group), butonly one navigation flow can be active in each category. Whenever you make anavigation flow active, the other navigation flows in the same category will becomeinactive.

Note:

The application requires one active global navigation flow. To make adifferent global navigation flow active, select another global navigation flowand activate it.


7-5

For information about categories, see Navigation Flow Customization Categories.

These are the operations users can and cannot perform on an active navigation flow:

• Name—Users can't modify the name.

• Delete—Users can't delete the navigation flow.

• Edit:

– Users can view the navigation flow definition, but they can't change anything.

– If the application is in administration mode, then users can save anymodifications.

• Activate or Deactivate—Users can activate or deactivate a navigation flow.

• Duplicate—Users can make a copy of a navigation flow.

To activate or deactivate a navigation flow:


2. In the Active column, click Active or Inactive. An active flow will be markedinactive. Conversely, an inactive flow will be marked active.

Customizing Labels for Cards, Tabs, and ClustersYou can customize the labels for cards (the icons that display on the Home page),tabs, and clusters. Labels are limited to 25 characters or less. For vertical tabs, thereis no character limitation since the label for vertical tabs displays as hover text.

To customize labels for cards, tabs, and clusters:

1. Open the Navigation Flow page and click the name of the navigation flow youwant to edit. See Viewing and Working with Navigation Flows.

2. If customizing the label for a card or cluster:

a. Click the name of the card or cluster you want to edit.

b. Enter a new name and save it.

Note:

• You can edit the label here. However, if the label is defined inthe Artifact Labels page on the Tools cluster, that definition willtake precedence and will display during runtime. To change alabel permanently, redefine it in the Artifact Labels page. See"Specifying Artifact Labels" in your Administering guide.

• Ensure that you adhere to the naming restrictions outlined in Viewing and Working with Navigation Flows.

3. If customizing the label for a tab:

a. Click the name of the card you want to edit.

b. In the tab listing on the Manage Tab page, click the name of the tab you wantto edit.


7-6

c. Enter a new name for the tab and save it.


Customizing Icons for Cards and Vertical TabsYou can change the icons used for cards and vertical tabs. You must pick from theavailable icons provided in the icon library.

To customize the icons for cards and vertical tabs:


2. If customizing the icon for a card:


b. Click the icon for the card, select a new icon from the library, and then save it.

3. If customizing the icon for a tab:

a. Click the name of the icon you want to edit.


c. Click the icon for the tab, select a new icon from the library, and then save it.


Hiding and Unhiding Cards and TabsYou can't hide the following navigation elements:

• The Application cluster and the Settings icon in the Application cluster.

• The Tools cluster and these icons in the Tools cluster:

– Access Control

– Navigation Flows

– Daily Maintenance

– Migration

To hide and unhide cards and tabs:

1. Click the Navigation Flow icon and click the name of the navigation flow you wantto edit. See Viewing and Working with Navigation Flows.

2. If hiding or unhiding a card:


b. Set Visible to Yes or No.

3. If hiding or unhiding a tab:




7-7

c. Set Visible to Yes or No.


Changing the Display Order of Cards on the Home PageYou can change the display order of cards in the Navigation Flow Designer. Cardsdisplay on the Home page in the order they appear within the listing

To change the display order of the cards on the Home page:


2. In the listing, use the up and down arrows in the Order column to move cards upor down in the navigation flow order.


Adding CardsThe icons you see on the application Home page are called cards. Cards are specificto each functional area of the application. Each card navigates users to thecorresponding area, where other information is displayed as one or more tabbedpages. You can create single page or multiple page (tabular) cards.

You can also group cards into clusters. See Grouping Cards into Clusters.

To add cards to a navigation flow:


2. To add an existing card to the navigation flow, click , click Add Existing Card/Cluster, and then select a card. If there is an existing card you want to add from

another subscription, click , click Add Existing Card/Cluster, select the targetsubscription under My Connections, and then choose the card you want to add toyour navigation flow.

Note the following:

• Cards can't be directly selected from Narrative Reporting and Profitability andCost Management using the Add Existing Card/Cluster option.

• Cards that are added from another navigation flow or from anothersubscription will display the localized labels that were defined in the sourcenavigation flow. To update the card labels in your navigation flow, on theHome page, click Tools, and then click Artifact Labels. See "SpecifyingArtifact Labels" in your Administering guide.

3. To add a new card to the navigation flow, click , click Add Card, and thenselect details for the new card:

• Name—Enter a label for the card.


7-8

Note:

Ensure that you adhere to the naming restrictions outlined in Viewingand Working with Navigation Flows.

• Visible—Select whether the card is visible to users on the Home page.

• Cluster—If clusters exist, select a cluster for the card or select None.

• Icon—Select the graphic that will be displayed for the card you're creating.Choose from the available graphics provided in the graphics library.

• Content—Select from the following options:

– Page Type—Select a single page or a multiple page (tabular) format.

– Artifact—Click to select an artifact in the Artifact Library; forexample, if the artifact is a form, then select the specific form from theartifact listing. Available artifacts include simple forms, dashboards, andfinancial reports. To select an artifact from another subscription, select thetarget subscription under My Connections, and then choose the artifactyou want to add.

Note:

Composite forms are not supported in navigation flows. Oraclerecommends that you create a dashboard instead.

– Orientation—For a card with a tabular page format, select Vertical orHorizontal.

• For a page with a tabular format, add new or existing tabs and sub tabs. See Adding Tabs to a Tabular Page.



Adding Tabs to a Tabular PageTabs can be horizontal or vertical. For example, the Valid Intersections card (underthe Application cluster) is a tabular page with two horizontal tabs at the top of thepage: Setup and Reports.

You can also create tabular pages with vertical tabs. Vertical tabs display a graphicand text appears when the cursor is hovered over the tab. Horizontal tabs display textlabels only.

To add tabs to a tabular page:


2. Add a new card by clicking Add Card or edit an existing card by clicking the nameof the card you want to edit.


7-9

3. On the Manage Card page, for Page Type, select Tabular Page.

A tab listing displays at the bottom of the Manage Card page.

4. To edit an existing tab, click a tab name from the tab listing, and edit tab details.

5. To add a new or existing tab:

a. To add an existing tab, click Add Existing Tab.

b. To add a new tab, click Add New Tab, and then edit tab details.

c. For Artifact, click to select an artifact in the Artifact Library; for example,if the artifact is a form, then select the specific form from the artifact listing.Available artifacts include simple forms, dashboards, and financial reports. Toselect an artifact from another subscription, select the target subscriptionunder My Connections, and then choose the artifact you want to add.

6. To add new or existing sub tabs to a tab:

a. Click the name of a tab in the in the tab listing.

b. For Page Type, select Tabular Page.

c. Click Add New Sub Tab or Add Existing Sub Tab, and then edit sub tabdetails.

d. For Artifact, click to select an artifact in the Artifact Library; for example,if the artifact is a form, then select the specific form from the artifact listing.Available artifacts include simple forms, dashboards, and financial reports. Toselect an artifact from another subscription, select the target subscriptionunder My Connections, and then choose the artifact you want to add.



Note:

• For cards with multiple tabs or sub tabs, the last tab accessed by a userwill be retained the next time the user accesses the card in the samesession. If the user logs out and then logs back in, the default tab will bedisplayed.

• Tabs or sub tabs that are added from another navigation flow or fromanother subscription will display the localized labels that were defined inthe source navigation flow. To update the tab labels in your navigationflow, on the Home page, click Tools, and then click Artifact Labels. See"Specifying Artifact Labels" in your Administering guide.

Removing Navigation Flows, Cards, and TabsYou can't remove the following navigation elements:

• The Application cluster and the Settings icon in the Application cluster.

• The Tools cluster and these icons in the Tools cluster:


7-10

– Access Control

– Navigation Flows

– Daily Maintenance

– Migration

To remove navigation flows, cards, and tabs:


2. If removing a navigation flow:

a. Select the navigation flow you want to remove.

b. In the upper right-hand corner of the page, click , and then select Delete.

Note:

You can't delete the predefined navigation flow, called Default.

3. If removing a card:

a. Click the name of the navigation flow you want to edit.

b. In the Remove column for the card you want to remove, click .

4. If removing a tab:

a. Click the name of the navigation flow you want to edit.

b. Click the name of the card you want to edit.

c. In the tab listing at the bottom of the Manage Tab page, in the Remove

column for the tab you want to remove, click .


Grouping Cards into ClustersA cluster is a grouping of cards. You must first create a cluster and then you canassign cards to it. You can also add existing clusters to navigation flows.

To group cards into clusters:

1. Create a new cluster or add an existing cluster:

a. Open the Navigation Flow page and click the name of the navigation flow inwhich you want to add a cluster. See Viewing and Working with NavigationFlows.

b. To create a new cluster, click , click Add Cluster, enter or select thecluster details, and then choose a graphic for the cluster.


7-11

Note:

Ensure that you adhere to the naming restrictions outlined in Viewingand Working with Navigation Flows.

c. To add an existing cluster, click , click Add Existing Card/Cluster. If there

is an existing cluster you want to add from another subscription, click , clickAdd Existing Card/Cluster, select the target subscription under MyConnections, and then choose the cluster you want to add to your navigationflow.

Note:

• Clusters can't be directly selected from Narrative Reporting andProfitability and Cost Management using the Add ExistingCard/Cluster option.

• Clusters that are added from another navigation flow or fromanother subscription will display the localized labels that weredefined in the source navigation flow. To update the clusterlabels in your navigation flow, on the Home page, click Tools,and then click Artifact Labels. See "Specifying Artifact Labels"in your Administering guide.

d. Click Save and Close.

The newly added cluster displays in the listing.

2. Select the cards to include in the cluster:

a. To the right of each card that you want to move, in the Order column, click .

b. Select the cluster, and then click OK.

The cards will appear in the listing as children of the cluster. Use the up and downarrows next to the cards to reorder the cards within the cluster, if needed.


Reloading a Navigation FlowTo display design changes while you're working with a navigation flow, you can reloadthe navigation flow.


7-12

To reload a navigation flow after making design changes:

1. From the Home page, click the down arrow next to the user name (upper rightcorner of the screen).

2. On the Settings and Actions menu, click Reload Navigation Flow.

Switching Navigation Flows at RuntimeIf you belong to multiple groups or if a navigation flow is assigned to a role, you mighthave access to more than one navigation flow.

To switch navigation flows at runtime:

1. From the Home page, click Navigator .

2. On the Navigator menu, click the down arrow next to the title of the navigationflow.

3. Select the navigation flow that you want to view.


7-13

Why Is My Referenced Card, Tab, or Cluster Not Visible?When customizing navigation flows to connect EPM Cloud subscriptions, at times theconnected artifacts may not be visible. Here are some common reasons why:

• The target subscription is down; for example, to perform routine dailymaintenance.

• The password provided in the connection definition is expired.

• The user name provided in the connection no longer has an administrator role.

• The product version of one of the subscriptions has changed; for example,17.09.xxx and 17.10.xxx don't communicate because both subscriptions must bethe same version.

Note the following:

– This version restriction only applies to the first four digits of the versionnumber.

– This version restriction impacts customers who have multiple EPM Cloudsubscriptions and who might have stopped taking monthly updates for a givensubscription.

• The password was not setup again after performing a Migration. Since passwordsare not migrated, you must ensure the password is setup again after the Migrationbackup is restored.

• The referenced navigation flow was deleted on the target subscription, or:

– The referenced navigation flow artifact (card, tab, or cluster) was deleted.

– The referenced artifact from the target flow was deleted or renamed.

– The currently logged in user's access to the given artifact was revoked.


7-14

8Designing Infolets

Related Topics

• About Infolets

• Anatomy of an Infolet

• Determining Infolet Content

• Using the Infolets Designer

• Creating Infolets

• Working with Infolets

• Customizing the Application Interface to Access Infolets

About InfoletsInfolets enable users to view and interact with high-level, essential informationgenerated from different sources so that they can quickly assess where to direct theirattention. Administrators create, redesign, delete, and assign permissions to infolets.

Watch this overview video to learn how to design infolets.

Overview Video

What is an Infolet?

An infolet is a self-contained, interactive box-shaped container used to displayinformation using text and charts. Infolets are interactive and use progressivedisclosure to display high-level, aggregated, essential information for quickconsumption at a glance, and then can be acted upon as needed. Infolets can beflipped and resized to display up to three charts or sets of values.

8-1


For more information about infolets, see Anatomy of an Infolet.

How Can I Use Infolets?

Use infolets to:

• Promote essential, easily consumable information

• Provide answers to your most critical questions:

– What is new or what has changed?

– What is the most important information that supports my work?

• Group key information by user role in a way that helps users quickly assess andprioritize their work

• Progressively display essential details and actions

Display these additional details in the various infolet views accessed by flipping orexpanding an infolet. However, a single infolet view is acceptable.

• Provide a visually rich means of displaying essential or summary information

Do not use infolets to feature highly complex information, such as reporting functions,or to present detailed visuals.

See Determining Infolet Content.

What is an Infolet Page?

An infolets page is a page that contains one or more infolets. It houses a container thatmanages the space occupied by the infolets and rearranges them depending on thesize of the browser and the size of the infolets. Each infolet you create belongs to aninfolet page. The Infolets card on the Home page provides a list of infolet pages.

Chapter 8About Infolets

8-2

Note:

Not all features pictured in the preceding image are supported in this update.Oracle plans to support these features in a later update.

See Working with Infolets.

Anatomy of an InfoletInfolet Views

An infolet supports up to three views:

1. Front view (required)

2. Back view (optional)

3. Expanded view (optional)

Chapter 8Anatomy of an Infolet

8-3

The front view is required, and:

• Provides a quick look or glimpse at high-level information that has a direct effecton your work; for example, the front view can display status, counts, totals, or themost recent updates

• Promotes a glancing action that helps you identify important information that youmay want to explore a bit more

• Uses all infolet sizes except 3x2 (see information about infolet sizes below)

• Returns the expanded view to its original size in the front view or back view

• Includes an Actions menu icon available only on hover and either a (optional) flipto back icon or an expand icon in the lower-right corner

Note:

If only one view is presented, it must be a front view.

The back view is optional, and:

• Presents analytical information (for example, a graph)

• Promotes a scanning action that helps you explore or become more familiar withthe information represented on the front view

• Is sized the same as the front view

• Includes an Actions menu icon available only on hover, a flip to front icon in thelower-left corner, and an (optional) expand icon in the lower-right corner

The expanded view is optional, and:

• Presents even more detailed information about the single data point orinterdependent data set presented in the front and back views; for example, the


8-4

expanded view can display more details about an object or a list of recent itemsthan what's displayed on either the front or back view

• Provides enough information to help you decide if you're ready to take action andmove to a focused context on a work area page

• Transitions smoothly from other views. You see a smooth, seamless expansion,as one infolet pushes others into new positions.

• Must be sized bigger than the front or back views

• Includes an Actions menu icon available only on hover, and a collapse icon in thelower-right corner

Infolet views honor the access permissions assigned to the underlying forms anddimensions. Therefore, the same infolet may display varying views from user to user ifthey have different access permissions.

Infolet Sizes

Infolets can be sized as follows:

Note:

1x1 refers to a box that spans one column and row width (170 pixels).

• 1x1

• 2x1

• 3x1

• 2x2

• 3x2 (expanded view only)

The size of the front and the back views are always the same. Changing the size ofthe front view will automatically reset the size of the back view. Because the size of theexpanded view must always be greater than the size of the front/back views, if the sizeof the front/back view of an infolet is enlarged, the expanded view automatically resetsto a larger size than the front/back view.

Note:

Front and back views cannot use the 3x2 size. This size is applicable for theexpanded view only.

The size, title, and subtitle of a view is set by the designer in the properties panel. See Using the Infolets Designer.

Navigating Between Infolet Views

An infolet can be created with one of the following view combinations:

1. Front view only

2. Front and back views


8-5

3. Front and expanded views

4. Front, back, and expanded views

Switching from one view to another is controlled by clicking a flip icon, an expand icon,or a collapse icon available in the bottom-right or bottom-left corner of the infolet.Hovering your cursor over the bottom corners reveals a flip, expand, or collapse icon.

Determining Infolet ContentConsider the following general tips when determining infolet content:

• Look to existing dashboards and work area pages.

Dashboards and work area pages are excellent starting points because theydisplay collections of information summaries.

• Apply the 10/90/90 principle.

Seek out the most essential, easily consumable information that addressesfrequently asked questions garnered from the top 10 percent of use cases. Theseuse cases can come from across your enterprise—from business intelligence,social, transactional, external, and so on.

Then focus this information to reveal what 90 percent of your users would benefitfrom viewing 90 percent of the time. You can apply this 10/90/90 percent principleto existing dashboard content, to existing work area page content, or generally, topercolate eligible information for an infolet.

• Restate your top use cases in the form of frequently asked business questions.

Present the corresponding infolet content in such a way as to answer thesebusiness questions; for example, how many orders are in jeopardy, listed bystatus?

• Look for one point or a tightly related, interdependent set of points, instead ofmultiple points of information.

The process of determining content for an infolet is similar to the process that isused to yield dashboard content—but to a deeper level of analysis. Look forinformation within a data point or data set that is suitable to be displayed in nomore than three views of information hierarchy and that answers a criticalbusiness question.

• Start with the single most important point.

An infolet displays aggregated information about a single data aspect or point ofinformation in relation to an event that the user needs to know about or a task thatthe user needs to address.

If a dashboard contains multiple aspects about one or more objects (for example,numeric totals and currency totals), start with the single most important point andadd that as a simple overview (for example, as a total using a stylized numericvalue) to the front view of an infolet. Then determine the content for the back view,if needed. Finally, determine the content for the expanded view, if needed.

An infolet should have no more than three views. If there is only a single data pointor only one tightly related, interdependent data set to display on an infolet, useonly the front view.

Chapter 8Determining Infolet Content

8-6

Related Links

Designing Forms for Infolets

Designing Charts for Infolets

Designing Forms for InfoletsUse only simple forms with small data sets in infolets. Permissions that are set forforms are honored in infolets.

You can create forms that are specifically used in infolets:

• Forms used in infolets should have fewer cells than a traditional data entry form;for example, forms used in infolets should only have up to 12 cells.

• Forms used in infolets should have no more than 12 rows and columns. If a formhas more than 12 rows and columns, the infolet will only display the first 12 rowsand columns.

• Infolets currently don't support Page dimensions or POVs, therefore forms used ininfolets should not contain Page dimensions.

• If a form that is used in infolets contains a grid with members that expand, theinfolet will display all the members in the form, including the expanded members.

Designing Charts for InfoletsUse the title and subtitle in charts to show static context.

There are six types of charts that you can use in infolets:

• Bar—Displays a graphical summary of multiple data values for comparisonpurposes. Bar charts can be plotted vertically or horizontally. Up to eight bars arerecommended for bar chart infolets.

• Column—Displays stacked bars that represent different data sets on top of eachother. The height of the resulting bar shows the combined result of the data sets.

• Doughnut—A circular graph which is divided into segments to compare data setsto one another. The blank center displays the sum of all data sets. Up to sixsegment values are recommended for doughnut chart infolets.

• Line—Use to visualize a trend in data over intervals of time.

• Pie—A circular graph which is divided into slices to compare data sets to oneanother. Up to six slices are recommended for pie chart infolets.

• Tile—Lets you select specific values from a data set to display. No more thanthree values are recommended for tile chart infolets.

Note:

Tile charts can only use the 1x1 size. You cannot resize an infolet usingthe tile chart until the chart type is changed. If you drag and drop a tilechart to an infolet that is greater than 1x1, you will be prompted tochange either the size of the infolet or the chart type.

Chapter 8Determining Infolet Content

8-7

Using the Infolets DesignerAdministrators use the Infolets Designer to create infolets and infolet pages. TheInfolets Designer enables easy toggling between runtime and designer views. Toaccess the Infolets Designer, launch the Infolets icon on the Home page and clickCreate, or click the Actions icon next to an infolets page in the listing, and then clickEdit. Clicking the infolet name in the listing, launches the runtime version of the infolet

page. You can toggle from runtime view to designer view by clicking .

Infolets Designer

Infolets Toolbar

On the upper right is the Infolets Toolbar.

—Adds a new infolet to the Infolets Designer

—Hides and unhides the Properties panel

—Click to perform these actions:

• Reset—Resets the Infolets Designer to a previously saved state

• Refresh—Refreshes the data from Essbase and updates the infolet definition fromthe database

• Runtime—Hides all Infolets Designer elements and displays the infolet as it wouldappear to users during runtime

Chapter 8Using the Infolets Designer

8-8

—From runtime mode, displays the Infolets Designer

Infolets Designer Palette

On the left is the Designer Palette. The Designer Palette has two tabs: Forms andChart Types. Highlight objects in the Designer Palette and then drag and drop themonto the drop zone.

Designer Palette objects:

• Forms—Select simple forms to include in the infolet by scrolling through the formsor by searching for them by name. For details about forms, see Designing Formsfor Infolets.

Note:

The access permissions set for forms are honored in infolets.

• Chart Types—Select the chart types to include in the infolet. Infolets displaysample data in the charts until you associate the chart with a form as its datasource. When you link a chart to a form, users can see the impact of changing

Chapter 8Using the Infolets Designer

8-9

data in the form on the associated charts. To associate a chart with a form,highlight a chart and drag and drop it onto the drop zone, in the Properties panel,click Sample, and then click Forms to select the data source. For details aboutcharts, see Designing Charts for Infolets.

Infolet Menu

The infolet menu contains the infolet delete and clear actions. To view the infoletmenu, hover over the upper right corner of the infolet, and then click the down arrow todisplay the menu options:

• Delete—Removes the infolet from the page

• Clear—Clears infolet details

Properties Panel

The properties panel on the right side of the Infolets Designer enables you view andwork with these infolet properties:

Note:

The header you specify is the same for all views of an infolet, but you canspecify a different subtitle for each view; for example, the front, back, andexpanded views of an infolet can each have different subtitles, but they musthave the same header.

• Header

• Subtitle

• Size—Displays the infolet in the selected size

• Chart Type—Displays the infolet data as the selected chart type

• Data—Displays the associated data source (Sample or Form)

• Form—Displays the selected infolet form

Actions such as delete and clear are on the infolet menu.

By default, the front view of an infolet is displayed in the properties panel. You can seethe other views by selecting them from the drop-down. If you flip or expand an infoletto view the back or expanded views, the properties for those views display in theproperties panel. In addition, the properties for the corresponding chart type are alsodisplayed in the properties panel.

Creating InfoletsTo create infolets:

1. From the Home page, click Infolets, and then click Create.

2. Click Infolets Page Name, and enter a title for the new infolets page you arecreating.

Chapter 8Creating Infolets

8-10

3. From the designer palette on the left, choose either the Forms tab or the ChartsType tab, highlight an object, and then drag and drop it onto the infolets dropzone.

4. Customize the infolet using selections made in the properties panel, and then clickSave.

You can easily duplicate and modify an infolet using the Copy As action on the Infoletlist page. From the list page, click the Actions icon next to the infolet you want to copy,and then click Copy As.

Working with InfoletsOnce you've created an infolets page, it is displayed in the infolets listing on theInfolets card.

The listing page for infolets supports folders. Folders enable you to assign permissionsto all infolets within a folder rather than assigning permissions to each individualinfolet. The infolets listing page uses the same folder hierarchy as dashboards anddata entry forms and all artifacts and folders reside under a root folder called Library.

To view and work with infolets:

1. From the Home page, click Infolets.

2. To work with infolets, perform an action:

• On the listing page for infolets, you can toggle between viewing infolets by a

flat view or a tree view:

Then you can search for infolets using Search . The flat view displaysonly the artifacts that meet the search criteria, not the folders that containthem. The tree (or hierarchical) view displays artifacts in the context of thefolders that contain them.

To search on another keyword, clear the search criteria by clicking X in theSearch box.

• To refresh the infolets listing, click Refresh.

• To create infolets, click Create. See Creating Infolets.

• To perform the following actions on infolet pages, click the Actions icon nextto the infolet page, and then select:

– Create Folder—Creates a folder in the listing

– Edit—Opens the infolet page in the Infolets Designer

– Rename—Renames the infolet page

– Copy As—Duplicates an infolet page

– Delete—Deletes the infolet page from the listing

– Move To—Moves an infolet page to another folder

– Default or Unmark—Default marks an infolet page as default and makesit accessible directly from the Home page by clicking the second infolet dotthat is displayed beneath the global header on the Home page. Unmarkremoves the default designation from the infolet page.

Chapter 8Working with Infolets

8-11

Note:

You can mark either an infolet page or a dashboard as default. Ifa dashboard is marked as default first and then you mark aninfolet page as default, the default dashboard will be overwritten.Conversely, if an infolet is marked default first, then anydashboard marked default later will overwrite the default infolet.

– Assign Permission—Enables you to assign Read, Write, and Noneaccess permissions to infolet pages and folders for individual users orgroups

Customizing the Application Interface to Access InfoletsYou can customize the application interface to add links to infolet pages from theHome page using the Navigation Flow Designer. When you customize your applicationinterface to access infolet pages, dots will appear on the Home page beneath theglobal header. Each dot that appears on the Home page represents an infolet pageand hovering over each dot displays the name of the infolet page. Clicking an infoletdot launches the infolet page associated with that dot. You can define up to seveninfolet dots on the Home page. If you've created connections to other EPM Cloudsubscriptions, you can also add links to infolet pages in other EPM Cloudsubscriptions.

Users will only see dots displayed on the Home page for infolet pages to which theyhave access. The types of infolet dots displayed are as follows:

• Home dot—This dot always appears first and it links to the Home page. There canonly be one home dot. If you are not viewing the Home page, clicking the homedot will bring you back to the Home page.

• User dot—Links to an infolet page marked by an end user as the default infoletpage. There can only be one user dot and it always appears after the Home dot onthe user's Home page. User dots cannot be added using the Navigation FlowDesigner. For more information about marking an infolet as the default, see Working with Infolets.

• Customizable dot—Links to infolet pages created by administrators. Customizabledots can be integrated into navigation flows and their visibility and the order inwhich they appear is determined by the navigation flow designer. There can be upto seven customizable dots and they always appear after the home and user dots.

To add infolet dots to your application interface using the Navigation Flow Designer:

1. From the Home page, click Tools, and then click Navigation Flows.

2. Select an inactive navigation flow in the listing, and then click the Infolets tab onthe Navigation Flow Designer.

Chapter 8Customizing the Application Interface to Access Infolets

8-12

3. Click .

4. In Manage Infolet, name the infolet dot, set visibility, and then click to selectan infolet in the Artifact Library.

Note:

You can select an infolet from another EPM Cloud subscription if you'vecreated connections to other subscriptions. First select the subscriptionunder My Connections, and then navigate to the infolet in thatsubscription.


Note:

Infolets can also be associated with a tab or a card in a navigation flow.While adding or updating a tab or a card, select an infolet in the ArtifactLibrary.

To view design time changes to the navigation flow, activate the navigation flow, andthen from the Home page, click the down arrow next to the user name (upper rightcorner of the screen) and click Reload Navigation Flow.

To learn more about designing navigation flows, see "Designing Custom NavigationFlows" in your Administering guide.

To learn more about connecting EPM Cloud subscriptions, see "ConnectingSubscriptions in EPM Cloud" in your Administering guide.

Chapter 8Customizing the Application Interface to Access Infolets

8-13

9Designing Financial Dashboards

Related Topics

• Designing Dashboards

• About Your Dashboard's Layout

• About the Gauge Chart Type

• About the Tile Chart Type

• Customizing Dashboard Colors

• Setting Line Width in Line and Combination Charts

• About Global and Local POVs

• Dashboard POVs and Valid Intersections

Designing DashboardsFinancial dashboards typically provide an overview by showing summary data. Theversatility of dashboards enables you to chart, evaluate, highlight, comment on, andeven change key business data. For example, you can change a driver such asVolume in a form that is in a dashboard and immediately see its impact in other formsand charts:

You can create a dashboard by selecting existing data forms and external artifactssuch as comments or an external URL. You can specify a chart type to display thedata, for example, a Pie chart, bar chart, or other chart type.

Note:

For details on Task Manager and Supplemental Data Manager Overview andCompliance dashboards, see "Monitoring Dashboards" in Working withFinancial Consolidation and Close.

To create a Financial dashboard:

1. On the Home page, from Dashboards, click Financial.

2. Click Create.

3. Enter a dashboard name.

• To change the default dashboard name, click its name, and enter a new namein the input box.

• To give the dashboard a title with custom formatting, click Settings, clear Usename as title, and then enter the title and set formatting the dialog box.

9-1

• When a new dashboard is created, the borders are hidden by default. To showborders, in Settings, change the Borders setting to Show.

4. From the design palette on the left, drag and drop objects onto the dashboardcanvas.

Select from these objects:

Table 9-1 Dashboard Objects

Object Description

Forms Select simple forms to include in the dashboard by navigatingthe forms folders or by searching for them by name.

Note:

The access permissions set for forms are honored indashboards.

Chart Types Select the chart types to include in the dashboard. When firstadded, a selected chart has sample data. You then associate itwith a form as its data source. When you link a chart to a form,users can immediately see the impact of changing data in theform on the associated charts.

The Combination chart type alternates displaying row data withvertical bars and lines in the chart. For example, the data inrow 1 of a form is displayed as a bar and the data in row 2 as aline, with alternating chart types for even and odd-numberedrows. Although the Combination chart type can display up to 20rows of data, it’s particularly useful when you want to comparetwo categories of data. For example, you want to compareGermany and France’s average exchange rates over severalyears, so the form has Germany rates in row 1 of the form, andFrance’s rates are in row 2.

For information on the Gauge chart type, see About the GaugeChart Type.

Tile Sometimes called performance tiles, a tile is a chart type thatlets you select specific values from the cube to display. See About the Tile Chart Type.

Commentary Select External Artifacts, and then Commentary. Enter textthat explains the data or charts.

URL Dynamic web page summary. Select External Artifacts, andthen URL. Insert only external site URLs starting with thehttps:// security protocol. Don't use internal or relativeURLs or URLs for unconsenting third party sites such asgoogle.com.

5. Customize the dashboard using the dashboards settings and the objects’ hovertoolbar, and then click Save.

See About Your Dashboard's Layout.

You can easily duplicate and modify a dashboard using Copy As on the Dashboardlist page. Select the dashboard, and then click Actions.

Chapter 9Designing Dashboards

9-2

About Your Dashboard's LayoutAbout setting up a dashboard layout:

• The first object you drag occupies the whole canvas.

• Then drag objects to the left, the right, the top, or the bottom of the existing object.

• The dashboard canvas provides two types of drop zones: One to place two objectsnext to each other, each occupying half the space, and the other to place threeobjects, each occupying a third of the space.

• You can design a dashboard with objects to display vertically, horizontally, andeach can have its own size.

• To resize an object that uses Flexible layout, drag the object’s border.

• To resize an object that uses Fixed layout, set its width or height percentage inSettings.

• The form layout can be asymmetric.

• In runtime mode, if a user doesn't have access to a form or if the form is missing,then an adjacent object takes its space. In designer mode, all empty objects aredisplayed so that the designer can choose to remove them.

About the Gauge Chart TypeGauge chart types are handy for showing whether data values fall within anacceptable range or not. You set the maximum value, the range maximums, and thegauge displays ranges as red, yellow, and green to help you quickly assess a currentvalue. So, gauge chart types help you identify problems in important data points ormeasures. For example, you could use a gauge to display the current sales, where thethresholds are set to represent the sales targets.

If the form has multiple values, you can display multiple gauges, up to a maximum of36 (the values in the first 6 rows and the first 6 columns in the form). The remainingvalues in the form are ignored. If you want the gauge chart to display only one value,then associate it with a form that has only one cell value.

You can select either a dial gauge or a status meter gauge. You can display a statusmeter gauge using either horizontal or vertical bars.

Dashboard designers can set:

• Maximum Value: The highest value on the gauge. The dashboard designer setsthe Maximum Value as a default, and then planners can temporarily change it atruntime. If the dashboard designer doesn't specify a maximum value, theapplication automatically sets the maximum value as greater than the value on thegauge.

• Thresholds:

– Low, Medium, and High thresholds: To visually indicate whether a measurelies in the acceptable range or not, these thresholds enable you to display thegauge in red, yellow and green based on the specified values.

– Thresholds where low values are desirable.

Chapter 9About Your Dashboard's Layout

9-3

– Appropriate labels for the thresholds that are displayed when hovering overthe thresholds in the gauge.

For example, here's a form's data:

Here's the resulting dial gauge:

Chapter 9About the Gauge Chart Type

9-4

Here's the resulting status meter gauge with vertical bars:

Note:

If a cell in the form is missing a value, no gauge is displayed for that cell.Also, you must specify at least 2 consecutive thresholds. The applicationneeds the middle threshold value to calculate the chart.

About the Tile Chart TypeA tile is a chart type that lets you select specific values from the cube to display. Inaddition to using a form as a data source, you can directly enter a cell intersection thatprovides the value for a tile. You can have up to 6 tiles across, and 4 rows down in adashboard, and give them a title. Until you associate a tile with data, it displays sampledata.

With a form as the data source for a tile:

• You can have up to six tiles per object.

• The values in the first column (up to the sixth row) are used to create the tiles.

Chapter 9About the Tile Chart Type

9-5

Note:

Sometimes in a form, the first column may be collapsed (hidden) whenviewed as a grid. But the collapsed column is still considered when thetile gets its values from the form.

• The tile’s title is the row’s title, and it gets its values from the first column, then byrow.

• You can set the tile’s title, the tile’s height percentage, legend, and can selectwhich axes from the form to include. For example, if you select a form with threerows, the tile displays three values.

With a cell intersection as the data source for a tile, you can have only one tile perobject.

Tip:

To select a tile chart type, expand the list of chart types by clicking the link atthe bottom of the list.

Here are options you can set for a tile chart type. Note that you can set whether thedisplayed value is horizontally aligned in the tile to the left, the center, or the right.

Scaling Large NumbersEspecially useful for large numbers, you can scale how a currency value is displayed.For example, if the tile value is 1,689,000 and you select K as the scaling option, thetile displays the value as 1689K. Your scaling options:

• None—No scaling is applied.

Chapter 9About the Tile Chart Type

9-6

• Auto—The value is displayed based on its range. For example, 1,500 displays as1.5K, 1,689,000 displays as 1.69M, 42,314,531,21l displays as 42.31B, and1,234,567,891,234 displays as 1.23T.

• K—The value is displayed as thousands units. For example, 1689000 displays as1689K.

• M—The value is displayed as millions units. For example, 12,3456,789 displays as123M.

• B—The value is displayed as billions units. For example, 12,345,678,912 displaysas 12B.

• T—The value is displayed as trillions units. For example, 1,234,567,891,234,567displays as 1,234T.

Customizing Dashboard ColorsMaybe your company uses a standard set of colors in charts to denote different typesof data. For example, dark blue might represent actual data versus light blue forbudget data. When you customize dashboard colors, you select colors in the order ofrows on the form. Series 1 represents the first row of data, and so on. You can assigneach row in the form a color that represents its data in the chart.

You can customize dashboard colors in Bar, Line, Area, Bubble, Column,Combination, Doughnut, Pie, Radar, and Scatter chart types.

1. With the chart on the dashboard's design palette, click Settings .

2. Click Colors.

3. Clear the Default check box, and then click the down arrow for the Series youwant to change.

Check the chart in the background to see the data type that each seriesrepresents.

4. Click the colors you want for the selected Series, and then click Close.

Note:

To select more shades of colors than the ones initially displayed, clickCustom Color....

Your selections apply only to the current chart. Follow these steps to change thecolors of other charts in the dashboard.

Setting Line Width in Line and Combination ChartsYou can set how thin or thick that lines display for Line and Combination chart types ina dashboard.

Chapter 9Customizing Dashboard Colors

9-7

1. With a Line or Combination chart on the dashboard's design palette, click Settings

.

2. Click the Line Weight counter to set the line width.

You can see the effect of your setting on the chart in the background.

Note:

The default width of lines in a Line and Combination chart type is 5pixels. You can select from 1 to 12 pixels.

About Global and Local POVsA local POV on a form reflects the dimension members the form designer selected forthat form. Dashboards and composite forms also support global POV bars, so that thelocal POVs that are common are combined in the global POV bar to avoid repeatingthem in each object. Here's a dashboard that shows a global POV bar (showing Entity,Product, and Year) and a local POV (the Plan drop-down list showing Q2):

Chapter 9About Global and Local POVs

9-8

With a global POV bar, if you change a page in the global POV bar and then click GO,the page changes for all objects that are based on forms. The global POV bar displaysat the top of the dashboard above all the objects, while the local POV bar displayswithin the object. User variables are supported in both global and local POVs indashboards.

In dashboard Settings, you can set whether to show or hide POVs and whether toenable or disable global POV bars. (If you select Hide for POV Bars, and Enable forGlobal POV Bar, the Hide option overrides the Enable option.) The global POV bar isenabled by default; if you disable it, the complete POV is displayed for each local POVas applicable.

About global POV bars:

• The POV Bar is made up of local POV dimensions, Page dimensions and uservariables.

• Depending on the local POV and page of each form on the dashboard, the globalPOV bar is automatically calculated.

• They are reflected in the other objects using forms in that dashboard. That is, theyapply to forms in a dashboard, to charts that are linked to forms, and to tiles thatuse forms as a data source. So if the dashboard doesn’t include a form as a datasource, then neither the local nor global POV bar is available.

Here's an example of how the global POV bar is calculated, based on the local POVdimensions for two forms:

The global POV bar is disabled:

• Form A local POV: Year, Entity, Product

• Form B local POV: Year, Entity, Project

The global POV bar is enabled:

• Global POV bar: Year, Entity

• Form A local POV: Product

• Form B local POV: Project

Because not all dimensions and page selections may be common to all forms on adashboard, the complete POV for a dashboard object may get split between the local

Chapter 9About Global and Local POVs

9-9

and global POV bar. The global POV bar and the local POV together contain thecomplete intersection information for each form on a dashboard.

If there is only one object on the dashboard that uses a form as a data source, thenthe entire POV/page of the form can be moved to the global POV bar.

If there is more than one object on a dashboard that use forms as a data source, thenthis is how the application determines which dimensions go in the global POV bar orstay in the local POV:

• If the dimension is in the POV or page of all the forms, and the member selectionis the same in all the forms, the dimension goes in the global POV bar.

• If the dimension is in the POV on one form and in the page of another form, thenthe dimension stays in the local POV.

• If the dimension is in the POV, then the same members must be selected in all theforms for the dimension.

• If the dimension is a page dimension, then the selected page members must bethe same and display in the same order in all the forms.

The POVs in dashboards honor valid intersections by hiding invalid Page members.See Dashboard POVs and Valid Intersections.

Dashboard POVs and Valid IntersectionsThe POVs in dashboards honor the valid intersections by hiding invalid Pagemembers. Just like in forms, the Page drop-down list is filtered for all selectedmembers in the POV and Page dimensions. Because dashboards support both globaland local POVs, the context for filtering the Page drop-down list depends on whichPOV the members are located. If the Page drop-down list is on a global POV, thefiltering context is only the global POV dimensions. If the Page drop-down list is on thelocal POV, the filtering context is all the global dimensions plus the dimensions on achart’s local POV.

See also About Global and Local POVs.

Chapter 9Dashboard POVs and Valid Intersections

9-10

10Working with Dimensions

Related Topics

• Dimensions Overview

• Viewing and Editing Dimensions

• Working with Dimension Hierarchies

• Adding Custom Dimensions

• Using Extended Dimensionality

• Defining Accounts

• Defining Entity Members

• Creating Alternate Hierarchies

• Financial Consolidation and Close Data Model Overview

• Working with Members

• Setting Up Currencies

• Setting Up Scenarios

• Customizing Application Years

• Working with Attributes

• Working with Attribute Values

• Working with User-Defined Attributes (UDAs)

• Working with Member Formulas

• Working with Alias Tables

Dimensions OverviewFinancial Consolidation and Close provides a set of consolidation and close featuresthat includes out-of-the-box translations, consolidation, eliminations and adjustments.Depending on the functionality required for the application, the system enables onlythe dimensions that are needed for the features.

By default, when you create an application, the system creates dimensions in thisorder:

• Account

• Period

• Data Source

• Consolidation

• Currency (Only if Multi-currency is selected)

• Entity

10-1

• Intercompany (Only if Intercompany is selected during application creation)

• Movement

• Scenario

• Year

• View

• Multi-GAAP (Only if Multi-GAAP is selected during application creation)

The order of the dimensions has an impact on the performance of the consolidation.Any change to the dimension order should first be carefully evaluated.

In addition to these dimensions, you can create custom dimensions. Add Customdimensions after the Intercompany dimension and before the Movement dimension.

You cannot make changes to the default properties of dimensions. The defaultproperties are used in seeded calculations. Each dimension is seeded with a set ofmembers. See Seeded Dimension Members.

The following sections describe the system-defined dimensions.

AccountThe Account dimension represents a hierarchy of natural accounts. Accounts storefinancial data for entities and scenarios in an application. Each account has a type,such as Revenue or Expense, that defines its accounting behavior. Every applicationmust include an Account dimension.

You define properties for Account dimension members, such as the Account type, thenumber of decimal places to display, and whether the account is an IntercompanyPartner account. See Defining Accounts.

PeriodThe Period dimension represents time periods, such as quarters and months. Itcontains time periods and frequencies by displaying the time periods in a hierarchy.For example, if the Actual scenario maintains data on a monthly basis, 12 periods ofdata are available for the year.

The system provides these options for the Period dimension:

• 12-months. If you select 12-months, you must then specify the first period of theFiscal Year. The default value is 12 months, with January as the beginning of theFiscal Year. If you use 12 months, all periods default to the calendar months withperiod labels of January, February, March, and so on.

• 13-period. If you select 13-periods, all periods default to period labels P1, P2, P3,and so on.

The system also creates Quarterly periods for both 12-month and 13-period options.You can create Half-Yearly periods during application creation.

Depending on the fiscal year information, the system builds the Period hierarchy forthe application.

To specify periods for an application, see Creating an Application.

Chapter 10Dimensions Overview

10-2

Data SourceThe Data Source dimension is used to track the source of data, to determine whetherdata is manually entered or loaded from a General Ledger, journal posting, or fromsupplemental detail.

The system stores the different types of input in the Data Source dimension. Itincludes journals input to provide a better audit trail when entity data is consolidated inthe consolidation path. You can view the separate data input journals input in both theProportion and Elimination members of the Consolidation dimension.

Watch this video to learn more about the Data Source dimension.

Using the Data Source Dimension

Data Source Members

By default, the system creates these Data Source members:

• FCCS_Total Data Source

• FCCS_NoDataSource

• FCCS_TotalInputAndAdjusted—A dynamic calculation member that is the parentof various data source inputs (Data Input, Supplemental Data, Other Load, JournalInput). If you want to track other sources of data, you can manually createadditional members under this Parent member.

• FCCS_Data Input—Stores all manual data entry or ASCII data load values

• FCCS_Total Eliminations

• FCCS_Intercompany Eliminations (Child member of FCCS_Total Eliminations.Optional - Only if tracking intercompany eliminations is selected during applicationcreation). Stores the intercompany elimination to track elimination by entity. Youcan add siblings of FCCS_Intercompany Eliminations (descendants ofFCCS_Total Eliminations) to create more detailed tracking of consolidationadjustment and elimination entries. When you view the data in the Contributionmember, you can view the data from Data Input separately from the IntercompanyEliminations Data Source member, even though the Total Data Source could bezero.

• FCCS_Supplemental Data (Optional - Only if selected during application creation).Stores all Supplemental detail data entered and posted through SupplementalData Manager

• FCCS_Journal Input (Optional - Only if selected during application creation). Usedfor data generated from posting of journal adjustments

• FCCS_PCON—Used for storing the Percent Consolidation

The optional members are created based on the options that you specify duringapplication configuration. You can create additional members in the hierarchy asneeded to track input. You cannot remove any of the system-created members.

To specify input members during application creation, see Creating an Application.


10-3


Adding Data Source Member Hierarchies

You can add Data Source member hierarchies as siblings to Total Data Source.

Note these guidelines for adding hierarchies:

• In new hierarchies, parent-level members can only be of the type "Label" or"Dynamic Calc".

• Base/Leaf-level members can be either "Dynamic Calc" or "Never Share".

• You can only enter data to leaf-level "Never Share" members.

• Leaf-level "Never Share" members that are outside of the Total Data Sourcehierarchy are not considered for aggregation to Total Data Source or Total Inputand Adjusted. They are also not considered for Intercompany Elimination.

• Only Translation and Movement calculations are performed on the leaf-level"Never Share" members that are outside of the Total Data Source hierarchy.

• Dynamic-calc leaf-level members are not considered in the consolidation orreporting translation process.

ConsolidationThe Consolidation dimension enables you to report on the details used to perform thedifferent stages of the consolidation process. It provides an audit trail of thetransactions applied to data during the consolidation process. It shows theconsolidation path for an entity reporting to its parent, from Entity Input to Contribution.

When you create an application, the system creates the Consolidation dimension withthe following hierarchy:

• Entity Input - The member that is used for all user input, including journal inputs.For a Base entity, this member represents input data and non-consolidationrelated business logic (for example, member formulas and allocations). For theParent entity, it represents data that is entered through journal entry.

• Entity Consolidation - The member that represents the total of the Contributionmembers at Parent Currency of its children entities becomes the EntityConsolidation at Entity Currency of the Parent Entity.

• Entity Total - The dynamic aggregation of Entity Input and Entity Consolidation.This is the starting point for translation and proportional consolidation.

• Proportion - For a specified entity, this member stores the values obtained afterapplying the percentage contributed to its parent, to the Entity Total.

• Elimination - Stores the Intercompany elimination values. The calculation is doneas part of the Consolidation business rule.

• Contribution - The consolidated result of a single Entity for a specific ParentEntity. This includes the Proportion data, Elimination data and ContributionAdjustments for the Parent/Child entity.

Note:

You cannot add or remove any members from this dimension.


10-4

CurrencyCurrencies store translated values for entities. Every application must include aCurrency. The Currency dimension must include a currency for each default currencyassigned to an entity in the Entity dimension.

When you create an application, the system creates the Currency dimension.However, it is only displayed if the application is a Multi-currency application. See Creating an Application.

You can create members in the Currency dimension for each currency needed in yourapplication. For each application, you specify a currency to use as the ApplicationCurrency.

See Setting Up Currencies.

EntityThe Entity dimension stores the entity hierarchy and represents the organizationalstructure 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 ofentities.

The Entity dimension is the consolidation dimension of the system. Hierarchies in theEntity dimension reflect various consolidated views of the data. Various hierarchiescan correspond to geographic consolidation, legal consolidation, or consolidation byactivity. All relationships among individual member components that exist in anorganization are stored and maintained in this dimension. Entities in an organizationcan be categorized as base, dependent, or parent entities. Base entities are at thebottom of the organization structure and do not own other entities. Dependent entitiesare owned by other entities in the organization. Parent entities contain one or moredependents that report directly to them.

You define properties for Entity dimension members, such as the default currency, andspecify whether the entity allows adjustments and stores intercompany detail. See Defining Entity Members.

IntercompanyThe Intercompany dimension represents all intercompany balances that exist for anaccount. It is used to store the Entity members for Intercompany transactions. If youenable this option when you create an application, the system creates anIntercompany dimension containing system members.

Note:

If you do not enable Intercompany Data when you configure features for theapplication, the system does not create the Intercompany dimension. See Creating an Application.


10-5

Entity dimension members have a member property called Intercompany that specifiesif the member should be included for intercompany transactions. If you select Yes forthis property, a member with the same name is created in the Intercompanydimension.

When you create intercompany transactions, each group must have at least oneintercompany account and one plug account. A plug account is an account that, wheneliminations are completed, stores the difference between two intercompany accounts.

To set up an application for intercompany transactions, you must perform theseactions:

• When defining accounts, specify the accounts that perform intercompanytransactions and specify a plug account for each intercompany account

• When defining entities, specify the entities that perform intercompany transactions

By default, the system creates these Intercompany members:

• No Intercompany - This member is used in member intersections to storeinformation such as currency rates. It cannot be renamed or edited.

• Intercompany Entities - This member is the parent member under which all ICPentities are created.

• Total Intercompany - This member is the top-most member in the hierarchy.

When an entity is enabled for Intercompany, the system automatically adds a newmember in the Intercompany dimension. You cannot manually add new members.

You cannot modify or delete Intercompany members.

MovementThe Movement dimension captures the movement details of an account. By default,the system provides members in the Movement dimension to capture the OpeningBalance, Closing Balance, changes, and FX calculations.

See Seeded Dimension Members.

It is also used for Cash Flow Reporting. System members named"FCCS_Mvmts_Operating", "FCCS_Mvmts_Investing", and "FCCS_Mvmts_Financing"are created as parent accounts to enable you to create additional movement details asneeded for Cash Flow reporting.

The Movement dimension enables you to perform these tasks:

• View details of the cash flow movements when viewing the Balance Sheet

• Automatically generate the Cash Flow due to the segregation of movementsbased on cash flow categories

When you create an application, the Movement dimension is created by default withseeded members, and adds system members based on the optional features that youenable. During application creation, the system creates cash flow members andhierarchies for Cash Flow Reporting in the Movement and Account dimensions.

You can create your own Movement members, but only within theFCCS_Mvmts_Subtotal parent, not within the FCCS_Mvmts_FX_Total parent.

Watch this video to learn more about setting up the Movement dimension.


10-6

Setting Up the Movement Dimension

Adding Movement Dimension Members

If you add Movement members, make sure that every new Movement member(Mvmts_) is added to both the FCCS_ClosingBalance and the FCCS_CashFlowhierarchies.

• Under the FCCS_ClosingBalance hierarchy, the new Movement member shouldhave a Consolidation Operator of Addition.

• Under the FCCS_CashFlow hierarchy, the new Movement member should have aConsolidation Operator of Subtraction.

Note:

As a best practice, it is not recommended that you create member formulasfor Movement dimension members, as they will have a significant impact onconsolidation performance.

Cash Flow - Movements Sign Reversal Logic

Indirect Cash Flow presents cash flow in terms of the movements of non-cashaccounts (that is, the sources and uses of cash). When you record a movement on anon-cash account, any increase in assets or expenses (DR "normal sign" accounts)causes a matching decrease in cash. Equally, any increase in liabilities, equity orrevenue (CR "normal sign" accounts) causes an increase in cash.

When you present the change in cash (operating, investing, financing) in terms of thenon-cash account movements, the sign of the cash movement is opposite to the signof the related non-cash account movement for assets and expenses and the samesign for liabilities, equity and revenue.

When you present the Cash Flow statement, you use the Movement dimensionmembers to detail the rows in the report. You also need to specify an account. Youcan use the top-level Balance Sheet account against which to report all movements inthe Cash Flow report, because the Cash Flow report rows are sufficient to define thedetail. You only need one Balance Sheet account to "gather" all movements.Generally, the top-level Balance Sheet account (which should always net to zero) isset as an Asset account.

When you report a movement posted to an Asset account as a change in cash, youneed to reverse the sign, because an increase in an Asset represents a decrease incash. When you report a movement that was posted to a Liability account as a changein cash, you also need to reverse the sign, because you are reporting against a singleBalance Sheet top member that is an Asset account. An amount posted as anincrease to a base Liability account will be reported at the top Balance Sheet Assetaccount with the opposite sign and therefore as a decrease in the total Balance Sheetamount (because as the Liability account movement entry aggregates up through theaccount hierarchy, the Account Type changes from Liability to Asset and therefore thesign of the data is flipped). You need to flip the sign of all non-cash movements whenpresenting cash flow, regardless of the Account Type on which the original postingwas made.


10-7


ScenarioThe Scenario dimension represents a set of data such as Actual, Budget, or Forecast.For example, the Actual scenario can contain data that reflects current businessoperations. The Budget scenario can contain data that reflects targeted businessoperations. The Forecast scenario typically contains data that corresponds topredictions for upcoming periods. A Legal scenario can contain data calculatedaccording to legal GAAP format and rules.

By default, the system creates the Actual system Scenario member. You can createadditional Scenario members.

See Setting Up Scenarios.

YearThe Year dimension represents the fiscal or calendar year for data.

When you create an application, you specify the range of years for the application.

The system builds the Year dimension based on the range that you specified. You canincrease the range of years after the application is created. However, you cannotdecrease the range. See Customizing Application Years.

ViewThe View dimension represents various modes of calendar intelligence such asPeriodic, Year-to-Date, and Quarter-to-Date frequencies. If you set the View toPeriodic, the values for each month are displayed. If you set the View to Year-to-Dateor Quarter-to-Date, the cumulative values for the year or quarter are displayed.

You load data into the system at the base-level view. Data is stored in the Periodicmember.

By default, when you create an application, the View dimension has these members:

• Periodic - Each period shows the data entered, calculated or derived for thisspecific period.

• YTD - Year-to-Date view. Periods within a year are cumulative.

• QTD - Quarter-to-Date view. Periods within a quarter are cumulative.

• HYTD - Half-Year-to-Date view. Periods within a half-year are cumulative. HYTD isonly created it if you selected it during application creation.

You cannot remove any View dimension members or create new members. You canedit member properties, such as Alias.

Multi-GAAPThe Multi-GAAP dimension is an optional dimension that is used if you need to reportyour financial statements in both local GAAP and in IFRS or other GAAP. Thisdimension tracks the local GAAP data input as well as any GAAP adjustments.

If you select the Multi-GAAP dimension during application creation, you can selectfrom these additional options:


10-8

• Enter Adjustment—You can select this option to enter GAAP adjustmentsmanually. You enter data in the "FCCS_Local GAAP" member. Adjustments tolocal GAAP for IFRS are entered in the "FCCS_Adjustments" member. The IFRSamount will be calculated.

• Calculate Adjustment—Select this option to allow the system to automaticallycalculate the adjustment amount based on the Local GAAP and IFRS amountentered. You enter data in the "FCCS_Local GAAP" and "FCCS_IFRS" members.The Adjustments amount will be calculated in the Adjustments member.

You can include additional members and hierarchies for other GAAP adjustments. Youcan modify member aliases, but not member labels.

By default, if you select this dimension, the system provides the following dimensionmembers:

• FCCS_IFRS

• FCCS_Local GAAP

• FCCS_Adjustments

To specify Multi-GAAP reporting during application creation, see Creating anApplication.

Viewing and Editing DimensionsYou can view and edit dimension properties using either the Classic or the Simplifieddimension editor.

The Simplified dimension editor enables you to check for invalid dimension memberproperties and take action to correct the properties. Invalid properties are bordered inred in the Simplified dimension editor grid.

Users with the security roles to view and edit dimensions in the Classic dimensioneditor can perform similar actions in the Simplified dimension editor.

See the following sections:

• To edit dimension properties using the Simplified dimension editor (accessed fromApplication Overview), see About Editing Dimensions in the Simplified DimensionEditor.

• To edit dimension properties using the Classic dimension editor (accessed fromthe Navigator), see Managing Dimensions.

Working with Dimension HierarchiesDimension hierarchies define structural and mathematical relationships, andconsolidations between members in the database. Relationships are representedgraphically in a collapsible hierarchy diagram. Upper-level dimension members arecalled parent members, and a member immediately below a parent member is referredto as its child. All members below a parent are referred to as descendants. Thebottom-level hierarchy members are called base-level members.

Data is 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-levelmembers. In some cases, data for base-level members is calculated.

Chapter 10Viewing and Editing Dimensions

10-9

Note:

As a best practice, a limit of 20 levels of hierarchy depth is recommended.

Expanding and Collapsing Dimension HierarchiesTo expand dimensions or members:



3. For Dimension, select the dimension and member to expand.


• Click Expand.

• Click Expand .

• Click the closed folder.

To collapse dimensions or members:



3. For Dimension, select the dimension to collapse.


• Click Collapse.

• Press the Left Arrow.

• Click Collapse .

• Click the open folders.

Navigating Dimension Hierarchies• Press the Up Arrow to move to the previous member.

• Press the Down Arrow to move to the next member.

• In Page, enter the page to view and click Go or press Enter.

• Click Start, Prev, Next, or End to view other pages.

By default, 14 members are displayed per page. You can change this by settingpreferences for Show the Specified Members on Each Dimensions Page

Finding Dimensions or MembersTo find dimension members in dimension hierarchies:



Chapter 10Working with Dimension Hierarchies

10-10

3. For Dimension, select the dimension for the member.

4. For Search, select Name, Alias, or Both.

5. Enter the member name, alias, or partial string for which to search.

6. Click Search Down or Search Up .

Sorting MembersYou can sort members in ascending or descending order, by children or descendants.Sorting members affects the outline.

To sort members:



3. For Dimension, select the dimension for the members.

4. On Dimensions, select the members whose children or descendants you want tosort.

5. For Sort, select children or descendants.

Sorting by children affects only members in the level immediately below theselected member. Sorting by descendants affects all descendants of the selectedmember.

6. Click Sort Ascending to sort by ascending order or Sort Descending tosort by descending order.

7. Click OK.

The next time you create or refresh the database, the outline is generated withmembers in the order that is displayed.

Moving Members Within the Dimension HierarchyYou can move one member or a group of members in the same branch.

To move members or branches among siblings:



3. For Dimension, select the dimension for the members to move.

4. Select the member or branch to move.


• Click Move Up to move the member up one position.

• Click Move Down to move the member down one position.

To move members, including parents and children:



Chapter 10Working with Dimension Hierarchies

10-11

3. For Dimension, select the dimension with the members to move.

4. Select the member or branch to move.

5. Click Cut.

You cannot Cut members after adding or editing dimensions, navigating todifferent pages, deleting members, or logging of. Cut is not available for rootdimension members.

6. Click the destination level under which to move the members.

7. Click Paste.

8. Click OK.

9. Update and validate business rules and reports.

Viewing a Member’s AncestorsTo view a member’s ancestors:



3. For Dimension, select a dimension.

4. Select the member in the dimension hierarchy.

5. Click Show Ancestors.

6. Click Close.

Showing Member UsageTo view where members are used in an application:



3. Select the dimension whose member usage you want to view.

4. Click Show Usage.

5. At the bottom of the Member Usage window, select where in the application toview the member's usage.

6. Click Go.

7. Click Close.

Adding Custom DimensionsIn addition to the system predefined dimensions, you can create up to two additionalCustom dimensions based on your application needs. Custom dimensions areassociated with the Account dimension and provide additional detail for accounts.

Chapter 10Adding Custom Dimensions

10-12

Note:

If Extended Dimensionality is enabled for the application, you can create upto four Custom dimensions. If the application is enabled with the Multi-GAAPreporting option, you can create three Custom dimensions. See CreatingExtended Dimension Applications.

The Dimensions list displays all of the dimensions for the application. When you createa dimension, the system adds it to the end of the Dimensions list.

When you add Custom dimensions, you define their properties, including name, alias,security, and attributes.

Table 10-1 Properties for Custom Dimensions

Property Value

Dimension Enter a name that is unique across alldimensions.

The Custom Dimension name cannot containthese characters:

Ampersand (&), Apostrophe (‘), Asterisk (*), Atsign (@), Backslash (\), Caret (^), Colon (:),Comma (,), Curly brackets ({}), Dollar sign ($),Double quotation marks ("), " Equal sign (=),Exclamation mark (!), Forward slash (/),Greater than (>), Less than (<), Line (|), Minussign (-), Number sign (#), Parentheses ( ),Percent sign (%), Period (.), Plus sign (+),Question mark (?), Semi-colon (;), Squarebrackets ([]), or Tabs.

Alias Optional: Select an alias table. Enter a uniquealternate name for the dimension.

Description Optional: Enter a description.

Plan Type Select the application types for which thedimension is valid. Clearing this option makesall members of the dimension invalid for thedeselected type.

Apply Security Allow security to be set on the dimensionmembers; must be selected before assigningaccess rights to dimension members.Otherwise, dimensions have no security andusers can access members without restriction.

Data Storage Select a data storage option. The default isNever Share.

Aggregation OptionsYou can define calculations within dimension hierarchies using aggregation options.Aggregation options determine how child member values aggregate to parentmembers:

• + Addition


10-13

• - Subtraction

• * Multiplication

• / Division

• % Percent

• ~ Ignore

• Never (do not aggregate, regardless of hierarchy)

Note:

All immediate children of the dimension name member must be set with anaggregation option of Ignore or Never. Seeded dimension members shouldalready have the Consolidation Operator set as Ignore. Use the topdimension member rather than the dimension name in forms and reports.

Children under a Parent member that has the Label Only data storageproperty must have the aggregation operator set to Ignore.

Financial Consolidation and Close has a consolidation script that performsthe consolidation of one entity into another. Do not change the consolidationoperator on Entities. If this Entity property is anything other than Ignore, theresults are incorrect.

Data Storage Options

Table 10-2 Data Storage Options

Option Impact

Store Stores data values of members.

Dynamic Calc Calculates data values of members, anddisregards the values.

Never Share Prohibits members in the same dimensionfrom sharing data values.

Shared Allows members in the same dimension toshare data values.

Label Only Displays the data of the first child memberregardless of the aggregation setting of thechildren.

About Dynamic CalcWith dynamically calculated members, the system calculates data values of members,and disregards these values. The limit is 100 children under a Dynamic Calc parent.Changing a member's storage to Dynamic Calc may result in loss of data, dependingon how the data was originally derived. You may need to update outlines, calculations,or both to get the dynamically calculated value.


10-14

Store Data StorageDo not set parent members to Store if their children are set to Dynamic Calc. With thiscombination, new totals for parents are not calculated when users save and refreshforms.

Shared Data StorageUse Shared to allow alternate rollup structures in the application.

Never Share Data StorageThe default data storage type is Never Share when you add user-defined customdimensions. You can use Never Share for parent members with only one childmember that aggregates to the parent, to apply access to the child member.

Label Only Data StorageLabel-only members are virtual members; they are typically used for navigation andhave no associated data. Note:

• You cannot assign level 0 members as label-only.

• Label-only members can display values.

• Making dimension members label-only minimizes database space by decreasingblock size.

• You cannot assign attributes to label-only members.

• In a multicurrency application, you cannot apply label-only storage to members ofthese dimensions: Entity, Versions, Currencies, and user-defined customdimensions. To store exchange rates, use Never Share.

• Data Storage for children of label-only parents is set to Never Share by default.

Caution:

Do not design forms in which label-only parents follow their first childmember, as you cannot save data in the first child member. Instead,create forms with label-only parents selected before their children, or donot select label-only parents for forms.

Setting Dimension Properties

Table 10-3 Dimension Properties

Property Value

Dimension Enter a dimension name.



10-15

Table 10-3 (Cont.) Dimension Properties

Property Value

Alias Optional: Select an alias table and enter analternate name of up to 80 characters.

Plan Type Select application types for which thedimension is valid.

Apply Security Allow security to be set on dimensionmembers. If you do not select this option,there is no security on the dimension, andusers can access its members withoutrestriction. Must be selected before assigningaccess rights to dimension members.

Data Storage Select data storage options:

• Store• Dynamic Calc• Never Share• Shared• Label OnlySee Data Storage Options.

Display Option Set application default display options for theMember Selection dialog box. Select MemberName or Alias to display members or aliases.Member Name:Alias displays members onthe left and aliases on the right. Alias:MemberName displays aliases on the left andmembers on the right.

Enable custom attribute display Display available and selected attributes fordimensions with associated attributes. Enablecustom attribute display for dimensions withattributes.

Setting Dimension Evaluation OrderEvaluation Order enables you to specify which data type prevails when a dataintersection has conflicting data types. For example, if Account members are set to theCurrency data type, and Product members are set to the Smart List data type, you canset whether the Currency or Smart List data type prevails at an intersection.

To set the dimension evaluation order:

1. Select Application, then Overview, and then Dimensions.


10-16

Note:

CAUTION: To modify the dimension Evaluation Order, do not use theDimension Editor under the Navigator menu. You must modify theEvaluation Order only from the Application Overview Dimensions tab.

In addition, the Service Administrator must always ensure that theevaluation order for the Status Replacement Type dimension is set to 2.This is required so that the seeded Data Status form displaysconsolidation statuses.

2. Click the button on the Evaluation Order column next to a dimension to set theorder of precedence.

Using Extended DimensionalityExtended Dimensionality is the ability to add additional Custom dimensions. Customdimensions are associated with the Account dimension and provide additional detailfor accounts. In addition to the system predefined dimensions, you can create amaximum of four Custom dimensions based on your application needs. If yourapplication is enabled with the Multi-GAAP reporting option, you can create threeCustom dimensions.

Note:

The ability to add four Custom dimensions is available in all new provisionedenvironments.

Two Custom dimensions are available in environnments provisioned beforeJune 2019. If you want to use more than two Custom dimensions in thoseenvironments, you must request the Extended Dimensionality update fromOracle Support. After you apply the update, you must create a newapplication. You cannot modify the number of dimensions in an existingapplication. When Extended Dimensionality is enabled, you can create fourCustom dimensions. If the application is enabled with the Multi-GAAPreporting option, you can create three Custom Dimensions.

To create an Extended Dimension application, see Creating Extended DimensionApplications.

Metadata Changes for Extended Dimensionality

When Extended Dimensionality is enabled for an application, the system makes thesechanges to seeded dimensions and members:

Custom Dimensions

For all Custom dimensions, the "Total Custom" members will have a Data Storageproperty of Dynamic Calc.

If you create any parent members in Custom dimensions, they must have the DataStorage property of Dynamic Calc.

Chapter 10Using Extended Dimensionality

10-17

Intercompany Dimension

The Intercompany Top member will be Dynamic Calc.

Multi-GAAP Dimension

The parent members in the Multi-GAAP dimension will be Dynamic Calc.

Period Dimension

The Quarters, HYs and Year Total member formulas will now have a constructNONEMPTYTUPLE(); at the beginning.

The solve order of these Dynamic Calc members are set to 52 so that they will beexecuted at the end.

View Dimension

QTD, HYTD and YTD member formulas will now be Never Share.

There will be three new members under the new parent member FCCS_View_SystemMembers:

• FCCS_HYTD_RULE

• FCCS_QTD_RULE

• FCCS_YTD_RULE

These are Dynamic Calc members that have a construct NONEMPTYTUPLE(); at thebeginning. The solve order of these Dynamic Calc members are set to 51. Thesemembers are System members and should not be modified.

If you add any new Dynamic Calc members to sparse dimensions, you shouldevaluate the implication of the calculation and set the solve order appropriately toachieve maximum performance gain. Those member formulas should start withNONEMPTYTUPLE();.

Defining AccountsThe Account dimension defines the chart of accounts for an application. When youcreate an application, the system creates the Account dimension with a hierarchy ofsystem and seeded members, some based on the features that you enable for theapplication. Seeded accounts are created with the prefix FCCS, for example,FCCS_IncomeStatement.

By default, the system creates these types of Account members:

• Seeded members

The basic Balance Sheet and Income Statement are created as seeded members.

The structure of the Balance Sheet is created with Dynamic Calc parent members.Two formats are available, the “Traditional” format (Assets = Liabilities + Owner’sEquity) and the “Net Assets” format (Assets + Liabilities = Owner’s Equity).

It is recommended that the initial upper level structure of the Balance Sheet (downto and including Total Assets, Total Liabilities and Total Equity) not be changed,although lower level accounts can be re-organized. Other seeded artifacts (suchas seeded consolidation rules) rely on the basic Balance Sheet structure ascreated by the system.

Chapter 10Defining Accounts

10-18

• Optional seeded members

These members are created based on application features that you enabled. Forexample, Ratio accounts required to perform the ratio calculation are optionalsystem members. Depending on which ratios you want to include as part of theapplication, those accounts will be seeded. Other examples include Return onSales and Gross Profit Margin.

If the Ownership Management feature is enabled, the basic balance sheetstructure is extended to ensure that base (level 0) accounts required by theseeded consolidation rules exist.

• Shared members

Some seeded members are also added to an alternate hierarchy as sharedmembers. For example, all the Account members listed under Income Statementor Balance Sheet system members which are set for a Cash Flow category have ashared instance created under the selected category in Cash Flow.

System Accounts

These accounts are provided by default when you create an application:

• FCCS_CSTATUS—Stores the calculation status value used by the system

• FCCS_CSTATUS FILTER—Stores the calculation status text for display in a dataform.

Income Statement Accounts

The Account dimension provides a pre-built hierarchy for the Income Statement. Thehierarchy is seeded with system members used for built-in calculations. You can addchild members to the parent members or additional sibling members to the seededmembers.

Note that the Income Statement is created as a hierarchy within the Owner’s EquityRetained Earnings Current account.

Balance Sheet Accounts

The Account dimension provides an initial pre-built hierarchy for the Balance Sheet.The hierarchy is seeded with members used for built-in calculations.

Two Balance Sheet formats are available for selection when the application is firstcreated:

• "Traditional" format (Assets = Liabilities + Owner’s Equity)

• "Net Assets" format (Assets + Liabilities = Owner’s Equity).


10-19

All Balance Sheet and Income Statement accounts must have the Flow Account typeassigned. All of these accounts must have an opening balance calculated and aMovement member associated with them to reflect the change for the period. FCCSsystem rules populate the Opening Balance movement member for all Flow typeaccounts. See Movement.

The Traditional and Net Assets seeded account dimensions include Level 0 membersthat are defined as Dynamic Calc. These members must have at least one memberadded as a child.

• FCCS_Cash And Cash Equivalents

• FCCS_Acct Receivable

• FCCS_Inventories

• FCCS_Fixed Assets

• FCCS_Other Long Term Assets

• FCCS_Acct Payable

• FCCS_Long Term Liabilities

• FCCS_Other Equity

• FCCS_Sales

• FCCS_Cost of Sales

• FCCS_Operating Expenses

• FCCS_Provision for Income Tax

For each of the above members, you must add a dummy account member with theseproperties:

• Data Storage Default = Store

• Data Storage Consol = Store

• Consol Operator: +

Historical Accounts

The Historical Accounts group contains accounts that are considered HistoricalOverride accounts. Historical accounts are translated at a weighted average of themovements over time rather than being translated at the current period ending rate.Override accounts are designated as either a Rate Override or an Amount Override fortranslation. Override accounts allow the user to enter either a Rate or an Amount tooverride the default translation. These historical override accounts are created by thesystem in the Historical Accounts grouping as shared members based on theExchange Rate Type selected for the primary member. There might not be anyseeded Historical Override accounts depending on the application creation settingsselected, so there might initially only be “placeholder” accounts in this hierarchy.Placeholder accounts are base members populated to ensure that the parent accountsare treated as parent accounts and are not mistaken as base accounts.FCCS_Investment In Sub is an example of an optional seeded Rate Override account.

If an account is a Historical Account, but does not contain an Override (for example,FCCS_Retained Earnings Prior), it is not included in the Historical Accounts hierarchy.

To specify that an account is a Historical Override Account, you must assign the"Historical Rate Override" or "Historical Amount Override" as the Exchange Rate Type.


10-20

If an Amount Override or a Rate Override is specified for the Historical account, thesystem uses the applicable override entry for the account during translation. If you donot enter an override rate or amount, the Historical Override account is translatedusing the rate specified for default translations. This gives the same translated resultsas for Historical (non-override) accounts.

A pre-built system form named Override Rates is generated from the Historicalaccount hierarchy to enable you to enter either the override amount or override rate foreach entity for each currency. See Predefined Forms.

Ratio Accounts

Ratio accounts are created under a separate account hierarchy if this option isenabled during application creation. All associated member formulas for thecalculations are also created for the accounts. Additionally, you can create your ownratio accounts.

Intercompany Account

For any Intercompany accounts that will be used for standard system eliminations, youmust assign attribute values to identify them as Intercompany accounts, as well asselecting the Plug account to be used for elimination. The accounts that are to beselected as Plug accounts must first be designated as Plug accounts by selecting thePlug accounts attribute.

Account Hierarchy Order

The Balance Sheet group should be the first hierarchy below the FCCS_SystemAccount, Exchange Rates, Entered Exchange Rates and Exchange Rates SystemMembers hierarchies.

You can add additional hierarchies in the Account dimension to include sharedBalance Sheet accounts or any additional accounts required. For example, the seededBalance Sheet Cash and NonCash hierarchy is an additional hierarchy containingshared copies of the Balance Sheet accounts.

Note:

As a best practice, a limit of 20 levels of hierarchy depth is recommended.

All additional hierarchies of the Balance Sheet that you create should be created afterFCCS_Total Balance Sheet - Cash and NonCash.

All alternate hierarchies of Income accounts can be placed in the Income Statementgrouping.

Account TypesEach account is associated with an “Account Type” that represents the accountingnature of the account.

Each account is categorized as either Flow or Balance. Flow Account typesaccumulate over time. Balance Account types represent a balance at a specific periodand therefore do not aggregate over time.


10-21

• Flow account types: Revenue, Expense

• Balance account types: Asset, Liability, Equity

Table 10-4 Account Types

Account Type Description

Expense Costs incurred by a company to generaterevenue. Examples of expenses are: cost ofsales, salary expense, travel expense.

Revenue Income received as a result of the sale ofgoods or services. Examples of revenueinclude Trade Sales, Income from Sales ofFixed Assets

Asset A resource that has economic value and fromwhich the company expects to generateincome over time. Examples of assets areinventory, fixed assets, accounts receivableand pre-paid insurance.

Liability Legal debts and obligations that companiesowe to third parties as a result of businessoperations. Examples of liabilities includeaccounts payable, accrued payroll, and notespayable.

Equity The value of ownership in a company andequal to the amount of assets remaining afterall debts are satisfied. Examples of equityaccounts include common stock, preferredstock, and retained earnings.

Saved Assumption Non-financial items used by a company forstatistical analysis and reporting purposes.Examples are square footage and headcount,units sold, miles traveled, and patientsadmitted.

Time Balance PropertyThe Time Balance property specifies how the system calculates the value of summarytime periods.

Table 10-5 Time Balance Properties

Time Balance Property Description Example

Flow Aggregate of all values for asummary time period as a periodtotal.

Jan: 10 Feb: 15 Mar: 20 Q1: 45

Balance Ending value in a summary timeperiod as the period total.

Jan: 10 Feb: 15 Mar: 20 Q1: 20

Summary of Account Types and Time BalanceEach account is associated with an Account Type and is categorized as either a Flowor Balance Time Balance. Flow accounts accumulate over time through the


10-22

aggregation of associated Movement entries. Balance accounts represent a balance ata specific period-end and do not aggregate over time.

Table 10-6 Summary of Account Types and Time Balance

Account Type Time Balance foraccounts insideBalance Sheethierarchy

Time Balance foraccounts outside ofBalance Sheethierarchy

Variance Reporting

Revenue Flow User-defined Non-Expense

Expense Flow User-defined Expense

Asset Flow User-defined Non-Expense

Liability Flow User-defined Non-Expense

Equity Flow User-defined Non-Expense

Saved Assumption Not applicable User-defined User-defined

Note that the Opening Balance movement of Flow accounts is calculated as theClosing Balance of the prior periods. Closing Balance is an aggregation of OpeningBalance and all movement amounts for the period. No Opening Balance is calculatedfor Balance accounts.

Aggregation (Consolidation Operator)The Aggregation (Consolidation Operator) determines how child accounts aggregateto the parent account. Note that this aggregation does not depend on, and isindependent of the account types.

See Aggregation Options.

Note:

Financial Consolidation and Close has a consolidation script that performsthe consolidation of one entity into another. Do not change the ConsolidationOperator on Entities. If this Entity property is anything other than Ignore, theresults will be incorrect.

The following table indicates how each Account Type behaves when totalled into aspecific type of parent account within the balanced Balance Sheet hierarchy. Forexample, when aggregated, Asset account values are aggregated into parent Assetand Expense accounts, and subtracted from parent Liability and Revenue accounts.

Table 10-7 Account Type Behaviors During Aggregation into Parent Accounts

Account Type Parent Account

Child Account Asset Liability Equity Revenue Expense

Asset Add Sub Sub Sub Add

Liability Sub Add Add Add Sub


10-23

Table 10-7 (Cont.) Account Type Behaviors During Aggregation into Parent Accounts

Account Type Parent Account

Child Account Asset Liability Equity Revenue Expense

Equity Sub Add Add Add Sub

Revenue Sub Add Add Add Sub

Expense Add Sub Sub Sub Add

SavedAssumption

Add Add Add Add Add

Note that Saved Assumption accounts should not be used within the balancedBalance Sheet because they are non-financial accounts. Saved Assumption accountscan be added or subtracted when aggregating to their parent accounts as required.

This example illustrates how different account types are aggregated into parentaccounts:

In this example, Total Assets is an Asset account and the parent of Fixed Assets (anAsset account) and Amortization (a Liability account). When the accounts areaggregated into the parent account, the Fixed Assets value of 100 is added, theAmortization value of 20 is subtracted, and the resulting value for Total Assets is 80.

Account Types and Variance ReportingAn account’s variance reporting property determines whether it is treated as anexpense when used in member formulas:

• Expense: The actual value is subtracted from the budgeted value to determine thevariance.

• Non-Expense: The budgeted value is subtracted from the actual value todetermine the variance.

Examples:

• When you are budgeting expenses for a time period, the actual expenses shouldbe less than the budget. When actual expenses are greater than budgetexpenses, the variance is negative. For example, if budgeted expenses are $100,and actual expenses are $110, the variance is -10.

• When you are budgeting nonexpense items, such as sales, the actual salesshould be more than the budget. When actual sales are less than budget, thevariance is negative. For example, if budgeted sales were $100, and actual saleswere $110, the variance is 10.


10-24

Saved AssumptionsYou use saved assumptions to identify key non-financial business drivers and ensureapplication consistency, by selecting time balance and variance reporting properties.

• Variance reporting determines the variance between budgeted and actual data, asan expense or non-expense.

• Time balance determines the ending value for summary time periods.

Examples of how time balance and variance reporting properties are used with savedassumption account members:

• Create a saved assumption of an expense type for variance reporting, assumingthat the actual number of employees is less than the number budgeted. Todetermine the variance, the system subtracts the actual amount from the budgetedamount.

• Make an assumption about the number of units sold at the end of the time period.Determine the final quantity for the summary time period by aggregating thenumber of units sold across time periods.

Data Types and Exchange Rate TypesThe Data Type determines how values are stored in account members, and theexchange rates used to calculate values. Available data types for account membervalues:

• Currency - Stores and displays in the default currency.

• Non-currency - Stores and displays as a numeric value.

• Percentage - Stores a numeric value and displays as a percent.

• Date - Displays as a date.

• Text - Displays as text.

For accounts with the Currency data type, these are exchange rate types:

• No Rate– Closing Balance of translated data is adjusted to an Ending Ratetranslation by calculating Foreign Exchange variation on Opening Balance andMovements.

• Historical – Closing Balance accumulated as a weighted average of the translatedmovements with no net Foreign Exchange variation. Foreign Exchange variation iscalculated but then transferred to Cumulative Translation Adjustment / UnrealizedGain or Loss on Translation.

• Historical Amount Override – Override amounts can be entered and the account isotherwise treated as a Historical account.

• Historical Rate Override – Override rates can be entered and the account isotherwise treated as a Historical account.

Defining Account PropertiesYou define properties for accounts, such as account types, and data types, andwhether they are Intercompany accounts.


10-25

For Intercompany accounts, see Setting Account Attribute Values.

To define account properties:



3. From the Dimension list, select Account.

4. Select Action, then select Add Child or Add Sibling.

5. On the Member Properties tab, enter account properties.

Table 10-8 Account Properties

Property Description

Name Enter a name that is unique across alldimension members.


Alias Table Optional: Select the alias table to store thealias name.

Alias Optional: Enter an alternate name for themember.

Account Type Select the account type:

• Expense• Revenue• Asset• Liability• Equity• Saved AssumptionSee Account Types.

Variance Reporting Select an option:

• Expense• Non-ExpenseSee Account Types and Variance Reporting.

Time Balance Specify how the system calculates the value ofsummary time periods:

See Time Balance Property.


10-26

Table 10-8 (Cont.) Account Properties


Exchange Rate Type Indicates the translation options for thefinancial accounts.• Historical• Historical Amount Override• Historical Rate Override• No Rate (for non-historical accounts)

Note:

By default, thesystem usesAverage Rate forFlow accounts,and Ending Ratefor Balanceaccounts. Thedefault settingscan be changed.

Source Cube Specify the source cube for the member.

Data Storage Select data storage options:

• Store• Dynamic Calc• Never Share• Shared• Label OnlySee Data Storage Options.

Two Pass Calculation Select whether to calculate values of membersbased on values of parent members or othermembers.

Allow Upper-Level Entity Input Specify whether parent Entity input is allowedfor this account.

Plan Type Indicates the application type for which themember is valid.

Data Type Select a data type:

• Unspecified• Currency• NonCurrency• Percentage• Date• Text• Smart ListsSee Data Types and Exchange Rate Types.

Smart Lists Optional: Select a Smart List to associate withthe member.


10-27

Table 10-8 (Cont.) Account Properties


Enable for Dynamic Children Enables users to create children for thismember by entering a member name in theruntime prompt for a business rule that hasbeen configured with a dynamic parentmember).

Number of Possible Dynamic Children This option is available if Enable for DynamicChildren is selected. Enter the maximumnumber of dynamically-added members thatusers can create. The default is 10.

Access Granted to Member Creator This option is available if Enable for DynamicChildren is selected. Determines the accessthat member creators have to dynamicmembers that they create with a runtimeprompt:• Inherit—The member creator will inherit

the closest parent's access to the newly-created member.

• None—The member creator will not beassigned any access to the newly-createdmember. (An administrator can laterassign the member creator access to themembers.)

• Read—The member creator will beassigned Read access to the newly-created member.

• Write—The member creator will beassigned Write access to the newly-created member.

Note:

If anadministratorchanges thesesettings, theyaffect only futuredynamicmembers; theydo notretroactivelyaffect dynamicmembers.

Setting Account Attribute ValuesYou specify Intercompany account and Comprehensive Income CumulativeTranslation Adjustment (CICTA) account attributes on the Attribute Values tab for level0 accounts. Note that these settings are not applicable to parent accounts.


10-28

When you set the Intercompany Account property to Yes, you must specify a Plugaccount.

To set Account Attribute values:

1. Select an existing level 0 Account member, click Edit and select the AttributeValues tab.

2. Enter this information:

Table 10-9 Intercompany Account Attribute Values

Attribute Description

Intercompany Account Specify if the account is an Intercompanyaccount. If set to Yes, a level 0 Plug accountmust also be specified for this account inorder for eliminations to be executed.

Note:

This option is only available ifIntercompany is enabled for theapplication.

Is Plug Account Specify if this level 0 account can be a Plugaccount.

Plug Account For the accounts that have Intercompanyset to Yes, and IsPlugAccount is not set,you can specify a Plug account. Accountswith this property set to Yes can be selectedas Plug Accounts.

Table 10-10 Comprehensive Income Cumulative Translation Adjustment(CICTA) Attribute Values

Attribute Description

Is CICTA Account Specify if this account is a replacement forthe seeded FCCS_CICTA account.

CICTA Redirection Account To redirect the FX-To-CICTA posting to anaccount other than the seededFCCS_CICTA account, specify the accountto use. Available accounts will have the “IsCICTA Account” setting (above) enabled.”.

3. Click Save.

4. If you add a Plug account:

a. Select the Account dimension member and select the Custom Attributesbutton.

b. Select the attribute Plug Account and click the Synchronize button.

This displays the newly added Plug account in the list of Plug Accounts on theright side of the Plug Account Attribute Values tree.


10-29

Defining Entity MembersBy default, the Entity dimension includes a Global Assumptions member in the entityhierarchy. The Global Assumptions member is used to store information such ascurrency rates. You cannot edit or rename it.

The system also creates the Total Geography member by default. This member isused for system forms. You can create new members as siblings to Total Geography,and you can create a hierarchy under it. You then need to change the Entity memberselector in the forms appropriately.

Shared entities must be entities that are also Intercompany Partners. If you share aparent of an entity that is an Intercompany Partner, eliminations will not occur.

You define attributes for Entity dimension members, such as the default currency andsecurity class, and to specify whether the entity allows adjustments.

By default, the Consolidation Operator for the Entity dimension is Ignore. A seededconsolidation script performs the consolidation of one entity into another. If theConsolidation Operator property is anything other than Ignore, the results areincorrect. See Aggregation (Consolidation Operator).

To define Entity properties, see Adding or Editing Members.

Note:

You define Entity properties in the same way as other dimensions. However,for Entity names, you cannot include a combination of the period (.) andsquare bracket ( [ ) characters.This combination of characters is reserved bythe system to denote a parent entity. For example:

EN_CONS4040.[CONS4040]EN_4040_TI.[CONS4050]

You can use either the period (.) or square bracket ( ]) individually, but notcombined consecutively in an Entity member name.

Intercompany Property for EntitiesFor Entity members, you specify if the member stores Intercompany detail. If you setthe Intercompany property for an Entity member, a member with the same name iscreated in the Intercompany dimension with the name ICP_<Entity Name>. The aliasfor the Default Alias Table for the new member is automatically set as the alias for theEntity. If an alias is not defined, it is automatically set as the name of the added Entity.

For example, when an entity named UK is marked as Intercompany, a member namedICP_UK is automatically created. If an alias is defined for UK, the same alias isautomatically set to the new Intercompany member ICP_UK. If an alias is not definedfor UK, the alias is automatically set to UK.

If the alias of an Entity member that is marked as Intercompany changes, the alias ofthe associated Intercompany member also must be changed to the new alias.

Chapter 10Defining Entity Members

10-30

If an Entity is marked as Intercompany and later the Intercompany property isremoved, the associated Intercompany member must be removed.

Base CurrencyFor a multicurrency application, specify each entity member’s base currency. Thedefault base currency for entity members is the currency specified when creating theapplication. For example, if U.S. Dollars is the default currency, you may specify Yenas the base currency for the Japan entity and U.S. Dollars for the United States entity.When you use forms that have values for the Japan entity, if the display currency is setto U.S. Dollars, values are converted to U.S. Dollars using the rates in the exchangerate table (assuming Yen is the local currency and U.S. Dollars is the reportingcurrency).

Creating Alternate HierarchiesIn the Entity dimension, you can create alternate hierarchies, where a single entity canhave multiple parents and contribute differently to each parent. The parent memberscan be in different currencies and the translation that happens in the parent currencymember will be different for these entities. To accomplish this, you use partially sharedmembers, where only a part of input data is shared across all instances of the entities.

The following example shows a leaf-level entity that has more than one parent.

In this example:

• Entity E111 is a child of both P11 and P12.

• Input data that is entered for E111 at either P11 or P12 is replicated to the otherentity after Save. You can enter the data at any of P11.E111 and P12.E111members.

• After consolidation, the calculated values at P11.E111 and P12.E111 can bedifferent. For example, suppose the application is a multi-currency application,where the currency of E111 is GBP. P11 currency is USD and P12 currency isEUR. When entering data to E111, data is always entered in the entity currencymember of the Currency dimension. The parent currency member is calculatedand the values for Parent currency for P11.E111 and P12.E111 will be different, asthe exchange rates between GBP and USD, and GBP and EUR can be different.

Chapter 10Creating Alternate Hierarchies

10-31

You can also create an entity hierarchy where a parent level entity has more than oneparent. However, a hierarchy where the parent level has multiple parents that havedifferent children is not supported.

You build an alternate hierarchy by creating partial share Entity members, andselecting "Shared" as the Data Storage member property. See Creating SharedMembers.

You can use shared hierarchies to meet your reporting needs, however, the number ofshared hierarchies affects performance, as they increase the database size andconsolidation times.

As a best practice:

• The top member of alternate hierarchies must have the Consol operator set asIgnore, to avoid duplicate values.

• Shared members must be added after non-shared members in the hierarchy.

• Alternate hierarchies are allowed outside the Closing Balance, but they should rollup to Total Movements.

In the Member Selector, you can view the parent and child relationships. When youselect an entity, the member selector displays it as Parent.Child, for example, NorthAmerica.USA. You can then select the entity you want, or if an entity has multipleparents, you can select each occurrence of the entity under different parents.

When you enter transaction data, you only need to enter data once, either for thePrimary or Shared member.

You can also enter data once in data forms. For example, suppose E111 is a partiallyshared entity that has two parents, E11 and E12. In a data form, if you enter theamount 100 in E11.E111 and save it, 100 is immediately shown in E12.E111. If youchange the amount to 150 in E12.E111 and save it, the same amount is reflected inE11.E111. In data forms, you can select whether to display the members of the Entitydimension as Parent.Child, and whether to display their currencies. See Setting FormDimension Properties.

When you export data, the same data is exported for partially shared entities and thedata is exported in the Parent.Child format. If you import data to one of the partiallyshared entities in a data file, the data is imported to the other one also.

When a journal entry is posted to one of the partially shared entities, the values areposted to all instances of that entity.

Any change that is made to one partially shared entity that results in a change ofcalculation or process management status will be reflected in other instances of theentity. For example, if one instance is consolidated and its status changes to OK, thestatus of the other instances changes to OK. The same rule applies for locking andunlocking of partially shared entities.

Security and valid intersection rules defined for an entity also apply for its partiallyshared instances.

Watch the following video to learn more about alternate hierarchies:

Configuring Alternate Hierarchies for Entities

Chapter 10Creating Alternate Hierarchies

10-32

https://apex.oracle.com/pls/apex/f?p=44785:265:0:::265:P265_CONTENT_ID:20012

Financial Consolidation and Close Data Model OverviewThe Financial Consolidation and Close "data model" starts with applying some basicrules, for example that Opening Balance = Closing Balance Prior Period, account-by-account.

This rule is amended in a balanced manner in several specific instances:

• First period of the year — Retained Earnings Total/ Closing Balance / Prior Periodis carried forward to Retained Earnings Prior / Opening Balance.

As a result, base members of Retained Earnings Total have no Opening Balance.

• Period 2 through 12 / 13 — Net Income (or Owner's Income if OwnershipManagement is enabled) / Closing Balance / Prior Period is carried forward toFCCS_REC_OBFXCTA.

As a result, base members of Net Income (or Owner's Income) have no OpeningBalance.

• All periods — Total Other Comprehensive Income / Closing Balance / Prior Periodis carried forward to FCCS_OR_OBFXCICTA / Opening Balance for Revenue andExpense type accounts.

As a result, base Revenue/Expense members of Total Other ComprehensiveIncome have no Opening Balance (other Asset / Liability / Equity accounts dohave a Closing Balance to Opening Balance carry forward on an account-by-account basis).

So within the total Other Comprehensive Income hierarchy, accounts can be addedusing the appropriate account type setting, based on how you expect the account tobe treated in terms of Closing Balance to Opening Balance carry forward. Revenueand Expense will carry forward to one single account (FCCS_OR_OBFXCICTA), whilethe remaining accounts will carry forward account-by-account. If Asset / Liability /Equity are used, and parent / subtotal accounts are created in the hierarchy to providegroupings (creating a "matrix" of data across the Account/Movement dimensions), thena combination of the Account and the Movement member can provide any variation ofreporting that is required.

Movement members:

• FCCS_TotalOpeningBalance — provides the opening balance (including any priorperiod adjustments posted in the current period)

• FCCS_Mvmts_Total — provides the changes for the current reporting period(including the net effect of the FX calculations)

• FCCS_ClosingBalance — provides the "life-to-date" balances for all accounts thathave their own opening balance

FX Opening and FX Movements are calculated on all accounts (but written to theOBFXCTA / OBFXCICTA for Revenue Expense accounts within the Net Income /Total Comprehensive Income hierarchies). For any account flagged as "historical"(Historical, Historical Rate Override, Historical Amount Override), the FX is calculatedbut is then transferred to the Cumulative Translation Adjustment (CTA) orComprehensive Income Cumulative Translation Adjustment (CICTA) account. Notethat Revenue and Expense accounts within the Net Income / Total ComprehensiveIncome hierarchies are assumed to be Historical accounts, translated at AverageRate, and with any FX variation calculations transferred to CTA/CICTA. These

Chapter 10Financial Consolidation and Close Data Model Overview

10-33

metadata Rate Type entry on these accounts is ignored and can be left as the default"No rate" entry.

These FX calculations can be viewed by displaying the relevant movements:

• FCCS_Mvmts_FX_Opening

• FCCS_Mvmts_FX_Movement

• FCCS_Mvmts_FX_to_CTA

• FCCS_Mvmts_FX_to_CICTA

Closing Balance for all non-historical accounts will be brought to an Ending Ratetranslation by the FX Opening and FX Movements calculations. Closing Balance of allhistorical accounts at a translated currency will be a weighted average of the periodicmovements translated at Average Rate on a period-by-period basis. The FX Openingand FX Movement are calculated on these accounts (to ensure that the B/S stillbalances) but is then transferred to the CTA/CICTA account. The total of the FX-to-CTA/FX-to-CICTA system entries across the entire B/S (that is, viewed at the top B/Saccount) must equal zero.

For reporting, Financial Reporting is a very powerful tool, and with a combination ofAccount and Movement in the rows, any of the data points in the "matrix" of data canbe retrieved as required. The Movement dimension can be hidden from view forpresentation and if necessary, either direct over-typing or the use of "memo" (LabelOnly) accounts can be used to provide alternative descriptions.

Working with MembersYou can add or edit members, assign access rights to members and rearrange thedimension member hierarchy.

For optimal performance, Financial Consolidation and Close Cloud provides limits onthe maximum number of dimension members allowed in each dimension. FinancialConsolidation and Close Cloud will stop you from saving non-compliant metadata witherror messages explaining that you have exceeded the acceptable number ofdimension members.

See these topics:

• Seeded Dimension Members

• Dynamic Members

• Adding or Editing Members

• Deleting Members

• Deleting Parent Members

• Working with Shared Members

• Creating Shared Members

Seeded Dimension MembersEach dimension is seeded with members to allow for flexible application configuration.Seeded members are created with the prefix FCCS, for example,FCCS_IncomeStatement or FCCS_TotalAssets.

Chapter 10Working with Members

10-34

The system also includes built-in calculations. See Built-in Calculations.

Guidelines for Seeded Members

• You cannot remove seeded members.

• You cannot rename seeded members.

• You cannot change the member property.

• You cannot change the built-in member formula.

• You can modify the member alias.

• You can modify the Exchange Rate type on accounts.

Adding Children to Seeded Base Members

Within the Account, Data Source, Movement, and MultiGAAP (if used) dimensions,there are FCCS_seeded members.

• If these members have a Data Storage property of Dynamic, you can add childrento them.

• If the Data Storage property is Store or Never Share, you cannot add children tothem.

See Data Storage Options.

Moving Seeded Members in Dimensions

If you do not want to use all of the seeded members, then you need to create user-specific members where appropriate. If you want to create additional parents forseeded members, you can create alternate hierarchies. You can move seededmembers to the new parent members.

You can reorder seeded members under a parent member. For example, this is thedefault order for FCCS_Operating Income with only seeded members:

If you want to add an Other Operating Income account, you can place it between thetwo seeded members.


10-35

Rearranging Seeded Account Members

Financial Consolidation and Close has a seeded Balance Sheet and IncomeStatement structure consisting of about 60 accounts (both parents and base). It ispossible to change the structure of the seeded hierarchy and add additional parentand base members to suit your requirements.

The following guidelines apply:

• The member names of the seeded accounts cannot be changed, but the aliasescan. An additional alias table can be added for a separate account description.Data can be loaded, viewed and searched (in a member selector) by alias as wellas by member name.

• Multiple alternative hierarchies can be created for differing reporting needs. Thesealternative hierarchies should include all base members in the primary hierarchy,but can otherwise be organized differently.

• Be aware that various system and seeded calculations will be lost if the seededaccount hierarchy is ignored. Many calculations have been incorporated into thesystem that rely on the account structure. As a minimum, the following calculationsrely on, and are applied to the seeded account members:

– Year-end transfer of prior period Retained Earnings Closing Balance toRetained Earnings Prior Opening Balance

– Period end transfer of P&L Closing Balance to FCCS_REC_OBFXCTAOpening Balance

– Period end transfer of Other Comprehensive Income (Revenue / Expense) toFCCS_OR_OBFXCICTA

– Balance the Balance Sheet (can be disabled)

– Foreign Exchange (FX) transfer to Cumulative Translation Adjustment (CTA)or Comprehensive Income Cumulative Translation Adjustment (CICTA)

– Seeded consolidation rules (can be un-deployed / disabled)

Note:

You should ensure that all base accounts are included in the seeded accountstructure, whether that structure is used for reporting or not.

If you know that changing the account structures of dimensions with dynamic calcparents will result in unwanted changes to the historical data, then you should notchange the structures. If however, you want to change the aggregation/calculation toreflect the new hierarchies, then you should unlock the entities, reconsolidate, and re-lock. If you want history to remain as it is, but use new aggregation/calculations forfuture data, then you should create alternative hierarchies to provide for bothvariations, change their rules if necessary (to make them time-specific) andreconsolidate wherever applicable.

Basic Required Balance Sheet Members

If you are creating an Extended Dimension application, during application creation, youcan select the Basic Accounts Reporting option. This option provides a simplified


10-36

hierarchy of the minimum required set of Account and Movement dimension membersbased on the enabled features and a minimum set of seeded forms.

Initial Required Balance Sheet Account Members

Balance Sheet Account Members with Multi-Currency Enabled

If you enable the Multi-Currency option, the system adds these currency relatedhierarchies.

Balance Sheet Accounts with Cumulative Translation Adjustment (CTA) Enabled


10-37

Accounts with Comprehensive Income Cumulative Translation Adjustment(CICTA) Enabled

Balance Sheet Accounts with Ratios Enabled

If you enable the Ratios option, the system adds the Ratio hierarchies and relatedsource accounts depending on which Ratio options are selected.


10-38


10-39

Balance Sheet Accounts with Intercompany Data with Tracking and OwnershipManagement Enabled

If you enable the Intercompany Data with Tracking option, additional options such asOwnership Management are then available. If you enable Ownership Management,the system adds the Ownership Management accounts and adds the CTA/CICTAaccounts if not already added, then adds the Driver accounts.


10-40

Basic Account Reporting - Indirect Cashflow Option

For the Basic Accounts Reporting option, if you enable the Indirect Cashflow option,the system adds the Cash Flow accounts and additional Cash Flow hierarchy.

Initial Required Movement Members


10-41

Note that two base (level 0) movements are created in addition to the OpeningBalance hierarchy. You can add any additional base movements as required.

Movement Members with Multi-Currency Enabled

If you enable the Multi-Currency option, the system adds the foreign exchange relatedmembers.

Movement Members with Intercompany Data with Tracking and OwnershipManagement Enabled

If you enable the Intercompany Data with Tracking option, additional options such asOwnership Management are then available. Enabling Ownership Managementenables the “Opening Balance Ownership Change” system rule which requiresadditional members (FCCS_Mvmts_Acquisitions, FCCS_Mvmts_Disposals). Theenablement of Ownership Management also seeds the standard configurableconsolidation rules which use FCCS_Mvmts_Acquisitions_Input andFCCS_Mvmts_Disposals_Input.


10-42

Movement Members with Indirect Cash Flow Enabled

For the Basic Accounts Reporting option, if you enable the Indirect Cashflow option,the system adds the Indirect Cash Flow hierarchies into the Closing Balancehierarchy.


10-43

Closing Balance Input Hierarchy

The seeded Closing Balance Input hierarchy enables you to load or enter ClosingBalance data and compare it to the derived Closing Balance.

Closing Balance data can be loaded to the FCCS_ClosingBalance_Input member ofthe Movement dimension. The purpose of loading data to this Movement member is toidentify any discrepancy between the aggregation of the Opening Balance plusperiodic movements to the parent Closing Balance member and the required closingbalance amount at entity currency. Closing Balance Input is not translated orconsolidated. This member can, however, be used at a data entry level in a data entryform to compare with the aggregated Closing Balance member, and can also be usedin Configurable Calculation rules to populate a default Movement member with thedifference between the current and required closing balance (for example, <defaultmovement> = Closing Balance Input - Closing Balance + <default movement). ClosingBalance Input can be loaded to either FCCS_Periodic or FCCS_YTD_Input, but willultimately be stored in FCCS_Periodic, from which any calculations should besourced.

FCCS_ClosingBalance_Variance is a parent member. The children ofFCCS_ClosingBalance_Variance are FCCS_ClosingBalance_Input andFCCS_ClosingBalance(Shared).

Note that FCCS_ClosingBalance_Input is not valid to validate the system-calculateddata and source data for Profit and Loss accounts.

CTA and CICTA Accounts

Cumulative Translation Adjustment (CTA )Account

By default, the system allows you to capture Foreign Exchange (FX) information in aseparate CTA account for all of the historical accounts. This CTA member represents


10-44

the total CTA adjustments. Calculation logic is included in the consolidation script forthe re-direction of the FX from the source historical accounts to the CTA account. Withone CTA account, all FX-CTA calculation results are accumulated to the single CTAaccount. The CTA account is part of Owner's Equity on the Balance Sheet for US-GAAP reporting purposes.

Comprehensive Income Cumulative Translation Adjustment (CICTA) Account

You can select to capture CTA adjustments in a single Comprehensive Income CTAaccount (CICTA) as part of the Statement for Comprehensive Income for IFRSreporting purposes. This account aggregates to the balance sheet Other Reservesaccount.

You may want to report historical FX adjustments in a different account and in adifferent section of the financial statements. This could be an account that is presentedas part of the Income Statement, and aggregates to Net Income and then to RetainedEarnings - Current. The seeded FCCS_CICTA account includes an optional CICTARedirection Account setting. By default, if CICTA is the selected method, then the FXcalculation from historical accounts is written to the FCCS_CICTA account. If youselect a different destination account by entering this account in the CICTARedirection Account attribute of FCCS_CICTA, then the destination for the FX toCICTA rule will be the specified account. See Setting Account Attribute Values.

During application creation, both the FCCS_CTA and FCCS_CICTA accounts arecreated. When you enable application features, you must specify which account touse.

Note:

By default, the CTA (Balance Sheet) option is selected. If you change thisoption to Comprehensive Income, you must run consolidation to move thedata to the CICTA account.

See Application Feature Descriptions.

Foreign Exchange (FX) Calculations in Net Income Hierarchy

The seeded Net Income hierarchy in the Account dimension includes a base membernamed FCCS_REC_OBFXCTA, Retained Earnings Current - Opening Balance - FX -CTA. It is a sibling of Net Income and a child of Retained Earnings Current.

This member is populated with the sum of the Opening Balance of the IncomeStatement accounts, and a single FX and single FX-to-CTA entry is made to thisaccount based on a calculation of the values for the total Income Statement.

If you want the Income Statement FX to be transferred to CTA, thenFCCS_REC_OBFXCTA should be set as a Historical account. If not, then it should beset as "No Rate".

Foreign Exchange (FX) Calculations in Other Comprehensive Income Hierarchy

The seeded Other Comprehensive Income hierarchy in the Account dimensionincludes a base member named FCCS_OR_OBFXCICTA, Other ComprehensiveIncome - Opening Balance - FX - CICTA. It is a sibling of Total Other ComprehensiveIncome and a child of Other Reserves.


10-45

This member is populated with the sum of the Opening Balance of the OtherComprehensive Income accounts, and a single FX and single FX-to-CICTA entry ismade to this account based on a calculation of the values for the Total OtherComprehensive Income statement.

If you want the Income Statement FX to be transferred to CICTA, thenFCCS_REC_OBFXCICTA should be set as a Historical account. If not, then it shouldbe set as "No Rate".

Setting Up Cash Flow for Negative Cash Accounts

You may want Cash accounts for negative cash items such as Bank Overdrafts, toreduce cash in the Cash Flow Statement, but include in the Liabilities section of theBalance sheet. To do this, you can modify the accounts in the FCCS_Total Non Cashsection of the seeded Balance Sheet hierarchy.

Watch this video for details about setting up cash flow.

Setting Up Cash Flow for Negative Cash Accounts

Built-in Calculations• Opening Balance

Opening balance is calculated from the prior period's Closing Balance. OpeningBalance of First Period of the year is retrieved from the Last Period of the PriorYear's Closing Balance.

The Opening Balance Adjustment is translated at the same effective rate as theClosing Balance from which the Opening Balance is carried forward. The ClosingBalance for Historical accounts is effectively a weighted average of the ratesapplied to all of the past movements.

The Effective Rate equals the Entity Currency Closing Balance from the priorperiod divided by the Parent Currency Closing Balance from the prior period. Notethat this effective rate must be calculated on an account-by-account basis becausethe ratios will differ.

This translation applies to all Historical accounts and to any Historical RateOverride accounts for which an override rate has not been entered, and to anyHistorical Amount Override accounts for which an override amount has not beenentered.

The method of the translation calculation is based on the method set as theDefault Translation settings for the Flow type (either Flow or Balance). The methodis either Periodic or Year-to-Date. If the default translation method is Periodic, thetranslation calculation applies the Periodic entity currency amount against theeffective rate and writes to the Periodic translated cell. If the default translationmethod is Year-to-Date, the translation applies the Year-to-Date entity currencyamount against the effective rate, then subtracts the Year-to-Date translatedamount of the prior period and writes the result to the Periodic translated cell.

The prior period from which the effective rate is calculated also takes into accountany Opening Balance Carry Forward overrides. If the Opening Balance for thecurrent year Budget scenario is carried forward from the Actual scenario, then theeffective rate is calculated from the Actual scenario.


10-46


The translation of Opening Balance Adjustments based on the calculated effectiverate requires that Entity currency and Parent currency Closing Balance data existsin the prior period. If Entity currency and Parent currency Closing Balance datadoes not exist in the prior period, then the Ending Rate for the prior period is used.If neither Closing Balance data nor Ending Rate data exists, then no translation iscarried out.

For Historical Rate Override or Historical Amount Override accounts, if an overridehas been entered, the override rate is used before reverting to the effective rate,then Ending rate and then no translation.

Due to the cumulative nature of some translation calculations, it is recommendedthat any translation to a Reporting Currency that is neither an entity's Entitycurrency or Parent currency be executed from the first period of the year.

• Opening Balance for Periodic View

For the First period of the year, Opening (translated) = Closing (translated) of Lastperiod of Prior year.

For any subsequent periods, Opening (translated) = Closing (translated) of Priorperiod of current year.

• Opening Balance for YTD View

Opening (translated) = Closing (translated) of Last period of Prior Year.

Total Opening (translated) = Closing (translated) of Last period of Prior Year plusyear-to-date current year Opening Balance Adjustments.

• Opening Balance for Retained Earnings Prior

Opening Balance for Retained Earnings Prior is the Closing Balance of TotalRetained Earnings from the end of the Prior Year for the first period of the year, forthe YTD member of each period of the year, and for the QTD member for the firstquarter.

For all other views and periods in the year, the Opening Balance is pulled from theClosing balance of Retained Earnings Prior of the previous period for periodic andquarter for QTD.

For example, for the Periodic View:

– Opening Balance January = Closing Balance of the last period of the prioryear

– Opening Balance February through December = Closing Balance of the priorperiod of the current year

For Income Statement accounts, the Closing Balance at year-end is transferred tothe Retained Earnings Prior account. This is carried out by carrying forward theClosing Balance of the Retained Earnings (Total) to Retained Earnings Prior.

From period to period other than over the year-end, the Closing Balance is carriedforward to the Opening Balance of the next period. However, the Closing Balanceof the Income Statement parent account is carried forward to the "RetainedEarnings Current - Opening Balance - FX - CTA" (FCCS_REC_OBFXCTA)account.

• Closing Balance

Closing Balance is always an aggregated total where Closing Balance = TotalOpening Balance + Movements Subtotal + FX Variance and CTA Adjustment.

• Movements


10-47

The details of movements are stored in separate members as needed and allmovements are translated based on the global translation default settings ofmethod and rate account.

• FX Variance Calculations

Exchange differences are calculated by calculating the translation of the openingbalance and movement source data at Ending Rate and comparing to the actualtranslated opening balance and movement values.

Note:

Do not perform FX calculations on Net Income Level 0 members.

• Historical Accounts

If an override amount or override rate is entered for a historical account, theoverride entry is applied to the translation. Otherwise, the account is translatedusing the application default method and rate.

• FCCS_Days Sales In Receivables and FCCS_Days Sales In Inventory

The following table shows where data is stored for FCCS_Days Sales InReceivables and FCCS_Days Sales In Inventory. Both of these seededcalculations are calculated at the following POV. Note that the table has the POVof Calculations. The other column shows options for reporting. Intercompany andCustom dimensions must be displayed at the "No" members.

Table 10-11 Seeded Calculations for FCCS_Days Sales In Receivables andFCCS_Days Sales In Inventory

Dimension Calculated POV Optional POV

Scenario All

Year All

Period All

View All

Entity All where data exists

Consolidation Entity Input, EntityConsolidation

Entity Total

Currency Entity Currency, ParentCurrency, ReportingCurrencies

Account FCCS_Days Sales InReceivables

FCCS_Days Sales InInventory

Intercompany No Intercompany

Movement No Movement Total Movement

Data Source No Data Source Total Data Source

Multi-GAAP Local GAAP,FCCS_Adjustments

IFRS (other parentmembers)

Custom No Custom


10-48

Dynamic MembersDynamic member are members with values that are dynamically calculated when thedata is requested. The values are not stored. The most common type of dynamiccalculation is ratio calculation.

To enable a parent member for adding dynamic children:

1. Edit the parent member and select the option Enable for Dynamic Children.

• Optional: Set the member property Number of Possible Dynamic Children(the default is 10). This setting determines the number of placeholders that arecreated for dynamically adding or loading members under the parent. If allplaceholders are used, subsequently added children are added as normalmembers and cannot be used until the database is refreshed.

• Optional: Set the member property Access Granted to Member Creator (thedefault is Inherit).

2. Refresh the database to create the placeholders for dynamic members in thedatabases in which the members are used.

Adding or Editing MembersYou define properties for dimension members using these values.

In addition to the member properties in this list, some dimensions require additionalmember properties.

• For account properties, see Defining Accounts.

• For entity properties, see Defining Entity Members.

• For currencies, see Setting Up Currencies.

• For scenarios, see Setting Up Scenarios.

Table 10-12 Member Properties

Property Value

Name Enter a name that is unique across alldimension members.


Alias Table Optional: Select the alias table to store thealias name.

Alias Optional: Enter an alternate name for themember.

For Entity members only: Base Currency Select the base currency for the Entitymember.


10-49

Table 10-12 (Cont.) Member Properties

Property Value

Data Storage Select a data storage property. The default isNever Share for new custom dimensionmembers (except root members).

• Store• Dynamic Calc• Never Share• Shared• Label Only

Two Pass Calculation Specify whether to recalculate values ofmembers based on values of parent membersor other members. Available for Account andEntity members with Dynamic Calc properties.

Allow Upper-Level Entity Input Specify whether parent Entity input is allowedfor this member.

Plan Type Select the application type for which themember is valid.

Data Type Select a data type:

• Unspecified• Currency• NonCurrency• Percentage• Date• Text• Smart ListsSee Data Types and Exchange Rate Types.

Smart Lists Optional: Select a Smart List to associate withthe member.

Enable for Dynamic Children Enables users to create children for thismember by entering a member name in theruntime prompt for a business rule that hasbeen configured with a dynamic parentmember).

Number of Possible Dynamic Children This option is available if Enable for DynamicChildren is selected. Enter the maximumnumber of dynamically-added members thatusers can create. The default is 10.


10-50

Table 10-12 (Cont.) Member Properties

Property Value

Access Granted to Member Creator This option is available if Enable for DynamicChildren is selected. Determines the accessthat member creators have to dynamicmembers that they create with a runtimeprompt:• Inherit—The member creator will inherit

the closest parent's access to the newly-created member.

• None—The member creator will not beassigned any access to the newly-createdmember. (An administrator can laterassign the member creator access to themembers.)

• Read—The member creator will beassigned Read access to the newly-created member.

• Write—The member creator will beassigned Write access to the newly-created member.

Note:

If anadministratorchanges thesesettings, theyaffect only futuredynamicmembers; theydo notretroactivelyaffect dynamicmembers.

To add or edit members:



3. From the Dimension list, select a dimension.


• To add a child member, select the parent level of the dimension hierarchy towhich to add a member and click Add Child.

• To add a sibling, select the level of the dimension hierarchy to which to add asibling and click Add Sibling.

• To edit a member, select that member from the dimension hierarchy and pressEnter or click Edit.


10-51

5. On Member Properties, set or change member properties described in the tableabove.

If you do not see the new member on the page, click Next.

6. Click Save to save information to the relational database and see changes in thedimension hierarchy.

7. Refresh the database so that edited members are visible to users entering data.

8. After creating a dimension member, you typically complete these tasks:

• Assign access. See Managing Security.

• Specify attributes. See Working with Attributes.

• To ensure that your metadata is valid, you can run the Metadata Validationreport at any time. See Metadata Validation Messages.

Deleting MembersEach data value is identified by a set of dimension member values and an applicationtype. Deleting dimension members or deselecting the application type results in dataloss when refreshing an application.

Caution:

Before starting this procedure, perform a backup. See the Oracle EnterprisePerformance Management System Backup and Recovery Guide.

Before deleting members, understand where in the application they are used (in whichforms, exchange rates, and so on) by using Show Usage.

To prevent a referential integrity problem with journals from occurring in theapplication, Financial Consolidation and Close verifies and prevents the deletion ofany metadata member that is referenced in a journal. See Journal Referential Integrity.

You must delete the entity member throughout the application before deleting it fromDimensions. For example, if the entity member is used in a form, you must delete itfrom the form before deleting it from Dimensions.

To delete members:



3. From the dimension hierarchy, select the entity member to delete.

4. Click Delete.

Deleting a base member also deletes its shared members.

5. Click OK.

6. Update and validate rules and reports.


10-52

Deleting Parent MembersData values are identified by a set of dimension member values and an applicationtype. Deleting dimension members or deselecting the application type results in dataloss when refreshing the application.

Caution:

Before starting this procedure, perform a backup. See the Oracle EnterprisePerformance Management System Backup and Recovery Guide.

To delete a parent member and all its descendants from the dimension hierarchy:



3. From the Dimension list, select the dimension whose member, descendants, orbranch that you want to delete

4. Click Delete.

5. Click OK.

Viewing Member Properties from FormsTo view member properties from forms:

1. On the Home page, click Data and then select a form.

2. In the form, select a row or column member and right-click.

3. Optional: Select Edit to view the member's properties, then click Cancel.

Working with Shared MembersSharing members allow alternate rollup structures within an application. A basemember must exist before you can create a shared member. You can create multipleshared members for the base member. A base member must display before its sharedmembers in position from top to bottom.

Shared members are available for Entity, Account and user-defined Customdimensions. Shared member values can be ignored to avoid double-counting valueswhen you roll up the outline.

Shared members share some property definitions with base members, such asmember name, alias name, base currency, and application types for which membersare valid. Shared members must have unique parent members and different rollupaggregation settings. Custom attributes, custom attribute values, and memberformulas are not allowed for shared members. Renaming base members renames allshared members.

Shared members cannot be moved to another parent member. You must deleteshared members and recreate them under different parent members.


10-53

You cannot share a parent member in Custom dimensions.

Shared members must be at the lowest level (level zero) in the hierarchy and cannothave children. The base member need not be level zero. You can enter data in sharedmembers, and values are stored with base members.

Shared members are displayed similarly to base members in the dimension hierarchyfor member selection in Oracle Smart View for Office.

See Creating Shared Members.

Creating Shared MembersYou create shared members the same way as other members, with these differences:

• The base member cannot be the parent of the shared member.

• You cannot add a shared member as a sibling to the base member.

• You must give the shared member the same name as its base member. It canhave a different description.

• You must select Shared as the Data Storage for the shared member.

Shared members must be added after the non-shared member. For example, in thefollowing Account dimension, Cash and Cash Equivalents are under FCCS_CurrentAssets as a non-shared member, and under FCCS_Total Cash as a shared member.Note that the non-shared member is first in the hierarchy and the shared member issecond.

Note:

You should not create shared members for the FCCS_No Data Sourcemember.


10-54

Setting Up CurrenciesInput Currencies

The Input currencies include the application currency and any currencies enabled forthe application. These currencies are used to assign as valid functional currencies forthe Entity and to enter exchange rates against.

When you create a currency for the application, the system provides a list of standardISO currency codes for selection. By default, the system creates Input currencies suchas USD, EUR, GBP, and so on. You should only enable the currencies that you needfor your application.

When you add a new currency to the Currency dimension, a new member isautomatically created under From Currency. The alias for the Default Alias table forthe new member must be set as the alias for the currency. If an alias is not defined, itmust be set as the name of the added currency.

For example, when a currency named GBP is added to the Currency dimension, anew member called From_GBP is automatically created in the From Currencydimension. If an alias is defined for GBP, the same alias must be set to From_GBPalso. If an alias is not defined for GBP, it must be set as GBP for From_GBP.

If the alias of a Currency member changes, the alias of the associated From Currencymember must also be changed to the new alias.

If a Currency member is removed, the associated From_Currency member must beremoved.

Reporting Currencies

A Reporting currency is the currency in which your company prepares financialstatements. When you create a currency for the application, you can enable it forreporting purposes. You can also disable a currency as a Reporting currency.

The system supports currency conversion from local currencies to one or moreReporting currencies. Converted Reporting currency values are stored and read-onlyfor all users. An application’s default currency is the default Reporting currency.

Only Reporting currencies are available for translation in the application. All Reportingcurrencies have a suffix of _Reporting, for example, USD_Reporting.

See Translation Process.

Each application is limited to 180 currencies, and each currency that is selected as aReporting currency counts as two currencies (Input currency and Reporting currency).

A Reporting currency has two mandatory members:

• Entity Currency—Used for data entry, when you manually enter data or load datainto the application. If your entity's functional currency is USD, and you enter datafor the Entity Currency member, when you want to report using the Reportingcurrency member USD for the entity, you must perform a translation toUSD_Reporting, because there is no data stored in USD_Reporting untiltranslation occurs.

• Parent Currency—Used to store the translated data as related to its parent. It isgenerated after consolidation and is a read-only member.

Chapter 10Setting Up Currencies

10-55

Reporting currency members are dynamic calculation members where the translationoccurs dynamically when the data is retrieved. The values are never stored forReporting currency members. The system only stores the Entity Currency and ParentCurrency values.

Note:

You cannot edit or delete the Entity Currency and Parent Currency members.You can only specify an Alias.

Working with Multiple CurrenciesIf an application supports multiple currencies, you can enable multiple currencies perentity on forms.

If multiple currencies are enabled, users can see values converted from the localcurrency to a reporting currency and can override a cell’s base currency.

Note:

• When the local currency is selected on forms, the default stored and displayedcurrency for cells is the entity’s base currency (which you specify). Users can enterdata values only into local currency members. If the local currency member isselected, all currencies specified for the application are available as input types.

• You can set dimension properties for each currency in the Edit Currency dialogbox. In preferences, users can select different display options, and can selectCurrency Setting to apply the properties set by the administrator.

• Currencies can be converted only to reporting currencies. Users cannot enter datainto cells displayed in reporting currencies. The application’s main currency is bydefault a reporting currency. You can change which currencies are reportingcurrencies.

• Currencies defined for the application are valid currencies for data entry. Validcurrencies for data entry are displayed in a list that users access by clicking theCurrency link during data entry.

• Currency codes associated with input values are stored as numeric values. Thesecodes are calculated in dimension formulas and business rules. The calculatedvalues of these currency codes may translate to currency codes that are incorrector invalid. Where there are children with mixed currencies, review calculatedresults on the upper levels.

• If a parent has multiple children, of whom only one child has an overriddencurrency, the parent inherits the overridden currency code (which is not displayedon forms).

• In certain cases, parent entities display #MISSING when trying to convert to aselected currency. Ensure that a currency rate is entered for each combination oflocal currencies and selected currencies on forms or reports. Currencycombinations must exist for all mixed-currency children entities and parentmembers.


10-56

ScalingYou can specify scaling data values when displayed in certain currencies. Forexample, you can set the scaling for Yen to Thousands, then enter 10,000 as a valuefor the Japan entity on a form with the Local member selected for the Currencydimension. When you select Yen as the currency member for the form, the scaling isapplied and 10 displays as the value for Japan.

Number FormattingYou can determine the initial display of numerical values for non-currency andcurrency data types in forms:

• Thousands separator:

– None: 1000

– Comma: 1,000

– Dot: 1.000

– Space: 1 000

• Decimal separator:

– Dot: 1000.00

– Comma: 1000,00

• Negative number sign:

– Prefixed minus: -1000

– Suffixed minus: 1000-

– Parentheses: (1000)

• Negative number color:

– Black

– Red

Viewing Currency UsageYou can view how an application uses a currency: whether a currency is the default, isused for triangulation currency or by an entity, or has a conversion or exchangerelationship with other currencies.

To see how currencies are used:



3. Select Currencies.

4. Select the currency for which you want information.



10-57

Creating CurrenciesYou can create members in the Currency dimension for each currency needed in yourapplication.

Select from a predefined list or create your own. You can specify:

• The three-letter code

• The symbol

• A description of up to 256 characters

• The scaling factor to use when values are displayed

• The alias table to use to display aliases

• Number formatting, including thousands separator, decimal separator, negativesign, and color

• Whether it is a reporting currency

Note:

The Triangulation currency to use for currency conversion is set from theapplication currency.

To create currencies:



3. Select Currency.

4. Click Add.

5. From Create Currency:

• To add a predefined currency, select Select standard Currencies.

• To create a currency, select Create new currency and specify properties:

– For Code, enter an abbreviation or identifier of up to three characters.

– Optional: For Description, enter a name, such as Japanese yen.

– For Symbol, enter a symbol or select a symbol from the list.

– Optional: For Scale, select how to enter and display the currency. Forexample, 3 yen represents 3000 yen if scaling is set to thousands.

– Optional: For Alias Table, select the alias table to use.

– Optional: For Alias, enter a name for the currency alias.

6. Optional: Select Reporting Currency.

7. Optional: For Thousands Separator, select how to display the thousandsseparator (it must differ from the decimal separator).


10-58

8. Optional: For Decimal Separator, select how to display numbers with decimalvalues (it must differ from the thousands separator).

9. Optional: For Negative Sign, select how to display negative numbers:

• Prefixed minus: -1000.

• Suffixed minus: 1000-

• Parentheses: (1000)

10. Optional: For Negative Color, select the display color.

11. Optional: Select the type of Data Storage.

12. Optional: Select Two Pass Calculation.

13. Optional: Select the Data Type.

14. Optional: Select a Smart List.

15. Click Save.

Editing CurrenciesTo edit currencies:



3. Select Currency.

4. Select the currency to edit.

5. Click Edit.

6. Modify properties:

• To select from the predefined symbols, select one from the Select fromPredefined Symbols drop-down list.

• To change the currency’s symbol, for Symbol, enter or select the symbol.

• For Scale, set how to enter and display the currency.

• For set currency precision (the number of digits to the right of the decimalplace), select a number from 1 to 10 from the Precision drop-down list.

None is the default.

• To specify the currency as a reporting currency, select Reporting Currency.

• For Thousands Separator, select how to display the thousands separator (itmust differ from the decimal separator).

• For Decimal Separator, select how to display numbers with decimal values (itmust differ from the thousands separator).

• For Negative Sign, select how to display negative numbers:

– Prefixed Minus: -1000

– Suffixed Minus: 1000-

– Parentheses: (1000)

– Use Default Setting: Apply the default setting for the currency.


10-59

• For Negative Color, select the display color.

7. Click Save.

Deleting CurrenciesYou cannot delete the default currency.

To delete currencies:



3. For Dimension, select Currencies.

4. For Currency, select the currency to delete.

5. Click Show Usage to determine if the currency is the default currency, atriangulation currency, or associated with an entity. You cannot delete a currencythat meets these criteria.

If you delete a currency defined in the exchange rate table, it is deleted from thetable.

6. Click Close, OK, Delete, and OK.


Setting Up ScenariosEach scenario contains data for accounts and other dimensions of each entity. Afterusers enter data for an entity for a scenario, they can submit or promote the data forthe entity to other users for review and approval.

About ScenariosUse scenarios to:

• Create forecasts.

• Enter data into scenarios.

• Associate scenarios with different time periods or exchange rates.

• Assign user access rights by scenario.

• Report on scenarios.

• Compare and analyze scenarios.

Time PeriodsAssign each scenario a range of years and time periods, and specify the BeginningBalance time period. When users access forms, they can enter into that scenario onlyyears and periods within the range. Years and periods outside of the range display asread-only. You can modify the time range.

Chapter 10Setting Up Scenarios

10-60

Access PermissionsSpecify access permissions to Scenario dimension members for groups or users todetermine who can view or modify data. A user or group can have only one of theseaccess permissions: Read, Write, or None. Access permissions for a user can becombined based on groups to which the user belongs.

Creating ScenariosTo create scenarios:



3. Select Scenarios.

4. Click Add Child.

5. For Scenario, enter a name.

6. Optional: For Description, enter a description.

7. For Start Yr., Start Period, End Yr., and End Period, select the time period toassociate with the scenario.

8. Optional: For Exchange Rate Table, select an exchange rate table to associatewith the scenario.

If an application uses multiple currencies, associate a scenario with an exchangerate table to enable currency conversions.

9. Optional: For Alias, select an alias table to associate with the scenario, and entera description.

10. Optional: Select Include BegBal as Time Period to include the BegBalance timeperiod in this scenario for currency conversion.

11. Optional: Select Enabled for Process Management to include this scenario inapprovals.

12. Click Save.

Editing ScenariosTo modify scenarios:



3. For Dimension, select Scenario.

4. Select the scenario to edit.

5. Click Edit.

6. Optional: For Scenario, enter a name.



10-61



If an application uses multiple currencies, associate a scenario with an exchangerate table to enable currency conversion.

10. Optional: For Alias, select an alias table to associate with the scenario, and enterthe description.

11. Optional: Select Enabled for Process Management to use this scenario inapprovals.

12. Click Save.

Deleting ScenariosWhen you delete scenarios, all references to the scenario are deleted. You cannotdelete scenarios assigned to an axis on a form. You must first remove references toscenarios from forms and assign different scenarios.

To delete scenarios:




4. Select the scenarios to delete. At least one scenario must remain in theapplication.

5. Click Delete.

6. Click OK.


Copying ScenariosOnly scenario properties are copied. Data values and access rights associated withthe original scenario are not copied to the new scenario.

To copy scenarios:




4. Select the scenario to copy.

5. Click Copy Scenario.

6. For Copy to Scenario, enter a name.




10-62


If an application uses multiple currencies, associate a scenario with an exchangerate table to enable currency conversion.

10. Optional: For Alias Table, select an alias table to associate with the scenario,and enter a description.

11. Optional: Select Enabled for Process Management to include this scenario inapprovals.

12. Click Save.

Customizing Application YearsWhen you create an application, you specify a range of years. After the application iscreated, you can increase the number of years used in the application.

Adding Years to the CalendarYou can add years to the application calendar, but you cannot decrease the number ofyears in the application.

To add years to the calendar:



3. Select Years.

4. Click Add Years.

5. For Number of Years to Add, enter the number of years to add to the calendar.

You can add a range of years either onto the end of the last defined year or beforethe first defined year.

6. Click Add Years.

Editing Year InformationYou can add or update the description and alias for a year.

To edit years:



3. Select Years.

4. Click Edit.

5. Enter a description for the year.

6. For Alias Table, select the alias table to use, and then enter an alias name.

7. Click Save.

Chapter 10Customizing Application Years

10-63

Working with AttributesUse attributes to group members using the same criterion. You can assign attributes tosparse dimensions only. You cannot assign attributes to label-only members. Attributedimensions do not have aggregation properties because parents are dynamicallycalculated.

The Account dimension is usually defined as dense, so you cannot assign attributes toit unless it is changed to sparse for all application types. If you change a dimensionfrom sparse to dense, all attributes and attribute values for that dimension areautomatically deleted.

Attributes can have data types of text, date, Boolean, and numeric. When attributesare defined, you can use the Member Selection dialog box to select attribute functions,such as Equal and GreaterOrEqual.

To create and change attributes, attribute values, and aliases:



3. Select a sparse dimension for which to define an attribute, attribute value, or alias.

Only sparse dimensions can contain attributes.

4. Select the top level in the dimension hierarchy, and click Edit.

5. In the Dimension Properties dialog box, click Custom Attributes.

If the dimension is not sparse, Custom Attributes is not available.

6. Select options:

• To create attributes, click Create. Type an attribute name, and select a datatype: Text, Date, Boolean, or Numeric. You cannot modify the data type afterthe attribute is created.

• To modify attributes, click Modify, and update the attribute name.

• To set aliases for attributes, select an attribute and an attribute value, clickAlias. Select an alias table, type an alias name, and click Close.

7. Click Close.

When you click Close, the hierarchy is validated and an error displays if issues aredetected. For example, date attribute values must be entered in the correct format,and numeric and date attribute dimensions must have at least one attribute valuedefined.


Understanding Attribute Data TypesAttribute dimensions can have a data type of text, numeric, Boolean, or date thatenables different functions for grouping, selecting, or calculating data. The attributetype applies only to level 0 members of the attribute dimension.

• Text attributes enable basic attribute member selection and attribute comparisonsin calculations. When you perform such comparisons, characters are compared.

Chapter 10Working with Attributes

10-64

For example, a package type Bottle is less than a package type Can because Bprecedes C in the alphabet.

• Numeric attribute dimensions use numeric values for the names of level 0members. You can include the names (values) of numeric attribute dimensionmembers in calculations. For example, you can use the number of ouncesspecified in an Ounces attribute to calculate profit per ounce for each product. Youcan also associate numeric attributes with ranges of base dimension values, forexample, to analyze product sales by market population groupings.

• Boolean attribute dimensions in a database contain only two members. When aBoolean attribute dimension is added, two attribute values, True and False, arecreated for this attribute dimension by default. A base dimension, such as Accountor Entity, can be associated with only one attribute dimension that has the Booleandata type.

• Date attributes can specify the date format as month-day-year or day-month-year,and sequence information accordingly. You can use date attributes in calculations,for example, comparing dates in a calculation for product sales since a specifieddate. Users can set the date format by selecting an option in Attribute DimensionDate Format in Application Settings preferences.

Deleting AttributesWhen you delete an attribute, all attribute values associated with the attribute are alsodeleted. Attribute values are removed from members to which they had beenassigned, and the attribute is removed from dimensions to which it was assigned.

To delete attributes:



3. Select the sparse dimension for which to delete an attribute, and click Edit.

4. Click Custom Attributes.

5. Select the attribute to delete.

6. Above the Attributes column, click Delete.

7. Click OK.


Working with Attribute ValuesAttribute values provide users with another way of selecting dimensions memberswhen using forms. Data values for attribute values are dynamically calculated but notstored.

Creating Attribute ValuesYou can define attribute values for sparse dimensions, which are typically the Entityand user-defined custom dimensions. After you define an attribute value for adimension, you can assign it to members of that dimension.

Chapter 10Working with Attribute Values

10-65

You can create attribute values in either the Classic Dimension Editor, or theSimplified Dimension Editor.

To create attribute values in the Classic Dimension Editor:



3. Select the sparse dimension for which to create an attribute value.

4. Select the top level in the dimension hierarchy.


6. On the Manage Attributes and Values page, select the attribute for which tospecify a value.

7. Above the Attribute Values column, click Create. If the options are available, youcan click Add Child or Add Sibling.

8. On Create Attribute Value, in Name, enter a name.

9. Click Save.

To create attribute values in the Simplified Dimension Editor:

1. On the Home page, click Application, and then click Overview.

2. Click the Dimensions tab.

3. For Cube, select All.

4. Select a dimension.

5. Click the Edit Dimension Properties tab on the left.

6. Under Custom Attributes at the bottom right, click Create.

7. Enter an attribute name, and click Save.

8. To edit or delete an attribute, click the Actions ellipsis icon next to theattribute.

Assigning Attribute Values to MembersYou can assign attribute values members of a dimension that are defined as sparsefor all application types. Attribute values must be assigned to the same-level sparsedimension members. Otherwise, errors display during refresh.

To assign attribute values to members:



3. Select the sparse dimension for whose member you want to assign an attributevalue.

4. In the Dimension hierarchy, select a member to which to assign an attributevalue.

5. Click Edit.

For members assigned attribute values: Click View to change a member’sattribute value.


10-66

6. Select Attribute Values.

7. Select attribute values to assign to the member.


• To assign the value to the selected member, click Add .

• To remove a value from the selected member, select the value to remove and

click Remove .

• To remove all values from the selected member, click Remove All .

9. Click Save.

Modifying Attribute ValuesTo modify attribute values:



3. Select the sparse dimension for which to modify an attribute value.



6. For Attributes, select the attribute containing the value to modify.

7. For Attribute Values, select the attribute value.

8. Above Attribute Values, click Modify.

9. On Modify Attribute Value, in Name, enter a name.

10. Click Save.

Deleting Attribute ValuesWhen you delete an attribute value, it is removed from custom dimension members towhich it is assigned.

To delete attribute values:



3. Select the sparse dimension containing the attribute for which to delete a value.



6. For Attributes, select the attribute containing attribute values to delete.

7. For Attribute Values, select attribute values to delete.

To select all attribute values for deletion, select Attribute Values.

8. Above the Attribute Values column, click Delete.

9. Click OK.


10-67


Working with User-Defined Attributes (UDAs)You can use user-defined attributes (UDAs) within member formulas and reports.UDAs return lists of members associated with the attribute. For example:

• For a Product dimension with several product members, you can create a UDAcalled New Products and assign this UDA to the new products in the Productdimension hierarchy. Then you can base certain calculations on the New Productsdesignation.

• If you use the @XREF function to look up a data value in another database tocalculate a value from the current database, you can add the HSP_NOLINK UDA tomembers to prevent the @XREF function from being created on all application typesthat are not the source type selected for that member.

UDAs are specific to dimensions. For example, creating a UDA for an Accountmember makes it available for non-shared Account members. Deleting it removes it forall Account members. To make UDAs available for multiple dimensions, create thesame UDA for multiple dimensions. For example, create a UDA named New for theAccount and Entity dimensions to make it available for Account and Entity members.

To select UDAs for members:



3. Select the dimension for whose members to associate the UDA.

4. From the dimension hierarchy, select a member and click Edit.

5. Select UDA.

6. Optional: To create a UDA, click Create.

7. Select UDAs for the member by moving them to Selected UDA and clicking Save:

• Add moves the selected UDAs to the Selected USA panel.

• Remove removes selected UDAs.

• Remove All removes all UDAs.

Creating UDAsTo create UDAs:

1. Navigate to the UDA tab in Dimensions.

2. On UDA, click Create.

3. Enter a name and click Save.

Changing UDAsTo change UDAs:


Chapter 10Working with User-Defined Attributes (UDAs)

10-68

2. On UDA, select a UDA and click Edit.

3. Change the name and click Save.

Deleting UDAsDeleting a UDA removes it for the dimension.

To delete UDAs:


2. Select the UDA and click Delete.

If you delete UDAs, you must update all member formulas, calculation scripts, andreports that reference them.

Working with Member FormulasYou can define member formulas to combine operators, calculation functions,dimension and member names, and numeric constants to perform calculations onmembers. Member formulas can also include:

• Operator type, function, value, member name, UDA, and so on allowed informulas.

• Predefined formula expressions, including Smart List values, that expand into aformula or value upon database refresh.

To define member formulas:



3. Select the dimension for whose member to add or change a formula.

4. Select the member and click Edit.

5. Select the Member Formula tab.

6. Select options for the following fields:

• Cube

Note:

A formula entered for the default cube is applied to all cubes unlessit is overridden by a different formula entered for a specific cube.

To move the formula from the default cube to a specific cube, youcan use Smart View. Find the formula and cut it from the defaultcube and paste it into a specific cube, for example, Consol.

• Data Storage—Select a data storage option. The default is Store.

Note: The Solve Order option is only for aggregate storage plan types and is notavailable.

7. In the text box, define formulas for the member.

Chapter 10Working with Member Formulas

10-69

8. Optional: To check the validity of the member formula, click Verify Syntax.

9. Click Save.

Before you click Save, clicking Reset restores the previous member formulainformation.

Viewing Details of Formula VerificationTo view details of the member formula syntax verification:

1. On Member Formula, click Verify Syntax.

2. If the member formula is not valid, click Show Details.

If the member formula is valid, Show Details is not selectable.

3. Click Save.

Working with Alias TablesRelated Topics

• About Alias Tables

• Creating Alias Tables

• Editing or Renaming Alias Tables

• Deleting Alias Tables

• Clearing Alias Tables

• Copying Alias Tables

About Alias TablesYou can assign alternate names, or aliases, to dimension members. You can createand update alias tables, and set a default alias table for the application.

Multiple alias tables support, for example, these language combinations:

• English, French, German, Spanish, and Italian

• Japanese and English

• Korean and English

• Turkish and English

Note:

You can set alias tables to display members in an application. To specifyAlias Table settings, see Managing Application and System Settings.

Creating Alias TablesTo create alias tables:

Chapter 10Working with Alias Tables

10-70


2. Under Create and Manage click Alias Tables.

3. On the Alias Tables page, click Add.

4. In Add - Alias Table, enter a name.

5. Click OK.

Editing or Renaming Alias TablesTo edit or rename alias tables:


2. Under Create and Manage, click Alias Tables.

3. On the Alias Table page, select the alias table.

4. Click Edit.

5. For Edit - Alias Table, enter a name.

6. Click OK.

Deleting Alias TablesTo delete alias tables:



3. On the Alias Table page, select the alias table that you want to delete.

You cannot delete the default alias table.

4. Click Delete.

5. Click OK.

Clearing Alias TablesYou can clear the contents of alias tables.

To clear alias tables:



3. On the Alias Table page, select the alias table to clear.

Clearing the alias table removes the contents of the table but does not remove thetable.

4. Click Clear Values.

5. Click OK.


10-71

Copying Alias TablesTo copy alias tables:



3. On the Alias Table page, select the alias table to copy.

4. Click Copy.

5. Select the destination alias table.

The destination alias table must exist. Copying does not create tables.

6. Click Copy.


10-72

11Editing Dimensions in the SimplifiedDimension Editor

Related Topics

• About Editing Dimensions in the Simplified Dimension Editor

• Accessing the Simplified Dimension Editor

• Working with the Simplified Dimension Editor Grid

• Editing Dimension Properties in the Simplified Dimension Editor

• Editing Member Properties in the Simplified Dimension Editor

About Editing Dimensions in the Simplified Dimension EditorThe Simplified dimension editor displays dimensions and members in a grid format.With the grid format, dimensions and members are editable on a single page. You canedit member properties directly on the grid and you can perform ad hoc operationssuch as zooming in, zooming out, keep selected, remove selected, and freeze.

Users with the security roles to view and edit dimensions in the Classic dimensioneditor can perform similar actions in the Simplified dimension editor.

The Simplified dimension editor enables you to check for invalid dimension memberproperties and take action to correct the properties. Invalid properties are bordered inred in the dimension editor grid.

For a detailed list of member properties, see Editing Member Properties in theSimplified Dimension Editor.

Related topics:

• Dimensions Overview

• Accessing the Simplified Dimension Editor

• Editing Dimension Properties in the Simplified Dimension Editor

• Editing Member Properties in the Simplified Dimension Editor

11-1

Accessing the Simplified Dimension EditorTo access the Simplified dimension editor:

1. From the Home page, click Application, and then click Overview.

2. Click Dimensions.

3. Click the down arrow to the right of Cube to filter the list of dimensions by cube.

4. Click the name of the dimension that you want to view.

5. Select from the following tabs:

• Edit Dimension Properties—Click to view and edit dimension details. See Editing Dimension Properties in the Simplified Dimension Editor.

• Edit Member Properties—Click to view and edit dimension members. See Editing Member Properties in the Simplified Dimension Editor.

To use the Classic dimension editor (accessed from the Navigator), see ManagingDimensions.

Working with the Simplified Dimension Editor GridRelated Topics

• Switching to Another Dimension

• Customizing the Column Layout

• Viewing Ancestors

• Showing Member Usage in an Application

• Focusing Your Editing

• Finding Members

• Sorting Members

• Moving Members to Another Hierarchy

• Working with Member Formulas

• Copying Member Names from Microsoft Excel

Switching to Another DimensionTo switch to another dimension while viewing the Simplified dimension editor grid:

1. View Edit Member Properties.

See Accessing the Simplified Dimension Editor.

2. Click the down arrow next to the dimension name at the top of the page.

Customizing the Column LayoutEach column in the Simplified dimension editor grid represents a member property(Member Name, Parent Member, Default Data Storage, and so on). The columnsthat initially display on the grid can be different based on which dimension type you are

Chapter 11Accessing the Simplified Dimension Editor

11-2

editing. You can customize the layout of columns in the Simplified dimension editorgrid by hiding, unhiding, or resizing columns. You can also display the complete set ofproperties (all columns) by clearing the Default mode option.

To customize the column layout in the Simplified dimension editor grid:



2. On the dimension grid, right-click any column heading.

A checklist of columns displays. Also displayed are column or grid resizingoptions.

3. Select or clear the check boxes for the columns you want to hide or unhide on thegrid.

Note:

To view all property columns in the grid, clear the Default mode checkbox. Default mode is selected by default, and limits the properties thatare displayed. Clearing this option displays a larger (complete) set ofproperties (as columns).

4. To change the size of the grid or the columns that are displayed on the grid, selector clear the following resizing options:

• Force fit columns—Resizes the columns so that all columns are visible onthe grid without scrolling.

• Synchronous resize—Resets the size of the grid to original settings.

Viewing AncestorsAncestors are all the members above the selected member in the dimensionhierarchy.

To view the ancestors for the selected member in the Simplified dimension editor grid:



2. Select a member on the dimension editor grid.

3. Click Show Ancestors.

Showing Member Usage in an ApplicationBefore performing such operations as deleting members, it's important to understandwhere in the application the members are used (in which forms, approval units,exchange rates, and so on) by using Show Usage.

To view where members are used in an application using the Simplified dimensioneditor:


Chapter 11Working with the Simplified Dimension Editor Grid

11-3


2. Select a member on the dimension editor grid.


Focusing Your EditingUse zoom in, zoom out, keep selected, remove selected, and freeze to focus yourediting while working in the Simplified dimension editor grid.

To perform these operations while viewing the dimension editor grid:



2. To focus your editing on specific members in the grid, select a member, and thenclick one of the following zoom operations:

• Zoom In Next level—Displays all members one level below the selectedmember

• Zoom In All levels—Displays all descendant members below the selectedmember

• Zoom In Bottom level—Displays all descendant members of the selectedmember that have no children

• Zoom Out—Displays the member one level above the selected member

3. To focus your editing on specific rows or columns in the grid, select a row orcolumn, and then choose from the following operations:

• Keep Selected—Displays only the selected row or column on the grid

• Remove Selected—Removes the selected row or column from the grid

• Freeze (Columns only)—Keeps the selected column and all columns to the leftof the selected column stationary so the column or columns cannot bescrolled. Only columns to the right of the frozen column can be scrolled. Forexample, you can freeze the first column that includes the member name sothat you can scroll and edit that member's properties and still see the membername. To unfreeze columns, click Freeze once again.

Finding MembersTo find dimension members in the Simplified dimension editor grid:

1. View Edit Member Properties for a dimension.


2. For Search, select Name, Alias, or Both.

3. Enter the search text (member name, alias, or partial string) for which to search.

4. Click Search Up or Search Down.

Sorting MembersYou can sort members in ascending or descending order, by children or descendants.Sorting members affects the outline.


11-4

To sort members using the Simplified dimension editor:



2. On the dimension grid, select the members whose children or descendants youwant to sort.

3. For Sort, select Children or Descendants.

Sorting by children affects only members in the level immediately below theselected member. Sorting by descendants affects all descendants of the selectedmember.

4. Click Sort Ascending or Sort Descending.

Moving Members to Another HierarchyTo move members to another hierarchy in the Simplified dimension editor:



2. In the Parent Member column of the grid, type a new parent name for the memberyou want to move.

3. Click Save.

Working with Member FormulasYou can define or edit member formulas directly in the Simplified dimension editorgrid, in the formula bar, or in the Member Formula dialog where you can validatemember formulas.

You can define member formulas to combine operators, calculation functions,dimension and member names, and numeric constants to perform calculations onmembers. Member formulas can also include:

• Operator type, function, value, member name, UDA, and so on allowed informulas.

• Predefined formula expressions, including Smart List values, that expand into aformula or value upon database refresh.

Best Practice:

• Use member formulas for Level 0 members only.

• Avoid using member formulas on Custom dimensions, unless required forreporting.

• Avoid using member formulas on the Movement dimension, due to consolidationperformance considerations.

• Two-pass calculations are recommended to be used on the Account dimensiononly.

To define or edit member formulas in the Simplified dimension editor:




11-5

2. In the Default Formula column of the grid, select the member for which you wantto define or edit a formula. Define or edit the formula for the member using one ofthe following options:

• Click the cell once more in the dimension editor grid to enter or edit theformula.

• Click within the formula bar above the dimension editor grid, and then enter oredit the formula.

• Click next to the formula bar, and then enter or edit the formula.

Tip:

To include member names in formulas, keep the focus on the formulacell in the grid. Press Ctrl while clicking the member name you want toinclude in the formula. The member name will display in the formula bar.

3. Optional: To check the validity of a member formula, click next to the formulabar, and then click Validate.

4. Click Save.

Copying Member Names from Microsoft ExcelTo copy and paste member names from Microsoft Excel:

1. In Excel, highlight the member names in one cell or in a range of cells, and pressCtrl+C to copy the data onto the clipboard.

2. Highlight and select the target cell or cells in the Simplified dimension editor, andthen press Ctrl+V.

3. When the Clipboard helper is displayed, press Ctrl+V again. The data is pasted tothe Clipboard helper.

4. Click Paste to paste the data into the Simplified dimension editor.

Editing Dimension Properties in the Simplified DimensionEditor

To access the Edit Dimension Properties tab in the Simplified dimension editor, fromthe Home page, click Application, and then click Overview. Click Dimensions, andthen click the name of the dimension for which you want to view dimension properties.

Table 11-1 Dimension Properties

Property Value

Dimension Enter a name that is unique across alldimensions.


Chapter 11Editing Dimension Properties in the Simplified Dimension Editor

11-6


Property Value

Alias Table and Alias Optional: Select an alias table. Enter analternate name for the dimension.

See Working with Alias Tables.

Cube Select the cubes for which the dimension isenabled. Clearing this option disables allmembers of the dimension for the deselectedcube.

Two Pass Calculation Recalculate values of members based onvalues of parent members or other members.Available for Account and Entity members withDynamic Calc properties.

Apply Security Allow security to be set on the dimensionmembers; must be selected before assigningaccess rights to dimension members.Otherwise, dimensions have no security andusers can access members without restriction.

Data Storage Select a data storage option. The default isNever Share.

• Store—Stores data values of members.• Dynamic Calc—Calculates data values of

members, and disregards the values.• Never Share—Prohibits members in the

same dimension from sharing datavalues.

• Label Only—Has no data associated withthe member.

• Shared—Allows members in the samedimension to share data values.

See Data Storage Options.

Display Option Set application default display options for theMember Selection dialog box. SelectMember Name or Alias to display membersor aliases. Member Name:Alias displaysmembers on the left and aliases on the right.Alias:Member Name displays aliases on theleft and members on the right.

Chapter 11Editing Dimension Properties in the Simplified Dimension Editor

11-7


Property Value

Hierarchy Type Available for dimensions bound to anaggregate storage cube. Aggregate storagedimensions are automatically enabled tosupport multiple hierarchies. The firsthierarchy in a multiple hierarchy dimensionmust be Stored.

Note:

For memberswith a Storedhierarchy type,the only validcubeaggregationoptions areAddition orIgnore. In astored hierarchy,the first membermust be set toAddition. Formembers with aDynamichierarchy type,all cubeaggregationoptions are valid.Stored hierarchymembers thatare not childrenof Label Onlymembers musthave Additionset as theconsolidationoperator.Children ofLabel Onlymembers can beset to Ignore.

Custom Attributes Click to Create or Synchronize customattributes for a dimension.

Editing Member Properties in the Simplified DimensionEditor

To access the Edit Member Properties tab in the Simplified dimension editor:

Chapter 11Editing Member Properties in the Simplified Dimension Editor

11-8


2. Click Dimensions, and then click the name of the dimension for which you want toview member properties.

3. Click Edit Member Properties.

4. To edit member properties in the Simplified dimension editor grid, click within agrid cell to edit text or to view a drop-down menu from which you can choosemember properties. You can also drag and drop member property values over torows and columns to fill in properties that are the same.

See Working with the Simplified Dimension Editor Grid.

Note:

Each column in the Simplified dimension editor grid represents a memberproperty. The list of properties (columns) that initially displays on the grid canbe different based on which dimension type you are editing. You cancustomize the layout of columns by hiding, unhiding, or resizing columns.You can also display the complete set of properties (all columns) by clearingthe Default mode option. To customize the column layout in the Simplifieddimension editor grid, see Customizing the Column Layout.

The following tables list the default dimension member properties.

For more information on member properties, see Working with Dimensions.

Table 11-2 Account Member Properties

Property Valid Values Default Value

Account Type Expense, Revenue, Asset,Liability, Equity, SavedAssumption

Expense

Variance Reporting Expense, Non-Expense Non Expense


11-9

Table 11-2 (Cont.) Account Member Properties


Exchange Rate Type No Rate, Average, Ending,Historical, Historical RateOverride, Historical AmountOverride

N

o

t

e

:

AverageandEndingareconsideredasNoRat

No Rate


11-10

Table 11-2 (Cont.) Account Member Properties


e.

Consol Consol op Addition, Subtraction,Multiplication, Division,Percent, Ignore, Never

Addition

Rates Consol op Addition, Subtraction,Multiplication, Division,Percent, Ignore, Never

Addition

Consol Data Storage Parent Member: DynamicCalc, Label Only

Child Member: Never Share,Dynamic Calc, Label Only,Shared

Parent Member: Dynamic Calc

Child Member: Never Share

Default Data Storage Parent Member: DynamicCalc, Label Only

Child Member: Never Share,Dynamic Calc, Label Only,Shared



Rate Data Storage Parent Member: DynamicCalc, Label Only

Child Member: Never Share,Dynamic Calc, Label Only,Dhared



Two Pass Calculation No, Yes No

Smart Lists None None

Data Type Currency, Non Currency,Unspecified, Percentage,Smart List, Date, Text

Currency

Time Balance Flow, Balance Flow

CICTA Redirection Account None None

Is CICTA Account None None

Intercompany Account None None

Plug Account None None

Is Plug Account None None

Alias Table Default Default

Enable for Dynamic Children No No

Number of Possible DynamicChildren

10 10

Access Granted to MemberCreator

Inherit Inherit


11-11

Table 11-3 Consolidation Member Properties



Inherit Inherit


Consol Data Storage Parent Member: DynamicCalc, Label Only

Child Member: Store


Child Member: Store

Default Data Storage Parent Member: DynamicCalc, Label Only

Child Member: Store


Child Member: Store

Rates Data Storage Parent Member: DynamicCalc, Label Only

Child Member: Store


Child Member: Store

Two Pass Calculation No No

Consol Consol op Addition, Never Addition

Rate Consol op Addition, Never Addition

Data Type Unspecified Unspecified




10 10


Inherit Inherit

Table 11-4 Currency Member Properties



Default Data Storage Store, Dynamic Calc, NeverShare, Label Only

Store




Symbol Predefined List None

Scale Predefined List 1

Precision Predefined List None

Reporting Currency No, Yes No

Thousands Separator Predefined List None

Decimal Predefined List Period

Negative Sign Predefined List Prefixed Minus

Negative Color Black, Red Black


11-12

Table 11-5 Custom Member Properties



Consol Data Storage Never Share, Shared,Dynamic Calc

Never Share

Default Data Storage Never Share, Shared,Dynamic Calc

Never Share

Rates Data Storage Never Share, Shared,Dynamic Calc

Never Share



Addition





10 10


Inherit Inherit

Table 11-6 DataSource Member Properties



Consol Data Storage Parent Member: DynamicCalc, Shared, Label

Child Member: Shared, Store,Dynamic Calc


Child Member: Store

Default Data Storage Parent Member: DynamicCalc, Shared, Label



Child Member: Store

Rates Data Storage Parent Member: DynamicCalc, Shared, Label



Child Member: Store



Addition





10 10


11-13

Table 11-6 (Cont.) DataSource Member Properties



Inherit Inherit

Table 11-7 Entity Member Properties


Base Currency Currencies in the Rates Cube(cannot be set to None)

Currencies in the Rates Cube(cannot be set to None)

Consol Data Storage Never Share, Share Never Share

Default Data Storage Never Share, Share Never Share

Rates Data Storage Never Share, Share Never Share


Consol Consol op Ignore Ignore

Rates Consol op Ignore Ignore


Unspecified


Intercompany (AttributeDimension)

Parent Member: None, Yes

Child Member: None

Parent Member: None

Child Member: None



10 10


Inherit Inherit

Table 11-8 Intercompany Member Properties



Consol Data Storage Never Share Never Share

Default Data Storage Never Share Never Share

Rates Data Storage Never Share Never Share


Consol Consol op Addition Addition





10 10


11-14

Table 11-8 (Cont.) Intercompany Member Properties



Inherit Inherit

Table 11-9 Movement Member Properties

Property Default Value Valid Values


Consol Data Storage Parent Member: Never Share,Dynamic Calc, Shared, LabelOnly

Child Member: Never Share,Shared, Label Only



Default Data Storage Parent Member: Never Share,Dynamic Calc, Shared, LabelOnly

Child Member: Never Share,Shared, Label Only



Two Pass Calculation No No, Yes

Consol Consol op Addition Addition, Subtraction,Multiplication, Division,Percent, Ignore, Never





10 10


Inherit Inherit

Table 11-10 Period Member Properties



Consol Data Storage Parent Member: DynamicCalc, Shared

Child Member: Store, Shared


Child Member: Store

Default Data Storage Parent Member: DynamicCalc, Shared



Child Member: Store

Rates Data Storage Parent Member: DynamicCalc, Shared



Child Member: Store



11-15

Table 11-10 (Cont.) Period Member Properties



Consol Consol op Addition Addition

Rates Consol op Addition Addition


Enable for ProcessManagement

Parent Member: No

Child Member: Yes

Parent Member: No

Child Member: Yes

Table 11-11 Scenario Member Properties



Start Year All the years in the application First Year

Start Period Select from valid values Select from valid values

End Year All the years in the application Last Year

End Period Select from valid values Select from valid values

Include BegBal as TimePeriod

Yes, No No

Enabled for ProcessManagement

Yes, No Yes

Exchange Rate Table None None

Consol Data Storage Parent Member: DynamicCalc, Shared

Child Member: Never Share,Shared



Default Data Storage Parent Member: DynamicCalc, Shared

Child Member: Never Share,Shared




Two Pass Calculation Parent Member: No, Yes

Child Member: No

Parent Member: No

Child Member: No


Addition

Rates Consol op Addition, Subtraction,Multiplication, Division,Percent, Ignore, Never

Addition


Unspecified




11-16

Table 11-11 (Cont.) Scenario Member Properties



10 10


Inherit Inherit

Table 11-12 View Member Properties



Enable for ProcessManagement

Yes Yes

Consol Data Storage Never Share, Dynamic Calc Never Share



Consol Consol op. Ignore Ignore





10 10


Inherit Inherit

Table 11-13 Year Member Properties

Property Default Value Valid Values


Consol Data Storage Parent Member: DynamicCalc, Store, Shared



Child Member: Store

Default Data Storage Parent Member: DynamicCalc, Store, Shared



Child Member: Store

Rates Data Storage Parent Member: DynamicCalc, Store, Shared



Child Member: Store


Data Type Unspecified Currency, Non Currency,Unspecified, Percentage,Smart List, Date, Text



11-17

Adding Members in the Simplified Dimension EditorTo add members in the Simplified dimension editor:



3. Click the down arrow next to Cube to filter the list of dimensions by cube.

4. Click the name of the dimension that you want to update.


Tip:

To choose a different dimension, click the down arrow next to thedimension name at the top of the page.

6. Add members:

• To add a child member, select the parent level member, and then click AddChild.

• To add a sibling member, select a member, and then click Add Sibling.

• To add an All Years parent member that includes all members of the Yearsdimension, select the Years dimension and then click Add All Years.

The All Years parent member enables users to view the accumulated dataacross multiple years, for example, a project's total cost up to its end date. TheAll Years member does not include the No Year member, if one is defined forthe application.

7. To set or change member properties, click a cell in the Edit Member Propertiesgrid and make updates. See Editing Member Properties in the SimplifiedDimension Editor.

8. To undo the last change you made before saving, click Undo.

9. To undo all changes that were made since the last save, click Refresh.

10. To save your changes, click Save.

11. To apply your changes across the application after a save, click RefreshDatabase.

12. After creating a dimension member, you typically complete these tasks:

• Assign access. Click Actions, and then click Assign Permissions.

• Assign custom attributes.

• To ensure that your metadata is valid, you can run the Metadata Validationreport at any time. See Validating Metadata.

Editing Members in the Simplified Dimension EditorYou can edit members directly in the Simplified dimension editor grid.

To edit members:


11-18




4. Click the name of the dimension that you want to edit.


Tip:


6. Take an action:

• To add members, see Adding Members in the Simplified Dimension Editor.

• To navigate the dimension editor grid and to focus your editing on certainmembers, rows, or columns, see Working with the Simplified Dimension EditorGrid.

• To modify member properties, click within a cell on the dimension editor gridand select an option from the drop-down list. For example, to edit the AccountType for an Account dimension member, click within a cell in the Account Typecolumn. Click the down arrow that appears within the cell, and then select anAccount Type option. For descriptions of member properties, see EditingMember Properties in the Simplified Dimension Editor.

• To delete members, see Deleting Members in the Simplified Dimension Editor.

7. To undo the last change you made before saving, click Undo.

8. To undo all changes that were made since the last save, click Refresh.

9. To save your changes, click Save.

10. To apply your changes across the application after a save, click RefreshDatabase.

Deleting Members in the Simplified Dimension EditorEach data value is identified by a set of dimension member values and a cube.Deleting dimension members or deselecting the cube results in data loss whenrefreshing an application. Deleting entity members deletes all approval units (includingdata) associated with them.

Before deleting members, understand where in the application they are used (in whichforms, approval units, exchange rates, and so on) by using Show Usage. See Showing Member Usage in an Application.

You must delete the entity member throughout the application before deleting it fromdimension. For example, if the entity member is used in a form, you must delete it fromthe form before deleting it from dimensions.

When deleting a large subtree of entities, you can improve performance if you firstexclude approval units for the subtree (by excluding the root member) for all scenariosand versions.


11-19

To delete members:




4. Click the name of the dimension that contains the member you want to delete.


Tip:


6. From the dimension editor grid, select the member to delete.

7. Click Delete Member.

Note:

Deleting a base member also deletes its shared members.

8. In the Delete Member query, click OK.


Adding Shared Members in the Simplified Dimension EditorSharing members allow alternate rollup structures within an application. A basemember must exist before you can create a shared member. You can create multipleshared members for the base member. A base member must display before its sharedmembers in position from top to bottom.

Shared members are available for Entity, Account, and user-defined customdimensions. Shared member values can be ignored to avoid double-counting valueswhen you roll up the outline.

Shared members share some property definitions with base members, such asmember name, alias name, base currency, and cubes for which members are valid.Shared members must have unique parent members and different rollup aggregationsettings. Custom attributes, custom attribute values, and member formulas are notallowed for shared members. Renaming base members renames all shared members.

Shared members cannot be moved to another parent member. You must deleteshared members and recreate them under different parent members. The basemember need not be level zero. You can enter data in shared members, and valuesare stored with base members.

To add shared members in the Simplified dimension editor:




11-20

2. Add shared members:

a. Add a child member with the same name as the base member.

b. For Parent Name of the new member, type a new parent name.

c. For Default Data Storage of the new member, select Shared.

3. Click Save.

Data storage properties for all other cubes will automatically be set to Shared.


11-21

12Managing Jobs

Related Topics

• Jobs Overview

• Viewing Pending Jobs and Recent Activity

• Scheduling Jobs

• Editing and Deleting Jobs

Jobs OverviewJobs are actions, such as exporting data or refreshing the database, which you canstart right away or schedule to run at intervals. The Jobs console enablesadministrators to manage jobs in a central location.

You can manage these types of jobs in the Jobs console:

• Run rules

• Import data

• Import metadata

• Export data

• Export metadata

• Refresh the database

• Run Invalid Intersection Reports

• Restructure a block storage cube (BSO)

• Import journals

• Import journal templates

• Export journals

• Export journal templates

• Non-consolidation jobs such as Task Manager and Supplemental Data jobs

Viewing Pending Jobs and Recent ActivityThe Jobs console lists jobs that are in a pending state under Pending Jobs. Jobs thatare processing, have run and are completed, or have errors are listed under RecentActivity.

12-1

Note:

Jobs are retained in the Jobs console for 90 days.

To view the job listings in the Jobs console:


2. Click Jobs.

3. Perform a task:

• To filter the list of pending jobs and recent activity, click the Filter icon ,select filter options, and then click Apply.

• To search for a job, enter text in the Search field, and then click the Search

icon .

• To view details for jobs, click the name of the job.

• To view details for Task Manager and Supplemental Data jobs:

a. Select the Non-Consolidation Jobs tab on the left.

b. Optional: Filter the Jobs list by Name, Status, Created By (or ModifiedBy), Start Date, or End Date.

Scheduling JobsYou can schedule when to run jobs (now or at a future time) and how often (once,daily, weekly, monthly, and yearly).

To schedule jobs:


2. Click Jobs.

3. Click Schedule Jobs.

4. On the Schedule Job page, General tab, select the type of job:

Chapter 12Scheduling Jobs

12-2

• Rules—Launches a business rule. The Business Rules page lists thebusiness rules that were created for the application.

Import Data—Runs a data import operation.

• Import Metadata—Runs a metadata import operation.

• Export Data—Runs a data export operation.

• Export Metadata—Runs a metadata export operation.

• Refresh Database—Launches the database refresh operation.

• Invalid Intersection Reports—Runs an Invalid Intersection Report.

• Restructure Cube—From Cube, select the cube to restructure. Performs afull restructure of a Block Storage cube (BSO) to eliminate or reducefragmentation. This will also remove empty blocks. It is not applicable for anAggregate Storage cube (ASO). See Restructuring Cubes.

• Import Journal—Runs a journal import operation.

• Import Journal Template—Runs a journal template import operation.

• Export Journal—Runs a journal export operation.

• Export Journal Template—Runs a journal template export operation.

5. Select when to run the job:

• Run Now

• Schedule starting from, and then select the date, time, and time zone.

6. Enter a Name for the job; for example, MyWeeklyCubeRefresh.

In the job listing in the Jobs console, the name that you enter displays along witha system-generated job name; for example, MyWeeklyCubeRefresh: RefreshDatabase.

7. For Recurrence pattern, select how often to run the job:

• Run Once

• Daily

• Weekly

• Monthly

• Yearly

8. Optional: To enter an end date, click the End Date checkbox, and then select thedate and time.

9. Click Next to continue.

10. The Job Details page lists the operations that were saved as a job. Select a job,and click Next.

11. From the Review page, review your selections.

• To continue, click Finish.

• To make changes, click Previous.

• To cancel the job, click Cancel.

Chapter 12Scheduling Jobs

12-3

Editing and Deleting JobsYou can only edit pending jobs, and delete only jobs that are pending or completed.You can delete one job or multiple jobs at once. If a job is in a processing state, youcannot edit or delete it.

To edit or delete a job:


2. Click Jobs.

3. To the right of a pending job, click the Actions icon, , and then select Edit orDelete.

4. To edit a job:

a. On the Edit Job page, make selections for when to run the job and how often,and then click Next.

Note:

You can only edit the schedule of the job. You cannot edit the jobtype or the job name.

b. Review your selections, and then click Finish.

5. To delete one or more jobs at once, select the check box next to the job or jobsthat you want to delete, and then click Delete.

Chapter 12Editing and Deleting Jobs

12-4

13Auditing Tasks and Data

Related Topics

• Configuring Audit Tasks

• Auditing Information Overview

• Viewing Audit Details

• Viewing Task Manager Audit Details

Configuring Audit TasksBy default, audit tracking is always enabled for all task groups. You can configure andchange the audit option for any task group.

To enable task auditing for a task:


2. Click Audit.

3. From the Audit Information page, click Configure.

4. From the Configure page, select a Task Group and click Apply.

Auditing will be started for the selected Task Group.

Auditing Information OverviewYou can use the Audit Information feature to view the tasks performed by users. Youcan filter audited tasks by Task Group (for example, Metadata Administration, Formsor Data), Action (such as Add or Modify), user ID, start time and end time.

You must be a Service Administrator to view and export task audit information.

By default, the system logs these user activities in the task audit:

• Data

• Metadata Administration

• Data Form definition

• Rules

• Journals, including journal actions and open and close period tasks

• User administration

• Security

• Clear Cell Details

• Copy Data and Clear Data details

• Approvals

13-1

• Task Manager history

The Audit Report page displays the following information:

• Task—The task name

• Time—Date and time

• Action—For example, Add or Modify

• Property—Audit properties

• Value

The Task Manager Audit page displays history records for Task Manager relatedobjects. These Task Manager objects are tracked:

• Alert

• Attribute

• Filter (Public only)

• Holiday Rules

• List (Public only), including the list filter condition and column selection

• Organizational Unit

• Schedule

• Setting

• Task

• Task Type

• Team

• Template

Viewing Audit DetailsTo view task audit details:

Chapter 13Viewing Audit Details

13-2


2. Click Audit.

3. Optional: Click the Task Manager Audit tab to view history records for TaskManager related objects. See Viewing Task Manager Audit Details.

4. By default, the Audit Information page displays all tasks. To filter tasks, clickFilter, and select filter criteria:

• Task Group - select one or more, or All. Default is All.

– If you select Metadata Administration, the system displays a list ofsubgroups where you can select sub-tasks for metadata:

* All

* Custom Dimension

* Member

* Year

* Alias

* Period

* View

* Currency

* Consolidation

* Scenario

* Entity

* ICP

* Account

– If you select Data Form, the system displays a list of subgroups whereyou can select sub-tasks for forms:

* All

* Form

* Form Folder

– If you select Data, the Intersection box is displayed, where you can enterthe member intersection. You can enter the full or partial memberintersection and the system can perform a wildcard search based on thecriteria that you specify.

• Action - select one or more, or All.

• User - enter a user ID. You can enter full or partial user ID information and thesystem can perform a wildcard search based on the criteria that you specify.

• Start time - click the calendar to select a start date.

• End time - click the calendar to select an end date.

Chapter 13Viewing Audit Details

13-3

Tip:

You can select Clear to clear your selections and return to the defaultvalues.

5. When you are done selecting filter criteria, click Apply.

The grid displays the top 1,000 records from the audit table that match the filtercriteria. You can scroll to view all the records.

6. Optional: To export the audit information to a Microsoft Excel spreadsheet, clickExport, and follow the download instructions.

When you select the Export option, the system exports all of the records thatmatch the filter criteria to a CSV file.

Best Practice:

The best practice is to manually export and truncate the audit tables. Otherwise,table size can become too large and users cannot log in to the application.Schedule regular archiving and purging of the audit log data, for example, at theend of every quarter. This prevents the audit log data in the system from growingover time. Maintain archived audit log files according to internal documentretention policy.

Viewing Task Manager Audit DetailsTo view Task Manager audit details:

1. On the Home page, click Tools, and then click Audit.

2. Select the Task Manager Audit tab.

3. Optional: To search for an object, enter search criteria in the Search text box.

4. Optional: From the Filter bar, select filter criteria from these categories:

• Object

• Name

• Modified On

• Modified By

• Modification

Note:

To hide the filter bar, click the Filter icon . To clear all filters, clickthe

icon at the right of the filter bar.

5. To display all columns, select View, then Columns, and then select Show All.

Chapter 13Viewing Task Manager Audit Details

13-4

6. To display specific columns, select View, then Columns, and select or deselectthe column names.

7. To reorder columns, select View, and then Reorder Columns, select the columnsand use the Up or Down arrows or drag them to change the order.

8. Optional: To export the audit information to a Microsoft Excel spreadsheet, clickExport, and follow the download instructions.When you select the Export option, the system exports all of the records matchingthe filter criteria to an xlsx file (format for Microsoft Excel versions 2007 and later).

The best practice is to manually export and truncate the audit tables. Otherwise,table size can become too large and users cannot log in to the application.

Note:

• Audit information is maintained for 6 months. If you want to accessaudit information beyond 6 months, download it and maintain a copyof the audit records.

• If data auditing is enabled, users can see what data has changed byselecting Actions, and then Change History.

Chapter 13Viewing Task Manager Audit Details

13-5

14Defining Valid Intersections

Related Topics

• Understanding Valid Intersections

• Creating Valid Intersections

• Managing Valid Intersections

• Suppressing Invalid Data in Forms

• Working with Valid Intersections in Forms

• Managing Invalid Intersection Reports

Understanding Valid IntersectionsValid intersections enable you to define rules, called valid intersection rules, whichfilter certain cell intersections to users when they enter data or select runtime prompts.For example, you can specify that certain programs are valid only for some periods ordepartments.

After valid intersections are defined, cells containing invalid data are read-only. Thisrestriction speeds the consolidation process and optimizes the information available tousers.

To better understand how valid intersections affect behavior in forms and in runtimeprompts, see Working with Valid Intersections in Forms.

To define valid intersections, you must become familiar with these valid intersectionconcepts:

• Valid intersection groups. See Valid Intersection Groups.

• Valid intersection rules. See Valid Intersection Rules.

• Anchor and nonanchor dimensions. See Anchor and Nonanchor Dimensions.

Valid Intersection GroupsValid intersection groups define:

• Dimensions to be included

• One of those dimensions as the anchor dimension

• Whether nonanchor dimensions are required or not

• Whether the anchor dimension members not specified or referenced will be validor invalid

Valid Intersection RulesValid intersection rules:

14-1

• Must use the same dimensions that were defined within their valid intersectiongroup

• Define only valid intersections

• Valid intersection rules within the same valid intersection group that produce anapparent conflict or overlap, are marked valid if either valid intersection rulecondition is met

See Example: Redundant or Overlapping Valid Intersection Rules Within theSame Valid Intersection Group.

• Valid intersection rules in different valid intersection groups that produce anapparent redundancy or overlap, are marked valid if they satisfy the requirementsof all valid intersection groups

Thus, if any valid intersection group marks an intersection invalid, regardless ofother valid intersection groups making it valid, the system will mark the intersectioninvalid. Invalid groups override valid group results.

Note:

If you want to remove valid intersections regardless of what other validintersection groups allows, then this rule must be in a different validintersection group.

See Example: Redundant or Overlapping Valid Intersection Rules Withinthe Same Valid Intersection Group.

Anchor and Nonanchor DimensionsAnchor and nonanchor dimensions:

• Anchor dimensions are always required dimensions in the type that is used in thevalid intersection evaluation.

See Example: Required Dimension.

• Nonanchor dimensions are either required or not required:

– If a nonanchor dimension is required, any type that does not use thatdimension will ignore any valid intersection group where that dimension istagged as required as it evaluates the valid intersections.

– If a nonanchor dimension is not required, any type that does not use thatdimension will still evaluate any valid intersection group that includes thatdimension as not required and evaluate the intersections of any otherdimensions in the valid intersection group in the type.

• Unselected anchor dimension members are valid by default, but you can markthem invalid by clearing the Unselected Members are Valid option. This optionmarks all intersections with anchor dimensions not selected in this rule as invalid.

See Example: Unselected Members are Valid.

Chapter 14Understanding Valid Intersections

14-2

Valid Intersection ExamplesThis section provides valid intersection group and valid intersection rule examples toillustrate a few simple, complex, and edge-case scenarios.

Example: Anchor and Nonanchor DimensionsThe choice of the anchor dimension is critical. Consider the following example, whichproduces a different result based on the anchor dimension definition:

• Valid intersection group 1 defines Entity as the anchor dimension and Product as anonanchor dimension.

• Valid intersection group 2 reverses this definition with Product as the anchordimension and Entity as the nonanchor dimension.

Table 14-1 Example - Anchor Dimension is Entity

Valid Intersection Group Anchor Dimension - Entity Nonanchor Dimension -Product

1 DESC(500-Manufacturing) -Unselected members arevalid

DESC(P_TP1 - ComputerEquipment)

Group 1 means entities that are descendants of Manufacturing are valid only withdescendant products of Computer Equipment. No other products are valid withdescendants of Manufacturing. All other entities besides descendants ofManufacturing are valid with all products, including descendants of ComputerEquipment.

Table 14-2 Example - Anchor Dimension is Product

Valid Intersection Group Anchor Dimension -Product

Nonanchor Dimension -Entity

2 DESC(P_TP1 - ComputerEquipment) - Unselectedmembers are valid

DESC(500-Manufacturing)

Group 2 means products that are descendants of Computer Equipment are only validwith descendant entities of Manufacturing. No other entities are valid with descendantsof Computer Equipment. All other products besides descendants of ComputerEquipment are valid with all entities, including descendants of Manufacturing.

Caution:

The choice of anchor dimension is significant. You will get dramaticallydifferent results if you choose the wrong anchor dimension.


14-3

Example: Required DimensionIn the following example, if a nonanchor dimension is not required, then the systemevaluates all remaining dimension intersections in the valid intersection group for atype that does not contain the nonrequired dimension. This behavior could result in theevaluation of a valid intersection group with only one effective dimension.

Table 14-3 Example - Required and Non-Required Nonanchor Dimensions


1 DESC(500-Manufacturing) -Unselected members are valid

DESC(P_TP1 - ComputerEquipment) - Not required

In Group 1, the product dimension is not required, and unselected entities are valid.Therefore, if the type of the form or business rule, at runtime, does not include theproduct dimension, the system evaluates the entity dimension selections to mark allentities as valid for a type that doesn’t contain the product dimension.

Table 14-4 Example - Required and Non-Required Nonanchor Dimensions


2 DESC(500-Manufacturing) -Unselected members areInvalid

DESC(P_TP1 - ComputerEquipment) - Not required

In Group 2, the product dimension is not required, and unselected entities are invalid.Therefore, if a type does not include the product dimension, the system evaluates theentity dimension selections to mark all entities except descendants of Manufacturingas invalid. Thereafter, any type that doesn’t use the product dimension will only allowdata entry in the descendants of Manufacturing entities.

Caution:

Carefully consider whether a nonanchor dimension is required or not,especially if the result leaves a valid intersection group with only oneeffective dimension. Additionally, selecting the Unselected Members areValid option for anchor dimension members also plays a significant role inthe system behavior for valid intersections. See Example: UnselectedMembers are Valid.

Example: Unselected Members are ValidIn the following example, two intersection groups are valid. In one group, the anchordimension unselected members are invalid (this option is cleared). In the other group,the anchor dimension unselected members are valid (this option is selected).


14-4

Table 14-5 Example - Unselected Members are Valid

Valid Intersection Group Anchor Dimension -Account


1 IDESC(BS - Balance Sheet) -Unselected members areinvalid

000 - No Department

2 IDESC(GP - Gross Profit) -Unselected members are valid

IDESC(403 - Sales)

Because Group 1 defines all unselected members are invalid, the system marksnoninclusive descendants of Balance Sheet invalid. Gross Profit is not an inclusivedescendant of Balance Sheet. So even though Group 2 explicitly states inclusivedescendants of Gross Profit are valid with inclusive descendants Sales entities, theinvalid definition from Group 1 overrides any further valid intersections of the sameanchor dimension member set.

Example: Redundant or Overlapping Valid Intersection Rules Within the SameValid Intersection Group

When valid intersection rules are within the same valid intersection group and produceany redundancy or overlap, the system marks an intersection valid if either of the validintersection rule conditions are met.

Table 14-6 Example - Redundant or Overlapping Valid Intersection RulesWithin the Same Valid Intersection Group

Valid Intersection Rule Anchor Dimension -Account


1 IDESC(GP - Gross Profit) -Unselected members areinvalid

IDESC(403 - Sales)


IDESC(TD - TotalDepartment)

Because Gross Profit is a descendant of Net Income and Sales is a descendant ofTotal Department, inclusive descendants of Gross Profit are valid with any inclusiveDescendant of Total Department. Rule 1 is a subset of Rule 2, so Rule 1 is effectivelya "No operation" rule and is unnecessary. There is no restriction on inclusivedescendants of Gross Profit accounts only being valid for inclusive descendants ofSales Entities.

Example: Redundant or Overlapping Valid Intersection Rules in Different ValidIntersection Groups

When valid intersection rules are in different valid intersection groups and produce anyredundancy or overlap, the system marks an intersection valid only if it satisfies therequirements of all valid intersection groups.

In the following example, there are redundant or overlapping rules in different groups:


14-5

Table 14-7 Example - Redundant or Overlapping Valid Intersection Rules inDifferent Valid Intersection Groups

Valid Intersection Rule Anchor Dimension -Account



IDESC(403 - Sales) -Required

2 IDESC(NI - Net Income) -Unselected members are valid

IDESC(TD - TotalDepartment) - Not required

Because Group 1 is further restrictive for inclusive descendants of Gross Profitaccounts being valid with inclusive descendants of Sales entities, the system enforcesthis group for these intersections. Other, non-Gross Profit accounts can still use allinclusive descendants of Total Department entities, but inclusive descendants ofGross Profit accounts must use inclusive descendants of Sales entities.

Redundancy or Overlap in Valid Intersection RulesValid intersection rules within the same intersection group, which produce anyapparent conflict or overlap, are marked valid if either valid intersection rule conditionis met.

If different valid intersection groups share the same attributes, including the anchordimension, required and nonrequired nonanchor dimensions, and UnselectedMembers are Valid attribute, they will be treated as rules of the same validintersection group.

Shared Members and Valid Intersection RulesShared members are supported in valid intersection rules. If a base member isselected for a valid intersection rule, any shared members are also included in therule. Conversely, if a shared member is selected for a valid intersection rule, the basemember is also included in the rule.

Substitution Variables and Valid Intersection RulesYou can use substitution variables in valid intersection rules. User variables are notsupported. Substitution variables can be set on the server, application, or databaselevel. The same substitution variable can exist on multiple levels; the system uses thefirst one it finds as it searches in this order:

1. Database

2. Application

3. Server

Evaluation OrderEvaluation order for valid intersection groups orders invalid results sets as quickly aspossible, increasing the speed and efficiency of the overall valid intersectionevaluation.


14-6

For example, the system evaluates the first valid intersection group in the list, then thesecond group, and so on. If the system finds an invalid intersection in the secondgroup in the list, it will stop evaluating the rest of the list because, once an intersectionis defined as invalid, it will override other valid intersection rule results.

To change the order in which groups are evaluated, see Changing the ValidIntersection Group Evaluation Order.

Creating Valid IntersectionsTo create a valid intersection:


2. Click Valid Intersections.

3. Create the valid intersection group:

a. Click Create.

b. Enter a name and description for the valid intersection group.

c. To select the anchor dimension, click the Down arrow, next to SelectAnchor Dimension.

d. Optional: By default, the anchor dimension members that are not specified inthe valid intersection rule are marked valid. To clear this option, click the Downarrow, next to the anchor dimension, and then click Unselected membersare valid.

e. To select additional dimension (called nonanchor dimension), click AddDimension.

f. Optional: By default, nonanchor dimensions are not required. To make anonanchor dimension required, click the Down arrow, next to thenonanchor dimension, and click Required.

4. Define the valid intersection rule:

a. Click Add Rule.

b. To select the range of members to include, exclude, or remove in the validintersection, click the Down arrow, next to the new rule:

• Click Edit to open the Select Members page and select members toinclude in the valid intersection rule.

• Click Add Exclusion to define an exclusion in the rule. You can exclude asubset of what is included for that dimension.

• Click Clear to clear the selection.

To delete a rule, click Delete .


The new valid intersection group is added to the end of the valid intersections list.To reorder the rules in the list, see Changing the Valid Intersection GroupEvaluation Order.

Chapter 14Creating Valid Intersections

14-7

Managing Valid IntersectionsRelated Topics

• Viewing Valid Intersections

• Changing the Valid Intersection Group Evaluation Order

• Disabling and Enabling Valid Intersection Groups

• Editing Details for a Valid Intersection Group

• Duplicating Valid Intersection Groups

• Deleting a Valid Intersection Group

Viewing Valid IntersectionsTo view valid intersections:



3. Perform a task:

• Create a valid intersection group. See Creating Valid Intersections.

• Reorder valid intersection groups. See Changing the Valid Intersection GroupEvaluation Order.

• Disable and enable valid intersection groups. See Disabling and EnablingValid Intersection Groups.

• Edit details for a valid intersection such as adding or removing dimensions in avalid intersection group. See Editing Details for a Valid Intersection Group.

• Duplicate an existing valid intersection group so that you can quickly create anew one. See Duplicating Valid Intersection Groups.

• Delete valid intersection groups. See Deleting a Valid Intersection Group.

Changing the Valid Intersection Group Evaluation OrderEvaluation order for valid intersection groups orders invalid results sets as quickly aspossible, increasing the speed and efficiency of the overall invalid intersectionevaluation.

To learn ore about evaluation order, see Evaluation Order.

To change the position of a valid intersection group in a list:



3. To the right of the valid intersection, click the Actions icon, .

4. Select Move Up or Move Down.

Chapter 14Managing Valid Intersections

14-8

Tip:

You can also drag valid intersection groups to move them up and downin the list.

Disabling and Enabling Valid Intersection GroupsValid intersection groups, by default, are enabled at the time of creation. If you do notwant a valid intersection group to be evaluated or used, you can disable it on the ValidIntersections tab. When a valid intersection is disabled, the valid intersection rule forthat group no longer applies when viewing forms or business rules. You can reenablea disabled valid intersection group.

To disable and enable a valid intersection group:



3. In the Enabled column of the valid intersection list, click the check mark next to thevalid intersection group that you are disabling or enabling.

Note:

The check mark is green if the group is enabled.

4. Ensure that any remaining groups that are enabled are still listed in the correctevaluation order in the valid intersections list. If they are not, move them up ordown in the order.

Editing Details for a Valid Intersection GroupTo edit valid intersection group details, you work with dimension members in themember selector. You can also define exclusions in valid intersection rules.

To edit valid intersection group details:



3. Click the name of the valid intersection group that you want to edit.

• To edit dimension details, next to the dimension, click the Down arrow, toselect the members to include, exclude, or remove in the valid intersectionrule:

– Click Edit to open the Select Members page and select members toinclude in the valid intersections rule. You can also type in the members orfunctions.

– Click Add Exclusion to define an exclusion in the rule. You can selectmembers to exclude; for example, you can select or include all children ofYearTotal except children of Q1 by excluding children of Q1.

Chapter 14Managing Valid Intersections

14-9

– Click Clear to clear the selection.

• To delete a dimension from a valid intersection group, next to the dimension,

click the Down arrow, and then click Delete .

• To remove a rule from a valid intersection group, click Delete .

• To add a dimension or rule to a valid intersection group, click Add Rule orAdd Dimension.


Duplicating Valid Intersection GroupsTo speed valid intersection group creation, you can duplicate an existing validintersection and then edit it.

To duplicate a valid intersection group:


2. Click Valid Intersections .

3. Click the Actions icon, to the right of a valid intersection group that you wantto duplicate, and then select Duplicate.

4. Open the valid intersection group and edit it.

5. Reorder the valid intersection groups, if needed. See Changing the ValidIntersection Group Evaluation Order.

Deleting a Valid Intersection GroupAfter a group is deleted, the valid intersection groups are reordered. If there are threevalid intersection groups, and the second one in the order is deleted, the third validintersection group becomes number two.

To delete a valid intersection group:



3. Click the Actions icon, , to the right of a valid intersection group that you wantto remove, and then select Delete.

4. Reorder the remaining valid intersections, if needed. See Changing the ValidIntersection Group Evaluation Order.

To delete a valid intersection rule from a valid intersection group, see Deleting a ValidIntersection Group.

Suppressing Invalid Data in FormsSuppressing invalid data hides rows or columns in forms that contain invalid data. Ifthis option is not selected, the system displays rows or columns that contain cells withdata that are invalid. Cells with invalid data are read-only.

Chapter 14Suppressing Invalid Data in Forms

14-10

To suppress invalid data in forms:

1. On the Home page, click Data.

2. Open the form and then click Layout.

3. Under Grid Properties, select Suppress invalid data - Rows and/or Suppressinvalid data - Columns.

Working with Valid Intersections in FormsUsing valid intersections prevents data entry for invalid intersections as defined in theapplicable valid intersection group. The affected cells in the form display as read-onlyfollowing standard, read-only color coding. If you hover the cursor over an invalidintersection, a tool tip displays indicating that the cell is read-only because it is definedas a invalid intersection.

The valid intersection group applies first to the form point of view and page axis. If thepoint of view intersections are all invalid, then a warning message is displayed, andthe form does not render a data grid until a valid intersection is selected.

If the point of view has valid intersections, then the rows and columns are filtered torestrict data entry at invalid intersections. If the Suppress Invalid Data option for theform is enabled, then the form suppresses invalid rows, columns, or both, asappropriate.

Any rows or columns, which consist of a mix of valid and invalid intersections, displaythose intersections as valid or invalid, as appropriate. Invalid intersections aredisplayed with standard, read-only shading and preclude data entry.

You can reset the point of view to the default, unfiltered list without closing andreopening the form by clearing the selections. You can also clear a selection, thusopening up more selections for other dimensions. You cannot render a form with adimension cleared, because valid members must be selected for each dimension.

In the member selector, invalid members are suppressed due to valid intersectionrules. You can display invalid members in the member selector using the ShowInvalid Members option. Invalid members are displayed but are unavailable forselection.

Note:

Valid intersection groups do not grant access to dimension members. Validintersection groups further restrict the valid intersections of dimensionmembers already granted to a user.

Table 14-8 Form Behavior if Valid Intersections are Applied

Action Behavior

Open a form The form renders with member selections asdefined in the form definition, adhering to theuser’s access rights for dimensions, andapplies valid intersection groups with the mostrecently used as current selections.

Chapter 14Working with Valid Intersections in Forms

14-11

Table 14-8 (Cont.) Form Behavior if Valid Intersections are Applied

Action Behavior

Select members from a point of viewdimension

• Enables you to select a member on thepoint of view

• In the member selector for a point of viewdimension, enables you to select from afiltered list of remaining validintersections, which is based on themembers that were selected for the otherpoint of view dimensions

• Ignores the order in which point of viewdimension members are selectedbecause selecting a member from anydimension included in a valid intersectiongroup dynamically filters the remainingdimension member lists for thosedimensions included in the validintersection group, as appropriate, whenthat dimension is selected

• Provides the option to hide invalidmembers from dimension lists or displaythem as unselectable in the point of view

• Provides the ability to reset the point ofview to the fully unfiltered list withoutclosing and reopening the form byclearing the selections

Note:

Ad hoc forms,both in Web andSmart View, willnot filter page orpoint of viewmembersaccording tovalid intersectiongroups.

Select Go to render a form based on point ofview selections. You can also click the rightarrow in the form point of view.

The form renders as defined based on thevalid point of view intersection.

Enter and save data The form data is entered and saved.

Managing Invalid Intersection ReportsYou can define reports that enable you to identify invalid intersections. You define thescope of the database that you want to scan for invalid intersections that contain data.When the report is run, it displays the results of your last two scans.

To manage Invalid Intersection reports, you must be a Service Administrator.

Chapter 14Managing Invalid Intersection Reports

14-12

See these tasks:

• Creating an Invalid Intersection Report

• Editing an Invalid Intersection Report

• Duplicating an Invalid Intersection Report

• Running an Invalid Intersection Report

• Deleting an Invalid Intersection Report

Creating an Invalid Intersection ReportTo create an Invalid Intersection report:


2. Click Valid Intersections, and then click the Reports tab.

3. Click Create.

4. Enter a name for the report.

5. Enter a report description.

6. From Cube, select Consol or Rates.

7. For Entity, Scenario, and View, click to select members, and then click OK.

8. Optional: To select a member from another dimension, click Add Dimension,select a dimension member, and click OK.

Tip:

To remove an optional dimension, click Delete next to thedimension.


• Save and Run now - to run the report immediately.

• Save and Run later - to save the report as a job to be run at a later time. TheSchedule Job dialog box displays. Select when to run the job and how often,and then click Submit.

Editing an Invalid Intersection ReportYou can edit an Invalid Intersection Report and change the name, description, andreport criteria.

To create an Invalid Intersection report:


2. Click Valid Intersections, and then click the Reports tab..

3. From the list of reports, select a report.

4. Click the Actions icon, and then select Edit.


14-13

5. Optional: Edit the report name or description.

6. Optional: Select different report criteria.

7. To save your changes, click Save and Close.

Duplicating an Invalid Intersection ReportTo create an Invalid Intersection report:


2. Click Valid Intersections, and then click the Reports tab.


4. Click the Actions icon, and then select Duplicate.

5. In the Duplicate dialog box, enter a Name for the new report and then click OK.

Running an Invalid Intersection ReportTo create an Invalid Intersection report:



The Invalid Intersection Reports page displays a list of existing reports.

Tip:

To search for a report, enter search criteria, and then click Search.


4. Click the Actions icon, and then select Run.

Deleting an Invalid Intersection ReportTo create an Invalid Intersection report:




4. Click the Actions icon, and then select Delete.


14-14

15Managing Forms

Forms are grids for entering data. You can create simple forms or composite forms tomeet your needs. Because composite forms consist of simple forms, you must createsimple forms before creating composite forms.

See these topics:

• Form Components

• Form Design Considerations

For information on form security, see Managing Forms Security.

Predefined FormsWhen you create an application, the system provides these forms. By default, theService Administrator and Power User have Modify access to these forms. A User orViewer can launch the form, but cannot modify the layout.

Note:

The forms that are displayed by default may depend on the features that areselected for the application.

If you selected the Basic Balance Sheet option when you created theapplication, all forms under the Balance Sheet, Cash Flow, and IncomeStatement folders are excluded. Other seeded forms are retained.

FCCS_Balance Sheet

Form Name Description

FCCS_Balance Sheet by Consolidation View the Balance Sheet accounts byconsolidation status.

FCCS_Balance Sheet by Movement Detail View the movement of each Balance Sheetaccount.

FCCS_Balance Sheet by Period View the Balance Sheet accounts by period.

FCCS_Balance Sheet Key Balances by View View key balances by View.

FCCS_Balance Sheet Movement Summary View a summary of the movement of BalanceSheet accounts.

FCCS_Cash Flow


View Cash Flow Period by Entity by View.

FCCS_Monthly Cash Flow by Entity View Monthly Cash Flow by Entity.

15-1


FCCS_Quarterly Cash Flow by Entity View Quarterly Cash Flow by Entity.

FCCS_Income Statement


FCCS_Income Dashboard Tile Chart View the Income Statement Dashboardaccounts.

FCCS_Income Statement by Period View the Income Statement accounts byPeriod.

FCCS_Monthly Net Income by Entity View Monthly Net Income by Entity.

FCCS_Monthly Sales by Entity View Monthly Sales by Entity.

FCCS_Quarterly Net Income by Entity View Quarterly Net Income by Entity.

FCCS_Quarterly Sales by Entity View Quarterly Sales by Entity.

User-Defined Forms

Note:

The predefined Rate forms are only provided if the Multi-currency option wasselected during application creation.

Form Name Description Dimension Members

Data Status View calculation and approval status,translate and consolidate data.

Rows = Entity - Hierarchy

Columns = Periods

Scenario - <selectable>

Year- <selectable>

Enter Exchange Rates - SinglePeriod

Enter exchange rates for the singleperiod selected in the Point of View

Rows = Currencies - From Currency,Account - Average Rate, EndingRate

Columns = To Currency


Year - <selectable>

Period

Enter Exchange Rates - Multi Period Enter exchange rates for multipleperiods to a single To Currencyselected in the Point of View.


Columns = Periods


Year - <selectable>

To Currency

Chapter 15Predefined Forms

15-2

Form Name Description Dimension Members

Exchange Rates Manage exchange rates. The form is prepopulated withcurrencies. You enable thecurrencies applicable for theapplication.You also identify which currency touse as the application currency. Bydefault, the currency rate data isentered in relation to the applicationcurrency.

Rows = All enabled currencies forthe application (From Currency).

Columns = Periods (all base periods)


Year - <selectable>

Entity- Global

Currency - To Currency <selectable>

Local Exchange Rates When you create new Local Rateaccounts, this seeded system Rateform automatically includes thenewly defined accounts.


Columns = Periods


Year - <selectable>

To Currency

Override Rates Manage override rates. Some Balance Sheet accounts arespecified as Historical Rate accounts(for example, Common Stocks,Investment in Subs). For HistoricalRate accounts, you can enter eitheran Override rate or Override amountfor the account.Rows = All accounts specified asHistorical Rate accounts

Rows = From Currency

Columns = Periods

Columns = To Currency


Year - <selectable>

Entity- <selectable>

Account - Override Rate

Form ComponentsRelated Topics

• Point of View

• Page Axis

• Rows and Columns

Chapter 15Form Components

15-3

Point of ViewSelect members for the Point of View to determine the context for pages, rows, andcolumns. For example, if the Scenario dimension is set to Budget in the Point of View,all data entered in pages, rows and columns is entered into the Budget scenario. ThePoint of View is set to one member, which a user cannot change, for each Point ofView dimension.

To simplify the form, in the Point of View you can specify only relevant members orinclude user variables.

Page AxisUse the page axis to specify combinations of members that may span dimensions sousers can work with data in smaller, more logical views. Each item on the page axiscan have members selected from one or more dimensions. Users see only membersthat they can access.

You can specify multiple page drop-down lists, and select members using relationshipfunctions or attributes. Switch between member sets by selecting them from the pageaxis.

You display member names or aliases on the page axis. You can specify the numberof members in a page dimension that enables a search drop-down list on the dataentry page, which is useful if the dimensions contain many members.

Rows and ColumnsRows and columns define the grid into which users enter data. For example, you canassign Unit Sales to the row axis and January to the column axis. When users accessforms, they can enter data into the cell where the Unit Sales row intersects with theJanuary column.

By default, forms have one set of rows and columns. You can add rows and columnsto create asymmetrical combinations of members.

Form Design ConsiderationsWhen you create a form, you associate it with a cube type, which determines theform’s valid members. You cannot change the cube type after assigning it.

You can edit form accounts if their source type matches the form’s cube type.

Forms and Access PermissionsBy assigning access to a form, you control which users can change its design (forexample, its layout and instructions) and input data. Users can select only members towhich they have Read or Write access. Users can edit forms only if they have accessto at least one member of each secured dimension. For example, if users have Read-only access to the Europe entity, the rows and columns on forms that include theEurope entity are displayed as Read-only. Users can change data only for members towhich they have Write access.

Chapter 15Form Design Considerations

15-4

Forms and CurrenciesFor a single-currency application, all entities use the currency selected when theapplication was created. For a multicurrency application, the selected Currencymember on forms determines the currency in which values display. When theCurrency member Local is selected for rows or columns, no currency conversionoccurs for those rows or columns, and users can enter data for the entities in theirnative currency. If a currency member other than Local is selected, data values areconverted to the selected currency for that row or columns, and the form is read-only.You can enter data in rows or columns that have Currency or Local as the selectedmember.

Forms and VersionsRows and columns with level 0 members allow data entry. Rows or columns set to aparent member are read-only. The Point of View must also be set to the level 0member to allow data entry.

Forms and AttributesYou can select members by selecting a shared attribute, for example, the Southattribute. Values can be entered and saved into rows and columns that use attributes.

Forms and Shared MembersYou cannot select shared members individually; instead, select them using arelationship function. For example, you could select an alternate functional rollup toinclude all members under that rollup. Values can be entered into rows or columns thatdisplay shared members and are saved to the base members in the database. Sharedmembers display in the same format as base members in forms.

Forms and CalculationsTo optimize calculations, select row members using relationships (such asDescendants or Children) instead of selecting children individually. Calculating totalsfor the parent of individually selected children could take several passes, dependingon the number of hierarchy levels.

Creating Simple FormsCreating simple forms involves these steps:

Chapter 15Creating Simple Forms

15-5

Table 15-1 Simple Form Creation Checklist

Task See This Topic

Set form layout, including:Adding form rows and columns

Assigning dimensions to columns and rows

Selecting dimension members for forms

Setting grid properties for the form

Setting dimension properties

Adding formula rows and columns

Setting display properties for the form

Setting printing options for the form

Adding and updating validation rules in forms

• Setting Form Layout• Setting Form Grid Properties• Setting Form Dimension Properties• Setting Display Properties• Setting Printing Options

Define page axis and Point of View Page Axis and Point of View

Set form precision, context menu associations,and whether to enable dynamic user variables

Setting Form Precision and Other Options

Define access permissions See Assigning Access to Forms and Folders.

Design formula rows and columns Adding Formula Rows and Columns

To create simple forms:



3. Click Actions, and then select Create simple form.

4. On the Properties tab, provide a form name of up to 80 characters, and anoptional description of up to 255 characters.

5. Select the Cube associated with the form.

6. Optional: Provide instructions for working with the form.

7. Click Next to specify the form layout.

You can also create composite forms, which are forms that display several simpleforms simultaneously. See Creating Composite Forms.

Setting Form LayoutWhen you create forms, the Layout tab initially contains one row and one column, andall dimensions are in the Point of View. When creating or editing forms, you can addrows and columns to a form, as necessary.

When setting row and column layout:

• Assign at least one dimension to the row and column axis.

• You cannot select the same dimension for multiple axes. (You can havedimensions on multiple axes if you set user variables in the Point of View).

• Select a dimension from any axis and drag it to the destination axis to move adimension form one axis to another.

• Select display properties.


15-6

To set or update the form layout:



3. Click Actions, and then select Create simple form.

4. On the Properties tab, specify the form properties.

The required fields on the Properties tab must be completed before you can moveto the Layout tab.

5. Click Layout.

6. Optional: Select a dimension, and then drag it to Rows or Columns, or within arow or column.

Note:

Initially, all dimension are in the form Point of View. You can dragdimensions from the Point of View to rows, columns, or to pages. Youcan also drag dimensions from any area in the grid (row column, Point ofView, or page) to any other area.

7. Optional: Select another dimension, and then drag it to Rows or Columns, orwithin a row or column.

8. Select each dimension’s members.

9. Select a row header (such as 1 or 2) to set row properties, or a column header(such as A or B) to set column properties, using the information in this table:

Table 15-2 Segment Properties

Option Description

Apply to all rows Apply settings to all rows; available whenthere are two or more rows. Clear this optionto set different properties for each row.

Apply to all columns Apply settings to all columns; availablewhen there are two or more columns. Clearthis option to set different properties foreach column.

Hide Hides the column or row on the form.

Read-only Creates a read-only row or column, enablingcomparison of old, read-only data with new,editable data

Show separator Creates a bold border before the segment tovisually distinguish it.

Suppress hierarchy Suppresses indentation

Suppress missing data Hides rows or columns without data. Clearto display rows or columns with "#MISSING"in cells when data is missing.


15-7

Table 15-2 (Cont.) Segment Properties

Option Description

Column width • Default: Use the column width definedat the grid level (under GridProperties)

• Small: Display seven decimal places.• Medium: Display 10 decimal places.• Large: Display 13 decimal places.• Size-to-Fit: Force all columns to fit in

the displayed space based on the topdata cell value.

• Custom: Select a custom size todisplay more than 13 decimal places,up to 999 places.

Row height • Default: Use the row height defined atthe grid level (under Grid Properties)

• Medium: Display standard row height.• Size-to-Fit: Force all rows to fit in the

displayed space.• Custom: Select a custom size in pixels

for the row height.

Global Assumptions Form To enable transferring global assumptionsfrom a test to a production environment for asimple form, select Global AssumptionsForm. Then update the form to store globalassumptions such as a tax rate.

10. Optional: Add formula rows or columns.

11. Optional: Add or update data validation rules.

Setting Form Grid PropertiesTo set form grid properties:

1. Open the form, and then click Layout.

2. In Grid Properties, set general row and column properties using the information inthis table:

Table 15-3 Form Grid Properties

Option Description

Suppress missing blocks (Rows only) Improves the performance ofthe Suppress missing data setting whensuppressing many rows, for example, 90%or more. The Suppress missing blockssetting can degrade performance if few orno rows are suppressed. Test forms beforeand after using this setting to determinewhether performance is improved. Also testforms whenever you make significantchanges to your application.


15-8

Table 15-3 (Cont.) Form Grid Properties

Option Description

Suppress missing data Hides rows or columns without data. Clearto display rows or columns with "#MISSING"in cells when data is missing.

Suppress invalid data Hides rows or columns with invalid data.Clear to display rows or columns thatcontain cells with data that is invalid. Cellswith invalid data are read-only.

Default row height • Medium• Size-to-Fit: Force all rows to fit in the

displayed space• Custom: Select a custom size in pixels

for the row height

Default column width • Small: Display seven decimal places• Medium: Display 10 decimal places• Large: Display 13 decimal places• Size-to-Fit: Force all columns to fit in

the displayed space based on the topdata cell value

• Custom: Select a custom size todisplay more than 13 decimal places,up to 999 places

Global Assumptions Form To enable transferring global assumptionsfrom a test to a production environment for asimple form, select Global AssumptionsForm. Then update the form to store globalassumptions such as a tax rate.

Suppress invalid Scenario/Time Periods Hides invalid Scenario/Time Periods.

Suppress Missing also Suppresses Zero When this option is selected along with theSuppress missing data option for forms, allrows or columns containing both #Missingand zeroes are suppressed.

When selected, this setting overrides theruntime suppression selections made forsuppressing missing data or zeroes inOracle Smart View for Office

3. Click Save to save your work and continue, or click Finish to save your work andclose the form.

Setting Form Dimension PropertiesYou can set and edit form dimension display properties, including whether to displaythe member name or alias in the form, hide the row or column, and permit users toview the member formula. These properties apply to row, column, page, and Point ofView dimensions.

To set dimension properties:


2. Click in a Point of View, page, row, or column to set dimension properties.

3. Select Dimension Properties:


15-9

Table 15-4 Form Dimension Properties


Apply to all row dimensions Applies properties to all row dimensions

Apply to all column dimensions Applies properties to all column dimensions

Apply to all page dimensions Applies properties to all page dimensions

Apply to all POV dimensions Applies properties to all Point of Viewdimensions

Member Name Displays the member name

Alias Displays the member alias

Member Formula Displays member formulas

Hide dimension Hides the dimension

Show consolidation operators Displays consolidation operators

Start expanded Available only for dimensions on rows orcolumns, choosing this option initiallydisplays the dimension member listexpanded

Enable custom attributes Available only for dimensions on rows orcolumns; enables custom attributes

Drill on Shared Members For row or column dimensions. Enabledrilling on shared members when the sharedmember is on a parent member for the mainhierarchy.

Show Currency Available for multi-currency applications;displays currencies

Show Qualified Name Displays the members of the Entitydimension as Parent.Child.Select Never, As Needed, or Always.

Selecting this option together with the ShowCurrency option displays the entity memberas Parent.Child (ParentCurrency, ChildCurrency).

This option is retained when the form isused in Oracle Smart View for Office.


Setting Display PropertiesYou can set and edit options for form display, such as hiding forms or displayingmissing values as blank, in the Layout tab.

You can also enable account-level annotations. Users can add annotations toaccounts in forms if they have Write access to the account, entity, scenario, and viewmembers. Account-level annotations can vary by different combinations of Scenario,View, and Entity dimensions.

Notes:

• The Account dimension must be assigned to a row axis.

• Account, Entity, View and Scenario dimensions cannot be assigned to the columnaxis.


15-10

• The Entity dimension can be assigned to the row, page, or Point of View axis.

• View and Scenario dimensions must be assigned to the page or Point of Viewaxis.

To set display properties:


2. Select Display Properties, and then select form options:

Option Description

Make form read-only Use this option to make the form read-only.You cannot set this option for compositeforms.

Hide form For example, hid forms that are part ofcomposite forms or are accessed frommenus or task lists.

Display missing values as blank Leave form cells empty where data does notexist. If this option is not selected, emptycells display the text "#MISSING".

Enable account annotations This option is only available if the Accountdimension is on the row.

Allow multiple currencies per entity If the application supports multiplecurrencies, allow entities to support multiplecurrencies, regardless of base currency.Users can select the currency for displayedcell values in forms.

Enable Mass Allocate Users must have the Mass Allocate role touse this option.

Enable Grid Spread Use this option to enable grid spread.

Enable cell-level document (Default) Enable users to add, edit, and viewdocuments in cells in the form, dependingon access permissions. To prevent usersfrom using documents in a form, clear thisoption.

Message for forms with no data Enter text to display in form rows for querieswithout valid rows. Leave blank to displaythe default text: There are no validrows of data for this form.


Setting Printing OptionsYou can set and edit preferences for printing form information in the Layout tab.

To set printing options:


2. Select Printing Options, and then set preferences for printing form information:


15-11

Table 15-5 Form Printing Options

Option Description

Include supporting detail Include supporting detail as extra rows inPDF files. Specify display format:• Normal Order: Prints supporting detail

in the same order as on the SupportingDetail page, after the member it isassociated with

• Reverse Order: Prints supporting detailin reverse order, before the memberassociated with it. Supporting detail forchildren displays above parents, andthe order of siblings is preserved.

Show comments Display text notes associated with cells

Format data Apply number format settings from the formto the displayed data

Show attribute members If attribute members are selected in theform, display them in PDF files

Apply precision Apply form precision settings (desirednumber of decimal points) to the displayeddata in PDF files

Show currency codes If the form supports multiple currencies,display currency codes in the form and inPDF files. Whether currency codes displaydepends on whether currency codes arepresent on any member in the form.If a currency code is present on anymember contained in the form, currencycodes display in the form regardless of theselection for this check box. If currencycodes are not present on members in theform, they are not displayed.

Show account annotations If account annotations are enabled for theform, select to display account annotationsin PDF files


Including Data Validation Rules in FormsIn the Layout tab, you can add and update validation rules to the grid, column, row, orcell. When rules are processed, they can change the color of cells, provide validationmessages to users during data entry, and can change the promotional path forApproval units. Validation rules are saved with the form.

Before adding data validation rules, it is important to consider the function the rule willperform and to plan the rule scope.

To include data validation rules in forms:


2. Select Validation Rules, and then select an option:


15-12

Note:

The menu options that display are context-sensitive, and depend onwhether rules have already been added, and if you previously selected amenu option. For example, if you right-click a cell that contains a ruleand select Copy Validation Rules, the Paste Validation Rules menuoption is displayed when you right-click another cell.

Table 15-6 Form Validation Rules Options

Option Description

Add/Edit Validation Rules Add or edit existing rules in the conditionbuilder are of the Data Validation RuleBuilder dialog box.

Copy Validation Rules Copy the selected rules to be pasted to anew location.

Paste Validation Rules Paste the previously copied rules to a newlocation.

Validate only for users with access tothis form

If the currently logged-in user does not haveaccess to the form, do not executevalidations associated with the form whenvalidating the Approval unit.

Validate only for pages with existingblocks

When enabled, the system figures out whichpage combinations have potential blocksand runs the validations only for those pagecombinations. There are a few exceptions tothis. If a page combination has any DynamicCalc, Label only, or Store with one childmember, then that page is always loaded.

Validate only for cells and pages the userhas access to

When enabled, validations are run as thecurrently logged-in user and not as theadministrator, which means the user’ssecurity will be applied to the formmembers.

Validate with each possible value foruser variables from approval unitdimensions

When enabled, the form will be validatedmultiple times by replacing the user variablefrom the approval dimension with everypossible value for the user variable. If notenabled, the form will be validated once withthe user variable replaced with all possiblevalues for the user variable. It is not enabledby default.

Validate with current approval unitmembers as values for user variables

When enabled, the user variable for theapproval dimension on the form will bereplaced by the approval unit memberbefore the validations are run. If notenabled, the user variable will be replacedwith all possible values for the user variable.It is not enabled by default.

3. Build and validate the rules.

4. In the form, click Next to continue building the form, and then validate and savethe form.


15-13

Setting Form Precision and Other OptionsIn Other Options, you set data precision, associate context menus with the form, andenable dynamic user variables.

You control data precision by applying minimum and maximum values for differentaccount types. For example, you can truncate and round the decimal portion of longernumbers.

To set form precision and other options:

1. Open the form, and then click Other Options.

2. In Precision, select options to set the number of decimal positions displayed in acell for Currency Values, Non-Currency Values, and Percentage Values.

Specify Minimum values to add zeros to numbers with few decimal places.Specify Maximum values to truncate and round the decimal portion of longernumbers. For example:

Table 15-7 Form Data Precision Examples

Value Minimum Precision Maximum Precision Displayed Value

100 0 Any 100

100 3 Any number greaterthan or equal to 3 orNone

100.000

100.12345 Any number lessthan or equal to 5

None 100.12345

100.12345 7 None 100.1234500

100.12345 Any number lessthan or equal to 3

3 100.123

100.12345 0 0 100

100.12345 2 4 100.1234

100 2 4 100.00

Notes:

• By default, the precision settings that you select here override the precisionset for the currency member. If instead you want the currency member’sprecision setting to apply for the form, select Use Currency memberprecision setting.

• Precision settings affect only the display of values, not their stored values,which are more accurate. For example, if Minimum Precision is set to 2, and ifthe system spreads the value 100 from Q1 into the months January, February,and March, the month cells display 33.33 when they are not selected. Whenthey are selected, they display their more accurate values (for example,33.33333333333333).

3. In Context Menus, associate menus with the form by selecting them fromAvailable Menus and moving them to Selected Menus, using the right and leftarrows.

4. If you select multiple menus, use the Up and Down arrows to set the order inwhich they display.


15-14

5. Select Enable Dynamic User Variables to allow dynamic user variables in theform.

6. Click Save.

Creating Asymmetric Rows and ColumnsAsymmetric rows and columns contain different sets of members selected across thesame dimensions. For example:

Row/Column A: Scenario = Actual, Time Period = Q1

Row/Column B: Scenario = Budget, Time Period = Q2, Q3, Q4

To create asymmetric rows or columns:


2. Click the Dimension Selector to select the dimension to modify.

3. Click the Member Selector to the right of the dimension name, and then modifythe members selected for this dimension.


Adding Formula Rows and ColumnsFormula rows contain formulas that apply to form rows. Formula columns containformulas that apply to form columns. For example, you can create a formula column(column D) that computes the percentage variance between the January sales(column A) and February sales (column B). The formula defined for a formula row orcolumn applies to all row or column dimensions. To define or assign existing formulasto forms, select the appropriate row or column on the Layout tab and then displayformula building options under Segment Properties.

Tip:

Consider adding a formula row between two other rows to create a blankrow. Blank rows are useful, for example, for visually separating subtotals andtotals within a form.

To add formula rows and columns:


2. On the Layout tab, right-click Rows or Columns.

3. Select Add Formula Row or Add Formula Column.

4. Click the new Formula Label that is displayed in the row or column, and thenenter the formula name.

5. Click the row or column number and specify any of the following displayed in theSegment Properties pane to the right:

• Hide hides the row or column

• Show separator displays the row or column separator


15-15

• Display formula on form displays the formula on the form when you click thatoption in the row or column header

6. For each dimension in Formula Data Type in the right pane, select a data type forthe formula result:

• Currency

• Non-Currency

• Percentage

• SmartList

If you select SmartList, select a Smart List from the drop-down list next to thedata type.

• Date

• Text

7. Define the formula to use for the row or column by entering the formula name inthe Formula field, and then clicking Edit.

8. Click Validate to ensure that the formula does not contain any errors.

9. Click OK to save the formula and to close the Formula window.

Defining Simple Form Page and Point of ViewYou can select dimensions and members for the page axis and Point of View. ThePoint of View dimensions and members must be valid for the form type and notassigned to a page, column, or row axis. The Point of View sets the unique dimensionmembers that define intersections of data.

When you set user variables for forms, the variable name displays in the Point of View.

To define page axis and Point of View:


2. Click the Dimension Selector and then drag the dimension to Page to add it tothe form page axis.

3. Click the Member Selector for each page axis dimension and select members.

4. Repeat these steps to assign multiple dimensions to the page axis.

Assigning multiple dimensions to the page axis enables users to selectdimensionality while entering data. Users can select Display Options to specifywhether the system sets the page selection to the most recently used selection.

5. In Dimension Properties, select or clear options for page dimensions.

6. Optional: Click the Dimension Selector and then drag the dimension to the Pointof View to add it to the form Point of View. Repeat this action for each dimensionthat you want to move to the Point of View.

7. In Point of View, click the Member Selector for each dimension and then selectmembers.

8. In Dimension Properties, select or clear options for Point of View dimensions.



15-16

Creating Composite FormsComposite forms display several forms simultaneously. Users can enter data and seeresults aggregated to an upper-level intersection, such as Total Revenue.

To create composite forms:



3. Click Actions, and then select Create composite form.

4. In the Properties tab, enter a form name of up to 80 characters, and an optionaldescription of up to 255 characters.

5. Optional: Select Hide Form to hide the form.

6. Optional: Enter instructions for the form.

7. Set the composite form layout.

8. Set the composite form section properties.

9. Set the composite form Point of View and Page display options.


Setting Composite Form LayoutEach area in the composite form is called a section. Initially, you specify whether todivide the composite form layout into two side-by-side sections, or two sections thatare stacked one above the other. There is also a custom layout option.

To set composite form layout:


2. In Select Layout, select an option:

• Custom Layout to create your own composite form layout.

Note:

The Custom Layout option is selected by default.

• 2-Row Layout to split the composite form into two sections, one on top of theother, divided by a horizontal line

• 2-Column Layout to split the composite form into two side-by-side sectionsdivided by a vertical line

After you select an option, the selected layout is displayed.

3. Add, rearrange, or delete simple forms as desired.

4. Optional: Click the Down arrow in the upper right side of a section to select thefollowing additional layout options for that section:

Chapter 15Creating Composite Forms

15-17

• Split Horizontally to split the section into two sections, one above the other

• Split Vertically to split the section into two side-by-side sections

Note:

When you split a composite form section that contains simple forms,the simple forms remain in the original section. For example, if yousplit a section vertically, the original section is divided into two side-by-side sections. The simple forms from the split section areincluded in the left section, and the right section is empty.

• Delete to remove a section from the composite form

When you delete a section from a composite form, the simple forms includedin that section are also deleted from the composite form, unless they areincluded in other sections of the composite form.

• Add Form to display the Form Selector dialog box, where you can selectadditional forms to add to the layout.

• Group as Tabs to display the forms in that section as tabs

• Ungroup Tabs to clear Group as Tabs.

5. Click Save to save the Composite Form layout.

Tip:

You can edit a simple form from within a composite form. Right-click thesimple form, and then select Form Designer and edit the form.

Adding Simple Forms to a Composite Form LayoutTo add a simple form to a section in a composite form, do one of the following steps:

• Drag a form from the Forms in <Form Folder> pane to the desired section.

• Click in the desired section, select the Down arrow, and select Add Form. In theForm Selector dialog box, select a form and click OK.

• Expand Section Properties and click the Add icon. In the Form selector dialog box,select a form and click OK.

When you are adding simple forms to a composite form, note the following guidelines:

• Composite forms can contain simple forms and ad-hoc forms.

• During runtime, the simple forms selected for the composite form display from leftto right, and then from top to bottom within each composite form section.

• If you select Group as Tabs, the form displays in the order selected.

• You can drag simple forms between sections of a composite form.


15-18

Rearranging Forms in the LayoutTo rearrange the simple forms in the composite form layout, expand SectionProperties, select a form, and click an arrow key. You can:

• Move the form to the top

• Move the form up

• Move the form down

• Move the form to the bottom

Editing Simple Forms from within a Composite FormWhile editing a composite form, you can edit a single form from the Layout tab. Thisoption is not available for ad-hoc forms.

To edit a simple form from a composite form:

1. Within the composite form, click the Layout tab.

2. Right-click a simple form, and then select Form Designer.

3. Edit the simple form.

Deleting Simple Forms from a Composite FormTo delete a simple form from a composite form, do one of these steps:

• Right-click the form and select Delete.

• Select the form in Section Properties and click the Delete icon.

• Uncheck the form in the Form Selector dialog box and click OK.

Setting Composite Form Section PropertiesEach section in a composite form is associated with properties set during creation.You can edit these properties after you create a form.

To set composite form properties:


2. Expand Section Properties.

3. Click in a composite form section and set the properties as desired.


15-19

Table 15-8 Composite Form Section Descriptions

Option Description

Forms Displays the simple forms in the section.The following options are available for eachform selected:• Display forms as tabs• Add form• Remove form• Edit from label• Move to top• Move up• Move down• Move to bottom

Name Section name to be displayed at the top ofthe section in Preview mode and at runtime.Select the Text icon to select a text styleand color for the section name.

Height Section height. Select:• Automatic to have the system set the

height• % (percentage sign) to set section

height to a percentage of the compositeform height

Width Width of the section. Select:• Automatic to have the system set the

width• % (percentage sign) to set section width

to a percentage of the composite formwidth

Forms per Row Select:• Automatic to have the system set the

number• Select a number from 1 to 20.The default is one form per row. If Formsper Column is set to a value other thanAutomatic, then Forms per Row is set toAutomatic.

Note:

If you have grouped the forms astabs, this option is not available.


15-20

Table 15-8 (Cont.) Composite Form Section Descriptions

Option Description

Forms per Column Select:• Automatic to have the system set the

number• Select a number from 1 to 20.The default is one form per column. IfForms per Row is set to a value other thanAutomatic, then Forms per Column is setto Automatic.

Note:

If you have grouped the forms astabs, this option is not available.

Set scope for all common dimensions asglobal

Sets all the common dimensions across allthe sections in the composite form to globaland displays a list of the global dimensionsin Page and Point of View in the GlobalDimensions properties.

Setting Composite Form Point of View and Page DimensionsThe composite form Point of View and page dimensions specify where within acomposite form each Point of View and Page dimension name displays. When youselect a section in a composite form, the right panel displays:

• Global Layout Dimensions, which list the Point of View and Page dimensionsthat display in the composite form heading.

Only dimensions that are common to all simple forms in all sections of thecomposite form and that contain the same members can be designated as Global.

• Common Dimensions, which list the Point of View and Page dimensionscommon to all the simple forms included in the selected composite form section.

You can specify where common dimensions display in composite forms. Commondimension display choices are:

– Local displays the dimension name in the simple form heading.

– Section displays the section name in the section heading.

Only dimensions that are common to al simple forms in a section and thatcontain the same members can be displayed in the section heading.

– Global displays the dimension name in the composite form heading.

Creating Master Composite FormsYou can design composite forms that have one master form and multiple simple forms.When you do so, the selection of members in the master form automatically filters tothe members in the simple forms, and the simple forms show only the details that arerelevant to the members highlighted in the master form.


15-21

For example, assume that a user is looking at a new computer line item in a form andwants to see the cash flow impact from this line item. In this scenario, you coulddesign a composite form that includes the following forms:

• A master form called "New Computers" that contains the following dimensions andmembers:

– Entity: MA

– Scenario: Budget

– Currency: Local

– Year: No Year

– Period: Beginning Balance

– Asset Class: Computers

– Line Items: Base SP1

• A simple form called "Cash Flow Impact"

In the master composite form, the user highlights the row Computers/Base SP1.

The simple form, "Cash Flow Impact", is filtered to show only the data that is relevantfor the members highlighted in the master composite form, "New Computers":Computers, Base SP1, Budget, and MA.

To designate a form as a master composite form:


2. Right-click the form, and then select Tag as Master Composite Form.

Note:

The master composite form applies to the entire composite form. So, fora composite form, there can be only one master form across all itssections.

To filter the data in a simple form (or forms) that is relevant to the data in a mastercomposite form, right-click the master composite form and select Apply Context.

Embedding Charts in Composite FormsAdministrators can design composite forms to display the data in sections as charts.Users can also drill down to the next level by clicking the underlined links or chartareas.

Design suggestions:

• Display the top section as a chart and the bottom section as a grid, so that userscan see the effect of data they enter in the bottom grid (when saved) as a chart onthe top.

• Include the same ad hoc grid twice, one to display as a grid and the other todisplay as a chart. Users can then perform ad hoc operations (such as Zoom In,Pivot To, and Keep Only) on the grid and view the changes in the chart.

• Create dashboards.


15-22

To embed charts in composite forms:

1. Create or edit the composite form, and then click Layout.

2. Click a composite form section, and then right-click on a form.

3. Select Display as Chart.

Display as Chart toggles with Display as Grid, allowing you to switch betweenthem.

4. On Chart Properties, select a chart type:

Table 15-9 Chart Types

Chart Type Description

Bar The length of each bar proportionallyrepresents a value over an independentvariable (for example, time).

Horizontal Bar Similar to the regular bar chart, but turnedon its side so that the dependent variable isdisplayed on the horizontal axis.

Line Displays data points (for example, sales ofvarious product lines) over time, connectedby lines.

Area Similar to the Line chart, but the areabetween the axis and the line is emphasizedwith color.

Pie Each slice of the pie chart proportionallyrepresents a class of data in relation to thewhole.

Scatter Each point represents the distribution ofdata for two variables.

5. Click OK.

6. Optional: To set where the chart displays the values that the chart represents(called the Legend), click Options, then click Legend, select one of the followingoptions and then click OK:

• Right: To display the legend to the right of the chart (default setting)

• Bottom: To display the legend at the bottom of the chart

• Left: To display the legend to the left of the chart

• Top: To display the legend at the top of the chart

7. Optional: To set where the chart labels (that is, the member names or aliases) aredisplayed, on Options, click Label, select one of the following options, and thenclick OK.

• Outside Max: To display the label above bar charts or, for non-bar charts,display the label above the data point for positive values and below the datapoint for negative values. This is the default setting.

• Center: To display the label centered on bar charts or, for non-bar charts,display the label above the data point for positive values and below the datapoint for negative values.


15-23

• Inside Max: To display the label on the bar, near the top, or for non-barcharts, display the label above the data point for positive values and below thedata point for negative values.

• Inside Min: To display the label inside on the bar, near the bottom, or for non-bar charts, display the label above the data point for positive values and belowthe data point for negative values.

• Max Edge: To display the label on the bar, or for non-bar charts, display thelabel at the data point.

Working with Forms and Form ComponentsRelated Topics

• Opening Forms

• Previewing Forms

• Editing Forms

• Moving, Deleting, and Renaming Forms

Opening FormsTo open a form for editing:



3. Select the tab for the type of form that you want to open.

4. Click the name of the form.

The form opens in edit mode in a new tab.

To open and view a form:


2. Select the tab for the type of form that you want to open.

3. Click the name of the form.

Previewing FormsWhile you are designing forms, you can preview the dimensions that are assigned tothe Point of View, columns, rows, and page axes. Previewing displays memberattributes, alias, and data associated with forms, although new data cannot beentered.

Previewing completes regular form design validation checks, and checks for properevaluation of any data validation rules included in the form. Data validation rules mustbe properly completed before the form can be saved. In addition, data validation rulesare saved as part of the form. If you do not save changes to a form, any datavalidation rule changes made after the form was last saved are lost.

To preview a form’s design:


Chapter 15Working with Forms and Form Components

15-24


3. With a form open, click Preview.

The form opens in edit mode in a new tab.

4. Resolve any issues reported during the design validation checks, including anyissues with data validation rules.

5. Save the form to ensure that updates are saved, including any changes to datavalidation rules.

Editing Forms• Editing Simple Forms

• Editing Composite Forms

You can edit the layout, members, and properties of both simple and composite forms.For example, you can add formula rows or columns to a simple form, or add forms to acomposite form.

Editing Simple FormsTo edit simple forms:



3. Select the form, then click Edit.

4. Select:

• Properties to edit the form name, description, and instructions.

• Layout to edit form layout.

• Other Options to edit form precision and to change which context menus areassociated with the form.

5. Click Finish to save your work and close the form.

Editing Composite FormsTo edit composite forms:



3. Take one of these actions:

• Select the form, click the Show Usage icon, and then click Edit.

• Select the form, and then click Edit.

Chapter 15Working with Forms and Form Components

15-25

Note:

When editing a composite form, this message may be displayed:"Modifications have been made to one or more included forms; if youwant to save changes to common dimensions, save the composite form".Determine what changes were made to the common dimensions of theincluded simple forms before saving changes to the composite form.

4. Select:

• Properties to edit the composite form name, description or instructions.

• Layout to edit form layout and properties.

5. Click Finish to save your work and close the form.

Moving, Deleting, and Renaming FormsTo move, delete, and rename forms:



3. Select the form.

4. Select a task:

• To move a form, click Move, and then select the destination folder.

Note:

You can move multiple forms simultaneously if they are in the samefolder.

• To delete a form, click Delete.

• To rename a form, click Rename, and then enter the new name.

5. Click OK.

Working with Substitution VariablesRelated Topics

• About Substitution Variables

• Creating and Assigning Values to Substitution Variables

• Deleting Substitution Variables

About Substitution VariablesSubstitution variables act as global placeholders for information that changesregularly. For example, you could set the current month member to the substitution

Chapter 15Working with Substitution Variables

15-26

variable CurMnth so that when the month changes, you do not need to manuallyupdate the month value in the form or the report script.

Creating and Assigning Values to Substitution VariablesTo create and assign values to substitution variables:


2. Under Create and Manage, click Variables.

3. Select the Substitution Variables tab.

4. Click Actions, then select Add.

5. On the Add Substitution Variable page, select the Cube.

6. For Name, enter the name of the substitution variable.

7. For Value, enter a value for the substitution variable.

8. Click OK.

Deleting Substitution VariablesTo delete substitution variables:



3. Select the Substitution Variables tab.

4. Select the substitution variable to delete.

5. Click Actions, then select Delete.

6. Click Yes.

Working with User VariablesRelated Topics

• About User Variables

• Managing User Variables

• Creating User Variables

• Deleting User Variables

About User VariablesUser variables act as filters in forms, enabling users to focus only on certain members,such as a department. Before you can associate a user variable with a form, you mustcreate the user variable.

Managing User VariablesYou can set user variables to limit the number of members displayed on a form,helping users focus on certain members. For example, if you create a user variable

Chapter 15Working with User Variables

15-27

called Division for the Entity dimension, users can select a member for their owndivision. You can create any number of user variables for each dimension, and selectuser variables for any axis in the form.

The typical sequence of steps:

1. If necessary, create the appropriate parent-level members in the dimensionoutline.

2. Define user variables for each dimension that you want users to be able to filter.

3. When designing the form, associate the user variable with the form.

4. Instruct users to select a member for the user variable associated with the form.

Before users can open forms that have user variables, they must select a memberfor User Variable Options in preferences. After selecting an initial value, they canchange it in the form or in preferences.

Creating User VariablesTo create user variables:



3. Select the User Variables tab.

4. Click Actions, then select Add.

5. In the User Variables window, for Dimension Name, select the dimension forwhich to create a user variable.

6. For User Variable Name, enter the name of the user variable.

7. Optional: Select Use Context to allow user variables to be used in the Point ofView. With this setting, the value of the user variable changes dynamically basedon the context of the form.

8. Click OK.

You can now associate the user variable with a form.

Deleting User VariablesTo delete user variables:



3. Select the User Variables tab.

4. Select the user variable to delete.

5. Click Actions, then select Delete.

6. Click Yes.

Chapter 15Working with User Variables

15-28

Working with Smart ListsAdministrators use Smart Lists to create custom drop-down lists that users accessfrom form cells. When clicking in cells whose members are associated with a SmartList (as a member property), users select items from drop-down lists instead ofentering data. Users cannot type in cells that contain Smart Lists. Smart Lists displayin cells as down arrows that expand when users click into the cells.

Perform these tasks to create and administer Smart Lists:

• Define Smart Lists

• Associate Smart Lists with members.

• Select dimensions for which Smart Lists are displayed.

• Optionally:

– Use Smart List values in member formulas.

– Set how #MISSING cells associated with Smart Lists display in forms.

– Synchronize Smart Lists in reporting applications

To create or work with Smart Lists:


2. Under Create and Manage, click Smart List.

3. Perform one action:

• To create a Smart List, click Create, enter the name, and click OK.

• To change a Smart List, select it and click Edit.

• To delete Smart Lists, select them, click Delete and OK. Deleting Smart listsalso deletes any associated mappings with dimension members and reportingapplications.

Data cells can display only one Smart List. If multiple Smart Lists intersect atcells, set which one takes precedence.

• Optional: Click Synchronize to synchronize Smart Lists in reportingapplication. See Synchronizing Smart Lists in Reporting Applications.

Synchronizing Smart Lists in Reporting ApplicationsYou can synchronize Smart Lists to map them to dimensions in reporting applications.

To synchronize Smart Lists in reporting applications:

1. Refresh the application database.

2. Refresh the reporting application mapping.



5. Click Synchronize, then click OK.

Chapter 15Working with Smart Lists

15-29

During synchronization, values from reporting applications in all existing mappingsare appended after the last Smart List item in the appropriate Smart list. If a SmartList is mapped to two dimensions, all members from the first mapping are insertedfirst, and then members from the second mapping are inserted. If a memberalready exists in a Smart List, it is not added again.

6. If Smart List items are mapped to more than one dimension, create a new SmartList with a new name, and then manually transfer related data.

Note:

Smart List names cannot have spaces in them. If you are synchronizingSmart Lists in a reporting application, ensure that any new members do nothave spaces in the name.

Adding or Changing Smart List PropertiesUse the Edit Smart List Properties tab to set Smart List properties

To set Smart List properties:



3. Select a Smart List and click Edit.

4. Define Smart List properties on Properties:

Table 15-10 Smart List Properties


Smart List Enter a unique name containing onlyalphanumeric and underscore characters(for example: Position) and no specialcharacters or spaces. Smart List names canbe referenced in formula expressions.

Label Enter the text to display when the Smart Listis selected. Spaces and special charactersare allowed.

Display Order How Smart Lists are sorted in the drop-down list: by ID, Name, or Label


15-30

Table 15-10 (Cont.) Smart List Properties


#MISSING Drop-Down Label Enter a label (for example, "NoJustification") to be displayed as an entry inthe Smart List whose value is #MISSING.

Notes:• It displays as the first selection in the

Smart List drop-down, allowing#MISSING as a selection in the form.

• When the cell is not in focus, this labeldisplays only if Drop-Down Setting isselected in the next option. Otherwise,#MISSING or a blank cell is displayed,depending on the Display MissingValues As Blank selection for the form.

• #MISSING labels determine only thedisplay of cells with #MISSING data;#MISSING remains the stored value.

#MISSING Form Label Determines how #MISSING values arerepresented in cells associated with SmartLists. Options:

• Drop-Down Setting: Displays the labelset in #MISSING Drop-Down Label.

• Form Setting: Displays #MISSING orleaves cells blank, depending on theDisplay Missing Values As Blankselection for the form. This selectiondetermines what is displayed in the cellwhen it is not the focus. When the cellis in focus, the Smart List item that isselected from the drop-down isdisplayed.

Automatically Generate ID Generate a numeric ID for each Smart Listentry. If you do not select this option, youcan customize Smart List ID values.

5. Click Save.

6. Select Entries.

Use the Entries tab to define selections on Smart Lists.

Adding or Changing Smart List EntriesUse the Edit /Add Smart Lists Entries tab to define the selections in the Smart List.

To define Smart List entries:



3. Select a Smart List and click Edit.

4. On Entries, define drop-down list items:

• For first items only: enter information into the first row.


15-31

• To add an item, click Add and enter the information.

• To delete an item, select it and click Delete.

• To edit an item, change the information in its row:

Table 15-11 Smart List Entries

Entry Property Description

ID Unique number that sets the order for thedisplayed entry. Customizable only ifAutomatically Generate ID is notselected on the Properties tab.

Name Unique alphanumeric name containingalphanumeric and underscore characters(for example: Customer_Feedback) andno special characters or spaces

Label Displayed text for the Smart List entry onthe drop-down list (for example: CustomerFeedback).

Items highlighted in red are duplicates.

5. Perform one action:

• Click Save.

• Select Preview.

Previewing Smart ListsPreview the defined Smart List on the Preview tab. The tab shows the Smart List asdisplayed in a drop-down list or a table.

Displaying #MISSING with Smart ListsAdministrators set values displayed in Smart Lists and data cells, including the displaywhen no data is in the cell. Cells can display no value, #MISSING, or (for cellsassociated with Smart Lists) a specified value.

Use these options to control the display of #MISSING when cells are not in focus:

Option Guideline

Blank When designing forms, select DisplayMissing Values as Blank.

When setting Smart List properties, selectForm Setting.

#MISSING When designing forms, do not select DisplayMissing Values as Blank.

When setting Smart List properties, selectForm Setting.


15-32

Option Guideline

A custom label, such as "No Change" When setting Smart List properties, enter thecustom label in the #MISSING Drop-DownLabel field (for example, No Change). SelectDrop-Down Setting.


15-33

16Managing Journals

Related Topics

• Creating Journal Groups

• Deleting Journal Groups

• Managing Journal Periods

• Setting Journal Options

• Journal Referential Integrity

Creating Journal GroupsAs a Service Administrator, you can create journal groups to classify journals and filterjournal lists.

For information on working with journals, see Working with Financial Consolidationand Close.

You can create journal groups to classify journals by type, and to filter journal lists.You can add or delete groups, edit group descriptions, and load groups during ajournals load.

When you create a journal and specify a journal group, the system validates the groupagainst the list of groups and displays an error message if the group that you specify isinvalid.

To manage journal groups, you must be the Service Administrator.

For information on working with journals, see the Working with Financial Consolidationand Close.

To create journal groups:

1. On the Home page, click Journals, then select Manage Journals.

2. From the Actions menu, click Groups.

3. Click Create.

4. Enter a name for the journal group.

5. Optional: Enter a journal group description.

6. Click Save.

Deleting Journal GroupsYou can delete a journal group if you are the Service Administrator and if there are nojournals associated with the group.

To delete journal groups:

16-1


2. From the Actions menu, click Groups.

3. Take one of these actions:

• Select one or more journal groups to delete, click Delete Selected, and thenclick Confirm at the confirmation prompt.

• To delete all journal groups, click Delete All, and then click Confirm at theconfirmation prompt.

Note:

If the group has any journal references in the application, the systemdisplays an error message that it cannot delete the group.

Managing Journal PeriodsBefore you can work with journals, you must open the time periods for the journals. Bydefault, all periods have an initial status of Unopened. You can open and close periodsat any time, but you cannot change an opened period to unopened.

To manage journal periods, you must be the Service Administrator.

To post journals, you must open the time periods for each scenario to which you wantto post. You cannot post journals to an unopened or closed period.

If there are Approved journals in the period, you cannot close it. If you select to close aperiod that contains Working or Submitted journals, a warning message is displayedthat non-posted journals were found for the period, but you can close it.

You cannot close a period if there are unposted auto-reversal journals in the period.

For information on working with journals, see the Working with Financial Consolidationand Close.

To open or close periods:


2. Click Manage Periods.

3. For Scenario and Year, select members of the periods that you want to open.

4. Select the periods to open or close.

5. To open the selected periods, from the Actions drop-down, select Open, or toclose them, click Close.

Setting Journal OptionsAdministrators have the ability to allow users with the User role to approve journals.This option is only displayed for administrators, and it applies to all journals.

If you disable this option, when a User tries to approve a journal, the system displaysan error message that they are not authorized to perform the task.

Chapter 16Managing Journal Periods

16-2

To enable or disable journal options:


2. From the Actions menu, select Journal Options.

By default, Allow users with User role to approve journals is enabled.

3. To disable the option, and not allow users with User role to approve journals,uncheck the checkbox, and then click Save.

Journal Referential IntegrityTo prevent a referential integrity problem with journals from occurring in theapplication, Financial Consolidation and Close verifies and prevents the deletion ofany metadata member that is referenced in a journal.

The system verifies member deletion from these dimensions for referential integrity:

• Scenario

• Account

• Entity

• Period

• Year

• View

• Custom

• When you delete a dimension member from the application (using either theSimplified or Classic Dimension Editor), the system displays a confirmationmessage asking you to confirm that you want to delete the member.

• If the member is referenced in a journal, the system displays the following errormessage and the member is not deleted.

Failed to delete member XXX because member is referred to inJournal(s) XXX.

Chapter 16Journal Referential Integrity

16-3

17Consolidating Data

Related Topics

• Consolidation Process

• Data Flow

• Consolidation Process Flow

• Intercompany Eliminations

• Consolidation Dimension

• Translation Process

• Translating Data

• About Exchange Rates

• Entering Exchange Rates

• Entering Override Rates

• Specifying Default Translation Settings

• Consolidation and Translation Security Access

• Calculation Status

• Consolidating Data

• Viewing Consolidation Progress

• Running a Consolidation Report

• Consolidation Examples

• Advanced Consolidation Overview

• Consolidation Logic

• Managing Consolidation Methods

• Modifying Consolidation Methods

• Adding Consolidation Methods

• Importing and Exporting Consolidation Methods

• Recomputing Ownership Data

• Managing Ownership

• Changing Manage Ownership Settings

• Importing and Exporting Ownership Data

• Ownership Settings Year to Year

• Ownership Settings in Forms and Configurable Calculation Rules

• Advanced Consolidation Rules

• About Configurable Consolidation Rules

17-1

• Managing Consolidation Rule-sets and Rules

• Creating Consolidation Rule-sets

• Creating Consolidation Rules

• Consolidation Strings

• Viewing Rule-Sets

• Deploying and Undeploying Rule-Sets

• Duplicating and Deleting Rule-Sets

• Seeded Consolidation Rules

Consolidation ProcessConsolidation is the process of gathering data from descendant entities andaggregating the data to parent entities. After you enter or load data into base-levelentities, calculate and adjust data, you run a consolidation for a selected Scenario,Year, Period and Entity to aggregate the data throughout the organization.

You launch the Consolidation process from forms or from data grids. You must havefirst loaded or entered data in base entities. See Consolidating Data.

Launching consolidation runs the consolidation rules for the specified scenario, period,and entity. The translation process is run as required to convert data from the childentity currency to the parent entity currency. If the child and parent entity use the samecurrency, the translation process is not run.

After you select the parent entity into which the dependent entities consolidate, therequired processes run automatically.

• 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 differentcurrencies, the system translates data based on the exchange rate.

• You can enter adjustments to data through journals.

• The consolidation process begins. You can make further adjustments tocontribution data through journals.

Data FlowFinancial Consolidation and Close provides several dimensions through which data"flows" from an input point to a consolidated point. These dimensions are the Entity,Consolidation and Currency dimensions.

Entity Dimension

The Entity dimension allows a multi-level hierarchy of entities, generally representingthe ownership structure of one or more owning (holding) companies and thecompanies in which the holding company has either direct or indirect ownership. Directownership is ownership of shares of an owned company, while indirect ownership isownership of a company through another company. For example, if company A ownsshares in company B, and company B owns shares in company C, then A has directownership of B, B has direct ownership of C, and A has indirect ownership of C.

Chapter 17Consolidation Process

17-2

Parent entities in Financial Consolidation and Close are generally expected torepresent the consolidated financial results of a holding company. Consolidatedfinancial statements are the "Financial statements of a group in which the assets,liabilities, equity, income, expenses and cash flows of the parent (company) and itssubsidiaries are presented as those of a single economic entity" (IAS 27, IFRS 10).Consolidated results are the aggregation of the results of the reporting company (alegal entity) and the companies that it owns, either directly or indirectly (all of which arelegal companies). Notably, consolidated results are NOT the aggregation of thepreviously consolidated results of other holding companies.

Consolidation / Currency Dimensions

Data flows from a child entity to a parent entity in a multi-currency application throughthe Consolidation and Currency dimensions. For a single-currency application, theCurrency dimension does not exist and data flows through only the Consolidationdimension.

Base Entity Data Entry

At a base (level 0) entity, the Entity Input member is used to enter data through dataforms, Smart View, Data Management, Journals, or Supplemental Data Manager inEntity Currency. The actual currency that Entity Currency represents in a multi-currency application is defined on an entity-by-entity basis.

The Opening Balance movement member is never entered directly to Entity Input butis carried forward from the Closing Balance of the prior period. Some ClosingBalances are carried forward to the Opening Balance of a different account (RetainedEarnings, Owner's Income, Total Other Comprehensive Income), but all ClosingBalances are carried forward.

Translation

Entity Input / Entity Currency is translated to Entity Input / Parent Currency in a multi-currency application. If the currency of the child and parent is the same, then thetranslation is at a rate of 1. Otherwise, the translation is carried out by applying therequired exchange rate and translation method to the untranslated data. Thistranslation from Entity Currency to Parent Currency is completed as part of theConsolidation process.

If required, the Entity Input data can be translated to one or more reporting currenciesthrough the Translation process. If the reporting currency is the same currency asrepresented by either the Entity Currency or the Parent Currency, then the data iscopied from the relevant source to the reporting currency. If the reporting currency isnot the same currency as represented by either the Entity Currency or the ParentCurrency, then the data is translated using the same process as translation from EntityCurrency to Parent Currency.

Opening Balances are never translated but are carried forward from the translatedClosing Balances of the prior period.

Entity Input aggregates to Entity Total. For a multi-currency application, thisaggregation occurs for Entity Currency, Parent Currency and any populated reportingcurrencies.

Proportionalization

Entity Total / Parent Currency (or Entity Total for a single-currency application) isproportionalized to the Proportion member. Proportionalization applies theConsolidation % defined for the child/parent combination to all Entity Total data points.

Chapter 17Data Flow

17-3

Opening Balances are never proportionalized, but are carried forward from the ClosingBalances of the prior period of the Proportion member. If the Consolidation % changesfrom one period to the next, the Opening Balance Ownership Change system rulegenerates adjustment entries in the Elimination member to adjust the OpeningBalance to the required current period Consolidation %.

Elimination

Entity Total / Parent Currency (or Entity Total for a single-currency application) can beeliminated and adjusted to the Elimination member. The Standard Elimination systemrule adjusts intercompany entries based on the account Intercompany and PlugAccount settings. Additional adjustments can be generated from ConfigurableConsolidation rules.

Opening Balances are always carried forward from Closing Balances of the priorperiod of the Elimination member.

Contribution to Parent

Proportion data aggregates with Elimination data to Contribution, and then to EntityConsolidation of the parent, combining with the Contribution data from the siblings (forexample, other children of the parent).

Opening Balances are always carried forward from Closing Balances of the priorperiod of the Entity Elimination Adjustments member.

Parent Entity Data Entry

At the parent entity, additional data can be introduced in the Entity Input member(currently through Journal entries only).

Entity Consolidation and Entity Input are then aggregated to Entity Total and translatedto Parent and Reporting currencies as required. The consolidation process thencontinues through the Consolidation / Currency dimensions from each child entity to itsparent.

Chapter 17Data Flow

17-4

Consolidation Process FlowFinancial Consolidation and Close processes data through the Consolidationdimension, beginning with local currency (“Entity Currency”) data in the Entity Input,Entity Consolidation and Entity Elimination Adjustment members, then progressing tothe same members for translated currency (for multi-currency applications only) andfinally the Proportion and Elimination consolidated data.

At each level of processing, various system calculations are executed. Some systemrules will always run while others can be disabled or configured. Custom rules can bealso added in pre-defined “insertion points”.

The Consolidation: Process screens, accessed from the Consolidation card, showsthe sequential flow of consolidation activities for each of the Local Currency,Translated and Consolidated levels, displayed as selected from the horizontal tabs.

Local Currency

Chapter 17Consolidation Process Flow

17-5

Opening Balance Carry Forward

At each level of the Entity, Consolidation and Currency dimensions, the ClosingBalance of the prior period is carried forward to the Opening Balance of the currentperiod for all Flow type accounts.

The local currency Opening Balance is retrieved from the local currency ClosingBalance of the prior reporting period of the same scenario. If the current period is thefirst period of the year, then the Opening Balance will be retrieved from the last periodof the prior year.

For all Balance Sheet accounts (account type Asset, Liability or Equity), the OpeningBalance is retrieved for all periods. For Income Statement accounts (account typeRevenue or Expense), the Opening Balance is retrieved for all periods except the firstperiod of the year.

The Opening Balance is retrieved:

• In the Periodic reporting view, from the Closing Balance of the prior period

• In the Quarter-to-date reporting view, from the Closing Balance of the prior quarter

• In the Half-year-to-date reporting view, from the Closing Balance prior half-year

• In the Year-to-date reporting view, from the Closing Balance of the prior year

After Opening Balance Carry Forward

Any deployed custom calculation rules created in the seeded “FCCS_10_AfterOpening Balance Carry Forward_LocalCurrency” Calculation Manager rule willexecute.

See Working with Configurable Calculations and Working within Calculation Manager.

Equity Pickup

The Equity Pickup system rule provides a built-in sequential calculation of EquityPickup for holding companies.

The Equity Pickup system rule will display only if Equity Pickup has been enabled,either during application creation or subsequently.

This rule will alter the sequencing of entity processing during a consolidation to ensurethat all holding companies are calculated after their siblings. The amended sequencingcan be turned off and on as required. The correct calculation of Equity Pickup also


17-6

requires the deployment of Equity Pickup consolidation rules (see Equity PickupOverview for further details of the Equity Pickup feature).

Balance the Balance Sheet

The next system rule executed at Local Currency is “Balance the Balance Sheet”. Thisrule is optional and can be enabled or disabled for all scenarios or on a scenario-by-scenario basis. If the rule is enabled, an out-of-balance Balance Sheet will bebalanced by the posting of a balancing amount to the seeded “FCCS_Balance”account.

Final Calculations

Any deployed custom calculation rules created in the seeded “FCCS_20_FinalCalculations_LocalCurrency” Calculation Manager rule will execute.


Ratios

If “Asset Management Ratios” option has been selected, then the “FCCS_Days SalesIn Receivables” and “FCCS_Days Sales In Inventory” ratios are calculated.

Translated

Note that the Translated tab is not available for single-currency applications.


At each level of the Entity, Consolidation and Currency dimensions, the ClosingBalance of the prior period is carried forward to the Opening Balance of the currentperiod for all Flow type accounts.

Note that Opening Balance is never translated. Opening Balance is always carriedforward from the Closing Balance of the prior period for the Applicable ConsolidationMembers and at Parent Currency.

The translated currency Opening Balance is retrieved from the translated currencyClosing Balance of the prior reporting period of the same scenario. If the current periodis the first period of the year, then the Opening Balance will be retrieved from the lastperiod of the prior year.


17-7







Default Translation

Default Translation applies the default translation settings to the translation of periodicmovement members. The default translation settings can be configured from theManage Defaults button on the Translation Overrides screen.

Any “Amount Override” and “Rate Override” entries are also applied to the translateddata.

See these topics:

• Translation Process

• Translating Data

• About Exchange Rates



• Specifying Default Translation Settings

Translation Overrides

Translation Override rules can be configured and deployed. The Entity Currencyvalues of a selection of data-points defined as the scope of the rule, applied againstthe specified exchange rate and translation method (Periodic or Year-to-Date) caneither replace or accumulate with the default translation results.

See these topics:

• Working with Override Translation Rules

• Creating Override Translation Rules

• Deploying Override Translation Rules

Foreign Exchange (FX) Calculations

The foreign exchange variation includes the calculation for both Opening Balance andtotal movements.

FX Opening stores the difference between the translation of Opening Balance at theEnding Rate for the current period and the Opening Balance retrieved from the priorperiod's translated Closing Balance.

FX Movements stores the difference between the translation of total movements at theEnding Rate for the current period and the translated total movements using theAverage rate or historical rate or amount overrides for the current period.


17-8

Foreign Exchange (FX) to Cumulative Translation Adjustment (CTA)

Historical accounts will always be translated using the default rate for the accountunless the account has the exchange rate type of "Historical Amount Override" or"Historical Rate Override". The FX Opening and FX Movements will be calculated forthe historical accounts using the appropriate override rate or amount if applicable.

The reverse of the total FX Opening and FX Movements amount will then be stored inthe FX to CTA or FX to CICTA Movement member so that the FX Total for thehistorical accounts will be zero. The same amount will also be posted to thedesignated CTA or CICTA account, depending on the setting for the application.


Any deployed custom calculation rules created in the seeded “FCCS_30_AfterOpening Balance Carry Forward_Translated” Calculation Manager rule will execute.


Final Calculations

Any deployed custom calculation rules created in the seeded “FCCS_40_FinalCalculations_Translated” Calculation Manager rule will execute.


Ratios


Consolidated


At all levels, the first process is the “Opening Balance Carry Forward”. At each level ofthe Entity, Consolidation and Currency dimensions, the Closing Balance of the priorperiod is carried forward to the Opening Balance of the current period for all Flow typeaccounts.

Note that Opening Balance is never consolidated, but always carried forward from theClosing Balance of the prior period.


17-9







Proportionalization

All data is posted to the "Proportion" Consolidation dimension member at theConsolidation percent.

Standard Eliminations

See Standard Elimination Consolidation Rules.

Opening Balance Ownership Change

See Opening Balance Ownership Change Consolidation Rules.

Configurable Consolidations

See About Configurable Consolidation Rules.


Any deployed custom calculation rules created in the seeded “FCCS_50_AfterOpening Balance Carry Forward_Consolidated” Calculation Manager rule will execute.


Final Calculations

Any deployed custom calculation rules created in the seeded “FCCS_60_FinalCalculations_Consolidated” Calculation Manager rule will execute.


Ratios


Intercompany EliminationsStandard Eliminations Overview

Companies record the results of transactions with other companies. Those othercompanies might be related companies or unrelated (that is, third party) companies.When reporting consolidated financial results, the impact of any transactions for whichthe legal companies within the scope of the consolidation have “common control” mustbe removed /eliminated from the consolidated results. The net results must bepresented as if the group of legal entities were a “a single economic unit”.

Chapter 17Intercompany Eliminations

17-10

Transactions with unrelated companies do not require elimination. Transactions withrelated companies might need to be eliminated or partially eliminated depending onwhether the related company is in the scope of the consolidated results and theaccounting requirements applied to the consolidation “arithmetic”.

The nature of the relationship between the related parties will determine the manner inwhich information from the in-scope companies is aggregated and eliminated toproduce the consolidated results. Different accounting standards will require somedifferent aggregation methods, but most standards follow similar general principles.

When an application is enabled for Intercompany accounts and contains Intercompanyaccount data, eliminations take place as part of the consolidation process.

Processing of Intercompany Eliminations

Data that are a result of transactions between two entities (that is, Intercompanytransactions), both being consolidated into a common parent entity, must beeliminated in order to present the parent entity consolidated results as “a singleeconomic unit”.

The intercompany transaction amounts are initially recorded twice. Each of the twoparties (companies) involved in the transaction records their view of the transaction.The transaction is recorded separately by each entity, with the other entity as the“Intercompany partner”. Note that the entries recorded by both entities represent thesame transaction, but are entered separately by the two entities involved in thattransaction.

The amounts to be eliminated are the amounts controlled “in common” by the parententity at which common ownership is represented in the organization hierarchy. Thenet effect of the eliminations must be zero (that is,. debits must equal credits), but thedata is reclassified in order to net out at the parent entity. If the source data from bothentities involved in the transaction is proportionalized at 100%, then the fullproportionalized amount must be eliminated. If the amount proportionalized by eitherentity is less than 100%, then only the lowest proportional amount is eliminatedbecause only the lowest proportionalized amount is controlled in common. Thereforean eliminated amount cannot exceed the proportionalized amount under anycircumstances. If the Consolidation % for either of the companies involved is 0% thenno elimination is processed.

Each elimination entry consists of two entries in the “FCCS_IntercompanyEliminations” Data Source dimension member in the Elimination Consolidationdimension member. The first entry reverses (or partially reverses) the originalintercompany amount. All dimension members to which the reversal is applied aretaken from the source POV with the exception of the Consolidation and Data sourcedimensions. An offsetting second entry is posted to the “Plug” account, as defined inthe metadata for the source intercompany account. As with the reversal entry, the Plugentry is posted to the “FCCS_Intercompany Eliminations” Data Source dimensionmember in the Elimination Consolidation dimension member. All dimension membersto which the Plug entry is applied are taken from the source POV with the exception ofthe Consolidation and Data source dimensions. If the Plug account is not set as anIntercompany account, then the Plug entry is posted to “FCCS_No Intercompany” inthe Intercompany dimension.

Conditions for Intercompany Eliminations

The Entity structure(s) for an application can be created as a “Flat” structure (oneparent entity with all directly owned and indirectly owned entities as immediate


17-11

children). The parent entity represents the consolidated results of the ultimate Holdingcompany. Alternatively, one or more multi-level (or “staged”) structures can becreated. In a multi-level structure, the sibling entities of each Holding company arethose companies directly owned by the Holding company. If those directly ownedcompanies themselves own other companies, then the sibling of the owning Holdingcompany is the consolidated parent of the owned Holding company.

In a Flat structure, the logic for determining whether an elimination is to be processedis simple. The following logic is applied:

Data is a candidate for elimination if:

1. The account is an intercompany account and has a valid Plug (clearing) accountassigned

2. The data has an Intercompany dimension entry of other than “FCCS_NoIntercompany” (that is, contains a valid partner)

3. The entity to which the intercompany transaction has been posted, and the partnerreferenced in the data definition (POV) both consolidate to the parent at greaterthan 0%

If these conditions are met, then the data is re-classified to the Plug account in theElimination dimension member at the lower of the entity Consolidation % and thepartner Consolidation %.

In a multi-level structure, the logic for determining whether an elimination is to beprocessed is in principle the same as in a Flat structure. However, the nature of amulti-level structure introduces additional potential complications. The following logic isapplied:

Data is a candidate for elimination if:

1. The account is an intercompany account and has a valid Plug (clearing) accountassigned

2. The data has an Intercompany dimension entry of other than “FCCS_NoIntercompany” (that is, contains a valid partner)

3. The entity to which the intercompany transaction has been posted, and the partnerreferenced in the data definition (POV) both consolidate to a common parent orancestor at greater than 0%

• a. The entity and partner might not both consolidate to an immediate commonparent…either or both the entity and partner might consolidate to a commonancestor via one or more intermediate parents.

• b. The relevant consolidation % used in the evaluation and posting of theelimination is the cumulative consolidation % derived by multiplying the level-by-level % from the entity or partner to the contribution to the common ancestor (thatis, the cumulative factor specific to a branch of the hierarchy culminating at thecommon ancestor). The cumulative Consolidation % represents the contributionfrom the source entity / partner to the common ancestor for each contributor.

• c. The “lower of entity or partner consolidation %” is applied to the sum of theentity cumulative %, aggregated across all siblings of the entity and the sum of thepartner cumulative %, aggregated across all siblings of the entity. In a multi-levelhierarchy, both the entity and the partner could exist in more than one branch ofthe hierarchy and could therefore aggregate to the common ancestor throughmultiple children of the common ancestor.


17-12

• d. The data point could be a candidate for elimination at more than one level of thehierarchy, immediately below more than one common ancestor. If the partnerexists in more than one branch of the hierarchy, then the entity’s consolidationpath up through the structure could encounter more than one common ancestor. Ifimmediately below the first (or a subsequent) common ancestor, the full entityamount is eliminated, then further elimination will not occur because theelimination amount cannot exceed the proportionalized amount. If no elimination(or only a partial elimination) occurred at previous levels of the hierarchy, then afurther elimination could be required immediately below the current commonancestor.

If these conditions are met, then the data is re-classified to the Plug account in theElimination dimension member at the lower of the sum (across sibling entities /branches) of the cumulative entity Consolidation % and the sum (across siblingentities / branches) of the cumulative partner Consolidation %. If the aggregatedpartner Consolidation % is lower than the aggregated entity Consolidation %, then thepartner % is applied.

Ensuring that Eliminations do not exceed Proportionalization

As previously noted, based on the concept of eliminating commonly controlledtransactions, the cumulative elimination amount of an intercompany transaction cannotexceed the proportionalized amount. The system must therefore ensure that if the netcontribution amount of an intercompany account has been reduced to zero, no furthereliminations can occur.

It is possible that a computerized system cannot and does not record an accumulationto zero accurately*. This is due to a “decimal precision” issue common to all computersystems. As a result, a situation might arise such that the net contribution of a sourceintercompany amount is not reduced to exactly zero when it does logically equal zero.The test as to whether further intercompany eliminations should be processed cantherefore not depend on the net contribution being equal to zero, but must instead bebased on the net contribution being “approximately equal” to zero.

The test for whether a net contribution amount is “approximately equal” to zero candepend on the magnitude of the data in the system. By default, FCCS applies “decimalprecision” of four decimals when applying the test. In this case, any net contribution ofless than 0.0001 will be considered as zero and further eliminations will not be appliedto the data. In most cases and for most currencies this level of precision shouldprovide sufficient accuracy. However, if unexpected eliminations still occur, aSubstitution Variable can be added to the application to modify the decimal precisionapplied to the test.

To add a substitution variable, navigate to the “Variables” card and select the“Substitution Variables” tab. Click on the plus symbol to add a new substitutionvariable. For “All Cubes”, enter “DecimalPrecision” as the Name (no space between“Decimal” and “Precision”). Enter the required number of decimals to consider whenapplying the “approximately equal” test. The greater the magnitude of data valuesentered (that is, the number of significant digits to the left of the decimal point), thelower the decimal precision entry might need to be.

Note that the decimal precision variable entry must be an integer (zero or a positive ornegative whole number) or subsequent consolidations might fail. A positive entry willround the net contribution amount to the specified number of decimal positions, zerowill round to an integer and a negative entry will round to a multiple of 10 (so forexample, a decimal precision of -2 will round 1,234,567.89 to 1,234,600, rounding tothe nearest 100).


17-13

*For the specific conditions relating to FCCS, please see “The Limits of Data Precisionin Essbase” at: https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=443798297810512&id=1311188.1&_afrWindowMode=0&_adf.ctrl-state=zlaqk3trz_4.

Consolidation DimensionThe Consolidation dimension provides an additional layer to the financial information,which enables you to view details on input values, adjustment, and contributioninformation. It includes entity data, such as the input value and any relatedadjustments to the entity’s data. As a dependent entity’s values roll up into its parentduring consolidation, the system stores consolidation detail including Proportion andElimination detail. Proportion detail contains the balances resulting from the executionof the proportionalization consolidation rule. This reflects the application of theconsolidation percentage on the source data. Elimination detail contains the results ofall other consolidation and elimination rules.

The Consolidation dimension includes the following members:

• Entity Input—This member represents input data and non-consolidation -relatedbusiness logic (for example, member formulas).

• Entity Consolidation—This is only available for a Parent entity. The amount inthis member represents the total of the Contribution from each of its child entities.This is a system-calculated amount as a result of the consolidation process.

• Entity Total—The summation of data of an entity, including both input andadjustment data stored in the Entity Input member, and the total contributionstored in the Entity Consolidation member (only for a parent entity).

• Proportion—The proportionalized values of the Entity Total member of a singleentity, for a specific parent entity during a consolidation of a consolidationhierarchy. There is one Entity Proportion member in the Consolidation dimensionfor every Parent/Child entity relationship.

• Elimination—Consolidation adjustment and elimination data for a specific Parent/Child entity is generated and stored in this member.

• Contribution—The consolidated result of a single entity for a specific ParentEntity. This includes the aggregation of the Proportion data and Elimination datafor the Parent/Child entity.

The Consolidation dimension enables you to report on the details used to perform thedifferent stages of the consolidation process. It stores intermediate results during theconsolidation process to record how the system adjusted the consolidated members. Itprovides an audit trail of the transactions applied to data during the consolidationprocess.

The following figure shows the Consolidation dimension with Intercompanyeliminations enabled:

Chapter 17Consolidation Dimension

17-14

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=443798297810512&id=1311188.1&_afrWindowMode=0&_adf.ctrl-state=zlaqk3trz_4



Note: * Entity Consolidation member is a dynamic calculated member and is onlyapplicable to the Parent entity. This member is calculated by the sum of all children’scontribution.

Translation ProcessFinancial Consolidation and Close provides currency translations for a multi-currencyapplication. The default translation process applies the Periodic translation method toFlow accounts and the Year-to-Date method to Balance accounts.

See Translating Data.

Translation During the Consolidation Process

When you consolidate data, currency translation occurs if the parent entity has adifferent default currency than the child entities. Translation to Parent Currency isperformed as part of the consolidation process. The parent currency for any entity thatis a child of the dimension name (“Entity”) is assumed to be the system currencyselected when the application was created.

When the system performs translation, if the source data is not consolidated or if datais impacted, it automatically consolidates the data before translating.

Translation to Reporting Currencies

If you want to translate data into a specific Reporting Currency, you select the targetReporting Currency and perform translation. Only currencies enabled for reporting areavailable for Reporting Currency translation. All Reporting Currencies have a suffix of_Reporting, for example, USD_Reporting.

Translation to Reporting Currencies is required for all periods. If prior periods in thecurrent year have not yet been translated, they will be translated before the selectedperiod. If there are prior years that have not been fully translated, you will need totranslate in sequence each year that has not yet been translated and then translatethe current year.

Each entity is translated independently of each other.

• If the default currency of the entity is the same as the Reporting Currency, then theentity currency is moved to Reporting Currency.

• If the default currency of the entity is not the same as the Reporting Currency, thenif there is a Parent Entity with a default currency that is the same as the ReportingCurrency, the Parent Currency is copied to the Reporting Currency.

Chapter 17Translation Process

17-15

• If neither the default currency for the entity nor the parent entity is the ReportingCurrency, then the entity currency is translated to the Reporting Currency.

Due to the cumulative nature of some translation calculations, it is recommended thatany translation to a Reporting Currency that is neither an entity's Entity currency orParent currency be executed from the first period of the year.

Note that only entity input and entity consolidation are translated. Proportion,Elimination and Contribution will not show up in Reporting Currency.

Exchange Rates

The Rate Cube contains all the exchange rate data with respect to any sourcecurrency to any destination currency. If there is no Override rate or amount for aHistorical Rate account, the system uses the global exchange rate for translation.

You can view the exchange rates used for calculations in a pre-defined data form. Youcan also use pre-defined forms to enter exchange rates and to enter override rates.See these sections:



• Predefined Forms

Translating DataCurrency translation converts data from one currency to another. You can translatedata from the entity’s input currency to any other reporting currency that has beendefined in the application. When you consolidate data, currency translation occurs ifthe parent entity has a different default currency than the child entities.

Financial Consolidation and Close provides default currency translations for a multi-currency application. By default, the translation process uses the Periodic Value (PVA)method for Flow accounts, and the Value at exchange rate (VAL) method for Balanceaccounts. The default method and exchange rate accounts used can be modified. See Specifying Default Translation Settings.

Translation is performed using calculation scripts and based on stored consolidateddata. When the system performs translation, if data is not consolidated or if data isimpacted, it automatically consolidates the data before translation. The systemtranslates the stored consolidated amount to the Reporting currency by applying theapplicable exchange rates.

Translation to Parent currency is performed as part of the consolidation process. If youwant to translate data into a specific Reporting currency, you select the targetReporting Currency and perform translation. Only currencies enabled for reporting areavailable for Reporting currency translation.

All accounts within the Balance Sheet grouping ("FCCS_Balance Sheet") except for"Saved Assumption" accounts are translated. The default translation is based on thedefault translation settings that you have selected from the Translation Overridesscreen (Periodic Translation at Average Rate is used by default unless modified).

All Movement dimension base (level 0) members are translated at the selectedtranslation settings except for the Opening Balance Adjustment member. Any overrideaccount entries for accounts specified as Historical Amount Override or Historical RateOverride Exchange Rate Type accounts are then applied, replacing the default

Chapter 17Translating Data

17-16

translations. If no override entries were made, then the Historical accounts remaintranslated at the default settings. Any deployed translation override rules are thenapplied, adjusting or replacing the default translation results.

Opening Balance Adjustment entries are deemed to be related to the prior period (forexample, prior period adjustments). Opening Balance Adjustment entries are thereforetranslated at the prior period Ending Rate. Historical accounts are translated at theprior period "effective rate" (the ratio of the prior period Closing Balance translatedamount divided by the prior period Closing Balance untranslated amount) on anaccount-by-account basis. It is possible that small extraneous amounts might createan invalid (unreasonable) effective rate that can incorrectly distort subsequenttranslation calculations. To avoid this issue, if the ratio of the calculated prior periodeffective rate to the prior period Ending Rate (or the reciprocal) exceeds 10, then theEnding Rate will be used for the translation (for example, if effective rate / ending rate< 0.1 or effective rate / ending rate > 10, then translate using the ending rate).

Foreign Exchange Variances (FX Opening, FX Movements) are then calculated tobring the aggregated Closing Balance to the equivalent of the untranslated ClosingBalance translated at Ending Rate. Then for all accounts that are defined with anExchange Rate Type of Historical, Historical Rate Override or Historical AmountOverride, the calculated FX is reversed in either the FX-to-CTA or FX-to-CICTAmovement members. The accumulation of these reversals for all accounts within theBalance Sheet top member (not the "FCCS_Balance Sheet" grouping, but the"FCCS_Total Balance Sheet" Traditional or Net Assets member) are then posted tothe CTA or CICTA account (within the Balance Sheet, the reversal of the calculatedFX and the posting to CTA / CICTA is a balanced entry).

After the translation process is complete, the translated data is stored. Adjustmentscan be made to the stored data using Configurable Calculation rules.

You can view the exchange rates used for calculations in a pre-defined data form. Youcan also use pre-defined forms to enter exchange rates and to enter override rates.See these sections:



• Predefined Forms

To translate data:


2. From the Forms list, click Data Status.

3. Select the point of view.

4. Select a cell for which to run translation rules.

5. From the Actions drop-down menu, select Business Rules.

6. From the Business Rules dialog, click Translate.

7. When the translation process successfully completes, the system displays aconfirmation message. Click OK.

Note that if a translation is interrupted, it might be necessary to run a ForceTranslate to reset the system and complete the required translation.

Chapter 17Translating Data

17-17

About Exchange RatesYou use exchange rates to convert values from one currency to another. You canenter rates from any source currency to any destination currency. To specify exchangerates, you must set up multiple currencies when creating an application.

See Creating Currencies and Translating Data.

Financial Consolidation and Close supports two system exchange rates - Average andEnding. The system translates Flow accounts using the Average rate and the Balanceaccount using the Ending rate.

Financial Consolidation and Close provides the ability to enter direct exchange rates,indirect exchange rates and cross-rates.

See Entering Exchange Rates.

Direct Exchange Rates

A direct exchange rate is the rate by which an untranslated amount is multiplied inorder to calculate the translated amount.

GBP to USD: 2.00

GBP 100 x 2.00 = USD 200

Note that the direct rate between a currency and itself is always assumed to be 1.

Indirect Exchange Rates

An indirect exchange rate is the reverse of a direct exchange rate. The untranslatedamount is divided by the rate to calculate the translated amount. The indirect rate forcurrency 1 to currency 2 is also the direct rate for currency 2 to currency 1.

USD to GBP = 0.50

GBP 100/ 0.50 = USD 200

USD 200 x 0.50 = GBP 100

Cross-Rates

Generally, exchange rates are quoted and entered in terms of a common or systemcurrency. When a translation is to be calculated with that system currency, the director indirect rate is applied. When a translation is to be calculated between two othercurrencies (for example, neither currency is the system currency), then the requiredcross-rate can be triangulated through the system currency.

Using USD as the system currency:

GBP to USD: 2.00 direct rate

EUR to USD: 0.80 direct rate

USD to EUR: 1.25 indirect rate

GBP to EUR = GBP to USD/ USD to EUR = 2.00 / 1.25 = 1.60

If only direct rates are entered to Financial Consolidation and Close, based on thesystem currency, the system will calculate the indirect rates and all of the cross-rates

Chapter 17About Exchange Rates

17-18

used in translations. If indirect rates or cross-rates are entered, FinancialConsolidation and Close will not overwrite the entered rates.

It is recommended that only direct rates be entered to Financial Consolidation andClose in order for the most accurate indirect and cross-rates to be generated. If forexample, an indirect rate is entered and it is not the reciprocal of the direct rate, then atranslation from currency 1 to currency 2 and then back to currency 1 will incorrectlynot yield the original amount. A similar issue can occur if cross-rates are entered.

Entering Exchange RatesFinancial Consolidation and Close provides the ability to enter direct exchange rates,indirect exchange rates and cross-rates. It is recommended that only direct rates beentered to Financial Consolidation and Close for the most accurate indirect and cross-rates to be generated.

See About Exchange Rates.

You can enter Exchange Rate data using two pre-built system Exchange Rate forms:

• Enter Exchange Rates - Single Period: Enter exchange rates for the singleperiod selected in the Point of View.

• Enter Exchange Rates - Multi Period: Enter exchange rates for multiple periodsto a single To Currency selected in the Point of View

Note:

The predefined Rate forms are only provided if the Multi-currency option wasselected during application creation. See Predefined Forms.

You can also import Exchange Rates. See Example: Data Import File - ExchangeRates.

To enter direct rates in a data form:


2. From the Forms list, click Enter Exchange Rates - Single Period, or EnterExchange Rates - Multi Period.

3. From the POV, select the Scenario, Year, and Periods.In the rows, select the level0 descendants in the "From Currency" dimension, excluding the currency definedas the system currency:ILvl0Descendants(From Currency) excluding USD

4. In the rows, select the level 0 descendants in the "From Currency" dimension,excluding the currency defined as the system currency:

ILvI0Descendants(From Currency) excluding USD

5. In the columns, select the level 0 descendants of "Entered Exchange Rates" in theAccount dimension:

ILvI0Descendants(Entered Exchange Rates)

6. Enter the direct rates and click Save.

7. From Actions, select Compute Rates.

Chapter 17Entering Exchange Rates

17-19

To view all rates in a form:

1. From the Home page, click Data, and then open the Exchange Rate form toreview the rates.

2. In the rows, select the level 0 descendants in the "From Currency" dimension:

ILvI0Descendants(From Currency)

3. In the columns, select the level 0 descendants of "Input Currencies" in theCurrency dimension:

ILvI0Descendants(Input Currencies)

4. In the columns, select the level 0 descendants of "Entered Exchange Rates" in theAccount dimension:

ILvI0Descendants(Exchange Rates)

After you have entered all the direct rates and executed the "Compute Rates" rule, alldirect, indirect and cross-rates will be displayed.

The direct rate entry and all rates display can be combined into one form for a singleperiod if required.

In this example, direct rates for USD, BRL, CAD, CHF and GBP are entered in the firsttwo columns against a system currency of EUR. All indirect and cross-rates are thendisplayed.

Entering Override RatesMost accounts use the standard translation method with the default exchange rates.Some Balance Sheet accounts are specified as Historical Rate accounts (for example,Common Stocks, Investment in Subs).

Accounts specified as Historical Rate accounts are translated using the override rateor override amount that you specify. If there is no override rate or amount for aHistorical Rate account, the system uses the global exchange rate for translation.

For Historical Rate accounts, the system provides a pre-built form for you to entereither an override rate or override amount for the account. All accounts using HistoricalRate overrides are also automatically created as shared members under the HistoricalAccount hierarchy. See Defining Accounts, and Predefined Forms.

Chapter 17Entering Override Rates

17-20

Note:

The predefined Rate forms are only provided if the Multi-currency option wasselected during application creation.

When you enter an override amount or rate to an Intercompany entry that has alreadybeen eliminated, the override will also be applied to the elimination entry. Theeliminated amount in Data Source "Intercompany Eliminations" will be adjusted by thesame ratio as the original source entry in one or more of the "Total Input and Adjusted"members.

You can also import Override Rates. See Example: Data Import File - Overrides.

To enter override rates:


2. From the Forms list, click Override Rates.

All accounts specified as Historical Rate accounts are listed in the rows.

3. From the POV, select a Scenario, Year, and Entity.

4. For an account, enter the amount or rate for the override, and click Save.

Specifying Default Translation SettingsBy default, the system provides standard translation methods on all accounts witheither a time balance property of Flow or Balance. You can select to change thesesettings and specify a default translation method and rate account for the application.

Security rights for Default Translation Settings

• Only service administrators can modify Default Translation Settings.

• Power users can view Default Translation Settings.

• Users and Viewers cannot modify Default Translation Settings.

System Default Translation Settings

When an application is first created, the system creates the following settings bydefault.

Balance account

• Translation method: Periodic

• Rate Account: Ending

Flow account

• Translation method: Periodic

• Rate Account: Average

You can select different translation settings for the application to use by default.Default translation methods are applied throughout the application unless Point ofView specific overrides exist.

Chapter 17Specifying Default Translation Settings

17-21

Note:

Any changes to the default translation settings impact existing data in theapplication. The calculation status changes from OK to System Change,and the status for all reporting currency changes to Needs Translation. Thisapplies to both locked and unlocked entities.

To specify default translation settings:

1. On the Home page, click Application and then click Consolidation.

2. From the Consolidation Process page, select the Translated tab.

3. From the list of rules, select Translation Overrides.

4. Click Manage Defaults.

5. When you open the Default Translation Methods page for the first time, it ispopulated with the system-provided default values. Select translation options forBalance and Flow accounts as needed.

Balance account

• Translation method: Periodic or Year To Date

• Rate Account: Average or Ending

Flow account

• Translation method: Periodic or Year To Date

• Rate Account: Average or Ending

Note:

Although you can create additional rate accounts for an application, youcan only select Average or Ending for the default translation accounts.

6. Click OK to save your changes.

Consolidation and Translation Security AccessThe following security access is required to consolidate or translate data:

• You must be an Administrator, Power User, or User.

• You must also have Write access to the Parent entity selected to be consolidatedor translated.

Note:

Entities that are locked are excluded from the consolidation process.

As an Administrator, you assign access to the Consolidate and Translate actions byassigning users access to the appropriate rule. When you assign a user Launchaccess to the Consolidate Business Rule, the user also has access to the Consolidate

Chapter 17Consolidation and Translation Security Access

17-22

action menu. When you assign a user Launch access to the Translate Business Rule,the user also has access to the Translate action menu.

Note:

Administrators have default access to all the rules in the application.

Calculation StatusOracle Financial Consolidation Close Cloud maintains the calculation status for eachScenario, Period, Entity and Parent entity combination. The calculation statusindicates whether data needs to be translated or consolidated. The calculation statuscan change as a result of several actions:

• Changing the organization structure

• Adding or deleting accounts

• Modifying entity attributes

• Entering data in data grids, or loading data from external sources

• Posting or unposting journals

• Reloading rules

• Changing percent consolidation

• Changing currency rates

• Changing override amount data

Table 17-1 Consolidation Statuses

Status Description

OK Data is OK - none of the data for the specifieddimensions has changed.

No Data No data exists for the specified dimensions.

Impacted Data has changed since last generated, whichrequires a reconsolidation to change its statusto OK. This occurs when a change to a baseentity data impacts a parent entity.

Needs Translation The selected dimension member is not theentity’s default currency and its translatedvalues may not be current.

System Change A change has occurred that may affect thedata for the specified dimensions. Forexample, a new rules file or metadata file hasbeen loaded, or the currency rate haschanged.

You can view the calculation status in forms and grids and then take action asnecessary. The following tables list available actions for forms and grids.

Chapter 17Calculation Status

17-23

Table 17-2 Entity Input/ Entity Currency - Base Entity

Status Description Action

No Data No data has been entered orgenerated.

None

OK None of the data haschanged.

None

Table 17-3 Entity Consolidation / Entity Currency - Parent Entity


OK None of the data haschanged.

None

Impacted A parent entity has beenimpacted by a change to achild entity.

Consolidate

Table 17-4 Entity Input/ Reporting Currency - Base Entity


OK None of the data has changed. None

Needs Translation Data needs to be translated becauseit has never been translated or datahas changed since the lasttranslation.

Translate

Table 17-5 Entity Consolidation/ Reporting Currency - Parent Entity


OK Consolidation has been done, anddata has been translated.

None

Needs Translation Data needs to be translated for thefollowing reasons:

1. Parent entity needsconsolidation first to generatethe Entity Consolidation dataand then translate.

2. Parent entity needs toreconsolidate first because childdata has changed and thentranslate.

3. Parent entity data is OK so onlyneed to translate.

Translate

1. The system will first consolidateand then translate.

2. The system will first consolidateand then translate.

3. Translation is required by user.

Chapter 17Calculation Status

17-24

Table 17-6 Proportion or Elimination / Parent Currency - Base Entity


No Data No data has been generatedfrom Consolidation.

Consolidate

OK Data is OK. None

Impacted Data has changed since lastgenerated, which requiresreconsolidation to change itsstatus to OK.

Consolidate

Table 17-7 Proportion or Elimination / Reporting Currency - Base Entity


No Data No data has been generated fromConsolidate and no translation hasbeen done.

Translate

OK Proportion and Elimination data hasbeen generated from Consolidationand data has also been translated.

None

Need Translation Data needs to be translated for thefollowing reasons:

1. Proportion data needs to be re-generated before translation.

2. Proportion data has beengenerated and is OK, buttranslation has not been run.

1. The system will reconsolidateand then translate data.

2. The system will translate onlythe Proportion data.

Consolidating DataYou can launch the Consolidation or Translation process from a form, and you canview the data status in a data grid. Oracle Financial Consolidation and Close Cloudprovides a predefined Data Status grid, which contains entities in the rows, andperiods in the columns. The data in the grid is based on the Scenario/Entity/Period/Currency information from the form.

Note:

Translation is performed as part of consolidation. For details on thetranslation process, see Translating Data.

To consolidate data, you must be a Service Administrator, Power User or User, andmust also have Write access to the Parent entity to be consolidated.

When you select a base entity to consolidate, the system performs the calculation forthe entity only. It does not consolidate to its parent entity.

When you select a parent entity, all descendants of the parent are also consolidated.

Chapter 17Consolidating Data

17-25

If you consolidate data for a period and the data for prior periods has not beenconsolidated, the data for the prior period is also consolidated. If you select toconsolidate the December period and any prior periods are impacted, the systemstarts consolidation from the first impacted period.

The consolidation process runs for entities that are Impacted. When the process iscomplete, the status of each successfully consolidated entity changes to OK.

You can use the Force Consolidate option to force consolidation to run on selectedcells. For example, if the consolidation process did not properly complete due to anexternal factor (a database crash, or the user stopped the process), it will leaveentities in a processing status. The system may also display an error message that a"failed consolidation needs to be reset". In these cases, you use the Force Consolidateoption, which consolidates all entities with data.

You can view the consolidation status in the Jobs console. If you want to runconsolidation but there is already a consolidation process running, you can run ForceConsolidate.

To consolidate data:


2. From the Forms list, click Data Status.

3. Select the point of view.

4. Select a cell for which to run consolidation.

5. From the Actions drop-down menu, select Business Rules.

6. From the Business Rules dialog, click Consolidate.

7. Optional: To force the consolidation process to run for all selected cells, clickForce Consolidate.

You can also run Force Consolidate from the Rules card. See Consolidation andTranslation Rules.

If running from a form, you can add Force Consolidate to the "Business Rules"option of the Form design. See Selecting Business Rules.

8. When the consolidation process successfully completes, the system displays aconfirmation message. Click OK.

9. To check consolidation status, open the Jobs console. See Viewing ConsolidationProgress.

Viewing Consolidation ProgressWhen you consolidate data, you can monitor the status of the task from the Jobsconsole. You can view pending jobs, or recent activity, including the completion status,date and time.

To view consolidation progress:


2. Click Jobs.

3. Review Pending Jobs and Recent Activity to check the status of theconsolidation.

Chapter 17Viewing Consolidation Progress

17-26

4. Click the name of the job to view Job Details.

Running a Consolidation ReportReport Overview

You can run a Consolidation report that provides a detailed audit trail of theconsolidation process. The report is available for multi-currency and single currencyapplications, and output options include HTML, PDF, or XLS format.

The Consolidation report provides the following information for a selected parententity:

• List of accounts (displayed in Columns)

• List of child companies within the selected consolidation group contributing to eachdisplayed account (displayed in Rows)

• Original reported closing balance (normally general ledger balance) for Assets andLiabilities and Equity, and current YTD balances for Profit and Loss

• Adjustments to the reported balance during consolidation, including manual journalentries, Multi-GAAP adjustments and automatic eliminations generated byIntercompany elimination and consolidation rules. These include Intercompanyeliminations, Acquisitions or Disposal entries (such as Investment Eliminations,Share Capital Eliminations, Reserves Eliminations), valuation adjustments, NCI,Equity accounting, and so on.

– Manual journals are displayed with both the journal label and description

– Automatic eliminations are displayed with Life-To-Date amount (OpeningBalance) and YTD amount on a rule-by-rule basis

– Adjustments are displayed in Entity currency of the selected Parent entity

• Net contribution of each immediate child entity for each account in the selectedgroup

• Any Variance - the total net contribution with consolidated group results

Setting Up the Report

The report displays one level of child entities for a parent entity with a multi-levelhierarchy.

For example, suppose you have the two-level entity structure shown below. APAC isthe top level group. There is one holding company (H Com), and one subsidiary (SCom), under the APAC group. There is a also a Subgroup under the APAC group, witha holding company (H LTD), and the S LTD company.

You would first run the Consolidation report using the APAC Group as the ParentEntity. The report would display results for the APAC group, including the holdingcompany (H Com), the subsidiary (S Com), and the Subgroup total.

To drill down into more detail, you would run the same report using "Subgroup" as theParent Entity, which would provide the total consolidation trail of the APAC group.

Chapter 17Running a Consolidation Report

17-27

You can display Journal details instead of a Summary amount when you use a ParentGAAP member or Parent accounts in the POV. Journal amounts are displayed on theirown accounts on a row named Manual Journals, but if you use a Parent account, theamount is displayed in the parent account in the row of the journal labels. If you selecta Parent GAAP member, all journals can be displayed label by label.

Creating the Report

To create a Consolidation report, you must be a Service Administrator or Power Userand have security rights to the data for the report.

For Number Formatting, the report can use the preferred number formatting style thatyou specify in Application Settings or User Preferences. See Specifying NumberFormatting Preferences.

To create a Consolidation report:

1. On the Home page, click Reports.

2. Click Consolidation Reports.

3. From the Consolidation Reports Jobs page, click Create.

4. From Report Filtering:

• Click on the Member Selector, select a Parent Entity for which to run thereport, and then click OK.

You can select only one entity. It must be Parent entity with at least one childentity. The report rows display all the entities in the next level under theselected parent entity.

• From the Member Selector, select one or more Accounts for which to run thereport, and then click OK.

You can select multiple accounts.

• From the Member Selector, select the Multi-GAAP dimension members forwhich to run the report, and then click OK.

You can select multiple Multi-GAAP members. This selection is only availableif the Multi-GAAP dimension is enabled for the application.

5. From the POV bar, select a Scenario, Year, and Period for the report, and thenclick OK.

6. From Display Options, edit the Report Title, or leave it blank.


17-28

If you leave the title blank, the report is generated with the "Consolidation TrailWorksheet" title.

7. For Column Display, select Account or Movement.

If you select Movement, the report displays all of the movements in level 0 underFCCS_ClosingBalance in the Columns. However, if the zero line display option is"No", the zero column will not be displayed in the report. Selecting Movementdisplays the movement details on a specific POV, and as a result the column willdisplay all the movement.

If you select multiple accounts in the POV, each account will be a sub-report. Ifyou select multiple accounts and then select the XLS output option, the XLS filewill have multiple sheets to display the result of different accounts.

The report displays the following information (if any) in Rows:

• Entity Name

• Original Balance

• Manual Journal

• Intercompany Elimination

• Auto-Elimination

• Subtotal

8. For Hierarchy Display, and Multi-GAAP Display, the report uses the defaultvalues, and you cannot change them.

9. For Zero Line Display, select Yes to display zero data lines, or leave the defaultsetting of No to suppress rows with only zero data.

10. For Member Display, select an option:

• Member Name

• Alias

• Name and Alias

11. From Report Type, select an option:

• HTML

• PDF

• XLS

12. To run the report immediately, click Run Report and then select to open or savethe report.

13. Optional: To save the report as a Job, which you can schedule to run immediatelyor at a later time, click Save as Job, enter a job name and optional description,and click Submit to save the job.

After you save a report, the report name and description are displayed in thereports list on the Consolidation Reports Jobs page.

14. To run a report that was saved as a job, use one of these methods:

• From the Consolidation Reports Jobs page, select the report from the list ofreports, select an Output Format, and click Run Report. You can downloadthe report file to a local path.


17-29

• To submit a report as a job, from the Consolidation Reports Jobs page,select the report and select an Output Format. From the Actions menu onthe right, click Submit, and then click OK.

Note that the default values for Scenario, Year, Period and Entity are thevalues you saved when you created the report. You can change the ParentEntity, Scenario, Period, or Years before submitting the job.

After submitting the report, navigate to the Job console and find the report inthe Jobs list. When the job status turns to completed, open the job and fromthe Job Details page, click View/Download to download the report.

• To schedule a report job, from the Schedule Jobs page, select the option toRun Consolidation Trail Report, then select Run Now, or schedule a timeand frequency to run it. You can select a saved report from a list of saved jobson the Job Details page.

15. Optional: To delete a report, from the Consolidation Reports Jobs page, selectthe report from the list of reports, and from the Actions menu on the right, clickDelete, then click Confirm.

Consolidation ExamplesRelated Topics

• Example 1: Reconsolidating Data from a Form

• Example 2: Consolidating Data from the Data Status Grid

• Example 3: Consolidating Data for Multiple Periods

Example 1: Reconsolidating Data from a FormIn this example, data has been loaded or entered in base entities and parent entitieshave also been consolidated. However, subsequently there has been a change to thebase entity data which causes an Impacted status at the parent entity. Consolidation islaunched from a form, after first reviewing the status grid and selecting the impactedparent entity for consolidation. After consolidation, the status changes to OK.

Chapter 17Consolidation Examples

17-30

• Reconsolidating at the intermediate parent entity only impacts the upper-levelparent entities.

• Reconsolidating the top-level parent entity consolidates all parent entities below.

Example 2: Consolidating Data from the Data Status GridThe Data Status grid contains all entities in the rows and periods in the columns. Itdisplays Calculation status, Approval status, and Lock status in the column for eachperiod. Consolidation is launched for the top parent or the intermediate parent from thegrid.

Example 3: Consolidating Data for Multiple PeriodsIn the Data Status Grid, consolidation is launched for the following periods:

• Consolidate first period (January)

• Consolidate last period (December)

• Consolidate intermediate period (April)

• Consolidate April when the January to February calculation status is OK, butMarch is impacted.

Advanced Consolidation OverviewStatutory reporting requires the presentation of consolidated financial statements.Consolidated financial statements are the "Financial statements of a group in whichthe assets, liabilities, equity, income, expenses and cash flows of the parent(company) and its subsidiaries are presented as those of a single economic entity"(IAS 27, IFRS 10). So consolidated results are the aggregation of the results of thereporting company (a legal entity) and the companies that it owns either directly orindirectly (all of which are legal companies). Notably, consolidated results are NOT theaggregation of the previously consolidated results of other holding companies.

Financial Consolidation and Close provides for a consolidation process through acombination of the Entity, Consolidation and Currency dimensions. The structure ofthe organization in the Entity dimension can be represented in a multi-level hierarchy.When this is the case, the consolidated results at any parent member that is not theimmediate parent of the legal entities, must generate the same results as if themember was the immediate parent of those legal entities.

Data is introduced to entities in an Entity Input Consolidation dimension member, atEntity Currency. Entity Input is a child of Entity Total and has two siblings, EntityConsolidation and Elimination Adjustments, but these siblings are only valid at aParent Entity level.

In a multi-currency application for all entities with one or more parents, the data ineach of the children of Entity Total is translated to Parent Currency. If the currency ofthe Parent Entity is the same as that of the Entity, then an exchange rate of 1 isapplied. Otherwise, either the Average Exchange Rate or the Ending Exchange Rateis applied depending on whether the Time Balance property of the account is Flow orBalance respectively. The translated data is posted to the Parent Currency member foreach of the base members of Entity Total.

Chapter 17Advanced Consolidation Overview

17-31

Entity Total / Parent Currency aggregated data then provides the source data forconsolidation to the contribution to the Parent entity. All data is proportionalized to theProportion Consolidation dimension member. A factor (multiplier) is applied to eachdata value. The factor applied is the Consolidation % defined for the specific Entity /Parent combination. All data at Entity Total / Parent Currency is proportionalizedexcept for the Opening Balance Movement dimension member. Opening Balance isalways carried forward from the Closing Balance of the prior reporting period for eachlevel in the Entity / Consolidation / Currency dimensions. Note that the prior periodfrom which the Closing Balance is drawn is dependent on the reporting view. For thePeriodic View, for example, Opening Balance is drawn from the Closing Balance of theprior period / month, while for the Quarterly View, Opening Balance is drawn from theClosing Balance of the prior quarter.

In addition to proportionalization, some Entity Total / Parent Currency data iseliminated or adjusted as required by consolidation logic. Any data that is required tocreate elimination or adjustment entries is multiplied by an appropriate factor andposted to the Elimination Consolidation dimension member. Multiple elimination andadjustment entries will usually be created from the Entity Total / Parent Currencysource entries, and will be grouped into balanced sets of entries, constituting aConsolidation Journal entry.

Proportion and Elimination data then aggregates to the Contribution member.Additional data can be entered to the Contribution Input member and aggregates withContribution to the top level Consolidation dimension member, Contribution Total.Contribution Total of each Entity/Parent combination then aggregates with ContributionTotal of sibling entities into Entity Consolidation/Entity Total of the parent entity.

Consolidation LogicData is proportionalized from the Entity Total / Parent Currency Consolidationdimension member to Proportion. The factor applied is always the Consolidation %defined for the Entity/Parent combination.

Data eliminated or adjusted might have the Consolidation % applied, or might use theOwnership % or Minority Interest (Non controlling interest) %. Other ratios might alsobe applied, such as the change in Ownership % or the lower of the entityConsolidation % and the Intercompany Partner Consolidation %.

The factors applied will be based on the Ownership Management of each Entity/Parentcombination for each Scenario, Year and Period. Ownership Management records theownership percentage for which a legal entity (an owning company) directly owns all orpart of another legal entity.

Ownership Management

Ownership management consists of managing global consolidation settings and theapplication of those consolidation settings to each entity hierarchy on a scenario-by-scenario, year-by-year and period-by-period basis. For details, see ManagingOwnership.

Managing Consolidation MethodsIn order to provide for advanced consolidations and eliminations, various parametersmust be established for each entity in the Entity dimension, in relation to its parent(s).Multiple consolidation methods are established to facilitate consolidation andelimination rules, each with preset or configurable parameters including:

Chapter 17Consolidation Logic

17-32

• Ownership %

• Consolidation %

• Minority (Non controlling) Interest %

A Control setting is also available to help determine the other settings for themethods.

The consolidation methods are then applied to the consolidating parent entity and itshierarchical descendants during the execution of consolidation, adjustment andelimination rules.

Financial Consolidation and Close Cloud provides several system methods:

• Holding

• Subsidiary

• Proportional

• Equity

• Not Consolidated

• Inactive

• Discontinued

Holding method

The Holding method is applied to the legal entity for which its immediate parentrepresents the consolidated results of that legal entity. The Holding method alwaysapplies an Ownership % of 100% and a Consolidation % of 100%. Control is Yes.There can be only one Holding method entity for each parent entity.

Subsidiary method

The Subsidiary method is applied to legal entities owned by the holding company andfor which the holding company exercises control. The Ownership % of a Subsidiarycompany generally ranges from 50% to 100%. Control is Yes and the Consolidation% is therefore 100%. Minority (Non-controlling) Interest equals 100% minus theOwnership %.

Proportional method

The Proportional method is applied to legal entities owned but not controlled by theholding company but requiring proportional consolidation. This generally applies toJoint Ventures. Control is No and the Consolidation % is equal to the Ownership %.

Equity method

The Equity method is applied to legal entities owned by the holding company and forwhich the holding company exercises significant influence but not control. TheOwnership % of an Equity company generally ranges from 20% to 50%. Control isNo and the Consolidation % is therefore 0%. Minority (Non-controlling) Interestalso equals 0%.

Not Consolidated method

The Not Consolidated method is applied to legal entities owned by the holdingcompany and for which the holding company exercises neither control nor significant

Chapter 17Managing Consolidation Methods

17-33

influence. The Ownership % of a Not Consolidated company generally ranges from0% to 20%. Control is No and the Consolidation % is therefore 0%. Minority (Non-controlling) Interest also equals 0%.

Inactive method

The Inactive method is reserved for future use.

Discontinued method

The Discontinued method is reserved for future use when system consolidation rulesare created for discontinued operations.

Ownership Range

Each of the methods can be assigned an Ownership % range that is used to populatethe method for an Entity parent/child combination based on the entered Ownership %for each Scenario, Year and Period. The range across the applicable methods must bea continuous range from 0% to 100%. Methods not assigned a range will not beapplied to an Entity parent/child combination by the system, but can be selected asrequired, overriding the range-based system-assigned entry.

The system methods comprising the 0% to 100% range are:

• Not Consolidated >= 0% to <=20%

• Equity >20% to <=50%

• Subsidiary >50% to <=100%

All other system methods have no range assigned.

Modifying Consolidation MethodsIf you are a Service Administrator, you can change some of the settings for systemmethods and add new methods.

To open the Manage Consolidation Methods screen:

1. On the Home page, click Application and then click Consolidation.The Manage Ownership page opens by default.

2. From the Actions menu on the Manage Ownership page, select ManageConsolidation Methods.

Changing System Method Ranges

The methods that comprise the 0% to 100% range are displayed at the top of theManage Consolidation Methods screen in ascending order of ranges, from Subsidiary(>50% to <=100%) to Equity (>20% to <= 50%) to Not Consolidated (>0% to<=20%).

You can change the ranges by increasing or decreasing the upper or lower rangesettings. For example, to change the Equity lower range from >20% to >25%, click onthe increment (Up arrow) button next to the lower range percentage field until itreaches 25%. As the lower range of the Equity method is increased, the upper rangeof the Not Consolidated method below will also change to 25%, preserving the 0% to100% continuous range.

Chapter 17Modifying Consolidation Methods

17-34

Removing Ranges from a System Consolidation Method

To remove a range from a method with a range assigned, click Actions (...) and selectRemove Range.

The range will be removed and the method will be re-positioned below the range-based methods. The upper range of the method previously below the method fromwhich the range has been removed will be adjusted to maintain the continuous 0% to100% range.

Adding Ranges to a System Consolidation Method

To add a range to a method that has no range applied:

1. Click Actions (...) in the relevant method row and select Add Range.A range from "=0" to "=0" will be added to the method and the method row will berepositioned at the bottom of the range-based methods.

Note that this will now overlap with the lowest method with a range (">=0)" and thesettings cannot be saved at this point.

2. Drag the method row and drop it onto the method row above which the methodwith the newly assigned range should be inserted.For example, drag the Proportional row and drop it onto the Equity row.

3. Adjust the upper and lower range entries of the newly positioned method asrequired.For example, change both the lower and upper range entries from 0% to 50%.Then change the operator of the upper range of the method below from <= to <.You can only save the changes when the range is continuous from 0 to 100.

Note that no other changes can be made to the system method settings. The Controland Consolidation % settings are pre-determined and cannot be modified. If the pre-set settings are not suitable, create a new method, add it to the range-based methodsand remove the range from the system method.

Adding Consolidation MethodsIf you are a Service Administrator, you can add new consolidation methods.

To add a new consolidation method:


2. Click Manage Ownership.

3. From the Actions menu, select Manage Consolidation Methods.

4. Click the Actions ellipsis (...) on a method row above or below the position inwhich the new method should be inserted.

5. Select either Add New Method Below or Add New Method Above.

If the new row is added within the range-based rows or immediately below the lastrange-based row, then a range-based new method will be added.

If the new row is inserted elsewhere, the new method will have no range assigned.

6. Required: Enter a name for the method.

Chapter 17Adding Consolidation Methods

17-35

7. The Control setting will default to Yes and the Consolidation % will default to100%. You can modify these settings as required.

If Control is changed to No, then Consolidation % will change to 0% but canthen be amended.

If Control is changed back to Yes, then Consolidation % will change to 100% butcan then be amended.

8. If the new method displays the Ownership % Range, select the operator andownership % for the lower and upper ranges. The settings of the lower range ofthe method above and the upper range of the method below will change asrequired to maintain a continuous range from 0 to 100.

9. If the new method displays the Ownership % Range and a range entry is notrequired, click Actions (...) and select Remove Range.

10. If the new method does not display a range slider bar and a range entry isrequired, click Actions in the relevant method row and select Add Range. Followthe steps described in "Adding a Range to a System Method".

11. Click Save to save your changes.

When you click Save, the settings will be validated and you must correct anyerrors before the changes are saved and you close the screen.

Note:

It is recommended that you save your changes after completing changesfor a single method rather than making multiple method changes andthen saving.

12. After you make changes to the Consolidation Methods range settings, you mustrecompute the POV-specific ownership data. A warning message will be displayedat the top of the Manage Ownership screen if the data has not been re-computed.

See Recomputing Ownership Data.

Importing and Exporting Consolidation MethodsYou can import and export Consolidation Method details.

You can import Consolidation Method data from a comma-delimited file that containsthe following columns.

• Method Name (required).

• Lower Limit Operator (required). EQ (=), LT (<), LE (<=), GT (>), GE (>=), EQ ifRangeOn= false

• Lower Limit (required). From 0 to 100. 0 if RangeOn equals false.

• Upper Limit Operator (required). Lower Limit Operator (required). EQ (=), LT (<),LE (<=), GT (>), GE (>=), EQ if RangeOn= false

• Upper Limit (required). From 0 to 100. 0 if RangeOn equals false.

• Control (required). YES or NO.

• Percent Consolidation (required). From 0 to 100 or POwn (OwnershipPercentage).

Chapter 17Importing and Exporting Consolidation Methods

17-36

• RangeOn (required). true or false.

Following is an example of Consolidation Method file contents:

Method Name, Lower Limit Operator, Lower Limit, Upper Limit Operator, Upper Limit, Control, Percentage Consolidation, RangeOn

SUBSIDIARY, GT, 70, LE, 100, YES, 100, true

NewMethod, GT, 50, LE, 70, YES, 100, true

PROPORTIONAL, EQ, 50, EQ, 50, NO, POwn, true

EQUITY, GT, 20, LT, 50, NO, 0, true

EQUITY, GT, 20, LT, 50, NO, 0, true

NOT_CONSOLIDATED, GT, 0, LE, 20, NO, 0, true

IN_ACTIVE, EQ, 0, EQ, 0, NO, 0, true

HOLDING, EQ, 0, EQ, 0, YES, 100, false

DISCONTINUED, EQ, 0, EQ, 0, NO, 0, false

To export Consolidation Methods:




4. Click Export and select a destination.

To load Consolidation Method data:




4. Click Import.

When Consolidation Method data is imported, the system validates the data to ensurethat the same conditions are applied as for on-screen entry. If any validations fail, thesystem provides an error message. If an import process fails, correct the source fileand then re-import.

Chapter 17Importing and Exporting Consolidation Methods

17-37

Recomputing Ownership DataAfter you make changes to Consolidation Methods range settings, you mustrecompute the POV-specific ownership data. A warning message will be displayed atthe top of the Manage Ownership screen if the data has not been recomputed.

To recompute Ownership data:

1. On the Home page, click Application, then Consolidation, and then clickManage Ownership.

2. Select Actions, and then select Recompute Ownership Data.

3. Select the Scenario, Year and Period(s) to recompute.

Note that recomputation will be applied to the selected period and all subsequentperiods.

Also note that if a recomputation of a POV is necessary, a consolidation of thatPOV will not complete until the Ownership data is recomputed.

4. Click Recompute.

5. From the Recomputation success message, click OK.

Note:

When the ownership data is recomputed, if the process takes longer than 60seconds, then the remainder of the process will be continued in thebackground and you can navigate to other screens if required. To view theprogress of the process, open the Jobs console.

You must also recompute ownership data after the Database is refreshed, regardlessof whether changes were made to the entity structure.

Managing OwnershipOwnership management consists of managing global consolidation settings and theapplication of those consolidation settings to each entity hierarchy on a scenario-by-scenario, year-by-year and period-by-period basis.

Ownership settings are applied to each Entity parent/child combination for eachScenario, Year and Period combination.

To access the Ownership Management screen:



3. Select the Entity parent member for which to view the hierarchy.

4. Select the Scenario, Year and Period.

5. Click the Update arrow button ( ) to update the screen to the selected POV.You can expand or collapse the hierarchy as required.

Chapter 17Recomputing Ownership Data

17-38

6. Click the Parent/Child button to view the full hierarchy.

7. Click the Parent/Legal Entity button to see the ultimate ownership settings foreach parent with each of its descendant legal entities (note that currently all baseentities are deemed to be Legal Entities).

Parent/Child View

Initially, all members will inherit the following settings:

• Ownership %: 100

• Control: Yes

• Consolidation Method: Subsidiary

• Consolidation %: 100

• Minority Interest %: 0

The only exception will be any shared entities (for example, where an entity existsmore than once in a single hierarchy). The first instance will inherit the settings notedabove while each subsequent instance will have the following settings:

• Ownership %: 0

• Control: No

• Consolidation Method: Not Consolidated

• Consolidation %: 0

• Minority Interest %: 0

Changing Manage Ownership Settings• Ownership %

You can change the Ownership % entry for any Entity parent/child combination asrequired.

After you change a percentage entry and exit the field, the system updates theControl, Consolidation Method, Consolidation % and Minority Interest % tothe entries for the method assigned to the range into which the enteredOwnership % falls.

• Control

The Control entry is assigned by the system based on the entered Ownership %and the method ranges. If required, you can change the system-assigned Controlentry.

To change the Control entry, select the required entry from the drop-down list.

If the Control entry has been changed from the system-assigned entry, the colorof the field will change to a yellow background.

To remove an override entry and revert to the system-assigned entry, fromActions (...), select Clear.

• Consolidation Method

The Consolidation Method entry is assigned by the system based on the enteredOwnership % and the method ranges. If required, you can change the system-assigned Consolidation Method entry.

Chapter 17Changing Manage Ownership Settings

17-39

To change the Consolidation Method entry, select the required entry from thedrop-down list. The methods available in the drop-down list are dependent on theOwnership % and Control settings. The Holding method will only be available forselection with 100% Ownership and Control = Yes. Other methods will beavailable for selection based on their Ownership Method Control settings. So ifControl = Yes, only those Methods with a Control setting of Yes will be displayed.To change the available Methods in the drop-down list, first change the Controlselection.

If the Consolidation Method entry has been changed from the system-assignedentry, the color of the field will change to a yellow background.

To remove an override entry and revert to the system-assigned entry, fromActions (...), select Clear.

Note that the combination of Control and Consolidation Method selected mustmatch the method settings. If Control is Yes, the selected Consolidation Methodmust be one of the methods for which Control has been defined as Yes.

• Consolidation %

The Consolidation % will be displayed based on the method settings.

You cannot modify this entry.

• Minority Interest %

The Minority Interest % will be displayed based on the method settings.


• Subsequent Changes to Ownership %

If you make changes to system-assigned Control and/or Consolidation Methodentries and then you enter a revised Ownership%, any user-selected entries willbe retained.

If the Control and/or Consolidation Method should be updated based on thenew Ownership%, then you must either clear the override entries or select newoverride entries.

Parent/Legal Entity View

After you complete the required changes in the Parent/Child view, click on the Parent/Legal Entity button to view and modify the ultimate ownership settings.

Each parent in the hierarchy selected in the POV will be listed, with a flat list of eachLegal Entity descendant of that parent. You can expand or collapse the hierarchies asrequired.

• Ownership %

The Ownership % displayed is the calculated percentage based on the series ofthe individual parent/child entries from the current parent to each legal entity. Forexample, if the Ownership % for P1.P2 is 80% and for P2.LE1 is 50%, then thecalculated cumulative Ownership % for P1.LE1 is 40% (80% * 50%).


• Control

The Control entry is assigned by the system based on the entered Ownership %and the method ranges. If required, you can change the system-assigned Controlentry. The behavior of this field is the same as in the Parent/Child view.

Chapter 17Changing Manage Ownership Settings

17-40

• Consolidation Method

The Consolidation Method entry is assigned by the system based on the enteredOwnership % and the method ranges. If required, you can change the system-assigned Consolidation Method entry. The behavior of this field is the same as inthe Parent/Child view.

• Consolidation %

The Consolidation % will be displayed based on the method settings.


• Minority Interest %

The Minority Interest % will be displayed based on the method settings.


Importing and Exporting Ownership DataYou can import and export ownership data.

Importing Ownership Data

The import ownership file must be a comma-delimited file that contains the followingcolumns:

• Scenario (required)

• Year (required)

• Period (required)

• Entity (required)

• Parent (required)

• POwn (optional). Ownership will default to 100 except for duplicate (shared)members in the same hierarchy, which will default to 0.

• Control (optional). Control will default to Yes if Ownership % is greater than 100,and to No otherwise.

• Method (optional). Method will default to Subsidiary except for duplicate (shared)members in the same hierarchy, which will default to Not Consolidated.

Chapter 17Importing and Exporting Ownership Data

17-41

Following is an example of Ownership file contents.

Scenario, Year, Period, Entity, Parent, POwn, Control, Method

Consol,FY18,Feb,[CE-0012-USD].[LE-0014-CAD],[CE-0011-EUR].[CE-0012-USD],80,,

Consol,FY18,Feb,[CE-0012-USD].[LE-0016-BRL],[CE-0011-EUR].[CE-0012-USD],50,,PROPORTIONAL

Consol,FY18,Feb,[CE-0012-USD].[LE-0017-GBP],[CE-0011-EUR].[CE-0012-USD],30,,

Consol,FY18,Feb,[CE-0012-USD].[LE-0018-EUR],[CE-0011-EUR].[CE-0012-USD],10,,

Consol,FY18,Jan,[CE-0013-GBP].[LE-0014-CAD],[CE-0011-EUR].[CE-0013-GBP],10,,

Consol,FY18,Jan,[CE-0013-GBP].[LE-0016-BRL],[CE-0011-EUR].[CE-0013-GBP],10,,

Consol,FY18,Feb,[CE-0012-USD].[LE-0016-BRL],[Entity].[FCCS_Total Geography],,NO,PROPORTIONAL

Note that Ownership % (POwn) is a required entry for all Parent/Child rows but shouldnot be entered for Parent / Legal Company rows where the Legal Company is not theimmediate child.

To import ownership data:



3. Select a Scenario, Year and Period to which to import data.Note that the Scenario, Year and Period in the import file must match the POVdisplayed.

4. From the Actions menu, select Import Ownership Data.

5. Click Browse and select the import file.

6. Click Import.

7. When you enter or import ownership settings, the system validates thedependencies between the related fields:

• The Method and Control combination must match the global settings.

• If the Method selected is Holding, then the Ownership % must be 100.

Chapter 17Importing and Exporting Ownership Data

17-42

Note:

When the ownership data is imported, if the process takes longer than 60seconds, then the remainder of the process will be continued in thebackground and you can navigate to other screens if required. To view theprogress of the process, open the Jobs console.

When ownership data is imported, it will be merged with any existing data. There mighttherefore be invalid ultimate ownership entries created. If an entity is present in morethan one branch of a hierarchy, data entered on-screen cannot be saved if thecombined ownership exceeds 100%. When loaded from a file, the ownership data isnot rejected so the combined ownership % of an entity could exceed 100%. If thisoccurs, an error message will be displayed at the top of the Manage Ownership screenin the period in which the discrepancy occurs:

Ownership data for certain Parent/Legal Company combinations are invalid.Please identify the incorrect ownership % in the Parent/Legal Company viewand then correct it inthe Parent/Child view.

In subsequent periods, a similar message will be displayed:

Ownership data for certain Parent/Legal Company combinations are invalidfor prior periods. Please identify the period and correct the period.

Navigate to the period in which the data is incorrect and select the Parent/Legal Entityview. Review the Parent/Legal Entity Ownership % entries. Any errors will behighlighted in red text. Note the entity (entities) with errors, return to the Parent/Childview and correct the necessary parent/child ownership % to ensure that the combinedownership does not exceed 100%.

Exporting Ownership Data

To export ownership data:



3. Select a Scenario, Year and Period for which to export data.

4. From the Actions menu, select Export Ownership Data.

5. Select a location in which to save the .csv file.

Note that any ownership data that was populated by the system as default data will notbe included in the export file. Only data that was entered by the user to override thedefault settings will be included in the export file. For details of default data settings,see Parent/Child View settings in Managing Ownership.

Ownership Settings Year to YearInitial default and override ownership settings will automatically be carried forwardfrom period to period within the same year but not to subsequent years. By copyingownership data, you can carry the most current settings from the last period in oneyear to the first period of the next year.

Chapter 17Ownership Settings Year to Year

17-43

Note that this option is only available in the last period of each year.

Application > Consolidation > Manage Ownership (tab) > Actions > CopyOwnership Data to Next Year

To copy ownership data to next year:



3. Select the last period of the current year in the POV.

4. From the Actions menu, select Copy Ownership Data to Next Year.

If ownership settings have not yet been copied to the first period of each subsequentyear, the entity structure will not be displayed in the subsequent years and anInformation message will be displayed:

No ownership data in the current year. Try "Copy ownership data to nextyear" action in the prior year last period.

When the ownership data is copied, if the process takes longer than 60 seconds, thenthe remainder of the process will be continued in the background the you can navigateto other screens if required. To view the progress of the process, open the Jobsconsole.

Ownership Settings in Forms and Configurable CalculationRules

You should only enter or update Ownership Settings in the Ownership Managementscreens. The settings should never be updated by direct entry or through rules.However, these settings can be displayed in data forms and can be referenced inConfigurable Calculation (Calculation Manager "insertion point") rules.

Ownership Settings in Data Forms

The POV to be used to retrieve the settings is as follows:

Select:

• Scenario

• Year

• Period

• Entity

• Account (descendants of FCCS_Drivers)

– FCCS_Consol Method (Current Period Consolidation Method)

– FCCS_Consol Method Prior (Prior Period Consolidation Method)

– FCCS_Percent Consol (Current Period Consolidation %)

– FCCS_Percent Consol Prior (Prior Period Consolidation %)

– FCCS_Percent Consol Change (Change in Consolidation % from Prior toCurrent Period)

– FCCS_Percent Ownership (Current Period Ownership %)

Chapter 17Ownership Settings in Forms and Configurable Calculation Rules

17-44

– FCCS_Percent Ownership Prior (Prior Period Ownership %)

– FCCS_Percent Ownership Change (Change in Ownership % from Prior toCurrent Period)

– FCCS_Percent Min (Current Period Minority Interest %)

– FCCS_Percent Min Prior (Prior Period Minority Interest %)

– FCCS_Percent Min Change (Change in Minority Interest % from Prior toCurrent Period)

• Data Source (descendants of FCCS_Source Entities)

– S_Parent Source (Parent entity in the primary entity hierarchy for directownership settings)

– S_<entity name> (Parent entity in a non-primary entity hierarchy for directownership settings and ancestor for ultimate ownership settings)

Fixed:

• Consolidation: FCCS_Entity Input

• Currency: No Currency

• Intercompany: FCCS_No Intercompany

• Movement: FCCS_No Movement

• Multi-GAAP: FCCS_No Multi-GAAP (if applicable)

• View: FCCS_Periodic

• Custom: No <custom name>

Ownership Settings in Configurable Calculation Rules

Ownership Settings are displayed:

• Against immediate parent in primary hierarchy

"FCCS_Consol Method" > "S_Parent Source" > "FCCS_Entity Input" > "NoCurrency" > "FCCS_Periodic" > "FCCS_No Movement" > "FCCS_No Multi-GAAP"> "FCCS_No Intercompany" > "No Product"

• Against immediate parent in non-primary hierarchy and for any Ancestor:

"FCCS_Consol Method" > "S_<Ancestor Entity Name>" > "FCCS_Entity Input" >"No Currency" > "FCCS_Periodic" > "FCCS_No Movement" > "FCCS_No Multi-GAAP" > "FCCS_No Intercompany" > "No Product"

Consolidation Method Values and Smart Lists

Consolidation methods are stored as Smart List entries. If you add a new consolidationmethod, the method name is appended to the ConsolidationMethod Smart List. Youcan see the index values associated with each consolidation method on the SmartLists "entries" tab for ConsolidationMethod. The ConsolidationMethod Smart List isavailable only when Ownership Management is enabled.

Chapter 17Ownership Settings in Forms and Configurable Calculation Rules

17-45

Advanced Consolidation RulesFinancial Consolidation and Close will proportionalize all source data, populating theProportion Consolidation dimension member. The source data is proportionalized atthe Consolidation % defined for the parent/child entity combination.

Configurable consolidation rules are used to generate additional entries to populatethe Elimination Consolidation dimension member. The Proportion and Eliminationmembers aggregate to the Contribution member. The source data comprises thesame data set as is proportionalized. See About Configurable Consolidation Rules.

There are two system consolidation rules that will always run in addition to optionalconfigurable consolidation rules. While system consolidation rules cannot be modifiedby the user, configurable consolidation rules can be created, modified, activated(deployed) and deactivated (un-deployed). Several seeded configurable consolidationrules are provided.

Chapter 17Advanced Consolidation Rules

17-46

Standard Elimination Consolidation Rules

The system standard elimination rules are based on account dimension settings andthe point-of-view of entered data. These elimination rules will reclassify relevant datato a clearing (plug) account such that the data offsets with similar data from otherentities.

So for example, Accounts Receivable data recorded by entity A with an IntercompanyPartner of entity B should offset Accounts Payable data recorded by entity B with anintercompany partner of entity A. In order for this offset to occur, the AccountsReceivable and Accounts Payable accounts must be set as "Intercompany" and acommon "plug" account must be assigned.

Data for either of these accounts is considered for elimination if the intercompanypartner of the data is a descendant of the parent of the entity currently beingprocessed. If the conditions are met, then a two-sided entry is posted to theElimination Consolidation dimension member. The first entry is a "reverseproportionalization". Data is posted to Elimination with a negative value of the originalsource data-point multiplied by a Consolidation %. The Consolidation % applied is thelower of the entity Consolidation % and the partner Consolidation %. The source datawas proportionalized (to the Proportion member) at the entity Consolidation % so thenet effect of the elimination entry is to reverse all or part of the proportionalized entry.The balancing entry is then posted to the plug account in the Elimination Consolidationdimension member. The net effect of this two-sided entry is to re-classify all or part ofthe intercompany data from the original account to the plug account.

The reclassified data is then aggregated to the Entity Consolidation member of theparent entity. If matching entries are aggregated from both the Accounts Receivableand Accounts Payable accounts then at Entity Consolidation of the parent entity, thenet data value will be zero. If mismatched amounts are reclassified and aggregated,then the data value in the plug account at Entity Consolidation will represent themismatch.

In an organization structure with shared entities, the aggregation of elimination entriesprocessed in relation to each of the branches in which the shared entity resides is notalways the result required when all instances of the shared entity are combined. For

Chapter 17Advanced Consolidation Rules

17-47

example, an entity might be owned at 40% by one immediate parent and 40% byanother, with the Equity method being applied in both cases. The lower of the entityand partner consolidation % is applied to the elimination. In this case, no eliminationsoccur because the Consolidation % for the Equity method is 0%. When the two sharedentities consolidate into their first common parent however, the combined ownership is80% and the Subsidiary method should be applied, with a Consolidation of 100%. Anadjustment is made at the first common parent at which the aggregated results of thelower level eliminations are incorrect for the current consolidation method. Thisadjustment is made in the Entity Elimination Adjustments Consolidation member of thefirst common parent.

Opening Balance Ownership Change Consolidation Rules

Ownership Management introduces the ability to change the Ownership % and theConsolidation Method for an Entity/Parent combination on a period-by-period basis.With a change in Ownership % and/or Consolidation Method, the Consolidation % canalso change from period-to-period.

Opening Balance is always carried forward from Closing Balance of the prior period foreach Consolidation dimension member. Opening Balance is not proportionalized.Opening Balance therefore represents the prior period proportionalization at the priorperiod Consolidation %. All other movements aggregating to Closing Balance areproportionalized at the current period Consolidation %.

In order to ensure that the Closing Balance of the current period reflects theConsolidation % of the current period, an adjustment is posted to reflect the change inConsolidation% of the unconsolidated prior period Closing Balance. If the change inthe Consolidation % is greater than zero, the entry is posted to "Acquisitions", and ifthe change is less than zero, the entry is posted to "Disposals".

Note that the seeded Movement members "FCCS_Mvmts_Acquisitions" and"FCCS_Mvmts_Disposals" are for system use only and any data entered to thesemembers will be cleared. Members "FCCS_Mvmts_Acquisitions_Input" and"FCCS_Mvmts_Disposals_Input" can be used for data entry.

About Configurable Consolidation RulesThe purpose of the consolidation rules in populating the Elimination member is tocreate journal entries from the source data in order to re-classify, adjust and eliminatereported data. When these journal entries are applied to financial accounts (BalanceSheet and Income Statement), the journal posting results should generate balancedentries.

Consolidation rules provide for the creation of "rule-sets". Each rule-set can containone or more rules. The rule-set represents a journal and each rule represents onejournal posting entry (a single journal detail row).

For details on creating rule-sets and rules, see these topics:



Watch the following video for information on configurable consolidation rules:

Managing Configurable Consolidation Rules

Chapter 17About Configurable Consolidation Rules

17-48


Rule-Sets

Several parameters can be applied to the rule-set:

1. Condition

A condition under which the rule-set is executed

The condition can be based on:

• The consolidation method applicable to the entity dimension parent/childcombination being processed

• Some combination of dimension members or dimension member attributes -the dimensions applicable for a rule-set condition are the "page" dimensions:Scenario, Year, Period, Entity (S/Y/P/E) and the "sub-cube" dimensions:Account, Intercompany, Movement, Data Source, Multi-GAAP (if applicable),plus any user-created custom dimensions

• A data value

The condition defaults to "Always run".

2. Factor

A factor to which to apply to the source data values

Source data is multiplied by the selected factor, the entity or partnerConsolidation %, Ownership %, Minority Interest %, change from period-to-period of any of these percentages, the lower of Entity or Partner values of any ofthese percentages, the prior period value of any of these percentages or a specificratio/percentage.

3. Source Data-Set

The source data-set that is to be processed by the consolidation rule-set defaultsto the “page” dimension members of Current Scenario, Current Year, CurrentPeriod, level 0 members of the “FCCS_Entity Total” Consolidation dimensionmember and “Parent Currency”. The source data-set can be modified to a differentPOV within certain limitations. In general, the source data-set cannot be a data-setthat will be impacted by the posting of data-points by the current consolidationprocess. See Creating Consolidation Rule-sets for further details.

4. Scope

A source data POV to filter the data-set to which to apply the rule-set on adimension by dimension basis. The default source POV includes all level 0members of the "sub-cube" dimensions: Account, Intercompany, Movement, DataSource, Multi-GAAP (if applicable), plus any user-created custom dimensions.

One or more selections of base (level 0) members can be made for sub-cubedimensions, including lists. The sub-cube dimension selections in the Source POVfilters and limits the execution of the rule from the total data set to only those data-points that fall within the sub-cube filter definitions. So the Source POV could, forexample, specify one single account to which to apply the rule-set. If a dimensionis not added to the Source POV, then all base members of that dimension areincluded in the data-set.

The page dimensions of Scenario, Year, Period and Entity can also be added tothe Scope of the rule-set. Filtering on a page dimension will prevent the rule-setfrom running against any dimension members not included in the scope of therule-set regardless of whether the member is in-scope for the consolidation


17-49

process. Note that this method of excluding page dimension members from thescope of the consolidation is more efficient than using the condition field, but willnot cater for selections that are conditional on more than one dimension.

5. Partner Elimination

If the Partner Elimination feature has been enabled for the application, and if oneor more rules within the rule-set is to write a Partner Elimination entry, click on theCreate Partner Elimination button. When selected, three dimensions will beadded to the scope of the rule-set if not already added by the rules-writer.

The Factor entry and Scope are optional at the rule-set level, but if defined, then thesesettings will be inherited by each of the rules within the rule-set.

Rules

One or more rules can be created within the rule-set. The Condition, Factor and Scopecreated at the rule-set level will be inherited by each rule and cannot be modified.

If the rule-set has been defined as a Partner Elimination rule-set, then individual rulescan then be set to write Partner Elimination data. Not all rules in a Partner Eliminationrule-set must write partner eliminations.

In addition to parameters inherited from the rule-set, additional parameters can bedefined for each rule:

1. A factor to which to apply to the source data values (if not defined at the rule-setlevel)

2. A Processing option of "Add" or "Subtract"

3. One or more Target "Redirection" dimension members

One or more target redirection members can be defined on a dimension-by-dimension basis (one redirection entry per dimension) for sub-cube dimensions. Ifno target redirection dimension members are defined, then the source data will bewritten to the target Elimination Consolidation dimension member using thesource dimension members. If a redirection member is defined, then the sourcedata will be written using the defined redirection member.

Note that if the "#Source POV entity#" entry is selected for redirection of theIntercompany dimension, then the redirection will be applied to the Intercompany"ICP_<Source POV Entity>" member.

Also note that if the Source POV Entity has not been designated as a validintercompany member (and the "ICP_<Source POV Entity>" member does notexist), then the redirection will be ignored and the data will be written to the SourcePOV Intercompany member.

If the rule is a Partner Elimination rule, the redirection for the Entity, Intercompanyand Data Source dimensions will be pre-set and cannot be changed.

4. Target "Redirection" conditions

Multiple target redirection members can be specified using one or more conditionsto determine when each redirection member is to be applied. A "condition block"can be created in the form of:

If <condition1> Then

<redirection member 1>

ElseIf <condition2>


17-50

<redirection member 2>

Else

Same as Source

End

If a condition is met during the execution of the rule, then the data is written usingthe redirection member of the source POV member as defined.

The target redirection condition allows multiple redirection members to be definedfor different conditions. The condition can be based on the dimension members ofthe source data point or a data value.

Example 1:

Source POV = Base members of Balance Sheet accounts

Account redirection 1 condition = Account is base member of the Net Incomeaccount

Account redirection 1 = Equity Company Income account

Account redirection 2 = Investment Elimination account

The above example would result in:

If the source account is a base member of the Net Income account then

Redirect to the Equity Company Income account

Else

Redirect to the Investment Elimination account

End If

Example 2:

Source POV = Base members of Balance Sheet accounts

Account redirection 1 condition = Account is base member of the Net Incomeaccount

Account redirection 1 = Equity Company Income account

Account redirection 2 condition = Account is base member of theComprehensive Income account

Account redirection 2 = Investment Elimination account

The above example would result in:

If the source account is a base member of the Net Income account then

Redirect and write to the Equity Company Income account

Else if the source account is a base member of the Comprehensive Incomeaccount then

Redirect and write to the Investment Elimination account

Else


17-51

Write to the source dimension member

End If

Managing Consolidation Rule-sets and RulesYou can create new rule-sets and rules, or copy existing items, either seeded systemrule-sets or user-created rule-sets.

To manage consolidation rule-sets and rules:


2. From the Consolidation Process page, select the Consolidated tab, and thenselect Configurable Consolidation.

Seeded system rule-sets are initially available in an un-deployed state. These rule-setscan be deployed or un-deployed as required. You can view seeded rule-sets andrules, but you cannot modify them. You can, however, copy a seeded rule-set andthen modify and deploy the copy.

See these topics:



Creating Consolidation Rule-setsYou can create new rule-sets or copy existing items, either seeded system rule-sets oruser-created rule-sets.

Watch the following video for information on creating consolidation rule-sets:

Creating Rule-Sets for Configurable Consolidations

To create a consolidation rule-set:



Chapter 17Managing Consolidation Rule-sets and Rules

17-52


3. Click the Create Rule Set icon.

4. From the new Rule Set screen, enter the Name of the rule-set.

5. Optional: Tap description to enter the description of the rule-set.

6. The Condition determines the conditions under which the rule-set will executeand will initially display "<None>Always Run". Click the link next to Condition tochange the condition, then select an option:

• Select one or more of the conditions in the drop-down list.

• Select the Advanced option to add condition blocks, or to group rule-setconditions.

To add condition blocks, see Adding Condition Blocks.

To group conditions, see Grouping Conditions

• For Factor, set a rule-set factor to which to apply to the source data valuewhen calculating the data to be written to the destination.

7. If the Partner Elimination feature has been enabled for the application, and if oneor more rules within the rule-set is to write a Partner Elimination entry, click on theCreate Partner Elimination button. The Entity, Intercompany and Data Sourcedimensions will be added to the Scope of the rule-set.

• Entity

“Descendants of Total Geography” will be populated by default but can bemodified

• Intercompany

– “#Sibling/Descendant of a Sibling#” will be populated and cannot bechanged

– Only data-points with an Intercompany Partner entry of a sibling ordescendant of a sibling of the current entity being processed can generatePartner Elimination entries

• Data Source

Level 0 descendants of Total Data Source will be populated by default andcan be changed

8. For Rule-set Scope, specify members to restrict the data set to which the rule-setwill be applied.

9. To save the rule-set, click Save and Close, or to continue creating rule-sets, clickSave and Continue.

Note:

Best practice: Where possible, exclude dimension members not required inthe source data set using the Rule-set Scope settings instead of using theCondition. This design technique will provide for better processingperformance. The Condition logic might be required for complex or multi-dimensional conditions but should be minimized where possible.

Chapter 17Creating Consolidation Rule-sets

17-53

Adding Condition Blocks

When you create a rule-set and click the Advanced Condition dialog box, you can clickthe Add (+) icon to add a condition block, or click the Delete (x) icon to remove acondition block.

Each condition block will initialize with these four fields:

• Dimension

Select a metadata dimension for which to set a condition, or select Data Value toapply a data value condition.

• Attribute

If you selected a metadata dimension for the <Dimension> field, select theattribute of that dimension required in the condition. The Member Name attribute isavailable for all dimensions. The Entity and Intercompany dimensions also provideOwnership settings such as Method, Consolidation %, Ownership %, MinorityInterest %, "Change" percentages, "Lower of entity and partner" percentages and"Prior period" percentages. The "Change" selections provide the change in theattribute from the prior period to the current period.

If you selected Data Value for the <Dimension> field, you can select a partial POVto define the data-point for which to apply the condition. If no entries are selected,then the Source POV is used as the data-point definition. A member of eachdimension can be selected in order to define a data-point other than the SourcePOV.

• Operator

Select the condition operator. The available operators will depend on the<Dimension> and <Attribute> selections. Valid operators include:

– Equals

– Does Not Equal

– Is Greater Than

– Is Not Greater Than

– Is Less Than

– Is Not Less Than

• Value/Method

Enter or select the value required against which the condition operator is applied.

If you selected Member Name in the <Attribute> field, the Member Selector for thatdimension will be available from which to select an entry or a "consolidationstring". Consolidation strings are available for the Entity and Intercompanydimensions. You can select these strings from the Member Selector by clicking theMembers link at the bottom of the Select Members dialog box and then selectingConsolidation Strings. See "Consolidation Strings".

• If you selected an Entity or Intercompany Consolidation Method, then a list ofmethods will be available.

• If you selected Consolidation %, Ownership %, Minority Interest % or Data Value,then you can enter a numeric value.


17-54

After you create a condition block, to add another condition, click the Add (+) icon. Theconjunction between the conditions is "And" by default, but you can change it to "Or","And Not", or "Or Not".

Grouping Conditions

After you add multiple condition blocks, you can group selected conditions. Groupingconditions determines required combinations of conditions.

To group conditions:

1. Click on the row of the first condition to include in the grouping, then hold downCtrl and select the required adjacent conditions.

2. After you select all adjacent conditions for the grouping, click and selectGroup from the drop-down list.

For example, if Condition A and Condition B are grouped, and Condition C andCondition D are grouped:

Then the condition is applied as:

(Condition A and Condition B) or (Condition C and Condition D).

In this case, the rule-set will execute if conditions A and B are met, or if conditions Cand D are met.

Note that only "Equals" and "Does Not Equal" are available for the Years and Perioddimensions. You cannot apply "before" or "after" logic. Use a list or multiple blockconditions to apply this type of logic.

Example 1:

Years | Member Name | Equals | FY16, FY17, FY18

Example 2:

Period | Member Name | Equals | Mar, Jun, Sep, Dec

Example 3:

Years | Member Name | Does Not Equal | FY16, FY17

Or

Years | Member Name | Equals | FY17

And

Period | Member Name | Equals | Jul, Aug, Sep, Oct, Nov, Dec

Rule-set Factor

The rule-set factor will by default display None. If this entry is retained, then the factorshould be set in each of the related rules. If this entry is changed, then the factorselected will apply to all rules in the rule-set.

Select one of the options in the first drop-down box:

• Current

• Change In


17-55

• Lower of entity or partner

• Specific %

• Prior

Then select one of the options in the second drop-down box:

• Entity Consolidation %

• Entity Ownership %

• Entity Minority Interest %

• Partner Consolidation %

• Partner Ownership %

• Partner Minority Interest %

Rule-set Source Data-set Definition

The source data-set to which the rule-set will be applied is by default drawn from theEntity Total data of the current Scenario, Year, Period and Entity. For a multi-currencyapplication the data will be Parent Currency. From within this data-set, the scope ofthe data to be processed by the rule-set can be further filtered by setting the scope(see “Setting the scope of the data-set”).

The data-set can be taken from a different scenario, year, period or consolidationmember, and for a multi-currency application from either Parent Currency or EntityCurrency. At present, the data must be taken from the current entity.

Changing the source POV for the Data-set

For each of the dimensions for which the source data-set can be drawn:

Scenario:

• Current Scenario (default selection)

• A specific scenario

• #Previous Scenario#

If #Previous Scenario# is selected then the scenario from which the first periodOpening Balance carry forward is drawn will be used during rules execution.

Year:

• Current Year (default selection)

• A specific year

• Current…

If Current… is selected, also select an offset. The offset number can be from 0 (nooffset) up to one less than the number of years in the application (so -9 for a 10-year application). The offset number will count backwards from the current yearbeing processed and draw the data set from that year. For example, in Apr FY18,an offset of -2 will draw data from Apr FY16.

The combination of Year offset and Period offset allows an offset of up to the totalnumber of periods in the application less one.

If the Year and / or Period offset selections, when combined with the current POV forwhich the consolidation is being run, cause the source POV to be outside of the limits


17-56

of the application (that is, a period or year before the first period and year defined inthe application), then the rule-set will not execute for that current POV. This will benoted in the Job Console but will not cause the consolidation to fail.

Entity:

Currently, only the Current Entity is available.

Consolidation:

Entity Total (default)

• Entity Input

• Entity Elimination Adjustment

• Entity Consolidation

• Proportion

• Elimination

• Contribution

Note that the Consolidation dimension members Proportion, Elimination orContribution cannot be selected unless a different Scenario is selected, or if a Year orPeriod non-zero offset is selected. This restriction is intended to ensure that the data-set to be used as the source of the rules is not dependant on the results of the rules.

Currency:

• Parent Currency (default)

• Entity Currency

Note that this selection is not available for a Single-Currency application.

Also note that for multi-currency applications, Entity Currency is not available ifProportion, Elimination or Contribution has been selected for the Consolidationdimension member.

Setting the Scope of the Data-set

Click the Add (+) icon below the Scope bar to add a dimension to the Source POVfilter definition. Select one of the available dimensions. Select the Member Selector

icon, , from the right side of the new dimension row or type in the name of therequired dimension. From the Member Selector, select one or more members or lists.

Specifying members in the Source POV will restrict the data-set to which the rule-setwill be applied. The Entity and Intercompany dimensions also provide a ConsolidationString selection for #Legal Company# and the Intercompany dimension provides for#Any ICP that is a descendant of the current parent#. See Consolidation Strings.

The rule-set Source POV will be inherited by any rule that is created within the rule-set. You cannot edit the inherited Source POV in the individual rules.

Creating Consolidation RulesTo create a consolidation rule:


Chapter 17Creating Consolidation Rules

17-57


3. Select the rule-set within which to create the rule.

All rules must be in a rule-set.

4. Click the Create Rule (+) icon.

5. In the new rule screen, enter the Name of the rule.

6. Optional: Tap description to enter the description of the rule.

7. Condition: This is inherited from the rule-set and cannot be modified in the rule.

8. For Factor: If the factor was set at the rule-set level, then that condition isinherited and cannot be modified in the rule. If the factor was not set at the rule-setlevel, then you should enter the factor for each rule.

Select one of these options in the first drop-down box:

• Current

• Change In

• Lower of entity or partner

• Specific %

• Prior

Then select one of the options in the second drop-down box:

• Entity Consolidation %

• Entity Ownership %

• Entity Minority Interest %

• Partner Consolidation %

• Partner Ownership %

• Partner Minority Interest %

9. For Processing Option, select Add or Subtract from the drop-down list. TheRule Processing option specifies whether to add or subtract the calculated datavalue to any data value already posted to the destination. See Rule ProcessingOption.

10. Rule Source POV: This is inherited from the rule-set and cannot be modified inthe rule.

11. Optional: To define a redirection of the data, click Redirect Members. See RuleRedirection.

12. Optional: If Partner Eliminations has been enabled for the rule-set, after selectingRedirect Members, select Enable Partner Elimination.

13. To save the rule, click Save and Close, or to continue creating rules, click Saveand Continue.

Rule Processing Option

The Add option will post the processed data to the Elimination Consolidationdimension in the same manner as proportionalization, applying the factor to the sourcedata value. The Subtract option will also apply the factor to the source data value butwill post the "reverse" value.


17-58

For example, to "reverse" the effect of proportionalization of an account, you wouldapply the Subtract option.

Note than when a data-point is "redirected" to a different account member, the accounttype is taken into account when the posting is processed. For example when:

• A positive amount sourced from a Revenue account is not redirected, or isredirected to a different Revenue account with the Add processing option, then apositive amount is posted to the Revenue account.

• A positive amount source from a Revenue account is not redirected, or isredirected to a different Revenue account with the Subtract processing option,then a negative amount is posted to the Revenue account.

• A positive amount sourced from a Revenue account is redirected to an Expenseaccount with the Add processing option, then a negative amount is posted to theExpense account.

• A positive amount sourced from a Revenue account is redirected to an Expenseaccount with the Subtract processing option, then a positive amount is posted tothe Expense account.

• A negative amount sourced from a Revenue account is redirected to an Expenseaccount with the Add processing option, then a positive amount is posted to theExpense account.

• A negative amount sourced from a Revenue account is redirected to an Expenseaccount with the Subtract processing option, then a negative amount is posted tothe Expense account.

The general rule is:

• Multiply the source amount by -1 if the "normal sign" of the Source Account Typeis different than the "normal sign" of the Target Account Type.

• If the selected Processing Option is Subtract, multiply again by -1.

The "normal sign" of the Account Types are:

• Revenue - Credit balance (-)

• Expense - Debit balance (+)

• Asset - Debit balance (+)

• Liability - Credit balance (-)

• Equity - Credit balance (-)

• Saved Assumption - Balance (+)

The rule Source POV is inherited from the rule-set and cannot be modified in the rule.

Rule Redirection

When the data defined by the Source POV is processed, the data values are multipliedby the factor and posted to the Elimination Consolidation dimension member. If noredirection is defined, then the POV of the Destination will be the same as the Source(other than the Consolidation member). The posting of the data can, however, beredirected to a different member of one or more of the sub-cube dimensions: Account,Intercompany, Movement, Data Source, Multi-GAAP (if applicable), or any user-created Custom dimension.

To define a rule redirection:


17-59

1. From the Create Rule screen, click Redirect Members.

The Source POV section of the screen will be split into the inherited Source POVon the left, and a Redirection column on the right.

2. In the Redirection column, the default redirection member is displayed as "Sameas source". You can add a redirection member by selecting a base member of thedimension from the member selector.

When posting to the Elimination Consolidation dimension member, the member fromthe Source POV will be replaced by the selected redirection member.

The Intercompany dimension also provides a Consolidation String selection for#Source POV Entity#. If you select this string, then the Intercompany member usedfor redirection will be the Intercompany equivalent of the Entity in the Source POV("ICP_<Source POV Entity>"). See Consolidation Strings.

You can apply different redirect members based on one or more conditions.

To add a condition to a redirection dimension:

1. Click the Add (+) icon at the right side of the column.

2. Create a condition to which to apply to a data point in order to determine theredirection.

• If the condition is met, then the data is posted to the first redirection member.

• If the condition is not met, then the data will be posted to the secondredirection member.

Select the redirection members from the Member Selector or leave as "Sameas Source", as required.

3. Continue to add conditions and redirection members as required by selecting theAdd (+) icon, or remove existing conditions by selecting the Delete (x) icon.

The conditions for each of the redirection entries are created using the same methodas the rule-set condition. See Creating Consolidation Rule-sets.

Partner Eliminations

If the rule is to write data to a partner, first select the Redirect Members button andthen select Enable Partner Elimination. For a Partner Elimination rule, the redirectionentry for the Entity, Intercompany and Data Source dimensions will pre-set and cannotbe changed.

Entity redirection

#Source POV Intercompany#

Intercompany redirection

#Source POV Entity#

Data Source redirection

Partner Eliminations

When the entity is processed and an eligible data-point is encountered, the PartnerElimination rule will write a data-point to the Elimination consolidation member of asibling of the entity being processed. If the intercompany partner itself is a sibling ofthe current entity, the data will be written to the partner but if not, will be written to anyancestor of the partner that is a sibling of the current entity. The POV of the data-point


17-60

written will include the entity of the source data-point as the intercompany partner andwill always be written to the Partner Eliminations Data Source member(“FCCS_Partner Eliminations”).

When Partner Elimination data is written to the Elimination member of a sibling, thecalculation status of that sibling is not impacted in the current period, but is impacted infuture periods. When the entity creating the partner elimination entry is re-consolidated, any data written to any sibling from that entity is first cleared and then re-posted as required. The posting and clearing of data in the Partner Elimination DataSource member of the Elimination Consolidation member is in effect “owned” by theentity that writes that data (identified by the intercompany entry) and not by the entityin which the data resides.

Note that if the partner of a data-point exists in multiple places in the entity hierarchy(that is, shared ownership) then one source data-point might generate multiple partnerelimination entries, at a single generation of the source entity or at multiplegenerations.

Watch the following video for information on creating consolidation rules:

Creating Consolidation Rules

Consolidation StringsThe following sections list the consolidation strings that can be used in consolidationrule-sets and rules. Consolidation strings provide logical references and can beselected from the dimension member selector.

To include consolidation strings:

1. Create a rule or rule-set.

See Creating Consolidation Rule-sets and Creating Consolidation Rules.

2. From the bottom of the Member Selector dialog box, select Members.

3. From the drop-down options, select Consolidation Strings, then select a string.

• #Legal Company#

The Legal Company string determines whether the current Entity or Intercompanymember represents a Legal Company. All base entities are Legal Companies.

Future enhancements will allow for the addition of Reporting Unit entities below aLegal Company parent entity.

You can use the Legal Company string for the Entity or Intercompany dimensionsin a rule condition or in the Source POV.

• #Any ICP that is a descendant of the current parent#

This string can be used in the Intercompany dimension Source POV and restrictsthe in-scope data-set to those data-points that have an Intercompany dimensionentry that represents a descendant of the parent entity of the Entity currently beingprocessed.

• #Source POV Entity#

Chapter 17Consolidation Strings

17-61


This string can be used in the Intercompany dimension redirection. TheIntercompany member used to write the data will be the Intercompany equivalentto the Entity in the Source POV ("ICP_<Source POV Entity>").

If the Source POV Entity has not been designated as a valid Intercompanymember (and the "ICP_<Source POV Entity>" member does not exist), then theredirection will be ignored and the data will be written to the Source POVIntercompany member. If the Source POV Intercompany member is a parentmember, then the rule and consolidation process will fail.

Viewing Rule-SetsFrom the Configurable Consolidation page, you can view rule-sets and rules.

You can also deploy and undeploy rule-sets, and duplicate or delete rule-sets andrules. See these topics:

• Deploying and Undeploying Rule-Sets

• Duplicating and Deleting Rule-Sets

To access the Configurable Consolidation page:



To view the Rule-sets by Status, select the appropriate option from the Status drop-down list:

• All Rules

This option displays all rule-sets. If a rule-set has been deployed and thenchanged but not yet redeployed, the Changed status icon is displayed next to therule-set name.

You can open and view any of the displayed rule-sets.

System rule-sets: You can view, duplicate, deploy and undeploy.

Non-system rule-sets and rules: You can view, modify, duplicate, deploy andundeploy.

If you open a Changed rule-set, the changes not yet deployed are displayed andyou can make additional changes.

If you open and modify a deployed and not changed rule-set, a "changed" copy ofthe rule-set is created when saved.

• Deployed

This option displays all deployed rule-sets. If a rule-set has been deployed andthen changed but not yet redeployed, the Deployed status icon is displayed next tothe rule-set name and the details of the deployed rule-set are displayed.

You cannot make any changes to deployed rule-sets in this view. To modify a rule-set that has been deployed, open the rule set in the All Rules view.

You can undeploy rule-sets from this view.

• Undeployed

Chapter 17Viewing Rule-Sets

17-62

This option displays all rule-sets that are not deployed. If a rule-set is undeployedand then changed, the status icon remains unchanged.

You can deploy rule-sets from this view.

• Changed After Deploy

This option displays all rule-sets that have been deployed and then changed butnot yet redeployed. The details of the rule-sets and rules reflect the changes madesince the previous deployment. You can make additional changes in this view.

You can deploy changes to rule-sets and rules from this view. If the changes arenot deployed, then the previously deployed version will remain active.

Deploying and Undeploying Rule-SetsTo deploy rule-sets:



There are three possible "states" for any rule-set:

• A rule-set that has been created but never deployed is "Undeployed" (identified bya blue circle)

• A rule-set that has been created and deployed is "Deployed" (identified by a greencircle with a check-mark)

• A rule-set that has been created and deployed and then changed is "Changed, yetto be redeployed" (indicated by a yellow triangle with an exclamation mark)

Any rule-set that has been deployed and then changed, but not yet redeployed,also exists in its original deployed state. When the changed rule is deployed, thenit replaces the previously deployed version.

Note:

• The background "gear" icon indicates that it is a system Rule-set.

• The background "person" icon indicates that it is a user-created Rule-set.

To deploy an undeployed or changed rule-set:

1. Select the rule-sets by selecting the checkbox to the left of the rule-set name.

Chapter 17Deploying and Undeploying Rule-Sets

17-63

You cannot deploy or undeploy individual rules.

2. Click Deploy or Undeploy.

Duplicating and Deleting Rule-SetsFrom the Configurable Consolidation page, you can view, duplicate and delete rule-sets and rules.

To access the Configurable Consolidation page:



Duplicating Rule-Sets

To duplicate a rule-set, or rule within a rule-set:

1. From the Configurable Consolidation list of rule-sets, select the row and click .

2. To duplicate a rule-set or rule, click Duplicate.

3. To duplicate both a rule-set and the rules within that rule-set, click Duplicate withRules.

Note:

To change the name of a rule-set or rule, the rule-set must be undeployed.

Changes to other fields do not require that the rule-sets be undeployed.

Deleting Rule-Sets

To prevent a referential integrity problem with configurable consolidation rules fromoccurring in the application, Financial Consolidation and Close verifies and preventsthe deletion of any metadata member that is referenced in the rule.

When you delete a dimension member from the application, if the member isreferenced in a configurable consolidation rule, the system displays a Failure error andthe member is not deleted.

To delete a rule-set, or rule within a rule-set:

1. From the Configurable Consolidation list of rule-sets, select the row and click .

2. To delete the item, click Delete.

If the rule-set or rule has been deployed and then changed, both the deployed andchanged items will be deleted.

Seeded Consolidation RulesSeveral seeded consolidation rule-sets provide generic Ownership Eliminationadjustments.

Chapter 17Duplicating and Deleting Rule-Sets

17-64

You cannot modify these rule-sets. The rule-sets are initially un-deployed, but can bedeployed or duplicated, and the copy can be modified and deployed.

Alternatively, you can create new rule-sets and rules. See Creating ConsolidationRule-sets and Creating Consolidation Rules.

Nine seeded system rule-sets have been defined:

• Investment

• Investment PP

• Owner's Equity (Subsidiary/Proportional)

• Owner's Equity (Subsidiary/Proportional) PP

• Owner's Equity (Equity)

• Owner's Equity (Equity) PP

• Owner's Equity (Holding)

• Net Income (Subsidiary)

• Net Income (Equity)

The first six rule-sets (Investment, Investment PP, Owner's Equity (Subsidiary/Proportional), Owner's Equity (Subsidiary/Proportional) PP, Owner's Equity (Equity),and Owner's Equity (Equity) PP) provide adjustment/elimination entries between theInvestment of a holding company in a subsidiary and the Owner's Equity of that ownedcompany, whether consolidated by the Subsidiary method (recognizing Minority/Non-Controlling Interest), the Proportional method or the Equity method.

The Goodwill - Offset asset account is used as the clearing/plug account between theinvestment and owner's equity adjustments. If the holding company investmentamount and the owned company pre-acquisition Owner's Equity amount(s) do notmatch, the difference will be recorded as Goodwill.

The Owner's Equity (Holding) rule-set prepares the Owner's Equity data of a Holdingcompany for subsequent elimination if the Holding company becomes a subsidiary at ahigher level in the organization structure.

Net Income (Subsidiary) and Net Income (Equity) rule-sets record the ongoing NetIncome impact for a Subsidiary (Minority interest) and an Equity company (Equityincome).

Pre-conditions for the Seeded Rule-Sets

The seeded rule-sets use the Intercompany dimension to track the legal entity(currently the base entity) to which elimination entries are related. All base entitiesmust therefore be designated as Intercompany entities (select the "ICP_Entity_Yes"attribute in the Entity dimension level 0 members) so that they exist in theIntercompany dimension in the form "ICP_<entity name>".

The data entered for Investment in Subsidiaries in the Holding Company must includean Intercompany dimension entry that identifies the owned entity. Data entered toOwner's Equity accounts do not need an Intercompany entry.

Watch the following video for information on seeded consolidation rules:

Equity Pickup

Chapter 17Seeded Consolidation Rules

17-65


Investment Rule-SetThe Investment rule-set consists of two rules/journal detail lines.

This rule-set transfers current period Investments to Goodwill for all Intercompanypartners representing siblings. The Goodwill entry will offset with the elimination ofOwner's Equity from the partner, leaving a net Goodwill value (if any).

Data posted to the Investment in Subsidiaries ("FCCS_Investment in Sub") accountmust include an Intercompany partner representing the company in which theinvestment is held in order for this rule to execute. The account can be set as an"Intercompany" account through metadata maintenance but no "plug" account shouldbe selected. If a "plug" account is entered to the Investment in Subsidiaries account,then both the Standard Eliminations and Investment rule will execute, doubling theelimination.

Table 17-8 Investment (Rule-set)

Entry Description

Condition( (Entity Current Method = Holding Or EntityCurrent Method = Subsidiary Or Entity CurrentMethod = Proportional And FCCS_Total DataSource < > 0 And Intercompany Consolidation> 0 Or Intercompany Consolidation % Change< > 0 Or Partner Current Method = Equity)

Factor Current \ Entity Consolidation %

Dimension Source POV

Account "FCCS_Investment in Sub"

Intercompany #Any partner that is a descendant of thecurrent parent#

Movement Base of "FCCS_ClosingBalance" Excluding"FCCS_OpeningBalance"

Data Source Base of "FCCS_TotalDataSource"

Table 17-9 Investment - Reverse Proportionalize (Rule)

Entry Description Redirect Target Member

Condition inheritedFactor inheritedProcessing Option Subtract

Dimension Source POVAccount inheritedIntercompany inheritedMovement inheritedData Source inherited "FCCS_Intercompany

Eliminations"


17-66

Table 17-10 Investment - Goodwill Offset (Rule)


Condition inheritedFactor inheritedProcessing Option Add


Account inherited "FCCS_Goodwill Offset"

Intercompany inheritedMovement inherited IF: "FCCS_Total Movements"

> "FCCS_Total Data Source"> 0

THEN:"FCCS_Mvmt_Acquisition_Input"

ELSE: "FCCS_MvmtDisposal_Input"

Data Source inherited "FCCS_IntercompanyEliminations"

Investment PP Rule-SetThe Investment PP rule-set consists of two rules/journal detail lines.

This rule-set transfers accumulated prior period (or more specifically current OpeningBalance) Investments to Goodwill for all Intercompany partners representing siblings.The Goodwill entry will offset with the elimination of Owner's Equity from the partner,leaving a net Goodwill value (if any).

Data posted to the Investment in Subsidiaries ("FCCS_Investment in Sub") accountmust include an Intercompany partner representing the company in which theinvestment is held in order for this rule to execute. The account can be set as an"Intercompany" account through metadata maintenance but no "plug" account shouldbe selected. If a "plug" account is entered to the Investment in Subsidiaries account,then both the Standard Eliminations and Investment rule will execute, doubling theelimination.

Table 17-11 Investment PP (Rule-set)

Entry Description

Condition (Entity Current Method = Holding Or EntityCurrent Method = Subsidiary Or Entity CurrentMethod = Proportional And FCCS_Total DataSource < > 0 And Intercompany Consolidation> 0 And Intercompany Prior Consolidation % =0)

Factor Current \ Entity Consolidation %


Account "FCCS_Investment in Sub"

Intercompany #Any partner that is a descendant of thecurrent parent#


17-67

Table 17-11 (Cont.) Investment PP (Rule-set)

Entry Description

Movement "FCCS_OpeningBalance


Table 17-12 Investment PP- Reverse Proportionalize (Rule)



Dimension Source POVAccount inheritedIntercompany inheritedMovement inherited IF: Intercompany Ownership

% Change > 0




Table 17-13 Investment PP- Goodwill Offset (Rule)





Intercompany inheritedMovement inherited

IF: "Intercompany Ownership% Change > 0




Owner's Equity (Subsidiary/Proportional) Rule-SetThe Owner's Equity (Subsidiary/Proportional) rule-set consists of three rules / journaldetail lines.


17-68

This rule-set applies the current period Ownership % and Minority Interest % to thecurrent period Owner's Equity changes excluding Retained Earnings Current andOther Reserves. This assumes that the changes in Owner's Equity accounts excludingRetained Earnings Current and Total Comprehensive Income are deemed to be pre-acquisition//pre-divestment changes and that the Retained Earnings Current andComprehensive Income changes are post-acquisition/post-divestment. Current yearpre-acquisition/pre-divestment Retained Earnings should be transferred from theRetained Earnings Current account to the Retained Earnings Current Pre-OwnershipChange account in order to be eliminated. This rule-set offsets with Investment inSubs (from Investment rule-set) and the two rule-sets use the Goodwill Offset accountas the clearing account.

This rule does not rely on any Intercompany data entry in order to execute. It will run atthe first consolidation level (that is, the immediate parent).

Table 17-14 Owner's Equity (Subsidiary/Proportional) (Rule-set)

Entry Description

Condition Entity Current Method = Subsidiary,Proportional and Total Data Source < > 0

Factor None


Account Base of "FCCS_Total Equity" Excluding Baseof "FCCS_Retained Earnings Current", Baseof "FCCS_Other Reserves", "FCCS_CTA"

Intercompany Base of "FCCS_Intercompany Top"



Table 17-15 Owners Equity (Subsidiary/Proportional)- Reverse Proportionalize(Rule)


Condition inheritedFactor Current \ Entity Consolidation

%

Processing Option Subtract

Dimension Source POVAccount inheritedIntercompany inheritedMovement inheritedData Source inherited "FCCS_Intercompany

Eliminations"

Table 17-16 Owners Equity (Subsidiary/Proportional) - Goodwill Offset (Rule)


Condition inheritedFactor Current / Entity Ownership %


17-69

Table 17-16 (Cont.) Owners Equity (Subsidiary/Proportional) - Goodwill Offset(Rule)


Processing Option Add

Dimension Source POVAccount inherited "FCCS_Goodwill Offset"

Intercompany inherited IF: Entity = #Legal Company#

THEN: #Source POV Entity#

Movement inherited IF: Entity Ownership %Change > 0


ELSE:"FCCS_Mvmt_Disposal_Input"


Table 17-17 Owners Equity (Subsidiary/Proportional)- Minority Interest (Rule)


Condition inheritedFactor Current \ Entity Minority

Interest %


Dimension Source POVAccount inherited "FCCS_Minority Interest"







Owner's Equity (Subsidiary/Proportional) PP Rule-SetThe Owner's Equity (Subsidiary/Proportional) Prior Period rule-set consists of fourrules / journal detail lines.

This rule-set applies an ownership change to the Owner's Equity accumulated to theend of the prior period (or more specifically to the current period opening balances).This assumes that the owned company is an ongoing entity in the application and thatonly the ownership relationship has changed. The prior period Owner's Equity should


17-70

therefore be eliminated to the extent that the Ownership % has changed from the priorperiod. This rule-set offsets with Investment in Subs (Investment rule-set) and the tworule-sets use the Goodwill Offset account as the clearing account.


Table 17-18 Owner's Equity (Subsidiary/Proportional) PP (Rule-set)

Entry Description

Condition Entity Current Method = Subsidiary,Proportional and Total Data Source < > 0 AndEntity Ownership % Change < > 0

Factor None


Account Base of "FCCS_Total Equity"


Movement "FCCS_OpeningBalance"


Table 17-19 Owners Equity (Subsidiary/Proportional) PP - ReverseProportionalize (Rule)


Condition inheritedFactor Change In \ Entity

Consolidation %


Dimension Source POVAccount inheritedIntercompany inheritedMovement inherited IF: Entity Ownership %

Change > 0




Table 17-20 Owners Equity (Subsidiary/Proportional) PP — Goodwill Offset +(Rule)


Condition inheritedFactor Change In/ Entity

Consolidation %




17-71

Table 17-20 (Cont.) Owners Equity (Subsidiary/Proportional) PP — GoodwillOffset + (Rule)









Table 17-21 Owners Equity (Subsidiary/Proportional) PP — Goodwill Offset -(Rule)


Condition inheritedFactor Change In/ Entity Minority

Interest %









Table 17-22 Owners Equity (Subsidiary/Proportional) PP- Minority Interest(Rule)


Condition inheritedFactor Change In\ Entity Minority

Interest %




17-72

Table 17-22 (Cont.) Owners Equity (Subsidiary/Proportional) PP- MinorityInterest (Rule)


Account inherited "FCCS_Minority Interest"







Owner's Equity (Equity) Rule-SetThe Owner's Equity (Equity) rule-set consists of two rules/journal detail lines.

This rule-set applies the current period Ownership % to the current period Owner'sEquity changes excluding Retained Earnings Current. This assumes that the changesin Owner's Equity accounts excluding Retained Earnings Current are deemed to bepre-acquisition/pre-divestment changes and that the Retained Earnings Currentchanges are post-acquisition/post divestment. Current year pre-acquisition/pre-divestment Retained Earnings should be transferred from the Retained EarningsCurrent account to the Retained Earnings Current Pre-Ownership Change account inorder to be eliminated.

This rule-set offsets with Investment in Subs (Investment rule-set) and the two rule-sets use the Goodwill Offset account as the clearing account. The other side of theentry recognizes the Investment in Equity Companies. There is no "ReverseProportionalization" entry because the Consolidation % is zero and nothing isproportionalized from an Equity method company.


Table 17-23 Owner's Equity (Equity) (Rule-set)

Entry Description

Condition Entity Current Method =Equity And Total DataSources < > 0

Factor Current / Entity Ownership %


Account Base of "FCCS_Total Equity" Excluding Baseof "FCCS_Retained Earnings Current", Baseof "FCCS_Other Reserves", "FCCS_CTA"

Intercompany "FCCS_No Intercompany"


17-73

Table 17-23 (Cont.) Owner's Equity (Equity) (Rule-set)

Entry Description



Table 17-24 Owners Equity - Goodwill Offset (Rule)




Intercompany inherited #Source POV Entity#





Table 17-25 Owners Equity - Investment in Equity Company (Rule)



Dimension Source POVAccount inherited "FCCS_Investment in Equity

Companies - Investment"







17-74

Owner's Equity (Equity) PP Rule-SetThe Owner's Equity (Equity) Prior Period rule-set consists of two rules/journal detaillines.

This rule-set applies an ownership change to the Owner's Equity accumulated to theend of the prior period (or more specifically to the current period opening balances).This assumes that the owned company is an ongoing entity in the application and thatonly the ownership relationship has changed. The prior period Owner's Equity shouldtherefore be eliminated to the extent that the Ownership % has changed from the priorperiod.

This rule-set offsets with Investment in Subs (from Investment rule-set) and the tworule-sets use the Goodwill Offset account as the clearing account. The other side ofthe entry recognizes the Investment in Equity Companies. There is no "ReverseProportionalization" entry because the Consolidation % is zero and nothing isproportionalized from an Equity method company.


Table 17-26 Owner's Equity (Equity) PP (Rule-set)

Entry Description

Condition Entity Current Method = Equity And Total DataSources < > 0 And Entity Ownership %Change < > 0



Account Base of "FCCS_Total Equity"


Movement "FCCS_OpeningBalance"


Table 17-27 Owners Equity PP- Goodwill Offset (Rule)









17-75

Table 17-27 (Cont.) Owners Equity PP- Goodwill Offset (Rule)



Table 17-28 Owners Equity PP- Investment in Equity Companies (Rule)




Companies - Investment"






Owner's Equity (Holding) Rule-SetThe Owner's Equity (Holding) rule-set consists of two rules / journal detail lines.

This rule-set applies the legal company entity name as the Intercompany Partner (ICP)entry for Owner's Equity accounts. The Owner's Equity of a Holding company does noteliminate but the Holding company might become a Subsidiary at the next level in theEntity hierarchy. In order to recognize the source of the elimination of Owner's Equityat that next parent level, the label of the original entity must be captured as the ICP atthe legal company level.


Table 17-29 Owner's Equity (Holding) (Rule-set)

Entry Description

Condition Entity Current Method = Holding And TotalData Sources < > 0



Entity #Legal Company#


17-76

Table 17-29 (Cont.) Owner's Equity (Holding) (Rule-set)

Entry Description

Account Excluding base of "FCCS_Retained EarningsCurrent", base of "FCCS_Other Reserves","FCCS_CTA"

Intercompany "FCCS_No Intercompany"



Table 17-30 Owners Equity - Reverse Proportionalize (Rule)



Dimension Source POVEntity inheritedAccount inheritedIntercompany inheritedMovement inheritedData Source inherited

Table 17-31 Owners Equity - Proportionalize with ICP (Rule)



Dimension Source POVEntity inheritedAccount inheritedIntercompany inherited #Source POV Entity#

Movement inheritedData Source inherited

Net Income (Subsidiary) Rule-SetThe Net Income (Subsidiary) rule-set consists of two rules/journal detail lines.

This rule-set splits the ongoing post-acquisition income of the Subsidiary between theOwner's share and the Minority Interest share. The entry splits out the Minority Interestshare in the Income Statement at the Minority Interest % and records the other side ofthe entry in the Minority Interest Equity account. The unadjusted remainder of the NetIncome (the amount representing the Ownership %) is aggregated to the Owners'Income.


17-77


Table 17-32 Net Income (Subsidiary) (Rule-set)

Entry Description

Condition Entity Current Method = Subsidiary and TotalData Sources < > 0

Factor Current / Entity Minority Interest %


Account Base of "FCCS_Retained Earnings Current",base of "FCCS_Other Reserves","FCCS_CTA"



Table 17-33 Net Income (Subsidiary) - MI Net Income (Rule)



Dimension Source POVAccount inherited "FCCS_Minority Interest

Income"

Intercompany inherited #Source POV Entity


Table 17-34 Net Income (Subsidiary) - Minority Interest (Rule)



Dimension Source POVAccount inherited "FCCS_Minority Interest"



Net Income (Equity) Rule-SetThe Net Income (Equity) rule-set consists of two rules / journal detail lines.

This rule-set records the ongoing post-acquisition income of the equity methodcompany as Equity Company Income in the Income Statement and records the otherside of the entry in the Investment in Equity Companies Investment Income account.Note that this Equity Companies Investment Income account (in the Non-Current


17-78

Assets section of the Balance Sheet) is distinguished from the "Equity Pickup"recorded at a legal company level. This entry is the equivalent of Equity Pickup but ata consolidated reporting level instead of a legal company reporting level.


Table 17-35 Net Income ((Equity) (Rule-set)

Entry Description

Condition Entity Current Method = Equity and Total DataSources < > 0



Account Base of "FCCS_Retained Earnings Current",base of "FCCS_Other Reserves","FCCS_CTA"



Table 17-36 Net Income (Equity) - Equity Company Income (Rule)



Dimension Source POVAccount inherited "FCCS_Equity Company

Income"

Intercompany inherited #Source POV Entity


Table 17-37 Net Income (Equity) - Investment in Equity Company Income (Rule)




Companies - Income"




17-79

Seeded Consolidation Rule Examples

The data displayed in the following examples use positive numbers to represent debitentries and negative numbers to represent credit entries. This should make thecalculations in the examples easier to understand without having to referencemetadata attributes, and will be valid regardless of the account type and consolidationoperators in the metadata.

The negative entries shown for the Common Stock accounts would actually be loadedas positive numbers to an application for which Common Stock is an “Equity” typeaccount. Credit balances for Common Stock, represented in the examples by negativenumbers, would be loaded to an application as positive amounts because credits in anEquity type account are represented by positive numbers.

Seeded Consolidation Rules - Example (January)


17-80


17-81


17-82

Seeded Consolidation Rules - Example (February)


17-83


17-84


17-85


17-86


17-87


17-88


17-89


17-90

Seeded Consolidation Rules - Example (March)


17-91


17-92


17-93


17-94


17-95


17-96


17-97


17-98

18Working with Rules

Related Topics

• Consolidation and Translation Rules

• Selecting Business Rules

• Assigning Access to Rules

• Working with Override Translation Rules

• Working with Configurable Calculations

• Equity Pickup Overview

• Working with On-Demand Rules

Consolidation and Translation RulesFinancial Consolidation and Close provides pre-built calculation scripts to handleconsolidation and translation. In addition, the system provides pre-built scripts andmember formulas for some of the standard calculation processes. These rules areprovided by default:

• Consolidate

• Force Consolidate

• Translate

• Force Translate

• DataLoad_PreProcess_Consol

• DataLoad_PostProcess_Consol

• DataLoad_PostProcess_Rates

• MetadataLoad_PostProcess_Consol

• FCCSFormStatusProcessor

• RefreshDatabase_PostProcess_Consol

• RefreshDatabase_DelegatePostProcess

• ComputeRates

• RefreshDatabase_PostProcess_Rates

• ClearEmptyBlock

You can filter the list of rules by Cube and Rule Type.

To view the list of rules:

1. On the Home page, click Rules.

2. To filter the list of rules, click the Filter icon.

18-1

3. From the Cube drop-down list, select a Cube: Consol or Rates, or use the defaultof All.

4. From the Rule Type drop-down list, select a type, or use the default of All:

• Scripts

• Rules

• Rulesets

• Templates

5. Click Apply to apply the filter.

Selecting Business RulesYou can associate business rules with a form, by cube. Users can launch associatedbusiness rules from the form to calculate values. You can set whether each businessrule associated with a form automatically launches when the form is opened or saved.

To select business rules for forms:

1. Take an action:

• To update the current form, click Actions, and then click Business Rules.

• To open a form for editing, go to the Home page and click the Navigator icon

, and then under Create and Manage, click Forms. Select the form, click

, and then click Business Rules.

2. From the Cube drop-down menu, select the cube.

3. From the Business Rules list, select the business rules to associate with theform, and move them to Selected Business Rules.

By default, the Calculate Form business rule is selected. Calculate Form isautomatically created for forms to calculate subtotals. You can clear CalculateForm to prevent users from calculating data in forms.

In addition, you can access the Calculate function from Configurable Calculations.See Working with Configurable Calculations.

a. On the Home page, click Application, and then click Consolidation.

b. Select a user-configurable rule, such as Final Calculation.

Calculation Manager opens in a different browser tab.

c. From the Actions menu, select Database Properties, expand and select theConsol cube, then click Calculation.

4. To change the order of selected business rules (the order in which rules displayand launch), select a business rule in Selected Business Rules and click the upor down arrow to move it up or down in the list. The rule listed first displays andlaunches first; the rule at the bottom of the list displays and launches last.

5. To set business rule properties, click Properties.

6. Click Save to save your work and continue creating or editing the form, or clickFinish to save your work and close the form.

Chapter 18Selecting Business Rules

18-2

Note:

When selecting business rules for composite forms, you can select whichbusiness rules run in composite forms. Business rules from included formsdon't run unless you select them for the composite form itself. For example,to run all the business rules associated with an included form named "TotalExpense Impact", select" Business rules for Total Expense Impact".

Assigning Access to RulesTo assign access to rules:


2. Under Create and Manage, click Rules Security.

3. Under Business Rule Folders, select the folder containing the rules, and thenselect the rules.

4. Click .

5. Perform a task:

• To add access, click Add , and then select from the list of available usersand groups.

For Type of Access:

– Select Launch to allow the selected users and groups to launch theselected rules.

– Select No Launch to prevent the selected users and groups fromlaunching the selected rules.

• To edit access, click , and then select the applicable Type of Access.

• To remove access, select the users or groups for which to remove access,

and then click .

Working with Override Translation RulesBy default, the system provides standard translation methods on all accounts witheither a time balance property of Flow or Balance. You can select to change thesesettings and specify a default translation method and rate account for the application.See Specifying Default Translation Settings.

You can also create translation rules to override the default translations. Use theseguidelines for override translation rules.

Chapter 18Assigning Access to Rules

18-3

Note:

For the procedures on creating and deploying override translation rules, see Creating Override Translation Rules and Deploying Override TranslationRules.

Security Rights for Override Translation Rules

• Only Service Administrators can create, modify, deploy, or delete translation rules.

• Power users have view access for translation rules.

• Users and Viewers cannot view or access translation rules.

Types of Override Translation Rules

You can create these types of override translation rules.

Using a different translation method

You can create a rule to specify a different translation method (Periodic or YTD) thanthe default translation setting.

Using a different translation method and rate account

You can create a translation rule with a different method and rate account than thedefault translation for a specific POV.

Referencing a different Scenario, Year and Period

You can create translation rules using a rate account referencing a different Scenario,Year and Period. By default, the rate account data is from the same Scenario, Yearand Period for which the translation is being processed. For example, if you aretranslating data for Actual, 2016, January, the system uses the rate account data fromActual, 2016, January. You can specify a rate account from a different Scenario, Yearand Period, such as Budget, 2016, January.

When you select the Scenario, Year and Period for the rate account, you can use arelative references and keyword for the Year and Period. These keywords and relativereferences are supported:

• Current

• Prior

• Next

• First

• Last

• Current + n

• Current - n

Any rate account which contains no data is translated using the value 0.

Using multiple dimensions

Chapter 18Working with Override Translation Rules

18-4

Translation override rules do not have a default Source POV dimension. You can addany of the following dimensions to restrict the data set to which the translation isapplied:

• Scenario

• Year

• Period

• Entity

• Account

• Intercompany

• Movement

• Data Source

• Multi-GAAP (if enabled)

• Additional custom dimensions (if enabled)

You should define at least one dimension when you create a rule. If no dimensions areselected, the system applies the rule to all members of all dimensions.

You can create translation rules that contain multiple dimensions (for example,Account, Custom, and so on). You can select multiple members for the selection, anduse functions such as IDescendant and IChildren.

Note that in the Source POV, you cannot select a single Parent member. The Parentmember can only be selected as part of a function list.

Using redirection to a different member

When you create a translation rule, you can specify redirection to a differentdestination member. The Source POV can include any members, including parent orsystem members. The Parent member can only be selected as part of a function listand must have redirection to a base member. You cannot select a single Parentmember.

The Redirection POV must be a base member and not a system-calculated member,such as Opening Balance or FX Opening. If you do not specify a redirection member,the system will process the translation and write to the same dimension members asthe source.

Historical Account Override Versus Translation Override

Historical accounts can use the default translation method, or use an override rate oramount. If the application also contains translation override rules for the historicalaccount, then the translation override rule overwrites the default translation.

Valid Members for Override Rules

You can select single members, multiple members or a function list for the source foreach specified dimension and redirect to only one base member of that dimension.

The View and Consolidation dimensions are not applicable when creating translationrules.

Overrides are allowed against Intercompany Eliminations at parent entity levels whenthe data is against Entity Consolidation.


18-5

Overrides are not allowed against Intercompany Eliminations with the Eliminationmember of the Consolidation dimension.

The availability of other dimensions is based on the features enabled for theapplication. You cannot select redirection members from Scenario, Year, Period, Entityand Data Source dimensions.

You cannot select a parent member for the POV, as a parent is aggregated fromtranslated base members.

You cannot select level 0 members that have the data storage property set to DynamicCalc; these are members that are calculated using Member Formulas or a system oruser-defined calculation script.

Reporting Currency

The translation rule applies to the selected entity when translating to all of its parentswith the same currency. For example, if Entity1 has two parents P1 and P2, and bothP1 and P2 have the same currency, the translation rule applies to both P1.Entity1, andP2.Entity1. The translation rule also applies to all reporting currencies.

Processing Options for Multiple Override Rules (Replace, Add, Subtract)

When you create translation rules, you select the translation method and rate accountto use for the translation. The translation rule overrides the default translation settingfor the selected POV. However, if you have multiple translation rules, and there is aconflict in the rules (for example, they reference the same cell with a differenttranslation method or rate account), the system uses the processing option that youselected for the rule: (Replace, Add or Subtract) to process the correct translationoverride amount to and replace the original default translation amount.

Replace Option

If you have multiple transaction rules with the same referenced POV and select theReplace option, the system uses the last translation rule.

For example, the first translation rule contains Acct1 that translates using PERIODICand MyRate. A second translation rule contains the same Acct1, but translates usingYTD and MyRate. The third translation rule contains the same Acct1 using PERIODICand NewRate. Since the third translation rule is the last one with Acct1 reference, thesystem uses the third rule for translation.

Add Option

The Add option is used for accumulating translation override rules.

If you have multiple transaction rules with the same referenced POV and select theAdd option, the rule accumulates to the override translation amount.

For example, the first translation rule contains Acct1 that translates using PERIODICand MyRate. A second translation rule contains the same Acct1 but translates usingYTD and MyRate. The third translation rule contains the same Acct1 and usesPERIODIC and NewRate. If all these rules have the Add option, the systemaccumulates all the translation override results. The override translation will alwaysreplace the default translation value.

Subtract Option

If you have multiple transaction rules with the same referenced POV and select theSubtract option, the rule subtracts from the previous override translation amount.


18-6

For example, the first translation rule contains Acct1 that translates using PERIODICand MyRate. A second translation rule contains the same Acct1 but translates usingYTD and MyRate. If these rules have the Subtract option, the system will subtract fromthe previous translated override result. The override translation will always replace thedefault translation.

Creating Override Translation RulesFor guidelines on override translation rules, see Working with Override TranslationRules.

To create override translation rules:




By default, the Manage Translation Override Rules page lists all the translationrules available in the application. This view is the To Be Deployed view. If youcreate a new rule, the rule is displayed in the list with a blue icon indicating thatthere has been a change and that it has not yet been deployed.

If you modify and save an existing rule, the rule is displayed with a yellow triangleindicating that there is a change. After the rule is deployed again, the change iconis no longer displayed.

From this view, you can add new translation rules and also deploy them.

4. Optional: To display all deployed rules, click Show Deployed Rules.

The Deployed view displays all the rules that are currently deployed to the system.This view is read-only. You cannot remove or modify any rules from this view.

5. To add a new translation rule, click the Add (+) icon.

6. Enter a name for the translation rule and a description.

7. From Translation Method, select Periodic or Year to Date.

8. From Rate Information, select a Rate account or a specific amount:

• FX Rates - Average

• FX Rates - Ending

• Specific Rate, then enter a rate.

By default, the current Scenario, Year and Period are used to determine the rateaccount value.

Optional: Click Advanced to specify different values for these dimensions.

9. Click Scope, and then select the Source members for the rule.

You must select at least one dimension to create the rule. You can selectadditional dimensions using the Add (+) icon, or remove dimensions using theRemove (X) icon. The members specified in the source are written to the samemember as the target unless you select Redirect Members.

You cannot create an override translation rule with parent or calculated members.

The View dimension is not available for override translation rules.


18-7

10. Optional: To enable redirection to a target, click Redirect Members, then clickthe Add + icon to display the member selector and select members for the TargetRedirection.

Scenario, Year, Period, Entity and Data Source dimensions are not available forredirection.

From the Actions menu on the right side, you can click Add Exclusion to excludespecific members, or Delete or Clear members.

For each dimension that you add to source, you can select the Redirect Membersoption. If you want to later remove redirection, click Remove Redirection to clearthe redirection information.

11. From Processing Option, select an option:

• Replace

• Add

• Subtract

12. Click Save and Close or Save and Continue.

13. To deploy rules, see Deploying Override Translation Rules.

Deploying Override Translation RulesYou can create multiple translation rules, but select only specific ones for deployment.

For example, you may have created five translation rules, but only deploy three ofthem. After deployment, the Deployed view shows the three deployed rules. The ToBe Deployed view displays all five rules.

Note:

When a translation rule is deployed, the calculation status changes from OKto System Change. This applies to both locked and unlocked entities.

Internally, when a rule is first created, it will not be part of the consolidation process.However, once a rule is deployed in the application, it will be included in theconsolidation process.




By default, the Manage Translation Override Rules page lists all the translationrules available in the application.

4. Click Deploy to open the Deploy Rules window.

The Deploy Translation Rules window is displayed, and all the rules that werepreviously deployed are automatically selected.

5. Select the rules you want to deploy, and unselect rules that you no longer wantdeployed.


18-8

If you uncheck an already selected rule and deploy the rules, the unchecked rulewill be un-deployed from the system.

6. From the Deploy Rules window, click Deploy to deploy the rules.

Creating Rate Accounts for Translation OverridesIn addition to the "Average Rate" and "Ending Rate" system Rate accounts that arecreated as part of the application, you can create additional Rate accounts. Theseuser-defined Rate accounts are used for Translation Override rules to perform specialtranslations using a different set of Rate data. You can create, edit, or delete user-defined Rate accounts.

Note:

You must be a Service Administrator to create, edit, or delete user-definedRate accounts.

Power Users and other Users are not able to access Translation Rules andcannot view or modify any user-defined Rate accounts.

See these topics:

• Editing User-Defined Rate Accounts

• Deleting User-Defined Rate Accounts

You can create a maximum of three new Global Rate accounts (for a total of fiveGlobal Rate accounts) and additional Local Rate accounts. Rate data entered toGlobal Rate accounts is applied to all entities while rate data entered to Local Rateaccounts is entered on an entity-by-entity basis.

When you create new Global Rate accounts, these seeded system Rate formsautomatically include the newly defined accounts:

• Enter Exchange Rates – Multi Period

• Enter Exchange Rates – Single Period

• Exchange Rates

When you create new Local Rate accounts, the Local Exchange Rates seeded Rateform automatically includes the newly defined accounts:

After you create a new Rate account, or perform any account maintenance on one,you must perform a Refresh Database. When you refresh the database, the systemupdates the “Entered Exchange Rates” and the “Exchange Rates” accounthierarchies.

The new user-defined Global Rate account is inserted as a child member of “EnteredExchange Rates”. It is a level 0 member of that hierarchy, and a sibling to the twoexisting system Rate accounts - Average Rate and Ending Rate. It has the sameproperties as the system Rate accounts.

The new user-defined Local Rate account is inserted as a child member of “ExchangeRates -> Local rates”. It is a level 0 member of that hierarchy.


18-9

When you perform the Compute Rate process in Data Forms or in the Rules card, thesystem computes the rates for all Global Rate accounts, including the new user-defined Global accounts. All of the computed Global Rate data is stored in the Ratescube and can be viewed in the seeded Data Forms. Entity-specific rate data entered toLocal Rate accounts is stored in the Consol cube and no additional calculations areperformed.

To create user-defined Rate accounts:




4. Click Manage Rate Accounts.

The system opens a popup box listing all available user-defined Rate accounts.

5. Click (+) to create a new Rate account.

6. Enter a Name, Description, and Alias.

Note:

The Alias information is used in the Default Alias table.

7. For Rate Type, select Global Rate or Local Rate.

Note that if a total of five Global Rate accounts already exist (the maximumpermitted), the Rate Type will default to Local Rate and cannot be changed. Toadd a new Global Rate account, an existing Global Rate account must first bedeleted.

8. Click OK.

9. Click Close to close the Manage Rate Accounts dialog box.

If the system detects that changes have been made, this message is displayed:

"To apply Rate account changes to the application, you must refresh the database.Would you like the System to perform Database Refresh upon close?"

• If you select Close and Refresh, the system opens the Refresh Databasepopup.

• If you select Close (without a Database Refresh), the system displays thiswarning message: "You must manually perform Database Refresh so thatRate account changes can take effect.". Click OK to exit the message box.

Editing User-Defined Rate Accounts

Note:



18-10






5. Select a Rate account and click the Edit icon.

6. Edit the account as needed. and click OK.

7. Click Close to close the Manage Rate Accounts dialog box.

If you made changes to the account, the system displays this message:

"To apply Rate account changes to the application, you must refresh the database.Would you like the System to perform Database Refresh upon close?"

• If you select Close and Refresh, the system opens the Refresh Databasepopup.

• If you select Close (without a Database Refresh), the system displays thiswarning message: "You must manually perform Database Refresh so thatRate account changes can take effect.". Click OK to exit the message box.

Deleting User-Defined Rate AccountsYou can only delete a user-defined Rate account if it is not referenced in TranslationOverride rules.

Note:







5. Select the Rate account from the list and click the Delete icon (X) to delete it.

6. At the confirmation prompt to delete the account, click Confirm.

Working with Configurable CalculationsWithin the consolidation process, internally Financial Consolidation and Closeperforms a set of calculations, then performs the standard translations and FXcalculations, and finally performs the standard consolidation and elimination.

Chapter 18Working with Configurable Calculations

18-11

In addition, Financial Consolidation and Close allows you to include additionalcalculation rules for your applications. The system provides insertion points within thedefault consolidation process where you can include your own calculation rules.

You write rules in script format using Calculation Manager, and then deploy them toFinancial Consolidation and Close. For information on using Calculation Manager, seeDesigning with Calculation Manager for Oracle Enterprise Performance ManagementCloud.

The following security access is required for configurable calculations:

• To create, modify, and delete rules, you must be the Service Administrator.

• To view rules, you must be a Service Administrator or Power User.

See these topics:

• Creating Configurable Calculations

• Configurable Calculation Rules

• System Calculations

Creating Configurable CalculationsTo create your own calculations, you write rules using Calculation Manager, and thendeploy them to Financial Consolidation and Close.

For information on using Calculation Manager, see Working within CalculationManager and the Designing with Calculation Manager for Oracle EnterprisePerformance Management Cloud guide.

Note:

To create calculations, you must be a Service Administrator.

You can edit an existing calculation rule at any time if you have the ServiceAdministrator role. You cannot remove any of the seeded calculation rules. If the ruleis no longer needed, you can delete the content from the rule.

You can only create calculations at the pre-defined insertion points.

You cannot modify the calculations that are performed by the system. However, youcan override some system calculations. See System Calculations.

To create configurable calculations:


2. From the Consolidation Process page, select the tab for which to createcalculations: Local Currency, Translated (if multi-currency application), orConsolidated.The Consolidation Process page displays a list of applicable system and user-defined calculations in the order in which they are executed.

3. When you select a rule, the rule Properties are displayed in the right panel. To

view the description of a rule, on the right panel, click the Information tab .


18-12

4. On the Consolidation Process page, click on an insertion point in the list of rules

indicated by a User icon:

If you are not a Service Administrator, the insertion point links are not enabled.

5. Optional: From Auto Create Blocks, click the link for No to change it to Yes andenable the system to create missing blocks for the configurable calculation.Changing this value will mark the Calculation Status as System Change. Tocontinue, click OK.

Note:

Enabling the Auto Create Blocks option may affect calculationperformance. For details on this option, see Enabling Auto Create Blocksfor Configurable Calculations.

6. The system opens Calculation Manager in a separate tab in the browser. Expandthe "Planning" folder and navigate to the "FCCS Consol Rules" folder rules. Theseare the rules that you are allowed to edit.

7. Drill down to the rule that corresponds to the insertion point.For example, the Calculation Manager rule: FCCS_10_After Opening BalanceCarry Forward_LocalCurrency

corresponds to the After Opening Balance Carry Forward insertion point.

For a list of rules and corresponding insertion points, see Configurable CalculationRules.

8. Edit the script and click Save, then click OK.You can also edit a rule by importing a Calculation Manager rule, and you canexport rules.

For guidance on applicable dimension members for each rule, see the commentsin the rule script.

9. When you are done editing a rule, from the menu bar, click Validate and Deploy.The system validates the rule and ensures that members and syntax are valid. Itmust pass validation before deployment.

If it passes validation, Calculation Manager deploys the rule. From the Deploystatus message, click OK.

Deployed insertion rules are included as part of the consolidation script.


18-13

10. If it fails validation, deployment fails and errors are logged in the Jobs console.Navigate to Jobs, then Recent Activity, and select the name of the rule to seethe error.

11. After you deploy a rule, the system changes the Calculation Status of theapplicable entities from OK to SC (System Change). Calculation Status of No Dataor Impacted remains the same. You must run the consolidation process to see theimpact of the new calculations.

Enabling Auto Create Blocks for Configurable CalculationsWhen you create configurable calculations, you can enable the Auto Create Blocksoption to have the system automatically create missing blocks. This can resolve issueswith missing data when you run configurable calculations.

See Creating Configurable Calculations.

Note:

If you are using Bottom-Up processing (@CALCMODE(BOTTOMUP) in yourcustom calculation, do not enable Auto Create Blocks for that customcalculation. Bottom-Up processing (@CALCMODE(BOTTOMUP) and AutoCreate Blocks are mutually exclusive features.

The system creates a data block for each unique combination of Sparse standarddimension members. The data block represents all the Dense dimension members forits combination of Sparse dimension members.

Assume you have four dimensions in your application:

Table 18-1 Example of Dimensions

S. No. Dimension Type Members Total Members

1 Scenario Sparse Actual, Budget 2

2 Year Sparse FY17, FY18 2

3 Period Sparse Jan, Feb 2

4 Account Dense Sales, Cash 2

The application has six Sparse and two Dense members. Assume all Sparse membersare of the Stored type.

All members of a Dense dimension constitute a block. So a block for this applicationwill look like this:

Data for ‘Sales’

Data for ‘Cash'

This type of block will exist for each combination of stored Sparse members in yourapplication:


18-14

Table 18-2 Example Block

S. No. Indexes Blocks

1 Actual FY17 Jan Sales(#Missing)

Cash(#Missing

2 Actual FY17 Feb Sales(#Missing)

Cash(#Missing

3 Actual FY18 Jan Sales(#Missing)

Cash(#Missing

4 Actual FY18 Feb Sales(#Missing)

Cash(#Missing

5 Budget FY17 Jan Sales(#Missing)

Cash(#Missing

6 Budget FY17 Feb Sales(#Missing)

Cash(#Missing

7 Budget FY18 Jan Sales(#Missing)

Cash(#Missing

8 Budget FY18 Feb Sales(#Missing)

Cash(#Missing

So your application has a total of eight blocks. As a general rule:

Total number of blocks = Product of all STORED sparse members of yourapplication

In this application example, 2 members from Scenario x 2 members from Year x 2members from Period = 8 blocks

Financial Consolidation and Close internally creates blocks in advance forconsolidation during the consolidation script generation. When you create additionalconfigurable calculations, some additional blocks may need to be created. When youenable Auto Create Blocks, missing blocks will be automatically created by thesystem.

Note:

Enabling the Auto Create Blocks option may affect calculation performance.

Configurable Calculation RulesYou manage configurable calculation rules from the Consolidation Process page.


18-15

Multi-Currency Applications

If you have a multi-currency application, the Consolidation Process page displaysthree tabs: Local Currency, Translated, and Consolidated.

The tabs depict the consolidation flow that Financial Consolidation and Close follows.It first performs calculations for base-level members in their local currency, thenperforms the translation to parent currency, and finally performs the consolidation.

Single Currency Applications

If you have a single currency application, the Consolidation Process page displays twotabs: Local Currency and Consolidated.

Calculation Rows

Each of the tabs on the Consolidation Process page displays multiple rows that depictin order, the flow of calculations that are performed. Each row is marked by one ofthese icons:

• — System. Represents that this calculation is done by FinancialConsolidation and Close.

• — Insertion point for user-defined rule. Represents the point in the processwhere you can insert your calculations from Calculation Manager.

When you select any of the rules in the list, the system displays a Properties panel onthe right with information such as the rule name, the consolidation members for whichthe rule would be processed, and any override specifications, if applicable.

When you click on a row where you can insert a user-defined calculation, CalculationManager opens in a separate tab in the browser.

Example:

1. From the Local Currency tab, click on either After Opening Balance CarryForward or Final Calculations.

The system opens Calculation Manager.

2. Expand the "Planning" folder on the left side until you see the FCCS Consolseeded rules in Calculation Manager, for example:

• FCCS_10_After Opening Balance Carry Forward_LocalCurrency

• FCCS_20_Final Calculations_LocalCurrency


18-16

3. The Calculation Manager rules correspond to the Configurable Calculation rows.For example:

• The Calculation Manager rule: FCCS_10_After Opening Balance CarryForward_LocalCurrency

corresponds to the: After Opening Balance Carry Forward row, where youcan add your own calculations. These are calculations to be performed afterthe Opening Balance Carry Forward calculations, but before balancing theBalance Sheet.

• The Calculation Manager rule: FCCS_20_Final Calculations_LocalCurrency

corresponds to the Final Calculations row, where you can add your ownadditional calculations to be performed after the Balance Sheet is balanced.

The following table lists the Financial Consolidation and Close rows for each tab andthe corresponding Calculation Manager rules.

Summary of Configurable Calculation Rules

Table 18-3 Multi-Currency Calculations

FCCS Tab FCCS Row Rule in Calculation Manager

Local Currency After Balance Carry Forward FCCS_10_After OpeningBalance CarryForward_LocalCurrency

Local Currency Final Calculations FCCS_20_Final_Calculations_LocalCurrency


18-17

Table 18-3 (Cont.) Multi-Currency Calculations


N

o

t

e

:

LocalCurrencyinsertionrulesarerestrictedto:E


18-18



ntityCurrency/EntityInput/EntityEliminationAdj/EntityConsoli


18-19



dation

Translated After Balance Carry Forward FCCS_30_After OpeningBalance CarryForward_Translated

Translated Final Calculations FCCS_40_Final_Calculations_Translated


18-20



N

o

t

e

:

Translatedinsertionrulesarerestrictedto:Pare


18-21



ntCurrency/EntityInput/EntityEliminationAdj/EntityConsolida


18-22



tion

Consolidated After Balance Carry Forward FCCS_50_After OpeningBalance CarryForward_Consolidated

Consolidated Final Calculations FCCS_60_Final_Calculations_Consolidated


18-23



N

o

t

e

:

Consolidatedinsertionrulesarerestrictedto:Par


18-24



entCurrency/Elimination.

Table 18-4 Single Currency Calculations


Local Currency After Balance Carry Forward FCCS_110_After OpeningBalance CarryForward_LocalCurrency

Local Currency Final Calculations FCCS_120_Final_Calculations_LocalCurrency

Consolidated After Balance Carry Forward FCCS_130_After OpeningBalance CarryForward_Consolidated

Consolidated Final Calculations FCCS_140_Final_Calculations_Consolidated

System CalculationsIf you are a Service Administrator, you can override or disable some systemcalculations.

See these topics:

• System Calculation Option for Custom Dimension Top Member

• Opening Balance Carry Forward


18-25

• Opening Balance Override Rules

• Balance the Balance Sheet Calculation

• Ratio Calculation

You can also create your own calculation rules to be inserted into the defaultconsolidation calculation process. See Creating Configurable Calculations.

To override or disable system calculations:


2. Select the Consolidation Process tab if it is not already selected.

3. Select the tab for which to configure calculations: Local Currency, Translated (ifmulti-currency application), or Consolidated.The Consolidation Process page displays a list of applicable system and user-defined calculations in the order in which they are executed.

4. When you select a rule, the Properties of the rule are displayed in the right panel.

To view the description of a rule, on the right panel, click the Information tab .

5. Optional: To disable the Balance system calculation for a scenario:

a. From the Local Currency tab, select the "Balance the Balance Sheet" rule.

b. From the right panel, under Disable by Scenario, select a Scenario memberusing the Member Selector.

c. Click Save to save the rule.

6. Optional: To enable a disabled system calculation:

a. Select the disabled calculation.

b. Remove the override entry.

c. Click Save to save the rule.

System Calculation Option for Custom Dimension Top MemberFor user-defined Custom dimensions, Service Administrators can select to processSystem Calculations using the Top Member of the Custom dimension, instead of alllevel 0 members, for faster performance. You can select specific Custom dimensionsfor which the option would apply.

Note that the System Calculation option applies only to user-defined Customdimensions, and does not apply to the Multi-GAAP dimension.

When selected, the System Calculation option applies to all scenarios and years.

If your application includes additional alterative hierarchies outside of the "TotalCustom XX" member, the Top Member option would not apply to the alternativehierarchies. To benefit from the Top Member processing option, you should redesignthe Custom dimension to include all hierarchies as part of the "Total Custom XX"member if applicable.


18-26

Note:

If your application is an Extended Dimension application, you may want toturn this feature off for better consolidation performance.

The option applies to the following System Calculations for all applicable currencymembers such as Entity Currency, Parent Currency and Reporting Currency:

• Opening Balance

– Includes both Opening Balance for movement and Retained Earnings Priorcalculation

– Opening Balance Ownership Change

• Foreign Exchange (FX) Calculations (for multi-currency applications)

– FX Opening

– FX Movement

– FX to Cumulative Translation Adjustment (CTA)

• Balance Calculation

During the Translation process, the translation from Entity Currency to ParentCurrency, and from Parent Currency to Reporting Currency, will continue to calculateat the Custom detail level. For any Translation Override rules and ConfigurableConsolidation rules, the system will process them according to the rule definition.

You can change the option at any time for an existing application. By default, theoption is disabled for all Custom dimensions. When the option is changed, the systemwill change the Calculation Status to SC (System Changed), and you canreconsolidate if needed. Any new system calculations will be performed based on thecurrently selected option.

The Task Audit log contains the history of changes to the System Calculation option. Itincludes the user who performed the setting change, the date and time it wasperformed, and the information that was changed - the original setting and the newlyupdated setting.

To set the System Calculation option:


2. Select the Consolidation Process tab.

3. Select the tab for which to configure calculations: Local Currency, Translated (ifmulti-currency application), or Consolidated.

4. Click the Options menu at the top of the page.

5. From System Calculation Options, select the dimensions for which Top Memberprocessing will be applied, then click Save.

Opening Balance Carry ForwardOpening Balance Carry Forward is a built-in system calculation to automatically carryforward the Opening Balance. It retrieves the Closing Balance from the prior periodand stores it in the Opening Balance member for all financial accounts. It will


18-27

dynamically retrieve the proper Closing Balance based on the view (Periodic, QTD,HTD, YTD).

Applicable Consolidation Members

Each member in the Consolidation dimension represents data in different stages withinthe consolidation process.

For each rule, you can see the Consolidation dimension members for which thecalculation will be processed.

In this rule where you are processing local currency data, you would run thecalculation for these members:

• Entity Input

• Entity Consolidation (for Parent entity)

• Elimination Adjustment (member for Ownership Management)

Opening Balance Override RulesThe system default behavior for the Opening Balance is to carry forward the ClosingBalance from the same Scenario as the Opening Balance to which the data is beingwritten.

For the Opening Balance, you can specify a different scenario from which to sourcethe Closing Balance data in the first period of each year.

For example, when recording projected future data such as a forecast, plan or budget,the reported Opening Balance is generally based on the most current actual data, toensure that the Closing Balances of the projected period reflect as accurate a result aspossible. It is also common to update a forecast with actual results of the transactionsduring the reporting periods as the actual data for those periods becomes available.

The override source scenario that you specify can be applied to all years, or can belimited to only specified years.

For all years in-the scope, any “prior period” relationship assumes that the prior periodfor any reporting period except the first reporting period is the immediately precedingreporting period of the same View and from the same scenario.

For the first reporting period of the year, the immediately preceding reporting period(the prior period) is the last reporting period of the prior year from the override sourcescenario.

Note:

The general requirements of the Closing Balance carry forward to OpeningBalance are not applied to any of the accounts within the Retained Earnings(Total) hierarchy including the Income Statement, Retained EarningsCurrent, Retained Earnings Prior, Dividends Declared or any additionalaccounts added within the Retained Earnings (Total) hierarchy. The carryforward of Total Retained Earnings at the end of a year to the OpeningBalance of the following year is always applied to the following year firstperiod Retained Earnings – Prior account only.


18-28

Opening Balance Adjustments Translation

Translation of Opening Balance Adjustments applies the exchange rate (or entitycurrency / translated currency ratio for historical accounts) from the prior period. ForPeriod 1, the rate / ratio applied is taken from the last period of the prior year from anoverride source scenario other than the current scenario.

Opening Balance Translation for Reporting Currencies

Opening Balance for Reporting Currencies is carried forward from the Closing Balanceof the prior period. If the Closing Balance of the prior period is not available in the firstreporting period, then the untranslated Opening Balance is translated at the exchangerate (or entity currency / translated currency ratio for historical accounts) from the priorperiod from an override source scenario other than the current scenario. If the rate /ratio is not available, then no translation occurs. When you run the translation process,the system prompts you to first translate the period(s) in the override source scenario.

Calculation and Consolidation Status

If one or more periods in a prior year of the override source scenario do not have anOK status, then a consolidation is not executed. When you run the consolidationprocess, the system prompts you to first consolidate the period(s) in the overridesource scenario.

Ownership Management Accounts

If any override rules have been added or deleted for Ownership Managementaccounts, the system prompts you to Recompute Ownership Data.

For the percentage accounts, the “change” account equals the current period valueless the prior period value except in the first periodic period of the year in which the“change” account equals the current period value less the prior period value of theoverride scenario.

For the Consolidation Method account, if the method has changed from period toperiod, then the “change” account value is true, otherwise the account value is “false”.In the first periodic period of the year, the prior period referred to is that of the overridescenario.

The “prior period” accounts reflect the values of the account in the prior period exceptin the first periodic period of the year in which the “prior period” account reflects thevalue from the override scenario.

To specify an Opening Balance calculation override rule:

1. On the Home page, click Application, then click Consolidation.


3. From the Local Currency tab, select the Opening Balance Carry Forwardcalculation.

The Opening Balance Override rules will display on the Translated andConsolidated tabs, but must be edited in the Local Currency tab.

4. From the right panel, under Overrides, click the Add (+) icon.

Note that multiple override rules can be created, but the settings for each rulecannot conflict with those of other rules.

5. In Override Name, enter the name of the rule.

6. Select options for the Opening Balance override:


18-29

• Year - Enter or select one or more years from the Member Selector. If no yearis selected, then the override applies to all years.

• Current Scenario - Enter or select one or more scenarios from the MemberSelector.

• Source Scenario - Enter or select one scenario from the Member Selector.

7. Click Save.

8. Optional: To delete an override rule, select the rule name and then select theDelete (X) icon.

Example:

For the Forecast scenario for FY18, you can specify the Opening Balance to beretrieved from the Closing Balance of the prior period (Dec FY17) of the Actualscenario.

Balance the Balance Sheet CalculationWhen you create a new application, the system includes an entry for the BalanceCalculation on the Consolidation Process page. The system can perform thiscalculation to ensure that the Balance Sheet is balanced (Total Assets = TotalLiabilities and Equity).

If the Balance Sheet is out of balance, a balancing amount is calculated and posted toa seeded account called "Balance" with the Movement dimension member "OtherCurrent Liabilities". This is a predefined miscellaneous Liability account which is usedsolely for the purpose of keeping the Balance Sheet balanced. You have the option todisable this calculation if you do not want the system to automatically balance theBalance Sheet for you.

Balance Account intersection:

• Account: FCCS_Balance

• Movement: FCCS_Mvmts_OtherCurrentLiabilities

• Data Source: FCCS_No Data Source


18-30

The FCCS_Balance account should populate correctly as long as all accounts fallwithin the Total Assets, Total Liabilities and Total Equity parent accounts.

The aggregation operator (Addition / Subtraction) must match correctly with theparent / child account types.

The system writes the FCCS_Balance entry to the "No Data Source" Data Sourcedimension member, so to see the balanced results, you will need to view the TotalData Source and Total Movement members.

To disable the Balance Sheet calculation:



3. From the Local Currency tab, select the Balance the Balance Sheet calculation.

4. From the right panel, under Disable by Scenario, use one of these methods:

• Add the selected Scenarios to the EXCLUDE clause (for example,Budget,Actual). This means that all Scenarios are disabled EXCEPT forBudget and Actual.

• Modify the entry by including only the Scenarios for which you want thecalculation disabled, for example, Consol,Forecast,ActBudDiff.

Note that there are two lines in the Member Selector.

• The first line is the list of Scenarios that should be disabled. Add the Scenariothat you want to disable on this line.

• The second line is an Exclusion line, which means that any Scenario listed inthe second line is effectively enabled (not disabled).

5. Click Save to save the rule.

6. Re-run the consolidation process.


The system will only process this calculation with local currency data for the EntityInput Consolidation member.

Ratio CalculationMost ratios, including Liquidity Ratios, Asset Management Ratios, Profitability Ratios,and Leverage Ratios, are dynamically calculated as needed. The two performance


18-31

Ratios - Days Sales in Inventory, and Days Sales in Receivables, are calculated aspart of the consolidation process.

These performance ratios are calculated as follows.

Days Sales in Inventory = (average inventory/annual cost of sales) * 365

Average inventory equals the inventory balance of the last 13 periods summed andthen divided by 13.

Annual Cost of Sales equals the sum of Cost of Sales for the current period, plus thepreceding 12 periods.

Days Sales in Receivables = 365/ (annual sales/average receivables)

Average receivables equals the receivables balance of the last 13 periods summedand then divided by 13.

Annual sales equal the sum of sales for the current period, plus the preceding 12periods.


• Entity Input

• Entity Consolidation

• Elimination Adjustment (member for Ownership Management)

To improve consolidation performance, you can disable the Ratio calculations of“FCCS_Days Sales in Receivables” and “FCCS_Days Sales in Inventory” for selectedscenarios if you do not use these calculations. This option is only available when theAsset Management feature is enabled.

To disable the ratio calculations:



3. From the Local Currency tab, select the Ratios calculation.

4. From the right panel, under Disabled Scenarios, click Add Scenario.

5. From Select Members, select the Scenario for which you want the calculationsdisabled, for example, Forecast, and click OK.

Note that there are two lines in the Member Selector.

• The first line is the list of Scenarios that should be disabled. Add the Scenariothat you want to disable on this line.

• The second line is an Exclusion line, which means that any Scenario listed inthe second line is effectively enabled (not disabled).

6. Click Save to save the rule.

7. Re-run the consolidation process.

Working within Calculation ManagerWhen you click on a Configurable Calculation rule from the Consolidation Processpage, the system opens Calculation Manager and you can work with the rule. By


18-32

default, the content of the seeded rule is empty, and only contains comments. You cancreate calculation logic using either of these methods:

• Use the graphical UI to drag and drop objects to the rules

In Graphical mode, you can use a Function Selector and Member Selector. Youcan drag and drop objects to the Designer.

• Edit rules using Essbase script

In Script mode, you can use a Function Selector and Member Selector. You cancut and paste, find and replace, show or hide comments, and import or export.

The Function Selector and Member Selector are fully supported in both the graphicaland script mode. You can always switch between the graphical and script mode byselecting the applicable option in the View drop-down:

• Designer

• Edit Script

• View Script

You can also comment out a section of the code for testing purposes (add or removecomments).

Calculation Manager features are enabled for Configurable Calculations.

For custom-defined functions supported by Calculation Manager, see https://docs.oracle.com/en/cloud/saas/enterprise-performance-management-common/ecalc/working_with_custom_defined_functions.html.

For detailed information on using Calculation Manager, see Designing with CalculationManager for Oracle Enterprise Performance Management Cloud.

You can perform validation at any time before or during the save process. The systemensures that the members and functions are valid and that the syntax is correct.

In order for your custom calculations to be part of the process, you must Deploy therule. If you encounter any errors during deployment, you can see the error detail in theJob console error log. After the rule is deployed, the system changes the calculationstatus to "System Change" (SC). You must reconsolidate data based on the changesmade to the rule that has been deployed.

Note that the calculations that you define in Calculation Manager cannot be executedstandalone. When the rule is deployed, Financial Consolidation and Close will insertthe script statements of the seeded rule into the appropriate places of theconsolidation logic.

You do not launch rules from within Calculation Manager. In addition, you cannotinclude Scenario/Year/Period/Entity as the OUTER FIX statement in your seeded rulebecause the selection of Scenario/Year/Period/Entity is determined by the user whoinvokes the consolidation from Financial Consolidation and Close. See Working withEssbase Calc Script.

Working with Essbase Calc ScriptEssbase Calc Script is the language available to you to write your own custombusiness logic in Financial Consolidation and Close. This section provides some basicEssbase constructs as well as restrictions applied to Financial Consolidation and


18-33

https://docs.oracle.com/en/cloud/saas/enterprise-performance-management-common/ecalc/working_with_custom_defined_functions.html



Close. For details regarding Essbase Calc Script, see Getting Started with EssbaseCloud for Administrators.

Common Syntax

• Semicolon

– Required at end of each statement

– Example: Sales = Sales * 1.50;

– Not needed after FIX and ENDFIX

• Double Quotes

– Member names with spaces / special characters / start with number

– Best practice is to always use double quotes around a member name

– Example: "Cash Ratio" = "Cash"/"Current Liabilities";

• Cross-dimensional Operator

– Use > to specify intersection of more than one dimension

– Example: "Sales" > "Changes In Net Income" > "Product1"

Comments

Comments start with /* and end with */.

Single or multi-line comments are supported.

You can use the toolbar icon to set or remove comment blocks.

FIX/ENDFIX

FIX/ENDFIX is one of the basic building blocks of any calc script. To do anycalculation, you must define a FIX/ENDFIX section and then place the actual businesscalculations within it.

Example: Assume "Products" is your custom dimension and you want to calculatenumber of Televisions sold. You could use the following syntax:

FIX("Televisions")

"Units_Sold" = "LED_TVs" + "UHD_TVs";

ENDFIX

The actual business calculation is:

"Units_Sold = "LED_TVs" + "UHD_TVs";, which calculates the number of Televisionssold.

Note:

You must put a semi-colon at the end of each calculation statement, but notfor FIX or ENDFIX.


18-34

The FIX/ENDFIX section limits members from various dimensions that participate incalculations within it. In this example, only "Televisions" are participating in thecalculations.

You can define nested FIXes also, such as the following:

The above calculation can also be written as shown below:

For example, @List is an Essbase function. Essbase provides many functions.However, Financial Consolidation and Close does not support all Essbase functions.See the "Essbase Function List" section for a list of supported functions.

FIX on Financial Consolidation and Close Dimensions

An Financial Consolidation and Close application can contain 13 dimensions,depending on the application features that are enabled. Out of the possible 13dimensions, you are not allowed to FIX on the following dimensions because thesystem automatically applies a FIX on them when a user invokes the consolidationprocess.

• Scenario

• Year

• Period

• View

• Entity

For example, suppose you have the following statement:

The system will fail deployment and an error message will be logged in the Jobsconsole with the appropriate information.

However, this does not mean that you cannot use these dimensions in the script.Generally, a calculation will have something like the syntax below:


18-35

Note that in FIX and "Left Hand side", you cannot use any member from the Scenario,Year, Period, Entity and View dimensions. But there is no such restriction on the "Righthand side" of the equation.

The following syntax would be allowed:

For the remaining eight dimensions, if you do not FIX on a particular dimension, thesystem will assume all the members from that dimension. For example, suppose youhave the following statement:

In this example, all remaining dimensions have a FIX except Account. In this case,Essbase will consider all members from the Account dimension for the calculationswithin FIX/ENDFIX.

Restricted Financial Consolidation and Close Members

Certain system members within each Financial Consolidation and Close are restrictedfrom being used or calculated in the calculation script. If restricted members are usedin the calculation, the system will fail validation or deployment and an error messagewill be logged in the Jobs console.

Remember that if no members are specified for the dimension, the system assumesALL members within the dimension. However, since restricted members are notallowed to be included as part of the process, you must explicitly exclude theserestricted members in your FIX dimension statements or on the Left-hand side of theexpression.

The following table is a complete listing of the restricted Financial Consolidation andClose members from these dimensions. Note that for the Currency and Consolidationdimensions, they are restricted based on the insertion rule being used. Note that eachseeded insertion rule includes information in the Comment section as to whichmember of the Currency and Consolidation dimension can be included for that rule.

Table 18-5 Restricted Dimension Members

Dimension Member ExpressionLeft-Hand Side

ExpressionRight-Hand Side

Scenario All Members No Yes

Year All Members No Yes

Period All Members No Yes

View All Members No Yes

Entity All Members No Yes

Account FCCS_CSTATUS No Yes

FCCS_CSTATUSFILTER

No Yes


18-36

Table 18-5 (Cont.) Restricted Dimension Members



FX Rates - Ending No Yes

FX Rates - Average No Yes

Average Rate No Yes

Ending Rate No Yes

SrcAverageRate No Yes

TgtAverageRate No Yes

SrcEndingRate No Yes

TgtEndingRate No Yes

FCCS_Balance No Yes

FCCS_CTA No Yes

FCCS_CICTA No Yes

FCCS_PercentControl

No Yes

FCCS_Current Ratio No Yes

FCCS_Quick Ratio No Yes

FCCS_Cash Ratio No Yes

FCCS_InventoryTurnover

No Yes

FCCS_Asset Turnover No Yes

FCCS_Days Sales InReceivables

No Yes

FCCS_Days Sales InInventory

No Yes

FCCS_Gross ProfitMargin

No Yes

FCCS_Return onSales

No Yes

FCCS_Return onEquity

No Yes

FCCS_Debt to EquityRatio

No Yes

FCCS_Debt Ratio No Yes

Data Source FCCS_System Types No Yes

FCCS_Rate Override No Yes

FCCS_AccountOverride

No Yes

FCCS_PCON No Yes

FCCS_Driver Source No Yes

Movement FCCS_OpeningBalance

No Yes

FCCS_OpeningBalance_Cash

No Yes

FCCS_FX_Total_NonCash

No Yes


18-37

Table 18-5 (Cont.) Restricted Dimension Members



FCCS_ClosingBalanceCash

No Yes

FIX On All Members of a Dimension Except Restricted Members

It is a common use case where you need to FIX on all level 0 members of a dimensionand that dimension may have restricted members. This example show how tooptimally FIX on all level 0 members except the restricted members of that dimension.

For example, the Account dimension has the highest number of restricted members.

Following is the calc script code snippet that can be used to FIX on all level 0 Accountmembers except restricted members:

@REMOVE( @LEVMBRS( "Account", 0 ), @LIST( @RELATIVE( "FCCS_SystemAccount", 0 ),@RELATIVE( "FCCS_Drivers", 0 ),@RELATIVE( "FCCS_Ratios",0 ),@RELATIVE( "Exchange Rates", 0 ) ) )

FIX on Sparse versus Dense dimensions

FIX is more effective when it is done on Sparse dimensions. In this case, FIX will makeEssbase pull blocks only for the combination of Sparse dimension members that aredefined in the FIX and skip the rest.

These sparse combinations work as indexes for Essbase to search the data blocksthat match indexes and pull them for calculations. Therefore, not all blocks are pulledfor the system to perform.

When FIX is used on a Dense dimension, dense members will be present in each datablock in Essbase. Therefore, this would have a performance impact if not usedcorrectly. Note than when FIX is on the Dense dimension, Essbase will pull all datablocks without limit to the number of blocks and will only limit to a portion within eachblock. Therefore, it may require multiple passes to the database to return theinformation.

For example, you could reference "Sales" and "PostSales" from the Accountdimension with the following statements:

When the system processes the first fix on "Sales", Essbase pulls all data blocks of theAccount dimension but only works on the one "Sales" account.


18-38

Later in the FIX statement on "PostSales", Essbase again pulls all data blocks of theAccount dimension but only works on the one "PostSales" account. In this case, twopasses are made to the database for these two accounts.

To avoid a performance issue, you can avoid using FIX on the Account dimension, butuse IF...THEN for a Dense dimension.

In this example where you are not using the FIX statement, you only need to makeone pass to the Essbase database.

The recommendation is to use FIX on Sparse dimensions, and use IF..THEN forDense dimensions to help calculation performance.

Member Block

Member blocks are also known as calculation blocks. Sometimes you will see the term"anchor" used for Member blocks. The syntax of a member block is as follows:

Following is an example of member block statements:

In this example, "My Total Opening Balance" is known as a calculation block memberor anchor. Whenever possible, this member should be a member from a Densedimension.

In the above calculation, we will only limit to the member "My FX Opening" and thecalculations are performed on the member specified in the FIX statement.

Note that when using IF statements, you will need a member block. You cannot writeIF statements outside of Member blocks.


18-39

Supported Essbase FunctionsThis section lists the Essbase functions that are supported for configurablecalculations and on-demand rules in Financial Consolidation and Close. "Y" indicatesthat the function is supported.

For detailed function information, see Oracle Essbase Technical Reference.

Common Essbase Functions

• FIX / ENDFIX - control scope

• Calculation Member Block

• Member Set: @LIST, @REMOVE, @RELATIVE, @CURRMBR, @CHILDREN,@DESCENDANTS, @SIBLINGS

• Conditional and Logical Operators: IF...ENDIF, < >, +, AND, OR, NOT

• Boolean: @ISMBR, @ISUDA, @ISACCTYPE, @SCHILD, @ISLEV, @ISANCEST

• Relationship: @GEN, @LEV, @CURGEN, @CURLEV

• Mathematical: @ABS, @SUM, @VAR, @ROUND, @MAX, + - * /

Essbase Construct Category Sub Category Supported

IF Calculation Functions Conditional andLogical Operators

Y

ELSE Calculation Functions Conditional andLogical Operators

Y

ELSE IF Calculation Functions Conditional andLogical Operators

Y

ENDIF Calculation Functions Conditional andLogical Operators

Y

> Calculation Functions Conditional andLogical Operators

Y

>= Calculation Functions Conditional andLogical Operators

Y

< Calculation Functions Conditional andLogical Operators

Y

<= Calculation Functions Conditional andLogical Operators

Y

= = Calculation Functions Conditional andLogical Operators

Y

< > Calculation Functions Conditional andLogical Operators

Y

!= Calculation Functions Conditional andLogical Operators

Y

AND Calculation Functions Conditional andLogical Operators

Y

OR Calculation Functions Conditional andLogical Operators

Y

NOT Calculation Functions Conditional andLogical Operators

Y

@ISACCTYPE Calculation Functions Boolean Y (See Note followingtable)


18-40


@ISANCEST Calculation Functions Boolean N

@ISCHILD Calculation Functions Boolean Y

@ISDESC Calculation Functions Boolean Y

@ISGEN Calculation Functions Boolean Y

@ISIANCEST Calculation Functions Boolean Y

@ISICHILD Calculation Functions Boolean Y

@ISIDESC Calculation Functions Boolean Y

@ISIPARENT Calculation Functions Boolean Y

@ISISIBLING Calculation Functions Boolean Y

@ISLEV Calculation Functions Boolean Y

@ISMBR Calculation Functions Boolean Y

@ISMBRUDA Calculation Functions Boolean Y

@ISPARENT Calculation Functions Boolean Y

@ISRANGENONEMPTY

Calculation Functions Boolean Y

@ISSAMEGEN Calculation Functions Boolean Y

@ISSAMELEV Calculation Functions Boolean Y

@ISSIBLING Calculation Functions Boolean Y

@ISUDA Calculation Functions Boolean Y

@ANCESTVAL Calculation Functions Relationship N

@ATTRIBUTEBVAL Calculation Functions Relationship N

@ATTRIBUTESVAL Calculation Functions Relationship N

@ATTRIBUTEVAL Calculation Functions Relationship N

@CURGEN Calculation Functions Relationship Y

@CURLEV Calculation Functions Relationship Y

@GEN Calculation Functions Relationship Y

@LEV Calculation Functions Relationship Y

@MDANCESTVAL Calculation Functions Relationship N

@MDPARENTVAL Calculation Functions Relationship N

@PARENTVAL Calculation Functions Relationship Y

@SANCESTVAL Calculation Functions Relationship N

@SPARENTVAL Calculation Functions Relationship N

@XREF Calculation Functions Relationship Y

@XWRITE Calculation Functions Relationship N

@ABS Calculation Functions Mathematical Y

@AVG Calculation Functions Mathematical N

@EXP Calculation Functions Mathematical N

@FACTORIAL Calculation Functions Mathematical N

@INT Calculation Functions Mathematical N

@LN Calculation Functions Mathematical N

@LOG Calculation Functions Mathematical N

@LOG10 Calculation Functions Mathematical N

@MAX Calculation Functions Mathematical N

@MAXS Calculation Functions Mathematical N

@MIN Calculation Functions Mathematical Y


18-41


@MINS Calculation Functions Mathematical N

@MOD Calculation Functions Mathematical Y

@POWER Calculation Functions Mathematical Y

@REMAINDER Calculation Functions Mathematical Y

@ROUND Calculation Functions Mathematical Y

@SUM Calculation Functions Mathematical Y

@TRUNCATE Calculation Functions Mathematical Y

@VAR Calculation Functions Mathematical Y

@VARPER Calculation Functions Mathematical N

@ALLANCESTORS Calculation Functions Member set N

@ANCEST Calculation Functions Member set Y

@ANCESTORS Calculation Functions Member set Y

@ATTRIBUTE Calculation Functions Member set Y

@BETWEEN Calculation Functions Member set N

@CHILDREN Calculation Functions Member set Y

@CURRMBR Calculation Functions Member set Y

@DESCENDANTS Calculation Functions Member set Y

@EQUAL Calculation Functions Member set Y

@EXPAND Calculation Functions Member set N

@GENMBRS Calculation Functions Member set Y

@IALLANCESTORS Calculation Functions Member set Y

@IANCESTORS Calculation Functions Member set Y

@ICHILDREN Calculation Functions Member set Y

@IDESCENDANTS Calculation Functions Member set Y

@ILANCESTORS Calculation Functions Member set Y

@ILDESCENDANTS Calculation Functions Member set N

@ILSIBLINGS Calculation Functions Member set Y

@INTERSECT Calculation Functions Member set Y

@IRSIBLINGS Calculation Functions Member set Y

@IRDESCENDANTS Calculation Functions Member set Y

@ISIBLINGS Calculation Functions Member set Y

@LANCESTORS Calculation Functions Member set Y

@LDESCENDANTS Calculation Functions Member set Y

@LEVMBRS Calculation Functions Member set Y

@LIST Calculation Functions Member set Y

@LSIBLINGS Calculation Functions Member set Y

@MATCH Calculation Functions Member set Y

@MBRCOMPARE Calculation Functions Member set Y

@MBRPARENT Calculation Functions Member set Y

@MEMBER Calculation Functions Member set Y

@MEMBERAT Calculation Functions Member set Y

@MERGE Calculation Functions Member set Y

@NEXTSIBLING Calculation Functions Member set Y

@NOTEQUAL Calculation Functions Member set Y

@PARENT Calculation Functions Member set Y


18-42


@PREVSIBLING Calculation Functions Member set Y

@RANGE Calculation Functions Member set Y

@RDESCENDANTS Calculation Functions Member set Y

@RELATIVE Calculation Functions Member set Y

@REMOVE Calculation Functions Member set Y

@RSIBLINGS Calculation Functions Member set Y

@SHIFTSIBLING Calculation Functions Member set N

@SIBLINGS Calculation Functions Member set Y

@UDA Calculation Functions Member set Y

@WITHATTR Calculation Functions Member set N

@ACCUM Calculation Functions Range and Financial Y

@AVGRANGE Calculation Functions Range and Financial Y

@COMPOUND Calculation Functions Range and Financial Y

@COMPOUNDGROWTH

Calculation Functions Range and Financial N

@CURRMBRRANGE Calculation Functions Range and Financial Y

@DECLINE Calculation Functions Range and Financial N

@GROWTH Calculation Functions Range and Financial N

@INTEREST Calculation Functions Range and Financial Y

@IRR Calculation Functions Range and Financial Y

@IRREX Calculation Functions Range and Financial N

@MAXRANGE Calculation Functions Range and Financial Y

@MAXSRANGE Calculation Functions Range and Financial N

@MDSHIFT Calculation Functions Range and Financial N

@MINRANGE Calculation Functions Range and Financial Y

@MINSRANGE Calculation Functions Range and Financial N

@NEXT Calculation Functions Range and Financial Y

@NEXTS Calculation Functions Range and Financial N

@NPV Calculation Functions Range and Financial Y

@PTD Calculation Functions Range and Financial N

@PRIOR Calculation Functions Range and Financial Y

@PRIORS Calculation Functions Range and Financial N

@RANGE Calculation Functions Range and Financial Y

@RANGEFIRSTVAL Calculation Functions Range and Financial Y

@RANGELASTVAL Calculation Functions Range and Financial Y

@SHIFT Calculation Functions Range and Financial Y

@SHIFTPLUS Calculation Functions Range and Financial Y

@SHIFTMINUS Calculation Functions Range and Financial Y

@SLN Calculation Functions Range and Financial N

@SUMRANGE Calculation Functions Range and Financial Y

@SYD Calculation Functions Range and Financial N

@XRANGE Calculation Functions Range and Financial Y

@ALLOCATE Calculation Functions Allocation N

@MDALLOCATE Calculation Functions Allocation N

@MOVAVG Calculation Functions Forecasting N


18-43


@MOVMAX Calculation Functions Forecasting N

@MOVMED Calculation Functions Forecasting N

@MOVMIN Calculation Functions Forecasting N

@MOVSUM Calculation Functions Forecasting N

@MOVSUMX Calculation Functions Forecasting N

@SPLINE Calculation Functions Forecasting N

@TREND Calculation Functions Forecasting N

@CORRELATION Calculation Functions Statistical N

@COUNT Calculation Functions Statistical Y

@MEDIAN Calculation Functions Statistical N

@MODE Calculation Functions Statistical N

@RANK Calculation Functions Statistical N

@STDEV Calculation Functions Statistical N

@STDEVP Calculation Functions Statistical N

@STDEVRANGE Calculation Functions Statistical N

@VARIANCE Calculation Functions Statistical N

@VARIANCEP Calculation Functions Statistical N

@TODATE Calculation Functions Date & Time Y

@CALCMODE Calculation Functions Misc Y

@CONCATENATE Calculation Functions Misc Y

@SUBSTRING Calculation Functions Misc Y

@NAME Calculation Functions Misc Y

@RETURN Calculation Functions Misc N

@CREATEBLOCK Calculation Functions Misc Y

+ (Adds) CalculationCommands

Mathematical Y

- (Subtracts) CalculationCommands

Mathematical Y

* (Multiplies) CalculationCommands

Mathematical Y

/ (Divides) CalculationCommands

Mathematical Y

% (EvaluatesPercentage)

CalculationCommands

Mathematical Y

( ) (Controls thecalculation order)

CalculationCommands

Mathematical Y

AGG CalculationCommands

Misc N

ARRAY CalculationCommands

Misc Y

CALC ALL CalculationCommands

CALC N

CALC AVERAGE CalculationCommands

CALC N

CALC DIM CalculationCommands

CALC Y (See Note followingtable)

CALC FIRST CalculationCommands

CALC N


18-44


CALC LAST CalculationCommands

CALC N

CALC TWOPASS CalculationCommands

Misc N

CCONV CalculationCommands

CLEAR N

CLEARBLOCK CalculationCommands

CLEAR Y

CLEARCCTRACK CalculationCommands

CLEAR N

CLEARDATA CalculationCommands

CLEAR Y

DATACOPY CalculationCommands

COPY Y

DATAEXPORT CalculationCommands

EXPORT N

DATAEXPORTCOND CalculationCommands

EXPORT N

DATAIMPORTBIN CalculationCommands

EXPORT N

EXCLUDE...ENDEXCLUDE

CalculationCommands

BLOCK N

FIX...ENDFIX CalculationCommands

BLOCK Y

FIXPARALLEL...ENDFIXPARALLEL

CalculationCommands

BLOCK N

LOOP...ENDLOOP CalculationCommands

BLOCK Y

POSTFIXPARALLEL CalculationCommands

BLOCK N

SET AGGMISSG CalculationCommands

SET N

SET CACHE CalculationCommands

SET N

SETCALCDIAGNOSTICS

CalculationCommands

SET N

SET CALCPARALLEL CalculationCommands

SET N

SET CALCTASKDIMS CalculationCommands

SET N

SET CCTRACKCALC CalculationCommands

SET N

SETCLEARUPDATESTATUS

CalculationCommands

SET N

SETCOPYMISSINGBLOCK

CalculationCommands

SET N

SETCREATEONMISSINGBLK

CalculationCommands

SET N


18-45


SETCREATEBLOCKONEQ

CalculationCommands

SET N

SETDATAEXPORTOPTIONS

CalculationCommands

SET N

SETDATAIMPORTIGNORETIMESTAMP

CalculationCommands

SET N

SETEMPTYMEMBERSETS

CalculationCommands

SET N

SETFRMLBOTTOMUP

CalculationCommands

SET N

SETFRMLRTDYNAMIC

CalculationCommands

SET N

SET LOCKBLOCK CalculationCommands

SET N

SET MSG CalculationCommands

SET N

SET NOTICE CalculationCommands

SET N

SET REMOTECALC CalculationCommands

SET N

SETRUNTIMESUBVARS

CalculationCommands

SET N

SETSCAPERSPECTIVE

CalculationCommands

SET N

SET UPDATECALC CalculationCommands

SET N

SET UPTOLOCAL CalculationCommands

SET N

THREADVAR CalculationCommands

Misc N

VAR CalculationCommands

Misc Y

Note:

@ISACCTYPE: This function only applies to Expense accounts. Any ofthese values may be used: First, Last, Average, Expense, and Twopass.

CALC DIM: You should only use CALC DIM on non-aggregated dimensions(for example, Movement, Intercompany, Multi-GAAP and Custom(s). It isrequired only if you need to reference an aggregated intersection in themiddle of your custom calculation.


18-46

Configurable Calculations Best PracticesBest Practices for Performance

Multiple Passes to Essbase

Every time the FIX statement is used in a rule, each FIX will trigger a separate pass tothe database. It would be best for performance reasons to avoid multiple passes toEssbase by not including too many separate FIX statements.


18-47

Bottom-Up versus Top-Down Processing

When Financial Consolidation and Close performs calculations, the system usesBottom-Up processing whenever possible. This is also the default option in FinancialConsolidation and Close.

If the calculations are complex where there's a need to examine every combination ofcells from all potential blocks, Essbase will perform Top-Down processing.

Using Bottom-Up processing, calculations are run only for existing blocks. Forexample, if you have A = B + C, the system will only calculate A if there is data ineither B or C. If both B or C blocks are empty, the system will not calculate A.

In the case of Top Down processing, if A = B > D + C > D, Essbase will look at allpotential data blocks with members in the database and look for the possiblecombination of the source (that is, B > D and C > D) and then perform the calculations.In this case, cross-referencing makes the calculation complex. The calculation couldbe rewritten to eliminate the cross-reference, thus making it faster.

For more information, see https://docs.oracle.com/cd/E57185_01/ESBTR/calcmode_func.html.

Example: Top-Down Processing

Suppose you are trying to reclassify data from "Closing Balance-Input" > "Data Input"to "Mvmts_Changes" > "Reclass_Data Input".


18-48

https://docs.oracle.com/cd/E57185_01/ESBTR/calcmode_func.html

https://docs.oracle.com/cd/E57185_01/ESBTR/calcmode_func.html

Example: Bottom-Up Processing

If you rewrite the above statements to use Bottom-Up processing, you can havepotential performance gain depending on how many data blocks exist in the database.

Note that the system will only run for those blocks in which data exists for "ClosingBalance Input" > "Data Input".

Writing to Restricted Members

In this example, suppose you want to reclassify "FCCS_Intercompany Eliminations" >"FCCS_Eliminations" > "Mvmts_NewBusiness" to "Data Input" > "FCCS_Eliminations"> "Mvmts Reclass."

However, since "FCCS_Intercompany Eliminations" is a restricted member for theData Source dimension, if you try to use a FIX on this member, the system returns anerror.

You can try to write the following statements, which force the system to use Top Downprocessing.

Example: Working with restricted members

Example: Rewrite the statements using Bottom-Up Processing


18-49

Note that in this example, you have a FIX on "FCCS_Intercompany Eliminations", butoverride it with "Data Input" in the member block, and the system will not return anerror during validation.

Entering Data in Closing Balance Input and Calculating Movement Based onUDAs

In this example, suppose you want to move Closing Balance Input into a specificMovement member. You could write a custom calculation with these requirements:

• Fix on sparse dimension member combinations together for Bottom-Upprocessing. Bottom-Up processing is related to blocks, and sparse dimensionsdefine a block.

• User-defined attributes (UDAs) are best processed together with a FIX on the UDAaccounts, to perform the same calculation.

• The example below assumes that all specified UDAs are defined on ASSET /LIABILITY / EQUITY Account Types.

• FIX on level zero Account dimension members relative to FCCS_Net Income

• Use a Boolean function rather than calculate member's level using @LEV forperformance improvement

• Use Boolean function @ISDESC to check if the member is a descendant. It willalways be a leaf member.

Example: Entering Data in Closing Balance Input and Calculating MovementBased on UDAs


18-50


18-51

Best Way to Use IF Condition

Below is a common example when you write the conditional statements using IF. Inthis example, you want to do a specific process in January, but do something differentfor the other months. If the calculation is written as below, the system will go throughthe check 12 times for all periods other than January, since it always checks forJanuary first, and then branch off to the ELSE clause.

Example: IF statement

Example: Rewrite using NOT IF

You can rewrite the IF statement so that 11 out of the 12 periods will get executed withthe IF clause and then drop out of the conditional branch. Only January will getexecuted in the ELSE clause once.

Using Top Custom Member System Calculation Option with ExtendedDimensionality

For user-defined Custom dimensions, Service Administrators can select to processSystem Calculations using the Top Member of the Custom dimension, instead of alllevel 0 members, for faster performance. You can select specific Custom dimensionsfor which the option would apply. See System Calculations.


18-52

If you are using an Extended Dimensionality environment, to make sure using theCustom Top Member does not slow down performance, you can create an emptyblock at "NoCustomX" at the beginning of the consolidation based on the Entity Inputand Entity Currency data, and use that block to perform all the calculations. Forexample, if you have 1000 Custom members in the Product Custom dimension, youcan create one block @"No Product", FIX on "No Product", and use Bottom-Upprocessing. The system then does not need to loop through all 1000 members of theProduct dimension, and you can use "Total Product" for the total value to improveoverall performance.

The following example shows a sample Calc Script:

Calculating FCCS_10 Member Blocks using Bottom-Up Processing

1. Use @CALCMODE(BOTTOMUP) and combine member block calculations.

2. Combine calculations in multiple FIX...ENDFIX into a single FIX...ENDFIX, if FIXmembers are the same across calculations.

Avoid FIX within FIX, if it is just a single calculation.

The following examples show running the calculation using Top-Down processing, andthen a modified example using Bottom-Up processing to improve query processing onthe right-hand side.

Example: Running FCCS_20 C1_Validation Using Top-Down Processing

Example: Running FCCS_20 C1_Validation Using Bottom-Up Processing


18-53

Best Practices for Creating Data Blocks

When a configurable calculation that writes to a data cell is executed, a data blockmust exist for data to be written to the database.

Data blocks are combinations of stored Sparse and Dense dimension members.

Separate data blocks are created for each combination of stored Sparse dimensions.The members in a Dense dimension equal one block.

When you create configurable calculations, you may need to create additional blocksto store the calculated results and resolve issues with missing data.

You can enable the Auto Create Blocks option to have the system automatically createmissing blocks. See Enabling Auto Create Blocks for Configurable Calculations.

If you use Bottom-Up processing in your configurable calculations, you shouldmanually create data blocks or ensure that data blocks already exist.

You can manually create data blocks using one of these methods:

• Assigning data during the data load process. For example, write a “Zero” to asingle Dense member intersection, and then write “#missing” to clear the “Zero”after block creation.

• Using the Essbase DATACOPY command, in which all blocks from the source arecopied to the destination, including the missing cells. However, this method canpotentially create unnecessary blocks and slow the consolidation process.


18-54

Creating Target Data Blocks for @SHIFT and @PRIOR Functions

When you use the @SHIFT or @PRIOR functions in calculation scripts, the target datablocks must exist before you can run the calculation. The target data blocks must existas either part of another calculation or data load, or must be created using the@CREATEBLOCK function.

Example Use Case:

Data exists in Actual, FY16, P12, ML_HFM. The data is being pulled from OracleHyperion Financial Management, and has not been loaded in Actual, FY16, P1,ML_HFM. The data must be retrieved from the prior year's P12 period, and a reversalentry should be reflected at Actual, FY17, P1, ML_HFM_Calc.

The calculation script is as follows:

No journals have been posted ("FCCS_Journal Input" in P13. The code is expected totake the following path, with "ML_HFM_Calc" as the sparse member anchor:

@SHIFT("P12"->"ML_HFM", -1, @CHILDREN("Years"));However, this returns #MISSING.

Workaround 1:


18-55

Workaround 2:


18-56

ClearEmptyBlocks Rule Guidelines

The ClearEmptyBlocks business rule helps to scavenge the Consol cube for anyempty data blocks. Empty data blocks could be generated as part of:

• OnDemand rule execution that generates empty blocks. For example, using the@CREATEBLOCK function, and then possibly a generated empty data blocknever gets utilized.

• An insertion point code (for example, FCCS_20) that possibly has block leaks dueto TOPDOWN calculations, perhaps from assigning #MISSING; using sparseanchors, instead of using @CALCMODE(BOTTOM UP)


18-57

• Financial Consolidation and Close System Calculations

Recommended Practice to Run ClearEmptyBlocks Rule

• A best practice is to run the rule after finishing any OnDemand Rule/insertion pointtests, when the script is in development phase. The ClearEmptyBlocks rule helpsto measure block statistics before and after execution of the calculation underdevelopment.

• In production phase, execute the rule after finishing a full year consolidation for agiven year.

An EPM Automate script could be scheduled to run after office hours, every weekend*:

call epmautomate runbusinessrule ClearEmptyBlocks Scenario ="<Scenario>" Year = "<Particular Year>"

Period = "ILv10Descendants(YearTotal)"

call epmautomate restructurecube Consol

*The schedule for this scavenge activity must maintain at least a gap of 3-4 hours withthe Daily Maintenance Cycle.

Calculation at Parent Currency Dependency

You should avoid dependencies between entities when calculations are done at theParent Currency. Since Parent Currency value must be translated first, if you try toreference Entity A's Parent Currency value in the calculation, if Entity A has not yetbeen consolidated, then the Parent Currency value of Entity A would have no value.

For example, if you try to reclassify data from "Entity A" > "ICP_B" > "Parent Currency"(source) to "Entity B" > "ICP_A" > "Parent Currency" (destination), data in Entity A(source) may not be available, since it may not have been consolidated, as bothentities Entity A and Entity B are being consolidated in parallel.

Therefore, in this case, the reclassification should be attempted at "Entity Currency"level and then it will be translated to "Parent Currency".

Best Practices for Calculations in Extended DimensionalityApplications

Extended Dimensionality Scripting Techniques

In Extended Dimensionality base applications, there are changes on the applicationmodeling side. Some of the key changes include:

1. Dimension order. The Movement dimension is the first sparse dimension in thedimension order, known as a bitmap dimension.

2. Intercompany dimension’s parent members are Dynamic Calc.

3. All Custom dimensions must have their parent members set to Dynamic Calc.

4. The idea is to have minimal upper level block count, and achieve dynamicaggregations during spreadsheet operations.


18-58

5. Points 2 and 3 above play a significant role while writing customized calculations,apart from the need to rewrite existing calculations, if Top/Parent members areused in existing calculations.

Avoid the following constructs:

1. CALC DIM, CALC ALL, AGG, and any other assignment-free expressions thatcalculate a sub-tree. A best practice is to limit use of CALC DIM and AGG todimensions where no stored members are dependent on dynamic members.

2. Do not use CREATENONMISSINGBLOCK or CREATEBLOCKONEQ incalculation scripts.

3. Avoid using these functions inside insertion points:

• @ALLOCATE

• @CREATEBLOCK

• @IRREX

• @MDALLOCATE

• @MDSHIFT

• @MOVSUMX

• @PTD

• @SANCESTVAL

• @STDEV

• @STDEVP

• @STDEVRANGE

• @SYD

• @TREND


18-59

Using a Sparse Member Block and BOTTOMUP

The Movement member "FCCS_Mvmts_NetIncome" is used as an anchor. TheMovement dimension is considered a bitmap dimension. It is the first sparsedimension after the Account dense dimension. As much as possible, calculationsinvolving a single Movement dimension member should use the Movement member asmember block (known as an anchor).

Calculation Involving Top/Parent Members as Source

1. Top members are Dynamic Calc, and cannot be used in FIX expressions, so usethem on the right hand side of calculation and redirect result to “No <member>”.

2. A single dense dimension member that stores the result of calculation, is to beplaced in FIX.


18-60

Best Practices for Calculations in Extended Dimensionality Applications

• Use BottomUp processing only when the right hand side calculation does notinvolve Top/Parent member(s).

• Use @Remove to remove Account instead of using @ISMBR check on Accountdense dimension.

• Use Boolean @ISLEV instead of @LEV and @CURRMBR.

• Remove restricted members from the FIX.

• Use Copy to create the target block if anchor approach does not work.

• Calculation should be performed only on one target Custom dimension member.

• Use @LIKE to make the script generic.

• Check for edge cases.

• Check for common cases first

• When calculations write to a single Movement dimension member, use theMovement member as a member block, known as an anchor.

• When calculations write to a single Account dimension member, move Accountmember to FIX.

Extended Dimension applications use a Hybrid aggregation mode. The SETHYBRIDBSOINCALCSCRIPT construct is available as part of Calculation Managerand controls whether cubes in the application use hybrid aggregation mode incalculation scripts when stored members depend on dynamic members.

For a list of Essbase Functions supported in Extended Dimensionality applications,see "Functions Supported in Hybrid Aggregation Mode" in Oracle Essbase TechnicalReference.

Customer A Use Case

In this use case, the original calculations included these issues:

• Manual Cash Flow calculations

• Performance was slow when Cash Flow calculations were inserted in insertionpoints versus without the calculations. One entity took two minues to consolidate,versus 40 seconds without the calculation.

• The calculation could not use the seeded Cash Flow due to their statutorypractices.

Original Calculations

The calculation does not perform well due to the following reasons:


18-61

1. The right-hand side calculations are basically queries to Essbase, because mostparent members of the respective dimensions are Dynamic Calc.

2. In the above case, two simultaneous queries are being launched, and only whenresults are fetched, will the actual calculation initiate., which leads to a slowformula cache.

3. The above script executes for every entity, during a consolidation, irrespective ofentity level.

Revised Calculation

The following example shows a revised calculation.

Equity Pickup OverviewBackground

A legal entity can be defined as:

An association, corporation, partnership, proprietorship, trust, or individual that haslegal standing in the eyes of law. A legal entity has legal capacity to enter intoagreements or contracts, assume obligations, incur and pay debts, sue and be sued inits own right, and to be held responsible for its actions.

A limited company (LC) is a form of incorporation that limits the amount of liabilityundertaken by the company's shareholders. A public limited company (PLC) is acompany whose securities are traded on a stock exchange and can be bought andsold by anyone.

Most major corporations consist of many companies that were brought together over aseries of years to create a corporate enterprise. The business combination of thesecompanies is carried out through share ownership between the companies.

Each company must report financial statements in accordance with the requirementsof the jurisdiction in which they operate. For example, all limited companiesincorporated in the UK must report to “Companies House”, the governmentorganization that is responsible for registering limited companies. Public limitedcompanies must also report in accordance with the requirements of the stockexchange on which they are registered. These public limited companies are required

Chapter 18Equity Pickup Overview

18-62

to report the consolidated financial results not only of the individual company but alsoof the companies in which they have an ownership interest.

A company that owns shares of other companies can be referred to as a “holding”company. This holding company might directly own all shares of another company,many shares or only a few shares. A holding company might also own shares in acompany that itself owns shares in another company, creating indirect ownership. Theextent to which a holding company controls the owned company determines how theresults of the owned company are to be combined with the results of the holdingcompany when presenting the consolidated results.

Generally, if a holding company owns in excess of 50% of another company’s votingshares then the owned company is “controlled” by the holding company. If a holdingcompany owns in excess of 20% but no more than 50% of the voting shares ofanother company then the holding company is deemed to have “significant influence”but not control of the owned company. If a holding company owns up to 20% of thevoting shares of another company then the holding company is deemed to haveneither significant influence nor control of the owned company.

A legal company generally records their investments in other legal companies usingthe “cost” method of accounting, except where required by local regulation. Under thecost method of accounting, the share purchase is recorded by the holding company atthe initial cost on the date of acquisition and generally remains without change untildisposal. When the shares are sold, any gain or loss on the investment is dulyrecorded. An alternative investment accounting method is the equity method. Underthe equity method, the initial cost recorded at the time of acquisition is adjustedperiodically based on the holding company’s share of profits or losses recorded by thecompany in which the investment is held.

This accounting method when applied to reporting by a legal company will be referredto as “Equity Pickup” (EPU) to distinguish it from the equity consolidation method.Equity Pickup is applied to the investments made and recorded by a legal company intheir legal company records. The equity consolidation method is used when a legalcompany aggregates data from the companies in which it has a direct or indirectownership and reports the consolidated results. The principle behind Equity Pickupaccounting and the equity consolidation method is essentially the same but is appliedunder different circumstances (legal company results vs. consolidated results).

To record the results of Equity Pickup, the holding company’s share of the change inOwner’s Equity for the period (generally profit or loss of the owned company, less theholding company’s share of any dividends declared), is recorded in the holdingcompany’s accounting records as income and as a corresponding increase in thevalue of the investment in the associated company. Any share of earnings of indirectlyheld companies is recorded by virtue of the owned company’s reported income havingalready recorded their equity earnings of all companies that they own.

In complex multi-level ownership structures, a specific sequence of Equity Pickupcalculations is required in order to achieve the correct results. For example, ifcompany A owns shares in Company B and Company B in turn owns shares incompany C, then the Equity Pickup for company B must be calculated before theEquity Pickup for company A is calculated, to ensure that the earnings and investmentadjustment made in company B is subsequently reflected accurately in company A.

Prerequisites

The Equity Pickup feature of Financial Consolidation and Close is based on thefollowing configuration settings and requirements:


18-63

• The Entity dimension hierarchy accurately represents the direct ownershiprelationships between holding companies and companies for which EPU will beapplied.

• The entities in the Entity dimension can be identified as legal companies.

• There is only one Holding method company under each parent entity and theentity currency of the Holding company and the parent entity is the same currency.

• If the EPU reported for each Holding company is to be identified by each legalcompany in which the holding company has either a direct or indirect ownershipinterest then:

All legal companies in the Entity dimension must be flagged as intercompany inthe Entity dimension and exist as level 0 entities in the Intercompany dimension

• If the EPU reported for each Holding company is to be identified by each legalcompany in which the holding company has only a direct ownership interest, withindirect ownership being grouped within “interim” directly owned holdingcompanies, then:

All legal companies and all parent entities in the Entity dimension must bespecified as Intercompany in the Entity dimension and exist as level 0 entities inthe Intercompany dimension.

See these topics:

• Enabling Equity Pickup

• Equity Pickup Processing

Watch the following video for information on equity pickup:

Seeded Consolidation Rules

Enabling Equity PickupBefore you can use the Equity Pickup feature, you must enable it from one of thesemethods:

• Application creation. See Creating an Application.


18-64


• From the Enablement screen after application creation. See Enabling ApplicationFeatures.

Note:

You can only enable Equity Pickup if the Ownership Management feature isenabled.


18-65

Metadata Changes for Equity Pickup

Enabling Equity-Pick-up will:

• Create the required metadata:

– Equity Pickup Income Statement and Balance Sheet accounts

– Equity Pickup source account (memo account)

– Equity Pickup DataSource member

• Accounts:

Data Source:

Once enabled, the seeded Equity Pickup metadata cannot be subsequentlyremoved.

• Add an EPU System Calculation rule in the Local Currency tab of theConsolidation: Process screen.

•

The Calculation Setting for the rule will be “Yes” (Active) when EPU is firstenabled.


18-66

If the Equity Pickup Calculation Setting is changed to “No” (Inactive), then theapplication will revert to non-EPU behavior.

For the Equity Pickup system rule, you can select an alternative Movementmember other than the default member. By default, the system rule uses theFCCS_Mvmts NetIncome member. An administrator can change the defaultentries to single level 0 members under FCCS_Mvmts Subtotal from theMovements dimension. From Equity Pickup Movement Members, click the Editicon to open the Member Selector and select members from the Movementsdimension, and then click OK.

• Add four seeded Configurable Consolidation rule-sets (three in a Deployed state,one un-deployed)

Consolidation Rules for Equity Pickup

The consolidation rule-sets deployed will determine:

• What source data set is used to generate the EPU results posted to each holdingcompany

• How the EPU results will be identified (all directly / indirectly owned companiesidentified separately or indirectly owned companies grouped within directly ownedcompanies)

• Whether the EPU results should be posted to a single member in each user-created Custom dimension (if any) or on a level 0 member-by-member basis

The four seeded consolidation rule-sets provide the following options:

EPU – Prepare Data Source


18-67

This rule-set gathers source data from the owned company for Total Equity excludingEquity Company Income.

For each client-created custom dimension, combines all level 0 data into a single “No<custom>” member for subsequent reporting.

This rule-set can be copied and the copy modified and deployed if required (for furtherdetails on copying and modifying rule-sets, see Managing Consolidation Rule-sets andRules). For example, if data is to be reported separately for all level 0 members of anapplication-specific custom dimension, then that dimension should be removed fromthe Scope of the copied rule-set. The EPU data will then be processed for eachmember of that dimension instead of being grouped into a single member. Be awarethat this might have a performance impact on the application.

EPU – Consolidate EPU Source Data


18-68

This rule-set consolidates the source data initially gathered by the first rule-set at theOwnership % and identifies the source directly or indirectly owned legal company fromwhich the data was derived

The source legal company is identified by the Intercompany member used whenconsolidating the data.

Note that all legal companies must therefore be identified is ICP_Entity_Yes in theEntity dimension such that a matching base member is created in the Intercompanydimension.

EPU – Consolidate EPU Source Data Indirect Grouping


18-69

This rule-set consolidates the source data initially gathered by the first rule-set at theOwnership % and identifies the source directly owned legal company from which thedata was derived.

The source legal company is identified by the Intercompany member used whenconsolidating the data.

Note that all legal companies and all parent entities must therefore be identified isIC_Entity_Yes in the Entity dimension such that a matching base member is created inthe Intercompany dimension.

Either the EPU – Consolidate EPU Source Data rule-set or the EPU – ConsolidateEPU Source Data Indirect Grouping rule-set should be deployed, but not both.

EPU – Reverse Holding Company Data


18-70

This rule-set reverses the Equity Pickup results posted to the holding company whenconsolidating to its parent.

The parent member represents the consolidated results of the holding company. Theinvestment in subsidiaries is recorded by different methods and calculations inconsolidated statements than those used in the legal (holding) company results.

The Reverse Holding Company Data rule-set will be applied to any movements towhich the system rule has written data.

Three of the four seeded consolidation rule-sets provided will be deployed whenEquity Pickup is initially enabled. If the Equity Pickup Calculation Setting is changedfrom “Yes” to “No”, the deployed EPU rule-sets should be un-deployed by the systemadministrator. If the Calculation Setting is changed from “No” to “Yes”, then therequired rule-sets (seeded or copied / modified) must be deployed by the systemadministrator.

Equity Pickup ProcessingDuring a regular consolidation process, the calculation of entities is based on abottom-up level-by-level approach starting from the lowest level of the entity hierarchy.The first group of entities to be calculated are all base (level 0) members (thoseentities that have no children). The next group to be processed are the level 1 parententities (those entities with no more than one level of descendants below them). Thenlevel 2 parents, and so on. This process ensures that all children of a parent entity areprocessed before that parent entity.

The sequence of processing required for correct Equity Pickup calculations is basedinstead on a bottom-up generation-by-generation approach. The top member isgeneration 0 and then each subsequent step down adds a generation. With thisapproach, each holding company is in the same generation as its siblings, whetherthose siblings are parent or base members. All level 0 non-holding entities areprocessed first. Then the highest generation of holding companies are processed,followed by the highest generation of parent entities, followed by the next highest


18-71

generation of holding company entities and then the next highest generation of parententities... and so on..

The following diagrams show the difference in processing in a very simple hierarchy(where legal company A owns legal companies B and D, and legal company B ownslegal company C). Equity Pickup processes by generation from the bottom up. Thestandard sequencing processes by level from the bottom up:

Entities in scope for processing

Consolidation considers the calculation status of each entity when determining whichentities are “in scope” for processing. When an entity is “Impacted”, that entity needsto be re-calculated to take into account any changes that caused the impacting. Inaddition, all ancestors of the entity are also impacted because their results need to bere-calculated due to the re-calculation of an entity on which their results aredependent. Similarly, subsequent periods of the same scenario al also impacted.

Example 1 – data entry to entity C

For the standard consolidation process, if data is entered to entity C in the exampleabove, then entities C, B Consolidated and A Consolidated are impacted. If AConsolidated is selected for consolidation, all three entities (C, B Consolidated and AConsolidated) will be re-calculated in sequence from level 0 to level 2.

For the Equity Pickup process, if data is entered to entity C, then entities C, BConsolidated and A Consolidated are all impacted, but in addition, entities B and Aalso need to be re-calculated because their data is dependent on the re-calculateddata from entity C. If A Consolidated is selected for consolidation, all entities (C, B, BConsolidated, A and A Consolidated) will be re-calculated in sequence fromGeneration 3 to Generation 1.

Example 2 – data entry to entity A and entity C

For the standard consolidation process, if data is entered to entities A and C in theexample above, then entities C, B Consolidated, A and A Consolidated are impacted.If A is selected for consolidation, only A will be re-calculated.

For the Equity Pickup process, if data is entered to entities A and C, then entities C, BConsolidated, A and A Consolidated are all impacted, but in addition, entity B alsoneeds to be re-calculated because its data is dependent on the re-calculated data fromentity C. If A is selected for consolidation, all entities except A Consolidated (C, B, BConsolidated and A) will be re-calculated in sequence from Generation 3 toGeneration 2 Holding. Consolidating entity A brings B Consolidated and its impacteddescendants into the scope of the consolidation process.


18-72

However, note that if no data is entered to A, selecting A for consolidation will notprocess a consolidation because A itself is not impacted. In this case, to update allentities, A Consolidated would need to be selected for consolidation as described inExample 1.

Example Equity Pickup calculation flow and required results

In order to ensure that when an Equity Pickup calculation is executed, the siblingsource entity data has already been updated, entities need to be calculated in therequired sequence as determined by the ownership chain.

Following is an example ownership chain:


18-73


18-74

Working with On-Demand RulesOn-Demand Rules are ad-hoc rules that can be used for calculations outside of theconsolidation process. An administrator can create on-demand rules to be executed byother users at any time.

Users who have launch permissions can invoke on-demand rules from data forms,Oracle Smart View for Office, post-Data Load processing, journal posting,Supplemental Data posting, or from the Rules card. You can verify or adjust an on-demand rule before invoking consolidation, since it is independent from theconsolidation process. You can execute calculations regardless of the currentcalculation status.

Using on-demand rules outside of the consolidation process reduces consolidationtime, since these calculations do not need to be repeated for each consolidation. Forexample, reclassification or adjustments, or loading life-to-date balances andredirecting them to the appropriate Movement members are calculations that may onlyneed to be executed one time. They are not required to be calculated every time aconsolidation process is launched.

You can attach on-demand rules to a data form so that you can execute thecalculations and verify the results while viewing the data in the form. This method isfaster than running a consolidation to view the results.

See Creating On-Demand Rules, and Adding On-Demand Rules to Data Forms.

You can also create customized calculations using Configurable Calculation rules. See Creating Configurable Calculations.

You create both on-demand rules and Configurable Calculation rules in CalculationManager using Essbase script statements.

• On-demand rules are executed on an as-needed basis outside of the consolidationprocess.

• Configurable Calculation rules are always executed as part of the consolidationprocess.

The following table is a summary of the features of On-Demand Rules andConfigurable Calculations.

Feature Summary On-Demand Rules Configurable Calculations

Rule content created byAdministrator

Yes Yes

No restriction of number ofrules created

Yes

Always executed as part ofConsolidation Process

Yes

Execute stand-alone ondemand

Yes

Execute regardless of existingCalculation Status

Yes

Launch from Data Form/Smart View /Rules card

Yes

Chapter 18Working with On-Demand Rules

18-75

Feature Summary On-Demand Rules Configurable Calculations

Calculation Managersupport Yes Yes

Support most Essbasefunctions

Yes Yes

Ability to write to ParentCurrency

Yes

Ability to write to EliminationConsolidation member

Yes

Ability to write to IntercompanyEliminations Data Sourcemember

Yes

User handling ofhousekeeping logic (SET,Block, Calc Dim)

Yes

Calculation Status Update Yes Yes

Validate and Deploy Rule Yes Yes

Import and Export Rule Yes Yes

Follow same best practices forrule writing

Yes Yes

Guidelines for On-Demand RulesYou create on-demand rules using Calculation Manager.

Templates can be dragged and dropped inside a rule. You can deploy a rule that usestemplates, but templates cannot be deployed standalone.

Replacement Variables

When you add a new rule, Calculation Manager automatically creates six systemReplacement Variables for the rule as Run-Time Prompts for the Scenario, Year,Period, Entity, Consolidation, and Currency dimensions. Users use the run-timeprompts to select members for these dimensions when they launch the rule. You canchange the run-time prompt texts for these variables, but you cannot remove them.Users can override the default member at run-time.

You can define additional Replacement Variables if needed for your rule.

When you launch an on-demand rule from the Rules card for the first time, if a defaultmember was not specified for a run-time prompt, the prompt is blank. On subsequentlaunches of the rule, the prompt displays the last member used.

When you launch on-demand rules from a form, the Run-Time Prompts by defaultdisplay the members from the Point of View of the currently selected cell. However, ifyou would like the system to always use a specific member for the dimension, you canselect the option to override with a specified value for the variable. If you specify avalue in Use as Override Value, it will also be used in the Rules card.

If you select the Is Hidden option for the replacement variable, the system will notprompt the user for the value at run time, but will use the value specified in theReplacement Variable definition for that variable. This option is the same wheninvoking from a Data Form or from the Rules card.


18-76

You can view all six system replacement variables as part of the rule in the Variabletab of the rule.

You must a enter a Value in the Validation column for the variable so that rule can bevalidated before deployment.

When you validate the rule, you must provide members for any of the Run-TimePrompt dimensions for which you did not provide a default in the Value column.

Dimension Members Supported for On-Demand Rules

On-Demand rules automatically insert the OUTER FIX statements for the followingdimensions as part of the rule script. You do not need to include these dimensions aspart of the FIX statement in the script. The value for these dimensions is provided inthe popup prompt where the users enters the values. The system uses default valuesfrom the source (for example, the cell POV if launched from a data form or a OracleSmart View for Office grid), but users can change the value before executing the rule.

See Working with Essbase Calc Script.

These members are supported for Run-Time Prompts in on-demand rules:

• Scenario - you must select one base member.

• Year - you must select one year.

• Period - you must select one base member.

• Entity - you can select one or more base or parent entities or functions.

• Currency - you can only select Entity Currency.

• Consolidation - you can only select Entity Input.

The following dimensions are not available for Run-Time Prompts, but are alsosupported for on-demand rules:

• View - you can only select Periodic view. The Periodic View member must bespecified in either the FIX statement or as a Target.

• Account and Movement - see Working with Essbase Calc Script. If you do notspecify members for any of these dimensions, the system processes the rule forall members. You should exclude any system-restricted members in the FIXstatement.

• Data Source - see Working with Essbase Calc Script.

Note:

The FCCS_Intercompany Eliminations member is not valid for on-demand rules.

• Multi-GAAP, Intercompany and Custom - If you do not specify members for thesedimensions, the system will process rules for all members in the dimension.

Best Practices for On-Demand Rules

For best practices on creating rules, see Configurable Calculations Best Practices and Working with Essbase Calc Script.


18-77

When you create an on-demand rule, you may need to include this logic:

• Include any SET commands required for Essbase to ensure proper settings

• Include any CREATE blocks or CLEAR Blocks command

• Include an appropriate CALC DIM statement for non-aggregated dimensions

The system will include the following sections in on-demand rules:

• Include OUTER FIX statement from the prompt

• Include any status handling routine

Creating On-Demand RulesYou can add custom rules to your application either to the consolidation process or ason-demand rules. Configurable Consolidation and Configurable Calculation rules runautomatically during consolidation. On-demand rules run when a user launches themfrom the Rules card or from a data form. They do not run as part of consolidation.

On-demand rules are also available in Oracle Smart View for Office, and as part ofpost-data load processing from Data Load.

You must be an Administrator to create, edit, or delete on-demand rules.Administrators can run on-demand rules, but Power Users and Users can only runthem if the Administrator provides launch permissions, and if they have access to theScenario, Year, Period, and Entity.

You can also add on-demand rules to forms. See Adding On-Demand Rules to DataForms.

Note:

You add on-demand rules to the Consol cube. You cannot add them to theRates cube. The Consol cube is seeded with six placeholder rules forConfigurable Calculations. You cannot delete or rename these rules.

To create on-demand rules:


2. Under Create and Manage, click Rules.

Calculation Manager opens and displays both System-created rules and User-defined rules.

3. Expand the "Planning" folder and navigate to the "FCCS Consol Rules" folder.

4. Right-click on the Rules folder and select New.

5. Enter a rule name and click OK.

The name must be unique and cannot start with the FCCS_. prefix. This prefix isreserved for seeded rules. You also cannot use the name of an existing systemrule, including ClearEmptyBlocks, Consolidate, ForceConsolidate, ForceTranslate,or Translate.


18-78

6. For Application Type, use "Planning". For Application, use the name of yourapplication.

7. For Cube, use the default setting of Consol.

The system will open to the Script editor where you can enter your scriptstatements. If you prefer to work in the graphical mode, you can change toDesigner in the drop-down list.

For a list of supported functions, see Working with Custom Defined Functions.

8. In the Properties pane, you can enter an optional description and comment for therule.

9. In the Value column, select default members for the Run-Time Prompts for theConsolidation, Currency, Entity, Period, Scenario, and Year dimensions:

• You must have Write access to the Scenario, Year, Period and Entity.

• For the Currency dimension, only "Entity Currency" is supported.

• For the Consolidation Dimension, only "Entity Input" is supported.

• If you use shared entities, you must explicitly define both the primary andshared entities in the Run-Time Prompt, in order for the shared entities to beimpacted.

• Note that the FIX statements in on-demand rules cannot include any run-timeprompt dimensions. You also cannot use run-time prompt dimensions in theleft side or Target side of formulas, although you can use these dimensions onthe right side or Source side.

10. To validate the rule, from the Actions menu, select Validate and Save.

You must specify members for any of the Run-Time Prompt dimensions for whichyou did not previously specify a default value.

If validation fails, from the Home page, click Application, and then click Jobs toview the job details.

11. From the confirmation prompt, click OK.

12. To view the rule, navigate to the Rules folder and right-click Refresh.

The new rule is displayed in the Rules list. On-demand rules are listed inalphabetical order after the seeded configurable calculation rules.

It does not become active until it is deployed.

13. To deploy the rule, from the Actions menu, select Deploy.

You cannot undeploy a rule after it has been deployed. If the rule is no longerneeded, you can delete it.

14. From the confirmation prompt, click OK.

15. To verify that the rule was deployed, on the Home page, click Rules and clickRefresh.

The deployed rule will be displayed in the list of rules after the system rules.

Adding On-Demand Rules to Data FormsYou can add on-demand rules to forms, by adding menu options to the Action menufor a form, or by adding the rules to the list of rules in the Business Rules dialog box.


18-79


When users are viewing or entering data in the form, they can execute the assignedon-demand rule from within the form so that they can see the calculated results in theform after execution.

To launch rules from a form, users must be assigned both access to the form andlaunch permissions for the rule. See Assigning Access to Rules.

To create Custom Menus for the calculation to be included as part of the form Actionmenu, see "Defining Action Menu Items" in Administering Planning Using theSimplified Interface.

To include on-demand rules as part of the Business Rules menu, you use theBusiness Rules tab of the Form designer.

You can decide how you want the on-demand rule to be processed for the form basedon the properties assigned for the business rule. For example, you can define an on-demand rule for the form with these actions:

• Run before loading the form

• Run after the form is loaded with data

• Run before saving the form data

• Use the members invoked from form

• Hide Run-Time Prompts

To add on-demand rules to a data form:


2. Under Create and Manage, click Action Menus.

3. Click New and enter a rule name, then click OK.

4. Select the menu, click Edit, and then click Add Child.

5. For Menu Item, enter a name for the menu option.

6. For Label, enter the menu text that you want to display to users.

Optional: You can provide a path to a graphic file on the server in the Icon field.

7. For Type, select Business Rule.

8. For Cube list, select Consol.

9. In the Business Rules list, select an on-demand rule.

You can enter a description or instructions for the rule in the Launch ConfirmationMessage field.

10. Use the Hide Prompt option to suppress the run-time prompts for the rule. If youhide the run-time prompts, the members in the current cell point of view are usedfor the run time prompt dimensions when the rule is launched. If override valueshave been defined in Calculation Manager, the override values are used.

11. Click Save to save the menu item, and then click Save again to save the menu.

12. Click the Navigator icon

13. Under Create and Manage, click Forms to open the form editor.

14. Select the Other Options tab to assign the menu to a form.

15. Click Finish.


18-80

To add on-demand rules to the list of business rules available from the BusinessRules dialog box:


2. Under Create and Manage, click Forms to open the form editor.

3. Select the Business Rules tab to add on demand rules to the list of businessrules.

4. In the Business Rules Properties area, specify options for the rule.

5. Click Finish.

To view and launch the rule in a form, see Launching On-Demand Rules.

Importing and Exporting On Demand RulesAdministrators can use the options available in Calculation Manager to import orexport on-demand rules.

To import on-demand rules:




4. Right-click Rules and select Import.

5. Click Browse and select the rule file to import.

To export on-demand rules:




4. Right-click Rules and select Export.

When you select the Export option, the system automatically exports all ruleswithin the folder, including the seeded calculation rules as well as the on-demandrules.

To export an individual on-demand rule, right-click on the rule and then select theExport option.

5. Specify a location in which to save the exported file.

Launching On-Demand RulesBy default, only Administrators can run on-demand rules. Other users can view andrun on-demand rules only if the Administrator assigns them launch access and if theyhave security access to the Scenario, Year, Period and Entity. See Assigning Accessto Rules.

You can launch on-demand rules using:

• Rules card

• Data forms


18-81

• Oracle Smart View for Office

Launching On-Demand Rules from the Rules Card

The Rules card displays a list of both System rules and User-defined On-Demandrules.

Users who have Launch permissions to rules can launch the rules.

To launch on-demand rules from the Rules card:

1. On the Home page, click Rules.

2. To filter the list of rules, click the Filter icon.

Only on-demand rules that have been deployed are displayed.

3. From the Cube drop-down list, select Consol.

On-demand rules are listed in alphabetical order after the system rules, and are

identified by a User icon:

4. From the list of rules, select an on-demand rule and click Launch.

To launch business rules, the rules must be deployed from Calculation Manager.

5. The system displays a popup window for you to enter dimension member valuesfor the Run-Time Prompts defined for the rule. If the rule is launched for the firsttime, the values in the prompt will be blank. Once a value has been entered for therule, the system will display the last value used as the default, but you can changeit if needed.

Note:

For the Entity dimension, you can specify multiple entities or a memberlist, but for all other dimensions, you specify only one member.

Launching On-Demand Rules from Data Forms

Administrators can attach an on-demand rule to a data entry form. When users view orenter data in the form, they can execute the on-demand rule from within the data form,so that the calculated results are displayed in the form after execution.

When you create on-demand rules, you specify Run-Time Prompts for Scenario, Year,Period, Entity, Currency, and Consolidation dimension members. You cannnot removeany system Run-Time Prompts, but you can modify them before launching the rule.

If the setting is selected to use the members in the form, the system automaticallydisplays the current members of the selected cell for the popup when the rule isinvoked. Only one member from each dimension is displayed in the run-time prompt.

The system will display only the Business Rules you have assigned to the form foruser to select. After selection, the system will display the Run-Time Prompt valuesbased on your POV selection.

If the user selects a block of cells by selecting an entire row or column when theylaunch the rule, the system uses the cell from upper-top-left corner as the selectioncell for the Run-Time Prompts.


18-82

You can launch on-demand rules either from the Action Menu drop-down list using aCustom Menu, or from the Business Rules option.

After you run on-demand rules, all entities included in the calculation process have acalculation status of Impacted, regardless of the original status. The system will notrun on-demand rules for entities that are locked. All applicable parent and ancestormembers are Impacted, and all future periods that have data are also Impacted.

To launch an on-demand rule in a form:

1. On the Home page, click Data, and then open the form.

2. From the Action menu, select Business Rules, and select the rule.

3. From the Launch Confirmation message, click OK.

4. In the Run-Time Prompt dialog box, click Launch, then specify values or use thedefault values for the prompts, and click OK.

Launching On-Demand Rules from Smart View

When you open a form in Smart View, the same options are available to launch on-demand rules as in data forms. You can launch the rule using the Business Rulesoption or from a Custom Menu.

To launch a rule using the Business Rule option:

1. Open a data form and select the Calculate menu option.

2. Select Business Rules, or select Rules on Form to view only the rules definedfor the form.

3. Select a business rule to launch.

4. When the system displays the Run-Time Prompt, select members for thedimensions, then click OK. By default, the system uses the members from thePOV cell. You can change the default values during execution time.

To launch a rule from the Custom Menu:

1. Open a data form, then right-click in a cell and select Smart View.

2. Select the menu option from the Custom Menu attached to the form.

3. From the Launch Confirmation message, click OK.

4. Select the members for the dimensions in the Run-Time Prompt, and click OK.

Calculation Status for On-Demand RulesWhen you launch an on-demand rule and specify the entities for the calculation, thesystem will process all entities from the list, regardless of the current calculation statusof the entity.

After an on-demand rule is executed, the status for all entities in the rule changes toImpacted.

When entities are Impacted, the system follows these rules for applicable parentmembers and ancestors as well as future periods.

Locked Entities


18-83

If an entity is Locked, the system does not execute the rule on the locked entity. If therule Run-Time Prompt contains multiple entities and only some are Locked, thesystem skips those entities but continues to run the rule for the other valid entities.

Entities with View or None Access

If a user has View or None access to the entity, the system will not run the rule forthese entities and they will not be impacted.

Entities with Errors

If an entity in a rule does not pass validation, the system will not run the rule for theentity and it will not be impacted. Rules are run only for valid entities.

Reference of Source Entities

When a rule references a source entity for data, the system ignores the status of thesource entity and processes the data at the time of retrieval.

Renaming On-Demand RulesYou can rename a rule if it has not been deployed, since the rule resides only inCalculation Manager before deployment.

After a rule is deployed, a copy of the rule resides in Calculation Manager and thedeployed rule exists in your Financial Consolidation and Close application. If yourename a rule after it has been deployed, the deployed rule in the application retainsthe original name, but it will have a new name in Calculation Manager. Although youcan continue to execute the rule with the old name in your application, you cannot editthe rule in Calculation Manager since the rule with the original name no longer existsin Calculation Manager. You will not be able to remove the deployed rule from yourapplication.

If you need to rename a deployed rule, you must create a new rule in CalculationManager with the same name as the deployed rule in Financial Consolidation andClose with the old rule name. You can leave the rule content empty but you need todeploy the new rule to replace the previously deployed rule. You can then delete thisrule in Calculation Manager and select the option to also delete the deployed object.After it is deleted, the old rule will no longer exist in Calculation Manager or FinancialConsolidation and Close.

Another workaround to rename a deployed rule is to assign a different label to a ruleobject using an Artifact Label. In Calculation Manager, the rule will exist with theoriginal name, but when it is associated with the deployed rule object in FinancialConsolidation and Close, it is linked to a new name using the artifact label created forthe rule. Using this method you will see the new artifact label for the original rule ratherthan the old rule name.

Deleting On-Demand RulesYou can delete on-demand rules that you no longer need. When you delete a rule, youshould always select the option to include the deployed object as part of the deletion ifthe rule has been deployed.

If you do not select this option, the rule will be deleted from Calculation Manager, butstill deployed in your application and you will no longer be able to edit it. If you want toremove the deployed rule, you must create a new rule with the same name in


18-84

Calculation Manager. You deploy the new rule so that both Calculation Manager andyour Financial Consolidation and Close are synchronized. Then you can delete thenewly created rule from Calculation Manager.

If you delete a rule that is referenced in a Custom menu attached to a data form, whenyou edit the Custom menu, the rule name will be blank. If the Custom menu is used ina data form, when you open the data form, you will no longer see the menu optionbecause no rule has been associated with the menu.

To delete on-demand rules:




4. Select a rule, right-click and select Delete.

5. From the warning message, click OK to continue.

Note:

If the rule has been deployed, the system warns you that the some of theselected objects have been deployed. Select the option to include thedeployed object as part of the deletion.

6. From the confirmation message that the rule was deleted, click OK.

7. To confirm that the rule was deleted from the list, right-click on the Rules folder,and click Refresh.


18-85

19Managing Approval Unit Hierarchies

Related Topics

• Creating Approval Unit Hierarchies

• Editing Approval Unit Hierarchies

• Viewing Approval Unit Hierarchy Usage

• Synchronizing Approval Unit Hierarchies

• Deleting and Renaming Approval Unit Hierarchies

• Exporting Approval Unit Hierarchies

• Importing Approval Unit Hierarchies

Creating Approval Unit HierarchiesAdministrators can set up an approval process and organize data into approval unitsfor the purpose of review. See Managing the Approval Process.

The Approval Unit hierarchy contains the entities that are part of the review process.An approval unit consists of a combination of Scenario, Year, Period and Entity.

You must be a Service Administrator to create, modify or delete an Approval Unithierarchy.

Watch the following video to learn more about approval unit hierarchies:

Managing the Approval Unit Hierarchy

To create an approval unit hierarchy:


2. Under Workflow, click Approval Unit.

3. Click Create.

4. Set up the hierarchy with an approval name, approval options, and template.

See Setting Up the Approval Unit Hierarchy.

5. Select the members to include in the approval process.

See Selecting Approval Unit Hierarchy Members.

6. Assign owners and reviewers for each stage of the approval process and createthe approval unit promotional path.

See Assigning Approval Unit Owners and Reviewers.

7. Click Save.

19-1


Setting Up the Approval Unit HierarchyDefault Approval Unit Hierarchy Assignment

When an application is created, the system automatically creates an Approval UnitHierarchy named "Total Geography". This Approval Unit Hierarchy contains all entitiesunder the "Total Geography" hierarchy. The approval template assigned to thisApproval Unit Hierarchy is "Consolidation". This template is used for the purpose ofLocking and Unlocking.

The Total Geography Approval Unit Hierarchy is also assigned to the Actual scenariofor all years and periods of the application by default, and the periods are started bydefault.

Existing Applications

If you have already started locking your periods in your application, you can continueto use the "Total Geography" Approval Unit Hierarchy for any remaining periods thatyou want to proceed with for locking.

However, if you would like to start using the review process available for ProcessManagement, you can either:

• Modify the existing "Total Geography" Approval Unit Hierarchy to use a newapproval template named "Consolidation - Bottom Up"

• Create a new Approval Unit Hierarchy and assign the entities which you like to beincluded in the Approval Unit Hierarchy for the review process.

It is recommended to create a new Approval Unit Hierarchy using the new approvaltemplate - "Consolidation - Bottom Up" for the approval process. This will avoid anyconfusion with existing periods that have already been locked under the existing "TotalGeography" Approval Unit Hierarchy.

New Applications

If you are creating a new application or if you have not locked any of the periods, youcan modify the default "Total Geography" Approval Unit Hierarchy to use the newapproval template - "Consolidation Bottom Up". If any of the period have already beenstarted, you must Restart the review process so that the system uses the newapproval template for the workflow.

To set up an approval unit hierarchy:



3. Take an action:

• To create a new hierarchy, click Create.

• To edit an existing hierarchy, select a hierarchy and click Edit.

4. Select Approvals Dimension.

5. In Hierarchy Name, specify the approval unit hierarchy name.

6. Optional: Specify a description.

7. In Enable Approvals, select:

Chapter 19Creating Approval Unit Hierarchies

19-2

• All to add all entities to the approval process

• Custom to include the parent entity and the generation level of entitiesspecified as approval units. Based upon the selection, the required entities areadded to the hierarchy.

• None - this will not automatically include any entities as approval units. Youcan manually select the entities to be included in the hierarchy.

8. From Approvals Template, select a template.

9. For Cube, leave the default setting of "Consol".

10. Take an action:

• Click Next or select Primary and Subhierarchy Selection to select the approvalunit members (see Selecting Approval Unit Hierarchy Members.

• Click Save and then OK to save changes and close the approval unit hierarchy.

Selecting Approval Unit Hierarchy MembersTo select approval unit hierarchy members:

1. Take an action:

• From Approvals Dimension, click Next or select Primary and SubhierarchySelection to continue defining an approval unit hierarchy.

• Select Workflow, and then Approval Unit to edit an approval unit hierarchy.

Notes:

• At any time during approval unit hierarchy member selection, you can clickReset to Default Hierarchy to reset it to its default membership defined in theApprovals Dimension page.

• Shared members are displayed in the primary hierarchy, but are not displayedin the alternate hierarchy. For example, if entity E1 is under parent P1, whichis the "primary" hierarchy in the Entity dimension, and if E1 is also definedunder another parent P2 in an alternate hierarchy in the Entity dimension,when you try to select E1 to be part of the Approval Unit Hierarchy, the systemonly displays the E1 that is under P1. If you expand P2, E1 will not bedisplayed.

2. Define how to display the entities in the approval unit hierarchy:

• Right-click and select Expand to expand the display.

• Right-click and select Collapse to collapse the display.

• Select All Entities to display all available entities for selection.

• Select Approval Units to display only the approval units that you enabledpreviously.

• For Search, select Name, Alias, or Both. Enter any part or all of a name inSearch to locate an entity, then click Search Up or Down in the hierarchy.

• To move from page to page in a multipage approval unit hierarchy, enter apage number in Page and click Go, or click Start (first page), Prev (previouspage), Next, or End (last page).


19-3

3. Optional: For approval units not included in the default settings for the approvalprocess, check the box to the left of the approval unit name to include it in theapproval process.

4. Optional: Right-click an approval unit name to define subhierarchy members forthe approval process, and then select one Include/Exclude option:

• Include Children to include the children of the approval unit.

• Include Member to include only the approval unit, but none of itsdescendants.

• Include All Descendants to include all descendants of the approval unit.

• Include Generation to include one or more approval unit generations. Specifythe generations to include when prompted.

• Exclude Children to exclude the children of the approval unit.

• Exclude Member to exclude only the approval unit, but none of itsdescendants.

• Exclude All Descendants to exclude all descendants of the approval unit.

• Exclude Generation to exclude approval unit generations. Specify thegenerations to exclude when prompted.

5. Take an action:

• Click Next or select Assign Owners to specify approval unit ownership.

• Click Save and then OK to save changes and close the approval unithierarchy.

Assigning Approval Unit Owners and ReviewersApproval unit ownership is inherited from the approval unit parents. Approval unitreviewers are also inherited. You can specify different approval unit owners andreviewers other than those inherited by the approval units.

You must be a Service Administrator to assign approval unit Owners and Reviewers.

• For Owner, you must assign one user or group as the Owner of the approval unit.The Owner should be assigned to the top level entity of the approval unithierarchy.

• For Reviewer, you can assign one or more users or groups as Reviewers of theapproval unit.

If you select individual users as Reviewers, all users must perform the Approve action,and the approvals must follow the order in which the users are entered. If you select agroup (or groups) as a Reviewer, any user within the group can be the Reviewer andcan promote to the next level.

To assign approval unit owners and reviewers:

1. Take an action:

• From Primary and Subhierarchy Selection, click Next or select AssignOwners to continue defining an approval unit hierarchy.

• Select Workflow, and then Approval Unit to edit an approval unit hierarchy.


19-4

2. Select an approval unit, then under Owner, click the Select Owner icon to searchfor and select an owner.

An approval unit can have only one owner. Either a user or a group can be theowner. Select the Users tab to assign an individual user as the owner. Select theGroups tab to assign a group as the owner.

3. Under Reviewer, click Search and select approval unit reviewers.

Reviewers can be individual users, a single group, or multiple groups. Select theUsers tab to assign individual users as reviewers. Select the Groups tab to assigna single group or multiple groups as reviewers.

Note:

If the reviewers are individual users, select the reviewers in the orderthat you want them to review the approval unit. The first reviewer in thelist is the first user to work on the approval unit. When the first reviewerpromotes the approval unit, the second reviewer selected becomes theapproval unit owner, and so on through the list of reviewers that youcreate.

4. Under Promotional Path, click to display the approval unit promotional pathfor the entity, verify that it is correct, and then correct any errors.

For an entity to be approved and locked, the entity must have gone through thepromotional path and reached the last owner or reviewer in the path. Only the lastowner/reviewer on the promotional path can approve or lock the entity.

5. Optional: Under Notify These Users, click Search to select the users to notifywhenever an approval action is performed for the approval unit.

In order to receive notifications, the user to be notified must set up email ID andenable approval notifications in User Preferences. See "Setting Up Email forNotifications" in Working with Oracle Financial Consolidation and Close Cloud.

6. Optional: Repeat these steps for other approval units to assign owners andreviewers.

7. Click Save to save your work and continue, or click OK to save your work andclose the approval unit hierarchy.

Assigning Approval Unit Hierarchies to ScenariosAfter you have defined your Approval Unit, you can assign the Approval Unit Hierarchyto a specific Scenario, Year and Period combination. Only Scenarios that haveApprovals Enabled in metadata are available for selection.

Note:

You assign only one Approval Unit Hierarchy to a specific Scenario/Year/Period. You cannot assign multiple Approval Unit Hierarchies to the sameScenario/Year/Period.


19-5

Note that the system automatically creates the "Total Geography" Approval UnitHierarchy and assigns all possible years and periods for the Actual scenario when anapplication is created. If you are creating a new Approval Unit Hierarchy and want toassign a Scenario/Year/Period that is already assigned to "Total Geography", it isrecommended that you first remove the Scenario/Year/Period entries from "TotalGeography" and then add them to the new Approval Unit Hierarchy.

To assign approval unit hierarchy Scenario, Year, and Period combinations:


2. Under Workflow, click Approval Unit Assignment.

3. Add a Scenario, Year and Period assignment:

a. Click in the Actions column for the approval unit.

b. From the Scenario column drop-down, select the scenario to associate withthe approval unit hierarchy.

c. From the Years column drop-down, select the year to associate with theapproval unit hierarchy.

d. From the Period column drop-down, select the periods to associate with theapproval unit hierarchy.

You can select multiple periods at once, for example, Actual, FY19, January,February, March, and so on.

e. Click OK.

A new assignment row is displayed.

Tip:

To remove an assignment, click Delete .

4. Click Save to save the assignments and continue.

Editing Approval Unit HierarchiesYou must be a Service Administrator to edit an approval unit hierarchy.

To edit an approval hierarchy:



3. Select an approval unit hierarchy, and click Edit.

4. Select the appropriate tab for the changes that you want to make:

• Approvals Dimension

See Setting Up the Approval Unit Hierarchy.

• Primary and Subhierarchy Selection

See Selecting Approval Unit Hierarchy Members.

Chapter 19Editing Approval Unit Hierarchies

19-6

• Assign Owners

See Assigning Approval Unit Owners and Reviewers.

• Usage

See Viewing Approval Unit Hierarchy Usage.

5. Click Save when done.

Viewing Approval Unit Hierarchy UsageApproval unit hierarchies might have dependencies such as Scenario, Year andPeriod assignments or data validation rules which are defined in forms. Ifdependencies exist for an approval unit hierarchy, the hierarchy cannot be deleteduntil the dependencies are removed. The Usage tab enables you to view approval unithierarchies so that you can see and remove the dependencies if needed.

To view approval unit hierarchy usage:



3. Select an approval unit hierarchy, click Edit, and then select Usage to viewapproval unit hierarchy dependencies.

4. Select Forms to view associated data validation rules in forms, or select ApprovalUnit Assignment to view associated scenario assignments.

• If data validation rules are associated, they are listed by form. Click the link todisplay the form in edit mode in a new tab. You can then update or delete therule to disassociate it from the hierarchy.

• If a Scenario, Year and Period combination is associated, they are listed byscenario. Click the link to display the assignment in a new tab. You can thenremove the assignment to disassociate it from the hierarchy.

5. If you remove dependencies, click Refresh on the Usage tab to refresh the list.

6. If you are deleting an approval unit hierarchy, repeat these steps until alldependencies are removed.

Synchronizing Approval Unit HierarchiesWhen you add, delete, or modify dimension members that are used in approval unithierarchies, the affected approval unit hierarchy must be synchronized with thechanges. When you display the list of approval unit hierarchies, the entry for eachapproval unit hierarchy specifies whether recent changes are reflected in the approvalunit hierarchy. Use this procedure to synchronize dimension member changes with theapproval unit hierarchy.

Chapter 19Viewing Approval Unit Hierarchy Usage

19-7

Note:

When you add dimension members, they are added as approval units only ifthey meet the criteria in the inclusion rules for the approval unit hierarchy.For example, if the added entity is a fourth-generation entity, and theinclusion rules specify generations one through three as approval units, theentity is not added as an approval unit. If the entity is a third-generationmember, however, it is added as an approval unit the next time the approvalunit hierarchy is edited and saved, or synchronized.

To synchronize changes to approval unit hierarchies:

1. Click the Navigator icon , and then under Workflow, click Approval Unit.

2. In the Synchronized column, approval unit hierarchies are labeled as follows:

• Synchronized—Changes are synchronized with the approval unit hierarchy

• Not Synchronized—Changes are not synchronized with the approval unithierarchy

• Locked By user—A user is editing or synchronizing the approval unithierarchy

Note:

If a user begins editing or synchronizing an approval unit hierarchy afteryou display the approval unit hierarchy list, the approval unit hierarchylist does not display "Locked" for the approval unit hierarchy. If you try tosynchronize this approval unit hierarchy, the synchronization does notoccur, and an error message states that it is being edited.

3. Select an approval unit hierarchy listed as Not Synchronized, and then clickSynchronize.

Changes are applied to the approval unit hierarchy, and the list of approval units isupdated according to the inclusion rules defined for the approval unit hierarchy.

Note:

You cannot synchronize changes to an approval unit hierarchy thatanother user is editing or synchronizing.

Deleting and Renaming Approval Unit HierarchiesYou can delete an approval unit hierarchy if it is not referenced by data validation rulesor scenario assignments. The Usage tab displays objects that reference the hierarchyso that you can disassociate them from the hierarchy if needed.

You can also change the name of an approval unit hierarchy. Renaming an approvalunit hierarchy does not affect the objects that reference it.

Chapter 19Deleting and Renaming Approval Unit Hierarchies

19-8

To delete or rename approval unit hierarchies:



3. Take an action:

• To delete, select the approval unit hierarchy to delete, and then click Delete.

• To rename, select the approval unit hierarchy to rename, click Rename, andenter a new name.

4. Click OK.

Exporting Approval Unit HierarchiesWhen you export an approval unit hierarchy, you create a file that contains theapproval unit hierarchy information, including the definition and assignmentinformation. After you create this file, you can copy its contents to an existing approvalunit hierarchy (see Importing Approval Unit Hierarchies).

To export approval unit hierarchies:

1. Click the Navigator icon , and then under Workflow, click Import and Export.

2. Select Export Approval Unit Hierarchy.

3. In Existing Approval Unit Hierarchy Name, select an approval unit hierarchy toexport.

4. Click OK.

5. When the Save dialog box is displayed, save the export file to a location of yourchoice.

6. Click Export or Done. Export performs the action, and Done closes the dialogbox.

Importing Approval Unit HierarchiesAn approval unit hierarchy can be populated with the contents of an approval unithierarchy import file, including the definition and assignment information. The importfile is the result of exporting an existing approval unit hierarchy. See ExportingApproval Unit Hierarchies.

Importing the approval unit hierarchy information doesn't create an approval unithierarchy. The approval unit hierarchy populated from the export file must exist andhave at least a name before the import. The import process always uses Replacemode, which means it first deletes all members of the approval unit hierarchy, andthen adds each member specified as a new member in the load file.

Note:

An approval unit hierarchy load deletes an existing member and its childrenfrom the hierarchy if the member isn't specified in the input file.

Chapter 19Exporting Approval Unit Hierarchies

19-9

To import an approval unit hierarchy:

1. Click the Navigator icon , and then under Workflow, click Import and Export.

2. Select Import Approval Unit Hierarchy.

3. In Existing Approval Unit Hierarchy Name, select the approval unit hierarchyreceiving the exported information.

Note:

The imported approval unit hierarchy includes the defined owner,reviewers, and rules for determining the promotional path.

If your Approval Unit Hierarchy is already started and you import anApproval Unit Hierarchy which may contain changes to assigned entities,errors will result. Before you import an Approval Unit Hierarchy file,ensure that the Approval Unit Hierarchy is not started by performingExclude, which resets the hierarchy to Not Started status.

4. For Approval Unit Hierarchy with Ownership, click Browse to select theexported approval unit hierarchy file to import.

5. Click OK.

6. Click Import or Done. Import performs the action, and Done closes the dialogbox.

If the message Import successful is displayed, the approval unit hierarchyinformation in the exported file was successfully copied to the approval unithierarchy that you selected in Existing Approval Unit Hierarchy Name.

If the message Import not successful. Some items have not been imported isdisplayed, click Details to view the log file. Correct the errors and retry importingthe approval unit hierarchy.

Chapter 19Importing Approval Unit Hierarchies

19-10

20Managing the Approval Process

Related Topics

• Approval Process Overview

• Enabling Approvals

• Starting the Approval Process

• Approval Unit Promotional Path

• Creating Approval Unit Annotation Reports

• Creating Approval Status Reports

• Data Validation Rules

• Locking and Unlocking Entities

Approval Process OverviewAdministrators can set up an approval process to transfer ownership of data, providereview control, and ensure data privacy.

For the purpose of review, data is organized into approval units. An approval unit is thecombination of data for a specific Scenario, Year, Period, and Entity. For example:

• Actual/FY18/Jan/Massachusetts

• Budget/FY19/Feb/New York

The approval process generally follows these steps:

• The administrator sets up the approval unit hierarchy.

• The administrator assigns a Scenario, Year and Period combination to theapproval unit hierarchy.

• The administrator starts the approval process.

• Owners and Reviewers promote approval units according to the promotional path.

• The last reviewer in the approval hierarchy approves the approval unit. It changesto Approved status. After an approval unit is Approved, no more changes can bemade to it.

• The administrator can optionally lock entities before closing the period.

Enabling ApprovalsBefore you can use the Approvals process, you must enable approvals for theScenario dimension in the metadata file. When the Enabled for Approvals option isenabled, the Scenario is available for selection in the Approval Unit Assignmentscreen.

To enable approvals:

20-1

1. On the Home page, click Application, and then click Overview.

2. Click Dimensions, and then select the Scenario dimension.


4. Select Enabled for Approvals.

5. Click Save.

Starting the Approval ProcessAn administrator manages the approval process, including setting up approval unithierarchies, assigning the approval unit hierarchy to a specific Scenario, Year andPeriod, setting up validation rules, and starting the review process.

See Creating Approval Unit Hierarchies.

During the approval process, the administrator can monitor the status of each entitywithin the approval unit hierarchy and perform approval actions for these entities. TheProcess Status is only available to the administrator. Other users perform approvalactions from the Approvals card on the Home page. See "Reviewing and ApprovingData" in Working with Financial Consolidation and Close.

After you have defined an Approval Unit Hierarchy and assigned it to a specificScenario, Year and Period, the approval process can be started. Only an Administratorcan start the approval process. After the process is started, the approval unit movesfrom one reviewer to another until the process is complete.

By default, the approval status is "Not Started". The Start process changes theapproval unit status to "Under Review".

When you start the approval process, the system starts the process for the entitieswithin the Approval Unit Hierarchy. You can instead start each base entity separately,however, when you start a base entity, its parent and ancestors will also be started.

If you start a parent entity, all of its descendants will be started.

After the Start process, the current owner for each entity is set to the first owner in thepromotional path, as displayed in the "Current Owner" column. As the approval unit ispromoted within the promotional path, the Current Owner and Location are updatedaccordingly. The Administrator can monitor the status of each entity within theApproval Unit Hierarchy and perform approval action for these entities from theProcess Status screen.

An Administrator can restart the process at any time by selecting a specific entity toExclude. The system clears all approval history for the entity, and you can select Startagain to restart the review process, which moves the entity to the first owner of thepromotional path.

To start the approval process:


2. Under Workflow, click Manage Approvals.

3. From Scenario, Year, and Period, select a valid scenario, year, and period.

4. Click Go.

Chapter 20Starting the Approval Process

20-2

In the graphical pie chart, you will see "no data displayed" if the Approval UnitHierarchy has not yet started.

5. From the View drop-down on the top right, select Tree View.

6. Select an approval unit and click Start to begin the approval process.

7. From the confirmation message that the approval unit has been started, click OK.

The Approved Status changes to Under Review.

For a list of all Approval Unit levels and available actions, see "Reviewing andApproving Data" in Working with Financial Consolidation and Close.

8. Optional: If you want to re-start the approval process for a specific entity, you canselect Exclude to remove an approval unit from the process, and reset theapproval status to "Not Started".

Caution:

After you exclude an approval unit, all associated annotations andhistory are discarded. Data values are retained.

Approval Unit Promotional PathWhen you select an Owner and Reviewers for an approval unit and its parents, you setthe approval unit promotional path.

After the review process has started for the Scenario, Year and Period for the approvalunit, the approval status is "Under Review" for the entity, and a current Owner isassigned to the entity according to the promotional path defined for the approval unithierarchy.

At this stage, only the current Owner of the approval unit with Write access can enteror modify data for the entity.

However, anyone either in the promotional path or outside of it with Read or Writeaccess can view the data.

The current Owner of the approval unit changes as the entity is promoted within thepromotional path. After an entity has been promoted to the next level, you no longerhave Write access to the data, although you continue to have Read access to theentity's data.

Chapter 20Approval Unit Promotional Path

20-3

Creating Approval Unit Annotation ReportsAdministrators can check Approval Unit status by reporting on annotations for a set ofScenarios and Approval Unit members. Annotation text displays chronologically, withthe most recent entry first.

To create reports for Approval Unit annotations:


, and then under Monitor and Explore, click System Reports.

2. Select the Approval Unit tab, and then click Annotations.

3. From Select Report Options, select the Scenario, Years, Period, and Entitycombination for which you want to generate a report. If Custom is selected, clickthe

Member Selector icon to select the custom members.

4. From Approval Status, select the status to display in the report.

5. Click Create Report and select where to save the report.

Creating Approval Status ReportsYou can view detailed status of the approval process using approval status reports. Allusers can access this report, however you will see only the approval units to which youhave Write access.

Approvals status reports provide the following information:

• Approval Unit

• Parent

• Status

• Previous, Current, and Next Owner

Chapter 20Creating Approval Unit Annotation Reports

20-4

• Current Location

• Total Value

• Last Status Change Date

Sample Approval Status Report

To create Approval Status reports:


, and then under Monitor and Explore, click System Reports.

2. Select the Approval Unit tab, and then click Approval Status.

3. From Select Approval Status, select the status to display in the report, or selectAll.

4. From Filters, select dimension members for Scenario, Years, and Period.

5. Optional: Select an Approval Unit Hierarchy if you want to filter on a subset ofan Approval Unit hierarchy.

6. Optional: Select Current Location's Generation.

7. Select a Format for the report:

• XLSX

• PDF

• XML

• HTML

8. Click Create Report and select where to save the report.

Data Validation RulesTo implement business policies and practices, administrators can build data validationrules that are checked when conditions are met in forms. Rules can generate

Chapter 20Data Validation Rules

20-5

validation messages, enforce limits on submitted approval unit data, and designate aspecific reviewer or owner to review data that meets some condition.

For example:

• Conditionalizing the approval unit promotional path

• Preventing the promotion of approval units that include invalid data

You define validation rules within a data form, and can specify options for validatingapproval units. See Including Data Validation Rules in Forms.

In the approval process, validation is run only for these actions:

• Promote

• Approve

• Lock

• Unlock

• Exclude (Administrator action; checks to ensure that the current period is notlocked)

Validation is not run when these actions are performed:

• Sign Off

• Reject

• Reopen

• Originate

• Take Ownership

• Start (administrator action)

Locking and Unlocking EntitiesYou can view the lock status, and lock and unlock entities on the Approvals page. Youcan also view the lock status and calculation status on the Data Status form.

During the data load process, the system does not load locked entities. If an entity islocked, or approved, you cannot submit, post, unpost a journal, or modify a data formthat contains that entity.

Watch the following video for information on the locking and unlocking process:

Promoting, Approving and Locking Data

To lock or unlock an entity, it is not necessary to create an approval unit. FinancialConsolidation and Close provides an approval unit named "Total Geography".

To lock or unlock entities, you must be a Service Administrator. When an application iscreated, an owner is automatically defined for the "FCCS_Total Geography" approvalunit. The owner is the same as the Service Administrator. Do not modify this, and donot define a group as an owner.

It is not necessary to define any reviewer for "FCCS_Total Geography", and there isno need to define owners or reviewers for its descendants.

Chapter 20Locking and Unlocking Entities

20-6


If you create any hierarchy outside of "FCCS_Total Geography". you must define theService Administrator as the owner for that hierarchy.

Locking Entities

You can lock data only if these conditions are met:

• The entity’s calculation status must be OK, No Data, or System Change. Youcannot lock an entity with Impacted calculation status.

• The prior period data must be locked. For example, you can only lock an entity inthe February period if it is locked in January.

To lock entities:

1. On the Home page, click Approvals.

2. Select the Total Geography approval unit.

By default, the Total Geography approval unit has a status of Not Synchronized,and must be synchronized.

3. Click the Synchronize icon to synchronize the approval unit.

Note:

You must repeat this step each time after you add or remove an entityand perform a database refresh.

4. To start the approval unit, click the Navigator con, and then select ManageApprovals.

If you do not start an approval unit, the entities in that approval unit will remain in"Not Started" status.

5. Select the Scenario, Year and Period that you want to start and click Go.

6. From the View list on the right, select Tree View.

7. Expand "Total Geography" until you see FCCS_Total Geography.

FCCS_Total Geography is in "Not Started" state.

8. Click Start to start "FCCS_Total Geography ".

The system then moves it and all its descendants to "Unlocked" state.


10. Click an unlocked approval unit.

11. On the Change Status page, click Change Status to change the status to Locked.

12. Click Done.

If an error occurs during the locking or unlocking process, the Approvals page displaysa Failed status next to the approval unit. Click the link to view a detailed validationreport and resolve the error.

Unlocking Entities

You can only unlock data for a period if the next period is unlocked. For example, youcan only unlock an entity in February if the entity is unlocked in March.


20-7

You can select the Unlock or Unlock Single option:

• Unlock - If you select the Unlock action on a parent entity, the system unlocks theparent entity and all its children.

• Unlock Single- If you select the Unlock Single action on a parent entity, thesystem unlocks only the parent entity, but not its children.

When you unlock an entity and select the owner for the entity, it can be any owner inthe previous promotional path, including the current owner. If you select theAutomatic option for the owner, the new owner will be the current owner of the entity.

To unlock entities:

1. From the Approvals page, click a locked approval unit.

2. On the Change Status page, from the Actions drop-down, select an option:

• Unlock - unlock the parent entity and all its descendants

• Unlock Single - unlock the parent entity only.

3. Click Done.

If an error occurs during the locking or unlocking process, the Approvals page displaysa Failed status next to the approval unit. Click the link to view a detailed validationreport and resolve the error.

Locking New Entities

When you add a new entity to a hierarchy, you must perform the following steps.

In this example, suppose you add a new entity "E01" to the Total Geography approvalunit.

1. Add the new entity to the hierarchy and perform a Database Refresh.


3. Select the "Total Geography" approval unit and click the Refresh icon.

The status will change from "Not Synchronized" to "Synchronized".

4. Click the Navigator icon, and then select Manage Approvals.

5. Select the Scenario, Year and Period and click Go.

6. Click Start to start "FCCS_Total Geography."

The status of "E01" will change from "Not Started" to "Unlocked" in that specificYear and Period.

7. When you start "E01" in any Year and Period:

• Its parent's state will change from "Locked" to "Unlocked" if the parent was in"Locked" state before starting "E01" in that Year and Period.

• Its parent's state will change from "Not Started" to "Unlocked" if the parent wasin "Not Started" state before starting "E01" in that Year and Period.

• Its parent's state will remain "Unlocked" if the parent was in "Unlocked" statebefore starting "E01" in that Year and Period.

8. Now you can lock the newly added Entity.

9. To update previously locked periods:


20-8

Suppose your application calendar is from FY16 to FY24 and you have locked allentities from January FY16 through December FY17. Since the newly added entitycame into existence in January FY18, you must Start the new Entity in all previousyears and periods, and then Lock it in each previous year and period.

For example, you would start the newly added Entity in January FY16, thenFebruary FY16 through December FY16, and January FY17 through DecemberFY17. Then you would lock it in those years and periods.


20-9

21Setting Up Task Manager

Related Topics

• Task Manager Terms

• Task Manager Overview

• Sample Task Flows

• Managing Task Manager System Settings

• Managing Task Manager Attributes

• Managing Alert Types

Task Manager TermsTasksA unit of action in the application, for example, data entry or data consolidation. Powerusers define the tasks that comprise a business process. Users can read taskinstructions, answer questions, submit, reassign, approve, and reject tasks, and canaccess tasks from email notifications or by logging on to the application.

IntegrationsA definition of a service provided by an application.

Task TypesIdentify and categorize commonly performed tasks; for example, Data Entry, or G/LExtract. The Task Type enables you to set default information, such as settings thatneed to be input by the user, and questions or instructions that are shared by all tasksof that type. Task Types are often based on Integration Types.

Execution TypesEnd-users, System-Automated Task, Event Monitoring Task

TemplatesBusiness processes that are repeatable. Administrators can create templates fordifferent types of business processes, such as monthly or quarterly.

SchedulesDefines the chronologically ordered set of tasks that must be executed for a specificbusiness process, and is the alignment of a template's generic business processdays, to calendar dates.

DashboardThis view presents a portal-style interface with views into schedules and task lists,and high-level summaries into which you can drill down for greater detail.

21-1

AlertsNotifications from users on issues that they encounter during the process, such ashardware or software issues. Users create alerts identifying a problem and assignthem to be resolved.

Task Manager OverviewTask Manager helps you define, execute, and report on the interdependent activities ofa business process. It provides centralized monitoring of all tasks and provides avisible, automated, repeatable system of record for running a business process.

You can:

• Define the tasks and schedule to ensure the most efficient task flow

• Automate the business process, track status, and provide notifications and alerts

• Notify users by email for delinquencies, due dates, status changes

• Monitor business process status from a dashboard

• Act quickly to fix errors and delays

• Analyze the effectiveness of the business process

A business process requires these steps:

1. The administrator sets up users. See "Managing Users and Roles" in the GettingStarted with Oracle Enterprise Performance Management Cloud for Administratorsguide.

2. The administrator completes the required setup procedures:

• Set up organizational units. See Managing Task Manager OrganizationalUnits.

• Set up global integration tokens. See Managing Global Integration Tokens.

• Set up holiday rules. See Managing Holiday Rules for Tasks.

• Set up attachment size. See Setting the Task Attachment Size.

• Enable email notifications. See Specifying Application Settings.

3. The administrator reviews the tasks required for a business process and sets upTask Types to ensure consistency across tasks and to leverage predefinedproduct integrations.

See Managing Task Types.

4. Because many business processes are repeatable, the administrator saves a setof tasks as a template to use for future periods. See Managing Task Templates.

For example, an administrator can set up a monthly or quarterly business processonce and then use it for all months or quarters. Tasks are defined with taskpredecessors, Assignees, and Approvers.

5. To initiate a business process, administrators generate a schedule (achronological set of tasks) by selecting a template and assigning calendar dates.The generic tasks in the template are applied to calendar dates. See ManagingSchedules.

6. To begin a business process, the administrator changes the schedule status fromPending to Open.

Chapter 21Task Manager Overview

21-2

7. The administrator can also modify and monitor the schedule as needed.

8. During the business process, users receive email notifications of assigned tasksand can click links in the email for direct access to assigned tasks.

9. Alternatively, users can log on to review and access assigned tasks in differenttypes of views.

10. When users complete tasks, the tasks are sent to approvers and can be viewed byother users.

11. Users can create alerts for issues, such as hardware or software issues, that theyencounter. Alerts are forwarded to Assignees and Approvers for resolution.

Watch this overview video to learn more.

Overview Video

Sample Task FlowsScenario 1: Power User

The Power User sets up a template and tasks for an upcoming business process.

• The Power User logs on and opens the Manage Templates page.

• The Power User selects the template for the business process.

• The Power User selects the calendar dates on which to line up the template tasks,and creates a schedule.

• The Power User then adds a task to the template.

• The Power User opens the schedule, which begins the process.

Scenario 2: Power User

The Power User monitors the status of activities through the Dashboard.

• The Power User logs on and checks the status of activities through Day 3.

• The user drills down to see the details of incomplete tasks.

• The Power User reviews open tasks for comments or attachments provided byassigned users.

Scenario 3: Approver

A user assigned as an Approver reviews a current task to determine whether it can beapproved.

• The assigned Approver receives an email notification of an outstanding task.

• From the email, the Approver selects the link for the task.

• The Task Actions page is launched outlining the process.

• The Approver reviews the document that the user submitted when completing thetask to ensure completeness.

• The Approver enters additional comments and approves the submission.

Chapter 21Sample Task Flows

21-3


• If another level of approval is required, the task is forwarded to the next approver.If the task was the last requiring approval, then the task completes, and thesystem runs the next task if it is ready.

• The Approver can reject a task instead of approving it, and the task is reassignedto the Assignee.

Scenario 4: User

A user logs on to the application and reviews and completes an assigned task.

• The user logs on and reviews their tasks.

• The user clicks the link for an assigned task.

• The task page is launched with instructions for the task, and a referencedocument.

• The user reviews the instructions and the reference document, processes theupdates, enters a comment about the task, and submits it for approval.

• The system automatically updates the task status and sends a notification to theassigned approver.

Scenario 5: User

A user responds to an email notification of a task to load data, clicks a link in the email,and then completes the task.

• The user receives an email notification of an outstanding task.

• From the email, the user selects the link for the page where the required processis documented.

• The user reviews the instructions for the task and opens the task.

• The user loads data into the system.

• The user enters a comment about the task and submits it for approval.

Managing Task Manager System SettingsRelated Topics

• Managing Global Integration Tokens

• Managing Task Manager Organizational Units

• Managing Holiday Rules for Tasks

• Changing Configuration Settings

Managing Global Integration TokensThe Global Integration Tokens feature enables creation of parameterized URLs. TheURLs can be used for a variety of purposes.

When creating the URL, the parameters are inserted into the URL. When the URL isclicked, the parameters are replaced with the appropriate values.

Chapter 21Managing Task Manager System Settings

21-4

For example, the following is an excerpt of the parameters:

…$YearName$%22%22Period%20Name%22&val6=%22$PeriodName$%22&col17=%22Logical%20Schedules%22.%22Year%20Name%22&val7=%22$Y earName$%22&col8=%22Logical%20Schedules%22.%22Deployment%20Name%22&val8=%22$ ScheduleName $%22

where

$YearName$ = 2012$PeriodName$ = Jan12$ScheduleName$ = DemoSchedule

The URL becomes:

…%222012%22%22Period%20Name%22&val6=%22Jan2012%22&col7=%22Logical%20Schedules%22.%22Year%20Name%22&val7=%222012%22&col8=%22Logical%20Schedules%22.%22Schedule%20Name%22&val8=%22DemoSchedule%22

Parameters can be configured from static parameters defined in your application,attributes of type Text and List, and the following native attributes assigned to Tasks,Templates, and Schedules:

• Period Name

• Schedule Name

• Task Name

• Task ID

• Year Name

You can access URLs from the following locations:

• Templates: After an administrator or power user adds a reference URL to atemplate in the Instructions section, the URL is clickable on the Instruction tab.

• Schedule: After an administrator or power user adds a reference URL to aschedule in the Instructions section, the URL is clickable in Instructions.

• Task Details: After an administrator or power user or task owner adds a referenceURL to a task in the Instructions section, the URL is clickable in Instructions.

• Task Types: After an administrator adds a reference URL to a Task Type in theInstructions section, the URL is clickable on the Instruction tab.

• Task Actions: Viewers of Task Actions can click the reference URLs.

Creating a Global Integration TokenUse these guidelines for creating Global Integration Tokens:

• The token name must be unique.

• Tokens can't be modified.

• Tokens shouldn't be deleted. When you try to delete a token, a warning isdisplayed: "Deleting a Global Integration Token will invalidate the URLs that arereferencing it. Are you sure you want to continue?"


21-5

To create a Global Integration token:

1. On the Home page, click Application, and then click Task Manager.

2. Click the System Attributes tab on the left, and then select Global IntegrationTokens.

3. Click New.

4. Enter:

• Name: A unique token name

• Type: Static or Task Attribute

• Token Value:

– If Task Attribute is selected as the Parameter Type, select the value thatis passed when the URL is rendered.

– If Static Attribute is selected as the Parameter Type, enter the value thatis passed when the URL is rendered.

5. Click Save.

Deleting a TokenTo delete a token:


2. Click the System Attributes tab on the left, and then select Global IntegrationTokens.

3. Select a token, then click Actions, and click Delete.

A warning message is displayed: "Deleting a Global Integration Token willinvalidate the URLs that are referencing it. Are you sure you want to continue?"

4. Click Yes to delete.

Managing Task Manager Organizational UnitsOrganizational Units enable administrators to model regions, entities, business units,divisions, departments, or any other entity that might be affiliated with a task.Organizational units are hierarchical to facilitate reporting.

When viewing a hierarchy, administrators can expand and collapse it to work withdifferent sections of the hierarchy.

Adding Organizational UnitsTo add an organization:


2. Click the Organizations tab on the left and then select Organizational Units.

3. Click Add Sibling.

4. On the Properties tab, enter:

• Name


21-6

Administrators can change the name, and it need not be unique.

• Organizational Unit ID

A unique ID used to identify the transaction for Migration purposes.Organizational Unit ID can't be changed after an organizational unit is set.

• Optional: Parent Organization

Enables Administrators to change the hierarchy.

• Description

• Time Zone

Determines which time zone applies to the organizational unit. Selection of atime zone is optional. If a time zone is not selected, the task time zone willrevert to the user’s time zone.

• Holiday Rule

Determines which list of holidays applies to the organizational unit. Selectionof a Holiday Rule is optional.

• Work Days

Determines which days of the week are work days.

5. The Access tab enables Administrators to assign viewer and commentator accessin a centralized location, rather than having to assign it to each task.

To select a user:

a. Select Actions, and then Add.

b. In Select Viewers, enter the First Name and Last Name, or click SearchUsers, then select Users or Teams.

c. In Search Results, select the users and click Add or Add All to move them tothe Selected list.

Importing Organizational UnitsTo import organizational units:

1. On the Home page, click Application and then click Task Manager.

2. Click the Organizations tab on the left and select Organizational Units.

3. Click Import .

• Click Browse to navigate to the CSV import file.

Sample Organizational import format:

Note:

The following section shows the import format. This examplerequires a pre-existing parent organizational unit named `Americas',a holiday rule named `US', and a viewer named "fm_user5".


21-7

"OrganizationalUnitID","Name","ParentOrganization","Description","TimeZone","HolidayRule","Calendar","Workdays","Viewer1","Commentator1""US2","US2","Americas","Import Organization US2 Example","ET(UTC-05:00)","US","",2-3-5,"fm_user5",""

• For Import Type, click one:

– Replace— Replaces the Organizational Unit detail with the OrganizationalUnit that is in the file that you are importing. It does not affect other unitsthat are not specified in the import file.

– Replace All— Imports a new set of Organizational Units that replaces theexisting Units. This option is useful when you want to replace a unit in onesystem with an updated definition from another system. OrganizationalUnits that are not specified in the import file are deleted.

4. Click Import.

Selecting an Organizational UnitAdministrators define organizational units in Organizations to help organize andschedule tasks.

To select an organization:


2. Click the Organizations tab on the left, and then select Organizational Units.

3. Select an organization. An arrow indicates a child organization exists. Expand theparent to select a child organization.

Managing Holiday Rules for TasksHoliday Rules are collections of holiday dates that Administrators use when schedulingtasks.

After you create a holiday rule, you can apply the rule to an organizational unit andthen apply the organizational unit to the schedule template.

See Applying a Holiday Rule to an Organizational Unit and Applying a Holiday Rule toa Schedule Template.

Creating Holiday RulesTo create holiday rules:


2. Click the Organizations tab on the left.

3. Click Holiday Rules.

4. Click New.

5. Enter:

• Holiday Rule ID

Holiday Rule ID is mandatory and must be unique.


21-8

• Name

The name of the holiday rule is mandatory and can be up to 50 characters.Uniqueness is not required.

• Year

The Year attribute behaves as a filter option. Users need not select a value forthis attribute. If they do, then the table should be filtered to display the datesassociated with the selected year.

6. To name a holiday, in the Holiday section, click Import ( ) to import the list ofholidays or click Add and enter the date and name of the holiday.

Applying a Holiday Rule to an Organizational UnitAfter you create a holiday rule, you can apply it to an organizational unit, and thenapply it to a schedule.

To apply a holiday rule:



3. Click Organizational Units.

4. Create or edit an organization.

5. On Properties, from the Holiday Rule drop-down, select your holiday rule.

6. Click Save and Close to save your changes.

Applying a Holiday Rule to a Schedule TemplateAfter you create a holiday rule and apply it to an organizational unit, you can apply theorganizational unit to a schedule template.

To apply a holiday rule:

1. On the Home page, click the Application icon .

2. Click Task Manager .

3. Click the Templates tab on the left.

4. Select a template and select Actions, and then Create Schedule.

5. For Schedule Parameters, specify the Schedule, Year, Period, and Day ZeroDate.

6. Under Date Mapping, click Advanced Configuration.

7. Select Set Value To next to Organizational Unit, and click the Search icon.


21-9

8. Select the organizational unit that you created or edited that contains the holidayrule and click OK.

9. Click OK.

The Schedule Parameters Date Mapping now shows the holiday.

Importing Holiday DatesYou can import dates into a holiday rule.

To import holiday dates:




4. Create or select a holiday rule.

5. From the Holiday Rules section, click Import .

• Click Browse to navigate to the CSV import file.

• For Import Type, click one:

– Replace—Replaces the holiday dates with the holiday dates in the file thatyou are importing. Does not affect other units that are not specified in theimport file.

– Replace All—Imports a new set of holiday dates that replaces the existingholiday dates. Use this option to replace unit in one system with anupdated definition from another system. Holiday dates that are notspecified in the import file are deleted.

6. Date Format

Select a Date Format from the drop-down list of allowed date formats. Dateformats are not translated. By default, the date format is set to the locale dateformat of the exported file location.

7. From the File Delimiter drop-down, select Comma or Tab.

8. Click Import.

Editing Holiday RulesTo edit holiday rules:


2. Click the Organizations tab on the left and then select Holiday Rules.

3. Select a rule.

4. Edit:

• Holiday Rule ID

Holiday Rule ID is mandatory and must be unique.

• Name

Can be up to 50 characters. Uniqueness is not required.


21-10

• Year

The Year attribute behaves as a filter option. Users need not select a value forthis attribute. If they do, then the table should be filtered to display the datesassociated with the selected year.

• Click Save

Duplicating Holiday RulesTo duplicate holiday rules:




4. Select a rule and click Duplicate.

5. Edit the rule as needed.

Deleting Holiday RulesYou cannot delete a holiday rule associated with an organizational unit that is notlogically deleted. A list of organizational units to which the holiday rule was assigned isdisplayed.

To delete holiday rules:


2. Click the Organizations tab and then select Holiday Rules.

3. Select a rule, select Actions, and then Delete.

Changing Configuration SettingsRelated Topics

• Allowing Comment Deletions

• Allowing Task Deletions

• Displaying Upcoming Tasks

• Approver Levels

• Enabling Email Notifications in Task Manager

• Reopening Tasks

• Specifying Task Display in Smart View

• Setting the Task Attachment Size

• Allowing Reassignment Request Approvals

Allowing Comment DeletionsA Service Administrator can decide to allow deletions of comments in tasks by usingthe Allow Comment Deletion configuration settings option. By default, this option isOff.


21-11

To allow users to delete comments:


2. Click the System Settings tab on the left.

3. Select Allow Comment Deletion.

4. Select Turn On to enable deletions, and then click Save.

Allowing Task DeletionsService Administrators can specify whether to allow tasks to be deleted. By default,this option is Off.

Note:

The setting affects only running and closed tasks.

To allow users to delete tasks:



3. Select Allow Task Deletion.

4. Select Turn On to enable deletions.

Displaying Upcoming TasksAs an administrator, you can decide whether to show only Current Tasks, or Currentand Upcoming Tasks on the Work List and Welcome Panel.

If you enable Current and Upcoming Tasks, users can see items currently available towork on, and also items in the upcoming workflow. For example, users can see anupcoming task that is due for them to approve, but not immediately available, as thepreparer has not yet finished the task.

By default, the system displays only Current Tasks.

To set the display for tasks:



3. Select Allow Upcoming Tasks.

4. Select an option for the Work List and Welcome Panel:

• Show Current Tasks Only

• Show Current and Upcoming Tasks

Approver LevelsApprover levels determine the number of levels that a task might be reviewed.


21-12

To change the approver level:

1. On the Home page, click Application, then click Task Manager.


3. Select Approver Levels.

4. In Approver Levels, select a value from 1 to 10.

Enabling Email Notifications in Task ManagerService Administrators can set up Email Notifications for Task Manager users. Whenyou enable email notifications, batch notifications are generated. When the notificationis no longer required, you can deactivate email notifications and reminders.

Note:

By default, email notifications are not enabled.

Administrators can also assign the number of days before a due date to send remindernotifications.

Due Date reminder notifications are emailed to Assignees and Approvers in theseconditions:

• Responsibility for a Task Manager action changes - sent based on information inthe action

• A due date is missed - sent based on information in the action

• A due date is approaching - sent based on the number of days in advance that youspecify

To enable email notifications:



3. Select Email Notifications.

4. For Email Notifications, select Turn On to initiate the notification, or Turn Off todeactivate the notification.

5. Enter an email for the From Address. You can edit the address to supply aspecific address, or to include a product acronym to alert the user where thenotification is coming from.

Email notifications also include the service name in the footer of the email. Forexample: “Note: This is an automated email notification generated from EPM TaskManager on efim.arcs”.

6. Enter the Number of days before due date to send reminder.

Reopening TasksIn Task Manager, there might be times when users need to reopen a task.Administrators can specify whether to allow open or closed tasks to be reopened.


21-13

To allow reopening of tasks:



3. Select Reopen.

4. Set the conditions to allow reopening of a task that is Open with an Assignee orApprover:

• Not Allowed - this is the default option and assignees or approvers cannotchange the workflow of an open task after it has been submitted or approved.

• Allowed for all approvers - allows approvers who have approved a task toreturn the workflow to themselves.

• Allowed for all assignees and approvers -- allows an assignee who hassubmitted a task or an approver who has approved a task to return theworkflow to themselves.

5. Set the conditions to allow reopening closed tasks:

• Not Allowed - this is the default option and users will not be able to reopen aclosed task.

• Allowed for final approver- allows only the final approver to reopen andreturn the workflow to themselves.

• Allowed for all approvers- allows an approver to reopen and return theworkflow to themselves.

• Allowed for all assignees and approvers - allows assignees and approversof a task to reopen and return the workflow to themselves.

Specifying Task Display in Smart ViewYou can configure the display of Task Manager tasks when they are launched fromOracle Smart View for Office by selecting columns to display, for example, TaskAttributes.

To select columns to display in Smart View:


2. Click the System Settings tab.

3. Select Smart View.

4. Under Columns, from the Available list, select the columns to display, then clickthe Add arrow keys to move them to the Selected column, or Remove to removethem.

You can select a maximum of 30 columns, and reorder the columns as needed.

5. Click Save to save your selection.

Setting the Task Attachment SizeTask Attachment Size determines the maximum attachment file that users can upload.This setting helps administrators adapt to work within limitations of the environment inwhich the application is installed.

To change the maximum task attachment size:


21-14



3. Select Task Attachment Size.

4. In Select maximum file upload size, select a value from 5 MB, with incrementalvalues of 5 MB, up to 100 MB.

Allowing Reassignment Request ApprovalsAs an Administrator, you can specify which workflow users can directly perform andapprove reassignment requests rather than submitting requests to an Administrator orPower User for approval.

Users can then approve reassignment requests from their Worklist.

To set up workflow users, see Selecting the Workflow.

Service Administrators should also see the reassignment requests if they are requiredto approve the requests in case the Task Owner is unavailable.

To allow workflow users to perform reassignments:



3. Select Reassignment Requests.

4. For Allow reassignment request approval by, select one or more options:

• Administrator

• Power User

• Users

Managing Task Manager AttributesAttributes are user-defined fields defined centrally by administrators and used in manyplaces.

You can specify different value types for attributes: Date, Date/Time, Integer, List,Multi-Line Text, Number, True/False, Text, User, and Yes/No. For example, you candefine a custom attribute named Auto Submit with a value type of Yes or No. Whenyou assign the Auto Submit attribute to an item, you can set it to Yes for tasks requiredby external users.

If you select the List type, you can define a pick list of values. For example, you candefine a List attribute named Sales Region, with North, South, East, and West asvalues.

You can create, edit, and delete attributes.

Note:

The maximum number of Task Manager attributes that you can create orimport is 10,000.

Chapter 21Managing Task Manager Attributes

21-15

Defining Task Manager AttributesTo define a Task Manager attribute:


2. Click the Attributes tab on the left.

3. Click New and enter:

• Name

• Type:

– Date

– Date/Time

– Integer

– List

If you select List, enter a list of valid responses to the question.

– Multi-Line Text

If you select Multi-Line Text, enter the Number of Lines, from 3 to 50lines. Multi-Line Text determines how many lines of text are visible,without scrolling, on the Actions dialog boxes. The maximum lengthshould be less than 4,000 characters.

Select Include Attachments if you want to include an Attachmentssection on the Actions dialog box.

– Number

If you select Number, select number formatting options:

* For Decimal Places, enter a value for the number of decimal placesto display.

* For Display As Percentage, check the box if you want a percentageto display.

* Select the Thousands Separator option if you want numbers todisplay a thousands separator (for example, 1,000.00)

* From the Currency Symbol list, select a currency symbol, forexample, Dollars ($).

* From the Negative Number list, select how to display negativenumbers, for example, (123).

* From the Scale list, select a scale value for numbers, for example,1000.

– Text

– True/False

– User

– Yes/No

– Calculation - Select to add logical and mathematical functions forattributes.


21-16

See Defining Calculation Attributes.

Defining Calculation AttributesCalculation attributes enable you to add logical and mathematical functions to derivevalues for attributes. They can be embedded within other calculated attributes toproduce complex functions. Calculated attributes are read-only. They can only beevaluated against Schedules.

Schedules: You can add any Calculation and the calculation is evaluated, regardlessof whether or not it was explicitly assigned to the task.

Templates: You cannot add a custom attribute that has the Calculation option selectedas a column or a filterable attribute.

When administrators add attributes to the Attributes sections in the Actions dialogs,they are viewable by workflow users. Administrators can restrict access to certain rolesby setting the access to Do Not Display. For example, for calculated attribute XYZ, anadministrator could set the access to Viewer: Do Not Display so that the XYZattribute is not displayed for users with only the Viewer role.

Any user role can add calculated attributes as columns in views and portlets. They canalso be added as filterable attributes in the Filter Panel.

When you create an attribute and select the Calculation option, a Calculationdefinition section is displayed.

Calculation Type

You can select from the following calculation types. The available types aredetermined by the Attribute Type (Text, Integer, and so on).

• Assign Value to List—Assign custom values to a List type attribute

• Assign List To Value—Assign custom list values to the values of a differentattribute. Only available for List type attributes.

• Conditional—A conditional calculation (If – Then – Else)

• Scripted—A free-form scripted calculation. Only available for attributes of typeInteger, Multi-line Text, Number, or Text.

The following table lists the Calculation types available for each Attribute type.

Attribute Type Assign Value to List Conditional Scripted Assign List to Value

Date

Date/Time

Integer X X X

List X X

Multi-Line Text X X X

Number X X X

Text X X X

True/False X

User

Yes/No X

Calculation Definition


21-17

The Scripted Calculation type enables you to enter a free-form calculation equation.You can use the Add Attribute and Add Function.

• Add Attribute—Select an attribute and insert the attribute into the CalculationDefinition box at the location of the cursor. If the cursor is in the middle of a wordor attribute, the word/attribute will be replaced in the definition. The script formatadds brackets {} around the name of the new attribute.

The only available attributes are Schedule attributes.

• Add Function—Select a function and add the function to the CalculationDefinition. The Function is added with placeholders for each parameter.

For example: Insert the DATE_DIFF function in the calculation definition:

DATE_DIFF(<Date1>, <Date2>, <Type>)

Then replace the placeholders with attributes:

DATE_DIFF( {Start Date}, {End Date}, 'DAYS')

Numeric and Date Functions

• Absolute Value: Returns the absolute value of a specified number. If a number isless than zero, the positive value of the number is returned. If the specifiednumber is equal to or greater than zero, the specified number is returned.

ABS(<Number>)

• Add Month: Returns a date offset a specified number of months from the startingdate. The date will always fall in the specified month offset. If the starting date hasa day value beyond what is in the offset month, the last day of the offset month willbe used. For example, EDate (31-Jan-2017, 1) returns (28-Feb-2017). ForMonths, enter the number of months before or after the start date. A positive valuefor months yields a future date. A negative value yields a past date.

ADD_MONTH(<Start Date>, <Months>, <Length>)

Example: ADD_MONTH(DATE(2017, 2, 15) 3)

• Date: Returns a date value based on specified integer values for the year, monthand day.

DATE(<Year>, <Month>, <Day>)

• Date Difference: Returns the difference in years, months, days, hours, minutes, orseconds between two dates. For DATE 1 and DATE 2, the values TODAY andNOW can be used, which denote the current date (with no time component) anddate-time, respectively.


Example: DATE_DIFF( {Start Date}, 'TODAY', 'DAYS')

• Day: Returns the day value of a date as an integer number

DAY(<DATE>)

• Extract Text: Returns the substring within the value, from the specified positions.

SUBSTRING(<Value>, <Location>, <Length>)

Example: SUBSTRING( {Name}, 4, 10)


21-18

• If Then Else: Allows you to insert a conditional calculation into the scriptedcalculation. IF_THEN_ELSE calculations can also be nested to support “ELSE IF”type calculations.

IF_THEN_ELSE(<Condition>, <Value1>, <Value2>)

Example: IF_THEN_ELSE( ( {Priority} = 'Low'), 1,IF_THEN_ELSE( ( {Priority} ='Medium'), 2, IF_THEN_ELSE( ( {Priority} = 'High'), 3, 0)))

Example: IF_THEN_ELSE( ( {Priority} = 'Low'), 'Good' IF_THEN_ELSE( ( {Priority}= 'Medium'), 'Better'. 'Best') )

• Instring: Returns the index of the substring within the value.

INSTRING(<Value1>, <Value to Search>)

Example: INSTRING({Name}, 'a')

• Lowercase: Returns the value in lower case

LOWERCASE(<Value>)

Example: LOWERCASE ({Task Code})

• Maximum: Returns the maximum value from a list of attributes. There can be anynumber of parameters.

MAX <Value1>, <Value2>, <ValueN>)

Example: MAX( {Scripted Substring Loc a}, {Scripted Substring Loc s}, {ScriptedSubstring Loc t} )

• Minimum: Returns the minimum value from a list of attributes. There can be anynumber of parameters.

MIN (<Value1>, <Value2>, <ValueN>)

Example: MIN( {Scripted Substring Loc a}, {Scripted Substring Loc s}, {ScriptedSubstring Loc t} )

• Month: Returns the month value of a date as an integer number (1-12)

MONTH (<DATE>)

• Power: Raises one number to the exponential power of another.

POWER(x,y) where x=BASE NUMBER,and y=EXPONENT and x and y can be attributesor calculations, as long as they are numeric.

Example: POWER(3,4)=81

Note:

Fractional values will reduce the number to its root. For example,POWER(27, 1/3) = 3 the cube root.

Negative values will perform an inverse of the exponential calculation.For example, POWER(2, -2) = 1 / (2^2) = 1 / 4 = .25.

• Round: Returns the value rounded to the decimal places specified

ROUND <Attribute>, <Decimal Places>)

Example: ROUND( ({Scripted Substring Loc t} / 7), '4')


21-19

• Text Location: Returns the index of the substring within the value, starting at 1 asthe first position.

INSTRING(<Value>, <Value To Search>)

Example: INSTRING( UPPERCASE( {Name} ), 'TAX' )

• Uppercase: Returns the value in upper case.

UPPERCASE(<Value>)

Example: UPPERCASE( {Name} )

• Year: Returns the year value of a date as an integer number.

YEAR (<DATE>)

Calculation Validation

The following validation checks are performed when you save the Calculation:

• The syntax of the Calculation is correct.

• The Attributes and Functions specified in the Calculation exist.

• Parameters to Functions are correct.

• No Circular Loops exist.

Importing List AttributesTo import Task Manager attributes of the List type:

1. Create an import file of List attributes in a TXT file format, with each value on aseparate line.

For example:

BlueYellowRedGreen

The import option is always "Replace All".



4. Select an attribute of type List, and click Edit.

5. Click Import .

6. Browse to a TXT import file.

7. Click Import. Import List Values displays the values: Total List Values,Completed, Errored, List Values Created, and List Values Updated.

If Completed Successfully, click OK.

If Completed with Errors, the errors are listed. To export the error list, clickExport to Excel .


21-20

Editing AttributesYou can edit the name of a custom Task Manager attribute. If the attribute type is aList, you can also add, rename, or delete list values.

To edit Task Manager attributes:



3. Select an attribute and click Edit.

4. Edit the attribute name.

Note:

If the attribute is a List type, you can add, rename, or delete list values.After a custom attribute is saved, you can't change its type.

5. Click OK.

All related templates, schedules, task types, or tasks are updated.

Duplicating AttributesYou can duplicate attributes.

To duplicate attributes:



3. Select an attribute to duplicate, and click Duplicate.

4. Click Close.

Deleting AttributesYou can delete attributes that you no longer need. When you delete an attribute, thesystem removes all references to the attribute.

To delete attributes:



3. Select the attributes to delete, and click Delete.

4. At the confirmation prompt, click Yes.


21-21

Viewing AttributesIn Attributes, you can specify which columns to display for the list of attributes, or showall. You can also reorder columns, sort columns by ascending or descending order,and change the column widths.

To display columns:



3. Do one or more of the following tasks:

• To display all columns, select View, then Columns, and then select Show All.

• To display specific columns, select View, then Columns, and select ordeselect the column names.

• To reorder columns, select View, and then Reorder Columns, select columnsand use the Up or Down arrows or drag them to change the order.

• To sort columns, hover over a column header until the Sort icons aredisplayed, and then click Sort Ascending or Sort Descending.

• To change column widths, hover over the column header dividers until thearrows display, and drag the columns to the desired width.

Searching for AttributesYou can use the Attributes dialog box to find attributes for Task Manager tasks. Youcan enter full or partial names on which to search.

To search for Task Manager attributes:



3. Enter full or partial search criteria for the attribute.

4. Click Search.

Managing Alert Types

Note:

The Alert Types feature is only available to administrators.

When performing a business process, users might encounter roadblocks such as ahardware failure, software issues, system failure, and so on. They can create an alertidentifying the problem, and attach it to the task.

For example, a user is running a business process and can’t log on to the system. Theuser creates the alert indicating “Software Issue” as the type and assigns it to the

Chapter 21Managing Alert Types

21-22

Service Administrator. The Administrator resolves the login issue, then closes the alertor submits it for approval.

You can maintain a list of alert types to categorize alerts.

Creating Alert TypesYou can create alert types to group alerts into categories, such as hardware failure,software issues, system failures, and so on.

Using alert types, you can analyze the types of issues that users encounter during thebusiness cycle and make changes to prevent them in future cycles.

To create an alert type:


2. Click the System Attributes tab on the left.

3. Select Alert Types.

4. Click New.

5. For Name, enter an alert type name.

6. For Description, enter an alert type description.

7. Click Enabled to enable the alert type.

8. Click OK to save the alert type.

Editing Alert TypesYou can edit the names and descriptions of alert types, and specify whether they areEnabled.

To edit an alert type:



3. Select the alert type, and click Edit.

4. Edit the alert type.

5. Click OK.

Viewing Alert TypesIn Alert Types, you can specify which columns to display for the list of alert types, orshow all. You can also reorder columns, sort columns by ascending or descendingorder, or change the column widths.

To display columns:



3. Select Alert Types.



21-23






Searching for Alert TypesYou can use Alert Types to find Task Manager alert types. You can enter full or partialnames on which to search.

To search for alert types:


2. Click the System Attributes tab on the left, and then select Alert Types.

3. Enter a partial or full name on which to search.

4. Optional: For additional search operators (such as Contains, Starts with, Endswith), click Advanced, and enter search criteria.

Click Add Fields to select additional fields for search criteria.

5. Click Search.

To reset the list to display all alert types, click Reset.

Deleting Alert TypesYou can delete alert types. When an alert type is deleted, the alert is not deleted;rather it loses its alert type assignment.

To delete an alert type:



3. Select Alert Types, and select the alert type.

4. Click Delete.


21-24

22Managing Teams for Task Manager

Teams are defined and provisioned with Owners, Assignees, Approvers, and Viewersroles. Then, rather than assigning named users these roles on a task, the role isassigned to the Team. Administrators and Power Users can add, edit, and deleteteams.

See these topics:

Adding Teams and Members for Task Manager

Editing Teams and Members for Task Manager

Deleting Teams and Removing Members

Managing Backup Assignments

Requesting a Reassignment in Task Manager

Adding Teams and Members for Task ManagerTo add teams and members:

1. On the Home page, click the Tools icon .

2. Click Access Control .

3. Click the Teams tab.

4. Click New.

5. On the Define Team screen, for each team, enter:

• Name

• Description

• Select the Task Manager tab and then select one or more roles for the team:

– Administrator

– Power User

– User

– Viewer

• To add members:

a. Under Members, click Add.

22-1

b. Enter the partial or full First Name, Last Name, or click Search to selectthe names.

c. In the Search Results section, click Add, or Add All to add the selectionsto the Selected list.

d. Click OK.

6. On the Team dialog box, select Primary User to have the tasks default to aClaimed status with that user.

Note:

Other team members can then claim the task.

7. Click OK.

Editing Teams and Members for Task ManagerTo edit teams or members:

1. On the Home page, click Tools, and then click Access Control.


3. Select a team, and click Edit .

4. Edit the teams and members and click OK.

5. Click OK.

Deleting Teams and Removing MembersThe following guidelines apply to deleting teams that are used in templates orschedules:

• If a team has been assigned to a task in a template, then it cannot be deleted. Todelete the team, first remove it from all tasks to which it is assigned.

• If teams are used in schedule tasks, then the deletion is allowed. The scheduletask can still see the team even though no new tasks can use the team.

To delete teams or members:



3. To delete teams, select a team, click Delete, and from the confirmation prompt,click Yes.

4. To remove members, double-click a team name, and on the Edit Team dialogbox, select a member and then click Remove.

5. Click OK.

6. On Manage Teams, click Close.

Chapter 22Editing Teams and Members for Task Manager

22-2

Managing Backup AssignmentsYou can assign backups for the Assignee and Approver roles only when the primaryuser is a named user, not a team or group.

• Assignee: For basic tasks (not automated tasks)

• Approver: For both basic and automated tasks

Note:

Administrators cannot back up owner assignments on templates, schedules,and tasks.

To assign a backup for a task:

1. Open the task for which you want to assign a backup.

2. Select the Workflow tab and select both an Assignee and Backup user.


Requesting a Reassignment in Task ManagerReassignment requests can only be initiated by users explicitly assigned the primaryworkflow role (as a named user). They cannot be submitted for backup roles, or bymembers of Teams/Groups assigned primary roles.

Assignees and Approvers can dispute an Assignee or Approver assignment on one ormore tasks by submitting a request to reassign the tasks.

From the Task Actions dialog box, workflow users (Assignees and Approvers) canrequest reassignment of their workflow role for selected or selected and future tasks.These requests require approval. Administrators and schedule/template Owners canstill reassign the task using the Edit Task dialog box without requiring approval.

To request reassignment for a task:

1. On the Home page, click Tasks.

2. Select the Schedule Tasks tab on the left.

3. From Actions, select Request Reassignment.

4. If you know the reassigned user, enable To User, and then enter orsearch for the name.

Note:

If you do not know the new user, then submit a request withoutspecifying the name of the user.

Chapter 22Managing Backup Assignments

22-3

5. Reassign the task by completing these options:

• Selected Tasks to reassign just the schedule task

• Selected and Future Tasks to reassign tasks for the schedule task and thecorresponding task in the source template

6. Enter a Justification for the reassignment.

7. Click OK.

Chapter 22Requesting a Reassignment in Task Manager

22-4

23Managing Task Types

Related Topics

• Task Types

• Creating Task Types

• Setting Task Type Properties

• Setting Task Type Parameters

• Specifying Task Type Instructions

• Specifying Task Type Questions

• Assigning Task Type Attributes

• Working With Task Type Rules

• Viewing Task Type History

• Editing Task Types

• Viewing Task Types

• Searching for Task Types

• Importing Task Types

• Exporting Task Types

• Deleting Task Types

Task TypesTask Types are saved definitions of commonly performed tasks. They identify andcategorize tasks commonly performed during a business process, for example, DataEntry or General Ledger Extract. Task Types enable you to set default information,such as settings that must be input by the user, and questions or instructions that areshared by all tasks of that type. For example, if you have a set of required questions tobe answered by users responsible for data loads, you can create a Data Load TaskType with the required questions. When you create data load tasks, you can select theData Load Task Type and the questions are automatically included in the tasks.

Two predefined Task Types are installed by default:

• Basic Task: Basic Task Type that does not contain instructions, questions, orattributes.

• Parent Task: Enables you to create parent tasks to define task hierarchies.

To create and manage Task Types, you must be assigned the Service Administratoror Power User security role. Power Users can create their own Task Types, but canonly view those of others.

23-1

Creating Task TypesTask Types enable you to set default information for a task, such as settings that needto be input by the user, or questions or instructions that are shared by all tasks of thattype.

To create a Task Type:


2. Click the Task Types tab on the left.

3. Click New.

4. See also:







Setting Task Type PropertiesThe Properties tab enables you to set the name, ID, and description, and associate anIntegration Type.

For End User Types, you can allow an Assignee to open a pending task prior to thescheduled time, if all task predecessor conditions have been met.

To set Task Type properties:

1. Create a new Task Type.

The Properties tab is displayed by default.

2. Enter a Name for the Task Type.

3. Enter a Task Type ID that can be used to identify the Task Type.

4. Enter a Task Type description.

5. To specify an Integration, click the magnifying glass to search for and select anIntegration, then click OK. Selecting an Integration enables the Task Type toinherit the parameters from that Integration.

6. Optional: For an End-User Type, select Allow Early Start to allow the Assigneeto open the task before the scheduled start time.

7. See also:





Chapter 23Creating Task Types

23-2


Setting Task Type ParametersThe Parameters tab enables you to set the parameters for the Task Type.

Note:

The Parameters tab is available only if you have selected an Integration thathas parameters that must be defined. Parameter values can be set at theTask Type level or at the task level.

Some tasks contain parameters that need to be changed each time that they areapplied to a schedule. For example, date-driven parameters for Data Entry tasks mayneed to be set to the current month each time they are added to a schedule. Whenyou set Task Type parameters, you can specify which parameters can be overriddenduring the scheduling process.

To set Task Type parameters:


2. Click the Task Types tab, and then click New.

3. Enter Task Type Name and Task Type ID.

4. Select the Parameters tab.

5. Enter parameter values as required.

6. Optional: To enable the parameter to be overridden at scheduling time, selectOverride at scheduling.

7. See also:






Specifying Task Type InstructionsYou can create a set of instructions for completing tasks. You can also add referencesto documents, files, or URLs to websites. For example, you can attach a policydocument as a reference, or a link to a product instruction guide.

To specify instructions:

1. On the Home page, click Application, and then Task Manager.

2. Click the Task Types tab, and then click New.

3. Enter the Task Type Name and Task Type ID.

Chapter 23Setting Task Type Parameters

23-3

4. Select the Instructions tab.

5. In Instructions, enter the instruction text.

To add a reference:

1. In the References section, click Add.

2. From the Type list, select one of these types:

• Local File

Enter a name, click Browse to select and attach the file, and click OK.

• URL

Enter a URL name, then enter the URL, for example: Oracle, http://www.oracle.com, and click OK.

Note:

You can add one or more attachments by using drag and dropfunctionality available from the Add Attachments dialog box. You canrename the attachment in the Name field, if desired. If you drag and dropmultiple attachments, you can upload them at one time.

You must access the Add Attachments dialog box to properly drag anddrop attachments.

3. See also:






Tip:

To delete a reference, select the reference, and click Delete.

Specifying Task Type QuestionsYou can specify Task Type questions that apply to all tasks with that Task Type.

Note:

The Questions tab is not available for a Task Type that uses an automatedIntegration.

To specify questions:

Chapter 23Specifying Task Type Questions

23-4

1. Create a new Task Type.

2. Select the Questions tab.

3. Click New.

4. From the New Question dialog box, for Question, enter the text for the question.

5. From the Type list, select a question type:

• Date

• Date and Time

• Integer

• List

Enter a list of valid responses to the question.

• Multi-Line Text

The maximum length should be less than 4,000 characters.

Enter the Number of Lines, from 3 to 50 lines. Multi-Line text determines howmany lines of text are visible, without scrolling, on the Actions dialog boxes.

Include Attachments- select if you want the custom attribute to include anattachments section.

6. Assign a Role. The purpose of assigning a role is to determine which role cananswer the question:

• Assignee

• Approver

• Owner

• Viewer

When re-ordering questions, you can only re-order within a role.

7. If the question is required, select Required.

The Required checkbox is disabled for Questions assigned to Owner or Viewerroles.

8. Click OK to save the question.

9. Optional: To change the order of questions, select a question, then click Move toTop, Move Up, Move Down, or Move to Bottom.

10. Optional: To edit a question, select the question and click Edit. To remove aquestion, select the question and click Delete.

11. Click Save and Close to save the Task Type.

12. See also:






Chapter 23Specifying Task Type Questions

23-5

Assigning Task Type AttributesTo locate Task Types in the system, you can apply attributes to the Task Type. Whenyou select an attribute, you can set a value for the attribute based on the attribute type.You can later filter by the attribute value.

For example, you may have a List attribute named Sales Region with the values ofNorth, South, East, and West. The current Task Type applies only to the West SalesRegion, so you can add the Sales Region attribute and set it to “West.”

To apply an attribute:


2. Click the Task Types tab on the left, and then click New.

3. Enter the Task Type Name and the Task Type ID.

4. Select the Attributes tab.

Enables administrators to assign attributes and provide values for the attributes.

To add an attribute, click Add. Enter:

• Attribute

Select an attribute from the list of defined attributes.

• Type

This field is not editable - it is populated by the Attribute.

• Value

Select a value associated with the type of attribute; for example, a numericvalue for Formatted Number attribute, a List for List attribute, multiple lines ofdisplayed text without scrolling for Multi-Line Text, a name of a person, User,or Yes or No for the Yes/No attribute.

• Access

All roles have view access unless otherwise specified in the Access box.

To add an access, for each of the roles:

a. Click Add.

b. Select a role: Owner, Assignee, Approver, with separate roles for eachApprover level currently in use in the application, or Viewer.

c. Select one of the Role access types.

– Do Not Display—Does not see this attribute on the Task Actionsdialog box, or in any of the dashboards, list views, or reports.

– Allow Edits—Has the ability to add, change, and remove values forthe attribute, but subject to the editability rules.

– Required—Requires a value for the attribute. The Required option isavailable for Assignees and Approvers. Until a value is provided,Assignees are prevented from submitting, and Approvers areprevented from approving.

d. Click OK.

Chapter 23Assigning Task Type Attributes

23-6

5. Click OK.

6. See also:







Working With Task Type RulesTask Type Rules apply to all Tasks of the same Task Type and thus serve as aconvenient mechanism to apply rules to groups of Tasks. Rules configured on theTask Type dialog propagate down to the Edit Task Dialog, appearing on the Rules tabin that dialog, in read-only form for template tasks, and copied to schedule tasks.

Available task type rules:

Auto Approve Task - Automatically completes specified approvals only if specifiedconditions have been met.

Example of conditions that could apply to this rule: If attributes have specified values(including calculated attributes)

When conditions are satisfied, the specified approver levels are marked as complete,thus progressing workflow to the next approval level, or to Closed if no additionalapproval levels exist.

Auto Approve Task runs when the Task status changes to Open with Approver.

Auto Submit Task - Causes a task to be submitted automatically if specifiedconditions are met.

When conditions are satisfied, the assignee role is marked as complete, thusprogressing workflow to the first approval level, or to Closed if no approval levels exist.

Auto-Submit Task rule runs when the Task status changes from Pending to Open withAssignee.

Prevent Task ApprovalThis rule prevents approval of a task based on attribute values, or othercharacteristics. This rule runs when the Approver clicks Approve.

Prevent Task SubmissionThis rule prevents submission of a task based on attribute values, or othercharacteristics. This rule runs when the Assignee clicks Submit.

To work with task type rules:



3. Click a task type and then click Edit.

4. Select the Rules tab. You can view the following information:

Chapter 23Working With Task Type Rules

23-7

• Order—The order of precedence.

• Rule—Name of the Rule

• Conditions—The choice of what conditions must exist before running the rule

5. To edit a rule, on the Rules tab, click Edit and update:

• Rule—Select a rule.

• Description—Optional. Explain why you configured the rule and how shouldbe used.

• Message (On some rules)

– Message to Approver—Define an optional message to approver in aprevent task approval rule.

– Message to Assignee—Define an optional message to assignee in aprevent task submission rule.

• Approver Level—Select the rule for all levels or select the Approver levels.

Note:

The Approver Level must be set on the Auto Approve Task rule, andthe Prevent Task Approval rule.

• Select Create Filter and populate the conditions section or select Use SavedFilter, and then select a filter. The filter selected and configured for the ruledetermines the conditions that trigger the rule to apply.

• Conditions—Select one:

– Use Saved Filter—The Conditions section displays a read-only version ofthe conditions associated with the saved filter.

– Create Filter—The Condition section is enabled.

Conjunction, Source, Attribute, Operand, and Value behave as they do forthe existing advanced filter feature.

• Filter Task—Specify on which task the conditions should be selected:Current Task, Any Predecessor, Specific Task (Provide the Task ID).

6. See also:






Viewing Task Type HistoryThe system maintains a history of Task Type actions, which you can view from theView Task Types dialog box. The History tab displays the components that wereupdated, the modification type, the old and new values, the user who made the

Chapter 23Viewing Task Type History

23-8

modification, and the change date. The information on the History tab is read-only andcannot be changed.

To view Task Type history:


2. Click the Task Types. tab on the left.

3. Select a Task Type and click Edit.

4. Select the History tab.

5. When you finish, click Save and Close or Cancel.

6. See also:






Editing Task TypesFrom the Task Types dialog box, you can edit Task Types. For example, you can addor delete attributes, edit parameters, add or delete questions, edit instructions, orchange the order of questions.

Editing Task Types may have an effect on tasks that are created from the Task Type.For tasks in a template, the effect is immediate. Changes to the Task Type(instructions, questions, and so on), are automatically updated in tasks of that type.There is no effect if you edit a Task Type in a schedule.

To edit a Task Type:



3. Select the Task Type that you want to edit.

4. Use one of these methods:

• Select Actions, and then Edit.

• Click the Edit icon.

• Right-click and select Edit.

5. Select the tab for the information you want to edit and edit the Task Type.


Viewing Task TypesIn Task Types, you can specify columns to display for the list of Task Types, or showall. You can reorder columns, sort columns by ascending or descending order, orchange the column widths.

To display columns:

Chapter 23Editing Task Types

23-9









Searching for Task TypesYou can use the Task Types dialog box to find Task Types. You can enter full orpartial names on which to search.

To search for Task Types:



3. Enter full or partial search criteria for the Task Type.

4. Optional: For additional search operators (such as Contains, Starts with, Endswith), click Advanced, and enter search criteria. Click Add Fields to selectadditional fields for search criteria.

5. Click Search.

Tip:

To reset the list to display all Task Types, click Reset.

Importing Task TypesYou can import Task Types or partial Task Type information from text files. Theprocess is similar to importing tasks into a template.

Note:

Task Type rules cannot be imported. Use Migration to import Task Typerules.

To import Task Types, you must have the Service Administrator or Power Usersecurity role.

Chapter 23Searching for Task Types

23-10

To import Task Types:



3. Click Actions, and then Import.

4. Click Browse and navigate to the file.

5. Select an import option:

• Replace—Completely replaces the definition of a Task Type with the definitionin the import file. This option replaces all Task Type detail with the informationthat is in the file that you are importing. It does not affect Task Types that arenot specified in the import file.

• Update—Updates partial information for Task Types. This option is not a fullreplacement of the Task Type details. Only details for the Task Typeproperties specified in the file are updated.

The system displays a warning that task types matching a task type ID in theimport file will be modified. If you do not want to overwrite the task type, clickCancel.

6. Select a Date Format.

Select a format from the drop-down list of allowed date formats. Date formats arenot translated. By default, the date format is set to the locale date format of theexported file location.

7. Select a File Delimiter for the import file: Comma or Tab. Comma is selected bydefault.

8. Click Import.

Exporting Task TypesYou can export Task Types to a comma-separated values (CSV) file, which can beread by Excel, then modify and reimport the file.

Note:

Task Type rules can't be exported. Use Migration to export Task Type rules.

To export Task Types:



3. Select a Task Type, then select Actions, and click Export.

4. Click Save File, and then OK.

5. Select a location in which to save the file, and click Save.

Chapter 23Exporting Task Types

23-11

Deleting Task TypesYou can delete Task Types that you no longer need. To delete a Task Type, you musthave Service Administrator or Power User security rights.

Note:

You cannot delete a Task Type if tasks belong to it.

To delete a Task Type:



3. Select the Task Type that you want to delete.


• Select Actions, and then Delete.

• Click the Delete icon.

• Right-click and select Delete.


Chapter 23Deleting Task Types

23-12

24Managing Task Templates

A task template defines a repeatable set of tasks required for a business process. It isused as a basis for creating schedules. You can create templates for different types ofprocesses.

Template tasks are not assigned to specific days on a calendar, but are defined usinggeneric days, for example, day-3, day-2, day-1, day 0, based on the process activities.You apply the task flow defined in the template to calendar dates when you createschedules.

If you are a Service Administrator or Power User, you can create, edit, delete, andhave viewer rights to templates.

Note:

The maximum number of task templates that you can create or import is10,000.

Creating Task TemplatesYou can create templates for specific tasks in a business process.

When you create a template, you can assign users or groups as viewers.

Watch this video to learn more about creating task templates.

Creating Task Templates.

To create a template:

1. Click the Application icon .

2. Click Task Manager


4. Click New.

5. Enter the necessary information in the template sections:

• Setting Template Properties

24-1


• Specifying Template Instructions

• Assigning Viewers to Templates

• Applying Template Attributes

• Specifying Day Labels

• Embedding Templates

• Working With Template Rules

Setting Template PropertiesThe Properties tab enables you to specify the template name, description, owner, andtime span.

You must assign a template owner to every template, which must be a ServiceAdministrator or Power User. The current ID is the default owner. The template owneris also the default owner of all tasks in the template unless overridden at the task level.

Tasks in a template are organized by numeric template days. Each template has aDay Zero. You can specify the number of days a template tracks before and after theZero day. Days before Day Zero are represented as Day-5, Day-4, and so on. Daysafter Day Zero are represented as Day 3, Day 4, and so on. A template has at leastone day (Day Zero), even if you do not specify days before or after it.

To set template properties:



3. From the New or Edit Template dialog, on the Properties tab, enter:

• Name

• Description


4. Enter the time span for the template.

• For Number of Days Before Day 0, select a number.

• For Number of Days After Day 0, select a number.

5. Optional: Select Embedded Only if the template is only to be used as anembedded template.

If this option is enabled, the template is not allowed to be deployed. This preventssupporting templates from being deployed by mistake.

6. For Owner, use the default owner or click Select Owner . Administrators, orPower Users configured with the Administrator or Power User roles are the onlyroles that will display when you click Search to select a user to assign as anOwner. Any member of the Shared Services group can perform the role, but thesame person cannot perform more than one role.




Chapter 24Creating Task Templates

24-2





Specifying Template InstructionsYou can specify instructions in the template for completing the business process.Users can view the instructions from tasks in the template. The instructions are alsotransferred to each schedule.

You may also want to supply additional detail to help users understand the purpose ofthe template and how to complete the tasks. You can attach additional references.

To specify template instructions:



3. From the New or Edit Template dialog, select the Instructions tab.

4. In Instructions, enter instruction text for each task in the template to include.

5. Click OK.

To add a reference:



• Local File


• URL

Enter a URL name, then enter the URL, for example: Oracle, http://www.oracle.com. and click OK.

Note:

To add a reference file or URL to multiple templates at one time:

a. Navigate to the templates main page.

b. You can multi-select (either highlight more than one row or selectmore than one using the SHIFT key), and then click Actions, thenAdd Reference, then File or URL.


24-3

Note:

You can also add one or more attachments by using drag and dropfunctionality available from the Add Attachments dialog box. You canrename the attachment in the Name field, if desired. If you drag and dropmultiple attachments, you can upload them at one time.









Assigning Viewers to TemplatesThe Viewers tab enables you to assign viewer rights to users who may view tasks inthe schedule and schedule tasks that are generated from the template. You canassign multiple users to a template as viewers. Viewers can be a team assignment. APower User viewer can view the template details and template tasks as read-only. AViewer has no template access, and only read-only access to schedules producedfrom the template.

Note:

Only users who have the task Viewer role can respond to questions.

To assign viewer rights:



3. From the New or Edit Template dialog, select the Viewers tab.

4. Click Add.

5. To search by users or teams, click Search Users, then select Users or Teams.

6. Enter a full or partial user name, then click Search.

7. To specifically identify a user, click Advanced, then enter a User ID, Emailaddress, or Description.

8. From the Search Results list, select IDs, then move them to the Selected box.

9. For additional details about the user, such as teams and roles, click Details.

10. Click Add or Add All to move users to the Selected list.


24-4

Tip:

To remove users, select them and click Remove or Remove All.








Applying Template AttributesTo locate templates in the system, you can apply attributes to the template. When youselect an attribute, you can set a value for the attribute based on the attribute type.You can later filter by the attribute value.

For example, you may have a List attribute named Sales Region with the values ofNorth, South, East, and West. The current template applies only to the West SalesRegion, so you can add the Sales Region attribute and set it to “West.”




3. From the New or Edit Template dialog, select the Attributes tab.

4. Click Add.

5. From the Attribute list, select an attribute.

6. For Value, depending on the attribute, select a value for the attribute from a drop-down list, or enter a value.

7. Click OK.








Specifying Day LabelsYou can customize the names of days in the template. Editing the name of the daydoes not change its sequential order.


24-5

Day Labels created in a template are copied to any schedule created from thetemplate.

To specify day labels:



3. From the New or Edit Template dialog, select the Day Labels tab.

4. Select a day to rename.

5. Rename the day from its default value to a custom name.

6. Click OK.








Embedding TemplatesYou can reuse tasks from one task template in another by embedding one templateinto another template. When you schedule tasks for a template, tasks for embeddedtemplates are also scheduled.

For example, you may have two processes that are essentially the same, with someadditional tasks for one of the processes. You can specify that one template embedsthe second template so if you change one template, you do not need to update theother one. When you generate a schedule, it will include the tasks from the othertemplate.

Note:

Only one level of embedding is possible. For example, if Template A isembedded in Template B, then Template B cannot be embedded in anothertemplate.

Embedded template are task templates that are not designed to be deployed directly,but rather to be used by other templates that are directly deployed. The ManageTemplates screen includes these columns to identify embedded templates:

• Embedded: a list of templates that are embedded in the current template. Blank ifnone.

• Embedded In: a list of templates that the current template is embedded in. Blank ifnone.

The columns are not displayed by default, but are available from the View menu.


24-6

To embed templates:



3. From the New or Edit Template dialog, select the Embedded Templates tab.

4. To identify previously embedded templates, from the top menu, select View, thenColumns, and select Embedded In or Embedded Templates.

5. From the Available Templates list, select a template to embed.

6. Click Move to move the template to the Embedded Templates list.

Tip:

To remove a template or templates, select the template from theEmbedded Templates list and click Remove or Remove All to move itto the Available Templates list.

7. Click OK.








Working With Template RulesTemplate rules apply to all tasks in the template, and rules are also applied to groupsof tasks. Rules that you configure in the Template dialog box apply to the Scheduledialog box and the Edit Task dialog box, and they are displayed on the Rules tabs, inread-only form.

Template rules:

Auto Approve Task - Automatically completes specified approvals if specifiedconditions have been met.

Examples of conditions that could apply to this rule:

• Attributes have specified values (including calculated attributes)

• Predecessor task contains an attribute with a specified value

When conditions are satisfied, the rule causes the specified approver levels to bemarked as complete, and workflow progresses to the next approval level or is closed ifno additional approval levels exist.

This rule runs when the Task status changes to Open with Approver.

Auto Submit Task - Automatically submits a task if specified conditions are met.


24-7

When conditions have been satisfied, the rule causes the assignee role to be markedas complete, thus progressing workflow to the first approval level, or to Closed if noapproval levels exist.

Notes:

1. Auto Submit Task runs when the Task status changes from Pending to Open withAssignee. Auto Submit Task rule honors predecessor relationship. It will only runwhen Finish-To-Finish predecessors have completed without error and FinishError-To-Finish predecessors have completed. When a Finish-To-Finishpredecessor is Closed by either user or rules, it should check for its Runningsuccessors and trigger Auto Submit Task rules if necessary.

2. Auto Submit Task rule is not triggered when the task has missing parameters.

Prevent Task ApprovalThis rule prevents approval of a task based on attribute values, or othercharacteristics. This rule runs when the Approver clicks Approve.

Prevent Task SubmissionThis rule prevents submission of a task based on attribute values, or othercharacteristics. This rule runs when the Assignee clicks Submit.

To work with template rules:

1. On the Home page, click the Application icon .



4. Double-click a template.



• Rule—Select the Rule


6. To create or edit a rule, on the Rules tab, click Create or Edit and update:

• Rule— Select a rule.






24-8

– Use Saved Filter—The Conditions section displays a read-only version ofthe conditions associated with the saved filter.



• Filter Task— Specify on which task the condition should be selected: CurrentTask, Any Predecessor, Specific Task (Provide the Task ID).

7. To delete, duplicate, or reorder a rule, click the appropriate button and follow theinstructions.








Viewing Template HistoryThe system maintains a history of template actions, which you can view from theTemplate dialog box. The History tab displays the components that were created orupdated, the modification type, the old and new values, the user who made themodification, and the change date. The information on the History tab is read-only.

To view template history:



3. Select a template for which to view history and click Edit.

4. Select the History tab.

5. Click OK.

6. Enter the necessary information in the template tabs:








Opening TemplatesYou can open and work with templates from the Templates dialog box.

Chapter 24Opening Templates

24-9

To open a template:



3. From Templates, select a template.


• Select Actions, and then Edit.

• Click the template.

• Right-click and select Edit.

Adding Tasks to TemplatesYou can add tasks to Task Manager templates. Each task has a start date and time.End-User tasks also have an end date and time when added to a template. The startday in a template corresponds to template days, rather than to calendar days.

Note:

The maximum number of tasks that you can add to a Task Manager templateis 500,000.

To add a task to a Task Manager template:



3. Select and open a template.

If you have a large list of templates, enter a full or partial name in the Search boxto search for templates from a list in the selection dialog.

4. Add tasks as required.

5. Click OK.

Editing TemplatesYou can edit Task Manager templates to change the properties, such as the name of atemplate and the number of days before and after Day Zero. If you reduce the numberof days before or after the Day Zero, tasks associated with those days are removed.Editing a template has no effect on schedules previously generated from that template.

You can edit, copy, and delete tasks in a template.

You must be working in the source template to edit tasks from embedded templates.

To edit a Task Manager template:



Chapter 24Adding Tasks to Templates

24-10

3. Select a template and click Edit.

4. Edit the template properties.

5. Click OK.

Importing Tasks into TemplatesYou can import tasks, or partial task data, from text files such as a Microsoft Excelspreadsheet, into a template. For example, you can enter task definitions as rows inExcel, save the file as a comma-separated values (CSV) file, and then import it into atemplate. You can also use the Import feature to quickly add many repetitive tasks byediting the fields in a text file and importing it, rather than creating individual tasks.

Note:

Before you import tasks into a template, you must specify task IDs that areunique in the template to ensure that no two tasks have the same ID.

To import tasks, you must have security rights to edit the template.

These options are available for importing tasks into a template:

• Replace

Replaces the definition of a task with the definition in the import file. This optionreplaces the task detail with the detail that is in the file that you are importing. Itdoes not affect other tasks in the template that are not specified in the import file.

• Update

Updates partial information for tasks. For example, in the import file, you mighthave made changes to task instructions, reassigned Owners, Assignees, andApprovers, or removed some attributes and added new attributes. You might alsohave made the same change to a large number of tasks, for example, adding anew attribute to 100 of 400 tasks. The update option is not a full replacement ofthe task details. Only details for the task properties specified in the file areupdated. For example, if the import file has only a column for a task instructions,the task name, Assignee, attributes, and other properties are not affected.

To import tasks into a template:

1. On the Home page, click Application, and then click Task Manager,


3. Select a template into which to import tasks.

4. Click Import Tasks.

5. Enter the name of the file to import, or click Browse to find the file.


• Replace— Replaces the definition of a task with the definition in the importfiles. It does not affect other tasks that are not specified in the import file.

• Update— Updates partial information for tasks. For example, in the import file,you might have made changes to task instructions, reassigned Owners,

Chapter 24Importing Tasks into Templates

24-11

Assignees, and Approvers, or removed some attributes and added newattributes. You might also have made the same change to a large number oftasks, for example, adding a new attribute to 100 of 400 tasks. The updateoption is not a full replacement of the task details. Only details for the taskproperties specified in the file are updated. For example, if the import file hasonly a column for a task instructions, the task name, Assignee, attributes, andother properties are not affected.

Note:

The system displays a warning that tasks in the template that match atask ID in the import file will be modified. If you do not want to overwritethe task, click Cancel to cancel the import process.



8. Select a File Delimiter for the import file:Comma or Tab. Comma is selected bydefault.

9. Click Import.

• If the import is successful, the “Import Success” dialog box is displayed, indicatingthe template name, the name of the file containing the tasks, and the total numberof tasks imported. Click OK.

• If errors are found, the import process is not run, and the “Import Errors” dialogbox displays errors. View the errors, then click OK to return to Manage Templates.

Table 24-1 Troubleshooting Import Errors

Error Resolution

Duplicate Task ID Check for duplicate Task IDs. Task IDs mustbe unique within the template or schedule.See Creating Tasks.

Task Name is too long The Task Name can contain a maximum of 80characters. See Setting Task Properties.

Organizational Value - "Invalid Value" The Organizational Value cannot be blank,contain bullet points or multiple lines.

Task Import File FormatThe task import file enables you to specify the task information that you want to importinto a template. The first row contains only the column headings that identify the datain that column, for example, TaskName. Separate rows are used to define each task.

Each task in the file must be given a unique ID in the TaskID column. You use thenumeric IDs to uniquely identify predecessors and parent tasks. For example, whenyou enter a parent task in the Parent column, you enter the numeric ID of the taskrather than the task name.

Chapter 24Task Import File Format

24-12

When you use the Replace or Replace All options, you can add, remove, and shift thecolumns but you cannot remove required columns. When you use the Update option,there are no required columns except TaskID, or TaskTypeID when you are importingTask Types. The data in each column must match the column ID in the first row.

Many column IDs may have an indeterminate amount of values. For example, a taskmay have many viewers. You can add parameters by modifying the ending number,for example, Viewer4, Viewer5, and so on.

The numbers that you append to the column IDs for Approvers, Questions, orReferences only represent the relative order with the other approvers, questions, orreferences. When you update these, the system matches by the name of the approver,question, or reference without regard to the number in the file format column. Toreplace question text, approvers, or reference names, you must use Replace mode.When you select Update mode, the system only adds a new question, approver, orreference if the file names do not match.

All Text Lookup rows in the file must match values stored in the application. Forexample, if you are importing Task Types, you must have specified values for themwhen you set up the application. For groups of column headings, if you have a certainnumber of one of the group, you must have the same number for other members. Forexample, if you have QText5, there must be a corresponding QType5.

Column ID Description Type

TaskID ID of task. Maximum of 80characters.

Text

TaskName Name of task Text

TaskType Task Type Text Lookup

Description Full description of task. Maximum of1000 characters.

Text

Priority Task priority (High, Medium, Low) Text Lookup

StartDate Start date, in template days (forexample, -5, 0, 1, 12)

For schedules, the start date must bea calendar date in the locale format.

Integer

StartTime Start time in HH:MM (24-hour), forexample: 13:00

Integer

EndDate User tasks only, in template days (forexample, -5, 0, 1, 12)

For schedules, the end date must bea calendar date in the locale format.

Integer

EndTime User tasks only, in HH:MM (24-hour),for example, 13:00

Integer

Duration Task duration in minutes (automatedtasks only)

Number

Owner Task owner Text Lookup

Assignee Task Assignee (user tasks only) Text Lookup

Active Whether the task is active. Onlyapplies to template import.

Boolean

StartEarly Whether the Assignee is allowed toopen a pending task prior to thescheduled start time

Boolean


24-13


RunAs RunAs user name. Only applicablefor system-automated tasks.

Text Lookup

Instruction Instruction text. Maximum of 2 GB. Text

Reference# Instruction reference (URL andContent Server references)

URL

RefText# Reference name, for URL references Text

RefType# Reference type (URL, Document) Text Lookup

RefURL# Reference URL, for URL references URL

RefDocId# Reference document ID, fordocument references

Integer

Approver# Approver Level User Name

Viewer# Task viewer User Name

QText# Required for question. Text ofquestion. Maximum of 255characters.

Text

QType# Required for question. Data type ofquestion (Text, Member, True/False,and so on)

Text Lookup

QReq# Required for question. Questionrequired? (Yes or No)

Boolean

QList# List of values for question, separatedby | symbol, for example, Red|Green|Blue|Yellow.

Text Lookup

QCurrSymbol# Currency format for question X Text

QDecPlaces# Number of significant digits after thedecimal places for question X

Number

QNegNumFmt# Negative number format for questionX

Text: - or ( )

QScale# Scale format for question X Number, in magnitude: 1000 and soon

QThouSep# Thousand separator indicator forquestion X

Boolean

Attribute# Attribute name, for example, Color Text Lookup

AttrVal# Attribute value, for example, Red.Maximum of 255 characters.

Text

AttrDisplay Display to user (in task action dialogbox) for attribute

Boolean

Param# Parameter name Text Lookup

ParmVal# Parameter value Text

Parent Task ID of the task parent Task ID

Predecessor# Predecessor task ID (from column A) Task ID

PredType# Required. Predecessor type (forexample, Finish to Start).

Text Lookup


24-14


PredTemplate# Name of the predecessor template orschedule, if the predecessor belongsto a different template or schedule

Text

When you import Task Types, these columns are used:

• TaskTypeID

• IntegrationType

• ParamOverride# - whether the parameter can be overridden

A sample task import file is provided. It contains these dynamic parameters, which youcan modify:

• Two questions

• Two attributes

• Two instructional references

• Three predecessor tasks

• Three approver levels

Exporting Tasks to Microsoft ExcelYou can export tasks from a template to a flat file in CSV format, then use MicrosoftExcel to modify the file. For example, you can export the tasks from a template in atest installation and import them to a template in a production installation. When youexport tasks from a template, they are saved to a CSV file.

To export tasks:



3. From Templates, select a template from which to export tasks.

4. Click Export Tasks.

5. Click Save File, then click OK.

6. Select a location in which to save the file, and click Save.

Reassigning Users in TemplatesYou may periodically need to reassign users to different tasks. For example, you maycreate a template and assign a user to certain tasks; however, later that employeeleaves the company and another employee assumes those tasks. You can use theReassign feature in the Templates dialog box to automatically change assignmentsinstead of manually searching for, opening, and editing individual tasks. The Reassignfeature enables you to quickly find the tasks associated with one user and reassignthem to another.

Chapter 24Exporting Tasks to Microsoft Excel

24-15

You can select the roles for which to reassign users. For example, if you select theOwner role, the system reassigns the user only in tasks in which the user wasassigned as the owner.

To reassign users:



3. Select the template in which you want to reassign users.

4. Select Actions, and then Reassign User.

5. Click Find User and enter the search criteria for the user that you want to replace:a. From the Select User dialog box, enter the first or last name for the user, and

click Search.

b. Select the user from the results, then click OK.

6. Click Replace with and enter search criteria for the user to whom you want toreassign tasks.

7. Select roles for the user that must be reassigned:

• Owner

• Assignee

• Approver

• Viewer

8. Click Reassign.

When the process ends, the system displays a “Reassign Users - Success”message that indicates that the user reassignment is complete, and displays thetemplate name and total number of user reassignments made.

Creating Schedules from TemplatesYou can create schedules from templates. Creating a schedule from a templatepopulates the schedule with the tasks in the template. If the source template hasembedded templates, the tasks in the embedded templates are included. Templateinstructions, viewers, and attributes are also added to the schedule.

You create schedules from templates from the Edit Templates dialog box. The LastSchedule column shows the last schedule created from each template. The Schedulescolumn shows the total number of schedules created from each template.

To create a schedule from a template, you must have the Service Administrator orPower User role.

The schedule starts in a Pending status, which gives you the opportunity to make finalchanges in the definition.

When template tasks are added from a template to a schedule, they are assignedcalendar dates based on their relationship to the template Day Zero. The dates canalso account for non-working days of the schedule if you specified them. For example,if Day 0 is a Friday, the tasks for Day 1 are placed on the following Monday if youselected to exclude weekend days. The Date Map displays the default calendar dateassigned to each template day. You can use the Date Map feature to adjust the dateassignments.

Chapter 24Creating Schedules from Templates

24-16

A task in one template can have predecessor tasks in other templates. When youcreate a schedule from a template, you can select predecessor tasks in schedules aspredecessors for tasks with predecessors in other templates. You use thePredecessor Task Links tab to select predecessor tasks in schedules. ThePredecessor Task Links tab lists all tasks with predecessors in other templates, andenables you to select a predecessor in a schedule for these tasks.

When you create a schedule from a template, you can globally update the taskparameters for a Task Type if the parameters have the override option enabled.

To create a schedule from a template:



3. Select the template that you want to schedule.

4. If the template was successfully validated, create the schedule: Click the Actionsicon on the right side, and then select Create Schedule, or click the CreateSchedule icon in the top menu.

On the Schedule Parameters tab, enter the following fields:

• Schedule Name

• Year

• Period

Select a period for the schedule.

• Day Zero Date

Select the calendar date to assign to the template Day Zero.

• Date Mapping

– Organizational Unit

– Calendar days

– Working days

– Advanced Configuration dialog box:

Click Advanced Configuration to override the Organizational Unit andWork Days configuration for all tasks in the schedule.

Tip:

You can create one global template and have that templatecreate the proper schedules for each regional entity, taking intoconsideration the holiday calendars, time zones, and work dayconfigurations of the entity.

* Organizational Unit

Select one:

* Use Task Value—Select a value from the Organizational Unit

Chapter 24Creating Schedules from Templates

24-17

* Set Value To—The selected organizational unit is applied to alltasks in the Schedule (even if the task in the template contained adifferent Organizational Unit value). Since all tasks have the sameOrganizational Unit, the Organizational Unit in the Date Mappingpanel on the Schedule from Template dialog box displays asRead Only.

* Work Days—If you do not assign an organizational unit to a task, andyou do not use the Override Work Days feature, than the applicationuses the following default: Monday – Friday are working days, andSaturday and Sunday are non-working days.

– Date Map—For each template day whose date assignment you want tomodify, in the Date column, enter the new date.

5. Optional: Select the Predecessor Task Links tab, select the schedule thatcontains the predecessor task and in the Assigned Task list, select thepredecessor task.

6. Optional: Select the Override Parameters tab, review the parameters, and foreach parameter that you want to modify, in the New Value column, enter a newvalue.

Note:

This Override Parameters tab displays only tasks that use a Task Typein which at least one parameter has the Override option enabled.

7. Click Create Schedule.

A schedule is created and populated with the tasks, instructions and viewers fromthe template. It has a status of Pending. By default the schedule is opened into aview when created.

Review the schedule and make adjustments as needed.

Manually Validating TemplatesWhen you generate a schedule from a template, the system automatically validatesthe template first to check for uniqueness violations, tasks that directly or indirectlydepend on each other, or a date-precedence mismatch. For example, you cannot havecircular predecessors.

You can manually validate a template. Validation is particularly useful to check forproblems after you import tasks into a template from a file. If the template has an error,you can use the navigation links in the validation results to navigate to the source ofthe error.

To manually validate a template:



3. From Templates, select a template.

4. Click Validate.

Chapter 24Manually Validating Templates

24-18

• If no errors exist, the system displays a “Template valid” message.

• If an error is displayed, click the link to the error.

Viewing Task Manager TemplatesIn the Templates dialog box, you can specify which columns to display for the list oftemplates, or show all. You can also reorder columns, sort columns by ascending ordescending order, or change the column widths.

To display columns:









Searching for TemplatesYou can use the Templates dialog box to quickly find Task Manager templates. Youcan enter full or partial names on which to search.

To search for templates:



3. Click the > sign to expand the Search box.

4. Enter full or partial search criteria.


Tip:


6. Click Search.

Chapter 24Viewing Task Manager Templates

24-19

Tip:

To reset the list to display all templates, click Reset.

Deleting TemplatesYou can delete Task Manager templates that you no longer need. To delete atemplate, you must have security rights to the template.

Deleting a template removes it from the list of available templates and removes tasksassociated with it. It does not directly affect a running schedule, however somereporting and dashboard metrics may use the template to link various schedule runstogether, which are not possible if the template is deleted.

To delete a Task Manager template:



3. Select the template, and click Delete.


Chapter 24Deleting Templates

24-20

25Managing Tasks

Tasks are the core units of action in a business process, such as data entry or dataconsolidation.

Each task has different parameters depending on the Task Type. If you have ServiceAdministrator or Power User security rights, you can create, edit, or delete tasks.

See Creating Tasks.

Creating TasksYou can add tasks to templates or schedules. If you create a task in a template, youassign the start and end date as days before or after Day Zero. If you create a task ina schedule, you select calendar dates for the start and end dates.

You can group tasks under parent tasks to provide a simpler view of the businessprocess. After viewing upper-level parent tasks, you can then drill into the underlyingtasks. Child tasks of parent tasks may have different owners than the parent task.

You can create a task using any of these methods:

• Drag and drop the Task Type onto a template or schedule in a view.

• Right-click on a task and select New.

Then enter the task information:

• Setting Task Properties

• Setting Task Parameters

• Specifying Task Instructions

• Selecting the Workflow

• Adding Task Questions

• Setting Task Access

• Setting Task Predecessors

• Applying Task Attributes

• Working With Task Rules

• Viewing Task History

Watch this video to learn more about creating tasks.

Creating Tasks

25-1


Setting Task PropertiesThe Properties dialog enables you to set the task name, task ID, description, task type,priority, start and end date or duration.

You also use Properties to specify task Owners and Assignees. If an Owner orAssignee is not available to work on the task (due to sick time, vacation, has left thecompany, or is simply too busy), you can reassign users associated with a task,template, or schedule. Template, schedule, and task Owners, Assignees, andApprovers may also reassign their tasks.

For end-user tasks, you can allow an Assignee to open a pending task prior to thescheduled time, if all task predecessor conditions have been met.

To set task properties:


2. Click the Templates tab on the left and then click Tasks.

3. Open a task.

4. Click Properties and enter this information:

• Enter a Task Name of 80 characters or less.

• Enter a Task ID that can be used to identify the task (required). Task IDs mustbe unique within the template or schedule.

• Enter a Description of 1000 characters or less.

Note:

You can use carriage returns and URLs in Descriptions, Questions,and Instructions.


Represents a hierarchical entity-type structure that you can use to model yourorganization. Define a separate organizational unit for each entity for whichseparate reporting is required, or for entities that require differentconfigurations for any of the following: time zones, holidays, work days, orviewer or commentator assignments. Organizational Units are defined insystem settings.

• Task Type (required)

Click Browse and select a Task Type.

• Priority

Select a priority for the task:

– High

– Medium

– Low

• Owner

Chapter 25Setting Task Properties

25-2

Use the default owner or click Select Owner to select a user or SharedServices group.

• Select Active to include this task in schedules generated from the template.

Note:

This option is not available for tasks created in schedules.


6. See also:










Setting Task ParametersThe Parameters dialog only contains data for tasks that are associated with anIntegration Type and have parameters. Integration Types provide links to externalapplications. From Parameters, you can set specific information about the task andhow it is run. The parameters are passed to the external application. For example, ifthe task contains a link to a data grid, you might use the Parameters dialog to select apoint of view for the grid.

To set task parameters:



3. From the New or Edit Task dialog box, click Parameters.

4. If the parameter values are not entered by the task type, you may enter therequired parameter values.

Note:

If the parameters are not defined when the task is ready to start, anemail is sent to the task owner. The task waits to start until the valuesare provided.

Chapter 25Setting Task Parameters

25-3

5. See also:










Specifying Task InstructionsTask owners can create a set of instructions for completing the task. All other userswho have access to the task are only able to read the instructions. If there are taskinstructions that are inherited from the Task Type, template, or schedule, thatinstruction text is displayed above the instruction text box and is read-only.

For template tasks, the Template and Task Types instructions are viewable but noteditable.

To specify instructions:


2. Click the Templates tab on the left, and then click Tasks.

3. From the New or Edit Task dialog box, click Instructions.

4. Enter the Instructions which can have unlimited characters.

To add a reference:

1. In the References section, select Actions, and then Add, or select the Add icon.


• Local File


• URL

Enter a URL name, then enter the URL, for example: Oracle, http://www.oracle.com.

Chapter 25Specifying Task Instructions

25-4

Note:

To add a reference file or URL to multiple tasks at one time:

a. Navigate to the Tasks page.

b. You can multi-select (either highlight more than one row or selectmore than one using the SHIFT key), and then click Actions, thenAdd Reference, then File or URL.

Note:

You can also add one or more attachments by using drag and dropfunctionality available from the Add Attachments dialog box. You canrename the attachment in the Name field, if desired. If you drag and dropmultiple attachments, you can upload them at one time.


3. See also:










Selecting the WorkflowTo select the Task Manager workflow:



3. From the Task dialog box, click Workflow.

4. The Workflow section contains the Assignee and Approver assignments. Enter thisinformation for the Assignee:

• Assignee—To select to assign an Assignee to a named user or Shared

Services Group, click .

The "Actual" attribute is available for each workflow stage, showing the actualuser for the completed workflow, for example Assignee (Actual). In the

Chapter 25Selecting the Workflow

25-5

workflow, the Actual column shows who performed work on the task,regardless of the user status.

Note:

The additional user information only appears if the task is reassignedafter it was completed by the initial user.

For an End-User task, for Assignee, click Select Assignee to find auser.

Note:

If you do not select an Assignee, the owner becomes the defaultAssignee. Parent and automated tasks have no Assignees.

• Backup—If you assigned a user for the primary Assignee, you can assign abackup user authorized as an Assignee:

a. Click Backup .

b. Enter the First Name and Last Name or click Search to select a backupuser.

c. Click OK.

• Starts

Select a start date, then select the time of day, in increments of 15 minutes, forthe task to start.

• Ends

Select an end date, then select the time of day, in increments of 15 minutes,for the task to end.

• Optional: For Minimum Duration, enter the minimum duration of a task in theform of Days, Hours, and Minutes. An At Risk criteria is based on the conditionif the Start date was missed and (the End_date minus the Current_date is lessthan the minimum task duration or the End_Date minus the Start_Date is lessthan the minimum duration). The At Risk tasks display in the Needs AttentionGraph in the Status Chart of the Dashboard.

• Optional: For an End-User task, select Allow Early Start to allow theAssignee to open the task before the scheduled start time.

Enter this information for the Approver:

• Level Name

• Backup

• End Date

5. See also:


Chapter 25Selecting the Workflow

25-6








Adding Task Questions

Note:

The Questions tab is not displayed for automated tasks or parent tasks.

When you create a task, you may want the Assignee to answer questions about theiractions before they indicate a task is complete. For example, you may ask if a certainprocess was followed when completing that task.

You can specify questions on the task. You can specify various types of questions,such as Text, Number, or True/False, and indicate whether they are required. If aquestion is required, the user must respond or they cannot submit the task forapproval. You can also order the questions by using the Move Up and Move Downbuttons.

For schedule tasks, users can respond to the questions from the Task Actions page. Ifyou are creating or updating a task in a template, an additional column displays,showing whether the row is locked or unlocked to indicate whether the user canremove or update the questions. Rows that are locked cannot be edited or deletedbecause they are inherited from the Task Type.

In templates, the Task Type questions are displayed, but are not editable.

Note:


To add a question:



3. From the Task dialog box, click Questions.

4. Click Add.

5. Enter the Question with 4000 characters or less.

6. From the Type list, select a type:

Chapter 25Adding Task Questions

25-7

• Date

• Date and Time

• Integer

• List

Enter a list of valid responses to the question.

• Multi-Line Text

The maximum length should be less than 4,000 characters.

Select Multi-Line Text, and then enter the Number of Lines, from 3 to 50lines. Multi-Line Text determines how many lines of text are visible withoutscrolling, on the Actions dialog boxes.

Select Include Attachments if you want to include an attachments section.

• Number

If you select Number, select number formatting options:

– For Decimal Places, enter a value for the number of decimal places todisplay.

– Select the Thousands Separator option if you want numbers to display athousands separator (for example, 1,000.00)

– From the Currency Symbol list, select a currency symbol, for example,Dollars ($).

– From the Negative Number list, select how to display negative numbers,for example, (123).

– From the Scale list, select a scale value for numbers, for example, 1000.

• Text

• True or False

• User

• Yes or No

7. Assign a Role (Assignee, Approvers, Owner, Viewer) to the question. Access isbased on responsibilities.

8. If the question is required, select Required.

The Required checkbox is disabled for Questions assigned to Owner or Viewerroles.

9. Click OK.

10. Optional: To change the order of questions, select a question, then click Move toTop, Move Up, Move Down, or Move to Bottom.

11. Optional: To edit a question, select the question and click Edit. To remove aquestion, select the question and click Delete.

12. See also:




Chapter 25Adding Task Questions

25-8







Setting Task AccessThe Access tab enables you to add or remove Viewers and Approvers for the currenttask. It also enables you to specify the order of approvers. You can specify up to tenapprovers and an unlimited number of viewers.

To set task access:

1. From the New Task dialog box, select the Access tab.

2. Enter the first or last name of the user, then click Search.

To specifically identify a user, click Advance, then enter a User ID, Email address,or Description.

Tip:

For additional details about the user, such as groups and roles, clickDetails.

3. Optional: To change the order of approvers, select users, then click Move to Top,Move Up, Move Down, or Move to Bottom.

Tip:

To remove a user from the Approvers or Viewers list, select the user,then click Remove.

4. See also:










Chapter 25Setting Task Access

25-9

Setting Task PredecessorsThe Predecessors tab enables you to set predecessors for the current task. Fortemplate tasks, you can choose a predecessor from another template, and forschedule tasks, you can choose a predecessor from another schedule. You mustassign a condition to the predecessor/successor relationship.

A task does not need predecessor tasks as long as a start date and time is specified. Ifboth are specified, the task begins when the predecessor tasks are started orcomplete (for Finish-to-Start) and the start date and time is reached.

You can set these conditions under which the predecessor relationship is established:

Condition Description

Finish to Start Default. The task starts as soon as thepredecessor task completes or finishes withwarning.

Finish Error to Start The task starts as soon as the predecessortask completes, even it is in error.

Finish Error to Finish The task completes as soon as thepredecessor task completes, even it is in error.

Finish to Finish The task cannot be marked as Complete untilthe predecessor task is marked as complete.This is primarily used for user tasks. Forexample, a user can start a documentsummary, but cannot mark it complete until theconsolidated data is final.

To set task predecessors:



3. From the New or Edit Task dialog box, select the Predecessors tab.

4. Click Add.

5. To search for a Predecessor:

a. Click Basic.

b. To refine the search, click Add Fields and select search fields; for example:Execution Type, Start Date, End Date.

c. From each of the Condition lists, select a condition.

d. Click OK.

6. Select a predecessor task(s) and click OK.

7. See also:





Chapter 25Setting Task Predecessors

25-10






Applying Task AttributesTo locate tasks in the system, you can apply attributes to the task. When you select anattribute, you can set a value for the attribute based on the attribute type. You can laterfilter by the attribute value.

For example, you may have a List attribute named Sales Region with the values ofNorth, South, East, and West. The current task applies only to the West Sales Region,so you can add the Sales Region attribute and set it to “West.”

To apply task attributes:

1. Open a task and select the Attributes tab.

To add an attribute, select Actions, and then Add. Enter:

• Attribute


• Type

This field is not editable - it is populated by the Attribute.

• Value

Select a value associated with the type of attribute; for example: a numericvalue for Formatted Number attribute, a List for List attribute, multiple lines ofdisplayed text without scrolling for Multi-Line Text, a name of a person, User,or Yes or No for the Yes/No attribute.

• Access

All roles have view access unless otherwise specified in the table below.

To add an access, for each of the Text Box and Attachments tabs:

a. Click Add.

b. Select a role.

c. Select one of the Role access types:

– Do Not Display—Does not see this attribute in any of thedashboards, list views, or reports.

– Allow Edits—Has the ability to add, change, and remove values forthe attribute, but subject to the editability rules.

– Required—Requires a value for the attribute.

2. Click OK.

3. See also:


Chapter 25Applying Task Attributes

25-11









Working With Task RulesTask rules affect task behavior. These rules enable users to assign rules directly totasks, especially when, because a rule is unique to a task, assigning rules isn’tappropriate at the Template, Schedule, or Task Type level. These rules apply to theTasks for which the rules were configured.

Available task rules:


Examples of conditions that could apply to this rule include:

• Attributes have specified values (including calculated attributes)

• Predecessor task contains an attribute with a specified value

When conditions are satisfied, the specified approver levels are marked as complete,thus progressing workflow to the next approval level, or to Closed if no additionalapproval levels exist.

This rule runs when the Task status changes to Open with Approver.


When conditions are satisfied, the assignee role is marked as complete, thusprogressing workflow to the first approval level, or to Closed if no approval levels exist.

This rule runs when the Task status changes from Pending to Open with Assignee.

Prevent Task ApprovalPrevents approval of a task based on attribute values, or other characteristics. Thisrule runs when the Approver clicks Approve.

Prevent Task SubmissionPrevents submission of a task based on attribute values, or other characteristics. Thisrule runs when the Assignee clicks Submit.

To work with task rules:

1. On the Home page, click Tasks, and then select the Schedule Tasks tab.

2. Create a task.

3. Select the Rules tab to open a New Rule.


Chapter 25Working With Task Rules

25-12



4. Under Rule, select the type of rule you want to use:

• Auto Approve Task

• Auto Submit Task

• Prevent Task Submission

• Prevent Task Approval

• Prevent Task Rejection

• Send Email on Update


5. Optional: Under Description, explain why you configured the rule and how itshould be used.

6. For Approver Level, select the rule for all levels or select the Approver levels.

7. Select the Filter to determine the conditions that trigger the rule to apply:

• Use Saved Filter—The Condition section displays a read-only version of theconditions associated with the saved filter.

• Create Filter—The Create Condition section is enabled. Select theconditions that apply for the advanced filter: Conjunction, Source, Attribute,Operand, and Value

8. Under Filter Task, select the task to which the conditions should be applied:Current Task, Any Predecessor, Specific Task (Provide the Task ID).

9. See also:










Viewing Task HistoryFor each task, the system retains a history of the changes made to it; for example, ashift in dates or change in ownership. Each change record includes the field,modification type such as added, created, or changed, the old and new values, theuser who made the change, and the date on which the change was made. Theinformation on this tab is read-only.

Chapter 25Viewing Task History

25-13

To view task history:

1. On the Home page, click Tasks, and then click the Schedule Task tab.

2. Select a task.

3. Select the History tab on the right.

4. When you finish, click Save and Close.

Working with the Task Dialog BoxTo view the Task dialog box:

1. On the Home page, click Tasks, and then Schedule Tasks

2. Select a task.

3. Click the Properties tab on the right to view the following fields:

• Name

• Task ID

• Status

• Schedule

• Priority

• Task Type

• Task Type

• Description

• Owner

• Start Date

• End Date

• Duration

• Actual Start Date

• Actual End Date

• Actual Duration

4. Click Instructions to display any instructions.

5. Click Alerts to display current alerts.

6. Click Workflow to view assignees for the tesk.

7. Click Attributes to view any attributes for the task.

8. Click Questions to view any questions that have been posted for the task.

9. Click Comments to view any comments that have been posted for the task.

10. Click Related Tasks to view any related tasks. You can view Predecessors orSuccessor tasks.

11. Click Parameters to view dashboard, cluster, application, and so on.

12. Click History to capture an audit trail of changes to the task. You can view theactivity for the task, including All Activity, Last 7 Days, and Today.

Chapter 25Working with the Task Dialog Box

25-14

13. Click Actions, select one of the following actions: .

• Submit Task

• Abort Task - The purpose of aborting a task (instead of performing a forcedclose) is to prevent successors from continuing and to keep the processmoving.

• Force Close Task

• Refresh

14. Click Close.

Importing and Exporting TasksImporting Tasks

To import tasks:

1. On the Home page, click Tasks, and then click Schedule Tasks.

2. Select a task, click Actions, and then Import.

3. Click Browse to find the import file.

4. Select an Import Type:

• Replace —Replaces the definition of a task with the definition in the importfile. This option replaces the task detail with the detail that is in the file that youare importing. It does not affect other tasks in the schedule that are notspecified in the import file.

• Update—Updates partial information for tasks. For example, in the import file,you might have made changes to task instructions, reassigned Owners,Assignees, and Approvers, or removed some attributes and added newattributes. You might also have made the same change to a large number oftasks, for example, adding a new attribute to 100 of 400 tasks. The updateoption is not a full replacement of the task details. Only details for the taskproperties specified in the file are updated. For example, if the import file hasonly a column for a task instructions, the task name, Assignee, attributes, andother properties are not affected.




7. Click Import.

Note:

The system displays a warning that tasks in a schedule that match a taskID in the import file will be modified. If you do not want to overwrite thetask, click Cancel.

Chapter 25Importing and Exporting Tasks

25-15

Exporting Tasks

To export tasks:


2. Select a task, click Actions, and then select Export.

3. Select Export options:

• Select All Tasks or Selected Tasks

• For Format: Select Formatted data (visible columns only) or Unformatteddata for future import

Note:

If you are an Administrator or Power User, you can select the format. Ifyou have User security rights, by default the Format option is Formatteddata (visible columns only), and it cannot be changed.

4. Click Export.

5. Select Open with Microsoft Office Excel (default), or Save File.

6. Click Close.

Editing TasksYou can edit tasks depending on their status and your security rights. For example,you can edit a task description, attributes, or end date.

For an Open task in a Task List, you cannot edit the start date, because the task hasstarted. You can only change the duration or the end date. You also cannot editinstructions, questions, Assignee, or approver, and you cannot add, delete, or editpredecessors. You can reassign the Assignee or approver from the Task Actionsworkflow.

To edit a task:

1. On the Home page, click Tasks, and highlight the task that you want to edit. TheEdit icon is enabled.

2. Click the Edit icon.

3. To edit task attributes:

Select the Attributes tab.

To add an attribute, click the Add icon to display the Add Attribute Assignmentdialog box., and make the following selections:

• Attribute


• Type

This noneditable field is populated by the Attribute.

• Value

Chapter 25Editing Tasks

25-16

Select a value associated with the type of attribute; for example: a numericvalue for Formatted Number attribute, a List for List attribute, multiple lines ofdisplayed text without scrolling for Multi-Line Text, a name of a person, User,or Yes or No for the Yes/No attribute.

• Access

Select the access to the attribute.

4. Click OK.

Adding AttachmentsIf you have an attachment you want to include with your task, such as a Word file,Excel spreadsheet or other document, you can use one of the following methods toattach the document to the task. You can attach multiple items at the same time.When you click OK, the system uploads all the documents that you attached.

To add an attachment to a task:

1. From the Home page, click Tasks, and then click Schedule Tasks.

2. Select a task.

3. Select the Comments tab.

4. Click the Attachment icon to open the Add Attachment dialog box.

5. Select one of the following options to attach the document:

• Browse to the location of the document.

• Drag and drop the document directly from your local directory.

6. Optional: Rename the document.

7. Click OK.

Sorting TasksFrom the Task List, you can sort tasks by ascending or descending order. You cansort by Schedule Name, Status, Owner, Start or End Date, or Duration.

To sort tasks:


2. Hover over a column header until the Sort icons display, and then click SortAscending or Sort Descending.

Searching for TasksYou can use the Task Find feature to find specific tasks. For example, you might enter“load” to find load tasks. You can search using full or partial words. You can scrollthrough the results using the Previous and Next buttons.

To search for a task:

1. On the Home page, click Tasks, and then select Schedule Tasks.

2. Enter a task name in the Search field.

Chapter 25Adding Attachments

25-17

3. Click Previous or Next to find the previous or next task that matches the searchcriteria.

Moving TasksYou can use views to move tasks. For example, you can move tasks in the Gantt view.

To move a task:


2. Select a task.

3. Right-click on the task and drag it to a new location, or cut, copy, and paste thetask.

4. Navigate to the target destination for the task and click OK.

Cutting, Copying, and Pasting TasksYou can use views to cut and copy tasks in templates and schedules. For example,you can copy a task from one schedule or template and paste it into another.

When you paste a task, the Task Details dialog box opens and enables you to modifythe task that you are pasting.

If you paste a task onto a parent task, the pasted task becomes a child of the parenttask. If you paste a task onto a child task, the pasted task becomes a sibling of thechild task.

Note:

Cut, Copy, and Paste features are not available for parent tasks. The Cutfunction is not available for scheduled (open or closed) tasks.

To cut, copy, or paste a task:

1. On the Home page, click Tasks and select a task.

2. Right-click on the task and select an action, or from the main toolbar, click atoolbar button:

• Select Cut to cut the task and store it on the clipboard.

• Select Copy to copy the task and store it on the clipboard.

3. Right-click on the task, then select Paste, or from the main menu toolbar, selectPaste.

The Task Details dialog box opens and enables you to make changes to the taskthat you are pasting.

4. Click OK to complete the paste operation.

The task is inserted and the views and filter views are refreshed to display thepasted task.

Chapter 25Moving Tasks

25-18

Reopening TasksYou can reopen tasks and choose to reestablish the predecessor and successorrelationships.

To reopen a task:

1. On the Home page, click Tasks and then click Schedule Tasks.

2. Select a closed task and double-click it.

3. On the Properties tab, under Actions , select Reopen Task. The Task is noweditable.

4. Add or delete predecessors and then click Save and Close.

Designate relationships:

• Designate predecessor tasks. Choose one:

– If there are predecessors, then you can choose this option: Re-establishpredecessor relationships - Tasks will open in original order.

– Ignore predecessor relationships - All tasks will re-open immediately.

• Designate successor tasks:

a. Select Re-Open Successor Tasks. The successor list is displayed.

b. Select the successor tasks.

5. Click OK to close. The task details dialog box closes and the task reopens basedon your selections. Click OK, otherwise, click Cancel.

Submitting TasksTo submit tasks:


2. Select the tasks that you need to submit.

To multiselect, press Ctrl for random selection or press Shift while you click thefirst and last row in a range.

3. Select Submit Task. A warning is displayed that this will complete the task. ClickYes to proceed.

4. Review any errors, and click OK

Approving or Rejecting TasksTo approve or reject tasks:

1. On the Home page, click Tasks, and select the tasks that you need to submit.

To multiselect, press Ctrl for random selection or press Shift while you click thefirst and last row in a range.

2. Highlight the selected Task, and under Actions, select Set Status, and thenselect Approve or Reject.

Chapter 25Reopening Tasks

25-19

3. Review any errors, and click OK

Managing Task ReassignmentsYou can use the Actions panel to work on multiple tasks simultaneously.

From the Task Actions dialog box, workflow users (Assignees and Approvers) canrequest reassignment of their workflow role for a single task. These requests requireapproval. Administrators and schedule/template Owners can reassign the task usingthe Edit Task dialog box without requiring approval.

To request a reassignment:


2. Click on a task to open the Task Properties.

3. Click the Actions menu and select Request Reassignment.

4. Enter or click Search to find the reassignment.

5. On the Create Reassignment Request, click the Select User button to select ToUser.

6. Under Reassign, and select the tasks to be reassiged:

• Selected Tasks

• Selected and Future Tasks

7. Enter a Justification for the reassignment.

8. Click OK and then Close.

Aborting TasksThe purpose of aborting a task (instead of performing a forced close) is to preventsuccessors from continuing and to keep the process moving:

• When a Finish-to-Start or Finish-Error-to-Start predecessor is aborted, itssuccessors remain as Pending. To keep the process moving, you must edit thesuccessors to remove the aborted predecessor and to start the successors.

• When a Finish-to-Finish or Finish-Error-to-Finish predecessor is aborted, to keepthe process moving, the task owner/schedule owner/administrator must force aclose of the successor.

Deleting TasksYou can delete tasks that you no longer need. To delete a task, you must haveService Administrator or Power User security rights.

In schedules, you can delete only tasks that have a status of Pending. You cannotdelete tasks that have a status of Open or Closed. If you delete a parent task, you canchoose to delete just the parent, or the parent and its children.

You can delete the schedule tasks using the actions menu on the task . (Delete will notappear in the menu when the task is open or completed.)

To delete a task:

Chapter 25Managing Task Reassignments

25-20

1. On the Home page, click Tasks, and select a task.

2. From Actions, and then select Delete.


Chapter 25Deleting Tasks

25-21

26Managing Schedules

A schedule defines a chronologically ordered set of tasks that must be executed for aspecific business process, and is the application of a template into the calendar. Forexample, you can apply the Quarterly template as Q1FY19 for the first Quarter, thenapply the template again as Q2FY19 for the second quarter.

Note:

The maximum number of schedules that you can create, import, or deploy is100,000.

Schedules have a status of Pending, Open, Closed, or Locked. You can change thestatus of a schedule from Pending to Open, or from Open to Closed or Locked.

Note:

After a schedule is set to Open, it cannot be reset to Pending.

After a schedule is set to Locked, its status cannot be changed.

Manually Creating SchedulesTo create a schedule, you must be an Administrator or Power User. A Power User canrun Create Schedule on a template or select New from Manage Schedules. You canmanually define a schedule from the Manage Schedules page, or create a schedulefrom a template. When you create a schedule from a template, all values are inheritedfrom the template definition.

Watch this video to learn more about creating schedules.

Creating Schedules

To manually create a schedule:

1. On the Home page, click the Application icon

26-1



3. Click the Schedules tab on the left.

4. Click New.

5. Enter schedule information on the schedule tabs:

• Setting Schedule Properties

• Adding Instructions to Schedules

• Assigning Schedule Viewers

• Applying Schedule Attributes

• Adding Day Labels

• Working With Schedule Rules

• Viewing Schedule History

Setting Schedule PropertiesThe Properties tab enables you to set the name, description, start and end dates, andowners for schedules. The schedule owner must be an Administrator or Power User.The default owner is the current user. The start and end dates specify the initial daterange for the schedule, however, after the schedule is created, you can add tasks withdates earlier or later and the properties are updated to reflect the earliest and latestdates.

To set schedule properties:

1. Create a new schedule and select the Properties tab:

• Name

• Description


• Start Date—Starting date for the schedule

• End Date—Ending date for the schedule

• Year

• Period

• Day Zero Date—The date to assign as day zero

• For Owner, use the default owner or click Select Owner .

• Status

Note:

The schedule status is initially set to Pending and is display only.

Chapter 26Manually Creating Schedules

26-2

• Source Template

2. To save and close, click OK or click the another tab; all entries are saved.








Adding Instructions to SchedulesYou can specify instructions and supporting documents for a schedule, which are theninherited by all tasks in the schedule.

To add instructions to a schedule:

1. Create a new schedule and select the Instructions tab.

2. In Instructions, enter instructions for the schedule.

3. To add a reference:

a. In the References section, Click Add.

b. From the Type list, select one of these types:

• Local File


• URL

Enter a URL name, then enter the URL, for example: Oracle, http://www.oracle.com, and click OK.

Note:

To add a reference file or URL to multiple schedules at one time:

i. Navigate to the Schedules main page.

ii. You can multi-select (either highlight more than one row orselect more than one using the SHIFT key), and then clickActions, then Add Reference, then File or URL.


26-3

Note:

You can also add one or more attachments by using drag and dropfunctionality available from the Add Attachments dialog box. Youcan rename the attachment in the Name field, if desired. If you dragand drop multiple attachments, you can upload them at one time.

You must access the Add Attachments dialog box to properly dragand drop attachments.

4. To save and close, click OK or click the Viewers tab; all entries are saved.








Assigning Schedule ViewersThe Viewers tab enables you to assign viewer rights for schedules. A schedule canhave multiple viewers, however they must have the product security roles. Viewersreceive read-only access to all tasks in the schedule.

Note:


To assign viewer rights:

1. Create a new schedule and select the Viewers tab.

2. Click Add.

3. To search by users or teams, click the Search Users button, then select Users, orTeams.

4. Enter a user name, or part of the name, then click Search.

5. To identify a user, click Advanced, then enter a User ID, Email address, orDescription.

6. From the Search Results list, select users.

7. For additional details about the user, such as teams and roles, click Details.

8. Click Add or Add All to move users to the Selected list.


26-4

Tip:

To remove users, select users, then click Remove or Remove All.

9. To save and close, click OK or click the Attributes tab; all entries are saved.








Applying Schedule AttributesTo locate schedules in the system, you can apply attributes to the schedule. When youselect an attribute, you can set a value for the attribute based on the attribute type.You can later filter by the attribute value.

For example, you may have a List attribute named Sales Region with the values ofNorth, South, East, and West. The current schedule applies only to the West SalesRegion, so you can add the Sales Region attribute and set it to “West.”


1. Create a new schedule and select the Attributes tab.

2. Click Add.

3. From the Attribute list, select an attribute.

4. For Value, depending on the attribute, select a value for the attribute from a drop-down list, or enter a value.

5. To save and close, click OK or click the Day Labels tab; all entries are saved.

6. Enter schedule information on the Schedule tabs:







Adding Day LabelsYou use business day labels in the business activity for a calendar day. Labels canmark a milestone day or specify the purpose of the day.

To add a day label to a schedule:


26-5

1. Create a new schedule and select the Day Labels tab.

2. Add a day label to a specific date.

3. To save and close, click OK or click the History tab; all entries are saved.








Working With Schedule RulesSchedule rules apply to all tasks in the schedule and thus apply rules to groups oftasks. Rules configured in the Schedule dialog box are copied to new schedule tasks.

Available schedule rules:


Example of conditions that could apply to this rule include: Attributes have specifiedvalues (including calculated attributes).

When conditions are satisfied, the specified approver levels are marked complete, andworkflow progresses to the next approval level, or closes if no additional approvallevels exist.


When conditions are satisfied, the Assignee role is marked complete, and workflowprogresses to the first Approval level, or closes if no Approval levels exist.

Prevent Task ApprovalPrevents approval of a task based on attribute values, or other characteristics.

Prevent Task SubmissionPrevents submission of a task based on attribute values, or other characteristics.

To view schedule rules:



3. Double-click a schedule.





5. To edit a rule, on the Rules tab, click Edit and update:


26-6

• Rule—Select a rule.



• Select Create Filter and populate the conditions section, or select Use SavedFilter, and then select a filter. The filter selected and configured for the ruledetermines the conditions that trigger the rule to apply.


– Use Saved Filter—The Condition section displays a read-only version ofthe conditions associated with the saved file.



• Filter Task—Specify on which task the conditions should be selected:Current Task, Any Predecessor, Specific Task (Provide the Task ID).








Setting Required Task ParametersThe task is in a pending state until the required parameters are filled in. If they are notfilled in before the specified start date, then an email notification is sent to the taskowner. In addition, the task shows up in views under Needs Attention. After therequired parameters are filled in, the task starts.

Opening SchedulesYou open schedules to add, edit, or work on tasks.

To open a schedule:




• Select Actions, and then Open.

• Click the Open icon.

• Right-click and select Open.

Chapter 26Setting Required Task Parameters

26-7

Editing SchedulesYou can edit schedules to change the properties, such as the name or the schedule orthe start and end dates. You cannot change the start date to a date later than the firsttask in the schedule, or the end date to a date earlier than the last task in theschedule. You can make changes to an Open or Pending schedule to modify pendingtasks. You cannot add, change, or delete tasks in a Closed or Locked schedule. Toedit a schedule, you must be the schedule owner or an Administrator.

To edit a schedule:



3. Select a schedule and click Edit.

4. Edit the schedule.

5. Click OK.

Adding Tasks to SchedulesYou can add tasks to a schedule if it is Pending or Open. You cannot add tasks to aClosed or Locked schedule.

Note:

The maximum number of tasks that you can add to a Task Managerschedule is 500,000.

To add a task to a schedule:



3. Open a schedule.

4. Add tasks.

Importing Tasks into SchedulesYou can import tasks, or partial task data, from text files into a schedule with a statusof Pending or Open. For example, if you have a Microsoft Excel spreadsheet with taskdefinitions, you can save the file as a CSV file, then import it into a schedule. You canalso use the Import feature to quickly add many repetitive tasks by editing the fields ina CSV file and importing it, rather than creating individual new tasks.

You cannot import tasks into schedules that have a Closed or Locked status.

Chapter 26Editing Schedules

26-8

Note:

Before you import a file to a schedule using the Update option for a closedtask, remove the Owner, Assignee, Approver, and Start Date and Time fieldsfrom the import file, or an error occurs.

If you import information on an End-User task that has started running, it is reset toOpen with Assignee status, and the answers to questions are cleared.

To import tasks into a schedule:



3. Click Import Tasks.

4. Enter the name of the file to import, or click Browse to find the file.


• Replace— Replaces the definition of a task with the definition in the importfile. This option replaces the task detail with the detail that is in the file that youare importing. It does not affect other tasks in the schedule that are notspecified in the import file.

• Update— Updates partial information for tasks. For example, in the import file,you might have made changes to task instructions, reassigned Owners,Assignees, and Approvers, or removed some attributes and added newattributes. You might also have made the same change to a large number oftasks, for example, adding a new attribute to 100 of 400 tasks. The updateoption is not a full replacement of the task details. Only details for the taskproperties specified in the file are updated. For example, if the import file hasonly a column for a task instructions, the task name, Assignee, attributes, andother properties are not affected.

Note:

The system displays a warning that tasks in the schedule that match atask ID in the import file will be modified. If you do not want to overwritethe task, click Cancel.




8. Click Import.

• If the import is successful, the “Import Success” dialog box is displayed,indicating the schedule name, the name of the file containing the tasks, andthe total number of tasks imported. Click OK.

Chapter 26Importing Tasks into Schedules

26-9

• If errors are found, the import process is not run, and the Import Errors dialogbox displays the errors. View the errors, then click OK to return to ManageSchedules.

Table 26-1 Troubleshooting Import Errors

Error Resolution

Duplicate Task ID Check for duplicate Task IDs. Task IDs mustbe unique within the template or schedule.See Creating Tasks.

Task Name is too long The Task Name can contain a maximum of80 characters. See Setting Task Properties.

Organizational value - "Invalid Value" The Organizational value cannot be blank,contain bullet points or multiple lines.

Updating Tasks in SchedulesYou may need to manually update information on a task that is running, and in thiscase, you can reopen it. When you reopen a task, it is reset to Open with Assigneestatus, and you can edit the information. For example, you can change the instructionsand references, attributes, and questions. If you make changes, previous answers toquestions are cleared.

Reopening a series of tasks does not reestablish the predecessor relationships. Allend-user tasks are reset to Open with Assignee. No tasks are reverted to Pendingstatus.

You can reopen tasks under these conditions:

Table 26-2 Conditions for Reopening Tasks

Task Status End-User

With Assignee/Running You can edit or import data into the Instruction, Attribute,or Question sections. When you save the task, it is resetto the Assignee, and the answers to questions arecleared.

With Approver You can edit or import data in to the Instruction,Attribute, or Question sections. When you save the task,it is reset to the Assignee, and the answers to questionsare cleared.

Closed/Error From Task Details, the task owner can click Reopen toreopen the task and make changes. When you save thetask, it is reset to the Assignee.

To update tasks in a schedule:



3. Open a schedule.

4. Select a task with a Closed or Error status, right-click, and then select View.

The View Task dialog box is displayed.

Chapter 26Updating Tasks in Schedules

26-10

5. Click Reopen.

6. Edit the task.

7. If the system displays a warning that the Assignee must complete the task again,or that the service will be executed again, click Yes to continue or No to cancel.


• For a Closed task, click Close.

• For an Error task, click Save and Close.

Reassigning Users in SchedulesYou may periodically need to reassign users to different schedules. For example, youmay create a schedule and assign a user to certain rights; however, later thatemployee leaves the company and another employee assumes those schedules. Youcan use the Reassign feature in the Schedules dialog box to automatically changeassignments instead of manually searching for, opening, and editing individualschedules. The Reassign feature enables you to quickly find the schedules associatedwith one user and reassign them to another.

You can reassign users for multiple schedules at a time. This can be helpful if yourapplication has a large number of schedules.

To reassign users:



3. Select one for more schedules for which you want to reassign users.

4. Select Actions, and then Reassign User.

5. For Find User, click Find User and enter search criteria for the user that you wantto replace:

a. From the Select User dialog box, enter the first or last name for the user, andclick Search.


6. For Replace with, click Find User and enter search criteria for the user to whomyou want to reassign tasks:

a. From the Select User dialog box, enter the first or last name for the user, andclick Search.


7. Select the Ending Between dates.

8. Select roles for the user that must be reassigned:

• Owner

• Assignee

• Approver

• Viewer

9. Click Reassign.

Chapter 26Reassigning Users in Schedules

26-11

When the process ends, the system displays a “Reassign Users - Success”message that indicates that the user reassignment is complete, and displays theschedule name and total number of user reassignments made.

Setting Schedule StatusYou manage the schedule lifecycle by setting the schedule status. You can set thestatus of a schedule to Open, Closed, or Locked, depending on its current status. Toset schedule status, you must be the schedule owner or Service Administrator.

You can set the status for multiple schedules at a time. This can be helpful if yourapplication has a large number of schedules.

These are the available statuses:

PendingThe schedule is not yet active. This is the default status of the schedule when it iscreated. For a schedule in Pending status, you cannot close or lock the schedule.

OpenThe schedule is open for work to be performed. Tasks in the schedule can be run.

ClosedThe schedule is no longer active but follow-up work may be required. Tasks in theschedule continue to proceed based on their definitions, but you cannot add tasks tothe schedule. Schedule owners or administrators can reopen a Closed schedule,which changes its status to Open.

LockedThe schedule is locked and cannot be modified. You can reopen a locked schedule, ifrequired.

When you create a schedule, it has a status of Pending by default so that you canmake final adjustments to it, and add, edit, or delete tasks.

To run a schedule, you change the status from Pending to Open. When the scheduleis opened, tasks begin to execute according to their definition. Status for tasks thathave met their starting condition are set to Open, and task notifications are sent totheir Assignees.

Note:

If a schedule task start time is reached and authorization has not beenprovided for a system-automated task, the task remains in the Pendingstatus and requires authorization.

When work on the schedule has reached a stage when follow-up work is all that isrequired, you set the status to Closed. You cannot add new tasks to a Closedschedule, however users can continue to work on tasks that are not complete. Youcan reopen a Closed schedule, which changes its status to Open.

When all tasks are completed, you set the status to Locked. You cannot edit a Lockedschedule, but you can set the status back to Open, if required.

Chapter 26Setting Schedule Status

26-12

To set schedule status:



3. Select one or more schedules for which to set status.

4. Select Actions, and then Set Status, or select the Set Status dropdown.

5. Click one of these status options, depending on the current status:

• Open

• Closed

• Locked

Viewing Schedule HistoryThe system maintains a history of schedule actions, which you can view from the EditSchedules dialog box. The History tab displays the components that were updated, themodification type, the old and new values, the user who made the modification, andthe change date. The information is read-only.

To view schedule history:


2. Click Schedules.

3. Select a schedule.

4. Select the History tab and review the schedule history.

• Modification Type—Indicates the type of change: Created, Changed, Added,Removed

• Modified On—Date of the modification

• Modified By—Name of user who modified the schedule

• Old Value

• New Value

5. Click OK.

Validating SchedulesYou can validate schedules with a status of Pending or Open. Validating a schedulechecks for problems with start and end dates, predecessor relationships, parent-childrelationships, and missing task parameters for product integrations. You cannotchange a schedule status from Pending to Open until all validation errors are resolved.To validate schedules, you must the schedule owner or Service Administrator.

To validate a schedule:



3. Select a schedule to validate.

4. Select Actions, and then Validate, or select the Validate icon.

Chapter 26Viewing Schedule History

26-13

• If there are no errors, the system displays a Schedule Valid success message.

• If errors exist, the system displays a list.

Locking SchedulesYou can lock a schedule to prevent users from making further changes.

To lock a schedule:



3. From the list of schedules, select a schedule.

4. Select Actions, and then Set Status, or from the Set Status dropdown, selectLocked.

5. Click Close.

6. Optional: If you need to reopen the Locked schedule, select Actions, and thenSet Status, or from the Set Status dropdown, select Open.

Viewing SchedulesIn Schedules, you can specify which columns to display for the list of schedules, orshow all. You can also reorder columns, sort columns by ascending or descendingorder, or change the column widths.

To display columns:









Searching for SchedulesYou can use Schedules to quickly find schedules. You can enter full or partial nameson which to search. You can search on additional fields such as Start Date and Owner.

To search for a schedule:



Chapter 26Locking Schedules

26-14

3. Click the greater than > sign to expand the Search box.

4. Enter full or partial search criteria for the schedule.


Tip:


6. Click Search.

Tip:

To reset the list to display all schedules, click Reset.

Deleting SchedulesYou can delete a schedule that you no longer need. To delete a schedule, you mustbe the schedule owner or Service Administrator. Deleting a schedule removes it andall references to it from the system.

To delete a schedule:



3. From Schedules, select the schedule that you want to delete.

4. Click Delete.

The system displays a warning that if you delete a schedule, it will alsopermanently delete all tasks within the schedule, and the only way to recover isfrom a backup.

5. To delete the schedule, click Yes.

Chapter 26Deleting Schedules

26-15

27Managing Task Manager Integrations

You can enable Task Manager tasks to include integrations with external applications.

An Integration requires an execution URL for user tasks and an optional set ofparameters. The execution URL launches the external program, and the parameterspass information required for the task to the external program. For example, theApprove Journals Integration contains parameters such as the Point of Viewdimension values for the journal.

To manage Task Manager Integrations, you must have the Service Administrator role.

When you create an Integration, you select one of these task types:

End User

Users must perform and validate the task. For example, the task may be a generictask such as submitting data, or it may require product integration to facilitate orvalidate its completion.

Process Automation

These integrations are automatically executed in external applications when their Startdate and time are reached, and their predecessor tasks are completed, for example,an overnight feed from a General Ledger. These tasks are often executed afterworking hours. They require limited user interaction and do not have Assignees.

Event Monitoring

These are based on events that occur in external applications, for example ApproveJournals.

Task Manager provides these pre-built Integrations:

• Cloud Integrations: End User and Process Automation integrations for EPM CloudConnections. See Task Manager Integrations with EPM Cloud Services.

• Cloud Integrations: Oracle Fusion integrations. See Task Manager Integrationswith Cloud and On-Premises Applications.

• On-Premises End User and Event Monitoring Integrations. See Task ManagerIntegrations with Cloud and On-Premises Applications.

• On-Premises Oracle E-Business Suite General Ledger, Accounts Payable, andAccounts Receivable Integrations. See Task Manager Integrations with Cloud andOn-Premises Applications.

If you require any other Integrations for Cloud or On Premises, you can create CustomIntegrations. See Creating Custom Task Manager Integrations.

Creating IntegrationsWhen you create Integrations, you select End-User as the Execution type. Users canthen create task types based on the defined Integrations, or validate the Integrations.

27-1

To create an Integration:


2. Click the Integrations tab on the left.

3. Click New.

Add information to the following sections:

• Setting Integration Properties

• Setting Integration Parameters

Setting Integration PropertiesYou can set properties for the Integration such as the associated application and End-User tasks.

For an End-User task, you can select the single sign-on (SSO) Parameter option toenable users to access an external web application without being prompted forauthentication. You can use an SSO parameter for an external application if thatapplication is integrated with the Oracle EPM System SSO framework.

To set Integration properties:

1. Select the Integration to edit.

2. In Properties, for Name, enter a name for the Integration.

3. Enter a Code, for example, HFM_CONS for the Hyperion Financial ManagementConsolidate integration task.

The code is used to execute the Integration and to map updates to an Integration.

4. Optional: In Description, enter a description for the integration task.

5. In Connection, select an application to which the task belongs.

Note:

You can maintain the list of applications from the Manage Connectionsicon in the Manage Connections dialog box.

6. For Execution Type, select End User Task and select options:

• End User Endpoint: To enter parameters for an End-User task, the End UserEndpoint should contain those parameters in these formats:

$Parameter Type Code$, for example $COLORS$. The system replaces theparameter tokens in the End User Endpoint with the information you specifiedfor the task parameters.

• Optional: Show in-line: Select whether to display the URL in line within theTask Actions dialog.

• Optional: SSO Parameter: Specify the name of the SSO parameter for yourapplication to include when executing the End-User task URL to the externalapplication. If you do not specify an SSO parameter, the system uses the EndUser URL.

Chapter 27Creating Integrations

27-2

7. Optional: Click Parameters.

Setting Integration ParametersTask Manager Integration parameters enable the application to pass information to theend point to control how the end point should perform its action. For example, whenyou run a consolidation, your program can pass which application to run theconsolidation against, and the dimension selections for the consolidation. You set theparameter values defined in the Integrations in the task or Task Type using theintegration.

Each parameter definition requires a name, description, unique code, type, andwhether a value is required. The parameter code is the token that replaces theparameter in the execution URL for user tasks, or the parameter name that is passedto the execution web service for system-automated integrations. Required values musthave a value for all tasks in a schedule before the schedule can be set to Open.

The Parameter Type controls the parameter value and how the user enters the valuein the task field. Supported parameter types:

To set Integration parameters:

1. In the Integrations dialog box, click Parameters.

2. Click New.

3. Enter a name for the parameter.

4. Enter a parameter code.

5. Enter a parameter tooltip.

6. From the Parameter Type list, select a type, and enter additional information forthe parameter:

• Check box: Boolean value

• Date: Date value

• Integer: Numeric value in whole numbers

• Number: Numeric value in whole numbers or fractions

• Options Group: Check box for a predefined set of values

• Static List: Predefined set of text values

• Task Information: Task information, for example, Assignee, duration, startand end dates

• Text: Free-form text value.

• EPM Artifact: Name of the artifact, such as the form or report

7. If the parameter requires a value, select Required.

8. Click OK to save the parameter.

9. Click Save and Close to save the Integration.

Editing IntegrationsYou can't edit the pre-built Integrations provided by default by the system. You canonly edit custom-built integrations that you created.

Chapter 27Editing Integrations

27-3

For an End-User type, you can edit the endpoint, change the point of view, or changethe list of values.

To edit an Integration:



3. Select an Integration, and click Edit.

4. Edit the Integration.


Validating IntegrationsYou can test and validate Task Manager Integration definitions from the Integrationsmodule before you create and execute tasks. You can provide parameter values forthe parameter definition, and then test those parameters. For End-User tasks, thesystem displays the end result URL web page.

The Validation results can contain any or all sections:

• Security Settings—Security settings for this Integration; includes the Requestand Response Security Policy and Keystore Alias specified in the application, andthe End-User URL and SSO Parameter of the Integration. These settings are setin the application of the Integration.

• Application Tokens—Lists the application-level tokens that exist for theIntegration. If there are no application-level tokens, this section is not displayed.

• Registry Settings—Displays the values from the installation registry, for example:

– Web Application settings, displayed only if the Web App setting is defined inthe application

– Web Service application settings, displayed only if the web service applicationsetting is defined in the application

• Parameters—This section is identical to the Parameters section for tasks and taskdetails, and enables you to provide values for Integration parameters. TaskInformation parameters are also displayed and editable, and parameter errors aredisplayed.

• Results—Displays the current End-User Endpoint URL with the tokens that youspecified. Click Refresh to update the URL.

To validate an Integration:



3. Select an Integration.

4. Click Validate.

End-User Integration Type: The system displays the security settings,Application Tokens if applicable, parameters, and results. Click Validate to openthe URL in a browser window.

Chapter 27Validating Integrations

27-4

Tip:

If you need to cancel the process, you can click Cancel Validation whenthe validation is in the Invoking or Waiting for Response stage.

5. When you finish running validations, click Close.

Deleting IntegrationsYou can delete Integrations that you no longer need. However, you can't delete pre-built Integrations provided by default and you can't delete an Integration while it isassociated with a Task Type.

To delete an Integration:



3. Select an Integration to delete.

4. Click Delete.


Managing ConnectionsIntegrations are assigned connections for the external products to which they link.From the Manage Connections module, you can maintain a list of connectionsassociated with the Integrations. You can search on and sort the list by connection.

• Adding Connections

• Editing Connections

• Deleting Connections

Adding ConnectionsYou can add connections to associate with an Integration Type. You can also specifythe security policy to use for an Integration Type.

In addition, you can specify application-level tokens and values for all IntegrationTypes in an application. When you specify an application-level token in an end-userURL or web service WSDL, the system replaces the token with the value defined forthat token in the application. For example, you can specify tokens with values forserver and port, and the system automatically applies those values to the IntegrationTypes in the application.

To add a connection:



3. Click Manage Connections.

4. Click New.

Chapter 27Deleting Integrations

27-5

5. Enter the connection.

6. Optional: Enter additional application properties.

7. Optional: To add an application-level token, in the Application Tokens table, clickAdd. Enter a token name and optionally a token value, and then click OK.

Tip:

To remove a token, click Delete.

Editing ConnectionsYou can edit the name of a connection, the security information, and application-leveltokens.

Note:

You cannot add or modify application tokens for seeded applications. Youcan only edit the token values.

You also use the Edit Connections dialog to enable pre-built Integrations. After youenable the Integration and fill in the parameters, you can then create tasks using TaskTypes for the enabled Integrations.

To edit a connection:




4. Select a connection, and click Edit.

5. To enable a pre-built Integration, select the connection, select Enabled, and fill inthe parameters.

You can enable or disable a connection at any time.

6. Edit the settings or tokens as needed, and click OK.

Deleting ConnectionsYou can delete connections that you no longer need for Integrations. You cannotdelete a connection while it is associated with an Integration Type. You must modifythe properties for each Integration Type that references the connection before you candelete the connection.

Note:

You cannot delete seeded Integration connections.

Chapter 27Managing Connections

27-6

To delete a connection:




4. Select a connection, and click Delete.

Viewing IntegrationsYou can view the properties and parameters of imported Integrations. You can specifywhich columns to display, or show all. You can also reorder columns, sort columns byascending or descending order, or change the column widths.

To display columns:



3. Select View, then Columns, and then select an option:

• To display all columns, select Show All.

• To display specific columns, select or deselect the column names.

To reorder columns:

1. Click Integrations.

2. Select View, and then Reorder Columns.

3. Select columns and use the Up and Down arrows to change the order.

To sort columns:

1. Click Integrations.

2. Hover over a column header until the Sort icons display, then click SortAscending or Sort Descending.

To change column widths:

1. Hover over the column header dividers until the arrows display.

2. Drag the columns to the desired width.

Searching for IntegrationsYou can use the Integrations dialog box to find Integrations. You can enter full orpartial names on which to search.

To search for Integrations:



3. Enter full or partial search criteria for the Integration.


Chapter 27Viewing Integrations

27-7

Tip:


5. Click Search.

Tip:

To reset the list to display all Integrations, click Reset.

Creating Custom Task Manager IntegrationsIn Task Manager, you can create and manage custom Process Automation or EventMonitoring integrations with external applications. An EPM Adapter enables you tocreate connections and integration flows in Integration Cloud Service using OracleEPM Cloud and other cloud and on-premises applications.

The following diagram shows the user and system flow for creating customintegrations:

See these topics:

• Creating Custom Process Automation Integrations

• Creating Custom Event Monitoring Integrations

Creating Custom Process Automation IntegrationsIn Task Manager, you can create custom process automation integrations withexternal applications. In a Process Automation integration, a task is automaticallyexecuted in an external application when its start date and time are reached, andwhen any predecessor tasks are completed, for example, an overnight feed from aGeneral Ledger.

Chapter 27Creating Custom Task Manager Integrations

27-8

Make sure you have the prerequisites and follow these steps to set up an integrationbetween Task Manager and an external application.

For an overview of the custom integrations flow, see Creating Custom Task ManagerIntegrations.

Prerequisites

To integrate Task Manager with an external application, you need:

• A subscription to Oracle Integration Cloud Service, to integrate with on-premisesand non-EPM Cloud services.

Note:

You need one Integration Cloud instance per Oracle EPM cloudinstance.

• The external application set up.

1. Subscribe to Oracle Integration Cloud/Oracle Autonomous Integration Cloud.See Integration Cloud Service Documentation for detailed information.

2. Install Integration Cloud Agent in your application environment to communicatewith your Oracle EPM cloud instance.. For details on setting up Integration CloudAgent, see Managing Agent Groups.

Note:

If the on-premises application services are deployed in an environmentset up in a demilitarized zone (DMZ) configuration so that these servicesare publicly accessible through the Internet, you do not need to installIntegration Cloud Agent.

Creating a Connection in Task Manager


2. Click the Integrations tab on the left, and then click Manage Connections.

3. Click New.

4. For Connection enter a name for the connection.

5. Select Enabled to enable the connection.

6. Select Cloud if the external application is a Cloud service.

7. Click OK to save the connection.

Setting Up the Integration in Task Manager

1. On the Home page, click Applications, and then click Task Manager.

2. Click the Integrations tab on the left, and then click New.

3. On the Properties tab, specify the required information:

a. For Name, enter a name for the Integration.


27-9

https://docs.oracle.com/en/cloud/paas/integration-cloud/index.html

https://docs.oracle.com/en/cloud/paas/integration-cloud/integrations-user/managing-agent-groups-and-connectivity-agent.html

b. For Code, enter an Integration Code for the integration task.

The code is used to execute the Integration and to map updates to anIntegration from a file import.

c. Optional: In Description, enter a description for the integration task.

d. For Connection, select an application to which the task belongs.

You can maintain the list of applications from the Manage Connections icon inthe Manage Connections dialog box.

e. For Execution Type, select Process Automation.

4. On the Parameters tab, specify the required information:

a. For Name, enter a name for the parameter.

b. For Parameter Code, enter a parameter code.

c. Optional: Enter a parameter tooltip.

d. From the Parameter Type list, select a type, and enter additional informationfor the parameter:







• Task Information: Task information, for example, Assignee, duration,start and end dates

• Text: Free-form text value.

• EPM Artifact: Name of the artifact, such as the form or report.

e. If the parameter requires a value, select Required.

f. Click OK to save the parameter.

g. Click Save and Close to save the Integration.

Creating a Task Type for the Integration



3. Click New.

4. On the Properties tab, specify a Task Type Name and Task Type ID. See Creating Task Types.

5. For Integration, click Search, select the Integration, and then click OK.

6. On the Parameters tab, set the Task Type parameters.

Setting Up a Connection in Task Manager




27-10

3. Click Manage Connections, and then from Actions, select Integration CloudConnection.

4. Specify the Integration Cloud connection URL and credentials and click Validate.After validation is successful, click Save. This saves the server and credentials ofthe connection.

Creating a Connection and Integration in Integration Cloud

1. Log in to Integration Cloud.

2. On the left, click Connections, and then click Create.

3. From Create Connection - Select Adapter, search for "Oracle EnterprisePerformance Management Cloud", and then click Select.

4. In Create New Connection, enter a Name and Identifier, and click Create.

5. Under Connection Properties, click Configure Connectivity.

6. Select the Service Type, enter the Connection URL, and click OK.

7. Click Configure Security.

8. In Credentials, for Security Policy, leave the default of Basic Authentication.

9. Enter the User name and Password, confirm the Password, and then click OK.

10. From the EPM Connection page, click Test, and then click Save.

11. From Integrations, click Create.

12. Enter a name and description for the integration.

13. Click Create.

14. Navigate to Connections.

15. From the list of Triggers, select the Oracle Enterprise PerformanceManagement Adapter and drag it to the diagram as the Start trigger.

16. From the list of Triggers, drag and drop the external application connection thattriggers the event.

17. From Operation Selection, select the operation for the external application.

18. Navigate to Mapping, and complete the mapping between the Source parameterand Target parameter.

19. From the list of Invokes, drag and drop the service connection and select UpdateTask Status Operation.

20. Edit and complete mapping the parameters.

21. Navigate to Tracking, and specify the Business Identifier for Tracking, forexample taskID, integrationCode, and parameters.

22. From the list of Integrations, select and activate the integration.

Completing the Integration Setup in Task Manager

Use these steps to complete the Integration setup in Task Manager.


2. Click the Integrations tab on the left and verify that the new Integration isdisplayed on the Integrations list.


27-11

3. In Task Manager, select Schedules, and create a new Schedule in Pending state.See Manually Creating Schedules.

4. Create the process automation task and add it to the schedule. See CreatingTasks.

5. From Schedules, select and open the schedule.

Creating Custom Event Monitoring IntegrationsIn Task Manager, you can create an Event Monitoring integration for an externalapplication. The Event Monitoring integration is triggered when an external eventoccurs in another Cloud service or on-premises application. An example of an EventMonitoring integration is a trigger from Oracle E-Business Suite - General Ledgerwhen a period, for example, January 2018, is closed.

Make sure you have the prerequisites and follow these steps to set up an integrationbetween Task Manager and an external application.

For an overview of the custom integrations flow, see Creating Custom Task ManagerIntegrations.

Prerequisites

To integrate Task Manager with an external application, you need:

• A subscription to Oracle Integration Cloud Service, to integrate with on-premisesand non-EPM Cloud services.

Note:

You need one Integration Cloud instance per Oracle EPM cloudinstance.

• The external application set up.

1. Subscribe to Oracle Integration Cloud / Oracle Autonomous Integration Cloud. See Integration Cloud Service Documentation for detailed information.

2. Install Integration Cloud Agent in your application environment to communicatewith your Oracle EPM cloud instance. For details on setting up Integration CloudAgent, see Managing Agent Groups.

Note:

If the on-premises application services are deployed in an environmentset up in a demilitarized zone (DMZ) configuration so that these servicesare publicly accessible through the Internet, you do not need to installIntegration Cloud Agent.

Setting Up the Integration in Task Manager


2. Click the Integrations tab on the left, and then click New.


27-12


https://docs.oracle.com/en/cloud/paas/integration-cloud/integrations-user/managing-agent-groups-and-connectivity-agent.html

3. On the Properties tab, specify the required information:

a. For Name, enter a name for the Integration.

b. For Code, enter an Integration Code for the integration task.

The code is used to execute the Integration and to map updates to anIntegration from a file import.

c. Optional: In Description, enter a description for the integration task.

d. For Connection, select an application to which the task belongs.

You can maintain the list of applications from the Manage Connections icon inthe Manage Connections dialog box.

e. For Execution Type, select Event Monitoring.

f. For Event Name, enter a name for the event.

4. On the Parameters tab, click New and specify the required information:

a. For Name, enter a name for the parameter.

b. For Parameter Code, enter a parameter code.

c. Optional: Enter a parameter tooltip.

d. From the Parameter Type list, select a type, and enter additional informationfor the parameter:







• Task Information: Task information, for example, Assignee, duration,start and end dates

• Text: Free-form text value

• EPM Artifact: Name of the artifact, such as the form or report

e. If the parameter requires a value, select Required.

f. Click OK to save the parameter.

g. Click Save and Close to save the Integration.

Setting Up the Integration in Integration Cloud

To set up the integration in Integration Cloud:

1. Log in to Integration Cloud Services.

2. Navigate to Connections.

3. From the list of Triggers, select the connection that triggers the event.

4. From the list of Triggers, select the service connection.

5. Navigate to Mapping, and complete the mapping between the Source parameterand Target parameter.


27-13

6. Navigate to Tracking, and specify the Business Identifier for Tracking.

7. From the list of Integrations, select and activate the integration.

Completing the Integration Setup in Task Manager

Use these steps to complete the Integration setup in Task Manager.


2. Click the Integrations tab on the left, and verify that the new Integration isdisplayed.

3. In Task Manager, click Schedules, and create a new Schedule in Pending state.See Manually Creating Schedules.

4. Create the event monitoring task and add it to the schedule. See Creating Tasks.

5. From Schedules, select and open the schedule.

6. Trigger the action that generates the event in the external application (for example,EBS).

7. Wait for the task to be completed.

8. Optional: To monitor the status of the Integration in Integration Cloud Services,log in to Integration Cloud and navigate to Monitoring.


27-14

28Using Task Manager and SupplementalData Manager Reports

Related Topics

• Generating Custom Reports for Task Manager and Supplemental Data Manager

• Creating a Task Manager Query

• Creating a Supplemental Data Query

• Creating a Template

• Setting Up a Report Group

• Creating a Report

• Generating the Report

• Using Task Manager Report Binders

• Generating Report Binders

• Viewing Report Binders

Generating Custom Reports for Task Manager andSupplemental Data Manager

You can create reports for Task Manager and Supplemental Data Manager. Thereports can be generated in PDF, CSV, HTML, XLS, or XLSX format.

Note:

Task Manager provides sample reports to assist you in getting started. Youcan use them as templates and can duplicate them as needed, then makemodifications or extend access to users. To duplicate a report, select thereport, then select Duplicate from the ellipsis button . You can then editthe newly created report.

You can also create custom reports. Building custom reports involves four steps andcan only be performed by a Service Administrator:

• Create a Task Manager or Supplemental Data Query from the New button of theQueries tab. See Creating a Task Manager Query or Creating a SupplementalData Query.

• Create a template. See Creating a Template.

• Set up a report group. See Setting Up a Report Group.

• Set up the report. See Creating a Report.

28-1

To build custom reports, you create a query whose definition can then be exported asan XML file. Import the XML file into Word and use it to create a template document,which must be in RTF format. Then you can set up a report group to group individualreports. Finally, generate the report, which uses both the query and the template youcreated and can be set with a default output of CSV, PDF, HTML, XLS or XLSX.

After you have built a custom report, the Service Administrator or other users whohave been granted access can generate the report. See Generating the Report.

Creating a Task Manager QueryCreating a query is the first step in creating a custom report.

To create queries:

1. From the Home Page, select Application, and then select the report (for example,Non-Consolidation Reports).

2. From the Queries tab, select New.

3. Select Task Manager Query.

4. On the New Query screen, enter a Name and an optional Description.

5. From Type, select an option:

• Parameter Query

A Parameter Query type is used to present a list of options that you canspecify for this parameter's value. Parameter Query allows you to present alist of options used when filling in a parameter's value for a Report Query,where the list of options is not a simple Attribute already defined, but is insteada complex query that you need to define.

This parameter query example provides a list of all .Task Manager periods:

SELECT PERIOD_ID, PERIOD_NAME FROM FCC_PERIODSWHERE APP_ID=1

• Report Query for Task Manager and Supplemental Data Reports

Select the records to be included in the report. You can apply a security filter,so users see only the data that they are authorized to see based on their rolesand the reports to which they are assigned. To apply a Security Filter to areport query, add the following syntax to the end of the query WHERECLAUSE statement.

$FCC_SECURITY_CLAUSE$

Note:

When using $FCC_SECURITY_CLAUSE$ in the query, the FCC_TASKSmust be aliased to TaskEO.

Chapter 28Generating Custom Reports for Task Manager and Supplemental Data Manager

28-2

Note:

Because many predefined queries included with Task Manager havethe Security Filter applied, you can use them as examples whenbuilding your own.

For example, the following Report Query specifies scheduled tasks to displayTask Code, Name, Assignee and Schedule for all High Priority tasks in theselected schedule.

SELECT TaskEO.TASK_CODEAS "$TASK_CODE$" ,

TaskEO.TASK_NAMEAS "$NAME$" ,

((SELECT CASE WHEN FIRST_NAME IS NULL AND LAST_NAME IS NULL THENUSER_LOGIN ELSE FIRST_NAME||' '||LAST_NAME END FROM FCM_USERS WHEREUSER_ID = (coalesce(AssigneeEO.ACTIVE_USER_ID,AssigneeEO.USER_ID))))AS "$ASSIGNEE$" ,

DeploymentEO.DEPLOYMENT_NAMEAS "$SCHEDULE$"

FROM FCC_TASKS TaskEO

LEFT OUTER JOIN FCC_ACCESS AssigneeEO ON (TaskEO.TASK_ID =AssigneeEO.SOURCE_ID AND AssigneeEO.ACCESS_TYPE = 'AS')

LEFT OUTER JOIN FCC_DEPLOYMENTS DeploymentEO ON (TaskEO.SOURCE_ID =DeploymentEO.DEPLOYMENT_ID)

WHERE (TaskEO.SOURCE_TYPE = 'DEPLOYMENT')

AND ((((TaskEO.PRIORITY=3 )

AND (TaskEO.SOURCE_ID=~SCHEDULE~ ))))

6. Click Generate Query to build the query from the New Query dialog. The dialogassists you in creating a query against the database by allowing you to select anyexisting attribute in the product to be queried and/or filtered against. The systemthen generates the SQL to match the specified attributes and filters, at which timeyou can modify and enhance it.

a. On the Select Type screen, select options:

• From Query, select Template Tasks or Schedule Tasks.

• Optional: Select the Apply Security checkbox to automatically apply theuser security filter to the generated query. This applies the Security tokento the query, to be filled in with the correct SQL when the report isgenerated.

b. Click Next.


28-3

7. From Select Columns, select the columns to display in the query, and then clickNext.

8. From Select Filters, click Create Condition or Create Condition Group andselect the conditions to create the filters to create the query.


28-4

9. Select OK.

10. Optional: If you want to use the report in the future, click Generate Sample XML.

11. Click Save.

12. To test the query for errors, click Validate from the New Query dialog. The querydisplays in the Queries tab.

Note:

You can easily delete a query, or duplicate a query using the Actionmenu.

Modifying A Query

A system administrator can edit a Task Manager query or Supplemental Data query.

1. From the Home Page, select Applications, then Reports.

2. In Reports, select Queries if is not already selected, and then Edit from nextto the query you are editing.

Note:

If it is locked, ask the System Administrator to unlock.


• Task Manager Query

• Supplemental Data Query

4. In Edit Query, edit the information as needed.


28-5

5. After you are done with your changes, click Save and Close.

Creating a Supplemental Data QueryCreating a query is the first step in creating a custom report.

To create queries:

1. From the Home Page, select Application, and then select the report (for example,Non-Consolidation Reports).

2. From the Queries tab, select New.

3. Select Supplemental Data Query.

4. On the New Query screen, enter a Name and an optional Description.

5. From Type, select an option:

• Parameter Query

A Parameter Query type is used to present a list of options that you canspecify for this parameter's value. Parameter Query allows you to present alist of options used when filling in a parameter's value for a Report Query,where the list of options is not a simple Attribute already defined, but is insteada complex query that you need to define.

This parameter query example provides a list of all Supplemental DataManager Query periods:

SELECT PERIOD_ID, PERIOD_NAME FROM FCC_PERIODSWHERE APP_ID=1

• Report Query for Task Manager and Supplemental Data Manager Reports

Select the records to be included in the report. You can apply a security filter,so users see only the data that they are authorized to see based on their rolesand the reports to which they are assigned. To apply a Security Filter to areport query, add the following syntax to the end of the query WHERECLAUSE statement.

$FCC_SECURITY_CLAUSE$

Note:

Because many predefined queries included with Task Manager havethe Security Filter applied, you can use them as examples whenbuilding your own.

For example, the following Report Query specifies scheduled tasks to displayTask Code, Name, Assignee and Schedule for all High Priority tasks in theselected schedule.

SELECT TaskEO.TASK_CODEAS "$TASK_CODE$" ,

TaskEO.TASK_NAMEAS "$NAME$" ,

((SELECT CASE WHEN FIRST_NAME IS NULL AND LAST_NAME IS NULL THENUSER_LOGIN ELSE FIRST_NAME||' '||LAST_NAME END FROM FCM_USERS WHERE


28-6

USER_ID = (coalesce(AssigneeEO.ACTIVE_USER_ID,AssigneeEO.USER_ID))))AS "$ASSIGNEE$" ,

DeploymentEO.DEPLOYMENT_NAMEAS "$SCHEDULE$"

FROM FCC_TASKS TaskEO

LEFT OUTER JOIN FCC_ACCESS AssigneeEO ON (TaskEO.TASK_ID =AssigneeEO.SOURCE_ID AND AssigneeEO.ACCESS_TYPE = 'AS')

LEFT OUTER JOIN FCC_DEPLOYMENTS DeploymentEO ON (TaskEO.SOURCE_ID =DeploymentEO.DEPLOYMENT_ID)

WHERE (TaskEO.SOURCE_TYPE = 'DEPLOYMENT')

AND ((((TaskEO.PRIORITY=3 )

AND (TaskEO.SOURCE_ID=~SCHEDULE~ ))))

6. Click Generate Query to build the query from the New Query dialog. The dialogassists you in creating a query against the database by allowing you to select anyexisting attribute in the product to be queried and/or filtered against. The systemthen generates the SQL to match the specified attributes and filters, at which timeyou can modify and enhance it.

a. On the Select Type screen, select the following:

• From Query, select Workflow.

• Optional: Select the Apply Security checkbox to automatically apply theuser security filter to the generated query. This applies the Security tokento the query, to be filled in with the correct SQL when the report isgenerated.

b. Click Next.

7. From Select Columns, select the columns to display in query, and then clickNext.


28-7

8. From Select Filters, click Create Condition or Create Condition Group andselect the conditions to create the filters to create the query.

9. Select OK.

10. Optional: If you want to use the report in the future, click Generate Sample XML.

11. Click Save.

12. To test the query for errors, click Validate from the New Query dialog. The querydisplays in the Queries tab.


28-8

Note:

You can easily delete a query, or duplicate a query using the Actionmenu.

Modifying A Query

A system administrator can edit a Supplemental Data Query.

1. From the Home Page, select Applications, then Non-Consolidation Reports.

2. From the Queries tab, select Edit from next to the query you are editing.

Note:

If it is locked, ask the System Administrator to unlock.


• Task Manager Query

• Supplemental Data Query

4. In Edit Query, edit the information as needed.

5. After you are done with your changes, click Save and Close.

Creating a TemplateCreating report templates is the second step in generating reports. To use a reportformat in the future, creating a template saves time. Report templates are created inMicrosoft Word with Oracle Business Intelligence Publisher Desktop client installed.Template creation also requires that you already generated the Sample XML duringquery creation. For additional BI Publisher help on templates, see Help on templates.To download the correct version of BI Publisher Desktop Client from the BI Publisherdownload page select the following:

1. From the downloads tab, select Accept License Agreement option.

2. Download BI Publisher version. The correct version is 11.1.1.7.

3. Select Save File to a location of your choice.

Note:

Make sure that a supported release of BI Publisher Desktop Client isinstalled. For more information on how to install, see Installing andConfiguring Oracle Business Intelligence.

To create a report template:

1. Open Microsoft Word with a new document.


28-9

https://docs.oracle.com/middleware/12213/bip/BIPRD/GUID-43369E75-4A64-4C70-956D-AB0DB496CA7A.htm#BIPRD2620

http://www.oracle.com/technetwork/middleware/bi-publisher/downloads/index.html

http://www.oracle.com/technetwork/middleware/bi-publisher/downloads/index.html

http://download.oracle.com/otn/nt/bi/111170/BIPublisherDesktop32.exe

https://docs.oracle.com/middleware/12213/lcm/BIEIG/toc.htm

https://docs.oracle.com/middleware/12213/lcm/BIEIG/toc.htm

2. Select the BI Publisher tab, then the Sample XML folder above Load Data.

3. Locate the SampleQuery.xml that was generated when you created the query andclick Open.A message displays, "Data Loaded Successfully". Click OK.

4. Select Insert, and then Table Wizard.

5. Select Table and click Next.

6. Select the default data set and click Next.

7. Select the desired fields to show in the report and click Next.

8. Select the Group By, then select the fields to group by, and then click Next.

9. Select the Sort By, then select the fields to sort by, and then click Finish.

10. Save the template as an RTF file; for example: MonthlyReport.rtf.

Setting Up a Report GroupCreating report groups is the third step in generating custom reports. A report groupenables you to group individual reports together for Task Manager and SupplementalData Manager so that you can organize reports in folder structures.

Note:

Nested Report Groups are not supported.

After a report group has been created, you can modify it if necessary. You canduplicate a report group but its name must be unique. You can also delete a reportgroup, however, deleting a report group deletes all reports associated with that group.

To create report groups:

1. From the Home Page, click Application, and then select Non-ConsolidationReports.

2. From the Report Groups tab, click New.

3. In the New Report Group, enter:

• Name

Enter a group name for the group of reports.

• Description

• Display to User

Select Display to User if you want this report group displayed to the user.

The Display to User option enables report writers to have a group of reportshidden while they are working on them.

4. On the Reports tab, reorder or edit reports that have been added to the reportgroup using the Move icons

.


28-10


Creating a ReportCreating report definitions is the fourth step in generating reports. User can createreports from the queries and assign them to groups.

To create report definitions:

1. From the Home Page, click Application, and then select Non-ConsolidationReports.

2. Select Reports, then New, and then Task Manager Report.

3. In New Report, enter:

• Name

• Description

• Query

Select a query.

• Template

Click Browse and then browse to a report template. You can upload anysupported Oracle Business Intelligence Publisher template format. See Creating a Template.


28-11

• Report Group

Select the Group Name for the report from the drop-down menu.

• Display to User

Select if you want the report displayed to a user.

• Output Format

Select a report output format that BI Publisher supports; for example: CSV,PDF, HTML, XLS or XLSX.

Note:

XLSX is not supported for graphs. HTML and XLS are not supportedfor graphs and charts.

4. To complete the report definition, you must set the parameters and access:

a. For Parameters, select the Parameters tab.

b. Select Actions, and then Add.

c. Select the parameter values.

d. Select the Access tab.

e. Select Actions, and then Add.

f. Select the Application Module and the Role from the drop-down menus.

Note:

The report must be granted access to at least one applicationmodule for the report to display in the corresponding Reports tab.

5. Select Save and Close.

Generating the ReportGenerating reports is the final step in the process. After a Service Administrator hasbuilt the custom report, any user granted access can generate the report.

To generate reports:

1. From the Home Page, click Reports.

2. Select a tab:

• Task Manager Reports

• Supplemental Data Manager

3. Select the reports you want to generate and then select the format: CSV, XLS,XLSX, HTML or PDF.


28-12

Note:

XLSX is not supported for graphs. HTML and XLS are not supported forgraphs and charts.

4. Click Generate.

5. Enter the Name, Schedule, and Period from the drop down menus.

6. Click Generate.The system displays a "Completed Successfully" status message.

7. Select Open with or Save File to save the ZIP file.

Using Task Manager Report BindersTask Manager report binders enable you to create a history of all activities thatoccurred as part of a schedule, for example, the Corporate Q1 Close. You use filters tospecify the schedule, tasks to include, and which task information to include.

Information for all tasks that meet the binder filter criteria are output in HTML to a ZIPfile. They contain HTML and other files. When you extract the ZIP file, a directorystructure is formed, in which you can access the HTML file to view the report binder.Because the report is self-contained in one file, it can easily be copied, printed, oremailed for internal or external reviews.

Generating Report BindersThe Generate Report Binder dialog box enables you to specify the parameters neededto create a report. When you open a schedule in a view and run Generate ReportBinder, the report binder is applied to the current view and incorporates only the taskswithin the current filtered view.

The report binder is generated and returned through the browser as a document.When you run Generate Report Binder, you have the option to open it immediately orto save it to disk as a ZIP file.

You can generate report binders for multiple schedules at a time. This can be helpful ifyour application has a large number of schedules.

To generate a report binder:

1. From the list of Schedules, select one or more schedules for which to generate areport binder.

2. From the Actions dropdown, select Generate Report Binder.

3. In Report Binder Name, enter a name.

4. In Description, enter a binder description.

For Schedule Name, the system automatically displays the name of the currentschedule.

5. From Optional Components, select the task components that you want to displayin the report:

• Alerts

Chapter 28Using Task Manager Report Binders

28-13

• Comments

• Attachments

Note:

Including attachments in the report greatly increases the size of thereport and may impact the performance.

6. Click Generate.

7. From File Download, select Save.

The Save As dialog box is displayed, and the ZIP file name is displayed at thebottom.

8. Select a directory for the ZIP file, click Save, then Close.

Viewing Report BindersWhen you generate a report binder, it is output in one zipped file. The ZIP file name isthe name that you specified for the Report Binder. The report pages are merged intoan HTML report, with page breaks for sections as required, so that the report can beprinted with a print command. If you choose to include attachments, a separateattachment appendix, containing links to attachments with corresponding tasks andalerts, is created, which you can print separately. All attachments are downloaded toseparate folders.

If you saved the report binder as a ZIP file, you can extract everything from the ZIP,which creates a directory structure with the same name as the report binder. You cansee the report binder by opening the HTML page in the directory. The first report pagecontains information on the report binder, the schedule, and displays a list of tasks andalerts available in the report binder. You can navigate to the Tasks section to see taskdetails such as status, Assignee, start and end dates, and duration. If a task has notstarted, the projected (scheduled) date is displayed. Each task is a link to a TaskDetail page. By default, it includes sections for Attributes, Instructions, Questions,Workflow, Predecessors, and History. If you selected the options to include Alerts andComments when you generated the report binder, those sections are also displayed.

The first page also contains a list of alerts into which you can drill further. From theAlert Detail page, you can navigate to the associated task.

To view report binders:

1. Navigate to the directory in which you downloaded the ZIP file, and double-clickthe file.

2. Extract the ZIP files to the desired directory.

3. Navigate to that directory and locate the subdirectory that matches the ZIP filename.

4. From the subdirectory, double-click report_binder_name.html to view the reportbinder.

Chapter 28Using Task Manager Report Binders

28-14

29Managing Supplemental Data

Related Topics

• Supplemental Data Process Overview

• Managing Supplemental Data System Settings

• Working with the Data Set Dashboard

• Managing Dimension Attributes in Supplemental Data Manager

• Working with Data Sets

• Creating Data Sets

• Adding Data Set Attributes

• Importing Data Set List Attributes

• Viewing Data Set History

• Deleting Data Set Attributes

• Editing Data Sets

• Copying Data Sets

• Deleting Data Sets

• Creating Supplemental Data Manager Form Templates

• Editing Form Templates

• Duplicating Form Templates

• Deleting Form Templates

• Deploying a Form Template to a Data Collection Period

• Un-Deploying a Form Template to a Data Collection Period

• Re-opening Supplemental Data Forms

• Validating Supplemental Data Total Against an Account Balance

• Managing Data Collection Workflow

• Working with Supplemental Data in Smart View

• Using Currency Translation

• Selecting Default Currency for Entity Members

• Setting Up Currency Attributes for Translation

Supplemental Data Process OverviewSupplemental Data Manager helps you organize, update, edit, and managesupplemental data, typically financial transactions. It is a robust ad hoc data collectionprocess useful for footnotes, disclosures, and supporting details. You can:

29-1

• Define the data definition and associated data forms for data collection

• Support the ability to create calculation formula and validation criteria

• Control and monitor the data collection workflow

Supplemental Data management requires these steps:

1. The Administrator or Power User completes the required setup procedures:

• Sets up users.

• Sets up metadata information referenced in a data set; for example, dimensiondefinition and members.

2. The Power User defines the data set:

• Creates data sets, attributes, and calculation and validation rules for theattributes.

Note:

Users can input or calculate an attribute.

• Creates additional Data Form Templates.

• Assigns workflow and access for each data form template.

• Deploys the form template to a specific data collection period to be ready forthe collection process.

– If the period is not open, then the form instances are in pending status.

– If the period is open, then the form instance is active and available for dataentry.

• Sends email alerts to assigned users for their related data forms.

3. The User loads the data:

• Loads data manually or uses a CSV file for each form data or web UI.

• Performs validation and ensures correctness of data.

• Submits data for approval.

4. The User assigned as the approver reviews and approves or rejects the data (mayhave multiple levels of approval).

5. The Administrator opens the Period after dimensions, data sets, and forms arecreated in the system, and also to start the data collection process.

6. The Administrator or Power User sends email alerts to assigned users for theirrelated data forms.

7. The User groups and filters data to focus on certain data segments.

8. The User views the summarized data after data is approved (depends on workflowoption) and posts data.

9. The Administrator closes and locks the Period for the data collection:

• Closes Period for Data Collection (prevents additional form instances to start)

• Locks Period for Data Collection (allow no additional changes)

Chapter 29Supplemental Data Process Overview

29-2

You can also use Oracle Smart View for Office for the data collection process. Whenyou install the Smart View Extension for Supplemental Data, you can manage the datacollection process and work with supplemental data forms using the SupplementalData menu option in Smart View. See Working with Supplemental Data in Smart View.

Watch these videos to learn more about using supplemental data:

Supplemental Data

Supplemental Data Workflow

Managing Supplemental Data System SettingsRelated Topics

• Setting Email Notifications in Supplemental Data Manager

• Setting Preferences for Supplemental Data

• Setting Supplemental Data Governors

Setting Email Notifications in Supplemental Data ManagerService Administrators can set up Email Notifications for Supplemental Data Managerusers. When you enable email notifications, batch notifications are generated. Whenthe notification is no longer required, you can deactivate email notifications andreminders.

Note:

By default, email notifications are not enabled.

You can also add an email as the From Address. Customize the from address, orperhaps include a product acronym to alert the user where the notification is comingfrom.

To set email notifications:

1. On the Home page, click Application, and then click Supplemental Data.


3. Select Email Notifications.

4. For Email Notifications, select Turn On to initiate the notification, or Turn Off todeactivate the notification.

5. Enter the email From Address. You can edit the email address to supply aspecific address, or to include a product acronym to alert the user where thenotification is coming from, for example, SDM.

6. Click Save.

Chapter 29Managing Supplemental Data System Settings

29-3



Setting Preferences for Supplemental DataYou can specify preferences for the number and cell formats to be displayed forSupplemental Data. You can specify the number of decimal places to display, how youwant to display negative numbers, cell styles, fonts, and colors.

To set Supplemental Data preferences:



3. On the System Settings page, click the Preferences link.

4. For Number Format, select these options:

• Decimal Places

• Negative Number

5. For Cell Format, select these options:

• Cell Styles

• Font, and then select Bold, Italic, or Underline

• Font size

• Text Color

• Background Color

6. Click Save.

Setting Supplemental Data GovernorsIn Supplemental Data, you can set governors on Data Set attributes to improveapplication performance. The system provides default settings, which you candecrease or increase up to the maximum value. It enforces the maximum limits whenobjects are created.

For example, you can specify the maximum number of Calculated attributes per DataSet. When you create Calculated attributes, if the number of attributes is below themaximum value, the system creates the attributes. If the maximum limit has beenreached, the attributes are not created and the system returns a validation messagethat the number is out of range. You can also specify the maximum number ofDimension attributes per Data Set, number of sections per Form Template, andnumber of attributes per Form Template Section, and number of attributes displayedon Data Analysis.

To set Supplemental Data governors:



3. On the System Settings page, click the Governors link.

4. Specify a maximum value of attributes or leave the default setting:

• Maximum Number of Calculated attributes per Data Set

• Maximum Number of Dimension attributes per Data Set

Chapter 29Managing Supplemental Data System Settings

29-4

• Maximum Number of Sections per Form Template

• Maximum Number of attributes per tabular Form Template Section

• Maximum Number of attributes displayed on Data Analysis

5. Click Save.

Working with the Data Set DashboardThe Supplemental Data Set dashboard contains the details of data sets, making iteasy to view and filter the information collected and processed as part of the datacollection and management process. You can also select and sort columns, viewSummary totals, and save and restore lists.

To work with data sets in the Data Set Dashboard:


2. From the left, click Data Analysis.

3. From the POV on the Supplemental Data Analysis page, select a Year, Period,and Scenario to define a data collection period.

4. From the Data Set dropdown list, select a data set for the data collection period.

5. Optional: Click Add a Filter, then enter a Value to filter. Available filters arebased on the data set you selected.

6. Optional: For more detailed filtering, from Add a Filter, click Advanced, thendefine filter criteria and create conditions.

To define a condition or group:

a. Click Create Condition or Create Condition Group.

b. Conjunction: Select And or Or. These state how this condition or group relateto prior sibling conditions or groups.

c. Attribute: An attribute is a field or value that a condition compares to a valuefor inclusion in the result set of a filter. An attribute denotes more than the listof user-defined attributes.

d. Operand: States what kind of evaluation to perform against the attribute.

e. Value: Specifies what values to compare the attribute against. The type ofattribute determines what input field is available.

f. To save, clear, or manage filters, click the Filters (...) button on the right of thepage.

7. From Actions, choose Select Columns to select columns for the data that youwant to display.

8. Optional: From Actions, select Export to Excel to export data from the data set.

9. Optional: From Actions, select Import to import data into the data set.

Click Browse to select the file, select to Replace or Update the existing file, selecta date format, and then click Import.

10. Optional: From List, switch between your available saved lists. The systemdisplays the filters and columns that you previously saved.

11. Click Summary to view a consolidated view of the data set's data.

Chapter 29Working with the Data Set Dashboard

29-5

Managing Dimension Attributes in Supplemental DataManager

Related Topics

• Adding Dimension Attributes

• Editing Dimension Attributes

• Deleting Dimension Attributes

Adding Dimension AttributesTo add dimension attributes:


2. Click the Dimensions tab on the left.

3. Select a dimension, then click Actions, and then Edit.

4. On the Attributes tab, click Actions, then New, and then Add Attribute.

Enter the following:

• Name

• Description

• Key Attribute

Select the Key Attribute check box if this attribute is the key attribute.

• Data Type

Select one:

– Date

– Date and Time

– Integer

– List

Select a method:

* Click Add, and then enter values for the attribute.

* To import or export list items from a CSV file, click Import or Export.

– Number

If you select Number, select formatting options (The defaults are set in thePreferences section of the System Settings).

* For Decimal Places, enter a value for the number of decimal placesto be displayed.

* Select Display as Percentage to display a percent sign.

* Select Thousands Separator to display a thousands separator (forexample, 1,000.00). The system displays the thousands separatorsymbol for the user locale.

Chapter 29Managing Dimension Attributes in Supplemental Data Manager

29-6

* In Negative Number, select how to display negative numbers; forexample, (123).

– Text (255 characters maximum)

– True or False

– Yes or No

• Default Value

The attribute is populated with this value by default, which you can override.

5. Click OK.

6. In Update Dimension, to select the new attribute as a "Key Attribute" for thedimension, select Key Attribute.

Note:

The system allows multiple attributes as key for a dimension.

Editing Dimension AttributesThe Members and Attributes section lists dimension members, descriptions andattributes, including leaf attributes and parent node, and the corresponding cube forthe dimension member.

To edit dimension attributes:



The Members and Attributes section displays dimension members, descriptionsand attributes, including leaf and parent node information, and correspondingdimension cubes.

3. Select a Local dimension, then click Actions, and then Edit.

4. On the Attributes tab, select an attribute, and then click Edit.

5. Edit the attribute as needed.

You can't change the data type if a member already exists for the dimension or ifthe attribute is referenced in a data set.

6. Click OK.

Deleting Dimension AttributesTo delete dimension attributes:



3. Select a Local dimension, then click Actions, and then Edit.

4. On the Attribute tab, select an attribute, and then click Delete.

Chapter 29Managing Dimension Attributes in Supplemental Data Manager

29-7

Note:

You can't delete an attribute if it is referenced in a data set.

5. From the confirmation prompt, click Yes.

Working with Data SetsData sets contain definitions of data tables. A data set consists of attributes ofinformation for any data record. Data sets can contain attributes from Dimension, andyou can enter attributes. Only Administrators or Power Users can create and updatethe data set definition.

Manage Data window sections:

• A master section displays a listing of Data Sets with columns: Name, Description,Last Updated on, and Last Updated By

• An Attributes section with columns: Name, Data Type, and Assign Workflow

• Associated Form Templates with columns: Name, Description, Scenario, and LastUpdate. You can add, edit, and remove form templates from the selected data set

Creating Data SetsA new data set always contains the Entity attribute and is always displayed to showthat you can assign this entity to a workflow.

Note:

The Entity key identifier and Assign Workflow options are selected by default.

Watch this video to learn more about creating data sets.

Creating Data Sets

To create data sets:


2. Click the Data Sets tab on the left.

3. Select Actions, and then New.

4. On the Properties tab, enter the data set information:

• Name—Enter a unique name.

• Description

5. On the Attributes tab, add attributes for the data set.

See Adding Data Set Attributes.

Chapter 29Working with Data Sets

29-8


Adding Data Set AttributesAttributes are user-defined fields defined centrally by administrators and used in manyplaces. You can specify different value types for attributes: Date, Date and Time, List,Number, Text, and True or False.

For data sets, you can add date calculation attributes such as a Start Date and EndDate for a data collection period.

To add data set attributes:



3. Select a data set, and then click Edit.

4. Select the Attributes tab, which has the following columns:

• Key Identifier

If no data exists for this data set, you can modify the Key Identifier andattributes of the data set.

The Key Identifier and Assign Workflow check box option for Entity is selectedby default. As you add attributes, you can select one or more as the KeyIdentifier.

Note:

Supplemental Data Manager does not support the Calculatedattribute as a Key Identifier attribute in data sets.

If you select the Calculated attribute as a Key Identifier, you mayencounter unexpected behavior and errors in data sets.

• Assign Workflow

Only attributes with Key Identifier ON can be assigned workflow. Assignworkflow ON means that you want to select members from this dimension toassign workflow to each preparer. To assign workflow, the attribute must be adimension, because you assign a workflow from a predefined list.

• Name

• Dimension Name

• Attribute Type (displayed if there are existing attributes)

• Data Type—Date, Date and Time, Integer, List, Number, Text, True or False,Yes or No

• Total—Enables you to specify the totaling method for the attribute:

– Sum: Additive total

– Average: The average of the rows with data. Rows without data are notcounted in the denominator

– Count: The count of the rows with data

Chapter 29Adding Data Set Attributes

29-9

– None: No total is calculated

5. Click Actions, then New, and then select:

• Add Attribute: Go to step 5.

• Add Attribute from Dimension:

a. Select a Dimension.

b. Select attributes from the Available Attributes list and Move them to theSelected Attribute list.

Note:

The system includes the key attribute of the dimension as aSelected Attribute. You cannot clear the key attribute.

c. Click OK and then Save or Save and Close.

6. If you selected Add Attribute, on Create New Attribute, enter the Properties tabinformation:

• Name

• Description

• Specify the Attribute Type:

Changing the Attribute Type overrides previously specified Validations orCalculations. You cannot change this setting after the attribute is created.

– Input: Input is the default, and the Validations tab is enabled.

Note:

For periods that have been opened and form instances created,the modified validation rule does not apply. Changes made applyonly to new form instances.

– Calculated: If type is Calculated, then the Calculated tab is enabled.

• Data Type

Select one:

– Date

– Date and Time

– Integer

– List

Click Add and enter values for the attribute. List is local to the Data Setand can't be shared among other Data Sets.

– Number

If you select Number, select formatting options to override the defaults setin the Preferences section of System Settings.


29-10

Note:

You can only enter numeric values for this attribute.

* For Decimal Places, enter the number of decimal places to display.

* Select Display as Percentage to display a percent sign.

* Select Use Thousands Separator to display a thousands separator(for example, 1,000.00). The system displays the thousands separatorsymbol for the user locale.

* In Currency, select the currency, for example, (INR)

* In Negative Number Format, select how to display negativenumbers; for example, (123).

* To scale a number, in Scale, select from 1000 to 1000000000000


– True or False

– Yes or No

• Required

If the attribute is required, you must enter a value in this field during data entry.

• Use Value

If Use Value is populated, the system applies the value entered by thedesigner for any record created by the user.

Note:

You can change the default value during data entry.

7. Click OK to save the attribute.

Note:

You must save the attribute before including it in a calculation.

8. To continue adding an attribute:

• If you selected Input for the Attribute Type, then select the Validations tab.

To add a conditional expression:

You can create a special validation rule for the value entered by the user.

a. Click Add.

b. Select an Operand and enter Value1 and Value2.

c. If you need a second condition, select from the following lists:

– Conjunction; for example, And, Or


29-11

– Operand; for example, Equals, Between, Does not Equal, Greaterthan, Is blank, Is not blank, Less than, Not between

– Value1 and Value2

d. Click OK.

• If you selected Calculated for the Attribute Type, then select the Calculationstab.

The following section is an example of how to add a calculation attribute.

a. Create a data set with these attributes:

Int1 Input and Data Type: Integer. Click OK, and on Edit Data Set, selectInt1 as a Key Identifier.

TextInput: Input and Data Type: Text.

b. To use the attribute in TextCalc, save the data.

c. Create an attribute TextCalc: Calculated and Data Type: Text.

d. On the Calculations tab, enter the following fields:

i. Calculation Type: Select Scripted.

ii. Add Function: Select TextLocation, and then click Add.

iii. INSTRING(<Value>, <Value To Search>) is added to CalculationDefinition.

iv. Click <Value> and either enter a value (enclosed in single quotationmarks and case sensitive), or, in Add Attribute, select an attribute,TextInput, and then click Add.

Note:

<Value> changes to {TextInput}.

v. Replace <Value to Search> with 'tion'

Note:

Ensure that you replace <xxx> with single quotation marks:'xxx'

Example INSTRING({TextInput}, 'tion')

9. To add a calculation expression, select a data type and calculation type asdescribed in the following table, and then click OK.


29-12

Table 29-1 Data Type and Calculation Type

Data Type selected on PropertiesTab

Calculation Type Description

For all data types Assign Value to List, and thenselect the Attribute value.

Note:

You must have saved theList attribute values.

Return an attribute value based onthe assignment to a List member.

For all data types Conditional For a given attribute, return attributevalue A if specified conditions havebeen met. If the conditions have notbeen met, return attribute value B.

List Assign List To Value Based on the value of an attribute,return the related member from thelist.

Numeric, Integer Formula Calculate an attribute using commonmathematical expressions.

Example: (A+B)/C

Numeric, Integer Round Round attribute to the specifiednumber of digits. The default is 2.

Text Concatenate Paste together text attributes. Thisincludes literal strings andautomatically converting non-textattributes to strings.

Example: First_Name+““+Last_Name+“:”+Birth_Date

Integer, Number, Text ScriptedSee the following section:"ScriptedFunctions".

A free-form scripted calculation.Scripted is available for attributes oftype Integer, Multi-line Text, Number,or Text.

10. Click Save, Save and Close, or Close.

Note:

Changes to data set attributes apply only to subsequent data collectionperiods.

Scripted Functions

• Absolute Value: Returns the absolute value of a specified number. If anumber is less than zero, the positive value of the number is returned. If thespecified number is equal to or greater than zero, the specified number isreturned.

ABS(<Number>)


29-13

• Add Month: Returns a date offset a specified number of months from thestarting date. The date will always fall in the specified month offset. If thestarting date has a day value beyond what is in the offset month, the last dayof the offset month will be used. For example, EDate (31-Jan-2017, 1) returns(28-Feb-2017). For Months, enter the number of months before or after thestart date. A positive value for months yields a future date. A negative valueyields a past date.

ADD_MONTH(<Start Date>, <Months>, <Length>)

Example: ADD_MONTH(DATE(2017, 2, 15) 3)

• Average Prior: Averages a numeric amount over the prior X periods.

AVERAGE_PRIOR(<Value>, <Number of Periods>, <To Currency*>

Example: AVERAGE_PRIOR( {Balance (Reporting)}, '2', 'EUR'

• Date: Returns a date value based on specified integer values for the year,month and day.

DATE(<Year>, <Month>, <Day>)

• Date Difference: Returns the difference in days, hours minutes, or secondsbetween two dates. For DATE 1 and DATE 2, the values TODAY and NOWcan be used, which denote the current date (with no time component) anddate-time, respectively.


Example: DATE_DIFF('TODAY', {Preparer End Date}, 'DAYS') orDATE_DIFF({Preparer End Date}, 'NOW', 'HOURS')

• Day: Returns the day value of a date as an integer number

DAY(<DATE>)

• Extract Text: Returns the substring within the value, from the positionsspecified.

SUBSTRING(<Value>, <Location>, <Length>)

Example: SUBSTRING( {Name} , 5, 10)

• If Then Else: Allows the user to insert a conditional calculation into thescripted calculation. IF_THEN_ELSE calculations can also be nested tosupport “ELSE IF” type calculations.

IF_THEN_ELSE(<Condition>, <Value1>, <Value2>)

Example:

IF_THEN_ELSE( {Risk Rating} = 'Low', 'Good',IF_THEN_ELSE( {Risk Rating} = 'Medium', 'Better',IF_THEN_ELSE({Risk Rating} = 'High', 'Best','Bad')))

• Lowercase: Returns the value in lower case.

LOWERCASE(<Value>)

Example: LOWERCASE( {Description} )

• Maximum: Returns the maximum value from a list of attributes. There can beany number of parameters.

MAX(<Value1>, <Value2>,<ValueN>)


29-14

Example: MAX( TRANSLATE( {Source System Balance (Entered)}, 'USD','Accounting'), TRANSLATE( {Source System Balance (Functional)}, 'USD','Accounting'), TRANSLATE( {Source System Balance (Reporting)}, 'USD','Accounting') )

• Maximum Prior: Returns the maximum value over the prior X periods.

MAX_PRIOR (<Value>, <Number of Periods>, <To Currency*>, <RateType*>, <Rate Period*>)

Example: MAX_PRIOR( {Balance (Functional)}, '6', 'CAD', 'REC')

• Minimum: Returns the minimum value from a list of attributes. There can beany number of parameters.

MIN(<Value1>, <Value2>,<ValueN>)

Example: MIN( TRANSLATE( { Balance (Entered)}, 'CAD', 'REC'),TRANSLATE( {Balance (Functional)}, 'CAD', 'REC'), TRANSLATE( {Balance(Reporting)}, 'CAD', 'REC') )

• Minimum Prior: Returns the minimum value over the prior X periods.

MIN_PRIOR (<Value>, <Number of Periods>, <To Currency*>, <Rate Type*>,<Rate Period*>)

Example: MIN_PRIOR( {Source System Balance (Functional)}, '6', 'EUR','Simplified')

• Month: Returns the month value of a date as an integer number (1-12)

MONTH (<DATE>)

• Power: Raises one number to the exponential power of another.

POWER(x,y) where x=BASE NUMBER,and y=EXPONENT and x and y can beattributes or calculations, as long as they are numeric.

Example: POWER(3,4)=81

Note:

Fractional values will reduce the number to its root. For example,POWER(27, 1/3) = 3 the cube root.

Negative values will perform an inverse of the exponentialcalculation. For example, POWER(2, -2) = 1 / (2^2) = 1 / 4 = .25.

• Prior: Returns the value of the specified prior period.

PRIOR(<Value>, <Number of Periods Prior*>, <To Currency*>

Example: PRIOR( {Source System Balance (Entered)}, '1', 'EUR'')

• Round: Returns the value rounded to the decimal places specified.

ROUND(<Value>, <Decimal Places>)

Example: ROUND( ({Scripted Translate} /7), 4)

• Sum Prior: Returns the sum of a value over the prior X periods.

SUM_PRIOR(<Value>, <Number of Periods>, <To Currency*>


29-15

Example: SUM_PRIOR( {Balance (Reporting)}, '3', 'EUR')

• Text Location: Returns the location of the substring within the attribute value,starting at 1 as the first position.

INSTRING(<Value>, <Value To Search>)

Example: INSTRING( UPPERCASE( {Name} ), 'TAX' )

• Translate: Translates a currency attribute to a numeric attribute using aspecified rate type.

TRANSLATE(<Value>, <To Currency>, <Rate Type>)

Example: TRANSLATE( {Balance (Entered)}, 'EUR', 'Acct')

• Uppercase: Returns the value in upper case.

UPPERCASE(<Value>)

Example: UPPERCASE( {Name} )

• Year: Returns the year value of a date as an integer number.

YEAR (<DATE>)

Importing Data Set List AttributesTo import attributes of type List:

1. Create an import file of type List in a TXT file format, with each value on aseparate line.

For example:

BlueYellowRedGreen



4. Create or select an attribute of type List, and then click Edit from theAssociated Form Templates area. The Edit Form dialog is displayed.

5. Click Import from the Users area.

6. Browse to a TXT import file.

7. Select an Import Type. Update is the default.

8. Select a File Delimiter for the import file from the drop-down: Comma or Tab.Comma is selected by default.

9. Click Import.

Import List Values displays the values: Total List Values, Completed, Errored,List Values Created, and List Values Updated.

If Completed Successfully, click OK.

If Completed with Errors, the errors are listed. To export the error list, clickExport to Excel .

Chapter 29Importing Data Set List Attributes

29-16

Viewing Data Set HistoryTo view Data Set history:



3. Select a data set and then click Edit.

4. View the following fields:

• Field

• Modification Type

• Supporting Object

• Modified By

• Modified On

• Old Value

• New Value

Deleting Data Set AttributesTo delete data set attributes:



3. Select a data set, and then click Edit.

4. Select the Attributes tab, then an attribute, then Actions, and then Delete:

• If data exists, you cannot delete the attribute.

• If no data exists, but the attribute is referenced in a form template, you cannotdelete the attribute without first removing the attribute from the form template.


Editing Data SetsTo edit data sets:



3. Select a data set, then click Actions, and then Edit.

Note:

You cannot edit attributes referenced from Dimensions.

Chapter 29Viewing Data Set History

29-17

Assign Workflow is read-only.

4. Properties tab:

Modify the Name and Description.

5. Attributes tab:

If data exists for this data set, you can modify the Key Identifier and attributes ofthe data set.

Copying Data SetsYou can copy a data set by using the Data Analysis dashboard. From the dashboard,you can export the data from one POV and import it into another POV.

To copy a data set:


2. From the left, click Data Analysis.

3. From the Data Set dropdown list, select a data set that you want to copy.

4. From the POV on the Supplemental Data Analysis page, select a Year, Period,and Scenario of the data that you want to copy.

5. From Actions, select Export to Excel to export data from the data set.

6. From the POV on the Supplemental Data Analysis page, select a Year, Period,and Scenario for the data set that you want to paste.

7. From Actions, select Import to import data into the data set.

Deleting Data SetsTo delete data sets:



3. Select a data set, then Actions, and then Delete.

• If data exists, you cannot delete the data set.

• If no data exists, however, form instances are created, and you cannot deletethe data set.


Creating Supplemental Data Manager Form TemplatesAdministrators and Power Users can manage Form Templates.

When creating Form Templates, Administrators can specify whether the template canbe used for creating Ad-Hoc Forms, and then select the users who are allowed tocreate them. You can select individual Users or Teams.

Chapter 29Copying Data Sets

29-18

Note:

When the workflow option is POST only, Ad-Hoc Form creation cannot beenabled.

Watch this video to learn more about creating supplemental data forms.

Supplemental Data Forms

For more information on working with and entering data into forms, see the Workingwith Financial Consolidation and Close guide.

To create form templates:


2. Click the Form Templates tab on the left.

3. Click New.

4. On the Properties tab, provide information:

• Name

Enter a unique form template name.

• Description

• Scenario

The Scenario dimension is created as part of the application.

Select a scenario for the template; for example: Actual or Budget.

• Optional: Select Allow Ad-Hoc Forms to allow users to create forms fromthe template.

From Users for Ad-Hoc Forms, click the Add (+) icon to open the MemberSelector, then select and add the users who can create forms, and click OK.

5. Access these tabs on the Create Form template:

• Sections

• Instructions

• Workflow

• Questions

• Access

• History

Specifying Form Template InstructionsAdministrators provide instructions on how to use the form. Instructions can includetext, attached files, and links to files in document repositories.

To specify form template instructions:

Chapter 29Creating Supplemental Data Manager Form Templates

29-19




3. In New Form Template or Edit Form Template, select the Instructions tab.

4. In Instructions, enter instruction text.

To add a reference to a file:


Tip:

To delete a reference, select the reference, and then click Delete.

2. Select a reference type:

• Local File—Browse the local file system and select a file. You must specify aName. Click OK to upload the file to the system and store it with the formtemplate.

• URL—Enter an external URL reference and give it a descriptive Name. ClickOK to store the URL in the application.

Working with Supplemental Data Manager Form SectionsEach section of a data entry form can collect data from different data sets or attributecombinations. Sections can have overlapping data sets or attributes; only one attributeper data set can be writable.

To create or edit sections:



3. In New Form Template or Edit Form Template, select the Sections tab.

4. Click New or select a section and click Edit. The Edit Form Template Section isdisplayed.

5. On the Properties tab, enter:

• Name

• Data Set

• Data Records

Select one:

– Rows—The attributes of the form are displayed as a table; you makeentries in the row. The system always displays the attribute name as theheader.

– Columns—The attributes of the form are displayed in the row andcolumns where the user enters the value for each attribute of the form.The fields include one data entry record per attribute. The system displaysthe attribute description as the row header of the form.

6. Enter information or view the following Section tabs:


29-20

• Columns: Form Template Sections: Columns Tab

• Group by: Form Template Sections: Group By Tab

• History: Form Template Sections: History Tab

7. To save your updates and go back to the Form Template Sections tab, click OK.

Form Template Sections: Columns TabAdministrators can create attributes for Supplemental Data Forms directly in the formtemplates, without needing to first create the attributes in Data Sets. The attributes willalso be available in Data Sets.

Open a Supplemental Data form.

On the Columns tab, select the columns for the form. The system displays all columnsof the Data Set that are not workflow columns.

To update the Columns tab:

1. In New Form Template or Edit Form Template, select the Section tab.

2. Click New, or select a section and click Edit.

3. In the Edit Form Template section, click the Columns tab, and select or view thefollowing columns:

• Included

Select other attributes to be included in the form.

• Name

The name of the Data Set attribute

• Dimension

The column from an attribute of a specific dimension. This is read-only.

• Data Type

The corresponding data type for the column (read-only).

• Column Width

The column width specified in pixels. The default value is Size to Fit.

– Small: Fixed pixel width of 50

– Medium: Fixed pixel width of 100

– Large: Fixed pixel width of 300

– Size to Fit: Fit the width of the column based on the longest text in therows

– Custom: Specify a width. Minimum value: 20. Maximum value: 999.

• Total

Total method for the attribute as specified in the Data Set. It is always read-only.

• Total Validation POV

Validation of Supplemental Data against account balances.


29-21

From the drop-down icons, select the Cube , and then the POV.

Note:

View Only column for each dimension attribute must be deselectedto validate against account balances.

• View Only

The column is for view only. If multiple forms are created for the same DataSet, then only one form can contain the column for input, including keycolumns.

4. Total Row

How the total row should be displayed:

• Top: Total row is displayed at the top of the table

• Bottom: Total row is displayed at the bottom of the table

• None: Total row is not displayed

5. Optional: To add new attributes to a Form Template Section, click the Add (+)icon, select Add Attribute and specify the attribute information.

The procedure for adding attributes in Form Template Sections is the same asadding attributes in a Data Set. See Adding Data Set Attributes.

6. Click OK to save the data.

Form Template Sections: Group By TabTo update the Group By tab:

1. Open a Supplemental Data form.



4. In the Edit Form Template Section, click the Group By tab.

5. Click the Columns, and then select or view the following columns:

• Include

Select other columns to be included in the Group By.

• Group By

Data in the main table should be grouped by the selected columns.

• Name

The name of the Data Set

• Dimension

The column from an attribute of a specific dimension (read-only).


29-22

• Data Type

The corresponding data type for the column (read-only).

• Total

Total method for the attribute as specified in the Data Set (read-only).

6. Total Row:

Indicates how the total row should be displayed:

• Top: Total row is displayed at the top of the table

• Bottom: Total row is displayed at the bottom of the table

• None: Total row is not displayed

7. Enter or view the information on the following tabs:

• Columns tab:Form Template Sections: Columns Tab

• History tab: Form Template Sections: History Tab


Form Template Sections: Mapping TabYou use the Mapping tab to specify the POV to which to post the form data. You canmap Supplemental Data Manager form entries based on attributes selected in theGroup By tab. The attribute amounts are summed using the attribute selected in theGroup By tab.

If you are using a List data type for an attribute on the Group By tab, you can mapindividual items on the list. In this case, edit the Mapping text to include @Listname.The @Listname will be used as a replacement for each child in the List attribute. Besure that all of the list members are identical to dimension members so there are noinvalid POVs.

Note:

As a best practice, clear the browser cache and re-login before creating orediting mapping.

To update the Mapping tab:


2. In New Form Template or Edit Form Template, select the Sections tab.

3. Click New, or select a section and click Edit. The Edit Form Template Section isdisplayed.

4. Click the Mapping tab.

5. Select the Connection.

The Source column defaults to the column that was selected when the assignmapping menu was chosen. Change to a different source column if needed.

6. From the Cube dropdown, select a cube from the list of available cubes.


29-23

7. Click the Member Selector to select members for the Point of View.

You must specify a member for each POV dimension. Make sure that the POV isvalid before mapping.

8. In Mapping, enter the POV.


Form Template Sections: History TabThe History tab logs changes to the form template sections.

To view the History tab:




4. In the Edit Form Template Section, click the History tab.

5. Click View to select the columns to display from the list, or select More Columnsto manage the visible columns and the order in which they display.

6. You can view the following information:

• Field

• Modification Type

• Supporting Object

• Modified By

• Modified On

• Old Value

• New Value

7. To go back to the Form Template Sections tab, click OK.

Assigning the WorkflowUse the Workflow tab to assign the workflow for the form.

To assign the workflow for the form:


2. In New Form or Edit Form, click the Workflow tab.

3. In When to Start, enter the following:

• Frequency—How often the data is collected for the form.

• Schedule from—The collection date:

– End Date––The end date of the period.

– Close Date––The closing date specified for the period.

• Start day Offset––The start date for the data collection of the form. Thisdetermines the number of days after the End date or Close Date that the datacollection date is authorized to begin. It can be a positive or negative number.


29-24

For example, you can prepare data a few days before the start day, and set -3for the collection to start 3 days from then.

4. In Workflow, enter the following:

• Workflow option––Select an option:

– Prepare

– Prepare and then Approve

– Prepare, then Approve, and then Post

– Prepare and then Post

– Post

• Level of Approval—Select up to 10 levels of approvers.

• Duration for—The maximum number of days allowed for a specific action peruser.

This data determines the scheduled completion date for submission, approval,and posting depending on the workflow option.

5. In the Users section, add or delete users in the enabled fields:

• To import or export users from a CSV file, click Import or Export.

To import a CSV file, create a file with each entry on a separate line per Entity.

• To add a user, click Actions, then New. Under the Entity column, click the

Entity Selector icon, select the Entity and click OK, and select each ofthe users that are assigned to the form template.

• To delete a user, select a user, then click Actions, and then Delete.

Specifying Form Template QuestionsQuestions are automatically grouped with roles. Within a role, the individual questionsare ordered. The order indicates the question’s order within the role.

To create questions:



3. In New Form or Edit Form, click the Questions tab.

4. Click New or Edit.

5. Enter the following:

• Question

Enter a question that prompts the user of the form's response.

• Data Type

Select a question type:

– Date

– Date and Time

– List


29-25

Click Add and enter values for the attribute.

– Integer

– Number

If you select Number, select formatting options:

* For Decimal Places, enter the number of decimal places to display.The default value is defined in System Preferences.

* Select Thousands Separator to display a thousands separator (forexample, 1,000.00). The system displays the thousands separatorsymbol for the user locale.

* From Currency, select the currency, for example, (INR)

If no currency is selected, the amount is not translated.

* From Negative Number, select how to display negative numbers; forexample, (123).


– True or False

– Yes or No

• Role—Specifies the role that the question is for.

• Required—Determines whether the question is mandatory or optional.

To delete questions:

1. In New Form or Edit Form, select the Questions tab.

2. Select a question and click Delete.

Setting Form Template AccessOn the Access tab, you determine which users are authorized and what function theyperform on the form.

• The top panel of the Access tab shows the list of users with View access.

• The bottom panel displays the entity's form data that the user has access to.

You can import lists of viewers in CSV files to quickly assign access to multiple users.Viewers can be users or teams. You then use the View option to determine the stageat which they can access a form. You can also export the list of users for analysis byadministrators.

Note:

You must define a Workflow before you assign Viewer access.

To add access:



3. Click New Form or Edit Form, and click the Access tab.


29-26

4. Click New, or select a user and click Edit.

5. In Viewers Access, select a user.

6. In Entities, by default, all the form data for a specific entity is selected. You selector clear data individually using the check box next to each. Select or clear all byclicking the check box in the title area.

Select a View Option:

• Always—You can view the data at any time even if the data entry is notcomplete or has not been submitted for approval.

• After Submission—You can view the data as soon as the data is submitted,even before it has been approved.

• After Approval—You can't view the data until after all levels of approvals aregranted.

7. Optional: To load Viewer Access for multiple users from a CSV file:

a. Click Import.

b. Browse to select the file.

c. For Import Type, select Replace All or Update.

d. Select a File Delimiter.

e. Click Import.

Viewing Form Template HistoryThe History tab logs changes to this form template.

To view form template history:



3. In New Form or Edit Form, click the History tab.

4. View the history, and then click Save, Save and Close, or Close.

Editing Form TemplatesTo edit form templates:



3. Select a form template, then select Actions from the top menu bar, or from theellipsis button (...) and selectEdit.

Duplicating Form TemplatesTo duplicate form templates:



Chapter 29Editing Form Templates

29-27

3. Select a form template, then select Actions from the top menu bar, or from theellipsis button (...) and selectDuplicate.

The Duplicate action creates a copy with a "copy" suffix added to the form name.In addition, all attributes are read-only to prevent multiple form templates havingwrite access to the same Data Set.

Deleting Form TemplatesTo delete form templates:



3. Select a form template, then select Actions from the top menu bar, or from theellipsis button (...), and select Delete.

4. Click Yes to confirm that you want to delete the template.

Deploying a Form Template to a Data Collection PeriodAfter you create a form, you can deploy it. You can also redeploy a previouslydeployed form.

When you redeploy a Supplemental Data Form, you can use the option to clearexisting data in the form. If the “Clear Data from Currently Deployed Forms” option isselected, when you redeploy the form, all existing data, comments and answers will beerased. If you make a minor change to a form, such as adding a new user to thetemplate, and do not select Clear Data, the existing data is retained when the form isredeployed.

To deploy a form template to a data collection period:



3. Click Deploy .

The Deploy Form Template displays Pending Period and Open Period DataCollection Periods to choose from.

4. To select another data collection period:

a. Click Search.

b. In Select Data Collection Period, select Year and Scenario.

c. Click Search to refresh the periods.

d. Select a period.

e. Click OK.

5. Select the form templates for that data collection period.

6. Click Deploy.

• If the form template already was deployed, a warning message says that allexisting form instances and data for that form template will be removed andnew form instances will be generated.

Chapter 29Deleting Form Templates

29-28

• If additional Form Templates that are not part of the original selection must bedeployed based on their data set relationships, Additional Form Templatesis displayed. Click OK.

7. If you are redeploying a form, select whether to Clear Data from CurrentlyDeployed Form:

a. If you do not select the checkbox, when the form template is redeployed, allexisting comments and answers will be erased, but existing data will beretained. All workflow related information will be reset to Open with Preparer.

b. If you select the Clear Data option, when the form template is redeployed, allexisting data, comments and answers will be erased. All workflow relatedinformation will be reset to Open with Preparer.

8. After deployment is completed, a confirmation dialog box indicates the followinginformation:

• Form Templates Selected: Total number of checked Form Templates fromthe Deploy dialog box, plus those added from data set relationships.

• Form Template and Period frequency do not match: Number of FormTemplates that do not match the DCP frequency. If nonzero, then click ViewDetails to display the form template missing the frequency.

• Total Forms to deploy: Total number of forms specified on each of the formtemplates.

• Errors: Total number of forms with errors. If non-zero, then click View Detailsto display the forms and the reason for the errors. No copying is done.

Un-Deploying a Form Template to a Data Collection PeriodTo un-deploy a form template to a data collection period:



3. Click Un-Deploy .

The Un-Deploy Form Template is displayed.

4. To select another data collection period:

a. Click Search.

The Select Data Collection Period is displayed.

b. Select Year and Scenario.

c. Click Search to refresh the Periods.

d. Select a Period.

e. Click OK.

5. Select the form template for that data collection period.

6. Click Un-Deploy.

A warning message displays: "As a result of un-deployment, all the existing datafor this period and also all forms will be deleted permanently."

7. Select the form templates, and then click Un-Deploy.

Chapter 29Un-Deploying a Form Template to a Data Collection Period

29-29

Re-opening Supplemental Data FormsYou can re-open a deployed Supplemental Data Form to correct data and continueworking with the form.

To re-open a Supplemental Data Form:



3. Click the Actions ellipsis button (...) for the form template, and select Forms.

The system displays a list of associated forms.

4. Click the Actions ellipsis button (...) and then select Re-Open.

This action will reset the workflow status back to Open with Preparer.

Validating Supplemental Data Total Against an AccountBalance

You can validate the supplemental data total against an account balance in FinancialConsolidation and Close. This is useful when you are loading account balances fromvarious General Ledger systems into your consolidation system and use SupplementalData Manager to collect parts or the sum of that account balance. Once collected, thetotal of the supplemental data must match the account balance before a preparer cansubmit the data form.

The POV setup is done during form template definition. The Scenario, Year, Period,and Entity are dynamically added to the fully qualified POV and the account balance isfetched during runtime, for example, during form opening. The advantage is thatvalidation of data is done in real time.

The first step in the validation process is that an administrator sets up the validation ofsupplemental data against the consolidation system through Form Template definition.After that, a Preparer of a form will see the Validation row on the form, and the systemensures that the form will not be submitted until the attribute and the account balancematch.

Setting Up the Validation

To set up the validation:



3. Select a template.

4. In Edit Form Template, select Sections and then select the Column tab.

5. From the Total Validation POV column dropdown, select a cube from the list ofavailable cubes.

6. Specify the POV by clicking on the Member Selector in the Total Validation POVcolumn next to the attribute that you are validating against.

Chapter 29Re-opening Supplemental Data Forms

29-30

Note:

You can only select leaf-level members, not parent members.

Make sure View Only is deselected.

Working with the Form

After you set up the validation and deploy a form, the account balance is displayed inthe Validation row with the POV.

If you try to add data and submit the form, the system checks and will only permit thesubmission if the total of the attribute equals the account balance. For example, if youadd data for Stationery:

If you add a Travel Expense of $100, you will see that the attribute value now matchesthe account balance, and the form is submitted.

Chapter 29Validating Supplemental Data Total Against an Account Balance

29-31

Managing Data Collection WorkflowThe data collection workflow follows this order:

1. Select a Data Collection period by Year, Period, Scenario. Defined in SystemSettings.

2. Deploy the Form Template.

3. Open the period to start the data collection process.

4. The system activates Form Instances based on Start Day offset. Applicable Forminstances are in Open status.

5. Email notifications are sent to preparers.

6. Start data entry.

7. The Prepare, Approve, and Post workflow process continues.

8. Close Period starts; no new form instances are generated. No new data entry isallowed.

9. Data collection that is in progress continues.

10. Lock Period starts; no changes can be made.

11. Data Collection is done for the period.

Working with Supplemental Data in Smart ViewYou can use Oracle Smart View for Office for the data collection process. When youinstall the Smart View Extension for Close and Supplemental Data Management, youcan manage the data collection process and work with supplemental data forms usingthe Supplemental Data menu option in Smart View.

To install the extension, see Getting Started with Oracle Enterprise PerformanceManagement Cloud for Administrators.

After you install the extension and create a connection, you can perform theseSupplemental Data tasks in Smart View:

• View a worklist of the forms that you need to act upon for preparation, approvaland posting

• View the Data Set dashboard that shows supplemental data in Excel throughSmart View

Chapter 29Managing Data Collection Workflow

29-32

• View a list of the Data Sets in the system for which you have View security rights

• Apply filters on the data collected as part of the data collection process.

Any Data Set filters or lists that you previously created for supplemental data areavailable in Smart View.

Security Considerations

• Service Administrators can view all Data Sets regardless of which legal entities arespecified in the data collection.

• Power Users and Users can see all Data Sets for which they are eligible as part ofthe workflow and according to their access roles for the legal entities.

• Users will see only the forms for which they are authorized. Depending on thesecurity role, the available options such as Save Data, Approve, or Reject changeto match the associated role.

Connecting to Smart View

1. From the Home page, select Downloads and download Smart View Extensionfor Close and Supplemental Data Management.

2. In Smart View, create a connection and enter the URL.

3. In the right panel, from Private Connections, select the Supplemental DataManager connection that you created.

4. In the Connection dialog box, enter a user name and password, then clickConnect.

Working with Supplemental Data Forms

1. From the Private Connections list, select the Supplemental Data Managerconnection.

2. Select the Supplemental Data tab and then click Refresh.

3. Expand Worklist.

The system displays a list of applicable forms, depending on your security access,for example:

Expense Form (Preparer Jan 16, 2017) E04 - Jan 2017 Actual

4. From the list of forms, select a form.

You can view or modify forms, answer questions, and enter comments. Forinformation on working with forms, see Working with Supplemental Data ManagerForm Sections.

5. When you are finished, select the appropriate action for the form:

• Save Data

• Submit Data

• Approve

• Reject

• Post Data

Chapter 29Working with Supplemental Data in Smart View

29-33

Working with the Supplemental Data Set Dashboard

1. From the Private Connections list, select the Supplemental Data Managerconnection.

2. Select the Supplemental Data tab and then click Refresh.

3. Expand Data Sets.

The system displays a list of applicable data sets, depending on your securityaccess. The list displays the Data Set name with the data set Year, Period andScenario, for example:

Debt Details DS (2017-Feb-Actual)

4. From the Data Sets list, select a data set and double click to open or view data init, or right-click and select Open.

5. Optional: To apply a filter:

a. From the Data Sets list in the right panel, right-click a data set name.

b. Click Apply Filters.

c. In Select Filter, select a filter from the list and click OK.

6. Optional: To apply a list:

a. From the Data Sets list in the right panel, right-click a data set name.

b. Click Apply List.

c. Select a list and click OK.

7. Optional: To remove filters and lists and reset the Data Set dashboard to thedefault values, right-click a data set name, select Reset, and then click OK.

Using Currency TranslationOften stakeholders in a data collection process in a company are based acrossmultiple geographical regions. The data preparers usually prepare the data in theirlocal currency while submitted data needs to be analyzed in the local currency of theparent company (for example, Headquarters.) Almost always, the final financial reportsare generated in the currency of the parent company. The currency translation featuregives you the capability to translate currency attributes from local to parent currencywithin Supplemental Data Management.

Currency translation uses the following process:

• The system stores the base currency (or default currency) of entity members inSupplemental Data Manager.

• If you are using a multi-currency application, the system also stores Currency RateTypes, and currency rates, using the Exchange Rates member of the Accountdimension in the Rates cube. The Rate Types and Currency Rates are read-onlyin Supplemental Data Manager.

You can select the default currency for Entity members. You then assign currencyattributes for entities. See Selecting Default Currency for Entity Members and SettingUp Currency Attributes for Translation.

Chapter 29Using Currency Translation

29-34

Selecting Default Currency for Entity MembersYou can select the default currency for each member of the Entity Dimension.

To select the default currency:

1. On the Home page, click Application and then click Supplemental Data.


3. In Dimensions, select Entity.

4. From Actions, select Members and Attributes.

5. For each member, select a currency in the Currency attribute. In the Currencydrop down, you will only see the currencies that are enabled in System Settings.

Note:

If you do not make a selection and you have chosen the currency property ofan attribute as Entity currency, translation will not work when forms aredeployed to this particular entity, since it has no currency to inherit.

Setting Up Currency Attributes for TranslationTo use currency translation, you create an attribute which takes in amounts (ormonetary value) in local currency of the entity. In the Edit Attribute dialog, there is aproperty named Currency. If you choose the Entity Currency value for that property,that particular attribute will inherit the currency from the entity to which the formtemplate is being deployed to. You can override it by selecting a different currency thatis displayed.

To demonstrate, here's an example with a simple data set of Employee MealExpenses that inputs meal expense data values manually in the local currency fromentities around the globe. You can choose whether to use the Entity currency oroverride it.

The attributes include: Employee ID, Employee Name, Meal Type, Amount, andAmount in HQ Currency. The goal is to take the Amount and translate into Amount inHQ Currency which is USD (dollars).

Chapter 29Selecting Default Currency for Entity Members

29-35

To translate local currency of input values into HQ currency:

1. On the Home page, click Application and then click Supplemental Data.


3. Select the data set and select Actions, then Edit.

4. From the Attributes tab, select the attribute (for example, Amount which is theinput value for the meal expenses from various teams around the globe), and clickActions, then Edit.

Chapter 29Setting Up Currency Attributes for Translation

29-36

5. In Currency, selecting Entity Currency means that this attribute (Amount) willinherit the currency of the Entity that the form is deployed to, which is "USD"(dollars) in this example.

6. Now look at the calculated attribute, Amount in HQ Currency, that was set upwith Currency in USD (dollars).

7. In Calculations, note how the Translate function has been set up to translate thevalues in "Amount" to USD currency using the "Average" exchange rate type.


29-37

8. Once the data set setup is complete, you can see the translation work in adeployed form. Here's an example showing a form template that has beendeployed to four different entities having four different currencies.

Let's take a look at the Monthly Meal Expenses for India. Once you enter the"Amount", the translated currency value shows up after you Save it. Note that thetranslation is calculated to the HQ currency.


29-38

9. You can also view this in the Data Set dashboard. Note the currency symbol in the"Amount" column and the translated values in the "Amount in HQ Currency"column.


29-39

30Managing Supplemental Data ManagerTeams

Teams are defined and provisioned with Owner, Assignee, and Approver roles. Then,rather than assigning named users these roles on a task, the role is assigned to theTeam. Administrators and Power Users can add, edit, and delete teams.

Adding Teams and Members for Supplemental DataManager

You can create teams specifically for Supplemental Data, for example, for working onSupplemental Data forms. You can then determine which users or teams can claim aform, and from Access, you can assign teams for workflow stages. Each team isassigned a role. By default, the User role is created.

When adding teams, you should maintain unique names for User IDs and teams. Donot add a team that has the same name as a User ID.

To add teams and members for Supplemental Data:


2. Click the Teams tab, and then click New.

3. Enter a Name and Description for the team.

4. Select the Supplemental Data tab.

5. Select User.

6. To add members:

a. From the Members section, click Add.

b. Enter the partial or full First Name, Last Name, or select Search to select thenames.

c. In the Search Results section, select Add, or Add All to add the selections tothe Selected list.

d. Click OK.

7. On the Define Team dialog box, select Primary User to have the tasks default to aClaimed status with that user.

Note:

Other team members can then claim the task.

8. Click OK.

30-1

Importing and Exporting Teams and Members forSupplemental Data Manager

Administrators and Power Users can perform a bulk update of teams and members byexporting a file, making changes and re-importing the file, rather than updating teamsand members individually. When the teams.csv file is exported, it provides a report ofthe teams and the members for each team. You can change the name of thedefault .csv file as required.

You need to perform the following steps:

• Create the export .csv file. See the format in "Supplemental Data Manager TeamFile Format" below.

• You can perform bulk edits for existing teams, or create new teams by editing theteams.csv file.

• Import the information back to the application.

Exporting Teams and Members

To perform a bulk export of Teams and Members:


2. Click the Manage Teams tab.

3. Select a team.

4. Click the Export File icon

5. Click Save to save the teams.csv file. The file provides a listing of all teams andthe members for each team.

Importing Teams and Members

When you import teams, the system merges the Team list. For example, if theapplication has Team 1, Team 2, and Team 3 defined, and the CSV file has Team 2and Team 4 defined, after the import process, Team 2 will be updated and Team 4 willbe added.

Team membership will be replaced by the contents of the CSV file. For example, if theapplication has Team 1 with membership of UserA, UserB, and UserC, and the CSVfile has a membership of UserB and UserD, after the import process, Team 1membership will include UserB and UserD.

To perform a bulk import of Teams and Members:


2. Click the Manage Teams tab.

3. Select a team.

4. Click Import , and complete the following information:

• Under File, browse to the exported .csv file.

Chapter 30Importing and Exporting Teams and Members for Supplemental Data Manager

30-2

• Under Import Type, select one of the following options:

– Click Replace to replace the rows that are in the export .csv file.

– Click Replace All to perform the import as follows:

* If the team exists in both the UI and the .csv file, the import willoverwrite to update the team in the UI.

* If additional teams exist in the UI but not in the .csv file, those teamswill be deleted.

* If additional teams exist in the .csv file but not in the UI, those teamswill be imported.

Caution:

Any entries that are not included in the import file will be deleted.

• Under File Delimiter, select Comma or Tab. The default is comma.

5. Click Import.The import runs, providing statistics on the progress of the import.

6. When the import is complete, verify the results in the Import Teams message boxand then click OK.

Supplemental Data Manager Team File Format

When you create a .csv file to import or export teams, it must use the following format:

CSV Element Required Description

#team Yes List of teams with teamdescription and roles

#team_children No List of team members

Roles No If team has specific roles,allowed values are Yes andNo. Default value is No.

Allowed roles areAdministrator, Power User,User and Viewer.

id Yes Uniquely identifies a team orteam name

Primary_user No Allowed values are Yes andNo. Default value is No ifeither the column or value isnot specified.

A sample CSV file is shown below.

Chapter 30Importing and Exporting Teams and Members for Supplemental Data Manager

30-3

Exporting Supplemental Data Manager UsersAdministrators and Power Users can export a list of users to a CSV file. You cannotimport the list of users, however the user information such as the user login can behelpful in creating a Team import file.

To export a list of Supplemental Data Manager users:


2. Click Manage Users.

3. Click Export to CSV.

4. Click Save to save the export.csv file.

Name User Login Status Teams Description

AppUser1 app1 Available Team1, Team 2 User1

AppUser2 app2 Available Team1 User2

View User1 view1 Available Team3, Team4,Team5

Viewer1

Editing Teams and Members for Supplemental DataManager

To edit teams or members for Supplemental Data:

1. On the Home page, click Tools, and then select Access Control.

2. Click the Teams tab

3. Select a team, and click Edit.

Chapter 30Exporting Supplemental Data Manager Users

30-4

4. Edit the teams and members and select OK.

Deleting Teams and Removing Members for SupplementalData Manager

To delete teams or members for Supplemental Data:



3. To delete teams, select a team, click Delete, and from the confirmationprompt, click Yes.

4. To remove members, double click a team name, and on the Edit Team dialog box,select a member and then click Remove from the Actions drop-down.

5. Click OK.

Chapter 30Deleting Teams and Removing Members for Supplemental Data Manager

30-5

ATask Manager Integrations with EPMCloud Services

If you are using Task Manager and have subscriptions to other EPM Cloud services,you can create connections between services and enable integrations using TaskManager functionality.

Pre-built integrations enable you to perform Task Manager tasks that access otherEPM Cloud functionality.

Pre-built integrations are provided within Task Manager for these EPM Cloud services:


• Planning

• Planning Modules


• Tax Reporting


To learn more about how to set up integrations, see Setting Up an Integration.

To learn more about which pre-built integrations are available, see Pre-Built EPMCloud Integrations.

To learn more about which end user integrations are available, see End UserIntegrations for EPM Cloud.

Setting Up an IntegrationMake sure you have the prerequisites and follow these steps to set up an integrationbetween Task Manager and other EPM Cloud services.

Prerequisites

To create integrations between EPM Cloud services, you need to:

• Obtain a subscription to the EPM Cloud service you want to integrate with.

• Set up connections between Task Manager and other EPM Cloud subscriptions.

To Create the Integration Type and Task Type

To set up the integration and create the Integration Type and Task Type:

1. Create the connection between Task Manager and the other services.

• Name the EPM Connect connection. For example, if integrating with AccountReconciliation (ARCS), a possible Connection Name could be ARCS.

• Specify the connection URL.

A-1

• Specify the user credentials.

For more information about connecting EPM Cloud subscriptions, see "ConnectingEPM Cloud Subscriptions" in the Financial Consolidation and Close or TaxReporting Administrator's Guide.



4. From the Integrations page, click Manage Connections.

5. On Manage Connections, from Actions, select Sync EPM Connections.

A message displays the progress of the synchronization, and the system createsthe Integration Type and Task Type.

See Managing Task Manager Integrations for details on using Integration Types.

Uploading and Downloading Files Within EPM ServicesIn Task Manager, you can use pre-built integration tasks to upload and download fileswithin the system. Using Task Manager integrations, you can automate a data extractfrom one service to import into another service. For example, you can copy data fromFinancial Consolidation and Close and import it into Tax Reporting.

To upload or download files within EPM services:

1. From the Home page, click Application, and then click Task Manager.



4. Select a connection.

5. From the list of pre-built integrations, select to upload or download a file. Forexample, select Copy File from FCCS to copy the file from the current FCCSmachine to a remote machine.

6. For File Name, browse to and select the file that you want to copy.

Appendix AUploading and Downloading Files Within EPM Services

A-2

7. In Save File As, enter a file name (which can be different than the original filename).

8. Optional: For External Directory Name, select the name of a directory.


Pre-Built EPM Cloud IntegrationsThese pre-built integrations are available for EPM Cloud services:


• Planning

• Planning Modules


• Tax Reporting


To use the pre-built EPM Cloud Integrations, you must specify parameters for theintegration. Many parameters for automated integrations are selectable from drop-down lists, which eliminates the need to manually enter values. For example, to run arule or ruleset, you can select from a list of business rules, such as ForceConsolidateor ForceTranslate.

Pre-Built Integrations for Account Reconciliation

Integration Name /Module

Module Description Parameters/ Description

Change PeriodStatus

ReconciliationCompliance

Changes the status of aperiod (Open, Closed,Pending, Locked)

Period: The name of theperiod, such as April 2016

Status: Pending, Open,Closed, Locked

Create Period EndReconciliations


Copies all selectedprofiles to a period andreturns success or failurestatus.

Period:(String):The nameof the period, such asApril 2016

Filter (String): The nameof the filter that matchesthe reconciliation

Import Balances ReconciliationCompliance

Imports balance datausing Data Managementfrom a previously createdData Load definition.


dl_Definition: The name ofa previously saved dataload using the formatDL_name such asDL_test

Appendix APre-Built EPM Cloud Integrations

A-3



Import Pre-MappedBalances


Imports pre-mappedbalances.

Period (String): The nameof the period, such asApril 2016

balanceType (LOV): SUB|SRC for sub system orsource system

currencyBucket:(String):Currency bucket, such asFunctional

file (String): The name ofthe file relative to theinbox, for example,balances.csv. The file hasto be uploaded to ARCSusing EPM Automate orREST API.

Import Pre-MappedTransactions


Imports pre-mappedtransactions for aparticular period.

transactionType: AllowedTransaction Types areBEX (Explained Balance),SRC (Adjustment toSource System), and SUB(Adjustment toSubsystem)

file (String): The name ofthe file relative to theinbox, for example,transactions.csv. The filehas to be uploaded toARCS using EPMAutomate or REST API.

dateFormat: Date Format,such as MM/dd/yyyy,dd/MM/yyyy, dd-MMM-yy,MMM d.yyyy, or All

Import Pre-MappedTransactions

TransactionMatching

Imports a file of pre-mapped transactions intoTransaction Matching.

dataSource: Text ID of thedata source where thetransaction will beimported to

file (String): The name ofthe file relative to theinbox, for example,transactions.csv. The filehas to be uploaded toARCS using EPMAutomate or REST API.

reconciliationType: TextID of the reconciliationtype where thetransaction file will beimported to, such as Bankto GL


A-4



Import Profiles ReconciliationCompliance

Imports profiles for aparticular period.

importType: The importtype. Supported valuesare Replace andReplaceAll

period: The period forwhich to import, such asApril 2016

profileType: The profiletype. Supported valuesare Profiles and Children

file (String): The name ofthe file relative to theinbox, for example,profiles.csv. The file hasto be uploaded to ARCSusing EPM Automate orREST API.

dateFormat: Date Format,such as MM/dd/yyyy,dd/MM/yyyy, dd-MMM-yy,MMM d.yyyy, or All

Import Rates ReconciliationCompliance

Imports rates for aparticular period and ratetype.


rateType: The rate type,such as Accounting

Import Rates(ReconciliationCompliance)

file (String): The name ofthe file relative to theinbox, for example,rates.csv. The file has tobe uploaded to ARCSusing EPM Automate orREST API.

importType: Supportedimport types are Replaceand ReplaceAll

MonitorReconciliations


Monitors list ofreconciliations in ARCS.

periodName (String):name of the period

filter (String): filter stringused to query list ofreconciliations

Run Auto Match TransactionMatching

Runs the auto matchprocess in TransactionMatching.

ReconTypeId: The TextID of the Reconciliationtype to be auto matched


A-5

Pre-Built Integrations for Planning and Planning Modules

Integration Name Description Parameters/ Description

Clear Cube Clears specific data withininput and reporting cubes

jobName: Name of the clearcube job.

Cube Refresh Refreshes the OLAP cube. jobName: Name of the refreshcube job.

Export Data Exports application data into afile using the export datasettings, including file name,specified in a job of typeexport data. The filecontaining the exported data isstored in the repository.

jobName: Name of the exportdata job.

exportFileName: Optional. Filename to which data is to beexported.

Import Data Imports data from a file in therepository into the applicationusing the import data settingsspecified in a job of typeimport data.

jobName: Name of the importdata job.

importFileName: Optional. Filename from which data is to beimported.

Import Metadata Imports metadata from a file inthe repository into theapplication using the importmetadata settings specified ina job of type import metadata.

jobName: The name of abatch defined in importmetadata.

Run Batch Rule Executes a batch of jobs thathave been defined in DataManagement

jobName: The name of thereport to be executed, such asDimension Map For POV(Dimension, Cat, Per) Path

reportFormatType: The fileformat of the report, PDF,XLSX, or HTML

parameters: Can vary in countand values based on thereport

Location: The location of thereport, such asComma_Vision

Run Business Rule Launches a business rule. jobName: The name of abusiness rule exactly as it isdefined

parameters: run time promptsin JSON syntax.

Run Business Rule Set Launches a business rule set.Rule sets with no runtimeprompts or runtime promptswith default values aresupported.

jobName: The name of abusiness rule set exactly as itis defined.

parameters: Run time promptsin JSON syntax


A-6


Run Data Management Report The Data Managementreporting frameworkrepresents a unified solutionthat incorporates source andtarget data, templates, anduser-defined SQL queries.Templates, created in OracleBusiness IntelligencePublisher, consume data inXML format and generatereports dynamically. You canadd SQL queries to extractdata from tables, or couplethem with the reportparameters to extend thedefinition of a standard report.Data Management reports canbe generated as PDF, Excel,Word, or HTML output.


reportFormatType: The fileformat of the report, - PDF,XLSX, or HTML




A-7


Run Data Rule Executes a Data Managementdata load rule based on thestart period and end period,and import or export optionsthat you specify.

jobName: The name of a dataload rule defined in DataManagement.

startPeriod: The first period forwhich data is to be loaded.This period name must bedefined in Data Managementperiod mapping.

endPeriod: The last period forwhich data is to be loaded.This period name must bedefined in Data Managementperiod mapping.

importMode: Determines howthe data is imported into DataManagement.

APPEND to add to the existingrule

POV data in DataManagement

REPLACE to delete the POVdata and replace it with thedata from the file

RECALCULATE to skipimporting the data, but re-process the data with updatedMappings and Logic Accounts.

NONE to skip data import intoData Management stagingtable

exportMode: Determines howthe data is exported into DataManagement.

STORE_DATA to merge thedata in the Data Managementstaging table with the existingOracle Hyperion Planning data

ADD_DATA to add the data inthe Data Management stagingtable to Planning

SUBTRACT_DATA to subtractthe data in the DataManagement staging tablefrom existing Planning data

REPLACE_DATA to clear thePOV data and replace it withdata in the Data Managementstaging table. The data iscleared for Scenario, Version,Year, Period, and Entity

NONE to skip data export fromData Management to Planning

fileName: An optional filename. If you do not specify a


A-8


file name, this API imports thedata contained in the file namespecified in the load data rule.The data file must alreadyreside in the INBOX prior todata rule execution.

Pre-Built Integrations for Financial Consolidation and Close and Tax Reporting


Clear Cube Clears specific data withininput and reporting cubes

jobName: Name of the clearcube job.

Cube Refresh Refreshes the OLAP cube. jobName: Name of the refreshcube job.

Export Data Exports application data into afile using the export datasettings, including file name,specified in a job of typeexport data. The filecontaining the exported data isstored in the repository.

jobName: Name of the exportdata job.

exportFileName: Optional. Filename to which data is to beexported.

Import Data Imports data from a file in therepository into the applicationusing the import data settingsspecified in a job of typeimport data.

jobName: Name of the importdata job.

importFileName: Optional. Filename from which data is to beimported.

Import Metadata Imports metadata from a file inthe repository into theapplication using the importmetadata settings specified ina job of type import metadata.

jobName:The name of a batchdefined in import metadata.



reportFormatType: The fileformat of the report - PDF,XLSX, or HTML



Run As: You must specify thisparameter in the Workflow tab.

Run Business Rule Launches a business rule. jobName: The name of abusiness rule exactly as it isdefined.

parameters: run time promptsin JSON syntax.


A-9


Run Business Rule Set Launches a business rule set.Rule sets with no runtimeprompts or runtime promptswith default values will besupported.

jobName: The name of abusiness rule set exactly as itis defined.

parameters: Run time promptsin JSON syntax

Run Consolidation This task is a utility task to runconsolidation. Task will promptuser to enter parameters forrunning the tasks such asScenario, Year, Period andEntity.

Scenario

Year

Period

Entity: Multiple entities can beadded with comma separator.







A-10




















A-11



Run As: You must specify thisparameter in the Workflow tab.

Run Force Consolidation This task is a utility task to runforce consolidation. The taskwill prompt the user to enterparameters for running thetasks such as Scenario, Year,Period and Entity.

Scenario

Year

Period

Entity: Multiple entities can beadded using a commaseparator.

Run Force Translation This task is a utility task to runforce translation. The task willprompt user to enterparameters for running thetasks such as Scenario, Year,Period and Entity.

Scenario

Year

Period


Run Translation This task is a utility task to runtranslation. The task willprompt user to enterparameters for running thetasks such as Scenario, Year,Period and Entity.

Scenario

Year

Period


Pre-Built Integrations for Profitability and Cost Management


Apply Data Grants Applies data grants for a givenOracle Profitability and CostManagement Cloudapplication. This API submitsa job to create and apply thedata grants in Essbase. ThisAPI removes all existing datagrants in Essbase andrecreates them with the latestinformation from theapplication. It can also beused to repair data grants ifthere are any issues.

None

Deploy ML Cube Deploy or redeploy thecalculation cube for a selectedOracle Profitability and CostManagement Cloudapplication.

isKeepData: Specify whetherto preserve existing data

isReplacecube: Specifywhether to replace existing

comment: Any user comments


A-12


Run ML Calc Run or clear calculations for aselected application. Use withManagement Ledger.

povGroupMember:The POVgroup member for which to runcalculations, such as2015_January_Actual

isClearCalculated: Whether toclear the calculation data, trueor false

subsetStart: Rule Set StartingSequence Number

subsetEnd: Rule Set EndingSequence Number

ruleName: Rule Name for aSINGLE_RULE

ruleSetName: Rule Set Namefor a SINGLE_RULE option

exeType: The execution typespecifies which rules to run;possible values areALL_RULES,RULESET_SUBSET,SINGLE_RULE. Otherparameters are requiredbased on the exeType value.

exeType: ALL_RULESoverrides all other optionssuch as subsetStart,subsetEnd, ruleSetName,ruleName, and so on.

exeType: RULESET_SUBSETconsiders only subsetStartand subsetEnd.

exeType: SINGLE_RULEconsiders only ruleSetNameand ruleName.

comment: Use comment text.

stringDelimiter: String delimiterfor POV group members, suchas an underscore (_).

Clear ML POV Clear model artifacts and datafrom a POV combination forany application.

povGroupMember: The POVgroup member for which to runcalculations, such as2015_January_Actual

isManageRule: Whether toclear the program rule details

isInputData: Whether to clearinput data

IsAllocatedValues: Whether toclear allocated values

stringDelimiter: String delimiterfor POV group members


A-13


Copy ML POV Copy model artifacts and datafrom a Source POVcombination to a DestinationPOV combination for anyapplication. Use withManagement Ledgerapplications.

povs: Included in the path

srcPOVMemberGroup: SourcePOV member group, such as2014_January_Actual

destPOVMemberGroup:Destination POV membergroup, such as2014_March_Actual

isManageRule: Whether tocopy the program rule details

isInputData: Whether to copyinput data

modelViewName: To copy aslice of data from source POVto destination POV

createDestPOV: Whether tocreate the destination POV if itdoes not already exist

stringDelimiter: String delimiterfor POV group members


A-14




















A-15




jobName: The name of abatch defined in DataManagement.






End User Integrations for EPM CloudEnd user integrations allow you to access functionality in other remote EPM Cloudenvironments while using Task Manager. This section lists the available end userintegrations for these EPM Cloud services:


• Planning and Planning Modules

• Financial Consolidation and Close and Tax Reporting


For a description of the remote EPM Cloud functionality, see the documentation forthat EPM Cloud service.

End User Integration Tasks for Account Reconciliation

• Console

• Reconciliation List (Period, Saved List)

• Reports

• Transaction List (Period, Saved List)

Appendix AEnd User Integrations for EPM Cloud

A-16

End User Integrations for Financial Consolidation and Close

• Approvals

• Configure Application

• Enter Form Data (Form)Required parameter is Form (EPM Artifact Type) displayed in drop down list inTask Details dialog.

• Export Data

• Export Metadata

• Export Journal

• Generate Financial ReportRequired parameter is the choice of report from drop down.

• Import Data

• Import Metadata

• Import Journal

• Invalid Intersections Report

• Generate Intercompany Matching Report

• Generate Journal Report

• Manage Approvals

• Manage Dimensions

• Manage Forms

• Manage Journals

• Manage Ownership

• Manage Periods

• Manage Valid Intersections

• Refresh Application

• View Dashboard (Dashboard)Required parameter is Dashboard (EPM Artifact Type) displayed in the drop downlist in the Task Details dialog.

• View Financial Reports

End User Integrations for Tax Reporting

• Approvals

• Configure Application

• Enter Form Data (Form)Required parameter Form (EPM Artifact Type) displayed in drop down list in TaskDetails dialog.

• Export Data

• Export Metadata

• Generate Financial Report


A-17

Required parameter is the choice of report from drop down.

• Import Data

• Import Metadata




• Manage Forms

• Manage Periods


• Refresh Application

• View Dashboard (Dashboard).Required parameter is Dashboard (EPM Artifact Type) displayed in the drop downlist in the Task Details dialog


End User Integrations for Planning and Planning Modules

• Approvals

• Enter Form Data (Form)Required parameter is Form (EPM Artifact Type) displayed in drop down list inTask Details dialog.

• Generate Financial ReportRequired parameter is the choice of report from drop down.




• Manage Rules


• View Dashboard (Dashboard).Required parameter is Dashboard (EPM Artifact Type) displayed in the drop downlist in the Task Details dialog


End User Integrations for Profitability and Cost Management

• Dashboards

• Generate Profitability Report

• Profit Curves (Profit Curve)Required parameter is Profit Curve (EPM Artifact Type) displayed in drop down listin Task Details dialog.

• View Dashboard (Dashboard).Required parameter is Dashboard (EPM Artifact Type) displayed in the drop downlist in the Task Details dialog.

View Report (Report)


A-18

BTask Manager Integrations with Cloud andOn-Premises Applications

This appendix describes how to set up theseTask Manager Integrations:

• Oracle Fusion Cloud Integrations

• On-Premises Integrations

• On-Premises Oracle E-Business Suite Event Monitoring Integrations

Oracle Integration Cloud Service is used to connect securely and exchange messagesbetween applications and services in the Cloud and on-premises. EPM Cloud usesIntegration Cloud as an integration platform forTask Manager to connect to non-EPMCloud services.

The following diagram shows the system and user flow that applies to FinancialConsolidation and Close and Tax Reporting:

End User Integrations for Oracle Fusion CloudTask Manager end user integrations allow you to access functionality in remote Cloudenvironments. This section lists the availableTask Manager end user integrationsavailable for Oracle Fusion Cloud.

For a description of the remote Cloud functionality, see the documentation for thatCloud service.

B-1

End User Integrations for Oracle Fusion Assets

• Asset Balances Reconciliation with General Ledger

• Calculate Depreciation

• Periodic Mass Copy for Tax Books

• Journal Entry Reserve Ledger Report

• Calculate Deferred Depreciation

• Create Assets Accounting

• Asset Cost Summary

• Asset Reserve Summary

• Period Close Exception Report

End User Integrations for Oracle Fusion Cash Management

• Create Accounting

• Subledger Period Close Exceptions Report

• Cash to General Ledger Reconciliation Report

End User Integrations for Oracle Fusion General Ledger

• Import Journals

• AutoPost Journals

• AutoReverse Journals

• Generate Allocation Rules

• General Ledger Trial Balance

• General Ledger Average Trial Balance

• General Ledger Journals Report

• General Ledger Journals Check Report

• General Ledger Journals Day Book Report

• General Ledger Journals Batch Summary Report

• General Ledger Report

• General Ledger Account Analysis for Contra Account Report

• General Ledger Average Balance Audit Account Analysis Report

• Revalue Balances

• Translation

• Extract Payables to General Ledger Reconciliation Data

• Extract Receivables to General Ledger Reconciliation Data

• Create Balance Sheet Closing Journals

• Create Income Statement Closing Journals

• Close General Ledger Periods

Appendix BEnd User Integrations for Oracle Fusion Cloud

B-2

• Open General Ledger Periods

• Transfer Balances to Secondary Ledger

• Transfer Balances Cross Ledgers

• Review Journals Dashboard

• General Ledger Account Analysis Report

• General Ledger Trial Balance Report

End User Integrations for Oracle Fusion Intercompany

• Transfer Intercompany Transactions to General Ledger

• Transfer Intercompany Transactions to Receivables

• Transfer Intercompany Transactions to Payables

• Intercompany Account Details Report

• Intercompany Transaction Summary Report

End User Integrations for Oracle Fusion Payables

• Import Transactions from External Systems

• Import Intercompany Transactions

• Import Expense Reports

• Validate Unvalidated Transactions

• Approve Transactions Requiring Approval

• Update Matured Bills Payable Status

• Apply Missing Conversion Rates

• Create Payables Accounting

• Payables Unaccounted Transactions Report

• Payables Unaccounted Transactions Report with Sweep Option

• Period Close Exceptions Report

• Open Items Revaluation Report

• Period End Reconciliation Reports

• Payables Trial Balance Report


• Create Mass Additions

• Transfer Cost to Cost Management

End User Integrations for Oracle Fusion Receivables

• Import AutoInvoice: Master

• Process Receipts Through Lockbox

• Create Automatic Receipt Batch

• Create Receipts Remittance Batch

• Clear Receipts Automatically


B-3

• Create Late Charge Batch

• Create Automatic Receipt Write-Offs

• Recognition Revenue

• Create Receivables Accounting

• Submit Subledger Period Close Exceptions Report

• Extract Reconciliation Data From Receivables to General Ledger

• Receivables Aging by General Ledger Account Report

• Run Period Close Reports

• Approve or Reject Customer Credits

End User Integrations for Oracle Fusion Tax

• Tax Reconciliation Report

• Tax Reconciliation by Taxable Account Report

Application Token Values for Fusion Integrations

Token Name Token Description

PORT Property used for URL-based integration. Theport used to access General LedgerApplication server. Example: 443. Default portnumber for http is 80 and https is 443

PROTOCOL Property used for URL-based integration. Theweb-based protocol used to access GeneralLedger Application server. Example: https

SERVER Property used for URL-based integration. TheGeneral Ledger Application server. Example:ucf6-abc-fa-ext.oraclecloud.com

PORT_BI Property used for URL-based integration. Theport used to access Oracle Fusion BIFoundations server. Example: 443. Defaultport number for http is 80 and https is 443

PROTOCOL_BI Property used for URL-based integration. Theweb-based protocol used to access OracleFusion BI Foundations server. Example: https

SERVER_BI Property used for URL-based integration. TheOracle Fusion BI Foundations server.Example: ucf6-abc-fa-ext.oraclecloud.com

PORT_ESS Property used for URL-based integration. Theport used to access ESS server. Example:443. Default port number for http is 80 andhttps is 443

PROTOCOL_ESS Property used for URL-based integration. Theweb-based protocol used to access ESSserver. Example: https

SERVER_ESS Property used for URL-based integration.TheESS server. Example: ucf6-abc-fa-ext.oraclecloud.com


B-4

Event Monitoring Integration Tasks for Oracle FusionGeneral Ledger

This section lists the provided Task Manager Integrations for Oracle Fusion GeneralLedger Event Monitoring. These are the events that can be monitored:

Event Monitoring Integration Tasks in Task Manager for Oracle Fusion GeneralLedger Connections

Business Event Description

Accounting Period Closed Signals when a general ledger accountingperiod is closed.

Accounting Period Opened Signals when a general ledger accountingperiod is opened.

Accounting Period Reopened Signals when a general ledger accountingperiod is reopened.

Journal Batch Approved Signals when a journal batch is approved.

Journal Batch Posting Completed Signals when a journal batch is posted

End User Integrations for On-Premises ApplicationsTask Manager end user integrations allow you to access functionality in on-premisesenvironments. This section lists the availableTask Manager end user integrations foron-premises applications.

For a description of the on-premises functionality, see the documentation for thatapplication.

End User Integrations for Financial Management

• Load Data

• Load IC Transactions

• Load Journals

• Manage Documents

• Approve Journals

• Create Journals

• Data Grids

• Extract Data

• Extract ICT

• Extract Journals

• IC Matching Template Report

• Intercompany Match By Account Report

• Intercompany Match By Transaction ID Report

• Intercompany Reports

Appendix BEvent Monitoring Integration Tasks for Oracle Fusion General Ledger

B-5

• Intercompany Transaction Report

• Journal Reports

• Ownership Management

• Post Journals

• Process Control

• Process ICT

• Task List

• Web Data Entry Forms

End User Integrations for Oracle E-Business Suite (EBS)

Accounts Payable Tasks

• Close Payable Period

• Expense Report Import

• Open Next Payable Period

• Payables Approval Workflow

• Review Holds and Release

• Open Interface Import (Payables Open Interface Import)

• Import Intercompany trans (Payables Open Interface Import)

• Validate All unvalidated Invoices (Invoice validation)

• Invoice on Hold Report

• Update Matured Payment Status (Update Matured Bills Payable Status)

• Transfer Journal Entries to GL

• Run Unaccounted Transaction Report (Unaccounted Transactions Report (XML)

• Run Unaccounted Transactions Sweep (Unaccounted Transactions Report (XML)

• Run Unaccounted Transactions Sweep Program (Unaccounted TransactionsReport (XML)

• Invoice Posted Register Report (Payables Posted Invoice Register)

• Payment Posted Register Report (Payables Posted Payment Register)

• Run Payables Trial Balance Report (Accounts Payable Trial Balance)

• Mass Additions Create

• Run Payables Key Indicators Report (Key Indicators Report)

• Run Financial Tax Register (RX-only: Financial Tax Register)

• Run Tax Audit Trail Report

• Run Use Tax Liability Report

• Run Intra-EU VAT Audit Trail Report

• Run Withholding Tax Report (AP Withholding Tax Report)

• Generate Withholding Tax Letters (AP Withholding Tax Letter)

Accounts Receivable Tasks

Appendix BEnd User Integrations for On-Premises Applications

B-6

• Approval Fina; AR Transaction Adjustments

• Create Final AR Transaction Adjustments

• Create Periodic Write-off

• Lock Box Receipts

• Open Subsequent Period Task

• Remove Manual Contingencies on Revenue

• Set Period to Close Pending

• Manually Apply Receipts

• Close Accounts Receivables Period

• Import Order Line Information for Invoice Creation (Autoinvoice Import Program)

• Import Order Line Information for Invoice Creation - Non-Oracle (AutoinvoiceImport Program)

• Run Revenue Recognition (Revenue Recognition)


• Run Unposted AR Items Report (Unposted Items Report)

• Run Receipts Register Report (Applied Receipts Register)

• Create Final Accounting and Transfer to GL (Create Accounting)

• Generate Receivables to GL Reconciliation (AR Reconciliation Report)

• Run Receivables Analytic Reports (Key Indicators Report - Summary)

General Ledger Tasks

• Accounts Receivable Reconciliation

• Generate AutoAllocation to allocate rent expense

• Consolidate financial results to corporate

• Maintain revaluation currency rates

• Review allocation formula for rent expense

• Subledger source journals review

• Generate recurring journal for bad debt accrual

• Open New Accounting Period/Close Accounting Period

• Post subledger source journals

• Review revaluation set for foreign currency holdings

• Reverse prior period accruals

• Run preliminary income statement reports

• Consolidate financial results to corporate

• Run translation to parent currency

• Run preliminary detail trial balance reports (Trial Balance - Detail)

• Run foreign currency journals report (Journals - Entered Currency)


B-7

End User Integrations for Profitability and Cost Management

• Job Library

• Manage Calculation

• Manage Database

• Manage Model Views

• Manage Queries

• Manage Rules

• Model Summary

• Model Validation

• POV Manager

• Rule Balancing

• System Reports

• Trace Allocations

End User Integrations for Calculation Manager

• System View

• Deployment View

End User Integrations for Planning and Budgeting Cloud Workspace

• Application Library

• Dimension Library

• Job Console

• Data Synchronization

End User Integrations for FDM

• Import Data

• Import Journals

• Import Multi-Period Data

End User Integrations for Financial Reporting

• Execute Book

• Execute Report

• Execute Snapshot Book

• Execute Snapshot Report

End User Integrations for Oracle Fusion Assets

• Prepare Source Lines and Submit Post Mass Additions

• Capitalize CIP Assets

• Manage Asset Financial Transactions


B-8

• Manage Asset Assignments

• Retire Assets

• Reinstate Assets

• Manage Mass Financial Transactions

• Manage Mass Retirements

• Manage Mass Transfers

• Asset Balances Reconciliation with General Ledger

• Calculate Depreciation

• Periodic Mass Copy for Tax Books

• Journal Entry Reserve Ledger Report

• Calculate Deferred Depreciation

• Create Assets Accounting

• Asset Cost Summary

• Asset Reserve Summary

• Period Close Exception Report

End User Integrations for Oracle Fusion Cash Management

• Bank Reconciliations


• Subledger Period Close Exceptions Report

• Cash to General Ledger Reconciliation Report

End User Integrations for Oracle Fusion General Ledger

• Import Journals

• AutoPost Journals

• AutoReverse Journals

• General Allocation Rules

• General Ledger Trial Balance

• General Ledger Average Trial Balance

• General Ledger Journals Report

• General Ledger Journals Check Report

• General Ledger Journals Day Book Report

• General Ledger Journals Batch Summary Report

• General Ledger Report

• General Ledger Account Analysis for Contra Account Report

• General Ledger Average Balance Audit Account Analysis Report

• Revalue Balances

• Translation


B-9


• Extract Receivables to General Ledger Reconciliation Data

• Create Balance Sheet Closing Journals

• Create Income Statement Closing Journals

• Close General Ledger Periods

• Open General Ledger Periods

• Transfer Balances to Secondary Ledger

• Transfer Balances Cross Ledgers

• Review Journals Dashboard

• Manage Journals

• Period Close Dashboard

• Financial Reporting Center Work Area

• Launch Workspace for Financial Reports

• Reconcile Payables to General Ledger

• Reconcile Receivables to General Ledger

• Manage General Ledger Accounting Periods

• Create Allocation Rules

• General Ledger Account Analysis Report

• General Ledger General Journals Report

• General Ledger Trial Balance Report

End User Integrations for Oracle Fusion Intercompany

• Intercompany Transactions Work Area

• Manage Intercompany Period Status

• Transfer Intercompany Transactions to General Ledger

• Transfer Intercompany Transactions to Receivables

• Transfer Intercompany Transactions to Payables

• Intercompany Account Details Report

• Intercompany Transaction Summary Report

End User Integrations for Oracle Fusion Payables

• Import Transactions from External Systems

• Import Intercompany Transactions

• Import Expense Reports

• Validate Unvalidated Transactions

• Approve Transactions Requiring Approval

• Update Matured Bills Payable Status

• Apply Missing Conversion Rates


B-10

• Create Payables Accounting

• Payables Unaccounted Transactions Report

• Payables Unaccounted Transactions Report with Sweep Option

• Period Close Exceptions Report

• Open Items Revaluation Report

• Period End Reconciliation Reports

• Payables Trial Balance Report


• Create Mass Additions

• Transfer Cost to Cost Management

• Complete or Cancel Incomplete Payment Process Requests

• Close Payables Period

• Open Next Payables Period

• Review Payables to General Ledger Reconciliation Report

End User Integrations for Oracle Fusion Accounts Receivable

• Import AutoInvoice: Master

• Process Receipts Through Lockbox

• Create Automatic Receipt Batch

• Create Receipts Remittance Batch

• Clear Receipts Automatically

• Create Late Charge Batch

• Create Automatic Receipt Write-Offs

• Recognition Revenue

• Create Receivables Accounting

• Submit Subledger Period Close Exceptions Report

• Extract Reconciliation Data From Receivables to General Ledger

• Receivables Aging by General Ledger Account Report

• Run Period Close Reports

• Approve or Reject Customer Credits

End User Integrations for Oracle Fusion Tax

• Tax Reconciliation Report

• Tax Reconciliation by Taxable Account Report

End User Integrations for Planning

• Business Rules

• Clear Cell Details

• Copy Data


B-11

• Copy Version

• Custom Links

• Data Form

• Data Load Settings

• Manage Currency Conversion

• Manage Data Forms


• Manage Exchange Rates

• Manage Menus

• Manage Process

• Manage Security Filters

• Manage Smart Lists

• Manage Task Lists

• Manage User Variables

• Planning Unit Hierarchy

• Scenario and Version Assignment

• Tasklists

End User Integrations for PeopleSoft 9.0

• Close Period for GL and Subsystems

• Run and Review PS/nVision Reports

• Process Subsystem and External Journals (Journal Generator)

• Enter Any Manual Journals

• Book Expense Accruals

• Enter Any Adjustment Vouchers

• Review/Correct Vouchers with Errors

• Review/Correct Match Exceptions

• Review Incomplete Deposits

• Resolve Pending Item Posting Errors

• Write Off Balances as Appropriate

• Update Doubtful Receivables

• Book Unbilled Revenue Accrual

• Finalize Unprocessed Bills

• Correct Billing Interface Errors

• Reconcile AP Control Accounts to GL

• Review Trial Balance report

• Reconcile AR Control Accounts to GL


B-12

• Reconcile Revenue (Billing) Accounts to GL

• Reconcile Asset Control Accounts to GL

• Review Expense Accruals

• Reconcile Open AP Liability Report to GL

• Review Aged AR Trial Balance

End User Integrations for PeopleSoft 9.1

• Close Period for GL and Subsystems

• Run and Review PS/nVision Reports

• Process Subsystem and External Journals (Journal Generator)

• Enter Any Manual Journals

• Book Expense Accruals

• Enter Any Adjustment Vouchers

• Review/Correct Vouchers with Errors

• Review/Correct Match Exceptions

• Review Incomplete Deposits

• Resolve Pending Item Posting Errors

• Write Off Balances as Appropriate

• Update Doubtful Receivables

• Book Unbilled Revenue Accrual

• Finalize Unprocessed Bills

• Correct Billing Interface Errors

• Reconcile AP Control Accounts to GL

• Review Trial Balance report

• Reconcile AR Control Accounts to GL

• Reconcile Revenue (Billing) Accounts to GL

• Reconcile Asset Control Accounts to GL

• Review Expense Accruals

• Reconcile Open AP Liability Report to GL

• Review Aged AR Trial Balance

Setting Up an IntegrationMake sure you have the prerequisites and follow these steps to set up an integrationbetween Task Manager and an external application.

Prerequisites

To integrate Task Manager with an on-premises application such as E-Business Suite,you need:

Appendix BSetting Up an Integration

B-13

• A subscription to Oracle Integration Cloud Service.

Note:

You need one Integration Cloud instance per FCCS or TRCS instance.

• The on-premises application such as Oracle E-Business Suite (EBS) set up.

1. Subscribe to Oracle Integration Cloud / Oracle Autonomous Integration Cloud. See Integration Cloud Service Documentation for detailed information.

2. Review and complete the pre-requisites for "Use Oracle E-Business SuiteBusiness Events to Trigger Integration Endpoint in Oracle Integration Cloud" forEBS adapter in Oracle Integration Cloud. https://docs.oracle.com/cloud/latest/related-docs/ICEBS/toc.htm

3. In Financial Consolidation and Close or Tax Reporting, from the Home page,select Application, and then click Task Manager.



6. From Manage Connections, under Actions, select Integration CloudConnection.

7. Specify the Integration Cloud connection URL and credentials and click Validate.After validation is successful, click Save. This saves the server and credential ofthe FCCS or TRCS connection.

Note:

Task Manager uses Integration Cloud for all the integrations to externalapplications that are non-EPM Cloud. The external applications can beanother Cloud service or an on-premises application such as E-BusinessSuite. These can be Process Automation or Event Monitoring integrationtypes.

8. Do one of the following depending on whether the EBS connections for GeneralLedger and Account Payable connections are already enabled:

• If the EBS connections for General Ledger and Account Payable is alreadyenabled, click Deploy and then Generate to deploy the correspondingIntegration Cloud integrations to Integration Cloud


B-14


https://docs.oracle.com/cloud/latest/related-docs/ICEBS/toc.htm

https://docs.oracle.com/cloud/latest/related-docs/ICEBS/toc.htm

• If the EBS connections for General Ledger and Account Payable connectionswere not enabled:

a. In Task Manager within Financial Consolidation and Close orTaxReporting , go to Manage Integrations, then from Action menu, selectManage Connections.

b. Select and edit Oracle E-Business Suite - General Ledger. Select theEnabled check box and click OK. Then click Deploy and then Generate.

c. Repeat steps for Oracle E-Business Suite - Account Payable.

The system creates the Integration Task Type and also deploys IntegrationCloud integrations to Integration Cloud service.

Note:

If you are doing this for first time and the connections in IntegrationCloud are not completed, all the Integration Cloud deployments will failduring activation. This is expected. To fix this:

a. Log in to Integration Cloud.

b. Navigate to Connections. You will see two connections namedFCCS and EBS. Optionally use Search.Edit FCCS connection:

• Click Configure Connectivity and enter FCCS url as <FCCSurl>/HyperionPlanning/rest/cmapi/v1

• Click Configure Security and enter the Service Administratorcredential of your FCCS service. Then click Test and then Save.

Note:

The Service administrator user ID should be in the formatspecified in the following link: https://docs.oracle.com/en/cloud/saas/enterprise-performance-management-common/prest/authentication.html

Edit EBS connection:

• Enter connection URL and credentials of your Oracle E-Businesssuite.

• Click Test and then Save.

c. From FCCS, open Task Manager and select Manage Integrations.

d. In Manage Connections, in Actions menu, select IntegrationCloud Connection and click Deploy and then Generate. This timethe deployment should complete without any errors.

9. Verify that the Integration - EBS linking is done properly. You can do this bylogging in to Oracle E-Business Suite as administrator and verify the IntegrationCloud REST service is added as subscriber for Business event. Here's anexample:


B-15

https://docs.oracle.com/en/cloud/saas/enterprise-performance-management-common/prest/authentication.html



Check that the Integration Cloud service was added. For example:

On-Premises Oracle E-Business Suite (EBS) IntegrationThese are theTask Manager Integrations for EBS Event Monitoring:

• EBSJournalApprove

• EBSJournalPost

• EBSJournalPeriodClose

• EBSJournalPeriodOpen

• EBSJournalPeriodReopen

Appendix BOn-Premises Oracle E-Business Suite (EBS) Integration

B-16

• EBSAPJournalPeriodOpenClose

These are the events that can be monitored:

Table B-1 Oracle E-Business Suite Events and Descriptions

Integration Name Event Name Description

Journal Approve Event oracle.apps.gl.Journals.journal.approve

GeneralLedger: JournalApproved

Journal Post Event oracle.apps.gl.Journals.journal.post GeneralLedger: PostingCompleted

Journal Period Close Event oracle.apps.gl.CloseProcess.period.close

GeneralLedger: PeriodClosed

Journal Period Open Event oracle.apps.gl.CloseProcess.period.open

GeneralLedger: PeriodOpened

Journal Period ReopenEvent

oracle.apps.gl.CloseProcess.period.reopen

GeneralLedger: PeriodReopened

Payables Period Open/Close Event

oracle.apps.ap.CloseProcess.period AccountsPayables:Period Open/Close/Reopen

Table B-2 General Ledger Journals Integration Type Parameters

Name Type Required Order Hidden

Batch ID Text Yes 1 N

Table B-3 General Ledger Close Process Period Integration Types Parameters


LedgerID Text Yes 1 N

PeriodName Text Yes 2 N

Table B-4 Accounts Payable Integration Types Parameters


LedgerID Text Yes 1 N

PeriodName Text Yes 2 N

Action Static List Yes 3 N

Verifying Results by Raising Business Events

Once you have configured the EBS Business event system to subscribe to therequired events, you can verify your results by raising business events. The followingsections describe how to run the EBS tasks that raise the events you track.


B-17

General Ledger - Journal Approved

oracle.apps.gl.Journals.journal.approveEBS Steps

1. Log on to EBS.

2. Select General Ledger, and then the Vision Operations (USA) role from the lefttree.

3. Select Journals, and then Enter and wait for Oracle Applications to start.

4. Click No for the “Find records in this folder?” message.

5. On the Find Journals screen, click New Batch.

Window (Vision Operation (USA)) displays.

6. In Batch, enter a unique batch name.

Note:

When you click Save, the cursor needs to be inside the Batch field.

7. Select File and then click Save to save the batch.

Note:

When you save, the cursor needs to be inside the Batch field.

8. Click OK for the “Please enter one or more Journals” message.

9. Click Journals.

10. Enter a unique name in Journal field.

11. Provide Line entries starting with Line 1. Provide debit and credit values for theaccounts.

12. After you finish entering the line values, move the cursor into the Journal field.

13. Navigate to the File menu and click New.

14. Click Yes for “Do you want to save the changes you made?” message.

Note:

By clicking Yes, you will be able to add multiple Journal entries into theBatch.

After you finish the journal entries for the last Journal, move the cursor into theJournal field.

15. Select File and then click Save to save the last journal entry.

16. Focus on the Batch (Vision Operation (USA)) and select Batch field.


B-18

17. Click Help and select Diagnostics, and then Examine.

18. Enter Oracle password:APPS.

19. In Field, enter JE_BATCH_ID and click inside Value to get the unique Journalbatch ID. For example,

• Block: BATCH

• Field: JE_BATCH_ID

• Value: 4776732

Copy this value to Notepad. This batch ID will be used as the value for the BatchID parameter of the Event Monitoring task.

Next Steps in Task Manager

1. Create a new Schedule in Pending state.

2. Create a task for event monitoring task to monitor Journal Approve Event(oracle.apps.gl.Journals.journal.approve).

3. On the Parameters tab, provide a value for Batch ID as the journal batch ID fromEBS.

4. Save the task and set the schedule to Open state.

Next Steps in EBS

1. On Batch (Vision Operation (USA), the Approve button is now enabled for thespecified batch.

2. Click Approve to raise the journal approval event.


1. Wait for the task to be set to Open state. It takes a few minutes to capture the EBSevent.

2. After 2-3 minutes, click Refresh in Task Manager.

Refer to this document for further information on Journal Batch Approval relatedinformation: http://download.oracle.com/docs/cd/A60725_05/html/comnls/us/gl/journa09.htm#t_ja_submit

General Ledger - Journal Post Event

oracle.apps.gl.Journals.journal.postEBS steps

1. Log on to EBS.


3. Select Journals, and then Enter and wait for Oracle Applications to start.

4. Click No for the “Find records in this folder?” message.

5. On the Find Journals screen, click New Batch.

Window (Vision Operation (USA)) displays.

6. In Batch, enter a unique batch name.


B-19

http://download.oracle.com/docs/cd/A60725_05/html/comnls/us/gl/journa09.htm#t_ja_submit

http://download.oracle.com/docs/cd/A60725_05/html/comnls/us/gl/journa09.htm#t_ja_submit

Note:

When you click Save, the cursor needs to be inside the Batch field.

7. Select File and then click Save to save the batch.

Note:

When you save, the cursor needs to be inside the Batch field.

8. Click OK for the “Please enter one or more Journals” message.

9. Click Journals.

10. Enter a unique name in the Journal field.

11. Provide Line entries starting with Line 1. Provide debit and credit values for theaccounts.

12. After you finish entering the line values, move the cursor into the Journal field.

13. Navigate to File and then click New.

14. Click Yes for “Do you want to save the changes you made?” message.

Note:

By clicking Yes, you will be able to add multiple Journal entries into theBatch.

After you finish the journal entries for the last Journal, move the cursor into theJournal field.

15. Select File and then click Save to save the last journal entry.

16. Focus on the Batch (Vision Operation (USA)) and select the Batch field.


18. Enter Oracle password: APPS.

19. In Field, enter JE_BATCH_ID and click inside Value to get the unique Journalbatch ID. For example,

• Block: BATCH

• Field: JE_BATCH_ID

• Value: 4776732

Copy this value to Notepad. This batch ID will be used as the value for the BatchID parameter of the Event Monitoring task.




B-20

2. Create a task for event monitoring task to monitor Journal Approve Event(oracle.apps.gl.Journals.journal.post).

3. On the Parameters tab, provide a value for Batch ID as the journal batch ID fromEBS.

4. Save task and set the schedule to Open state.

Next Steps in EBS

1. On the Batch (Vision Operation (USA)), the Approve button is now enabled for thespecified batch.

2. Click Post to raise the journal approval event.

3. Examine the status of EBS request by selecting the View, then Requests, thenSpecific Requests.

4. Specify the Request ID that was noted earlier.




Refer to this document for further information on Journal Batch Post relatedinformation: http://download.oracle.com/docs/cd/A60725_05/html/comnls/us/gl/conten07.htm#w_conts_post

General Ledger - Journal Period Close

oracle.apps.gl.CloseProcess.period.close

EBS Steps

1. Log on to EBS.


3. Select Open/Close, and then Enter and wait for Oracle Applications to start.

The Find Periods dialog displays.

4. Click Find. The Open and Close Period dialog displays.

5. From the list of displayed periods, choose which one you want to close.

6. Select the Status column for that period.

7. Click Status Options. The status list box opens.

8. Select the Closed status and click OK. Then note the period in Notepad.

9. To save the status, select File and then click Save.



12. Enter Oracle password: APPS.

13. In Field, enter LEDGER_ID and click inside Valueto get the unique Ledger ID. Forexample,

• Block: PREVIOUS


B-21

http://download.oracle.com/docs/cd/A60725_05/html/comnls/us/gl/conten07.htm#w_conts_post

http://download.oracle.com/docs/cd/A60725_05/html/comnls/us/gl/conten07.htm#w_conts_post

• Field:LEDGER_ID

• Value:1

Copy this value to Notepad. This Ledger ID will be used as the value for theLEDGER_ID parameter of the Event Monitoring task.



2. Create a task for event monitoring task to monitor Journal Close Event(oracle.apps.gl.CloseProcess.period.close).

3. On the Parameters tab, provide a value for Ledger ID and Period Name fromEBS. For example: Period Name: Dec-10 and Ledger ID: 1


Next Steps in EBS

1. Close the Open and Close Period dialog.

2. Click OK in the Submit Request Node message box.

3. Examine the status of EBS request by selecting View, then Requests, and thenSpecific Requests.




Refer to this document for more information on General Ledger Periods:

http://docs.oracle.com/cd/A60725_05/html/comnls/us/gl/openper.htm

General Ledger - Journal Period Open

oracle.apps.gl.CloseProcess.period.open

EBS Steps

1. Log on to EBS.





5. From the list of displayed periods, choose which one you want to open.

6. Copy the period you want to open in Notepad.




10. In Field, enter LEDGER_ID and click inside Valueto get the unique Ledger ID. Forexample,


B-22


• Block: PREVIOUS

• Field:LEDGER_ID

• Value:1

Copy this value to Notepad. This Ledger ID will be used as the value fortheLEDGER_ID parameter of the Event Monitoring task.



2. Create a task for an event monitoring task to monitor Journal Period Open Event(oracle.apps.gl.CloseProcess.period.open).



Next Steps in EBS

1. Click Open Period.

2. Select the period to open and click OK to raise the event.



1. Wait for the task to be set to open state. It takes a few minutes to capture the EBSevent.




General Ledger - Journal Period Reopen

oracle.apps.gl.CloseProcess.period.reopen

EBS Steps

1. Log on to EBS.

2. Select General Ledger, and then theVision Operations (USA) role from the lefttree.




5. From the list of displayed periods, choose which one you want to reopen.

6. Copy the period you want to reopen in Notepad.





B-23


10. In Field, enter LEDGER_ID and click inside Value to get the unique Ledger ID.For example,

• Block: PREVIOUS

• Field:LEDGER_ID

• Value:1




2. Create a task for an event monitoring task to monitor Journal Period ReopenEvent (oracle.apps.gl.CloseProcess.period.reopen).


4. Save task and set the schedule to Open state.

Next Steps in EBS

1. Click Open Period.

2. Select the closed period to open and click OK to raise the event.







Account Payables Period Open/Close

oracle.apps.ap.CloseProcess.period

EBS Steps

1. Log on to EBS.

2. Expand Payables, and then the Vision Operations (USA) role from the left tree.

3. Expand Accounting, and select Control Payables Periods. This launches theControl Payables Periods form.

4. Specify the Ledger and Operation Unit. Do not close the Find Payables Periodsdialog. Instead, perform the following steps to identify the Ledger ID value.


6. If requested for credentials, specify the APPS schema credentials. The ExamineFields and Variable Values form displays.

7. In Block, enter PERIOD_QF. In Field, enter SET OF BOOKS, and click insideValue, to get the unique Ledger ID numeric value. For example,


B-24


• Block: PERIOD_QF

• Field:SET OF BOOKS

• Value:1




2. Create a task for an event monitoring task to monitor Payables Period Open/Close Event (oracle.apps.ap.CloseProcess.period).

3. On the Parameters tab, provide a value for Ledger ID, Period Name and Actionfrom EBS. For example, Ledger ID: 1, Period Name: Dec-10 and Action: Closed


Next Steps in EBS

1. Find the period in EBS Control Payables Periods.

2. Click on Period Status column for that period.

3. In Control Statuses form, select the appropriate status.

4. Select File, and then Save to raise the event.




Note:

The EBS implementation raises the events only for Closed and Openstatuses. Permanently Closed status will not raise any event.

Refer to this document for further information on Payables Periods:https://docs.oracle.com/cd/A60725_05/html/comnls/us/ap/ctlperst.htm


B-25

https://docs.oracle.com/cd/A60725_05/html/comnls/us/ap/ctlperst.htm

CFinancial Consolidation and Close BestPractices

Best practices describe effective ways to use a feature. The following table provideslinks to the best practices mentioned in this guide.

Category Best Practice For See this Section

Validating Metadata Validating metadataproperties

Validating Metadata

Creating Alternate Hierarchies Working with sharedhierarchies

Creating Shared Members

Account Dimensions Defining accounts Account Hierarchy Order

Dimension Hierarchies Setting up dimensionhierarchy levels

Working with DimensionHierarchies

Loading Data Importing the data file Loading the Data Import File

Application Database Working with the applicationdatabase

Refreshing the Database

Using Member Formulas Defining or editing memberformulas in the Simplifieddimension editor

Working with MemberFormulas

Configurable Calculations Creating configurablecalculations

Configurable CalculationsBest Practices

Essbase Calc Script Essbase calc script commonsyntax

Working with Essbase CalcScript

Extended DimensionalityApplications

Extended dimensionalityscripting techniques

Best Practices forCalculations in ExtendedDimensionality Applications

Auditing Data Maintaining audit tables Viewing Audit Details

Auditing Tasks Working with audit tables Viewing Task Manager AuditDetails

Monitoring Your Application Monitoring your application tounderstand application usage

Working with Activity Reportsand Access Logs

Managing Applications Deleting an application Removing an Application

On-Demand Rules Creating on-demand rules Best Practices for On-Demand Rules

Consolidation Rule-sets Working with consolidationrule-sets

Creating Consolidation Rule-sets

Supplemental Data ManagerForm Templates

Mapping Supplemental DataManager

Form Template Sections:Mapping Tab

C-1