Oracle EDMCS Hands On Training Guide

Enterprise Data
Management Cloud
Service (EDMCS)
Training Guide
Release 19.05
July 19, 2019
1
Table of Contents
Scenario 1: Register Applications................................................................................................... 5
Exercise 1 Register Financials Cloud General Ledger Application ............................................................6

Exercise 2 Define Connections for Financials Cloud Application ..............................................................8
Exercise 3 Configure Financials Setup .................................................................................................................9
Exercise 4 Add Chart of Accounts Segments ................................................................................................... 11
Exercise 5 Add Trees for Segments .................................................................................................................... 12
Exercise 6 Complete Financials Cloud General Ledger Registration ..................................................... 13
Exercise 7 Register Enterprise Planning and Budgeting Application ................................................... 15
Exercise 8 Define Connections for EPBCS Application ................................................................................ 16
Exercise 9 Specify Cubes and Application Settings ...................................................................................... 18
Exercise 10 Add Dimensions to EPBCS Application ........................................................................................ 20
Exercise 11 Complete EPBCS Application Registration ................................................................................. 22
Exercise 12 Register Custom Application........................................................................................................... 23
Exercise 13 Add Dimensions and Node Types .................................................................................................. 25
Exercise 14 Define Properties for Node Types ................................................................................................. 27
Exercise 15 Define Import and Export Settings ............................................................................................... 31
Exercise 16 Complete Custom Application Registration .............................................................................. 32
Scenario 2: Understand Information Model ............................................................................. 34
Exercise 1 Manage Nodes and Properties Using Node Types ................................................................... 35

Exercise 2 Manage Hierarchies using Hierarchy Sets ................................................................................. 37
Exercise 3 Group and Filter Nodes Using Node Sets .................................................................................... 39
Exercise 4 View Related Objects in a Data Chain .......................................................................................... 41
Exercise 5 Inspect Properties............................................................................................................................... 43
Scenario 3: Import Enterprise Data From Applications ....................................................... 46
Exercise 1 Import Dimensions From Files....................................................................................................... 47

Exercise 2 Import Dimensions From Connections ....................................................................................... 50
Exercise 3 Review Imported Data in Default Views ..................................................................................... 56
Scenario 4: Work with Enterprise Data in Views .................................................................... 58
Exercise 1 Open Views ............................................................................................................................................ 59

Exercise 2 Browse Hierarchy Viewpoints ........................................................................................................ 60
Exercise 3 Browse List Viewpoints..................................................................................................................... 61
2
Exercise 4 Search for Nodes .................................................................................................................................. 62
Exercise 5 Inspect Viewpoints ............................................................................................................................. 63
Exercise 6 Display Properties as Columns ...................................................................................................... 65
Exercise 7 Download Viewpoints ........................................................................................................................ 67
Scenario 5: Change Enterprise Data With Requests .............................................................. 69
Exercise 1 Create Requests ................................................................................................................................... 70

Exercise 2 Make Changes to Lists ........................................................................................................................ 70
Exercise 3 Make Changes to Hierarchies ......................................................................................................... 73
Exercise 4 Load Changes From Spreadsheets ................................................................................................ 78
Exercise 5 Validate Changes and Resolve Issues ........................................................................................... 81
Exercise 6 Add Comments ..................................................................................................................................... 83
Exercise 7 View and Add Attachments .............................................................................................................. 84
Exercise 8 Submit Requests .................................................................................................................................. 86
Exercise 9 View Request Activity ........................................................................................................................ 87
Scenario 6: Create Alternate Views and Viewpoints .............................................................. 91
Exercise 1 Create Views .......................................................................................................................................... 92

Exercise 2 Create Viewpoints ............................................................................................................................... 93
Exercise 3 Create Node Types .............................................................................................................................. 97
Exercise 4 Create Hierarchy Sets ..................................................................................................................... 100
Exercise 5 Create Node Sets ............................................................................................................................... 102
Exercise 6 Copy Viewpoints ............................................................................................................................... 107
Exercise 7 Bind Viewpoints to Dimensions .................................................................................................. 109
Exercise 8 Archive Viewpoints.......................................................................................................................... 112
Scenario 7: Share Enterprise Data Across Applications .................................................... 115
Exercise 1 Create Node Type Converters ...................................................................................................... 116

Exercise 2 Display Viewpoints Side By Side ................................................................................................. 118
Exercise 3 Compare Viewpoints ....................................................................................................................... 121
Exercise 4 Locate Nodes Across Viewpoints ................................................................................................ 123
Exercise 5 Add Nodes Across Viewpoints ..................................................................................................... 124
Exercise 6 Align Nodes and Properties Between Viewpoints ................................................................ 126
Exercise 7 Compare Relationships and Properties ................................................................................... 127
Exercise 8 Resolve Property Differences Between Viewpoints ............................................................ 130
Scenario 8: Map Enterprise Data Across Applications ....................................................... 133
3
Table of Contents
Exercise 1 Create Source Node Types............................................................................................................. 134

Exercise 2 Create Mapping Hierarchy Sets ................................................................................................... 135
Exercise 3 Create Mapping Node Sets ............................................................................................................. 137
Exercise 4 Map Nodes Across Applications Using Requests .................................................................. 138
Exercise 5 Create Mapping Keys for Dimensions ....................................................................................... 143
Scenario 9: Synchronize Enterprise Data Across Applications ....................................... 147
Exercise 1 Create Subscriptions For Target Viewpoints ......................................................................... 148

Exercise 2 Submit Request For Source Viewpoints ................................................................................... 151
Exercise 3 Subscription Request Using Auto-Submit ............................................................................... 154
Exercise 4 Subscription Request Assigned to User ................................................................................... 158
Scenario 10: Govern Enterprise Data Across Applications .............................................. 163
Exercise 1 Grant Permissions to Users .......................................................................................................... 164

Exercise 2 Enable Approval Policies ............................................................................................................... 165
Exercise 3 Create and Assign Request ............................................................................................................ 168
Exercise 4 Submit Request for Approval ....................................................................................................... 172
Exercise 5 Approve Requests ............................................................................................................................ 180
Exercise 6 Review Request Approvals and History................................................................................... 185
Scenario 11: Export Enterprise Data To Applications ....................................................... 187
Exercise 1 Validate Viewpoints Before Export ........................................................................................... 188

Exercise 2 Export Dimensions to Files ........................................................................................................... 190
Exercise 3 Export Dimensions to Connections............................................................................................ 192
Exercise 4 Export Mappings ............................................................................................................................... 197
Scenario 12: Control User Access .............................................................................................. 202
Exercise 1 Provision Users and Groups with Roles ................................................................................... 203

Exercise 2 Assign Permissions to Applications .......................................................................................... 205
Exercise 3 Assign Permissions to Views ........................................................................................................ 206
Scenario 13: Migration and Daily Maintenance ................................................................... 209
Exercise 1 Export Snapshots .............................................................................................................................. 210

Exercise 2 Import Snapshots ............................................................................................................................. 213
Scenario 14: Automate Tasks...................................................................................................... 215
Exercise 1 Download and Install EPM Automate ....................................................................................... 216

Exercise 2 Export and Import Snapshot using EPM Automate ............................................................. 217
4
Scenario 1: Register Applications

This scenario demonstrates how to register external business applications in
Oracle Enterprise Data Management Cloud Service. In this scenario, you will
register an Oracle Financials Cloud General Ledger application, an Oracle
Enterprise Planning and Budgeting Cloud application, and a Custom application.
5
Exercise 1 Register Financials Cloud General Ledger Application

1) Sign in to Enterprise Data Management Cloud Service as user “admin1” with a password of
“epmEDM1!”.
2) From the Home page, click the “Applications” icon.
3) The list of registered applications is displayed.
6
1) Click the “Register” button to register a new application.
2) The list of available application types is displayed. Select “Financials Cloud General Ledger”.
3) Enter a Name and Description for the application. Click “Next”.
7
End of Exercise
Exercise 2 Define Connections for Financials Cloud Application

1) Click “Add” to define a connection to a live Financials Cloud General Ledger application.
2) Define the parameters of the new connection.
 Name: Financials Cloud
 Instance Location: https://fincloudgl-uscompany-fcgl.US11.oraclecloud.com
 Username: administrator
 Password: oracle
8
3) Click “Next” to save the connection. Click “Next” again to proceed.
4) Click “Create” to create a draft Financials Cloud General Ledger application.
End of Exercise
Exercise 3 Configure Financials Setup

1) The Financial Setup screen is displayed to continue application registration.
9
2) Specify the Active Languages for the General Ledger application (enter Tab between each value).
 English
 German
 Japanese
3) Specify the Base Language for the General Ledger application.
 English
4) Use the default settings for the other General Ledger application options. Click “Next”.
 Allow Multiple Active Tree Versions: True (checked)
 Allow Multiple Root Nodes: True (checked)
 Allow Duplicate Nodes: True (checked)
 Max Depth: -1 (no limit)
10
End of Exercise
Exercise 4 Add Chart of Accounts Segments

1) On the Add Segments screen, click the Add button to register a chart of accounts segment.
2) Enter information for the new chart of accounts segment. Click Next to continue.
 Value Set Code
 Corporate Acount
 Value Set Description
 Account segment in Corporate chart of accounts
 Natural Account Segment: True (checked)
 Value Type (for Name of account): Numeric
 Max Length (for Name of account): 5
