The Deployment Implementation PBCS

PTS Workshop
Oracle Planning and

Budgeting Cloud Service:
Implementation Training
The Deployment: Successfully

Implementing Planning in the Cloud
1 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

Oracle Proprietary - For Partner Attendees Only. Restricted to Personal Use in an Oracle partner training class.
Implementing a Cloud Solution – What’s Different?
– Handoff from Sales to Implementation
Topics – Features and Functional Differences between On-
Premises and In the Cloud
Technical Information – About the Oracle Cloud
Environment
– Deployment
– Security
– Maintenance and Patching

What is the typical handoff from
sales to consulting?
Ideal vs. Reality

What do you know coming in?
 Customer Expectations
 Business Requirements

Sales to Implementation Handoff
Customer is Sold on PBCS Benefits
 Software licensing & annual support

 Hardware/infrastructure
COST & TIME  System patches and upgrades
AGILITY  Adoption is easy

 Get the latest and greatest features
 Elastic: grows with the business
 Accelerates time to value by focusing
INNOVATION on the application not infrastructure
 IT won’t mind

Planning On-Premises and Cloud Offering (1/3)
Features and Functional Differences
Application Management Hyperion Planning PBCS
Access Control Hyperion Shared Services Oracle Cloud Identity Management
Native Directory used for provisioning Native Directory used to support artifact
information and to support artifact migration and group-based access control to
migration artifacts
User Directory Configuration and Functional users are permitted to manage Each PBCS instance is supported using an
Management user directories identity domain (a slice of Oracle Cloud
Identity Management)
Does not support the configuration

of additional external user directories
Only the Identity Domain Administrator

can manage the identity domain for the
service.
Delegated User Management Supports delegated user management, Does not support delegated user
which enables the creation of a hierarchy of management
administrators
Custom Roles Supports the use of custom roles that Does not support the use of custom roles
aggregate application-specific roles

Product Components Hyperion Planning PBCS
Planning Supports multiple Planning applications at a Supports only one Planning application at a
time time
Supports optional modules such as Capital Supports core Oracle Hyperion Planning
Expense Planning, Project Financial only; no modules
Planning, Workforce Planning, and Public
Sector Planning and Budgeting
Essbase Permits direct access Does not permit direct access to Essbase
Essbase Administration Services is available Essbase Administration Services is not

available; however, key features are available
in Calculation Manager
Financial Reporting Uses Java Monitoring and Management Does not permit changing Oracle Hyperion
Console (JConsole), which is available to Financial Reporting properties using
Financial Reporting Administrators, to define JConsole
and manage Financial Reporting properties
Users are not allowed to output book to static
HTML websites

Tool Hyperion Planning PBCS
EPM Architect (EPMA) Can be used for Planning PBCS does not use EPMA
Financial Data Management Enterprise Drill back capability available through Drill back capability available to all sources
Edition (FDMEE) adapters supported by FDM through flat files using the
Data Management features within PBCS
Data Relationship Management Supported through flat files and EPMA Supported through flat files and automation to
PBCS
Essbase ASO ASO is part of Hyperion Planning and needs ASO is part of PBCS application and included
to be separately licensed in the pricing
Reporting Financial Reports is part of Hyperion Financial Reports is part of PBCS
Planning license subscription
Smart View Smart View for Office is part of Hyperion Smart View for Office is included in PBCS
Planning license subscription
Other Oracle Data Integration, flat files, and Excel Flat files, and Excel extracts
extracts

November 2014 Patch .601
 Enhanced Automation Utility (EPM Automate)  Benefits
 New Inbox and Outbox for PBCS – Cross Browser Tablet Friendly Interface
 Simplified Tablet Friendly User Interface – Powerful end user features
– Dashboards – Automate PBCS routines
– On The Fly Report Creation – More self learning options
– Drag and Drop Ad-hoc
– User Defined Formats
– Scheduler
– Admin Console
 Nightly LCM backup includes application data
 Member on the fly without modules
 New Videos and Tutorials
 Browser Support: Safari, Chrome, IE11, FF31

Implementing a Cloud Solution – What’s Different?
– Handoff from Sales to Implementation
Topics – Features and Functional Differences between On-
Premises and In the Cloud
Technical Information – About the Oracle Cloud
Environment
– Deployment
– Security
– Maintenance and Patching

Oracle Cloud Service Data Centers
Linlithgow
Chicago
Japan
Amsterdam
London
Ashburn
Singapore
Austin
Sydney
Defense in Depth 24x7 Monitoring and State of the Art 15,000 Global Support 99.5% Availability
Security & Compliance Support Facilities Personal, 27 Languages Power & Cooling

Deployment EPM Copy FR Studio SmartView Browser
Model HTTPS HTTPS HTTPS
Load Balancer
 Each Planning Service
OHS/OAM
deployment serves a
FMW Home
single tenant
Planning
Instance Home
 OPC Services are shared IDM
between tenants Data
Database Directories
Planning
Component
OPC
Components
Oracle Cloud Physical Data Center Security
 Access cards required
and inventoried nightly
 Multiple security zones
and “Man Traps”
 Biometric scanners
 24 x 7 video surveillance
 Customer tours
available

Oracle Operations Staffed with 100% Oracle Employees
 Platform Maintenance  Security Team

 System Upgrades  Regulatory Compliance
 Network Issues Access to  Chief Privacy Officer
 SLO Guarantees Systems Only Audited By:
For:
Ops
Staff
 Qualifications
 Policies  Background Checks
 Processes Governed By: Must Have: inc employment
 Laws & Regulations Referral Checks
 Code of conduct and  Privacy and Legal
ethics Training

Security Configuration
 All users are in IDM and are managed via IDM Console.
 Customers can also create Native groups inside PBCS.
 Provisioning is done automatically based on roles in IDM.
– Security UI in shared services is customized to only show what is needed
for PBCS.
Oracle Cloud Hosting and Delivery Policies: http://www.oracle.com/us/corporate/contracts/cloud-hosting-delivery-policies-1881437.pdf
For security considerations and best practices for Oracle Cloud customers, see Getting Started with Oracle Cloud Release 13.2, Chapter 7
Securing Oracle Cloud: http://docs.oracle.com/cloud/latest/trial_paid_subscriptions/CSGSG.pdf

What kind of changes will go into a patch
 Patches can include any software change as long is it is not requiring

the customer to do any level of training on their side and customers
can finish their workflows the same manner they did before the patch
was applied.
– For example, new options can be added to menu items in a patch but
menu items cannot be renamed, removed to moved to a different location
on the screen.

Process for Patching and Upgrading (1 of 2)
Patching Upgrades
 Patch Bundles are staged monthly: 1st Friday  Availability of new version announced in Cloud portal
 Patch Bundles are applied based on customer-defined  Scheduled by Customer and Oracle
cadence either on 1st Friday or 3rd Friday  Upgrades planned : 3 times / year
 Recommendation for customers: Setup for 1st Friday for
test environment and 3rd Friday for production
environment
Month 1 Month 2
Week 1 Week 2 Week 3 Week 4 Week 1 Week 2 Week 3 Week 4
Test
Monthly Patch
PB to Test PB to Prod PB to Test PB to Prod
Bundles (PB)
Production

Process for Patching and Upgrading (2 of 2)
Scheduling a patch to be applied

How to Build Out a Planning Solution as a Cloud
Service
Topics – Following Design Best Practices
– Reviewing How to Get Started
– Setting Up and Managing Cloud Users and
Administrators
– Creating a Planning Application
– Managing Integrations and Source Data Loads
– Using Smart View
– Performing Essbase Administrative Tasks
– Using Financial Reporting

