![Choosing Setup Options
Related Topics
• Setting Up the Calendar and Task Flow Type
Set up the calendar and task flow type for the application. You can set the period
frequency, start and end years, fiscal period, and enable rolling forecasts. Then you can
designate which task flow type to use.
• Setting Up Currencies
Specify the main currency for the application, and establish whether the application
supports multiple currencies.
• Customizing the Cube Names
Specify custom names for the input (block storage) and reporting (aggregate storage)
cubes used in the application.
• Setting Up Custom Dimensions and Metadata
Categorize data values into dimensions. You can create up to 32 user-defined, custom
dimensions.
Setting Up the Calendar and Task Flow Type
Set up the calendar and task flow type for the application. You can set the period frequency,
start and end years, fiscal period, and enable rolling forecasts. Then you can designate which
task flow type to use.
The calendar establishes the application's period frequency, start and end years, first month
of fiscal year (if monthly) or the start date of the first fiscal period (if weekly or quarterly), and
lets you enable a rolling forecast and period duration.
For the fiscal year, set the fiscal year first month and specify whether the fiscal year starts
from the same calendar year or the previous calendar year. You can later set up calculations
based on the calendar year, for example, using formula expressions. When setting up
formulas for an application, consider that formula expressions such as [TPDate] and
[FirstDate] produce different results if the application starts in the same calendar year or
previous calendar year.
On this screen you can also choose a Task Flow Type for the application:
• Task List: Task lists are a classic feature which guides users through the planning
process by listing tasks, instructions, and end dates.
For more information about task lists, see Administering Task Lists.
• EPM Task Manager: This is the default option for new applications. EPM Task Manager
provides centralized monitoring of all tasks and provides a visible, automated, repeatable
system of record for running a application.
For more information about EPM Task Manager, see Administering Tasks with Task
Manager.
Chapter 3
Creating a Planning and Budgeting Cloud Application
3-19](https://image.slidesharecdn.com/epbcsadminguide-231128083734-20a7d52e/85/EPBCS-ADMIN-GUIDE-pdf-60-320.jpg)
![• caret (^)
• ampersand (&)
• asterisk (*)
• parentheses ( )
• hyphen-minus (-)
• plus (+)
• colon (:)
• semicolon (;)
• 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 export
scenarios. Note the following exceptions.
Import and Export Metadata Delimiter Exceptions
Don't use these delimiter characters in metadata import and export files.
Table 6-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 file
contains consolidation properties that use
these characters
angle brackets (< >) Causes an error if a property uses the value
<none>
Chapter 6
Importing and Exporting Data and Metadata
6-18](https://image.slidesharecdn.com/epbcsadminguide-231128083734-20a7d52e/85/EPBCS-ADMIN-GUIDE-pdf-112-320.jpg)
![were accepted for loading (verify actual load with Essbase log files), 0
were rejected.
• The error is noted as an error in the import and export status with the following entry
details:
Category: Data record
Record Index: 2
Message: Unable to load specified data value in Record 2: (aDate:
exampleBadDateValue)
• If multiple casting errors occur, each error is recorded in the same error message:
Unable to load specified data values in Record 2: (aSl: aaaaaaasl1),
(aPercent: cc), (aDate: exampleBadDateValue), (aCurr: bb)
• If the error message count exceeds the maximum limit, it will issue the following
message:
The warning [Unable to load specified data values] message count limit (100)
exceeded: no more warnings of this type will be issued.
Exporting Data
To export data to a file:
1. Click Application, and then click Overview.
2. Click Actions, and then click Export Data.
3. Click Create.
4. On the Export Data page, select the target environment 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. See Uploading and Downloading
Files Using the Inbox/Outbox Explorer.
5. Select the cube.
Note:
The driver/column dimension in the Export Data job definition needs to be
dense.
6. Select the file type:
• 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 that you want
to use in the export file. For a list of supported delimiter characters and 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 dynamic calculation
members during export.
Chapter 6
Importing and Exporting Data and Metadata
6-27](https://image.slidesharecdn.com/epbcsadminguide-231128083734-20a7d52e/85/EPBCS-ADMIN-GUIDE-pdf-121-320.jpg)
![Table 8-1 (Cont.) Member Relationships
Relationship Members Included
Relative Returns a member relative to the specified member at the same
generation with the specified offset.
Examples: Relative("Jan", 4) returns May, which is January plus 4
months in a standard monthly Period dimension; Relative("Jan", -2)
returns Nov, which is January minus 2 months in a standard
monthly Period dimension.
Relative Range Returns all of the members from the starting member to the offset
member when going forward or from the offset member to the
starting member when going backwards.
Examples: RelativeRange("Jan", 4) returns Jan, Feb, Mar, Apr, May;
RelativeRange("Jan", -2) returns Nov, Dec, Jan.
Note:
Member relationships work for any dimension, not just the Period dimension.
We've used the Period dimension in our examples because it's easier to
explain as time is linear.
Using Wildcards in Searches
You can use these wildcard characters to search for members.
Table 8-2 Wildcard Characters
Wildcard Description
? Match any single character
* Match zero or multiple characters. For example, enter "sale*"
to find "Sales" and "Sale" because * includes zero or more
characters after the word "sale."
The default search uses the * wildcard. For example, entering
"cash" searches for "*cash*" and returns "Restricted Cash",
"Cash Equivalents", "Cash", and "Noncash Expenses"
because the word "cash" appears within each matched item.
# Match any single number (0-9)
[list] Match any single character within a specified list of characters.
You can list specific characters to use as wildcard. For
example, enter [plan] to use all the letters within the brackets
as a single wildcard character. You can use the "-" character to
specify a range, such as [A-Z] or [!0-9]. To use the "-" character
as part of the list, enter it at the beginning of the list. For
example, [-@&] uses the characters within the brackets as
wildcard characters.
[!list] Match any single character not found within a specified list of
characters. The "-" character can also be used to indicate a
range, such as [!A-Z] or [!0-9].
Chapter 8
Using Wildcards in Searches
8-6](https://image.slidesharecdn.com/epbcsadminguide-231128083734-20a7d52e/85/EPBCS-ADMIN-GUIDE-pdf-173-320.jpg)
![division before working in the form. The first time you select a variable for a form, you
do it in preferences. Afterward, you can update the variable in preferences or in the
form.
To select user variables for forms:
1. Create the form (see Creating Forms).
2. On Member Selection, click the Variables tab, expand User Variables, and then
select user variables the same way you select members, using the arrows to move
user variables to and from Selected Members.
User variables are displayed for the current dimension. For example, user
variables for the Entity dimension might display as follows:
Division = [User Variable]
When selected, a user variable is preceded by an ampersand. For example:
Idescendants(&Division)
3. Click OK.
Selecting UDAs as Members
You can select members for forms based on a common attribute, which you have
defined as a user-defined attribute (UDA). Before you can associate the UDA with a
form, you must create the UDA. See Working with UDAs.
When you create forms with UDAs, any members that are assigned to the UDA are
dynamically added to the form. For example, if you create a UDA called New Products
and assign this UDA to the new products in the Product dimension hierarchy, the form
will automatically display the new products at runtime.
To select UDAs for forms:
1. Create the form (see Creating Forms).
2. On Member Selection, click the Variables tab, expand the UDAs, and then select
the UDAs the same way you select members, using the arrows to move UDAs to
and from the Selected Members.
UDAs are displayed for the current dimension only. When selected, a UDA is
preceded by UDA. For example:
UDA(New Products)
3. Click OK.
Chapter 8
Selecting UDAs as Members
8-12](https://image.slidesharecdn.com/epbcsadminguide-231128083734-20a7d52e/85/EPBCS-ADMIN-GUIDE-pdf-179-320.jpg)
![• [Schedule Name] Monitor: Available for each schedule that is open and with tasks in
the future. This option checks if any tasks need to be open in a schedule.
• Task Status Update: Background service which executes and monitors the process
automated tasks.
Managing Schedules
A schedule defines a chronologically ordered set of tasks that must be executed for a specific
business process, and is the application of a template into the calendar. For example, you
can apply the Quarterly template as Q1FY19 for the first Quarter, then apply the template
again as Q2FY19 for the second quarter.
The maximum number of schedules that you can create, import, or deploy is 100,000.
Schedules have a status of Pending, Open, Closed, or Locked. You can change the status 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.
• Schedule Owners and Viewers are notified by an email when a Schedule is
deleted.
• An immediate reassignment request notification is sent out to administrators
and schedule owners when an assignee or approver requests a reassignment.
Manually Creating Schedules
To create a schedule, you must be an Administrator or Power User. A Power User can run
Create Schedule on a template or select New from Manage Schedules. You can manually
define a schedule from the Manage Schedules page, or create a schedule from a template.
When you create a schedule from a template, all values are inherited from 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 Application.
2. Click Task Manager.
3. Click the Schedules tab on the left.
4. Click New.
5. Enter schedule information on the schedule tabs:
• Setting Schedule Properties
Chapter 12
Managing Schedules
12-93](https://image.slidesharecdn.com/epbcsadminguide-231128083734-20a7d52e/85/EPBCS-ADMIN-GUIDE-pdf-346-320.jpg)
EPBCS ADMIN GUIDE.pdf
- 1. Oracle® Fusion Cloud EPM Administering Planning E94139-59
- 2. Oracle Fusion Cloud EPM Administering Planning, E94139-59 Copyright © 2001, 2023, Oracle and/or its affiliates. Primary Author: EPM Information Development Team This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license 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 for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf 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 end users are "commercial computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms governing the U.S. Government's use of Oracle cloud services 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 that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle®, Java, and MySQL are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used 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 registered trademark 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 expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible 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.
- 3. Contents Documentation Accessibility Documentation Feedback 1 Creating and Running an EPM Center of Excellence 2 Getting Started About Planning 2-1 Application Features 2-2 Launching the Application 2-3 About the Home Page 2-4 Using Dynamic Tabs in Redwood Experience 2-8 Considerations When Using the Application Interface 2-10 Managing Application Access 2-10 Enabling Access to Application Artifacts On Mobile Devices 2-10 About Cell Formatting 2-11 Copying and Pasting Data Between Microsoft Excel and Application Web Forms 2-11 About Instant Save 2-11 About Autosave 2-11 3 Creating a Planning Application Creating an EPM Cloud Service Application 3-1 EPM Cloud Services 3-1 About EPM Cloud Services 3-2 EPM Standard Cloud Service 3-2 EPM Enterprise Cloud Service 3-4 Creating an EPM Enterprise Cloud Service Application 3-5 Creating an EPM Standard Cloud Service Application 3-8 iii
- 4. What Applications Can I Migrate to EPM Standard Cloud Service and EPM Enterprise Cloud Service? 3-9 Migration Paths for Legacy EPM Cloud Snapshots 3-10 Migration Paths for EPM Standard Cloud Service and EPM Enterprise Cloud Service Snapshots 3-12 Migrating Planning Snapshots 3-12 EPM Cloud URL 3-13 Enabling Strategic Modeling for Custom Applications 3-14 Product Name and Terminology Changes 3-14 Creating a Planning and Budgeting Cloud Application 3-14 About Creating a Planning and Budgeting Cloud Application 3-15 Selecting the Application Type 3-15 Creating a Reporting Application 3-16 Creating a Sample Application 3-17 Creating a Standard Application 3-18 Choosing Setup Options 3-19 Setting Up the Calendar and Task Flow Type 3-19 Setting Up Currencies 3-21 Customizing the Cube Names 3-26 Setting Up Custom Dimensions and Metadata 3-26 Planning and Budgeting Cloud URL 3-27 Taking the Product Tour 3-27 Managing Application Ownership 3-28 4 Creating a FreeForm App Understanding FreeForm 4-1 FreeForm App Sources 4-3 Important Considerations for FreeForm Apps 4-4 Creating a FreeForm Application Type 4-5 Creating a FreeForm App Using an Outline File or Snapshot 4-6 Creating a FreeForm App Using the Application Creation Wizard 4-7 FreeForm Apps FAQ 4-9 5 Setting Up Access Permissions About User and Role Management 5-1 Application Artifacts That Can Be Assigned Permissions 5-1 Types of Access Permissions 5-2 Managing Permissions to Artifacts 5-4 About Assigning Permissions to Artifacts, Rules, and Folders 5-4 Adding, Changing, and Removing Permissions to Artifacts and Folders 5-5 iv
- 5. Adding, Changing, and Removing Permissions to Rules and Rules Folders 5-5 Reporting on Access Permissions 5-6 Working with Access Permissions Reports 5-7 Retrieving Changed Information from Access Control 5-7 6 Managing Applications Application Overview 6-2 Refreshing the Application 6-2 Managing Cubes 6-3 Viewing and Managing Cubes 6-3 Adding Cubes 6-4 Clearing Cubes 6-4 About Clearing Cubes 6-4 Creating Clear Cube Jobs 6-4 Starting and Deleting Clear Cube Jobs 6-6 Scheduling Clear Cube Jobs 6-6 Improving Cube Performance 6-6 Managing Dimensions 6-8 Filtering the Dimension View by Cube 6-9 Creating Dimensions 6-9 Setting User Preferences 6-9 Administering Variables 6-10 Working with Substitution Variables 6-10 About Substitution Variables 6-10 Creating and Assigning Values to Substitution Variables 6-10 Deleting Substitution Variables 6-11 Working with User Variables 6-11 About User Variables 6-12 Creating User Variables 6-12 Managing User Variables 6-13 Setting Limits for User Variables on Forms 6-13 Deleting User Variables 6-14 Viewing Activity Reports 6-14 Importing and Exporting Data and Metadata 6-15 Importing Metadata 6-15 Creating the Metadata Import File 6-15 Loading the Metadata Import File 6-19 Exporting Metadata 6-21 Importing and Exporting Data 6-22 Importing Data 6-23 v
- 6. Driver Member Casting Errors 6-26 Exporting Data 6-27 Viewing Data Import and Export Status 6-29 Importing Exchange Rates for a Simplified Multicurrency Application 6-29 Creating and Refreshing Application Databases 6-30 Creating Application Databases 6-30 Before Refreshing the Database 6-31 Refreshing Application Databases 6-31 Adding an Aggregate Storage Outline to an Application 6-31 About Aggregate Storage 6-32 Process for Adding an Aggregate Storage Database to an Application 6-32 Converting an EPM Standard Cloud Service to EPM Enterprise Cloud Service 6-33 Converting a Planning Application 6-34 Converting to a Standard Application 6-34 Converting a Standard or Reporting Application to an Enterprise Application 6-35 Conversion Considerations 6-36 Removing an Application 6-36 Setting the Daily Maintenance Process Start Time 6-37 Uploading and Downloading Files Using the Inbox/Outbox Explorer 6-38 7 Setting up Strategic Modeling Getting Started Checklist for Strategic Modeling 7-1 Enabling Strategic Modeling in Planning Modules 7-2 Enabling Strategic Modeling for Custom Applications 7-2 Working with Templates 7-2 Creating and Uploading Custom Templates 7-3 Changing the Owner and Access Permissions for Custom Templates 7-3 Creating a Strategic Modeling Model 7-4 Setting Up Model Access Permissions 7-5 About Model Access Permissions 7-6 Specifying Global Access Permissions for All Models 7-8 Specifying Access Permissions for a Model 7-8 Changing a Model's Owner 7-9 Changing Model Properties 7-9 Pushing Data Between Strategic Modeling and Planning 7-9 Using Groovy Business Rules with Strategic Modeling 7-10 Groovy Business Rule Examples 7-10 Pushing Data Between Strategic Modeling and Planning Using Data Maps 7-10 Defining Advanced Data Maps 7-14 Using Microsoft Excel to Define Advanced Data Maps 7-17 vi
- 7. Associating Data Maps with a Model 7-17 Associating Data Maps with a Scenario Rollup 7-18 Defining Strategic Modeling Data Map Options 7-20 Running a Data Map 7-20 Integrating Data Between Strategic Modeling and Financials 7-21 Pushing Data from a Strategic Modeling Model to Multiple Strategic Modeling Models 7-23 Pushing Data from a Strategic Modeling Model to Multiple Strategic Modeling Models Using Data Maps 7-23 Defining Account Configuration 7-24 Running a Data Map 7-26 Associating Model to Model Data Maps to Source Model 7-27 Using Microsoft Excel to Define Model to Model Data Maps 7-27 Pushing Data from a Strategic Modeling Scenario Rollup to a Strategic Modeling Scenario Rollup 7-28 Using Microsoft Excel to Define Scenario Rollup to Scenario Rollup Data Maps 7-29 Managing Metadata with Model Change Management 7-30 Defining Target Models for Model Change Management 7-31 Defining Metadata to Copy with Model Change Management 7-31 Copying Metadata from Source to Target 7-35 Editing or Deleting a Model Change Management Definition 7-35 8 Using the Member Selector Working with Members 8-1 Making Selections 8-1 Member Relationships 8-5 Using Wildcards in Searches 8-6 Selecting Attribute Values as Members 8-7 Selecting Members for Forms 8-9 Selecting Substitution Variables as Members 8-10 Selecting User Variables as Members 8-11 Selecting UDAs as Members 8-12 9 Connecting Environments in EPM Cloud About Connecting EPM Cloud Environments 9-1 Considerations for Migrating EPM Cloud Connections 9-3 Creating, Editing, and Deleting Connections to Other EPM Cloud Environments 9-4 Connecting to External Web Services 9-6 Specifying Advanced Options for External Connections 9-7 Navigating Across EPM Cloud Environments 9-8 Customizing Navigation Flows to Access Other EPM Cloud Environments 9-9 vii
- 8. Grouping Cards from Other EPM Cloud Environments into Clusters 9-9 Configuring Cards with Tabs from Multiple EPM Cloud Environments 9-12 Using Direct URLs to Integrate Connected Environments 9-15 Copying Individual URLs 9-16 Exporting All URLs to a CSV File 9-16 10 Designing Custom Navigation Flows Understanding Navigation Flows 10-1 What Can Be Customized in the Business Process Interface? 10-1 Navigation Flow Customization Categories 10-2 Navigation Flow Permissions 10-2 Predefined Navigation Flows 10-2 Viewing and Working with Navigation Flows 10-3 Navigation Flow Design Best Practices and Naming Considerations 10-4 Creating and Duplicating Navigation Flows 10-4 Editing a Navigation Flow 10-5 Activating and Deactivating Navigation Flows 10-6 Using Validate to Find Missing Artifacts in Navigation Flows 10-7 Resolving Navigation Flows that Display a Warning Icon 10-7 Customizing Labels for Cards, Tabs, and Clusters 10-8 Customizing Icons for Cards and Vertical Tabs 10-9 Hiding and Unhiding Clusters, Cards, and Tabs 10-9 Changing the Display Order of Cards on the Home Page 10-10 Adding Cards 10-10 Adding Tabs to a Tabular Page 10-12 About Using URLs to Embed Third-Party Pages in EPM Cloud Applications 10-14 Removing Navigation Flows, Cards, and Tabs 10-15 Grouping Cards into Clusters 10-16 Reloading a Navigation Flow 10-18 Switching Navigation Flows at Runtime 10-18 11 Editing Dimensions in the Simplified Dimension Editor About Editing Dimensions in the Simplified Dimension Editor 11-1 Dimension Overview 11-2 About Dimensions and Members 11-2 About Sparse and Dense Dimensions 11-2 About Dimension Hierarchies 11-2 About Custom Dimensions 11-3 Aggregation Options 11-3 viii
- 9. Storage Options 11-3 About Entities 11-5 About Accounts 11-6 Account Types 11-6 Saved Assumptions 11-9 Data Type and Exchange Rate Type 11-9 Accounts, Entities, Periods, and Cubes 11-10 Accessing the Simplified Dimension Editor 11-10 Working with the Simplified Dimension Editor Grid 11-11 Switching to Another Dimension 11-11 Customizing the Column Layout 11-11 Viewing Ancestors 11-12 Showing Member Usage in an Application 11-12 Focusing Your Editing 11-13 Finding Members 11-13 Moving Members 11-13 Sorting Members 11-14 Moving Members to Another Hierarchy 11-14 Working with Member Formulas 11-15 Copying Member Names from Microsoft Excel 11-15 Editing Dimension Properties in the Simplified Dimension Editor 11-16 Editing Member Properties in the Simplified Dimension Editor 11-17 Accessing Edit Member Properties 11-17 Adding Members in the Simplified Dimension Editor 11-21 Editing Members in the Simplified Dimension Editor 11-22 Deleting Members in the Simplified Dimension Editor 11-23 Adding Shared Members in the Simplified Dimension Editor 11-24 Assigning Access to Dimension Members 11-25 Adding, Editing, and Removing Access to Members 11-25 About Effective Access Permissions to Shared Members 11-26 Working with Attributes in the Simplified Dimension Editor 11-26 Deleting Attributes in the Simplified Dimension Editor 11-28 Working with UDAs in the Simplified Dimension Editor 11-28 Working with Attribute Values in the Simplified Dimension Editor 11-30 Setting Up Scenarios and Specifying Versions 11-31 Setting Up Scenarios 11-31 About Scenarios 11-31 Creating, Editing, and Deleting Scenarios 11-32 Copying Scenarios 11-33 Specifying Versions 11-34 About Versions 11-34 ix
- 10. Target and Bottom Up Versions 11-35 Creating, Editing, and Deleting Versions 11-35 Viewing Version Types 11-36 12 Administering Tasks with Task Manager Setting Up Task Manager 12-1 Task Manager Terms 12-1 Task Manager Overview 12-2 Sample Task Flows 12-3 Managing Task Manager Views, Lists, and Filters 12-5 Viewing Task Manager Lists 12-5 Working with List Views 12-6 Working with Filters 12-6 Managing Task Manager System Settings 12-9 Managing Global Integration Tokens 12-9 Managing Task Manager Organizational Units 12-11 Managing Holiday Rules for Tasks 12-13 Changing Configuration Settings 12-16 Managing Task Manager Attributes 12-29 Defining Task Manager Attributes 12-30 Defining Calculation Attributes 12-31 Importing List Attributes 12-35 Editing Attributes 12-35 Duplicating Attributes 12-36 Deleting Attributes 12-36 Viewing Attributes 12-36 Searching for Attributes 12-37 Managing Task Types 12-37 Task Types 12-38 Creating Task Types 12-38 Setting Task Type Properties 12-38 Setting Task Type Parameters 12-39 Specifying Task Type Instructions 12-40 Specifying Task Type Questions 12-41 Assigning Task Type Attributes 12-42 Working With Task Type Rules 12-43 Viewing Task Type History 12-45 Editing Task Types 12-46 Viewing Task Types 12-46 Searching for Task Types 12-47 x
- 11. Importing Task Types 12-47 Exporting Task Types 12-48 Deleting Task Types 12-49 Managing Task Templates 12-49 Creating Task Templates 12-49 Setting Template Properties 12-50 Specifying Template Instructions 12-51 Assigning Viewers to Templates 12-52 Applying Template Attributes 12-53 Specifying Day Labels 12-53 Embedding Templates 12-54 Working With Template Rules 12-55 Viewing Template History 12-57 Opening Templates 12-57 Adding Tasks to Templates 12-58 Editing Templates 12-58 Importing Tasks into Templates 12-59 Task Import File Format 12-60 Exporting Tasks to Microsoft Excel 12-63 Reassigning Users in Templates 12-64 Creating Schedules from Templates 12-64 Manually Validating Templates 12-67 Viewing Task Manager Templates 12-68 Searching for Templates 12-69 Deleting Templates 12-69 Managing Tasks 12-70 Creating Tasks 12-70 Setting Task Properties 12-71 Setting Task Parameters 12-72 Specifying Task Instructions 12-73 Selecting the Workflow 12-74 Adding Task Questions 12-76 Setting Task Viewers 12-78 Setting Task Predecessors 12-78 Applying Task Attributes 12-80 Working With Task Rules 12-81 Viewing Task History 12-82 Working with the Task Dialog Box 12-83 Importing and Exporting Tasks 12-84 Editing Tasks 12-85 Adding Attachments 12-86 xi
- 12. Sorting Tasks 12-86 Searching for Tasks 12-86 Moving Tasks 12-87 Cutting, Copying, and Pasting Tasks 12-87 Reopening Tasks 12-88 Submitting Tasks 12-90 Approving or Rejecting Tasks 12-91 Managing Task Reassignments 12-91 Canceling Tasks 12-91 Deleting Tasks 12-92 Managing Services 12-92 Managing Schedules 12-93 Manually Creating Schedules 12-93 Setting Schedule Properties 12-94 Adding Instructions to Schedules 12-95 Assigning Schedule Viewers 12-95 Applying Schedule Attributes 12-96 Adding Day Labels 12-97 Working With Schedule Rules 12-97 Setting Required Task Parameters 12-99 Opening Schedules 12-99 Editing Schedules 12-99 Adding Tasks to Schedules 12-99 Importing Tasks into Schedules 12-100 Updating Tasks in Schedules 12-101 Reassigning Users in Schedules 12-102 Authorizing Process-Automated Tasks 12-103 Setting Schedule Status 12-104 Viewing Schedule History 12-105 Validating Schedules 12-106 Locking Schedules 12-106 Viewing Schedules 12-107 Searching for Schedules 12-107 Deleting Schedules 12-108 Managing Task Manager Integrations 12-108 Managing Integrations with EPM Cloud Services 12-109 Adding Pre-built Integrations within the EPM Cloud 12-110 End User Integrations for EPM Cloud 12-111 Automation Integrations for EPM Cloud 12-114 Copy and Delete Integration Files 12-139 Managing Integrations with Cloud and On-Premises Applications 12-141 xii
- 13. End User Integrations for Oracle Cloud ERP 12-142 Event Monitoring Integrations for Oracle Cloud ERP 12-145 End User Integrations for On-Premises Applications 12-151 Setting Up an Integration 12-159 On-Premises Oracle E-Business Suite (EBS) Integration 12-162 Creating Custom Integrations 12-171 Creating End User Integration 12-172 Creating Custom Process Automation Integrations 12-172 Creating Custom Event Monitoring Integrations 12-175 Working with Integrations 12-178 Creating Integrations 12-178 Viewing Integrations 12-180 Editing Integrations 12-181 Searching for Integrations 12-181 Validating Integrations 12-182 Deleting Integrations 12-182 Managing Connections 12-182 Adding Connections 12-182 Editing Connections 12-183 Deleting Connections 12-184 Managing Alert Types for Task Manager 12-184 Creating Alert Types 12-184 Setting Alert Type Properties 12-185 Specifying Alert Type Instructions 12-187 Selecting the Alert Type Workflow 12-188 Assigning Alert Type Viewers 12-188 Adding Questions for Alert Types 12-189 Applying Alert Type Attributes 12-191 Viewing Alert Type History 12-191 Viewing Alert Types 12-191 Editing Alert Types 12-192 Searching for Alert Types 12-193 Deleting Alert Types 12-193 Using Task Manager Reports 12-193 Generating Custom Reports for Task Manager 12-194 Creating a Task Manager Query 12-195 Creating a Template 12-199 Setting Up a Report Group 12-199 Creating a Report 12-200 Searching and Filtering Queries, Report Groups, or Reports 12-202 Generating the Report 12-202 xiii
- 14. Understanding Reports Security 12-203 Using Task Manager Report Binders 12-204 Generating Report Binders 12-205 Viewing Report Binders 12-205 13 Designing Dashboards The Power of Dashboards 13-1 Creating and Managing Dashboards 13-3 About Dashboard Versions 13-3 Creating and Managing Dashboards 1.0 13-4 Concepts in Designing 1.0 Dashboards 13-4 Creating Dashboards 1.0 13-6 Creating Dashboards Containing Master Forms and Details 13-8 About Your Dashboard's Layout - Version 1.0 13-9 About the Gauge Chart Type 13-9 About the Tile Chart Type 13-12 Customizing Dashboard Colors 13-13 About Global and Local POVs in 1.0 Dashboards 13-14 Dashboard POVs and Valid Intersections 13-16 Creating and Managing Dashboards 2.0 13-16 Concepts in Designing 2.0 Dashboards 13-17 Creating Dashboards 2.0 13-23 About the Geomap Chart Type 13-24 About the Pyramid Chart Type 13-25 About the Waterfall Chart Type 13-26 Using Tables in Dashboards 13-29 About the Gauge Chart Type for Dashboard 2.0 13-30 About the Radar Chart Type for Dashboard 2.0 13-32 About the Combination Chart Type for Dashboard 2.0 13-34 About Global and Local POVs in 2.0 Dashboards 13-36 About Quick Analysis 13-38 14 Designing Infolets About Infolets 14-1 Anatomy of an Infolet 14-3 Determining Infolet Content 14-6 Designing Forms for Infolets 14-7 Designing Charts for Infolets 14-7 Using the Infolets Designer 14-8 xiv
- 15. Creating Infolets 14-10 Working with Infolets 14-11 Customizing the Interface to Access Infolets 14-12 15 Configuring IPM About IPM 15-1 About IPM Insights 15-1 Considerations for IPM Insights 15-5 Configuring IPM Insights 15-7 Considerations for Defining the Slice for Insights 15-10 Configuring Additional Insight Settings 15-10 Running and Scheduling Insights 15-11 Editing, Duplicating, and Deleting Insights 15-12 Bring Your Own ML: About Machine Learning Model Import 15-12 Considerations for Bring Your Own ML 15-14 Importing an ML Model 15-14 Deploying an ML Model to Planners 15-16 16 Setting Up Predictions to Run Automatically with Auto Predict About Auto Predict 16-1 Auto Predict Considerations 16-2 Creating Auto Predictions for Forecasts 16-3 Configuring Advanced Auto Predict Options 16-4 Data Screening Options 16-4 Data Attributes Options 16-5 Methods Options 16-5 Running Auto Predict Predictions 16-6 Editing, Deleting, or Duplicating Auto Predict Prediction Definitions 16-7 Reviewing Detailed Reports for Auto Predict Predictions 16-7 17 Managing Sandboxes About Sandboxes 17-1 Enabling Sandboxes 17-2 Enabling Version Members 17-3 How Sandboxes Work with HSP_View and Version Members 17-3 The HSP_View Dimension 17-4 Sample Formula for the ConsolidatedData Member 17-4 Sandbox Version Members 17-5 Sandbox Implications on Member Formulas 17-5 xv
- 16. What Happens When a Sandbox is Published? 17-6 Managing Sandboxes 17-6 Sandboxes and Other Functionality 17-6 18 Defining Valid Intersections and Cell-Level Security Defining Valid Intersections 18-1 Understanding Valid Intersections 18-1 Valid Intersection Groups 18-2 Valid Intersection Rules 18-2 Anchor and Nonanchor Dimensions 18-3 Valid Intersection Examples 18-3 Redundancy or Overlap in Valid Intersection Rules 18-6 Shared Members and Valid Intersection Rules 18-6 Substitution Variables and Valid Intersection Rules 18-6 Evaluation Order 18-7 Creating Valid Intersections 18-7 Managing Valid Intersections 18-8 Viewing Valid Intersections 18-9 Filtering Valid Intersections 18-10 Importing and Exporting Intersections 18-10 Changing the Valid Intersection Group Evaluation Order 18-12 Disabling and Enabling Valid Intersection Groups 18-13 Editing Details for a Valid Intersection Group 18-13 Duplicating Valid Intersection Groups 18-15 Deleting a Valid Intersection Group 18-15 Suppressing Invalid Data in Forms 18-15 Clearing Invalid Data 18-16 About Invalid Data 18-16 Working With Invalid Intersection Reports 18-16 Clearing Data at Invalid Intersections 18-17 Working with Valid Intersections 18-17 Working with Valid Intersections in Application Forms 18-17 Working with Valid Intersections in Calculation Manager Rule Runtime Prompts 18-19 Defining Cell-Level Security 18-19 Understanding Cell-Level Security 18-19 Creating Cell-Level Security Definitions 18-20 Viewing Cell-Level Security Definitions 18-21 Filtering Cell-Level Security Definitions 18-22 Importing and Exporting Cell-Level Security Definitions 18-23 Testing Cell-Level Security 18-25 xvi
- 17. Reordering the Cell-Level Security Definitions List 18-25 19 Defining Data Maps and Creating File-Based Integrations 20 Managing Jobs How Jobs Save You Time 20-1 Viewing Pending Jobs and Recent Activity 20-1 Scheduling Jobs 20-2 Job Types 20-3 Scheduling Jobs to Run Later 20-5 Scheduling Hourly Jobs 20-7 Editing and Canceling Jobs 20-9 Duplicating Jobs 20-10 Canceling Rules Jobs and Ruleset Jobs 20-11 Downloading Export Files From Your Outbox 20-11 21 Auditing Tasks and Data Auditing Overview 21-1 Enabling Audit Tracking 21-2 Viewing Audit Details 21-3 22 Managing Data Validation Creating and Updating Data Validation Rules 22-1 Formatting Cells and Setting the Promotional Path 22-4 Viewing Data Validation Rules 22-5 Order of Evaluation and Execution for Data Validation Rules 22-6 Conditions Supported by the Rule Builder 22-6 If Condition Values 22-6 Then Condition Values 22-14 Range Condition Values 22-14 Data Validation Conditional Operators 22-15 Data Validation Rule Scenarios 22-16 23 Managing Application and System Settings What Application and System Settings Can I Specify? 23-1 Defining User Variables 23-9 xvii
- 18. Customizing Your Display 23-9 Announcing Upcoming Events 23-11 Specifying Artifact Labels 23-11 Which Artifact Labels Can be Localized? 23-11 Working With the Artifact Labels Grid 23-12 Adding Languages and Defining Localized Artifact Labels 23-13 Exporting and Importing Artifact Labels for Editing 23-14 24 Accessing More Administrative Tasks About the Navigator Menu 24-1 Administering Data Load Settings 24-2 Importing Using Data Management 24-3 Importing Data Using Data Management 24-3 Import Scenario Case 1: Importing Data when Member Names Match 24-3 Import Scenario Case 2: Importing Data when Member Names Do Not Match 24-3 Scheduling Jobs in Data Management 24-7 Drilling Through to Source Data 24-8 For More Information 24-8 Administering Action Menus 24-11 Creating and Updating Action Menus 24-11 Working with Action Menu Items 24-11 Defining Action Menu Items 24-12 Administering Alias Tables 24-17 About Aliases 24-17 About Alias Tables 24-18 Working with Alias Tables 24-18 Specifying a Default Alias Table and Setting Member and Alias Display Options 24-19 Administering Dimensions 24-19 About Dimensions 24-20 Working with Dimension Hierarchies 24-20 Filtering the Dimension View by Cube 24-20 Sorting Members 24-21 Viewing a Member’s Ancestors 24-21 Determining Where Members Are Used in an Application 24-21 About Custom Dimensions, Entities, Accounts, Periods, and Cubes 24-21 Adding or Editing User-Defined Custom Dimensions 24-22 Setting Dimension Properties 24-22 Setting Dimension Density and Order 24-23 Setting the Evaluation Order 24-24 Working with Members 24-24 xviii
- 19. Finding Dimension Members 24-25 About Assigning Access to Members 24-25 Adding or Editing Members 24-25 Deleting Members 24-30 Deleting Parent Members 24-31 Working with Shared Members 24-31 Creating Shared Members 24-32 About Dynamic Members 24-32 Working with Attributes 24-34 Understanding Attribute Data Types 24-35 Deleting Attributes 24-36 Working with Attribute Values 24-37 Creating Attribute Values 24-37 Assigning Attribute Values to Members 24-38 Editing and Deleting Attribute Values 24-38 Customizing Calendars 24-39 Defining How Calendars Roll Up 24-39 Creating and Editing Summary Time Periods 24-39 Deleting Summary Time Periods 24-40 Working with the Years Dimension 24-41 Adding Years to the Calendar 24-41 Editing Year Information 24-42 Renaming Time Periods 24-42 Assigning Aliases to Summary Time Periods 24-42 Editing the BegBalance Member 24-43 Setting Up Currencies 24-43 Enabling Multiple Currencies 24-43 Specifying Exchange Rates 24-51 Setting up Dynamic Time Series Members 24-52 Additional Supported Application Features 24-54 Considerations for Alternate Hierarchies in Period Dimensions 24-55 Working with UDAs 24-55 Working with Member Formulas 24-56 Viewing Details of Formula Validation 24-57 Working with Formula Expressions 24-58 Administering Forms 24-62 About Forms 24-62 Form Components 24-63 Form Design Considerations 24-64 Understanding Implied Sharing in Forms 24-65 Creating Forms 24-66 xix
- 20. Defining the Layout 24-67 About Precision Settings 24-80 Setting Form Precision and Other Options 24-80 Moving Data Using Smart Push 24-81 Creating Asymmetric Rows and Columns 24-81 Adding Formula Rows and Columns 24-82 Defining Form Page and Point of View 24-82 Designing Specific Types of Forms 24-83 Designing Forms for Multiple Currencies 24-83 Designing Forms with Formula Rows and Columns 24-84 Designing Forms with Data Validation 24-84 Designing Forms with Global Assumptions 24-84 Designing Forms for Rolling Forecasts 24-84 Designing Flex Forms 24-88 Working with Forms and Form Components 24-89 Selecting and Opening Forms and Folders 24-89 Previewing Forms 24-90 Printing Form Definitions 24-90 Searching for Forms 24-91 Editing Forms 24-91 Moving, Deleting, and Renaming Forms 24-92 How Cell Formatting in Smart View Persists in Planning 24-92 Managing Forms and Folders 24-93 Creating Folders 24-93 Working with Folders 24-94 Administering Rules 24-94 About Rules 24-95 Adding and Removing Rules in Forms 24-95 Setting Business Rule Properties 24-96 Viewing Rules Usage 24-98 About Runtime Prompts 24-101 Understanding Runtime Prompts 24-101 About Runtime Prompts and Approvals Security 24-105 Designing Secure Runtime Prompts 24-106 Using Groovy Rules 24-107 About Groovy Business Rules 24-107 Java API Reference for Groovy Rules 24-109 Groovy Business Rule Examples 24-109 Groovy Business Rule Tutorial Videos 24-109 Groovy Business Rule Tutorials 24-110 Groovy Rule Business Scenarios 24-112 xx
- 21. Administering Rules Security 24-123 Assigning Access to Rules 24-124 Adding, Editing, and Removing Access to Rules 24-124 Assigning Access to Groovy Templates 24-125 Administering Smart Lists 24-125 Working with Smart Lists 24-125 Synchronizing Smart Lists in Reporting Applications 24-126 Setting Smart List Properties 24-127 Defining Smart List Entries 24-129 Previewing Smart Lists 24-129 Displaying #MISSING with Smart Lists 24-130 Administering Task Lists 24-130 Working with Task Lists 24-131 Adding Instructions to Task Lists 24-131 Adding Tasks to Task Lists 24-131 Editing Task Lists 24-135 Editing Tasks 24-135 Copying and Moving Tasks 24-136 Moving and Reordering Task Lists 24-136 Clearing Task Lists 24-137 Deleting Tasks and Task Lists 24-137 Assigning Access to Task Lists 24-138 Adding Access to Task Lists 24-138 Changing and Removing Access to Task Lists 24-138 Clearing Cell Details 24-139 Copying Data 24-140 Copying Versions of Data 24-142 Administering Application Diagnostics 24-143 About Application Diagnostics 24-143 Assumptions 24-143 How Application Diagnostics Works 24-144 Using Application Diagnostics Graphs 24-144 Launching Application Diagnostics 24-145 Modifying Artifacts for Optimal Performance 24-146 Managing Approvals 24-147 About the Approvals Process 24-147 About Approval Units 24-148 Approvals Process 24-148 Data Validation Rules 24-149 Task Lists 24-149 Setting Up Email for Approvals Notification 24-149 xxi
- 22. Defining the Approvals Process 24-150 Budget Process 24-150 Approval Operations and Data Validations 24-150 Starting and Supporting the Review Process 24-151 Managing Submission Phases with Approval Groups 24-151 Understanding Approval Groups 24-152 Defining Approval Groups 24-152 Approval Group Anchor and Nonanchor Dimensions 24-153 Editing, Duplicating, and Deleting Approval Groups 24-154 Assigning Approval Groups to an Approval Unit Hierarchy 24-154 Printing Approval Unit Annotations 24-156 Creating Approval Status Reports 24-156 Approval Unit Promotional Path 24-158 Modifying the Approval Unit Promotional Path 24-158 Design Considerations for Approval Unit Promotional Path Data Validation Rules 24-161 Managing Approval Unit Hierarchies 24-161 About Approval Unit Hierarchies 24-161 Working with Approval Unit Hierarchies 24-161 Assigning Approval Unit Hierarchy Scenario and Version Combinations 24-174 A Naming Restrictions Naming Restrictions for Applications and Databases A-1 Naming Restrictions for Dimensions, Members, and Aliases A-2 Dimension and Member Names in Calculation Scripts, Report Scripts, Formulas, Filters, and Substitution Variables A-5 Restrictions for User and Group Names A-6 B Form Formula Functions About Form Formula Functions B-1 Working with Formulas B-1 Creating Formulas B-1 Editing Formulas B-2 Deleting Formulas B-2 Formula Functions B-2 Arguments B-4 Numeric Arguments B-4 Row, Column, or Cell Reference Arguments B-4 Property Arguments B-6 Embedded Functions as Arguments B-9 Abs B-9 xxii
- 23. Average B-10 AverageA B-11 Count B-12 CountA B-13 Difference B-14 Eval B-15 IfThen, If B-15 Notes on Conditions B-18 Complex Conditions B-18 Max B-19 Min B-19 Mod B-20 PercentOfTotal B-21 Pi B-22 Product B-22 Random B-23 Round B-23 Sqrt B-24 Sum B-24 Truncate/Trunc B-25 Variance/Var B-26 VariancePercent/VarPer B-28 C Optimizing the Application Optimizing Performance C-1 About Reordering Dimensions C-1 Writing #MISSING Values C-1 Other Performance Optimization Tips C-2 D Understanding Application Artifacts Planning Artifacts D-1 Configuration Artifacts D-1 Essbase Data Artifacts D-2 Global Artifacts D-2 Cube Artifacts D-4 Relational Data Artifacts D-4 Security Artifacts D-5 xxiii
- 24. E Using Smart View to Manage Applications About Managing Applications in Smart View E-1 Installing Smart View and the Admin Extension for Application Management E-2 Controlling the Display of Application Management Options in Smart View E-4 Downloading the Application Templates E-4 Downloading the Template in Smart View E-5 Downloading the Application Template Zip File from the Web Interface E-5 Creating an Application E-6 Working with Artifacts in the Application Template E-7 About Working with Artifacts in the Application Template E-8 Application Definition E-8 Dimension Definition E-12 Attribute Dimension Definition E-18 Data Definition E-19 Substitution Variable Definition E-21 Security Definition E-22 Advanced Settings Definition E-23 Updating an Application in Smart View E-27 Deleting an Application E-28 Planning Admin Extension and Office AutoCorrect E-29 F Using Smart View to Import and Edit Application Metadata About Using Smart View to Work with Application Metadata F-1 Installing Smart View and the Admin Extension for Editing Dimensions F-2 Using Smart View Grids to Import and Edit Application Metadata F-3 About the Smart View Grid F-3 The Smart View Grid and Ribbon Display F-4 Guidelines for Using the Smart View Grid F-5 Default Metadata Dimension Member Properties F-6 Importing Dimensions in Smart View F-8 Importing Dimensions in Smart View for Office F-9 Importing Dimensions in Smart View (Mac and Browser) F-10 Editing Members in Smart View F-12 Adding Application Members in Smart View F-12 Adding Members in Smart View F-13 Guidelines for Adding Members in Smart View F-14 Moving Members in Smart View F-14 Guidelines for Moving Members in Smart View F-15 Working with Attribute Dimensions F-15 Adding Attribute Dimension Members in Smart View F-15 xxiv
- 25. Adding Attribute Dimension Members in Smart View for Office F-15 Adding Attribute Dimension Members in Smart View (Mac and Browser) F-17 Associating Attribute Dimension Members with Dimension Members F-19 Designating Shared Members in Smart View F-21 Refreshing Databases F-21 Refreshing Databases in Smart View for Office F-21 Refreshing Databases in Smart View (Mac and Browser) F-22 Planning Admin Extension and Office AutoCorrect F-24 G Best Practices for Designing Your Application Best Practices for Getting Started G-1 Best Practices for Planning Your Application G-3 Best Practices for Applying Your Design G-5 Best Practices for the Design Walkthrough G-5 H Frequently Asked Questions xxv
- 26. Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup? ctx=acc&id=docacc. Access to Oracle Support Oracle customers that have purchased support have access to electronic support through 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=trs if you are hearing impaired. Documentation Accessibility xxvi
- 27. Documentation Feedback To provide feedback on this documentation, click the feedback button at the bottom of the page in any Oracle Help Center topic. You can also send email to epmdoc_ww@oracle.com. xxvii
- 28. 1 Creating and Running an EPM Center of Excellence A best practice for EPM is to create a CoE (Center of Excellence). An EPM CoE is a unified effort to ensure adoption and best practices. It drives transformation in business processes related to performance management and the use of technology- enabled solutions. Cloud adoption can empower your organization to improve business agility and promote innovative solutions. An EPM CoE oversees your cloud initiative, and it can help protect and maintain your investment and promote effective use. The EPM CoE team: • Ensures cloud adoption, helping your organization get the most out of your Cloud EPM investment • Serves as a steering committee for best practices • Leads EPM-related change management initiatives and drives transformation All customers can benefit from an EPM CoE, including customers who have already implemented EPM. How Do I Get Started? Click to get best practices, guidance, and strategies for your own EPM CoE: Introduction to EPM Center of Excellence. Learn More • Watch the Cloud Customer Connect webinar: Creating and Running a Center of Excellence (CoE) for Cloud EPM • Watch the videos: Overview: EPM Center of Excellence and Creating a Center of Excellence. • See the business benefits and value proposition of an EPM CoE in Creating and Running an EPM Center of Excellence. 1-1
- 29. Chapter 1 1-2
- 30. 2 Getting Started Planning is a budgeting and forecasting solution that integrates financial and operational planning processes and improves forecast accuracy. Related Topics • About Planning The Planning application is a related set of dimensions and dimension members used to meet a set of planning needs. • Application Features Key features in the Planning application enable you to reduce budgeting and planning cycles and improve forecast reliability. • Launching the Application • About the Home Page After you create the business process, the Home page is the launch point for accessing your business process tasks. • Using Dynamic Tabs in Redwood Experience Work on related artifacts within tabs without navigating away from a parent artifact. • Considerations When Using the Application Interface • Managing Application Access About Planning The Planning application is a related set of dimensions and dimension members used to meet a set of planning needs. Each Planning application has its own accounts, entities, scenarios, and other data elements. See this guide for Planning administration tasks, including: • Creating, deleting, and managing a Planning application • Creating forms, task lists, and menus • Managing currency conversions and exchange rates • Identifying the review and approval process, requirements, and participants, and managing the budgeting process Tutorials Tutorials provide instructions with sequenced videos and documentation to help you learn a topic. Your Goal Learn How Get an introduction to Planning. Planning Overview 2-1
- 31. Your Goal Learn How Get an introduction to: • A typical planning process using Planning • Planning, budgeting, and forecasting workflow concepts and tools • The benefits of planning using multiple scenarios • The budget submission process Planning Process Overview Log on to Planning, navigate Planning, and access Planning in Oracle Smart View for Office. Navigating Planning Application Features Key features in the Planning application enable you to reduce budgeting and planning cycles and improve forecast reliability. The application: • Facilitates collaboration, communication, and control across multidivisional global enterprises • Provides a framework for perpetual planning, to manage volatility and frequent planning cycles • Decreases the total cost of ownership through a shorter roll out and implementation phase, and easier maintenance for an application • Enhances decision-making with reporting, analysis, and planning • Promotes modeling with complex business rules and allocations • Integrates with other systems to load data Videos Your Goal Watch This Video Get an introduction to the key features in Planning. Overview: Tour of Planning in EPM Enterprise Cloud Links to topics about the key application features described in the video: • Designing Dashboards • Managing Sandboxes • Editing Dimension Properties in the Simplified Dimension Editor • Using Ad Hoc for Data Entry and Analysis • Defining Valid Intersections • Moving Data from One Cube to Another Cube Using Smart Push in Administering Data Integration for Oracle Enterprise Performance Management Cloud • Using Your Own Excel Formulas in Planning Chapter 2 Application Features 2-2
- 32. Tutorials Tutorials provide instructions with sequenced videos and documentation to help you learn a topic. Your Goal Learn How Learn which options are available for integrating with Planning. Getting Started with Integration for Oracle EPM Cloud Planning Launching the Application This topic describes the unique launch URLs that are used to launch Oracle Enterprise Performance Management Cloud applications. A Service Administrator is responsible for providing the unique URLs to users. Launching EPM Standard Cloud Service and EPM Enterprise Cloud Service Applications Customers provisioned to EPM Standard Cloud Service and EPM Enterprise Cloud Service instances will use URLs similar to the following to access their environments: • Production environment URL: https://epm- idDomain.epm.dataCenter.oraclecloud.com/epmcloud • Test environment URL: https://epm-test- idDomain.epm.dataCenter.oraclecloud.com/epmcloud For example, for EPM Cloud environments provisioned with identity domain exampleDoM in exampleDC data center, the URLs may be as follows: • Production environment: https://epm-exampleDoM.epm.exampleDC.oraclecloud.com/ epmcloud • Test environment: https://epm-test-exampleDoM.epm.exampleDC.oraclecloud.com/ epmcloud This is a change from previous versions of EPM Cloud where each application used a separate context to access environments. See Sample EPM Cloud URLs in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators . Launching a Planning and Budgeting Cloud Application To launch a Planning and Budgeting Cloud application, enter the following URL in a new browser window: https://Oracle PBCS service name/HyperionPlanning; For example: https://testnew1-testnew1.pbcs.us1.oraclecloud.com/HyperionPlanning; Chapter 2 Launching the Application 2-3
- 33. For information about enabling access to application artifacts on mobile devices and for considerations when using the application, see Managing Application Access. About the Home Page After you create the business process, the Home page is the launch point for accessing your business process tasks. The interface provides an intuitive user experience and an overview for quick access to commonly used functions. For example, users can access their tasks, work with data, approve budgets, view reports, and control settings. Service Administrators can manage and customize the business process, create forms, dashboards, and infolets, import and export data and metadata, schedule jobs, define valid intersections, make announcements, and create cross-environment connections. All newly created or re-created Oracle Enterprise Performance Management Cloud services, business processes, and applications use the Redwood Experience as the default theme. You can change the general look and feel of your EPM Cloud environment on the Appearance page. On the Appearance page, you can enable the Redwood Experience or choose a classic theme. Each theme provides different background colors, icon styles, and so on. You can also add a branding logo and background images to the Home page. To change the general look and feel of your environment, see Customizing Your Display. Example Home Page Displaying the Redwood Experience Global Header The global header is the area that stretches across the top of the user interface. It contains navigation icons as well as access to accessibility settings and the Settings and Actions menu. You can also switch between navigation flows from the global header. Parts of the global header from left to right: Chapter 2 About the Home Page 2-4
- 34. Global Header Part Description The Navigator icon opens the Navigator menu, which serves as a sitemap of the business process and displays links to all of the business process pages to which you have access. Note: Some of the links in the Navigator menu are available only if you're accessing the business process from the desktop. Click the Oracle logo to return to the Home page while working elsewhere in the business process. You can display a custom logo instead of the Oracle logo by selecting a Logo Image on the Appearance page. The name of the current business process. You can hide the business process name by selecting No for the Display Business Process Name option on the Appearance page. The Home icon refreshes the Home page or returns you to the Home page while working elsewhere in the business process. Click the Accessibility Settings icon to enable accessibility features. If you belong to multiple groups or if a navigation flow is assigned to a role, click the navigation flow icon to switch navigation flows at runtime. Click your user name to access the Settings and Actions menu. Work Area The work area on the Home page displays either a theme-based background image or a custom background image. The icons that display in the work area link you to each functional area of the business process to which you have access; for example, Financials, Dashboards, Approvals, and Data. The three dots above an icon label denotes that the icon opens a grouping of sub-icons, called a cluster. The Academy icon links you to a variety of resources about using the business process. To replace the theme-based background image in the work area with a custom background image, select Background Image on the Appearance page. Infolet Navigation If your business process uses infolets to show high-level, essential information, you can explore them by clicking the dots that appear beneath the global header. Arrows are also available on the sides of the Home page to help you navigate easily between the Home page and infolet dashboard pages. Chapter 2 About the Home Page 2-5
- 35. Announcements Panel The Announcements Panel displays your user name and profile picture (if set), any system announcements entered by the Service Administrator, and helps you track your activity. Chapter 2 About the Home Page 2-6
- 36. • You can set your profile picture to display at the top of the Announcements panel of the Home page. To set your profile picture, click Tools, and then User Preferences. For more information, see Setting Your Profile Picture in Working with Planning . • Activity: Summarizes system announcements (the most recent announcement, sorted by effective date, appears at the top) and lists your open tasks. Click Announcements to flip the panel and view announcements. Click Tasks Due Today to flip the panel and view your tasks. • Recent: Displays a list of links to recently visited forms and dashboards (up to 15 items). Clicking a link will launch the item in a secondary window. Clicking the star next to a link will tag it as a favorite. • Favorites: Displays a list of links to forms or dashboards that were tagged as favorites, and prevents them from being overwritten. Click a link in Favorites to launch the item in Chapter 2 About the Home Page 2-7
- 37. a secondary window. To add items to Favorites, click Recent to view your recent user activity, and then click the star to the right of the item. • : Click the Tour icon to launch a video about key features in the business process. Videos Your Goal Watch This Video Explore the default Redwood Experience theme. Overview: Announcing EPM Cloud's new Redwood Theme Learn how to customize the interface to streamline workflow. Overview: Customizing Workflow in Enterprise Performance Management Cloud Using Dynamic Tabs in Redwood Experience Work on related artifacts within tabs without navigating away from a parent artifact. About Dynamic Tabs Dynamic tabs enable you to view multiple artifacts on a single page. For example, if you've a form open, you can open other related forms, and dashboards. These additional artifacts are denoted by horizontal tabs at the bottom of the page. This feature is for users who do want to view multiple artifacts simultaneously, but don't want to have multiple browser windows open. The dynamic tabs feature is available only if Redwood Experience is enabled. Note: You can enable Redwood Experience on the Appearance page of your business process. Chapter 2 Using Dynamic Tabs in Redwood Experience 2-8
- 38. Dynamic tabs terminology: • Dynamic Tab: A tab that is added at the bottom of the page to the right of the source tab when a related artifact is launched. Only dynamic tabs will display a close icon. • Source Tab: The page from where the dynamic tab was launched. If your Oracle Enterprise Performance Management Cloud environment includes tabs from another EPM Cloud environment, dynamic tabs are supported for those cross-environment tabs. Considerations When Using Dynamic Tabs • You must enable Redwood Experience to use dynamic tabs. If you're using a theme other than Redwood Experience for your business process, dynamic tabs aren't available. • You can open up to 30 tabs on a page. If you attempt to open more than 30 tabs, you'll see a message prompting you to close a few tabs before opening new tabs. • Long artifact names will appear truncated on tabs. Working with Dynamic Tabs Source and dynamic tabs display at the bottom of the page on which you're working. When you launch a new dynamic tab from an existing tab or listing page, the new tab is added to the right of the existing tab and the focus will move to the newly launched tab. Dynamic tabs are preserved for the current session only. The last tab displayed is retained the next time you access the page within the same session. If you log out and then log back in, if you reload a navigation flow, or if you switch to another navigation flow, dynamic tabs won't be retained. If there is any unsaved data, you'll be prompted to save it before you proceed. Each new action you perform opens a new dynamic tab. For example, you perform a drill through on Form1 and then perform a drill through on Form2, this will open two dynamic tabs. If you perform another drill through on Form1, the action will relaunch the previously opened tab. Artifacts that were launched in dynamic tabs will also be listed in your recent history on the Announcements Panel. Dynamic tabs can also be added to Favorites in the Announcements Panel. Dynamic tabs display a close icon. If there is any unsaved data on a tab, you'll be prompted to save it before closing the tab. After a tab is closed, the focus will move to the tab that's to the left of the closed tab. If you're closing a tab that's not in focus, the focus remains on the tab that's currently in view. To close all dynamic tabs, right-click any horizontal tab displayed at the bottom of the page and click Close All Tabs. Videos Your Goal Watch This Video Learn how to navigate with dynamic tabs to multi-task with different artifacts. With dynamic tabs, you can open related artifacts while keeping the original artifacts open. Navigating with Dynamic Tabs Chapter 2 Using Dynamic Tabs in Redwood Experience 2-9
- 39. Considerations When Using the Application Interface Note the following considerations when using the application interface: • The interface supports only Landscape mode for iPad and Android tablets. • The user experience on tablets is better on iPad than on Android devices. • Oracle recommends using the Safari web browser with iPads and Google Chrome with Android devices. • If you use Windows 10, the interface might appear in a magnified (or zoomed in) state if your scaling isn't set to 100%. Windows 10, by default, might have 125% or 150% scaling. • A PDF viewer is required to view reports on the tablet. Oracle recommends the Adobe PDF viewer, but it can be opened in Kindle or Polaris Office on Android devices or a similar application on the iPad. • For information on copying and pasting data between Microsoft Excel and application web forms, see Copying and Pasting Data Between Microsoft Excel and Application Web Forms. Managing Application Access Related Topics • Enabling Access to Application Artifacts On Mobile Devices • About Cell Formatting • Copying and Pasting Data Between Microsoft Excel and Application Web Forms • About Instant Save • About Autosave Enabling Access to Application Artifacts On Mobile Devices To work with artifacts such as forms, task lists, and business rules on mobile devices, Service Administrators must enable access to those artifacts for users. To enable access to application artifacts on mobile devices: 1. From the Home page, click Navigator , and then under Setup, click Access Simplified Interface. 2. In Access Simplified Interface, click to launch the forms, tasks, and rules selector. 3. In the Selector, select the forms, tasks, and rules you want to enable for mobile device access, and then click OK. 4. Back in Access Simplified Interface, select the Forms, Tasks, and Rules tabs to view the artifacts that are enabled for mobile device access. Chapter 2 Considerations When Using the Application Interface 2-10
- 40. About Cell Formatting You can apply either the formatting saved in Oracle Smart View for Office or the formatting set up in Planning for the form. To select which formatting to apply: 1. In the form, click Actions, and then Apply. 2. Click: • Cell Styles: To use Planning's formatting • Custom Styles: To use the formatting saved in Smart View Copying and Pasting Data Between Microsoft Excel and Application Web Forms To copy and paste data from Microsoft Excel: 1. In Excel, highlight the data in one cell or in a range of cells, and press Ctrl+C to copy the data onto the clipboard. 2. Highlight and select the target cell or cells in the application Web form, and then press Ctrl+V. 3. When the Clipboard helper is displayed, press Ctrl+V again. The data is pasted to the Clipboard helper. 4. Click Paste to paste the data into the application Web form. About Instant Save When users work in forms and they click Save, their new or changed data is saved instantly —without a confirmation message—if the structure of the form hasn't changed. For example, instant save works automatically unless any of these options is selected for the form (because they change the structure of the form): • Suppress missing data • Suppress missing blocks • A business rule is selected to launch on Save (other than the default Calculate Form and Calculate Currencies business rules). About Autosave If the Grid Property option Enable Autosave is selected for a form, when users move out of a cell, their changes are automatically saved, with no prompt or message. Cell values are aggregated to their parents, and the affected cells display with a green background. Also, with this option selected, users can use Ctrl+Z to undo changes. For autosave to work, the following suppress options must be turned off because they change the structure of the form: • Suppress missing data • Suppress missing blocks Chapter 2 Managing Application Access 2-11
- 41. For more information on this option and its dependent option, Run Form Rules on Autosave, see Setting Form Grid Properties. Chapter 2 Managing Application Access 2-12
- 42. 3 Creating a Planning Application Create an application based on your planning needs. Depending on the type of Oracle Enterprise Performance Management Cloud service you've purchased, there are two approaches to creating an application: • EPM Standard Cloud Service or EPM Enterprise Cloud Service application. See Creating an EPM Cloud Service Application. • Planning and Budgeting Cloud application. See Creating a Planning and Budgeting Cloud Application. Creating an EPM Cloud Service Application Create an Oracle Enterprise Performance Management Cloud Service application based on your planning needs. Related Topics • EPM Cloud Services • Creating an EPM Enterprise Cloud Service Application • Creating an EPM Standard Cloud Service Application • What Applications Can I Migrate to EPM Standard Cloud Service and EPM Enterprise Cloud Service? • EPM Cloud URL • Enabling Strategic Modeling for Custom Applications You can enable Strategic Modeling for use with existing Custom and Planning Modules applications. • Product Name and Terminology Changes EPM Cloud Services Oracle has two Oracle Enterprise Performance Management Cloud services: Oracle Enterprise Performance Management Standard Cloud Service (EPM Standard Cloud Service) and Oracle Enterprise Performance Management Enterprise Cloud Service (EPM Enterprise Cloud Service). To create EPM Cloud services applications, read these topics: • About EPM Cloud Services • EPM Standard Cloud Service • EPM Enterprise Cloud Service To create a Planning and Budgeting Cloud application, see Creating a Planning and Budgeting Cloud Application. 3-1
- 43. About EPM Cloud Services EPM Standard Cloud Service and EPM Enterprise Cloud Service provide end-to-end applications to meet the requirements of most organizations and ensure a connected and agile experience across multiple applications: • EPM Standard Cloud Service • EPM Enterprise Cloud Service The applications and features available to you depend on the specific Oracle Enterprise Performance Management Cloud service that you purchased. Generally, the EPM Enterprise Cloud Service includes everything in the EPM Standard Cloud Service as well as additional offerings as illustrated in the following image: Videos Your Goal Watch This Video Learn the differences between EPM Standard Cloud Service and EPM Enterprise Cloud Service. Overview of EPM Standard Cloud Service and EPM Enterprise Cloud Service Learn how to set up Planning in Oracle EPM Standard Cloud and Oracle EPM Enterprise Cloud. Setting Up Planning in Cloud EPM EPM Standard Cloud Service EPM Standard Cloud Service is a suite of business processes, primarily for small and mid-sized businesses, and for businesses with lower complexity requirements to Chapter 3 Creating an EPM Cloud Service Application 3-2
- 44. support planning and budgeting, consolidation and close, account reconciliation, and narrative reporting processes. The following image describes what's available in EPM Standard Cloud Service: Additionally, Data Management, which enables you to integrate data from source systems, is included with EPM Standard Cloud Service. Clients and command line tools, such as Oracle Smart View for Office and EPM Automate Utility, are also included. An EPM Standard Cloud Service instance allows you to deploy and use one of the supported business processes. To deploy another business process, you must request another EPM Standard Cloud Service subscription or remove the current business process. Watch this video to learn more about the value of EPM Standard Cloud Service and EPM Enterprise Cloud Service: Overview of EPM Standard Cloud Service and EPM Enterprise Cloud Service Planning delivers instant value and greater productivity for business planners, analysts, modelers, and decision-makers across all lines of business of an enterprise. Planning is available with: • Capital • Financials • Projects • Workforce • Strategic Modeling With the exception of Strategic Modeling, these are available with preseeded configurable content including dimensions, models, forms, rules, dashboards, infolets, and reports. Strategic Modeling is available with standard and industry templates that can be leveraged to create a customized scenario models with flexible blended scenario business cases. Chapter 3 Creating an EPM Cloud Service Application 3-3
- 45. The Planning business process available in the EPM Standard Cloud Service does not support the following: • Custom application, which allows a high degree of application customization to support business requirements • FreeForm application, which enables you to deploy applications with no dimension requirements and also create applications using Essbase outline files • Use of the Groovy scripting language to create or customize business rules See Overview of Planning (Planning and Budgeting Cloud) in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators . Watch this video for an overview of Planning in EPM Standard Cloud Service: Overview: Planning in EPM Standard Cloud EPM Enterprise Cloud Service EPM Enterprise Cloud Service comprises the full suite of Oracle Enterprise Performance Management Cloud business processes supporting a comprehensive array of activities spanning planning and budgeting, consolidation and close, account reconciliation, profitability and cost management, tax reporting, enterprise data management, and narrative reporting. The following image describes what's available in EPM Enterprise Cloud Service: Chapter 3 Creating an EPM Cloud Service Application 3-4
- 46. Watch this video to learn more about the value of EPM Standard Cloud Service and EPM Enterprise Cloud Service: Overview of EPM Standard Cloud Service and EPM Enterprise Cloud Service An EPM Enterprise Cloud Service instance allows you to deploy and use one of the supported business processes. To deploy another business process, you must request another EPM Enterprise Cloud Service instance or remove the current business process. The business processes that you deploy share the same identity domain to facilitate user management and assigning of roles. Access to resources belonging to a business process is individually controlled for each business process. EPM Enterprise Cloud Service supports custom applications, module-based Planning, and FreeForm applications to deliver instant value and greater productivity for business planners, analysts, modelers, and decision-makers across all lines of business of an enterprise. Custom applications facilitate creation of a streamlined process-driven custom solution. Module-based Planning comes bundled with pre-packaged Capital, Financials, Projects, Strategic Modeling, and Workforce modules. FreeForm applications help you to create an unrestricted free form dimension solution using an Essbase outline file. Additionally, EPM Enterprise Cloud Service supports the use of the Groovy scripting language to customize business rules in Planning. See Overview of Planning (Planning and Budgeting Cloud) in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators . Watch this video for an overview of Planning in EPM Enterprise Cloud Service: Overview: Planning in EPM Enterprise Cloud Creating an EPM Enterprise Cloud Service Application The landing page is your starting point for creating an application and for viewing overview videos that help you get started. Chapter 3 Creating an EPM Cloud Service Application 3-5
- 47. Each subscription to the EPM Enterprise Cloud Service allows you to create one application. Click SELECT under the application description to see available options. About Making Selections to Create an Application The EPM Enterprise Cloud Service landing page presents the applications that you can create. Note: After you initiate the creation of an application, you cannot return to the landing page. If wish to return to the landing page to create a different application, you must first reset your environment to its original state. See Switching to a Different Business Process in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators . You have three options to create an application: • Create a sample application • Create a new application • Use an existing snapshot to create an application These options are displayed on an application-specific landing page similar to the following illustration: Creating a Planning Application On the landing page, click SELECT under Planning to view available options for creating a Planning application. • Create a sample application: Click CREATE to automatically create the Vision sample application, which is a valuable tool to explore the planning and budgeting process. See Creating a Sample Application. • Create a new application: Click START to create a Planning application. You can create a Custom, FreeForm, or Planning Modules application to meet your business needs. – Custom: Supports most planning and budgeting requirements through complex business logic, such as business rules and allocations. Select this option if your requirements would necessitate a high degree of application customization. See Creating a Standard Application. Additionally, when you create an application of type Custom, you have the option to enable Strategic Modeling for use with your application. You do this Chapter 3 Creating an EPM Cloud Service Application 3-6
- 48. by selecting the Strategic Modeling option on the Create Applications: Details screen. You can enable Strategic Modeling for use with your custom applications even if you do not enable it when creating the application. To enable Strategic Modeling for an existing EPM Enterprise Cloud Service custom application. See Enabling Strategic Modeling for Custom Applications. Note: You can create a single currency or multicurrency application. Multicurrency custom applications are created using simplified multicurrency. – Free Form: Supports a FreeForm application and does not require Currency, Entity, Scenario, and Version dimensions and their member hierarchies. FreeForm applications are created using an Essbase outline file (OTL) from an on-premises deployment to import dimensions and members. The outline file name can have a maximum of eight characters because the file name is used to name the cube of the FreeForm application. See Creating a FreeForm App. For information on loading data into a FreeForm application, see Loading Data to a Free Form Application in Administering Data Integration for Oracle Enterprise Performance Management Cloud . – Module: Sets up the cubes required for Capital, Financials, Projects, Workforce and Strategic Modeling. Choose this option to create an application that supports best practices and industry standard functionality. See Creating an Application in Administering Planning Modules . Note: You can create a single currency or multicurrency application. Multicurrency applications are created using simplified multicurrency. • Migrate: Click MIGRATE to create a custom Planning application from a snapshot that you previously uploaded to the environment. See What Applications Can I Migrate to EPM Standard Cloud Service and EPM Enterprise Cloud Service? in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators for prerequisites and snapshot compatibility. Note: You cannot enable Strategic Modeling for your custom application after importing a snapshot created from an application for which Strategic Modeling is not enabled. Strategic Modeling is automatically enabled if the snapshot contains Strategic Modeling artifacts. See these topics in Administering Migration for Oracle Enterprise Performance Management Cloud : – Backing up Artifacts and Application in Administering Migration for Oracle Enterprise Performance Management Cloud Chapter 3 Creating an EPM Cloud Service Application 3-7
- 49. – Uploading Archives to the Service in Administering Migration for Oracle Enterprise Performance Management Cloud – Importing Artifacts and Application from a Snapshot in Administering Migration for Oracle Enterprise Performance Management Cloud Creating an EPM Standard Cloud Service Application The landing page is your starting point for creating an application and for viewing an overview video tour to help you get started. Each subscription to the EPM Standard Cloud Service allows you to create one application. About Making Selections to Create an Application The EPM Standard Cloud Service landing page presents the applications that you can create. Note: After you initiate the creation of an application, you cannot return to the landing page. If wish to return to the landing page to create a different application, you must first reset your environment to its original state. See Switching to a Different Business Process in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators . You have two options to create an application: • Choosing your own settings to create the application • Using an existing snapshot to create the application These options are displayed on an application-specific landing page similar to the following illustration: Chapter 3 Creating an EPM Cloud Service Application 3-8
- 50. Creating a Planning Application On the landing page, click SELECT under Planning to view available options for creating a Planning application. Note: You can have only one custom input cube and one reporting cube in the application. • Create a new application: Click START to create a Module-based Planning application. See Setting Up Your Application in Administering Planning Modules . • Migrate: Click MIGRATE to import a Standard Planning application from a snapshot that you previously uploaded to the environment. See What Applications Can I Migrate to EPM Standard Cloud Service and EPM Enterprise Cloud Service? for prerequisites and snapshot compatibility. See these topics in Administering Migration for Oracle Enterprise Performance Management Cloud : – Backing up Artifacts and Application in Administering Migration for Oracle Enterprise Performance Management Cloud – Uploading Archives to the Service in Administering Migration for Oracle Enterprise Performance Management Cloud – Importing Artifacts and Application from a Snapshot in Administering Migration for Oracle Enterprise Performance Management Cloud What Applications Can I Migrate to EPM Standard Cloud Service and EPM Enterprise Cloud Service? The following applications provide an option to migrate a snapshot to create an application in EPM Standard Cloud Service and EPM Enterprise Cloud Service environments. • Planning • Financial Consolidation and Close • Account Reconciliation • Profitability and Cost Management Chapter 3 Creating an EPM Cloud Service Application 3-9
- 51. • Tax Reporting • Data Management Note: Tax Reporting, Data Management, and Profitability and Cost Management applications are not available in EPM Standard Cloud Service. These Migration Scenarios are Always Supported • You can migrate a EPM Standard Cloud Service or EPM Enterprise Cloud Service application. For example, after creating a snapshot of an EPM Standard Cloud Service application, you recreated the service. You can use the snapshot to recreate the EPM Standard Cloud Service application. • You can migrate a snapshots created in a EPM Standard Cloud Service or EPM Enterprise Cloud Service test environment to a production environment, and conversely. • For legacy environments, migration of snapshots from test to production environments, and conversely, is supported if both environments use the same Essbase version. You can also migrate from a legacy environment that uses Non- Hybrid Essbase to an environment that uses Hybrid Essbase, but not conversely. See About Essbase in EPM Cloud in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators for more information. These Migration Scenarios are Never Supported • Migrating a snapshot from EPM Standard Cloud Service or EPM Enterprise Cloud Service to a legacy environment. • Migrating snapshots taken from environments that use Hybrid Essbase to environments that use Non-Hybrid Essbase. • Migrating a snapshot from EPM Standard Cloud Service, EPM Enterprise Cloud Service or legacy environments to On-premises deployments. Migration Paths for Legacy EPM Cloud Snapshots Legacy snapshot refers to a snapshot taken from an Oracle Enterprise Performance Management Cloud environment that is not an EPM Standard Cloud Service or EPM Enterprise Cloud Service environment. By default, these environments are configured with an Essbase version that does not support hybrid cubes (referred to as Non-hybrid Essbase). Because the following legacy environments allow you to enable Hybrid BSO cubes, they may already be configured with an Essbase version that supports hybrid cubes (referred to as Hybrid Essbase). • Enterprise Planning and Budgeting Cloud • Planning and Budgeting Cloud with Plus One option See About Essbase in EPM Cloud in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators for detailed information on Essbase use in EPM Cloud. Chapter 3 Creating an EPM Cloud Service Application 3-10
- 52. For legacy environments, a self-service operation using the recreate EPM Automate Utility command is available to upgrade Non-Hybrid Essbase to Hybrid Essbase. After upgrading Essbase, you can enable Hybrid BSO cubes in Enterprise Planning and Budgeting Cloud. Note: You can upgrade legacy Planning and Budgeting Cloud environments to use Hybrid Essbase. However, you cannot enable the use of Hybrid BSO cubes in these environments. Table 3-1 Migration Scenarios for Legacy EPM Cloud Snapshots Legacy Snapshot Source Available Migration Paths Unavailable Migration Paths Planning and Budgeting Cloud (Non-Hybrid Essbase) • EPM Enterprise Cloud Service Custom • Legacy Planning and Budgeting Cloud (Non-Hybrid Essbase) • Legacy Planning and Budgeting Cloud (Hybrid Essbase) • EPM Enterprise Cloud Service (Planning Modules, FreeForm) • EPM Standard Cloud Service Planning Planning and Budgeting Cloud with Plus One option (Hybrid or Non- Hybrid Essbase) • EPM Enterprise Cloud Service Planning Modules • Legacy Planning and Budgeting Cloud with Plus One option (Hybrid or Non- Hybrid Essbase) • EPM Standard Cloud Service • EPM Enterprise Cloud Service (FreeForm, Custom) • Legacy Planning and Budgeting Cloud (Non-Hybrid Essbase) Enterprise Planning and Budgeting Cloud (Non- Hybrid Essbase) • Legacy Enterprise Planning and Budgeting Cloud (Non- Hybrid or Hybrid Essbase) • EPM Enterprise Cloud Service (Planning Modules) • EPM Standard Cloud Service • EPM Enterprise Cloud Service (Custom, FreeForm) Enterprise Planning and Budgeting Cloud (Hybrid Essbase) • Legacy Enterprise Planning and Budgeting Cloud (Hybrid Essbase) • EPM Enterprise Cloud Service (Planning Modules) • EPM Standard Cloud Service • EPM Enterprise Cloud Service (Custom, FreeForm) • Legacy Enterprise Planning and Budgeting Cloud (Non- Hybrid Essbase) • *On-Premises 11.2.x Planning • On-Premises 11.1.2.4 Planning • On-Premises 11.1.2.3 Planning *On-Premises 11.2.x Planning that uses Essbase 21c cannot be migrated to EPM Cloud. • EPM Enterprise Cloud Service Custom • Legacy Planning and Budgeting Cloud • EPM Standard Cloud Service • EPM Enterprise Cloud Service (Planning Modules, FreeForm) • Legacy Enterprise Planning and Budgeting Cloud (Non- Hybrid Essbase) Chapter 3 Creating an EPM Cloud Service Application 3-11
- 53. Migration Paths for EPM Standard Cloud Service and EPM Enterprise Cloud Service Snapshots All EPM Standard Cloud Service and EPM Enterprise Cloud Service environments that use Essbase use the newest version of Essbase that is capable of supporting Hybrid Cubes. By default, Custom Planning, Planning Modules, and FreeForm applications use Hybrid BSO cubes. See About Essbase in EPM Cloud in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators . Table 3-2 Migration Scenarios for EPM Standard Cloud Service and EPM Enterprise Cloud Service Snapshots Snapshot Source Available Migration Paths Unavailable Migration Paths EPM Standard Cloud Service Planning • EPM Standard Cloud Service Planning • EPM Enterprise Cloud Service Planning Modules • EPM Enterprise Cloud Service (FreeForm, Custom) • Legacy Planning and Budgeting Cloud • Legacy Enterprise Planning and Budgeting Cloud EPM Enterprise Cloud Service Custom Planning EPM Enterprise Cloud Service Custom Planning • EPM Enterprise Cloud Service • EPM Enterprise Cloud Service (FreeForm, Planning Modules) • Legacy environments (including those using Hybrid Essbase) EPM Enterprise Cloud Service Planning Modules EPM Enterprise Cloud Service Planning Modules • EPM Standard Cloud Service • EPM Enterprise Cloud Service (Custom, FreeForm) • Legacy environments (including those using Hybrid Essbase) EPM Enterprise Cloud Service FreeForm EPM Enterprise Cloud Service FreeForm • EPM Standard Cloud Service • EPM Enterprise Cloud Service (Custom, Planning Modules) • Legacy environments (including those using Hybrid Essbase) Migrating Planning Snapshots These Planning migration scenarios are supported. Chapter 3 Creating an EPM Cloud Service Application 3-12
- 54. Note: • Legacy application refers to an application from the newest update of a non- EPM Enterprise Cloud Service or EPM Standard Cloud Service subscription. • Migration of applications from legacy Planning and Budgeting Cloud, Enterprise Planning and Budgeting Cloud, and Planning and Budgeting Cloud with Plus One option creates standard BSO cubes, which you may convert to Hybrid cubes. • For instructions on migrating on-premises Planning applications to Oracle Enterprise Performance Management Cloud, see Migrating On-Premises Applications to EPM Cloud in Administering Migration for Oracle Enterprise Performance Management Cloud. Note: Attempts to import Groovy-based business rules and templates into a business process that does not support Groovy will fail. For example, EPM Standard Cloud Service planning and financial consolidation and close business processes do not support Groovy-based business rules. Import of business rules and templates exported from an application that supports Groovy, for example, from an EPM Enterprise Cloud Service Planning business process, into EPM Standard Cloud Service Planning business process will fail. EPM Cloud URL Customers provisioned to EPM Standard Cloud Service and EPM Enterprise Cloud Service instances will use URLs similar to the following to access their environments: • Production environment URL: https://epm- idDomain.epm.dataCenter.oraclecloud.com/epmcloud • Test environment URL: https://epm-test- idDomain.epm.dataCenter.oraclecloud.com/epmcloud For example, for Oracle Enterprise Performance Management Cloud environments provisioned with identity domain exampleDoM in exampleDC data center, the URLs may be as follows: • Production environment: https://epm-exampleDoM.epm.exampleDC.oraclecloud.com/ epmcloud • Test environment: https://epm-test-exampleDoM.epm.exampleDC.oraclecloud.com/ epmcloud A Service Administrator is responsible for providing the unique URLs to users. This is a change from previous versions of EPM Cloud where each application used a separate context to access environments. See Sample EPM Cloud URLs in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators . Chapter 3 Creating an EPM Cloud Service Application 3-13
- 55. Enabling Strategic Modeling for Custom Applications You can enable Strategic Modeling for use with existing Custom and Planning Modules applications. To enable Strategic Modeling for an EPM Enterprise Cloud Service Custom application: 1. Sign into the Custom or Planning Modules application as a Service Administrator. 2. Click Application and then Overview. 3. From Actions, select Enable Strategic Modeling. 4. If you are using navigation flows, complete a step to activate Strategic Modeling artifacts: • Reload Navigation Flows. • Sign out and then sign in again. To enable Strategic Modeling in a Planning Modules application, see Enabling Strategic Modeling in Planning Modules. Product Name and Terminology Changes EPM Standard Cloud Service and EPM Enterprise Cloud Service have introduced some product name and terminology changes which may not be reflected in the user assistance collaterals, such as guides, learning paths, videos, screen shots, and online help. Table 3-3 Product Name and Terminology Changes Old Terminology New Terminology Planning and Budgeting Cloud Planning Enterprise Planning and Budgeting Cloud Planning Enterprise Planning and Budgeting Cloud business processes; for example, Workforce Planning Modules Enterprise Performance Reporting Cloud Narrative Reporting Cloud Service Business process Creating a Planning and Budgeting Cloud Application Create a Planning and Budgeting Cloud application based on your planning needs. Related Topics • About Creating a Planning and Budgeting Cloud Application • Selecting the Application Type • Creating a Reporting Application • Creating a Sample Application • Creating a Standard Application Chapter 3 Creating a Planning and Budgeting Cloud Application 3-14
- 56. • Choosing Setup Options • Planning and Budgeting Cloud URL • Taking the Product Tour About Creating a Planning and Budgeting Cloud Application Before you create your Planning and Budgeting Cloud application, we've provided some guidelines and best practices to help you determine your requirements and design your application so that it meets your business needs: • See Best Practices for Designing Your Application. • Click Take a quick tour. For more information, see Taking the Product Tour. To create an application: 1. Log in and select Start under Finance, and then select Planning & Budgeting. 2. Select the type of application you want to create. See Selecting the Application Type. • Creating a Reporting Application • Creating a Sample Application • Creating a Standard Application • Choosing Setup Options Videos Your Goal Watch This Video Learn how to create a Planning and Budgeting Cloud application. Creating Planning Applications in Oracle Planning and Budgeting Cloud Tutorials Tutorials provide instructions with sequenced videos and documentation to help you learn a topic. Your Goal Learn How Get an introduction to the Oracle Enterprise Performance Management Cloud Services, instances, business processes, and features, and to learn how to create Planning business processes in EPM Cloud Service: Standard and Enterprise subscriptions. Creating the Planning Business Process Selecting the Application Type Select an application type: • Standard: Builds advanced applications for any business process. Select from two options: – Sample: Quickly and automatically creates a demo application using the sample Vision application that's provided. See Creating a Sample Application. Chapter 3 Creating a Planning and Budgeting Cloud Application 3-15
- 57. – New: Builds an advanced custom application. See Creating a Standard Application. • Enterprise: Builds custom applications or uses predefined business processes to create applications for Financials, Workforce, Capital, and Projects. You can also build a Strategic Modeling solution. See Administering Planning Modules . Note: Only customers who purchase an Enterprise PBCS license or a PBCS Plus One Business Process option license can select the Enterprise application type. See Frequently Asked Questions for an explanation of the PBCS Plus One Business Process option license. • Reporting: Builds a basic application that you can expand over time. See Creating a Reporting Application. Creating a Reporting Application A Reporting application is a basic application with one cube and the core components that you need to get up and running quickly. If you later decide that you need more complex business logic, you can convert a Reporting application into a Standard or Enterprise application. A Reporting application: • Consists of one cube • Allows you to add more dimensions • Allows MDX member formulas only • Doesn't support business rules, map reporting, copy data, copy versions, exchange rates, or currency conversion • Can be converted into a Standard or Enterprise application Note: – To convert a Reporting application into a Standard application, see Converting to a Standard Application. – To convert a Reporting application into an Enterprise application, see Converting a Standard or Reporting Application to an Enterprise Application. Default dimensions and characteristics for a Reporting application: • Account: Only the root member is provided. • Entity: Only the root member is provided. • Period: Members are created based on the answers provided during setup. Users can add an alternate hierarchy later. The Beginning Balance and Year Total periods are provided. Chapter 3 Creating a Planning and Budgeting Cloud Application 3-16
- 58. • Years: Number of years, history, and future years are broken up based on the values chosen during application creation. An All Year parent is provided. More years can be added later. The default number of years is 10. • Scenario: Five scenarios are provided: Plan, Actual, Forecast, Variance, and Variance Comments. • Version: Three versions are provided: Base, What If, and Final. Hierarchical versions are allowed, for example, Base (child member)+What If (child member)=Final (parent member). Note: Generic members aren't added to the dimensions. To create a Reporting application: 1. Click Reporting. 2. Name your application and enter a description. Note: Ensure that you adhere to the application naming restrictions outlined in Naming Restrictions. 3. The application provides setup options that you can select to help you create the initial framework for your planning process. If you need help deciding which options to choose, see Choosing Setup Options. 4. Review the summary screen, and, if the selections you made are correct, click Create. After you create the application, populate it by performing these steps: • Import metadata using the import feature. See Importing Metadata. • Populate data by importing data from your source system. See Importing and Exporting Data. Creating a Sample Application Planning provides a Sample application, called Vision, that lets you quickly create an application with artifacts and data. Note: To create a Standard application, see Creating a Standard Application. To automatically create the Sample application, click Standard, and then click Sample. When application creation is completed (this will take several minutes), you'll see an Application created successfully message. Chapter 3 Creating a Planning and Budgeting Cloud Application 3-17
- 59. To manage the application after it's created, see Managing Applications. Creating a Standard Application A Standard application is an advanced application with two cubes and the option to add more cubes. Complex business logic, such as business rules and allocations, is supported. You can't convert a Standard application into a Reporting application. A Standard application: • Allows you to add additional dimensions • Enables sandboxes for the block storage cubes that are created when you create the application. (You can also enable sandboxes for custom cubes when you create the cube.) • Supports custom calendars (up to weeks of the month) • Supports business rules • Allows member formulas • Can't be converted into a Reporting application • Can be converted into an Enterprise application Note: To convert a Standard application into an Enterprise application, see Converting a Standard or Reporting Application to an Enterprise Application. To create a Standard application: 1. Click Standard. 2. Click New. 3. Name your application and enter a description. Note: Ensure that you adhere to the application naming restrictions outlined in Naming Restrictions. 4. The application provides setup options that you can select to help you create the initial framework for your planning process. For descriptions of the setup options, see Choosing Setup Options. 5. Review the summary screen, and, if the selections you made are correct, click Create. After you create a Standard application, populate it by performing these steps: • Import application metadata using the import feature. See Importing Metadata. • Populate application data by importing data from your source system. See Importing and Exporting Data. Chapter 3 Creating a Planning and Budgeting Cloud Application 3-18
- 60. Choosing Setup Options Related Topics • Setting Up the Calendar and Task Flow Type Set up the calendar and task flow type for the application. You can set the period frequency, start and end years, fiscal period, and enable rolling forecasts. Then you can designate which task flow type to use. • Setting Up Currencies Specify the main currency for the application, and establish whether the application supports multiple currencies. • Customizing the Cube Names Specify custom names for the input (block storage) and reporting (aggregate storage) cubes used in the application. • Setting Up Custom Dimensions and Metadata Categorize data values into dimensions. You can create up to 32 user-defined, custom dimensions. Setting Up the Calendar and Task Flow Type Set up the calendar and task flow type for the application. You can set the period frequency, start and end years, fiscal period, and enable rolling forecasts. Then you can designate which task flow type to use. The calendar establishes the application's period frequency, start and end years, first month of fiscal year (if monthly) or the start date of the first fiscal period (if weekly or quarterly), and lets you enable a rolling forecast and period duration. For the fiscal year, set the fiscal year first month and specify whether the fiscal year starts from the same calendar year or the previous calendar year. You can later set up calculations based on the calendar year, for example, using formula expressions. When setting up formulas for an application, consider that formula expressions such as [TPDate] and [FirstDate] produce different results if the application starts in the same calendar year or previous calendar year. On this screen you can also choose a Task Flow Type for the application: • Task List: Task lists are a classic feature which guides users through the planning process by listing tasks, instructions, and end dates. For more information about task lists, see Administering Task Lists. • EPM Task Manager: This is the default option for new applications. EPM Task Manager provides centralized monitoring of all tasks and provides a visible, automated, repeatable system of record for running a application. For more information about EPM Task Manager, see Administering Tasks with Task Manager. Chapter 3 Creating a Planning and Budgeting Cloud Application 3-19
- 61. Note: There is no migration from existing Task Lists to the EPM Task Manager. If you want to continue using classic Task Lists, select the Task List option during application creation. To set up the calendar and task flow type: 1. Select the Period Frequency: • Monthly • Weekly • Quarterly • Custom 2. Select the Start and End year for the application. 3. Specify fiscal year information based on the Period Frequency: • For Monthly, select the first month of the fiscal year. If you create an application with a first month of something other than January, you must also select the Fiscal Year Start Date. The selection of this parameter is critical for the correct creation of the Years dimension and the underlying calculations for periods. For more information, see About the Calendar. • For Weekly and Quarterly, specify the start date of the first fiscal period 4. If you set the frequency to Monthly, select a Weekly Distribution option: Even, 445, 454, or 544. Weekly distribution sets the monthly distribution pattern, based on the number of fiscal weeks in a month. This selection determines how data in summary time periods spreads within the base time period. When users enter data into summary time periods, such as quarters, the value is distributed over base time periods in the summary time period. If you select a weekly distribution pattern other than Even, the application treats quarterly values as if they were divided into 13 weeks and distributes weeks according to the selected pattern. For example, if you select 5-4-4, the first month in a quarter has five weeks, and the last two months in the quarter have four weeks. 5. Decide whether to enable rolling forecasts and set the period duration. See About Rolling Forecasts. Rolling Forecast is available only if the start month is January. 6. Select a Task Flow Type for the application: • Task List: Guides users through the planning process by listing tasks, instructions, and end dates. For more information about task lists, see Administering Task Lists. • EPM Task Manager: This is the default option for new applications. EPM Task Manager provides centralized monitoring of all tasks and provides a visible, automated, repeatable system of record for running an application. Chapter 3 Creating a Planning and Budgeting Cloud Application 3-20
- 62. For more information about EPM Task Manager, see Administering Tasks with Task Manager. About the Calendar For 12 month calendars where you select something other than January for the First Month of Fiscal Year, you must also select the Fiscal Year Start Date. The selection of this parameter is critical for the correct creation of the Years dimension and the underlying calculations for periods. Fiscal Year Start Date options: • Same Calendar Year. Set the fiscal year (FY) to start with the current calendar year (CY). For example, in a 12-month calendar, selecting the year 2024 with a starting period of Jun creates the starting year as FY24, defined as Jun-CY24 to May-CY25. • Previous Calendar Year. Set the fiscal year (FY) to start with the previous calendar year (CY). For example, in a 12-month calendar, selecting the year 2024 with a starting period of Jun creates the starting year as FY24, defined as Jun-CY23 to May-CY24. The following table provides examples of how the First Month of Fiscal Year and the Fiscal Start Year options affect the calendar for the application, assuming the Fiscal Start Year is 2022. Table 3-4 Examples of First Month of Fiscal Year and Fiscal Year Start Date Calendar Options for 12 Month Calendars First Month of Fiscal Year Fiscal Year Start Date Period - Year Years Dimension January Not applicable. This option is not available when January is selected as the first month of the fiscal year. Jan-CY22 to Dec-CY22 FY22 July Same Calendar Year Jul-CY22 to Jun-CY23 FY22 July Previous Calendar Year Jul-CY21 to Jun-CY22 FY22 February Same Calendar Year Feb-CY22 to Jan-CY23 FY22 February Previous Calendar Year Feb-CY21 to Jan-CY22 FY22 December Same Calendar Year Dec-CY22 to Nov-CY23 FY22 December Previous Calendar Year Dec-CY21 to Nov-CY22 FY22 Setting Up Currencies Specify the main currency for the application, and establish whether the application supports multiple currencies. To set up the currency: 1. During application setup, select the main currency for the application. Chapter 3 Creating a Planning and Budgeting Cloud Application 3-21
- 63. 2. Specify whether the application supports more than one currency, and if so, then select one of the following multiple currency options: • Standard: Creates the Currency dimension and a hidden dimension called HSP_Rates to store the exchange rates. See About Standard Multicurrency. Not available for Module and Custom application types. • Simplified: Creates the Currency dimension and additional accounts are added to store the exchange rates. See About Simplified Multicurrency. After the application is created, you can't change this option. Multiple currency support is available for level 0 members, regardless of base currency. The same currencies and exchange rates are used across cubes. About Simplified Multicurrency In a Simplified multiple currency application, a single Currency dimension is added to the application and exchange rates are stored in the Accounts dimension. Here is the workflow for working with a Simplified multiple currency application: 1. During application creation, select a main currency against which the entire application will refer to when a currency conversion is done. 2. After the application is created, in the Currency dimension, create a Currency member for each currency in the application. The Currency members you create are listed under Input Currencies. Data is entered or loaded in an input currency and data can be entered or loaded into multiple input currencies for any given combination; for example Entity and Account. 3. While creating a Currency member, you can specify whether the currency you're adding is also a reporting currency. Select the Reporting Currency option to make a currency a reporting currency. Note: Each application has one main currency, and is allowed to have many reporting currencies. 4. You can assign security to the Currency dimension to make Currency dimension members read-only based on user access. To enable security for the Currency dimension, click the Edit Dimension Properties tab, and then select Apply Security. See Editing Dimension Properties in the Simplified Dimension Editor. 5. For simplified multiple currency applications with a custom aggregate storage cube, you must enable the Account, Period, and Currency dimensions for the custom aggregate storage cube. All dimensions in default aggregate storage cubes are enabled by default, but you must enable these dimensions manually for custom aggregate storage cubes. To enable Account, Period, and Currency dimensions for custom aggregate storage cubes, edit dimension properties for each dimension and select to enable them for the aggregate storage cube. See Editing Dimension Properties in the Simplified Dimension Editor. 6. Refresh the application. The Calculate Currency rule converts the input values from the current currency to the reporting currencies. Exchange rates are calculated from the input currency to the main currency of the application. Triangulation is used to calculate from an input currency to all reporting currencies. Chapter 3 Creating a Planning and Budgeting Cloud Application 3-22
- 64. 7. Enter exchange rate data to the exchange rate form that was automatically created and seeded during application creation. The exchange rate form is called Exchange Rates to Main Currency ; for example, Exchange Rates to USD. Enter the exchange rates by period for all input currencies against the main currency. You must enter the values across all intersections under which you wish to see the converted data. Note: You can also export the Exchange Rate Template to input and load currency exchange rates. See Importing Exchange Rates for a Simplified Multicurrency Application. Exchange rates are stored in the Account dimension and they contain the ending and average rates used to convert foreign currencies into the main currency. These rates are in FX Rates-Average and FX Rates-Ending. These rates are locked and can't be deleted. Users with view permissions can view the rates for the currencies on the Exchange Rates to Main Currency form. Note: You can't move an Account member that is under an Exchange Rates account out from under Exchange Rates because the Exchange Rates account is locked. To move an Exchange Rate member out of the Exchange Rates account, you must delete the member and then re-add it to the new location. 8. There are two ways to view Reporting currency values: • Calculate Currencies rule on a form: On the data input form, add the Calculate Currencies business rule. To add this rule, click the Action menu, and then select the Business Rule option. You can use the Run After Save or Run Before Load business rule properties. When data is entered for the input currency and the Calculate Currency rule is executed, the currency is converted and displays in the reporting currency form. Chapter 3 Creating a Planning and Budgeting Cloud Application 3-23
- 65. Note: – Ensure that any forms created have the same intersection as that of the Exchange Rates to Main Currency form, with respect to Scenario, Version, and Year. – Ensure that both the input and converted forms have the same structure, the only difference between the forms being the currency. – Associate the Calculate Currencies rule to the forms where the input is being provided. You can set up forms to automatically run these rules when data in the form is saved. If not, users must manually launch the rule to convert data from one currency to the reporting currencies. After the rule is run, view the converted values by opening the form for which you want to see the converted values or by selecting that currency's member from the Currency dimension. – The Calculate Currencies rule is associated with forms in a block storage cube. Simplified currency conversion isn't supported for aggregate storage cubes. – You can restrict currency calculations in forms and batch currency rules based on the range defined for the scenario time period. In Application Settings, select Yes for Enable currency calculation based scenario time period. • Create and launch a custom rule: To create a custom rule, from the Home page, click Navigator , and then under Create and Manage, click Currency Conversions. For Currency, enter the reporting currency. Then enter the Scenario, Version Type, and Version details. Specify the Years for which you want to calculate the currency conversion rule. Click Save. To launch the rule, from the Home page, click Rules. To the right of the business rule, click Launch. Note: If you've enabled currency calculation based on the scenario time period, you cannot specify Years and you can only specify one Scenario. Note: The behavior of the currency conversion script (whether to honor calculate currencies based on scenario definition) is dependent on the application setting at the time of script generation. See What Application and System Settings Can I Specify? Chapter 3 Creating a Planning and Budgeting Cloud Application 3-24
- 66. Videos Your Goal Watch This Video Learn how to set up multiple currencies in Planning. Setting Up Multiple Currencies in Planning Tutorials Tutorials provide instructions with sequenced videos and documentation to help you learn a topic. Your Goal Learn How Learn how to automatically translate data to reporting currencies in Planning forms. Automatically Translating Data to Reporting Currencies in Planning About Standard Multicurrency If you're familiar with Planning, then you're familiar with the Standard multiple currency approach. This is the approach that your current Planning applications use. Selecting the standard multiple currency option during application creation creates two additional dimensions called Currency and HSP_Rates. You can add more currencies as members of the Currency dimension. The HSP_Rates dimension is a hidden dimension that stores exchange rates. This dimension includes these members and others that store currency rates: • Hsp_InputValue: Stores data values • Hsp_InputCurrency: Stores currency types for data values For more information, see Hsp_Rates Dimension for Standard Multicurrency Applications. For an account with a currency data type, you can choose from one of the following exchange rate types: • Historical • Average • Ending For more information, see Data Type and Exchange Rate Type. Based on the exchange rate type, a user-defined attribute (UDA) is associated with the account that is used in the currency calculation. You can associate an entity to a currency. For example, when you associate the entity USA to the currency USD, the local currency in the form for the USA entity is USD. You can create multiple exchange rate tables, each representing a different business scenario. Each scenario can be associated with only one exchange rate table. You can run a calculate currency rule that generates the rule at runtime based on the members included in the form. This rule can be set to run when the form is saved or loaded, based on the requirement. Chapter 3 Creating a Planning and Budgeting Cloud Application 3-25
- 67. For more information about using the standard multiple currency approach, see Administering Dimensions. Customizing the Cube Names Specify custom names for the input (block storage) and reporting (aggregate storage) cubes used in the application. You can customize the names for the cubes during application creation only. If no cube names are specified during application creation, then the input (block storage) cube name defaults to "Plan1" and the reporting cube (aggregate storage) name defaults to the application name. Caution: After a cube is added, you can't rename it or delete it. To customize the cube names: 1. In Name of Input Cube, enter a name for the data entry (block storage) cube. 2. In Name of Reporting Cube, enter a for the reporting (aggregate storage) cube. At this point in the application creation process, you can also enable sandboxes. For information about sandboxes, see Managing Sandboxes. Setting Up Custom Dimensions and Metadata Categorize data values into dimensions. You can create up to 32 user-defined, custom dimensions. The application includes two custom dimensions: Account and Entity. Use Account and user-defined dimensions to specify data to gather from users. Use Entity to model the flow of planning information in the organization and establish the plan review path. If you selected the Standard multicurrency option during application creation, the application includes the Hsp_Rates dimension for storing exchange rates. This dimension includes these members and others that store currency rates: • Hsp_InputValue: Stores data values • Hsp_InputCurrency: Stores currency types for data values For detailed information about custom dimensions and Hsp_Rates, see Editing Dimensions in the Simplified Dimension Editor. Chapter 3 Creating a Planning and Budgeting Cloud Application 3-26
- 68. Note: You have the option to either manually enter member names or you can set up Account, Entity, and custom dimension members by importing from metadata files. To import from metadata, you first export the metadata for each dimension to a flat file and then, on this window, import their metadata by browsing to that flat file. For instructions on creating the flat file, see Creating the Metadata Import File. To set up custom dimensions: 1. To add a dimension or rename a prefilled dimension, to the right of Dimension Type in the Dimension Name column, enter the name of the dimension. Dimension names can have up to 80 characters and can include spaces. 2. For each dimension, enter its member names. For example, for the Version dimension, you could enter Budget2014. You can add members later. The Number of Records column displays the number of members either entered or in the flat file. 3. Optional: To import metadata for Account, Entity, or a custom dimension from a flat file, click Browse. Use this method for importing smaller dimensions (for example, 1,000 members or fewer); use the Import and Export method (described in Importing and Exporting Data and Metadata) for incremental updates or for loading larger dimensions. For instructions on creating flat files, see Creating the Metadata Import File. If the file has so many members that application performance would be impacted, an error displays and the number of records displayed is 0 (zero). 4. Click Create. 5. If you have more metadata to load, continue to Importing Metadata. Planning and Budgeting Cloud URL To launch the Planning and Budgeting Cloud application, enter the following URL in a new browser window: https://Oracle PBCS service name/HyperionPlanning; For example: https://testnew1-testnew1.pbcs.us1.oraclecloud.com/HyperionPlanning; For information about enabling access to application artifacts on mobile devices and for considerations when using the application, see Managing Application Access. Taking the Product Tour Clicking Take a quick tour links you to useful information about getting started with the application. It also provides best practices for determining your requirements and designing Chapter 3 Creating a Planning and Budgeting Cloud Application 3-27
- 69. your application, tutorials for administering the application, and links you to the Help Center where the documentation library is located. To take the product tour: 1. Click Take a quick tour. 2. Click the buttons at the bottom of the screen to page through the tour screens. Managing Application Ownership The Service Administrator who creates the application is auto-assigned the Application Owner function. When a Service Administrator with the Application Owner function is deleted or when the user’s predefined role assignment is downgraded (for example, from Service Administrator to Power User), the Application Owner function is reassigned to the next available Service Administrator user (in alphabetical order) for the application, and then role of the current Application Owner user is deleted or changed to sync up with Access Control. If there are no available Service Administrators, then the Service Administrator user is not deleted or the role is not changed. Oracle will contact you with next steps to resolve the issue. Any Service Administrator can use System Settings to take over or reassign the Application Owner role to any available Service Administrator. See What Application and System Settings Can I Specify?. Chapter 3 Managing Application Ownership 3-28
- 70. 4 Creating a FreeForm App FreeForm apps use an open dimensional cube construct allowing you to create cubes with any dimension combination you need. Related Topics • Understanding FreeForm • FreeForm App Sources • Important Considerations for FreeForm Apps • Creating a FreeForm Application Type • FreeForm Apps FAQ Understanding FreeForm FreeForm enables you to create an application with the cubes and dimensions of your choice without being constrained by the cube and dimension limitations imposed by standard applications. With FreeForm, you can model and build your own cubes while preserving the ability to leverage business process functionalities. FreeForm can be accessed using Oracle Smart View for Office or Oracle Enterprise Performance Management Cloud screens; they support Groovy scripts for custom functions, and business rules for calculations. Note: The following features are not available in FreeForm because these features require the provided Scenario, Version, Period, and Year dimensions to be present: • Predictive Planning • Auto-Predict • IPM Insights In FreeForm, the Scenario, Version, Period, and Year dimensions can be defined as custom dimensions. In addition, the following features are not available in FreeForm: • Sandboxes • Approvals • Task Manager You can create applications with multiple cubes or you can create an application with a single cube and then add more cubes later (up to 12 cubes total). See the table below for a feature comparison of a single cube FreeForm app to a multi-cube FreeForm app. 4-1
- 71. Comparing Features of a Single Cube FreeForm App to a Multi-Cube FreeForm App Feature Single Cube FreeForm App Multi-Cube FreeForm App Number of cubes • The application has only one cube. • The single cube can be either block storage (BSO) or aggregate storage (ASO). • The BSO cube is automatically set as a Hybrid-BSO cube. • The application can have up to 12 cubes. • The cubes can be any combination of ASO and BSO. • BSO cubes are automatically set as Hybrid-BSO cubes. Cube Creation The single cube can be created in one of the following ways: • From an existing Essbase outline (OTL) file or Essbase Migration package • Manually using the application creation wizard • Of the 12 cubes that are allowed, only the first cube can be created from an OTL file or an Essbase Migration package. • The remaining cubes can then be added using the web interface (from the Home page, click Application, then click Overview, select the Cubes tab, and then click Create). If the first cube was created using the web interface, then it is no longer possible to process an OTL file or an Essbase Migration package. However, you can still create the remaining cubes using the web interface. • Each multi-cube FreeForm app generates its own outline on Essbase. The dimensionality is shared, but not the outline itself. Additional Features of a Multi-Cube FreeForm App • The maximum number of dimensions allowed in a FreeForm app is 26. • Cubes can share dimensions or have standalone dimensionality. • All dimensions can be custom; or native account, period, and/or entity dimensions can be inherited by the cubes. • Cross-cube data maps, Smart Push, and Copy Data support are available for FreeForm app types. Multi-cube FreeForm apps are constrained by these existing business process assumptions: • Members must be unique across all the cubes within FreeForm. • Governors are applicable at the application level and not at the cube level. • The input outlines must not be enabled to allow duplicate member names. Chapter 4 Understanding FreeForm 4-2
- 72. Videos Your Goal Learn How Get an introduction to FreeForm. Introduction to FreeForm Apps in Cloud EPM Create FreeForm apps from on-premises Essbase outline (OTL) files and snapshots. Creating FreeForm applications from on- premises Essbase outline files and snapshots Create multi-cube FreeForm apps with an Essbase outline Creating Multi-Cube FreeForm Apps from Essbase Outlines Create FreeForm apps with a Hybrid BSO cube Creating FreeForm Applications with a Hybrid BSO Cube Create FreeForm apps with an ASO or reporting cube Creating FreeForm Applications with a Reporting/ASO Cube Create multi-cube FreeForm apps with a BSO or ASO cube Creating Multi-Cube FreeForm Apps from BSO and ASO Cubes Learn how to create FreeForm apps using an Excel template. Using the Excel template, you learn how to define application properties, manage cubes, create dimensions and members, attributes, access permissions, and load data into the FreeForm application. Creating Multi-Cube FreeForm Applications with an Excel Template - Part 1 Learn how to update FreeForm apps using an Excel template and verifying changes in the web interface. After creating your FreeForm application using an Excel template, learn how you can use the same template to make modifications to dimensions, members, substitution variables, and security. Then, in the Planning web interface, assign Application Management options, review the application properties and definition, and the data you imported. Creating Multi-Cube FreeForm Applications with an Excel Template - Part 2 FreeForm App Sources You can build FreeForm apps by creating dimensions using the application creation wizard. Alternatively, you can use an outline (OTL) file or snapshot from an on-premises release 11.1.2.4.xxx (or later) single cube Essbase application to create a FreeForm app. When you use an Essbase cube OTL file or Essbase application snapshot as the source for a FreeForm app, Account, Period (time), and Entity (country) dimensions are created and mapped automatically. Additionally, Version and Scenario dimensions of the Essbase application are created as custom dimensions. As a result, out of the box Workflow functionality is not supported in FreeForm apps. Chapter 4 FreeForm App Sources 4-3
- 73. Service Administrators build a FreeForm app using the application creation wizard or these sources: • An Outline file from on-premises release 11.1.2.4.xxx (or later) single cube Essbase application You may use an OTL file from an on-premises release 11.1.2.4.xxx (or later) single cube Essbase application to create the structure of the FreeForm app. New cubes may be added or created for this FreeForm app at a later time. Because the OTL file name is assigned to the cube created for the FreeForm app, the file name must be eight characters or less. Longer file names will cause the process to fail. Generally, the OTL file is available in the EssbaseServer/essbaseserver1/app/ <app_Name> directory within your on-premises Essbase deployment. Because the OTL file does not contain application data, you must extract Essbase data to a file. Use MaxL, Essbase Studio, or another tool to export data from an Essbase application. The data must be exported in an Essbase data file format. After creating the application, import the extracted data, selecting Essbase as the source type. You can import from a locally stored data file or from a file that was uploaded to the Oracle Enterprise Performance Management Cloud inbox. For detailed instructions, see Importing Data. • An application snapshot from an on-premises release 11.1.2.4.xxx (or later) single cube Essbase application This option simplifies application creation by migrating an existing Essbase application snapshot (ZIP file) that was created using Migration. This process automates dimensions loading, substitution variables creation, calculation scripts conversion as graphical rules, and data load. New cubes may be added or created for this FreeForm app at a later time. Important Considerations for FreeForm Apps Note: Do not attempt to create FreeForm apps by importing Essbase Migration snapshots into an Oracle Enterprise Performance Management Cloud environment. Importing snapshots using Migration is supported only for snapshots created from a previous FreeForm app. • Data maps and other multi-cube features are unavailable if you create a single cube FreeForm app using the application creation wizard. • Essbase snapshots with Custom Defined Functions (CDF) and CDF references cannot be used to create FreeForm apps. • Make sure that the OTL file or Essbase application snapshot that you are using does not contain objects with system restricted names; for example, a member named FY02 in the Year dimension. You must rename or remove such restricted names before generating the OTL file or snapshot that you plan to use to create the application. See Naming Restrictions. Chapter 4 Important Considerations for FreeForm Apps 4-4
- 74. • Ensure that the OTL file or Essbase application snapshot that you are using does not have member and alias names that are longer than 80 characters. If member and alias names are longer than 80 characters, you must remove or shorten them or the import will not be successful. See Naming Restrictions. • If the OTL file that you are using contains Year Total and Beginning Balance members, the Beginning Balance member must be the first child under the Period dimension, and Year Total must be the second child under Period dimension. These members require special handling and can be moved to appropriate positions by modifying the .csv files in the Migration snapshot before restoring the snapshot. • If you plan to use an OTL file or snapshot stored in your EPM Cloud environment as the source, upload the file before starting the application creation process. Use the uploadFile EPM Automate Utility command or Migration to upload the OTL file or snapshot to an EPM Cloud environment. • Imported data may not be editable in FreeForm apps. At times, the data is set as Read- only. • Member outline must be unique in the application. • If you create a FreeForm app by importing an OTL or snapshot, you can add or create new cubes for this FreeForm app at a later time. • If you create a FreeForm app by adding new cubes in the application creation wizard, an Essbase cube OTL or Essbase application snapshot cannot be imported into this FreeForm app at a later time to create new cubes. Do not use the following reserved words to name dimensions and members in FreeForm: Table 4-1 Reserved words that should not be used as member names in FreeForm Reserved words BU Version_1 Users Attribute Dimensions HSP_Entity ConsolidatedData Groups Default HSP_Period BaseData Calendars Task Lists HSP_Version SandBoxData Currencies Menus HSP_XCRNCY Super User Predefined CalcMgrRules HSP_Years Strategic Planner FX_Tables CalcMgrRulesets HSP_View Service Administrator Forms CalcMgrVariables HSP_Metric CalcMgrTemplates Aliases HSP_Rates Root Cubes HSP_Scenario Dimensions Planning Units HSP_Account Creating a FreeForm Application Type Before you create a FreeForm app, review the important considerations and the reserved words that should not be used as member names in FreeForm apps. See Important Considerations for FreeForm Apps. Service Administrators can create a FreeForm application type in the following ways: • Importing an Essbase outline file or snapshot of a single Essbase cube. • Creating an application with a single cube (you can keep it to a single cube or add more cubes later) Chapter 4 Creating a FreeForm Application Type 4-5
- 75. • Creating an application with multiple cubes To create a FreeForm application type: 1. On the EPM Enterprise Cloud Service landing page, click SELECT under Planning. 2. On the Planning landing page, click START under Create a new application. 3. Enter a Name and Description for the application. 4. From Application Type, select Free Form. 5. For Application Setup, select from the following options: • Import Essbase OTL/LCM: Creates a FreeForm app from an on-premises Essbase outline file or snapshot. Only one outline or snapshot is allowed. To continue creating a FreeForm app using this application setup option, see Creating a FreeForm App Using an Outline File or Snapshot. • Create Cubes: Creates a FreeForm app that uses one or more cubes. Use this option to manually create FreeForm apps based on your own models using custom dimensions. During this process, you can map the custom dimensions that you want to use as Entity, Period, and Account dimensions, and you can also add other custom dimensions to support your model. To continue creating a FreeForm app using this application setup option, see Creating a FreeForm App Using the Application Creation Wizard. Note: If creating a FreeForm app with the Create Cubes option in the application creation wizard, an Essbase outline file or snapshot can no longer be imported into this application. You can still create new cubes at a later time using the web interface. If creating a FreeForm app using the Import Essbase OTL/LCM option in the application creation wizard, new cubes can be created for this application at a later time using the web interface. Creating a FreeForm App Using an Outline File or Snapshot To continue creating a FreeForm app using an outline file or snapshot: 1. Select the location of the source OTL file or the Essbase application snapshot: • Select Local to access the source OTL file or snapshot from the computer from which you are currently accessing Oracle Enterprise Performance Management Cloud. For Import File, click Choose File and then select the source OTL file or snapshot. • Select Inbox to access the source OTL file or snapshot from your EPM Cloud environment. From Select One, select the source OTL file or snapshot. 2. Click Next. 3. Review application information and then click Create. Chapter 4 Creating a FreeForm Application Type 4-6
- 76. When application creation is complete, EPM Cloud Home page is displayed. 4. Make sure that errors were not reported during application creation. • Open the Jobs console by clicking Application, and then Jobs • Verify that the Create Database and Process Outline activities finished without errors. Correct any reported errors. 5. Optional: If you created the application using an OTL file as the source, import application data. See Importing Data. If you used a snapshot as the application source, the application creation process automatically imports data. 6. Create application users in identity domain and assign predefined roles as needed. See Managing Users and Roles in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators . 7. Set up access permissions as needed. See Setting Up Access Permissions. Creating a FreeForm App Using the Application Creation Wizard To continue creating a FreeForm app using the application creation wizard: 1. For No. Of Cubes, select the number of cubes you'd like to use to create your FreeForm app. You can add up to 12 cubes now, or you can start with one cube and then add more cubes later on the Application Overview page. Note: If you create a single cube FreeForm app, data maps and other multi-cube features are unavailable until you add cubes to the FreeForm app. Also for a data map to work there needs to be at least one block storage (BSO) cube, and the source for the data map needs to be a BSO cube. 2. In Cube Name, enter a name for each cube, maximum eight characters. 3. Select Is ASO, if the cube is an aggregate storage cube. If the Is ASO checkbox is cleared, then the cube is a Hybrid block storage cube. Note: Reporting applications that use ASO cubes, generally, store data in aggregate views and can handle a higher number of dimensions than BSO without adversely affecting performance. 4. Click Next. The Create Dimensions page is displayed. From this screen, you can create up to three dimensions and assign one each to Account, Entity, and Period default dimension types. Additional dimensions can be added later in the web interface. Chapter 4 Creating a FreeForm Application Type 4-7
- 77. Note: FreeForm apps do not require standard dimensions. You can create an application with only custom dimensions containing members of your choice. The dimensions you create and its structure are not governed by the constraints imposed on standard Planning application dimensions. 5. In Create Dimensions, create and map default application dimensions. Complete a step: • To create dimensions and map them to default dimension types, select the Enabled check box and then type in dimension names. Note: Enabling dimensions is not automatic. Just like custom applications, you must manually enable dimensions for FreeForm apps. You can do this now, or you can enable them later. • To create a dimension and assign a dimension type, select the check box in a row and then type in a dimension name. • To create a shell application, do not change anything in this screen. You can add and map dimensions to shell applications after the application creation process is complete. 6. Click Next. 7. In Review, verify the settings that you selected and then click Create. The application creation process may take a few minutes. 8. In the Application Creation Status screen, click OK. The Planning Home page is displayed. 9. Optional: Create custom dimensions, if needed. a. Click Application, then Overview, and then select the Dimensions tab. b. For Cube, select a cube that you created for your FreeForm app or select All. c. Click Create. d. Complete the dimension details for each dimension you want to add, and then click Done. For descriptions of the dimension properties, see Editing Dimension Properties in the Simplified Dimension Editor. Select Enabled to indicate whether the dimension is to be used in this cube. Note: Enabling dimensions is not automatic. Just like custom applications, you must manually enable dimensions for FreeForm apps. e. Click Action and then Refresh Database to refresh the cube. Chapter 4 Creating a FreeForm Application Type 4-8
- 78. 10. Optional: Import application data. See Importing Data in Administering Planning. 11. Optional: If you created a shell application with a view to import a snapshot, access Migration, then delete the application, and then complete the import process. a. Upload a snapshot from a FreeForm app to your environment. See Uploading Archives to the Service in Administering Migration for Oracle Enterprise Performance Management Cloud for detailed instructions. b. Import the snapshot. See Importing Artifacts and Application from a Snapshot in Administering Migration for Oracle Enterprise Performance Management Cloud for detailed instructions. 12. Create application users in identity domain and assign predefined roles as needed. See Manage Users and Roles in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators . 13. Set up access permissions as needed. See Setting Up Access Permissions. FreeForm Apps FAQ Related Links General: • What is the difference between Essbase and an EPM Cloud FreeForm app? • When will current Essbase 21c versions be adopted in EPM Cloud? • What is the impact of having EPM Cloud + Essbase 21c? How will they work together? Data movement, reporting, Smart View connections, and so on. • What is the recommendation for customers for their Essbase cubes when migrating from On-premise EPM to EPM Cloud? • What are the default hardware settings that will limit processing? • What EPM license do I need to have to get multi-cube FreeForm? FreeForm App Details: • Are all FreeForm apps considered custom applications? • Does multi-cube FreeForm app mean that I can have 12 cubes, each with only 2 or 3 dimensions? • What kind of Administration Interface is available in FreeForm apps? • Does Cube Refresh refresh all cubes at once? • What about size thresholds? • Will slow changing attributes be supported in FreeForm apps? • Is there direct access to FreeForm cubes through Smart View and Oracle Analytics Cloud and Data Visualization? • Are hybrid cubes supported with FreeForm apps? • Do FreeForm apps offer a repository of multiple applications? • Is load of metadata through Data Management available with Freeform apps? • Do we lose any Planning Custom App Type related functionality in FreeForm apps? • Can you use Groovy if you select FreeForm apps? Chapter 4 FreeForm Apps FAQ 4-9
- 79. • Can you remove a dimension after adding it? • Can you use Planning Migration files to create an application similar to the OTL or the Migration zip files? • Can you import multiple outline or Migration files? • Is FreeForm only available with the Enterprise version of EPM (vs. what was previously called PBCS)? • How do you upload dimensions (and hierarchies) from a legacy Hyperion Planning application into EPM using FreeForm? • Can we refresh the database from Smart View? • Are partitions enabled? • How can we configure the security filters? • Is the task management feature similar to Financial Consolidation and Close where it can be integrated, or is it just basic tasks? Can you please comment on this feature? • How do you manage dimensions for FreeForm? • Can I take a backup of a FreeForm app and then migrate it to a Financial Consolidation and Close or Planning Modules Cloud application? • What about the business rules script, will they be migrated properly? And the configurable consolidation rule with regard to the Financial Consolidation and Close application? • Does migration of an OTL work with all versions of Essbase? • Is there no restriction for Data Integration in FreeForm that needs Scenario/Time period dimensions? • Can we import data if the application is already created? • Could you provide information about how the EPM Integration Agent feature is being used in Data Exchange? • Is there the capability to create custom dimensions and business rules? Essbase Migration Technical Questions: • What tuning capabilities, if any, will be made available for FreeForm apps? • Is partitioning supported? Transparent, Linked, Replicated? • What about the MaxL Language for Admins, Automation, Shell integration? • Are the MDX functions going to be supported? • Aside from Data Management/ETL how else can we recreate rules files in FreeForm apps? This could be cumbersome in Data Management. • For large scale ASO databases, what is the preferred data load mechanism in FreeForm apps? • Any plans to create a CDF to Groovy migration tool? • What Essbase artifacts can I migrate into FreeForm apps and how? • What objects are skipped when Essbase outline files or Migration files are imported into FreeForm apps? • How do Essbase features map to FreeForm apps in EPM Cloud? Chapter 4 FreeForm Apps FAQ 4-10
- 80. What is the difference between Essbase and an EPM Cloud FreeForm app? Essbase as a solution can be bought as an on-premise solution or for deployment through Oracle Cloud Infrastructure (OCI). It is deployed as an OCI solution with the customer having full deployment control of the cubes. FreeForm apps are a SaaS solution offered by Oracle Enterprise Performance Management Cloud that allows Essbase cubes to be imported into EPM Cloud and deployed standalone. FreeForm apps have a hybrid architecture with a relational component beyond the Essbase cubes. FreeForm apps can have up to 12 cubes and up to 29 dimensions across all cubes. When will current Essbase 21c versions be adopted in EPM Cloud? Adoption of the latest Essbase versions into EPM Cloud is based on the impact on our customers – functional and performance. We are currently evaluating 21c for EPM Cloud adoption, and FreeForm apps will be one of the early adopters. What is the impact of having EPM Cloud + Essbase 21c? How will they work together? Data movement, reporting, Smart View connections, and so on. Essbase 21c on OCI is an IaaS deployment. FreeForm is a SaaS deployment. Data will need to be extracted from either environment or moved to the other. Oracle Smart View for Office shared connections can connect within the same platform so you can connect multiple FreeForm apps using one shared EPM connection. Essbase 21c on OCI would be a private connection when FreeForm is a shared connection in Smart View. Any data exchange between FreeForm apps and Essbase 21c on OCI or on-premise will be an export-import of data. What is the recommendation for customers for their Essbase cubes when migrating from On-premise EPM to EPM Cloud? On-premise customers migrating their on-premise EPM instances to EPM Cloud should migrate their Essbase reporting or planning cube instances into FreeForm apps in EPM Cloud. This will ensure consistent access to EPM business processes all within SaaS EPM Cloud. This also avoids data latency and data movement across environments. Also, it will ensure there is one place to maintain access rights and security. Customers can leverage all the latest features in theEPM Cloud platform and future enhancements on an ongoing basis. What are the default hardware settings that will limit processing? We operate based on named user licensing and the Cloud hosting policy guides performance expectations. EPM Cloud uses a standardized Cloud hardware configuration, and customers can make change requests using the Service Request process. What EPM license do I need to have to get multi-cube FreeForm? FreeForm apps are available with EPM Enterprise Cloud. Are all FreeForm apps considered custom applications? Yes. All FreeForm apps are fully custom with no out-of-box content. You have full flexibility in dimensions and members. You can create cubes of any dimension combination as long as the total cubes are less than 26 custom dimensions. You can map Account, Period, or Entity dimensions if they are part of the cube dimensionality to the default dimension types. We automatically map these dimensions if they exist in the source outline or Migration file. Chapter 4 FreeForm Apps FAQ 4-11
- 81. Does multi-cube FreeForm app mean that I can have 12 cubes, each with only 2 or 3 dimensions? Up to 12 cubes are allowed in a FreeForm app, in any combination of BSO and ASO cubes. Each cube can have the exact needed dimensions without requiring any required dimensions or members. What kind of Administration Interface is available in FreeForm apps? Essbase admin console features to the extent relevant in SaaS are available through Calculation Manager or the dimension editor in the FreeForm app. Since it is a web- based application there are other admin interfaces in EPM web applications that allow administrators to manage EPM applications. Does Cube Refresh refresh all cubes at once? FreeForm deployments are cubes contained within one FreeForm app. You can have up to 12 cubes. Refresh is by application across all cubes. There is no concept of cube-specific refresh in EPM Cloud. What about size thresholds? There are no file size limits in the new EPM Enterprise Cloud where FreeForm is available. Dimension size and data volumes are handled on a case-by-case basis. There is a standard well established support protocol for upscaling the thresholds. Will slow changing attributes be supported in FreeForm apps? Some customers have asked for this, but the demand for it is not high enough. We will investigate it based on customer connect feedback in Cloud Customer Connect. Is there direct access to FreeForm cubes through Smart View and Oracle Analytics Cloud and Data Visualization? Smart View connections to FreeForm apps goes through the standard Smart View EPM Cloud interface. FreeForm apps can be accessed from Oracle Analytics Cloud and using Data Visualization using the direct connect capability in Oracle Analytics Cloud. Are hybrid cubes supported with FreeForm apps? FreeForm apps support creation of Hybrid BSO cubes and ASO cubes Do FreeForm apps offer a repository of multiple applications? Repository is by application but can be connected into from another application. Data across applications can be blended in web and Smart View. Is load of metadata through Data Management available with Freeform apps? Yes. Data Management metadata load is supported where there is at least one BSO cube. We will be supporting FreeForm apps with only ASO cubes through Data Management in the near term. The import of metadata using the Outline Load Utility (OLU) is an option. Chapter 4 FreeForm Apps FAQ 4-12
- 82. Do we lose any Planning Custom App Type related functionality in FreeForm apps? Common platform functionality which does not depend on required Planning dimensions is all available. Open dimensional approvals is on the roadmap. Can you use Groovy if you select FreeForm apps? Yes. All platform features are available with FreeForm apps. All business rules, including Groovy rules, are supported with FreeForm apps. Can you remove a dimension after adding it? You can unselect the dimension from the cube and the next cube refresh will remove the dimension association from that cube. Can you use Planning Migration files to create an application similar to the OTL or the Migration zip files? FreeForm apps are meant for Essbase outline/Migration imports or as build-from-scratch applications. On-premise Planning applications map to custom application types in EPM Enterprise Cloud. Can you import multiple outline or Migration files? FreeForm only accepts one outline or Migration file to create an application. Additional cubes can be created in the interface and associated to this outline. We don’t import multiple outline or Migration files into a single application. Is FreeForm only available with the Enterprise version of EPM (vs. what was previously called PBCS)? FreeForm apps are available with EPM Enterprise Cloud. How do you upload dimensions (and hierarchies) from a legacy Hyperion Planning application into EPM using FreeForm? Options are to load using an Essbase outline file (OTL), dimension extracts from source and import, manage using web interface/SmartView extension, or manually create. Can we refresh the database from Smart View? Yes, a refresh from Smart View is possible. Right-click on Dimensions, and then Refresh Databases. Are partitions enabled? No. Partitions are not required within FreeForm since it is a SaaS deployment in EPM Cloud where alternate solutions are available. Data maps and Smart Push can be used to feed data across cubes. Partitioning requires both Disk I/O and network access, both of which are not allowed by Oracle SaaS Cloud. In Cloud, the disk and network have been virtualized. With a mixture of ASO and BSO cubes in the same FreeForm app and with use of Hybrid BSO, data maps, Smart Push, and Groovy, partitioning is not necessary. How can we configure the security filters? Security is controlled through access controls, users are granted access to an application and then objects from there. In addition, cell-level security exists in FreeForm. Chapter 4 FreeForm Apps FAQ 4-13
- 83. Is the task management feature similar to Financial Consolidation and Close where it can be integrated, or is it just basic tasks? Can you please comment on this feature? FreeForm uses task lists. The Task Manager feature is now available in Planning applications, but not in FreeForm. How do you manage dimensions for FreeForm? Dimension management can be completed in a number of ways: • Manually in the solution using the web interface and Smart View • Integrated from a source solution using Data Management and import dimension jobs • Using an integration tool such as Oracle Fusion Cloud Enterprise Performance Management Infrastructure (OCI) • From Oracle Data Relationship Management (DRM) with integration • Using Oracle Enterprise Data Management Cloud, part of the EPM Enterprise solution, which provides a full enterprise data governance and control capability Can I take a backup of a FreeForm app and then migrate it to a Financial Consolidation and Close or Planning Modules Cloud application? No, FreeForm is a different business process and, as such, is not portable to other business processes. What about the business rules script, will they be migrated properly? And the configurable consolidation rule with regard to the Financial Consolidation and Close application? No, FreeForm is a different business process and, as such, is not portable to other business processes. Does migration of an OTL work with all versions of Essbase? You can use an outline (OTL) file or snapshot from an on-premises release 11.1.2.4.xxx (or later) single cube Essbase application to create a FreeForm app. For more information, see FreeForm App Sources. Is there no restriction for Data Integration in FreeForm that needs Scenario/Time period dimensions? To use Data Management in FreeForm you must have a minimum of Account, Period, and Scenario dimension types defined. For more information, see Loading Data to a Free Form Application in Administering Data Integration for Oracle Enterprise Performance Management Cloud. Can we import data if the application is already created? Data can be imported using the data import capability. For more information, see Importing Data. Migration-based data imports can only be used during application creation. Chapter 4 FreeForm Apps FAQ 4-14
- 84. Could you provide information about how the EPM Integration Agent feature is being used in Data Exchange? The EPM Integration Agent is a fully unified solution for extracting and transforming data and metadata from your on-premises or any system such as a third-party cloud, and delivering it to the Oracle Enterprise Performance Management Cloud. You can connect to and load data from on-premises data sources using custom SQL queries or pre-packaged queries to import data from sources such as EBS and the PeopleSoft General Ledger. For more information, see EPM Cloud to On-premises Connectivity Using the EPM Integration Agent in Administering Data Integration for Oracle Enterprise Performance Management Cloud. Is there the capability to create custom dimensions and business rules? Yes. FreeForm, by design, is a completely open business process and, as such, dimensions and business rules would all be custom built. What tuning capabilities, if any, will be made available for FreeForm apps? Since FreeForm apps are a SaaS application, tuning is managed by Oracle. To the extent needed, database properties are available within the Calculation Manager interface. Is partitioning supported? Transparent, Linked, Replicated? No. Partitions are not required within FreeForm since it is a SaaS deployment in EPM Cloud where alternate solutions are available. Data maps and Smart Push can be used to feed data across cubes. Partitioning requires both Disk I/O and network access, both of which are not allowed by Oracle SaaS Cloud. In Cloud, the disk and network have been virtualized. With a mixture of ASO and BSO cubes in the same FreeForm app and with use of Hybrid BSO, data maps, Smart Push, and Groovy, partitioning is not necessary. What about the MaxL Language for Admins, Automation, Shell integration? Direct scripting is prevented for SaaS Cloud security reasons. Given it is a SaaS platform, we don’t allow open ended scripts. There are other alternatives available in EPM Cloud for MaxL. EPM Automate, EPM Agent, and Groovy are good alternatives. Are the MDX functions going to be supported? MDX is already supported to some extent for ASO in FreeForm apps. MDX scripting for custom calc and allocation is exposed since 20.05 through Groovy scripts. Aside from Data Management/ETL how else can we recreate rules files in FreeForm apps? This could be cumbersome in Data Management. Currently we support import of Essbase format data into FreeForm apps. See Defining Data Load Rule Details in Administering Data Management for Oracle Enterprise Performance Management Cloud . For large scale ASO databases, what is the preferred data load mechanism in FreeForm apps? Use the Essbase file format or use Data Management. Chapter 4 FreeForm Apps FAQ 4-15
- 85. Any plans to create a CDF to Groovy migration tool? There are no plans for CDF migration to Groovy. Given Java security considerations, CDF migration cannot be done. Groovy is a good modern alternative. What Essbase artifacts can I migrate into FreeForm apps and how? Essbase Artifact FreeForm Import File? Notes Application and cube metadata Yes Cubes and outline metadata are imported. Calculation scripts Yes Imported into Calculation Manager and used as business rules Data Yes Level zero import from source or using Migration Disk volumes NA Drill through definitions No Managed through Data Management Excel workbooks and files NA Remapped with EPM Connections in Smart View Filters No Metadata security is maintained in relational schema. Linked Reporting Objects (LROs) No Attachments and comments are managed separately in EPM. Location aliases NA Log files No Outlines and formulas Yes Partitions No Alternatives with data maps and Smart Push across cubes are available. Report scripts No Other export alternatives are available. Rule files, text files, .csv files Yes Scenarios NA Substitution variables Yes Users No Managed separately in IDM in EPM SaaS Cloud User roles No Managed separately in IDM in EPM SaaS Cloud What objects are skipped when Essbase outline files or Migration files are imported into FreeForm apps? Essbase Artifact Reason object was skipped during import Custom Defined Function (CDF) CDFs are possible, but given Java security consideration, cannot be done now. Groovy is a good alternative. Custom Defined Macro (CDM) CDMs in Essbase are old artifacts. Using a Calculation Manager design time prompt on a rule is a better implementation of that same concept. Chapter 4 FreeForm Apps FAQ 4-16
- 86. Essbase Artifact Reason object was skipped during import Location Alias Location Alias is a short-cut name that allows you to reference a physical Essbase database through its server name, app name, database name, username, and password. FreeForm apps are self-contained within a single application with multiple databases. Data maps and Smart Push can be used within the application for this. Report Scripts Alternatives for data import and export are available in EPM Cloud through Groovy and EPM Automate. Load Rules Data Management offers the ability to pick up load rules, which can be done separately. How do Essbase features map to FreeForm apps in EPM Cloud? Native Essbase 11g Feature FreeForm Apps in EPM Cloud Active/Passive Cubes Can be supported using implementation setup Calc Scripts Business Rules Custom Defined Functions/Macros Groovy Database Versioning Automation with Migration snapshots. Additional pods. Oracle Essbase Administration Services Outline View/Edit Dimension Editor Essbase Cell-Level Security Cell-Level Security in EPM Cloud applications Linked Reporting Objects Cell Comments, Doc Attachments, Supporting Details Load Rules Data Management Rules, Groovy, Dimension/ Data Import, OLU Export, Level 0 (automated) exports MaxL scripts EPM Automate, EPM Agent, and Groovy Partitioning Cross-Cube Data Maps/Smart Push with Groovy is an effective alternative Report Scripts Export rules, other query/automation solutions in EPM Cloud Text List Smart List across all dimensions Chapter 4 FreeForm Apps FAQ 4-17
- 87. 5 Setting Up Access Permissions Assign access permissions to application artifacts such as dimensions, forms, dashboards, and task lists. Related Topics • About User and Role Management • Application Artifacts That Can Be Assigned Permissions • Types of Access Permissions • Managing Permissions to Artifacts • Reporting on Access Permissions • Retrieving Changed Information from Access Control About User and Role Management This business process employs several security layers to ensure security. Infrastructure components, which are implemented and managed by Oracle, create a secure environment for the application. Business process-level security is ensured by using the following mechanisms that permit only authorized users to access the application: • Single Sign-on (SSO) • Role-based access to the business process Global roles are granted through the Oracle Cloud Identity Console. See Getting Started with Oracle Enterprise Performance Management Cloud for Administrators . Access permissions are granted through the application interface and are described in this chapter. Tutorials Tutorials provide instructions with sequenced videos and documentation to help you learn a topic. Your Goal Learn How Learn how to manage security in Access Control and set up access permissions in the business process. The Background and Security Overview sections in this tutorial describes the layers of business process security. Setting Up Security in Planning Application Artifacts That Can Be Assigned Permissions You can assign permissions to: 5-1
- 88. • Dimensions, including user-defined dimensions Note: You can assign permissions to members by selecting the dimension property Apply Security. If you omit or clear the Apply Security setting, all users can access the dimension's members. By default, the Account, Entity, Scenario, and Version dimensions are enabled for access permissions. Optionally, you can enable this option for Period, Years, and Custom dimensions. See Editing Dimension Properties in the Simplified Dimension Editor. • Launch privileges to rules • Rule folders • Forms • Dashboards • Infolets • Reports, Books, and Bursting Definitions • Form folders • Dashboard folders • Infolet folders • Reports and Documents folders • Task lists • Groovy templates Types of Access Permissions Access permissions include Read, Write, and None. You can also set who can launch which rules. • Launch: Allow launch privileges Note: View user types have no Write permission to dimension members, so can't launch rules having runtime prompts that include members, dimensions, member ranges, or cross-dimension runtime prompt types. They can, however, launch rules having runtime prompts of other types (for example, date type). • No Launch: Disallow launch privileges Chapter 5 Types of Access Permissions 5-2
- 89. Note: If a user inherits Launch permission to a rule by belonging to a group, and is also assigned No Launch permissions by belonging to another group, the more restrictive No Launch assignment takes precedence. You can specify access permission for individual users and each group. When you assign a user to a group, that user acquires the group's access permissions. If an individual's access permissions conflict with those of a group the user belongs to, user access permissions take precedence. Inheriting Permissions Inheritance determines the user or group’s access permissions. You can specify an attribute that causes the children or descendants of that member to inherit its permissions. Assigned permissions take precedence over inherited permissions. You can include or exclude the member from the permissions setting. Table 5-1 Options for Inheriting Access Permissions Inheritance Option Permission Assignment Member Only to the currently selected member Children To all children members in the level below the currently selected member iChildren To the currently selected member and all children members in the level below it Descendant To all descendant members below the currently selected member iDescendant To the currently selected member and all descendant members below it How Permissions are Evaluated When evaluating permissions, the application gives precedence in this order: 1. Role-level security. Users with the Service Administrator role have permissions to all application elements. 2. For Power User, User, and Viewer user types, permissions that are specifically assigned to users. 3. Permission assignments that are acquired by belonging to a group. Note: If one member belongs to two groups with different permissions assigned to group members, the least restrictive permission takes precedence. For example, if one group assigns the member Read permission and another group assigns the same member Write permission, Write takes precedence. However if one of the groups assigns no permission (None) to its members, None takes precedence over Read and Write. 4. Parent-level assignments (for example, to parent members or folders). Chapter 5 Types of Access Permissions 5-3
- 90. Managing Permissions to Artifacts Related Topics • About Assigning Permissions to Artifacts, Rules, and Folders • Adding, Changing, and Removing Permissions to Artifacts and Folders • Adding, Changing, and Removing Permissions to Rules and Rules Folders About Assigning Permissions to Artifacts, Rules, and Folders Service Administrators can assign permissions to artifacts (forms, dashboards, infolets, reports, books, and bursting definitions), rules, and folders. For information on assigning permissions to dimension members, see Types of Access Permissions and Assigning Access to Dimension Members. Principles: • Artifacts (Forms, Dashboards, Infolets, Reports, Books, and Bursting Definitions): – Users and Power Users can view or enter data only into forms to which they have permissions (and can work only with members to which they have permissions). – Service Administrators and Power Users can design artifacts. – Power Users can access artifacts they created or to which a Service Administrator assigned them permissions. – Service Administrators have Write permissions to all dimension members and to all artifacts. • Rules: – Users and Power Users can see and launch only rules to which they are assigned Launch permission. – Rulesets inherit launch permissions from the rules included in the ruleset. • Folders: – Users who are assigned permissions to a folder can access the items in that folder, unless they are assigned more specific permissions. Likewise, Users have Launch permission to the Calculation Manager rules in folders to which they are assigned permissions, unless they are assigned more specific permissions. – When you assign permissions to a folder, all folders under it inherit that permission. – If you assign specific permissions (for example, None or Write) to a folder, that permission takes precedence over its parent folder's permissions. For example, if a user has Write permission to Folder1 that contains Folder2 to which the user has None permission, the user can open Folder1, but doesn't see Folder2. – If you assign specific permissions (for example, Launch) to a Calculation Manager folder, that permission takes precedence over its parent folder's Chapter 5 Managing Permissions to Artifacts 5-4
- 91. permissions. For example, if a user has Launch permission to RulesFolder1 that contains RulesFolder2 to which the user has No Launch permission, the user can open RulesFolder1, but doesn't see RulesFolder2. – If a user has None permission to a folder called Folder1 that contains a form called Form1 to which the user has Write permission, the user can see Folder1 and Form1. – If a user has No Launch permission to a Calculation Manager folder called RulesFolder1 that contains a rule called Rule1 to which the user has Launch permission, the user can see RulesFolder1 and Rule1. For procedures, see Adding, Changing, and Removing Permissions to Artifacts and Folders and Adding, Changing, and Removing Permissions to Rules and Rules Folders. Adding, Changing, and Removing Permissions to Artifacts and Folders The permissions assigned to artifacts (forms, dashboards, infolets, and reports, books, and bursting definitions) and folders refer to the ability to modify the artifact and folder definitions and not the underlying data. To assign permissions to artifacts and folders: 1. Navigate to the artifact (Data, Dashboards, Infolets, Reports, or Documents) listing page. 2. Click the Actions icon next to the artifact or folder, and then click Assign Permission. Note: You can assign permissions to only one artifact or folder at a time. 3. Click Permissions. 4. Perform a task: • To add permissions, click Add User/Group, and then select from the list of available users and groups. • To edit the type of permissions, select an option: – Click Read to allow the selected users and groups to view the artirfact or folder in the listing, but not allow them to create, edit, or delete the artifact or folder information. – Click Write to allow the selected users and groups to view the artifact or folder in the listing, and to create, edit, or delete the artifact or folder information. – Click None if you don't want the selected users or groups to view the artifact or folder in the listing. • To remove permissions, click next to the user or group. Adding, Changing, and Removing Permissions to Rules and Rules Folders To assign permissions to rules and rules folders: 1. Click Rules. 2. Select the rule or rule folder, click , and then click Assign Permission. Chapter 5 Managing Permissions to Artifacts 5-5
- 92. Note: You can assign permissions to only one rule or folder at a time. 3. Click Permissions. 4. Perform a task: • To add permissions, click Add User/Group, and then select from the list of available users and groups. • To edit the type of permissions, select an option: – Click Launch to allow the selected users and groups to launch the selected rules. – Click No Launch to prevent the selected users and groups from launching the selected rules. • To remove permissions, click next to the user or group. Reporting on Access Permissions You can view current access permissions and print reports. To report on current access permissions for users and groups in the application: 1. From the Home page, click Navigator , and then under Monitor and Explore, click System Reports. 2. Click Access Control. 3. On Select User or Group, select from the available options. 4. From the left Available panel, select and move users or groups on which to report to the Selected panel. 5. From the left Available Objects panel, select and move objects on which to report to the Selected Objects panel. 6. Select reporting options: • For Show Matching Access of Type, select the access to view: Read, Write, or None. • For Group the Results By, select how to view the report: Users or Objects. • From the Report Type sections, select Assigned Access or Effective Access: Chapter 5 Reporting on Access Permissions 5-6
- 93. Table 5-2 Access Report Types Report Type Description Options Assigned Access Summarizes access permissions that Service Administrators assign Specify whether access permissions are assigned by member selection relation or group membership: • Show matching access of relation: Member, Children, Children (inclusive), Descendants, or Descendants (inclusive). • Show Inherited From Group: Shows access permissions inherited by users in a group. Effective Access Summarizes access permission assignments as the application evaluates them (for example, by member selection relation, such as children, or group membership). This is useful if there are conflicts in access permissions. Note: Effective Access reports can't be generated for groups. Describe the origin of the effective access permissions by selecting Show effective access origin. For example, a user named JSomebody may be assigned Write access permissions to Entity1 and belong to a group named Sales that is assigned Read access permissions to Entity1. This setting would show that JSomebody has Write access permissions to Entity1 because individual assigned access permissions supersede access permissions inherited by group membership. 7. Click Create Report. Working with Access Permissions Reports The report on access permissions displays in Adobe Acrobat. You can use the Adobe Acrobat toolbar to work with the report. Retrieving Changed Information from Access Control Changes to group names or group membership from Access Control are not reflected in the application. To apply changes, you must reimport security artifacts. To synchronize information after modifying group properties: 1. Access the environment as a Service Administrator. 2. Click Tools, and then Migration. 3. Export Security artifacts: a. Click Core, and then select Security. b. Click Export. c. Enter a file name and click OK. d. Review the Migration Status Report to ensure that the export is successful. e. Click Close. 4. Import the snapshot that you created: Chapter 5 Retrieving Changed Information from Access Control 5-7
- 94. a. On the Migration page, click Snapshots. b. Under Actions, click next to the snapshot that you created in the preceding step, and then click Import. c. Click OK. d. Review the Migration Status Report to ensure that the import is successful. e. Click Close. Chapter 5 Retrieving Changed Information from Access Control 5-8
- 95. 6 Managing Applications View and manage applications, cubes, and dimensions using the application console. Related Topics • Application Overview Start here to learn about managing applications, dimensions, and dimension members. • Refreshing the Application Refresh the application whenever you make changes to the application structure. • Managing Cubes Use the cube editor to let you view or add cubes for Standard applications. • Managing Dimensions Start here to learn how to manage dimensions and dimension members. • Setting User Preferences • Administering Variables • Viewing Activity Reports Monitor user activities with activity reports. • Importing and Exporting Data and Metadata Move data and metadata in and out of the application using Planning . • Importing Exchange Rates for a Simplified Multicurrency Application Import exchange rates for a simplified multiple currency application using a template. • Creating and Refreshing Application Databases Things you need to know before you refresh the application database. • Adding an Aggregate Storage Outline to an Application Understand what aggregate storage is and how to use it in an application. • Converting an EPM Standard Cloud Service to EPM Enterprise Cloud Service Learn how to convert an EPM Cloud Service application from Standard to Enterprise. • Converting a Planning Application Learn how to convert Planning applications from Reporting to Standard, and from Standard or Reporting to Enterprise. • Removing an Application Proceed with caution when removing an application. • Setting the Daily Maintenance Process Start Time Understand how to determine and set the most convenient time to start the hour-long daily maintenance process. • Uploading and Downloading Files Using the Inbox/Outbox Explorer Use the Inbox/Outbox Explorer to upload files to the server or download them to your computer. 6-1
- 96. Application Overview Start here to learn about managing applications, dimensions, and dimension members. An application is a related set of dimensions and dimension members used to meet a set of business process needs. Each application has its own accounts, entities, scenarios, and other data elements. To create an application, see Creating a Planning Application. After an application is created, you can view and manage it using the application console. To view the application console, click Application, and then click Overview. The application console shows the application properties (including the application type) and application statistics, such as the number of tasks, plans, approval hierarchies, and rules in your application. It also lists the cubes (for Standard applications) and dimensions (for Reporting applications) used by the application. • To view the application overview, click Overview. • To manage cubes, click Cubes. See Managing Cubes. • To manage dimensions, click Dimensions. See Managing Dimensions. • To view activity reports, click Activity. See Viewing Activity Reports. Refreshing the Application Refresh the application whenever you make changes to the application structure. Changes you've made to the application are not reflected to users performing data entry and approvals tasks until you refresh the application. For example, if you modify properties of a dimension member, or add a member, or change access permissions, users will not see the updates you've made until you refresh the application. To refresh the application: 1. Click Application, and then click Overview. 2. Click Refresh. Note: The application is automatically refreshed during an application update. Information about the refresh is captured in a job called Content Update. To view the progress and details of the content update process, use the Jobs console, which you can access by clicking Jobs in the Application cluster in the Home page. See Viewing Pending Jobs and Recent Activity in this guide for information on how to view jobs, and Setting Content Update Start Time in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators for information about setting the Content Update start time. Chapter 6 Application Overview 6-2
- 97. Managing Cubes Use the cube editor to let you view or add cubes for Standard applications. You can add up to seven total cubes to a Standard application. After a cube is added, it will behave like any other cube. Videos Your Goal Watch This Video Learn how to manage cubes. Applications are made up of one or more cubes that store metadata and data. Managing Cubes in Planning Related Topics • Viewing and Managing Cubes • Adding Cubes • Clearing Cubes • Improving Cube Performance Viewing and Managing Cubes To view and manage cubes: 1. Click Application, and then click Overview. 2. Click Cubes. 3. Perform one task: • To view the details of a cube, click the name of the cube that you want to view. • To add a cube, click Create, then complete the cube details, and then click Done. Note: When you create a new block storage cube, you can select the option Enable Sandboxes. Selecting this option also provides the Enable Sandboxes option for Version members. See Managing Sandboxes. For cube details, see Adding Cubes. Note: You can rename a cube only during application creation. After a cube is added, you can't rename or delete it. Chapter 6 Managing Cubes 6-3
- 98. Adding Cubes You can add up to seven total cubes—three block storage cubes and three corresponding aggregate storage cubes plus one consolidating aggregate storage cube, each with a unique aggregate storage application name. After a cube is added, it behaves like any other application cube. If the cube maps to an aggregate storage database, then aggregate storage limitations apply. Note: For an aggregate storage cube, you must specify an application name to contain the database since an aggregate storage database must reside in its own application. Clearing Cubes Related Topics • About Clearing Cubes • Creating Clear Cube Jobs • Starting and Deleting Clear Cube Jobs • Scheduling Clear Cube Jobs About Clearing Cubes The application enables you to clear specific data within input and reporting cubes. You can start the Clear Cube job right away or schedule it to run later. Note: The Clear Cube job deletes the data you specify within input and reporting cubes, but it doesn't delete the cube definition in the application's relational tables. Creating Clear Cube Jobs To create a Clear Cube job: 1. Click Application, and then click Overview. 2. Click Actions, and then Clear Cube. 3. On the Clear Cube page, click Create, complete the job name, select the cube, then select a clear option: • Clear All: For both block storage and aggregate storage cubes, delete all data within a cube that is associated with the entities you select: Chapter 6 Managing Cubes 6-4
- 99. – Supporting Details – Comments – Attachments – Essbase Data • For block storage cubes only: – Upper-level blocks: Delete data in upper-level blocks – Non-input blocks: Delete data in non-input blocks – Dynamic blocks: Delete data in dynamic blocks – Empty blocks: Delete blocks with #MISSING values • For aggregate storage cubes only: – All Aggregations: Delete all aggregate views – Partial Data (Basic Mode): Clear the data in the specified region. You can select the point of view using the member selector . * Supporting Details * Comments * Attachments * Essbase Data Logical: In which the input cells in the specified region are written to a new data slice with negative, compensating values that result in a value of zero for the cells you want to clear. The process for logically clearing data completes in a length of time that is proportional to the size of the data being cleared. Because compensating cells are created, this option increases the size of the database. * Essbase Data Physical: In which the input cells in the specified region are physically removed from the aggregate storage database. The process for physically clearing data completes in a length of time that is proportional to the size of the input data, not the size of the data being cleared. Therefore, you might typically use this method only when you need to remove large slices of data. – Partial Data (Advanced Mode): Clear Essbase data only by using an MDX expression in the text box provided. * Essbase Data Logical: In which the input cells in the specified region are written to a new data slice with negative, compensating values that result in a value of zero for the cells you want to clear. The process for logically clearing data completes in a length of time that is proportional to the size of the data being cleared. Because compensating cells are created, this option increases the size of the database. * Essbase Data Physical: In which the input cells in the specified region are physically removed from the aggregate storage database. The process for physically clearing data completes in a length of time that is proportional to the size of the input data, not the size of the data being cleared. Therefore, you might typically use this method only when you need to remove large slices of data. 4. Click Save and Close. 5. To view the job on the Clear Cube listing page, click Refresh. Chapter 6 Managing Cubes 6-5
- 100. To start the Clear Cube job right away or to delete a job, see Starting and Deleting Clear Cube Jobs. To schedule a Clear Cube job to run immediately, later, or at intervals, go to the Jobs page. See Scheduling Jobs . Tip: To streamline the job creation process for subsequent Clear Cube jobs, you can duplicate an existing job using the Save As option, then update it. See Duplicating Jobs. Starting and Deleting Clear Cube Jobs To start a Clear Cube job right away or to delete a job: 1. Click Application, and then click Overview. 2. Click Actions, and then Clear Cube. 3. On the Clear Cube listing page, click next to the Clear Cube job that you want to start or delete, and then select one of the following options: • Click Submit to start the job right away. • Click Delete to delete the job. Scheduling Clear Cube Jobs You can schedule a Clear Cube job to run later or at intervals. To schedule a Clear Cube job, go to the Jobs page. See Scheduling Jobs. Improving Cube Performance Jobs You Can Schedule to Improve Cube Performance The application enables you to schedule jobs that improve cube performance. These jobs include: • Restructure Cube: Performs a full restructure of a block storage cube to eliminate or reduce fragmentation. This will also remove empty blocks. Running this job won't push any changes from the business process to Essbase. • Compact Outline: Compacts the outline file of an aggregate storage cube. Compaction helps keep the outline file at an optimal size. Compacting the outline doesn't clear the data. Running this job won't push any changes from the business process to Essbase. • Merge Data Slices: Merges incremental data slices of an aggregate storage cube. Fewer slices improve a cube’s performance. You can merge all incremental data slices into the main database slice or merge all incremental data slices into a single data slice without changing the main database slice. You can optionally remove cells that have a value of zero. • Optimize Aggregation: Generates optimized views based on collected query tracking information in an aggregate storage cube. This job has two actions: Chapter 6 Managing Cubes 6-6
- 101. – Enable Query Tracking: Records a meaningful set of queries, and then uses the recorded query data to select the most appropriate set of aggregate views to materialize for that database. You must enable query tracking and allow it sufficient time to collect data before executing the aggregation process based on query data. Once enabled, query tracking continues until query tracking is disabled, the cube is reloaded or refreshed, the outline is compacted, the application is shut down, or additional aggregate views are materialized for the database. Query tracking does not resume automatically after these actions occur. Note: The following actions clear the stored query tracking information from the aggregate storage cube, but they do not disable query tracking: * Merging incremental data slices * Clearing data * Clearing existing aggregations * Clearing partial data * Loading data into the aggregate storage cube – Execute Aggregation Process: Calculates aggregations for aggregate storage databases that contain data and to which you are granted Calculation permission. To perform an aggregation, you use system recommended views. The selection of views and aggregation processes are combined into one, non-configurable operation performed by the server. You can optionally specify the maximum disk space for the resulting files, base the view selection on user querying patterns, and include rollup hierarchies in the view selection. Select one or more of the following options: * Based on query data?: Aggregate the views the server selects, based on collected user querying patterns. This option is only available if query tracking is turned on. * Include rollup option?: Include secondary hierarchies (with default level usage) in the view selection process. * Include growth size option?: Aggregate the views the server selects, until the maximum growth of the aggregated database exceeds limits you specify. Enter the size (in ratio) beyond which the server should stop the aggregation. You can start the jobs right away or schedule them to run later. Note: Users can stay logged in during these actions. Related Topics • Scheduling Jobs • Optimize BSO Cubes in Oracle Enterprise Performance Management Cloud Operations Guide Chapter 6 Managing Cubes 6-7
- 102. • Optimizing Aggregate Storage Option Cubes in Oracle Enterprise Performance Management Cloud Operations Guide Managing Dimensions Start here to learn how to manage dimensions and dimension members. Dimensions categorize data values. These dimensions are provided with the application: Account, Entity, Scenario, Version, Period, Currency (for a multicurrency application), and Years. Dimensions on the Dimensions page are listed in order of precedence. The order of dimensions is critical for the structure and performance of an application. The order of your dimensions determines how your data calculations will perform. Evaluation Order enables you to specify which data type prevails when a data intersection has conflicting data types. For example, if Account members are set to the Currency data type, and Product members are set to the Smart List data type, you can set whether the Currency or Smart List data type prevails at an intersection. Note: For a Smart List to be viewable in forms, the dimension to which the Smart List type member belongs must be first in the evaluation order. See Working with Smart Lists. To manage dimensions: 1. Click Application, click Overview, and then click Dimensions. 2. Perform a task: • To filter the dimensions by cube, see Filtering the Dimension View by Cube. • To view and edit the properties of dimensions and their members, click the name of the dimension. See Editing Dimensions in the Simplified Dimension Editor. • To reorder the dimensions, click the up or down arrow in the Order column next to the dimension that you want to move. • To set a different evaluation order, click the Evaluation Order field next to the dimension that you want to update. • To rename a dimension, click the name of the dimension that you want to rename, select the Edit Dimension Properties tab, and then enter a new name in the Dimension field. See Editing Dimension Properties in the Simplified Dimension Editor. • To create a dimension, click Create. See Creating Dimensions. • To import metadata, click Import. See Importing Metadata. • To export metadata, click Export. See Exporting Metadata. Chapter 6 Managing Dimensions 6-8
- 103. Filtering the Dimension View by Cube For a Standard application, you can filter the dimension view by cube. When you select a cube, only dimensions used in that cube are displayed. To filter the dimension view by cube: 1. Click Application, click Overview, and then click Dimensions. 2. Click the down arrow to the right of Cube to filter the list of dimensions by cube. By default, the application displays all cubes for a standard application. If the dimension list is filtered, the application displays only the dimensions used in the selected cube. Filtering by cube (rather than viewing all cubes) also enables you to view these details about a dimension: • Order of precedence • Dimension density Note: The Dense column is hidden for applications that contain only ASO cubes. If an application contains a BSO cube or a BSO and an ASO cube, the Dense column displays for both cubes. • Evaluation order For information about editing dimensions, see Editing Dimensions in the Simplified Dimension Editor. Creating Dimensions Creating a dimension adds it to the list of dimensions in the dimension view. To create a dimension: 1. Click Application, click Overview, and then click Dimensions. 2. Click Create. 3. On the Create Dimension page, enter or select values for the properties that are displayed. For descriptions of the properties, see Editing Member Properties in the Simplified Dimension Editor. For information about editing dimensions, see Editing Dimensions in the Simplified Dimension Editor. Setting User Preferences Service Administrators specify defaults for the current application. However, users can override these application defaults by setting preferences to control many aspects of the application, such as their profile photo and how numbers display in the application. Chapter 6 Setting User Preferences 6-9
- 104. To learn more about user preferences options, see Setting Your Preferences in Working with Planning . To learn more about application defaults and system settings, see Managing Application and System Settings. Administering Variables Related Topics • Working with Substitution Variables • Working with User Variables Working with Substitution Variables Related Topics • About Substitution Variables • Creating and Assigning Values to Substitution Variables • Deleting Substitution Variables About Substitution Variables Substitution variables act as global placeholders for information that changes regularly. For example, you could set the current month member to the substitution variable CurMnth so that when the month changes, you need not update the month value manually in the form or the report script. You create and assign values to substitution variables within the application. These substitution variables are then available in the application when you select members for a form. For more information about selecting substitution variables, see Selecting Substitution Variables as Members. Note: If you migrated an application that uses Global variables, you can view, but not edit, them in the application. Creating and Assigning Values to Substitution Variables To create a substitution variable and assign values to it: 1. From the Home page, click Tools, and then click Variables. 2. Select the Substitution Variables tab. 3. Click . A new variable is added to the bottom of the list. 4. Scroll to the bottom of the list, click the down arrow next to the Cube name for the newly added variable, and then select the cube. Chapter 6 Administering Variables 6-10
- 105. 5. For Name, enter the name of the substitution variable (up to 80 characters). 6. For Value, enter a value for the substitution variable (up to 255 characters). Note: • You can specify a range of values when defining substitution variables; for example, FY16:FY18. You can define a substitution variable range for base members and parent members. For base members, you can use a single colon (:) or a double colon (::) as delimiters; for example, SunEnT 110::111. However for parent members, you can only use a single colon (:). • If the substitution variable will be used in data export job definitions for block storage cubes and the member name is numeric only, the member name must be placed in double quotation marks in the Value field; for example, "1100" or "000". The double quotation marks aren't necessary for alphanumeric member names; for example, a1110. However if this variable will be selected in data export job definitions for aggregate storage cubes, you can't place the member name in double quotation marks in the Value field. Therefore if you need to use the same member name in substitution variables for data export jobs defined for both types of cubes, you must define two different substitution variables; one with quotes and one without 7. Click Save. Deleting Substitution Variables To delete substitution variables: 1. From the Home page, click Tools, and then click Variables. 2. Select the Substitution Variables tab. 3. Next to the substitution variable you want to delete, click . 4. To confirm deletion, click Yes. Working with User Variables Related Topics • About User Variables • Creating User Variables • Managing User Variables • Setting Limits for User Variables on Forms • Deleting User Variables Chapter 6 Administering Variables 6-11
- 106. About User Variables User 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 must create the user variable. When you create forms with user variables, users must first select values in preferences for the variable before opening forms. Afterward, users can change the variable on the form only if it's a dynamic user variable. Otherwise, they must continue to set the variable in preferences. For example, if you create a user variable called Division, users must select a division before working in the form. Tip: Attributes are another way to filter forms. But instead of explicitly filtering by an attribute (like Red), you can create a user variable for the attribute dimension, and then use the user variable as the filter. Then you can enable the user variable as a dynamic user variable which allows users to change the value of the filter at runtime. This is a useful technique that allows for dynamic filtering. The first time users select a variable for a form, they must do so in preferences. After that, they can update the variable in preferences or in the form. For information about selecting user variables as members, see Selecting User Variables as Members. Creating User Variables To create user variables: 1. From the Home page, click Tools, and then click Variables. 2. Select the User Variables tab. 3. Click . A new variable is added to the bottom of the list. 4. Scroll to the bottom of the list and click the down arrow next to the Dimension name for the newly added variable. For Select Dimension, select the dimension for which to create a user variable (including attribute dimensions). 5. In the User Variable Name column, enter the name of the user variable. 6. Click to select dimension members. Chapter 6 Administering Variables 6-12
- 107. Note: The Use Context setting means the value can't be chosen by the user from user preferences. Instead, the value is passed from another form based on its Point of View context and the value will change dynamically based on the context of the form. However if the user variable is used elsewhere, such as in rows and columns, you must create a different user variable so the user can set its own value for it because it won’t be set dynamically. 7. Click OK. You can now associate the user variable with a form. See Selecting User Variables as Members. You can also set limits for user variables on forms. See Setting Limits for User Variables on Forms. Afterward, users can select members for the user variable. See Working with Planning . Managing User Variables You 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 called Division for the Entity dimension, users can select a member for their own division. You can create any number of user variables for each dimension (including attribute dimensions), and select user variables for any axis in the form. See Defining Form Page and Point of View. The typical sequence of steps: 1. If necessary, create the appropriate parent-level members in the dimension outline. 2. Define user variables for each dimension you want users to be able to filter (including attribute dimensions). See Creating User Variables. 3. When designing the form, associate the user variable with the form. See Selecting User Variables as Members. 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 member for User Variable Options in preferences. After selecting an initial value, they can change it in the form or in preferences. See Working with Planning . Setting Limits for User Variables on Forms You can limit which members users can see or select on individual forms by limiting their member selections for a user variable. The user variable limit applies the restriction to all users at the form level, regardless of their access permissions. In addition to setting the limits by members, Service Administrators can select limits by function (for example, "IChildren(Existing Employees)". To set up user variable limits: 1. During form design, select Enable Dynamic User Variables to allow dynamic user variables in the form. See Setting Form Precision and Other Options. Chapter 6 Administering Variables 6-13
- 108. 2. Create a user variable. See Creating User Variables. 3. In the User Variable Definition field on the Variables page under the User Variables tab, click , and add or remove members to set limits. To select members by function, click and select from the available options. 4. In the form designer, assign the user variable to the page axis. See Defining Form Page and Point of View. Deleting User Variables You can delete user variables if they are not associated with a form. If you attempt to delete a user variable that is used in a form, you'll see an error message saying it cannot be deleted. The message will also provide the names of the forms where the user variable is used. To delete user variables not associated with forms: 1. From the Home page, click Tools, and then click Variables. 2. Select the User Variables tab. 3. Next to the user variable you want to delete, click . 4. To confirm deletion, click Yes. Viewing Activity Reports Monitor user activities with activity reports. The Activity Report enables Service Administrators to understand application usage. It also helps streamline application design by identifying user requests, calculation scripts, forms, reports, and so on. Two versions of the report; an HTML version and a JSON version, are available. Oracle Enterprise Performance Management Cloud retains Activity Reports for the last 60 days only. Oracle recommends that you download and create backup copies on a local computer to analyze them for historical trends. The Activity Report is automatically generated in these situations: • Every day during daily maintenance of the service • Each time you submit a Provide Feedback submission • Every time you execute the resetService EPM Automate command to restart an environment. For details about the information that is provided in activity reports, see Activity Report Contents in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators. To view activity reports: 1. Click Application, and then click Overview. 2. Click Activity Reports. Chapter 6 Viewing Activity Reports 6-14
- 109. 3. To view the report details, click View next to the name of the report that you want to view. Importing and Exporting Data and Metadata Move data and metadata in and out of the application using Planning . Related Topics • Importing Metadata You can import metadata from a flat file in a comma-delimited, tab-delimited, or other format. • Exporting Metadata You can export metadata to a flat file in a .csv (comma-delimited) or .txt (tab-delimited or other delimiter character) format. • Importing and Exporting Data Importing Metadata You can import metadata from a flat file in a comma-delimited, tab-delimited, or other format. These artifacts are supported in the imports: • Dimensions • Smart Lists • Exchange rate tables To import metadata, perform these tasks: • Create an import file for each artifact that you want to import. See Creating the Metadata Import File. • Load the import file or files (you can import multiple dimension files at the same time). See Loading the Metadata Import File. Note: • You cannot rename members of attribute dimensions during a metadata import. Renaming of members will be ignored. • You cannot delete attribute dimensions while importing metadata. Videos Your Goal Watch This Video Learn how to import metadata. Importing Metadata in Cloud EPM Creating the Metadata Import File Related Topics • About the Metadata Import File Chapter 6 Importing and Exporting Data and Metadata 6-15
- 110. • Example Entity Dimension Import File • Other Supported Delimiter Characters About the Metadata Import File Before you begin loading, you must create an import file for each artifact you want to import (dimensions, smart lists, and exchange rate tables). The import file must contain a header record, and then below the header record, a list of metadata records that you want to import or update. The file format can be .csv (comma-delimited) or .txt (tab-delimited or other delimiter characters). 1. A header record, the first line in the file: • Lists the dimension and any member properties used by subsequent metadata records; the header record and subsequent records don't need to include all properties; properties that are not included are inherited from the corresponding parent's default property value • Is case sensitive • Can list properties in any order, as long as the subsequent metadata records are in the same order • Can use comma or tab delimiters. Other delimiter characters can be used if they are supported and the same delimiter character is used throughout the file. For a list of supported delimiter characters and exceptions, see Other Supported Delimiter Characters. 2. After the header record, a list of metadata records that you want to import or update. Each metadata record contains a delimited list (comma, tab, or other) of property values that matches the order designated in the header record. A metadata record can skip a property that is specified in the header record; in this case, the default property is assumed. Note: Only characters that are included in the UTF-8 character set are supported in import or export files. Characters that aren't included in the UTF-8 character set are considered invalid. For dimension name restrictions, see Naming Restrictions for Dimensions, Members, and Aliases. For an example import file, see Example Entity Dimension Import File. Example Entity Dimension Import File Chapter 6 Importing and Exporting Data and Metadata 6-16
- 111. In this example, the import file loads an Entity dimension with the required header record and three data records. This example is comma-delimited. The header record specifies the member to be imported (Entity), the parent member (Parent) into which to import 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 members exist: Entity e1 e2 e1(Shared) The first data record (e1, Entity) imports Entity member e1 as a child under the root member Entity. Unspecified values assume the default. For example, if data storage isn't 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 is specified, 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 data storage to Shared. Other Supported Delimiter Characters In addition to commas and tabs, the application supports these delimiter characters in import and export files: • tilde (~) • grave accent (`) • exclamation point (!) • number sign (#) • question mark (?) • dollar sign ($) • percent sign (%) Chapter 6 Importing and Exporting Data and Metadata 6-17
- 112. • caret (^) • ampersand (&) • asterisk (*) • parentheses ( ) • hyphen-minus (-) • plus (+) • colon (:) • semicolon (;) • 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 export scenarios. Note the following exceptions. Import and Export Metadata Delimiter Exceptions Don't use these delimiter characters in metadata import and export files. Table 6-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 file contains consolidation properties that use these characters angle brackets (< >) Causes an error if a property uses the value <none> Chapter 6 Importing and Exporting Data and Metadata 6-18
- 113. Note: Any character that conflicts with a character in a member name will cause an error. Import and Export Data Delimiter Exceptions Table 6-2 Import and Export Data Delimiter Exceptions Delimiter Character Reason for Exception apostrophe (') Causes an error if used in a cube name parentheses ( ) Causes an error if used in a data import file double quotation mark ("") Creates an empty file hyphen-minus (-) Causes an error if used in a data import file Loading the Metadata Import File To load the metadata import file: 1. Create a metadata import file for each artifact (dimensions, smart lists, and exchange rate tables) that you want to import. See Creating the Metadata Import File. 2. Click Application, and then click Overview. 3. Click Dimensions, and then click Import. 4. On the Import Metadata page, click Create. 5. Select the location of the metadata import file or files: • Local: Loads the import file or files from a location on your computer. For Import File, click Browse to select the import file on your computer for the artifact you're importing. • Inbox: Loads the import file or files from the server. Enter the name of the file in Import File. See Uploading and Downloading Files Using the Inbox/Outbox Explorer. 6. For File Type, select Comma delimited, Tab delimited, or Other. If Other is selected, enter the delimiter character that is used in the import file. For a list of supported delimiter characters and exceptions, see Other Supported Delimiter Characters. 7. Select Clear Members to delete members not explicitly specified in the load file before performing the import. Chapter 6 Importing and Exporting Data and Metadata 6-19
- 114. Note: • Any member not specified is deleted from the application outline after importing the dimension unless it's an ancestor of a member that was specified, or it's a base member of a shared member that was specified. • If Clear Members isn't selected, the import will only add or update existing members. Oracle recommends loading the metadata file without selecting Clear Members to make sure the file loads successfully. Then, select Clear Members and execute the import again • Clear Members is unavailable in certain dimensions where members must exist and are critical to the application. Currently, these dimensions are Currency, Period, Scenario, Version, and Years. • Members that can't be deleted in the dimension editor for any reason (for example, because they're used in a form or in a validation rule) won't be deleted. 8. Optional: If the location selected is Inbox, click Save as Job to save the import operation as a job, which you can schedule to run right away or at a later time. You can't select this option if Local is selected. See Managing Jobs. Note: • Saving an import operation as a job is useful to batch a load sequence; for example, import metadata, then import data, then run rules when the data load is complete. • You can run up to five import jobs at one time. • If you want to review the data that was rejected during the metadata import job, you can specify an Error File on the Save as Job dialog. This file will provide information about the metadata records that were not imported for each dimension. If an error zip file is specified, a separate error file is created for each dimension, then the error files are zipped together, and the zip file is stored in the Outbox where you can download the file using Inbox/Outbox Explorer. See Uploading and Downloading Files Using the Inbox/Outbox Explorer. Tip: To streamline the job creation process for subsequent Import Metadata jobs, you can duplicate an existing job using the Save As option, then update it. See Duplicating Jobs. 9. Optional: If the location selected is Local, click Validate to test whether the import file format is correct. Chapter 6 Importing and Exporting Data and Metadata 6-20
- 115. 10. Click Import to run the import operation. If the cubes listed in the import file don't match the cube names in the application, the application will ignore unrecognized cube columns. If the import fails, a Failed status will display in the Last Validate/Import column. Click Failed to view the detailed status. If the import is successful, a Completed status will display in the Last Validate/Import column. To view details about the successful import, click Completed, and then in the Show drop-down, select All. When performing metadata loads as a part of cloning environments or importing snapshots using Migration or EPM Automate, Oracle Enterprise Performance Management Cloud uses the multi-pass solution. This solution automatically initiates another load of the same metadata input file if the previous metadata load resulted in rejected records. Exporting Metadata You can export metadata to a flat file in a .csv (comma-delimited) or .txt (tab-delimited or other delimiter character) format. These artifacts are supported in the exports: • Dimensions • Smart Lists • Exchange rates The application creates an export file for each artifact (.txt or .csv, depending on the file type), and all export files are consolidated into one zip file. You must extract the .csv or .txt files from the zip file if you want to use the files as import files (for example, when importing into another application). Note: Only characters that are included in the UTF-8 character set are supported in export or import files. Characters that aren't included in the UTF-8 character set are considered invalid. For dimension name restrictions, see Naming Restrictions for Dimensions, Members, and Aliases. Videos Your Goal Watch This Video Learn how to export metadata. Exporting Metadata in Cloud EPM To export metadata to a flat file: 1. Click Application, and then click Overview. 2. Click Dimensions, and then click Export. 3. On the Export Metadata page, click Create. 4. Select the target environment of the export file: • Local: Saves the export file to a location on your local computer. Chapter 6 Importing and Exporting Data and Metadata 6-21
- 116. • Outbox: Saves the export file to the server where you can use it to schedule the export job. See Uploading and Downloading Files Using the Inbox/Outbox Explorer. Click Save as Job to save the export operation as a job, which you can schedule to run right away or at a later time. You can't select this option if Local is selected. Note: – You can run up to five export jobs at one time. – When scheduling export jobs, you can specify a unique output file name for each job. – For more information about scheduling jobs, see Managing Jobs. Tip: To streamline the job creation process for subsequent Export Metadata jobs, you can duplicate an existing job using the Save As option, then update it. See Duplicating Jobs. 5. Select the artifact or artifacts to export. 6. Select an option: • 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 that you want to use in the export file. For a list of supported delimiter characters and exceptions, see Other Supported Delimiter Characters. 7. Click Export, and then specify where to save the export file. Importing and Exporting Data After the dimensions are imported, you can populate the application data. You can't do a direct data load. You must import data from a file. Videos Your Goal Watch This Video Learn how to export and import data in your business process. Exporting and Importing Data in Planning Related Topics • Importing Data • Driver Member Casting Errors Chapter 6 Importing and Exporting Data and Metadata 6-22
- 117. • Exporting Data • Viewing Data Import and Export Status Importing Data Before importing data, you must: • Define or load metadata and refresh the database. See Importing Metadata. • Prepare the data load file. Source data must be in a business process-specific data file format or in an Essbase data file format. • Ensure the data load files do not contain any thousands separators, quotes, and so on, around data values. Up to one single . (decimal point) character is supported. • Ensure the data import file type is .csv, .txt, or .zip. You can create a data import file based on a template, or you can generate one based on the source system. To use a template, run the export data process in your business process and use the exported file as a template. See Exporting Data. Note: When importing data, no validation is performed on intersections to determine which are valid, and data is loaded to all intersections. To review data that has been loaded into invalid intersections, run the Invalid Intersection report before importing data to see and clear invalid intersections. See Working With Invalid Intersection Reports. To import data: 1. Click Application, and then click Overview. 2. Click Actions, and then click 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. See Uploading and Downloading Files Using the Inbox/Outbox Explorer. Note: Valid data import file types are .csv, .txt, or .zip. 5. Select the Source Type of the data import file: • Default: Select this source type to load data in a business process-specific data file format. If you select this option, you must choose between Comma delimited, Tab delimited, or Other. Chapter 6 Importing and Exporting Data and Metadata 6-23
- 118. Note: – If an import error occurs during a business process-specific data load, the import will continue to load valid data (partial load). Any errors will be noted in the import and export status. See Viewing Data Import and Export Status. – For a list of supported delimiter characters and exceptions, see Other Supported Delimiter Characters. – If data is exported to a file in a business process-specific format, you can use Notepad to change the database name in the file; for example, ASOCube, and then import the data file into the aggregate storage outline (provided all dimensions exist in the aggregate storage outline). • Essbase: Select this source type to load data in an Essbase data file format. If you select this option, you must choose a cube. For Delimiter, specify the delimiter for the Essbase data; options are Space or Tab. Note: Stop In Case of Error is selected by default. If this option is selected and any import errors occur during an Essbase data load, the import will quit and no data will be loaded. If this option is cleared, data will continue to load even if there are errors. 6. Enter or select the source file: • If you selected Local, click Browse to navigate to the source file. • If you selected Inbox, enter the name of the file in Source File. 7. Optional: Clear Include Metadata to improve data import performance and to prevent members from changing position in the outline during data import. Regardless of this option setting, the required metadata must already exist in the business process and in the Essbase outline before you can load the application data. 8. Click Save as Job to save the import operation as a job, which you can schedule to run later. Chapter 6 Importing and Exporting Data and Metadata 6-24
- 119. Note: • Save as Job is available only when Inbox is selected. • Saving an import operation as a job is useful to batch a load sequence, for example, import metadata, then import data, then run rules when the data load is complete. See Managing Jobs. • You can run up to five import jobs at one time. • If you want to review the data that was rejected during the data import job, you can specify an Error File on the Save as Job dialog. This file will provide information about the data records that were not imported. If an error zip file is specified, the zip file is stored in the Outbox where you can download the file using Inbox/Outbox Explorer. See Uploading and Downloading Files Using the Inbox/Outbox Explorer. Tip: To streamline the job creation process for subsequent Import Data jobs, you can duplicate an existing job using the Save As option, then update it. See Duplicating Jobs. 9. Optional: Click Validate to test whether the import file format is correct. 10. Click Import to run the import operation. Note: There is no import option in this business process to clear data before import. Therefore, the import will not overwrite existing data values with #MISSING values. However, you can run a clear cube job prior to import, or clear data with a script/rule or using the REST API: • You can run a Clear Cube job that enables you to clear specific business process data within input and reporting cubes. See Clearing Cubes. • You can write a business rule that uses the CLEARDATA Essbase command to clear specific data values. See CLEARDATA in Technical Reference for Oracle Analytics Cloud - Essbase . • You can use the Clear Data Slices REST API to clear business process and Essbase data for a specified region. See Clear Data Slices in REST API for Enterprise Performance Management Cloud. Caution: If the evaluation order in the application is changed after exporting data, the import may have unexpected results. Chapter 6 Importing and Exporting Data and Metadata 6-25
- 120. If a value in a data load input file doesn't match the evaluated driver member type; for example, if the evaluated type of a driver member is "date" and it's corresponding input value isn't a valid date format, a driver member casting error occurs. See Driver Member Casting Errors. Table 6-3 Videos Your Goal Watch This Video Learn the highlights of loading data into your business process. Overview: Loading Data in Planning and Budgeting Cloud Table 6-4 Tutorials Your Goal Learn How Learn how to import and export data in your business process, including importing exchange rates into multicurrency business processes. Loading Data in Planning Driver Member Casting Errors A driver member casting error occurs when a value in a data load input file doesn't match the evaluated driver member type. Here are some examples of driver member casting errors: • If a driver member is of type "Date" and it's corresponding input value isn't a valid date format • If a nonexistent Smart List value is specified for a driver member of type "Smart List" • If a nonnumeric value is supplied for a member of type "Currency," "Data," or "Percent." A casting error can occur for each driver member specified in the input file and for every occurrence in a data record, so the number of casting errors for a given input record ranges from 0 to the number of drivers. Because successful driver member bindings can occur along with driver member binding errors, the application will not reject the entire input record, but the error will be noted in the import and export status. See Viewing Data Import and Export Status. Consider the following data record input file where a bad date value is specified: Entity, aDate, aSl, aText, aCurr, aPercent, Point-of-View,Data Load Cube Name e1, exampleBadDateValue, sl1, text11, 888, 0.99, "FY15,Current,""BUVersion_1"",Local,u1,Jan",Plan1 Error messages displayed: • After loading the data, the status window will read: Outline data store load process finished (Invalid data values were not loaded). 7 data records were read, 7 data records were processed, 7 Chapter 6 Importing and Exporting Data and Metadata 6-26
- 121. were accepted for loading (verify actual load with Essbase log files), 0 were rejected. • The error is noted as an error in the import and export status with the following entry details: Category: Data record Record Index: 2 Message: Unable to load specified data value in Record 2: (aDate: exampleBadDateValue) • If multiple casting errors occur, each error is recorded in the same error message: Unable to load specified data values in Record 2: (aSl: aaaaaaasl1), (aPercent: cc), (aDate: exampleBadDateValue), (aCurr: bb) • If the error message count exceeds the maximum limit, it will issue the following message: The warning [Unable to load specified data values] message count limit (100) exceeded: no more warnings of this type will be issued. Exporting Data To export data to a file: 1. Click Application, and then click Overview. 2. Click Actions, and then click Export Data. 3. Click Create. 4. On the Export Data page, select the target environment 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. See Uploading and Downloading Files Using the Inbox/Outbox Explorer. 5. Select the cube. Note: The driver/column dimension in the Export Data job definition needs to be dense. 6. Select the file type: • 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 that you want to use in the export file. For a list of supported delimiter characters and 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 dynamic calculation members during export. Chapter 6 Importing and Exporting Data and Metadata 6-27
- 122. Note: Excluding dynamic members from exported data improves performance during data exports. 9. For Decimals, specify the number of decimal positions (0-16) to format the data after export, or select the default None to use the default precision formatting. For example, specifying a decimal value of 3 in the Decimals field will result in the exported data displaying three digits to the right of the decimal point, wherever applicable. Note: Selecting None formats the decimal number as specified in the default precision settings, whereas selecting 0 formats the data to display a whole number. For example, if the data value you are exporting is 123.45678, selecting 0 will export the data as 123 and selecting None will export the data as 123.45678. 10. Select the slice of data to be exported. Note: If you're exporting data from an aggregate storage cube and you're exporting multiple members simultaneously, make sure that at least one of the members you select is a non-shared member. You can export shared members individually because it's equivalent to selecting a base member. However, selecting level 0 descendants of a parent member whose descendants are all shared members is equivalent to not selecting any members from a dimension and the export will not run. Therefore, you must ensure that one of the members selected is a non- shared member. 11. Optional: Click Save as Job to save the export operation as a job, which you can schedule to run immediately or at a later time. Note: • Save as Job is available only when Outbox is selected. • You can run up to five export jobs at one time. • When scheduling export jobs, you can specify a unique output file name for each job. • For more information about scheduling jobs, see Managing Jobs. Chapter 6 Importing and Exporting Data and Metadata 6-28
- 123. Tip: To streamline the job creation process for subsequent Export Data jobs, you can duplicate an existing job using the Save As option, then update it. See Duplicating Jobs. 12. Click Export, and then specify where to save the data export file. Note: To reduce the size of data export files, if a form has an entire row of #MISSING values, the row will be omitted from the data export file. Viewing Data Import and Export Status To view the status of a data import and export: 1. Click Application, and then click Jobs. 2. Click the name of the import or export job under Recent Activity. The status page displays messages for Errors, Warnings, Info, and All. If there are errors and you specified an error file name while defining the job, you can download the generated error file using the Error File link. Importing Exchange Rates for a Simplified Multicurrency Application Import exchange rates for a simplified multiple currency application using a template. To simplify managing exchange rates for a simplified multiple currency application, you can export the provided template, enter exchange rates in a spreadsheet, and import the rates to your application. You can import exchange rates right away or schedule an Import Exchange Rates job to run later. Note: To view the exchange rates options, the application must have been created with the Multicurrency option enabled and the Multicurrency Type must be Simplified. A Currency dimension is then created. If you're unsure whether your multicurrency application is simplified, the existence of a Currency dimension will confirm it. See About Simplified Multicurrency. To import exchange rates using a template: 1. From the Home page, click Application, and then Overview. Chapter 6 Importing Exchange Rates for a Simplified Multicurrency Application 6-29
- 124. 2. From the Actions menu, select Export Exchange Rate Template, and then open ExchangeRateTemplate.csv or save it locally. 3. In the template file, enter average and ending currency exchange rates for each period and each currency, specify members for the POV, and then save the file. Note: The number 1 represents the exchange rate for the default currency in the application. Enter rates relative to the default currency. 4. From the Actions menu, select Import Exchange Rates, click Create, browse for the file, and then click Import. Note: You can schedule the import to run as a job that runs right away or at a later time. To schedule an Import Exchange Rates job, select the Inbox option, point to an import file that is located in the Inbox, and then click Save as Job. See Scheduling Jobs. Tip: To streamline the job creation process for subsequent Import Exchange Rates jobs, you can duplicate an existing job using the Save As option, then update it. See Duplicating Jobs. Creating and Refreshing Application Databases Things you need to know before you refresh the application database. Related Topics • Creating Application Databases • Before Refreshing the Database • Refreshing Application Databases Creating Application Databases The application database, which stores data for each cube in the application, is created when the application is created. To create a Planning application, see Creating a Planning Application. If you need to clear the data, you can do so using Calculation Manager. To refresh the data, see Refreshing Application Databases. Chapter 6 Creating and Refreshing Application Databases 6-30
- 125. Before Refreshing the Database You must refresh the database after changing the application structure, and modifying artifacts such as dimensions and members. Oracle recommends that you notify all users, asking them to save their work and close the application, before you refresh the database. Before refreshing the database: • Back up your application and export data from all databases. • Decide if you want to enable all users or just the current Service Administrator to use the application in administration mode during the refresh • Decide if you want to log off all users • Terminate any active application requests Refreshing Application Databases To refresh the database: 1. See Before Refreshing the Database. 2. Click Application, and then click Overview. 3. Click Actions, and then Refresh Database. 4. On the Refresh Database page, click Create, and then select from the following options: Before Refresh Database • Enable use of the application for: Lets All users or Administrators (or the current logged in Service Administrator) access the application in administration mode during the refresh • Log off all users: Logs off all application users before starting the refresh • Stop all active requests: Terminates any active requests in the Essbase application before starting the refresh After Refresh Database Enable use of the application for: Lets All users or Administrators use the application after the refresh 5. To refresh the database now, click Refresh Database. To run the refresh later, as a job, click Save as Job. See Managing Jobs. Tip: To streamline the job creation process for subsequent Refresh Database jobs, you can duplicate an existing job using the Save As option, then update it. See Duplicating Jobs. Adding an Aggregate Storage Outline to an Application Understand what aggregate storage is and how to use it in an application. Chapter 6 Adding an Aggregate Storage Outline to an Application 6-31
- 126. Related Topics • About Aggregate Storage • Process for Adding an Aggregate Storage Database to an Application About Aggregate Storage Aggregate storage is the database storage model that supports large-scale, sparsely distributed data that is categorized into many, potentially large dimensions. Selected data values are aggregated and stored, typically with improvements in aggregation time. Aggregate storage is an alternative to block storage (dense-sparse configuration). Aggregate Storage Outline Cube Characteristics • The application doesn't generate XREFs on aggregate storage databases. XREFs can only be generated on block storage databases. • Because the application doesn't require all base dimensions on an aggregate storage database, approvals may not apply to the aggregate storage database if an approvals dimension is missing. If this is the case, normal security would apply. • Dynamic time series members are not applicable for the Period dimension in an aggregate storage application. • Creating and refreshing security filters are not applicable for aggregate storage databases. Optimizing Aggregate Storage Cubes Performance of aggregate storage reporting cubes is governed by many factors, including the number of slices in the cube, the outline of the cube, and the type of dimensions in the cube. See Optimizing Aggregate Storage Option Cubes in Oracle Enterprise Performance Management Cloud Operations Guide. Process for Adding an Aggregate Storage Database to an Application To add an aggregate storage database to an application: 1. Create an aggregate storage cube. Perform one task: • Create an aggregate storage cube during application creation. To create a Planning application, see Creating a Planning Application. • Add a new cube using the cube editor. See Managing Cubes. 2. Add dimensions to the aggregate storage cube. See Editing Dimensions in the Simplified Dimension Editor. • If a Currency, Years, Scenario, or Version dimension is valid for an aggregate storage cube, the dimension members are also valid for an aggregate storage cube. • To perform currency calculations in a simplified multiple currency application for a custom aggregate storage cube, you must enable the Account, Period, and Currency dimensions for the aggregate storage cube. These dimensions in default aggregate storage cubes are enabled by default, but you must Chapter 6 Adding an Aggregate Storage Outline to an Application 6-32
- 127. enable them manually for custom aggregate storage cubes. To enable Account, Period, and Currency dimensions for custom aggregate storage cubes, edit dimension properties for each dimension and select to enable them for the aggregate storage cube. See Editing Dimension Properties in the Simplified Dimension Editor. 3. Add dimension members. See Adding Members in the Simplified Dimension Editor. 4. Refresh the outline for the application. See Refreshing Application Databases. 5. Create a form using the dimensions associated with the aggregate storage database. See Administering Forms. Converting an EPM Standard Cloud Service to EPM Enterprise Cloud Service Learn how to convert an EPM Cloud Service application from Standard to Enterprise. Note: This topic discusses converting an EPM Standard Cloud Service to an EPM Enterprise Cloud Service. To convert a Planning application, see Converting a Planning Application. To increase the number of cubes and to use the logic required to support more extensive calculations and other advanced functionality such as IPM Insights, you can perform an in- place conversion from EPM Standard Cloud Service to EPM Enterprise Cloud Service. For a list that details the applications and features available to you in EPM Standard Cloud Service and EPM Enterprise Cloud Service, see About EPM Cloud Services. Only customers who have purchased an EPM Enterprise Cloud license can convert from Standard to Enterprise. You will be asked to confirm that you have the Enterprise order ID to complete the conversion. Caution: Converting an application can't be undone. Be sure you back up your data before converting. To convert from an EPM Standard Cloud application to an EPM Enterprise Cloud application: 1. Click Application, and then click Overview. 2. Click Actions, and then select Convert to Enterprise. 3. In the Convert to Enterprise dialog, select the checkbox to confirm you have the Enterprise order ID, and then click Convert to Enterprise. Chapter 6 Converting an EPM Standard Cloud Service to EPM Enterprise Cloud Service 6-33
- 128. Note: After converting to Enterprise, users will need to refresh the Planning node in Calculation Manager to enable them to create Groovy rules. Without refresh, users might not get the drop-down to select Groovy in the script editor of Calculation Manager. Converting a Planning Application Learn how to convert Planning applications from Reporting to Standard, and from Standard or Reporting to Enterprise. Note: This topic discusses converting Planning applications. To convert an EPM Cloud Service application from Standard to Enterprise, see Converting an EPM Standard Cloud Service to EPM Enterprise Cloud Service. Related Topics • Converting to a Standard Application • Converting a Standard or Reporting Application to an Enterprise Application • Conversion Considerations Converting to a Standard Application To increase the number of cubes and use the logic required to support more extensive calculations, convert a Reporting application to a Standard application. During conversion, one cube, and the associated dimensions are added to your application. After conversion, you can add up to six additional cubes (three aggregate storage outline cubes and three block storage outline cubes). You can enable sandboxes while converting a Reporting application to a Standard application. However, after you convert to a Standard application, you can't later enable it for sandboxes To enable sandboxes, see Enabling Sandboxes. Caution: Converting an application can't be undone. Be sure you back up your data before converting. To convert to a Standard application: 1. Click Application, and then click Overview. 2. Click Actions, and then select Convert to Standard. Chapter 6 Converting a Planning Application 6-34
- 129. Converting a Standard or Reporting Application to an Enterprise Application Learn about converting an application in this topic. • If you purchased EPM Cloud after June 4, 2019, see New EPM Cloud Services in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators to learn about migrating an application to the new services. • If you purchased EPM Cloud before June 4, 2019, you can convert a Standard or Reporting application to an Enterprise application. To convert a Standard or Reporting application: 1. Review the conversion considerations. See Conversion Considerations. 2. Back up the Standard or Reporting application. 3. Open the application, and then click Application , and then Overview . 4. Click Actions, then Convert to Enterprise, and then Continue to proceed. A message lets you know if the application is converted to Enterprise. If successful, log off. The application type is changed to "Enterprise", which includes options to enable and configure the Planning modules, and enables Groovy scripting. Metadata and data isn't changed during the conversion. 5. Log on and enable features that you need. These validations are performed when you enable features: • There can't be a member that already exists with the same name as any of the custom and base dimensions you specify in Map/Rename Dimensions. For example, if you create a custom dimension called Market in Financials, there can't be a member called Market in any other dimension. • There can't be a member with the name NO_<<customDimension>>, Total_<Dimension>>, All_<<Dimension>>, where <<Dimension>> is the actual dimension name you specified. For example, if you rename Plan Element in Financials to Element for a custom dimension, there can't be No Element, Total Element. This is specific to modules that depend on any non-prefixed member. • The data storage for the Period and Account dimensions must be set to Never Share. • The Year dimension name must be Years. • 18 alias tables are predefined. The maximum supported is 32 (1 used internally). The conversion process attempts to merge the predefined alias tables with the alias tables in the existing application; if the count goes above 30, you get a validation error. Chapter 6 Converting a Planning Application 6-35
- 130. • The conversion process calculates the number of existing dimensions in the application and the number of new dimensions that would be created if the module is initialized. If resulting sum of both is greater than 32 (the maximum allowed), you'll see a validation error. • For Projects, the name you specify for Program (a custom dimension option) shouldn’t already exist as a non-attribute dimension. • For Workforce, none of the version members can be Label only. 6. Recreate any user defined navigation flows. When you convert an on-premises Oracle Hyperion Planning R11.1.2.1 (supported version) application to Planning using Migration, the same rules above apply. Conversion Considerations You can convert a Standard or Reporting application to an Enterprise application if: • You are commercially authorized to implement an application of type "Enterprise". • It does not use weekly, quarterly, or custom time periods. • You rename the Year dimension to Years prior to converting. • It uses simplified multicurrency (that is, it's not a standard currency application), if it's a multicurrency application. • Artifact names don't use these prefixes: – oep_: Prefix for common artifacts – ofs_: Prefix for Financials artifacts – owp_: Prefix for Workforce artifacts – opf_: Prefix for Projects artifacts – ocx_: Prefix for Capital artifacts Note that custom navigation flows are not converted. You need to recreate them after you convert the application. Removing an Application Proceed with caution when removing an application. Because removing an application will delete all of its contents and any scheduled jobs, make a backup of your application. To remove an application: 1. Click the Application, then click Overview. 2. Click Actions, and then Remove Application. Chapter 6 Removing an Application 6-36
- 131. Setting the Daily Maintenance Process Start Time Understand how to determine and set the most convenient time to start the hour-long daily maintenance process. A business process instance requires one hour every day to perform routine maintenance. Service Administrators can select (and change) the most convenient time to start the hour- long daily maintenance process. For information about daily maintenance operations and scheduling the maintenance start time for an environment, see Managing Daily Maintenance in Getting Started with Oracle Enterprise Performance Management Cloud for Administrators. Note: There is a system setting called Export EPM Cloud Smart List textual data during daily maintenance for incremental data import that, depending on if this setting is enabled, could impact the duration of the export. For more information and for recommendations about using this setting, see the following topics: • Exporting Smart List Textual Data During Daily Maintenance for Incremental Data Import in Oracle Enterprise Performance Management Cloud Operations Guide • What Application and System Settings Can I Specify? To prevent automatic backup from failure due to scheduled jobs, EPM Cloud disallows certain scheduled jobs to start while the daily maintenance process is running. The following jobs are prevented from starting during the daily maintenance: • Import Data • Import Metadata • Export Data • Export Metadata • Refresh Database • Clear Cube • Restructure Cube • Compact Outline • Merge Data Slices • Optimize Aggregation If the system prevents a job from starting, the reason will be stated in the Job Details. If you've enabled email notifications for the Job Console, you'll receive an email notification when a job does not start. If you have a job that is scheduled to start during the daily maintenance process, it is recommended that you reschedule your job to start outside of the daily maintenance window. See Scheduling Jobs. Chapter 6 Setting the Daily Maintenance Process Start Time 6-37
- 132. Uploading and Downloading Files Using the Inbox/Outbox Explorer Use the Inbox/Outbox Explorer to upload files to the server or download them to your computer. To schedule an import or export job, see Scheduling Jobs. To upload or download files: 1. Click Application, and then click Overview. 2. Click Actions, and then Inbox/Outbox Explorer. 3. Optional: Filter by name, refresh the listing, and upload files from the server. 4. To upload a file from the server, click Upload. In the Upload File dialog box, click Browse, select the file to upload, and then click Upload File. 5. To download a file from the server, select the desired file, then click , and then click Download File. 6. Click Close to close the Inbox/Outbox Explorer and return to the Overview tab. Note: There is an upload file size limit of 2GB. If your upload file exceeds the size limit, either select a smaller file or use EPM Automate to upload the larger file. For information about EPM Automate, see Working with EPM Automate for Oracle Enterprise Performance Management Cloud . Chapter 6 Uploading and Downloading Files Using the Inbox/Outbox Explorer 6-38
- 133. 7 Setting up Strategic Modeling Related Topics • Getting Started Checklist for Strategic Modeling • Enabling Strategic Modeling in Planning Modules • Enabling Strategic Modeling for Custom Applications You can enable Strategic Modeling for use with existing Custom and Planning Modules applications. • Working with Templates • Creating a Strategic Modeling Model • Setting Up Model Access Permissions • Changing Model Properties • Pushing Data Between Strategic Modeling and Planning • Pushing Data from a Strategic Modeling Model to Multiple Strategic Modeling Models • Pushing Data from a Strategic Modeling Scenario Rollup to a Strategic Modeling Scenario Rollup • Managing Metadata with Model Change Management Use Model Change Management to copy metadata from a source model to one or more target models. Getting Started Checklist for Strategic Modeling Perform these tasks to set up Strategic Modeling: 1. Create an application, or identify an existing application to use. For Planning, see Creating a Planning Application. For Planning Modules, see Creating an Application in Administering Planning Modules. 2. Enable Strategic Modeling. See Enabling Strategic Modeling in Planning Modules or Enabling Strategic Modeling for Custom Applications. 3. Review the provided templates, and upload any custom templates required for your organization. See Working with Templates. 4. Create a model from a template. See Creating a Strategic Modeling Model. 5. Set up access permissions. See Setting Up Model Access Permissions. 6. After you enable Strategic Modeling, refresh the database. Click Application, then Overview, and then from the Actions menu, select Refresh Database, then Create, and then Refresh Database. Tutorials Tutorials provide instructions with sequenced videos and documentation to help you learn a topic. 7-1
- 134. Your Goal Learn How Get an introduction to Strategic Modeling. Introduction to Strategic Modeling Enabling Strategic Modeling in Planning Modules Before users can start strategic planning, you must enable Strategic Modeling. To enable Strategic Modeling in Planning Modules: 1. From the Home page, click Application, and then click Configure. 2. From the Configure list, select Strategic Modeling, and then click Enable Features. 3. Log out and log in again to see the newly enabled feature. There are no configuration tasks required for Strategic Modeling. The Strategic Modeling provided templates are populated. To enable Strategic Modeling for Custom applications, see Enabling Strategic Modeling for Custom Applications. Enabling Strategic Modeling for Custom Applications You can enable Strategic Modeling for use with existing Custom and Planning Modules applications. To enable Strategic Modeling for an EPM Enterprise Cloud Service Custom application: 1. Sign into the Custom or Planning Modules application as a Service Administrator. 2. Click Application and then Overview. 3. From Actions, select Enable Strategic Modeling. 4. If you are using navigation flows, complete a step to activate Strategic Modeling artifacts: • Reload Navigation Flows. • Sign out and then sign in again. To enable Strategic Modeling in a Planning Modules application, see Enabling Strategic Modeling in Planning Modules. Working with Templates Use templates to quickly create a model. Templates include a hierarchical set of accounts without time periods or data. Strategic Modeling includes templates for commonly used account structures. You can use one of the provided templates, or create and upload custom templates. Oracle provides these templates: Chapter 7 Enabling Strategic Modeling in Planning Modules 7-2
- 135. • Standard • Utility • Healthcare • Retail • Higher Education These templates are available when you enable Strategic Modeling so you can get up and running quickly. You can't modify the templates provided by Oracle, but you can save a copy of a template and modify it for your business use case. To review the account structure of the provided templates and any custom templates you've uploaded: 1. From the Home page, click Strategic Modeling, and then click Templates. 2. From the Action menu for the template you want to review, click Open. 3. Change the Scenario, Dataview, or Account Groups to show different sets of accounts. You can also review and edit the account structure in the templates provided by Oracle using Strategic Modeling in Oracle Smart View for Office. Creating and Uploading Custom Templates You can create a custom template by saving a copy of one of the templates Oracle provides and customizing it. Review the account structure in the provided templates to determine which most closely suits your business needs, and then use Oracle Smart View for Office to customize and upload the template for use on the Web. You can also use Smart View to upload templates you created from the on premise version of Oracle Hyperion Strategic Finance for use on the Web. Changing the Owner and Access Permissions for Custom Templates All users (except those with No Access) can view the out-of-box templates provided with Strategic Modeling. Administrators can change the owner and the access permissions for custom templates. To change the owner or access permissions for custom templates: 1. From the Home page, click Strategic Modeling, and then click Templates. 2. From the Action menu next to the template you want to modify, click Properties. 3. Change the owner of the template if required. 4. Click Permissions. 5. Click to add users or groups and assign them access to the template. For information about user and group permissions, see Setting Up Model Access Permissions. 6. To replace the current permissions with default permissions, click Inherit Default Access. 7. Click Apply to save the changes. Chapter 7 Working with Templates 7-3
- 136. Creating a Strategic Modeling Model Administrators and Modelers can create Strategic Modeling models using templates— financial model frameworks that contain predefined reporting and modeling standards. Oracle includes several pre-defined templates to get you up and running quickly. You can also create a model that is based on an existing model. Users check out models to work with them, or they can work with a copy of the model. When users work with a copy of a model, they can't save changes to the data or to the model. When you create a model, the model is populated with a hierarchical chart of accounts, a time structure, reports, dataviews, account groups, and all the metadata from the template or the model it was created from. You must have already created an application and enabled Strategic Modeling. If you want to use a custom template (customized using Oracle Smart View for Office) to create the model, it must already be uploaded. To create a Strategic Modeling model: 1. From the Home page, click Strategic Modeling, and then click Models. 2. Click Create. 3. On the General page, specify the following options and then click Next. • Specify a model name and description. • Select whether to create the model from a template, from an existing model in the current application, or from a local .alc file, and then select the template, model, or file. If you are creating a model from a local .alc file, the file must have already been converted in Smart View for use on the Cloud. To integrate Strategic Modeling data with Financials, select the Financials template. • Select Place at Root to create a standalone model or a model that will be the parent of another model, or to create a hierarchical structure, clear Place at Root and select a model from Parent Model. Creating a hierarchical model structure can be useful for scenario rollups and managing access control, or for visually organizing models. • Select a base currency and units. Each model can have its own currency and units, independent of the application. If you create a model from a local .alc file or from an existing file if you keep source data, these options are not available; the model is created using the units and currency of the original model. Note: You set up currency conversions in Smart View. See Translating Currencies in Working with Strategic Modeling in Smart View. Chapter 7 Creating a Strategic Modeling Model 7-4
- 137. • If you created the model from an existing model, select Keep Time Structure if you want the new model to use the same time period structure as the existing model. If you selected Keep Time Structure, you can select Keep Source Model Data to include the source model's data values in the accounts. If you select Keep Time Structure, skip to step 5. • If you created a model using the Financials template for integration with Financials, in Select Entity, select a Financials Entity dimension member. The model will be mapped to the selected Entity dimension member. This option is available only when creating a model from the Financials template. For more information, see Integrating Data Between Strategic Modeling and Financials. 4. On the Calendar, Time Period, and Configure Years pages, specify the options for building the calendar for this model. 5. Review the model creation options, and then click Create Model. The model is created with a chart of accounts and a calendar structure based on the options you selected. You can convert an Oracle Hyperion Strategic Finance model to a Strategic Modeling model in Smart View. See Working with Strategic Modeling in Smart View . Video Your Goal Watch This Video Learn about creating a Strategic Modeling model. Creating Strategic Models in Oracle Enterprise Planning Cloud Setting Up Model Access Permissions Planning administrators are set up as Strategic Modeling administrators and can set up access permissions that define the type of access users and groups have to models and Strategic Modeling features—global permissions that apply to all models in the application, and permissions for individual models. When you assign access permissions to an individual model, any models nested under that model in the model hierarchy inherit the access permissions from the parent. If a model is inheriting access permissions (either from the global level or from a parent), as long as you have not made any changes to the individual model's access permissions, it will continue to inherit any changes to access permissions. However, once you modify an individual model's access permissions, it no longer inherits any permission changes from either the global level or the parent (depending on where it inherited permissions from). Available roles include Modeler, Analyst, Viewer, and No Access. See About Model Access Permissions for more information about these roles. These permissions also apply to models when you work with Strategic Modeling in Oracle Smart View for Office. Model access details: • Planning users (except Administrators) are available in the Users list to assign model access. Note that access permissions in Strategic Modeling are unrelated to those in Planning. You must give users access to Strategic Modeling models even if they have access to the Planning application. Chapter 7 Setting Up Model Access Permissions 7-5
- 138. • When a model is first created, it is set up with Default permissions and Owner permissions. You can't delete these. Any newly added user or group gets the default permissions. By default, the Default permissions and new users and groups have the No Access role. If you assign global access, all new models inherit that access. • When a user has no access to a model, no model actions or options are available. When a user has no access to a menu item, it doesn't appear on the Actions menu. Video Your Goal Watch This Video Learn about setting up model access permissions. Setting Up Model Access for Strategic Modeling in Oracle Enterprise Planning Cloud About Model Access Permissions Administrators can perform these tasks: • Enable Strategic Modeling • Assign access permissions • Create, delete, and modify models and scenario rollups • Upload templates, assign access to custom templates, and delete templates Users' access to scenario rollups comes from the Global Access. Chapter 7 Setting Up Model Access Permissions 7-6
- 139. Table 7-1 Model Access Permissions Role Access Modeler • Models: – Create – Open - Check out and check in – Open as Copy – Save as Local File – Delete – Model Data Maps • Account View: All options are available – Find Account – Account Forecast – Subaccounts – Goal Seek – Scenario Manager – Audit Trail – Simulations – Enter data, Calculate, and Save – Change the Point of View to display different account groups, scenarios, and dataviews • Scenario rollups: All options are available • Templates: View templates, delete custom templates, import templates • Reports: All options are available • In Oracle Smart View for Office: – Models: Copy Local File to Server, Delete Model, Input Status, Account Groups, Funding Options, Required Elements, Template Name – Time management: Time tab. All options are available – Scenarios: All options are available – Dimensions: All options are available * Create Custom Dimensions * Assign Custom Dimensions Analyst • Models: – Open - Check out and check in – Open as Copy – Save as Local File • Account View – Find Account – Account Forecast – Goal Seek – Audit Trail – Enter Data, Calculate, and Save – Change the Point of View to display different account groups, scenarios, and data views • Templates: View templates • Reports: View reports Chapter 7 Setting Up Model Access Permissions 7-7
- 140. Table 7-1 (Cont.) Model Access Permissions Role Access Viewer • Models: – Open as Copy – Save as Local File • Account View – Find Account – Goal Seek – Audit Trail; however, viewers can't make changes to inputs – View the grid in read only mode (can't Enter Data or Save) – Change the Point of View to display different account groups, scenarios, and data views • Templates: View templates • Reports: View reports No Access No access Specifying Global Access Permissions for All Models To specify global access permissions that apply to all models: 1. From the Home page, click Strategic Modeling, then Models, and then Global Access. 2. Specify a role for each user or group. 3. Click to add users or groups and assign them global access. 4. Click Apply. Specifying Access Permissions for a Model If you set up global access permissions, each individual model inherits access permissions from the global access list. You can modify the permissions for each model. Children models inherit permissions from the parent model, unless the parent has no specific permission, in which case they inherit the global access permissions. Once you modify an individual model's access permissions, it no longer inherits any permission changes from either the global level or the parent (depending on where it inherited permissions from). To specify access permissions for a specific model: 1. From the Home page, click Strategic Modeling, and then Models. 2. From the Action menu next to the model you want to modify, click Properties. 3. Click Permissions and then specify the user and group permissions for the model. 4. Click to add users or groups and assign them access to the model. Chapter 7 Setting Up Model Access Permissions 7-8
- 141. 5. To replace the current permissions with default permissions, click Inherit Default Access. 6. Click Apply to save the changes. Changing a Model's Owner You can change the owner of a model. To change a model's owner: 1. From the Home page, click Strategic Modeling, and then Models. 2. From the Actions menu next to the model you want to modify, click Properties. 3. Change the owner, and then click Apply. Changing Model Properties Administrators and model owners can change the properties of a model. To change a model's properties: 1. From the Home page, click Strategic Modeling, and then Models. 2. From the Actions menu next to the model you want to modify, click Properties. 3. Change the properties, and then click Apply: • Owner—Specify the account owner. • Default Units—Specify the default units for the model. • Default Currency—Specify the default currency for the model. • Account View Input Decimal Places—Specify the number of decimals to display for input accounts. • Account View Output Decimal Places—Specify the number of decimals to display for output accounts. Pushing Data Between Strategic Modeling and Planning You can push data between Strategic Modeling and Planning in two ways: • Data Maps and Smart Push—Provides an easy-to use interface that automatically maps same-named dimensions and members and allows you to define the mapping between other dimensions and members. You can define complex mappings to or from a single dimension to or from multiple dimensions. The feature also provides a Microsoft Excel template to further simplify setting up detailed mappings and import them using a familiar interface. Using Data maps and Smart Push works for most use cases. See Pushing Data Between Strategic Modeling and Planning Using Data Maps. • Groovy Rules—Provides a powerful rule-based method for creating complex data maps using Groovy scripting language. Use Groovy rules to define complex mappings. For example, you can define a Groovy rule that pulls data from Planning for targeted regions based on the current form, such as only from edited cells. You can also perform calculations on data before pushing it, such as applying a scaling factor. See About Groovy Business Rules and Using Groovy Business Rules with Strategic Modeling. Chapter 7 Changing Model Properties 7-9
- 142. Using Groovy Business Rules with Strategic Modeling You can create Groovy business rules to push data between Planning cubes and Strategic Modeling models. For information about designing Groovy rules, see Creating a Groovy Business Rule in Designing with Calculation Manager for Oracle Enterprise Performance Management Cloud and Using Groovy Rules in Administering Planning . Video Your Goal Watch This Video Learn about using Groovy rules with Strategic Modeling. Integrating Strategic Models Using Groovy Rules Groovy Business Rule Examples Example Groovy scripts are available. To see example Groovy scripts: 1. See the Java API Reference for Oracle Enterprise Performance Management Cloud Groovy Rules, http://docs.oracle.com/cloud/latest/epm-common/GROOV/. 2. Do one of the following: • Under Example Groovy Scripts on the main page, click the word " here " to view sample scripts: • Under All Classes in the left pane, click a class to see the examples for that class. For example, to see Strategic Modeling examples, click the StrategicModel class in the left pane. Pushing Data Between Strategic Modeling and Planning Using Data Maps You can push data between Strategic Modeling and Planning using data maps. You can define data maps that push data: • From a Strategic Modeling model or scenario rollup to a Planning cube. • From a Planning cube to a Strategic Modeling model. • From a Planning cube to a Strategic Modeling scenario rollup. Advanced options let you define complex mappings to or from multiple dimensions to or from a single dimension and between members with different names. These advanced data map options are available only if Strategic Modeling is enabled and is a source or target in the data map. Administrators have privileges to create, edit, and run data maps. Chapter 7 Pushing Data Between Strategic Modeling and Planning 7-10
- 143. To create a data map: 1. From the Home page, click Application, then Data Exchange, and then click Data Maps. 2. Click Create. 3. Enter a name and description for the data map. 4. Under Source, select the source for the data. You can select: • A Planning input cube (Block Storage) from the available cubes for the current application. Note: Reporting cube (Aggregate Storage) is not supported as a source. • A Strategic Modeling model. You can select from any models in the selected application. • A Strategic Modeling scenario rollup. You can select from any scenario rollups in the current application. When the source is a scenario rollup, metadata is pulled from the root model of the scenario rollup. Note: If you don’t see your Strategic Modeling model in the list, from the Actions menu, select Synchronize. You can perform synchronize action in two ways: a. In the initial data maps screen (step 1) by accessing it through Actions of a listed data map. b. During creation/modification of a data map, by using the Actions • Planning to Planning—Updates metadata changes in the target Strategic Modeling model. • Planning to Strategic Modeling—Updates metadata changes in the target Strategic Modeling model. • Strategic Modeling to Planning—Updates only metadata in the source Strategic Modeling model. • Strategic Modeling to Strategic Modeling—Updates the metadata changes for both the source and target models. 5. Under Target, select: • A Planning input cube (Block Storage) or reporting cube (Aggregate Storage) from the available applications, if the source is a model or a scenario rollup. • Select Model to select a Strategic Modeling model if the source is a Planning input cube (Block Storage). • Select Scenario Rollup to select a Strategic Modeling scenario rollup if the source is a Planning input cube (Block Storage). Chapter 7 Pushing Data Between Strategic Modeling and Planning 7-11
- 144. If you don’t see your Strategic Modeling model or scenario rollup in the list, from the Actions menu, select Synchronize. 6. Define how to map dimensions between source and target: Under each mapped dimension, click Select, and then select the artifact or artifacts to use. These dimensions are automatically mapped: • Model in Strategic Modeling and Entity in Planning. You can select multiple models (from a list of all the models in the application) as a target. For example, you might have multiple entities in Planning that map to multiple models in Strategic Modeling. Multiple selections must have a one to one mapping between model and entity. • Scenario (or Business Case if the source or target is a scenario rollup) in Strategic Modeling to Scenario in Planning. Multiple selections must have a one to one mapping between Scenario or Business Case in Strategic Modeling and Scenario in Planning. • Account in Strategic Modeling to Account in Planning. You can select multiple accounts. Tip: Account members with the same name are automatically mapped (based on the Description in Strategic Modeling and the Name in Planning.) Click Map in the Account row to see the mappings. Tip: If you know all of the member names, you can skip this step and enter the member names directly in Advanced Data Maps. See Defining Advanced Data Maps. • Dimensions with the same name. Other dimensions are in the Unmapped Dimensions list. 7. Map any remaining dimensions from the Unmapped Dimensions list if required. Click the arrow next to a dimension in the Unmapped Dimension list to move it to the Mapping area. Select the dimension to map it to, and then click Select to select the members to map. For any unmapped dimensions, select a member. 8. Map any custom dimensions. Map custom dimensions in the same way you map base dimensions. Members associated with a custom dimension are shown under the custom dimension rather than under the Account dimension. If the data map includes accounts that aren't part of the custom dimension, map the root of the custom dimension in Strategic Modeling to a specific member in Planning. Data for accounts that aren't part of the custom dimension are pushed to this member. 9. If required, you can map to or from multiple dimensions to or from a single dimension: Chapter 7 Pushing Data Between Strategic Modeling and Planning 7-12
- 145. a. Click Actions next to a mapping row and then select Add Source Mapping or Add Target Mapping. b. Select the additional dimension to map, and then select the members to map. For example, you might want to map the Time dimension in Strategic Modeling to the Years and Period dimensions in Planning. Or, you might want to map the Business Case in Strategic Modeling to Scenario and Version in Planning. Including the Version dimension allows runtime input when you run the scenario rollup. 10. To exclude source members from the data map, click Actions next to a mapping row and then select Add Exclusion. Define the member or members to exclude and then click OK. The excluded member or members are shown on the Data Maps page. Excluding members while moving data is useful if you don't want to overwrite certain data at the target location or if you want to avoid getting warnings if data at the target location is not present. Also, exclusions can ignore specific source member data while data is required for all other source members. When excluding members from a dimension, the member list for the dimension must contain at least one member that is not on the excluded member list in order for the data map to successfully save and run. To remove one or more excluded members from the exclusion list, click the members in the exclusion list, and remove the member or members from the list using the Member Selector. To remove the entire exclusion, click Actions next to a mapping row and then select Remove Exclusion. Tip: If you set up Smart Push for a form, you can also exclude members from the Smart Push. See Configuring Smart Push for a Form. When you define Smart Push for a Planning form to push data to Strategic Modeling, the members defined for the Smart Push must match the members defined in the data map. 11. If the member names don't match in the source and target, or when mapping to or from multiple dimensions to or from a single dimension, you must define an advanced data map. See Defining Advanced Data Maps. You can also use advanced data maps to define mappings when you know all the member names. 12. Click Save and Close at any time. If the data map definition is not yet complete, you will receive an error, but you can save the data map as a draft so you can continue to work on it at another time. 13. Associate the data map with a model or scenario rollup: • If the source is a model, you can optionally associate the data map with a model. See Associating Data Maps with a Model. • If the source is a scenario rollup, you must associate the data map with a scenario rollup. See Associating Data Maps with a Scenario Rollup. Chapter 7 Pushing Data Between Strategic Modeling and Planning 7-13
- 146. Note: Planning to Strategic Modeling scenario rollup data maps are not available for association in Planning forms. 14. Optionally, specify options that define how to execute the data map. See Defining Strategic Modeling Data Map Options. For Planning data map options, see Defining Data Map Options. For information about running data maps, see Running a Data Map. Videos Your Goal Watch This Video Learn about creating data maps to move data between Strategic Modeling and Planning. Creating Data Maps and Moving Data from Strategic Models After Consolidation Creating Data Maps to Move Data between Planning Cubes and Strategic Models Learn how to move data using data maps from Planning to a Strategic Consolidation Model, and between models within a Strategic Consolidation Model. Mapping Data into Business Cases for Parent Models Defining Advanced Data Maps When member names don't match in the source and target, or when mapping to or from multiple dimensions to or from a single dimension, you must define an advanced data map. 1. Click Map in a mapping row to define the advanced mapping. For example, you might want to map multiple accounts from Planning into a single account in Strategic Modeling. The Edit Data Map page lets you define mapping on each tab. Tabs include Basic Info, Source Selection, Target Selection, a tab for each mapped dimension, and if they exist, Unmapped Source and Unmapped Target dimensions. The Source Selection and Target Selection tabs contain a superset of the details to be mapped on the other tabs. 2. Click a tab to define the mapping details. For each dimension, the Source members are listed. • For each Source member where the member names between source and target are different, add the Target member. (Target members must be level zero members in the hierarchy). • If you've already excluded members, they are listed in the Source Selection tab, in the dimension(Excluded) column. • To exclude members from the data map, in the Source Selection tab, click the column header for the dimension you want to exclude a member from, Chapter 7 Pushing Data Between Strategic Modeling and Planning 7-14
- 147. click Add Exclusion , and then in the dimension(Excluded) column, define the members to exclude. – If you exclude a member that is already mapped, click the tab for the dimension and update the mapping for the member. – To remove a member from the Excluded list, select the member and then press the Delete key. If you remove a member from the Excluded list, click the tab for the dimension and add the mapping for the member. – To remove the exclusion, click the column header for the dimension and then click Remove Exclusion . • Specify an operator if required. The default operator is +. The operator for a row defines the operation to use for the current row. For example, to have multiple accounts from the source aggregate and map to a single account in the target, add a row for each member in the source, each mapped to the same target member. By default, the + operator for each row defines the aggregation. Or, you might want to map multiple periods in a cube (Jan through Dec) to a single time period in a Model (2018). • You can Copy Rows or Paste Rows or copy and paste data from one tab to another. • Add as many rows as needed to define all the members to map. Click Insert Row to add a mapping definition between a source and target member. • If needed, click Delete Invalid Entries to clear any mapping rows where the source is invalid and clear any invalid target members. 3. When mapping from multiple dimensions to a single dimension, for example from Years and Period in Planning to Time in Strategic Modeling, the Edit Data Map page is populated the all the possible source combinations. Select the corresponding target members for each source combination you need. If you've defined any exclusions, the excluded members are not listed. If there are some source combinations you don't need to map to, select the row and then click Delete Row . This source combination will not be automatically populated again if you return to the Edit Data Map page. If you later want to see the deleted source combinations, click Populate Detailed Mappings . The Edit Data Map page is updated to show all possible source combinations. 4. Click Done. Note the following about mapping members: • When member names in source and target match and are automatically mapped, they are not listed on the Mapping Details page. • You can only select target members that are listed on the Target Selection tab. If you need a different member, return to the Data Maps page and select it from the Target Chapter 7 Pushing Data Between Strategic Modeling and Planning 7-15
- 148. member list. (If you didn't enter members on the Data Maps page, you're not restricted in this way.) To simplify defining an advanced data map, you can export the data map definition to Excel, edit the data map template in Excel, and then import it. See Using Microsoft Excel to Define Advanced Data Maps. About Data Maps and Custom Dimensions Note the following when defining data maps when some of the Strategic Modeling accounts in the data map are associated with custom dimensions and some are not. When creating a data map from Planning to Strategic Modeling, the data moves based on the following rules. • When the root of the dimension in Strategic Modeling is part of the detailed mapping: – For accounts where this dimension is applicable, the root dimension mapping is ignored. (Data can’t be written to the root for valid accounts.) – For accounts where this dimension is not applicable, only the root dimension mapping is considered. (Data can’t be written to the nonexistent leaf members.) – For dimensions that have no members in Strategic Modeling, the data is always written to the root. (The root member is the only available member.) • When the root of the dimension in Strategic Modeling is not part of the detailed mapping: – For accounts where this dimension is applicable, data movement occurs as defined in the data map definition. (Data can be written to all the members in the mappings.) – For accounts where this dimension is not applicable, each member in the target is replaced with the root dimension. The aggregated data for all the members is moved to the root of the Strategic Modeling dimension. If this is not the behavior you want, make sure you map the appropriate member in Planning to the root dimension in Strategic Modeling. • When the dimension is part of the Unmapped Dimensions (for the Target): – For the accounts where this dimension is applicable, the data is pushed to the member defined in the target. – For the accounts where this dimension is not applicable, the data is pushed to the root. When creating a data map from Strategic Modeling to Planning, the data moves based on the following rules. When the root of the dimension in Strategic Modeling is part of the detailed mapping: • When the custom dimension has multiple members selected, the custom dimension's root is applicable only for members whose custom dimension is not enabled. • As part of data map validation, a check mandates mapping the custom dimension's root to avoid data duplication when custom dimensions are enabled. The root member is ignored if the section for the Custom dimension has multiple members in the mapping. Chapter 7 Pushing Data Between Strategic Modeling and Planning 7-16
- 149. • Members assigned to the custom dimensions push the child members' values to Planning. If only the root member is defined in the data map, then the root member is pushed to Planning. Using Microsoft Excel to Define Advanced Data Maps To simplify defining an advanced data map, use Microsoft Excel to define the data map. 1. Define the basic dimension mappings in the Data Maps page. 2. From the Actions menu, select Export Data Map, and then open the file with Microsoft Excel. 3. Update the Source and Target tabs if needed, and the detailed mappings in each tab of the Excel worksheet, and then save it. 4. In the Data Maps page, from the Actions menu, select Import Data Map, and then save the data map. Videos Your Goal Watch This Video Learn about importing data maps. Importing Data Maps and Moving Data from Strategic Models to Planning Reporting Cubes Using Excel Data Maps for Moving Data between Planning Cubes and Strategic Models Associating Data Maps with a Model When the source of a data map is a model, you can associate the data map with the model and specify that the data map should run when you check in the model. 1. From the Home page, click Strategic Modeling and then click Models. 2. From the Action menu next to the model you want to associate a data map with, click Properties, and then click Data Maps. 3. From the Available Data Maps list, click the data map that you want to associate with the model and then click to move the data map to the Associated Data Maps list. Any data maps that have this model as a source or that have this model in the source section of the detailed mapping for the model are listed. Tip: You can also drag and drop the data map to the Associated Data Maps list. You can associate multiple data maps with a model. 4. To run the data map when the model is checked in, select Run on Check-In. Chapter 7 Pushing Data Between Strategic Modeling and Planning 7-17
- 150. 5. Click Apply. You can also delete a data map association with a model. Associating Data Maps with a Scenario Rollup Strategic Modeling operates on an individual model in a scenario rollup as follows: 1. Refresh Phase: Refresh data maps bring data into scenario rollups from outside sources, such as a Planning cube or Strategic Modeling models that are not part of the rollup. They are run before the scenario rollup if you select the Refresh option for the business case in Run Rollup and Data Maps. 2. Before Phase: Execute any data maps that are assigned to run before the model is processed. These should move data into the current model. These data maps run automatically during a scenario rollup when they are associated with the scenario rollup. 3. Process Model: Models that are leaf nodes are prepared to be rolled up into their parent nodes, making sure that they are completely calculated, including any required currency translation. Models that are parent nodes roll up their child nodes and are then completely calculated, including any required currency translation. 4. After Phase: Execute any data maps that are assigned to run after the model is processed. These should move data from this model into other models that need the results from the current model. These data maps run automatically during a scenario rollup when they are associated with the scenario rollup. 5. Publish Phase: Publish data maps push final rolled up data to external targets, for example, Planning, after a scenario rollup is complete if you select the Publish option for the business case in Run Rollup and Data Maps. Note: • Planning to Strategic Modeling scenario rollup type data maps are only available for association in the Refresh phase for the models present in the scenario rollup on which the data maps are defined. These will be considered as external source data maps with respect to the scenario rollup. • Strategic Modeling scenario rollup to Strategic Modeling scenario rollup type data maps are available for association in the Before/After phase of the models within the respective scenario rollup upon which the data maps are defined. • In a Strategic Modeling scenario rollup, let’s take a particular scenario. If a data map is associated as a Before data map for Model A and if this data map is setup to have Model A as a target model and if Model A is a parent model, the data map results could be overwritten by the scenario rollup from its children. To associate data maps with a scenario rollup: 1. From the Home page, click Strategic Modeling and then click Scenario Rollups. Chapter 7 Pushing Data Between Strategic Modeling and Planning 7-18
- 151. 2. Open the scenario rollup you want to associate data maps with. 3. Click a model in the scenario rollup hierarchy, and then click the Data Maps tab. 4. From the drop-down list, select when you want the data map to run—Refresh, Before, After, or Publish. The data maps list is filtered depending on your selection and is based on the data map definition and whether the model is part of the source or target. For example: • If the currently selected model is either the target of the data map or is present in the target section of the dimension mapping for the model, the data map can run before the model rolls up and will be listed if you select Before. • If the currently selected model is either the source of the data map or is present in the source section of the dimension mapping for the model, the data map can run after the model rolls up and is listed if you select After. 5. From the Available Data Maps list, click the data map that you want to associate with the model, and then click to add the data map to the Associated Data Maps list. Tip: You can also search for a data map or drag and drop the data map to the Associated Data Maps list. 6. Make sure Run on Rollup is selected so the data map runs when you run the scenario rollup. 7. Click Apply. 8. Repeat this process for any models, including the root model, with which you want to associate data maps. 9. Click Close. Notes: • Data maps associated with the Before or After phase will not run when a rollup is in the Ready state, unless models are altered by Refresh phase data maps. • During the scenario rollup, data maps that are associated with the After phase that push data from a parent down to one or more children can trigger a two-pass rollup. • When running scenario rollups, when the source of a data map is either Planning or a Strategic Modeling model outside the current scenario rollup, the data map is considered to be an external source data map. This type of data map is typically used to prepare the models for scenario rollup by importing the data from external sources. Tip: To see all the data maps associated with the models in the scenario rollup, from the Actions menu, select Set Data Maps. Chapter 7 Pushing Data Between Strategic Modeling and Planning 7-19
- 152. Defining Strategic Modeling Data Map Options Specify data map options that apply to Strategic Modeling data maps. Note: For Planning data map options, see Defining Data Map Options in Administering Data Integration for Oracle Enterprise Performance Management Cloud . 1. View the Data Maps listing page. 2. Select an existing data map or click Create to create a new one. 3. Click Options (or if creating a new data map, click Actions, and then click Options). 4. Specify data map options, and then click OK. Table 7-2 Strategic Modeling Data Map Options Data Map Option Description Import #missing value as (Only available for data maps where Planning is the source and Strategic Modeling is the target) • Ignore: Ignores the imported #missing value and retains the existing value in the target cell. • Zero As Output (default): Imports the #missing values and sets their output value to 0 in the target cells. • NaN: Imports the #missing values and sets their output value to NaN (Not a Number) in the target cells. • Zero As Input: Sets the input cell to 0, no back calculation required. Import NaN value as (Only available for data maps where Strategic Modeling is both the source and the target) • Ignore: Ignores the imported NaN value and retains the existing value in the target cell. • Zero As Output (default): Imports the NaN value and sets the output value to 0 in the target cells. • NaN: Imports the NaN values and sets their output value to NaN in the target cells. • Zero As Input: Sets the input cell to 0, no back calculation required. For cells that are not being imported • Preserve Input Values(default): Preserves the existing input data values in the model during the data import • Preserve Output Values: Preserves the existing output data values in the model during the data import Push data for mapped custom dimension root When the mapping contains both the parent and child members of the custom dimension, this option pushes the data for the custom dimension root to the target. Running a Data Map Data maps run automatically in the following situations: Chapter 7 Pushing Data Between Strategic Modeling and Planning 7-20
- 153. • If the source is a model and you associated the data map with the model and selected Run on Check-In, when you make a change to the model and check it in, the data map runs and Smart Push pushes the data to Planning. • If the source is a scenario rollup and you associated the data map with the scenario rollup and selected Run on Rollup, in Scenario Rollups, click Run. On the Run Rollup and Data Maps page, select Refresh and/or Publish to run data maps associated with those phases. Before and After data maps run automatically. If you mapped the Business Case in Strategic Modeling to Scenario and Version in Planning, when you run the scenario rollup, you have the option to select Overwrite Target Version, which overwrites the Version defined in the data map. If Version is in the Unmapped section, the selected Overwrite Target Version is ignored. • If the source is a Planning cube, associate the data map with a form and specify it to Run on Save. See Configuring Smart Push for a Form. You can associate multiple data maps with a single form. If the source is a model or a Planning cube, you can also run data maps from the Data Maps page: From the Home page, click Application, then Data Exchange, and then click Data Maps. From the Actions menu for the data map you want to run, select Clear and Push Data. Note: The Clear and Push Data option is unavailable for Planning to Strategic Modeling scenario rollups. To check the status of the data map and Smart Push job, from the Home page, click Application, and then click Jobs. Click the job name to see information and status about the Smart Push job. If there is an error, click Error to see details to help you resolve the error. Note: Data maps that push data from Planning to multiple Strategic Modeling models and have missing accounts in the target will be ignored and the data will be pushed for all valid accounts. The job details will provide a listing of dimension members that were ignored because they weren't available in the target model. Integrating Data Between Strategic Modeling and Financials You can push data between models in Strategic Modeling and income statements in Financials using the provided template and data maps. To complete this task, both Strategic Modeling and Financials must be enabled, in any order. Income Statement must be enabled in Financials. 1. Enable Financials with Income Statement enabled, and then create a Financials application. See Configuring Financials in Administering Planning Modules. 2. Enable Strategic Modeling, and then create a new model. Chapter 7 Pushing Data Between Strategic Modeling and Planning 7-21
- 154. • On the General page of the Create New Model wizard, select Create Model From Template, and then select Financial from the Select Template list. • In Select Entity, select a Financials Entity dimension member. The model will be mapped to the selected Entity dimension member. • If the Planning application is multi-currency, select a currency from the Currency list. If the Planning application is single currency, this option is not available, and it defaults to the application's currency. • The Calendar, Time Period, and Configure Years pages of the Create New Model wizard are not available when you create a model from the Financial template. The Start and End Period dates are set based on the Planning application. Year Configuration is monthly. When you create the model, two data maps are created. The data maps' detailed mappings are automatically populated between the dimension members in Strategic Modeling and in Financials. You can optionally view the detailed data maps: From the Home page, click Application, then click Data Exchange, and then click Data Maps. • <Model_Name>_SMtoPLDatamap pushes data from Strategic Modeling to the Target version in Financials. By default, the data map is associated with the model you just created and is set to run when you check in the model. • <Model_Name>_PLtoSMDatamap pushes data from the Working version in Financials to Strategic Modeling. For more details about enabling Strategic Modeling, see Enabling Strategic Modeling in Planning Modules. For more details about creating a Strategic Modeling model, see Creating a Strategic Modeling Model. 3. To push data from Strategic Modeling to Financials: a. Check out the Strategic Modeling model, enter data, and then calculate the scenario or all scenarios. b. Check in the model. If the data map is set to run on check-in (the default), when you check in the model, the data map runs and the Smart Push job is submitted. Tip: To check the status of the job, from the Home page, click Application and then click Jobs. In Financials, open the income statement to review the data that was pushed. From the Home page, click Financials, then click Revenue, and then click Income Statement. 4. To push data from Financials to Strategic Modeling use one of these methods: • Run the data map from the Data Maps page: From the Home page, click Application , then Data Exchange , and then click Data Chapter 7 Pushing Data Between Strategic Modeling and Planning 7-22
- 155. Maps. From the Actions menu for <Model_Name>_PLtoSMDatamap, select Clear and Push Data. • Associate the <Model_Name>_PLtoSMDatamap data map with a form and set it up for Smart Push. See Configuring Smart Push for a Form. If you later enable additional accounts in Financials, edit the data maps to add the detailed mapping between the accounts in Financials and the accounts in Strategic Modeling. For more information about editing data maps and detailed mappings, see Defining Advanced Data Maps. Note: You can make a copy of the data maps before editing them so you can keep the original data map definition. Note: Custom dimensions in Strategic Modeling and a custom chart of accounts in Financials are not supported when pushing data between Strategic Modeling and Financials. Pushing Data from a Strategic Modeling Model to Multiple Strategic Modeling Models You can push data from a Strategic Modeling Model (Source) to Multiple Strategic Modeling Models (Target) controlled by different properties specified at the account level. Pushing Data from a Strategic Modeling Model to Multiple Strategic Modeling Models Using Data Maps You can push data from a Strategic Modeling Model to Multiple Strategic Modeling Models using data maps. You can define Model to Model Data Maps that push data. Administrators have privileges to create, edit, and run data maps. To create Model to Model Data Maps: 1. From the Home page, click Application, then Data Exchange, and then click Data Maps. 2. Click Create. 3. Enter a name and description for the data map. 4. Under Source, select the source for the data: Select Model. The Select Model page is displayed. 5. Select a Strategic Modeling model and click Select. Chapter 7 Pushing Data from a Strategic Modeling Model to Multiple Strategic Modeling Models 7-23
- 156. If you don’t see your Strategic Modeling model in the list, from the Actions menu, select Synchronize. 6. Under Target, select Models. Note: This option is available only when a Strategic Modeling model is selected on the source. 7. Click Select under the Target section of the dimension mapping row for Model. The Select Members page is displayed. 8. Select the Models and click OK. Note: The Target can be multiple models. You can push the data from one source model to multiple target models. If you don’t see your Strategic Modeling model in the list, from the Actions menu, select Synchronize. 9. Click Select in the Source section of the dimension mapping row for Account. The Select Members page is displayed. 10. Select the accounts and click OK. Note: Notice that selected Account Members are displayed in both Source and Target columns. 11. Click Configure. The Edit Data Map page is displayed with the selected account configuration. 12. Update the default member values for Scenario, Value, Time Periods, and Cell Text as required and click Done. 13. Click Save and Close Defining Account Configuration You can edit the data map to set the properties for each selected account in the source. This defines the values that are used when pushing the data between models. To define account configuration: 1. On the Data Maps page, click Configure. Chapter 7 Pushing Data from a Strategic Modeling Model to Multiple Strategic Modeling Models 7-24
- 157. The Edit Data Map page displays the selected account configuration. On this page you can update Basic Information, Options, Selection, and Account Configuration. 2. For Account Configuration, click Scenario and make your selections for the selected account. Note: • These selections are used in the data push for the selected account. • For scenario rollups you will see the Business Case column in place of the Scenario column. The Business Case column displays the default option Any and this option is not editable. This is because the account configuration for the data movement is applicable for all the business cases in the current scenario rollup. The exact business cases for which the data movement happens will be determined at runtime based on your business case selection. 3. Click Value and select a value for the selected account. Note: The Value defines what data of the selected account to be pushed: • Input: Data from Input Value is pushed for the selected account. • Output: Data from Output Value is pushed for the selected account. • None: No data is pushed for the selected account 4. Click Time Periods and select a value for the selected account. Note: The value for Time Periods defines the data from which periods the data to be pushed for the selected account: • History: History Period data is pushed for the selected account. • Forecast: Forecast Period data is pushed for the selected account. 5. Click Cell Text and select a value for the selected account. Chapter 7 Pushing Data from a Strategic Modeling Model to Multiple Strategic Modeling Models 7-25
- 158. Note: The value for Cell Text defines the cell text from which cell text to be pushed for the selected account: • Scenario: The cell text for the Scenario cell is pushed for the selected account. • Time Series: The cell text for the time period cells is pushed for the selected account. • None: No cell text is pushed for the given account. 6. Click Done. You can do the following actions in the Account Configuration: • Click Add Accounts , this lists the Accounts page. Select the required accounts and click Select to add accounts. • Click Delete Row : Select the row to be deleted and click the Delete Row button. • Click Copy Row(s) : Select the row to be copied and click the Copy Row button. • Click Paste Row(s) : Click on the grid and click the Paste Row button. • Click Delete Invalid Entry : Click to delete invalid entry. • Click Find : Click and enter the word for search. Running a Data Map You run the Data Map after creating and defining the account configuration. 1. From the Home page, click Application, then Data Exchange, and then click Data Maps. 2. From the Actions menu for the data map you want to run, select Clear and Push Data. Chapter 7 Pushing Data from a Strategic Modeling Model to Multiple Strategic Modeling Models 7-26
- 159. To check the status of the data map and Smart Push job, from the Home page, click Application, and then click Jobs. Click the job name to see information and status about the Smart Push job. If there is an error, click Error to see details to help you resolve the error. Associating Model to Model Data Maps to Source Model When you associate model to model data maps to the source model, and when the model is checked in, the target models are automatically updated. To associate model to model data maps to a source model: 1. From the Home page, click Strategic Modeling, and then click Models. 2. From the Actions menu next to the source model, click Properties. 3. Click the Data Maps tab. 4. From the Available Data Maps list, select the data map that you want to associate with the model. 5. Click the data map, and then click . The selected data map is displayed on the Associated Data Maps list. Note: You can also drag and drop the data map to the Associated Data Maps list. 6. To run the data map when the model is checked in, select Run on Check-In in the Associated Data Maps list. 7. Click Apply. Using Microsoft Excel to Define Model to Model Data Maps You can use Microsoft Excel to define the Model to Model Data Maps. 1. Define the basic dimension mappings in the Data Maps page. 2. From the Actions menu, select Export Data Map. 3. Open the Exported Excel sheet containing Accounts, Source and Target Models. a. In the Selection sheet, update the Accounts and target models if needed. b. In the Account Configuration, update the accounts you modified in the selection sheet. 4. In the Data Maps page, from the Actions menu, select Import Data Map, and then save the data map. Chapter 7 Pushing Data from a Strategic Modeling Model to Multiple Strategic Modeling Models 7-27
- 160. Pushing Data from a Strategic Modeling Scenario Rollup to a Strategic Modeling Scenario Rollup You can push data from a Strategic Modeling scenario rollup to a Strategic Modeling scenario rollup using data maps. You can define scenario rollup to scenario rollup data maps that push the data between the models of a scenario rollup for given business cases. Administrators must have privileges to create, edit, and run data maps. To create scenario rollup to scenario rollup data maps: 1. From the Home page, click Application, then Data Exchange, and then click Data Maps. 2. Click Create. 3. Enter a name and description for the data map. 4. Under Source, select the source for the data: Select Scenario Rollup. The Select Scenario Rollup page is displayed. 5. Select a scenario rollup and click Select. If you don’t see your Strategic Modeling scenario rollup in the list, from the Actions menu, select Synchronize. 6. Under Target, select the scenario rollup. 7. Click Select under the Source and Target sections of the dimension mapping row for Model. The Select Members page is displayed. 8. Select the models for Source and Target and click OK. Note: The target can be multiple models. You can push the data from one source model to multiple target models. If you don’t see your Strategic Modeling model in the list, from the Actions menu, select Synchronize. 9. Click Select in the Source section of the dimension mapping row for Account. The Select Members page is displayed. 10. Select the accounts and click OK. Note: Notice that selected Account Members are displayed in both Source and Target columns. Chapter 7 Pushing Data from a Strategic Modeling Scenario Rollup to a Strategic Modeling Scenario Rollup 7-28
- 161. 11. Click Configure. See Defining Account Configuration. The Edit Data Map page is displayed with the selected account configuration. 12. Update the default member values for Value, Time Periods, and Cell Text as required, and then click Done. Note: Business Case displays Any and cannot be edited. 13. Click Save and Close. When running scenario rollup to scenario rollup type data maps, data movement happens with respect to business cases and contributing scenarios. The business case information is dynamic and is retrieved at runtime based on the business cases selected in the Run dialog, and data movement occurs based on the selected business case/contributing scenario between the source and target models for account/custom dimension selection defined in the data maps. Note: The Clear and Push Data option is not available for scenario rollup to scenario rollup type data maps. Scenario rollup to scenario rollup type data maps are only run from within the scenario rollup. Using Microsoft Excel to Define Scenario Rollup to Scenario Rollup Data Maps You can use Microsoft Excel to define the scenario rollup to scenario rollup data maps. 1. Define the mappings on the Data Maps page. 2. From the Actions menu, select Export Data Map. 3. Open the exported Excel sheet and update it as needed: a. In the Selection sheet, update the Source Model, Target Model, and Account columns. b. In the Account Configuration sheet, update the accounts you modified in the Selection sheet. Note: For scenario rollup to scenario rollup data maps, instead of a Scenario column, there is a column for Business Case. The only value allowed in the Business Case column is Any. All values other than Any that are present in the Business Case column will default to Any when the Excel sheet is imported into the application. Chapter 7 Pushing Data from a Strategic Modeling Scenario Rollup to a Strategic Modeling Scenario Rollup 7-29
- 162. 4. In the Data Maps page, from the Actions menu, select Import Data Map, and then save the data map. Managing Metadata with Model Change Management Use Model Change Management to copy metadata from a source model to one or more target models. Organizations work with different models to perform their strategic planning. Some models might be more granular, and others might focus on a specific territory or region. Typically, many of the models have a similar structure. For example, custom dimensions, accounts, scenarios, and time periods might differ only slightly. You can create a master source model in which you build the master structure of accounts, account groups, custom dimensions, time structure, and scenarios. You manage metadata by copying all or part of the metadata from this source model to one or more target models. You can also copy incremental changes from the source model to the target models. To use model change management, first create a base model to use as the source. The source model should include the accounts, account groups, custom dimensions, time structure, and scenarios that you want to copy to any target models. After a source model is created, you can use Model Change Management to copy any of the metadata to one or more target models. Overview of steps in Model Change Management: 1. Create the Model Change Management definition by selecting one or more target models. See Defining Target Models for Model Change Management. 2. Define the metadata to copy: • Accounts and account attributes • Account groups • Custom dimensions • Time • Scenarios See Defining Metadata to Copy with Model Change Management. 3. Run Model Change Management to copy the metadata from the source model to target model or models. See Copying Metadata from Source to Target. 4. If needed, you can edit or delete a Model Change Management definition. See Editing or Deleting a Model Change Management Definition. Videos Your Goal Watch This Video Learn about copying subaccounts and account attributes with Model Change Management. Copying Subaccounts and Account Attributes with Model Change Management in Enterprise Planning Cloud. Chapter 7 Managing Metadata with Model Change Management 7-30
- 163. Your Goal Watch This Video Learn about copying account groups with Model Change Management. Copying Account Groups with Model Change Management in Enterprise Planning Cloud. Learn about copying scenarios with Model Change Management. Copying Scenarios with Model Change Management in Enterprise Planning Cloud. Learn about copying time periods with Model Change Management. Copying Time Periods with Model Change Management in Enterprise Planning Cloud. Tip: When copying accounts, account groups, scenarios, and reports, Strategic Modeling attempts to match the order of items in the target model as closely as possible to the order in the source model. Defining Target Models for Model Change Management To manage metadata with Model Change Management, first define the target models to copy metadata to. 1. From the Home page, click Strategic Modeling, and then click Models. 2. From the Actions menu for the model you want to use as a source, click Model Change Management, then click Open, and then click Edit. 3. On the Map Target Model tab , click Add Target , select the target model or models you want to copy metadata to, and then click OK. The list includes all the models in the application. Click Exclude to prevent a target model from being included when Model Change Management runs; metadata is not copied to this model. 4. Define the metadata to copy, and then click Save. See Defining Metadata to Copy with Model Change Management. To delete a target model, select it and then click Remove Target . Defining Metadata to Copy with Model Change Management To manage metadata with Model Change Management, after defining the target models, define the metadata to copy. 1. On the Model Change Management page, click Configure Model to specify the metadata to copy. Chapter 7 Managing Metadata with Model Change Management 7-31
- 164. 2. Define the subaccounts to copy: On the Accounts tab, click Add and then click Add Subaccount Change. The list displays all the accounts that have subaccounts. Select the accounts that have the subaccounts that you want to copy to the target models, and then select from additional options for copying subaccounts: • Keep account details in the target—Keeps account hierarchy details in the target even if they do not exist in the source. • Copy account attributes—Copies the attributes of the selected account to the target. For all accounts, copies: – Account Name – Forecast Method – Subtotal Method – Account Note – Exchange Rate For Memo accounts, copies: – Account Name – Calculation Method – Aggregation Method – Output Type – Output Unit • Delete accounts not in the source—Deletes any accounts in the target that are not in the source. Oracle recommends that you select this option. Clearing this selection can cause errors during scenario rollup. All of the subaccounts from the selected accounts are copied to the target. 3. Define the account attributes to copy: On the Accounts tab, click Add and then click Add Account Attribute Change. Select the accounts that have the attributes that you want to copy to the target models, select the scenarios to copy for the selected accounts, and then select from additional options for copying account attributes: Note: Account names are not translated to other languages, as they are user- editable fields. • Rename Accounts—Renames accounts in the target to match those in the source. • Copy Other Account Attributes—When you select this option, these account attributes are copied from the source to the target: – For all accounts, copies: * Forecast Method Chapter 7 Managing Metadata with Model Change Management 7-32
- 165. * Subtotal Method * Account Note * Exchange Rate – For Memo accounts, copies: * Calculation Method * Aggregation Method * Output Type * Output Unit Tip: To edit the selections for accounts, click the link in the Change Details column on the Accounts tab. 4. Define the account groups to copy: On the Account Groups tab, click Add Account Group . Select the account groups you want to copy to the target models, and then select from the following options: • Do not overwrite account group in the target—Does not overwrite the account group if it already exists in the target. • Overwrite account group in the target—Overwrites the account group if it already exists in the target. • Delete account group in the target—Deletes any account groups in the target that are not in the source. Tip: Use Search Account Groups to easily find the account groups to copy. 5. Define how to handle custom dimensions when copying to the target: On the Custom Dimensions tab, click Copy Custom Dimensions to copy the custom dimensions to the target, and then select from the following options: • Assign accounts to custom dimensions in the target—Copies the account assignments along with the custom dimension structure to the target. For example, if the Sales account in the source is associated with a custom dimension, when the custom dimension structure is copied to the target, selecting this option assigns the custom dimension to the Sales account in the target. • Keep subhierarchies in custom dimensions in the target—When a custom dimension is in the target and in the source, allows you to keep child dimension members that are in the custom dimension in the target that are not in the source. • Delete custom dimensions not in the source—Deletes custom dimensions in the target that are not in the source. Oracle recommends that you select this option. Clearing this selection can cause errors during scenario rollup. Chapter 7 Managing Metadata with Model Change Management 7-33
- 166. Tip: Click Preview Source Custom Dimensions to review the custom dimensions in the source model before making your selections. 6. Define how to handle time periods when copying to the target: On the Time tab, click Copy Time Structure to copy the time structure to the target, and then select one or more of the following options for retaining time structure details in the target: • Allow the target to keep time period details—Allows the target to retain time detail that is not in the source. For example if the source contains only years but the target also contains quarters, selecting this option retains the quarters in the target when you copy the time structure. • Allow the target to keep years earlier than years defined in the source—For example if the source model's time structure includes 2018 - 2022, and the target model includes 2015 - 2020, selecting this option results in the target model time structure to include 2015 - 2022. • Allow the target to keep years later than years defined in the source—For example if the source model's time structure includes 2017 - 2022, and the target model includes 2018 - 2025, selecting this option results in the target model time structure to include 2017 - 2025. If you leave these options cleared, the time structure of the source completely replaces the time structure of the target. Tip: Click Preview Source Time Periods to review the time periods in the source model before making your selections. 7. Define how to handle scenarios when copying to the target: On the Scenarios tab, click Add Scenario Change , select the scenarios to copy to the target, select from the following options, and then click Add: • Do not overwrite scenario in the target—Keeps any scenarios already in the target, even if they are not in the source. • Overwrite scenario in the target—Overwrites scenarios in the target. • Delete scenario in the target—Deletes scenarios in the target that aren't in the source. If needed, after you've defined the scenarios to copy, you can change the options on the Scenarios tab: Click Change Details next to the scenario, and select a new option. 8. Define how to handle reports when copying to the target: On the Reports tab click Add Report Change , select the reports to copy to the target, select from the following options, and then click the confirm icon Chapter 7 Managing Metadata with Model Change Management 7-34
- 167. : • Do not overwrite if the Report exists in the target - If the report already exists in the target, it is left alone. • Overwrite if the Report exists in the target - Overwrites existing reports in the target models. • Remove the Report - Removes the report from target models if it exists. If needed, after you've defined the scenarios to copy, you can change the options on the Reports tab: Click Change Details next to the report, and select a new option. 9. Click Save and Close. Copying Metadata from Source to Target To manage metadata with Model Change Management, after defining the target models and the metadata to copy, copy the metadata from source to target. 1. From the Home page, click Strategic Modeling, and then click Models. 2. From the Actions menu for the source model, click Model Change Management, then click Open, and then click Run. Model Change Management locks the targets briefly to write the new metadata. If a target is locked by another user, the target is skipped and noted in the log. 3. Check the status of the model change management job: From the Home page, click Application, and then click Jobs. Click the job name to see information and status about the job. If there is an error, click Error to see details to help you resolve the error. You can also check the job status on the Model Change Management page: From the Actions menu for the source model, click Model Change Management and then click Status. You see the status for each target model and the overall status for the source model. 4. Review your changes in the target model or models. Editing or Deleting a Model Change Management Definition If needed, you can edit or delete a Model Change Management definition. 1. From the Home page, click Strategic Modeling, and then click Models. 2. • To edit a model change management definition: From the Actions menu for the source model, click Model Change Management, then click Open, and then click Edit. • To delete a model change management definition: From the Actions menu for the source model, click Model Change Management and then click Delete. If the model is locked by another user, you can view the Model Change Management definition but you can't make changes to it. Chapter 7 Managing Metadata with Model Change Management 7-35
- 168. 8 Using the Member Selector Related Topics • Working with Members • Making Selections • Member Relationships • Using Wildcards in Searches • Selecting Attribute Values as Members • Selecting Members for Forms • Selecting Substitution Variables as Members • Selecting User Variables as Members • Selecting UDAs as Members Working with Members Use the Select Members dialog box to select the members to use with the following features: • Business rule runtime prompts • User variables • Dynamic variables • Data export • Ad hoc grids • Point of view and page axis where valid intersection rules are applied • Valid intersections If variables and attributes are defined, you can select variables and attributes. You can display and select members by member name or alias. The display options that you define for the Member Selection dialog box override those defined as an application default by a Service Administrator, and those specified as an application preference. If drop-down member selectors are defined for row dimensions on a form, you can select members directly from the list, enter data, and add rows to a form. See Entering Data for Suppressed or Excluded Members in Working with Planning . Making Selections Only members, substitution variables, and attributes to which you have access are displayed. The Selections pane only displays if you invoke the member selector for multiple member selection. 8-1
- 169. If valid intersection rules are used, only valid members are displayed in application forms and in runtime prompts for Calculation Manager rules. In ad hoc forms, both on the Web and in Oracle Smart View for Office, the application doesn't filter by valid intersections rules in point of view and page axis. Only cells in grids honor valid intersection rules in ad hoc forms. To make selections: 1. Click . 2. Optional: Perform these tasks: • To enter search criteria (member name or alias only), press Enter (from the desktop) or click Search (on mobile). Note: The search isn't case-sensitive. You can search for a word, multiple words, or wildcard characters. See Using Wildcards in Searches. • To change display options such as viewing variables and attributes, showing alias names, showing member counts, sorting alphabetically, refreshing the member list, or clearing selections, click next to Search, and then select from the list of display options. • To filter the members that are displayed in the member list, under next to Search, select Add Filter, and then select from the list of filter options. Note: Android users can click to view and select filter options. 3. Make selections by clicking a member in the member list. To understand how related members are selected, see Member Relationships. Chapter 8 Making Selections 8-2
- 170. Note: • Selected members display a check mark and are moved to the Selections pane, if applicable. • To expand a parent member to see its child members, click the expansion icon to the right of the parent member name. Clicking the expansion icon will not select the parent member. • To clear selections you have made, click and then select Clear Selection. At times, you may find that a point of view and page axis member you want to select is suppressed. This occurs because a dimension selection in the point of view and page axis has invalidated other dimensions due to valid intersections that were applied. To resolve this issue, use the Clear Selection option to clear the point of view and page axis members you previously selected. Then you can use the point of view and page axis again to select members that were previously suppressed. • To show all the members that are suppressed due to valid intersection rules, click and then select Show Invalid Members. Invalid members are displayed but are unavailable for selection. 4. Optional: Perform these tasks: • To further refine which related members are selected in the Selections pane, click to the right of the member to display the member relationships menu: Chapter 8 Making Selections 8-3
- 171. Click the relationship name to select the related members, excluding the selected member. Click the include icon to the right of the relationship name to select the related members, including the selected member. For descriptions of the relationships, see Member Relationships. • If substitution variables or attributes are defined, below the member selection area, click next to Members, and then select Substitution Variables or Attributes to select members for substitution variables or attributes. Members are displayed as children. Only members to which the user has read access are displayed in forms. • To move or remove members in the Selections pane, click next to Selections. • To highlight the location of a selected member within the dimension hierarchy, double-click the member name in the Selections pane. Note: To highlight the location of a selected member on a mobile device, tap the member name in the Selections pane, and then tap Locate under next to Selections. 5. When you're done making selections, click OK. Chapter 8 Making Selections 8-4
- 172. Member Relationships This table describes which members and related members are included during member selection. Table 8-1 Member Relationships Relationship Members Included Member The selected member Ancestors All members above the selected member, excluding the selected member Ancestors (inc) The selected member and its ancestors Children All members in the level immediately below the selected member Children (inc) The selected member and its children Descendants All descendants of the selected member, excluding the selected member Descendants (inc) The selected member and its descendants Siblings All members from the same level in the hierarchy as the selected member, excluding the selected member Siblings (inc) The selected member and its siblings Parents The member in the level above the selected member Parents (inc) The selected member and its parent Level 0 Descendants All descendants of the selected member that have no children Left Siblings The members that appear before the selected member with the same parent Left Siblings (inc) The selected member and its left siblings Right Siblings The members that appear after the selected member with the same parent Right Siblings (inc) The selected member and its right siblings Previous Sibling The member that appears immediately before the selected member with the same parent Next Sibling The member that appears immediately after the selected member with the same parent Previous Level 0 Member The previous level zero member that appears before the selected member Examples: PrevLvl0Mbr(Jan) returns BegBalance; PrevLvl0Mbr(Jul) returns Jun; PrevLvl0Mbr(BegBalance) returns an empty result Next Level 0 Member The next level zero member that appears after the selected member Examples: NextLvl0Mbr(Mar) returns Apr; NextLvl0Mbr(Dec) returns an empty result Previous Generation Member The member that appears immediately before the selected member within the same generation Next Generation Member The member that appears immediately after the selected member within the same generation Chapter 8 Member Relationships 8-5
- 173. Table 8-1 (Cont.) Member Relationships Relationship Members Included Relative Returns a member relative to the specified member at the same generation with the specified offset. Examples: Relative("Jan", 4) returns May, which is January plus 4 months in a standard monthly Period dimension; Relative("Jan", -2) returns Nov, which is January minus 2 months in a standard monthly Period dimension. Relative Range Returns all of the members from the starting member to the offset member when going forward or from the offset member to the starting member when going backwards. Examples: RelativeRange("Jan", 4) returns Jan, Feb, Mar, Apr, May; RelativeRange("Jan", -2) returns Nov, Dec, Jan. Note: Member relationships work for any dimension, not just the Period dimension. We've used the Period dimension in our examples because it's easier to explain as time is linear. Using Wildcards in Searches You can use these wildcard characters to search for members. Table 8-2 Wildcard Characters Wildcard Description ? Match any single character * Match zero or multiple characters. For example, enter "sale*" to find "Sales" and "Sale" because * includes zero or more characters after the word "sale." The default search uses the * wildcard. For example, entering "cash" searches for "*cash*" and returns "Restricted Cash", "Cash Equivalents", "Cash", and "Noncash Expenses" because the word "cash" appears within each matched item. # Match any single number (0-9) [list] Match any single character within a specified list of characters. You can list specific characters to use as wildcard. For example, enter [plan] to use all the letters within the brackets as a single wildcard character. You can use the "-" character to specify a range, such as [A-Z] or [!0-9]. To use the "-" character as part of the list, enter it at the beginning of the list. For example, [-@&] uses the characters within the brackets as wildcard characters. [!list] Match any single character not found within a specified list of characters. The "-" character can also be used to indicate a range, such as [!A-Z] or [!0-9]. Chapter 8 Using Wildcards in Searches 8-6
- 174. Selecting Attribute Values as Members If attribute members are defined, you can select attribute values on the Select Members dialog box. For attribute members, selecting a non-level 0 attribute selects all level 0 descendants and applies the operator to each. For attributes of type numeric, date, and Boolean (where false = 0 and true = 1), evaluation is based on the minimum and maximum values. For text attributes, evaluation is based on the position from top to bottom in the hierarchy. The top position has the lowest value, and the bottom position has the highest value. Example: Numeric attribute In this example, the selected operator is applied to each level 0 descendant, based on the numeric value. For example, selecting NotEqual and Small in the Member Selection dialog box includes all values not equal to 1 and not equal to 2, so the selection includes 3, 4, 5, and 6. Selecting Greater and Small includes all values greater than 1 or greater than 2, so the selection includes 2, 3, 4, 5, and 6. Size Small 1 2 Medium 3 4 Large 5 6 Table 8-3 Example: Numeric Attribute Evaluation Selected Operator Selected Attribute Value Result Explanation Equal Large 5, 6 The Equal operator is applied to all level 0 descendants of Large, which includes 5 and 6. Less Medium 1, 2, 3 The Less operator is applied to all level 0 descendants of Medium. This includes values < 3 OR < 4, which results in 1, 2, and 3. Greater Medium 4, 5, 6 The Greater operator is applied to all level 0 descendants of Medium. This includes values > 3 OR > 4, which results in 4, 5, and 6. Chapter 8 Selecting Attribute Values as Members 8-7
- 175. Table 8-3 (Cont.) Example: Numeric Attribute Evaluation Selected Operator Selected Attribute Value Result Explanation GreaterOrEqual Medium 3, 4, 5, 6 The GreaterOrEqual operator is applied to all level 0 descendants of Medium. This includes values >=3 OR >= 4, which results in 3, 4, 5, and 6. LessOrEqual Medium 1, 2, 3, 4 The LessOrEqual operator is applied to all level 0 descendants of Medium. This includes values <=3 OR <=4, which results in 1, 2, 3, and 4. NotEqual Medium 1, 2, 5, 6 The NotEqual operator is applied to all level 0 descendants of Medium. This includes values not equal to 3 AND not equal to 4, which results in 1, 2, 5, and 6. Example: Text attribute For text attributes, the selected operator is applied to each level 0 descendant based on its position in the hierarchy, from top (lowest value) to bottom (highest value). In this example, Envelope is at the top position and has the lowest value. Packet has the next higher value, followed by Box, Carton, Barrel and Crate. Crate is at the bottom position and has the highest value. For this text attribute, selecting Less and Small includes values that are less than Envelope or less than Packet. Because Envelope is less than Packet, the resulting selection includes only Envelope. Likewise, selecting Greater and Large includes values that are greater than Barrel or greater than Crate, so the resulting selection includes only Crate. Containers Small Envelope Packet Medium Box Carton Large Barrel Crate Chapter 8 Selecting Attribute Values as Members 8-8
- 176. Table 8-4 Example: Text Attribute Evaluation Selected Operator Selected Attribute Value Result Explanation Equal Medium Box, Carton The Equal operator is applied to all level 0 descendants of Medium, which includes Box and Carton. NotEqual Medium Envelope, Packet, Barrel, Crate The NotEqual operator is applied to all level 0 descendants of Medium. This includes values not equal to Box AND not equal to Carton, which results in Envelope, Packet, Barrel, and Crate. Less Medium Box, Packet, Envelope The Less operator is applied to all level 0 descendants of Medium. This includes everything at a lower position than Carton OR a lower position than Box, which results in Box, Packet, and Envelope. LessOrEqual Medium Envelope, Packet, Box, Carton The LessOrEqual operator is applied to all level 0 descendants of Medium. This includes everything at the same position as Carton OR at a lower position than Carton, which results in Envelope, Packet, Box, and Carton. Selecting Members for Forms When selecting members for forms: • To filter members from certain users, restrict their access permissions to members, and then refresh the plan. • The order of members in the Selected Members list determines the order on forms. To change the order, select a member and click the Up or Down Arrow above the selected members list. Note: If you select members individually and select their parent first, the parent displays in the form at the top of its member hierarchy. (Note that depending on the number of hierarchy levels, calculating totals for the parent of individually selected members could take several passes, slowing calculations). The parent of members selected by relationship, for example, by I(Descendants), displays at the bottom of the hierarchy. • In the Layout tab of the Form Management dialog box, you can open the Member Selection dialog box by clicking the member selection icon, or by right-clicking a row or column and selecting Select Members. • To select different sets of members across the same dimension, see Creating Asymmetric Rows and Columns. • For forms with multiple dimensions in a row or column, you can set member selection options for a dimension by selecting that dimension from the Dimensions drop-down list Chapter 8 Selecting Members for Forms 8-9
- 177. that is displayed in the Member Selection dialog box for multiple dimensions in a row or column. • If you click the member selection icon, an option is displayed for Place Selection in Separate Rows or Place Selection in Separate Columns. This adds the selection to the rows or columns after the last existing row or column on the form. For example, for a form that contains members Acct1, Acct2, and Acct3 in Column A, if you select these members with Place Selection in Separate Columns selected, Acct1 is selected for column A, Acct2 for column B, and Acct3 for column C. If you select the members without this option, all of the members are selected for column A. This feature is available for single members only, not for members selected with functions, such as Children (inc). For example, if you select Q/IChildren for Column A and select Place Selection in Separate Columns, the form layout isn't changed. • All settings except Count are retained after the Member Selection dialog box is closed, and members in the Member Selection dialog box are displayed based on user-defined settings. Members displayed on the Layout tab don't inherit the display settings defined in Member Selection dialog box. Instead, they are displayed using the member name. • To define different sets of members for a dimension, see Creating Asymmetric Rows and Columns. • To set display, functionality, and printing options, see Setting Form Precision and Other Options. Selecting Substitution Variables as Members Substitution variables act as global placeholders for information that changes regularly. Substitution variables are especially useful for developing and reporting on rolling forecasts. When you select substitution variables as members on the form, their values are based on dynamically generated information. For example, you could set the current month member to the substitution variable CurMnth so that when the month changes, you need not update the month value manually in the form or the report script. Chapter 8 Selecting Substitution Variables as Members 8-10
- 178. Note: • When you open or calculate values on forms, the application replaces substitution variables with values assigned to them. • You create and assign values to substitution variables within the application. These substitution variables are then available in the application when you select members for a form. For instructions on creating and assigning values to substitution variables using the application, see Working with Substitution Variables. • Substitution variables must be appropriate for the context in forms. For example, you could select a substitution variable named CurrQtr with a value of Qtr2 as a member of the Time Period dimension. It's not valid to select a substitution variable named CurrYr for the Years dimension if its value is Feb. You can set substitution variables at the application or database level. The same substitution variable can exist on multiple levels; the application uses the first one it finds as it searches in this order: 1. Database 2. Application • You can select from substitution variables if they are enabled for runtime prompts in business rules, and their values match a member set in the runtime prompt for a business rule. • The application checks the validity of substitution variables when they are used (for example, when the form is opened). It doesn't check when you design forms, so you should test substitution variables by saving and opening forms. • If you migrated an application that uses Global variables, you can view, but not edit, them in this business process. To specify substitution variables in forms: 1. Create the form (see Creating Forms). 2. In Member Selection, click the Variables tab, expand Substitution Variables, and then select substitution variables the same way you select members, to move substitution variables to and from Selected Members. When selected, a substitution variable is preceded by an ampersand (&). For example: &CurrentScenario 3. Click OK. Selecting User Variables as Members User 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 must create the user variable. See Managing User Variables. When you create forms with user variables, users must select values for the variable before opening forms. For example, if you create a user variable called Division, users must select a Chapter 8 Selecting User Variables as Members 8-11
- 179. division before working in the form. The first time you select a variable for a form, you do it in preferences. Afterward, you can update the variable in preferences or in the form. To select user variables for forms: 1. Create the form (see Creating Forms). 2. On Member Selection, click the Variables tab, expand User Variables, and then select user variables the same way you select members, using the arrows to move user variables to and from Selected Members. User variables are displayed for the current dimension. For example, user variables for the Entity dimension might display as follows: Division = [User Variable] When selected, a user variable is preceded by an ampersand. For example: Idescendants(&Division) 3. Click OK. Selecting UDAs as Members You can select members for forms based on a common attribute, which you have defined as a user-defined attribute (UDA). Before you can associate the UDA with a form, you must create the UDA. See Working with UDAs. When you create forms with UDAs, any members that are assigned to the UDA are dynamically added to the form. For example, if you create a UDA called New Products and assign this UDA to the new products in the Product dimension hierarchy, the form will automatically display the new products at runtime. To select UDAs for forms: 1. Create the form (see Creating Forms). 2. On Member Selection, click the Variables tab, expand the UDAs, and then select the UDAs the same way you select members, using the arrows to move UDAs to and from the Selected Members. UDAs are displayed for the current dimension only. When selected, a UDA is preceded by UDA. For example: UDA(New Products) 3. Click OK. Chapter 8 Selecting UDAs as Members 8-12
- 180. 9 Connecting Environments in EPM Cloud Related Topics • About Connecting EPM Cloud Environments • Considerations for Migrating EPM Cloud Connections • Creating, Editing, and Deleting Connections to Other EPM Cloud Environments • Connecting to External Web Services • Specifying Advanced Options for External Connections • Navigating Across EPM Cloud Environments • Customizing Navigation Flows to Access Other EPM Cloud Environments • Using Direct URLs to Integrate Connected Environments About Connecting EPM Cloud Environments Overview Service Administrators can connect multiple EPM Cloud environments of the following types: • Account Reconciliation • Enterprise Profitability and Cost Management • Financial Consolidation and Close • FreeForm • Narrative Reporting • Planning • Planning Modules • Profitability and Cost Management • Oracle Sales Planning Cloud • Oracle Strategic Workforce Planning Cloud • Tax Reporting Once Service Administrators set up the connections, users who have access across EPM Cloud environments can navigate across them from a single access point with one login. Also artifacts such as forms and dashboards, from across environments can be co-mingled within a cluster or within tabs on a card in navigation flows. Artifacts in the target environment are accessible based on the user's role. 9-1
- 181. Note: You can also connect directly Oracle Analytics Cloud Enterprise Edition or Professional Edition 5.6 to EPM Cloud Platform, provided you have both services. When you've configured the connection, you can visualize data from EPM Cloud business processes in Oracle Analytics Cloud. You no longer have to model EPM data in a metadata repository (RPD) file to create visualizations and dashboards in Oracle Analytics Cloud. For more information, see the Oracle Analytics Cloud documentation. Which EPM Cloud environments can I connect? The source environment is the environment from which you're creating the connection. The target environment is the environment to which you're connecting from the source environment. You can connect these source environments (these environments can also be target environments): • FreeForm • Financial Consolidation and Close • Planning • Planning Modules • Sales Planning • Tax Reporting Source environments can also connect to these target environments (these environments can't be source environments): • Account Reconciliation • Enterprise Profitability and Cost Management • Narrative Reporting • Profitability and Cost Management • Strategic Workforce Planning What are the ways I can connect to other EPM Cloud environments? • Toggle between the source environment and the target environment on the Navigator menu. See Navigating Across EPM Cloud Environments. • Customize navigation flows in the source environment to access clusters, cards, and artifacts in other target environments from the Home page. See Customizing Navigation Flows to Access Other EPM Cloud Environments. • Use direct URLs to seamlessly integrate connected environments. See Using Direct URLs to Integrate Connected Environments. Considerations • Only Service Administrators create cross-environment connections. Chapter 9 About Connecting EPM Cloud Environments 9-2
- 182. Users click a navigation link to open the linked environment. Access within the linked environment is determined by the predefined role and access permissions, if any, assigned to the user. • For cross-environment navigation to be seamless, all environment instances to which cross-environment navigation flows are setup must belong to the same identity domain. Note: If the target and source environment instances are not on the same identity domain, then you'll not be able to establish a connection between them. • Service Administrators cannot configure cross-environment connections using corporate SSO (identity provider) credentials. If your environments are configured for SSO, ensure that identity domain credentials are maintained for the Service Administrators who configure cross-environment connections. See Enabling Sign In With Identity Domain Credentials. • Migrating cross-environment connections between test and production environments can cause issues in certain use case scenarios. For more information, see Considerations for Migrating EPM Cloud Connections. • Vanity URLs are not supported in cross-environment connections. Videos Your Goal Watch This Video Watch this video to learn how to customize an EPM Cloud workflow. Overview: Configure Navigation Flows to Integrate EPM Cloud Business Processes Watch this video series to learn about connected planning. You'll see the overall connected planning solution and how planning solutions can be connected through cross pod smart push and navigation flows to provide a seamless experience for planners across different departments. In the first video, the focus is on Financials and Sales. The next video focuses on Strategic Workforce Planning and IT Planning. The last video focuses on Marketing Campaign Planning. Overview: Connected Planning - Aligning Sales Plans with Financial Targets Overview: Connected Planning - Strategic Workforce and IT Planning Overview: Connected Planning - Managing Marketing Campaigns Considerations for Migrating EPM Cloud Connections Oracle recognizes that it's common practice for Service Administrators to try out new features, such as connecting environments, on test environments and then migrate to production environments. However, in doing so, it could cause some issues after migration. Here are some use case scenarios that you need to be aware of. In the following scenarios, assume you have environments for Financial Consolidation and Close and Planning. Chapter 9 Considerations for Migrating EPM Cloud Connections 9-3
- 183. Use Case Scenario 1: Test to Production When migrating connections from test environments to production environments, ensure that connections that were defined in the test environment are changed to point to the corresponding production environments. For example, a Service Administrator has defined a connection between the test environments of Planning and Financial Consolidation and Close. The Service Administrator then uses this connection to build a navigation flow in Planning that refers to a card in the Financial Consolidation and Close. The snapshot that the Service Administrator creates for migrating the Planning test environment will include connections and navigation flows, including the connection to Financial Consolidation and Close test environment. On migrating the snapshot into the Planning production environment, Planning will have an undesirable connection to the Financial Consolidation and Close test environment. You must manually change undesirable connections to point to the corresponding production environment either before or after migrating the environment. 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 Service Administrator might be trying to migrate a snapshot from a production environment into a test environment to resolve an issue. Because the connections created in the test environment still points to a production environment, it is important for the Service Administrator to modify connections so that they point to a test environment. Connections in test environments that point to a production environment may inadvertently tamper with the production environment. Creating, Editing, and Deleting Connections to Other EPM Cloud Environments Before you can create connections to other EPM Cloud environments, you must ensure you have access to the source and target environments you're connecting. You must also have URLs for the other environments you're connecting and login details for each environment such as user ID (Service Administrator) and password. To create, edit, duplicate, and delete connections: 1. Login to the source environment. 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. On the Select Provider to Create Connection page, select the target environment you want to add. c. Enter the target environment connection details: Chapter 9 Creating, Editing, and Deleting Connections to Other EPM Cloud Environments 9-4
- 184. – Click Change Provider to select a different target environment. – In Connection Name enter name for this navigation link; for example, Consolidation Application. – Enter an optional description for the link. – In URL, enter the URL of the target environment instance; for example, http(s)://your-target-host-url.com. This is the URL that you normally use to sign in to the target environment instance. – Use Service Administrator and Password to specify the credentials of a Service Administrator. Note: * These credentials are used only to define and validate the navigation link. When a user logs in, their own role and access will be applied to access the target environment. * Do not prefix user names with the domain name for connections to other EPM Cloud environments. However, the domain name is still needed for connections to other external Web services. See Connecting to External Web Services. – The Domain field is automatically populated based on the URL you enter. If there is no domain in the URL, then the Domain field is left blank. 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. Note: If you edit the URL to connect to a new service type, you could cause navigation flows to break. If you want to connect to a different service, Oracle recommends creating a new connection instead. 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 the connection you want to duplicate, click . b. Click Duplicate. c. Enter a name for the duplicate connection, then click OK. • To delete a connection: Chapter 9 Creating, Editing, and Deleting Connections to Other EPM Cloud Environments 9-5
- 185. a. On the Manage Connections page, in the Action column next to the connection you want to delete, click . b. Click Delete. When target environments are connected to an EPM Cloud source environment, they are listed in the My Connections pane on the Navigator menu of the source environment. The My Connections pane on the Navigator menu is where you can navigate across environments. See Navigating Across EPM Cloud Environments. For troubleshooting assistance, see Handling Issues with Navigation Flows in Oracle Enterprise Performance Management Cloud Operations Guide . Connecting to External Web Services Service Administrators can also connect to external Web services for the purpose of reading data from and writing to an external Web service. This connection can be referenced or used in a Groovy script to create a communications link between the Groovy script and the external HTTP/HTTPS resource. For more details and examples of how this connection can be used in a Groovy script, see the Java API documentation for the Connection and the HttpRequest objects in the EPM Groovy object model. Note: The Other Web Service Provider connection type is only available for use with those business processes that allow Groovy Rules to be created. See the Oracle Enterprise Performance Management Cloud, Groovy Rules Java API Reference. Before you can create connections to external Web services, you must ensure you have access to the Web service you're connecting. You must also have URLs for the Web service and any login details, if required. To create a connection to an external Web service: 1. Login to the source environment. 2. From the Home page, click Tools, and then click Connections. 3. On the Manage Connections page, click Create. 4. Click Other Web Service Provider. 5. Enter a Connection Name and a Description for the connection. 6. Enter the URL for the target connection. 7. Enter optional advanced options for the URL. Chapter 9 Connecting to External Web Services 9-6
- 186. Note: The optional advanced options enable you to specify query or header parameters when defining an external connection. See Specifying Advanced Options for External Connections. 8. Enter User and Password login credentials for the connection, if required. In some cases, such as connecting to Oracle Fusion Cloud Enterprise Performance Management services, the domain name may need to be prefixed to the user name; for example, <Identity Domain>.<User Name>. To understand basic authentication for EPM Cloud REST APIs and for instructions on finding your identity domain, see Basic Authentication - for Classic and OCI in REST API for Enterprise Performance Management Cloud. 9. Click Save and Close. Specifying Advanced Options for External Connections The optional advanced options enable you to specify query or header parameters when defining an external connection. Note: The ability to define query parameters for an external connection is only available for use with those business processes that allow Groovy Rules to be created. See the Oracle Enterprise Performance Management Cloud, Groovy Rules Java API Reference. To specify advanced options for external connections: 1. Create an external connection or open an existing external connection. See Connecting to External Web Services. 2. Enter connection details, and then click Show Advanced Options. 3. Specify query details as follows: • : Add query • : Delete query • Type: Select Header or Parameter. Header sets a default header that will be sent on every request made for this connection. Parameter sets a default query parameter that will be sent on every request made for this connection. • Secure: If selected, the value entered in the Value field will be encrypted. Clearing the Secure check box for a row will remove the value. Chapter 9 Specifying Advanced Options for External Connections 9-7
- 187. An example header that one would secure is the Bearer Token for external Web services that supports Bearer Authentication, or the API Key query parameter for external Web services that supports API keys for authentication. • Name: Enter a name for the header or query parameter. • Value: Enter the value for the header or query parameter. Navigating Across EPM Cloud Environments Once a Service Administrator creates connections to other EPM Cloud environments, the connections are listed in the My Connections pane on the Navigator menu. You can toggle between the environments from this location. You must have access to the other environments in order to open them. Artifacts are accessible based on the user's role. To open another Oracle Enterprise Performance Management Cloud environment: 1. From the Home page, click Navigator . 2. If environments are connected and you have access to those environments, you'll see a list of connected environments in the My Connections pane. Click an environment to open it. Note: Click the icon to the right of the environment name to open the environment in a new window. Chapter 9 Navigating Across EPM Cloud Environments 9-8
- 188. Customizing Navigation Flows to Access Other EPM Cloud Environments You can customize the business process interface to access other EPM Cloud environments from the Home page of a source environment. For example, you can add artifacts to the Home page, such as forms or reports, from other EPM Cloud environments. You can group these artifacts (called cards) into clusters by customizing navigation flows. Clusters and cards from target EPM Cloud environments can be directly included in the navigation flows of source EPM Cloud environments. You can also use the Navigation Flow Designer to customize cards to have tabular pages where each tab is an artifact from a different environment. These two use cases describe in detail how to customize navigation flows to access other EPM Cloud environments: • Grouping Cards from Other EPM Cloud Environments into Clusters • Configuring Cards with Tabs from Multiple EPM Cloud Environments To learn more about designing navigation flows, see Designing Custom Navigation Flows. Grouping Cards from Other EPM Cloud Environments into Clusters You can group cards from various EPM Cloud environments into a cluster that is accessible from the Home page of a source environment. For example, you can create a cluster within Financial Consolidation and Close consisting of cards with pre-built external reports from Narrative Reporting. Chapter 9 Customizing Navigation Flows to Access Other EPM Cloud Environments 9-9
- 189. Cards from multiple environments can also be included within the same cluster on a source environment. For example, a Tax Reporting user can launch a Journals icon from Financial Consolidation and Close without leaving Tax Reporting. You create clusters and add cards to clusters by customizing navigation flows. For general information about navigation flows, see Designing Custom Navigation Flows. To create a cluster made up of cards from other EPM Cloud environments: 1. Launch the Navigation Flow page and create a navigation flow or edit an existing navigation flow: Note: To create a navigation flow, you must first select an existing navigation flow and make a copy of it. Then edit the duplicate navigation flow details and 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 select Create Copy. Enter a name for the navigation flow, and then click OK. Chapter 9 Customizing Navigation Flows to Access Other EPM Cloud Environments 9-10
- 190. Note: New flows are marked Inactive until they are activated by the Service Administrator. To activate or deactivate a navigation flow, in the Active column, click Active or Inactive. Only one navigation flow at a time can be active. c. To edit an existing navigation flow, click the name of the navigation flow you want to edit. Note: Editing is only possible if the navigation flow is inactive. If the navigation flow you want to edit is active, ensure you mark it Inactive 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 the navigation flow in which you want to add a cluster. b. To create a new cluster, right-click a card or cluster (or click ), 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 environment, right-click a card or cluster (or click Add Existing Card/Cluster), select the target environment under My Connections, and then choose the cluster you want to add to your navigation flow. Note the following: • Clusters can't be directly selected from Narrative Reporting and Profitability and Cost Management using the Add Existing Card/Cluster option. • Clusters that are added from another navigation flow or from another environment will display the localized labels that were defined in the source navigation flow. To update the cluster labels in your navigation flow, on the Home page, click Tools, and then click Artifact Labels. See Specifying Artifact Labels. 3. Select the cards to include in the cluster using one of these options: • Navigate to the card you want to add to the cluster. If the card is within another environment, first select the environment under My Connections, and then navigate to the card in that environment. Assign the card to a cluster using one of these options: – To the right of the card that you want to move, in the Order column, click . Select the cluster, and then click OK. – Click the name of the card to view the card details, then for Cluster select a cluster for the card, and then click OK. • Navigate to the cluster in which you want to add the new card. If the cluster is within another environment, first select the environment under My Connections, and then Chapter 9 Customizing Navigation Flows to Access Other EPM Cloud Environments 9-11
- 191. navigate to the cluster in that environment. Right-click the cluster (or click ), click Add Card In Cluster, and then select an option: – Select Add Existing Card, to select an existing card or to add existing cards from another cluster to the selected cluster. – Select Add Card, and then enter card details to add a new card to the selected cluster. Note: You cannot add a card to a cluster if the card or the cluster is already referenced from another navigation flow. The cards will appear in the listing as children of the cluster. Use the up and down arrows 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 the Setting and Actions menu, click Reload Navigation Flow. If you can't see your referenced artifacts after activating and reloading the navigation flow, see Handling Issues with Navigation Flows in Oracle Enterprise Performance Management Cloud Operations Guide. Configuring Cards with Tabs from Multiple EPM Cloud Environments You can also customize cards in navigation flows to have tabular pages where each tab is an artifact from a different environment. For example, a Planning user can click a Revenue icon which launches a card with horizontal tabs showing reports from Narrative Reporting. Chapter 9 Customizing Navigation Flows to Access Other EPM Cloud Environments 9-12
- 192. You create tabular cards by customizing navigation flows. For general information about navigation flows, see Designing Custom Navigation Flows. To configure a card made up of tabs and sub tabs from other EPM Cloud environments: 1. Launch the Navigation Flow page and create a navigation flow or edit an existing navigation flow: Note: To create a navigation flow, you must first select an existing navigation flow and make a copy of it. Then edit the duplicate navigation flow details and 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 select Create Copy. Enter a name for the navigation flow, and then click OK. Note: New flows are marked Inactive until they are activated by the Service Administrator. To activate or deactivate a navigation flow, in the Active column, click Active or Inactive. Only one navigation flow at a time can be active. c. To edit an existing navigation flow, click the name of the navigation flow you want to edit. Chapter 9 Customizing Navigation Flows to Access Other EPM Cloud Environments 9-13
- 193. 2. Add a tabular card with artifacts from various target environments: a. If there is an existing card you want to add from another environment, from the Navigation Flow page, right-click a card or cluster (or click ), click Add Existing Card/Cluster, select the target environment under My Connections, and then choose the card you want to add to your navigation flow. Note the following: • Cards can't be directly selected from Narrative Reporting and Profitability and Cost Management using the Add Existing Card/Cluster option. • Cards that are added from another navigation flow or from another environment will display the localized labels that were defined in the source 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. b. To add a new tabular card to the navigation flow, from the Navigation Flow page, right-click a card or cluster (or click ), 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. 3. Add tabs and sub tabs to the tabular card: a. To add an existing tab, right-click a tab, click Add Existing Tab (or click the Add Existing Tab button), and then select a tab from the Object Library. b. To add a new tab, right-click a tab, click Add New Tab (or click the Add New Tab button), and then edit tab details. c. Right-click a tab, click Add New Sub Tab or Add Existing Sub Tab (or click the Add New Sub Tab or Add Existing Sub Tab buttons), and then choose a sub tab from the Object Library or edit sub tab details. 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 reports. To select an artifact from another environment, select the target environment under My Connections, and then choose the artifact you want to add to your sub tab. e. Repeat adding tabs and sub tabs until the card is complete. 4. Click Save and Close. Chapter 9 Customizing Navigation Flows to Access Other EPM Cloud Environments 9-14
- 194. Note: • For cards with multiple tabs or sub tabs, the last tab accessed by a user will be retained the next time the user accesses the card in the same session. If the user logs out and then logs back in, the default tab will be displayed. • Tabs or sub tabs that are added from another navigation flow or from another environment will display the localized labels that were defined in the source navigation flow. To update the tab labels in your navigation flow, on the Home page, click Tools, and then click Artifact Labels. See Specifying Artifact Labels. You must reload the navigation flow to view your design time changes. To reload a navigation flow, click the down arrow next to your user name. Then on the Setting and Actions menu, click Reload Navigation Flow. If you can't see your referenced artifacts after reloading the navigation flow, see Handling Issues with Navigation Flows in Oracle Enterprise Performance Management Cloud Operations Guide. Using Direct URLs to Integrate Connected Environments Other source systems like Oracle ERP Cloud can embed URLs to directly link to artifacts contained in cards, tabs, and sub-tabs within connected Oracle Enterprise Performance Management Cloud environments. Other Cloud environments like Oracle ERP Cloud use direct URL links to open connected EPM Cloud content like forms, dashboards, infolets, and reports. To make the integration between EPM Cloud and other systems seamless, you can copy the unique URLs for the artifacts within a connected EPM Cloud business process. You can copy the unique URLs in one of two ways: • Copy the individual URL for an artifact in the business process. See Copying Individual URLs. Chapter 9 Using Direct URLs to Integrate Connected Environments 9-15
- 195. • Export all of the URLs in the business process to a CSV file, then find and copy the unique URLs. See Exporting All URLs to a CSV File. Videos Your Goal Watch This Video Learn how to use direct links to embed EPM Cloud content in other systems such as ERP Cloud and NetSuite. Overview: Embed Content Using Direct Links Copying Individual URLs Use the Copy URL option on the artifact listing page to copy the unique URL for an artifact (dashboards, forms, infolets, or reports) in your Oracle Enterprise Performance Management Cloud business process. To copy the unique URL for an artifact: 1. From the Home page, open the listing page for the artifact. For example, click Dashboards, Data, Infolets, or Reports. 2. From the listing page, click next to the artifact, and then select Copy URL. 3. The Copy URL dialog displays the unique URL for the artifact. Copy the URL. Only users with access to the targeted artifact can perform actions on it. Exporting All URLs to a CSV File Use the Export URLs option to create a CSV file that provides the unique URLs for each card, tab, or sub-tab within a connected Oracle Enterprise Performance Management Cloud business process. URLs are grouped by navigation flow and cluster, so the URLs are easier to find within the CSV file. You can open the CSV file with a text editor or Microsoft Excel and embed the relevant URL within the source system pages to serve as a launch point into EPM Cloud. To export EPM Cloud URLs to a CSV file: 1. Log into an EPM Cloud environment. 2. From the Home page, click the down arrow next to the user name (upper right corner of the screen). 3. On the Settings and Actions menu, click Export URLs, and then click Save. The system saves a CSV file to the default download folder on your local machine, and the filename is automatically generated with the current date and time of the server; for example, 19_Feb_2021 13_15_38 Navigation Flow URLs.csv. Find the file in your download folder, and open it with a text editor or with Microsoft Excel. Viewing the Exported URLs File The CSV file lists all of the URLs in the business process. Each card, tab (vertical tab), and sub-tab (horizontal tab) has a unique URL. When viewed in a text editor like Notepad or in Microsoft Excel, it identifies the unique URL for each card, tab, and sub- tab, so the URLs for each artifact can be more easily found. URLs are grouped by navigation flow and by cluster. Chapter 9 Using Direct URLs to Integrate Connected Environments 9-16
- 196. Note: Only cards, tabs, and sub-tabs have URLs. Navigation flows and clusters don't have URLs. Table 9-1 Direct URLs Export File Headers Header Description Navigation Flow Name The name of the navigation flow; for example, Default or Financial Flow. Status Status of the navigation flow; for example, Active or Inactive. Type Type of entry; for example, cluster, card, tab, or sub tab Name The cluster, card, tab or sub-tab name where the artifact is contained. This entry will be empty for clusters or cards which do not contain an artifact directly. Artifact Type The type of artifact; for example, Form, Dashboards, Financial Reports, and URL type artifacts. Artifact Name The name of the artifact or, in the case of an URL type artifact, the direct URL of the target page. Caution: If a direct URL is displayed, do not confuse this URL with the unique URL you'll use to integrate the connected environments. URL This is the unique URL you will use to integrate connected environments. Visible Indicates whether the artifact in the navigation flow is visible on the Home page to users or groups; for example, Y or N. Role/Group The role or group who can view the navigation flow. If a navigation flow is Global, then it can be seen by all users. Description The description of the navigation flow, if provided. The URLs export file provides the information separated by a vertical bar or pipe ( | ) delimiter character. See the following example direct URLs export file as viewed in Notepad: To view the URLs export file in Microsoft Excel: Chapter 9 Using Direct URLs to Integrate Connected Environments 9-17
- 197. 1. Open Excel, and then click the Data menu. 2. Click New Query, then From File, and then click From CSV. 3. Find and select the CSV file you exported, and then click Import. A new window displays the data in the CSV file. 4. To make the first row of the CSV file the header row, click Edit, click Use First Row as Headers, and then click Close and Load. The resulting Excel file will look like the following example: Find and copy the unique URL (found in the URL column) for the card, tab, or sub-tab that you wish to have integrated into the other connected environment. Only the URL target will open and users with access to the targeted artifact can perform the same actions as if they're working within the target business process. Chapter 9 Using Direct URLs to Integrate Connected Environments 9-18
- 198. 10 Designing Custom Navigation Flows Customize the business process interface using navigation flows. Navigation flows enable designers to control how roles or groups interact with the business process. Related Topics • Understanding Navigation Flows • Viewing and Working with Navigation Flows Understanding Navigation Flows Navigation flows give business process designers control over how various roles, or groups, interact with the business process. The Navigation Flow Designer enables you to customize the business process interface. For example, you can change the names of the cards and clusters that display on the Home page and the order in which they are displayed. You can hide cards, create new cards, and group cards into clusters. You can also customize the vertical and horizontal tabs that display on a card. Videos Your Goal Watch This Video Learn how to customize navigation flows. Designing Navigation Flows in Planning View the highlights of customizing workflows for connected environments. Overview: Configure Navigation Flows to Integrate EPM Cloud Business Processes Related Topics • What Can Be Customized in the Business Process Interface? • Navigation Flow Customization Categories • Navigation Flow Permissions • Predefined Navigation Flows • Viewing and Working with Navigation Flows What Can Be Customized in the Business Process 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 • Add new cards • Add existing cards 10-1
- 199. • 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 Categories Navigation 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, User or Power 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 navigation flows exist at multiple levels, updates are applied in the order of highest (global) to lowest (groups). For example, if you create a navigation flow that displays an icon on the Home page named "My Tasks", and then another Service Administrator duplicates the navigation flow, makes the following changes to the card, and then associates the navigation flow with a 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 "Sales Tasks" Users who belong to the group called Sales will see the label "Sales Tasks" in the navigation flow instead of "My Tasks," and all other users will see the label "Company Tasks". Navigation Flow Permissions The business process offers three levels of permissions for navigation flows: • Role-based: Permissions are granted to users or groups assigned to a specific role; for example, a User will see different cards displayed on the Home page than a Service Administrator • Artifact-based: Permissions are granted to users or groups who can see certain artifacts; for example, a User will see only the forms to which they have been assigned permission • Global: Permissions are granted to all users Predefined Navigation Flows The business process comes with one predefined navigation flow, called Default. The Default navigation flow is read only; therefore, you can't make any modifications to it. These are the operations you can and cannot perform on the Default navigation flow: • Name: You can't modify the name. Chapter 10 Understanding Navigation Flows 10-2
- 200. • 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 Flows Service Administrators can view a list of navigation flows, including the predefined navigation flow, within the Navigation Flow page. The Navigation Flow page lists each navigation flow by name, indicates the role or the group that has access to the navigation flow (if assigned), and provides a description of the navigation flow (if provided). The listing also indicates whether the navigation flow is active or not. To view the navigation flow: 1. Click Tools, and then click Navigation Flows. 2. To work with a navigation flow, perform an action: • For design best practices and considerations, see Navigation Flow Design Best Practices and Naming Considerations. • To create and duplicate navigation flows, see Creating and Duplicating Navigation Flows. • To edit a navigation flow, see Editing a Navigation Flow. • To activate or deactivate a navigation flow, see Activating and Deactivating Navigation Flows. • To validate navigation flows and to learn how to find and resolve navigation flow elements with missing artifacts, see Using Validate to Find Missing Artifacts in Navigation Flows. • To resolve a navigation flow in the listing that is displaying a warning icon , see Resolving Navigation Flows that Display a Warning Icon. • To rename cards and tabs, see Customizing Labels for Cards, Tabs, and Clusters. • To customize the graphics used for cards and tabs, see Customizing Icons for Cards and Vertical Tabs. • To hide and unhide cards and tabs, see Hiding and Unhiding Clusters, Cards, and Tabs. • To change the display order of cards on the Home page, see Changing the Display 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. Chapter 10 Viewing and Working with Navigation Flows 10-3
- 201. Navigation Flow Design Best Practices and Naming Considerations To provide an optimal user experience and to avoid excessive scrolling on the Home page and within cards and tabs, you must adhere to the following guidelines when designing navigation flows: • Keep the top level items (cards and clusters) to no more than 16 visible items. • Add no more than 16 visible cards to a cluster. • Add no more than 10 visible vertical tabs within a card. • Add no more than 20 visible sub tabs (horizontal tabs) within a vertical tab. • Label names on sub tabs (horizontal tabs) display only the first 30 characters at runtime. Hovering your cursor over the tab reveals the entire label. Note: If you attempt to exceed the visibility limits, you will see a warning message telling you that you've exceeded the limit. There are naming restrictions for navigation flows, cards, clusters, tabs, and infolets (if your business process uses infolets) in navigation flows. You cannot use these special characters: • ampersand ( & ) • less than sign ( < ) • greater than sign ( > ) • quotation mark ( " ) • backslash ( ) • plus sign ( + ) Creating and Duplicating Navigation Flows To create a navigation flow, you must first select an existing navigation flow and make a 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 Navigation Flows. 2. 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. Chapter 10 Viewing and Working with Navigation Flows 10-4
- 202. Note: Ensure that you adhere to the navigation flow naming restrictions outlined in Navigation Flow Design Best Practices and Naming Considerations. 4. Edit details for the navigation flow. See Editing a Navigation Flow. Note: New flows are marked Inactive until they are activated by the Service Administrator. To activate a navigation flow, see Activating and Deactivating Navigation Flows. To reload a navigation flow to view design time changes, see Reloading a Navigation Flow. Editing a Navigation Flow To edit a navigation flow: 1. Open the Navigation Flow page. See Viewing and Working with Navigation Flows. 2. Click the name of the navigation flow you want to edit. Note: The predefined navigation flow isn't editable. However, you can create a copy of a predefined navigation flow and edit the copy. See Predefined Navigation Flows. You'll see a page listing the cards and clusters in the navigation flow. On this page you can edit the role or goup assignation, designate which clusters and cards are visible on the Home page, change the order in which the navigation flow clusters and cards are displayed, add cards to clusters or remove them, and remove clusters and cards from the navigation flow. • Assign To: Click to assign the navigation flow to a group of users or to a role. • Visible: Edit the visibility of the navigation flow clusters and cards on the Home page by selecting or deselecting them in the Visible column. Note: Ensure that you adhere to the navigation flow guidelines for visibility outlined in Navigation Flow Design Best Practices and Naming Considerations. • Order: Clusters and cards are listed in the order in which they are displayed on the Home page, if visible. Selecting an up or down arrow option repositions the clusters Chapter 10 Viewing and Working with Navigation Flows 10-5
- 203. and cards in the listing and changes the display order of the clusters and cards on the Home page. Selecting the right arrow moves a card into a cluster. • Remove: Removes the cluster or card from the navigation flow. 3. Click a cluster or card to edit details. For descriptions of card details, see the following topics: • Adding Cards • Adding Tabs to a Tabular Page To reload a navigation flow to view design time changes, see Reloading a Navigation Flow. Activating and Deactivating Navigation Flows You can create multiple navigation flows for each category (global, role, or group), but only one navigation flow can be active in each category. Whenever you make a navigation flow active, the other navigation flows in the same category will become inactive. Note: Each business process requires one active global navigation flow. To make a different global navigation flow active, select another global navigation flow and activate it. 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 business process is in administration mode, then users can save any modifications. • 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: 1. Open the Navigation Flow page. See Viewing and Working with Navigation Flows. 2. In the Active column, click Active or Inactive. An active flow will be marked inactive. Conversely, an inactive flow will be marked active. Chapter 10 Viewing and Working with Navigation Flows 10-6
- 204. Using Validate to Find Missing Artifacts in Navigation Flows While viewing the Navigation Flow listing, you might see navigation flow nodes or artifacts displaying an error icon . This error occurs because artifacts that were associated with the navigation flow were either renamed or removed and they are now considered missing. You'll need to edit the navigation flow to associate it with either a renamed artifact or with a different artifact before you can activate the navigation flow. You might not realize that artifacts are considered missing, so it's recommended that you validate your navigation flows before setting them to Active status. Note: To resolve a navigation flow displaying a warning icon , see Resolving Navigation Flows that Display a Warning Icon. To validate navigation flows to find missing artifacts and reassociate them: 1. Open the Navigation Flow page. See Viewing and Working with Navigation Flows. 2. If they aren't already deactivated, set the navigation flows you want to validate to Inactive status. See Activating and Deactivating Navigation Flows. 3. Highlight the row or rows of the navigation flows you want to validate. 4. Click , and then select Validate. If artifacts are missing, you'll see an error message indicating which navigation flows are referencing artifacts that cannot be found. 5. Click the name of each navigation flow with the error, and then expand the nodes which display the error icon until you reach the Manage page which displays the missing artifact. 6. For Artifact, click to select the renamed artifact or a different artifact in the Artifact Library. 7. Click Save and Close. 8. Repeat the validation on your navigation flows and drill down to make corrections, as needed, until you see a message indicating the navigation flows are valid. 9. Activate the navigation flows. See Activating and Deactivating Navigation Flows. To reload a navigation flow to view design time changes, see Reloading a Navigation Flow. Resolving Navigation Flows that Display a Warning Icon While viewing the Navigation Flow listing, you might see a navigation flow displaying a warning icon . This occurs because the group that was associated with the navigation flow was deleted. You'll need to edit the navigation flow to associate it with a group or role before you can activate the navigation flow. Chapter 10 Viewing and Working with Navigation Flows 10-7
- 205. Note: To resolve navigation flows displaying an error icon , see Using Validate to Find Missing Artifacts in Navigation Flows. To resolve the navigation flow: 1. Open the Navigation Flow page. See Viewing and Working with Navigation Flows. 2. Click the name of the navigation flow displaying the warning icon . 3. For Assign To, click to assign the navigation flow to a group of users or to a role, then click Save and Close. 4. Activate the navigation flow. See Activating and Deactivating Navigation Flows. To reload a navigation flow to view design time changes, see Reloading a Navigation Flow. Customizing Labels for Cards, Tabs, and Clusters You 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, there is 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 you want 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 in the Artifact Labels page on the Tools cluster, that definition will take precedence and will display during runtime. To change a label permanently, redefine it in the Artifact Labels page. See Specifying Artifact Labels. • Ensure that you adhere to the naming restrictions outlined in Navigation Flow Design Best Practices and Naming Considerations. 3. If customizing the label for a tab: a. Click the name of the card you want to edit. Chapter 10 Viewing and Working with Navigation Flows 10-8
- 206. b. In the tab listing on the Manage Tab page, click the name of the tab you want to edit. c. Enter a new name for the tab and save it. To reload a navigation flow to view design time changes, see Reloading a Navigation Flow. Customizing Icons for Cards and Vertical Tabs You can change the icons used for cards and vertical tabs. You must pick from the available icons provided in the icon library. To customize the icons for cards and vertical tabs: 1. Open the Navigation Flow page and click the name of the navigation flow you want to edit. See Viewing and Working with Navigation Flows. 2. If customizing the icon for a card: a. Click the name of the card you want to edit. 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. b. In the tab listing on the Manage Tab page, click the name of the tab you want to edit. c. Click the icon for the tab, select a new icon from the library, and then save it. To reload a navigation flow to view design time changes, see Reloading a Navigation Flow. Hiding and Unhiding Clusters, Cards, and Tabs You cannot 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 Ensure that you adhere to the navigation flow guidelines for visibility outlined in Navigation Flow Design Best Practices and Naming Considerations. To hide and unhide clusters, cards, and tabs: 1. Click the Navigation Flow icon and click the name of the navigation flow you want to edit. See Viewing and Working with Navigation Flows. 2. Edit the Home page visibility of the navigation flow clusters and cards by selecting or deselecting them in the Visible column. 3. If hiding or unhiding a tab: a. Click the name of the card you want to edit. b. In the tab listing on the Manage Tab page, select or deselect the check box in the Visible column. To reload a navigation flow to view design time changes, see Reloading a Navigation Flow. Chapter 10 Viewing and Working with Navigation Flows 10-9
- 207. Changing the Display Order of Cards on the Home Page You can change the display order of cards in the Navigation Flow Designer. Cards display on the Home page in the order they appear within the listing To change the display order of the cards on the Home page: 1. Open the Navigation Flow page. See Viewing and Working with Navigation Flows. 2. In the listing, use the up and down arrows in the Order column to move cards up or down in the navigation flow order. To reload a navigation flow to view design time changes, see Reloading a Navigation Flow. Adding Cards The icons you see on the Home page represent cards. Cards are specific to each functional area of the business process. Each card navigates users to the corresponding area, where other information is displayed as one or more tabbed pages. You can create single page or multiple page (tabular) cards. To ensure an optimal user experience, review the navigation flow design best practices. See Navigation Flow Design Best Practices and Naming Considerations. You can also group cards into clusters. See Grouping Cards into Clusters. To add cards to a navigation flow: 1. Open the Navigation Flow page and click the name of the navigation flow you want to edit. See Viewing and Working with Navigation Flows. 2. To add an existing card to the navigation flow, right-click a card or cluster in the list (or click ), click Add Existing Card/Cluster, and then select a card. If there is an existing card you want to add from another environment, right-click a card or cluster in the list (or click ), click Add Existing Card/Cluster, select the target environment under My Connections, and then choose the card you want to add to your navigation flow. Note the following: • Cards can't be directly selected from Narrative Reporting and Profitability and Cost Management using the Add Existing Card/Cluster option. • Cards that are added from another navigation flow or from another environment will display the localized labels that were defined in the source 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. • A reference card is a card that is already referenced from another navigation flow. References to already referenced cards are not supported in navigation flows and will not be available for selection in the Object Library when adding an existing card; for example: – A card referring to a remote artifact or remote tab will not be available from the Object Library when adding an existing card. Chapter 10 Viewing and Working with Navigation Flows 10-10
- 208. – A card referring to a tab from another navigation flow will not be available from the Object Library when adding an existing card. A card is added to the list as a sibling under the card or cluster that is currently selected. To add a card to a cluster, see Grouping Cards into Clusters. Note: Cards that are added without first selecting a card or cluster are added to the end of the list. 3. To add a new card to the navigation flow, right-click a node in the list (or click ), click Add Card, and then select details for the new card: Table 10-1 New Card Details Label Description Name Enter a label for the card. Ensure that you adhere to the naming restrictions outlined in Navigation Flow Design Best Practices and Naming Considerations. 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. Page Type Select Single Page or Tabular Page format. Content Source If you selected the Single Page format, select Artifact or URL: • 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 reports. To select an artifact from another environment, select the target environment under My Connections, and then choose the artifact you want to add. • For URL, enter a complete URL; for example, a URL to embed an Oracle Analytics Cloud dashboard in a card, then click Preview to validate the URL in a popup window. Insert only external site URLs starting with the https:// security protocol. Don't use internal or relative URLs or URLs for unconsenting third-party sites. See About Using URLs to Embed Third-Party Pages in EPM Cloud Applications. Orientation If you selected the Tabular Page format, select Vertical or Horizontal, and then add new or existing tabs and sub tabs. See Adding Tabs to a Tabular Page. A card is added to the list as a sibling under the card or cluster that is currently selected. To add a card to a cluster, see Grouping Cards into Clusters. Chapter 10 Viewing and Working with Navigation Flows 10-11
- 209. Note: Cards that are added without first selecting a card or cluster are added to the end of the list. 4. Click Save and Close. To reload a navigation flow to view design time changes, see Reloading a Navigation Flow. Adding Tabs to a Tabular Page Tabs can be horizontal or vertical. For example, the Valid Intersections card (under the Application cluster) is a tabular page with two horizontal tabs: Setup and Reports. Note: If Redwood Experience is enabled, the Setup and Reports tabs are at the bottom of the page. You can also create tabular pages with vertical tabs. Vertical tabs display a graphic and text appears when the cursor is hovered over the tab. Horizontal tabs display labels with text only or text with icons. To ensure an optimal user experience, review the navigation flow design best practices. See Navigation Flow Design Best Practices and Naming Considerations. To add tabs to a tabular page: 1. Open the Navigation Flow page and click the name of the navigation flow you want to edit. See Viewing and Working with Navigation Flows. 2. Edit an existing card by clicking the name of the card you want to edit, or add a new card by right-clicking a card (or clicking ), and then clicking Add Card. 3. On the Manage Card page, select the following options: • For Page Type, select Tabular Page. • For Orientation, select Vertical or Horizontal. 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, right-click a tab in the listing at the bottom of the Manage Card page, click Add Existing Tab (or click the Add Existing Tab button), select a tab from the Object Library, and then click OK. Chapter 10 Viewing and Working with Navigation Flows 10-12
- 210. Note: A reference tab is a tab that is already referenced from another navigation flow. References to already referenced tabs are not supported in navigation flows and will not be available for selection in the Object Library when adding an existing tab; for example: • A tab referring to a remote artifact or remote sub-tab will not be available from the Object Library when adding an existing tab. • A tab referring to a sub tab from another navigation flow will not be available from the Object Library when adding an existing tab. b. To add a new tab, right-click a tab, click Add New Tab (or click the Add New Tab button), and then edit tab details. c. Select the content for the new tab: • 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 reports. To select an artifact from another environment, select the target environment under My Connections, and then choose the artifact you want to add. • For URL, enter a complete URL; for example, a URL to embed an Oracle Analytics Cloud dashboard in a tab, then click Preview to validate the URL in a popup window. Insert only external site URLs starting with the https:// security protocol. Don't use internal or relative URLs or URLs for unconsenting third-party sites. See About Using URLs to Embed Third-Party Pages in EPM Cloud Applications. A tab is added to the list as a sibling under the tab that is currently selected. Note: Tabs that are added without first selecting a tab are added to the end of the list. 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. Right-click a tab, and click Add New Sub Tab or Add Existing Sub Tab (or click the Add New Sub Tab or Add Existing Sub Tab button), and then edit sub tab details. d. Select the content for the new sub tab: • 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 reports. To select an artifact from another environment, select the target environment under My Connections, and then choose the artifact you want to add. Chapter 10 Viewing and Working with Navigation Flows 10-13
- 211. • For URL, enter a complete URL; for example, a URL to embed an Oracle Analytics Cloud dashboard in a sub tab. Click Preview to validate the URL in a popup window. Insert only external site URLs starting with the https:// security protocol. Don't use internal or relative URLs or URLs for unconsenting third-party sites. See About Using URLs to Embed Third-Party Pages in EPM Cloud Applications. A sub tab is added to the list as a sibling under the tab that is currently selected. Note: Sub tabs that are added without first selecting a tab are added to the end of the list. 7. Click Save and Close. To reload a navigation flow to view design time changes, see Reloading a Navigation Flow. Note: • For cards with multiple tabs or sub tabs, the last tab accessed by a user will be retained the next time the user accesses the card in the same session. If the user logs out and then logs back in, the default tab will be displayed. • Tabs or sub tabs that are added from another navigation flow or from another environment will display the localized labels that were defined in the source navigation flow. To update the tab labels in your navigation flow, on the Home page, click Tools, and then click Artifact Labels. See Specifying Artifact Labels. About Using URLs to Embed Third-Party Pages in EPM Cloud Applications Oracle Enterprise Performance Management Cloud uses IFrame to embed third-party URLs. IFrame requires that the page that is being embedded must give approval to the page that is embedding it. For example, if we want to embed a page from sharepoint.com into an EPM Cloud application, then sharepoint.com must allow oraclecloud.com to embed the page from sharepoint.com. This can be achieved by adding oraclecloud.com in the Content Security Policy of the web application whose page you need to embed. When embedding a third-party page you also must consider if the page is available to the public or if it requires a login. For example, pages from wikipedia.org do not need any authentication. Chapter 10 Viewing and Working with Navigation Flows 10-14
- 212. If you are embedding a page that requires authentication, you need to see if SSO can be enabled for the page. If not, then your page may not load inside IFrame. As a workaround, log in to that web application in another browser tab, and then if you access the same page from the EPM Cloud application, it will open. This URL support feature allows you to embed the following types of pages: • Other Oracle products (would need to enable SSO) • Web applications owned by customer (would need to allow the EPM Cloud application by updating the Content Security Policy and enabling SSO, or likewise) • Pages from the public domain (for example, wikipedia.org) Removing Navigation Flows, Cards, and Tabs You 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: – Access Control – Navigation Flows – Daily Maintenance – Migration To remove navigation flows, cards, and tabs: 1. Open the Navigation Flow page. See Viewing and Working with Navigation Flows. 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 . To reload a navigation flow to view design time changes, see Reloading a Navigation Flow. Chapter 10 Viewing and Working with Navigation Flows 10-15
- 213. Grouping Cards into Clusters A cluster is a grouping of cards. You must first create a cluster and then you can assign cards to it. You can also add existing clusters to navigation flows. To ensure an optimal user experience, review the navigation flow design best practices. See Navigation Flow Design Best Practices and Naming Considerations. To assign cards to 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 in which you want to add a cluster. See Viewing and Working with Navigation Flows. b. To create a new cluster, right-click a card or cluster in the list (or click ), click Add Cluster, enter or select the cluster details, and then choose a graphic for the cluster. Note: Ensure that you adhere to the visibility and naming restrictions outlined in Navigation Flow Design Best Practices and Naming Considerations. A cluster is added to the list as a sibling under the cluster that is currently selected. Note: Clusters that are added without first selecting a card or cluster are added to the end of the list. c. To add an existing cluster, right-click a card or cluster in the list (or click ), click Add Existing Card/Cluster. If there is an existing cluster you want to add from another environment, right-click a card or cluster in the list (or click ), click Add Existing Card/Cluster, select the target environment under My Connections, and then choose the cluster you want to add to your navigation flow. Chapter 10 Viewing and Working with Navigation Flows 10-16
- 214. Note: • Clusters can't be directly selected from Narrative Reporting and Profitability and Cost Management using the Add Existing Card/ Cluster option. • Clusters that are added from another navigation flow or from another environment will display the localized labels that were defined in the source navigation flow. To update the cluster labels in your navigation flow, on the Home page, click Tools, and then click Artifact Labels. See Specifying Artifact Labels. • A reference cluster is a cluster that is already referenced from another navigation flow. References to already referenced clusters are not supported in navigation flows and will not be available for selection in the Object Library when adding an existing cluster. A cluster is added to the list as a sibling under the card or cluster that is currently selected. Note: Clusters that are added without first selecting a card or cluster are added to the end of the list. d. Click Save and Close. 2. Select the cards to include in the cluster using one of these options: a. Navigate to the card you want to add. If the card is within another environment, first select the environment under My Connections, and then navigate to the card in that environment. Assign the card to a cluster using one of these options: • To the right of the card in the Order column, click , select the cluster, and then click OK. • Click the name of the card to view the card details, then for Cluster select a cluster for the card, and then click OK. b. Navigate to the cluster in which you want to add a card, then right-click the cluster (or click ), click Add Card In Cluster, and then select an option: • Select Add Existing Card, to select an existing card or to add existing cards from another cluster to the selected cluster. • Select Add Card, and then enter card details to add a new card to the selected cluster. Chapter 10 Viewing and Working with Navigation Flows 10-17
- 215. Note: You cannot add a card to a cluster if the card or the cluster is already referenced from another navigation flow. c. Click Save and Close. The cards will appear in the listing as children of the cluster. Use the up and down arrows next to the cards to reorder the cards within the cluster, if needed. To reload a navigation flow to view design time changes, see Reloading a Navigation Flow. Reloading a Navigation Flow To display design changes while you're working with a navigation flow, you can reload the navigation flow. To reload a navigation flow after making design changes: 1. From the Home page, click the down arrow next to the user name (upper right corner of the screen). 2. On the Settings and Actions menu, click Reload Navigation Flow. Switching Navigation Flows at Runtime If you belong to multiple groups or if a navigation flow is assigned to a role, you might have access to more than one navigation flow. To switch navigation flows at runtime: 1. From the Home page, click . 2. Select the navigation flow you want to view. Chapter 10 Viewing and Working with Navigation Flows 10-18
- 216. Chapter 10 Viewing and Working with Navigation Flows 10-19
- 217. 11 Editing Dimensions in the Simplified Dimension Editor Work with application dimensions and members in the simplified grid interface. Related Topics • About Editing Dimensions in the Simplified Dimension Editor • Dimension Overview • 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 • Setting Up Scenarios and Specifying Versions About Editing Dimensions in the Simplified Dimension Editor The 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 can edit member properties directly on the grid and you can perform ad hoc operations such as zooming in, zooming out, keep selected, remove selected, and freeze. Videos Your Goal Watch This Video Get an introduction to the Simplified dimension editor. Overview: Dimension Editor in Planning Tutorials Tutorials provide instructions with sequenced videos and documentation to help you learn a topic. Your Goal Learn How Learn how to add and edit dimensions and members in the Simplified dimension editor. Managing Dimensions in Planning Related Topics • Creating Dimensions • Dimension Overview • Accessing the Simplified Dimension Editor 11-1
- 218. • Working with the Simplified Dimension Editor Grid • Editing Dimension Properties in the Simplified Dimension Editor • Editing Member Properties in the Simplified Dimension Editor • Setting Up Scenarios and Specifying Versions Dimension Overview Related Topics • About Dimensions and Members • About Sparse and Dense Dimensions • About Dimension Hierarchies • About Custom Dimensions • About Entities • About Accounts • Accounts, Entities, Periods, and Cubes About Dimensions and Members Dimensions categorize data values. Seven dimensions are included with the application: Account, Entity, Scenario, Version, Period, Years, and Currency. You can create up to 32 user-defined custom dimensions. Members are components of dimensions. About Sparse and Dense Dimensions Sparse dimensions lack data values for the majority of member combinations. Dense dimensions have data values for the majority of member combinations. At least one dense dimension is required. Custom attributes can't be assigned to dense dimensions. The application designates the Account and Period dimensions as dense, and the remaining dimensions as sparse. To optimize performance for sparse dimensions, the application searches for and calculates only occupied data values in each dimension combination, reducing calculation time and disk usage. You can modify these settings. About Dimension Hierarchies Dimension hierarchies define structural and mathematical relationships, and consolidations between members in the application. Relationships are represented graphically in a collapsible hierarchy diagram. The levels below the cube name are dimensions, and the levels below each dimension are members. The Period dimension can contain the member YearTotal, which contains members Q1, Q2, Q3, and Q4. Members Q1, Q2, Q3, and Q4 contain their own members for the corresponding months in the year. To consolidate data values in the Period dimension, roll up monthly data values to get quarterly data values, and quarterly data values to get yearly data values. Chapter 11 Dimension Overview 11-2
- 219. Members of the same level that belong to the same dimension or member are called siblings. For example, Q1, Q2, Q3, and Q4 are siblings because they are at the same level in the hierarchy, and are members of the same member, YearTotal. The members of a dimension are called children of the dimension. Members that belong to a member are called children of that member. The member YearTotal is a child of Period, the members of Q1, Q2, Q3, and Q4 are children of YearTotal, and Jan, Feb, and Mar are children of Q1. Q1 is the parent of Jan, Feb, and Mar, YearTotal is the parent of Q1, Q2, Q3, and Q4, and Period is the parent of YearTotal. About Custom Dimensions The application includes two custom dimensions: Account and Entity. You can edit the names of these dimensions, and create up to 32 user-defined dimensions. Caution: You can't delete custom dimensions after you create them. Use Account and user-defined dimensions to specify data to gather from users. Use Entity to model the flow of planning information in the organization and establish the plan review path. • Aggregation Options • Storage Options Aggregation Options You can define calculations within dimension hierarchies using aggregation options. Aggregation options determine how child member values aggregate to parent members: • + Addition • - Subtraction • * Multiplication • / Division • % Percent • ~ Ignore • Never (don't aggregate, regardless of hierarchy) Storage Options When working with dimensions, it's important to understand the different data storage options and how to use them in the business process. • Table 1 • About Dynamic Calc • Dynamic Calc Versus Dynamic Calc and Store • About Store Data Storage Chapter 11 Dimension Overview 11-3
- 220. • About Shared Data Storage • About Never Share Data Storage • About Label Only Data Storage Table 11-1 Storage Options Option Impact Dynamic Calc and Store Calculates data values of members, and stores values. 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 data values. Shared Allows members in the same dimension to share data values. Label Only Has no data associated with the member. About Dynamic Calc With dynamically calculated members, the application calculates data values of members, and disregards these values. As a best practice, Oracle recommends a limit of 100 children under a Dynamic Calc parent. Changing a member's storage to Dynamic Calc may result in loss of data, depending on how the data was originally derived. You may need to update outlines, calculations, or both to get the dynamically calculated value. Dynamic Calc Versus Dynamic Calc and Store In most cases, you can optimize calculations and lower disk usage by using Dynamic Calc instead of Dynamic Calc and Store when calculating members of sparse dimensions. Use Dynamic Calc and Store for members of sparse dimensions with complex formulas, or that users retrieve frequently. For members of dense dimensions, use Dynamic Calc. Dynamic Calc and Store provides only a small decrease in retrieval time and regular calculation time, and doesn't significantly lower disk usage. For data values accessed concurrently by many users, use Dynamic Calc. Retrieval time may be significantly lower than for Dynamic Calc and Store. Note: • Don't use Dynamic Calc for base-level members for which users enter data. • Don't use Dynamic Calc for a parent member if you enter data for that member in a target version. Parent members set to Dynamic Calc are read-only in target versions. • Data values are not saved for Dynamic Calc members. Chapter 11 Dimension Overview 11-4
- 221. About Store Data Storage Don't set parent members to Store if their children are set to Dynamic Calc. With this combination, new totals for parents are not calculated when users save and refresh forms. About Shared Data Storage Use Shared to allow alternate rollup structures in the application. About Never Share Data Storage The default data storage type is Never Share when you add user-defined custom dimensions. You can use Never Share for parent members with only one child member that aggregates to the parent, to apply access to the child member. About Label Only Data Storage Label Only members are virtual members; they are typically used for navigation and have no associated data. Note: • You can't assign level 0 members as Label Only. • Label Only members can display values. • Making dimension members Label Only minimizes database space by decreasing block size. • You can't assign attributes to Label Only members. • In a multicurrency application, you can't apply Label Only storage to members of these dimensions: Entity, Versions, Currencies, and user-defined custom dimensions. To store exchange rates, use Never Share. • Data storage for children of Label Only parents is set to Never Share by default. Caution: Don't design forms in which Label Only parents follow their first child member, as you can't save data in the first child member. Instead, create forms with Label Only parents selected before their children, or don't select Label Only parents for forms. About Entities Entities typically match your organization’s structure, such as geographical regions, departments, or divisions. Create entity members for groups that submit plans for approval. Entity members help define budget review, or approvals. See Managing Approvals. Chapter 11 Dimension Overview 11-5
- 222. For example, you may have regional centers preparing budgets for country headquarters. The country headquarters may prepare plans for corporate headquarters. To match this structure, create members for the regions, countries and headquarters. Specify regions as children of country members, and country members as children of headquarters. Forms support multiple currencies per entity, enabling data entry for multiple currencies and reporting against one currency. However, the application supports a base currency for each entity. You can set the currency for entered values, which are converted to other currencies having defined exchange rates. About Accounts Account dimension members specify the information needed from users. Create an account structure that lets budget preparers input data for budget items. You can define calculations in the account structure. Related Topics • Account Types • Saved Assumptions • Data Type and Exchange Rate Type Account Types Account type defines accounts’ time balance (how values flow over time) and determines accounts’ sign behavior for variance reporting with member formulas. Examples of Using Account Types Table 11-2 Using Account Types Account Type Purpose Expense Cost of doing business Revenue Source of income Asset Company resource Liability and Equity Residual interest or obligation to creditors Saved assumption Centralized planning assumptions ensuring consistency across the application Summary of Account Types Table 11-3 Summary of Account Types Account Type Time Balance Variance Reporting Revenue Flow Non-Expense Expense Flow Expense Asset Balance Non-Expense Liability Balance Non-Expense Chapter 11 Dimension Overview 11-6
- 223. Table 11-3 (Cont.) Summary of Account Types Account Type Time Balance Variance Reporting Equity Balance Non-Expense Saved Assumption User-defined User-defined Variance reporting and time balance settings are system-defined; only Saved Assumption is user-defined. Time Balance Property Time balance specifies how the application calculates the value of summary time periods. Table 11-4 Time Balance Properties Time Balance Property Description Example Flow Aggregate of all values for a summary time period as a period total. Jan: 10 Feb: 15 Mar: 20 Q1: 45 First Beginning value in a summary time period as the period total. Jan: 10 Feb: 15 Mar: 20 Q1: 10 Balance Ending value in a summary time period as the period total. Jan: 10 Feb: 15 Mar: 20 Q1: 20 Average Average for all the child values in a summary time period as the period total. Jan: 10 Feb: 15 Mar: 20 Q1: 15 Fill The value set at the parent is filled into all its descendents. If a child value changes, the default aggregation logic applies up to its parent. Consolidation operators and member formulas overwrite Fill values when the members are recalculated. Jan: 10; Feb: 10; Mar: 10; Q1: 30 Weighted Average - Actual_Actual Weighted daily average, based on the actual number of days in a year; accounts for leap year, in which February has 29 days. In the example, the average for Q1 is calculated: (1) Multiply each month’s value in Q1 by the number of days in the month, (2) Sum these values, (3) Divide the total by the number of days in Q1. Assuming it's a leap year, the result is calculated: (10 * 31 + 15 * 29 + 20 * 31) / 91 = 15 Note that this time balance property is only supported for dimensions bound to a block storage cube. Aggregate storage cubes do not support the Weighted Average - Actual_Actual time balance property. Jan: 10 Feb: 15 Mar: 20 Q1: 15 Weighted Average - Actual_365 Weighted daily average, based on 365 days in a year, assuming that February has 28 days; doesn't account for leap years. In the example, the average for Q1 is calculated: (1) Multiply each month’s value in Q1 by the number of days in the month, (2) Sum these values, (3) Divide the total by the number of days in Q1. Assuming it's not a leap year, the result is calculated: (10 * 31 + 15 * 28 + 20 * 31) / 90 = 15 Jan: 10 Feb: 15 Mar: 20 Q1: 15 Chapter 11 Dimension Overview 11-7
- 224. Table 11-4 (Cont.) Time Balance Properties Time Balance Property Description Example Custom Spreading is disabled and the application designer is expected to add customized spreading. For instance, you can feed a value into the period total (Q1) using Groovy rules and it will calculate the summary time periods using the Flow method. NA Disable Spreading is disabled and the summary time period is read-only. Disable prevents data from being entered on non-level zero periods. The Flow method is used to aggregate into the period total (Q1), but it won’t spread down to the summary time periods. NA Note: • You can use the Weighted Average - Actual_Actual and Weighted Average - Actual_365 time balance properties only with a standard monthly calendar that rolls up to four quarters. For information on how the application calculates and spreads data with the different Time Balance settings, see Working with Planning . • For Custom and Disable time balance properties, the application designer needs to be aware of the storage characteristics of the member that they write to, be it aggregated storage or block storage. For example, you can only save to level zero members in aggregated storage and if you try to save to a dynamic calc member, it’ll be ignored and overwritten when recalculated. Also note that spreading only happens in the grid prior to save, be it automatic or using a Groovy rule. After the grid is saved, normal Essbase behavior will take over with regard to saving and reading data (that is, normal outline math will apply, member formulas, time balance, and so on). Account Types and Variance Reporting An account’s variance reporting property determines whether it's treated as an expense when used in member formulas: • Expense: The actual value is subtracted from the budgeted value to determine the variance • Non-Expense: The budgeted value is subtracted from the actual value to determine the variance Setting Account Calculations for Zeros and Missing Values With time balance properties First, Balance, and Average, specify how database calculations treat zeros and missing values with the Skip options. Chapter 11 Dimension Overview 11-8
- 225. Table 11-5 Effect of Skip Options When Time Balance is Set to First Skip Option Description Example None Zeros and #MISSING values are considered when calculating parent values (the default). In the example, the value of the first child (Jan) is 0, and zeros are considered when calculating the parent value, so Q1 = 0. Jan: 0 Feb: 20 Mar: 25 Q1: 0 Missing Excludes #MISSING values when calculating parent values. In the example, the value of the first child (Jan) is #MISSING, and #MISSING values are not considered when the calculating parent values, so Q1 = second child (Feb), or 20. Jan: #MISSING Feb: 20 Mar: 25 Q1: 20 Zeros Excludes zero values when calculating parent values. In the example, the value of the first child (Jan) is 0, and zero values are not considered when calculating parent values, so Q1 = the second child (Feb), or 20. Jan: 0 Feb: 20 Mar: 25 Q1: 20 Missing and Zeros Excludes #MISSING and zero values when calculating parent values. In the example, the value of the first child (Jan) is zero, and the value of the second child (Feb) is missing. Because missing and zero values are not considered when calculating parent values, Q1 = the third child (Mar), or 25. Jan: 0 Feb: #MISSING Mar: 25 Q1: 25 Saved Assumptions Use saved assumptions to centralize planning assumptions, identifying key business drivers and ensuring application consistency. You select time balance and variance reporting properties. • Variance reporting determines the variance between budgeted and actual data, as an 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 saved assumption account members: • Create a saved assumption of an expense type for variance reporting, assuming that the actual amount spent on headcount is less than the amount budgeted. To determine the variance, the application subtracts the actual amount from the budgeted amount. • Determine the value for office floor space by using the time period’s last value. • Make an assumption about the number of product units sold at the end of the time period. Determine the final value for the summary time period by aggregating the number of units sold across time periods. Data Type and Exchange Rate Type Data type and exchange rate type determine how values are stored in account members, and the exchange rates used to calculate values. Available data type for account members’ values: • Currency: Stores and displays in the default currency. Chapter 11 Dimension Overview 11-9
- 226. • 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. In a multiple currency application, for accounts with the Currency data type, available Exchange Rate types (valid for any time period): • Average: Average exchange rate • Ending: Ending exchange rate • Historical: Exchange rate in effect when, for example, earnings for a Retained Earnings account were earned or assets for a Fixed Assets account were purchased. In a Simplified multiple currency application, for accounts with the Currency data type, available Exchange Rate types (valid for any time period): • FX Rates - Average • FX Rates - Ending Accounts, Entities, Periods, and Cubes By assigning cubes for Account, Entity, and Period members, you set to which cubes the members’ children have access. For example, Total Sales Account may be valid for Revenue and P&L, but Fixed Assets Account may be valid for only Balance Sheet. Not assigning a cube to a member prevents that member’s children from accessing that cube. When moving members, if the new parent is valid for different cubes, members remain valid only for cubes they have in common with the new parent. If the new parent of an account member has another source cube, the member’s source cube is set to the first new valid cube of that member. Entities and Cubes Typically, entity members prepare different plans. When defining entity members, specify cubes for which they are valid. Because forms are associated with cubes, you can control which entity members can enter data for each cube. Accounts and Cubes If accounts are valid for multiple cubes, specify the source cube to determine which cube’s database stores the account value for them. Accessing the Simplified Dimension Editor To 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. Chapter 11 Accessing the Simplified Dimension Editor 11-10
- 227. 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. Working with the Simplified Dimension Editor Grid Work with grid elements in the simplified grid interface. Related Topics • Switching to Another Dimension • Customizing the Column Layout • Viewing Ancestors • Showing Member Usage in an Application • Focusing Your Editing • Finding Members • Moving Members • Sorting Members • Moving Members to Another Hierarchy • Working with Member Formulas • Copying Member Names from Microsoft Excel Switching to Another Dimension To 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 Layout Each column in the Simplified dimension editor grid represents a member property (Member Name, Parent Member, Default Data Storage, and so on). The columns that initially display on the grid can be different based on which dimension type you're editing. You can customize the layout of columns in the Simplified dimension editor grid by hiding, unhiding, or resizing columns. You can also display the complete set of properties (all columns) by clearing the Default Mode option; for example, by clearing Default Mode, you can view the UDA column for the Account dimension (the UDA column is hidden in Default Mode). To customize the column layout in the Simplified dimension editor grid: 1. View Edit Member Properties. See Accessing the Simplified Dimension Editor. 2. On the dimension grid, right-click any column heading. Chapter 11 Working with the Simplified Dimension Editor Grid 11-11
- 228. A checklist of columns displays. Also displayed are column or grid resizing options. 3. Select or clear the check boxes for the columns you want to hide or unhide on the grid. Note: To view all property columns in the grid, clear the Default Mode check box. Default Mode is selected by default, and limits the properties that are displayed. Clearing this option displays a larger (complete) set of properties (as columns). 4. To change the size of the grid or the columns that are displayed on the grid, select or clear the Force fit columns option. Selecting this option resizes the columns so that all columns are visible on the grid without scrolling. Viewing Ancestors Ancestors are all the members above the selected member in the dimension hierarchy. To view the ancestors for the selected member in the Simplified dimension editor grid: 1. View Edit Member Properties. See Accessing the Simplified Dimension Editor. 2. Select a member on the dimension editor grid. 3. Click Actions, and then select Show Ancestors. Showing Member Usage in an Application Before performing such operations as deleting members, it's important to understand where 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 dimension editor: Chapter 11 Working with the Simplified Dimension Editor Grid 11-12
- 229. 1. View Edit Member Properties. See Accessing the Simplified Dimension Editor. 2. Select a member on the dimension editor grid. 3. Click Actions, and then Show Usage. Focusing Your Editing Use zoom in, zoom out, keep selected, remove selected, and freeze to focus your editing while working in the Simplified dimension editor grid. To perform these operations while viewing the dimension editor grid: 1. View Edit Member Properties. See Accessing the Simplified Dimension Editor. 2. To focus your editing on specific members in the grid, select a member, and then click one of the following zoom operations: • Zoom In Next level: Displays all members one level below the selected member • Zoom In All levels: Displays all descendant members below the selected member • Zoom In Bottom level: Displays all descendant members of the selected member 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 or column, 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 left of the selected column stationary so the column or columns can't be scrolled. Only columns to the right of the frozen column can be scrolled. For example, you can freeze the first column that includes the member name so that you can scroll and edit that member's properties and still see the member name. To unfreeze columns, click Freeze once again. Finding Members To find dimension members in the Simplified dimension editor grid: 1. View Edit Member Properties for a dimension. See Accessing the Simplified Dimension Editor. 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. Moving Members To move members: 1. View Edit Member Properties. Chapter 11 Working with the Simplified Dimension Editor Grid 11-13
- 230. See Accessing the Simplified Dimension Editor. 2. Select the member to move. 3. To move the member up one position, click . To move the member down one position, click . Sorting Members You can sort members in ascending or descending order, by children or descendants. Sorting members affects the outline. For example, you can alphabetize a list of child members by sorting in descending order to help users quickly locate members in hierarchies in the Simplified dimension editor. Note: You can sort dimensions in Planning Modules except for the following: • Dense dimensions • The "Plan Element" dimension in Financials • The "Project Element" dimension in Projects (regardless of whether you rename it or not) To sort members using the Simplified dimension editor: 1. View Edit Member Properties. See Accessing the Simplified Dimension Editor. 2. On the dimension grid, select the members whose children or descendants you want to sort. 3. For Sort, select Children or Descendants. Note: • If you do not see the Sort options at the top of the page, click . • Sorting by children affects only members in the level immediately below the selected member. Sorting by descendants affects all descendants of the selected member. 4. Click or . Moving Members to Another Hierarchy To move members to another hierarchy in the Simplified dimension editor: 1. View Edit Member Properties. See Accessing the Simplified Dimension Editor. Chapter 11 Working with the Simplified Dimension Editor Grid 11-14
- 231. 2. In the Parent Member column of the grid, type a new parent name for the member you want to move. 3. Click Save. Working with Member Formulas You can define or edit member formulas directly in the Simplified dimension editor grid, in the formula bar, or in the Member Formula dialog where you can validate member formulas. You can define member formulas to combine operators, calculation functions, dimension and member names, and numeric constants to perform calculations on members. Member formulas can also include: • Operator type, function, value, member name, UDA, and so on allowed in formulas. • Predefined formula expressions, including Smart List values, that expand into a formula or value upon database refresh. To define or edit member formulas in the Simplified dimension editor: 1. View Edit Member Properties. See Accessing the Simplified Dimension Editor. 2. In the Default Formula column of the grid, select the member for which you want to define or edit a formula. Define or edit the formula for the member using one of the following options: • Click the cell once more in the dimension editor grid to enter or edit the formula. • Click within the formula bar above the dimension editor grid, and then enter or edit 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 formula cell in the grid. Press Ctrl while clicking the member name you want to include 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 formula bar, and then click Validate. 4. Click Save. Copying Member Names from Microsoft Excel To 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 press Ctrl+C to copy the data onto the clipboard. 2. Highlight and select the target cell or cells in the Simplified dimension editor, and then press Ctrl+V. Chapter 11 Working with the Simplified Dimension Editor Grid 11-15
- 232. 3. When the Clipboard helper is displayed, press Ctrl+V again. The data is pasted to the Clipboard helper. 4. Click Paste to paste the data into the Simplified dimension editor. Editing Dimension Properties in the Simplified Dimension Editor To access the properties of a dimension in the Simplified dimension editor: 1. From the Home page, click Application, and then click Overview. 2. Click the Dimensions tab, and then click the name of the dimension for which you want to view dimension properties. 3. Click the Edit Dimension Properties tab . Dimension properties must conform to guidelines listed in Naming Restrictions. Table 11-6 Dimension Properties Property Value Dimension Enter a name that is unique across all dimensions. Description Optional: Enter a description. Alias Table and Alias Optional: Select an alias table. Enter an alternate name for the dimension. See Administering Alias Tables. Cube Select the cubes for which the dimension is enabled. Clearing this option disables all members of the dimension for the deselected cube. Two Pass Calculation Recalculate values of members based on values of parent members or other members. Available for Account and Entity members with Dynamic Calc or Dynamic Calc and Store properties. Apply Security Allow security to be set on the dimension members; must be selected before assigning access rights to dimension members. Otherwise, dimensions have no security and users can access members without restriction. See Assigning Access to Dimension Members. Data Storage Select a data storage option. The default is Never Share. • Store: Stores data values of members. • Dynamic Calc and Store: Calculates data values of members, and stores values. • Dynamic Calc: Calculates data values of members, and disregards the values. • Never Share: Prohibits members in the same dimension from sharing data values. • Label Only: Has no data associated with the member. • Shared: Allows members in the same dimension to share data values. See Storage Options. Chapter 11 Editing Dimension Properties in the Simplified Dimension Editor 11-16
- 233. Table 11-6 (Cont.) Dimension Properties Property Value Display Option Set application default display options for the Member Selection dialog box. Select Member Name or Alias to display members or aliases. Member Name:Alias displays members on the left and aliases on the right. Alias:Member Name displays aliases on the left and members on the right. Hierarchy Type Available for dimensions bound to an aggregate storage cube. Aggregate storage dimensions are automatically enabled to support multiple hierarchies. The first hierarchy in a multiple hierarchy dimension must be Stored. For members with a Stored hierarchy type, the only valid cube aggregation options are Addition or Ignore. In a stored hierarchy, the first member must be set to Addition. For members with a Dynamic hierarchy type, all cube aggregation options are valid. Stored hierarchy members that are not children of Label Only members must have Addition set as the consolidation operator. Children of Label Only members can be set to Ignore. Custom Attributes Click to Create or Synchronize custom attributes for a dimension. Editing Member Properties in the Simplified Dimension Editor Related Topics • Accessing Edit Member Properties • Adding Members in the Simplified Dimension Editor • Editing Members in the Simplified Dimension Editor • Deleting Members in the Simplified Dimension Editor • Adding Shared Members in the Simplified Dimension Editor • Assigning Access to Dimension Members Accessing Edit Member Properties To access the Edit Member Properties tab in the Simplified dimension editor: 1. From the Home page, click Application, and then click Overview. 2. Click Dimensions, and then click the name of the dimension for which you want to view member properties. 3. Click Edit Member Properties. 4. To edit member properties in the Simplified dimension editor grid, click within a grid cell to edit text or to view a drop-down menu from which you can choose member properties. You can also drag and drop member property values over to rows and columns to fill in properties that are the same. See the Member Properties table below for property options and descriptions. See Working with the Simplified Dimension Editor Grid Chapter 11 Editing Member Properties in the Simplified Dimension Editor 11-17
- 234. Note: Each column in the Simplified dimension editor grid represents a member property. The list of properties (columns) that initially displays on the grid can be different based on which dimension type you're editing. You can customize the layout of columns by hiding, unhiding, or resizing columns. You can also display the complete set of properties (all columns) by clearing the Default mode option. To customize the column layout in the Simplified dimension editor grid, see Customizing the Column Layout. Members must conform to guidelines listed in Naming Restrictions. Shared members must be consistent with Adding Shared Members in the Simplified Dimension Editor. Table 11-7 Member Properties Property Value Member Name A name that is unique across all dimension members Parent Member If the member has a parent in the hierarchy, the parent name. Description Optional: A description of the member (you can use the same description for multiple members) Note: Editing the description of a seeded member is not allowed. Descriptions for all other members added by users can be edited. Alias Table Optional: The alias table which stores the alias name. Enter an alternate name for the member in Alias. See Administering Alias Tables. For Account members only: Account Type Select Expense, Revenue, Asset, Liability, Equity, or Saved Assumption. For descriptions, see Account Types. For Account members only: Variance Reporting If the account type is Saved Assumption, select Expense or Non-Expense. Designate the saved assumption as a revenue, asset, liability, or equity account. For Account members only: Time Balance Select Flow, First, Balance, Average, Fill, Weighted Average - Actual_Actual, or Weighted Average - Actual_365. For descriptions, see Time Balance Property. For Account members only: Skip If the account type is Asset, Equity, or Liability, select None, Missing, Zeros, or Missing and Zeros. For descriptions, see Setting Account Calculations for Zeros and Missing Values. Chapter 11 Editing Member Properties in the Simplified Dimension Editor 11-18
- 235. Table 11-7 (Cont.) Member Properties Property Value For Account members only: Exchange Rate Type Select Average, Ending, or Historical. For descriptions, see Data Type and Exchange Rate Type. Data Type Select Currency, Non-currency, Percentage, Date, or Text. For descriptions, see Data Type and Exchange Rate Type. For Account members only: Distribution Sets the weekly distribution. Available for leaf Account members if the option was selected when creating the application and the base time period is 12 months. Hierarchy Type Available for dimensions bound to an aggregate storage cube. Aggregate storage dimensions are automatically enabled to support multiple hierarchies. The first hierarchy in a multiple hierarchy dimension must be stored. For members with a stored hierarchy type, the only valid cube aggregation options are Addition or Ignore. In a stored hierarchy, the first member must be set to Addition. For members with a dynamic hierarchy type, all cube aggregation options are valid. Stored hierarchy members that are not children of Label Only members must have Addition set as the consolidation operator. Children of Label Only members can be set to Ignore. Data Storage The data storage property. Never Share is the default for new custom dimension members (except root members). Two Pass Calculation Recalculate values of members based on values of parent members or other members. Available for Account and Entity members with Dynamic Calc or Dynamic Calc and Store properties. For Entity members only: Base Currency For Standard multiple currency applications only, select the Entity member’s base currency. Chapter 11 Editing Member Properties in the Simplified Dimension Editor 11-19
- 236. Table 11-7 (Cont.) Member Properties Property Value Cube Consol op Select an aggregation option for each cube: • Not used for Cube (member will be invalid for cube) • Addition • Subtraction • Multiplication • Division • Percent • Ignore • Never (member doesn't aggregate, regardless of hierarchy) You can select a source cube only if multiple cubes are valid for the member. Only cubes and aggregation options for which the member’s parent is valid are available. If the parent isn't valid for a cube or aggregation option, neither is the child member. Deselecting a cube for an account or entity parent member deselects it for all descendents of that parent. For members with a stored hierarchy type, the only valid aggregation options are Addition or Ignore. You can set usage by cube for members of custom dimensions and the Period dimension, similar to the Account and Entity dimensions. CAUTION! Deselecting a cube for dimension members after data is entered into an application may result in loss of data when an application is refreshed. For account members, data is lost if the deselected cube is the source cube. For Entity members only: Base Currency For Standard multiple currency applications only, select the base currency for the Entity member. For Account members only: Source Cube Select the source cube for the member. A shared member is a pointer to the base member and isn't stored; this is disabled for shared members. The source cube of a shared Account member matches the source cube of the base member, even though Source Plan field is unavailable because it doesn't apply to shared members. Smart Lists Optional: Select a Smart List to associate with the member. Solve Order Specifies the order in which formulas are evaluated. Enter a whole number between 0 and 100000. The formulas for members that have a specified solve order are calculated in order from the lowest solve order to the highest. The default is 0. Solve Order is available for aggregate storage cubes and also for block storage cubes that are enabled for Hybrid. Solve Order for block storage cubes is only editable using the Simplified dimension editor. Enable for Dynamic Children Enables users to create children for this member by entering a member name in the runtime prompt for a business rule that has been configured with a dynamic parent member. Number of Possible Dynamic Children This option is available if Enable for Dynamic Children is selected. Enter the maximum number of dynamically-added members that users can create. The default is 10. Chapter 11 Editing Member Properties in the Simplified Dimension Editor 11-20
- 237. Table 11-7 (Cont.) Member Properties Property Value Access Granted to Member Creator This option is available if Enable for Dynamic Children is selected. Determines the access that member creators have to dynamic members that they create with a runtime prompt: • Inherit: The member creator will inherit the closest parent's access to the newly-created member. • None: The member creator will not be assigned any access to the newly-created member. (A Service Administrator can later assign the member creator access to the members.) • Read: The member creator will be assigned Read access to the newly-created member. • Write: The member creator will be assigned Write access to the newly-created member. If a Service Administrator changes these settings, they affect only future dynamic members; they don't retroactively affect dynamic members. Adding Members in the Simplified Dimension Editor Members must conform to guidelines listed in Naming Restrictions. To add shared members, see Adding Shared Members in the Simplified Dimension Editor. To add members in the Simplified dimension editor: 1. From the Home page, click Application, and then click Overview. 2. Click the Dimensions tab. 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. 5. Click the Edit Member Properties tab. Tip: To choose a different dimension, click the down arrow next to the dimension name at the top of the page. 6. Add members: • To add a child member, select the parent level member, click Actions, and then click Add Child. Note: Child members inherit the dimension properties of the parent member. Chapter 11 Editing Member Properties in the Simplified Dimension Editor 11-21
- 238. • To add a sibling member, select a member, click Actions, and then click Add Sibling. • To add years to the calendar, select the Years dimension, click Actions, and then click Add Years. Enter the number of years to add, click Apply, and then confirm whether to add the years to the end of the calendar. Click Yes to add years after the End year. Click No to add years before the Start year. • To add an All Years parent member that includes all members of the Years dimension, select the Years dimension, click Actions, and then click Add "All Years". The All Years parent member enables users to view the accumulated data across multiple years, for example, a project's total cost up to its end date. The All Years member doesn't include the No Year member, if one is defined for the application. 7. To set or change member properties, click a cell in the Edit Member Properties grid and make updates. See Editing Members in the Simplified Dimension 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 Refresh Database. 12. After creating a dimension member, you typically complete these tasks: • Assign access. Click Actions, and then click Assign Permissions. • Assign custom attributes. See Editing Dimension Properties in the Simplified Dimension Editor. Editing Members in the Simplified Dimension Editor You can edit members directly in the Simplified dimension editor grid. To edit members: 1. From the Home page, click Application, and then click Overview. 2. Click the Dimensions tab. 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 edit. 5. Click the Edit Member Properties tab. Tip: To choose a different dimension, click the down arrow next to the dimension name at the top of the page. 6. Take an action: • To add members, see Adding Members in the Simplified Dimension Editor Chapter 11 Editing Member Properties in the Simplified Dimension Editor 11-22
- 239. • To navigate the dimension editor grid and to focus your editing on certain members, rows, or columns, see Working with the Simplified Dimension Editor Grid. • To modify member properties, click within a cell on the dimension editor grid and select an option from the drop-down list. For example, to edit the Account Type for an Account dimension member, click within a cell in the Account Type column. Click the down arrow that appears within the cell, and then select an Account Type option. For descriptions of member properties, see Editing Member Properties in the Simplified Dimension Editor. Note: To view all property columns in the grid, right-click any heading on the grid and scroll down until you see the Default mode check box. Clear the Default mode check box to view all the property columns in the grid. • 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 Refresh Database. Deleting Members in the Simplified Dimension Editor Each 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 when refreshing an application. Deleting entity members deletes all approval units (including data) associated with them. Before deleting members, understand where in the application they are used (in which forms, 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 from dimension. For example, if the entity member is used in a form, you must delete it from the form before deleting it from dimensions. When deleting a large subtree of entities, you can improve performance if you first exclude approval units for the subtree (by excluding the root member) for all scenarios and versions. See Approvals Process. To delete members: 1. From the Home page, click Application, and then click Overview. 2. Click Dimensions. 3. Click the down arrow next to Cube to filter the list of dimensions by cube. 4. Click the name of the dimension that contains the member you want to delete. 5. Click Edit Member Properties. Chapter 11 Editing Member Properties in the Simplified Dimension Editor 11-23
- 240. Tip: To choose a different dimension, click the down arrow next to the dimension name at the top of the page. 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. 9. Update and validate business rules and reports. Adding Shared Members in the Simplified Dimension Editor Sharing members allow alternate rollup structures within an application. A base member must exist before you can create a shared member. You can create multiple shared members for the base member. A base member must display before its shared members in position from top to bottom. Shared members are available for Entity, Account, and user-defined custom dimensions. Shared member values can be ignored to avoid double-counting values when you roll up the outline. Shared members share some property definitions with base members, such as member name, alias name, base currency, and cubes for which members are valid. Shared members must have unique parent members and different rollup aggregation settings. Custom attributes, custom attribute values, and member formulas are not allowed for shared members. Renaming base members renames all shared members. Note: Shared members must have the same names as their base member. Also, base and shared member names are case-sensitive. Shared members can't be moved to another parent member. You must delete shared members and recreate them under different parent members. The base member need not be level zero. You can enter data in shared members, and values are stored with base members. To add shared members in the Simplified dimension editor: 1. View Edit Member Properties. See Accessing the Simplified Dimension Editor. 2. Add shared members: Chapter 11 Editing Member Properties in the Simplified Dimension Editor 11-24
- 241. 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. Assigning Access to Dimension Members Before you can assign access to members of user-defined custom dimensions, you must select the Apply Security check box on the dimension’s Edit Dimension Properties page. See Editing Dimension Properties in the Simplified Dimension Editor. To assign access to dimension members: 1. View Edit Member Properties. See Accessing the Simplified Dimension Editor. 2. Select the member, and then click . 3. Click Permissions. 4. Add, edit, or remove permissions. • Adding, Editing, and Removing Access to Members • About Effective Access Permissions to Shared Members Adding, Editing, and Removing Access to Members You can specify which users and groups can access the selected member. To assign, edit, and remove access permissions to members: 1. View Edit Member Properties. See Accessing the Simplified Dimension Editor. 2. Select the member, and then click . 3. Click Permissions. 4. Click Add User/Group. 5. To add access: a. Click to select the users and groups to access the selected member. Click Users to display all user names; click Groups to display all groups. b. Optional: Select a relationship. For example, select Children to assign access to the children of the selected member. 6. To modify access: a. Select the access type for the displayed users or groups. Click Users to display all user names; click Groups to display all groups. Chapter 11 Editing Member Properties in the Simplified Dimension Editor 11-25
- 242. b. Optional: Select a relationship. For example, select Children to assign access to children of the selected member. 7. To remove access, click . 8. Click OK. 9. Click Close. About Effective Access Permissions to Shared Members You can't assign access directly to a shared member. A shared member inherits access permissions from its base member, parent, or ancestor. The application checks access permissions at each level, first by user, then by group, based on the member’s access permissions inheritance relationship. If multiple access permissions exist, the least restrictive access permission is applied (for example, Write access takes precedence over Read access). Sample Parent and Child Entity Members Table 11-8 Example of Inherited Access to Shared Members Case Access Permission Effective Access for Base and Shared Member CA Explanation Case 1 CA (base) = None iDescendants (West) = Read Read CA inherits Read access from its West parent because Read is less restrictive than None. Case 2 iDescendants (United States) = None iDescendants (West) = Read iDescendants (Sales Region 1) = Write Write CA inherits Write access from its Sales Region 1 parent because Write is less restrictive than Read or None. Case 3 iDescendants (United States) = Write iDescendants (West) = None iDescendants (Sales Region 1) = Read Write CA inherits Write access from its United States parent because Write is less restrictive than Read or None. Working with Attributes in the Simplified Dimension Editor Attributes describe characteristics of data, such as the size and color of products. You can use attributes to group and analyze members of dimensions based on their Chapter 11 Working with Attributes in the Simplified Dimension Editor 11-26
- 243. characteristics. For example, you can analyze product profitability based on size or packaging, and you can make more effective conclusions by incorporating market attributes, such as the population size of each market region, into your analysis. You can assign attributes to sparse dimensions only. You can't assign attributes to label-only members. Attribute dimensions don't have aggregation properties because parents are dynamically calculated. The Account dimension is usually defined as dense, so you can't assign attributes to it unless it's changed to sparse for all cubes. If you change a dimension from sparse to dense, all attributes and attribute values for that dimension are automatically deleted. Attributes can have data types of text, date, Boolean, and numeric, as described in Understanding Attribute Data Types. Attribute names must conform to guidelines listed in Naming Restrictions. To create or edit attributes in the Simplified dimension editor: 1. From the Home page, click Application, click Overview, and then click Dimensions. 2. Select a sparse dimension for the attribute. Note: Only sparse dimensions can contain attributes. 3. Click the Edit Dimension Properties tab. 4. Select options: • To create an attribute, next to Custom Attributes, click Create. Type an attribute name, and select a data type: Text, Date, Boolean, or Numeric. Note: – You can't modify the type after the attribute is created. – Before working with date attributes, you must select the Attribute Dimension Date Format in Application Settings and save it. See Understanding Attribute Data Types. • To modify attributes, under Custom Attributes, click next to the attribute you want to modify, select Edit, and then update the attribute name. • To set aliases for attributes, select an attribute and an attribute value, click . Select an alias table, type an alias name, and click Save. 5. Click Close. When you click Close, the hierarchy is validated and an error displays if issues are detected. For example, date attribute values must be entered in the correct format, and numeric and date attribute dimensions must have at least one attribute value defined. Chapter 11 Working with Attributes in the Simplified Dimension Editor 11-27
- 244. 6. Update and validate business rules and reports. Related topics: • Deleting Attributes in the Simplified Dimension Editor • Working with UDAs in the Simplified Dimension Editor • Working with Attribute Values in the Simplified Dimension Editor Note: Instead of explicitly filtering by an attribute (like Red, for instance), you can create a user variable for the attribute dimension, and then use the user variable as the filter. Then you can enable the user variable as a dynamic user variable which would allow users to change the value of the filter at runtime. This is a useful technique that allows for dynamic filtering. See Managing User Variables. Deleting Attributes in the Simplified Dimension Editor When you delete an attribute, all attribute values associated with the attribute are also deleted. Attribute values are removed from members to which they had been assigned, and the attribute is removed from dimensions to which it was assigned. To delete attributes in the Simplified dimension editor: 1. From the Home page, click Application, click Overview, and then click Dimensions. 2. Click the name of the dimension with the attribute you want to delete, and then click the Edit Dimension Properties tab. 3. Under Custom Attributes, click next to the attribute you want to edit, and then select Delete. 4. Click Yes. 5. Update and validate business rules and reports. Working with UDAs in the Simplified Dimension Editor You can use user-defined attributes (UDAs), descriptive words or phrases, within calc scripts, member formulas, reports, and forms. UDAs return lists of members associated with the UDA. For example: • For a Product dimension with several product members, you can create a UDA called New Products and assign this UDA to the new products in the Product dimension hierarchy. Then you can base certain calculations on the designation New Products. • For the budget review process, rather than creating a data validation rule for each owner in a product line (some product lines can have hundreds of owners), you can create a UDA containing the user names that apply to members using the approval unit hierarchy. Then in the data validation rule, you can enter a lookup function which will return the user names stored in the UDA for the current Chapter 11 Working with Attributes in the Simplified Dimension Editor 11-28
- 245. member. For example, create a UDA for each user in the promotional path and assign a prefix to the UDA name (for example, ProdMgr:Kim). • When designing forms, you can use a UDA to select members for forms based on a common attribute. When you create forms with UDAs, any members that are assigned to the UDA are dynamically added to the form. For example, if you create a UDA called New Products and assign this UDA to the new products in the Product dimension hierarchy, the form will automatically display the new products at runtime. When selected in the form designer, a UDA is preceded by UDA; for example, UDA(New Products). • You can use the HSP_UDF UDA to prevent a formula from being overwritten when the application is refreshed. You must log on to each database associated with the business process and create the member formula with a UDA. The syntax for this UDA is: (UDAs: HSP_UDF). • If you use the @XREF function to look up a data value in another database to calculate a value from the current database, you can add the HSP_NOLINK UDA to members to prevent the @XREF function from being created on all cubes that are not the source cube selected for that member. UDAs are specific to dimensions. For example, creating a UDA for an Account member makes it available for non-shared Account members. Deleting it removes it for all Account members. To make UDAs available for multiple dimensions, create the same UDA for multiple dimensions. For example, create a UDA named New for Account and Entity dimensions to make the UDA named New available for Account and Entity members. To work with UDAs in the Simplified dimension editor: 1. From the Home page, click Application, click Overview, and then click Dimensions. 2. Click on the name of the dimension for whose members to associate the UDA. 3. Select the Edit Member Properties tab. 4. On the dimension grid, right-click any column heading, and then clear the Default Mode option to make the UDA column visible. 5. Locate the member to add the UDA, and then scroll to the UDA column. 6. Click in the UDA cell to display the UDA management dialog. 7. Select a task: • To create a UDA, click , enter a name, and then click Save. Note: Use no more than 60 characters when naming UDAs. If creating a UDA for approvals, assign a prefix to the beginning of the name (for example, ProdMgr:Name). A prefix indicates that the UDA contains a user name and enables the data validation rule to look up the user. Use the same prefix for all approvals UDAs. Chapter 11 Working with Attributes in the Simplified Dimension Editor 11-29
- 246. • To modify a UDA, select the UDA, click , change the name, and then click Save. • To delete a UDA, select the UDA, click , and then confirm deletion. Note: Deleting the UDA removes it for the whole dimension. If you delete UDAs, you must update all member formulas, calc scripts, and reports that reference them. • To clear UDA selections, click . 8. To add or remove UDAs for the member, use the arrows to move UDAs to and from the Selected UDA panel. 9. Click OK. Working with Attribute Values in the Simplified Dimension Editor Attribute values provide users with another way to select dimension members when using forms. Data values for attributes are dynamically calculated but not stored. You can define attribute values for sparse dimensions, which are typically the Entity and user-defined custom dimensions. After you define an attribute value for a dimension, you can assign it to members of that dimension. Creating Attribute Values in the Simplified Dimension Editor 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 an attribute dimension. 5. In Edit Member Properties, add members: • To add a child member, select the parent level member, click Actions, and then click Add Child. Note: Child members inherit the dimension properties of the parent member. Chapter 11 Working with Attributes in the Simplified Dimension Editor 11-30
- 247. • To add a sibling member, select a member, click Actions, and then click Add Sibling. 6. To set or change member properties, click a cell in the Edit Member Properties grid and make updates. See Editing Member Properties in the Simplified Dimension Editor. 7. To save your changes, click Save. Assigning Attribute Values to Base Dimensions When an attribute dimension is associated with a base dimension, it displays in the Simplified Dimension Editor in the same way as a regular dimension. To view attribute dimensions in the listing, select All in the Cube drop-down list on the main dimension page. Then you can select the attribute dimension to add values to the grid. To assign attribute values to base dimensions: 1. Open the Edit Member Properties page for the base dimension and find the column with the name of the attribute dimension. 2. Click within the grid for a specific member to display a drop-down list with attribute values, and then select an attribute value from the list. 3. Click Save on the Edit Member Properties page to assign the value to the base member. Setting Up Scenarios and Specifying Versions Related Topics • Setting Up Scenarios • Specifying Versions Setting Up Scenarios Each scenario/version combination contains data for accounts and other dimensions of each entity. After users enter data for an entity for a scenario and version, they can submit or promote the data for the entity to other users for review and approval. • About Scenarios • Creating, Editing, and Deleting Scenarios • Copying Scenarios About Scenarios Use scenarios to: • Apply different planning methods • Create forecasts • Enter data into scenarios • Associate scenarios with different time periods or exchange rates • Assign user access rights by scenario • Report on scenarios Chapter 11 Setting Up Scenarios and Specifying Versions 11-31
- 248. • Compare and analyze scenarios Time Periods Assign each scenario a range of years and time periods, and specify the Beginning Balance time period. When users access forms, they can enter into that scenario only years and periods within the range. Years and periods outside of the range display as read-only. You can modify the time range. Exchange Rate Table If a Standard multicurrency application converts currencies, assign an exchange rate table to the scenario. By assigning different exchange rate tables to scenarios, you can model the effects of currency rate assumptions. Access Permissions Specify access permissions to Scenario dimension members for groups or users to determine who can view or modify data. A user or group can have only one of these access permissions: Read, Write, or None. Access permissions for a user can be combined based on groups to which the user belongs. Creating, Editing, and Deleting Scenarios To create, edit, or delete scenarios: 1. From the Home page, click Application, and then click Overview. 2. Click Dimensions, click the Scenario dimension, and then click the Edit Member Properties tab. 3. Choose an action: • To create a scenario, click , and then go to step 4. • To delete a scenario, select the scenario to delete, then click , and then confirm the deletion. Note: When you delete scenarios, all approval units that use the scenario (including data) are deleted. You can't delete scenarios used in approval units that are started, or assigned to an axis on a form. You must first remove references to scenarios from forms and assign different scenarios. • To edit a scenario, click within the grid cells in the Simplified dimension editor grid to edit text or to view a drop-down menu from which you can choose member properties. Go to step 4. Chapter 11 Setting Up Scenarios and Specifying Versions 11-32
- 249. Note: Each column in the Simplified dimension editor grid represents a member property. The columns that initially display on the grid will differ based on which dimension type you're editing. You can customize the layout of columns in the Simplified dimension editor grid by hiding, unhiding, or resizing columns. You can also display the complete set of properties (all columns) by clearing the Default mode option. To clear the Default mode option, on the dimension grid, right-click any column heading, scroll down until you see the Default mode option, and then clear it. See Working with the Simplified Dimension Editor Grid. 4. In the Member Name column, enter a name for the scenario. 5. In the Start Yr., End Yr., Start Period, and End Period columns, define the time periods to associate with the scenario. 6. You can also perform these optional steps: • In the Description column, enter a description for the scenario. • To update the alias, select one of the Alias Table columns (choose default or a language) to associate with the scenario, and enter an alias name. • In the Beg.Bal. as Time Period column, specify whether to include the BegBalance time period in this scenario for currency conversion. • In the Enabled for Process Management column, specify whether to include this scenario in approvals. • In the Exchange Rate Table, select an exchange rate table to associate with the scenario. Note: If an application uses multiple currencies, associate a scenario with an exchange rate table to enable currency conversions. 7. Click Save. Copying Scenarios Only scenario properties are copied. Data values and access rights associated with the original scenario are not copied to the new scenario. To copy scenarios: 1. From the Home page, click Application, and then click Overview. 2. Click Dimensions, click the Scenario dimension, and then click the Edit Member Properties tab. 3. In the Simplified dimension editor grid, select the scenario to copy. 4. Click . Chapter 11 Setting Up Scenarios and Specifying Versions 11-33
- 250. The duplicate scenario is added to the Simplified dimension editor grid and _copy is appended after the member name. 5. In the Member Name column, enter a new name for the duplicate scenario. 6. In the Start Yr., End Yr., Start Period, and End Period columns, define the time periods to associate with the scenario. 7. You can also perform these optional steps: • In the Description column, enter a description for the scenario. • To update the alias, select one of the Alias Table columns (choose default or a language) to associate with the scenario, and enter an alias name. • In the Beg.Bal. as Time Period column, specify whether to include the BegBalance time period in this scenario for currency conversion. • In the Enabled for Process Management column, specify whether to include this scenario in approvals. • In the Exchange Rate Table, select an exchange rate table to associate with the scenario. Note: If an application uses multiple currencies, associate a scenario with an exchange rate table to enable currency conversions. 8. Click Save. Specifying Versions Use versions to group data used by an application. • About Versions • Target and Bottom Up Versions • Creating, Editing, and Deleting Versions • Viewing Version Types About Versions Use the Scenario and Version dimensions to create plans to be reviewed and approved. Each scenario/version combination contains data for accounts and other dimensions of each entity. After users enter data for an entity for a scenario and version, they can submit or promote the data for the entity to other users for review and approval. Use versions to: • Allow multiple iterations of a plan • Model possible outcomes based on different assumptions • Manage dissemination of plan data • Facilitate target settings Chapter 11 Setting Up Scenarios and Specifying Versions 11-34
- 251. Target and Bottom Up Versions You can create target and bottom up versions. With bottom up versions, you enter data into bottom level members; parent level members are display-only and don't permit data entry. Parent member values are aggregated from bottom level members. For target versions, you can enter data for members at any level in the hierarchy. You can use business rules to distribute values from parent members to their descendants. Use target versions to set high-level targets for your plan. Users working with bottom up versions can reference these targets when they enter plan data. Target versions use top-down budgeting. Manage Approvals Tasks are not allowed, and children of target members must be blank (for example, #MISSING) to enable data input at the top level. Target members must be set to Store (Dynamic Calc overrides data input with sum of children). Creating, Editing, and Deleting Versions To create, edit, or delete versions: 1. From the Home page, click Application, and then click Overview. 2. Click Dimensions, click the Version dimension, and then click the Edit Member Properties tab. 3. Choose an action: • To create a version, click , and then go to step 4. • To delete a version, select the version to delete, then click , and then confirm the deletion. Note: You can't delete versions that are used in approval units that are started or are assigned to axes on forms. You must remove references to versions from forms and assign another version to axes. At least one version must remain in the application. • To edit a version, click within the grid cells in the Simplified dimension editor grid to change the version name and access rights. Go to step 4. Chapter 11 Setting Up Scenarios and Specifying Versions 11-35
- 252. Note: Each column in the Simplified dimension editor grid represents a member property. The columns that initially display on the grid will differ based on which dimension type you're editing. You can customize the layout of columns in the Simplified dimension editor grid by hiding, unhiding, or resizing columns. You can also display the complete set of properties (all columns) by clearing the Default mode option. To clear the Default mode option, on the dimension grid, right-click any column heading, scroll down until you see the Default mode option, and then clear it. See Working with the Simplified Dimension Editor Grid. 4. In the Member Name column, enter a name for the version. 5. In the Type column, select the type of version to display for the application: • Standard Target: Values are entered from the parent level down • Standard Bottom Up: Values are entered at the lowest member level and aggregated upward 6. You can also perform these optional steps: • In the Description column, enter a description for the scenario. • To update the alias, select one of the Alias Table columns (choose default or a language) to associate with the version, and enter an alias name. • In the Beg.Bal. as Time Period column, specify whether to include the BegBalance time period in this scenario for currency conversion. • In the Enabled for Process Management column, specify whether to include this version in approvals. Note: This option isn't available for target versions. 7. Click Save. 8. Update and validate business rules and reports. Viewing Version Types To view version types: 1. From the Home page, click Application, and then click Overview. 2. Click Dimensions, click the Version dimension, and then click the Edit Member Properties tab. 3. In the Simplified dimension editor grid, the Type column displays these version types: • Standard Target: Values are entered from the parent level down. Chapter 11 Setting Up Scenarios and Specifying Versions 11-36
- 253. • Standard Bottom Up: Values are entered at the lowest member level and aggregated up. Chapter 11 Setting Up Scenarios and Specifying Versions 11-37
- 254. 12 Administering Tasks with Task Manager Task Manager provides centralized monitoring of all tasks and provides a visible, automated, repeatable system of record for running a business process. Related Topics • Setting Up Task Manager • Managing Task Types • Managing Task Templates • Managing Tasks • Managing Schedules • Managing Task Manager Integrations • Managing Alert Types for Task Manager • Using Task Manager Reports Setting Up Task Manager Related Topics • Task Manager Terms • Task Manager Overview • Sample Task Flows • Managing Task Manager Views, Lists, and Filters • Managing Task Manager System Settings • Managing Task Manager Attributes Task Manager Terms Tasks A unit of action in the application, for example, data entry or data consolidation. Power users define the tasks that comprise a business process. Users can read task instructions, answer questions, submit, reassign, approve, and reject tasks, and can access tasks from email notifications or by logging on to the application. Integrations A definition of a service provided by an application. Task Types Identify and categorize commonly performed tasks; for example, Data Entry, or G/L Extract. The Task Type enables you to set default information, such as settings that need to be input 12-1
- 255. by the user, and questions or instructions that are shared by all tasks of that type. Task Types are often based on Integration Types. Execution Types End-users, System-Automated Task, Event Monitoring Task Templates Business processes that are repeatable. Administrators can create templates for different types of business processes, such as monthly or quarterly. Schedules Defines the chronologically ordered set of tasks that must be executed for a specific business process, and is the alignment of a template's generic business process days, to calendar dates. Dashboard This 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. Alerts Notifications from users on issues that they encounter during the process, such as hardware or software issues. Users create alerts identifying a problem and assign them to be resolved. Task Manager Overview Task Manager helps you define, execute, and report on the interdependent activities of a business process. It provides centralized monitoring of all tasks and provides a visible, automated, repeatable system of record for running a business process. Note: During application creation, you were presented with two task flow type options: Task List and EPM Task Manager. EPM Task Manager is the default option for new applications. For information about administering Task Lists, see Administering Task Lists. 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 Getting Started with Oracle Enterprise Performance Management Cloud for Administrators guide. Chapter 12 Setting Up Task Manager 12-2
- 256. 2. The administrator completes the required setup procedures: • Set up organizational units. See Managing Task Manager Organizational Units. • Set up global integration tokens. See Managing Global Integration Tokens. • Set up holiday rules. See Managing Holiday Rules for Tasks. • Set up attachment size and other system settings. See Setting Task Manager Governors. • Enable email notifications. See Setting Up Email for Notifications in Working with Planning. 3. The administrator reviews the tasks required for a business process and sets up Task Types to ensure consistency across tasks and to leverage predefined product integrations. See Managing Task Types. 4. Because many business processes are repeatable, the administrator saves a set of 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 process once and then use it for all months or quarters. Tasks are defined with task predecessors, Assignees, and Approvers. 5. To initiate a business process, administrators generate a schedule (a chronological set of tasks) by selecting a template and assigning calendar dates. The generic tasks in the template are applied to calendar dates. See Managing Schedules. 6. To begin a business process, the administrator changes the schedule status from Pending to Open. 7. The administrator can also modify and monitor the schedule as needed. 8. During the business process, users receive email notifications of assigned tasks and 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 different types of views. 10. When users complete tasks, the tasks are sent to approvers and can be viewed by other users. 11. Users can create alerts for issues, such as hardware or software issues, that they encounter. Alerts are forwarded to Assignees and Approvers for resolution. Watch this overview video to learn more. Overview Video Sample Task Flows Scenario 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. Chapter 12 Setting Up Task Manager 12-3
- 257. • 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 by assigned users. Scenario 3: Approver A user assigned as an Approver reviews a current task to determine whether it can be approved. • 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 the task to ensure completeness. • The Approver enters additional comments and approves the submission. • 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 the system runs the next task if it is ready. • The Approver can reject a task instead of approving it, and the task is reassigned to 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 reference document. • The user reviews the instructions and the reference document, processes the updates, enters a comment about the task, and submits it for approval. • The system automatically updates the task status and sends a notification to the assigned 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. Chapter 12 Setting Up Task Manager 12-4
- 258. • From the email, the user selects the link for the page where the required process is 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 Views, Lists, and Filters Related Topics: • Viewing Task Manager Lists • Working with List Views • Working with Filters Viewing Task Manager Lists The Task Manager list provides a central place to manage all your tasks. It displays a list of tasks and their status for a selected Year, Period and Schedule. If you are an Administrator, you can see all the available tasks in the system, and the user who is working on them. If you are a user other than an Administrator, you can see all active tasks for your role that need your attention. To view tasks: 1. On the Home page, click Tasks. 2. Click Tasks on the left navigation. 3. Select a Year, Period, and Schedule. 4. Optional: To search for a task, in the Search field, enter any text or numeric for which to search the task list. 5. Optional: To filter the list of tasks, click Add a Filter in the filter bar and specify filter criteria. Sample Task List Chapter 12 Setting Up Task Manager 12-5
- 259. Working with List Views List views present records for on screen viewing and provide drill-down capabilities into record details. To see more rows displayed, from the View Selector on the right hand side, select Compact view. Lists provide these reporting features: • Columns can be added to or removed from the view and re-ordered. • Filters can be applied to limit the records included in the list. Saving List Views To save a list view: 1. Adjust the view to see the data you would like by adjusting filters, columns or sorting on your List. 2. From Actions, click Save List. 3. In the Save List dialog, enter a Name (can enter a maximum of 80 characters) and optionally a description (can enter a maximum of 255 characters), and then click OK. To see all the saved lists, click the List drop down selector. Publishing List Views An Administrator or Power User can also select Publish to make a private list view available to other users. Click the Filters icon on the right side of the filter bar, select Manage Filters, and then click Publish. The saved view is duplicated and there is now a private and public version. The public version will show a check mark in the Public column. Setting Default View You can also use the Set Default action for a published saved view. The Administrator or Power User sets the view as the default so that the saved list view will not only be available to all users of that view type, but it will also be selected by default when a user opens that view type. Working with Filters You can use the filtering capability to access particular lists of tasks by clicking the Show Filter Bar icon next to the Search field and then setting the filters you want. You can also create/add a new filter, save, delete, and manage your filters. Adding Filters To add filter: 1. On the Home page, click Tasks. 2. Click Tasks on the left navigation. Chapter 12 Setting Up Task Manager 12-6
- 260. 3. In the Schedule Tasks window, click Add a Filter. 4. Select the filter condition from the POV filter bar drop-down for example, Alert. 5. Select the necessary operator and value; for example, Equals and Yes. Saving Filters After you have set your filter conditions that you want to save: 1. Select the icon on the right side of the filter bar, and click Save Filter. 2. Enter a Name (for example, "My_Filter") and Description (optional). Notice that under Filter Definition -> Filter Criteria, Alert equals Yes. This is the same value you selected when adding the filter. 3. Click OK. 4. Click on the icon and you will notice that the newly saved filter named My_Filter now displays. Note: • You can enable the filters you have created by clicking on each of the respective filters. • To clear and reset everything, select the Clear All Filters option. Managing Filters Select the Manage Filters option on the Filters menu to work on the filters that you have created. Chapter 12 Setting Up Task Manager 12-7
- 261. The Filters window provides these options: • Click to add a new filter. – Enter the filter Name and Description (optional). – Select the filter Type (Alert, Schedule, or Template). – To define filter conditions, select Create Condition or Create Condition Group. – Click OK. • To edit a filter, click . • To duplicate a filter, click . • To delete a filter, click . Click OK to confirm deletion. Chapter 12 Setting Up Task Manager 12-8
- 262. • To publish a filter, click . Publishing a filter allows other users to use the same filter. • To manage or reorder filter columns, click . Managing Task Manager System Settings Related Topics • Managing Global Integration Tokens • Managing Task Manager Organizational Units • Managing Holiday Rules for Tasks • Changing Configuration Settings Managing Global Integration Tokens The Global Integration Tokens feature enables creation of parameterized URLs. The URLs can be used for a variety of purposes. When creating the URL, the parameters are inserted into the URL. When the URL is clicked, the parameters are replaced with the appropriate values. 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 Chapter 12 Setting Up Task Manager 12-9
- 263. The URL becomes: … %222012%22%22Period%20Name%22&val6=%22Jan2012%22&col7=%22Logical%20Sche dules%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 a template in the Instructions section, the URL is clickable on the Instruction tab. • Schedule: After an administrator or power user adds a reference URL to a schedule in the Instructions section, the URL is clickable in Instructions. • Task Details: After an administrator or power user or task owner adds a reference URL 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 the Instructions section, the URL is clickable on the Instruction tab. • Task Actions: Viewers of Task Actions can click the reference URLs. Creating a Global Integration Token Use these guidelines for creating Global Integration Tokens: • The token name must be unique. • Tokens can't be modified. • Tokens shouldn't be deleted. If you try to delete a token, a warning will display: "Deleting a Global Integration Token will invalidate the URLs that are referencing it. Are you sure you want to continue?" To create a Global Integration token: 1. On the Home page, click Application, and then click Task Manager. 2. Click the System Settings tab on the left, and then select Global Integration Tokens. 3. Click New. 4. Enter: • Name: A unique token name • Type: Static or Task Attribute • Token Value: Chapter 12 Setting Up Task Manager 12-10
- 264. – If Task Attribute is selected as the Parameter Type, select the value that is passed when the URL is rendered. – If Static Attribute is selected as the Parameter Type, enter the value that is passed when the URL is rendered. 5. Click Save. Deleting a Token To delete a token: 1. On the Home page, click Application, and then click Task Manager. 2. Click the System Settings tab on the left, and then select Global Integration Tokens. 3. Select a token, and then click Delete. A warning message is displayed: "Deleting a Global Integration Token will invalidate the URLs that are referencing it. Are you sure you want to continue?" 4. Click Yes to confirm deletion. Managing Task Manager Organizational Units Organizational 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 with different sections of the hierarchy. Adding Organizational Units To add an organization: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Organizations tab on the left and then select Organizational Units. 3. Click Add Sibling. 4. On the Properties tab, enter: • Name: You can enter a maximum of 255 characters. 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. The Organizational Unit ID can't be changed after an organizational unit is set. You can enter a maximum of 255 characters. • Optional: Parent Organization: Enables Administrators to change the hierarchy. • Description: You can enter a maximum of 255 characters. • Timezone: Determines which time zone applies to the organizational unit. Selection of a time zone is optional. If a time zone is not selected, the task time zone will revert to the user’s time zone. • Holiday Rule: Determines which list of holidays applies to the organizational unit. Selection of a Holiday Rule is optional. Chapter 12 Setting Up Task Manager 12-11
- 265. • Work Days: Determines which days of the week are work days. 5. The Access tab enables Administrators to assign viewer and commentator access in a centralized location, rather than having to assign it to each task. To select a user: a. Click Add. b. In Select Viewers, enter the First Name and Last Name, or click Search Users, then select Users or Groups . c. In Search Results, select the users and click Add or Add All to move them to the Selected list. Importing Organizational Units To 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 Choose File to navigate to the CSV import file. Sample Organizational import format: Note: The following section shows the import format. This example requires a pre-existing parent organizational unit named "Americas", a holiday rule named "US", and a Viewer named "fm_user5". "OrganizationalUnitID","Name","ParentOrganization","Description","T imeZone","H olidayRule","Calendar","Workdays","Viewer1","Commentator1" "US2","US2","Americas","Import Organization US2 Example","ET (UTC-05:00)","US","",2-3-5,"fm_user5","" • For Import Type, select one: – Replace: Replaces the Organizational Unit detail with the Organizational Unit that is in the file that you are importing. It does not affect other units that are not specified in the import file. – Replace All: Imports a new set of Organizational Units that replaces the existing Units. This option is useful when you want to replace a unit in one system with an updated definition from another system. Organizational Units that are not specified in the import file are deleted. • For File Delimiter, select Comma, Tab, or Other. 4. Click Import. Chapter 12 Setting Up Task Manager 12-12
- 266. Selecting an Organizational Unit Administrators define organizational units in Organizations to help organize and schedule tasks. To select an organization: 1. On the Home page, click Application, and then click Task Manager. 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 the parent to select a child organization. Managing Holiday Rules for Tasks Holiday Rules are collections of holiday dates that Administrators use when scheduling tasks. After you create a holiday rule, you can apply the rule to an organizational unit and then apply the organizational unit to the schedule template. See Applying a Holiday Rule to an Organizational Unit and Applying a Holiday Rule to a Schedule Template. Creating Holiday Rules To create holiday rules: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Organizations tab on the left. 3. Click Holiday Rules. 4. Click New. 5. Enter: • Holiday Rule ID: You can enter a maximum of 255 characters. The Holiday Rule ID is mandatory and must be unique. • Name: You can enter a maximum of 50 characters. The Name does not need to be unique. • Year: The Year attribute behaves as a filter option. You don't need to select a value for this attribute. If you do, the table is filtered to display the dates associated with the selected year. 6. To name a holiday, in the Holiday section, click Import ( ) to import the list of holidays, or click New and enter the date and name of the holiday. Applying a Holiday Rule to an Organizational Unit After you create a holiday rule, you can apply it to an organizational unit, and then apply it to a schedule. To apply a holiday rule: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Organizations tab on the left. Chapter 12 Setting Up Task Manager 12-13
- 267. 3. Click Organizational Units. 4. Create or edit an organization. 5. On Properties, from the Holiday Rule drop-down, select a holiday rule. 6. Click Save. Applying a Holiday Rule to a Schedule Template After you create a holiday rule and apply it to an organizational unit, you can apply the organizational unit to a schedule template. To apply a holiday rule: 1. On the Home page, click Application. 2. Click Task Manager. 3. Click the Templates tab on the left. 4. Select a template, click the Actions icon to the right of the template, and then select Create Schedule. 5. For Schedule Parameters, specify the Schedule, Year, Period, and Day Zero Date. 6. Under Date Mapping, click Advanced Configuration. 7. For Organizational Unit, select Use Task Value or Set Value To. For Set Value To, click the Search icon to select an organizational unit. 8. Select the organizational unit that you created or edited that contains the holiday rule and click OK. 9. Click OK. The Schedule Parameters Date Mapping now shows the holiday. Importing Holiday Dates You can import dates into a holiday rule. To import holiday dates: 1. On the Home page, click Application and then click Task Manager. 2. Click the Organizations tab on the left. 3. Click Holiday Rules. 4. Create or select a holiday rule. 5. Above the Holiday section, click Import . 6. Click Choose File to navigate to the CSV import file. 7. For Import Type, select one: • Replace: Replaces the holiday dates with the holiday dates in the file that you are importing. Does not affect other units that are not specified in the import file. • Replace All: Imports a new set of holiday dates that replaces the existing holiday dates. Use this option to replace unit in one system with an updated Chapter 12 Setting Up Task Manager 12-14
- 268. definition from another system. Holiday dates that are not specified in the import file are deleted. 8. For Date Format, select a format from the drop-down list of allowed date formats. Date formats are not translated. By default, the date format is set to the locale date format of the exported file location. 9. For File Delimiter, select Comma, Tab, or Other. 10. Click Import. Editing Holiday Rules To edit holiday rules: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Organizations tab on the left and then select Holiday Rules. 3. Select a rule. 4. Edit the following fields: Note: The Holiday Rule ID is not editable. • Name: The name can be a maximum of 50 characters. It does not need to be unique. • Year: The Year attribute behaves as a filter option. You do not need to select a value for this attribute. If you do, the table is filtered to display the dates associated with the selected year. 5. Click Save. Duplicating Holiday Rules To duplicate holiday rules: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Organizations tab on the left. 3. Click Holiday Rules. 4. Select a rule and click Duplicate. 5. Edit the rule as needed. Deleting Holiday Rules You cannot delete a holiday rule associated with an organizational unit that is not logically deleted. A list of organizational units to which the holiday rule was assigned is displayed. To delete holiday rules: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Organizations tab, and then select Holiday Rules. 3. Select a rule, and then click Delete. Chapter 12 Setting Up Task Manager 12-15
- 269. Changing Configuration Settings Related Topics • Allowing Comment Deletions • Allowing Task Deletions • Enabling Email Notifications • Setting Task Manager Governors • Allowing Reassignment Request Approvals • Reopening Tasks • Specifying Task Display in Smart View • Displaying Upcoming Tasks in Worklist and Welcome Panel Allowing Comment Deletions A Service Administrator can decide to allow deletions of comments in tasks by using the Allow Comment Deletion configuration settings option. By default, this option is Off. To allow users to delete comments: 1. On the Home page, click Application, and then click Task Manager. 2. Click the System Settings tab on the left. 3. Select Allow Comment Deletion. 4. Select Turn On to enable deletions. Allowing Task Deletions Service 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: 1. On the Home page, click Application, and then click Task Manager. 2. Click the System Settings tab on the left. 3. Select Allow Task Deletion. 4. Select Turn On to enable deletions. Chapter 12 Setting Up Task Manager 12-16
- 270. Enabling Email Notifications Service Administrators can set up Email Notifications for Task Manager users. When you enable email notifications, batch notifications are generated. When the notification is 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 reminder notifications. Due Date reminder notifications are emailed to Assignees and Approvers in these conditions: • Responsibility for a Task Manager action changes - sent based on information in the 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 you specify To enable email notifications: 1. On the Home page, click Application, and then click Task Manager. 2. Click the System Settings tab on the left. 3. Select Email Notifications. 4. For Email Notifications, select Turn On to initiate the notification, or Turn Off to deactivate the notification. 5. Enter an email for the From Address. You can edit the address to supply a specific address, or to include a product acronym to alert the user where the notification is coming from. If the From Address field can be edited, enter the email. Otherwise, the default of no.reply@oraclecloud.com displays and cannot be edited. Email notifications also include the service name in the footer of the email. For example: "Note - This is an automated email notification generated from EPM Task Manager on efim.arcs". 6. Enter the Number of days before due date to send reminder. 7. Select the User Specified checkbox. When the administrator selects this checkbox, then the users can customize their personal email notification settings. If the administrator does not select this checkbox, user inherits the settings made by the administrator. 8. Use Email Start Time and Email End Time to specify the time period in a day when scheduled emails will be sent. This setting will take effect in each user's individual time Chapter 12 Setting Up Task Manager 12-17
- 271. zone. 9. Specify settings for Notification Type. The following types of notifications can be defined: • Late Notification • Status Change Notification • Due Date Reminder Notification Select an option for Notify Me: • Immediately: For example for Status Change Notification, expand Task Manager, and then expand again to choose You are the alert approver and alert status changes to open with approver. Then select Immediately to be notified as soon as an approver takes action. Note: If you set Notify Me to Immediately, the email notifications are sent immediately even when it is outside of the user's email start/end time. • Once a day • Every 2 hours • Every 3 hours Chapter 12 Setting Up Task Manager 12-18
- 272. • Every 4 hours • Every 6 hours • Mixed • Never: Select this option to deactivate a notification. Note that this option is only applicable for Status Change Notification and Due Date Reminder Notification. For Late Notification, only the following notification types get this option: – You are the task owner and task assignee is late – You are the task owner and task approver is late Note: For each type of notification, expand each notification preferences and choose when to be notified: For example for Status Change Notification, expand Task Manager, then expand and select You are the task approver and task approver is late. Select Every 2 hours as a choice of notification. Note that you can override a setting at a lower level (for example, configure Notification Type to Every 2 hours, and override one of the Conditions to Once a Day). Then the parent setting(s) displays the word Mixed, to provide a visual indication that more than one preference setting has been assigned to child level settings. You can change the value from Mixed to a different preference setting; the child level settings are changed to the new setting. If an Administrator disables the Email Notifications in Services, then notifications are suspended. For more information, see Managing Notification Types and Settings. See also, Setting Up Email for Notifications in Working with Planning. Managing Notification Types and Settings Service Administrators can define the default settings of all Task Manager notifications for all users under Notification Types. Late Notification Options Table 12-1 Table for Late Notification Types Notification Valid Values You are the task approver and task approver is late • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day Chapter 12 Setting Up Task Manager 12-19
- 273. Table 12-1 (Cont.) Table for Late Notification Types Notification Valid Values You are the task assignee and task assignee is late • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the task owner and task assignee is late • Never • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the task owner and task approver is late • Never • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day Status Change Notification Options Table 12-2 Table for Status Change Notification Types Notification Valid Values You are the alert assignee and alert status changes to open with assignee • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the alert approver and alert status changes to open with approver • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the alert owner and alert status changes to open with owner • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day Chapter 12 Setting Up Task Manager 12-20
- 274. Table 12-2 (Cont.) Table for Status Change Notification Types Notification Valid Values You are the alert owner and alert status changes to open with assignee • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the alert owner and alert status changes to open with approver • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the alert owner and alert status changes to completed • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are an alert viewer and alert status changes to open with owner • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are an alert viewer and alert status changes to open with assignee • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are an alert viewer and alert status changes to open with approver • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day Chapter 12 Setting Up Task Manager 12-21
- 275. Table 12-2 (Cont.) Table for Status Change Notification Types Notification Valid Values You are an alert viewer and alert status changes to completed • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the schedule owner and schedule is created • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the schedule owner and schedule status changes to open • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the schedule owner and schedule status changes to closed • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the schedule owner and schedule status changes to locked • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the schedule viewer and schedule is created • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day Chapter 12 Setting Up Task Manager 12-22
- 276. Table 12-2 (Cont.) Table for Status Change Notification Types Notification Valid Values You are the schedule viewer and schedule status changes to open • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the schedule viewer and schedule status changes to closed • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the schedule viewer and schedule status changes to locked • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the task assignee and task status changes to open with assignee • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the task approver and task status changes to open with approver • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the backup assignee and the primary assignee is unavailable • Never • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the backup approver and the primary approver is unavailable • Never • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day Chapter 12 Setting Up Task Manager 12-23
- 277. Table 12-2 (Cont.) Table for Status Change Notification Types Notification Valid Values You are the task authorizer and schedule status changes to open • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the task owner and task status changes to open with assignee • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the task owner and task status changes to open with approver • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the task owner and task status changes to closed • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the task owner and task status changes to force closed • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the task owner and task status changes to aborted • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day Chapter 12 Setting Up Task Manager 12-24
- 278. Table 12-2 (Cont.) Table for Status Change Notification Types Notification Valid Values You are the task viewer and task status changes to open with assignee • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the task viewer and task status changes to open with approver • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the task viewer and task status changes to closed • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the task viewer and task status changes to force closed • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the task viewer and task status changes to aborted • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the journal submitter and the journal needs to be posted • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day Chapter 12 Setting Up Task Manager 12-25
- 279. Table 12-2 (Cont.) Table for Status Change Notification Types Notification Valid Values You are the journal approver and the journal needs approval • Never • Immediately • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day Due Date Reminder Notification Options Table 12-3 Table for Due Date Reminder Notification Types Notification Valid Values You are the task approver and task is "At Risk" • Never • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the task assignee and task is "At Risk" • Never • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the task owner and task is "At Risk" • Never • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the task assignee and assignee due date is within 1 days • Never • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day You are the task approver and approver due date is within 1 days • Never • Every 2 hours • Every 3 hours • Every 4 hours • Every 6 hours • Once a day Chapter 12 Setting Up Task Manager 12-26
- 280. Setting Task Manager Governors In Task Manager, you can set governors on various system settings and the system provides default settings which you can decrease or increase up to the maximum value. For example, you can specify the maximum number of rows to display in lists. • Maximum Number of Items displayed in a List: Determines the maximum number of rows displayed in a List view; for example, Schedule Tasks. • Maximum Approver Levels: Determine the number of levels that a task might be reviewed. • Select maximum file upload size (MB): Determines the maximum attachment file size that users can upload. This setting helps administrators adapt to work within limitations of the environment in which the application is installed. To set Task Manager governors: 1. On the Home page, click Application, and then click Task Manager. 2. Click the System Settings tab on the left. 3. On the Manage System Settings page, click Governors. 4. Specify a maximum value or leave the default setting: • Maximum Number of Items displayed in a List: The default is 10000. • Maximum Approver Levels: Select a value from 1 to 10. • Select maximum file upload size (MB): Select a value from 5 MB, with incremental values of 5 MB, up to 100 MB. 5. Click Save. Allowing Reassignment Request Approvals As an Administrator, you can specify which workflow users can directly perform and approve reassignment requests rather than submitting requests to an Administrator or Power User for approval. Users can then approve reassignment requests from their Worklist. Service Administrators should also see the reassignment requests if they are required to approve the requests in case the Task Owner is unavailable. To allow workflow users to perform reassignments: 1. On the Home page, click Application, and then click Task Manager. 2. Click the System Settings tab on the left. 3. Select Reassignment Requests. 4. For Allow reassignment request approval by, select one or more options: • Administrator • Power User • Users Chapter 12 Setting Up Task Manager 12-27
- 281. Reopening Tasks In 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. To allow reopening of tasks: 1. On the Home page, click Application, and then click Task Manager. 2. Click the System Settings tab on the left. 3. Select Reopen. 4. Set the conditions to allow reopening of a task that is Open with an Assignee or Approver. For Task is Open with Assignee or Approver: • Not Allowed: This is the default option and assignees or approvers cannot change the workflow of an open task after it has been submitted or approved. • Allowed for all approvers: Allows approvers who have approved a task to return the workflow to themselves. • Allowed for all assignees and approvers: Allows an assignee who has submitted a task or an approver who has approved a task to return the workflow to themselves. 5. Set the conditions to allow reopening closed tasks. For Task is Closed: • Not Allowed: This is the default option and users will not be able to reopen a closed task. • Allowed for final approver: Allows only the final approver to reopen and return the workflow to themselves. • Allowed for all approvers: Allows an approver to reopen and return the workflow to themselves. • Allowed for all assignees and approvers: Allows assignees and approvers of a task to reopen and return the workflow to themselves. Specifying Task Display in Smart View You can configure the display of Task Manager tasks when they are launched from Oracle Smart View for Office by selecting columns to display; for example, Task Attributes. To select columns to display in Smart View: 1. On the Home page, click Application, and then click Task Manager. 2. Click the System Settings tab. 3. Select Smart View. 4. Under Column Selection, from the Available list, select the columns to display, then click the Add arrow keys to move them to the Selected column, or Remove to remove them. You can select a maximum of 30 columns, and reorder the columns as needed. 5. Click Save to save your selection. Chapter 12 Setting Up Task Manager 12-28
- 282. Displaying Upcoming Tasks in Worklist and Welcome Panel As an administrator, you can decide whether to show only Current Tasks, or Current and Upcoming Tasks in the Workflow of the Worklist and Welcome Panel. If you enable Current and Upcoming Tasks, users can see items currently available to work on, and also items in the upcoming workflow. For example, users can see an upcoming task that is due for them to approve, but not immediately available, as the preparer has not yet finished the task. You also have the option to display the tasks with description (default) or by the Task ID/ Organizational Unit. By default, the system displays only Current Tasks. To set the display for tasks: 1. On the Home page, click Application, and then click Task Manager. 2. Click the System Settings tab on the left. 3. Select Worklist and Welcome Panel. 4. Select an option for Workflow: • Show Current Tasks Only • Show Current and Upcoming Tasks 5. Select an option for Optional Field: • Description (default) • Task ID • Organizational Unit Managing Task Manager Attributes Attributes are user-defined fields defined centrally by administrators and used in many places. 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 can define a custom Chapter 12 Setting Up Task Manager 12-29
- 283. attribute named Auto Submit with a value type of Yes or No. When you assign the Auto Submit attribute to an item, you can set it to Yes for tasks required by external users. If you select the List type, you can define a pick list of values. For example, you can define a List attribute named Sales Region, with North, South, East, and West as values. You can create, edit, and delete attributes. Note: The maximum number of Task Manager attributes that you can create or import is 10,000. Defining Task Manager Attributes To define a Task Manager attribute: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Attributes tab on the left. 3. Click New, then on the Properties tab specify the following properties: • Name: You can enter a maximum of 80 characters. Note: You can create an object using the same name that you used earlier and deleted. Any objects that were previously linked to the deleted object will be associated with the new object. • Description: You can enter a maximum of 255 characters. • Type: – Date – Date/Time – Integer: Allows a value between -2147483648 and 2147483647. For Total, specify the totaling method for the attribute: * None (default): No total is calculated. * Average: The average of the rows with data. Rows without data are not counted in the denominator * Count: The count of the rows with data. * Sum: Additive total. – List: Click List Values to enter a list of valid responses to the question. You can enter a maximum of 255 characters. – Multi-Line Text: Click Format and specify the Number of Lines, from 3 to 50 lines. Multi-Line Text determines how many lines of text are visible, Chapter 12 Setting Up Task Manager 12-30
- 284. without scrolling, on the Actions dialog boxes. The maximum length should be less than 4,000 characters. Select Include Attachments if you want to include an Attachments section on the Actions dialog box. – Number: Enter a value xxxxxxxxxxxxxxxxx.xxxxxxxxx (17 digits and 9 decimal places). Click Format and select number formatting options: * For Decimal Places, enter a value for the number of decimal places to display. * For Display As Percentage, select if you want a percentage to display. * Select the Thousands Separator option if you want numbers to display a thousands separator (for example, 1,000.00). * For Currency Symbol, select a currency symbol; for example, $ (United States of America Dollar). * For Negative Number, select how to display negative numbers; for example, (123). * For Scale, select a scale value for numbers; for example, 1000. – Text: Enter a maximum of 4000 characters. – True/False – User – Yes/No • Calculation: Select to add logical and mathematical functions for attributes in the Calculation tab. See Defining Calculation Attributes. Defining Calculation Attributes Calculation attributes enable you to add logical and mathematical functions to derive values for attributes. They can be embedded within other calculated attributes to produce complex functions. Calculated attributes are read-only. They can only be evaluated against Schedules. Schedules: You can add any Calculation and the calculation is evaluated, regardless of whether or not it was explicitly assigned to the task. Templates: You cannot add a custom attribute that has the Calculation option selected as 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 roles by setting the access to Do Not Display. For example, for calculated attribute XYZ, an administrator could set the access to Viewer: Do Not Display so that the XYZ attribute is not displayed for users with only the Viewer role. Any user role can add calculated attributes as columns in views and portlets. They can also be added as filterable attributes in the Filter Panel. To define a calculation attribute: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Attributes tab on the left. Chapter 12 Setting Up Task Manager 12-31
- 285. 3. Click New, and then on the Properties tab enter a Name for the attribute, and then select an attribute Type. 4. Select the Calculation option. 5. On the Calculation tab, select a Calculation Type. You can select from the following calculation types. The available types are determined 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 different attribute. Only available for List type attributes. • Conditional: A conditional calculation (If – Then – Else) • Scripted: A free-form scripted calculation. Only available for attributes of type Integer, 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 The Scripted Calculation type enables you to enter a free-form calculation equation. You can use Add Attribute and Add Function: • Add Attribute: Select an attribute and insert the attribute into the Calculation Definition box at the location of the cursor. If the cursor is in the middle of a word or attribute, the word/attribute will be replaced in the definition. The script format adds 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 Calculation Definition. 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') Chapter 12 Setting Up Task Manager 12-32
- 286. Numeric and Date Functions • Absolute Value: Returns the absolute value of a specified number. If a number is less than zero, the positive value of the number is returned. If the specified number 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 starting date. The date will always fall in the specified month offset. If the starting date has a day value beyond what is in the offset month, the last day of 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 the start date. A positive value for 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, month and day. DATE(<Year>, <Month>, <Day>) • Date Difference: Returns the difference in years, months, days, hours, minutes, or seconds between two dates. For DATE 1 and DATE 2, the values TODAY and NOW can be used, which denote the current date (with no time component) and date-time, respectively. DATE_DIFF(<Date1>, <Date2>, <Type>) 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) • If Then Else: Allows you to insert a conditional calculation into the scripted calculation. 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') • Length: Takes a text value as a parameter and returns an integer which is the number of characters in the text. If the value is empty/null, the calculation will return 0. Length ({<attribute>}) Chapter 12 Setting Up Task Manager 12-33
- 287. Example: LENGTH("Value") would return 5, and LENGTH({Name}) would return the number of characters in the name of the object. Use the calculation with SUBSTRING to extract the last four characters of a text value. SUBSTRING( {MyString}, LENGTH ({MyString}) - 4 • 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 any number of parameters. MAX <Value1>, <Value2>, <ValueN>) Example: MAX( {Scripted Substring Loc a}, {Scripted Substring Loc s}, {Scripted Substring Loc t} ) • Minimum: Returns the minimum value from a list of attributes. There can be any number of parameters. MIN (<Value1>, <Value2>, <ValueN>) Example: MIN( {Scripted Substring Loc a}, {Scripted Substring Loc s}, {Scripted Substring 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 attributes 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 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') • Text Location: Returns the index of the substring within the value, starting at 1 as the first position. INSTRING(<Value>, <Value To Search>) Example: INSTRING( UPPERCASE( {Name} ), 'TAX' ) • Uppercase: Returns the value in upper case. UPPERCASE(<Value>) Chapter 12 Setting Up Task Manager 12-34
- 288. 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 Attributes To 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 a separate line. For example: Blue Yellow Red Green The import option is always "Replace All". 2. On the Home page, click Application, and then click Task Manager. 3. Click the Attributes tab on the left. 4. Select an attribute of type List, and click Edit. 5. Click Import . 6. For File, click Choose File, find a TXT import file, and then select a File Delimiter. 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, click Export to Excel . Editing Attributes You can edit the name of a custom Task Manager attribute. If the attribute type is a List, you can also add, rename, or delete list values. To edit Task Manager attributes: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Attributes tab on the left. Chapter 12 Setting Up Task Manager 12-35
- 289. 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 Attributes You can duplicate attributes. To duplicate attributes: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Attributes tab on the left. 3. Select an attribute to duplicate, and click Duplicate. 4. Click Close. Deleting Attributes You can delete attributes that you no longer need. When you delete an attribute, the system removes all references to the attribute. To delete attributes: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Attributes tab on the left. 3. Select the attributes to delete, and click Delete. 4. At the confirmation prompt, click Yes. Viewing Attributes In Attributes, you can specify which columns to display for the list of attributes, or show all. You can also reorder columns, sort columns by ascending or descending order, and change the column widths. To display columns: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Attributes tab on the left. 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 then select or deselect the column names. Chapter 12 Setting Up Task Manager 12-36
- 290. • To reorder columns, select View, and then Reorder Columns, select columns and 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 are displayed, and then click Sort Ascending or Sort Descending. • To change column widths, hover over the column header dividers until the arrows display, and drag the columns to the desired width. Searching for Attributes You can use the Search function in the Attributes list to find attributes for Task Manager tasks. You can enter full or partial names on which to search. Using the filter bar, you can control the attributes that you see in the list. By default, all attributes are displayed. To search for Task Manager attributes: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Attributes tab on the left. 3. To search for an attribute, enter search criteria in the Search text box. 4. Optional: From the filter bar, click on a category to display additional search operators such as Equals, Does Not Equal, Contains, Does Not Contain, Starts With, and Ends With. You can filter attributes using these categories: Name, Type, Calculation, Created By, Created On, Last Updated By, or Last Updated On. Note: • Click Add a Filter to view all categories. • To hide the filter bar, click the Filter icon. • To clear all filters, click Clear All Filters in the icon. Managing Task Types Related Topics • Task Types • Creating Task Types • Viewing Task Type History • Editing Task Types • Viewing Task Types • Searching for Task Types • Importing Task Types • Exporting Task Types Chapter 12 Managing Task Types 12-37
- 291. • Deleting Task Types Task Types Task Types are saved definitions of commonly performed tasks. They identify and categorize tasks commonly performed during a business process, for example, Data Entry 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 are shared by all tasks of that type. For example, if you have a set of required questions to be answered by users responsible for data loads, you can create a Data Load Task Type with the required questions. When you create data load tasks, you can select the Data 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, or attributes. • Parent Task: Enables you to create parent tasks to define task hierarchies. To create and manage Task Types, you must be assigned the Service Administrator or Power User security role. Power Users can create their own Task Types, but can only view those of others. Creating Task Types Task Types enable you to set default information for a task, such as settings that need to be input by the user, or questions or instructions that are shared by all tasks of that type. To create a Task Type: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Task Types tab on the left. 3. Click New. 4. See also: • Setting Task Type Properties • Setting Task Type Parameters • Specifying Task Type Instructions • Specifying Task Type Questions • Working With Task Type Rules • Viewing Task Type History Setting Task Type Properties The Properties tab enables you to set the name, ID, and description, and associate an Integration Type. For End User Types, you can allow an Assignee to open a pending task prior to the scheduled time, if all task predecessor conditions have been met. To set Task Type properties: Chapter 12 Managing Task Types 12-38
- 292. 1. Create a new Task Type. The Properties tab is displayed by default. 2. Enter a Task Type Name. You can enter a maximum of 80 characters. 3. Enter a Task Type ID that can be used to identify the Task Type. You can enter a maximum of 80 characters. 4. Enter a Description for the Task Type. You can enter a maximum of 255 characters. 5. To specify an Integration, click the magnifying glass to search for and select an Integration, then click OK. Selecting an Integration enables the Task Type to inherit the parameters from that Integration. 6. Optional: For an End-User Type, select Allow Early Start to allow the Assignee to open the task before the scheduled start time. 7. See also: • Setting Task Type Parameters • Specifying Task Type Instructions • Specifying Task Type Questions • Working With Task Type Rules • Viewing Task Type History Setting Task Type Parameters The 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 that has parameters that must be defined. Parameter values can be set at the Task Type level or at the task level. Some tasks contain parameters that need to be changed each time that they are applied to a schedule. For example, date-driven parameters for Data Entry tasks may need to be set to the current month each time they are added to a schedule. When you set Task Type parameters, you can specify which parameters can be overridden during the scheduling process. To set Task Type parameters: 1. On the Home page, click Application, and then click Task Manager. 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, select Override at Scheduling. 7. See also: Chapter 12 Managing Task Types 12-39
- 293. • Setting Task Type Properties • Specifying Task Type Instructions • Specifying Task Type Questions • Working With Task Type Rules • Viewing Task Type History Specifying Task Type Instructions You can create a set of instructions for completing tasks. You can also add references to documents, files, or URLs to websites. For example, you can attach a policy document 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. 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: Click Choose File to select and attach the file, enter a Name, and then click OK. • URL: Enter the URL and a URL Name; for example, http://www.oracle.com, Oracle, and then click OK. Note: You can add one or more attachments by using drag and drop functionality available from the Add Attachments dialog box. You can rename the attachment in the Name field, if desired. If you drag and drop multiple attachments, you can upload them at one time. You must access the Add Attachments dialog box to properly drag and drop attachments. Tip: To delete a reference, select the reference, and click Delete. 3. See also: • Setting Task Type Properties • Setting Task Type Parameters Chapter 12 Managing Task Types 12-40
- 294. • Specifying Task Type Questions • Working With Task Type Rules • Viewing Task Type History Specifying Task Type Questions You 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 automated Integration. To specify questions: 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/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. For Number of Lines, enter a value between 3 and 50 lines. Multi-Line text determines how many lines of text are visible, without scrolling, on the Actions dialog boxes. Select Attachments if you want the custom attribute to include an attachments section. • Number: Select formatting options to override the defaults set in the Preferences section of System Settings: – For Decimal Places, enter the number of decimal places to display. – Select Display as Percentage to display a percent sign. – Select Thousands Separator to display a thousands separator (for example, 1,000.00). The system displays the thousands separator symbol for the user locale. – For Currency Symbol, select the currency; for example, $ (United States of America Dollar). – For Negative Number, select how to display negative numbers; for example, (123). – To scale a number, in Scale, select from 1000 to 1000000000000. Chapter 12 Managing Task Types 12-41
- 295. • True/False • Text: The maximum length is 255 characters. • User • Yes/No 6. Assign a Role. The purpose of assigning a role is to determine which role can answer 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 Viewer roles. 8. Click OK to save the question. 9. Optional: To change the order of questions, select a question, then click Move to Top, Move Up, Move Down, or Move to Bottom. 10. Optional: To edit a question, select the question and click Edit. To remove a question, select the question and click Delete. 11. Click Save and Close to save the Task Type. 12. See also: • Setting Task Type Properties • Setting Task Type Parameters • Specifying Task Type Instructions • Working With Task Type Rules • Viewing Task Type History Assigning Task Type Attributes To locate Task Types in the system, you can apply attributes to the Task Type. When you 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 of North, South, East, and West. The current Task Type applies only to the West Sales Region, so you can add the Sales Region attribute and set it to "West". To apply an attribute: 1. On the Home page, click Application, and then click Task Manager. 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. Chapter 12 Managing Task Types 12-42
- 296. 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's populated by the Attribute. • Value: Select a value associated with the type of attribute; for example, a numeric value for Formatted Number attribute, a List for List attribute, multiple lines of displayed 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 each Approver 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 Actions dialog box, or in any of the dashboards, list views, or reports. – Allow Edits: Has the ability to add, change, and remove values for the attribute, but subject to the editability rules. – Required: Requires a value for the attribute. The Required option is available for Assignees and Approvers. Until a value is provided, Assignees are prevented from submitting, and Approvers are prevented from approving. d. Click OK. 5. Click OK. 6. See also: • Setting Task Type Properties • Setting Task Type Parameters • Specifying Task Type Instructions • Specifying Task Type Questions • Working With Task Type Rules • Viewing Task Type History Working With Task Type Rules Task Type Rules apply to all Tasks of the same Task Type and thus serve as a convenient mechanism to apply rules to groups of Tasks. Rules configured on the Task Type dialog propagate down to the Edit Task Dialog, appearing on the Rules tab in 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 specified conditions have been met. Example of conditions that could apply to this rule: If attributes have specified values (including calculated attributes) Chapter 12 Managing Task Types 12-43
- 297. 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 additional approval 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 specified conditions are met. When conditions are satisfied, the assignee role is marked as complete, thus progressing 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 with Assignee. • Prevent Task Approval: This rule prevents approval of a task based on attribute values, or other characteristics. This rule runs when the Approver clicks Approve. • Prevent Task Submission: This rule prevents submission of a task based on attribute values, or other characteristics. This rule runs when the Assignee clicks Submit. • Send Email on Update: This rule runs based on user actions on the task. Hence, you must set the conditions for the rule appropriately. The most common condition is to have a condition with the Status attribute or the Status Detailed attribute: – Status attribute: The only valid value that you can select is Closed. Pending, Open, and Error are all statuses that result from automated actions on the task. – Status Detailed attribute: The valid statuses are with the approver. To work with task type rules: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Task Types tab on the left. 3. Click a task type and then click Edit. 4. Select the Rules tab. You can view the following information: • 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 it should be used. • Message (for some rules as noted below): – Message to Approver: Define an optional message to approver in a Prevent Task Approval rule. – Message to Assignee: Define an optional message to assignee in a Prevent Task Submission rule. • Approver Level: For certain rules, select the rule for All Levels or select the Approver levels. Chapter 12 Managing Task Types 12-44
- 298. Note: The Approver Level must be set on the Auto Approve Task rule, and the Prevent Task Approval rule. • Select Create Filter and populate the conditions section or select Use Saved Filter, and then select a filter. The filter selected and configured for the rule determines the conditions that trigger the rule to apply. • For Conditions, select one: – Use Saved Filter: The Condition section displays a read-only version of the conditions associated with the saved filter. – Create Filter: The Condition section is enabled. Conjunction, Source, Attribute, Operator, and Value behave as they do for the existing advanced filter feature. • For Filter Task, specify on which task the conditions should be selected: – Current Task – Any Predecessor – Specific Task: Provide the Task ID. Note: When you make changes to a rule definition, the additional information is added to the audit log. You can view the changes both in the History tab as well as the Audit Report. 6. See also: • Setting Task Type Properties • Setting Task Type Parameters • Specifying Task Type Instructions • Specifying Task Type Questions • Viewing Task Type History Viewing Task Type History The system maintains a history of Task Type actions, which you can view from the View Task Types dialog box. The History tab displays the components that were updated, the modification type, the old and new values, the user who made the modification, and the change date. The information on the History tab is read-only and cannot be changed. To view Task Type history: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Task Types tab on the left. 3. Select a Task Type and click Edit. Chapter 12 Managing Task Types 12-45
- 299. 4. Select the History tab. 5. When you finish, click Save and Close or Cancel. Editing Task Types From the Task Types dialog box, you can edit Task Types. For example, you can add or delete attributes, edit parameters, add or delete questions, edit instructions, or change 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: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Task Types tab on the left. 3. Select the Task Type that you want to edit. 4. Use one of these methods: • Select the Actions icon to the right of the Task Type, and then select 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. 6. Click Save and Close. Viewing Task Types In Task Types, you can specify columns to display for the list of Task Types, or show all. You can reorder columns, sort columns by ascending or descending order, or change the column widths. To display columns: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Task Types tab on the left. 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 then select or deselect the column names. • To reorder columns, select View, and then Reorder Columns. Select columns and 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 are displayed, and then click Sort Ascending or Sort Descending. • To change column widths, hover over the column header dividers until the arrows display, and drag the columns to the desired width. Chapter 12 Managing Task Types 12-46
- 300. Searching for Task Types You can use the Search function in the Task Types list to find Task Types. You can enter full or partial names on which to search. Using the filter bar, you can control the task types that you see in the list. By default, all task types are displayed. To search for task types: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Task Types tab on the left. 3. To search for a task type, enter search criteria in the Search text box. 4. Optional: From the filter bar, click on a category to display additional search operators such as Equals, Does Not Equal, Contains, Does Not Contain, Starts With, and Ends With. You can filter task types using these categories: Name, Task Type ID, Integration, Execution Type, Created By, Created On, Description, Last Updated By, Last Updated On, and User Created. Note: • Click Add a Filter to view all categories. • To hide the filter bar, click the Filter icon. • To clear all filters, click the icon, and then click Clear All Filters. Importing Task Types You can import Task Types or partial Task Type information from text files. The process is similar to importing tasks into a template. Note: Task Type rules cannot be imported. Use Migration to import Task Type rules. To import Task Types, you must have the Service Administrator or Power User security role. To import Task Types: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Task Types tab on the left. 3. Click Actions, and then Import. 4. Click Choose File and navigate to the file. 5. Select an Import Type: Chapter 12 Managing Task Types 12-47
- 301. • Replace: Completely replaces the definition of a Task Type with the definition in the import file. This option replaces all Task Type detail with the information that is in the file that you are importing. It does not affect Task Types that are not specified in the import file. The system displays a warning that task types matching a task type ID in the import file will be modified. If you do not want to overwrite the task type, click Cancel. Note: You can select the Keep Attachments checkbox to retain attachments to task types that are being replaced. • Update: Updates partial information for Task Types. This option is not a full replacement of the Task Type details. Only details for the Task Type properties specified in the file are updated. 6. Select a Date Format. Select a format from the drop-down list of allowed date formats. Date formats are not translated. By default, the date format is set to the locale date format of the exported file location. 7. Select a File Delimiter for the import file. Choose Comma, Tab, or choose Other to specify any single character for the Other Delimiter. 8. Click Import. Exporting Task Types You can export Task Types to a comma-separated values (CSV) file, which can be read by Excel, then modified and reimported. Note: Task Type rules can't be exported. Use Migration to export Task Type rules. To export Task Types: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Task Types tab on the left. 3. Select one or more Task Types, click Actions, and then select Export. 4. In the Export Task Types dialog, select from the following export options: • For Rows, select All Task Types or Selected Task Types. • For Format, select Formatted data or Unformatted data for future import. 5. Click Export and then Close. Chapter 12 Managing Task Types 12-48
- 302. Deleting Task Types You can delete Task Types that you no longer need. To delete a Task Type, you must have Service Administrator or Power User security rights. Note: You cannot delete a Task Type if tasks belong to it. To delete a Task Type: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Task Types tab on the left. 3. Select the Task Type that you want to delete. 4. Use one of these methods: • Select Actions, and then Delete. • Click the Delete icon. • Right-click and select Delete. 5. At the confirmation prompt, click Yes. Managing Task Templates A task template defines a repeatable set of tasks required for a business process. It is used as a basis for creating schedules. You can create templates for different types of processes. Template tasks are not assigned to specific days on a calendar, but are defined using generic 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 create schedules. If you are a Service Administrator or Power User, you can view, create, edit, and delete templates. Note: The maximum number of task templates that you can create or import is 10,000. Creating Task Templates You 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. Chapter 12 Managing Task Templates 12-49
- 303. Creating Task Templates. To create a template: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left. 3. Click New. 4. Enter the necessary information in the template sections: • Setting Template Properties • Specifying Template Instructions • Assigning Viewers to Templates • Applying Template Attributes • Specifying Day Labels • Embedding Templates • Working With Template Rules Setting Template Properties The Properties tab enables you to specify the template name, description, owner, and time span. You must assign a template owner to every template, which must be a Service Administrator or Power User. The current ID is the default owner. The template owner is 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 a Day Zero. You can specify the number of days a template tracks before and after the Zero day. Days before Day Zero are represented as Day-5, Day-4, and so on. Days after Day Zero are represented as Day 3, Day 4, and so on. A template has at least one day (Day Zero), even if you do not specify days before or after it. To set template properties: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left. 3. From the New or Edit Template dialog, on the Properties tab, enter: • Name: You can enter a maximum of 80 characters. • Description: You can enter a maximum of 255 characters. • Organizational Unit 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 an embedded template. Chapter 12 Managing Task Templates 12-50
- 304. If this option is enabled, the template is not allowed to be deployed. This prevents supporting templates from being deployed by mistake. 6. For Owner, use the default owner or click Select Owner . Administrators, or Power Users configured with the Administrator or Power User roles are the only roles that will display when you click Search to select a user to assign as an Owner. Any member of the Shared Services group can perform the role, but the same person cannot perform more than one role. 7. Enter the necessary information in the template sections: • Specifying Template Instructions • Assigning Viewers to Templates • Applying Template Attributes • Specifying Day Labels • Embedding Templates • Working With Template Rules Specifying Template Instructions You can specify instructions in the template for completing the business process. Users can view the instructions from tasks in the template. The instructions are also transferred to each schedule. You may want to supply additional detail to help users understand the purpose of the template and how to complete the tasks. You can attach additional references. You can easily see if a task includes instructions within the Schedule Task and Template Task lists. You can add the Instructions column to your list view and see the textual instructions for the task. To specify template instructions: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left. 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: 1. In the References section, click Add. 2. From the Reference Type list, select one of these types: • Local File: Click Choose File to select and attach the file, enter a name, and click OK. • URL: Enter the URL, then enter a URL name; for example: http://www.oracle.com., Oracle, and then click OK. 3. Enter the necessary information in the template sections: • Setting Template Properties • Assigning Viewers to Templates Chapter 12 Managing Task Templates 12-51
- 305. • Applying Template Attributes • Specifying Day Labels • Embedding Templates • Working With Template Rules Assigning Viewers to Templates The Viewers tab enables you to assign viewer rights to users who may view tasks in the schedule and schedule tasks that are generated from the template. You can assign multiple users to a template as viewers. Viewers can be a team or group assignment. A Power User viewer can view the template details and template tasks as read-only. A Viewer has no template access, and only read-only access to schedules produced from the template. Note: Only users who have the task Viewer role can respond to questions. To assign viewer rights: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left. 3. From the New or Edit Template dialog, select the Viewers tab. 4. Click Add. 5. To search by users or groups, click Search Users, then select Users or Groups . 6. Enter a full or partial user name, then click Search. 7. To specifically identify a user, click Advanced, then enter a User ID or Email address. 8. From the Search Results list, select users, then move them to the Selected pane. 9. For additional details about the user, such as groups or roles, click Details. 10. Click Add or Add All to move users to the Selected list. Tip: To remove users, select them, and then click Remove or Remove All. 11. Enter the necessary information in the template sections: • Setting Template Properties • Specifying Template Instructions • Applying Template Attributes • Specifying Day Labels • Embedding Templates Chapter 12 Managing Task Templates 12-52
- 306. • Working With Template Rules Applying Template Attributes To locate templates in the system, you can apply attributes to the template. When you 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 of North, South, East, and West. The current template applies only to the West Sales Region, so you can add the Sales Region attribute and set it to "West". To apply an attribute: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left. 3. From the New Template or Edit Template dialog, select the Attributes tab. 4. Click Add. 5. From the Attribute list, select an attribute. The Type field is not editable; it's populated by the 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. 8. Enter the necessary information in the template sections: • Setting Template Properties • Specifying Template Instructions • Assigning Viewers to Templates • Specifying Day Labels • Embedding Templates • Working With Template Rules Specifying Day Labels You can customize the names of days in the template. Editing the name of the day does not change its sequential order. Day Labels created in a template are copied to any schedule created from the template. To specify day labels: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left. 3. From the New Template 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. You can enter a maximum of 20 characters. 6. Click OK. Chapter 12 Managing Task Templates 12-53
- 307. 7. Enter the necessary information in the template sections: • Setting Template Properties • Specifying Template Instructions • Assigning Viewers to Templates • Applying Template Attributes • Embedding Templates • Working With Template Rules Embedding Templates You can reuse tasks from one task template in another by embedding one template into another template. When you schedule tasks for a template, tasks for embedded templates are also scheduled. For example, you may have two processes that are essentially the same, with some additional tasks for one of the processes. You can specify that one template embeds the second template so if you change one template, you do not need to update the other one. When you generate a schedule, it will include the tasks from the other template. Note: Only one level of embedding is possible. For example, if Template A is embedded in Template B, then Template B cannot be embedded in another template. Embedded templates are task templates that are not designed to be deployed directly, but rather to be used by other templates that are directly deployed. The Manage Templates screen includes these columns to identify embedded templates: • Embedded: a list of templates that are embedded in the current template. Blank if none. • Embedded In: a list of templates that the current template is embedded in. Blank if none. The columns are not displayed by default, but are available from the View menu. To embed templates: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left. 3. To identify previously embedded templates, click View, then Columns, and then select Embedded In or Embedded Templates. 4. From the New Template or Edit Template dialog, select the Embedded Templates tab. 5. From the Available Templates list, select a template to embed. 6. Click Move to move the template to the Embedded Templates list. Chapter 12 Managing Task Templates 12-54
- 308. Tip: To remove a template or templates, select the template from the Embedded Templates list and click Remove or Remove All to move it to the Available Templates list. 7. Click OK. 8. Enter the necessary information in the template sections: • Setting Template Properties • Specifying Template Instructions • Assigning Viewers to Templates • Applying Template Attributes • Specifying Day Labels • Working With Template Rules Working With Template Rules Template rules apply to all tasks in the template, and rules are also applied to groups of tasks. Rules that you configure in the Template dialog box apply to the Schedule dialog box and the Edit Task dialog box, and they are displayed on the Rules tabs, in read-only form. Template rules: • Auto Approve Task: Automatically completes specified approvals if specified conditions 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 be marked as complete, and workflow progresses to the next approval level or is closed if no 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. When conditions have been satisfied, the rule causes the assignee role to be marked as complete, thus progressing workflow to the first approval level, or to Closed if no approval levels exist. Chapter 12 Managing Task Templates 12-55
- 309. Note: – Auto Submit Task runs when the Task status changes from Pending to Open with Assignee. Auto Submit Task rule honors predecessor relationship. It will only run when Finish-To-Finish predecessors have completed without error and Finish Error-To-Finish predecessors have completed. When a Finish-To-Finish predecessor is Closed by either user or rules, it should check for its Running successors and trigger Auto Submit Task rules if necessary. – Auto Submit Task rule is not triggered when the task has missing parameters. • Prevent Task Approval: This rule prevents approval of a task based on attribute values, or other characteristics. This rule runs when the Approver clicks Approve. • Prevent Task Submission: This rule prevents submission of a task based on attribute values, or other characteristics. This rule runs when the Assignee clicks Submit. To work with template rules: 1. On the Home page, click Application, then click Task Manager. 2. Click the Templates tab on the left. 3. Open a template. 4. Select the Rules tab. You can view the following information about the rules that are associated with a template: • Order: The order of precedence • Rule • Conditions: The conditions that must exist before running the rule 5. To create or edit a rule, on the Rules tab, click New or Edit and update: • Rule: Select a rule. Note: When you make changes to a rule definition, the additional information is added to the audit log. You can view the changes both in the History tab as well as the Audit Report. • Description: Optional. Explain why you configured the rule and how it should be used. You can enter a maximum of 255 characters. • Approver Level: Select All Levels or select the Approver levels. • Select Create Filter and populate the conditions section or select Use Saved Filter, and then select a filter. The filter selected and configured for the rule determines the conditions that trigger the rule to apply. • Conditions: Chapter 12 Managing Task Templates 12-56
- 310. – Use Saved Filter: The Conditions section displays a read-only version of the conditions associated with the saved filter. – Create Filter: The Conditions section is enabled and you can click Create Condition or Create Condition Group to specify conditions. Conjunction, Source, Attribute, Operator, and Value behave as they do for the existing advanced filter feature. • Filter Task: Specify for which task the condition should be selected: – Current Task – Any Predecessor – Specific Task: Provide the Task ID 6. To delete, duplicate, or reorder a rule, click the appropriate button and follow the instructions. 7. Enter the necessary information in the template sections: • Setting Template Properties • Specifying Template Instructions • Assigning Viewers to Templates • Applying Template Attributes • Specifying Day Labels • Embedding Templates Viewing Template History The system maintains a history of template actions, which you can view from the Template dialog box. The History tab displays the components that were created or updated, the modification type, the old and new values, the user who made the modification, and the change date. The information on the History tab is read-only. To view template history: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left. 3. Select a template for which to view history and click Edit. 4. Select the History tab. 5. Click OK. Opening Templates You can open and work with templates from the Templates dialog box. To open a template: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left. 3. From Templates, select a template. 4. Use one of these methods: Chapter 12 Managing Task Templates 12-57
- 311. • Click the Actions icon to the right of the template, and then select Edit. • Click the template. • Right-click and then select Edit. Adding Tasks to Templates You 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 start day 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 template is 500,000. To add a task to a Task Manager template: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left. 3. Select and open a template. If you have a large list of templates, enter a full or partial name in the Search box to search for templates from a list in the selection dialog. 4. Add tasks as required. 5. Click OK. Editing Templates You can edit Task Manager templates to change the properties, such as the name of a template and the number of days before and after Day Zero. If you reduce the number of 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: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left. 3. Select a template and click Edit. 4. Edit the template properties. 5. Click OK. Chapter 12 Managing Task Templates 12-58
- 312. Importing Tasks into Templates You can import tasks, or partial task data, from text files such as a Microsoft Excel spreadsheet, into a template. For example, you can enter task definitions as rows in Excel, save the file as a comma-separated values (CSV) file, and then import it into a template. You can also use the Import feature to quickly add many repetitive tasks by editing 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 are unique 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 option replaces the task detail with the detail that is in the file that you are importing. It does 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 might have made changes to task instructions, reassigned Owners, Assignees, and Approvers, or removed some attributes and added new attributes. You might also have made the same change to a large number of tasks, for example, adding a new attribute to 100 of 400 tasks. The update option is not a full replacement of the task details. Only details for the task properties specified in the file are updated. 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. • Delete: Deletes tasks and associated information based on a list of task IDs provided in a file. The required information to perform a delete is a file with a column of task IDs. To import tasks into a template: 1. On the Home page, click Application, and then click Task Manager, 2. Click the Templates tab on the left. 3. Select a template into which to import tasks. 4. Click Import Tasks. 5. Enter the name of the file to import, or click Choose File to find the file. 6. Select an import option: • Replace: Replaces the definition of a task with the definition in the import files. It does not affect other tasks that are not specified in the import file. Note: You can select the Keep Attachments checkbox to retain attachments to tasks that are being replaced. Chapter 12 Managing Task Templates 12-59
- 313. • 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 new attributes. You might also have made the same change to a large number of tasks, for example, adding a new attribute to 100 of 400 tasks. The update option is not a full replacement of the task details. Only details for the task properties specified in the file are updated. 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. Note: The system displays a warning that tasks in the template that match a task ID in the import file will be modified. If you do not want to overwrite the task, click Cancel to cancel the import process. • Delete: Deletes tasks and associated information based on a list of task IDs provided in a file. The required information to perform a delete is a file with a column of task IDs. 7. Select a Date Format. Select a format from the drop-down list of allowed date formats. Date formats are not translated. By default, the date format is set to the locale date format of the exported file location. 8. Select a File Delimiter for the import file. Select Comma or Tab. Select Other to specify any other single character as the Other Delimiter. 9. Click Import. • If the import is successful, the Import Success dialog box is displayed, indicating the template name, the name of the file containing the tasks, and the total number of tasks imported. Click OK. • If errors are found, the import process is not run, and the Import Errors dialog box displays errors. View the errors, then click OK to return to the Templates page. Table 12-4 Troubleshooting Import Errors Error Resolution Duplicate Task ID Check for duplicate Task IDs. Task IDs must be unique within the template or schedule. See Creating Tasks. Task Name is too long The Task Name can contain a maximum of 80 characters. See Setting Task Properties. Organizational Value - "Invalid Value" The Organizational Value cannot be blank, contain bullet points or multiple lines. Task Import File Format The task import file enables you to specify the task information that you want to import into a template. The first row contains only the column headings that identify the data in that column, for example, TaskName. Separate rows are used to define each task. Chapter 12 Managing Task Templates 12-60
- 314. Each task in the file must be given a unique ID in the TaskID column. You use the numeric IDs to uniquely identify predecessors and parent tasks. For example, when you enter a parent task in the Parent column, you enter the numeric ID of the task rather than the task name. When you use the Replace or Replace All options, you can add, remove, and shift the columns but you cannot remove required columns. When you use the Update option, there are no required columns except TaskID, or TaskTypeID when you are importing Task 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 task may 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, or References only represent the relative order with the other approvers, questions, or references. 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. To replace question text, approvers, or reference names, you must use Replace mode. When you select Update mode, the system only adds a new question, approver, or reference if the file names do not match. All Text Lookup rows in the file must match values stored in the application. For example, if you are importing Task Types, you must have specified values for them when you set up the application. For groups of column headings, if you have a certain number of one of the group, you must have the same number for other members. For example, if you have QText5, there must be a corresponding QType5. Note: When you need to create multiple lines of text in the import file (for example, in Instructions), use this syntax to indicate a new line: 'n'. Do not use hard returns to separate lines of text. Column ID Description Type TaskID ID of task. Maximum of 80 characters. Text TaskName Name of task Text TaskType Task Type Text Lookup Description Full description of task. Maximum of 1000 characters. Text Priority Task priority (High, Medium, Low) Text Lookup StartDate Start date, in template days (for example, -5, 0, 1, 12) For schedules, the start date must be a calendar date in the locale format. Integer StartTime Start time in HH:MM (24-hour), for example: 13:00 Integer EndDate User tasks only, in template days (for example, -5, 0, 1, 12) For schedules, the end date must be a calendar date in the locale format. Integer Chapter 12 Managing Task Templates 12-61
- 315. Column ID Description Type EndTime User tasks only, in HH:MM (24-hour), for example, 13:00 Integer Duration Task duration in minutes (automated tasks only) Number Owner Task owner Text Lookup Assignee Task Assignee (user tasks only) Text Lookup Active Whether the task is active. Only applies to template import. Boolean StartEarly Whether the Assignee is allowed to open a pending task prior to the scheduled start time Boolean RunAs RunAs user name. Only applicable for system-automated tasks. Text Lookup Instruction Instruction text. Maximum of 2 GB. Text Reference# Instruction reference (URL and Content 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, for document references Integer Approver# Approver Level User Name Viewer# Task viewer User Name QText# Required for question. Text of question. Maximum of 255 characters. Text QType# Required for question. Data type of question (Text, Member, True/False, and so on) Text Lookup QReq# Required for question. Question required? (Yes or No) Boolean QList# List of values for question, separated by | symbol, for example, Red|Green| Blue|Yellow. Text Lookup QCurrSymbol# Currency format for question X Text QDecPlaces# Number of significant digits after the decimal places for question X Number QNegNumFmt# Negative number format for question X Text: - or ( ) QScale# Scale format for question X Number, in magnitude: 1000 and so on QThouSep# Thousand separator indicator for question X Boolean Attribute# Attribute name, for example, Color Text Lookup AttrVal# Attribute value, for example, Red. Maximum of 255 characters. Text Chapter 12 Managing Task Templates 12-62
- 316. Column ID Description Type AttrDisplay Display to user (in task action dialog box) 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 (for example, Finish to Start). Text Lookup PredTemplate# Name of the predecessor template or schedule, if the predecessor belongs to 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 you can modify: • Two questions • Two attributes • Two instructional references • Three predecessor tasks • Three approver levels Exporting Tasks to Microsoft Excel You can export tasks from a template to a flat file in CSV format, then use Microsoft Excel to modify the file. For example, you can export the tasks from a template in a test installation and import them to a template in a production installation. When you export tasks from a template, they are saved to a CSV file. To export tasks: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left. 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. Chapter 12 Managing Task Templates 12-63
- 317. Reassigning Users in Templates You may periodically need to reassign users to different tasks. For example, you may create a template and assign a user to certain tasks; however, later that employee leaves the company and another employee assumes those tasks. You can use the Reassign feature in the Templates dialog box to automatically change assignments instead of manually searching for, opening, and editing individual tasks. The Reassign feature enables you to quickly find the tasks associated with one user and reassign them to another. You can reassign users for multiple templates at a time. This can be helpful if your application has a large number of templates. You can select the roles for which to reassign users. For example, if you select the Owner role, the system reassigns the user only in tasks in which the user was assigned as the owner. When tasks are reassigned, email notifications are sent immediately to reassigned users. To reassign users: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left. 3. Select one for more templates for which you want to reassign users. 4. Select Actions, and then Reassign User. 5. For Find User, enter the search criteria for the user that you want to replace: a. Click Find User, then from the Select User dialog box, enter the first or last name for the user, and then 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 to reassign 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 the template name and total number of user reassignments made. Creating Schedules from Templates You can create schedules from templates. Creating a schedule from a template populates the schedule with the tasks in the template. If the source template has embedded templates, the tasks in the embedded templates are included. Template instructions, viewers, and attributes are also added to the schedule. Chapter 12 Managing Task Templates 12-64
- 318. You create schedules from templates from the Edit Templates dialog box. The Last Schedule column shows the last schedule created from each template. The Schedules column shows the total number of schedules created from each template. To create a schedule from a template, you must have the Service Administrator or Power User role. You can use REST API to create Task Schedules from Templates. This will allow you to create an automated routine to generate all of your periodic task schedules. For more information, see Deploy Task Manager Templates in REST API for Oracle Enterprise Performance Management Cloud . The schedule starts in a Pending status, which gives you the opportunity to make final changes in the definition. When template tasks are added from a template to a schedule, they are assigned calendar dates based on their relationship to the template Day Zero. The dates can also 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 you selected to exclude weekend days. The Date Map displays the default calendar date assigned to each template day. You can use the Date Map feature to adjust the date assignments. A task in one template can have predecessor tasks in other templates. When you create a schedule from a template, you can select predecessor tasks in schedules as predecessors for tasks with predecessors in other templates. You use the Predecessor Task Links tab to select predecessor tasks in schedules. The Predecessor Task Links tab lists all tasks with predecessors in other templates, and enables you to select a predecessor in a schedule for these tasks. Tip: When you create a schedule from a template, you can globally update the task parameters for a Task Type if the parameters have the override option enabled. See Setting Task Type Parameters. To create a schedule from a template: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left. 3. Select the template that you want to schedule. 4. If the template was successfully validated, create the schedule. Click the Actions icon on the right side, and then select Create Schedule, or click the Create Schedule icon above the listing. On the Schedule Parameters tab, enter the following fields: • Schedule: The name of the schedule. • Year: Select the schedule year. • Period: Select a period for the schedule. • Day Zero Date: Select the calendar date to assign to the template Day Zero. • Date Mapping: Chapter 12 Managing Task Templates 12-65
- 319. – Organizational Unit – Calendar days – Working days – Advanced Configuration dialog box: Click Advanced Configuration to override the Organizational Unit and Work Days configuration for all tasks in the schedule. Tip: You can create one global template and have that template create the proper schedules for each regional entity, taking into consideration the holiday calendars, time zones, and work day configurations of the entity. * Organizational Unit Select one: * Use Task Value: Select a value from the Organizational Unit * Set Value To: The selected organizational unit is applied to all tasks in the Schedule (even if the task in the template contained a different Organizational Unit value). Since all tasks have the same Organizational Unit, the Organizational Unit in the Date Mapping panel on the Schedule from Template dialog box displays as Read Only. * Work Days: If you do not assign an organizational unit to a task, and you do not use the Override Work Days feature, than the application uses the following default: Monday – Friday are working days, and Saturday and Sunday are non-working days. – Date Map: For each template day whose date assignment you want to modify, in the Date column, enter the new date. Chapter 12 Managing Task Templates 12-66
- 320. Note: Day Labels are applied to the dates within the Date Mapping. That is, whatever the template day level is, the same will be applied to the schedule for the dates that were mapped. Day mapping may vary by Organization Unit within the Date Mapping. If there is no Organization Unit assigned to the template level, the "Unassigned" day mapping will be applied to the schedule. If the template has an Organization Unit assigned, then the day mappings for that Organization Unit will be assigned to the schedule. For multiple days mapped to the same date, the day labels will be concatenated with comma. Non-working days will have a blank day label. The Organization Unit drop-down list is used for Date Mapping. It contains only Unassigned and Organization Units related to the template. The Org Unit dropdown list in Create Schedule dialog is for date mappings, not for the Organization Unit of the created schedule. It only contains the Unassigned and the Organization Unit related to the template. 5. Optional: Select the Predecessor Task Links tab, select the schedule that contains the predecessor task and in the Assigned Task list, select the predecessor task. 6. Optional: Select the Override Parameters tab, review the parameters, and for each parameter that you want to modify, in the New Value column, enter a new value. Note: The Override Parameters tab displays only tasks that use a Task Type in 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 from the template. It has a status of Pending. By default the schedule is opened into a view when created. Review the schedule and make adjustments as needed. Manually Validating Templates When you generate a schedule from a template, the system automatically validates the template first to check for uniqueness violations, tasks that directly or indirectly depend on each other, or a date-precedence mismatch. For example, you cannot have circular predecessors. You can manually validate templates. Validation is particularly useful to check for problems after you import tasks into a template from a file. Chapter 12 Managing Task Templates 12-67
- 321. The validation results show the template names, status, and error messages. You can sort the list of validation results by Template Name or Status. To manually validate templates: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left. 3. From Templates, select one or more templates to validate. 4. Click Validate. If no errors exist, the validation results show a "Template is valid" message. If errors exist, it shows the error details. Viewing Task Manager Templates In the Templates dialog box, you can specify which columns to display for the list of templates, or show all. You can also reorder columns, sort columns by ascending or descending order, or change the column widths. To display columns: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left. 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 then select or deselect the column names. • To reorder columns, select View, and then Reorder Columns. Select columns and then 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 are displayed, and then click Sort Ascending or Sort Descending. • To change column widths, hover over the column header dividers until the arrows display, and drag the columns to the desired width. Chapter 12 Managing Task Templates 12-68
- 322. Searching for Templates You can use the Search function in a Templates list to quickly find Task Manager templates. You can enter full or partial names on which to search. Using the filter bar, you can control the templates that you see in the list. By default, all templates are displayed. To search for templates: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left. 3. To search for a template, enter search criteria in the Search text box. 4. Optional: From the filter bar, click on a category to display additional search operators such as Equals, Does Not Equal, Contains, Does Not Contain, Starts With, and Ends With. You can filter templates using these categories: Name, Owner, Organizational Unit, Days After Day 0, Days Before Day 0, Embedded In, Embedded Only, Embedded Templates, Description, Created By, Created On, Last Updated By, or Last Updated On. Note: • Click Add a Filter to view all categories. • To hide the filter bar, click the Filter icon. • To clear all filters, click Clear All Filters in the icon. Deleting Templates You can delete Task Manager templates that you no longer need. To delete a template, you must have security rights to the template. Deleting a template removes it from the list of available templates and removes tasks associated with it. It does not directly affect a running schedule, however some reporting and dashboard metrics may use the template to link various schedule runs together, which are not possible if the template is deleted. To delete a Task Manager template: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left. 3. Select the template, and click Delete. 4. At the confirmation prompt, click Yes. Chapter 12 Managing Task Templates 12-69
- 323. Managing Tasks Tasks are the core units of action in a business process, such as data entry or data consolidation. Each task has different parameters depending on the Task Type. If you have Service Administrator or Power User security rights, you can create, edit, or delete tasks. See Creating Tasks. See also: Managing Services Creating Tasks You can add tasks to templates or schedules. If you create a task in a template, you assign the start and end date as days before or after Day Zero. If you create a task in a 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 business process. After viewing upper-level parent tasks, you can then drill into the underlying tasks. 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 Viewers • Setting Task Predecessors • Applying Task Attributes • Working With Task Rules • Viewing Task History Watch these videos to learn more about creating tasks. Creating Tasks The following tutorial contains additional information on creating tasks: Viewing, Updating, and Adding Tasks in Task Manager Chapter 12 Managing Tasks 12-70
- 324. Setting Task Properties The 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 or Assignee is not available to work on the task (due to sick time, vacation, has left the company, or is simply too busy), you can reassign users associated with a task, template, or schedule. Template, schedule, and task Owners, Assignees, and Approvers may also reassign their tasks. For end-user tasks, you can allow an Assignee to open a pending task prior to the scheduled time, if all task predecessor conditions have been met. Automated tasks have no Assignees, however you can specify Run As users for users under which tasks of that type are run. Event Monitoring tasks have no Assignees and Run As users. To set task properties: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left and then click the Tasks tab. Note: If you've enabled the Redwood Experience, the Tasks tab displays at the bottom of the page instead of at the top. 3. Open a task. 4. Click Properties and enter this information: • Task Name: Enter a maximum of 80 characters or less. • Task ID: Identifies the task (required). Task IDs must be unique within the template or schedule. You can enter a maximum of 80 characters or less. • Description: Enter a maximum of 255 characters or less. Note: You can use carriage returns and URLs in Descriptions, Questions, and Instructions. • Organizational Unit: Represents a hierarchical entity-type structure that you can use to model your organization. Define a separate organizational unit for each entity for which separate reporting is required, or for entities that require different configurations for any of the following: time zones, holidays, work days, or viewer or commentator assignments. Organizational Units are defined in system settings. • Task Type: Click the magnifying glass and select a Task Type (required). • For Priority, select from the following options: – High Chapter 12 Managing Tasks 12-71
- 325. – Medium – Low • Owner: Use the default owner or click Select Owner to select a user or group. • Select Active to include this task in schedules generated from the template. Note: This option is not available for tasks created in schedules. 5. Click Save and Close. 6. See also: • Setting Task Parameters • Specifying Task Instructions • Selecting the Workflow • Adding Task Questions • Setting Task Viewers • Setting Task Predecessors • Applying Task Attributes • Working With Task Rules • Viewing Task History Setting Task Parameters The Parameters dialog only contains data for tasks that are associated with an Integration Type and have parameters. Integration Types provide links to external applications. From Parameters, you can set specific information about the task and how it is run. The parameters are passed to the external application. For example, if the task contains a link to a data grid, you might use the Parameters dialog to select a point of view for the grid. To set task parameters: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left and then click the Tasks tab. Note: If you've enabled the Redwood Experience, the Tasks tab displays at the bottom of the page instead of at the top. 3. From the New Task or Edit Task dialog box, click Parameters. 4. If the parameter values are not entered by the task type, you may enter the required parameter values. Chapter 12 Managing Tasks 12-72
- 326. Note: If the parameters are not defined when the task is ready to start, an email is sent to the task owner. The task waits to start until the values are provided. 5. See also: • Setting Task Properties • Specifying Task Instructions • Selecting the Workflow • Adding Task Questions • Setting Task Viewers • Setting Task Predecessors • Applying Task Attributes • Working With Task Rules • Viewing Task History Specifying Task Instructions Task owners can create a set of instructions for completing the task. All other users who have access to the task are only able to read the instructions. If there are task instructions that are inherited from the Task Type, template, or schedule, that instruction text is displayed above the instruction text box and is read-only. For template tasks, the Template and Task Types instructions are viewable but not editable. To specify instructions: 1. On the Home page, click Application and then click Task Manager. 2. Click the Templates tab on the left, and then click the Tasks tab. Note: If you've enabled the Redwood Experience, the Tasks tab displays at the bottom of the page instead of at the top. 3. From the New Task 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, click Add. 2. From the Reference Type list, select one of these types: • Local File: Click Choose File to select and attach the file, enter a Name, and then click OK. • URL: Enter the URL and URL Name; for example, http://www.oracle.com, Oracle. 3. See also: Chapter 12 Managing Tasks 12-73
- 327. • Setting Task Properties • Setting Task Parameters • Selecting the Workflow • Adding Task Questions • Setting Task Viewers • Setting Task Predecessors • Applying Task Attributes • Working With Task Rules • Viewing Task History Selecting the Workflow To select the Task Manager workflow: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left and then click the Tasks tab. Note: If you've enabled the Redwood Experience, the Tasks tab displays at the bottom of the page instead of at the top. 3. From the New Task or Edit Task dialog box, click Workflow. 4. The Workflow section contains the Assignee and Approver assignments. Note: You cannot assign the same user to multiple roles within the workflow. Enter this information 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 actual user for the completed workflow, for example Assignee (Actual). In the 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 reassigned after it was completed by the initial user. Chapter 12 Managing Tasks 12-74
- 328. For an End-User task, for Assignee, click Select Assignee to find a user. If you do not select an Assignee, the owner becomes the default Assignee. Parent and automated tasks have no Assignees. Note: For a Process-Automated task, click Run As, search for and select a user under which tasks of this type are run, and click OK. If the selected Run As user is the user who also created the task, then the user can authorize the task, without being prompted to re-enter their password. • Backup: If you assigned a user for the primary Assignee, you can assign a backup user authorized as an Assignee: a. Click Backup . b. Enter the First Name and Last Name or click Search to select a backup user. c. Click OK. • Starts: Select a start date, then select the time of day, in increments of 15 minutes, for the 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 the form of Day(s), Hour(s), and Minute(s). An At Risk criteria is based on the condition if the Start date was missed and (the End_date minus the Current_date is less than the minimum task duration or the End_Date minus the Start_Date is less than the minimum duration). The At Risk tasks display in the Needs Attention Graph in the Status Chart of the Dashboard. • Optional: For an End-User task, select Allow Early Start to allow the Assignee to open the task before the scheduled start time. Enter this information for the Approver: • Level • Name • Backup • End Date 5. See also: • Setting Task Properties • Setting Task Parameters • Adding Task Questions • Setting Task Viewers • Setting Task Predecessors • Applying Task Attributes Chapter 12 Managing Tasks 12-75
- 329. • Working With Task Rules • Viewing Task History 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 their actions before they indicate a task is complete. For example, you may ask if a certain process 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 a question is required, the user must respond or they cannot submit the task for approval. You can also order the questions by using the Move Up and Move Down buttons. For schedule tasks, users can respond to the questions from the Task Actions page. If you 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 can remove or update the questions. Rows that are locked cannot be edited or deleted because they are inherited from the Task Type. In templates, the Task Type questions are displayed, but are not editable. Note: Only users who have the task Viewer role can respond to questions. To add a question: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left, and then click the Tasks tab. Note: If you've enabled the Redwood Experience, the Tasks tab displays at the bottom of the page instead of at the top. 3. From the New Task or Edit Task dialog box, click Questions. 4. Click Add. 5. Enter the Question with a maximum of 2000 characters or less. 6. For Type, select from the following options: • Date Chapter 12 Managing Tasks 12-76
- 330. • Date/Time • Integer: Enter a value between -2147483648 and 2147483647. • List: Enter a list of valid responses to the question (up to 255 characters). • Multi-Line Text: Enter the Number of Lines, from 3 to 50 lines. Enter a maximum of 4000 characters. Multi-Line Text determines how many lines of text are visible without scrolling, on the Actions dialog boxes. Select Attachments if you want to include an attachments section. • Number: Enter a value xxxxxxxxxxxxxxxxx.xxxxxxxxx (17 digits and 9 decimal places). Select number formatting options: – For Decimal Places, enter a value for the number of decimal places to display. – For Display As Percentage, check the box if you want a percentage to display. – Select the Thousands Separator option if you want numbers to display a thousands separator (for example, 1,000.00). – For Currency Symbol, select a currency symbol; for example, $ (United States of America Dollar). – For Negative Number, select how to display negative numbers; for example, (123). – For Scale, select a scale value for numbers; for example, 1000 or 1000000000000. • True/False • Text: You can enter a maximum of 4000 characters. • User • Yes/No 7. Assign a Role (Assignee, Approver, Owner, Viewer) to the question. Access is based on responsibilities. 8. If the question is required, select Required. The Required checkbox is disabled for Questions assigned to Owner or Viewer roles. 9. Click OK. 10. Optional: To change the order of questions, select a question, then click Move To Top, Move Up, Move Down, or Move To Bottom. 11. Optional: To edit a question, select the question and click Edit. To remove a question, select the question and click Delete. 12. See also: • Setting Task Properties • Setting Task Parameters • Specifying Task Instructions • Adding Task Questions • Setting Task Viewers • Setting Task Predecessors • Applying Task Attributes Chapter 12 Managing Tasks 12-77
- 331. • Working With Task Rules • Viewing Task History Setting Task Viewers The Viewers tab enables you to add or remove Viewers for the current task. You can specify an unlimited number of viewers. To set task access: 1. From the New Task dialog box, select the Viewers tab. 2. Enter the first or last name of the user, then click Search. To specifically identify a user, click Advanced, then enter a User ID or Email address. Tip: For additional details about the user, such as groups and roles, click Details. 3. To remove a user from the Viewers list, select the user, then click Remove. 4. See also: • Setting Task Properties • Setting Task Parameters • Specifying Task Instructions • Selecting the Workflow • Adding Task Questions • Setting Task Predecessors • Applying Task Attributes • Working With Task Rules • Viewing Task History Setting Task Predecessors The Predecessors tab enables you to set predecessors for the current task. For template tasks, you can choose a predecessor from another template, and for schedule tasks, you can choose a predecessor from another schedule. You must assign a condition to the predecessor/successor relationship. A task does not need predecessor tasks as long as a start date and time is specified. If both are specified, the task begins when the predecessor tasks are started or complete (for Finish to Start) and the start date and time is reached. You can set these conditions under which the predecessor relationship is established: Chapter 12 Managing Tasks 12-78
- 332. Condition Description Finish to Start Default. The task starts as soon as the predecessor task completes or finishes with warning. Finish Error to Start The task starts as soon as the predecessor task completes, even if it is in error. Finish Error to Finish The task completes as soon as the predecessor task completes, even if it is in error. Finish to Finish The task cannot be marked as Complete until the predecessor task is marked as complete. This is primarily used for user tasks. For example, a user can start a document summary, but cannot mark it complete until the consolidated data is final. To set task predecessors: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left and then click the Tasks tab. Note: If you've enabled the Redwood Experience, the Tasks tab displays at the bottom of the page instead of at the top. 3. From the New Task or Edit Task dialog box, select the Predecessors tab. 4. Click Add. 5. To search for a Predecessor task, click Expand Search, enter the Task Name, then click the Search button. To refine the search, click Advanced, and enter advanced search criteria. 6. Select a predecessor task(s) and click OK. 7. See also: • Setting Task Properties • Setting Task Parameters • Specifying Task Instructions • Selecting the Workflow • Adding Task Questions • Setting Task Viewers • Applying Task Attributes • Working With Task Rules • Viewing Task History Chapter 12 Managing Tasks 12-79
- 333. Applying Task Attributes To locate tasks in the system, you can apply attributes to the task. When you 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 of North, 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. Click Add, then enter the following: • 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 numeric value for Formatted Number attribute, a List for List attribute, multiple lines of displayed 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 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 the dashboards, list views, or reports. – Allow Edits: Has the ability to add, change, and remove values for the attribute, but subject to the editability rules. – Required: Requires a value for the attribute. 2. Click OK. 3. See also: • Setting Task Properties • Setting Task Parameters • Specifying Task Instructions • Selecting the Workflow • Adding Task Questions • Setting Task Viewers • Setting Task Predecessors • Working With Task Rules • Viewing Task History Chapter 12 Managing Tasks 12-80
- 334. Working With Task Rules Task rules affect task behavior. These rules enable users to assign rules directly to tasks, especially when, because a rule is unique to a task, assigning rules isn’t appropriate at the Template, Schedule, or Task Type level. These rules apply to the Tasks for which the rules were configured. Available task rules: • Auto Approve Task: Automatically completes specified approvals only if specified conditions have been met. 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 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. When conditions are satisfied, the assignee role is marked as complete, thus progressing 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 Approval: Prevents approval of a task based on attribute values, or other characteristics. This rule runs when the Approver clicks Approve. • Prevent Task Submission: Prevents submission of a task based on attribute values, or other characteristics. This rule runs when the Assignee clicks Submit. • Send Email on Update: This rule runs based on user actions on the task. Hence, you must set the conditions for the rule appropriately. The most common condition is to have a condition with the Status attribute or the Status Detailed attribute: – Status attribute: The only valid value that you can select is Closed. Pending, Open, and Error are all statuses that result from automated actions on the task. – Status Detailed attribute: The valid statuses are with the approver. To work with task rules: 1. On the Home page, click Tasks, and then Tasks. 2. Select the Rules tab to open a New Rule. You can view the following information: • Order: The order of precedence. • Rule: Name of the Rule • Conditions: The choice of what conditions must exist before running the rule 3. Under Rule, select the type of rule you want to use: • Auto Approve Task • Auto Submit Task • Prevent Task Submission Chapter 12 Managing Tasks 12-81
- 335. • Prevent Task Approval • Prevent Task Rejection • Send Email on Update • Select Create Filter and populate the conditions section or select Use Saved Filter, and then select a filter. The filter selected and configured for the rule determines the conditions that trigger the rule to apply. Note: When you make changes to a rule definition, the additional information is added to the audit log. You can view the changes both in the History tab as well as the Audit Report. 4. Optional: Under Description, explain why you configured the rule and how it should be used. 5. For Approver Level, select the rule for All Levels or select the Approver levels. 6. 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 the conditions associated with the saved filter. • Create Filter: The Condition section is enabled. Select the conditions that apply for the advanced filter: Conjunction, Source, Attribute, Operator, and Value. 7. Under Filter Task, select the task to which the conditions should be applied: Current Task, Any Predecessor, Specific Task (provide the Task ID). 8. See also: • Setting Task Properties • Setting Task Parameters • Specifying Task Instructions • Selecting the Workflow • Adding Task Questions • Setting Task Viewers • Setting Task Predecessors • Applying Task Attributes • Viewing Task History Viewing Task History For each task, the system retains a history of the changes made to it; for example, a shift 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, the user who made the change, and the date on which the change was made. The information on this tab is read-only. To view task history: Chapter 12 Managing Tasks 12-82
- 336. 1. On the Home page, click Tasks, and then Tasks. 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 Box You can view a list of tasks from the Schedule Tasks page. You can filter the available schedule list by date or status. To view the Tasks from the Schedule Tasks page: 1. On the Home page, click Tasks, and then Tasks. 2. For Schedule, select a schedule, or select All if you do not want to filter the list. 3. Optional: To filter the schedule list by year or period, select a Year and Period. 4. Optional: To filter the schedule list by status, from Schedule Status, select a status. 5. Select a task. 6. 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 7. Click Instructions to display any instructions. 8. Click Alerts to display current alerts. 9. Click Workflow to view assignees for the tesk. 10. Click Attributes to view any attributes for the task. 11. Click Questions to view any questions that have been posted for the task. 12. Click Comments to view any comments that have been posted for the task. Chapter 12 Managing Tasks 12-83
- 337. 13. Click Related Tasks to view any related tasks. You can view Predecessors or Successor tasks. 14. Click Parameters to view dashboard, cluster, application, and so on. 15. Click History to capture an audit trail of changes to the task. You can view the activity for the task, including All Activity, Last 7 Days, and Today. 16. Click Actions, then select one of the following actions: • Submit Task • Abort Task: Cancels a task. The purpose of canceling a task (instead of performing a forced close) is to prevent successors from continuing and to keep the process moving. • Force Close Task • Refresh 17. Click Close. Importing and Exporting Tasks Importing Tasks To import tasks: 1. On the Home page, click Tasks, and then Tasks. 2. Select a task, click Actions, and then Import Tasks. 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 import file. This option replaces the task detail with the detail that is in the file that you are importing. It does not affect other tasks in the schedule that are not specified in the import file. The system displays a warning that tasks in a schedule that match a task ID in the import file will be modified. If you do not want to overwrite the task, click Cancel. You can select the Keep Attachments checkbox to retain attachments to tasks that are being replaced. • 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 new attributes. You might also have made the same change to a large number of tasks, for example, adding a new attribute to 100 of 400 tasks. The update option is not a full replacement of the task details. Only details for the task properties specified in the file are updated. 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. • Delete: Deletes tasks and associated information based on a list of task IDs provided in a file. The required information to perform a delete is a file with a column of task IDs. 5. Select a Date Format. Chapter 12 Managing Tasks 12-84
- 338. Select a format from the drop-down list of allowed date formats. Date formats are not translated. By default, the date format is set to the locale date format of the exported file location. 6. Select a File Delimiter for the import file: Comma or Tab. Choose Other to specify any single character as the Other Delimiter. 7. Click Import. Exporting Tasks To export tasks: 1. On the Home page, click Tasks, and then Tasks. 2. Select a task, click Actions, and then select Export Tasks. 3. Select Export options: • Select All Tasks or Selected Tasks. • For Format, select Formatted data (visible columns only) or Unformatted data for future import. Note: If you are an Administrator or Power User, you can select the format. If you have User security rights, by default the Format option is Formatted data (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 Tasks You 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 has started. You can only change the duration or the end date. You also cannot edit instructions, questions, Assignee, or approver, and you cannot add, delete, or edit predecessors. You can reassign the Assignee or approver from the Task Actions workflow. To edit a task: 1. On the Home page, click Tasks, and highlight the task that you want to edit. The Edit icon is enabled. 2. Click the Edit icon. 3. To edit task attributes: Click the Attributes tab. To add an attribute, click the Add icon to display the Add Attribute Assignment dialog box, and then make the following selections: • Attribute: Select an attribute from the list of defined attributes. Chapter 12 Managing Tasks 12-85
- 339. • Type: This noneditable field is populated by the Attribute. • Value: Select a value associated with the type of attribute; for example, a numeric value for Formatted Number attribute, a List for List attribute, multiple lines of displayed 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 Attachments If 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 to attach 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. On the Home page, click Tasks, and then 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 Tasks From the Task List, you can sort tasks by ascending or descending order. You can sort by Schedule Name, Status, Owner, Start or End Date, or Duration. To sort tasks: 1. On the Home page, click Tasks, and then click Tasks. 2. Hover over a column header until the Sort icons display, and then click Sort Ascending or Sort Descending. Searching for Tasks You 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 scroll through the results using the Previous and Next buttons. To search for a task: 1. On the Home page, click Tasks, and then click Tasks. 2. Enter a task name in the Search field. Chapter 12 Managing Tasks 12-86
- 340. 3. Click Previous or Next to find the previous or next task that matches the search criteria. Moving Tasks You can use views to move tasks. For example, you can move tasks in the Gantt view. Note: Move is not available for parent tasks. To move a task: 1. On the Home page, click Tasks, and then click Tasks. 2. Select a task. 3. Right-click on the task and drag it to a new location, or cut, copy, and paste the task. 4. Navigate to the target destination for the task and click OK. Cutting, Copying, and Pasting Tasks You 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 modify the task that you are pasting. If you paste a task onto a parent task, the pasted task becomes a child of the parent task. If you paste a task onto a child task, the pasted task becomes a sibling of the child task. Note: Cut, Copy, and Paste features are not available for parent tasks. The Cut function 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 Actions, and then select: • Cut: Cuts the task and stores it on the clipboard. • Copy: Copies the task and stores it on the clipboard. 3. Right-click on the task, then select Paste, or from the main menu toolbar, click Actions, and then select Paste. The Task Details dialog box opens and enables you to make changes to the task that you are pasting. 4. Click OK to complete the paste operation. Chapter 12 Managing Tasks 12-87
- 341. The task is inserted and the views and filter views are refreshed to display the pasted task. Reopening Tasks You can reopen tasks and choose to reestablish the predecessor and successor relationships.This is available on both manual end user tasks as well as automated tasks. Reopening an automated task will execute the task with the same parameters. If modifications to the automated task parameters are required, edit the closed automated task and select Reopen Task. Reopening a Manual Task To reopen a task: 1. On the Home page, click Tasks, and then Tasks. 2. Select a closed task and click Open or click on the task name. 3. On the Action dialog, select Reopen Task from the Actions menu. You can choose which successors to automatically reopen and restore the predecessor links when a task is reopened. From the list of these successor tasks, you can choose all of them, none (default), or some subset for reopening. Table 12-5 Successor Type - Use Case Example Successor Type Description Use Case Example Direct Successors The simplest case is a single line of successors and is likely to be the most common case. Each Closed or Errored (less likely) task that is a successor of the task to be reopened is eligible to be reopened If Task A is reopened, 'Task B', 'Task C' and 'Task D' are available to be reopened. Mixed Status Successors Once an Open or Pending task is encountered, it and any subsequent tasks are not eligible to be reopened. If Task A is reopened, only 'Task B' is available to be reopened. Multiple Successors A task can have more than one successor. Each branch should be followed to determine eligible tasks. This should extend all the way down the tree. If Task A is reopened, 'Task B', 'Task C', 'Task D' and 'Task E' are available to be reopened. Chapter 12 Managing Tasks 12-88
- 342. Table 12-5 (Cont.) Successor Type - Use Case Example Successor Type Description Use Case Example Parent Tasks Parent tasks will be automatically be reopened if they were closed prior to their child task re-opening. In this case, any successor tasks of the parent are eligible to be reopened. If Task A is reopened, 'Task B', 'Task C', 'Task D' and 'Task E' are available to be reopened. 'Parent A' is automatically reopened. • If there are no eligible successor tasks, the Reopen Tasks dialog displays a confirmation message prompting you to reopen the specified task. – Click Yes, to close the dialog and reopen the task. – Click No, to close the dialog without reopening the task. • If there are eligible successors to the task to be reopened, the Reopen Tasks dialog displays a confirmation message listing the successors with checkboxes, and you can select them to reopen. – Name checkbox: Selecting the Name checkbox toggles between selecting all or selecting none of the successors. By default, this is unchecked and all of the tasks are unchecked. – Successor Name: Selecting a checkbox next to a successor task will cause it to reset when the task reopens. Chapter 12 Managing Tasks 12-89
- 343. – Generation: Read-only field indicating the distance from the task being reopened. Parent tasks will not count as part of this calculation. – Relationship: Read-only field displaying the relationship to the task being reopened. – Click Yes to close the dialog and reopen the task. – Click No, to close the dialog without re-opening the task 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-establish predecessor 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 based on your selections. Click OK, otherwise, click Cancel. Reopening an Automated Task To reopen an automated task and change the automation parameters: 1. On the Home page, click Tasks, and then Tasks. 2. Select a closed automated task and click the Edit icon. 3. On the Task Details dialog, click Reopen. The Task is now editable. 4. Click on the parameters tab and update parameters as needed. 5. Click Save and Close. The service will display a confirmation message to reopen the automated task. • Click Yes, to close the dialog and reopen the task. • Click No, to close the dialog without reopening the task. If there are eligible successors to the task to be reopened, the Reopen Tasks dialog displays a confirmation message listing the successors with checkboxes, and you can select them to reopen. See the previous section Reopening a Manual Task. Submitting Tasks To submit tasks: 1. On the Home page, click Tasks, and then click Tasks. 2. Select the tasks that you need to submit. To multiselect, press Ctrl for random selection or press Shift while you click the first and last row in a range. 3. Select Submit Task. A warning is displayed that this will complete the task. Click Yes to proceed. Chapter 12 Managing Tasks 12-90
- 344. 4. Review any errors, and click OK. Approving or Rejecting Tasks To approve or reject tasks: 1. On the Home page, click Tasks, and then click Tasks. 2. Select the tasks that you need to submit. To multiselect, press Ctrl for random selection or press Shift while you click the first and last row in a range. 3. Highlight the selected Task, and under Actions, select Set Status, and then select Approve or Reject. 4. Review any errors, and click OK. Managing Task Reassignments You can use the Actions panel to work on multiple tasks simultaneously. From the Task Actions dialog box, workflow users (Assignees and Approvers) can request reassignment of their workflow role for a single task. These requests require approval. Administrators and schedule/template Owners can reassign the task using the Edit Task dialog box without requiring approval. When tasks are reassigned, email notifications are sent immediately to reassigned users. To request a reassignment: 1. On the Home page, click Tasks, and then click Tasks. 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 To User. 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. Canceling Tasks The purpose of canceling (or aborting) a task (instead of performing a forced close) is to prevent successors from continuing and to keep the process moving: • When a Finish-to-Start or Finish-Error-to-Start predecessor is canceled, its successors remain as Pending. To keep the process moving, you must edit the successors to remove the canceled predecessor and to start the successors. • When a Finish-to-Finish or Finish-Error-to-Finish predecessor is canceled, to keep the process moving, the task owner/schedule owner/administrator must force a close of the successor. Chapter 12 Managing Tasks 12-91
- 345. Deleting Tasks You can delete tasks that you no longer need. To delete a task, you must have Service Administrator or Power User security rights. In schedules, you can delete only tasks that have a status of Pending. You cannot delete tasks that have a status of Open or Closed. If you delete a parent task, you can choose 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 not appear in the menu when the task is open or completed.) To delete a task: 1. On the Home page, click Tasks, and then click Tasks. 2. Click Actions, and then select Delete. 3. At the confirmation prompt, click Yes. Managing Services The Services (Homepage > Application > Services) option allows you to view the status of certain service related tasks. Green indicates that it's running. Actions to take from Services are Run Now or Restart. Note: You can use Run Now to take an immediate action such as run open tasks. You should only use Restart if there was a service shutdown and this option is not green. Restart resets the service without running the service itself. • System Maintenance: Refers to actions that Task Manager performs routinely within Tasks, such as the user synch process and cleanup of the database and is not the same as actions taken at the Cloud level called Daily Maintenance. Daily Maintenance is accessed by clicking Tools, then Daily Maintenance, includes actions such as operational maintenance and backup snapshots performed in the Cloud on test or production environments. • Task Email Notifications: Used to notify users that work has been assigned to them. A Service Administrator can use the option on Services to Restart or Run Now. Note: – There is a separate option that a Service Administrator can use to turn off email notifications under Application → Configuration → Settings → System Maintenance Process. – Email notifications contain service and tenant information in the footer to help identify where an email is coming from. Chapter 12 Managing Tasks 12-92
- 346. • [Schedule Name] Monitor: Available for each schedule that is open and with tasks in the future. This option checks if any tasks need to be open in a schedule. • Task Status Update: Background service which executes and monitors the process automated tasks. Managing Schedules A schedule defines a chronologically ordered set of tasks that must be executed for a specific business process, and is the application of a template into the calendar. For example, you can apply the Quarterly template as Q1FY19 for the first Quarter, then apply the template again as Q2FY19 for the second quarter. The maximum number of schedules that you can create, import, or deploy is 100,000. Schedules have a status of Pending, Open, Closed, or Locked. You can change the status 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. • Schedule Owners and Viewers are notified by an email when a Schedule is deleted. • An immediate reassignment request notification is sent out to administrators and schedule owners when an assignee or approver requests a reassignment. Manually Creating Schedules To create a schedule, you must be an Administrator or Power User. A Power User can run Create Schedule on a template or select New from Manage Schedules. You can manually define a schedule from the Manage Schedules page, or create a schedule from a template. When you create a schedule from a template, all values are inherited from 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 Application. 2. Click Task Manager. 3. Click the Schedules tab on the left. 4. Click New. 5. Enter schedule information on the schedule tabs: • Setting Schedule Properties Chapter 12 Managing Schedules 12-93
- 347. • Adding Instructions to Schedules • Assigning Schedule Viewers • Applying Schedule Attributes • Adding Day Labels • Working With Schedule Rules • Viewing Schedule History Setting Schedule Properties The Properties tab enables you to set the name, description, start and end dates, and owners 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 date range for the schedule, however, after the schedule is created, you can add tasks with dates earlier or later and the properties are updated to reflect the earliest and latest dates. To set schedule properties: 1. Create a new schedule and select the Properties tab: • Name: You can enter a maximum of 80 characters. • Description: You can enter a maximum of 255 characters. • Organizational Unit • 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 • Owner: Use the default owner or click Select Owner . • Status Note: The Status field does not display until the new schedule is saved. The schedule status is initially set to Pending and is display only. • Source Template 2. To save and close, click OK or click another tab; all entries are saved. 3. Enter schedule information on the schedule tabs: • Adding Instructions to Schedules • Assigning Schedule Viewers • Applying Schedule Attributes • Adding Day Labels Chapter 12 Managing Schedules 12-94
- 348. • Working With Schedule Rules • Viewing Schedule History Adding Instructions to Schedules You can specify instructions and supporting documents for a schedule, which are then inherited 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 Reference Type list, select one of these types: • Local File: Click Choose File to select and attach the file, enter a Name, and click OK. • URL: Enter the URL, then enter a URL Name; for example, http://www.oracle.com, Oracle, and then click OK. 4. To save and close, click OK or click the Viewers tab; all entries are saved. 5. Enter schedule information on the schedule tabs: • Setting Schedule Properties • Assigning Schedule Viewers • Applying Schedule Attributes • Adding Day Labels • Working With Schedule Rules • Viewing Schedule History Assigning Schedule Viewers The Viewers tab enables you to assign viewer rights for schedules. A schedule can have multiple viewers, however they must have the product security roles. Viewers receive read- only access to all tasks in the schedule. Note: Only users who have the task Viewer role can respond to questions. To assign viewer rights: 1. Create a new schedule and select the Viewers tab. 2. Click Add. Chapter 12 Managing Schedules 12-95
- 349. 3. To search by users or groups, click the Search Users button, then select Users or Groups . 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 or Email . 6. From the Search Results list, select users. 7. For additional details about the user, such as groups, roles, and assignments, click Details. 8. Click Add or Add All to move users to the Selected list. 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. 10. Enter schedule information on the schedule tabs: • Setting Schedule Properties • Adding Instructions to Schedules • Applying Schedule Attributes • Adding Day Labels • Working With Schedule Rules • Viewing Schedule History Applying Schedule Attributes To locate schedules in the system, you can apply attributes to the schedule. When you 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 of North, South, East, and West. The current schedule applies only to the West Sales Region, so you can add the Sales Region attribute and set it to "West". To apply an attribute: 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: • Setting Schedule Properties • Adding Instructions to Schedules • Assigning Schedule Viewers Chapter 12 Managing Schedules 12-96
- 350. • Adding Day Labels • Working With Schedule Rules • Viewing Schedule History Adding Day Labels You use business day labels in the business activity for a calendar day. Labels can mark a milestone day or specify the purpose of the day. To add a day label to a schedule: 1. Create a new schedule and select the Day Labels tab. You can enter a maximum of 20 characters. 2. Add a day label to a specific date. 3. To save and close, click OK or click the Rules tab; all entries are saved. 4. Enter schedule information on the schedule tabs: • Setting Schedule Properties • Adding Instructions to Schedules • Assigning Schedule Viewers • Applying Schedule Attributes • Working With Schedule Rules • Viewing Schedule History Working With Schedule Rules Schedule rules apply to all tasks in the schedule and thus apply rules to groups of tasks. Rules configured in the Schedule dialog box are copied to new schedule tasks. Available schedule rules: • Auto Approve Task: Automatically completes specified approvals only if specified conditions have been met. Example of conditions that could apply to this rule include: Attributes have specified values (including calculated attributes). When conditions are satisfied, the specified approver levels are marked complete, and workflow progresses to the next approval level, or closes if no additional approval levels exist. • Auto Submit Task: Automatically submits a task if specified conditions are met. When conditions are satisfied, the Assignee role is marked complete, and workflow progresses to the first Approval level, or closes if no Approval levels exist. • Prevent Task Approval: Prevents approval of a task based on attribute values, or other characteristics. • Prevent Task Submission: Prevents submission of a task based on attribute values, or other characteristics. To view schedule rules: 1. On the Home page, click Application, and then click Task Manager. Chapter 12 Managing Schedules 12-97
- 351. 2. Click the Schedules tab on the left. 3. Double-click a schedule. 4. Select the Rules tab. You can view the following information: • Order: The order of precedence • Rule: The 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 it should be used. You can enter a maximum of 255 characters. • Approver Level: Select the rule for all levels or select the Approver levels. • Select Create Filter and populate the conditions section, or select Use Saved Filter, and then select a filter. The filter selected and configured for the rule determines the conditions that triggers the rule to apply. • Conditions: – Use Saved Filter: The Condition section displays a read-only version of the conditions associated with the saved filter. – Create Filter: The Condition section is enabled. Conjunction, Source, Attribute, Operator, and Value behave as they do for the existing advanced filter feature. • For Filter Task, specify the task for which the conditions should be selected: – Current Task – Any Predecessor – Specific Task (provide the Task ID) Note: When you make changes to a rule definition, the additional information is added to the audit log. You can view the changes both in the History tab as well as the Audit Report. 6. Enter schedule information on the schedule tabs: • Setting Schedule Properties • Adding Instructions to Schedules • Assigning Schedule Viewers • Applying Schedule Attributes • Adding Day Labels • Viewing Schedule History Chapter 12 Managing Schedules 12-98
- 352. Setting Required Task Parameters The task is in a pending state until the required parameters are filled in. If they are not filled in before the specified start date, then an email notification is sent to the task owner. In addition, the task shows up in views under Needs Attention. After the required parameters are filled in, the task starts. Opening Schedules You open schedules to add, edit, or work on tasks. To open a schedule: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Schedules tab on the left. 3. Use one of these methods: • Select Actions to the right of the schedule in the listing, and then select View. • Highlight a schedule, then click the View icon. • Right-click the highlighted schedule, and then select View. Editing Schedules You can edit schedules to change the properties, such as the name or the schedule or the start and end dates. You cannot change the start date to a date later than the first task in the schedule, or the end date to a date earlier than the last task in the schedule. You can make changes to an Open or Pending schedule to modify pending tasks. You cannot add, change, or delete tasks in a Closed or Locked schedule. To edit a schedule, you must be the schedule owner or an Administrator. To edit a schedule: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Schedules tab on the left. 3. Select a schedule and click Edit. 4. Edit the schedule. 5. Click OK. Adding Tasks to Schedules You can add tasks to a schedule if it is Pending or Open. You cannot add tasks to a Closed or Locked schedule. Note: The maximum number of tasks that you can add to a Task Manager schedule is 500,000. Chapter 12 Managing Schedules 12-99
- 353. To add a task to a schedule: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Schedules tab on the left. 3. Open a schedule. 4. Add tasks. Importing Tasks into Schedules You can import tasks, or partial task data, from text files into a schedule with a status of Pending or Open. For example, if you have a Microsoft Excel spreadsheet with task definitions, you can save the file as a CSV file, then import it into a schedule. You can also use the Import feature to quickly add many repetitive tasks by editing the fields in a CSV file and importing it, rather than creating individual new tasks. You cannot import tasks into schedules that have a Closed or Locked status. Note: Before you import a file to a schedule using the Update option for a closed task, remove the Owner, Assignee, Approver, and Start Date and Time fields from the import file, or an error occurs. If you import information on an End-User task that has started running, it is reset to Open with Assignee status, and the answers to questions are cleared. To import tasks into a schedule: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Schedules tab on the left. 3. Click Import Tasks. 4. Enter the name of the file to import, or click Choose File to find the file. 5. Select an import option: • Replace: Replaces the definition of a task with the definition in the import file. This option replaces the task detail with the detail that is in the file that you are importing. It does not affect other tasks in the schedule that are not specified in the import file. Note: You can select the Keep Attachments checkbox to retain attachments to tasks that are being replaced. • 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 new attributes. You might also have made the same change to a large number of Chapter 12 Managing Schedules 12-100
- 354. tasks, for example, adding a new attribute to 100 of 400 tasks. The update option is not a full replacement of the task details. Only details for the task properties specified in the file are updated. 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. Note: The system displays a warning that tasks in the schedule that match a task ID in the import file will be modified. If you do not want to overwrite the task, click Cancel. • Delete: Deletes tasks and associated information based on a list of task IDs provided in a file. The required information to perform a delete is a file with a column of task IDs. 6. Optional: Select Keep Attachments to retain any attachments associated with a task that is being replaced. 7. Select a Date Format. Select a format from the drop-down list of allowed date formats. Date formats are not translated. By default, the date format is set to the locale date format of the exported file location. 8. For File Delimiter for the import file, select Comma or Tab. Select Other to specify any single character as the Other Delimiter. 9. 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, and the total number of tasks imported. Click OK. • If errors are found, the import process is not run, and the Import Errors dialog box displays the errors. View the errors, then click OK to return to the Schedules page. Table 12-6 Troubleshooting Import Errors Error Resolution Duplicate Task ID Check for duplicate Task IDs. Task IDs must be unique within the template or schedule. See Creating Tasks. Task Name is too long The Task Name can contain a maximum of 80 characters. See Setting Task Properties. Organizational value - "Invalid Value" The Organizational value cannot be blank, contain bullet points or multiple lines. Updating Tasks in Schedules You may need to manually update information on a task that is running, and in this case, you can reopen it. When you reopen a task, it is reset to Open with Assignee status, and you can edit the information. For example, you can change the instructions and references, attributes, and questions. If you make changes, previous answers to questions are cleared. Chapter 12 Managing Schedules 12-101
- 355. Reopening a series of tasks does not reestablish the predecessor relationships. All end-user tasks are reset to Open with Assignee. No tasks are reverted to Pending status. You can reopen tasks under these conditions: Table 12-7 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 reset to the Assignee, and the answers to questions are cleared. 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 questions are cleared. Closed/Error From Task Details, the task owner can click Reopen to reopen the task and make changes. When you save the task, it is reset to the Assignee. To update tasks in a schedule: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Schedules tab on the left. 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. 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. 8. Perform an action: • For a Closed task, click Close. • For an Error task, click Save and Close. Reassigning Users in Schedules You may periodically need to reassign users to different schedules. For example, you may create a schedule and assign a user to certain rights; however, later that employee leaves the company and another employee assumes those schedules. You can use the Reassign feature in the Schedules dialog box to automatically change assignments instead of manually searching for, opening, and editing individual schedules. The Reassign feature enables you to quickly find the schedules associated with one user and reassign them to another. You can reassign users for multiple schedules at a time. This can be helpful if your application has a large number of schedules. To reassign users: Chapter 12 Managing Schedules 12-102
- 356. 1. On the Home page, click Application, and then click Task Manager. 2. Click the Schedules tab on the left. 3. Select one or more schedules for which you want to reassign users. 4. Click Actions, and then Reassign User. 5. For Find User, click Find User and enter 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. For Replace With, click the Replace With icon and enter search criteria for the user to whom you want to reassign tasks: 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. 7. Select the Ending Between dates. 8. Select roles for the user that must be reassigned: • Owner • Assignee • Approver • Viewer 9. Click Reassign. When the process ends, the system displays a Reassign Users - Success message that indicates that the user reassignment is complete, and displays the schedule name and total number of user reassignments made. Authorizing Process-Automated Tasks When you create Process-Automated tasks, for security purposes, you specify a user account under which the task is run. To preserve security, you may require authorization to perform the task if any of these conditions occurs: • If you add a Process-Automated task with an alternate runtime user known as the Run As user to a schedule, from a template or by manually adding the task • When you set a schedule to Open status, the system automatically issues a request for authorization if it has not been completed. If the parameters of a task are modified by a user other than the Assignee (or task owner if the owner is also the Assignee), the authorization is reset to Unauthorized and must be obtained by entering a password. For Process-Automated tasks, if a user other than the specified or default Run As user modifies the parameters, the task is reset to Unauthorized. Authorization ensures that the user performing the Process Automated task has security privileges for the application and data for which the task runs. An administrator who knows the credentials of the runtime user can perform the authorization or issue a request to the user to obtain authorization. When the Process Automated task is scheduled to run, if authorization is not provided, the task is not run, and its status changes to Needs Attention. If an owner or Assignee edits the Chapter 12 Managing Schedules 12-103
- 357. task, the task details indicate that authorization is required. In this case, only the Run As user can authorize the task. A user who receives a request for authorization can access the authorization on the Worklist from a link in the email or by logging on to the application. Note: From a Schedule or from a Worklist, before the task Start Date, the Administrator, Schedule Owner, or Task Owner can authorize the task. After the task Start Date, only the Run As user can authorize the task. To authorize a task: 1. On the Home page, click Application, and then click Task Manager 2. Select the Schedules tab on the left. 3. Select a schedule. 4. Select Actions, and then select Authorize Tasks. The system displays a Users selection list and a table of unauthorized tasks for the selected schedule. The user selection list is populated with users that have pending Process-Automated tasks assigned to them that require authorization. 5. From the user selection list, select a user. The system displays a list of unauthorized tasks for that user. Your user name displays first on the list in bold by default. If you have no unauthorized tasks, the list is blank. 6. Select a task that needs authorization. 7. To view task details, click a task name and review the task parameters. Tip: To contact the task owner by email, click the Owner name next to the task and view the user details. Setting Schedule Status You manage the schedule lifecycle by setting the schedule status. You can set the status of a schedule to Open, Closed, or Locked, depending on its current status. To set 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 your application has a large number of schedules. These are the available statuses: • Pending: The schedule is not yet active. This is the default status of the schedule when it is created. For a schedule in Pending status, you cannot close or lock the schedule. Chapter 12 Managing Schedules 12-104
- 358. • Open: The schedule is open for work to be performed. Tasks in the schedule can be run. • Closed: The schedule is no longer active but follow-up work may be required. Tasks in the schedule continue to proceed based on their definitions, but you cannot add tasks to the schedule. Schedule owners or administrators can reopen a Closed schedule, which changes its status to Open. • Locked: The schedule is locked and cannot be modified. You can reopen a locked schedule, if required. When you create a schedule, it has a status of Pending by default so that you can make final adjustments to it, and add, edit, or delete tasks. To run a schedule, you change the status from Pending to Open. When the schedule is opened, tasks begin to execute according to their definition. Status for tasks that have met their starting condition are set to Open, and task notifications are sent to their Assignees. Note: If a schedule task start time is reached and authorization has not been provided for a system-automated task, the task remains in the Pending status and requires authorization. When work on the schedule has reached a stage when follow-up work is all that is required, you set the status to Closed. You cannot add new tasks to a Closed schedule, however users can continue to work on tasks that are not complete. You can 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 Locked schedule, but you can set the status back to Open, if required. To set schedule status: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Schedules tab on the left. 3. Select one or more schedules for which to set status. 4. Click 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 History The system maintains a history of schedule actions, which you can view from the Edit Schedules dialog box. The History tab displays the components that were updated, the modification type, the old and new values, the user who made the modification, and the change date. The information is read-only. To view schedule history: 1. On the Home page, click Application, and then click Task Manager. Chapter 12 Managing Schedules 12-105
- 359. 2. Click the Schedules tab on the left. 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 the user who modified the schedule • Old Value • New Value 5. Click OK. Validating Schedules You can validate schedules with a status of Pending or Open. Validating a schedule checks for problems with start and end dates, predecessor relationships, parent-child relationships, and missing task parameters for product integrations. You cannot change a schedule status from Pending to Open until all validation errors are resolved. To validate schedules, you must be the schedule owner or Service Administrator. The validation results show the schedule names, status, and error messages. You can sort the results by Schedule Name or Status. To validate schedules: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Schedules tab on the left. 3. Select one or more schedules to validate. 4. Click Actions, and then select Validate. If no errors exist, the validation results show a "Schedule is valid " message. If errors exist, it shows the error details. Locking Schedules You can lock a schedule to prevent users from making further changes. To lock a schedule: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Schedules tab on the left. 3. From the list of schedules, select a schedule. 4. Select the Actions icon to the right of the schedule in the listing, and then select Set Status, or from the Set Status dropdown, select Locked. 5. Optional: If you need to reopen the Locked schedule, select Actions, and then Set Status, or from the Set Status dropdown, select Open. Chapter 12 Managing Schedules 12-106
- 360. Viewing Schedules In Schedules, you can specify which columns to display for the list of schedules, or show all. You can also reorder columns, sort columns by ascending or descending order, or change the column widths. To display columns: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Schedules tab on the left. 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 then select or deselect the column names. • To reorder columns, select View, then Reorder Columns, select columns, and then 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 are displayed, and then click Sort Ascending or Sort Descending. • To change column widths, hover over the column header dividers until the arrows display, and drag the columns to the desired width. Searching for Schedules You can use the Search text box in a Schedules list to quickly find schedules. You can enter full or partial names on which to search. Using the filter bar, you can control the schedules that you see in the list. By default, all schedules are displayed. To search for a schedule: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Schedules tab on the left. 3. To search for a schedule, enter search criteria in the Search text box. 4. Optional: From the filter bar, click on a category to display additional search operators such as Equals, Does Not Equal, Contains, Does Not Contain, Starts With, and Ends With. You can filter schedules using these categories: Name, Year, Period, Status, Start Date, and End Date. Click Add a Filter to add additional filters: Created By, Created On, Day Zero Date, Description, Last Updated By, Last Updated on, Organizational Unit, Owner, and Tasks. Chapter 12 Managing Schedules 12-107
- 361. Note: • Click Add a Filter to view all categories. • To hide the filter bar, click the Filter icon. • To clear all filters, click Clear All Filters in the icon. Deleting Schedules You can delete a schedule that you no longer need. To delete a schedule, you must be the schedule owner or Service Administrator. Deleting a schedule removes it and all references to it from the system. To delete a schedule: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Schedules tab on the left. 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 also permanently delete all tasks within the schedule, and the only way to recover is from a backup. 5. To delete the schedule, click Yes. Managing Task Manager Integrations You can enable Task Manager tasks to include integrations within the EPM Cloud and other external applications. Task Manager allows the user to incorporate integrated tasks within their business processes. These simplify the process by automating manual tasks or including embedded application pages or links. To manage Task Manager Integrations, you must have the Service Administrator role. Task Manager support the following Integration types: End User An End User integrated task requires the user to interact with an application web page. These application web pages are displayed within the task or included as links within the task. An Integration requires an execution URL for user tasks and an optional set of parameters. The execution URL launches the external program, and the parameters pass information required for the task to the external program. For example, the Approve Journals Integration contains parameters such as the Point of View dimension values for the journal. Chapter 12 Managing Task Manager Integrations 12-108
- 362. Users must perform and validate the task. For example, the task may be a generic task such as submitting data, or it may require product integration to facilitate or validate its completion. Process Automation A Process Automation task initiates an action within the connected application. These integrations are automatically executed in external applications when their Start date and time are reached, and their predecessor tasks are completed, for example, an overnight feed from a General Ledger. These tasks are often executed after working hours. They require limited user interaction and do not have Assignees. Event Monitoring An Event Monitoring task is a task which is passive. It does not initiate any action but monitors another application awaiting for an action or status to occur. Once the action or status occurs, the task is marked complete. These are based on events that occur in external applications, for example Approve Journals. Task Manager provides these pre-built Integrations: • Cloud Integrations: End User and Process Automation integrations for EPM Cloud Connections. See Managing Integrations with EPM Cloud Services. • Cloud Integrations: Oracle Cloud ERP. See Managing Integrations with Cloud and On- Premises Applications. • On-Premises End User and Event Monitoring Integrations. See Managing Integrations with Cloud and On-Premises Applications. • On-Premises Oracle E-Business Suite General Ledger, Accounts Payable, and Accounts Receivable Integrations. See Managing Integrations with Cloud and On-Premises Applications. If you require any other Integrations for Cloud or On Premises, you can create Custom Integrations. See Creating Custom Integrations. Managing Integrations with EPM Cloud 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 Task Manager functionality. Pre-built integrations enable you to perform Task Manager tasks that access other EPM Cloud functionality. Pre-built integrations are provided within Task Manager for these EPM Cloud services: • Account Reconciliation • Enterprise Data Management • Financial Consolidation and Close • Planning and Planning Modules • Profitability and Cost Management • Tax Reporting To learn more about how to set up integrations, see Adding Pre-built Integrations within the EPM Cloud. Chapter 12 Managing Task Manager Integrations 12-109
- 363. To learn more about which end user integrations are available, see End User Integrations for EPM Cloud. To learn more about which pre-built automated integrations are available, see Automation Integrations for EPM Cloud. Adding Pre-built Integrations within the EPM Cloud Make sure you have the prerequisites and follow these steps to set up an integration between Task Manager and other EPM Cloud services. Prerequisite To create integrations between EPM Cloud services, you need to obtain a subscription to the EPM Cloud service you want to integrate with. To Create the Integration Type and Task Type You can add EPM Cloud integrations by adding a connection to the other EPM Cloud services and then deploy the Integrations and Task Types. To add Pre-built integrations within the EPM Cloud: 1. Create the connection between the service which contains Task Manager and the other service: • On the Home page, click Tools, and then click Connections. • Click Create to create a new connection: – For Enterprise Data Management, select Other Web Service Provider. – For all other EPM services, select Oracle Enterprise Performance Management Cloud provider. • Name the EPM Connect connection. For example, if integrating with Planning, a possible Connection Name could be PBCS . • Specify the connection URL. • Specify the user credentials. • Additionally for Other Web Service Provider, you must specify advanced options. Click Show Advanced Options. – For Type, select Parameter. – For Name, enter SERVICE_TYPE (this is a fixed value). – For Value, enter EDMCS (this is a fixed value). For more information about connecting EPM Cloud subscriptions, see Connecting Environments in EPM Cloud . 2. On the Home page, click Application, and then click Task Manager. 3. Click the Integrations tab on the left. 4. From the Integrations page, click Manage Connections. Chapter 12 Managing Task Manager Integrations 12-110
- 364. 5. On Manage Connections, from Actions, select Sync EPM Connections. A message displays the progress of the synchronization, and details the integrations added to the service. An Integration Type and Task Type is added for each Integration. See also: • End User Integrations for EPM Cloud • Automation Integrations for EPM Cloud End User Integrations for EPM Cloud End user integrations allow you to access functionality in other remote EPM Cloud environments while using Task Manager. This section lists the available end user integrations for these EPM Cloud services: • Account Reconciliation • Planning and Planning Modules • Financial Consolidation and Close and Tax Reporting • Profitability and Cost Management For a description of the remote EPM Cloud functionality, see the documentation for that EPM Cloud service. End User Integration Tasks for Account Reconciliation • Console • Reconciliation List (Period, Saved List) • Reports • Transaction List (Period, Saved List) Chapter 12 Managing Task Manager Integrations 12-111
- 365. 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 in Task Details dialog. • Export Data • Export Metadata • Export Journal • Generate Financial Report Required 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 down list 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 Task Details dialog. • Export Data • Export Metadata • Generate Financial Report Chapter 12 Managing Task Manager Integrations 12-112
- 366. Required parameter is the choice of report from drop down. • Import Data • Import Metadata • Invalid Intersections Report • Manage Approvals • Manage Dimensions • Manage Forms • Manage Periods • Manage Valid Intersections • Refresh Application • View Dashboard (Dashboard). Required parameter is Dashboard (EPM Artifact Type) displayed in the drop down list in the Task Details dialog • View Financial Reports 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 in Task Details dialog. • Generate Financial Report Required parameter is the choice of report from drop down. • Invalid Intersections Report • Manage Approvals • Manage Dimensions • Manage Rules • Manage Valid Intersections • View Dashboard (Dashboard). Required parameter is Dashboard (EPM Artifact Type) displayed in the drop down list in the Task Details dialog • View Financial Reports 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 list in Task Details dialog. • View Dashboard (Dashboard). Required parameter is Dashboard (EPM Artifact Type) displayed in the drop down list in the Task Details dialog. View Report (Report) Chapter 12 Managing Task Manager Integrations 12-113
- 367. Automation Integrations for EPM Cloud These pre-built integrations are available for EPM Cloud services: • Account Reconciliation • Enterprise Data Management • Financial Consolidation and Close • Planning and Planning Modules • Profitability and Cost Management • Tax Reporting To use the pre-built EPM Cloud Integrations, you must specify parameters for the integration. Many parameters for automated integrations are selectable from drop- down lists, which eliminates the need to manually enter values. For example, to run a rule or ruleset, you can select from a list of business rules, such as ForceConsolidate or ForceTranslate. Integrations for EPM Cloud (Common) Integration Name / Module Module Description Parameters/ Description Copy File from Planning All EPM Cloud Services except Enterprise Data Management Copies a file from current service where Task Manager is configured to another EPM Cloud Service. For example, if you have configured Task Manager in Planning and set up Account Reconciliation connection, Copy File from Planning copies the file from Planning to Account Reconciliation. • File Name: Name of the file that you want to copy. • Save File As: Name of the file that you want to save. This can be different than the original file name. • External Directory Name (Optional): Name of the directory. Copy File to Planning All EPM Cloud Services except Enterprise Data Management Copies a file to current service where Task Manager is configured from another EPM Cloud service. • File Name: Name of the file that you want to copy. • Save File As: Name of the filethat you want to save. This can be different than the original file name. • External Directory Name (Optional): Name of the directory. Delete File From Planning All EPM Cloud Services except Enterprise Data Management Deletes a file from a EPM cloud service. File Name: Name of the file that you want to delete. Chapter 12 Managing Task Manager Integrations 12-114
- 368. See also, Copy and Delete Integration Files Integrations for Account Reconciliation Integration Name / Module Module Description Parameters/ Description Change Period Status Reconciliation Compliance Changes the status of a period (Open, Closed, Pending, Locked). Period: The name of the period Status: Pending, Open, Closed, Locked Create Period End Reconciliations Reconciliation Compliance Copies all selected profiles to a period and returns success or failure status. Period: The name of the period Filter: The name of the filter that matches the reconciliation Import Balances Reconciliation Compliance Imports balance data using Data Management from a previously created Data Load definition. Period: The name of the period dl_Definition: The name of a previously saved data load using the format DL_name such as DL_test Import Pre-Mapped Balances Reconciliation Compliance Imports pre-mapped balances. Period: The name of the period BalanceType: SUB|SRC for sub system or source system CurrencyBucket: Currency bucket, such as Functional File: The name of the file relative to the inbox, for example, balances.csv. The file has to be uploaded to ARCS using EPM Automate or REST API. Import Pre-Mapped Transactions Reconciliation Compliance Imports pre-mapped transactions for a particular period. TransactionType: Allowed Transaction Types are BEX (Explained Balance), SRC (Adjustment to Source System), and SUB (Adjustment to Subsystem) File: The name of the file relative to the inbox, for example, transactions.csv. The file has to be uploaded to ARCS using EPM Automate or REST API. DateFormat: Date Format, such as MM/dd/yyyy, dd/MM/yyyy, dd-MMM-yy, MMM d,yyyy, or All. Chapter 12 Managing Task Manager Integrations 12-115
- 369. Integration Name / Module Module Description Parameters/ Description Import Pre-Mapped Transactions Transaction Matching Imports a file of pre- mapped transactions into Transaction Matching. DataSource: Text ID of the data source where the transaction will be imported to File: The name of the file relative to the inbox, for example, transactions.csv. The file has to be uploaded to ARCS using EPM Automate or REST API. ReconciliationType: Text ID of the reconciliation type where the transaction file will be imported to, such as Bank to GL. DateFormat: Date Format, such as MM/dd/yyyy, dd/MM/yyyy, MM-dd-yyyy, d-M-yyyy, dd-MMM-yy, MMM d, yyyy Import Profiles Reconciliation Compliance Imports profiles for a particular period. ImportType: The import type. Supported values are Replace and ReplaceAll Period: The period for which to import ProfileType: The profile type. Supported values are Profiles and Children File: The name of the file relative to the inbox, for example, profiles.csv. The file has to be uploaded to ARCS using EPM Automate or REST API. DateFormat: Date Format, such as MM/dd/yyyy, dd/MM/yyyy, d-M-yyyy, dd-MMM-yy, MMM d, yyyy, or All Chapter 12 Managing Task Manager Integrations 12-116
- 370. Integration Name / Module Module Description Parameters/ Description Import Rates Reconciliation Compliance Imports rates for a particular period and rate type. Period: The name of the period RateType: The rate type, such as Accounting Import Rates (Reconciliation Compliance) File: The name of the file relative to the inbox, for example, rates.csv. The file has to be uploaded to ARCS using EPM Automate or REST API. ImportType: Supported import types are Replace and ReplaceAll Monitor Reconciliations Reconciliation Compliance Monitors list of reconciliations in ARCS. Period: The name of the period Filter: Filter string used to query list of reconciliations Run Auto Match Transaction Matching Runs the auto match process in Transaction Matching. ReconTypeId: The Text ID of the Reconciliation type to be auto matched View Reconciliations Reconciliation Compliance View reconciliations for a specified period. Period: The name of the period Saved List: The name of a Public saved list View Transactions Transaction Matching View transactions for a specified period. Period: The name of the period Saved List: The name of a Public saved list Integrations for Enterprise Data Management Integration Name Description Parameters/ Description Export Dimension Exports a dimension from Enterprise Data Management to a configured connection. This is a process-automated integration. See Adding Pre-built Integrations within the EPM Cloud. Application: The name of the Enterprise Data Management application from which to export the dimension. Dimension: The name of the dimension to export. Connection: Optional. The name of the connection to which to export the dimension. File Name: The file and path from which to export the dimension. Chapter 12 Managing Task Manager Integrations 12-117
- 371. Integration Name Description Parameters/ Description Export Dimension Mapping Exports a Dimension Mapping from Enterprise Data Management to a configured connection. This is a process- automated integration. Application: The name of the Enterprise Data Management application from which to export the Dimension Mapping. Dimension: The name of the Dimension Mapping to export. Connection: Optional. The name of the connection to which to export the Dimension Mapping. Mapping Location: The location to which to export the Dimension Mapping. File Name: The file and path from which to export the Dimension Mapping. Import Dimension Imports a Dimension from a configured connection to an Enterprise Data Management application. This is a process- automated integration. See Adding Pre-built Integrations within the EPM Cloud. Application: The name of the Enterprise Data Management application to which to import the dimension. Dimension: The name of the dimension to import. Connection: The name of the connection from which to import the dimension. File Name: The file and path from which to import the dimension. Import Option: Optional. Determines how the data is imported into Enterprise Data Management. Extract Dimension Extracts a dimension from Enterprise Data Management to a configured connection. This is a process-automated integration. Application: The name of the Enterprise Data Management application from which to extract the dimension. Dimension: The name of the dimension to extract. Extract: The name of the extract. Connection: The name of the connection to which to extract the dimension. File Name: The file and path from which to extract the dimension. Integrations for Financial Consolidation and Close and Tax Reporting Integration Name Description Parameters/ Description Clear Cube Clears specific data within input and reporting cubes. Name: Name of the clear cube job. Chapter 12 Managing Task Manager Integrations 12-118
- 372. Integration Name Description Parameters/ Description Copy Ownership Data to Next Year Automates task to copy the ownership data from the last period of a year to the first period of the next year. For more information, see copyOwnershipDataToNextYe ar in Working with EPM Automate for Oracle Enterprise Performance Management Cloud . Scenario: The name of the scenario, such as Actual, selectable Years: Selectable Cube Refresh Refreshes the OLAP cube. Name: Name of the refresh cube job. Clear Data Executes a Clear Data job using the profile name. For more information about using Clear Data in Financial Consolidation and Close, see Clear Data. For more information about using Clear Data in Tax Reporting, see Clear Data. Profile Name: Clear data profile name. Copy Data Executes a Copy Data job using the profile name. For more information about using Copy Data in Financial Consolidation and Close, see Copy Data. For more information about using Copy Data in Tax Reporting, see Copy Data. Profile Name: Copy data profile name. Export Data Exports application data into a file using the export data settings, including file name, specified in a job of type export data. The file containing the exported data is stored in the repository. Name: Name of the export data job. Export File Name: Optional. File name to which data is to be exported. Export Data Mapping Exports a Data Mapping defined in Data Management to a specified location. This is a process- automated integration. For more information, see Adding Pre-built Integrations within the EPM Cloud. Member mappings define relationships between source members and target dimension members within a single dimension. Dimension: The dimension name for a specific dimension to import, such as ACCOUNT, or ALL to import all dimensions. File Name: The file and path from which to export mappings. The file format can be .CSV, .TXT, .XLS, or .XLSX. Include the outbox in the file path, for example, outbox/BESSAPPJan-06.csv. Location Name: The name of the location to which to export. Chapter 12 Managing Task Manager Integrations 12-119
- 373. Integration Name Description Parameters/ Description Export Ownership Data Automates task to export ownership data from a entity to a comma-delimited CSV file. For more information, see exportOwnershipData in Working with EPM Automate for Oracle Enterprise Performance Management Cloud . Entity: The name of the entity. Scenario: The name of the scenario, such as Actual. Selectable. Years: Selectable Period: The name of the period, such as January. Selectable. File Name: The name of the file to export. Import Data Imports data from a file in the repository into the application using the import data settings specified in a job of type import data. Name: Name of the import data job. Import File Name: Optional. File name from which data is to be imported. Chapter 12 Managing Task Manager Integrations 12-120
- 374. Integration Name Description Parameters/ Description Import Data Mapping Imports a Data Mapping defined in Data Management to a specified location. This is a process- automated integration. Member mappings define relationships between source members and target dimension members within a single dimension. You can import member mappings from a selected Excel, .CSV or .TXT file. Job Type: The job type, MAPPINGIMPORT. Job Name: The dimension name for a specific dimension to import, such as ACCOUNT, or ALL to import all dimensions. File Name: The file and path from which to import mappings. The file format can be .CSV, .TXT, .XLS, or .XLSX. The file must be uploaded prior to importing, either to the inbox or to a sub-directory of the inbox. Include the inbox in the file path, for example,inbox/ BESSAPPJan-06.csv. Import Mode: MERGE to add new rules or replace existing rules, or REPLACE to clear prior mapping rules before import. Validation Mode: Whether to use validation mode: true or false. An entry of true validates the target members against the target application; false loads the mapping file without any validations. Note that the validation process is resource intensive and takes longer than the validation mode of false; the option selected by most customers is false. Location Name: The Data Management location where the mapping rules should be loaded. Mapping rules are specific to a location in Data Management. Import Metadata Imports metadata from a file in the repository into the application using the import metadata settings specified in a job of type import metadata. Name: The name of a batch defined in import metadata. Chapter 12 Managing Task Manager Integrations 12-121
- 375. Integration Name Description Parameters/ Description Import Ownership Data Automates task to import ownership data from a CSV file available in the environment into a period. For more information, see importOwnershipData in Working with EPM Automate for Oracle Enterprise Performance Management Cloud . Scenario: The name of the scenario, such as Actual. Selectable. Years: Selectable Period: The name of the period, such as January. Selectable. File Name: The name of the file to import. Journal Period Opens or closes a journal period automatically. The system will close the period only if there are no Approved and Unposted journals. If there are Approved and Unposted journals, the system will not close the period, and returns an error. If there are Unposted journals in Working and Submitted status, the system will close the period, with a warning. Scenario: The name of the scenario, such as Actual Year: The year, such as FY20 Period: The name of the period, such as January Action: Open or Close Chapter 12 Managing Task Manager Integrations 12-122
- 376. Integration Name Description Parameters/ Description Monitor Enterprise Journals N o t e : T h i s i n t e g r a t i o n i s a p p l i c a b l e o n l y f o r F i n a n c i a l Monitors the completion status of Journals within a Year/Period or filtered list. Year: Optional. The year, such as 2022. Selectable. Period: Optional. The name of the period, such as January. Selectable. Filter Name: Optional.The name of the Filter you created to monitor the status of the Enterprise Journals. N o t e : T h o u g h a l l t h e p a r a m e t e r s a r e o p t i o n a l, y Chapter 12 Managing Task Manager Integrations 12-123
- 377. Integration Name Description Parameters/ Description C o n s o l i d a t i o n a n d C l o s e o u m u s t s p e c i f y a t l e a s t a F i l t e r N a m e o r Y e a r a n d P e r i o d . Chapter 12 Managing Task Manager Integrations 12-124
- 378. Integration Name Description Parameters/ Description Recompute Ownership Data Automates task for recomputing of ownership data. For more information, see recomputeOwnershipData in Working with EPM Automate for Oracle Enterprise Performance Management Cloud . Scenario: The name of the scenario, such as Actual Years: The year, such as FY20 Period: The name of the period, such as January Run Batch Rule Executes a batch of jobs that have been defined in Data Management. Name: The name of the report to be executed, such as Dimension Map For POV (Dimension, Cat, Per) Path Report Format Type: The file format of the report - PDF, XLSX, or HTML Parameters: Can vary in count and values based on the report Location: The location of the report, such as Comma_Vision Run As: You must specify this parameter in the Workflow tab. Run Business Rule Launches a business rule. Name: The name of a business rule exactly as it is defined. Parameters: Run time prompts in JSON syntax. Parameter name should exactly be same as defined in rule definition. For example, { "MyScenario1":"Current", "MyVersion1":"BU Version_1", "ToEntity":"CA", "Rule_Level_Var":"AZ", "planType":"Plan1"} Following format is also supported, example: "Scenario=Actual" "Entity=Total Geography" "Year=FY21" "Period=Apr" Chapter 12 Managing Task Manager Integrations 12-125
- 379. Integration Name Description Parameters/ Description Run Business Rule Set Launches a business rule set. Rule sets with no runtime prompts or runtime prompts with default values will be supported. Name:The name of a business rule set exactly as it is defined. Parameters: Run time prompts in JSON syntax. Parameter name should exactly be same as defined in rule definition. For example, { "MyScenario1":"Current", "MyVersion1":"BU Version_1", "ToEntity":"CA", "Rule_Level_Var":"AZ", "planType":"Plan1"} Following format is also supported, example: "Scenario=Actual" "Entity=Total Geography" "Year=FY21" "Period=Apr" Run Consolidation This task is a utility task to run consolidation. Task will prompt user to enter parameters for running the tasks such as Scenario, Year, Period and Entity. Scenario Year Period Entity: Multiple entities can be added with comma separator. Chapter 12 Managing Task Manager Integrations 12-126
- 380. Integration Name Description Parameters/ Description Run Data Rule Executes a Data Management data load rule based on the start period and end period, and import or export options that you specify. Job Name: The name of a data load rule defined in Data Management. Start Period: The first period for which data is to be loaded. This period name must be defined in Data Management period mapping. End Period: The last period for which data is to be loaded. This period name must be defined in Data Management period mapping. Import Mode: Determines how the data is imported into Data Management. APPEND to add to the existing rule POV data in Data Management REPLACE to delete the POV data and replace it with the data from the file RECALCULATE to skip importing the data, but re- process the data with updated Mappings and Logic Accounts. NONE to skip data import into Data Management staging table Export Mode: Determines how the data is exported into Data Management. STORE_DATA to merge the data in the Data Management staging table with the existing Financial Consolidation and Close or Tax Reporting data ADD_DATA to add the data in the Data Management staging table to Financial Consolidation and Close or Tax Reporting SUBTRACT_DATA to subtract the data in the Data Management staging table from existing Financial Consolidation and Close or Tax Reporting data REPLACE_DATA to clear the POV data and replace it with Chapter 12 Managing Task Manager Integrations 12-127
- 381. Integration Name Description Parameters/ Description data in the Data Management staging table. The data is cleared for Scenario, Version, Year, Period, and Entity NONE to skip data export from Data Management to Financial Consolidation and Close or Tax Reporting File Name: Optional. If you do not specify a file name, this API imports the data contained in the file name specified in the load data rule. The data file must already reside in the INBOX prior to data rule execution. Run As: You must specify this parameter in the Workflow tab. Run Force Consolidation This task is a utility task to run force consolidation. The task will prompt the user to enter parameters for running the tasks such as Scenario, Year, Period and Entity. Scenario Year Period Entity: Multiple entities can be added using a comma separator. Run Force Translation This task is a utility task to run force translation. The task will prompt user to enter parameters for running the tasks such as Scenario, Year, Period and Entity. Scenario Year Period Entity: Multiple entities can be added with comma separator. Run Translation This task is a utility task to run translation. The task will prompt user to enter parameters for running the tasks such as Scenario, Year, Period and Entity. Scenario Year Period Entity: Multiple entities can be added with comma separator. Chapter 12 Managing Task Manager Integrations 12-128
- 382. Integration Name Description Parameters/ Description Lock Unlock Data Integration Locks or unlocks an integration for a location, category and period in Data Exchange. This is a process- automated integration. Operation: Choose from lock or unlock. Lock Type: Choose whether the Lock/Unlock operation is for an application or a location. Period: Specify the period of the POV from the integration or data load rule defined in Data Exchange, for example, "Jan-21". Category: Specify the predefined Scenario value based on the POV Category from the integration (data rule) definition. The categories available are those that are created in the Data Integration set-up, such as "Actual." Application (Optional): If selected Lock Type is application, specify the name of application, for example, "Vision". Location (Optional): If selected Lock Type is location, specify the name of the location. If the location is locked, data cannot be loaded to it. Unlock By Location (Optional): This parameter can be specified when selected operation is lock and selected location is application. If checked when locking the target application, then the system locks all rules present in the location under target application and not the application-level lock. For more information, see Lock and Unlock POV Integrations for Planning and Planning Modules Integration Name Description Parameters/ Description Clear Cube Clears specific data within input and reporting cubes. Name: Name of the clear cube job. Chapter 12 Managing Task Manager Integrations 12-129
- 383. Integration Name Description Parameters/ Description Cube Refresh Refreshes the OLAP cube. Name: Name of the refresh cube job. Export Data Exports application data into a file using the export data settings, including file name, specified in a job of type export data. The file containing the exported data is stored in the repository. Name: Name of the export data job. Export File Name: Optional. File name to which data is to be exported. Import Data Imports data from a file in the repository into the application using the import data settings specified in a job of type import data. Name: Name of the import data job. Import File Name: Optional. File name from which data is to be imported. Import Metadata Imports metadata from a file in the repository into the application using the import metadata settings specified in a job of type import metadata. Name: The name of a batch defined in import metadata. Run Batch Executes a batch of jobs that have been defined in Data Management. Name: The name of the report to be executed, such as Dimension Map For POV (Dimension, Cat, Per) Path Report Format Type: The file format of the report, PDF, XLSX, or HTML Parameters: Can vary in count and values based on the report Location: The location of the report, such as Comma_Vision Run Business Rule Launches a business rule. Name: The name of a business rule exactly as it is defined. Parameters: Run time prompts in JSON syntax. Parameter name should exactly be same as defined in rule definition. For example, { "MyScenario1":"Current", "MyVersion1":"BU Version_1", "ToEntity":"CA", "Rule_Level_Var":"AZ", "planType":"Plan1"} Following format is also supported, example: "Scenario=Actual" "Entity=Total Geography" "Year=FY21" "Period=Apr" Chapter 12 Managing Task Manager Integrations 12-130
- 384. Integration Name Description Parameters/ Description Run Business Ruleset Launches a business ruleset. Rulesets with no runtime prompts or runtime prompts with default values will be supported. Name: The name of a business ruleset exactly as it is defined. Parameters: Run time prompts in JSON syntax. Parameter name should exactly be same as defined in rule definition. For example, { "MyScenario1":"Current", "MyVersion1":"BU Version_1", "ToEntity":"CA", "Rule_Level_Var":"AZ", "planType":"Plan1"} Following format is also supported, example: "Scenario=Actual" "Entity=Total Geography" "Year=FY21" "Period=Apr" Chapter 12 Managing Task Manager Integrations 12-131
- 385. Integration Name Description Parameters/ Description Run Data Rule Executes a Data Management data load rule based on the start period and end period, and import or export options that you specify. Job Name: The name of a data load rule defined in Data Management. Start Period: The first period for which data is to be loaded. This period name must be defined in Data Management period mapping. End Period: The last period for which data is to be loaded. This period name must be defined in Data Management period mapping. Import Mode: Determines how the data is imported into Data Management. APPEND to add to the existing rule POV data in Data Management REPLACE to delete the POV data and replace it with the data from the file RECALCULATE to skip importing the data, but re- process the data with updated Mappings and Logic Accounts. NONE to skip data import into Data Management staging table exportMode: Determines how the data is exported into Data Management. STORE_DATA to merge the data in the Data Management staging table with the existing Oracle Hyperion Planning data ADD_DATA to add the data in the Data Management staging table to Planning SUBTRACT_DATA to subtract the data in the Data Management staging table from existing Planning data REPLACE_DATA to clear the POV data and replace it with data in the Data Management staging table. The data is cleared for Scenario, Version, Year, Period, and Entity NONE to skip data export from Data Management to Planning File Name: Optional. If you do not specify a file name, this API imports the data Chapter 12 Managing Task Manager Integrations 12-132
- 386. Integration Name Description Parameters/ Description contained in the file name specified in the load data rule. The data file must already reside in the INBOX prior to data rule execution. Lock Unlock Data Integration Locks or unlocks an integration for a location, category and period in Data Exchange. This is a process- automated integration. Operation: Choose from lock or unlock. Lock Type: Choose whether the Lock/Unlock operation is for an application or a location. Period: Specify the period of the POV from the integration or data load rule defined in Data Exchange, for example, "Jan-21". Category: Specify the predefined Scenario value based on the POV Category from the integration (data rule) definition. The categories available are those that are created in the Data Integration set-up, such as "Actual." Application (Optional): If selected Lock Type is application, specify the name of application, for example, "Vision". Location (Optional): If selected Lock Type is location, specify the name of the location. If the location is locked, data cannot be loaded to it. Unlock By Location (Optional): This parameter can be specified when selected operation is lock and selected location is application. If checked when locking the target application, then the system locks all rules present in the location under target application and not the application-level lock. For more information, see Lock and Unlock POV Chapter 12 Managing Task Manager Integrations 12-133
- 387. Integrations for Profitability and Cost Management Integration Name Description Parameters/ Description Apply Data Grants Applies data grants for a given Oracle Profitability and Cost Management Cloud application. This API submits a job to create and apply the data grants in Essbase. This API removes all existing data grants in Essbase and recreates them with the latest information from the application. It can also be used to repair data grants if there are any issues. None Deploy ML Cube Deploy or redeploy the calculation cube for a selected Oracle Profitability and Cost Management Cloud application. isKeepData: Specify whether to preserve existing data isReplacecube: Specify whether to replace existing comment: Any user comments Chapter 12 Managing Task Manager Integrations 12-134
- 388. Integration Name Description Parameters/ Description Run ML Calc Run or clear calculations for a selected application. Use with Management Ledger. povGroupMember: The POV group member for which to run calculations, such as 2015_January_Actual isClearCalculated: Whether to clear the calculation data, true or false subsetStart: Rule Set Starting Sequence Number subsetEnd: Rule Set Ending Sequence Number Rule: Rule Name for a SINGLE_RULE ruleSetName: Rule Set Name for a SINGLE_RULE option exeType: The execution type specifies which rules to run; possible values are ALL_RULES, RULESET_SUBSET, SINGLE_RULE. Other parameters are required based on the exeType value. exeType: ALL_RULES overrides all other options such as subsetStart, subsetEnd, ruleSetName, ruleName, and so on. exeType: RULESET_SUBSET considers only subsetStart and subsetEnd. exeType: SINGLE_RULE considers only ruleSetName and ruleName. Comment: Use comment text. Delimiter: String delimiter for POV group members, such as an underscore (_). Chapter 12 Managing Task Manager Integrations 12-135
- 389. Integration Name Description Parameters/ Description Clear ML POV Clear model artifacts and data from a POV combination for any application. POV GroupMember: The POV group member for which to run calculations, such as 2015_January_Actual isManageRule: Whether to clear the program rule details isInputData: Whether to clear input data IsAllocatedValues: Whether to clear allocated values stringDelimiter: String delimiter for POV group members Copy ML POV Copy model artifacts and data from a Source POV combination to a Destination POV combination for any application. Use with Management Ledger applications. POVs: Included in the path srcPOVMemberGroup: Source POV member group, such as 2014_January_Actual destPOVMemberGroup: Destination POV member group, such as 2014_March_Actual isManageRule: Whether to copy the program rule details isInputData: Whether to copy input data modelViewName: To copy a slice of data from source POV to destination POV Create Dest POV: Whether to create the destination POV if it does not already exist String Delimiter: String delimiter for POV group members Chapter 12 Managing Task Manager Integrations 12-136
- 390. Integration Name Description Parameters/ Description Run Data Rule Executes a Data Management data load rule based on the start period and end period, and import or export options that you specify. Job Name: The name of a data load rule defined in Data Management. Start Period: The first period for which data is to be loaded. This period name must be defined in Data Management period mapping. End Period: The last period for which data is to be loaded. This period name must be defined in Data Management period mapping. Import Mode: Determines how the data is imported into Data Management. APPEND to add to the existing rule POV data in Data Management REPLACE to delete the POV data and replace it with the data from the file RECALCULATE to skip importing the data, but re- process the data with updated Mappings and Logic Accounts. NONE to skip data import into Data Management staging table Export Mode: Determines how the data is exported into Data Management. STORE_DATA to merge the data in the Data Management staging table with the existing Profitability and Cost Management data ADD_DATA to add the data in the Data Management staging table to Profitability and Cost Management SUBTRACT_DATA to subtract the data in the Data Management staging table from existing Profitability and Cost Management data REPLACE_DATA to clear the POV data and replace it with data in the Data Management staging table. Chapter 12 Managing Task Manager Integrations 12-137
- 391. Integration Name Description Parameters/ Description The data is cleared for Scenario, Version, Year, Period, and Entity NONE to skip data export from Data Management to Profitability and Cost Management File Name: Optional. If you do not specify a file name, this API imports the data contained in the file name specified in the load data rule. The data file must already reside in the INBOX prior to data rule execution. Run Batch Rule Executes a batch of jobs that have been defined in Data Management. Job Name: The name of a batch defined in Data Management. Update Dimension Uploads a new dimension flat file for an application created using a flat file. This is a process-automated integration. For more information, see Update Dimensions As a Job. File Name: Data file name Seperator Character: Optional Parameter Chapter 12 Managing Task Manager Integrations 12-138
- 392. Integration Name Description Parameters/ Description Lock Unlock Data Integration Locks or unlocks an integration for a location, category and period in Data Exchange. This is a process- automated integration. Operation: Choose from lock or unlock. Lock Type: Choose whether the Lock/Unlock operation is for an application or a location. Period: Specify the period of the POV from the integration or data load rule defined in Data Exchange, for example, "Jan-21". Category: Specify the predefined Scenario value based on the POV Category from the integration (data rule) definition. The categories available are those that are created in the Data Integration set-up, such as "Actual." Application (Optional): If selected Lock Type is application, specify the name of application, for example, "Vision". Location (Optional): If selected Lock Type is location, specify the name of the location. If the location is locked, data cannot be loaded to it. Unlock By Location (Optional): This parameter can be specified when selected operation is lock and selected location is application. If checked when locking the target application, then the system locks all rules present in the location under target application and not the application-level lock. For more information, see Lock and Unlock POV Copy and Delete Integration Files The following integrations are common for EPM Cloud: • Copy File from <EPM Cloud Service> • Copy File to <EPM Cloud Service> Chapter 12 Managing Task Manager Integrations 12-139
- 393. • Delete File from <EPM Cloud Service> Example To perform these integrations: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Integrations tab on the left. 3. From the list of pre-built integrations, select Copy File from <EPM Cloud Service>. This copies a file from the Current Task Manager service to a Remote EPM Cloud Service. For example, if you have configured Task Manager in Planning and set up Account Reconciliation connection, Copy File from Planning copies the file from Planning to Account Reconciliation. Note: This applies to all remote EPM Cloud services except Enterprise Data Management. • Enter the following Parameters: – File Name: Browse to and select the file that you want to copy. – Save File As: Enter a file name (which can be different than the original file name). – External Directory Name (Optional): Select the name of a directory. • Click Save and Close. 4. Select Copy File to <EPM Cloud Service>. This copies a file to the current service where Task Manager is configured from another EPM Cloud service. Chapter 12 Managing Task Manager Integrations 12-140
- 394. Note: This applies to all remote EPM Cloud services except Enterprise Data Management. • Enter the following Parameters: – File Name: Browse to and select the file that you want to copy. – Save File As: Enter a file name (which can be different than the original file name). – External Directory Name (Optional): Select the name of a directory. • Click Save and Close. 5. Select Delete File from <EPM Cloud Service>. This deletes a file from an EPM Cloud service. Note: This applies to all remote EPM Cloud services except Enterprise Data Management. • For File Name, browse to and select the file that you want to delete. • Click Save and Close. See also, Automation Integrations for EPM Cloud. Managing Integrations with Cloud and On-Premises Applications This appendix describes how to set up these pre-built Task Manager Integrations: • Oracle Cloud ERP Integrations • On-Premises Integrations • On-Premises Oracle E-Business Suite Event Monitoring Integrations EPM Cloud uses Oracle Integration cloud as an integration platform for Task Manager to perform automated tasks with non-EPM Cloud services. Chapter 12 Managing Task Manager Integrations 12-141
- 395. The following diagram shows the system and user flow that applies to Planning: End User Integrations for Oracle Cloud ERP Task Manager end user integrations allow you to access functionality in remote Cloud environments. This section lists the availableTask Manager end user integrations available for Oracle Cloud ERP. For a description of the remote Cloud functionality, see the documentation for that Cloud service. End User Integrations for Oracle Cloud ERP - Assets • Asset Balances Reconciliation with General Ledger • Asset Cost Summary • Asset Reserve Summary • Calculate Depreciation • Calculate Deferred Depreciation • Capitalize CIP Assets • Create Assets Accounting • Journal Entry Reserve Ledger Report • Manage Asset Assignments • Manage Asset Financial Transactions • Manage Mass Retirements • Manage Mass Transfers • Periodic Mass Copy for Tax Books Chapter 12 Managing Task Manager Integrations 12-142
- 396. • Period Close Exception Report • Prepare Source Lines and Submit Post Mass Additions • Reinstate Assets • Retire Assets End User Integrations for Oracle Cloud ERP - Cash Management • Bank Statement Reconciliation • Create Accounting • Cash to General Ledger Reconciliation Report • Subledger Period Close Exceptions Report End User Integrations for Oracle Cloud ERP - General Ledger • AutoPost Journals • AutoReverse Journals • Close General Ledger Periods • Create Allocation Rules • Create Balance Sheet Closing Journals • Create Income Statement Closing Journals • Extract Payables to General Ledger Reconciliation Data • Extract Receivables to General Ledger Reconciliation Data • Financial Reporting Center Work Area • General Accounting Dashboard • Generate Allocation Rules • General Ledger Trial Balance • General Ledger Average Trial Balance • General Ledger Journals Report • General Ledger General Journals Report • General Ledger Journals Details Report • General Ledger Journals Day Book Report • General Ledger Journals Batch Summary Report • General Ledger Account Details Report • General Ledger Account Analysis for Contra Account Report • General Ledger Average Balance Audit Account Analysis Report • General Ledger Account Analysis Report • General Ledger Trial Balance Report • Import Journals • Manage General Ledger Accounting Periods • Manage Journals Chapter 12 Managing Task Manager Integrations 12-143
- 397. • Open General Ledger Periods • Period Close Dashboard • Reconcile Payables to General Ledger • Reconcile Receivables to General Ledger • Revalue Balances • Translation • Transfer Balances Cross Ledgers • Transfer Balances to Secondary Ledger End User Integrations for Oracle Cloud ERP - Intercompany • Intercompany Account Details Report • Intercompany Reconciliation • Intercompany Transaction Summary Report • Intercompany Transactions Work Area • Manage Intercompany Period Status • Transfer Intercompany Transactions to General Ledger • Transfer Intercompany Transactions to Receivables • Transfer Intercompany Transactions to Payables End User Integrations for Oracle Cloud ERP - Payables • Apply Missing Conversion Rates • Complete or Cancel Incomplete Payment Process Requests • Create Payables Accounting • Create Mass Additions • Extract Payables to General Ledger Reconciliation Data • Import Payables Invoices • Import Payables Payment Requests • Manage Payables Period • Open Items Revaluation Report • Payables Unaccounted Transactions Report • Payables Invoices Landing Page • Payables Unaccounted Transactions Report with Sweep Option • Payables Trial Balance Report • Period Close Exceptions Report • Review Payables to General Ledger Reconciliation Report • Transactions Pending Approvals • Transfer Cost to Cost Management • Update Matured Bills Payable Status Chapter 12 Managing Task Manager Integrations 12-144
- 398. • Update Matured Bills Payable Status • Validate Unvalidated Transactions End User Integrations for Oracle Cloud ERP - Receivables • Approve or Reject Customer Credits • Billing Work Area • Clear Receipts Automatically • Create Automatic Billing Adjustments • Create Automatic Receipt Batch • Create Receipts Remittance Batch • Create Late Charge Batch • Create Automatic Receipt Write-Offs • Create Receivables Accounting • Extract Reconciliation Data From Receivables to General Ledger • Import AutoInvoice: Master • Manage Receivables Accounting Periods • Manage Revenue Adjustments • Receivables Balances Work Area • Process Receipts Through Lockbox • Recognize Revenue • Receivables Aging by General Ledger Account Report • Submit Subledger Period Close Exceptions Report End User Integrations for Oracle Cloud ERP - Tax • Tax Reconciliation Report • Tax Reconciliation by Taxable Account Report Application Token Values for Cloud ERP Integrations Token Name: SERVER Token Description: Property used for URL-based integration, for example, as in this fictitious URL: https://customer_chosen_domain_name_fa.DC.oraclecloud.com Note: Do not specify forward slash ( / ) at the end of the URL. Event Monitoring Integrations for Oracle Cloud ERP This section lists the out of box event monitoring integrations for Oracle Cloud ERP. Chapter 12 Managing Task Manager Integrations 12-145
- 399. Note: For custom process automation or event monitoring integration to Oracle Cloud ERP, see Creating Custom Task Manager Integrations. Supported Events for Oracle Cloud ERP General Ledger The following events are supported for General Ledger: Source Event Description General Ledger Accounting Period Closed Signals when a general ledger accounting period is closed. General Ledger Accounting Period Opened Signals when a general ledger accounting period is opened. General Ledger Accounting Period Reopened Signals when a general ledger accounting period is reopened. General Ledger Journal Batch Approved Signals when a journal batch is approved. General Ledger Journal Batch Posting Completed Signals when a journal batch is posted. Integrations Added to Existing Out of Box Connection The table lists integrations that are added to monitor these business events from Task Manager, which includes: • Integration Types in Task Manager • Task Types in Task Manager • Integration Flows in Integration Cloud Connection Name Integration Name Integration Code Event Name Description Parameter(s) Oracle Cloud ERP - General Ledger Period Close Event R13GLPeriod Close Accounting Period Closed Oracle Cloud ERP General Ledger Period Close Event Monitoring LedgerName: Name of the Ledger. For example, US Primary Ledger. Period: Name of the Period. For example, 01-19. Chapter 12 Managing Task Manager Integrations 12-146
- 400. Connection Name Integration Name Integration Code Event Name Description Parameter(s) Oracle Cloud ERP - General Ledger Period Open Event R13GLPeriod Open Account Period Opened Oracle Cloud ERP General Ledger Period Open Event Monitoring LedgerName: Name of the Ledger. For example, US Primary Ledger. Period: Name of the Period. For example, 01-19. Oracle Cloud ERP - General Ledger Period Reopen Event R13GLPeriod Reopen Accounting Period Reopened Oracle Cloud ERP General Ledger Period Reopen Event Monitoring LedgerName: Name of the Ledger. For example, US Primary Ledger. Period: Name of the Period. For example, 01-19. Oracle Cloud ERP - General Ledger Journal Approve Event R13GLJourna lBatchAppro ve Journal Batch Approved Oracle Cloud ERP General Ledger Journal Batch Approve Event Monitoring BatchName: Journal Batch Name Period: Name of the Period. For example, 01-19. Oracle Cloud ERP - General Ledger Journal Post Event R13GLJourna lBatchPost Journal Batch Posted Oracle Cloud ERP General Ledger Journal Batch Post Event Monitoring BatchName: Journal Batch Name Period: Name of the Period. For example, 01-19. Setting Up the Integration in Task Manager In Task Manager, you can create an Event Monitoring integration for Oracle Cloud ERP - General Ledger. The Event Monitoring integration is triggered when an external event occurs in another Cloud service or on-premises application. Make sure the business events are enabled in Oracle Cloud ERP. You can verify the events using REST API. See these topics in the "ERP Business Events REST Endpoints" section of the REST API for Oracle Financials Cloud guide: https://docs.oracle.com/en/cloud/saas/financials/22d/farfa/api-erp-business-events.html To verify the events, see "Get all business event records". If any event is not enabled, see "Update the enabled indicator for a business event". Follow these steps to set up an integration between Task Manager and Oracle Cloud ERP: 1. On the Home page, click Application, and then click Task Manager. Chapter 12 Managing Task Manager Integrations 12-147
- 401. 2. Click the Integrations tab on the left, then click Manage Connections, and then click Integration Cloud Connection. 3. On the Integration Cloud Connection dialog, add the required information: a. For URL, enter the Oracle Integration Cloud URL. b. For Service Administrator and Password, enter the Service Administrator credentials. c. Click Validate. d. After successful validation, click Save and then close the dialog. Enabling the Oracle Cloud ERP - General Ledger Connection To enable the Oracle Cloud ERP - General Ledger connection: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Integrations tab on the left, then click Manage Connections. 3. Select Oracle Cloud ERP - General Ledger from the list, click Actions, and then select Edit. 4. In the Edit Connection dialog, select Enabled, and then click OK. 5. In the Deploy to Integration Cloud dialog, click Generate. If the Oracle Cloud ERP - General Ledger connection is already enabled, deploy the integration flow to Oracle Integration Cloud by selecting the event monitoring integrations from the Integrations screen, and clicking Deploy to Integration Cloud from the toolbar. Then click Generate in the Deploy to Integration Cloud dialog. The integration flow is deployed to the Integration Cloud and you can view the flow by logging in to Integration Cloud Services. Note: The first time you enable the connection to Integration Cloud, all Integration Cloud deployments will fail during activation. The Administrator must activate the integrations in Integration Cloud. Before activating the integrations, the Administrator must set up the integration in Integration Cloud. Setting Up the Integration Flow in Integration Cloud To set up the integration flow in Integration Cloud: 1. Log in to Integration Cloud Services. 2. Navigate to Connections. EPM Fusion Connection and EPM Connection are automatically created. 3. Edit the connections by providing the environment and credential information. For details on prerequisites for creating a connection, see Prerequisites for Creating a Connection. • EPM Fusion Connection is the connection to the Oracle Cloud ERP. See Using the Oracle ERP Cloud Adapter for more details. Chapter 12 Managing Task Manager Integrations 12-148
- 402. • EPM Connection is the connection to the EPM Cloud Service in Task Manager. See Using the Oracle Enterprise Performance Management Cloud Adapter with Oracle Integration for more details. After configuring, testing, and saving the connections, you see a green check mark next to the connections. 4. Return to Task Manager and select Integrations. 5. Select the integration from the list, then click Deploy to Integration Cloud from the toolbar. 6. In the Deploy to Integration Cloud dialog, click Generate. The Cloud Integration deployment is successful. Verify the activation status in the Integration Cloud by logging into the Oracle Integration Cloud service, then Integrations. Adding the Event Monitoring Task to a Template or a Schedule After the set up is complete, you can add the event monitoring tasks to a schedule or a template. 1. On the Home page, click Application, and then click Task Manager. 2. Click the Templates tab on the left and create a new template; for example, ERP Event Template. 3. Create the event monitoring task. See Creating Tasks. In the Task Type, make sure to select Oracle Cloud ERP - General Ledger, then select the event monitoring task; for example, Period Open Event. 4. In Task Manager, click Template, select ERP Event Template, and create a schedule. See Creating Schedules from Templates. 5. In Task Manager, click Schedules, select the schedule, and change the status to Open. You can monitor the schedule task in the Schedule Tasks screen. Triggering the Period Close Event in Oracle Cloud ERP To raise the Period Close event in Oracle Cloud ERP: 1. Login to Oracle Cloud ERP. 2. Select the General Accounting tab, then Period Close. 3. Click General Ledger and select the period, then click Close Period. Chapter 12 Managing Task Manager Integrations 12-149
- 403. 4. Wait for a few minutes for the task to be completed. Then navigate to the Schedule Tasks screen in Tasks to verify the task is closed. Triggering the Period Open/Reopen Event in Oracle Cloud ERP To raise the Period Open event in Oracle Cloud ERP: 1. Login to Oracle Cloud ERP. 2. Select the General Accounting tab, then Period Close. 3. Click General Ledger and select the period, then click Open Period. 4. Wait for a few minutes for the task to be completed. Then navigate to the Schedule Tasks screen in Tasks to verify the task is closed. Note: If you open a period that has never been opened, the Period Open Event is triggered. If you open a period that has been closed before, the Period Reopen Event is triggered. Triggering the Journal Batch Approved Event in Oracle Cloud ERP To raise the Journal Batch Approved event in Oracle Cloud ERP: 1. Login to Oracle Cloud ERP. 2. Select the General Accounting tab, then Journals. 3. Click Requiring My Approval and select the journal batch, then click Approve. 4. Wait for a few minutes for the task to be completed. Then navigate to the Schedule Tasks screen in Tasks to verify the task is closed. Note: You can trigger the Journal Batch Approved event only if it is the last approval in the multi level approval process. Triggering the Journal Post Event in Oracle Cloud ERP To raise the Journal Batch Approved event in Oracle Cloud ERP: 1. Login to Oracle Cloud ERP. Chapter 12 Managing Task Manager Integrations 12-150
- 404. 2. Select the General Accounting tab, then Journals. 3. Click Tasks and select Create Journal. 4. In Create Journal screen, specify the required information, then click Save. Note: The journal batch name and accounting period should match the parameters of the task in the Task Manager schedule. 5. Wait for a few minutes for the task to be completed. Then navigate to the Schedule Tasks screen in Tasks to verify the task is closed. End User Integrations for On-Premises Applications Task Manager end user integrations allow you to access functionality in on-premises environments. This section lists the availableTask Manager end user integrations for on- premises applications. For a description of the on-premises functionality, see the documentation for that application. End User Integrations for Hyperion 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 • Intercompany Transaction Report • Journal Reports • Ownership Management • Post Journals • Process Control • Process ICT • Task List Chapter 12 Managing Task Manager Integrations 12-151
- 405. • 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 Transactions Report (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 • 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 Chapter 12 Managing Task Manager Integrations 12-152
- 406. • 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 (Autoinvoice Import Program) • Run Revenue Recognition (Revenue Recognition) • Create Accounting • 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) End User Integrations for Hyperion Profitability and Cost Management • Job Library • Manage Calculation • Manage Database • Manage Model Views • Manage Queries • Manage Rules • Model Summary Chapter 12 Managing Task Manager Integrations 12-153
- 407. • Model Validation • POV Manager • Rule Balancing • System Reports • Trace Allocations End User Integrations for Oracle Fusion Assets • Prepare Source Lines and Submit Post Mass Additions • Capitalize CIP Assets • Manage Asset Financial Transactions • 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 • 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 • General Allocation Rules • General Ledger Trial Balance • General Ledger Average Trial Balance Chapter 12 Managing Task Manager Integrations 12-154
- 408. • 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 • 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 Chapter 12 Managing Task Manager Integrations 12-155
- 409. • 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 • Extract Payables to General Ledger Reconciliation Data • 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 Chapter 12 Managing Task Manager Integrations 12-156
- 410. • 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 Hyperion Planning • Business Rules • Clear Cell Details • Copy Data • Copy Version • Custom Links • Data Form • Data Load Settings • Manage Currency Conversion • Manage Data Forms • Manage Dimensions • 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 Chapter 12 Managing Task Manager Integrations 12-157
- 411. • 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 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 Chapter 12 Managing Task Manager Integrations 12-158
- 412. • Reconcile Open AP Liability Report to GL • Review Aged AR Trial Balance Setting Up an Integration Make sure you have the prerequisites and follow these steps to set up an integration between Task Manager and an external application. Prerequisites To integrate Task Manager with an on-premises application such as E-Business Suite, you need: • A subscription to Oracle Integration Cloud Service. Note: You need one Integration Cloud instance for each Planning 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 in "Use Oracle E-Business Suite Business Events to Trigger Integration Endpoint in Oracle Integration Cloud" for EBS adapter in Oracle Integration Cloud: https://docs.oracle.com/cloud/latest/related-docs/ICEBS/ toc.htm 3. In Planning, from the Home page, select Application, and then click Task Manager. 4. Click the Integrations tab on the left. 5. Click Manage Connections. 6. From Manage Connections, under Actions, select Integration Cloud Connection. 7. Specify the Integration Cloud connection URL and credentials and click Validate. After validation is successful, click Save. This saves the server and credential of the Planning connection. Chapter 12 Managing Task Manager Integrations 12-159
- 413. Note: Task Manager uses Integration Cloud for all the integrations to external applications that are non-EPM Cloud. The external applications can be another Cloud service or an on-premises application such as E-Business Suite. These can be Process Automation or Event Monitoring integration types. 8. Do one of the following depending on whether the EBS connections for General Ledger and Account Payable connections are already enabled: • If the EBS connections for General Ledger and Account Payable are already enabled, click Deploy and then Generate to deploy the corresponding Integration Cloud integrations to Integration Cloud • If the EBS connections for General Ledger and Account Payable connections are not enabled: a. In Task Manager within Planning, go to Integrations, then click Manage Connections. b. Select and edit E-Business Suite - General Ledger. Select the Enabled check box and click OK. Then click Deploy and then Generate. c. Repeat these steps for E-Business Suite - Account Payables. The system creates the Integration Task Type and also deploys Integration Cloud integrations to Integration Cloud service. Chapter 12 Managing Task Manager Integrations 12-160
- 414. Note: If you are doing this for first time and the connections in Integration Cloud are not completed, all the Integration Cloud deployments will fail during activation. This is expected. To fix this: a. Log in to Integration Cloud. b. Navigate to Connections. You will see two connections named FCCS and EBS. Optionally use Search. Edit FCCS connection: • Click Configure Connectivity and enter FCCS url as <FCCS url>/ HyperionPlanning/rest/cmapi/v1 • Click Configure Security and enter the Service Administrator credential of your FCCS service. Then click Test and then Save. Note: The Service administrator user ID should be in the format specified 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-Business suite. • Click Test and then Save. c. From FCCS, open Task Manager and select Manage Integrations. d. In Manage Connections, in Actions menu, select Integration Cloud Connection and click Deploy and then Generate. This time the deployment should complete without any errors. 9. Verify that the Integration - EBS linking is done properly. You can do this by logging in to Oracle E-Business Suite as administrator and verify the Integration Cloud REST service is added as subscriber for Business event. Here's an example: Chapter 12 Managing Task Manager Integrations 12-161
- 415. Check that the Integration Cloud service was added. For example: On-Premises Oracle E-Business Suite (EBS) Integration These are theTask Manager Integrations for EBS Event Monitoring: • EBSJournalApprove • EBSJournalPost • EBSJournalPeriodClose • EBSJournalPeriodOpen • EBSJournalPeriodReopen • EBSAPJournalPeriodOpenClose Chapter 12 Managing Task Manager Integrations 12-162
- 416. These are the events that can be monitored: Table 12-8 Oracle E-Business Suite Events and Descriptions Integration Name Event Name Description Journal Approve Event oracle.apps.gl.Journals.journal.approve General Ledger: Journal Approved Journal Post Event oracle.apps.gl.Journals.journal.post General Ledger: Posting Completed Journal Period Close Event oracle.apps.gl.CloseProcess.period.close General Ledger: Period Closed Journal Period Open Event oracle.apps.gl.CloseProcess.period.open General Ledger: Period Opened Journal Period Reopen Event oracle.apps.gl.CloseProcess.period.reope n General Ledger: Period Reopened Payables Period Open/Close Event oracle.apps.ap.CloseProcess.period Accounts Payables: Period Open/ Close/Reopen Table 12-9 General Ledger Journals Integration Type Parameters Name Type Required Order Hidden Batch ID Text Yes 1 N Table 12-10 General Ledger Close Process Period Integration Types Parameters Name Type Required Order Hidden LedgerID Text Yes 1 N PeriodName Text Yes 2 N Table 12-11 Accounts Payable Integration Types Parameters Name Type Required Order Hidden 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 the required events, you can verify your results by raising business events. The following sections describe how to run the EBS tasks that raise the events you track. General Ledger - Journal Approved oracle.apps.gl.Journals.journal.approve EBS Steps Chapter 12 Managing Task Manager Integrations 12-163
- 417. 1. Log on to EBS. 2. Select General Ledger, and then the Vision Operations (USA) role from the left tree. 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 the accounts. 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 the Batch. After you finish the journal entries for the last Journal, move the cursor into the Journal 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. 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 Journal batch ID. For example, Chapter 12 Managing Task Manager Integrations 12-164
- 418. • Block: BATCH • Field: JE_BATCH_ID • Value: 4776732 Copy this value to Notepad. This batch ID will be used as the value for the Batch ID 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 from EBS. 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 the specified batch. 2. Click Approve to raise the journal approval event. Next Steps in Task Manager 1. Wait for the task to be set to Open state. It takes a few minutes to capture the EBS event. 2. After 2-3 minutes, click Refresh in Task Manager. Refer to this document for further information on Journal Batch Approval related information: 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.post EBS steps 1. Log on to EBS. 2. Select General Ledger, and then the Vision Operations (USA) role from the left tree. 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. Chapter 12 Managing Task Manager Integrations 12-165
- 419. 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 the accounts. 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 the Batch. After you finish the journal entries for the last Journal, move the cursor into the Journal 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. 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 Journal batch 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 Batch ID 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.post). 3. On the Parameters tab, provide a value for Batch ID as the journal batch ID from EBS. 4. Save task and set the schedule to Open state. Next Steps in EBS Chapter 12 Managing Task Manager Integrations 12-166
- 420. 1. On the Batch (Vision Operation (USA), the Approve button is now enabled for the specified batch. 2. Click Post to raise the journal approval event. 3. Examine the status of EBS request by selecting the View, then Requests, then Specific Requests. 4. Specify the Request ID that was noted earlier. Next Steps in Task Manager 1. Wait for the task to be set to Open state. It takes a few minutes to capture the EBS event. 2. After 2-3 minutes, click Refresh in Task Manager. Refer to this document for further information on Journal Batch Post related information: 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. 2. Select General Ledger, and then the Vision Operations (USA) role from the left tree. 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. 10. Select the Status column for that period. 11. Click Help and select Diagnostics, and then Examine. 12. Enter Oracle password: APPS. 13. In Field, enter LEDGER_ID and click inside Valueto get the unique Ledger ID. For example, • Block: PREVIOUS • Field: LEDGER_ID • Value: 1 Copy this value to Notepad. This Ledger ID will be used as the value for the LEDGER_ID parameter of the Event Monitoring task. Next Steps in Task Manager 1. Create a new Schedule in Pending state. Chapter 12 Managing Task Manager Integrations 12-167
- 421. 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 from EBS. For example: Period Name: Dec-10 and Ledger ID: 1 4. Save the task and set the schedule to Open state. 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 then Specific Requests. Next Steps in Task Manager 1. Wait for the task to be set to Open state. It takes a few minutes to capture the EBS event. 2. After 2-3 minutes, click Refresh in Task Manager. 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. 2. Select General Ledger, and then the Vision Operations (USA) role from the left tree. 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 open. 6. Copy the period you want to open in Notepad. 7. Select the Status column for that period. 8. Click Help and select Diagnostics, and then Examine. 9. Enter Oracle password:APPS. 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 Copy this value to Notepad. This Ledger ID will be used as the value for theLEDGER_ID parameter of the Event Monitoring task. Next Steps in Task Manager Chapter 12 Managing Task Manager Integrations 12-168
- 422. 1. Create a new Schedule in Pending state. 2. Create a task for an event monitoring task to monitor Journal Period Open Event (oracle.apps.gl.CloseProcess.period.open). 3. On the Parameters tab, provide a value for Ledger ID and Period Name from EBS. For example: Period Name: Dec-10 and Ledger ID: 1 4. Save the task and set the schedule to Open state. Next Steps in EBS 1. Click Open Period. 2. Select the period to open and click OK to raise the event. 3. Examine the status of EBS request by selecting View, then Requests, and then Specific Requests. Next Steps in Task Manager 1. Wait for the task to be set to open state. It takes a few minutes to capture the EBS event. 2. After 2-3 minutes, click Refresh in Task Manager. 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 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 left tree. 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 reopen. 6. Copy the period you want to reopen in Notepad. 7. Select the Status column for that period. 8. Click Help and select Diagnostics, and then Examine. 9. Enter Oracle password:APPS. 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 Copy this value to Notepad. This Ledger ID will be used as the value for the LEDGER_ID parameter of the Event Monitoring task. Next Steps in Task Manager Chapter 12 Managing Task Manager Integrations 12-169
- 423. 1. Create a new Schedule in Pending state. 2. Create a task for an event monitoring task to monitor Journal Period Reopen Event (oracle.apps.gl.CloseProcess.period.reopen). 3. On the Parameters tab, provide a value for Ledger ID and Period Name from EBS. For example: Period Name: Dec-10 and Ledger ID: 1 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. 3. Examine the status of EBS request by selecting View, then Requests, and then Specific Requests. Next Steps in Task Manager 1. Wait for the task to be set to Open state. It takes a few minutes to capture the EBS event. 2. After 2-3 minutes, click Refresh in Task Manager. Refer to this document for more information on General Ledger Periods: http://docs.oracle.com/cd/A60725_05/html/comnls/us/gl/openper.htm 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 the Control Payables Periods form. 4. Specify the Ledger and Operation Unit. Do not close the Find Payables Periods dialog. Instead, perform the following steps to identify the Ledger ID value. 5. Click Help and select Diagnostics, and then Examine. 6. If requested for credentials, specify the APPS schema credentials. The Examine Fields and Variable Values form displays. 7. In Block, enter PERIOD_QF. In Field, enter SET OF BOOKS, and click inside Value, to get the unique Ledger ID numeric value. For example, • Block: PERIOD_QF • Field: SET OF BOOKS • Value: 1 Copy this value to Notepad. This Ledger ID will be used as the value for the LEDGER_ID parameter of the Event Monitoring task. Next Steps in Task Manager 1. Create a new Schedule in Pending state. Chapter 12 Managing Task Manager Integrations 12-170
- 424. 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 Action from EBS. For example, Ledger ID: 1, Period Name: Dec-10 and Action: Closed 4. Save the task and set the schedule to Open state. 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. Next Steps in Task Manager 1. Wait for the task to be set to Open state. It takes a few minutes to capture the EBS event. 2. After 2-3 minutes, click Refresh in Task Manager. Note: The EBS implementation raises the events only for Closed and Open statuses. 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 Creating Custom Integrations In Task Manager, you can create and manage custom Process Automation or Event Monitoring integrations with external applications. An EPM Adapter enables you to create connections and integration flows in Integration Cloud Service using Oracle EPM Cloud and other cloud and on-premises applications. The following diagram shows the user and system flow for creating custom integrations: Chapter 12 Managing Task Manager Integrations 12-171
- 425. See these topics: • Creating Custom Process Automation Integrations • Creating Custom Event Monitoring Integrations Creating End User Integration When you create Integrations, you select End-User as the Execution type. Users can then create task types based on the defined Integrations, or validate the Integrations. To create an Integration: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Integrations tab on the left. 3. Click New. See also, Setting Integration Properties and Setting Integration Parameters. Creating Custom Process Automation Integrations In Task Manager, you can create custom process automation integrations with external applications. In a Process Automation integration, a task is automatically executed in an external application when its start date and time are reached, and when any predecessor tasks are completed, for example, an overnight feed from a General Ledger. When you create a Process Automation task, if you have set up email notifications, the task Owner automatically receives an email notification when the task starts or is completed. The Assignee that is specified when you set up a workflow receive an action notification when there is a change in the task status and an action needs to be performed, such as an approval, and the Owner receives a notification when the approval is completed. Make sure you have the prerequisites and follow these steps to set up an integration between Task Manager and an external application. For an overview of the custom integrations flow, see Creating Custom Integrations. Chapter 12 Managing Task Manager Integrations 12-172
- 426. Prerequisites To integrate Task Manager with an external application, you need: • A subscription to Oracle Integration Cloud Service, to integrate with on-premises and non-EPM Cloud services. Note: You need one Integration Cloud instance per Oracle EPM cloud instance. • 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 communicate with your Oracle EPM cloud instance. For details on setting up Integration Cloud Agent, see Managing Agent Groups. Note: If the on-premises application services are deployed in an environment set up in a demilitarized zone (DMZ) configuration so that these services are publicly accessible through the Internet, you do not need to install Integration Cloud Agent. Creating a Connection in Task Manager 1. On the Home page, click Application and then click 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. b. For Code, enter an Integration Code for the integration task. The code is used to execute the Integration and to map updates to an Integration from a file import. c. Optional: In Description, enter a description for the integration task. Chapter 12 Managing Task Manager Integrations 12-173
- 427. d. For Connection, select an application to which the task belongs. You can maintain the list of applications from the Manage Connections icon in the Manage Connections dialog box. e. For Execution Type, select Process Automation. 4. On the Parameters tab, click New and then 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 information for the parameter: • Checkbox: 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, 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 1. On the Home page, click Application, and then click Task Manager. 2. Click the Task Types tab on the left. 3. Click New. 4. On the Properties tab, specify a Task Type Name and Task Type ID. 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 1. On the Home page, click Application, and then click Task Manager. 2. Click the Integrations tab on the left. 3. Click Manage Connections, and then from Actions, select Integration Cloud Connection. 4. Specify the Integration Cloud connection URL and credentials and click Validate. After validation is successful, click Save. This saves the server and credentials of the connection. Chapter 12 Managing Task Manager Integrations 12-174
- 428. Note: Enter the URL: https://<SERVICE_NAME>- <TENANT_NAME>.integration.ocp.oraclecloud.com Creating a Connection and Integration in Integration Cloud 1. Log in to Integration Cloud. 2. Create a connection using Oracle Enterprise Performance Management Cloud adapter to your EPM server. Refer to this link for more details: Create a Connection to Oracle Enterprise Performance Management Cloud. 3. Create one or more connections to the other application as needed. 4. Create Process Automation Integration using the connections created and activate it. Refer to this example: Using the Oracle Enterprise Performance Management Cloud Adapter with Oracle Integration. Completing the Integration Setup in Task Manager Use these steps to complete the Integration setup in Task Manager. 1. On the Home page, click Application, and then click Task Manager. 2. Click the Integrations tab on the left and verify that the new Integration is displayed on the Integrations list. 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 Creating Tasks. 5. From Schedules, select and open the schedule. Creating Custom Event Monitoring Integrations In Task Manager, you can create an Event Monitoring integration for an external application. The Event Monitoring integration is triggered when an external event occurs in another Cloud service or on-premises application. An example of an Event Monitoring integration is a trigger from Oracle E-Business Suite - General Ledger when a period, for example, January 2018, is closed. Make sure you have the prerequisites and follow these steps to set up an integration between Task Manager and an external application. For an overview of the custom integrations flow, see Creating Custom Integrations. Prerequisites Note: Event monitoring can also be triggered through any integration tool capable of invoking REST APIs. In that case you do not need the below prerequisites. To integrate Task Manager with an external application, you need: Chapter 12 Managing Task Manager Integrations 12-175
- 429. • A subscription to Oracle Integration Cloud Service, to integrate with on-premises and non-EPM Cloud services. Note: You need one Integration Cloud instance per Oracle EPM cloud instance. • 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 communicate with your Oracle EPM cloud instance. For details on setting up Integration Cloud Agent, see Managing Agent Groups. Note: If the on-premises application services are deployed in an environment set up in a demilitarized zone (DMZ) configuration so that these services are publicly accessible through the Internet, you do not need to install Integration Cloud Agent. Setting Up the Integration in Task Manager 1. On the Home page, click Application, 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: 4. 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 an Integration 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 in the Manage Connections dialog box. e. For Execution Type, select Event Monitoring. f. For Event Name, enter a name for the event. 5. 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 information for the parameter: Chapter 12 Managing Task Manager Integrations 12-176
- 430. • Checkbox: 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, 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 Note: If you are not planning to use Integration Cloud, skip this step. To set up the integration in Integration Cloud: 1. Log in to Integration Cloud. 2. Create a connection using Oracle Enterprise Performance Management Cloud adapter to your EPM service. Refer to this link for more details: Create a Connection to Oracle Enterprise Performance Management Cloud. 3. Create one or more connections to the other application as needed. 4. Create Event Monitoring Integration using the connections created and activate. Refer to this example: Using the Oracle Enterprise Performance Management Cloud Adapter with Oracle Integration. Setting Up the Integration without Integration Cloud Note: If you are planning to use Integration Cloud, skip this step. Configure the integration tool which you are planning to use. 1. Review the REST API, Update Task Status for Event Monitoring in REST API for Oracle Enterprise Performance Management Cloud . 2. Configure the integration tool to call the REST API to close the Event Monitoring task passing the parameters for the event. Chapter 12 Managing Task Manager Integrations 12-177
- 431. For more information, see Update Task Status for Event Monitoring in REST API for Oracle Enterprise Performance Management Cloud . Completing the Integration Setup in Task Manager Use these steps to complete the Integration setup in Task Manager. 1. On the Home page, click Application, and then click Task Manager. 2. Click the Integrations tab on the left, and verify that the new Integration is displayed. 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). If you are not using Integration Cloud but other integration tool, invoke the REST API from the integration tool. Note: Pass the parameters as expected by the integration type, event, parameters, otherwise the task will not be considered if they do not match. 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. Working with Integrations Related Topics: • Creating Integrations • Viewing Integrations • Editing Integrations • Searching for Integrations • Validating Integrations • Deleting Integrations Creating Integrations When you create Integrations, you select End-User as the Execution type. Users can then create task types based on the defined Integrations, or validate the Integrations. To create an Integration: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Integrations tab on the left. Chapter 12 Managing Task Manager Integrations 12-178
- 432. 3. Click New. Add information to the following sections: • Setting Integration Properties • Setting Integration Parameters Setting Integration Properties You 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 to enable users to access an external web application without being prompted for authentication. You can use an SSO parameter for an external application if that application 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. You can enter a maximum of 80 characters. 3. Enter a Code, for example, HFM_CONS for the Hyperion Financial Management Consolidate integration task. You can enter a maximum of 90 characters. 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. You can enter a maximum of 255 characters. 5. In Connection, select an application to which the task belongs. Note: You can maintain the list of applications from the Manage Connections icon in the Manage Connections dialog box. 6. For Execution Type, select End User and select options: • End User Endpoint: To enter parameters for an End User task, the End User Endpoint should contain these parameters in these formats: $ Parameter Type Code $, for example $COLORS$. The system replaces the parameter tokens in the End User Endpoint with the information you specified for the task parameters. • Optional: Show in-line: Select whether to display the URL in line within the Task Actions dialog. • Optional: SSO Parameter: Specify the name of the SSO parameter for your application to include when executing the End User task URL to the external application. If you do not specify an SSO parameter, the system uses the End User URL. 7. Optional: Click Parameters. Chapter 12 Managing Task Manager Integrations 12-179
- 433. Setting Integration Parameters Task Manager Integration parameters enable the application to pass information to the end point to control how the end point should perform its action. For example, when you run a consolidation, your program can pass which application to run the consolidation against, and the dimension selections for the consolidation. You set the parameter values defined in the Integrations in the task or Task Type using the integration. Each parameter definition requires a name, description, unique code, type, and whether a value is required. The parameter code is the token that replaces the parameter in the execution URL for user tasks, or the parameter name that is passed to the execution web service for system-automated integrations. Required values must have 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 value in the task field. Supported parameter types: To set Integration parameters: 1. In the New Integration 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 for the parameter: • Checkbox: 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, start and 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. Viewing Integrations You can view the properties and parameters of imported Integrations. You can specify which columns to display, or show all. You can also reorder columns, sort columns by ascending or descending order, or change the column widths. Chapter 12 Managing Task Manager Integrations 12-180
- 434. To display columns: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Integrations tab on the left. 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 Sort Ascending 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. Editing Integrations You can't edit the pre-built Integrations provided by default by the system. You can only edit custom-built integrations that you created. For an End User type, you can edit the endpoint, change the point of view, or change the list of values. To edit an Integration: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Integrations tab on the left. 3. Select an Integration, and click Edit. 4. Edit the Integration. 5. Click Save and Close. Searching for Integrations You can use the Search box on the Integrations page to find Integrations. You can enter full or partial names on which to search. To search for Integrations: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Integrations tab on the left. 3. In the Search box, enter full or partial search criteria for the Integration. 4. Press Enter. Chapter 12 Managing Task Manager Integrations 12-181
- 435. To reset the list to display all Integrations, clear the Search box and then press Enter. Validating Integrations You can test and validate Task Manager Integration definitions through a test schedule and adding a task to the schedule. To validate an Integration: 1. In Task Manager, click Schedules, then click New to create a Schedule in Pending state. See Manually Creating Schedules. 2. Add a task based on the integration to be validated to the schedule. See Creating Tasks. 3. From Schedules, select and open the schedule. 4. From Tasks, click Schedule. Select the schedule and view the Task. 5. For Event Monitoring Task, trigger the action that generates the event in the external application (for example, EBS). If you are not using Integration Cloud but other integration tool, invoke the REST API from the integration tool. Deleting Integrations You 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 is associated with a Task Type. To delete an Integration: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Integrations tab on the left. 3. Select an Integration to delete. 4. Click Delete. 5. At the confirmation prompt, click Yes. Managing Connections Integrations are assigned connections for the external products to which they link. From the Manage Connections module, you can maintain a list of connections associated with the Integrations. You can search on and sort the list by connection. • Adding Connections • Editing Connections • Deleting Connections Adding Connections You can add connections to associate with an Integration Type. You can also specify the security policy to use for an Integration Type. In addition, you can specify application-level tokens and values for all Integration Types in an application. When you specify an application-level token in an end-user Chapter 12 Managing Task Manager Integrations 12-182
- 436. URL or web service WSDL, the system replaces the token with the value defined for that token in the application. For example, you can specify tokens with values for server and port, and the system automatically applies those values to the Integration Types in the application. To add a connection: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Integrations tab on the left. 3. Click Manage Connections. 4. Click New. 5. Complete the New Integration Properties and Parameters, then click Save and Close. 6. Optional: To add an application-level token, click Manage Connections. Click New or select a Connection and click Edit. In the Application Tokens table, click Add. Enter a Token Name and optionally a Token Value, and then click OK. Tip: To remove a token, click Delete. Editing Connections You can edit the name of a connection, the security information, and application-level tokens. Note: You cannot add or modify application tokens for seeded applications. You can only edit the token values. You also use the Edit Connections dialog to enable pre-built Integrations. After you enable the Integration and fill in the parameters, you can then create tasks using Task Types for the enabled Integrations. To edit a connection: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Integrations tab on the left. 3. Click Manage Connections. 4. Select a connection, and click Edit. 5. To enable a pre-built Integration, select the connection, select Enabled, and fill in the parameters. You can enable or disable a connection at any time. 6. Edit the settings or tokens as needed, and click OK. Chapter 12 Managing Task Manager Integrations 12-183
- 437. Deleting Connections You can delete connections that you no longer need for Integrations. You cannot delete a connection while it is associated with an Integration Type. You must modify the properties for each Integration Type that references the connection before you can delete the connection. Note: You cannot delete seeded Integration connections. To delete a connection: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Integrations tab on the left. 3. Click Manage Connections. 4. Select a connection, and click Delete. Managing Alert Types for Task Manager Note: The Alert Types feature is only available to administrators. When performing a business process, users might encounter roadblocks such as a hardware failure, software issues, system failure, and so on. They can create an alert identifying 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. The user selects an alert type, which directs the alert to the proper resources to resolve their issue. See these topics: • Creating Alert Types • Editing Alert Types • Viewing Alert Types • Searching for Alert Types • Deleting Alert Types Creating Alert Types When users encounter roadblocks during a business process, they can create alerts identifying a problem. Chapter 12 Managing Alert Types for Task Manager 12-184
- 438. You can define Alert Types for stored procedures which capture critical information and assign key personnel for issue resolution. Using Alert Types, you can analyze the types of issues that users encounter during the business cycle and make changes to prevent them in future cycles. To create an alert type: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Alert Types tab on the left. 3. Click New. 4. Enter the necessary information on the Alert Type tabs: • Setting Alert Type Properties • Specifying Alert Type Instructions • Selecting the Alert Type Workflow • Assigning Alert Type Viewers • Adding Questions for Alert Types • Applying Alert Type Attributes • Viewing Alert Type History Setting Alert Type Properties The Properties tab enables you to specify the alert type name and description, and associate it with a Task Manager object, such as a task or schedule. An individual alert can be associated with multiple objects. You can place restrictions on the relationship between the alert and its associated object. Not all restrictions can be applied to all objects. Table 12-12 Alert Restrictions Restriction Description Example None No restrictions on the status of the object and the status of the alert A user raises a ‘slow performance’ alert while working on a reporting task. While this affects how long the task takes, it does not prevent the task from completing normally. Even if the task completes, the user still wants the alert open until the performance issue is resolved. Prevent Workflow Workflow on the object cannot proceed forward (no submits, approvals, and so on) until the alert is closed. This does not prevent claims or rejections (workflow moving backward). It also does not prevent an Administrator or Owner from forcing the workflow forward. A user raises an alert that the reporting system is down. This will prevent any work on reporting tasks until the alert is resolved. Preventing workflow includes preventing status changes from Pending to Open and Open to Closed. Chapter 12 Managing Alert Types for Task Manager 12-185
- 439. Table 12-12 (Cont.) Alert Restrictions Restriction Description Example Prevent Close The object cannot be moved into a closed state until the alert is closed. However, intermediate workflow may proceed. This does not prevent an Administator or Owner from closing or ‘force closing’. A user raises an alert that some comparison data is missing for a reporting task. While this does not prevent the report from being created and going through initial approvals, the report should not be fully signed off until it can be compared to the missing data. An object may have multiple alerts with different restrictions. If this is the case, the following rules will apply in order of precedent: 1. If any open alert associated with the object has a Prevent Workflow restriction, Prevent Workflow will stop the object's (for example, a Task) workflow until the alert is closed. 2. If any open alert associated with the object has a Prevent Close restriction, then the object cannot be closed until the alert(s) is closed. In addition, an alert may be associated with multiple objects. If it has more than one Prevent Close restriction to different objects, the alert will only be closed when the last object is closed. To set alert type properties: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Alert Types tab on the left. 3. Click New to open New Alert Type, which will default to the Properties tab. 4. For Name, enter an alert type name. You can enter a maximum of 80 characters. 5. Enter an Alert Type ID. You can enter a maximum of 80 characters. An Alert Type ID is required, and must be unique. 6. Optional: For Description, enter an alert type description. You can enter a maximum of 255 characters. 7. Optional: From the Associated With drop-down list, select an object, such as a task, with which to associate the alert. 8. Optional: For Restrictions, enter any restrictions for the alert. For example, if you select Prevent Close for an alert on a task, the user can't complete the close task until the alert is complete. If you select All Types for Associated With, no restrictions are available. 9. Select from the following values for both Period Selection and Year Selection: • Required – The user is required to associate the Alert with a Year or Period. • Visible – The user may associate the Alert with a Year or Period. • Hidden – The property is hidden and the Alert will not be associated with a Year or Period. These options indicate how Periods and Years are associated with an Alert. Chapter 12 Managing Alert Types for Task Manager 12-186
- 440. 10. Select Allow Remove Associations option to remove an existing association from an Alert. If you unselect this option, you will not be able to remove existing associated artifacts from the Alert. 11. Click Enabled to enable the alert type. Only alert types that are Enabled are displayed in the list of available Alert Types and available for selection when creating new alerts. 12. Click an Alert Type tab and continue entering information. When you are done entering the Alert Type information, click Save and Close. Note: You cannot create an alert on an existing alert. • Specifying Alert Type Instructions • Selecting the Alert Type Workflow • Assigning Alert Type Viewers • Adding Questions for Alert Types • Applying Alert Type Attributes Specifying Alert Type Instructions You can specify instructions in an alert type to help users understand what they need to do for the alert. You can add additional references from File and URL attachments. To specify instructions for an alert type: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Alert Types tab on the left. 3. From the New or Edit dialog, select the Instructions tab. 4. In Instructions, enter instruction text for the alert type. To add a reference: 1. In the References section, click Attach a file or Attach a link. • Attach a file Click Choose File to select and attach the file. For Name, enter a name or use the filename. Click OK. • Attach a link Enter the URL, then enter a Name for the URL; for example: https://www.oracle.com, Oracle. Click OK. 2. Click an Alert Type tab and continue entering information. When you are done entering the alert type information, click Save and Close. • Selecting the Alert Type Workflow • Assigning Alert Type Viewers Chapter 12 Managing Alert Types for Task Manager 12-187
- 441. • Adding Questions for Alert Types • Applying Alert Type Attributes Selecting the Alert Type Workflow The Workflow section contains the Assignee and Approver assignments. You can also select Backup users. To select the Alert Type workflow: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Alert Types tab on the left. 3. From the New or Edit dialog, click the Workflow tab. 4. For Assignee, click the Member Selector and select an assignee. The assignee is the user or group assigned to work on the alert when one is created of this type. If you do not specify an assignee, the user who creates the alert will need to fill one in. 5. Optional: For Backup User, select a backup user for the assignee: a. On the Home page, select Tools, then Access Control, and then Task Manager Users. b. Edit the assignee ID and change the Status field to Unavailable. c. Then from the Alert Types Workflow tab, you can select a backup user. The Backup User is the backup individual assigned to work on the alert if the main assignee is out of office. You must have previously assigned an assignee and a backup assignee. 6. Click Add (+) to add an Approver, and enter this information for the Approver: • User Name • Backup User: You can specify a default backup Approver user for the alert if the main Approver is out of the office. This is not required. Level displays the approvers in the order they were entered. You can reorder the Approver list by selecting an approver and clicking the arrow buttons to move them up or down in the list. You can add one or more levels of default Approver users or groups for the alert when one is created of this type. These are not required. If you do not specify Approvers, the user who creates the alert has the option to add them. 7. Click an Alert Type tab and continue entering information. When you are done entering the Alert Type information, click Save and Close. • Assigning Alert Type Viewers • Adding Questions for Alert Types • Applying Alert Type Attributes Assigning Alert Type Viewers The Viewers tab enables you to assign Viewer rights for alert types. Viewers have read-only access. Chapter 12 Managing Alert Types for Task Manager 12-188
- 442. To assign Viewer rights: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Alert Types tab on the left. 3. Click New or Edit and click on the Viewers tab. 4. Click Add and select the name of the user or group that will have View access to the alert. The system opens the Member Selector. It is editable for external Viewers. 5. Optional: Click Add External User to add a user outside the system who needs to be notified about the alert. The external user will not have any visibility to the alert, they will only receive notifications. No service access is granted. 6. Specify an Email Address for the viewer. The email address is editable for external Viewers. If there are duplicate email addresses in the list, you cannot save changes to the alert type. 7. Select a Notification Priority to indicate at what alert priority the users will be alerted via email. Notifications will be sent for the priority level or higher. So if set to High, notifications will be sent only when the alert is set to High. If set to Low, then they will be notified for all priority types (Low, Medium, High). If this is blank (default), no notification will be sent. 8. Click an Alert Type tab and continue entering information. When you are done entering the Alert Type information, click Save and Close. • Adding Questions for Alert Types • Applying Alert Type Attributes Adding Questions for Alert Types When you create an Alert Type, you may want a user to answer questions about their actions before they indicate the Alert Type is complete. For example, you may ask if a certain process was followed when completing that task. Questions can be set to the Administrator, Assignee, Approver, Owner, or Viewer roles. This allows key details to be gathered from the user experiencing the issue. You can specify various types of questions, such as Text, Number, or True/False, and indicate whether they are required. If a question is required, the user must respond or they cannot submit the task for approval. You can also order the questions by using the Move Up and Move Down buttons. To add a question: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Alert Types tab on the left. 3. From the New or Edit dialog, select the Questions tab. 4. Click New. 5. For Question, enter text for the question, with a maximum of 4000 characters. 6. From the Type list, select a question type: Chapter 12 Managing Alert Types for Task Manager 12-189
- 443. • Date • Date/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 50 lines. Multi-Line Text determines how many lines of text are visible without scrolling, on the Actions dialog boxes. • Number If you select Number, select number formatting options: – For Decimal Places, enter a value for the number of decimal places to display. – Select the Thousands Separator option if you want numbers to display a thousands separator (for example, 1,000.00) – From the Currency Symbol list, select a currency symbol; for example, $ (United States of America Dollar). – 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/False • User • Yes/No 7. Assign the Role (Owner, Assignee, Approver, Viewer) of the user who should answer the question. 8. If the question is required, select Required. Required indicates that the question must be answered by the user before they can proceed. Required questions can be set for Assignees, Approvers, and Owners. This is disabled for the System Administrator and Viewer role. 9. Click OK. 10. Optional: To change the order of questions, select a question, then click Move To Top, Move Up, Move Down, or Move To Bottom. 11. Optional: To edit a question, select the question and click Edit. To remove a question, select the question and click Delete. 12. Click an Alert Type tab and continue entering information. When you are done entering the Alert Type information, click Save and Close. • Applying Alert Type Attributes • Viewing Alert Type History Chapter 12 Managing Alert Types for Task Manager 12-190
- 444. Applying Alert Type Attributes When you 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 of North, South, East, and West. The current alert type applies only to the West Sales Region, so you can add the Sales Region attribute and set it to "West". To apply an attribute: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Alert Types tab on the left. 3. Click New or Edit , and select the Attributes tab. 4. Click Add. 5. From the Attribute list, select an attribute. 6. From Value, depending on the attribute, select a value for the attribute from a drop-down list, or enter a value. 7. Optional: To change access for the attribute, select a Role and Access. 8. Click Save and Close. 9. To edit other alert type information, see these topics: • Setting Alert Type Properties • Specifying Alert Type Instructions • Selecting the Alert Type Workflow • Assigning Alert Type Viewers • Adding Questions for Alert Types Viewing Alert Type History The system maintains a history of alert type actions. The History tab displays the components that were created or updated, the modification type, the old and new values, the user who made the modification, and the change date. The information on the History tab is read-only. To view alert type history: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Alert Types tab on the left. 3. Edit an alert type and select the History tab. 4. View the history, then click Save and Close. Viewing Alert Types In Alert Types, you can specify which columns to display for the list of alert types, or show all. You can also reorder columns, sort columns by ascending or descending order, or change the column widths. To display columns: Chapter 12 Managing Alert Types for Task Manager 12-191
- 445. 1. On the Home page, click Application, and then click Task Manager. 2. Click the Alert Types tab on the left. 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 or deselect the column names. • To reorder columns, select View, and then Reorder Columns, select columns and 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 are displayed, and then click Sort Ascending or Sort Descending. • To change column widths, hover over the column header dividers until the arrows display, and drag the columns to the desired width. Editing Alert Types You can edit the names and descriptions of alert types, and specify whether they are Enabled. When you enable an alert type, it is displayed in the list of available Alert Types. Normally, items in a locked schedule cannot be edited or modified. However, alerts associated with a locked schedule can be updated, have their workflow progress and even be removed from the schedule or deleted. To edit an alert type: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Alert Types tab on the left. 3. Select the alert type and click Edit. 4. Edit the alert type. 5. Click Save and Close. Chapter 12 Managing Alert Types for Task Manager 12-192
- 446. Searching for Alert Types You can use the Search function in the Alert Types list to quickly find alert types. You can enter full or partial names on which to search. Using the filter bar, you can control the alert types that you see in the list. By default, all alert types are displayed. To search for alert types: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Alert Types tab on the left. 3. To search for an alert type, enter search criteria in the Search text box. 4. Optional: From the filter bar, click on a category to display additional search operators such as Equals, Does Not Equal, Contains, Does Not Contain, Starts With, and Ends With. You can filter alert types using these categories: Name, Alert Type ID, Enabled, Description, Created By, Created On, Last Updated By, or Last Updated On. Note: • Click Add a Filter to view all categories. • To hide the filter bar, click the Filter icon. • To clear all filters, click Clear All Filters in the icon. Deleting Alert Types You 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: 1. On the Home page, click Application, and then click Task Manager. 2. Click the Alert Types tab on the left. 3. Select the alert type. 4. Click Delete, and then click OK. Using Task Manager Reports Related Topics • Generating Custom Reports for Task Manager • Creating a Task Manager Query • Creating a Template • Setting Up a Report Group Chapter 12 Using Task Manager Reports 12-193
- 447. • Creating a Report • Searching and Filtering Queries, Report Groups, or Reports • Generating the Report • Understanding Reports Security • Using Task Manager Report Binders • Generating Report Binders • Viewing Report Binders Generating Custom Reports for Task Manager You can create reports for Task Manager . The reports can be generated in PDF, CSV, HTML, or XLSX format. Note: Task Manager provides sample reports to assist you in getting started. You can use them as templates and can duplicate them as needed, then make modifications or extend access to users. To duplicate a report, select the report, then select Duplicate from the ellipsis button . You can then edit the newly created report. You can also create custom reports. Building custom reports involves four steps and can only be performed by a Service Administrator: • Create a Task Manager query from the New button of the Queries tab. See Creating a Task Manager Query . • Create a template. See Creating a Template. • Set up a report group. • Set up the report. To build custom reports, you create a query whose definition can then be exported as an 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 individual reports. Finally, generate the report, which uses both the query and the template you created and can be set with a default output of CSV, PDF, HTML, or XLSX. After you have built a custom report, the Service Administrator or other users who have been granted access can generate the report. See Generating the Report. Chapter 12 Using Task Manager Reports 12-194
- 448. Note: If you are managing your migration from Oracle Classic environment to Oracle Cloud Infrastructure (OCI) and have any custom reports, you may have to update the custom report's query definitions in the Target Service. This is because the internal IDs for objects (for example, Tasks, Journals, Attributes, etc.) may change during the migration. However, in case of Oracle managed migration, there will not be any change in the internal object IDs, so changes to custom report definitions is not required. Creating a Task Manager Query Creating a query is the first step in creating a custom report. To create queries: 1. From the Home Page, click Application, and then click Task Manager. 2. Select the Task Manager Reports tab on the left. 3. On the Queries tab, click New. 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 can specify for this parameter's value. Parameter Query allows you to present a list 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 instead a 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_PERIODS WHERE APP_ID=1 • Report Query : 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 roles and the reports to which they are assigned. To apply a Security Filter to a report query, add the following syntax to the end of the query WHERE CLAUSE statement. $FCC_SECURITY_CLAUSE$ When using$FCC_SECURITY_CLAUSE$ in the query, the FCC_TASKS must be aliased to TaskEO Because many predefined queries included with Task Manager have the Security Filter applied, you can use them as examples when building your own. For example, the following Report Query specifies scheduled tasks to display Task Code, Name, Assignee and Schedule for all High Priority tasks in the selected schedule. SELECT TaskEO.TASK_CODEAS "$TASK_CODE$", TaskEO.TASK_NAMEAS "$NAME$" , ((SELECT CASE WHEN FIRST_NAME IS NULL AND LAST_NAME IS NULL THEN USER_LOGIN ELSE FIRST_NAME||' '||LAST_NAME END FROM FCM_USERS WHERE Chapter 12 Using Task Manager Reports 12-195
- 449. 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 dialog assists you in creating a query against the database by allowing you to select any existing attribute in the product to be queried and/or filtered against. The system then generates the SQL to match the specified attributes and filters, at which time you 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 the user security filter to the generated query. This applies the Security token to the query, to be filled in with the correct SQL when the report is generated. b. Click Next. 7. From Select Columns, select the columns to display in the query, and then click Next. Chapter 12 Using Task Manager Reports 12-196
- 450. 8. From Select Filters, click Create Condition or Create Condition Group and select the conditions to create the filters to create the query. 9. Click 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. You can also select Validate from the drop-down list. Chapter 12 Using Task Manager Reports 12-197
- 451. The query displays in the Queries tab. Note: You can easily delete a query, or duplicate a query using the Action menu. • Click Validate and Explain Plan from the drop-down to validate the query and also generate the execution plan for this query. A .txt file that uses the same name as the query is generated. You can view or download the generated plan. Open this file to view the generated plan which contains the sequence of steps that is performed to run this query. If the performance of a query is suboptimal, you can use this plan to understand the cause of the problem and determine the best way to improve the query performance. Note: By default generation of execution plans is available only for OCI (Gen 2) environments. To enable it for Classic environments, contact Oracle using a service request. Modifying A Query A system administrator can edit a Task Manager query . 1. From the Home Page, click Application, and then click Task Manager. 2. Select the Task Manager Reports tab on the left. 3. Select the Queries tab if it's not already selected, and then Edit from next to the query you are editing. Note: If it is locked, ask the System Administrator to unlock. 4. Select Task Manager query. 5. In Edit Query, edit the information as needed. 6. After you are done with your changes, click Save and Close. Chapter 12 Using Task Manager Reports 12-198
- 452. Creating a Template Creating report templates is the second step in generating custom reports. Report templates are created in Microsoft Word with Oracle BI Publisher Desktop installed. Template creation also requires that you already generated the Sample XML during query creation. To create a report template: 1. Open Microsoft Word with a new document. 2. Select the BI Publisher tab, then select the Sample XML folder above Load Data. 3. Locate the SampleQuery.xml that was generated when you created the query and click Open. When the 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 Group By, select the fields to group by, and then click Next. 9. Select Sort By, select the fields to sort by, and then click Finish. 10. Save the template as an .rft file; for example: SampleQuery.rtf. Setting Up a Report Group Creating report groups is the third step in generating custom reports. A report group enables you to group individual reports together for Task 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 can duplicate a report group but its name must be unique. You can also delete a report group, 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 click Task Manager. 2. Select the Task Manager Reports tab on the left. 3. From the Report Groups tab, click New. 4. In the New Report Group window, enter: • Name: Enter a group name for the group of reports. • Description • Display to User: Select if you want this report group displayed to the user. Chapter 12 Using Task Manager Reports 12-199
- 453. The Display to User option enables report writers to have a group of reports hidden while they are working on them. 5. On the Reports tab, reorder or edit reports that have been added to the report group using the Move icons . 6. Click Save and Close. Creating a Report Creating report definitions is the fourth step in generating reports. Users can create reports from the queries and assign them to groups. To create report definitions: 1. From the Home Page, click Application, and then click Task Manager. 2. Select the Task Manager Reports tab on the left. 3. Select Reports, and then click New. 4. In New Report, enter: • Name • Description • Query: Select a query. • Template: Click Browse and then browse to a report template. You can upload any supported Oracle Business Intelligence Publisher template format. See Creating a Template. • 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 from one of the following options: – xlsx: Not supported for graphs. – html: Not supported for graphs and charts. – pdf – csv: Does not use a template and is better at faster data retrieval. – csv (Formatted): Is best suited for a simple data table with formatted data and does not support images, graphics, or styling in the template. Note: The csv (Formatted) output format takes additional time to generate the report to honor template formatting when compared to the csv format. Therefore, you can select csv to generate the data quickly or csv (Formatted) to generate formatted template based data. Chapter 12 Using Task Manager Reports 12-200
- 454. 5. To complete the report definition, you must set the parameters and access: a. For Parameters, select the Parameters tab. Parameters from the query are identified and added to the list. Update the following: • Display Name • Parameter Type: The available options are: – Task Manager – Task Manager Attribute – Text – Date – Date/Time – Number – Query – Integer – True/False – Yes/No – User • Display To User: Clear the checkbox if you do not want the parameter to be displayed and want the value to be used. You can use a single query to create multiple reports. In such scenarios, few parameters are hidden and values defined in the Parameters tab are used. • Attribute/Query: For Attributes, the drop-down lists the attributes for Task Manager. For Query, the drop-down lists all queries of the Parameter Type. This can be used to make parameters such as dynamic LOVs. See Creating a Task Manager Query • Parameter Value: The default value is displayed. b. For Access, select the Access tab. c. From the drop-down lists, select the Application Module, then select a Role for the Application Module. For example, you can select Task Manager for the Application Module, then select to assign access to the Power User role. You can use Add (+) or Remove (X) to change the list of users who can access the report. Note: The report must be granted access to at least one application module for the report to display in the corresponding Reports tab. 6. Click Save and Close. Chapter 12 Using Task Manager Reports 12-201
- 455. Searching and Filtering Queries, Report Groups, or Reports Using the search field and filter options, you can control the records that you see in the list of queries, report groups, or reports. To filter queries, report groups, or reports: 1. From the Home Page, click Application, and then click Task Manager. 2. Select the Task Manager Reports tab on the left. 3. Select the Queries, Report Groups, or Reports tab. 4. Enter search criteria in the Search text box. 5. Optional: From the filter bar, click on a category to display additional search operators such as Equals, Does Not Equal, Contains, Does Not Contain, Starts With, and Ends With. Note: • Click Add a Filter to view all categories. • To hide the filter bar, click the Filter icon. • To clear all filters, click Clear All Filters in the icon. Generating the Report Generating reports is the final step in the process. After a Service Administrator has built the custom report, any user or group granted access can generate the report. A Service Administrator can also use REST API commands to generate a report. For detailed information, see Generate Report for Financial Consolidation and Close and Tax Reporting in REST API for Oracle Enterprise Performance Management Cloud. For large reports, the runAsync parameter for report generation in REST API allows reports to run asynchronously (value of true). To generate reports: 1. From the Home Page, click Tasks, and then select the Reports tab on the left. 2. Select the report you want to generate. You can use the quick Search option to find a report under a selected group. 3. For Output Format, select from the following: • xlsx: Not supported for graphs. • html: Not supported for graphs and charts. • pdf • csv: Does not use a template and is better at faster data retrieval. Chapter 12 Using Task Manager Reports 12-202
- 456. Note: For reports that contain more than 10,000 records, it is recommended to use the csv format. • csv (Formatted): Is best suited for a simple data table with formatted data and does not support images, graphics, or styling in the template. Note: The csv (Formatted) output option takes additional time to generate the report to honor template formatting when compared to the csv format. Therefore, you can select CSV to generate the data quickly or csv (Formatted) to generate formatted template-based data. 4. Click Generate. 5. Enter the Name, and then select the Schedule and Period from the drop down menus. 6. Click Generate. When done, the system displays a "Completed Successfully" status message. Note: • Click Back to preserve the parameter values that you have selected and regenerate the report. • Click Reset to clear the parameter values that you have selected and regenerate the report. 7. Select Open with or Save File to save the ZIP file. The report generation process uses a backend job framework that runs report jobs in the background. If the report has an error, for example, if the size is greater than the recommended size, you see a message stating the error in the Generate Report dialog before the report is generated. For reports with very large number of records, it is recommended to use filtering to break the report down to fewer records. Understanding Reports Security This topic describes the security for standard reports and custom reports in Task Manager . Note: A Service Administrator can also use REST API commands to generate user details report. For detailed information, see Generate User Details Report for Account Reconciliation, Financial Consolidation and Close, and Tax Reporting in REST API for Oracle Enterprise Performance Management Cloud . Chapter 12 Using Task Manager Reports 12-203
- 457. Standard (Predefined) Reports Security A security clause is in all standard report queries. This means that the reports have a security filter enforced on these reports by default. For example, Power User security (established under Access Control), to allow access to certain tasks is enforced on reports. A Power User with access to only certain tasks can only see reports for those tasks. Administrators can edit reports to give users access to a report using the Access tab in the Edit Report dialog. This ensures that if you allow users to see reports, they can only see data appropriate for them as determined by the Administrator. The security clause is also included as part of the following predefined Task Manager reports: • At Risk Tasks • Task Compliance Analysis • Early Tasks • Late Tasks • Task Performance Analysis by Organizational Unit • Rejected Tasks • Task Audit Trail • Users with Late Tasks Assigning User Access to Standard Reports An Administrator can decide to give access to standard reports to various users. This is done by using the Access tab on the Edit Report dialog. To grant users access to a report: 1. From the Home Page, click Application, and then click Task Manager. 2. Select the Task Manager Reports tab on the left. 3. From Reports, select the report you want, and from Actions, select Edit. 4. On the Edit Report dialog, under Access, you can use Add (+) or Remove (X) to change the list of users who can access that report. 5. Click Save or Save and Close. Custom Reports Security For custom reports, you can determine when you create your query whether you want to have a security clause inserted into the query and then assign access to the report to users. This means that the creator of the report determines who should be given access. Using Task Manager Report Binders Task Manager report binders enable you to create a history of all activities that occurred as part of a schedule, for example, the Corporate Q1 Close. You use filters to specify the schedule, tasks to include, and which task information to include. Chapter 12 Using Task Manager Reports 12-204
- 458. Information for all tasks that meet the binder filter criteria are output in HTML to a ZIP file. They contain HTML and other files. When you extract the ZIP file, a directory structure 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, or emailed for internal or external reviews. Generating Report Binders The Generate Report Binder dialog box enables you to specify the parameters needed to create a report. When you open a schedule in a view and run Generate Report Binder, the report binder is applied to the current view and incorporates only the tasks within 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 or to save it to disk as a ZIP file. You can generate report binders for multiple schedules at a time. This can be helpful if your 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 a report binder. 2. From the Actions dropdown, select Generate Report Binder. 3. For Report Binder Name, enter a name. 4. For Description, enter a binder description. 5. From Optional Components, select the task components that you want to display in the report: • Alerts • Comments • Attachments Note: Including attachments in the report greatly increases the size of the report 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 the bottom. 8. Select a directory for the ZIP file, click Save, then Close. Viewing Report Binders When you generate a report binder, it is output in one zipped file. The ZIP file name is the name that you specified for the Report Binder. The report pages are merged into an HTML report, with page breaks for sections as required, so that the report can be printed with a print command. If you choose to include attachments, a separate attachment appendix, containing Chapter 12 Using Task Manager Reports 12-205
- 459. links to attachments with corresponding tasks and alerts, is created, which you can print separately. All attachments are downloaded to separate 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 can see the report binder by opening the HTML page in the directory. The first report page contains information on the report binder, the schedule, and displays a list of tasks and alerts available in the report binder. You can navigate to the Tasks section to see task details such as status, Assignee, start and end dates, and duration. If a task has not started, the projected (scheduled) date is displayed. Each task is a link to a Task Detail page. By default, it includes sections for Attributes, Instructions, Questions, Workflow, Predecessors, and History. If you selected the options to include Alerts and Comments 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 the Alert 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-click the file. 2. Extract the ZIP files to the desired directory. 3. Navigate to that directory and locate the subdirectory that matches the ZIP file name. 4. From the subdirectory, double-click report_binder_name.html to view the report binder. Chapter 12 Using Task Manager Reports 12-206
- 460. 13 Designing Dashboards Design dashboards that show summary data to users. Dashboards enable users to chart, evaluate, highlight, comment on, and even change key business data. Related Topics • The Power of Dashboards • Creating and Managing Dashboards The Power of Dashboards Dashboards typically provide an overview to users at the beginning of their planning and forecast process by showing summary data. The versatility of dashboards enables users to chart, evaluate, highlight, comment on, and even change key business data. They can change a driver in a form that's in a dashboard and immediately see its impact in other forms and charts: Sample 1.0 Dashboard with a Form and a Chart Sample 2.0 Dashboard with Multiple Charts 13-1
- 461. You create dashboards by simply dragging and dropping a variety of objects from the library panel on the left to the dashboard workspace. With dashboards, you can: • Include up to six forms that dynamically update, including their associated charts, as users change data in the form. • Include up to nine charts or tiles. Tiles display a specific value from the cube. To provide the value for each tile, you can specify a form or a cell intersection as a data source. • Switch easily between using the design mode and runtime mode, so you can see exactly what the dashboard user will see. • Depict data interactively with a wide variety of chart types such as area, bar, bubble, column, combination bar and line, doughnut, funnel, gauge, scatter, radar, and so on. • Control the dashboard’s layout. • Depending on the form design, enable users to drill down into underlying detail and select which members to work with. • Include user variables in the global POV bar and the local POV. • In certain charts, customize the colors and line width, and show or hide gridlines. • In 1.0 dashboards: – Add links to dynamically display external Web pages. – Include explanations of data called Commentary in the dashboard. – Tag a form as master and then filter members from the master form to detail forms or charts within the same dashboard. • In 2.0 dashboards: – Add hierarchical labels in charts. – Use a logarithmic scale in relevant chart types. – Add a secondary Y-axis in relevant chart types. Chapter 13 The Power of Dashboards 13-2
- 462. When users use a dashboard (referred to as runtime), they can set many aspects of the object, such as the type of chart displayed, the dashboard’s title, and so on. A toolbar is available for each object type. Dashboard users can change and save data, run rules, and so on. However, changes made in runtime to the chart type options aren't saved for the next session. Clicking Save in runtime saves the data, but not the dashboard definition. Service Administrators create, redesign, delete, and assign permissions to dashboards and dashboard folders. Videos Your Goal Watch This Video Learn how to create 1.0 dashboards. Creating Dashboards in Oracle Planning and Budgeting Cloud Learn how to create 2.0 dashboards. Designing Dashboards 2.0 in EPM Cloud Planning Related Topics • About Dashboard Versions • Concepts in Designing 1.0 Dashboards • Concepts in Designing 2.0 Dashboards • Creating and Managing Dashboards Creating and Managing Dashboards • About Dashboard Versions • Creating and Managing Dashboards 1.0 • Creating and Managing Dashboards 2.0 About Dashboard Versions Dashboards are currently available in two versions: • Dashboard: Uses Oracle ADF technology • Dashboard 2.0: Uses Oracle JET technology Both dashboard versions currently coexist in the same business process at the same time. Existing dashboards (Dashboard) use ADF technology and the behavior of the ADF-based dashboards remains unchanged. You can still create and update these dashboards in your business process as you did before. Dashboard 2.0 uses the existing dashboard functionality and enhances it with Oracle JET technology for faster rendering, sophistication, ease of use, improved flexibility, better visualization, and additional designs. Dashboard 2.0 supports new chart types like Waterfall, Pyramid, and Geomap and new sub- chart types for Radar, Combination, and Gauge charts. It also supports creating tables in dashboards with visual inline views of data, called Spark Charts. To help you differentiate between the dashboard versions on the Dashboards listing page, we've provided an icon in front of each dashboard: Chapter 13 Creating and Managing Dashboards 13-3
- 463. • : Dashboard (1.0) If you open a dashboard with a Dashboard (1.0) icon, you'll be working with the ADF functionality to edit the dashboard. • : Dashboard 2.0 If you open a dashboard with a Dashboard 2.0 icon, you'll be working with the JET functionality to edit the dashboard. When you create a new dashboard, select from the following dashboard versions: • Dashboard • Dashboard 2.0 Related Topics • Creating and Managing Dashboards 1.0 • Creating and Managing Dashboards 2.0 Creating and Managing Dashboards 1.0 • Concepts in Designing 1.0 Dashboards • Creating Dashboards 1.0 • Creating Dashboards Containing Master Forms and Details • About Your Dashboard's Layout - Version 1.0 • About the Gauge Chart Type • About the Tile Chart Type • Customizing Dashboard Colors • About Global and Local POVs in 1.0 Dashboards • Dashboard POVs and Valid Intersections Concepts in Designing 1.0 Dashboards Helpful information as you design 1.0 dashboards: Chapter 13 Creating and Managing Dashboards 13-4
- 464. • On the left is the design palette. Simply drag and drop objects from the palette to the canvas. Tip: Drag an object to a border line. The drag icon changes to a plus sign when you can drop the object in an allowed space. See About Your Dashboard's Layout - Version 1.0. • On the top right are settings for the entire dashboard: • Click Settings to set these general aspects of the dashboard: Table 13-1 Dashboard General Settings Option Description Use name as title By default, this option is selected. Clear this option to give the dashboard a title with custom formatting. Borders When you create a new dashboard, borders are hidden by default. To show borders in newly-created dashboards, select Show. Layout Select Fixed (default) or Flexible. POV Bars Select Show (default) or Hide. Global POV Bar Select Enable (default) or Disable. For information about POVs, see About Global and Local POVs in 1.0 Dashboards. • When you hover over a dashboard object, a toolbar for that object displays in the upper right corner: Chapter 13 Creating and Managing Dashboards 13-5
- 465. Note: Dashboard (1.0) hover icons provide options such as Instructions (available only if instructions are configured for a form), Actions, Save, Refresh, Settings, and Maximize, depending on the type of object. • As you create a dashboard, click Runtime so that you can immediately see how the dashboard looks and works to a dashboard user. To return to designer mode to continue designing the dashboard, click . • By default, missing or suppressed data is plotted as zeros in graphs. You can clear the Plot Missing Values as Zero setting to ignore missing or suppressed data in certain chart types so it's no longer plotted as zeros. • The listing page for dashboards supports folders. Folders enable you to assign permissions to all dashboards within a folder rather than assigning permissions to each individual dashboard. The dashboard listing page uses the same folder hierarchy as infolets and data entry forms and all artifacts and folders reside under a root folder called Library. Note: Only administrators can add files (for example, dashboards, infolets, forms, reports, and so on) to the Library root folder. • On the listing page for dashboards, you can toggle between viewing dashboards by a flat view or a tree view: Then you can search for dashboards using Search . The flat view displays only the dashboards that meet the search criteria, not the folders that contain them. The tree (or hierarchical) view displays dashboards in the context of the folders that contain them. To search on another keyword, clear the search criteria by clicking in the Search box. Creating Dashboards 1.0 Need help deciding which dashboard version to choose? See About Dashboard Versions. Note: To create a version 2.0 dashboard, see Creating Dashboards 2.0. 1. From the Home page, click Dashboards, and then click Create. Chapter 13 Creating and Managing Dashboards 13-6
- 466. 2. From the options provided, select Dashboard. 3. Enter a name by clicking the default dashboard name and entering a new name in the input box. You can give the dashboard a title with custom formatting, click Settings, clear Use name as title, and then enter the title and set formatting the dialog box. 4. From the design palette on the left, drag and drop objects onto the dashboard canvas. Select from these objects: Table 13-2 Dashboard Objects Object Description Forms Select forms to include in the dashboard by navigating to the forms folders or by searching for them by name. To view instructions for forms after they've been added to the dashboard, hover over the form and click Instructions . The access permissions set for forms are honored in dashboards. Chapter 13 Creating and Managing Dashboards 13-7
- 467. Table 13-2 (Cont.) Dashboard Objects Object Description Chart Types Select the chart types to include in the dashboard. When first added, a selected chart has sample data. You then associate it with a form as its data source. When you link a chart to a form, users can immediately see the impact of changing data in the form on the associated charts. By default, missing or suppressed data is plotted as zeros. For selected chart types (Area, Bubble, Combination, Line, Radar, and Scatter), you can disable this setting by clearing the Plot Missing Values as Zero option in the chart's settings. When this option is cleared, the missing or suppressed data is ignored and is no longer plotted for those chart types. The Combination chart type alternates displaying row data with vertical bars and lines in the chart. For example, the data in row 1 of a form is displayed as a bar and the data in row 2 as a line, with alternating chart types for even and odd-numbered rows. Although the Combination chart type can display up to 20 rows of data, it’s particularly useful when you want to compare two categories of data. For example, you want to compare Germany and France’s average exchange rates over several years, so the form has Germany rates in row 1 of the form, and France’s rates are in row 2. For information on the Gauge chart type, see About the Gauge Chart Type. The Tile chart type, sometimes called performance tiles, lets you select specific values from the cube to display. See About the Tile Chart Type. Commentary Select External Artifacts, and then Commentary. Enter text that explains the data or charts. Note that the text limit is 2000 characters, including any formatting tags that are added for rich text. URL Dynamic web page summary. Select External Artifacts, and then URL. Insert only external site URLs starting with the https:// security protocol. Don't use internal or relative URLs or URLs for unconsenting third party sites such as google.com. 5. Customize the dashboard using the dashboards settings and the objects’ hover toolbar, and then click Save. See About Your Dashboard's Layout - Version 1.0. You can easily duplicate and modify a dashboard using Copy As on the Dashboard list page. Select the Actions icon next to the dashboard you want to copy. Creating Dashboards Containing Master Forms and Details You can design dashboards that have one master form and multiple detail (or target) objects (forms or charts). When you do so, the selection of members in the master form automatically filters to the members in the target objects, and the target objects show only the details that are relevant to the members highlighted in the master form. Considerations when designing dashboards with master forms and target objects: • Master forms must always be a form (you cannot tag a chart as a master form). Chapter 13 Creating and Managing Dashboards 13-8
- 468. • The target objects can be forms or charts. • The dashboard containing a master form must always contain more than one object. • Only one form on a dashboard can be tagged as master. If you want to tag a different form on a dashboard as master, you must first untag the existing master form. To create a dashboard containing a master form and target objects: 1. Create a dashboard with at least one form and one or more target objects. See Creating and Managing Dashboards. 2. Ensure the dashboard is in designer mode by clicking Actions, and then clicking Edit. 3. Select the form on the dashboard that you want to designate as master, click the Settings icon for that form, and then select Tag as Master. To filter the data in the target forms or charts that is relevant to the data in a master form, right-click the relevant data in the master form and select Apply Context. About Your Dashboard's Layout - Version 1.0 About setting up a dashboard layout in version 1.0: • 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 objects next to each other, each occupying half the space, and the other to place three objects, each occupying a third of the space. • You can design a dashboard with objects to display vertically, horizontally, and each can have its own size. • To resize an object that uses Flexible layout, drag the object’s border. You can also click an object's handle to expand it, and then click the handle again to restore the object to its original size. • To resize an object that uses Fixed layout, set its width or height percentage in Settings. • 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 are displayed so that the designer can choose to remove them. About the Gauge Chart Type Gauge chart types are handy for showing whether data values fall within an acceptable range or not. You set the maximum value, the range maximums, and the gauge displays ranges as red, yellow, and green to help you quickly assess a current value. So, gauge chart types help you identify problems in important data points or measures. For example, you could use a gauge to display the current sales, where the thresholds are set to represent the sales targets. If the form has multiple values, you can display multiple gauges, up to a maximum of 36 (the values in the first 6 rows and the first 6 columns in the form). The remaining values 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. Chapter 13 Creating and Managing Dashboards 13-9
- 469. You can select either a dial gauge or a status meter gauge. You can display a status meter gauge using either horizontal or vertical bars. Dashboard designers can set: • Maximum Value: The highest value on the gauge. The dashboard designer sets the Maximum Value as a default, and then users can temporarily change it at runtime. If the dashboard designer doesn't specify a maximum value, the application automatically sets the maximum value as greater than the value on the gauge. • Thresholds: – Low, Medium, and High thresholds: To visually indicate whether a measure lies in the acceptable range or not, these thresholds enable you to display the gauge in red, yellow and green based on the specified values. – Thresholds where low values are desirable. – Appropriate labels for the thresholds that are displayed when hovering over the thresholds in the gauge. For example, here's a form's data: Chapter 13 Creating and Managing Dashboards 13-10
- 470. Here's the resulting dial gauge: Here's the resulting status meter gauge with vertical bars: Chapter 13 Creating and Managing Dashboards 13-11
- 471. 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 application needs the middle threshold value to calculate the chart. About the Tile Chart Type A tile is a chart type that lets you select specific values from the cube to display. In addition to using a form as a data source, you can directly enter a cell intersection that provides the value for a tile. You can have up to 6 tiles across, and 4 rows down in a dashboard, and give them a title. Until you associate a tile with data, it displays sample data. 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. Note: Sometimes in a form, the first column may be collapsed (hidden) when viewed as a grid. But the collapsed column is still considered when the tile 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 by row. • You can set the tile’s title, the tile’s height percentage, legend, and can select which axes from the form to include. For example, if you select a form with three rows, the tile displays three values. With a cell intersection as the data source for a tile, you can have only one tile per object. Tip: To select a tile chart type, expand the list of chart types by clicking the link at the bottom of the list. Here are options you can set for a tile chart type. Note that you can set whether the displayed value is horizontally aligned in the tile to the left, the center, or the right. Chapter 13 Creating and Managing Dashboards 13-12
- 472. Scaling Large Numbers Especially 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, the tile displays the value as 1689K. Your scaling options: • None: No scaling is applied. • Auto: The value is displayed based on its range. For example, 1,500 displays as 1.5K, 1,689,000 displays as 1.69M, 42,314,531,211 displays as 42.31B, and 1,234,567,891,234 displays as 1.23T. • K: The value is displayed as thousands units. For example, 1689000 displays as 1689K. • M: The value is displayed as millions units. For example, 123,456,789 displays as 123M. • B: The value is displayed as billions units. For example, 12,345,678,912 displays as 12B. • T: The value is displayed as trillions units. For example, 1,234,567,891,234,567 displays as 1,234T. Customizing Dashboard Colors Maybe your company uses a standard set of colors in charts to denote different types of data. For example, dark blue might represent actual data versus light blue for budget data. When you customize dashboard colors, you select colors in the order of rows on the form. Series 1 represents the first row of data, and so on. You can assign each 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. Chapter 13 Creating and Managing Dashboards 13-13
- 473. 3. Clear the Default check box, and then click the down arrow for the Series you want to change. Check the chart in the background to see the data type that each series represents. 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, click Custom Color.... Your selections apply only to the current chart. Follow these steps to change the colors of other charts in the dashboard. About Global and Local POVs in 1.0 Dashboards A local POV on a form reflects the dimension members the form designer selected for that form. Dashboards also support global POV bars, so that the local POVs that are common are combined in the global POV bar to avoid repeating them in each object. Dashboard 1.0 POVs Example Here's a 1.0 dashboard showing a global POV bar (showing Entity, Product, and Year) and a local POV (the Plan drop-down list showing Q2): Chapter 13 Creating and Managing Dashboards 13-14
- 474. 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 displays at the top of the dashboard above all the objects, while the local POV bar displays within the object. User variables are supported in both global and local POVs in dashboards and you can change dynamic user variables directly from the POV bar. In dashboard Settings, you can set whether to show or hide POVs and whether to enable or disable global POV bars. (If you select Hide for POV Bars, and Enable for Global POV Bar, the Hide option overrides the Enable option.) The global POV bar is enabled by default; if you disable it, the complete POV is displayed for each local POV as applicable. About global POV bars: • The POV Bar is made up of local POV dimensions, Page dimensions and user variables. • Depending on the local POV and page of each form on the dashboard, the global POV bar is automatically calculated. • They are reflected in the other objects using forms in that dashboard. That is, they apply to forms in a dashboard, to charts that are linked to forms, and to tiles that use forms as a data source. So if the dashboard doesn’t include a form as a data source, 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 POV dimensions 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 a dashboard, the complete POV for a dashboard object may get split between the local and global POV bar. The global POV bar and the local POV together contain the complete intersection information for each form on a dashboard. Chapter 13 Creating and Managing Dashboards 13-15
- 475. If there is only one object on the dashboard that uses a form as a data source, then the 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, then this is how the application determines which dimensions go in the global POV bar or stay in the local POV: • If the dimension is in the POV or page of all the forms, and the member selection is 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, then the dimension stays in the local POV. • If the dimension is in the POV, then the same members must be selected in all the forms for the dimension. • If the dimension is a page dimension, then the selected page members must be the same and display in the same order in all the forms. The POVs in 1.0 dashboards honor valid intersections by hiding invalid Page members. See Dashboard POVs and Valid Intersections. Dashboard POVs and Valid Intersections The POVs in dashboards honor the valid intersections by hiding invalid Page members. Just like in forms, the Page drop-down list is filtered for all selected members in the POV and Page dimensions. Because dashboards support both global and local POVs, the context for filtering the Page drop-down list depends on which POV the members are located. If the Page drop-down list is on a global POV, the filtering context is only the global POV dimensions. If the Page drop-down list is on the local POV, the filtering context is all the global dimensions plus the dimensions on a chart’s local POV. See also About Global and Local POVs in 1.0 Dashboards. Creating and Managing Dashboards 2.0 Related Topics • Concepts in Designing 2.0 Dashboards • Creating Dashboards 2.0 • About the Geomap Chart Type • About the Pyramid Chart Type • About the Waterfall Chart Type • Using Tables in Dashboards • About the Gauge Chart Type for Dashboard 2.0 • About the Radar Chart Type for Dashboard 2.0 • About the Combination Chart Type for Dashboard 2.0 • About Global and Local POVs in 2.0 Dashboards • About Quick Analysis Chapter 13 Creating and Managing Dashboards 13-16
- 476. Concepts in Designing 2.0 Dashboards This topic contains helpful information as you design 2.0 dashboards: Dashboard 2.0 Designer The Dashboard Designer consists of the following dashboard components: • Library Panel • Dashboard Toolbar • Dashboard Workspace • Properties Panel • Dashboard Objects Data Sources for Charts Dashboard 2.0 supports ad hoc grids, forms, and cubes for choosing the data. You pick the data sources from the library panel. Note: You can include a maximum of nine components (charts) in a dashboard. • The Data Source Type property shows the selected data source in the tab of the properties panel. • When using a cube as the data source for quick analysis, drag and drop a cube from the library panel to the dashboard workspace, then click in the Search box and either enter Chapter 13 Creating and Managing Dashboards 13-17
- 477. the member name or launch the member selector to choose members. The tab will then display in the properties panel where you can pivot the dimensions and choose which dimensions appear on the POV, row, or column axis. See About Quick Analysis. Note: There is an upper limit of 50 members across all dimensions that can be selected to create a chart using quick analysis. This limit together with the number of dimensions in the cube will determine the maximum size of the grid that is supported for a chart based on quick analysis. • When the data source is a form or an ad hoc grid, the data is fetched using the form definition. You can change the source form by clicking the Form property in the tab of the properties panel. Note: Only forms with a maximum of 100 cells on a column and 100 cells on row for a total of 10,000 cells, including row and column header cells, can be visualized in a chart. More Helpful Information About Dashboards 2.0 • As you create a dashboard, click and then select Run Dashboard to immediately see how the dashboard looks and works to a dashboard user. To return to designer mode to continue designing the dashboard, click and then select Edit Dashboard. • To help you differentiate between the dashboard versions on the Dashboards listing page, we've provided an icon in front of each dashboard: – : Dashboard (1.0) – : Dashboard 2.0 • By default, missing or suppressed data is plotted as zeros. For selected chart types (Area, Bubble, Combination, Line, Radar, and Scatter), you can disable this setting by selecting the Plot Missing Values as Zero option in the chart's settings. When this option is cleared, the missing or suppressed data is ignored and is no longer plotted as zeros for those chart types. • The listing page for dashboards supports folders. Folders enable you to assign permissions to all dashboards within a folder rather than assigning permissions to each individual dashboard. The dashboard listing page uses the same folder Chapter 13 Creating and Managing Dashboards 13-18
- 478. hierarchy as infolets and data entry forms and all artifacts and folders reside under a root folder called Library. Note: Only administrators can add files (for example, dashboards, infolets, forms, reports, and so on) to the Library root folder. • On the listing page for dashboards, you can toggle between viewing dashboards by a flat view or a tree view: Then you can search for dashboards using Search . The flat view displays only the dashboards that meet the search criteria, not the folders that contain them. The tree (or hierarchical) view displays dashboards in the context of the folders that contain them. To search on another keyword, clear the search criteria by clicking in the Search box. Videos Your Goal Watch This Video Learn how to create a dashboard with multiple components in the Dashboard Designer for Dashboards 2.0. Creating Dashboards in Dashboards 2.0 Library Panel On the left side of the Dashboard Designer is the library panel where you select the content for dashboard objects. Simply drag and drop objects from the library panel to the workspace or search for content using the Search box. Content in the library panel is grouped into these categories: Table 13-3 Library Panel Content Categories Icon Description Cubes Library (ad hoc and standard forms) Visualizations (charts) Tip: You can minimize and maximize the library panel by hovering over the panel and clicking the horizontal bar that displays on the middle right. Chapter 13 Creating and Managing Dashboards 13-19
- 479. Dashboard Toolbar In the upper right corner of the Dashboard Designer is the dashboard toolbar where, in addition to saving and closing your dashboard, you can perform these dashboard tasks: Table 13-4 Dashboard Toolbar Icon Description Adds a new empty dashboard widget to the design canvas (this is an alternative to drag and drop) Hides and unhides the Properties Panel Click to perform these actions: • Revert to Saved: Resets the Dashboard Designer to a previously saved state • Refresh Data: Refreshes the data from Essbase and updates the dashboard definition from the database • Run Dashboard: Hides all Dashboard Designer elements and displays the dashboard as it would appear to users during runtime • POV Bar : Hide Dimension Labels: If your dashboard contains a global POV bar, select to hide the dimension names on the global POV bar. Clearing this option once again displays dimension names on the global POV bar. • POV Bar : Auto-Apply: If your dashboard contains a global or local POV, enable this action to automatically apply changes to the POV. If you don't want to automatically apply changes, clear this option. When cleared, Apply and Reset buttons will display on your POVs to manually apply or clear your changes. Dashboard Workspace To the right of the library panel is the dashboard workspace. In addition to drag and drop, you can use the Search box to specify or search for the data you want to display for each widget (an empty object in the dashboard workspace into which you can add a dashboard object). • The first object you drag and drop occupies the entire workspace, then drag additional objects from the library panel to the left, the right, the top, or the bottom of the existing object. • To move an object to another part of the dashboard, click the object, and then hover your cursor over the upper edge of the object until you see the drag icon. Drag and drop the object to the left, right, top, or bottom of another object and the other objects on the dashboard will move and realign. • To maximize an object so it fills the canvas, click , and then click Maximize. The object will fill the workspace, and the other objects on the workspace will be Chapter 13 Creating and Managing Dashboards 13-20
- 480. hidden. Clicking and then Restore resizes the object to its original size and makes the other objects in the workspace visible again. • To change the height and the width of objects in the dashboard, select a dashboard object, then in the Properties panel on the right click to view and change the object's height and width. Note: In runtime mode, if a user doesn't have access to an object like a form, or if the form is missing, then an adjacent object will take its space. In designer mode, all empty objects are displayed so that the designer can choose to remove them. Properties Panel On the right side of the Dashboard Designer is the Properties Panel where you can set general properties for the entire dashboard as well as object-specific properties: Table 13-5 Properties Panel Icon Description Set general properties for the entire dashboard such as displaying object borders, hiding POV bars, enabling global POVs, and choosing a background color for your dashboard. For information about POVs, see About Global and Local POVs in 2.0 Dashboards. Set properties for selected objects in the dashboard such as object height, width, and background color. You can also change the object and data source type. Chapter 13 Creating and Managing Dashboards 13-21
- 481. Table 13-5 (Cont.) Properties Panel Icon Description Set display properties for the selected object such as how to scale values, show or hide row dividers or grid lines, choose different font sizes and colors for headers and data, set orientation vertically or horizontally, define legend positions, add spark charts to tables, and so on. Note: For data visualizations in Dashboard 2.0, the custom color palette now supports only 12 colors instead of 15. If you created a dashboard in 21.07 or earlier and you used 15 colors in your visualization, you will continue to see 15 colors at runtime. However when you try to change the custom colors, the dashboard designer will only display 12 colors from which you can select and save. Set POV, Row, and Column properties for the selected cube for quick analysis. Dashboard Objects When you hover over an object in the workspace, a toolbar for that object displays in the upper right corner: Table 13-6 Dashboard Object Toolbar Icon Description Displays the object data as the selected chart type Click to perform the following actions on the selected dashboard object: • Refresh: Requeries the data and displays the chart with the data • Maximize: Hides the other objects and displays the selected chart in full canvas mode • Restore: If an object is maximized, restores the object to its original size and makes the other objects on the canvas visible again • Delete: Removes the selected object and, when the dashboard is saved, removes it from the database. If you close the dashboard without saving, the object is restored when the dashboard is reopened. Chapter 13 Creating and Managing Dashboards 13-22
- 482. Creating Dashboards 2.0 Need help deciding which dashboard version to choose? See About Dashboard Versions. Note: To create a version 1.0 dashboard, see Creating Dashboards 1.0. To create a version 2.0 dashboard: 1. From the Home page, click Dashboards, and then click Create. 2. From the options provided, select Dashboard 2.0. 3. Enter a name for the dashboard by clicking the default dashboard name and entering a new name in the input box. 4. Drag and drop content from the library panel on the left onto the dashboard workspace. Customize the dashboard using the dashboard settings and properties. For a detailed description of the Dashboard Designer, see Concepts in Designing 2.0 Dashboards. 5. Click Save. You can easily duplicate and modify a dashboard using Copy As on the Dashboard listing page. Select the Actions icon next to the dashboard you want to copy. Chapter 13 Creating and Managing Dashboards 13-23
- 483. About the Geomap Chart Type Geomaps are geographical maps with overlays and charts that display some measure about each of the geographical areas that are displayed. Hovering over the bubbles or the color highlight in the Geomap displays a data label. Note: Color highlight geomaps are designed to show any variances (red or green, depending upon your Desired Variance Trend setting) based on the values in the underlying data. If a geomap region has missing values in the 1st or 2nd column or if the values in those columns are equal and there is no variance, the region will be highlighted blue. Hovering over a highlighted region displays a bar chart with all the values for the row except for any missing values. Example Geomap - USA Sales Using Data Bubbles Example Geomap - World Sales Using Color Highlight Chapter 13 Creating and Managing Dashboards 13-24
- 484. Dashboard designers can set these geomap chart properties: Table 13-7 Geomap Chart Properties Setting Description Map Layer Select World or narrow the scope of the map to a continent such as Asia, North America, or Africa. Type The Data Bubbles geomap displays data as sized bubbles over the map layer. The Color Highlight geomap compares two data values, displaying geographical areas that have an increase in green, and those with a decrease in red. Select Data Bubbles or Color Highlight and then specify the following additional options: • For Data Bubbles, select the desired settings for Label (Show or Hide), Label Color, and Bubble Color. • For Color Highlight, specify the Desired Variance Trend (Increase or Decrease). Geography Names We've provided you with a metadata load file that contains the geographical elements the geomap uses like countries, states, and cities. Click to download a CSV file which you can then upload into a dimension as new members or (with some manual changes) as aliases to existing members in your application. Note that geomaps only work if the geography names in the forms match exactly the geography names that Dashboard 2.0 uses for its map layers. So if your entity/geography dimension says, for example, USA, that won't be recognized as a valid name in the map layer, which uses United States. Videos Your Goal Watch This Video Learn how to download geography members for geomap charts, then import them into your dimension. You learn how to set up both data bubble and color highlight geomap charts. Creating Geomaps in Dashboards 2.0 About the Pyramid Chart Type Pyramid chart types use a triangle diagram to represent hierarchies visually. The triangle is divided into sections, illustrating vertically top-down and broad-narrow structures and processes. Example 3D Pyramid Chart Chapter 13 Creating and Managing Dashboards 13-25
- 485. Dashboard designers can set these pyramid chart properties: Table 13-8 Pyramid Chart Properties Setting Description Legend Position Choose Left, Right, Top, Bottom, or None. Value Scale Especially useful for large numbers, you can scale how a value is displayed. For example, if the value is 1,689,000 and you select K - Thousand as the scaling option, the chart displays the value as 1,689K. Your scaling options: • None: No scaling is applied. • Auto: The value is displayed based on its range. For example, 1,500 displays as 1.5K, 1,689,000 displays as 1.69M, 42,314,531,211 displays as 42.31B, and 1,234,567,891,234 displays as 1.23T. • K - Thousand: The value is displayed as thousands units. For example, 1,689,000 displays as 1689K. • M - Million: The value is displayed as millions units. For example, 123,456,789 displays as 123M. • B - Billion: The value is displayed as billions units. For example, 12,345,678,912 displays as 12B. • T - Trillion: The value is displayed as trillions units. For example, 1,234,567,891,234,567 displays as 1,234T. 3D Graph Choose Yes to visualize the data as a 3D chart. Color Select Default or click a section of the pyramid chart and choose a custom color for that section. About the Waterfall Chart Type Waterfall charts display a running total of positive and negative values, which is helpful in showing how you arrived at a net value from an initial value. Waterfall charts are used to portray how an initial value is affected by a series of intermediate positive or negative values. Usually the initial and the final values (end points) are represented by whole columns, while the intermediate values are shown as floating columns that begin based on the value of the previous column. The columns can be color-coded to distinguish between positive and negative values. Chapter 13 Creating and Managing Dashboards 13-26
- 486. Example Waterfall Chart - Inventory Analysis This example visualizes changes in a single account over time. Example Waterfall Chart - P & L Statement This example has expense accounts that are shown as a negative change to Total Revenue, and income accounts that are shown as a positive change, for a final Net Income value. Dashboard designers can set these waterfall chart properties: Chapter 13 Creating and Managing Dashboards 13-27
- 487. Table 13-9 Waterfall Chart Properties Setting Description Value Scale Especially useful for large numbers, you can scale how a value is displayed. For example, if the value is 1,689,000 and you select K - Thousand as the scaling option, the chart displays the value as 1,689K. Your scaling options: • None: No scaling is applied. • Auto: The value is displayed based on its range. For example, 1,500 displays as 1.5K, 1,689,000 displays as 1.69M, 42,314,531,211 displays as 42.31B, and 1,234,567,891,234 displays as 1.23T. • K - Thousand: The value is displayed as thousands units. For example, 1,689,000 displays as 1689K. • M - Million: The value is displayed as millions units. For example, 123,456,789 displays as 123M. • B - Billion: The value is displayed as billions units. For example, 12,345,678,912 displays as 12B. • T - Trillion: The value is displayed as trillions units. For example, 1,234,567,891,234,567 displays as 1,234T. Grid Lines Select Hide or Show to display the x-axis lines of the grid. Connecting Lines Select Hide or Show to display the lines connecting the end of each column to the beginning of the next column. This helps visualize the flow of the data in the chart. Plot Deltas Select Yes to automatically calculate and plot the common start and end points from one bar to the next based on the values provided. This is useful for showing the trend for balance type of accounts. Otherwise, select No to manually set increase and decrease points. When No is selected, you can manually set these increase/ decrease options on a bar-by-bar basis: • Bar Direction: Select a bar to manually set the bar direction to increase/decrease. • All bars: Display a list of all bars in the chart to manually set bar directions to increase/decrease. The manual options you can set for each bar are Auto, Reverse, and Total. Auto will consider the positive/negative values from the data source and plot accordingly. Reverse will change the sign, and Total will make the chart restart at the corresponding bar. Increase Decrease Total Select a color for each property. End Bar Select whether to Hide or Show the end bar on the chart. In the preceding example, the end bar is shown. If the end bar is shown, you can specify a label. Axes Select a Custom Range for the X-Axis and the Y-Axis, or select Off. Chapter 13 Creating and Managing Dashboards 13-28
- 488. Videos Your Goal Watch This Video Learn how to create waterfall charts to track the changes in a single account over time and to track how multiple accounts interact to produce a final total. Creating Waterfall Charts in Dashboards 2.0 Using Tables in Dashboards Tables in dashboards provide a list view of the data showing multiple values from a form or grid. You can embed mini-charts into each row of the table, called Spark Charts, which plot column data. Tables are also searchable. Example Dashboard Showing Plain Tables Example Dashboard Showing a Table With a Spark Chart Dashboard designers can set these table properties: Chapter 13 Creating and Managing Dashboards 13-29
- 489. Table 13-10 Table Properties Setting Description Value Scale Especially useful for large numbers, you can scale how a value is displayed. For example, if the value is 1,689,000 and you select K - Thousand as the scaling option, the table displays the value as 1,689K. Your scaling options: • None: No scaling is applied. • Auto: The value is displayed based on its range. For example, 1,500 displays as 1.5K, 1,689,000 displays as 1.69M, 42,314,531,211 displays as 42.31B, and 1,234,567,891,234 displays as 1.23T. • K - Thousand: The value is displayed as thousands units. For example, 1,689,000 displays as 1689K. • M - Million: The value is displayed as millions units. For example, 123,456,789 displays as 123M. • B - Billion: The value is displayed as billions units. For example, 12,345,678,912 displays as 12B. • T - Trillion: The value is displayed as trillions units. For example, 1,234,567,891,234,567 displays as 1,234T. Row Divider Choose Show or Hide. Font Specify size and color options for headers and data. Spark Chart • Chart Type: Select Bar, Line, Area, and Line with Area with associated options. Or you can select None. • Header: Column header for the Spark Chart column • Starting Index: Column index where to start charting data • Ending Index: Column index where to stop charting data Videos Your Goal Watch This Video See how to create a dashboard with multiple components in the Dashboard Designer for Dashboards 2.0. You create a dashboard with a table, a table with a spark chart, and a tile chart. Creating Table, Spark, and Tile Charts in Dashboards 2.0 About the Gauge Chart Type for Dashboard 2.0 Gauge chart types show you whether data values fall within an acceptable range or not. You set the minimum and maximum values, the range maximums, and the gauge uses red, yellow, and green traffic lighting to help you quickly assess a current value and identify problems in important data points or measures. For Dashboards 2.0, you can select circular, horizontal, and vertical gauge types. Dashboard 2.0 Example - Circular Gauge Type Chapter 13 Creating and Managing Dashboards 13-30
- 490. Dashboard 2.0 Example - Horizontal and Vertical Gauge Types Dashboard designers can set these gauge chart type properties: Chapter 13 Creating and Managing Dashboards 13-31
- 491. Table 13-11 Gauge Chart Type Properties Setting Description Value Scale Especially useful for large numbers, you can scale how a value is displayed. For example, if the value is 1,689,000 and you select K - Thousand as the scaling option, the chart displays the value as 1,689K. Your scaling options: • None: No scaling is applied. • Auto: The value is displayed based on its range. For example, 1,500 displays as 1.5K, 1,689,000 displays as 1.69M, 42,314,531,211 displays as 42.31B, and 1,234,567,891,234 displays as 1.23T. • K - Thousand: The value is displayed as thousands units. For example, 1,689,000 displays as 1689K. • M - Million: The value is displayed as millions units. For example, 123,456,789 displays as 123M. • B - Billion: The value is displayed as billions units. For example, 12,345,678,912 displays as 12B. • T - Trillion: The value is displayed as trillions units. For example, 1,234,567,891,234,567 displays as 1,234T. Gauge Type Select from the following options: • Circular • Horizontal • Vertical Minimum Value Maximum Value The lowest and highest values on the gauge. The dashboard designer sets the values as a default, and then users can temporarily change them at runtime. If the dashboard designer doesn't specify these values, the application automatically sets the minimum value as zero and the maximum value as greater than the value on the gauge. Desired Goal Specify whether High values or Low values are desirable. Low Threshold Medium Threshold High Threshold To visually indicate whether a measure lies in the acceptable range or not, these thresholds enable you to display the gauge in red, yellow and green based on the specified values. Specify a text Label and a number Value for each threshold. About the Radar Chart Type for Dashboard 2.0 A radar chart is a two-dimensional chart type designed to plot one or more series of values over multiple quantitative variables. Radar charts are best for determining Chapter 13 Creating and Managing Dashboards 13-32
- 492. which variable in the data is doing better than the rest. Hence, they are mostly used for performance analysis. For Dashboards 2.0, you can select bar, line, area, scatter, and bubble radar types. Dashboard 2.0 Example - Radar Bar Chart Type Dashboard 2.0 Example - Radar Line Chart Type Dashboard designers can set these radar chart type properties: Chapter 13 Creating and Managing Dashboards 13-33
- 493. Table 13-12 Radar Chart Type Properties Setting Description Value Scale Especially useful for large numbers, you can scale how a value is displayed. For example, if the value is 1,689,000 and you select K - Thousand as the scaling option, the chart displays the value as 1,689K. Your scaling options: • None: No scaling is applied. • Auto: The value is displayed based on its range. For example, 1,500 displays as 1.5K, 1,689,000 displays as 1.69M, 42,314,531,211 displays as 42.31B, and 1,234,567,891,234 displays as 1.23T. • K - Thousand: The value is displayed as thousands units. For example, 1,689,000 displays as 1689K. • M - Million: The value is displayed as millions units. For example, 123,456,789 displays as 123M. • B - Billion: The value is displayed as billions units. For example, 12,345,678,912 displays as 12B. • T - Trillion: The value is displayed as trillions units. For example, 1,234,567,891,234,567 displays as 1,234T. Type Select from the following options: • Bar • Line • Area • Scatter • Bubble Legend Position Choose Left, Right, Top, Bottom, or None. Grid Lines Select Hide or Show. Logarithmic Scale Especially useful for displaying numerical data that covers a wide range of values (typically, the largest numbers in the data are hundreds or even thousands of times larger than the smallest numbers), a logarithmic scale displays these values in a way that is more compact and readable. Select whether to use a logarithmic scale in your radar chart. Color Select Default or click data in the chart and choose a custom color for that data. About the Combination Chart Type for Dashboard 2.0 The combination chart is a visualization that lets you merge into one chart any combination of bar, line, and area charts. Chapter 13 Creating and Managing Dashboards 13-34
- 494. You can also add a secondary Y-axis on the opposite side from the primary Y-axis. Adding a secondary Y-axis lets you display the scale for one measure that doesn't scale appropriately with the other measures on the chart; for example, showing a percentage measure and a currency measure on the same chart. Dashboard 2.0 Example - Area Bar Line Combination Chart Dashboard designers can set these combination chart type properties: Table 13-13 Combination Chart Type Properties Setting Description Value Scale Especially useful for large numbers, you can scale how a value is displayed. For example, if the value is 1,689,000 and you select K - Thousand as the scaling option, the chart displays the value as 1,689K. Your scaling options: • None: No scaling is applied. • Auto: The value is displayed based on its range. For example, 1,500 displays as 1.5K, 1,689,000 displays as 1.69M, 42,314,531,211 displays as 42.31B, and 1,234,567,891,234 displays as 1.23T. • K - Thousand: The value is displayed as thousands units. For example, 1,689,000 displays as 1689K. • M - Million: The value is displayed as millions units. For example, 123,456,789 displays as 123M. • B - Billion: The value is displayed as billions units. For example, 12,345,678,912 displays as 12B. • T - Trillion: The value is displayed as trillions units. For example, 1,234,567,891,234,567 displays as 1,234T. Chapter 13 Creating and Managing Dashboards 13-35
- 495. Table 13-13 (Cont.) Combination Chart Type Properties Setting Description Line Weight Click the counter to set the line width. Note that the default width of a line is 5 pixels. You can select from 1 to 12 pixels. Legend Position Choose Left, Right, Top, Bottom, or None. Label Position Set the position of the data labels on the chart. Choose Outside Bar Edge, Center, Inside Bar Edge, or None. Grid Lines Select Hide or Show. Logarithmic Scale Especially useful for displaying numerical data that covers a wide range of values (typically, the largest numbers in the data are hundreds or even thousands of times larger than the smallest numbers), a logarithmic scale displays these values in a way that is more compact and readable. Select whether to use a logarithmic scale in your combination chart. Dual Y Select which data to plot on a secondary Y-axis which will appear on the opposite side of the chart from the primary Y-axis. When the data values in a chart vary widely from data series to data series, or when you have mixed types of data (for example, currency and percentages), you can plot one or more data series on a secondary vertical (Y) axis. While the secondary Y-axis can be used with any line and bar chart type, it is more commonly used with the combination chart type, which helps to distinguish the data series that are plotted on the secondary Y-axis. For example, use a bar for the primary Y- axis, and line for the secondary Y-axis. Series Select the bar/line/area combination for the chart. Color Select Default or click data in the chart and choose a custom color for that data. Axes Select a Custom Range for the X-Axis, Y-Axis, and Dual Y-Axis, or select Off. About Global and Local POVs in 2.0 Dashboards A local POV on a form reflects the dimension members the form designer selected for that form. Dashboards also support global POV bars, so that the local POVs that are common are combined in the global POV bar to avoid repeating them in each object. Dashboard 2.0 POVs Example This 2.0 dashboard shows a global POV bar (showing Entity, Product, and Year) and local POVs (the drop-down list for Q2): Chapter 13 Creating and Managing Dashboards 13-36
- 496. With a global POV bar, if you change a page in the global POV bar and POV Bar : Auto- Apply is enabled, the page changes for all objects in the dashboard that are based on forms. The global POV bar displays at the top of the dashboard above all the objects, while the local POV bar displays within the object. User variables are supported in both global and local POVs in dashboards and you can change dynamic user variables directly from the POV bar. In the dashboard toolbar Actions menu (in both the runtime and edit modes), you can set whether to hide dimension labels in the global POV (POV Bar : Hide Dimension Labels) and whether to enable or disable automatically applying changes (POV Bar : Auto-Apply). If you clear the POV Bar : Auto-Apply option, Apply and Reset buttons will display on your POVs to manually apply or clear your changes. About global POV bars: • The POV Bar is made up of local POV dimensions, Page dimensions and user variables. • Depending on the local POV and page of each form on the dashboard, the global POV bar is automatically calculated. • They are reflected in the other objects using forms in that dashboard. That is, they apply to forms in a dashboard, to charts that are linked to forms, and to tiles that use forms as a data source. So if the dashboard doesn’t include a form as a data source, 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 POV dimensions for two forms: The global POV bar is disabled: • Form A local POV: Year, Entity, Product Chapter 13 Creating and Managing Dashboards 13-37
- 497. • 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 a dashboard, the complete POV for a dashboard object may get split between the local and global POV bar. The global POV bar and the local POV together contain the complete 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, then the 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, then this is how the application determines which dimensions go in the global POV bar or stay in the local POV: • If the dimension is in the POV or page of all the forms, and the member selection is 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, then the dimension stays in the local POV. • If the dimension is in the POV, then the same members must be selected in all the forms for the dimension. • If the dimension is a page dimension, then the selected page members must be the same and display in the same order in all the forms. Dashboard 2.0 POV Bar Considerations Consider the following when using POV bars in Dashboards 2.0: • For POV bar Page drop-down lists, the number of members shown in the page drop-down is controlled in User Preferences under Page Options. (From the Home page, click Tools, then User Preferences, and then click Display to view the Page Options.) If the number of items in the page drop-down exceeds this limit, then users cannot view them. Note that this will be fixed in a future release with the ability to use the member selector to browse through the rest of the members, similar to Dashboards 1.0. • POV bar valid combinations are not yet supported. Note that this will be fixed in a future release and the behavior is expected to be similar to that in Dashboards 1.0. About Quick Analysis Quick Analysis lets you add components to dashboards without having a prebuilt form. You create an ad hoc query by typing member names in the Search bar or using the Member Selector, and then you control the layout of the query in the Layout tab of the Properties panel. Example 2.0 Dashboard Quick Analysis Chart in Design Mode Chapter 13 Creating and Managing Dashboards 13-38
- 498. To create a quick analysis in your dashboard: 1. Select a cube for the query. You can do this in one of two ways: • Click in the workspace Search box to display a list of cubes, then select a cube. • Drag and drop a cube from the library panel to the dashboard workspace. Note: With either method, the system starts with a default query; a single intersection in the cube driven from your Most Recently Used, or MRU. The default query varies based on what you've recently been looking at in the cube. 2. Refine the query by specifying members for the query: • In the Search box, type member names to display an auto-complete list from the cube. • Launch the member selector to select members, and then click OK. Note: When using the Search box to find members for quick analysis and more than 25,000 members are present in a cube, the Search box only searches the first 3000 members in the dimension for the cube. If the cube contains less than 25,000 members, then the Search box will search through all members. To search a cube with more than 25,000 members, launch the member selector to make your quick analysis selections. 3. Select a chart type for the query. Chapter 13 Creating and Managing Dashboards 13-39
- 499. Click to select a chart type; for example, Bar . 4. In the Properties panel, click the Layout tab . 5. Drag and drop the dimensions in the Layout tab of the Properties panel to other sections of the Layout tab to change the POV, Row, and Column layout of the dashboard object. Videos Your Goal Watch This Video Discover how to add quick analysis components to dashboards without having a prebuilt form. You learn how to create an ad hoc query in the Dashboard Designer and format the results by changing the dimension layout and applying visualizations. Creating Quick Analyses in Dashboards 2.0 Chapter 13 Creating and Managing Dashboards 13-40
- 500. 14 Designing Infolets Related Topics • About Infolets • Anatomy of an Infolet • Determining Infolet Content • Using the Infolets Designer • Creating Infolets • Working with Infolets • Customizing the Interface to Access Infolets About Infolets Infolets enable users to view and interact with high-level, essential information generated from different sources so that they can quickly assess where to direct their attention. Service Administrators create, redesign, delete, and assign permissions to infolets. What is an Infolet? An infolet is a self-contained, interactive box-shaped container used to display information using text and charts. Infolets are interactive and use progressive disclosure to display high- level, aggregated, essential information for quick consumption at a glance, and then can be acted upon as needed. Infolets can be flipped and resized to display up to three charts or sets of values. 14-1
- 501. 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 and prioritize their work • Progressively display essential details and actions Display these additional details in the various infolet views accessed by flipping or expanding 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 that manages the space occupied by the infolets and rearranges them depending on the size of the browser and the size of the infolets. Each infolet you create belongs to an infolet page. The Infolets card on the Home page provides a list of infolet pages. Note: Not all features pictured in the preceding image are supported in this update. Oracle plans to support these features in a later update. Chapter 14 About Infolets 14-2
- 502. See Working with Infolets. Videos Your Goal Watch This Video Learn how to design infolets. Learn how infolets give different users and groups quick, functionally-tailored access to the key data that they need to prioritize their immediate activities and guide their decision making. Overview: Creating Custom, Interactive Views of Key Data in Planning Using Infolets Anatomy of an Infolet Infolet Views An infolet supports up to three views: 1. Front view (required) 2. Back view (optional) 3. Expanded view (optional) Chapter 14 Anatomy of an Infolet 14-3
- 503. The front view is required, and: • Provides a quick look or glimpse at high-level information that has a direct effect on your work; for example, the front view can display status, counts, totals, or the most recent updates • Promotes a glancing action that helps you identify important information that you may 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) flip to 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 with the 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 the lower-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 or interdependent data set presented in the front and back views; for example, the expanded view can display more details about an object or a list of recent items than what's displayed on either the front or back view Chapter 14 Anatomy of an Infolet 14-4
- 504. • Provides enough information to help you decide if you're ready to take action and move 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 the lower- right corner Infolet views honor the access permissions assigned to the underlying forms and dimensions. Therefore, the same infolet may display varying views from user to user if they 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 of the front view will automatically reset the size of the back view. Because the size of the expanded view must always be greater than the size of the front/back views, if the size of the front/back view of an infolet is enlarged, the expanded view automatically resets to a larger size than the front/back view. Note: Front and back views cannot use the 3x2 size. This size is applicable for the expanded 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 3. Front and expanded views Chapter 14 Anatomy of an Infolet 14-5
- 505. 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 Content Consider 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 they display collections of information summaries. • Apply the 10/90/90 principle. Seek out the most essential, easily consumable information that addresses frequently asked questions garnered from the top 10 percent of use cases. These use 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 benefit from viewing 90 percent of the time. You can apply this 10/90/90 percent principle to existing dashboard content, to existing work area page content, or generally, to percolate 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 these business questions; for example, how many orders are in jeopardy, listed by status? • Look for one point or a tightly related, interdependent set of points, instead of multiple points of information. The process of determining content for an infolet is similar to the process that is used to yield dashboard content—but to a deeper level of analysis. Look for information within a data point or data set that is suitable to be displayed in no more than three views of information hierarchy and that answers a critical business question. • Start with the single most important point. An infolet displays aggregated information about a single data aspect or point of information in relation to an event that the user needs to know about or a task that the 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 and add that as a simple overview (for example, as a total using a stylized numeric value) 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 point or only one tightly related, interdependent data set to display on an infolet, use only the front view. Related Links Designing Forms for Infolets Chapter 14 Determining Infolet Content 14-6
- 506. Designing Charts for Infolets Designing Forms for Infolets Use only forms with small data sets in infolets. Permissions that are set for forms 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 form has more than 12 rows and columns, the infolet will only display the first 12 rows and columns. • Infolets currently don't support Page dimensions or POVs, therefore forms used in infolets should not contain Page dimensions. • If a form that is used in infolets contains a grid with members that expand, the infolet will display all the members in the form, including the expanded members. Designing Charts for Infolets Use 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 comparison purposes. Bar charts can be plotted vertically or horizontally. Up to eight bars are recommended for bar chart infolets. • Column: Displays stacked bars that represent different data sets on top of each other. 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 sets to one another. The blank center displays the sum of all data sets. Up to six segment 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 one another. Up to six slices are recommended for pie chart infolets. • Tile: Lets you select specific values from a data set to display. No more than three values are recommended for tile chart infolets. Note: Tile charts can only use the 1x1 size. You cannot resize an infolet using the tile chart until the chart type is changed. If you drag and drop a tile chart to an infolet that is greater than 1x1, you will be prompted to change either the size of the infolet or the chart type. Chapter 14 Determining Infolet Content 14-7
- 507. Using the Infolets Designer Service Administrators use the Infolets Designer to create infolets and infolet pages. The Infolets Designer enables easy toggling between runtime and designer views. To access the Infolets Designer, launch the Infolets icon on the Home page and click Create, or click the Actions icon next to an infolets page in the listing, and then click Edit. 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 from the database • Runtime: Hides all Infolets Designer elements and displays the infolet as it would appear to users during runtime Chapter 14 Using the Infolets Designer 14-8
- 508. : From runtime mode, displays the Infolets Designer Infolets Designer Palette On the left is the Designer Palette. The Designer Palette has two tabs: Forms and Chart Types. Highlight objects in the Designer Palette and then drag and drop them onto the drop zone. Designer Palette objects: • Forms: Select forms to include in the infolet by scrolling through the forms or by searching for them by name. For details about forms, see Designing Forms for Infolets. Note: The access permissions set for forms are honored in infolets. • Chart Types: Select the chart types to include in the infolet. Infolets display sample data in the charts until you associate the chart with a form as its data source. When you link a Chapter 14 Using the Infolets Designer 14-9
- 509. chart to a form, users can see the impact of changing 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 about charts, see Designing Charts for Infolets. Infolet Menu The infolet menu contains the infolet delete and clear actions. To view the infolet menu, hover over the upper right corner of the infolet, and then click the down arrow to display 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 and work with these infolet properties: Note: The header you specify is the same for all views of an infolet, but you can specify a different subtitle for each view; for example, the front, back, and expanded views of an infolet can each have different subtitles, but they must have 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 see the other views by selecting them from the drop-down. If you flip or expand an infolet to view the back or expanded views, the properties for those views display in the properties panel. In addition, the properties for the corresponding chart type are also displayed in the properties panel. Creating Infolets To create infolets: 1. From the Home page, click Infolets, and then click Create. 2. Click Untitled Infolets Page, and enter a title for the new infolets page you are creating. Chapter 14 Creating Infolets 14-10
- 510. 3. From the designer palette on the left, choose either the Library tab or the Visualizations tab, highlight an object, and then drag and drop it onto the infolets drop zone. Alternatively, you can click at the top of the page to add a new infolet to the workspace. 4. If the Properties panel isn't already displaying, click at the top of the page to reveal it. Customize the highlighted infolet using selections made in the Properties panel. 5. Click Save. You can easily duplicate and modify an infolet using the Copy As action on the Infolet list page. From the list page, click the Actions icon next to the infolet you want to copy, and then click Copy As. Working with Infolets Once you've created an infolets page, it is displayed in the infolets listing on the Infolets card. The listing page for infolets supports folders. Folders enable you to assign permissions to all infolets within a folder rather than assigning permissions to each individual infolet. The infolets listing page uses the same folder hierarchy as dashboards and data entry forms and all artifacts and folders reside under a root folder called Library. Note: Only administrators can add files (for example, dashboards, infolets, forms, reports, and so on) to the Library root folder. 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 displays only the artifacts that meet the search criteria, not the folders that contain them. The tree (or hierarchical) view displays artifacts in the context of the folders that contain them. To search on another keyword, clear the search criteria by clicking X in the Search box. • To refresh the infolets listing, click Refresh. • To create infolets, click Create. See Creating Infolets. Chapter 14 Working with Infolets 14-11
- 511. • To perform the following actions on infolet pages, click the Actions icon next to 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 makes it accessible directly from the Home page by clicking the second infolet dot that is displayed beneath the global header on the Home page. Only one infolet page can be marked as default, and a "(Default)" prefix displays before the name of that infolet in the listing. Unmark removes the default designation from the infolet page. Note: You can no longer mark a dashboard page as default. Only an infolet page can be marked as default. – Assign Permission: Enables you to assign Read, Write, and None access permissions to infolet pages and folders for individual users or groups Customizing the Interface to Access Infolets You can customize the business process interface to add links to infolet pages from the Home page using the Navigation Flow Designer. When you customize your interface to access infolet pages, dots will appear on the Home page beneath the global header and arrows will display to help you navigate easily between the Home Page and infolet dashboard pages. Each dot that appears on the Home page represents an infolet page and hovering over each dot displays the name of the infolet page. Clicking an infolet dot launches the infolet page associated with that dot. You can define up to seven infolet dots on the Home page. If you've created connections to other EPM Cloud environments, you can also add links to infolet pages in other EPM Cloud environments. Chapter 14 Customizing the Interface to Access Infolets 14-12
- 512. Users will only see dots displayed on the Home page for infolet pages to which they have 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 can only be one home dot. If you are not viewing the Home page, clicking the home dot will bring you back to the Home page. • User dot: Links to an infolet page marked by an end user as the default infolet page. There can only be one user dot and it always appears after the Home dot on the user's Home page. User dots cannot be added using the Navigation Flow Designer. For more information about marking an infolet as the default, see Working with Infolets. • Customizable dot: Links to infolet pages created by Service Administrators. Customizable dots can be integrated into navigation flows and their visibility and the order in which they appear is determined by the navigation flow designer. There can be up to seven customizable dots and they always appear after the home and user dots. To add infolet dots to your business process 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 on the Navigation Flow Designer. 3. Click . 4. In Manage Infolet, name the infolet dot, set visibility, and then click to select an infolet in the Artifact Library. Note: You can select an infolet from another EPM Cloud environment if you've created connections to other environments. First select the environment under My Connections, and then navigate to the infolet in that environment. 5. Click Save and Close. Chapter 14 Customizing the Interface to Access Infolets 14-13
- 513. 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 Artifact Library. To view design time changes to the navigation flow, activate the navigation flow, and then from the Home page, click the down arrow next to the user name (upper right corner of the screen) and click Reload Navigation Flow. To learn more about designing navigation flows, see Designing Custom Navigation Flows. To learn more about connecting EPM Cloud environments and for information about the Copy URL feature, see Connecting Environments in EPM Cloud. Chapter 14 Customizing the Interface to Access Infolets 14-14
- 514. 15 Configuring IPM Related Topics • About IPM Oracle EPM Cloud provides Intelligent Performance Management—IPM—integrated directly in your Planning applications to inform your planning decisions with predictive capabilities and accelerate insight discovery with financial pattern recognition. • About IPM Insights IPM Insights empowers finance and operational users with data science optimized for multidimensional planning and forecasting use cases. • Configuring IPM Insights Configure IPM Insights to define the insights that planners see on the Insights dashboard. • Running and Scheduling Insights After configuring insights, you can run them any time. You can also set up a job to run insights at a regular interval, for example, when you have a new set of actuals. • Editing, Duplicating, and Deleting Insights You can edit, delete, or duplicate existing insight definitions. • Bring Your Own ML: About Machine Learning Model Import With Bring Your Own ML, EPM administrators can import a fully trained Machine Learning (ML) model and deploy it to a Planning application. Planners can then leverage robust, ML-based forecasting that uses advanced predictive modeling techniques to generate more accurate forecasts. About IPM Oracle EPM Cloud provides Intelligent Performance Management—IPM—integrated directly in your Planning applications to inform your planning decisions with predictive capabilities and accelerate insight discovery with financial pattern recognition. Learn more about the Oracle EPM Cloud IPM offerings: • Auto Predict enables you to jumpstart your planning process and improves the accuracy of your forecasts with powerful and automated predictive capabilities. See About Auto Predict. • IPM Insights reduces time spent in data analysis with financial pattern recognition that offers insights to planners, which they can evaluate and take action on. See About IPM Insights. • Machine Learning Model Import lets business users harness the power of data science by performing what-if analysis on a trained ML model that has been imported into a Planning application. See Bring Your Own ML: About Machine Learning Model Import. About IPM Insights IPM Insights empowers finance and operational users with data science optimized for multidimensional planning and forecasting use cases. 15-1
- 515. IPM Insights analyzes past data and predicted data, helping you find patterns and insights into data that you might not have found on your own. Insights can be trends, anomalies, forecast bias, or variations. With IPM Insights, the insight discovery phase of the planning process is automated with data science and financial pattern recognition, enhancing your forecast effectiveness. Using IPM Insights, you can analyze and explore data across any account. IPM Insights automates processing large amounts of multidimensional data, so that as new actuals come into the system, you quickly detect patterns in your data or hidden correlations, streamlining reporting, improving your forecasting, and strengthening your decision making. You spend less time in analysis, saving time in the overall planning process. IPM Insights offers these benefits: • Reduces time spent in data analysis. • Minimizes hidden biases. • Improves forecast accuracy and reliability, enhancing forecast effectiveness with informed decision-making. • Encourages collaboration with your colleagues. • Helps you detect trends early to enhance strategic decision-making. IPM Insights provides three types of insights, using both historical and predicted data: • Forecast variance and bias insights reveal hidden bias in forecasts submitted by planners by analyzing historical data. This type of insight measures the variance or bias between two historical scenarios such as Forecasts and Actuals, and calculates the percentage of risk associated with the current forecast. Forecast variance indicates the level accuracy of the forecasts submitted by planners. Forecast bias indicates the tendency of the direction of forecast error. For example, a tendency to forecast in excess of the actuals is called the over- forecasting bias; a tendency to forecast below the actuals is called the under- forecasting bias. IPM Insights triggers an insight when either the variance or risk crosses the specified threshold. • Prediction insights help you uncover significant deviations in forecasts compared to predicted values. This type of insight looks for variances between two future scenarios such as forecasts and computer-generated predictions, and can calculate a measure of risk, for example the risk of meeting a target forecast. By comparing a planner’s forecast with a machine-generated prediction, prediction insights measure the variance as well as the presence of any hidden bias (a planner’s tendency towards over-forecasting or under-forecasting). IPM Insights triggers an insight when either the variance or bias crosses the specified threshold. • Anomaly insights detect unusual patterns in data that deviate from expected results. This type of insight detects outlier values that vary widely from other values, for example, a sudden volatility in actuals compared to the base level, or missing actuals data. Anomalies can result from key business actions or they could contain valuable information about a hidden trend. IPM Insights triggers an insight when an outlier measure crosses the specified threshold. To get started with IPM Insights, administrators configure insights and then run them, and can schedule them to run on a regular basis. Chapter 15 About IPM Insights 15-2
- 516. Planners can then review and analyze insights in a dashboard, and take appropriate action to improve the forecast. Figure 15-1 Forecast and Bias Insight Chapter 15 About IPM Insights 15-3
- 517. Figure 15-2 Prediction Insight Figure 15-3 Anomaly Insight Chapter 15 About IPM Insights 15-4
- 518. Videos Your Goal Watch This This overview introduces you to Insights. Insights empowers finance and operational users with data science optimized for multidimensional planning and forecasting use cases. Insights analyzes past data and predicted data, helping you find patterns and insights into data that you might not have found on your own. You can evaluate those insights and take action on them. Overview: Insights in Cloud EPM Considerations for IPM Insights The following are some of the considerations and best practices for leveraging the benefits of IPM Insights and Auto Predict. Considerations: • IPM Insights requires an EPM Enterprise Cloud service subscription. In addition, you can use IPM Insights with Oracle Sales Planning Cloud and Oracle Strategic Workforce Planning Cloud. • IPM Insights works with Custom and Modules application types. • IPM Insights and Auto Predict are not yet available in FreeForm applications; this is on the roadmap. • IPM Insights works only with applications with Hybrid Essbase enabled. • IPM Insights is available only with Redwood Experience enabled. (Auto Predict does not require Redwood Experience to be enabled, except for configuring advanced Auto Predict options. Configuring advanced auto predict options is available only with Redwood Experience enabled.) .) For more information about Auto Predict considerations, see Auto Predict Considerations. • IPM Insights honors both member level security and cell level security, so planners see insights only for slices of data to which they have access. However, note that insights are not generated for a user when cell level security is defined on Year/Period dimensions. IPM Insights Support Matrix Review the table for a summary of the supported SKUs, business processes, and application types for IPM Insights. Chapter 15 About IPM Insights 15-5
- 519. Table 15-1 IPM Insights Support SKU Business Process Application Type Supported? Comments EPM Enterprise Planning Modules Supported • Hybrid Essbase must be enabled • Redwood Experience must be enabled Planning Custom Supported • Hybrid Essbase must be enabled • Redwood Experience must be enabled Planning Freeform Not supported Other business processes Not supported Legacy SKU Planning Enterprise Planning and Budgeting Cloud Not supported Planning Planning and Budgeting Cloud Not supported Other business processes Not supported EPM Standard Planning Standard Module Not supported Other business processes Not supported Sales Planning Planning Sales Planning Supported • Hybrid Essbase must be enabled • Redwood Experience must be enabled Strategic Workforce Planning Planning SWP Supported • Hybrid Essbase must be enabled • Redwood Experience must be enabled Netsuite Planning Netsuite PB Not supported Best practices: Chapter 15 About IPM Insights 15-6
- 520. • Historical Data: Prediction results are more accurate the more historical data you have. There should be at least twice the amount of historical data as the number of prediction periods. For example to predict 12 months in the future, you should have at least 24 months of historical data. At the time of prediction, if there is not enough historical data available, a warning is displayed. • Time Granularity of Predictions: Because the lowest Period dimension member level in an Insights job determines the time granularity of the prediction, create the Insights job using the lowest level of Period members possible so that the greatest amount of historical data can be used. For more information about the statistical methods used in IPM Insights, see IPM Insights Metrics in Working with Planning. Configuring IPM Insights Configure IPM Insights to define the insights that planners see on the Insights dashboard. You configure IPM Insights by selecting the type of analysis to perform, specifying the slice definitions for analysis, configuring the analysis, and then defining the settings for the insights displayed on the Insights dashboard. You can define insights for as many data intersections as you need. Planners see insights only for slices of data to which they have access. You can also define a prediction using Auto Predict to predict future performance based on historical data and schedule a job to run that prediction definition, automating the prediction process. You can use these prediction results as input for generating insights. To configure IPM Insights: 1. From the Home page, click IPM and then click Configure. 2. Click Create. 3. In IPM Configurator, on the Types page, enter a name and description. 4. Select Auto Predict to predict future performance based on historical data using time series forecasting techniques. Prediction results can be used as input for generating prediction insights. For more information about Auto Predict, see Setting Up Predictions to Run Automatically with Auto Predict. If you select only Auto Predict and don't select any insights, you enter data on only on the Types page and on the Define Slice page of IPM Configurator. 5. Select the types of insights to generate, and then click Next. You can select as many as you need. • Forecast Bias Insights. Reveals hidden bias in forecasts submitted by planners by analyzing historical data. Measures the variance or bias between two historical scenarios such as Forecasts and Actuals. • Prediction Insights. Looks for variance between future scenarios such as forecasts made by planners and computer-generated predictions. In Do you have prediction data available?, if you have prediction data available and know where prediction data is, select Yes. If not, select No and Auto Predict is automatically selected. Auto Predict uses the historical data for the intersection you defined to generate prediction data that is used for the insight. You can also use a prediction based on Machine Learning instead of auto prediction. • Anomaly Insights. Detects outlier values that vary widely from other values. You can also choose to just run Auto Predict by selecting Auto Predict. Chapter 15 Configuring IPM Insights 15-7
- 521. 6. On the Define Slice page, define the slice of data to analyze for historical and future data, and then click Next. For considerations on using dynamic calc parent members in the slice definition, see Considerations for Defining the Slice for Insights. • In the Historical Data section, select the cube and then define the slice of data for the historical data—both actuals and the forecasts provided by the planners. The slice definitions show all the dimensions for the cube, except for the Year and Period dimensions. All members start out with their root member selected. Specify the number of years of historical data to include in the analysis. Specify the current period. (This selection is not needed if the insight type selection includes Prediction Insights or Auto Predict.) • In the Future Data section, select the cube and then define the slice of data for the future data—both the forecast provided by planners, and the base prediction (most likely scenario). If the data is available, click to add a definition for the slice of data for the best case and worst case scenarios. Define the periods of future data to include in the analysis. If you selected Auto Predict, prediction results are stored in this location. 7. On the Configure page, configure the insights by defining the error tolerance and thresholds for insights, and then click Next. IPM Configurator selects default metrics for analysis. • Auto Predict: If you select Show Advanced Options, select additional options to define an auto predict job. For more information, see Configuring Advanced Auto Predict Options. • Forecast Variance & Bias Insights: Select an error tolerance percentage, which defines the percentage variance between historical forecasts submitted by planners and actuals that lies within acceptable range. If the percentage variation crosses the error tolerance limit, it is considered for bias calculation. For example, if you enter .05, any difference of 5% or above between historical forecasts and historical actuals is considered a significant variance (and considered either under-forecasting or over-forecasting) and triggers an insight. You can select or modify the metric and threshold for deviation on the Advanced Options page. See Configuring Additional Insight Settings. An insight is generated when either deviation or bias crosses the specified threshold. • Prediction Insights: Select a threshold percentage, which defines the acceptable percentage variance between future forecasts submitted by planners and computer-generated predictions. An insight is generated when either deviation or risk crosses the specified threshold. For example, if you enter 25%, any difference of 25% or above between future forecasts and future predictions would be considered a significant variance (and considered either under-forecasting or over-forecasting). and would trigger an insight. • Anomaly Insights: Select a threshold, which defines the acceptable threshold for Z-score value (the standard deviation from the mean of the values). Chapter 15 Configuring IPM Insights 15-8
- 522. Anything that is too far from zero (the threshold is usually a Z-score of 3 or -3) should be considered an outlier. An insight is generated when the specified outlier detection metric crosses the specified threshold. For example, if you enter 3, anything that is three standard deviations or higher from the mean would be considered an outlier, and would trigger an insight. If you want to configure additional options, such as selecting the metrics to use, click Show Advanced Options. See Configuring Additional Insight Settings. 8. On the Settings page, configure the settings that define how to display the insights to planners, and then click Save. • Display Dimensions: Select the dimensions that planners will use to navigate and analyze the insights. The dimensions you select will display on the Insights dashboard. • Impact Magnitide Thresholds: When insights are displayed on the Insights dashboard, this setting categorizes insights into High, Medium, and Low groups based on the percentage impact calculated for each insight. This helps users focus attention on the insights that have more extreme variations. For example, if you specify 30% as the Low threshold and 60% as the High threshold, any insight with a percentage impact less than 30% is in the Low category; any insight with a percentage impact greater than 60% is in the High category. 9. Now you're ready to run the insights you configured. See Running and Scheduling Insights. Insight definitions are saved as global artifacts (in the Auto Predict folder under Global Artifacts) and are backed up with the maintenance snapshot. Videos Your Goal Watch This Video Learn how to configure insights to automate data analysis. Administrators configure insights to define the insights that planners see on the Insights page. You select the type of analysis to perform, specify the slice definitions for analysis, configure the analysis, and then define the settings for the insights displayed on the Insights page. You can run the insight or schedule it to run on a regular basis. Oracle Fusion Cloud EPM - Configuring Insights Tutorials Tutorials provide instructions with sequenced videos and documentation to help you learn a topic. Chapter 15 Configuring IPM Insights 15-9
- 523. Your Goal Learn How Learn how to configure IPM Insights by selecting the type of analysis to perform, specifying the slice definitions for analysis, configuring the analysis, and then defining the settings for the insights displayed on the Insights dashboard. You can define insights for as many data intersections as you need. Planners see insights only for slices of data to which they have access. Configuring Insights Considerations for Defining the Slice for Insights In IPM Insights, you can generate insights for dynamic calc parent members. • For reporting cubes (Aggregate Storage, or ASO cubes), there is no restriction on including dynamic calc parent members in insight definitions. • For data entry cubes (Block Storage, or BSO cubes), you can’t include dynamic calc parent members or any dynamic calc member even at the leaf level, however you can use this solution: – Create an alternate hierarchy with shared members for parents that you want to consider for insight generation. The parent members should be defined as level zero members in the alternate hierarchy. When you configure the insight slice definition, make sure to select the members from the alternate hierarchy. – As a best practice, move the data to the reporting cube (Aggregate Storage, or ASO cube) using data maps, and then generate insights from that cube. Including dynamic calc parent members in insights is especially helpful when you have a large number of members: you don't have to define multiple slice definitions for level zero members; you can define the slice definition to include a parent member. Considerations: • To avoid delays in insight generation for reporting cubes (ASO), consider not including dynamic parent members that have formulas in insight definitions. • Because the number of alternate hierarchies you can create is limited, for data entry cubes (BSO), as a best practice, move the data to the reporting cube (ASO cube) using data maps, and then generate insights from that cube. • For ASO cubes, prediction insights require that the slice definition includes only level zero members. Alternatively, to generate prediction insights for dynamic calc parent members, don’t enable Auto Predict. Or, run the prediction in BSO, and then move the results to ASO. Configuring Additional Insight Settings On the IPM Configurator Configure page, click Show Advanced Options to define the metrics and trigger criteria for insights. For information about Auto Predict Advanced Options, see Configuring Advanced Auto Predict Options. • For Forecast Variance & Bias Insights: – Deviation Metric Chapter 15 Configuring IPM Insights 15-10
- 524. * Metric: Select the metric to use for analysis for the variations between the historical actuals and the historical forecasts submitted by planners. * Threshold: Select the deviation percentage at which to trigger an insight. For example, if you specify 15 as the threshold, any time the deviation between historical actuals and the historical forecasts submitted by planners is 15% or greater, an insight is generated. – Bias Metric * Error Tolerance Limit: Specify a percentage for the error tolerance limit. For example, if you enter 5%, any difference of 5% or greater between historical forecasts and historical actuals is considered a significant variance. * Bias Metric: Specify the metric to use to measure forecast bias. * Bias Threshold: Select the deviation percentage at which to trigger an insight. • For Prediction Insights: – Deviation Metric * Metric: Select the metric to use for analysis for the variations between the future forecasts submitted by planners and computer-generated predictions. * Threshold: Select the deviation percentage between the future forecasts submitted by planners and computer-generated predictions at which to trigger an insight. – Risk % and Threshold: Select the risk level you are willing to tolerate of not meeting your forecast before triggering an insight. This setting evaluates the probability of meeting or missing the target for your current forecast numbers. • For Anomaly Insights: – Method: Select the anomaly detection metric to use for analysis. – Threshold: Select the threshold at which to trigger an insight. For details on the metrics used in IPM Insights, see IPM Insights Metrics in Working with Planning. Running and Scheduling Insights After configuring insights, you can run them any time. You can also set up a job to run insights at a regular interval, for example, when you have a new set of actuals. When you run an insight, IPM Insights analyzes the data at each available intersection and looks for patterns and anomalies. To run insights: 1. From the Home page click IPM and then click Configure. 2. From the Actions menu next to the insight you want to run, click Run. 3. To review the insight jobs, from the Home page, click Application, then click Jobs, and then select the insight. You can see the job status and the associated subjobs for each type of insight or auto prediction. For information about scheduling IPM Insights jobs, see Scheduling Jobs. IPM Insights has its own job type, called Insights. Chapter 15 Running and Scheduling Insights 15-11
- 525. Insights are available on the Insights dashboard for six months, after which they are purged the next time you run an IPM Insights job. Tutorials Tutorials provide instructions with sequenced videos and documentation to help you learn a topic. Your Goal Learn How Learn how to run and schedule Insights in EPM Cloud. Running and Scheduling Insights Editing, Duplicating, and Deleting Insights You can edit, delete, or duplicate existing insight definitions. To edit, delete, or duplicate an insight definition: 1. From the Home page, click IPM, then click Configure. 2. From the Actions menu next to an insight, click Edit, Duplicate, or Delete. Bring Your Own ML: About Machine Learning Model Import With Bring Your Own ML, EPM administrators can import a fully trained Machine Learning (ML) model and deploy it to a Planning application. Planners can then leverage robust, ML-based forecasting that uses advanced predictive modeling techniques to generate more accurate forecasts. Data scientists gather and prepare historical data related to a business problem, train the algorithm, and generate a PMML file (Predictive Model Markup Language, a standard language used to represent predictive models) using a third party tool. These predictive analytic models and machine learning models use statistical techniques or ML algorithms to learn patterns hidden in large volumes of historical data. Predictive analytic models use the knowledge acquired during training to predict the existence of known patterns in new data. EPM administrators can then import and configure the fully trained ML model, which generates two Groovy rules. Adminstrators attach the rule to a form or dashboard, or schedule a job to generate prediction results on a regular basis. This puts the benefits of machine learning and the power of data science into the hands of business users, enhancing the planning and budgeting process and leading to better business decisions. For example, you can predict product volume for an entity, using key drivers such as average sales price, planned spend on promotions and advertising, historical volumes, and estimated industry volumes. You can import ML Models and use them to predict numeric values in other finance use cases, for example: • Trade promotion impacts on sales uplifts • Marketing mix modeling to drive better ROMI • Internal and external driver impacts on revenue forecasts Chapter 15 Editing, Duplicating, and Deleting Insights 15-12
- 526. • Predictive cash forecasting for better cash position Overview of Steps Prerequisite: Data scientists build and train the ML model in a data science tool (any third party tool or Oracle Data Science Cloud) and save it as a PMML file. Next, EPM administrators put the model to work to get business value from the trained model: 1. Administrators import the ML model in PMML format to a Planning application and define how the input variables and target variable maps to dimension members or cell values in the Planning application. This step generates automatic Groovy rules that connect the ML model to the Planning application. Two Groovy rules are generated for each ML model definition: one rule to associate with a form or dashboard, which allows users to make predictions on demand, and another to generate large scale predictions in a scheduled job for bulk processing. See Importing an ML Model. 2. Administrators deploy the ML model in a Planning application by associating the Groovy rule to relevant action menus, forms, or dashboards. See Deploying an ML Model to Planners. Administrators can also create a job to run the Groovy rule in a batch process. 3. Planners leverage ML-powered business rules in forms to generate predicted values, which are saved on the form. Planners can perform what-if analysis using the generated predictions, or modify predicted values on the form. Planners add value with their expertise and judgement, and then finalize the forecast. 4. This is an iterative process. As planners make predictions based on the ML model, administrators can measure the performance of the model, and can work with data scientists to update or replace the ML model when needed. Then, administrators re- import and deploy the retrained ML model. When you re-import the retrained ML model, the Groovy rules are regenerated. Videos Your Goal Watch This This overview introduces you to Bring Your Own ML (Machine Learning), where EPM Administrators can import a fully trained ML model and deploy it to a Planning application. Planners can then leverage robust, ML-based forecasting that uses advanced predictive modeling techniques to generate more accurate forecasts. Overview: Bring Your Own Machine Learning (ML) Learn how to configure ML model import for Bring Your Own Machine Learning. You import a fully trained ML model into Planning. You follow the steps in a wizard to map, analyze, and test the model. After saving the model, two Groovy rules are created. To complete the integration process, see the related video for deploying an ML model to Planning. Configuring Machine Learning (ML) Model Import Chapter 15 Bring Your Own ML: About Machine Learning Model Import 15-13
- 527. Your Goal Watch This Learn how to deploy an ML Model to Planning. After configuring the ML Model Import, you integrate the PMML file into your planning application by creating an Action Menu with the Groovy rule generated from the configured ML model. Then you associate the Action Menu with a Planning form. When Planners run the rule from the form, the rule returns the set of predicted values. Deploying a Machine Learning (ML) Model to Planning Considerations for Bring Your Own ML The following are some of the considerations for Bring Your Own ML. Considerations: • Bring Your Own ML requires an EPM Enterprise Cloud service subscription; it is not available in EPM Standard Cloud. In addition, you can use Bring Your Own ML with Oracle Sales Planning Cloud and Oracle Strategic Workforce Planning Cloud. It is also available with Enterprise Planning and Budgeting Cloud. • Bring Your Own ML requires Groovy rules. • Bring Your Own ML works with Custom, Free Form, and Modules application types. • Bring Your Own ML is available only with Redwood Experience enabled. Importing an ML Model Import a fully trained ML model into a Planning application to prepare it for use by business users. Prerequisite: Before you can import the ML model, the data science team must build, train, and save the ML model as a PMML file. To import an ML model to a Planning application: 1. From the Home page, click IPM and then click ML Models. 2. Click Import, and then drag and drop the PMML file, or browse to it and select it. On the Import Model page, you see information about the PMML file, such as the target column (the variable to be predicted using the ML model) and the training date. 3. Enter a model name and description, and then click Next. 4. On the Generate Rule page, enter information that will generate a Groovy rule to associate with forms or dashboards: In Model Mapping, select the cube where the ML model will be used and define the scope of data in which to use the ML model by selecting a member or set of members from each dimension. 5. Map Input and Output to the appropriate Planning dimensions and members in the cube and then click Next. The Input and Output sections contain the list of input features (features/columns that are used to make predictions) and target feature (column that is expected to Chapter 15 Bring Your Own ML: About Machine Learning Model Import 15-14
- 528. be predicted). Planning analyzes the PMML file to generate the list of inputs and outputs. Input features are independent variables, similar to drivers, that act as input to your system. When you make predictions, the model uses input features to predict your output. In this step, you map the input from the ML model to the output in the Planning cube. Input describes how to extract the data from the ML model. Output defines the target measure you want to predict and where to paste the predicted values in the Planning application. For example, product, price, and industry volume, the input features, might be used to predict volume, the output. • In the Input area, for each input feature, select an Input Type and if you select Cell Value or Member, select the members or dimensions in the Planning application to map to. Input types: – Prompt: If you don't have a member or dimension in Planning that maps to this input value from the ML model, when the predicion is made, prompt the user to enter an estimate for the value. – Cell Value: Map an input feature to one or more dimension members in the Planning cube. For example, the input feature called Price maps to an account member called Price in the Planning application. – Member: Map an input feature to a dimension in the Planning cube. For example, the Input feature called Product maps to the Product dimension in the Planning application. • In the Output area, select an Input Type and if you select Cell Value or Member, select the members or dimensions in the Planning application to map to to store prediction results. 6. In Analyze Model, review the ML model and then click Next. This step represents MLX (Machine Learning Explainability), and extracts additional information about the ML model. For example, review Regression Coefficients to see how the relative impact of key input features is used to predict the output. The height of the bar represents the incremental effect of one unit increase in an input feature on the target variable. 7. In Test Model, test the ML model by generating a prediction for a set of sample values. For each Input, enter a sample input value and then click Predict. 8. Review the predicted Output value, and then click Save and Close. 9. Click Yes to confirm the creation of Groovy Rules. Two Groovy rules are generated for each ML model definition: • ML_MLModelName_Form: Use this rule to associate with a form or dashboard, which allows users to make predictions on demand. • ML_MLModelName : Use this rule to generate large scale predictions in a scheduled job for bulk processing. You can review the generated rules in Calculation Manager. The Groovy rules define the name and location of the PMML file, along with input and output based on the mapping you defined. For more information on using these generated Groovy rules, see Deploying an ML Model to Planners. Tutorials Tutorials provide instructions with sequenced videos and documentation to help you learn a topic. Chapter 15 Bring Your Own ML: About Machine Learning Model Import 15-15
- 529. Your Goal Learn How Learn how to import a fully trained ML model and deploy it to a Planning application. Planners can then leverage robust, ML-based forecasting that uses advanced predictive modeling techniques to generate more accurate forecasts. Importing ML Models Deploying an ML Model to Planners Deploy an imported ML model to make it available to planners on forms and dashboards. Planners can use machine learning to generate a prediction. After importing a PMML model, EPM administrators integrate the PMML file into the Planning application by associating the generated Groovy rule with Planning forms. You can first review the Groovy rules in Calculation Manager to validate the mappings and make changes if needed. When the Groovy rule is finalized, you can associate it with relevant forms or dashboards. Make the Groovy rule available to planners by creating an Action Menu that you associate with a form. To associate an ML Groovy rule with a form: 1. Create an Action Menu item: a. From the Navigator, under Create and Manage, click Action Menus. b. Click , enter the menu's name, and then click OK. c. Select the new menu item, click , and then click Add Child. d. Enter a Menu Item name, and give it a label, for example, Predict Volume, of type Business Rule, and select the appropriate cube and Groovy rule with the Form suffix, for example: ML_MLModelName_Form. Then click Save. For more information, see Creating and Updating Action Menus. 2. Associate the action menu with a form: a. From the Navigator, under Create and Manage, click Forms. b. Navigate to the form, click , and under Other Options, click the Action Menu item you created. Associate the menu with the form by moving it from Available Menus to Selected Menus. Then click Save. For more information, see Administering Forms. When a planner selects the Action Menu item from the form, it triggers the Groovy rule. The rule picks the data for all input drivers, sends it to the PMML file for processing, returns the set of prediction values, and pastes them to the output, as defined in the Import Model wizard. The rule runs in the context of the form, predicting values only for cells on the form. Security is honored so that planners see predictions only for intersections to which they have access. Planners can run through various what-if scenarios to adjust their forecasts and plans, or adjust the predicted values. Chapter 15 Bring Your Own ML: About Machine Learning Model Import 15-16
- 530. Note that planners must have access to the model, form, rule, and members in order to run the rule. Running an ML Groovy Rule as a Batch Job You can run the ML Groovy rule as a job. The batch rule runs for all cells for the full scope of the model, not just for cells on a particular form. You can set it up to run as a recurring job, for example, to load predictions so they are available to planners on a regular basis. To run or schedule a batch job, in Jobs, select a Job Type of Rules, and then select the Groovy batch version of the business rule for the PMML model—ML_MLModelName . For information about scheduling jobs, see Scheduling Jobs. Tutorials Tutorials provide instructions with sequenced videos and documentation to help you learn a topic. Your Goal Learn How Learn how to take the Groovy rule created from an imported ML Model, and add it to a form. Then you make predictions with the ML model in Planning. Making Predictions with ML Models Chapter 15 Bring Your Own ML: About Machine Learning Model Import 15-17
- 531. 16 Setting Up Predictions to Run Automatically with Auto Predict Related Topics • About Auto Predict With Auto Predict, administrators can define a prediction to predict future performance based on historical data and schedule a job to run that prediction definition, automating the prediction process. • Creating Auto Predictions for Forecasts Create an Auto Predict prediction definition to automate predictions. • Running Auto Predict Predictions You can run an Auto Predict prediction definition from the Auto Predict page or the IPM page, or you can schedule a job to run the prediction automatically. • Editing, Deleting, or Duplicating Auto Predict Prediction Definitions You can edit, delete, or duplicate existing Auto Prediction prediction definitions. • Reviewing Detailed Reports for Auto Predict Predictions You can review Auto Predict prediction result details in a downloadable report in an Excel worksheet format, including details such as prediction status, method used, and prediction accuracy. About Auto Predict With Auto Predict, administrators can define a prediction to predict future performance based on historical data and schedule a job to run that prediction definition, automating the prediction process. Auto Predict uses the same forecasting and statistical methods as Predictive Planning, but unlike Predictive Planning, you aren’t limited to running a prediction on a form. You can predict values for thousands of cells at once, when needed, by scheduling a job, and automatically write prediction results to a scenario/version—in the same cube or in a different cube from the historical data. You can also include Best and Worst Case prediction results. When you run the prediction, historical data for each member in the Auto Predict definition is retrieved and then analyzed using time series forecasting techniques to predict the future performance for these members. Auto Predict is useful: • When you have large amounts of data to predict. • To jumpstart the forecasting process by pre-filling a prediction scenario with predictions based on historical data. Then, planners can compare predictions to forecasts. • For variance analysis. Seed a prediction scenario with prediction results, and compare predictions to forecast. To incorporate variance thresholds, you can define a groovy rule that requires planners to add explanatory commentary at a defined threshold, for example if the forecast is 5% greater than the prediction. 16-1
- 532. • To pre-populate your Forecast or Plan scenarios before starting a forecast or planning cycle. Planners can use these prediction results as a starting point for their forecasts, and make adjustments as needed. • To keep predictions up-to-date as actuals come in by scheduling Auto Predict jobs. When new actuals come in, the job can run automatically to populate the cube; planners can see updated predictions and compare to forecast and plan. Use Auto Predict results in forms, dashboards, and in ad-hoc analysis. You can also use Auto Predict prediction results within Smart View. You define a prediction to read historical data from a cube (typically an ASO cube) and write prediction results to the same cube or to a different cube, for example to a BSO cube where planning and forecasting is done. To work with Auto Predict: 1. Define the Auto Predict prediction. See Creating Auto Predictions for Forecasts. 2. Modify application settings if needed to set the Prediction Interval. These settings are shared with Predictive Planning. By default, the prediction interval for worst and best cases is 2.5% and 97.5%. See Managing Application and System Settings. 3. Run the Auto Predict prediction: See Running Auto Predict Predictions. • Run the Auto Prediction from the Auto Predict or IPM list. • Schedule a job to run the Auto Predict prediction automatically. Videos Your Goal Watch This Video Learn how to set up an auto predict definition, and schedule a job to run that definition. See how to prefill a prediction scenario to jump start the forecasting process, and how to directly compare the system’s predictions to your ongoing forecast in real time. You compare predictions to Forecast and incorporate variance thresholds that require you to enter explanatory commentary. Also see how to seed plans or forecasts prior to starting the forecast cycle. Forecasting with Auto Predict in EPM Cloud Planning Auto Predict Considerations • Auto Predict works with EPM Standard and EPM Enterprise applications for Custom and Module application types when Hybrid Essbase is enabled. For legacy applications, Auto Predict works with legacy Enterprise Planning and Budgeting Cloud Service and Planning and Budgeting Cloud Service Plus One (PBCS +1), when the Essbase version is upgraded to the version that supports Hybrid Essbase and Hybrid Essbase is enabled. In addition, you can use IPM Insights with Oracle Sales Planning Cloud and Oracle Strategic Workforce Planning Cloud. • Auto Predict is not available in freeform applications. Chapter 16 About Auto Predict 16-2
- 533. • Auto Predict is available in all themes, except for configuring advanced Auto Predict options. Configuring advanced auto predict options is available only with Redwood Experience enabled. • Auto Predict works with custom time periods in Planning and alternate time periods in Planning modules; for example in Financials you can predict at both a weekly level and at a monthly level in the same application. • Prediction results are more accurate the more historical data you have. There should be at least twice the amount of historical data as the number of prediction periods. When series have less than six historical data points, Auto Predict does not use forecasting, instead it uses a straight line fit for the prediction series. In this case there are results only for the base case. Best case and worst case are not calculated, because the values would be the same as the base case. • For details about the statistical forecasting methods used in Auto Predict predictions, see Predictive Planning Forecasting and Statistical Descriptions in Working with Planning . • Planners can do predictions directly on a form. For more information, see Improving Forecasting Accuracy with Predictive Planning in Working with Planning . Creating Auto Predictions for Forecasts Create an Auto Predict prediction definition to automate predictions. To create an Auto Predict prediction definition: 1. From the Home page, click Application, then click Overview, and then from the Actions menu, select Auto Predict. Alternatively, if Redwood Experience is enabled and you are using IPM Insights, from the Home page, click IPM and then click Configure. 2. Click Create. 3. On the Types page, enter a name and a description for the Auto Predict definition. Additionally, if you are using IPM Insights, select Auto Predict in the Generate Predictions area. Then click Next. 4. On the Define Slice page, define the slice of data to analyze for historical and future data, and then click Save. • In the Historical Data section, select the cube and then define the slice of data for the historical data—both actuals and the forecasts provided by the planners. The slice definitions show all the dimensions for the cube, except for the Year and Period dimensions. All members start out with their root member selected. Specify the number of years of historical data to include in the analysis. • In the Future Data section, select the cube and then define the slice of data for future data. Auto Predict results are stored in this location. You can click to add a definition for the slice of data for the best case and worst case scenarios. The prediction interval used to define the Best Case and Worst Case results is defined in Settings for the application and is shared with Predictive Planning. See What Application and System Settings Can I Specify?. Define the periods of future data to include in the analysis. Chapter 16 Creating Auto Predictions for Forecasts 16-3
- 534. You can predict at a weekly level in Financials. To predict at a weekly level, when defining the Auto Predict definition, in the Predict section, you must select Specific Period for the Start Period. Tip: When setting the Start for a prediction, when the start is Specific Period, for the Select Period Member Selector, you can select by substitution variable for the Current Period. In this way, job definitions are updated each time the value for the substitution variable is updated—change the value for the substitution variable and you don't have to edit every job to update the current period. To select for Substitution Variables, in the lower left corner of the Member Selector, select Substitution Variable from the list. 5. On the Configure page, click Save if you want to keep the default prediction options. If you want to define advanced options, click Show Advanced Options. For details on advanced auto predict options, see Configuring Advanced Auto Predict Options. After defining the Auto Predict prediction, you can run the prediction from the Auto Predict page or from the IPM page, or you can schedule a job to run the prediction automatically. See Running Auto Predict Predictions. Auto Predict definitions are saved as global artifacts and are backed up with the maintenance snapshot. Configuring Advanced Auto Predict Options If you haven't yet created an Auto Predict prediction definition, see Creating Auto Predictions for Forecasts. When you're configuring Auto Predict prediction definitions, you can use default prediction options, or on the Configure page, click Show Advanced Options. Showing advanced options gives you additional options for: • Data Screening: See Data Screening Options • Data Attributes: See Data Attributes Options • Prediction Methods: See Methods Options Data Screening Options Historical data can have missing values and outliers, which are data points that differ significantly from the rest of the data. Data Screening options enable you to select several ways of handling missing values and identifying and adjusting outliers. Because adjusted outliers are treated as missing values, both of these situations are discussed and handled together. Select from these options for Data Screening. • Adjust Outliers: When this option is selected, when an outlier is detected in the series, outlier values are replaced with the prediction trend line value to avoid the impact of outliers. Chapter 16 Creating Auto Predictions for Forecasts 16-4
- 535. • Fill in missing values: When this option is selected, if there are missing values in the time series, the missing values are populated with the prediction trend line value to continue with the prediction. • Minimum missing threshold: When this option is selected, missing values in the time series are filled until the threshold is met. If the number of missing values is above the threshold provided, the prediction is not done. The maximum value can't be greater than 50%. Data Attributes Options Select from these options for data attributes and seasonality: • Override prediction range: When this option is selected, the prediction overrides the minimum number of historical data points typically required to run a prediction. Instead, it predicts the number of periods based on the number of historical data points that are available. For example, it predicts y periods when 2y historical data points are available. If this option is not selected, if the prediction range is set to x periods, a minimum of 2x historical data points are required to run a prediction. If the minimum number of historical data points are not available, the prediction does not proceed. • Auto Detect: When this option is selected, the prediction automatically detects seasonality based on the data. • Yearly Seasonal Override (12 periods): When this option is selected, seasonality is defined by the number of level 0 periods from the selected hierarchy. In cases where the number of historical data points is less than 2x of yearly seasonality, the prediction reverts to using Auto Detect for seasonality. • Custom: When this option is selected, you can override the seasonality with a custom value by providing it in Periods per cycle. You can select this option when seasonality is not yearly. • Periods per cycle: When Custom is selected, select the exact number of periods to be considered. If not enough data points are available, the prediction reverts to using Auto Detect for seasonality. The maximum allowed value for Periods per cycle is half of the total number of historical data range periods. Methods Options Select the method to use for predictions. • Apply seasonal methods: Seasonal forecasting methods extend the nonseasonal forecasting methods by adding an additional component to capture the seasonal behavior of the data. For information on seasonal methods, see Classic Seasonal Forecasting Methods in Working with Planning. The prediction selects the best seasonal forecasting method to use. • Apply non-seasonal methods: Nonseasonal methods attempt to forecast by removing extreme changes in past data where repeating cycles of data values are not present. For information on non-seasonal methods, see Classic Nonseasonal Forecasting Methods in Working with Planning. The prediction selects the best nonseasonal forecasting method to use. • Use ARIMA: For more information about Autoregressive Integrated Moving Average (ARIMA), see ARIMA Time-series Forecasting Methods in Working with Planning. Chapter 16 Creating Auto Predictions for Forecasts 16-5
- 536. • Use Extended ARIMA Search: Performs extended model search on ARIMA models by comparing with historical data. Results are accurate, but analysis will take noticeably more time. Running Auto Predict Predictions You can run an Auto Predict prediction definition from the Auto Predict page or the IPM page, or you can schedule a job to run the prediction automatically. Running an Auto Predict Prediction To run an Auto Prediction prediction definition: 1. From the Home page, click Application, then click Overview, and then from the Actions menu, select Auto Predict. Alternatively, if you are using IPM Insights, from the Home page, click IPM and then click Configure. 2. From the list, click Actions next to an Auto Predict definition, and then select Run. For Auto Predict predictions with a large number of cells to calculate, in Run Parameters, select a dimension and then click Run Now. This setting is used to speed up an Auto Predict job by running predictions in parallel in separate prediction threads. For these parallel jobs to be efficient, choose a dimension that will result in evenly spread data for each prediction thread. 3. To review a summary of the prediction, review details in the Jobs Console: Click Application, then Jobs, and then click the prediction definition name on the Jobs page. If a long-running prediction job is interrupted by an automated maintenance window, when the maintenance is complete, the prediction job picks up where it left off. Scheduling an Auto Predict Job For information about scheduling Auto Predict jobs, see Scheduling Jobs. Auto Predict has its own job type, called Auto Predict. For Auto Predict predictions with a large number of cells to calculate, in Run Parameters, select a dimension and then click OK. This setting is used to speed up an Auto Predict job by running predictions in parallel in separate prediction threads. For these parallel jobs to be efficient, choose a dimension that will result in evenly spread data for each prediction thread. For recurring jobs, the selected dimension is used for jobs until you change it. Before running a scheduled prediction job, Auto Predict analyzes certain factors to determine if prediction results would change. If the prediction results would not change, the Auto Predict job is not run. For example, if the historical range was set for the last three years and there has been no change in the start period/year for prediction, the historical data for analysis would be the same and the prediction results wouldn’t change. In this case, to optimize performance and prevent unnecessary jobs from running, the Auto Predict job is skipped. A message is displayed indicating that the job will not run. If you want to run the prediction anyway, you can run the job from the Auto Predict page. Chapter 16 Running Auto Predict Predictions 16-6
- 537. Editing, Deleting, or Duplicating Auto Predict Prediction Definitions You can edit, delete, or duplicate existing Auto Prediction prediction definitions. To edit, delete, or duplicate an Auto Predict prediction definition: 1. From the Home page, click Application, then click Overview, and then from the Actions menu, select Auto Predict. Alternatively, if you are using IPM Insights, click IPM and then click Configure. 2. From the list, click Actions next to an Auto Predict definition, and then select Edit, Duplicate, or Delete. Reviewing Detailed Reports for Auto Predict Predictions You can review Auto Predict prediction result details in a downloadable report in an Excel worksheet format, including details such as prediction status, method used, and prediction accuracy. The Excel workbook contains several worksheets: • Summary: A summary of the prediction including details about the prediction and POV used. • Report: A detailed report of the prediction displayed by series using the alias for member names. Includes details such as status, accuracy, prediction method, seasonality, adjusted outliers, error measure, and other prediction statistics. • SV_Series_Data_CubeName (Smart View Series Data) data access sheet: Data access for the cube used for the prediction using Smart View. Also allows you to perform ad hoc analysis on prediction data. For multiple cube jobs, includes a worksheet for the source cube and a worksheet for the prediction cube. The detailed report is automatically generated when an Auto Predict job runs and is available in compressed format in the Outbox when the job is complete. The report is overwritten the next time the Auto Predict prediction job runs. Reviewing the Report To review the report from the Auto Predict page: 1. From the Home page, click Application, then click Overview, and then from the Actions menu, select Auto Predict. Alternatively, if you're using IPM Insights, from the Home page, click IPM and then click Configure 2. From the Actions menu next to an Auto Predict definition, select Download Report. To download the report from the Outbox: 1. From the Home page, click Application, and then click Overview. 2. From the Actions menu, select Inbox/Outbox Explorer. 3. Look for AP_JobName.zip and download the file. Chapter 16 Editing, Deleting, or Duplicating Auto Predict Prediction Definitions 16-7
- 538. Analyzing Prediction Data On the SV_Series_Data_CubeName worksheet, you can perform ad hoc analysis using Smart View and drill into prediction data: 1. Select the SV_Series_Data_CubeName worksheet. The worksheet is populated with basic information including the historical date range, the prediction date range, and a member to start analysis. 2. Connect to the server where the Auto Predict prediction was run. 3. Select the cube used for the prediction (the cube name is appended to the worksheet name) and then select Set Active Connection for this Worksheet. If the prediction definition uses two cubes, a source cube and a prediction cube, repeat this step on both SV_Series_Data_CubeName worksheets, selecting the appropriate cube to associate with each worksheet. 4. Click Refresh. Tips for analyzing prediction data: • For members you want to analyze, copy and paste the members from the Report worksheet (from the Series Dimension columns) to the SV_Series_Data_CubeName worksheet. • On the Report worksheet, you can sort to analyze data in different ways. For example, sort on the Accuracy column to review cases with low accuracy. Then, copy and paste the members you want to analyze further to the SV_Series_Data_CubeName worksheet, for example, the ten members with the lowest accuracy. • Use Excel charting features to visualize prediction results in different ways. • If you want to use Predictive Planning on the worksheet data, you must first pivot all of the dimensions from the columns, other than the month and year, to the POV using the Planning Ad Hoc menu. Chapter 16 Reviewing Detailed Reports for Auto Predict Predictions 16-8
- 539. 17 Managing Sandboxes Enable users to use sandboxes to keep their work private while experimenting with various outcomes as they develop their plans. Related Topics • About Sandboxes • Enabling Sandboxes • Enabling Version Members • How Sandboxes Work with HSP_View and Version Members • What Happens When a Sandbox is Published? • Managing Sandboxes • Sandboxes and Other Functionality About Sandboxes Sandboxes enable users to keep their work private (from other non-administrators) as they develop their plans (see Building a Plan Privately in Working with Planning). Users may want to privately experiment with various outcomes in a sandbox without having others see their numbers until they've completed their analysis. When they're ready to make their numbers public (to others having access to them), they publish the data in the sandbox. Some basics about sandboxes: • Sandboxes are enabled at the cube level. You can select the Sandboxes option for block storage cubes that are seeded when you create the application. You can also enable sandboxes when you create a new block storage cube. You can’t later change the sandboxes option for existing cubes, including cubes created by default such as Plan1. See Enabling Sandboxes. • By default, forms and ad hoc grids are in base view. When a user starts working in a sandbox, the form switches from base view to sandbox view. In sandbox view, the user's data is saved independently of the application's data. When users are done privately modifying and analyzing data in the sandbox, they publish the sandbox. When published, the new and changed data is saved to the application. The form is then back in base view. See What Happens When a Sandbox is Published?. • To provide access to sandboxes for users with the User role, you must enable the Apply Security option for the Version dimension. See also Enabling Sandboxes and Enabling Version Members. • All access permissions are in effect in sandboxes, including security on approval units. For example, if the Version member is part of an approval unit that is in the approvals process, users have write access only when they are the current owner of the approval unit. • Users can have multiple sandboxes and switch among them. 17-1
- 540. • Multiple users can simultaneously work in multiple sandboxes without affecting each other's work. • Service Administrators can see the names of (and data in) all sandboxes, which version member they're based on, who created each one, when they were last modified. Service Administrators can also delete anyone's sandbox. To manage sandboxes, from the Home page, click Application, then click Overview, then Actions, and then Manage Sandboxes. • Because dynamic members are automatically calculated, users can immediately see the effect of their changes. • When a cube is enabled for sandboxes, a dimension called HSP_View is added, with three members: BaseData, SandboxData, and ConsolidatedData. See How Sandboxes Work with HSP_View and Version Members. • When working in a sandbox, users can add members, but those members aren't added to the base version when the sandbox is published. Videos Your Goal Watch This Video Learn how to analyze data with sandboxes. Analyzing Data with Sandboxes in Oracle Planning and Budgeting Cloud Enabling Sandboxes To enable sandboxes: 1. When you create an application, a block storage cube is created, which you can enable for sandboxes by selecting the Sandboxes option. You can also enable sandboxes when you create custom block storage cubes by selecting Enable Sandboxes. You can enable sandboxes only in Standard applications and for custom cubes created in Enterprise applications, not for Reporting applications. After you enable sandboxes for a cube, you can’t later disable that option. If you enable sandboxes for a cube, Version members have the Enable Sandboxes option. 2. Create and enable Version members for sandboxes, as described in Enabling Version Members. 3. If needed, modify member formulas so that they calculate correctly in both base view and sandbox view. Member formulas may be impacted by the new HSP_View dimension. To ensure that member formulas use the correct data for all versions, they must reference "ConsolidatedData"/Sandbox. See: • The topics in How Sandboxes Work with HSP_View and Version Members • Working with Member Formulas Chapter 17 Enabling Sandboxes 17-2
- 541. Note: In Data Maps, all data mapping occurs at the HSP_View BaseData intersection. The base view is selected by default. 4. Design or modify forms that you want to support sandboxes so that either: • The Version dimension is on the Page axis. • The Version dimension is a POV that has a user variable. Note: – Forms that don't meet one of the above conditions do not display sandbox options. – In a sandbox, the HSP_View member is fixed on the POV and can't be changed. – The only business rules that users can run in a sandbox are the default Calculate Form and Calculate Currencies rules. – You can't import or export when you're in the sandbox view. Enabling Version Members To make versions available to sandboxes, Service Administrators create Version members and then select the member property Enable Sandboxes. When users switch to sandbox view, they select an enabled Version member, and then the data in the sandbox is tied to that version. When the user switches back to base view, the base version data is displayed. If a user publishes their sandbox data, the modified data in the sandbox is saved to the application and displays in the base view. See How Sandboxes Work with HSP_View and Version Members and What Happens When a Sandbox is Published?. Tip: To edit member properties, from the Home page, click Navigator , and then under Create and Manage, click Dimensions. Note that the Dimensions link is available only if you're accessing the application from the desktop. How Sandboxes Work with HSP_View and Version Members Related Topics • The HSP_View Dimension Chapter 17 Enabling Version Members 17-3
- 542. • Sample Formula for the ConsolidatedData Member • Sandbox Version Members • Sandbox Implications on Member Formulas The HSP_View Dimension When a cube is enabled for sandboxes, the HSP_View dimension is created with the following members. • The BaseData member defines the data intersection when users are working in the base view in a form. When users are not working in a sandbox, data is stored at the intersection of the BaseData member. • The SandboxData member stores the data when a user works with data in a sandbox. • The ConsolidatedData member is dynamically calculated; it retrieves data from the SandboxData member if it's available. Otherwise, the ConsolidatedData member retrieves data from the BaseData member of the base version. Note: • You can't change the HSP_View dimension or its members. You should not change the order of the HSP_View dimension in Performance Settings. To view Performance Settings, from the Home page, click Navigator , and then under Create and Manage, click Dimensions. • In a form, the HSP_View member is fixed on the POV and can't be changed. • Aggregations at the top levels of sparse dimensions are not supported in Sandbox view. Sample Formula for the ConsolidatedData Member Assuming that Market is a sparse dimension and that Working is a base version, here is a sample formula for the ConsolidatedData member: IF(@ISLev("Market",0)) IF(@ISLev("Entity",0)) IF (@ISLev("Period", 0)) IF(NOT (@ismbr(@relative("Sandboxes",0)))) BaseData; ELSE IF (SandboxData== #MISSING ) IF(@ISCHILD("Sandboxes_Working")) "Working"->BaseData; ENDIF ELSE SandboxData; ENDIF ENDIF Chapter 17 How Sandboxes Work with HSP_View and Version Members 17-4
- 543. ENDIF ENDIF ENDIF Sandbox Version Members When an application is enabled for sandboxes, a Sandbox member is created under the Version dimension. When a sandbox is created, a Version member is added under the Version Sandbox member, with the name given by the creator of the sandbox. Example: • The data in the base form is stored at the intersection of the HSP_View BaseData member and the base version (for example, Working). • The data in the sandbox is stored at the intersection of the respective member from the Version dimension (for example, Sandbox 1) and the HSP_View member SandboxData. Sandbox Implications on Member Formulas When you create or modify member formulas, for data to be calculated correctly in both the base and sandbox views, member formulas must refer to the intersection of the HSP_View ConsolidatedData member and the sandbox Version member. Example: Chapter 17 How Sandboxes Work with HSP_View and Version Members 17-5
- 544. What Happens When a Sandbox is Published? When a user publishes the data in a sandbox: • The modified data in the sandbox is saved to the application only for those intersections that are visible in the base view at the time the data is published and only for those cells to which the user has write permission. Sandbox data is saved to the base view in all affected forms and cubes. Even if the user has modified data in multiple forms or different page/POV combinations, all modified data, supporting detail, and comments are moved to the application. • The application deletes the sandbox. (Service Administrators can delete sandboxes before the data in them is published. See Managing Sandboxes.) • If the publish action takes longer than the three minute default, then the job runs in the background and is displayed in the Job. Note: If multiple users publish sandbox data to the same member in the base view, the most recently published data overwrites previously published data. Managing Sandboxes To manage sandboxes: 1. Click Application, then click Overview, then Actions, and then Manage Sandboxes. 2. To filter the list of sandboxes, click , and then complete any of these fields: • Sandbox Name • Base Version • Created By 3. To delete sandboxes, click their names, and then Delete. Sandboxes and Other Functionality • Oracle Smart View for Office: – Sandbox functionality is available in Smart View, though you can't create, delete, or publish data from Smart View. – In ad hoc analysis, users can see the HSP_View members, which includes sandbox and base data. – Selecting the ConsolidatedData member displays the data entered in both the sandbox and the original base data. Chapter 17 What Happens When a Sandbox is Published? 17-6
- 545. – Sandboxes are supported for Smart Slices, but the HSP_View dimension is hidden. – In Planning Admin Extensions, the HSP_View dimension is displayed under Dimensions, but you can't change member properties. Likewise, you can't change the member properties of sandbox Version members. • Financial Reporting: To report on base view data, select the BaseData member of the HSP_View dimension. To report on sandbox data, select the ConsolidatedData member for HSP_View. • Data Management: The HSP_View dimension is visible in the mappings, but you can map only the BaseData member. • Migration: If you clone an application using Migration, Oracle recommends that you select the Sandbox Changes option. If you're importing sandboxes and data, you must select Sandbox Changes if you want to publish the sandbox data. • Oracle Hyperion Public Sector Planning and Budgeting: Decision Packages and Budget Requests don't support sandboxes. Chapter 17 Sandboxes and Other Functionality 17-7
- 546. 18 Defining Valid Intersections and Cell-Level Security Define rules that restrict who can enter or view data in your application. You can restrict who can enter data in your application by creating rules that mark certain member intersections as valid (or invalid) for data entry. These rules are called valid intersections. You can also restrict who can view data in your application by creating rules that remove read or write access to cells that a user would normally have access to due to their regular security. These rules are called cell-level security. • To define valid intersections, see Defining Valid Intersections. • To define cell-level security, see Defining Cell-Level Security Defining Valid Intersections Define valid intersection rules which filter certain cell intersections to users when they enter data or select runtime prompts. Related Topics • Understanding Valid Intersections • Creating Valid Intersections • Managing Valid Intersections • Suppressing Invalid Data in Forms • Clearing Invalid Data • Working with Valid Intersections Understanding Valid Intersections Valid intersections are cell intersections that are filtered based on rules you define, called valid intersection rules, which filter 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 or departments. After valid intersections are defined, cells containing invalid data are read-only. This restriction speeds the planning process and optimizes the information available to users. Conversely, you might have a use case where data entry is allowed in most cell combinations and you only need to prevent data entry to a select few cell combinations. In this case you can ease the definition process by defining invalid intersections. You define invalid intersections in the same way that you define valid intersections except you can specify the invalid intersection definition type while creating the intersection group. To better understand how valid intersections affect behavior in forms and in runtime prompts, see Working with Valid Intersections. 18-1
- 547. Videos Your Goal Watch This Video Learn how to manage valid intersections. Managing Valid Intersections in Cloud EPM Related Topics • Valid Intersection Groups • Valid Intersection Rules • Anchor and Nonanchor Dimensions • Valid Intersection Examples • Redundancy or Overlap in Valid Intersection Rules • Shared Members and Valid Intersection Rules • Substitution Variables and Valid Intersection Rules • Evaluation Order Valid Intersection Groups Valid 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 valid or invalid Valid Intersection Rules Valid intersection rules: • Must use the same dimensions that were defined within their valid intersection group • Valid intersection rules within the same valid intersection group that produce an apparent conflict or overlap, are marked valid if either valid intersection rule condition is met • Valid intersection rules in different valid intersection groups that produce an apparent redundancy or overlap, are marked valid if they satisfy the requirements of all valid intersection groups Thus, if any valid intersection group marks an intersection invalid, regardless of other valid intersection groups making it valid, the system will mark the intersection invalid. Invalid groups override valid group results. Chapter 18 Defining Valid Intersections 18-2
- 548. Note: If you want to remove valid intersections regardless of what other valid intersection groups allow, then this rule must be in a different valid intersection group. See Valid Intersection Examples. Anchor and Nonanchor Dimensions Anchor and nonanchor dimensions: • Anchor dimensions are always required dimensions in the cube that is used in the valid intersection evaluation. • Nonanchor dimensions are either required or not: – If a nonanchor dimension is required, any cube that doesn't use that dimension will ignore any valid intersection group where that dimension is tagged as required as it evaluates the valid intersections. – If a nonanchor dimension isn't required, any cube that doesn't use that dimension will still evaluate any valid intersection group that includes that dimension as not required and evaluate the intersections of any other dimensions in the valid intersection group in use in the cube. • Unselected anchor dimension members are valid by default, but you can mark them invalid by clearing the Unselected Members are Valid option. This option marks all intersections with anchor dimension members not selected in this rule as invalid. See Valid Intersection Examples. Valid Intersection Examples This section provides valid intersection group and valid intersection rule examples to illustrate a few simple, complex, and edge-case scenarios. Example: Anchor and Nonanchor Dimensions The choice of the anchor dimension is critical. Consider the following example, which produces a different result based on the anchor dimension definition: • Valid intersection group 1 defines Entity as the anchor dimension and Product as a nonanchor dimension. • Valid intersection group 2 reverses this definition with Product as the anchor dimension and Entity as the nonanchor dimension. Table 18-1 Example - Anchor Dimension is Entity Valid Intersection Group Anchor Dimension - Entity Nonanchor Dimension - Product 1 DESC(500 - Manufacturing) - Unselected members are valid DESC(P_TP1 - Computer Equipment) Chapter 18 Defining Valid Intersections 18-3
- 549. Group 1 means entities that are descendants of Manufacturing are valid only with descendant products of Computer Equipment. No other products are valid with descendants of Manufacturing. All other entities besides descendants of Manufacturing are valid with all products, including descendants of Computer Equipment. Table 18-2 Example - Anchor Dimension is Product Valid Intersection Group Anchor Dimension - Product Nonanchor Dimension - Entity 2 DESC(P_TP1 - Computer Equipment) - Unselected members are valid DESC(500 - Manufacturing) Group 2 means products that are descendants of Computer Equipment are only valid with descendant entities of Manufacturing. No other entities are valid with descendants of Computer Equipment. All other products besides descendants of Computer Equipment are valid with all entities, including descendants of Manufacturing. Caution: The choice of anchor dimension is significant. You'll get dramatically different results if you choose the wrong anchor dimension. Example: Required Dimension In the following example, if a nonanchor dimension isn't required, then the application evaluates all remaining dimension intersections in the valid intersection group for a cube that doesn't contain the nonrequired dimension. This behavior could result in the evaluation of a valid intersection group with only one effective dimension. Table 18-3 Example - Required vs. Non-Required Nonanchor Dimensions Valid Intersection Group Anchor Dimension - Entity Nonanchor Dimension - Product 1 DESC(500 - Manufacturing) - Unselected members are valid DESC(P_TP1 - Computer Equipment) - Not required In Group 1, the product dimension isn't required, and unselected entities are valid. Therefore, if the cube of the form or business rule, at runtime, doesn't include the product dimension, the application evaluates the entity dimension selections to mark all entities as valid for a cube that doesn't contain the product dimension. Table 18-4 Example - Required vs. Non-Required Nonanchor Dimensions Valid Intersection Group Anchor Dimension - Entity Nonanchor Dimension - Product 2 DESC(500 - Manufacturing) - Unselected members are invalid DESC(P_TP1 - Computer Equipment) - Not required Chapter 18 Defining Valid Intersections 18-4
- 550. In Group 2, the product dimension isn't required, and unselected entities are invalid. Therefore, if a cube doesn't include the product dimension, then the application evaluates the entity dimension selections to mark all entities except descendants of Manufacturing as invalid. Thereafter, any cube that doesn't use the product dimension will only allow data 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 one effective dimension. Additionally, selecting the Unselected Members are Valid option for anchor dimension members also plays a significant role in the system behavior for valid intersections. See Valid Intersection Examples. Example: Unselected Members are Valid In the following example, two intersection groups are valid. In one group, the anchor dimension unselected members are invalid (this option is cleared). In the other group, the anchor dimension unselected members are valid (this option is selected). Table 18-5 Example - Unselected Members are Valid Valid Intersection Group Anchor Dimension - Account Nonanchor Dimension - Entity 1 IDESC(BS - Balance Sheet) - Unselected members are invalid 000 - No Department 2 IDESC(GP - Gross Profit) - Unselected members are valid IDESC(403 - Sales) Because Group 1 defines all unselected members as invalid, the application marks noninclusive descendants of Balance Sheet invalid. Gross Profit isn't an inclusive descendant of Balance Sheet. So even though Group 2 explicitly states inclusive descendants of Gross Profit are valid with inclusive descendants Sales entities, the invalid definition from Group 1 overrides any further valid intersections of the same anchor dimension member set. Example: Redundant or Overlapping Valid Intersection Rules Within the Same Valid Intersection Group When valid intersection rules are within the same valid intersection group and produce any redundancy or overlap, the system marks an intersection valid if either of the valid intersection rule conditions are met. Table 18-6 Example - Redundant or Overlapping Valid Intersection Rules Within the Same Valid Intersection Group Valid Intersection Rule Anchor Dimension - Account Nonanchor Dimension - Entity 1 IDESC(GP - Gross Profit) - Unselected members are valid IDESC(403 - Sales) 2 IDESC(NI - Net Income) - Unselected members are valid IDESC(TD - Total Department) Chapter 18 Defining Valid Intersections 18-5
- 551. Because Gross Profit is a descendant of Net Income and Sales is a descendant of Total Department, inclusive descendants of Gross Profit are valid with any inclusive Descendant of Total Department. Rule 1 is a subset of Rule 2, so Rule 1 is effectively a "No operation" rule and is unnecessary. There is no restriction on inclusive descendants of Gross Profit accounts only being valid for inclusive descendants of Sales Entities. Example: Redundant or Overlapping Valid Intersection Rules in Different Valid Intersection Groups When valid intersection rules are in different valid intersection groups and produce any redundancy or overlap, the system marks an intersection valid only if it satisfies the requirements of all valid intersection groups. In the following example, there are redundant or overlapping rules in different groups: Table 18-7 Example - Redundant or Overlapping Valid Intersection Rules in Different Valid Intersection Groups Valid Intersection Group Anchor Dimension - Account Nonanchor Dimension - Entity 1 IDESC(GP - Gross Profit) - Unselected members are valid IDESC(403 - Sales) - Required 2 IDESC(NI - Net Income) - Unselected members are valid IDESC(TD - Total Department) - Not required Because Group 1 is further restrictive for inclusive descendants of Gross Profit accounts being valid with inclusive descendants of Sales entities, the application enforces this group for these intersections. Other, non-Gross Profit accounts can still use all inclusive descendants of Total Department entities, but inclusive descendants of Gross Profit accounts must use inclusive descendants of Sales entities. Redundancy or Overlap in Valid Intersection Rules Valid intersection rules within the same valid intersection group, which produce any apparent conflict or overlap, are marked valid if either valid intersection rule condition is met. If different valid intersection groups share the same attributes, including the anchor dimension, required and not required nonanchor dimensions, and Unselected Members are Valid attribute, they will be treated as rules of the same valid intersection group. Shared Members and Valid Intersection Rules Shared members are supported in valid intersection rules. If a base member is selected for a valid intersection rule, any shared members are also included in the rule. Conversely, if a shared member is selected for a valid intersection rule, the base member is also included in the rule. Substitution Variables and Valid Intersection Rules You can use substitution variables in valid intersection rules. User variables are not supported. Substitution variables can be set on the Essbase server, application, or Chapter 18 Defining Valid Intersections 18-6
- 552. database level. The same substitution variable can exist on multiple levels; the application uses the first one it finds as it searches in this order: 1. Database (cube) 2. Application 3. Server Evaluation Order Evaluation order for valid intersection groups orders invalid results sets as quickly as possible, increasing the speed and efficiency of the overall valid intersection evaluation. For example, the application evaluates the first valid intersection group in the list, then the second group, and so on. If the application finds an invalid intersection in the second group in the list, it will stop evaluating the rest of the list because, once an intersection is defined as invalid, it will override other valid intersection rule results. To change the order in which the groups are evaluated, see Changing the Valid Intersection Group Evaluation Order. Creating Valid Intersections You can define rules to filter certain cell intersections to users when they enter data, select members, or select runtime prompts. To create a valid intersection: 1. Click Application, and then click Valid Intersections. 2. If it isn't already selected, click the Setup tab. Note: If Redwood Experience is enabled, the Setup tab is at the bottom of the page. 3. Create the valid intersection group: a. Click Create. b. Enter a name and description for the new intersection. c. The Enabled checkbox is selected by default. To disable the valid intersection group, clear the Enabled checkbox. You can also enable or disable a valid intersection group directly on the Valid Intersections page. See Disabling and Enabling Valid Intersection Groups. d. For Definition Type, select one of the following: • Valid Intersection • Invalid Intersection e. To select the anchor dimension for the intersection group, click next to Select Anchor Dimension. Chapter 18 Defining Valid Intersections 18-7
- 553. f. Optional: By default, the anchor dimension members that are not specified in the valid intersection rule are marked valid. To clear this option, click next to the anchor dimension, and then click Unselected members are valid. For an explanation of this option and for an example of how it's used, see Anchor and Nonanchor Dimensions. g. To select additional dimensions (called nonanchor dimensions), click Add Dimension. h. Optional: By default, nonanchor dimensions are not required. To make a nonanchor dimension required, click next to the nonanchor 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 valid intersection, click next to the dimensions in the new rule: • Click Edit to open the Select Members page and select the members, substitution variables, and attributes to include in the valid intersection rule. See Using the Member Selector. • Click Exclude or Exclude All to define the dimension members you want to exclude from the rule: – Exclude: Selecting this option excludes members by ID. Only the specified members (base or shared) will be excluded. – Exclude All: Selecting this option excludes members by name. If a base member is specified, then the base and all of its shared members will be excluded. If a shared member is specified, then this member, its base member, and all other shared members of this member will be excluded. • Click Clear to clear the selection. To delete a rule, click . 5. Click Save and Close. 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 Group Evaluation Order. Managing Valid Intersections Related Topics • Viewing Valid Intersections • Filtering Valid Intersections • Importing and Exporting Intersections • Changing the Valid Intersection Group Evaluation Order • Disabling and Enabling Valid Intersection Groups • Editing Details for a Valid Intersection Group Chapter 18 Defining Valid Intersections 18-8
- 554. • Duplicating Valid Intersection Groups • Deleting a Valid Intersection Group Viewing Valid Intersections To view valid intersections: 1. Click Application, and then click Valid Intersections. 2. If it isn't already selected, click the Setup tab. Note: If Redwood Experience is enabled, the Setup tab is at the bottom of the page. 3. To search the entire listing for certain intersections, enter search criteria in the Search box and then click to display only the intersections that meet the search criteria. 4. To filter the listing so it displays only the intersections that meet the filter criteria, specify the following filter options: • : Click to display the Filter page where you can select from a robust list of filter options. For a complete list of filter options and their descriptions, see Filtering Valid Intersections. • : Click to clear all filters. • Enabled: Filters the list so you view only the intersections that are enabled (Yes), not enabled (No), or select All. • Definition Type: Filters the list so you view only the intersections that are the Valid Intersection or Invalid Intersection types, or select All. 5. You can also perform these tasks on the Valid Intersections page: • Actions menu: To import and export valid intersections, see Importing and Exporting Intersections . • Create: See Creating Valid Intersections. • Refresh: Click to refresh the intersections listing. 6. For each listing on the intersections page you can perform the following tasks: • Enabled column: Indicates whether an intersection is enabled. Click the check mark next to the intersection to disable or enable it. A green check mark indicates that the definition is enabled. See Disabling and Enabling Valid Intersection Groups. • Action column: Click to edit, duplicate, or delete an intersection, or to move it up or down in the listing order. See the following topics: – Changing the Valid Intersection Group Evaluation Order – Editing Details for a Valid Intersection Group – Duplicating Valid Intersection Groups – Deleting a Valid Intersection Group Chapter 18 Defining Valid Intersections 18-9
- 555. Filtering Valid Intersections You can filter the list of intersections by certain criteria such as whether the intersection is enabled or not, whether the definition is valid or invalid, when it was modified, and by whom. When you filter, only the intersections that meet the filter criteria are displayed on the Valid Intersections page. To filter intersections: 1. Click Application, and then click Valid Intersections. 2. Click to specify filter criteria: • Enabled: View only the intersections that are enabled (Yes), not enabled (No), or select All. • Definition Type: View only the intersections that are the Valid Intersection or Invalid Intersection types, or select All. • Modified: View only the intersections that were modified before or after a certain date and time, or the intersections modified within a range of dates or times. Select After, Before, or Between and then click to specify the date and time criteria. • Modified By: View only the intersections modified by selected users. 3. Click More to further refine the filter criteria: • Dimensions • Anchor Dimensions • Unselected members are valid: Choose Yes, No, or All. • Additional Dimensions Required: Choose Yes, No, or All. 4. Click Apply. Importing and Exporting Intersections About Importing and Exporting Valid Intersections You can export the filtered list of valid intersections from the listing page to a location on your local computer, or you can export them to the server. If no filter is defined on the listing page, then all intersections are exported. Use the Import action to import intersections into the application from a location on your local computer or import them from the server. When you perform an import, the system tests the import file for anything that might break a definition; for example, if a cube is missing, or if an anchor dimension doesn't exist, or if a subrule is not found, errors are logged in the error file. Import jobs will only complete successfully if the import file has no errors. Depending on the export or import location you choose, the intersections are exported or imported in either an Excel file format (XLSX) or a zip file format. Chapter 18 Defining Valid Intersections 18-10
- 556. Note: Locked valid intersection rules are not exported when you export valid intersections. Locked valid intersection rules (and rules that start with restricted prefixes such as FCCS_, OCX_, OEP_, OFS_, OPF_, OWP_, TRCS_) are not imported when you import valid intersections. Valid Intersections Import File The Excel import file must have two sheets with the following names for the first and second sheets: 1. Rules 2. Sub Rules The Rules sheet has the following column headings: • Name • Position • Description • Enabled • Definition Type • Anchor Dim Name • Anchor Dimension Apply to Selected Members • Dim1 • Dim1 Required • Dim2 • Dim2 Required • Dim X • Dim X Required The Sub Rules sheet has the following column headings: • Name - This column must contain the name of the Rule from the first sheet • Anchor Members • Anchor Exclusion • Anchor Exclusion All • Dim1 Members • Dim1 Exclusion • Dim1 Exclusion All • Dim2 Members • Dim2 Exclusion • Dim2 Exclusion All • Dim X Members Chapter 18 Defining Valid Intersections 18-11
- 557. • Dim X Exclusion • Dim X Exclusion All Exporting and Importing Valid Intersections To export and import intersections: 1. Click Application, and then click Valid Intersections. 2. Apply filters to the listing, as needed. See Filtering Valid Intersections. 3. To export, click Actions, then Export, and then select the target location for the export file: • Local: Saves the export file to a location on your local computer. If you choose this option, click Export, and then specify where to save the export file. • Outbox: Runs a job that saves the export file in a zip format to the server which you can download now or use to schedule an export job later. If you choose this option, click Save and Run Job. To download the export file from the Outbox: a. Click Application, and then click Jobs. b. Under Recent Activity click the export job. c. On the Job Details page, click to select a download location for the export file. You can also download the export file from the Inbox/Outbox Explorer for your business process. 4. If editing the export file in Excel, note that the Excel file has two sheets: Rules and Sub Rules. 5. To import, click Actions, then Import, and then select the location of the import source file: • Local: Loads the import file from a location on your computer. For Source File, click Browse to select the import file on your computer, and then click Import. • Inbox: Runs a job that loads the import file from the server. The import file must be in a zip file format. Enter the name of the file in Source File, click Save and Run Job, and then specify the Name and Error File on the Save as Job dialog. The error file provides information about the intersections that were not imported. You can download the error file from the Inbox/Outbox Explorer for your business process. Changing the Valid Intersection Group Evaluation Order Evaluation order for intersection groups orders invalid results sets as quickly as possible, increasing the speed and efficiency of the overall intersection evaluation. To learn more about evaluation order, see Evaluation Order. To change the position of a valid intersection group in a list: 1. Click Application, and then click Valid Intersections. 2. If it isn't already selected, click the Setup tab. Chapter 18 Defining Valid Intersections 18-12
- 558. Note: If Redwood Experience is enabled, the Setup tab is at the bottom of the page. 3. To the right of the intersection group in the listing, click . 4. Select Move Up or Move Down. Tip: You can also drag intersection groups to move them up and down in the list. Disabling and Enabling Valid Intersection Groups Intersection groups, by default, are enabled at the time of creation. If you don't want an intersection group to be evaluated or used, you can disable it on the Valid Intersections page. When an intersection group is disabled, the intersection rule for that group no longer applies when viewing application forms, business rules, or runtime prompts. You can also reenable a disabled intersection group. To disable and enable an intersection group: 1. Click Application, and then click Valid Intersections. 2. If it isn't already selected, click the Setup tab. Note: If Redwood Experience is enabled, the Setup tab is at the bottom of the page. 3. In the Enabled column of the intersection list, click the check mark next to the intersection group that you're 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 correct evaluation order in the intersections list. If they are not, then move them up or down in the order. See Changing the Valid Intersection Group Evaluation Order. Editing Details for a Valid Intersection Group To edit intersection group details, you work with dimension members in the member selector. You can also define exclusions in intersection rules. To edit intersection group details: 1. Click Application, and then click Valid Intersections. Chapter 18 Defining Valid Intersections 18-13
- 559. 2. If it isn't already selected, click the Setup tab. Note: If Redwood Experience is enabled, the Setup tab is at the bottom of the page. 3. Click the name of the intersection group you want to edit. Note: A pagination bar displays at the bottom of the rules page. If you have a large number of rules, you can use the pagination bar to easily navigate between the rules pages and to jump to a specific page. The page size options (number of rules per page), which you can select on the pagination bar, are 25, 50, 100, and All. (Note that the All option isn't available if you have more than 300 rules.) • To edit dimension details, next to the dimension, click to select the members to include, exclude, or remove in the intersection rule: – Click Edit to open the Select Members page and select members, substitution variables, and attributes to include in the intersection rule. You can also type in the members or functions. See Using the Member Selector. – Click Exclude or Exclude All to define the dimension members you want to exclude from the rule: * Exclude: Selecting this option excludes members by ID. Only the specified members (base or shared) will be excluded. * Exclude All: Selecting this option excludes members by name. If a base member is specified, then the base and all of its shared members will be excluded. If a shared member is specified, then this member, its base member, and all other shared members of this member will be excluded. – Click Clear to clear the selection. • To delete a dimension from an intersection group, next to the dimension, click , and then click . • To remove a rule from an intersection group, click . • To add a dimension or a rule to an intersection group, click Add Rule or Add Dimension. 4. Click Save and Close. Chapter 18 Defining Valid Intersections 18-14
- 560. Duplicating Valid Intersection Groups To speed intersection group creation, you can duplicate an existing intersection group and then edit it. To duplicate an intersection group: 1. Click Application, and then click Valid Intersections. 2. If it isn't already selected, click the Setup tab. 3. Click to the right of the intersection group you want to duplicate, and then select Duplicate. The duplicate group is added to the end of the intersections list with the word "Copy" appended to the name. 4. Open the intersection group and edit it. 5. Reorder the intersection groups, if needed. See Changing the Valid Intersection Group Evaluation Order. Deleting a Valid Intersection Group After a group is deleted, the intersection groups are reordered. If there are three intersection groups, and the second one in the order is deleted, the third intersection group becomes number two. To delete an intersection group: 1. Click Application, and then click Valid Intersections. 2. If it isn't already selected, click the Setup tab. Note: If Redwood Experience is enabled, the Setup tab is at the bottom of the page. 3. Click to the right of the intersection group that you want to remove, and then select Delete. 4. Reorder the remaining intersections, if needed. See Changing the Valid Intersection Group Evaluation Order. To delete an intersection rule from an intersection group, see Editing Details for a Valid Intersection Group. Suppressing Invalid Data in Forms Suppressing invalid data hides rows or columns in application forms that contain invalid data. If this option isn't selected, then the application displays rows or columns that contain cells with data that are invalid. Cells with invalid data are read-only. To suppress invalid data in forms: 1. From the Home page, click Navigator , and then under Create and Manage, click Forms. Chapter 18 Defining Valid Intersections 18-15
- 561. 2. Select the form, click , and then click Layout. 3. Under Grid Properties, select Suppress invalid data - Rows and/or Suppress invalid data - Columns. 4. Click Save. Clearing Invalid Data Related Topics • About Invalid Data • Working With Invalid Intersection Reports • Clearing Data at Invalid Intersections About Invalid Data If data already exists at intersections, then adding or modifying valid intersections invalidates the existing data. Creating a valid intersection rule or modifying an existing valid intersection rule doesn't clear data in the invalid intersections. You must generate a valid intersection rule report, which will show where data exists at invalid intersections, and then determine whether to clear the data. Note: Data may remain at an invalid intersection for historical purposes or for use in forward looking scenarios. Therefore, it's not a requirement to clear data at invalid intersections. Working With Invalid Intersection Reports You can view reports that show data at invalid intersections on the Reports tab of the Valid Intersections page. Invalid Intersection Reports lists existing reports, their status, and the last time they were run. To work with invalid intersection reports: 1. Click Application, then Valid Intersections, and then click the Reports tab. Note: If Redwood Experience is enabled, the Reports tab is at the bottom of the page. 2. Perform a task: • To refresh the listing, click Refresh. • To create a report, click Create, name the report, select the cube, choose the scope of the report, and then select when to run the report. You can run the report now or run the report later by saving it as a job. To save a report without Chapter 18 Defining Valid Intersections 18-16
- 562. running it, click Save and Close. To remove a report after it's run, click Remove Reports. Note: Invalid intersection reports are not supported for aggregate storage cubes. Aggregate storage cubes are not listed in the Cube drop-down list. • To edit a report, click , and then Edit. • To copy a report, click , and then Duplicate. • To run a report, click , and then Run. • To delete a report, click , and then Delete. Clearing Data at Invalid Intersections Users with appropriate permissions can clear the invalid data if the data isn't needed. To clear invalid data, run the report, and then click Clear Invalid Intersections. Working with Valid Intersections Related Topics • Working with Valid Intersections in Application Forms • Working with Valid Intersections in Calculation Manager Rule Runtime Prompts Working with Valid Intersections in Application Forms Using valid intersections prevents data entry for invalid intersections as defined in the applicable valid intersection group. The affected cells in the form display as read-only following standard, read-only color coding. If you hover the cursor over an invalid intersection, a tool tip displays indicating the cell is read-only because it's defined as an invalid intersection. The valid intersection group applies first to the form point of view and page axis. If the point of view intersections are all invalid, then a warning message is displayed, and the form doesn't 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 to restrict data entry at invalid intersections. If the Suppress Invalid Data option for the form is enabled, then the form suppresses invalid rows, columns, or both, as appropriate. Any rows or columns, which consist of a mix of valid and invalid intersections, display those intersections as valid or invalid, as appropriate. Invalid intersections are displayed with standard, read-only shading and preclude data entry. Application users can reset the point of view to the default, unfiltered list without closing and reopening the form by clearing the selections. Application users can also clear a selection, thus opening up more selections for other dimensions. They will not be able to render a form with a dimension cleared, because valid members must be selected for each dimension. Chapter 18 Defining Valid Intersections 18-17
- 563. In the member selector, invalid members are suppressed due to valid intersection rules. Application users can display invalid members in the member selector using the Show Invalid Members option. Invalid members are displayed but are unavailable for selection. Note: Valid intersection groups don't grant access to dimension members. Valid intersection groups further restrict the valid intersections of dimension members already granted to an application user. Table 18-8 Form Behavior if Valid Intersections are Applied Action Behavior Open a form The form renders with member selections as defined in the form definition, adhering to the user's access rights for dimensions, and applies valid intersection groups with the most recently used as current selections. Select members from a point of view dimension The application: • Enables users to select a member on the point of view • In the member selector for a point of view dimension, enables users to select from a filtered list of remaining valid intersections, which is based on the members that were selected for the other point of view dimensions • Ignores the order in which point of view dimension members are selected because selecting a member from any dimension included in a valid intersection group dynamically filters the remaining dimension members lists for those dimensions included in the valid intersection group, as appropriate, when that dimension is selected • Provides the option to hide invalid members from dimension lists or display them as unselectable in the point of view • Provides the ability to reset the point of view to the fully unfiltered list without closing and reopening the form by clearing the selections Note that ad hoc forms, both in Web and Oracle Smart View for Office, will not filter page or point of view members according to valid intersection groups. Select Go to render a form based on point of view selections. You can also click the right arrow in the form point of view. The form renders as defined based on the valid point of view intersections. Enter and save data The form data is entered and saved. Chapter 18 Defining Valid Intersections 18-18
- 564. Working with Valid Intersections in Calculation Manager Rule Runtime Prompts Valid intersection groups apply to runtime prompts when launched from within the context of the application. Runtime prompts will prevent users from selecting invalid intersections as defined in the valid intersection groups. Filtering according to valid intersection groups isn't supported in Oracle Smart View for Office forms. The rule, however, will not launch if you choose an invalid intersection in the runtime prompts both in the Web and in Smart View. Table 18-9 Runtime Prompt Behavior if Valid Intersections are Applied Action Behavior Launch a Calculation Manager rule runtime prompt The application: • Prevents the user from selecting invalid intersections within the runtime prompt based on the valid intersection group • Prevents the Calculation Manager rule from executing if there are invalid intersections in the runtime prompts Enter valid intersections The valid intersection is allowed to be entered. Defining Cell-Level Security Define security rules which restrict users and groups from viewing data in certain cell intersections in forms. Related Topics • Understanding Cell-Level Security • Creating Cell-Level Security Definitions • Viewing Cell-Level Security Definitions • Filtering Cell-Level Security Definitions • Importing and Exporting Cell-Level Security Definitions • Testing Cell-Level Security • Reordering the Cell-Level Security Definitions List Understanding Cell-Level Security About Cell-Level Security Service Administrators applying cell-level security can deny access to cells that a user would normally have access to due to their regular security. Cell-level security is therefore defined as an exception to the existing member security. For example, a Department Manager requires access to all accounts in their own department, but only a certain account in all other departments. With the usual metadata security the Manager would have access to all accounts across all departments, but using cell-level security enables the Service Administrator to control the intersection of all accounts with the Manager's department and only the specific account in all other departments. Chapter 18 Defining Cell-Level Security 18-19
- 565. Cell-level security uses rules, similar to valid intersection rules, to deny read or write access to users viewing certain cell intersections anywhere a cell is shown (for example, forms, runtime prompts, Smart View, reports, dashboards, infolets, and so on). When cell-level security rules are applied, users with read access can see the data value in a cell but the cell is not editable. If users are denied read access to a cell, the value displayed in the cell is #noaccess. If you are a Service Administrator, you can define and assign cell-level security rules to any user or group. Cell-level security doesn't affect you. Anchor and Nonanchor Dimensions Cell-level security definitions use anchor and nonanchor dimensions: • Anchor dimensions are always required dimensions in the cube that is used in the cell-level security definition. • Nonanchor dimensions are either required or not: – If a nonanchor dimension is required, any cube that doesn't use that dimension will ignore any cell-level security definitions where that dimension is tagged as required. – If a nonanchor dimension isn't required, any cube that doesn't use that dimension will still evaluate any cell-level security definition that includes that dimension as not required and evaluate the definitions of any other dimensions in the definition in use in the cube. – By default, nonanchor dimensions aren't required. To make a nonanchor dimension required, click next to the nonanchor dimension, and click Required. • By default, the anchor dimension members that are not specified in the rule are included in the security definition, but you can clear this option by clicking next to the anchor dimension, and then clicking Apply to Selected Members Only. Creating Cell-Level Security Definitions To create a cell-level security definition: 1. Click Application, and then click Cell-Level Security. 2. Create the definition: a. Click Create. b. Enter a name and description for the definition. c. The Enabled checkbox is selected by default. To disable the definition, clear the Enabled checkbox. You can also enable or disable a definition directly on the Cell-Level Security Definitions page. d. To define cube-specific security, click Cubes and select from the list of cubes or select All. e. An anchor dimension is required. To select the anchor dimension, click Select Anchor Dimension. For information about anchor and nonanchor dimensions, see Understanding Cell-Level Security Chapter 18 Defining Cell-Level Security 18-20
- 566. f. Optional: By default, the anchor dimension members that are not specified in the rule are included in the security definition. To clear this option, click next to the anchor dimension, and then click Apply to Selected Members Only. g. To select additional dimensions (called nonanchor dimensions), click Add Dimension. h. Optional: By default, nonanchor dimensions are not required. To make a nonanchor dimension required, click next to the nonanchor dimension, and click Required. 3. Define the cell-level security rule: a. Click Add Rule. b. In the Users, Groups column, click to find the users and groups to include in the cell-level security rule. c. For Restriction, choose Deny Read (default) or Deny Write. Deny Read is the default option because it is the most restrictive. If users are denied read access to a cell, the value displayed in the cell is #noaccess. Users with Deny Write access can see the data value in a cell but the cell is not editable. d. Click next to the dimensions in the new rule: • Click Edit to open the Select Members page and select the members, substitution variables, and attributes to include in the cell-level security rule. • Click Exclude or Exclude All to define the dimension members you want to exclude from the rule: – Exclude: Selecting this option excludes members by ID. Only the specified members (base or shared) will be excluded. – Exclude All: Selecting this option excludes members by name. If a base member is specified, then the base and all of its shared members will be excluded. If a shared member is specified, then this member, its base member, and all other shared members of this member will be excluded. • Click Clear to clear the selection. To delete a rule, click . 4. Click Save. The new cell-level security definition is added to the end of the list. Definitions are evaluated in the order they appear in the list. To reorder the definitions list, see Reordering the Cell- Level Security Definitions List. After a definition is created, you can test it in a form to see how the form will look from a user's perspective. See Testing Cell-Level Security. Viewing Cell-Level Security Definitions To view cell-level security definitions: 1. Click Application, and then click Cell-Level Security. 2. To search the entire listing for certain definitions, enter search criteria in the Search box and then click to display only the definitions that meet the search criteria. Chapter 18 Defining Cell-Level Security 18-21
- 567. 3. To filter the listing so it displays only the definitions that meet the filter criteria, specify the following filter options: • : Click to display the Filter page where you can select from a robust list of filter options. For a complete list of filter options and their descriptions, see Filtering Cell-Level Security Definitions. • : Click to clear all filters for Effective Assignment, Enabled, and Restriction. • Effective Assignment: Filters the list so you view only the definitions that effect certain users or groups. • Enabled: Filters the list so you view only the definitions that are enabled (Yes), not enabled (No), or select All. • Restriction: Filters the list so you view only the definitions that are assigned the Deny Read or Deny Write restriction, or select All. 4. You can also perform these tasks on the Cell-Level Security Definitions page: • Actions menu: To import and export definitions, see Importing and Exporting Cell-Level Security Definitions. • Test: See Testing Cell-Level Security. • Create: See Creating Cell-Level Security Definitions. • Refresh: Click to refresh the definitions listing. 5. For each listing on the definitions page you can perform the following tasks: • Enabled column: Indicates whether a definition is enabled. Click the check mark next to the definition to disable or enable it. A green check mark indicates that the definition is enabled. • Action column: Click to edit, duplicate, or delete a definition, or to move it up or down in the listing order. Filtering Cell-Level Security Definitions You can filter the list of cell-level security definitions by certain criteria such as by cube, by restriction, or by date. When you filter, only the definitions that meet the filter criteria are displayed on the Cell-Level Security Definitions page. To filter cell-level security definitions: 1. Click Application, and then click Cell-Level Security. 2. Click to specify filter criteria: • Cubes: View only the definitions in the selected cube or cubes, or select All. • Enabled: View only the definitions that are enabled (Yes), not enabled (No), or select All. • Restriction: View only the definitions that are assigned the Deny Read or Deny Write restriction, or select All. • Modified: View only the definitions that were modified before or after a certain date and time, or the definitions modified within a range of dates or times. Chapter 18 Defining Cell-Level Security 18-22
- 568. Select After, Before, or Between and then click to specify the date and time criteria. • Modified By: View only the definitions modified by selected users. • Effective Assignment: View only the definitions that effect the selected users or groups. 3. Click More to further refine the filter criteria: • Dimensions • Anchor Dimensions • Anchor Dimension: Apply to Selected Members Only: Choose Yes, No, or All. • Additional Dimensions Required: Choose Yes, No, or All. 4. Click Apply. Importing and Exporting Cell-Level Security Definitions About Importing and Exporting Cell-Level Security Definitions You can export the filtered list of cell-level security definitions from the listing page to a location on your local computer, or you can export them to the server. If no filter is defined on the listing page, then all cell-level security definitions are exported. Use the Import action to import cell-level security definitions into the application from a location on your local computer or import them from the server. When you perform an import, the system tests the import file for anything that might break a definition; for example, if a cube is missing, or if an anchor dimension doesn't exist, or if a subrule is not found, errors are logged in the error file. Import jobs will only complete successfully if the import file has no errors. Depending on the export or import location you choose, the application definitions are exported or imported in either an Excel file format (XLSX) or a zip file format. Cell-Level Security Import File The Excel import file must have two sheets with the following names for the first and second sheets: 1. Rules 2. Sub Rules The Rules sheet has the following column headings: • Name • Position • Description • Enabled • Valid Cubes - This column can contain either All or a list of comma-separate names of cubes, such as Plan1, Plan2 • Anchor Dim Name • Anchor Dimension Apply to Unselected Members Chapter 18 Defining Cell-Level Security 18-23
- 569. • Dim1 • Dim1 Required • Dim2 • Dim2 Required • Dim X • Dim X Required The Sub Rules sheet must have the following column headings: • Name - This column must contain the name of the Rule from the first sheet • Users • User Groups • Restriction This column can contain Deny Read or Deny Write • Anchor Members • Anchor Exclusion • Anchor Exclusion All • Dim1 Members • Dim1 Exclusion • Dim1 Exclusion All • Dim2 Members • Dim2 Exclusion • Dim X Members • Dim X Exclusion • Dim X Exclusion All Exporting and Importing Cell-Level Security Definitions To export and import cell-level security definitions: 1. Click Application, and then click Cell-Level Security. 2. Apply filters to the listing, as needed. See Filtering Cell-Level Security Definitions. 3. To export, click Actions, then Export, and then select the target location for the export file: • Local: Saves the export file to a location on your local computer. If you choose this option, click Export, and then specify where to save the XLSX export file. • Outbox: Runs a job that saves the export file in a zip format to the server which you can download now or use to schedule an export job later. If you choose this option, click Save and Run Job. To download the export file from the Outbox: a. Click Application, and then click Jobs. b. Under Recent Activity click the Export CLS job. Chapter 18 Defining Cell-Level Security 18-24
- 570. c. On the Job Details page, click to select a download location for the cell-level security export file. You can also download the export file from the Inbox/Outbox Explorer for your business process. 4. If editing the export file in Excel, note that the Excel file has two sheets: Rules and Sub Rules. 5. To import, click Actions, then Import, and then select the location of the import source file: • Local: Loads the import file from a location on your computer. For Source File, click Browse to select the import file on your computer, and then click Import. • Inbox: Runs a job that loads the import file from the server. The import file must be in a zip file format. Enter the name of the file in Source File, click Save and Run Job, and then specify the Name and Error File on the Save as Job dialog. The error file provides information about the definitions that were not imported. You can download the error file from the Inbox/Outbox Explorer for your business process. Testing Cell-Level Security After defining cell-level security and enabling it, you can test it to see what an effected user would see when they view a form. Testing ensures that users are seeing only the cell values they are allowed to see and nobody is seeing more than they should. To test a definition, you must enable it. To test cell-level security: 1. Click Application, and then click Cell-Level Security. 2. Enable the definition you want to test. 3. Click Test, and then select the form that you want to test. 4. In the Select or Enter a User Name text box, specify a user name or click to select a user, and then click OK. Note: You can test only one user at a time. The form displays the user access to each cell as Read, Write, or None. Reordering the Cell-Level Security Definitions List Cell-level security definitions are evaluated in the order they appear on the definitions list; for example, the application evaluates the first cell-level security definition in the list, then the second definition, and so on. To change the position of a cell-level security definition in the list: 1. Click Application, and then click Cell-Level Security. 2. To the right of the cell-level security definition, click . 3. Select Move Up or Move Down. Chapter 18 Defining Cell-Level Security 18-25
- 571. Tip: You can also drag cell-level security definitions to move them up and down in the list. Chapter 18 Defining Cell-Level Security 18-26
- 572. 19 Defining Data Maps and Creating File-Based Integrations Data Integration is the mechanism by which integration processes are performed in Oracle Enterprise Performance Management Cloud. You can define file-based and direct integration sources, create mapping rules to translate source data in the required target format, and execute and manage the periodic data loading process. To learn how to create a file-based integration see Creating File-Based Integrations in Administering Data Integration for Oracle Enterprise Performance Management Cloud. Define data maps to move data, comments, attachments, and supporting detail from source cubes and Smart Lists to target reporting cubes to consolidate data. To learn how to define data maps, see Defining Data Maps in Administering Data Integration for Oracle Enterprise Performance Management Cloud. 19-1
- 573. 20 Managing Jobs Schedule jobs to perform common administrative tasks and lighten your workload. You can start jobs right away or schedule jobs to run later at intervals. Related Topics • How Jobs Save You Time • Viewing Pending Jobs and Recent Activity • Scheduling Jobs • Editing and Canceling Jobs • Duplicating Jobs • Canceling Rules Jobs and Ruleset Jobs • Downloading Export Files From Your Outbox How Jobs Save You Time Jobs are actions such as exporting data or refreshing the database, which you can start right away or schedule to run later at intervals. To lighten your workload, define jobs to perform common administrative tasks such as: • Importing and exporting metadata and data • Refreshing the database • Mapping cubes Viewing Pending Jobs and Recent Activity To view the job listings in the Jobs console: 1. Click Application, and then click Jobs. 2. Perform any task: • To filter jobs and activity by criteria such as date or job type, click • To search for job by name, enter text in the Search, and then click . • To view a job's details, click the job. 20-1
- 574. Note: • The application is automatically refreshed during an application upgrade. If any refresh errors occur during an application upgrade, you can view the errors on the Jobs page. These errors are captured in the job called Content Update. • Jobs older than 90 days are purged. Scheduling Jobs To schedule jobs: 1. Click Application, then Jobs, and then click Schedule Jobs. 2. Specify the following: • The type of job you're creating. For a list of jobs and descriptions, see Job Types. • When to run the job. You can schedule a job to run now or to run later. If scheduling the job to run later, see Scheduling Jobs to Run Later. 3. Click Next. 4. Select a job from the job list. Depending on the job type, there may be additional options and considerations. See Job Types. Note: • You can run up to five import or export jobs at one time. • For export jobs, you can specify a unique output file name for each job. From the job listing page, click next to the selected job and specify the output file name with a zip extension. The unique file name you specify will override the default export file name when the job runs. • To prevent automatic backup from failure due to scheduled jobs, EPM Cloud disallows certain scheduled jobs to start while the daily maintenance process is running. If the system prevents a job from starting, the reason will be stated in the Job Details. If you've enabled email notifications for the Job Console, you'll receive an email notification when a job does not start. If you have a job that is scheduled to start during the daily maintenance process, it is recommended that you reschedule your job to start outside of the daily maintenance window. See Setting the Daily Maintenance Process Start Time. 5. Click Next. 6. Review your choices. If satisfactory, click Finish. To edit or cancel a job after scheduling it, see Editing and Canceling Jobs. Chapter 20 Scheduling Jobs 20-2
- 575. Job Types Table 20-1 Job Types Job Type Description Rules Runs a rule that you select. Note the following: • You can filter the rules list by cube and by rule type. • You must click the check mark next to the rule you want to run before you can proceed. • For rules jobs with runtime prompts, clicking the check mark next to a rule will display the runtime prompt parameters. Set the runtime prompt values with which to run the rule in the job scheduler, and then click OK. • Hidden runtime prompts will pick up the default values that were set at design time in Calculation Manager. See About Rules. Import Data * Performs a data import that was saved as a job. See Importing Data. Import Exchange Rates Imports exchange rates for a simplified multicurrency application. See Importing Exchange Rates for a Simplified Multicurrency Application. Import Metadata * Performs a metadata import that was saved as a job. See Importing Metadata. Import Cell-Level Security Definition Imports a cell-level security definition that was saved as a job. See Importing and Exporting Cell-Level Security Definitions. Import Valid Intersections Imports valid intersections that were saved as a job. See Importing and Exporting Intersections. Export Data * Performs a data export that was saved as a job. You can specify a unique output file name for each Export Data job. From the job list, click next to the selected job and specify the Output File Name using a zip extension. You can verify the export file name on the Review page. The unique file name will override the default export file name when the job runs. See Exporting Data. Note: The driver/column dimension in the Export Data job definition needs to be dense. Chapter 20 Scheduling Jobs 20-3
- 576. Table 20-1 (Cont.) Job Types Job Type Description Export Metadata * Performs a metadata export that was saved as a job. You can specify a unique output file name for each Export Metadata job. From the job list, click next to the selected job and specify the Output File Name using a zip extension. You can verify the export file name on the Review page. The unique file name will override the default export file name when the job runs. See Exporting Metadata. Export Cell-Level Security Definitions Exports a cell-level security definition that was saved as a job. See Importing and Exporting Cell-Level Security Definitions. Export Valid Intersections Exports valid intersections that were saved as a job. See Importing and Exporting Intersections. Refresh Database * Refreshes the application database. See Creating and Refreshing Application Databases. Data Map Performs a data mapping operation. See Defining Data Maps in Administering Data Integration for Oracle Enterprise Performance Management Cloud. Invalid Intersection Reports Runs a report that shows where data exists at invalid intersections. See Working With Invalid Intersection Reports. Clear Cube * Performs a cube clearing operation. See Creating Clear Cube Jobs. Restructure Cube * Performs a full restructure of a block storage cube to eliminate or reduce fragmentation. This will also remove empty blocks. Running this job won't push any changes from the business process to Essbase. See Improving Cube Performance. Compact Outline * Compacts the outline file of an aggregate storage cube. Compaction helps keep the outline file at an optimal size. Compacting the outline doesn't clear the data. Running this job won't push any changes from the business process to Essbase. See Improving Cube Performance. Merge Data Slices * Merges incremental data slices of an aggregate storage cube. Fewer slices improve a cube’s performance. You can merge all incremental data slices into the main database slice or merge all incremental data slices into a single data slice without changing the main database slice. You can optionally remove cells that have a value of zero. See Improving Cube Performance. Optimize Aggregation * Generates optimized views based on collected query tracking information in an aggregate storage cube. For additional option descriptions, see Improving Cube Performance. Administration Mode Changes the login level for a business process. If you select Administrators, all non-administrative users will be logged off from the application after job execution. To restore access to an application for all users, select All users. See What Application and System Settings Can I Specify? Chapter 20 Scheduling Jobs 20-4
- 577. Table 20-1 (Cont.) Job Types Job Type Description Execute Bursting Definition Runs a report bursting job If you're using the next-generation Reports reporting solution, the bursting feature enables you to run a single report or book for more than one member of a single dimension for one data source, and publish a PDF output for each member. See "Working with Bursting" in Designing with Reports for Oracle Enterprise Performance Management Cloud. Auto Predict Runs an Auto Predict job definition. When you run the prediction job, historical data for each member in the Auto Predict definition is retrieved and then analyzed using time series forecasting techniques to predict the future performance for these members. Running the prediction as a job is useful when you have large amounts of data to predict or when you want to keep prediction results up-to-date as part of your planning and forecasting cycle. For additional information about Auto Predict job parameters, see Running Auto Predict Predictions. For information about creating Auto Predict prediction definitions, see About Auto Predict. Insights Runs an IPM Insights insight definition. For information about configuring IPM Insights insight definitions, see Configuring IPM Insights. *The system will prevent this job from starting if it's scheduled to start while the daily maintenance process is running. Oracle recommends that you reschedule this job to start outside of the daily maintenance window. See Setting the Daily Maintenance Process Start Time. Scheduling Jobs to Run Later Table 20-2 Scheduling Jobs Options Option Description Schedule starting from Select the starting date and time, including the time zone. Name Specify a name for the scheduled job; for example, MyDailyCubeRefresh. The name you specify is displayed along with the job name (which you'll choose on the next screen); for example, MyDailyCubeRefresh : Refresh Database. Chapter 20 Scheduling Jobs 20-5
- 578. Table 20-2 (Cont.) Scheduling Jobs Options Option Description Recurrence Pattern Specify the frequency with which to run the job: • Hourly: Hourly jobs run according to a timetable which is based on the values you set in the Schedule starting from and Hour fields. The schedule for Hourly jobs restarts each day during the midnight hour and the recurring job starts at the first hour, second hour, third hour (and so on up to 12 hours) after the midnight hour, depending on the value you select in the Hour field. So for example, if you specify a value of 5 in the Hour field, the possible times the job could start are during the 12:00 AM hour, the 5:00 AM hour, the 10:00 AM hour, the 3:00 PM hour, and the 8:00 PM hour each day. If the scheduled start time for a job is 12:48 PM and you set the Hourly recurrence for 5 Hours, the job will start at 3:48 PM, which is the first scheduled time available after 12:48 PM in which to start a 5-hour recurring job. Then the job will run again at 8:48 PM, 12:48 AM, 5:48 AM, and 10:48 AM. For the default recurrence of 1 Hour, the job will start running at the start time you specify and continue to run each hour until the ending date and time; for example, if the scheduled start time for a job is 12:48, the job will run at 12:48, 1:48, 2:48, 3:48 and so on. For a schedule of times based on the values selected in the Hour field, see Scheduling Hourly Jobs. • By Minute: Set the Frequency for 15 or 30 minutes. The job will start running in 15 or 30 minutes and continue to run at the selected frequency until the ending date and time; for example, if you set the job to run every 15 minutes and the starting time is 3:15, the job will start to run at 3:30, then 3:45, and so on. Jobs cannot be scheduled to run in increments smaller than 15 minutes. • Run Once: The job will run once at the starting date and time. • Yearly: The job will run at the starting date and time and continue to run each year thereafter until the end date. • Monthly: The job will run at the starting date and time and continue to run each month thereafter until the end date. Chapter 20 Scheduling Jobs 20-6
- 579. Table 20-2 (Cont.) Scheduling Jobs Options Option Description • Weekly: The job will run at the starting date and time and continue to run each week until the end date. • Daily: The job will run at the starting date and time and continue to run each day until the end date. End Date If the job is recurring, select an ending date and time. Scheduling Hourly Jobs Hourly jobs run according to a timetable which is based on the values you set in the Schedule starting from and Hour fields. The schedule for Hourly jobs restarts each day during the midnight hour and the recurring job starts at the first hour, second hour, third hour (and so on up to 12 hours) after the midnight hour, depending on the value you select in the Hour field. For example, if you specify a value of 5 in the Hour field, the hours during which the job will run each day are 12 AM, 5 AM, 10 AM, 3 PM, and 8 PM. The start time indicates the hour and minute when the system should start honoring the schedule, and the end time indicates when the system should stop. So if the start time is 12:48 PM on 11/18, then that means 12:48 AM, 5:48 AM, and 10:48 AM have already occurred on the current day (11/18) and the next available timeslot is 3:48 PM, which is when the scheduled job will run for the first time. After that it will run at 8:48 PM on 11/18. However on 11/19 it starts over again and will run at 12:48 AM, 5:48 AM, 10:48 AM, and so on until the system reaches the specified end time (in this case, 12:48 PM on 11/19). Note: When a job spans two days, the job runs during the midnight hour the next day and re-sets the recurrence pattern. To schedule hourly jobs, see Scheduling Jobs. Chapter 20 Scheduling Jobs 20-7
- 580. Table 20-3 Timetable for Hourly Jobs Hourly Recurrence Timetable 1 (default) AM: 12:00, 1:00, 2:00, 3:00, 4:00, 5:00, 6:00, 7:00, 8:00, 9:00, 10:00, 11:00 PM: 12:00, 1:00, 2:00, 3:00, 4:00, 5:00, 6:00, 7:00, 8:00, 9:00, 10:00, 11:00 For example, if the scheduled start time is 12:48 PM and you set the hourly recurrence for 1 hour, the job will run for the first time at 12:48 PM, and then again at 1:48 PM, 2:48 PM, 3:48 PM, and so on. 2 AM: 12:00, 2:00, 4:00, 6:00, 8:00, 10:00 PM: 12:00, 2:00, 4:00, 6:00, 8:00, 10:00 For example, if the scheduled start time is 12:48 PM and you set the hourly recurrence for 2 hours, the job will run for the first time at 12:48 PM, and then again at 2:48 PM, 4:48 PM, 6:48 PM, and so on. 3 AM: 12:00, 3:00, 6:00, 9:00 PM: 12:00, 3:00, 6:00, 9:00 For example, if the scheduled start time is 12:48 PM and you set the hourly recurrence for 3 hours, the job will run for the first time at 12:48 PM, and then again at 3:48 PM, 6:48 PM, 9:48 PM, 12:48 AM, 3:48 AM, and so on. 4 AM: 12:00, 4:00, 8:00 PM: 12:00, 4:00, 8:00 For example, if the scheduled start time is 12:48 PM and you set the hourly recurrence for 4 hours, the job will run for the first time at 12:48 PM, and then again at 4:48 PM, 8:48 PM, 12:48 AM, 4:48 AM, and so on. 5 AM: 12:00, 5:00, 10:00 PM: 3:00, 8:00 For example, if the scheduled start time is 12:48 PM and you set the hourly recurrence for 5 hours, the job will run for the first time at 3:48 PM, and then again at 8:48 PM, 12:48 AM, 5:48 AM, 10:48 AM, and so on. 6 AM: 12:00, 6:00 PM: 12:00, 6:00 For example, if the scheduled start time is 12:48 PM and you set the hourly recurrence for 6 hours, the job will run for the first time at 12:48 PM, and then again at 6:48 PM, 12:48 AM, 6:48 AM, and so on. Chapter 20 Scheduling Jobs 20-8
- 581. Table 20-3 (Cont.) Timetable for Hourly Jobs Hourly Recurrence Timetable 7 AM: 12:00, 7:00 PM: 2:00, 9:00 For example, if the scheduled start time is 12:48 PM and you set the hourly recurrence for 7 hours, the job will run for the first time at 2:48 PM, and then again at 9:48 PM, 12:48 AM, 7:48 AM, and so on. 8 AM: 12:00, 8:00 PM: 4:00 For example, if the scheduled start time is 12:48 PM and you set the hourly recurrence for 8 hours, the job will run for the first time at 4:48 PM, and then again at 12:48 AM, 8:48 AM, and so on. 9 AM: 12:00, 9:00 PM: 6:00 For example, if the scheduled start time is 12:48 PM and you set the hourly recurrence for 9 hours, the job will run for the first time at 6:48 PM, and then again at 12:48 AM, 9:48 AM, 6:48 PM, and so on. 10 AM: 12:00, 10:00 PM: 8:00 For example, if the scheduled start time is 12:48 PM and you set the hourly recurrence for 10 hours, the job will run for the first time at 8:48 PM, and then again at 12:48 AM, 10:48 AM, 8:48 PM, and so on. 11 AM: 12:00, 11:00 PM: 10:00 For example, if the scheduled start time is 12:48 PM and you set the hourly recurrence for 11 hours, the job will run for the first time at 10:48 PM, and then again at 12:48 AM, 11:48 AM, 10:48 PM, and so on. 12 AM: 12:00 PM: 12:00 For example, if the scheduled start time is 12:48 PM and you set the hourly recurrence for 12 hours, the job will run for the first time at 12:48 PM, and then again at 12:48 AM, and so on. Editing and Canceling Jobs You can edit the schedule for pending jobs, and delete pending and complete jobs. You can't modify or delete jobs that are processing. Chapter 20 Editing and Canceling Jobs 20-9
- 582. To edit or delete jobs: 1. Click Application, and then click Jobs. 2. To change when a job runs, click , then Edit and modify the schedule. Note: When changing the frequency of a job, the job will not run at the new frequency until the next time it runs at the previous frequency; for example, if the job is set up to recur daily and you change the frequency to hourly, the job won't start running at the new hourly frequency until after the scheduled daily job runs the next day. If you want the job to begin running at the new frequency sooner, Oracle recommends that you delete the scheduled job and create a new one. 3. To delete jobs, select them, click , and then Delete. Duplicating Jobs Use the Save As option to create a duplicate of an existing job, and then update it to avoid starting over making selections each time you create a new job. Save As is supported for the following job types: • Export Data • Import Data • Export Metadata • Import Metadata • Refresh Database • Clear Cube • Import Exchange Rates Note: For descriptions of the job types, see Job Types. To duplicate a job: 1. Click Application, and then click Overview. 2. Click Actions, and then select one of the following actions: • Export Data • Import Data • Export Metadata • Import Metadata • Refresh Database Chapter 20 Duplicating Jobs 20-10
- 583. • Clear Cube • Import Exchange Rates 3. On the listing page, click in the Actions column next to the job that you want to duplicate, and then select Save As. 4. Enter a name for the new job, and then click OK. After the duplicate job is created, you can then open the job and update it. The error file for the duplicate job will automatically use the new job name as a prefix. Canceling Rules Jobs and Ruleset Jobs You can cancel ruleset or rule jobs that are processing and display in Recent Activity. To cancel these jobs, click Application, then click Jobs. To cancel a rules job, click beside the job, then , and then Cancel. To cancel a ruleset, click , then on Job Details, and then Cancel. Downloading Export Files From Your Outbox After running a metadata or data export job, you can download the export file from the Outbox. To download files: 1. Click Application, and then click Jobs. 2. Under Recent Activity, click the job. 3. At the top of Job Details, click the export file option to select a download location. Chapter 20 Canceling Rules Jobs and Ruleset Jobs 20-11
- 584. 21 Auditing Tasks and Data Related Topics • Auditing Overview • Enabling Audit Tracking • Viewing Audit Details Auditing Overview Use the Audit feature to view data tasks performed by users. You can filter audited tasks by audit type (example, Data, Approvals, or Clear Cell Details), date range (for example, Yesterday or Last 60 Days), and user name. You must be a Service Administrator to enable audit tracking, and to view and export audit information. These are the types of user activities the system can log in the task audit: Table 21-1 Tasks That Can be Audited Audit Types Tracked Changes Dimension Administration • Dimension hierarchy: Adding a member or dimension; moving, deleting, and changing properties; renaming a member and dimension • Performance settings: Resetting a dimension's dense or sparse setting, changing the order of dimensions • Currencies: Adding or deleting currencies, setting a triangulation or reporting currency Alias Table Administration Changes to alias tables: Creating, copying, renaming, deleting, and clearing Data • Cell values • Supporting detail • Account annotations • Cell-level documents Launch Business Rules Updates from calculation scripts and business rules (including runtime prompts) Form Definition Forms: Creating, moving, deleting forms (The audit record doesn't record how the design changed.) Form Folder Administration Folders: Created, moved, and deleted Approvals Approvals: Approval unit owners and status 21-1
- 585. Table 21-1 (Cont.) Tasks That Can be Audited Audit Types Tracked Changes Copy Version Versions copied, including supporting detail, cell text, cell attachments, and data without any details. The audit record doesn't record details (such as data and supporting detail) of the copied version. Security Access permissions to dimension members, forms, form folders, business rules, and task lists Users Administration Users added, changed, and deleted Groups Administration Groups added, changed, and deleted; users added and removed Tasklist Task lists: created, updated, saved, moved, and deleted Copy Data Users' selections for Static Dimensions, Source Dimension, and Destination Dimension, including supporting detail, cell text, cell attachments, and data without any details Clear Cell Details Users' selections for clearing supporting details, comments, and attachments Variables Variables (substitution variables and user variables): Added, changed, and deleted The Audit page displays the following information: • Audit (task) • Source • Action • User • Name • Date • Details • Property • Old Value • New Value All columns can be sorted in ascending or descending order. Enabling Audit Tracking Audit tracking isn't enabled by default. Service Administrators must enable auditing so data changes can be tracked. To enable auditing: 1. On the Home page, click Tools, and then click Audit. 2. From the Audit page, click Enable Auditing. Chapter 21 Enabling Audit Tracking 21-2
- 586. 3. From the Enable Auditing page, select an audit task or tasks, and then click Save and Close. Viewing Audit Details You can view and export up to 180 days of audit details in the business process interface. To view audit details: 1. On the Home page, click Tools, and then click Audit. If auditing is enabled, by default the Audit page displays the audit records for Data tasks for the Last 7 Days. To enable auditing, see Enabling Audit Tracking. 2. To filter, click , and select filter criteria: • Audit Types: Select one or more, or All. For a list of audit types and descriptions, see Auditing Overview. • Date Range: Select Today, Yesterday, Last 7 Days, Last 30 Days, Last 60 Days, or Last 180 Days. Note: – You can't select a date range prior to 180 days from today. The date range you select must occur between today and 180 days prior to today (including today). – The business process retains up to 365 days of audit details from the current system date. To export more than 180 days of audit details, you can use the EPM Automate exportAppAudit command or the REST API Export Audit job. See Working with EPM Automate for Oracle Enterprise Performance Management Cloud or REST API for Oracle Enterprise Performance Management Cloud . • User Name: Enter a user name or click to search for the user. 3. When you're done selecting filter criteria, click Apply. The grid displays the first 200 records from the audit table that match the filter criteria. You can view a legend at the bottom of the table if the filter criteria has more than 200 records in it. 4. To export the audit information to a Microsoft Excel spreadsheet, click Export, and follow the download instructions. When you select the Export option, the system exports all of the records matching the filter criteria to an xlsx file (format for Microsoft Excel versions 2007 and later). Chapter 21 Viewing Audit Details 21-3
- 587. Note: If data auditing is enabled, users can see what data has changed by selecting Actions, and then Change History. Chapter 21 Viewing Audit Details 21-4
- 588. 22 Managing Data Validation Related Topics • Creating and Updating Data Validation Rules • Formatting Cells and Setting the Promotional Path • Viewing Data Validation Rules • Order of Evaluation and Execution for Data Validation Rules • Conditions Supported by the Rule Builder • Data Validation Conditional Operators • Data Validation Rule Scenarios Creating and Updating Data Validation Rules To implement business policies and practices, you can build data validation rules that are checked when conditions are met in forms. Validation messages can be generated if entered data violates validation rules. You can also build limits on submitted approval unit data using validation rules, and designate a reviewer, owner, or notifier to review data that meets some condition. For example, data validation can ensure that a department’s capital expenses adhere to company policies by preventing users from submitting budgets that contain capital expenditures that fall outside the company’s guidelines. Sample scenarios that can be addressed using data validation rules are described in Data Validation Rule Scenarios. Defining data validation rules involves these main tasks: • Identifying the data cells or location that you want to display with validation messages or in different colors when conditions are met. • Identifying the cells that need to participate during rule evaluation, and defining the rule accordingly. • Creating the data validation rule at the location identified, as described in this topic. To create and update validation rules: 1. On the Home page, click Navigator , and then under Create and Manage, click Forms. 2. Create or edit a form, and then on the Fo