11
3) Define a minimum and maximum numeric value for Corporate Account segment values. Click
Next to continue.
 Minimum: 10000
 Maximum: 99999
End of Exercise
Exercise 5 Add Trees for Segments

1) Click “Add” on the Add Trees screen to register a tree for the Corporate Account segment.
2) Enter information for the Corporate Account segment tree. Click Next to continue.
 Tree Code
 All Corporate Accounts
12
 Tree Version Name
 V1
 Version Start Date: <beginning of current month>
 Version End Date: <end of current month>
3) The tree and tree version are registered for the Corporate Account segment. Click Next.
4) The Corporate Account segment is registered for the General Ledger application. Click Next.
Exercise 6 Complete Financials Cloud General Ledger Registration

1) On the Financial Categories screen, you can add or remove financial categories to match the
configuration of the Financials Cloud application. Click Next to continue.
13
2) Review the registration summary for the Financials Cloud General Ledger application.
3) Click “Apply” to complete registration of the General Ledger application.
4) A new Financials Cloud General Ledger application is activated and displayed on the Applications
page. Data chain objects have also been created for the dimensions you added to the registered
application.
14
End of Exercise
Exercise 7 Register Enterprise Planning and Budgeting Application

2) The list of available application types is displayed. Select “Enterprise Planning and Budgeting
Cloud”.
15
End of Exercise
Exercise 8 Define Connections for EPBCS Application

4) Click “Add” to add a connection to a live EPBCS application.
16
5) Define the parameters of the new connection.
 Name: EPBCS
 Instance Location: https://planbudget-uscompany-entplan.US11.oraclecloud.com
 Identity Domain: uscompany
 Username: administrator
 Password: oracle
6) Click “Next” to save the connection. Click “Next” again to proceed.
17
7) Click “Create” to create a draft Enterprise Planning and Budgeting Cloud application.
End of Exercise
Exercise 9 Specify Cubes and Application Settings

1) Click “Add” to add a cube to the Enterprise Planning application.
2) Define a Cube Name and Cube Type for the application. Click “Next”.
18
 OEP_FS (for Financial planning)
 BSO
3) The “OEP_FS” cube has been added to the Enterprise Planning application. Click “Next”.
4) Specify application settings for the Enterprise Planning application.
 Aliases (enter Tab between each value)
 English
 German
 Japanese
 Multi-currency: True
 Currencies (enter Tab between each value)
19
 USD
 EUR
 JPY
5) Click “Next” to proceed.
End of Exercise
Exercise 10 Add Dimensions to EPBCS Application

1) Click “Add” to add a dimension to the application.
2) Define a Name and Description for the dimension. Configure the following additional
parameters:
 Dimension Type: Entity
 Allow Shared Nodes: True
 Valid Cubes: OEP_FS
 External Dimension Name: Entity
20
3) Click “Next”. Click “Add” to add an attribute to the dimension.
4) Define an Attribute Name and Attribute Values. Click “Next”.
 Attribute Name: Country
 Attribute Values (enter Tab between each value):
 USA
 Germany
 Japan
21
5) The Country attribute has been added for the Entity dimension. Click “Next”.
6) The Entity dimension has been added to the Enterprise Planning application. Click “Next” to
proceed.
End of Exercise
Exercise 11 Complete EPBCS Application Registration

1) Click the “Apply” button to apply changes made during the registration process.
22
2) A new Enterprise Planning and Budgeting Cloud application is activated and displayed on the
Applications page. Data chain objects have also been created for the dimensions you added to
the registered application.
End of Exercise
Exercise 12 Register Custom Application

2) The list of available application types is displayed. Select “Custom”.
23
4) Click the “Create” button. A new draft application will be created.
24
End of Exercise
Exercise 13 Add Dimensions and Node Types

1) Click “Add” to register a dimension for the new application.
2) Enter details for the new dimension. Click “Next”.
 Dimension Name: Product
 Dimension Type: Hierarchy
 External Dimension Name: Product
 Allow Shared Nodes: True
25
3) Click “Add” to add a new node type to the Product dimension.
4) Enter information for the node type. Click “Next”.
 Node Type Name: Product
 Node Type Description: Product dimension members
 Node Type Qualifier: P_
 Node Type Qualifier Position: Prefix
26
End of Exercise
Exercise 14 Define Properties for Node Types

1) From the Properties screen, you can add new properties or select existing properties for a node
type. The Name property is included by default.
2) Click the “Create” button to create a new property.
3) Select the “Custom.String Template” property template. Define a Name and Description for the
property. Click Next.
 Name: Data Storage
 Description: Data storage in financial consolidation app
27
4) Define the parameters of the new property. For this property, configure the following
parameters:
 Maximum length: 30
 Use Allowed Values List: True
 Include Blank Entry (in list): False
 Enter the following allowed values (enter Tab key in between each value)
o Store
o Dynamic Calc
o Dynamic Calc and Store
o Label Only
o Shared
28
 Default Value: Store
 Inheritance (from a parent in a hierarchy): Positional
 Column Header (for import and export): Data Storage
5) Click Next. The property is added to the Product node type for the Product dimension.
6) Click the “Select” button to select an existing property. Find the “Core.Description” property
and select it. Click OK.
29
7) Define the parameters of the Description property for the Financial Consolidation application.
Enter a Column Header for the Description property. Click Next.
8) The property is added to the node type.
9) Click the “Move Up” arrow on the Core.Description property to order it above the Custom.Data
Storage property.
30
10) Click “Next” to complete the setup of the Product node type. Click “Next” again to proceed.
End of Exercise
Exercise 15 Define Import and Export Settings

1) Based on the configuration of the dimension you have registered, you may need to define
additional settings for import and export purposes.
2) Top nodes in hierarchy viewpoints are identified by a specific value in the Parent column of
import and export files. The default value is blank. To use a different value to indicate a top
node, enter a value for the Top Node Indicator.
31
3) Check the “Use Node Type Column” and “Use Parent Node Type Column” options when a
dimension has multiple node types. These file columns are used to import and export node type
information for nodes and parents.
4) Click “Next” to proceed. The Product dimension has been added to the
Financial Consolidation application.
End of Exercise
Exercise 16 Complete Custom Application Registration

1) Click “Next”. Review the registration summary. Click the “Apply” button to apply changes made
during the registration process.
32
2) A “Financial Consolidation” application is created and displayed on the Applications page.
3) Data chain objects have also been created for the dimensions you added to the registered
application.
End of Exercise
End of Scenario
33
Scenario 2: Understand Information
Model
Scenario 2: Understand Information Model

This scenario demonstrates the data objects in the Oracle Enterprise Data
Management Cloud information model. In this scenario, you will review node
types created by the application registration to manage nodes for each
dimension. Next, you will review hierarchy sets used to manage hierarchies in
application dimensions. You continue by reviewing node sets and viewpoints
used to filter and display nodes for application dimensions. Finally, you will
view related data objects in a data chain and inspect a property.
34
Exercise 1 Manage Nodes and Properties Using Node Types

1) Click the “Node Types” icon at the top of the page.
2) View the node types used by the applications that have been registered. Each node type
manages an independent set of nodes with a specific set of properties.
3) Scroll down and click on the “Product” node type for the “Corporate Planning” application to
inspect its details.
4) A qualifer can be defined for a node type if nodes should be prefixed with text to make their
name unique. In this example, “P_” is used to make “Product” nodes unique in the “Product”
dimension.
35
5) Click the “Properties” tab. View the properties for the “Product” node type.
6) Click “Edit” to edit the properties for the “Entity” node type. Mark the “PLN.Alias:Default”
property as Required. Click “Save” to save the changes.
36
7) Click “Close” to exit the node type inspector.
End of Exercise
Exercise 2 Manage Hierarchies using Hierarchy Sets

1) Click the “Hierarchy Sets” icon at the top of the page.
2) View the hierarchy sets used by the applications that have been registered. Each hierarchy set
manages a set of nodes related into one or more hierarchies.
3) Click on the “ALL CORPORATE ACCOUNTS| V1” hierarchy set for the “Financials Cloud”
application to inspect its details.
37
4) Click the “Definition” tab. View the node types for the Account hierarchy set. Click “Edit” to
modify the hierarchy set.
5) View the “Allow Shared Nodes” as True. This setting allows the same node to exist under
multiple parents in a hierarchy set.
6) Set “Use Custom Order” to True. This setting allows nodes to be sorted under a parent using a
custom order.
38
7) Click “Save” to save changes. Click “Close” to exit the hierarchy set inspector.
End of Exercise
Exercise 3 Group and Filter Nodes Using Node Sets

1) Click the “Node Sets” icon at the top of the page.
2) View the node sets used by the applications that have been registered. Each node set manages
a group of node types and/or top nodes in a hierarchy set.
3) Click on the “Corporate Company” node set for the “Financials Cloud” application to inspect its
details.
39
4) Click the “Definition” tab. View the node types for the Companies list node set.
5) Click “Close” to exit the node set inspector.
6) Click on the “Account” node set for the “Financial Consolidation and Close” application to
inspect its details.
40
7) Click the “Definition” tab. View the node type and top nodes from the Account hierarchy set
used in this node set.
End of Exercise
Exercise 4 View Related Objects in a Data Chain