What are Design Best Practices
for Implementation?
 Process
 Customer Expectations
 Business Requirements

Planning Design Best Practices
Follow typical project management guidelines, but closely align with PBCS benefits
messaging (handoff from Sales to Implementation):
1. Requirements – Getting Started
a) Review business processes, company financial statements, key revenue and expense areas
b) Gather existing spreadsheets
c) Gather reporting requirements
d) Gather planning and forecast requirements
e) Plan data sources
2. Design – Planning Your Application
a) Establish the goals, key objectives, and scope of the implementation
b) Design dimensions
c) Design calculations
d) Determine revenue and expense requirements and drivers
e) Determine the approval process
3. Putting it All Together – Application Wizard

Managing Rapid Deployment Scope
 Goal is ~4-8 week deployments

 Identify core requirements to meet immediate needs
 Review Design questions with Client in advance of Design Session
– ~2 weeks prior to Design Meeting
– Allow them to get answers ready for design decisions rather than debating
them during design meetings
– Have client bring examples of calculations, reports, data extracts, etc. to
design meetings or even share them beforehand
 Advanced preparation will enable more efficient Design Sessions

Continued
 Identify critical Forms, Reports, and Calculations to meet core

requirements
– Avoid overly complex requirements for initial deployment
 Commit to limited scope and avoid “Scope creep”
– Avoid veering off from simple requirements to more detailed requirements
during initial deployment
– Add additional requirements to subsequent phases of deployment

Continued
 Use a “Phased” approach to deployment

– Quick “Win” now
– Learn lessons for more efficient, future deployments enabling more
complexity in similar timeframe
– Expand the deployment as-needed
 Focus on Phase 1
 Start simple and add detail later

High-level Project Plan

Rapid Deployment Tools & Tips
Tools
 Flat File Import/Export

– Dimensions
– Data
 Smart View Admin Extension
– Load dimensions directly into Hyperion Planning from Smart View
 Admin Tutorials
– Best Practice Design guide
– Tutorial Vignettes for Admin tasks

Tools Continued
 Application Build Process Task List

– Build Phase
 Structure, Forms, Business Logic, Task Lists, Reports, Security,
Process Management
– Testing Phase
 Unit & System Testing
– Rollout Phase
 Training, Documentation, Application preparation

Tools Continued
 Application Monitor
– Entire Application
– Types of Artifacts (e.g. Forms, Planning Units)
– Individual Artifacts
 Design-time & Run-time Monitoring
– Identifies design flaws and suggests fixes
– Prevents Users from executing actions if design flaws are not resolved

Tips
 Leverage Substitution Variables & Run-time Prompts

– Forms, Calcs, & Reports
 Leverage “Calc Flag” Concept for identifying forecast/planning periods
 Limit detail to key decision-making information only
– Minimize number and size of Dimensions
 Limit Form usage as Reports
– Ease of use
– Faster to build

Feedback and Questions
 What other challenges/bottlenecks prevent Rapid Deployment?

 Other questions, thoughts, or concerns?
 Commitment to Rapid Deployment for PBCS

Service
Administrators

Certification Matrix for PBCS R13.2
Client Software
 Internet Explorer 9, 10, 11 (Version 9 and 10 are not supported in Compatibility

View mode)
 Firefox ESR 17, 24, 31
 Google Chrome 29 and later on Android devices
 Apple Safari 6 on Apple iPad
 Smart View
– Smart View 11.1.2.5+
– Microsoft Office 2007, 2010 or 2013
– .NET Framework 4.0
Note: .NET Framework 4.5 is required to install Oracle Smart View for Office from Oracle Planning and Budgeting Cloud Service without saving the
installer locally.
Using Oracle Planning and Budgeting Cloud Services > Prerequisites: https://docs.oracle.com/cloud/latest/pbcs_common/CSPGS/ch01s05.html

Browser Requirements
 Firefox or IE
– IE
 Details are on the next slides
– Firefox ESR
 http://www.mozilla.org/en-
US/firefox/organizations/all.html then choose your
language and install
 Firefox requires Remote XUL Manager Add-on,
available at https://addons.mozilla.org/en-
US/firefox/addon/remote-xul-manager/
 After installing Remote XUL Manager, in Firefox go to
Menu Tools > Web Developer > Remote XUL
Manager and add planning.us0.oraclecloud.com then
click the X after the entry has been added

IE9 Settings (1 of 4)
 Within Internet options

– Open ‘Trusted Sites’ within Security Tab
– Add the https address for the pod




Internet Options (for Firefox and IE)
 You may need to adjust security settings. Be sure they are set to Medium-High
or lower. The Internet Options are accessible via the Control Panel or via the
Tools menu in IE. They apply to Firefox as well are not exclusive to the
browser, but are for the OS.

Troubleshooting web page loading
 If any web pages won’t load, clear your browser’s cache
– http://support.mozilla.org/en-US/kb/how-clear-firefox-cache
 At the top of the Firefox window, click on the Tools
menu and then select Options
 Select the Advanced panel
 Click on the Network tab
 In the Cached Web Content section, click Clear Now.
– http://answers.microsoft.com/en-us/ie/forum/ie9-windows_vista/how-
to-clear-the-cache-and-cookies-in-ie-9/3f44ced3-d81a-4745-b070-
3e748cebc937
 Open IE, Press F12, then Ctrl + R
 A pop-up "Are you sure you want to clear browser
cache" pops up
 Select Yes

Welcome Email Sent After Pod is Provisioned

My Account versus My Services
Oracle Cloud provides two applications for monitoring and operating services:
 My Account: Let’s you monitor the status of services for an entire account, across multiple data
centers and identity domains. My Account displays information about active, expired, and
pending services. You use My Account to activate your services and to view the status calendar.
If you are also a buyer, you can access Oracle Store from My Account.
 My Services: Lets you monitor and operate all active services within a single identity domain.
You use My Services to perform all operating tasks, after your services are activated.

Sign in to the pod with your credentials
Note: Copying the temporary password from the Oracle Cloud email works in the initial cloud sign on screen
but not in the Password Management screen. The workaround is to backspace once at the end of the old
password box since an extra space is added.

My Services - Dashboard

My Services – Application Details
 Details for the service

- Location
- Metrics
- Ability to launch service (opens workspace URL)
 Additional information
- Start date
- CSI #
- Status,
- etc.
- Note: SFTP info is for downloading data after
termination of service

My Services - Users
 To access Users tab, user must have the Identity Domain Administrator Role (ID admin)
 What you can do from My Services User Page:
- Add users and assign roles
- Bulk import users
- Bulk assign roles

My Services - Notifications
 Used to show Notifications for all cloud services

 “Show” filter can be used to restrict which services apply
 For PBCS, expected to be blank unless the application is under unplanned Blackout by Cloud Ops.
This does not include the Daily Automatic Maintenance Window.

Accessing the PBCS Landing Page
 To access, Menu: Navigate > Planning

Administration
 This is designed to be the starting point
to access PBCS. It duplicates some of
the menu items but has a lot of new
functionality.

Planning and Budgeting Cloud Service Workspace
Using the Navigate Menu
You can access the following from the Navigate menu:
 Applications: Accesses Planning components. Applications is displayed only when a
user has rights and applications are available.
 Explore: Enables you to organize, search for, or assign access permissions to files.
When you select Explore, the view pane shows folders, and the content pane shows files
and folders.
 Administer: Enables you to manage Workspace Settings, Reporting Settings,
Annotations, Planning Administration, Data Management, Calculation Manager, and
Application Management.
 Schedule: Enables you to schedule batches.
 Open Items: Provides easy access to artifacts that you currently have open in Planning