1) Click the “Data Chain” tab to view related data objects for the selected node set. The Account
node set has one related node type, hierarchy set, and viewpoint.
41
2) Click the “Node Types” icon to view the node types for the node set.
3) Click the “Hierarchy Set” icon to view the hierarchy set for the node set.
4) Click the “Viewpoints” icon to view the viewpoints for the node set.
42
End of Exercise
Exercise 5 Inspect Properties

1) Click the “Properties” icon at the top of the screen.
2) Properties configured for all applications are displayed on the Properties page.
3) Click the Search icon and search for the “Data Storage” property. Multiple properties were
found.
43
4) Click on the “Custom.Data Storage” property to inspect the property.
5) Select the Parameters tab to view the applications using the property. View the property
parameters for the Financial Close application.
44
6) Click the “Close” button to close the property inspector.
End of Exercise
End of Scenario
45
Scenario 3: Import Enterprise Data From
Applications
Scenario 3: Import Enterprise Data From Applications

This scenario demonstrates how to import data from registered applications
into Oracle Enterprise Data Management Cloud Service.
46
Scenario 3: Import Data From Applications
Exercise 1 Import Dimensions From Files

1) Click the “Applications” icon to view the list of applications.
2) From the Actions column, select the “Financial Consolidation and Close” application and choose
the “Import” menu item.
3) Select the “Account” dimension for which to import data.
47
4) In your “Source Files” folder, open the “Accounts.csv” file in a text editor or Excel.
5) View the contents of the file. A column header identifies each column of data. The Name
column identifies the name of the node being imported. For hierarchies, the Parent column
identifies the parent of the node being imported. Other columns match the names of properties
used in the dimension.
6) Choose an Input Source of “File”.
48
7) Click to select a file or drop a file.
8) Click the “Import” button to import data from the file. A status message is displayed once the
import has completed.
9) In the History, view the import status and number of records imported for the dimension.
49
10) Click “Close” to exit the import screen.
End of Exercise
Exercise 2 Import Dimensions From Connections

NOTE: This exercise requires a live Enterprise Planning and Budgeting service to connect to, which
is not availble for this training. It is for reading purposes only. Continue with Exercise 3 after
reading.
1) In a new browser tab, access Enterprise Planning and Budgeting Cloud Service.
2) From the Home page, click “Application” and “Overview”.
3) View the details of the Enterprise Planning and Budgeting application. Select the “Dimensions”
tab.
50
4) The dimensions for the Enterprise Planning and Budgeting application are displayed.
5) Navigate to the Inbox and Outbox Explorer in Enterprise Planning and Budgeting Cloud Service.
6) Choose “Outbox” as the target Location for the export.
51
7) Select the “Entity” dimension to export and use a comma delimited export file format.
8) Click “Save as Job”, enter a job name, and click “Save” to save the dimension export job.
9) The dimension export job has been saved. Click OK and Close.
10) From the Actions menu for the “Entity Export” job, select “Submit” to run the export job. Click
OK.
52
11) From the Actions menu, select the “Inbox/Outbox Explorer”.
12) View the “Entity Export.zip” file in the Outbox.
13) In Enterprise Data Management Cloud Service, click the “Applications” icon to view the list of
applications.
14) Click on the “Corporate Planning” application to inspect it.
53
15) Select the “Connection” tab. Click “Edit”.
16) Modify the “Instance Location” to use your Enterprise Planning and Budgeting Cloud Service
machine name. Click “Save” and “Close”.
17) From the Actions column, select the “Corporate Planning” application and choose the “Import”
menu item.
18) Select the “Entity”dimension.
54
19) Choose an Input Source of “Connection”. Select the “Production” connection from which to
import data for the selected dimension.
20) Select the “Entity Export.zip” file in the Planning Outbox to be imported.
21) Click the “Import” button to import data from the connection.
22) In the History, view the import staus and number of records imported for the dimension.
55
23) Click “Close” to exit the import screen.
End of Exercise
Exercise 3 Review Imported Data in Default Views

1) From the Applications page, select the “Financial Consolidation and Close” application.
2) In the Default View column, click the “Financial Consolidation and Close” view to open it.
3) The default view is opened to display viewpoints for dimensions in the “Financial Consolidation
and Close” application.
56
4) The “Account” viewpoint is displayed to show imported data for the “Account” dimension.
5) Click “Close” to close the view and display the Views page.
End of Exercise
End of Scenario
57
Scenario 4: Work with Enterprise Data
using Views
Scenario 4: Work with Enterprise Data in Views

This scenario demonstrates how views are used to organize, browse, search,
and download data in Oracle Enterprise Data Management Cloud Service.
58
Scenario 4: Work with Enterprise Data Using Views
Exercise 1 Open Views

1) Views for all applications are displayed. A default view exists for each application. Additional
views can be created for different data management scenarios.
2) Click on the name of the “Corporate GL” view to open it. This is a view for the “Financials Cloud”
application.
3) Viewpoints in the view are displayed as tabs.
End of Exercise
59
Exercise 2 Browse Hierarchy Viewpoints

1) View the Account viewpoint which is a hierarchy of nodes of the Account node type.
2) Expand a node to view its child nodes in the hierarchy.
3) Select a node to view the properties of the node in the hierarchy. Node and relationship
properties are displayed.
60
End of Exercise
Exercise 3 Browse List Viewpoints

1) Select the “Line of Business” viewpoint which is a list of nodes of the Entity node type.
2) Select a node to view the properties of the node.
3) Use the Back and Forward buttons to navigate between previously selected nodes.
61
4) Use the pager to navigate through a large list of nodes.
End of Exercise
Exercise 4 Search for Nodes

1) Select the “Cost Center” viewpoint.
2) Click the Search icon and enter search text. Hit Enter to perform the search.
3) A list of nodes which contain the search text are displayed. Click on a node in the search results
to navigate to the node in the viewpoint.
4) Use the breadcrumbs below the hierarchy to navigate to ancestor nodes of the selected node.
62
End of Exercise
Exercise 5 Inspect Viewpoints

1) Select the “Product” viewpoint. From the viewpoint tab menu, select “Inspect” to view the
details of the viewpoint.
2) View the following details for the viewpoint on the General tab.
63
3) Select the “Definition” tab. The list of node type(s) used by the viewpoint are displayed. For
each node type, the Allowed Actions and Displayed Properties are listed.
4) Select the “Properties” tab. Property labels and descriptions are displayed here and can be
customized for the viewpoint if necessary.
64
End of Exercise
Exercise 6 Display Properties as Columns

1) On the Properties tab, click “Edit” to edit the properties for the viewpoint.
2) Check the “As Column” box for the “Summary” and “Level” properties.
3) Click “Save” to save your changes to the viewpoint.
4) Click “Close” to exit the viewpoint inspector.
65
5) Click OK to reload the view to display the selected properties for the viewpoint.
6) Browse the additional properties for nodes in the viewpoint.
7) Click the “Hide Properties” button to hide the property pane for more space to view properties
as columns.
66
End of Exercise
Exercise 7 Download Viewpoints

1) Select the “Product” viewpoint.
2) From the viewpoint tab menu, select “Download” to download the viewpoint to a spreadsheet
for offline use.
3) Open the spreadsheet file that was downloaded in the web browser.
67
4) View the contents of the spreadsheet. The column header row includes Name, Parent, Node
Type, Parent Node Type columns along with columns for each property in the viewpoint.
End of Exercise
End of Scenario
68
Scenario 5: Change Enterprise Data With
Requests
Scenario 5: Change Enterprise Data With Requests

This scenario demonstrates how requests are used to make changes to data in
Oracle Enterprise Data Management Cloud Service.
69
Exercise 1 Create Requests

1) Click the “New Request” button to create a new request.
2) The Requests pane expands to display the contents of a new draft request.
3) Enter a Title and Description for the request.
End of Exercise
Exercise 2 Make Changes to Lists

1) Click on the “Line of Business” viewpoint tab.
70
2) Click the Add icon above the list of “Line of Business” nodes.
3) A new “Line of Business” node is added to the list. Define a Name and Description for the node.
4) A request item for the new “Line of Business” node is added to the request. The request item
shows the number of changes (2), the viewpoint where the changes were made (Line of
Business) and the action performed (Add).
5) Select a different “Line of Business” node. Update the “End Date” and “Enabled” properties for
that node.
71
6) A request item for the updated “Line of Business” node is added to the request. The request
item shows the number of changes (2), the viewpoint where the changes were made (Line of
Business) and the action performed (Update).
7) Click the menu icon for the node and select Delete. The node is marked for deletion.
72
8) A request item for the deleted “Line of Business” node is added to the request. The request
item shows the number of changes (1), the viewpoint where the changes were made (Line of
Business) and the action performed (Delete).
End of Exercise
Exercise 3 Make Changes to Hierarchies

1) Click on the “Cost Center” viewpoint tab.
2) Click the Add icon above the hierarchy of “Cost Center” nodes and select Add Top Node.
3) A new “Corporate Cost Center” node is added as a top node. Define a Name and Description for
the Cost Center top node. Set the Summary property to “Yes” and the Allow Posting property to
“No”.
73
4) A request item for the added “Cost Center” node is added to the request. The request item
shows the number of changes (5), the viewpoint where the changes were made (Cost Center)
and the action performed (Add).
5) Click the menu icon for the node and select Add Child.
6) A new Cost Center node is added as a child of the selected node. Define a Name and
Description for the Cost Center child node. Set the Summary property to “Yes” and the Allow
Posting property to “No”.
74
7) Click the menu icon for the “US” node and select “Insert Here”.
8) In the Cost Center viewpoint, expand nodes “T” and “100” and select node “121”. Click OK.
75
9) Node “121” is inserted as a child of the “US” node.
10) Expand node “200”. Drag and drop node “221” from parent “200” to parent “US”. The node
has been moved.
11) Drag and drop a request item to parent node “200” in the hierarchy. The request item node has
been inserted as a child of that node.
76
12) Request item “221” now has two actions (Move and Insert) in different locations in the
viewpoint.
13) Click the menu icon for node “223” and select Remove. The node is marked for removal.
77
End of Exercise
Exercise 4 Load Changes From Spreadsheets

1) In your Source Files folder, open the “Product Changes.xlsx” file in Excel.
2) From the request menu, select “Load Request Items”.
3) The Load Request Items dialog is displayed. Click to select a file or drop a file.
78
4) Choose the “Product Changes.xlsx” file and click “Open”.
5) Preview the file contents to be loaded into the request. File format issues such as missing or
unknown columns are identified.
79
6) Click “Load” to load the file. A summary displays the overall status of the file load.
7) Five new request items are added to the request. Each items shows the number of changes
made for each node in the viewpoint.
8) Click on request item “333” to view the “Product” viewpoint and action type. Click on the
request item instance to navigate to the node in the viewpoint. This step can be repeated for
the other 3 request items.
80
End of Exercise
Exercise 5 Validate Changes and Resolve Issues

1) Request items are validated based on the configuration of the node types, hierarchy sets, and
viewpoints. Invalid request items are marked with validation issues.
2) The Issues icon shows how many validation issues there are in the request.
3) Click the “Issues” icon to view only request items with validation issues.
81
4) Expand request item “460” to identify which viewpoint and action has the validation issue.
5) Select the invalid request item instance to navigate to node “460” in the “Product” viewpoint.
Validation messages are displayed for the node.
6) From the menu for request item “460”, select “Validate” (this is a known issue and should not be
required). Invalid properties for the node are outlined in red. Click on the Name property editor
to view validation message for the property.
82
7) Update the Name to “470” to resolve the validation issue. The property update is revalidated
and the validation issue disappears when valid.
End of Exercise
Exercise 6 Add Comments

1) Click the Comments icon to display the Comments pane.
2) To add a comment, click the Add Comment icon.
3) Enter comments for the request. Hit Tab or Enter to save your comment.
83
End of Exercise
Exercise 7 View and Add Attachments

1) Click the Attachments icon to display the Attachments pane.
2) Files used to load request items are attached to the request.
3) Click the name of a Request File attachment to download the file. Load status and error
messages for records which could not be loaded are recorded in a request file.
4) Click the “Add Attachment” button.
84
5) On the Attach File dialog, click to select a file or drop a file.
6) Select the “Meeting Notes.docx” file and click “Open”.
7) View the file to be attached and modify the filename (if necessary). Click the “Attach” button.
85
8) The file is attached to the request.
End of Exercise
Exercise 8 Submit Requests

1) Click the “Submit” button to submit the request.
2) Changes in the request will be re-validated and committed to data in the viewpoints. If
successful, the request is closed and you are returned to the Active View of the data where the
newly updated data is displayed.
86
3) Select the “Cost Center” viewpoint. Expand the “Alternate” node to view the changes from the
request which are now committed.
4) Click “Close” to close the view.
End of Exercise
Exercise 9 View Request Activity

1) Click “Requests” from the top of the page.
2) View the submitted request. It now has a status of Completed.
87
3) Click on the name of the request. Completed requests are displayed in the request inspector.
4) Select the “Details” tab to view the request items in the request.
5) Expand a request item to view the changes for the item.
88
6) Click the menu icon on the Details tab and select “Download to File”.
7) All request items are downloaded to a spreadsheet file. Open the file to view its contents.
Request items for different viewpoints are placed on different worksheets.
8) Comments and attachments are also avaiable from the request inspector. Click the
“Comments” or “Attachments” tab to view them.
89
9) Click “Close” to exit the request inspector.
End of Exercise
End of Scenario
90
Scenario 6: Create Alternate Views and
Viewpoints
Scenario 6: Create Alternate Views and Viewpoints

This scenario demonstrates how to create views and viewpoints to build
alternate business perspectives as well as share and map data across
applications in Oracle Enterprise Data Management Cloud Service.
91
Exercise 1 Create Views

1) Click “Views” from the top of the page.
2) Click the “Create” button to create a new view.
3) Enter a Name and Description for the view. Click “Create” to save your changes.
4) The new view is displayed in the view inspector.
End of Exercise
92
Exercise 2 Create Viewpoints

1) Select the “Definition” tab in the view inspector.
2) Click the “Create” button to create a new viewpoint in the view.
3) Select “Financials Cloud” as the application and “Corporate Product” as the dimension for the
viewpoint.
4) Enter a Name and Description for the viewpoint. Click “Create” to save your changes.
93
5) The new viewpoint is created in a Draft status because it does not have a Node Set. Click “Edit”
on the “Product” viewpoint inspector.
6) Select the “ALL CORPORATE PRODUCTS | V1” node set in the “Financials Cloud” application for
the viewpoint.
7) Click “Save”. The viewpoint is now placed in Active status.
94
8) Click the “My Alternate View” tab at the bottom of the inspector to inspect the view again.
Select the “Definition” tab to display the viewpoints for the view.
9) Click the “Create” button to create another viewpoint in the view.
10) Select “Corporate Planning” as the application and “Cost Center” as the dimension for the
viewpoint.
95
11) Enter a Name and Description for the viewpoint. Click “Create” to save your changes.
12) Click “Edit” on the viewpoint inspector. Select the “Cost Center” node set in the “Corporate
Planning” application for the viewpoint. Click “Save”
96
13) The new viewpoints for “Product” and “Cost Center” are added to the view.
14) Click “Close” to exit the inspector.
End of Exercise
Exercise 3 Create Node Types

2) Click the “Create” button to create a new node type.
new node type.
4) Define a Name and Description for the new Product node type. Click “Create”.
97
5) The “Channel” node type is displayed in the inspector. Select the “Properties” tab to view
properties of the node type. Click “Edit” to edit the properties for the “Channel” node type.
6) Click the “Manage” button. Select the “FCGL.Enabled”, “FCGL.Start Date”, and “FCGL.End Date”
properties. Click OK.
98
7) The selected properties are added to the “Channel” node type. Mark the “Description” property
as Required. Click “Save”.
8) Click “Close” to exit the node type inspector.
99
End of Exercise
Exercise 4 Create Hierarchy Sets

2) Click the “Create” button to create a new hierarchy set.
3) Select “Corporate GL” as the application and “Product” as the dimension for the hierarchy set.
4) Define a Name and Description for the new hierarchy set. Click “Create”.
100
5) The “Products By Channel” hierarchy set is displayed in the inspector. Select the “Definition”
tab. Click “Edit” to edit the node types for the hierarchy set.
6) Click the “Manage” button. Select the “Channel” and “Corporate Product” node types. Click OK.
7) The node types are selected for the hierarchy set. Change the Child Option for “Channel” to
Selected and select child node types “Channel” and “Corporate Product”. Change the Child
Option for “Corporate Product” to Selected and select child node type “Corporate Product”.
101
8) The “Allow Shared Nodes” option should be set to True. This setting allows the same node to
exist under multiple parents in a hierarchy set.
9) Set “Use Custom Order” to True. This setting allows nodes to be sorted under a parent using a
custom order.
10) Click “Save” to save changes. The hierarchy set is now configured and set to Active status.
11) Click “Close” to exit the hierarchy set inspector.
End of Exercise
Exercise 5 Create Node Sets

102
2) Click the “Create” button to create a new node set.
node set.
4) Define a Name and Description for the new node set. Click “Create”.
5) The “Product By Channel” node set is displayed in the inspector. Click “Edit”. Select the
“Product By Channel” hierarchy set.
103
6) Click “Save”. The node set is now active. Select the “Definition” tab to view the hierarchy set
and node types used by the node set.
8) Click “Views” at the top of the page.
9) From the Actions menu for the “My Alternate View”, select “Inspect”.
104
10) Select the “Definition” tab. Click “Create” to create a new viewpoint.
11) Select “Financials Cloud” for the application and “Corporate Product” for the dimension.
12) Define a Name and Description for the viewpoint. Click “Create”.
105
13) Click “Edit” on the viewpoint inspector. Select the “Product By Channel” node set. Click “Save”
to set the viewpoint to Active status.
14) Select the “My Alternate View” tab from the bottom of the inspector. Select the “Definition”
tab. Click “Edit”.
106
15) From the Actions menu for the “Product By Channel” viewpoint, select “Up” to reorder the
viewpoints.
16) Click “Save” to save the changes to the view.
17) Click “Close” to exit the inspector.
End of Exercise
Exercise 6 Copy Viewpoints