and Budgeting Cloud Service Workspace.

Planning and Budgeting Cloud Service Workspace
Other Tasks
You can access the following tasks from the File menu:
 Create Documents – Oracle Hyperion Financial Reporting book or batch.

 Open and print Documents or URLs
 Set User General Preferences – change default settings for displaying document paths,
prompting to save files, setting accessibility mode, and displaying email addresses.

Introducing New Simplified User Interface
PSU.601 November 2014
 An alternative interface to PBCS for accessing common
planning tasks
 Does not directly impact existing customers or new PBCS
customers
 Existing or New Customers URL will still go to existing
workspace UI
 Existing customers are not required to use new UI for
existing features
 Workspace Landing Page has a new icon for accessing
simplified UI if users want to use this new UI
 New features in November patch will be available only
within Simplified Interface
 New Simplified UI will have a navigation to existing UI
features that are not yet exposed within the simplified UI
See videos and tutorials for PSU.601 that illustrate the new Simplified Interface: https://www.youtube.com/playlist?list=PLdhsk2_nr_0Xj7f0OYj-0e1nO6j4VtVdB

Simplified User Interface
 Mobile and desktop friendly

 Multiple OS and Browser support
 Consistent across Oracle Cloud services
 Multiple themes and user defined
background
 Announcements and custom profiles
 Minimalistic yet resourceful
 End user and admin separation points
 Benefit
– Easier LOB adoption with intuitive
mobile friendly interface

Simplified Application Creation
 Get up and running quick

 Choose based on simple and complex use
case
 Create full blown sample for familiarity
 Out of box best practice guide
 Product tour videos
 Functional tutorial videos
 Out of box rolling forecast application

Built-In Analysis And Reporting: Dashboards
 Dashboards within planning application

 On the fly mash-up using forms, adhoc
grids with free form text and urls
 No data export needed. Uses the same
data you plan on
 Supports all data types – text, numeric and
url
 Benefits
– Tablet friendly
– Business User focused
– Easy and quick creation

Built-In Analysis And Reporting: Ad-hoc
 Simplified mobile friendly ad-hoc

– Drag and Drop | Pivot and Zoom
 Analysis in same Planning application
 Benefits
– Analyze and get to root cause quickly
– User friendly pivots and icon ribbons
– Power user and end user collaboration
– Analyze information in Excel, desktop
or mobile

Built-In Analysis And Reporting: Reports
 Simplified report creation & consumption

 Create on demand by users
 Benefits
– Use ad-hoc as an optional authoring tool
– Business user friendly
– Easy and quick creation
– No data export needed

Unified Admin Console
 Visual application overview

 Plan Type and dimension management
 Import export dimensions and data
 Job and schedule management
 Benefits
– Ready visibility to application usage
– Simplified management of artifacts

Job Manager & Scheduler
 Create and manage routine jobs

– Rules, import, export, refresh etc.
 Schedule routines for automation
 Benefits
– Mobile friendly
– Sequence batch jobs
– Manage lights out automation

Online Academy
 Getting started guides

– For admins and end users
 Best practice guide
 Functional Videos and Tutorials
– Overview videos
– Deep Dive walk through tutorials

Delete Application
If one exists

Create Demo Application
 Click the Create Application icon then choose Demo Application
 Wait for the application to be created (takes several minutes)

Launch the app
Using Standard Interface

Launch the app
Using Simplified Interface
See videos and tutorials for PSU.601 that illustrate the new Simplified Interface: https://www.youtube.com/playlist?list=PLdhsk2_nr_0Xj7f0OYj-0e1nO6j4VtVdB

Lab Exercises #1 and 2
Navigate PBCS Workspace

Walk Through Vision Demo
Application

Service
Administrators

User Management
Planning On-Premises and Cloud Offering Differences
 For PBCS, Oracle Cloud Portal is used for user management rather than
Shared Services Console
 Shared Services Console is only used for native security and for ACL
 For PBCS using the My Services application, the identity domain administrator
manages users and their roles in the identity domains that s/he has been
assigned to manage
– The service administrator can be the same person as the identity domain
administrator
– If you are assigned as the identity domain administrator for more than one identity
domain, you must sign in to each identity domain separately to manage users and
roles in that identity domain.

Predefined PBCS Roles
Role Name Description
Identity Domain Creates users and assigns them to roles.

Administrator Not a functional role; it does not inherit access privileges granted through functional roles.
Manages both the test and production instances of the service of the identity domain.
Service Name Performs all functional activities in Oracle Planning and Budgeting Cloud Service related to creating
Service Administrator and administer Planning application and service components.
Service Name Views and interacts with data: create and maintain forms, Smart View worksheets, business rules,
Power User task lists, and Financial Reporting reports. Controls approvals process, performs actions on
Planning units with write access, and assigns owners and reviewers. Creates and saves Smart
Slices.
Service Name Enters and submits plans for approval, analyzes forms using ad hoc features, and controls the
Planner ability to drill through to the source system.
Service Name Views and analyzes data through forms and any data access tools.
Viewer
To create unique role names that distinguish the roles belonging to a specific service (identity domain), Oracle Identity
Management prepends the service name to the role names.
 Roles belonging to the test instance are distinguished by appending -test to the service name.
See Using Oracle Planning and Budgeting Cloud Service, Appendix C Mapping On-Premises Roles to Oracle Planning and Budgeting Cloud Service Roles:
http://docs.oracle.com/cloud/latest/pbcs_common/CSPGS.pdf

After Signing In, Admin Navigates to User Tab

Click Add

My Services - Security: Add User
 Include first name, last name, email address then (optionally) assign user name in place of email address
 Choose appropriate role(s) to assign
- Identity Domain Administrator role allows access to manage users
- Roles with …-test… are for the test pod
 Oracle Cloud will email user with message similar to one above.
 Admin needs to send users the URL to the system since it is not included in the email from Oracle Cloud (covered in
the Using PBCS documentation)
 Upon first sign on user will change password

On First Sign In, User is Asked to Change Password
Note: Copying the temporary password from the Oracle Cloud email works in the initial cloud sign on screen
but not in the Password Management screen. The workaround is to backspace once at the end of the old
password box since an extra space is added.

My Services - Users: Import Users
 Using Import button, an ID admin can create multiple users at one time
 Text file should include header with First Name, Last Name, Email and then one row per user
 After file is processed, all ID admins will receive email with results of import (can take up to a few hours)
 Oracle Cloud will also email each user with message similar to one when users area added one at a time
 ID Admin needs to then grant roles to each. This can be done one at a time (click manage roles) or in bulk (see next
slide)
 Admin needs to send users the URL to the pods (production and/or test) since they are not included in the email from
Oracle Cloud (this is covered in the Using PBCS documentation)
 Upon first sign on, each user will change password

My Services - Users: Bulk Role Assignment
 The Email above is example of what all ID Admins receive. If there was an issue with creation of any users the details would be
included.
 ID admin then opens the CSV file and saves a copy for each of the roles they want to assign. ID admin then ensures that each file
includes only the header and the users for the specific role. In this example there is only one user with one role.
 After file is processed a message shows how many users were batch assigned the role
 Admin needs to send users the URLs to the pods (production and/or test) since they are not included in the email from Oracle
Cloud (this is covered in the Using PBCS documentation)
 Upon first sign on, each user will change password

My Services - Users: Additional Notes
 SFTP Users = used to download data after service is terminated

 Custom Roles = not used with PBCS
 Identity Self Service = used to change password or challenge questions. If a user does not have the ID Admin role this
is the only tab they can use.

User and Role Management Actions

My Services - Security
Demo
Service
Administrators