1) From the Views page, click on the name of the “My Alternate View” view to open it.
2) The viewpoints you created are displayed in the view.
107
3) Select the “Cost Center” viewpoint. From the viewpoint tab menu, select “Copy” to copy the
viewpoint.
4) The Copy Viewpoint dialog is displayed. Enter a Name and Description for the new viewpoint to
be created.
5) Specify whether to Copy Nodes and Copy Relationships to the new viewpoint. Copy Nodes
copies the node type(s) for the viewpoint. Copy Relationships copies the hierarchy set and its
relationships.
6) Click the “Copy” button to perform the copy. You are notified that new data chain objects were
created for the copied viewpoint. Click OK.
108
7) The new viewpoint is added to and displayed in the view.
8) Inspect the new viewpoint and identify the copied node set and hierarchy set for the viewpoint.
End of Exercise
Exercise 7 Bind Viewpoints to Dimensions

1) View the Binding Status of the “Cost Center Reorg” viewpoint. This viewpoint is currently
“Unbound”.
109
2) Click the name of the Dimension on the viewpoint inspector to inspect the “Cost Center”
dimension.
3) Select the “General” tab on the dimension inspector to view the bindings and bound viewpoints
for the “Cost Center” dimension.
4) Click the “Cost Center” binding to inspect it.
110
5) The “Cost Center” binding is displayed in the binding inspector. Click “Edit”.
NOTE: This screen has a known issue where the values for the Binding Type, View, and
Viewpoint parameters are displayed below the labels instead of to the right.
6) Select “My Alternate View” as the view and “Cost Center Reorg” as the viewpoint.
7) Click “Save”. The selected viewpoint is now bound to the dimension for the application. This
viewpoint will be used for exports to the external application.
111
8) Select the “Cost Center” dimension tab at the bottom of the inspector.
9) View the new Bound Viewpoint for the “Cost Center” dimension.
End of Exercise
Exercise 8 Archive Viewpoints

1) Select the “Cost Center Reorg” tab at the bottom of the inspector.
2) Click the view “My Alternate View” on the viewpoint inspector to inspect it.
3) Select the “Definition” tab in the view inspector.
112
4) Click on the name of the “Cost Center” viewpoint.
5) Click “Edit” to edit the viewpoint. Change the Status of the viewpoint to “Archived”.
6) Click “Save” to archive the viewpoint. Once archived, the viewpoint will no longer be displayed
in the open view and cannot be used for requests, imports, or exports.
113
7) Click “Close” to close the viewpoint inspector. Click OK to reload the view.
8) The archived “Cost Center” viewpoint is no longer displayed in the view.
9) Click “Close” to close the view and return to the Views page.
End of Exercise
End of Scenario
114
Scenario 7: Share Enterprise Data Across
Applications
Scenario 7: Share Enterprise Data Across Applications

This scenario demonstrates how to share nodes, relationships, and properties
across dimensions of multiple applications in Oracle Enterprise Data
Management Cloud Service.
115
Scenario 7: Share Data Across Applications
Exercise 1 Create Node Type Converters

2) Click on the name of the “Entity” node type for the “Financial Consolidation and Close”
application to inspect it.
3) Select the “Converters” tab. Click “Edit”.
4) Click “Add” to add a source node type. Select “Financials Cloud” as the application and
“Corporate Company” as the node type. Click OK.
5) For the selected source node type, define which properties to copy to the target node type.
Select “FCGL.Description US” from the Source node type for the PLN.Alias: Default property in
the Target node type.
116
6) Click “Save” to save the node type converter. Click “Close” to close the inspector.
7) Click on the “Entity” node type for the “Corporate Planning” application to inspect it.
8) Select the “Converters” tab. Click “Edit”.
117
9) Click “Add” to add a source node type. Select “Financial Consolidation and Close” as the
application and “Entity” as the node type. Click OK.
10) For the selected source node type, define which properties to copy to the target node type.
Properties which are common between node types are defaulted.
11) Click “Save”. Click “Close” to close the node type inspector.
End of Exercise
Exercise 2 Display Viewpoints Side By Side

118
2) Click on the “Entity Maintenance” view to open it.
3) Click the “Side By Side” icon in the upper right.
4) The selected viewpoint and the next viewpoint are displayed side by side.
5) You can navigate viewpoints independently side by side. Select a node on the left side. Expand
a node on the right side. Properties are displayed below each selected node.
119
6) Click the “Hide Properties” button to hide the properties and only view nodes.
120
End of Exercise
Exercise 3 Compare Viewpoints

1) Click the “Compare” icon on the far left side. The Compare pane is displayed.
2) Choose to compare “Left to Right”. Compare results wil be displayed for the source viewpoint.
The source viewpoint is the left side in a “Left to Right” compare.
121
3) Select whether to compare all nodes in the viewpoints or only bottom level nodes. Bottom level
nodes are nodes with no children in hierarchy viewpoint. All nodes in a list viewpoint are
considered bottom level nodes.
4) Choose the type of comparison you want to do. Select “Find Missing Nodes”.
5) Click the “Compare” icon to perform the compare. Compare results are displayed in the
Compare pane. Nodes with compare results are marked in the viewpoint.
6) Nodes which are missing from the other viewpoint are displayed in the compare results. Select
node “103” in the compare results to navigate to the node in the source viewpoint.
122
End of Exercise
Exercise 4 Locate Nodes Across Viewpoints

1) Select node “102” to find where it is located in the “Financial Consolidation” viewpoint. Click
the “Locate” icon to locate the node in the other viewpoint.
2) Node “C_102” is found and selected in the target viewpoint. The node type converter(Financial
Consolidation and Close: Entity) was used to locate the node across applications.
123
End of Exercise
Exercise 5 Add Nodes Across Viewpoints

1) Click the “New Request” button to create a new draft request.
2) Drag and drop node “103” from the compare results to the parent of the node which was
located in the target viewpoint (C_100).
124
3) The source node gets converted to a node of a target node type based on node type converters.
A new node gets added to the target viewpoint and inserted under the specified parent.
4) Click the “Show Properties” button at the bottom of the page to view properties again.
5) View the properties of the added node. Properties have been copied to the new node based on
node type converters. The Name of the node is prefixed with the Qualfier text if configured for
the target node type.
125
End of Exercise
Exercise 6 Align Nodes and Properties Between Viewpoints

1) Change the viewpoints being compared. Select “Planning and Budgeting” for the right side and
“Financial Consolidation” for the left side.
2) Click the “Align” icon on the left side to align properties across viewpoints for nodes selected on
the left side. Align mode is enabled.
3) Select node “C_102” in the “Financial Consolidation” viewpoint. Node “C_102” is automatically
located in the “Planning and Budgeting” viewpoint when Align mode is enabled.
126
4) Properties are aligned for both viewpoints based on common properties and other properties
mapped in the node type converter. Properties below the double line could not be aligned.
5) The property difference indicator identifies there is a difference between values for the aligned
properties.
End of Exercise
Exercise 7 Compare Relationships and Properties

1) In the Compare pane, check the “Compare Relationships” and “Compare Properties” options.
Uncheck, the “Find Missing Nodes” option.
127
2) Click the “Compare” icon to run the compare.
3) Nodes with different relationships and properties are displayed in the compare results.
4) Select node “C_All_Corp_Comp_V1” in the Different Relationships group.
5) The node is found in both viewpoints. This has a parent in the left viewpoint but does not in the
right viewpoint.
128
6) Expand the Different Property Values group in the compare results. Nodes with different
properties are displayed.
7) Select node “C_102” in the Different Properties group. The node is found in both viewpoints.
129
8) View the property difference for node “C_102” across the viewpoints.
Exercise 8 Resolve Property Differences Between Viewpoints

1) Copy the Alias value from node “C_102” in the “Financial Consolidation” viewpoint.
130
2) Paste the value into the Alias property for node “C_102” in the “Planning and Budgeting”
viewpoint..
3) The property difference has been resolved and the difference indicator is no longer displayed.
4) Click the “Requests” finger tab on the far left side. The draft request is displayed containing
request items for node “C_103” and “C_102”.
5) Enter a title for the request.
131
6) Click “Submit” to submit the request and commit the changes.
End of Exercise
End of Scenario
132
Scenario 8: Map Enterprise Data Across
Applications
Scenario 8: Map Enterprise Data Across Applications

This scenario demonstrates how to manage mappings between dimensions of
different applications in Oracle Enterprise Data Management Cloud Service to
be used by external data loading processes.
133
Scenario 8: Map Data Across Applications
Exercise 1 Create Source Node Types

1) Click “Applications” from the top of the page.
2) View two applications (Acquired GL and Corporate Planning) which have different Account
dimensions. Accounts from the “Acquired GL” application need to be mapped to Accounts in
the “Corporate Planning” application.
4) Click on the “Acquired Account” node type for the “Corporate Planning” application to inspect it.
5) This node type was created to manage “Account” nodes from the “Acquired GL” to be mapped
to “Account” nodes in the “Corporate Planning” application.
134
6) Select the “Converters” tab. A node type converter has been added for “Account” nodes in the
“Acquired GL” application.
7) Click “Close” to close the inspector.
End of Exercise
Exercise 2 Create Mapping Hierarchy Sets