Creating a Planning Application
Workflow
Step 1: Create Application Structure
Step 2: Load Metadata
Step 3: Load Data
Step 4: Create Forms Folders and Forms, and Assign Access
Step 5: Set up Task Lists and Tasks, and Assign Access
Step 6: Create Reports
Step 7: Create Business Rules to Transform Data
Step 8: Create Documents
Step 9: Run Diagnostics

What are the Metadata and Data
Load Tools available for
On-Premises?
 Outline Load Utility

 Planning Outline Load
 ODI Adapter for Planning
 FDMEE
 EPMA

Application Creation
 For PBCS, in Application Wizard

– Can create only one Planning application
– Allowed to name first BSO and ASO plan type
– Do not create data sources linking the relational database and the Essbase server
 Use Plan Type Editor (same functionality as On-Prem)

– Manage plan types: delete, rename, add
– Add Aggregate Storage database to a Planning application
 You are allowed up to three generic plan types total and one ASO database for each BSO database plus
one additional ASO database for consolidation purposes.
 For an ASO database type, you must specify an application name to contain the Essbase database since
an ASO database must reside in its own application.
 When creating ASO plan type, ensure that all ASO applications are unique across the enterprise.

PBCS: Create Application Structure
1. On the Landing Page, click Create Application, and then
New Application.
2. Enter or select application details using the application
creation checklist as a guide.
– Name must be <=8 characters with no spaces or special characters.
– Because the locale of Oracle Cloud servers is English (US), you
must enter application names using English characters. If you are
using a browser locale other than English and a non-English
keyboard, switch to English (US) before entering the application
name.
3. Set up Currency and Calendar.
4. Define required dimensions. An application must contain Year,
Time Period, Scenario, Version, Account, and Entity
dimensions. Custom dimension is optional.
– You have the option to upload the members of Scenario, Version,
Account, Entity and Custom dimensions from metadata files
(comma-separated value files).
5. Click Create.

Lab Exercise #3
Application Wizard and New

Application Creation Task List

Service
Administrators

Custom Dimensions and Metadata Setup
 For PBCS, metadata setup options:
– Application Wizard: Either manually enter member names or set up Account,
Entity, and custom dimension members by importing from metadata files
– Import and Export > Import Metadata from File: Import metadata or to perform
incremental updates from the source system (if needed, create a new dimension on
import)
– Import or update Planning dimensions using Smart View for Excel using the
Planning Admin Extension utility

PBCS: Metadata Flat File
 For each dimension for which you want to import members and their properties, create a
metadata flat file in .csv format
 Flat file format:
– A header record as the first line in the file: List the dimension and any member properties used by subsequent
metadata records. Properties that are not included are inherited from the corresponding parent's default property
value. List properties in any order, as long as the subsequent metadata records are in the same order.
– After the header record, a list of metadata records: Each metadata record contains a comma-separated list 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.

PBCS: Load Metadata
1. Prepare the files from which metadata is to be imported. You need a
metadata file for each dimension that you want to load into the application.
2. Select Administration, then Import and Export, and then Import Metadata
from File.
3. In Dimension to Import, select the dimension to load from file.
4. In Metadata File to Import, select the file in which you defined the metadata
for the dimension.
5. Under Options, select Database Refresh. Select additional options as
needed.
6. Click Validate to verify that the settings are acceptable.
7. Click Run.

Data Loading
 For PBCS, data loading options:
– Planning Application Screens / Web Interface: Load data from flat files
 Use Case: Load data directly in Oracle Hyperion Planning and native Oracle
Essbase formats
 Example: Excel file that does not require mapping
– Data Management: Load delimited data files
 Use Case: Load data in any format and then map it to a Planning application.
Data that you want to load reflects relationships. Drill through to the application
from which the data was sourced.
 Example: Data from ERP source systems and requires mapping

PBCS: Load Data from Flat File
Two data import file formats:
 Planning
– Select the Dimension into which to load data, whose member fields correspond to
the header record in the data file.
– Specify Driver Members specified for the import dimension. If you leave this field
empty and you specified import and driver members on the Administration Data
Load Settings window, those settings are used for the import.
 Native Essbase
– These files can be formatted in either Cell list or Column list format. Cell list format
specifies a single cell value for each record, whereas Column list format specifies
multiple cell values for each record.

Loading Data Using Planning Screens
1. On the Landing Page, click Launch
Application.
2. Select Administration, then Import and
Export, and then Import Data from File.
3. Specify settings in Import and Export.
4. Click Validate to verify that the settings are
acceptable.
5. Click Run.
6. To determine that the load process completed
without errors, click View Status after the
process is complete.

Import/Export Metadata and Data Jobs
Simplified Interface
On the Home page, click Console. On the
Application tab:
1. Click Inbox/Outbox Explorer. Upload files to the
Planning Inbox/Outbox and download files from the
server to your local computer. You use these files
to schedule import and export jobs.
2. Click Dimensions to Import or Export metadata.
3. Click Actions to Import Data and Export Data.

4. Click or tap the Job icon to schedule import
and export jobs.

Source Integration in PBCS
Supports Seamless Metadata and Data Integration
Data & Metadata
Meta
data
Oracle EBS,
PeopleSoft, JDE, Fusion
APPs, SAP R/3 Web Interface
Flat Planning & Budgeting
Data Warehouse File Financial Reports
Data Mart Cloud Service (PBCS)
Data
Microsoft Office
Other
Systems
Drill-Through (no write back to source)

Managing Integrations
For PBCS R13.2 PSU.601, Data Management support:
 Includes version 11.1.2.3.510 of FDMEE:
– Multi-period data loading
– Excel template data loading
– EPM Copy with data load rule parameter
 Only handles data; does not handle any metadata
 Supports only file-based source systems – process assumes the file has been loaded into PBCS
prior to kicking off the load job
 Does not support data write-back
 Supports drill through from PBCS back to source
– Can drill back directly to any source as long as the flat file is configured to contain the drill back URL to that
source (any source that you can drill to with an HTTP URL can be your source in Data Management)
– Need to be in a network where the source landing page is accessible when running PBCS since typically you
are drilling back to a secure source behind a firewall

Process Overview: Importing Data
Using Data Management (same as On-Premises)
1. Export data from the source system to a text file (fixed width file or a delimited file, e.g., a .csv file).
2. Configure System, Target Application, and User Settings.

3. Register source systems (PBCS v1 currently supports only file-based source systems).
4. Register target application for use with Data Management.
5. Define import formats and locations.
6. Define the relationship between the source system data to Planning members using data load mappings.
a) Define period mappings for Year and Period dimensions.
b) Define category mappings for the Scenario dimension.
c) Create the Data Load Member mappings.
7. Define data load rules for the Location. You can create multiple data load rules for the application so that you can
import data from multiple sources into a target application.
8. Use Data load Workbench to extract data from the source system and import the data into Planning target application
by executing the data load rules.

Data Management Drill Through
PBCS 13.2
 PBCS using Data Management feature can drill back directly to any source as long as the flat file is configured to
contain the drill back URL to that source.
 For drill back to source to work, customer needs to be in a network where the source landing page is accessible when
running PBCS since typically they are drilling back to a secure source behind a firewall.
 When loading data via a file or the open interface table, you must configure the drill URL manually in the source
system definition and the import format definition. The FDMEE Drill Through URL Details white paper explains how to
set up the drill URL definition when using a file or interface table as a data source.
 To drill through to the FDMEE Landing Page, set drill region flag to ‘Yes’ when registering the target Planning
application – a drill region definition is passed to the target application, in addition to the actual data, to indicate that a
cell is “drillable”.
 To drill through to the source system, configure drill-through URL components in the source system definition and the
import format definition:
- Server Component – defined for each source system.
- Detail Component – defined automatically if using the predefined integration, or manually if using file based integration.
In all cases, you must specify the drill-through source server, and optional URL details when using file based loads.
For list of URLs for the Oracle-branded ERPs and for SAP, see HYPERION FINANCIAL DATA QUALITY MANAGEMENT ENTERPRISE EDITION (FDMEE) –
DRILL THROUGH URL DETAILS Doc ID 1636621.1: https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?id=1636621.1

Loading Single Period Files
Batch Loading into a Range of Periods
1. Create a file for each period and append the Period Name or Period Key to the file name. For Period Name, use the
FDMEE period name you defined in Period Mapping. For Period Key, specify the data format of the period key that is
appended to the file name inJAVA date format (specifically, SimpleDateFormat).
Example: Trial Balance_Jan-13, Trial Balance_Feb-13, Trial Balance_Mar-13
2. Upload the files to the Cloud Inbox folder. You can use the File Transfer Utility in command line mode, or you can
create a Windows batch file that runs the command with the parameters supplied for each line in the batch file. If you
create a batch file, then you can run this by hand from the command line prompt in Windows, or you can schedule it
with some Windows scheduling utility.
3. Define a data load rule to read in the multiple files. When you set up the data load rule, include the file name, but not
the date (example: Trial Balance_.csv). Select the option for File Name Suffix Type that you used in naming your
files, either Period Name or Period Key.
4. Define a batch to run the data load rule. When the rule is executed, it will pick up the date from the POV and then
load the files. Import from the Inbox folder can be scheduled in PBCS Data Management using the scheduling
capabilities that come with FDMEE to load the multiple files together.
For instructions, see Administering Data Management for Oracle Planning and Budgeting Cloud Service, Chapter 2 Subtopic “Defining Data Load Rule Details for
a file-based Source System”: http://docs.oracle.com/cloud/latest/pbcs_common/CSDMA.pdf

Loading Multiple Period Files
Using Multiple Period Data Load Rule
 In the Data Load Rule, specify an import format multiple period data load to load a file
containing multiple data values that correspond to different periods.
 The Import Format selected must have the same target as the Location selected in the
POV. If the import format is not specified, then the import format from the Location is
used.
 The starting and ending period selected for the rule are used to determine the specific
periods in the file when loading a multiple period data file.
 For data files containing amounts that are not for contiguous periods, explicitly map the
respective amount of columns to required periods in the data rule. When you execute
the rule, the data is loaded to the periods as specified in the explicit mapping.

PBCS: Methods to Import /Export Metadata and Data
Summary
 Metadata
– PBCS Web Interface has an import / export feature that can import and export metadata.
– Metadata can also be updated using Smart View for Excel using the Planning Admin Extensions utility.
 Data
– Import
 If the use case is simple and data loads do not have any mapping (many to one, etc.) or drill through
requirements, data can be loaded using PBCS Web interface using csv format flat files. This file format can
load into multiple periods across multiple cube intersections using one file.
 For more advanced use cases (mapping/drill through etc.) use the Data management (FDMEE) feature in
PBCS. Currently FDMEE accepts only single period file formats. FDMEE will support multi-period loads in
PBCS later in 2014.
– Export
 Use the Planning Web Interface to export data from PBCS. This is a multi-period file format. Use this to load
Planning data into any target systems.

Lab Exercise #4
Metadata and Data

Management

Service
Administrators

Smart View
 For PBCS R13.2, compatible with Smart View 11.1.2.5+
– Smart View 11.1.2.5 is backward compatible with all EPM products R11.1.2.3.x and R11.1.2.2
 Supported upgrade paths to Smart View Release 11.1.2.5: 11.1.2.x and 11.1.1.4.x
– When upgrading from release 11.1.1.3.x and earlier, Oracle recommends uninstalling Smart View before installing release
11.1.2.5.
 Includes Planning Administration and Predictive Planning Extensions – installers available from PBCS Workspace
 Smart View Extension Support
– If you are working with Smart View extensions, you must use version 11.1.2.3 or higher of the extensions. If you want to use the
Oracle Hyperion Strategic Finance Extension with Smart View 11.1.2.3, then you must upgrade to at least the 11.1.2.3 version of
the extension. Smart View 11.1.2.5 is not compatible with extension versions older than 11.1.2.3.
– You must have Oracle Business Intelligence Enterprise Edition release 11.1.1.7 or 11.1.1.7.1 to use the Oracle BI EE-related
features in Smart View.
 Parity (mostly) with On-Premises Smart View 11.1.2.5+ features
– Oracle Smart View for Office works with data sources for both on-premises providers and for Oracle Planning and Budgeting
Cloud Services
– Offline mode not available – not on par with current Planning Smart View functionality

Install Smart View
 Smart View pre-req is Microsoft Office

2007 or 2010, 32-bit with VBA installed.
 Menu: Tools > Install > Smart View
 Save the file. Note: .NET Framework 4.5 is required

to install Oracle Smart View for Office from Oracle
Planning and Budgeting Cloud Service without saving the
installer locally.
 Close all MS Office applications.
 Right click SmartView.exe and Run as

Administrator.
- If SV is already installed the installer will handle the
upgrade by uninstalling the older version and re-
installing the new version.

Configure and Use Smart View (1 of 2)
 Open Excel.
 Choose the Smart View Tab and Click
Options then Advanced.
 In the Shared Connection URL enter
https://YourInstance#.planning.us0.oraclecl
oud.com/workspace/SmartViewProviders.
 In the Formatting tab check Adjust Column
Width.
 Click dropdown next to OK and select
Save As Default.
Configure and Use Smart View (2 of 2)
 Click Panel.
 Click Shared Connections.
 Enter your credentials in the Sign In
to Oracle Cloud screen.
 In the Shared Connections panel
choose Oracle Hyperion Planning,
Fusion Edition then expand Vision.
 Open the Operating Plan Task.
 Double click 5.0 Revenue Plan >
Revenue Plan –Products task.
 You can test using Smart View by
editing a cell and click Submit Data
to change the value in Planning.
FYI – If you are using Firefox, next time you run it, you’ll be asked to add the Smart View add-on
The add-on is to support opening a Web grid in Firefox into Smart View
Install Planning Admin Extension
 In the PBCS Workspace select Tools >

Install > Planning Admin Extension.
Right-click the downloaded file and select
Run as Administrator.
 Right Click on PlanningSVExtension.msi
and select install. Once the install dialog is
displayed click the Next button.
 Select the Installation Folder and Click the
Next button to start the install.
Install Predictive Planning
 Smart View must be installed, configured for use
with your instance and closed, prior to installing
Predictive Planning.
 Menu: Tools > Install > Predictive Planning
 Save the file.
 Be sure you’ve uninstalled any previous versions
(listed as Oracle Crystal Ball in add/remove
programs).
 Run preditiveplanning.exe.
 Follow the Install Shield instructions.
 After the install is complete, open Excel, go to the
Smart View > Options tab and then Extensions to
confirm there is an entry for Predictive Planning.
Service
Administrators
Essbase Administrative Tasks
Using Calculation Manager
 From the System View, select Tools, and then Database Properties. In the Enterprise
View, select application / database.
 In the right pane, view and edit Essbase database properties
– Perform calculation tasks, checks on dimensions and members, view info on blocks, edit cache sizes, etc.
 In the left pane, right-click the application or database
– Remove locks from database objects
– Start and stop applications
– Start and stop databases
– Remove locks on objects
– Restructure databases
– Create simulations to help optimize database settings
– Clear blocks of data from databases
Calculation Manager Database Properties
Demo
Service
Administrators
Warning: Financial Reporting Studio
 Be advised that the version of FR Studio that ships with PBCS (11.1.2.3.400) is not