135
2) Click on the “Account Mapping” hierarchy set for the “Corporate Planning” application to
inspect it.
3) This hierarchy set was created to manage mappings between “Account” nodes in the “Acquired
GL” application and the “Corporate Planning” application.
4) Click the “Definition” tab. The “Account” and “Acquired Account” node types are being used.
The child node types are configured to allow “Account” nodes to be parents of “Acquired
Account” nodes to manage source-to-target relationships.
136
5) Click “Close” to close the inspector.
End of Exercise
Exercise 3 Create Mapping Node Sets

2) Click the “Account Mapping” node set to inspect it. This node set was created to manage
account mappings between the “Acquired GL” application and the “Corporate Planning”
application.
3) Click the “Definition” tab. View the node types and top nodes for the “Account Mapping” node
set.
137
End of Exercise
Exercise 4 Map Nodes Across Applications Using Requests

2) Click on the “Account Maintenance” view to open it.
3) Select the “Acquired Account” viewpoint. This list of acounts from the “Acquired GL”
application must be mapped to the “Corporate Planning” application.
138
4) Click the “Side By Side” icon to display the “Acquired Account” and “Account Mapping”
viewpoints side by side.
5) Expand nodes in the “Account Mapping” viewpoint. This hierarchy manages mapping
relationships between “Account” nodes and “Acquired Account” nodes. “Acquired Account”
nodes are placed as children of “Account” nodes in the mapping hierarchy.
139
6) Click the “Compare” finger tab to the far left. Select “Find Missing Nodes”. Click the Play icon to
compare the “Acquired Account” viewpoint to the “Account Mapping” viewpoint.
7) Acquired accounts which have not been mapped are displayed as missing nodes in the compare
results.
140
8) Click “1310” to navigate to the node in the “Acquired Account” viewpoint.
10) To map a source application node to a target application node in the mapping viewpoint, drag
and drop the node from the source viewpoint and drop it on the target application node.
141
11) The source node is converted to a target node type used for mapping and inserted under the
target application node that it is mapped to.
12) View the properties of the “Acquired Account” which were copied when the source node was
mapped.
142
13) Click the “Submit” button to commit the changes to dimension mappings for the target
application.
End of Exercise
Exercise 5 Create Mapping Keys for Dimensions

1) From the Actions menu on the “Corporate Planning” view, select “Inspect”.
2) Select the “Definition” tab. Click “Create” to create a viewpoint to export mappings.
143
3) Select “Corporate Planning” as the application and “Account” as the dimension.
4) Define a Name and Description for the mapping viewpoint. Click “Create” to create the
viewpoint.
5) Click “Edit”. Select the “Account Mapping” node set. Click “Save”.
6) Click on the “Account” dimension to inspect it.
144
7) Select the “Mapping” tab in the dimension inspector.
8) Click “Edit” and select the “Account Mapping” viewpoint to export mappings for the dimension.
9) Click “Create” to create a mapping key for the dimension.
10) Enter a Location Name, select “Acquired Account” as the source node type, and “Account” as
the target node type for the mapping key.
145
11) Click “Save” to save the mapping keys for the “Account” dimension in the “Corporate Planning”
application.
End of Exercise
End of Scenario
146
Scenario 9: Synchronize Enterprise Data
Across Applications
Scenario 9: Synchronize Enterprise Data Across

Applications
This scenario demonstrates how to synchronize changes across dimensions of
different applications using subscriptions in Oracle Enterprise Data
147
Scenario 9: Synchronize Data Across Applications
Exercise 1 Create Subscriptions For Target Viewpoints

2) Open the “Product Maintenance” view by clicking on it.
3) This view contains similar viewpoints across the Corporate GL, Planning, and Financial Close
applications.
4) Expand the top node of the “Corporate GL” viewpoint. Changes to this viewpoint should be
synchronized with the “Plan” and “Close” viewpoints.
5) Select the “Plan” viewpoint, click the menu icon, and choose the Inspect menu item.
148
6) From the viewpoint inspector, select the Subscriptions tab.
7) Click the “Create” button to create a subscription for the “Plan” viewpoint.
8) From the create subscription dialog, select the “Corporate GL” viewpoint from the “Product
Maintenance” application.
9) The Name of the subscription is defaulted based on the selected viewpoint. It can be optionally
modified.
149
10) Enter a Description for the subscription and click “Create”.
11) The “Product Maintenance | Corporate GL” subscription is created for the “Plan” viewpoint.
Click “Edit” to edit the subscription.
12) Set the following subscription parameters and click “Save” to save your changes.
13) Click on the view “Product Maintenance” to inspect the view.
14) Select the “Definition” tab and click on the “Close” viewpoint name to inspect it.
150
15) Select the “Subscriptions” tab in the “Close” viewpoint inspector.
16) The “Close” viewpoint also has a subscription to the “Corporate GL” viewpoint in the “Product
Maintenance” view. Click the “Close” button.
End of Exercise
Exercise 2 Submit Request For Source Viewpoints

1) Click the “New Request” button to create a new request for the “Product Maintenance” view.
151
2) Select the “Corporate GL” viewpoint.
3) Expand node “T” and “200 and select node “220”.
4) Click the menu icon for node “220” and select the Add Child menu item.
5) For the “New Corporate Product” node, define the following properties:
 Name: 224
 Description: SmartWatch
152
6) Modify the title of the request to include “SmartWatch”.
7) Click the “Submit” button to submit the request. The request was successfully submitted.
8) Click the Navigate menu icon in the upper left and select “Requests” from the Navigator menu.
9) View the completed “SmartWatch” request. Two subscription requests have been generated to
synchronize these changes to the “Plan” and “Close” viewpoints.
153
End of Exercise
Exercise 3 Subscription Request Using Auto-Submit

1) For subscription requests which pass validations and are auto-submitted, the assignee of the
subscription gets notified of the completed request and no further action is required. Here is an
example of this notifiation:
2) From the Home page, click the “Requests” icon.
154
3) The Requests page is displayed. Click the “My Activity” filter, select “Submitted”, and click OK.
4) A subscription request for the “Product Maintenance” viewpoint was auto-submitted by the
user and is in Completed status.
5) Click the title of the subscription request to inspect it.
155
6) Select the “Details” tab to view the request item for the subscription request. Expand the
request item to view the request actions which were performed.
7) Click “Close” on the request inspector. Click on the “Product Maintenance” view on the
subscription request in Request Activity.
156
8) The “Product Maintenance” view is opened. Select the “Close” viewpoint.
9) Search for “224”. Node “P_224” was found in the “Close” viewpoint. Select the search result to
navigate to the node which was added by the auto-submitted subscription request.
10) Sign out of Oracle Enterprise Data Management Cloud Service.
End of Exercise
157
Exercise 4 Subscription Request Assigned to User

1) Request assignees configured for subscriptions receive notifications for subscription requests.
Here is an example of a notification for a subscription request which has validation issues and is
assigned to the user for resolution.
1) Sign in to Enterprise Data Management Cloud Service as user “user2” with a password of
“epmEDM1!”.
158
2) From the Home page, click the “Activity” tab.
3) The “Activity” tab displays a summary of requests the user needs to work on or has submitted.
One draft request is assigned to the user. Click the “Draft Requests” link.
4) The Requests page is displayed and is filtered to Draft requests which are Assigned to the user.
A subscription request for the “Product Maintenance” view is displayed with 1 request item and
1 validation issue.
159
5) Click on the ID or title of the draft request to open it.
6) The subscription request is opened in the “Product Maintenance” view. This request includes a
request item for node “P_224” in the “Plan” viewpoint.
160
7) The “Alias: Default” property has a validation issue. Place your cursor in the editor for the
“Alias: Default” property to edit it.
8) Define a value for the “Alias: Default” property to resolve the validation issue.
9) Click the “Submit” button to submit the updated subscription request for the “Plan” viewpoint.
10) The subscription request was successfully submitted.
11) Click the Search icon and search for “smartwatch”. Node “P_224” was found. Select it to
navigated to the committed node in the “Plan” viewpoint.
161
End of Exercise
End of Scenario
162
Scenario 10: Govern Enterprise Data
Across Applications
Scenario 10: Govern Enterprise Data Across

Applications
This scenario demonstrates how to govern enterprise data using permissions,
approval policies, and collaborative workflows in Oracle Enterprise Data
163
Scenario 10: Govern Data Across Applications
Exercise 1 Grant Permissions to Users

“epmEDM1!”.
2) Select the “Applications” icon from the Home page.
3) Click the “Financials Cloud” application to inspect it.
4) Select the “Permissions” tab to display users who have permissions to access the application.
164
5) Click “Edit” to edit permissions for the “Financials Cloud” application.
6) Select the Add a User dropdown and choose “User2 Training”.
7) From the Permission dropdown for user “Betty Anderson”, select “Submitter”.
8) Click “Save” to save your changes.
End of Exercise
Exercise 2 Enable Approval Policies