backward compatible with on-premises Planning.
 If you have an existing FR Studio, you will need to uninstall FR Studio prior to installing
the PBCS version.
 FR features that are specific to Essbase and HFM data sources will not be available or
exposed for FR on PBCS. If you need to use FR for on-premise Essbase and HFM
applications in conjunction with PBCS, you will need to install 2 versions of FR Studio.
 If you need to access different servers e.g., PBCS and on-premises, you have the option
to install a 2nd version of FR Studio and change the registration to switch between the
two, provided you are using FR Studio 11.1.2.3 or later.
– For details on Installing Multiple Versions of Financial Reporting Studio on a Client Machine, see
http://docs.oracle.com/cd/E40248_01/epm.1112/epm_install/frameset.htm?ch05s09s06.html
Install Financial Reporting Studio
 In the PBCS Workspace select Tools >

Install > Financial Reporting Studio.
 Save the file.
 Close all browsers.
 Uninstall FR Studio (listed as Financial
Reporting Studio in Add or Remove
Programs or Programs and Features)
 Right-click the downloaded file and
select Run as Administrator.
 During install wait for the command
prompt to close before clicking the
finish button.
Configure Financial Reporting Studio
 FR Studio login for ‘User Name’ field

requires the user’s identity domain
preceding the user name with a “dot”
separator, e.g.
‘planningdomain2.ksullivan’
 The ‘Server URL’ should not include a
port.
Workspace Access to FR Studio
 Ability to launch FR Studio from Workspace

– ‘Open in’ Studio Preview and ‘Launch FR Studio’
– Currently, user will need to authenticate into the FR Studio client when
launching or previewing from Workspace
Security Authentication Differences
Financial Reporting Studio
 When launched from the Desktop, the default example, ‘http(s)://server:port’

which is shown in the Server URL field has been removed.
– Until a valid connection is made from the Desktop or Workspace, this field will be
empty when presented.
– After that, a max of 5 unique MRU connections will be available in the drop-down list
as in other versions.
 When launched from Workspace:
– The login form will be presented.
– The ‘Server URL’ will be read-only and present the Workspace host from which it
was launched.
Security Authentication Differences
Command Line Utilities
 In ManageUserPov.properties and SchedulerJobsCopier.properties:

– The ‘AdminUser’ also requires the user’s domain preceding the user name with a ‘dot’
separator, e.g. ‘planningdomain2.ksullivan’. The ‘DatasourceUser’ does not.
– The ‘FRWebServer’ and ‘BaseFRWebApp’ URLs should not include a port, e.g.
‘FRWebServer = https://pod1.planning.us0.oraclecloud.com’ without quotes
Financial Reporting
 PBCS customers will not have physical access to the FR server. They will not be able to make configuration or
JConsole settings, or view FR server files. Therefore:
– Certain JConsole settings to be preset for PBCS customers
– Some functionality that is reliant on server access will be disabled
– FR Server logs, and other files such as Budget Book CSS files, cannot be accessed by customers
– Users are not allowed to output book to static HTML websites
 Default JConsole setting is preset in 11.1.2.3.400:
– MaxEmailAttachmentSize setting = '10000‘
 This applies to Batch Bursting, where the largest email attachment size in 10mb
 In FR on PBCS, only the Planning database connection is available when creating a new database connection in the
Workspace or in FR Studio.
– Essbase and HFM database connection types are not available.
– Only functionality related to Planning Details database connections are available
Financial Reporting Batch Scheduler
 Export as HTML Web Page’ is disabled

– This feature is dependent on customer
access to FR server CSS and other files
to customize and generate the HTML web
page.
 ‘Export to an external directory’ is also
disabled for ‘Export to PDF’ and ‘Export
to MHTML’
– This feature is dependent on customer
access to retrieve files in a specific folder
on the FR server.
Application Management
– Migrating Applications from On-Premises to Cloud
Topics Service
– Migrating Applications in the Cloud
 From Cloud Service Production to
Production/Test (Cloning)
 From Cloud Service Test to Production
– Backing Up and Restoring Artifacts from Application
Snapshots
– Using File Transfer Utility
Migrating: From On-Premises to the Cloud
 General Prerequisites
– Migrating from on-premises EPM System Release 11.1.2.1.x.
– The user performing the import operation must have the Service Administrator role
– Ensure that the application name in Oracle Planning and Budgeting Cloud Service is the same as the on-premises application name.
 Artifacts Not Supported

– Shared Services custom roles
– Enterprise Resource Planning Integrator/Oracle Hyperion Financial Data Quality Management/FDMEE artifacts
– Reporting and Analysis Annotations and Batch Jobs (Note that ACLs defined for Financial Reports are lost during migration and must
be defined manually in Oracle Planning and Budgeting Cloud Service.)
– Oracle Essbase global substitution variables (If your application has global substitution variables, convert them into application-specific
variables before migrating.)
– Workspace Pages and Personal Pages
 Applications and Modules Not Supported
– Horizontal planning modules such as Oracle Hyperion Workforce Planning, Oracle Hyperion Capital Asset Planning, and Oracle
Hyperion Public Sector Planning and Budgeting
– Oracle Hyperion EPM Architect-enabled Planning applications
Other Considerations
 Report Mapping Artifacts and ASO Cubes
– Report Mapping artifacts could have references to Essbase ASO cubes in your on-premises environment and
may fail to import into PBCS. Oracle recommends that you not select them for migration. You can manually
create an ASO cube in Planning, and then recreate report mappings.
 Business Rules
– Security access is not migrated and must be manually defined in PBCS.
– When defining security access, you may need to review and make modifications prior to migration:
 Locations: The Location tab of each business rule should always contain the specific location of the application plan
type/database and not “All Locations”. Assign each rule to only one application plan type/database.
 Launch Variable: Ensure that the Launch variable in the Variables tab of the Business Rules rule has a valid Planning location
provided in the Locations tab (Planning application specified and not Essbase).
 Macros: If there are any prompts in the macro, ensure that they have an associated prompt text.
 Location for Sequences: Ensure that the Variable tab of the sequence has the same location as the respective rule's launch
variable.
 Projects: In Planning, the Business Rules projects are migrated into artifacts called Folders. Planning does not allow duplicates of
the same artifact in multiple folders. As a result, you may need to rearrange your projects to accommodate Planning's
specifications.
Process Flow
Step 1: Migrate the Security Model
Step 2: Export Artifacts from the On-Premises Deployment
Step 3: Zip the Exported Artifacts and Upload the ZIP File to Planning and Budgeting
Cloud Service Workspace
Step 4: Import Artifacts to the Oracle Planning and Budgeting Cloud Service Production
Environment
Step 5: Validate and Troubleshoot
Steps in On-Premises Environment
 Login to Hyperion Shared Services.
 Identify On-Premises users, groups and
roles.
 Create Data Upload Files.
– Users.csv
– Groups.csv
– AssignedRoles.csv
Steps in PBCS Environment
 Login into Oracle Cloud Portal.
 Navigate to Security -> Users and click on
Import.
 Load Users.csv into Oracle Cloud Identity
Domain.
 Navigate to Roles.
 Load RoleAssignments.csv into Oracle
Cloud Identity Domain.
– Create role upload files, one for each user
type, to assign users to default Oracle
Planning and Budgeting Cloud Service
roles.
 Login into PBCS. Navigate to Navigate ->
Administer -> Application Management.
 Expand Application Groups -> Foundation
and Select Shared Services.
 On the right hand panel expand Native
Directory.
 Right click on Groups and select ‘Import