1) From the application inspector, select the “Definition” tab to view the dimensions in the
“Financials Cloud” application.
165
2) Click the “Corporate Company” dimension to inspect it.
3) From the dimension inspector, select the “Policies” tab to view the polices for the dimension.
4) An approval policy is available for the “Corporate Company” dimension. The policy is disabled
by default. Click the “GL Entity Approval” policy to inspect it.
5) Select the “Definition” tab in the policy inspector. Click “Edit” to edit the approval policy for the
“Corporate Company” dimension.
166
6) Configure the following parameters for the approval policy of the “Corporate Company”
dimension in the “Financials Cloud” application:
 Enabled: True
 Approval Method: Parallel
 One Approval Per Group: True
 Include Submitter: True
 Reminder Notification: After 2 Days
 Approval Escalation: After 2 Reminders
167
7) From the “Add an Approval Group” dropdown, select the “Corp Accounting” user group.
8) The “Corp Accounting” group is listed as an approval group and the total approvals required is
one approval from that group.
9) Click “Save” to save your changes and enable the approval policy.
10) Click “Close” to close the policy inspector for the “Corporate Company” dimension in the
“Financials Cloud” application.
End of Exercise
Exercise 3 Create and Assign Request

1) Click the “Views” icon at the top of the page.
168
2) Click the “Entity Maintenance” view to open it.
4) Click the “Add Node” icon for the “Corporate GL” viewpoint.
5) A “New Corporate Company” node is added to the list. Set the following properties for the
node:
 Name: 121
 Description: US 1 Health
 Description US: US 1 Health
6) Click the menu icon for request item “121” in the “Corporate GL” viewpoint and select the “Add
Comment” menu item.
169
7) Enter a comment for the request item to explain or justify the change being made. Click “Save”
to save the comment.
8) From the Actions dropdown for the request, choose the “Assign” menu item.
170
9) From the “Select an Assignee” dropdown, select “User 2 Training”.
10) Enter a comment directed at the new assignee. Click OK.
11) The request has been assigned to user “User 2” to complete and submit it.
171
End of Exercise
Exercise 4 Submit Request for Approval

1) Sign in to Oracle Enterprise Data Management Cloud Service as user “user2” with password
“epmEDM1!”.
172
2) On the Home page, the user has 1 draft request assigned to them. Click “Draft Requests” to
view the assigned request.
3) Request Activity is displayed and filtered to Draft requests which are Assigned to the current
user.
4) Click the title of the assigned request to open it.
5) The assigned request is displayed in the “Entity Maintenance” view. The user can visualize the
changes made by the original user.
6) Click the “1 Comments” link to view the comment for request item “121” in the “Corporate GL”
viewpoint.
173
7) Assigned requests can be modified since they are still in Draft status. Select the “Financial
Consolidation” viewpoint.
8) Expand the hierarchy to node “C_100” in the “Financial Consolidation” viewpoint.
9) Select “121” from the request items list and drag-and-drop it to node “C_100” in the “Financial
Consolidation” viewpoint.
174
10) Node “C_121” is added to the “Financial Consolidation” viewpoint under parent “C_100”.
11) Click the “Side By Side Layout” icon to view the “Financial Consolidation” and “Planning and
Budgeting” viewpoints side by side.
175
12) Select node “C_100” in the “Financial Consolidation” viewpoint and click the “Locate” icon.
13) Node “C_100” was located in the “Planning and Budgeting” viewpoint.
176
14) Drag-and-drop node “C_121” from the “Financial Consolidation” viewpoint to parent “C_100” in
the “Planning and Budgeting” viewpoint.
177
15) The node has now been added to 3 applications by 2 different users. All of these applications
have approval policies enabled at the dimension level.
16) Define a title for the request. Click the “Submit” button to submit the request for approval.
17) The request is now in In-Flight status. Click the request menu icon and choose the “Inspect”
menu item.
178
18) In the request inspector, select the “Approvals” tab to view approval related information for the
request.
19) The Remaining Approvals section identfies the approval policies in effect and how many
approvals are required for each policy. An approval is required for the dimension in each
application affected by this request.
20) The Invitees section identifies the users and groups which are invited to approve the request.
21) Click “Close” to exit the request inspector. Sign out of Oracle Enterprise Data Management
Cloud Service.
End of Exercise
179
Exercise 5 Approve Requests

1) Approvers receive notifications inviting them to approve the request. Here is an example of an
invitation to approve a request for the “Entity Maintenance” view.
“epmEDM1!”.
180
3) On the Home page, the user has 1 request to approve. Click “Requests to Approve” to view the
request.
4) Request Activity is displayed and filtered to In Flight requests to which the current user is
invited.
181
5) Click the title of the in-flight request to open it.
6) The request to be approved is displayed in the “Entity Maintenance” view.
7) The request items are filtered to those which require approval from the current user. Request
items cannot be modified during approval.
8) The approver can visualize the changes to the viewpoints by selecting request items in the
request.
182
9) Click the “1 Comments” link to view the comment for request item “121” in the “Corporate GL”
viewpoint. The approver can optionally reply to the comment or add a separate comment of
their own.
10) Click the “Actions” menu in the upper right. The approver can perform one of 3 workflow
actions during the Approve stage.
 Approve – allow changes in the request to be committed
 Pushback – send the request back to the submitter to modify and resubmit
 Reject – close the request without committing the changes
183
11) Click the “Approve” button to approve the request. Enter an optional comment during approval.
Click OK to proceed.
12) Upon final approval, the request is validated and committed to the viewpoints.
End of Exercise
184
Exercise 6 Review Request Approvals and History

1) Click the Navigate menu icon in the upper left and select “Requests” from the menu.
2) View the approved request in Completed status. Click the request title to inspect the completed
request.
3) Select the “Approvals” tab. View the approvals for the request including which user for which
policy. “Admin1” is an approver for all 3 policies and his approval was recorded for each one.
185
4) Select the “History” tab. Request history is displayed showing user activities which took place
during the life of the request.
End of Exercise
End of Scenario
186
Scenario 11: Export Enterprise Data To
Applications
Scenario 11: Export Enterprise Data To Applications

This scenario demonstrates how to export data from Oracle Enterprise Data
Management Cloud Service to target business applications.
187
Exercise 1 Validate Viewpoints Before Export

2) Click on the “Financial Consolidation and Close” view to open it.
3) The Account viewpoint is bound to the Account dimension in the “Financial Consolidation and
Close” application. From the viewpoint tab menu, select “Validate”.
4) The viewpoint is validated and validation results are shown in the Validate pane. A message is
displayed to communicate the validation status.
188
5) Click “New Request” to create a new request.
6) Click on node “Supplemental” in the validation results to navigate to the node in the “Account”
viewpoint. The validation messages for the node are displayed.
7) The “Aggregation” property is outlined in red indicating it has a validation issue.
189
8) Click on the property and select “~” to resolve the validation issue.
9) Click “Submit” to submit the request and commit the property update.
End of Exercise
Exercise 2 Export Dimensions to Files

1) Click “Applications” at the top of the page.
2) From the Actions menu for the “Financial Consolidation and Close” application, select “Export”.
190
3) Select the “Account” dimension to export.
4) Choose an Export Target of “File”.
5) Click “Export” to export the dimension. A status message is displayed once the export
completes.
191
6) The export file is downloaded to the web browser.
7) Open the export file to view the contents.
8) Click “Close” to exit the export screen.
End of Exercise
Exercise 3 Export Dimensions to Connections

is not available for this training. It is for reading purposes only. Continue with Exercise 4 after
reading.
1) From the Actions menu for the “Corporate Planning” application, select “Export”.
192
2) Select the “Entity” dimension to be exported.
3) Choose an Export Target of “Connection” and “Production” as the connection.
4) Change the file name to “Entity.csv”.
5) Click “Export” to export the dimension. The dimension export file is transferred to the
Enterprise Planning and Budgeting Cloud Service inbox. A status message is displayed for the
export.
6) Click “Close” to close the export screen.
193
7) Access Enterprise Planning and Budgeting Cloud Service and select “Application” and
“Overview” from the home page.
8) From the Actions menu, select “Inbox/Outbox Explorer”.
9) View the dimension export file from Enterprise Data Management Cloud Service in the Inbox.
194
10) Click “Close” to close the Inbox/Outbox Explorer. Select the “Dimensions” tab.
11) Click the “Import” button to import a dimension. Click “Create” on the Import Metadata screen.
12) Select “Inbox” for the Location.
13) For the “Entity” dimension, enter “Entity.csv” as the import file.
14) Click “Save as Job” to save the import job. Define a Name for the job. Click “Save”.
195
15) Click “Close” on the Import Metadata screen. The “Entity Import” job is displayed.
16) From the Actions menu for the “Entity Import” job, select “Submit” to run the import job. Click
OK and “Close” on the Import Metadata screen.
17) Select “Jobs” from the top of the page.
196
18) View the results of the “Entity Import” job. The dimension was successfully imported.
End of Exercise
Exercise 4 Export Mappings