after Edit’. Load Groups.csv into Oracle
Planning and Budgeting Cloud Service
Native Directory.
Step 2: Export On-Premises Artifacts
 Login to Hyperion Shared Services as
LCM Administrator and export the
following:
– Planning Application Artifacts
 Select all the artifacts except the Report
Mappings artifact under Global Artifacts.
– Calc Manager Artifacts
– Financial Reporting Artifacts
 Select all Financial Reporting objects
associated with the Planning application.
 Select any third-party content; for example,
documents and HTML files.
 Select the UserPOVs for the users that
were migrated as part of the security model
migration.
Step 2: Export On-Premises Essbase Data
 Use Essbase Administration Services
(EAS) to export data for all the plan
types; for example, PlanType1.txt.
– Note: When the data size exceeds 2 GB,
Essbase Administration Services splits
the data into multiple files and names
them as PlanType_1.txt, PlanType_2.txt,
and so on.
 When exporting data, ensure that the
name of the data file is the same as the
plan type name.
Step 3: Zip Exported On-Premises Artifacts
 Archive the exported applications into a
single snapshot.
– Navigate to the File System folder where the
EPM System artifacts were exported. By
default, this is in
MIDDLEWARE_HOME/user_projects/epmsyst
em1/import_export/admin@native directory.
– Under the File System folder, select all the
folders that were exported and zip up the
contents using a third-party software such as
7-Zip.
– In the Parameters field, enter cu=on. This
setting preserves the Unicode paths and file
names.
Step 3: Upload Zip File to PBCS Workspace
 Login to Planning and Budgeting Cloud
Service and navigate to Application
Management.
 Upload the On-Premises application
snapshot.
 Note: You can also use the File Transfer
Utility to upload the artifacts.
Step 4: Import Artifacts to PBCS
 Navigate Application Management ->
Application Snapshots. Explore the
application in the imported snapshot one
by one.
– OnPremisePlanningAp
– OnPremiseRep
 Select all the artifacts and Import the

application one at a time.
– Products must be imported in the following
order:
a. Reporting and Analysis
b. Planning
c. Calculation Manager
Step 4: Import Data to PBCS
 Export the Essbase data artifact from
PBCS. This can be used as a template
LCM snapshot to load the Essbase
data that was exported in the On-
Premises environment using EAS.
 Navigate to Application Management>
Application Groups.
 Expand the group containing the Planning
application, and then explore the Planning
application.
 Export Essbase Data.
Step 4: Import Data to PBCS
 Download the Essbase Data Snapshot
and extract the contents of the ZIP file
to a temporary location.
 Use it as a template.
– Copy the data file that you exported from EAS
in the Essbase Data folder (Application Name/
resource/Essbase Data)
– The data exported from Essbase Release
11.1.2.1.x and copied into the Release 11.1.2.3
archive must have the same name as the plan
type.
 Archive the snapshot and upload it

back to PBCS.
 Import it using Application Management
(LCM).
 Check the Migration Status Report to ensure that the import was successful.
 Validate that Essbase data migrated correctly.
 Check that Planning application migrated successfully.
– Open Planning data forms and compare it with same data forms from the source environment.
– Verify that dimensions and task lists were migrated. Verify that the dimensions exist and contain the correct
members.
 Verify that you can view the Financial Reporting reports associated with the application.
Topics Service
Snapshots
– Using File Transfer and EPM Automate Utilities
Migrating: Applications from Cloud Service
Production to Production/Test (Cloning)
Process Flow
Step 1: Export Oracle Planning and Budgeting Cloud Service Artifacts
Step 2: Set Up the Target Environment
Step 3: Import Artifacts to the Target Environment
Step 1: Export PBCS Artifacts
Steps in Production Environment
 Navigate to Application Management > Application Groups.
 Expand Foundation -> Shared Services -> Native Directory. Select Groups.
 Expand FDM -> FDM Enterprise Edition -> Application Data -> Planning Applications. Select the Planning application
to migrate and Global Setup Artifacts.
 Expand Planning application -> Select All artifacts.
 Expand Foundation -> Calculation Manager -> Planning. Select All artifacts.
 Expand Reporting and Analysis -> Reporting and Analysis -> Repository Objects. Select:
– All Financial Reporting objects associated with the Planning application.
– Any third-party content; for example, documents and HTML files.
– AnnotationsInternalFolder––Select the annotations associated with Planning reports.
– HRInternalFolder––Expand HRInternal folder and do the following:
 Expand DataSources, and select the data sources associated with the Planning application.
 Expand HRScheduler, and select batch jobs associated with the Planning application.
 Expand UserPov, and select the User POV associated with the Planning application.
– Security
 Export
Step 2: Set Up Target Environment
Steps in Source Production Environment
 Navigate to Application Management -> Application Snapshots
 Download the folder you exported and save the archive to your local system.
Steps in Target Production/Test Environment

 Upload the archive that you downloaded from the source environment.
– Note: You can also use the File Transfer Utility to upload the artifacts.
Step 3: Import Artifacts to Target Environment
 Navigate to Application Management -> Application Snapshots.
 Import the file that you uploaded.
 The Migration Status Report is displayed. Continue refreshing the report until it is
complete.
 Check the Migration Status Report to ensure that the import was successful.
 In the target instance, do the following:
– Open a Planning data form that contains driver data and compare with a data form from the
source environment.
– Verify that dimensions and task lists were migrated. Verify that the dimensions exist and contain
the correct members.
– Verify that you can view the Financial Reporting reports, annotations, and user POVs
associated with the application.
Migrating: Applications from Cloud Service Test
to Production
Process Flow
Step 1: Export Oracle Planning and Budgeting Cloud Service Artifacts
Step 2: Set Up the Target Environment
Step 3: Import Artifacts to the Target Environment
Step 4: Optional: Refresh Production Data from Data Management
Step 1: Export PBCS Artifacts
Steps in Test Environment
 Follow same steps listed for Migrating Applications from Cloud Service
Production to Production/Test (Cloning) .
 Differences:
– Expand Planning application -> Select All artifacts except clear Essbase Data under
Global Setup Artifacts, and Relational Data.
– Export Incremental Artifacts: For example, you may add a new Planning data form, edit
a few existing forms, and modify a business rule.
 Log in to the test environment.
 Navigate to Application Management -> Application Snapshots. Right-click the
desired artifact to select Modified Since to display report showing all of the
artifacts that have been either added or modified since last exported snapshot.
 Select any artifacts that have been added or modified to export.
 If the list of changes becomes long and difficult to manage, you can re-baseline
the application by right clicking the snapshot and selecting Repeat Export.
Step 2: Set Up Target Environment and
Step 3 Import Artifacts to the Target Environment
Production to Production/Test (Cloning).
Step 4: Optional: Refresh Production Data from
Data Management
 Navigate -> Administer > Data Management.
 On the Workflow tab, click Data Load Rule.
 In right pane, verify the information, and then click Execute.
 In the Execute Rule dialog box, make the desired selections, and then click Run.
 In the left pane, on the Workflow tab, click Data Load Workbench, and then verify the
data.
Production to Production/Test (Cloning).
Lab Exercise #6
Migration: From On-Premises

to the Cloud
Topics Service
Snapshots
Backing Up Application Artifacts to a Snapshot
This procedure now includes Planning Essbase data in the snapshot. Essbase data is backed up during the
maintenance window defined by the Service Administrator.
 Navigate to Application Management -> Application Groups.
 Expand Foundation -> Shared Services -> Native Directory. Select Groups.
 Expand FDM -> FDM Enterprise Edition -> Application Data -> Planning Applications. Select the Planning application to migrate.
 Expand Planning application -> Select All artifacts. Under Global Setup Artifacts, clear Essbase Data.
 Expand Foundation -> Calculation Manager -> Planning. Select All artifacts.
 Expand Reporting and Analysis -> Reporting and Analysis -> Repository Objects. Select:
– All Financial Reporting objects associated with the Planning application.

– Any third-party content; for example, documents and HTML files.
– AnnotationsInternalFolder––Select the annotations associated with Planning reports.
– HRInternalFolder––Expand HRInternal folder and do the following:
 Expand DataSources, and select the data sources associated with the Planning application.
 Expand HRScheduler, and select batch jobs associated with the Planning application.
 Expand UserPov, and select the User POV associated with the Planning application.
– Security
 Click Export
Restoring Application Artifacts from Previous
Snapshots
 Right-click the snapshot to restore, and then select Import.
Lab Exercise #7
Snapshots – Backing Up and

Restoring Artifacts
Topics Service
Snapshots
File Transfer Utility
 The File Transfer Utility provides an alternative way to upload and download artifacts between on-premises and PBCS
environments without using the browser. It is not supported for Linux and UNIX.
 Menu: Tools > Install > EPMCopy.exe. Save the file locally and run in a Windows command prompt (cmd.exe).
 EPMCopy Parameters:
– Username—User name of the user performing the operation
– Password—Password
– Tenant—Tenant name
– From—Server path/file system path (the client path cannot include spaces)
– To—File system path/server path (the client path cannot include spaces)
– [Timeout=n]—Optional: HTTP Client connection timeout
 Specify the content to upload and download:

– FROM and TO are defined as a combination of: POD URL + files + service + filename
 POD URL is your pod URL
 Files is the mandatory keyword to specify the file transfer
 Service is the keyword used to specify the following:
– URL/files/lcm—Path to Application Management content
– URL/files/inbox—Path to Data Management content
 File name is the name of the uploaded file in PBCS
– Examples:
 EPMCopy username=XX password=YY tenant=ZZ From=c:\planapp1.zip To=“https://URL/files/lcm/upload1”
 EPMCopy username=XX password=YY tenant=ZZ From=c:\fdmdata.csv

To=“https://tenant1.planning.oraclecloud.com/files/inbox/cldata.csv”
EPM Automate Utility
The EPM Automate Utility enables Service Administrators to remotely perform Oracle Planning and Budgeting Cloud
Service tasks. It enables Service Administrators to automate the following repeatable tasks:
 Import and export metadata
 Import and export Planning application data

 Refresh the application
 Run business rules on data
 Copy data from one cube to another; typically, from a BSO cube to an ASO cube or from a
 BSO cube to another BSO cube
 Upload files into Oracle Planning and Budgeting Cloud Service repository
 Download files from Oracle Planning and Budgeting Cloud Service repository
 Export and import application and artifact snapshots using Application Management
 List the files in the Oracle Planning and Budgeting Cloud Service repository
 Delete files from the Oracle Planning and Budgeting Cloud Service repository
EPM A Automate is currently not supported for Linux and UNIX.
See Using Oracle Planning and Budgeting Cloud Service, Appendix B Using the EPM Automate Utility:
http://docs.oracle.com/cloud/latest/pbcs_common/CSPGS.pdf
Lab Exercise #8
File Transfer Utility
Troubleshooting
– Application Monitor and Grid Diagnostics
Topics – Feedback and Problem Reporting
– MoS (My Oracle Support)
Application Monitoring
 Tune application
with diagnostics
 Carry out routine
health checks
 Ensure application
performance is
maintained
See Administering Planning for PBCS, Chapter 12 Working with Planning Application Administration, Section About Monitoring and Optimizing Performance Using
the Application Monitor: http://docs.oracle.com/cloud/latest/pbcs_common/CSPAG.pdf
Provide Feedback
 Direct feedback from the user

 Provides technical support with pertinent info
 Customer also needs to open SR
 Screen shot (privacy protected)
 System and user activity reports
My Oracle Support – Sign In
 https://support.oracle.com
• Customer should choose Portal = Cloud Support
Oracle Cloud Support – Dashboard
 Displays summary of
user SRs
 Displays summary of
company’s SRs
Oracle Cloud Support – Service Requests
 Displays list of user SRs

 Filterable by Service
Type, Service Name,
Status, Updated Date
 Clicking SR Number
opens a specific SR
Oracle Cloud Support – Manage Service Request
 Used to review, update and

close a specific SR
Oracle Cloud Support – Create Service Request
Lab Exercise #9
Application Monitor and Grid

Diagnostics
Bonus Lab
Case Study
EPM Automate
Facilitates Lights Out End To End Automation
Overview  Benefits
 Command Line Utility  Secure: https protocol for communication
 Can be installed on client  Use within client side scripts
 Remote execution of pre defined commands – Sample Scripts in documentation
 Nov 2014 patch has LCM and Planning commands  Use Windows scheduler
 Phase 2 to include FDM EE commands
Lights Out Automation Tasks
 Upload files into service repository
 Download files from a service repository
 Run Planning Jobs
– Import and export metadata
– Import and export Planning application data
– Refresh application
– Run business rules
– Copy data from one cube to another
 Export and import LifeCycle Management artifact snapshots
 List the files in the Service repository
 Delete files from the Service repository
Calculation Manager
 List of Location Aliases
 Tracking Queries
 Compacting a Database Outline
 Merging Incremental Data
 Aggregating System Generated Views
 Selecting a Compression Dimension
 Displaying Level Information
 Managing Requests
 Switching Between Desktop and Classic Modes
Data Management for PBCS - FDMEE
 Recent PBCS Patches  11.1.2.3.601

 Includes FDMEE release 11.1.2.3.510  Includes FDMEE bug fixes in release 11.1.2.3.520
 Multi-period data loading
 Clear target based on POV and then reload data
 Excel template data loading
 Override All Data:
 No scripting
 Turn on/off with option in system settings
 No calc scripts
 EPMCopy with data load rule parameter  If “on”, then prompt user before continuing

The Deployment Implementation PBCS

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

The Deployment Implementation PBCS

Uploaded by

Copyright:

Available Formats

PTS Workshop

Oracle Planning and

The Deployment: Successfully

1 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

2 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

Ideal vs. Reality

3 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

 Software licensing & annual support

COST & TIME  System patches and upgrades

AGILITY  Adoption is easy

4 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

Access Control Hyperion Shared Services Oracle Cloud Identity Management

Does not support the configuration

Only the Identity Domain Administrator

5 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

Essbase Administration Services is available Essbase Administration Services is not

6 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

7 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

8 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

9 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

10 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

Model HTTPS HTTPS HTTPS

between tenants Data

12 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

 Platform Maintenance  Security Team

13 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

Oracle Cloud Hosting and Delivery Policies: http://www.oracle.com/us/corporate/contracts/cloud-hosting-delivery-policies-1881437.pdf

14 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

 Patches can include any software change as long is it is not requiring

15 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

16 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

17 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

18 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

19 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

20 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

 Goal is ~4-8 week deployments

21 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

 Identify critical Forms, Reports, and Calculations to meet core

22 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

 Use a “Phased” approach to deployment

23 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

24 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

 Flat File Import/Export

25 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

 Application Build Process Task List

26 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

27 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

 Leverage Substitution Variables & Run-time Prompts

28 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

 What other challenges/bottlenecks prevent Rapid Deployment?

29 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

30 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

 Internet Explorer 9, 10, 11 (Version 9 and 10 are not supported in Compatibility

31 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

32 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

 Within Internet options

33 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

34 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

35 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

36 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

37 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

38 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

39 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.