is not availble for this training. It is for reading purposes only. Continue with Scenario 12 after
reading.
1) From the Actions menu for the “Corporate Planning” application, choose “Export Mapping”.
2) Select a dimension to export mappings.
197
3) Select “US COA Location” for the Location.
4) Choose an Export Target of “Connection” and “Production” as the connection.
5) Change the file name to “Account Mappings.csv”.
6) View the details of the “Account” dimension mapping export.
7) Click “Export” to export the dimension to the connection. The mapping export file is transferred
to the Data Management inbox in Enterprise Planning and Budgeting Cloud Service. A status
message is displayed for the export.
198
8) Click “Close” to close the export screen.
9) Access Enterprise Planning and Budgeting Cloud Service and use the menu to navigate to Data
Management.
10) A new browser window is opened to display Data Management (you may need to allow popups
in your browser). Select “Data Load Mappings” from the menu on the left.
11) Use the “US COA Location” for importing the mappings.
12) Select the “Account” dimension for which to import mappings.
13) Select “Import->Dimension”, select the “Inbox” folder, and select the “Account Mappings.csv”
file. Click OK.
199
14) Select “Merge” as the import mode and “No Validate” for valdiation. Click OK to import the
mappings.
15) View the imported mappings in Enterprise Planning and Budgeting Cloud Service.
200
End of Exercise
End of Scenario
201
Scenario 12: Control User Access

This scenario demonstrates how to provision users and groups with roles and
permissions to control their level of access in Oracle Enterprise Data
202
Exercise 1 Provision Users and Groups with Roles

1) Click the “Access Control” icon from the top of the page.
2) Click “Create” to create a user group.
3) Define a Name for the group.
4) Select the Users tab and search for “*u*”. Select user “User2 and click Move to assign them as a
member of the group.
5) Click “Save”. The “Data Managers” user group is created.
203
6) Select the “Provision Roles” tab.
7) From the Actions menu for user “Barry”, select “Provision”.
8) Select the “View Creator” role and click “Move” to assign the role to “User2”. Click “OK”.
9) Change the “Users” dropdown to “Groups”.
204
10) Search for “Data*”. The “Data Managers” group is found. From the Actions menu, select
“Provision”.
11) Select the “Application Creator” role and click “Move” to assign the role to the “Data Managers”
group. Click “OK”.
End of Exercise
Exercise 2 Assign Permissions to Applications

1) Click the “Applications” icon at the top of the page.
2) Click on the “Financials Cloud” application to inspect it.
3) Select the “Permissions” tab. Click “Edit” to assign permissions.
205
4) Select the “Add a Group” dropdown and choose “Data Managers”.
5) From the Permission dropdown, select “Data Manager”.
6) Click “Save” to save assigned permissions for the application. Click “Close”
End of Exercise
Exercise 3 Assign Permissions to Views

206
2) Select the “Corporate Planning” view and from the Actions menu, choose “Inspect”.
3) Select the “Permissions” tab. Click “Edit” to assign permissions.
4) Select the “Add a User” dropdown and choose “User 2”.
5) The user gets granted the “Owner” permission for the view.
207
6) Click “Save” to save assigned permissions for the view. Click “Close”.
End of Exercise
End of Scenario
208
Scenario 13: Migration and Daily
Maintenance
Scenario 13: Migration and Daily Maintenance

This scenario demonstrates how to create and import snapshots used for
migration and maintenance purposes in Oracle Enterprise Data Management
Cloud Service.
209
Exercise 1 Export Snapshots

1) Sign in as user “admin1” with password “epmEDM1!”.
2) This user is a “Service Administrator” role user. Click the “Migration” icon at the top of the
page.
3) On the Categories tab, click the “Enterprise Data Management” category.
210
4) View the migration artifacts for Enterprise Data Management. Expand the Repository and
Security folders.
5) Click “Select All”. The Repository and Security artifacts are selected. Click “Close”.
6) Click the “Groups and Memberships” category to view those migration artifacts.
211
7) Expand the “Native Directory” folder and click “Select All”. Click “Close”.
8) All artifacts have been selected. Click “Export” to create a migration snapshot with these
artfiacts included.
212
9) Enter a name of “Snapshot_Example” for the snapshot. Click OK.
10) The migration status report shows the progress of the snapshot export. Click “Refresh” until the
process is complete.
11) Click “Close” to exit the migration status report.
End of Exercise
Exercise 2 Import Snapshots

1) Select the “Snapshots” tab. View the migration snapshots which were previously created. Find
the snapshot you created and expand it to view the artifact types it contains.
2) From the Actions menu for the snapshot you created, select the “Import” menu item. Click “OK”
to confirm.
213
3) The migration status report is displayed to monitor the status of the snapshot import process.
Click “Refresh” until the process is complete. Click “Close”.
End of Exercise
End of Scenario
214
Scenario 14: Automate Tasks

This scenario demonstrates how to download EPM Automate and use it to
automate service administrator tasks in Oracle Enterprise Data Management
Cloud Service.
215
Exercise 1 Download and Install EPM Automate

1) From the Settings and Actions menu, select the “Downloads” menu item.
2) In the EPM Automate section, click the appropriate Download button for your environment.
3) Run the EPM Automate installer to install the EPM Automate command-line interface.
End of Exercise
216
Exercise 2 Export and Import Snapshot using EPM Automate

1) Run the EPM Automate program (on Windows from Start->All Programs).
2) Enter the following commands. Replace the URL with one you used to access your environment.
epmautomate login a598717.admin1 epmEDM1! https://planning-test-

a598717.pbcs.us9.oraclecloud.com/epm
epmautomate exportsnapshot Snapshot_Example
epmautomate importsnapshot Snapshot_Example userPassword=epmEDM1!

resetPassword=false
epmautomate logout
3) View the results of the commands.
4) Click “Migration” at the top of the page.
217
5) Select the “Reports” tab. Click “Migration Status” to view the export and import snapshot
operations you performed using commands in EPM Automate.
End of Exercise
End of Scenario
218

Oracle EDMCS Hands On Training Guide

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Oracle EDMCS Hands On Training Guide

Încărcat de

Drepturi de autor:

Formate disponibile

Enterprise Data

July 19, 2019

Scenario 1: Register Applications................................................................................................... 5

Exercise 1 Register Financials Cloud General Ledger Application ............................................................6

Scenario 2: Understand Information Model ............................................................................. 34

Exercise 1 Manage Nodes and Properties Using Node Types ................................................................... 35

Scenario 3: Import Enterprise Data From Applications ....................................................... 46

Exercise 1 Import Dimensions From Files....................................................................................................... 47

Scenario 4: Work with Enterprise Data in Views .................................................................... 58

Exercise 1 Open Views ............................................................................................................................................ 59

Scenario 5: Change Enterprise Data With Requests .............................................................. 69

Exercise 1 Create Requests ................................................................................................................................... 70

Scenario 6: Create Alternate Views and Viewpoints .............................................................. 91

Exercise 1 Create Views .......................................................................................................................................... 92

Scenario 7: Share Enterprise Data Across Applications .................................................... 115

Exercise 1 Create Node Type Converters ...................................................................................................... 116

Scenario 8: Map Enterprise Data Across Applications ....................................................... 133

Exercise 1 Create Source Node Types............................................................................................................. 134

Scenario 9: Synchronize Enterprise Data Across Applications ....................................... 147

Exercise 1 Create Subscriptions For Target Viewpoints ......................................................................... 148

Scenario 10: Govern Enterprise Data Across Applications .............................................. 163

Exercise 1 Grant Permissions to Users .......................................................................................................... 164

Scenario 11: Export Enterprise Data To Applications ....................................................... 187

Exercise 1 Validate Viewpoints Before Export ........................................................................................... 188

Scenario 12: Control User Access .............................................................................................. 202

Exercise 1 Provision Users and Groups with Roles ................................................................................... 203

Scenario 13: Migration and Daily Maintenance ................................................................... 209

Exercise 1 Export Snapshots .............................................................................................................................. 210

Scenario 14: Automate Tasks...................................................................................................... 215

Exercise 1 Download and Install EPM Automate ....................................................................................... 216

Scenario 1: Register Applications

Exercise 1 Register Financials Cloud General Ledger Application

2) From the Home page, click the “Applications” icon.

3) The list of registered applications is displayed.

1) Click the “Register” button to register a new application.

3) Enter a Name and Description for the application. Click “Next”.

Exercise 2 Define Connections for Financials Cloud Application

2) Define the parameters of the new connection.

 Name: Financials Cloud

 Instance Location: https://fincloudgl-uscompany-fcgl.US11.oraclecloud.com

3) Click “Next” to save the connection. Click “Next” again to proceed.

4) Click “Create” to create a draft Financials Cloud General Ledger application.

Exercise 3 Configure Financials Setup

3) Specify the Base Language for the General Ledger application.

 Allow Multiple Active Tree Versions: True (checked)

 Allow Multiple Root Nodes: True (checked)

 Allow Duplicate Nodes: True (checked)

 Max Depth: -1 (no limit)

Exercise 4 Add Chart of Accounts Segments

 Value Set Code

 Value Set Description

 Account segment in Corporate chart of accounts

 Natural Account Segment: True (checked)

 Value Type (for Name of account): Numeric

 Max Length (for Name of account): 5

Exercise 5 Add Trees for Segments

 All Corporate Accounts

 Tree Version Name

 Version Start Date: <beginning of current month>

 Version End Date: <end of current month>

Exercise 6 Complete Financials Cloud General Ledger Registration

3) Click “Apply” to complete registration of the General Ledger application.

Exercise 7 Register Enterprise Planning and Budgeting Application