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

Integrating Fusion Financials with

Planning and Budgeting as a
Cloud Service (PBCS)
Mike Casey
mike.casey@oracle.com
Director, Product Management

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

 Safe Harbor
THE INFORMATION CONTAINED IN THIS DOCUMENT IS FOR INFORMATIONAL
SHARING PURPOSES ONLY. IT IS NOT A COMMITMENT TO DELIVER ANY
MATERIAL, CODE, OR FUNCTIONALITY, AND SHOULD NOT BE RELIED UPON IN
MAKING PURCHASING DECISIONS. THE DEVELOPMENT, RELEASE, AND TIMING
OF ANY FEATURES OR FUNCTIONALITY DESCRIBED IN THIS DOCUMENT REMAINS
AT THE SOLE DISCRETION OF ORACLE.

THIS DOCUMENT IN ANY FORM, SOFTWARE OR PRINTED MATTER, CONTAINS

PROPRIETARY INFORMATION THAT IS THE EXCLUSIVE PROPERTY OF
ORACLE. YOUR ACCESS TO AND USE OF THIS CONFIDENTIAL MATERIAL IS
SUBJECT TO THE TERMS AND CONDITIONS OF YOUR ORACLE SOFTWARE
LICENSE AND SERVICE AGREEMENT, WHICH HAS BEEN EXECUTED AND WITH
WHICH YOU AGREE TO COMPLY. THIS DOCUMENT AND INFORMATION
CONTAINED HEREIN MAY NOT BE DISCLOSED, COPIED, REPRODUCED OR
DISTRIBUTED TO ANYONE OUTSIDE ORACLE WITHOUT PRIOR WRITTEN
CONSENT OF ORACLE. THIS DOCUMENT IS NOT PART OF YOUR LICENSE
AGREEMENT NOR CAN IT BE INCORPORATED INTO ANY CONTRACTUAL
AGREEMENT WITH ORACLE OR ITS SUBSIDIARIES OR AFFILIATES.

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

 Agenda

 Overview
 Fusion GL data file extract
 PBCS file based data loading
 Drill-through considerations

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

 Overview – Integrating PBCS with Fusion GL

 PBCS V1 file based integration only

 Fusion extract via a seeded BI
Publisher report
– Additional reports or customizations possible
– Save as a CSV for easy loading

 Map into PBCS using Data

Management
– Data Management is FDMEE 11.1.2.3.000

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

Fusion GL Data File Extract

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

 Fusion GL File Extract – Step 1
 Logon to Fusion
General Ledger
 Click on “Navigator”
link
 Select “Scheduled
Processes”

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

 Fusion GL File Extract – Step 2
 Click on “Schedule
New Process” button
 Search and select
“Trial Balance” report

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

 Fusion GL File Extract – Step 3
 Enter parameters
 Click on “Output” tab

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

 Fusion GL File Extract – Step 4
 Select mhtml output
format

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

 Fusion GL File Extract – Step 5
 Click on the
“Process” when the
report completes
 Click on the “Report
Output Name” to
open the file

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

 Fusion GL File Extract – Step 6
 The report will open
in Excel
 Save in CSV format
for use in PBCS

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

 Fusion Extract – Additional Considerations

 Other reports can be created via

BI Publisher
– Knowledge of BIP and source system
schema required

 Reports can be scheduled and

emailed

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

PBCS File Based Data Loading

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

Data and Metadata Loading Overview
 Flat file based data and metadata
loading
 One method to load metadata
– Native Planning metadata feature
 Two options for Data
– Native Planning Data Load
– Financial Data Quality
Management, Enterprise Edition
 Select Data Management from
workspace menu

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

Metadata Loading
 Available only via Planning
 Flat file only
 File format is the same as classic
planning
 Members can also be entered
directly using the Planning
dimension management feature

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

Data Loading via Planning
 Flat file only
 Load using Planning UI
 Source file format is the same as
classic Planning or Essbase load file
 All data must include valid
dimensionality
– Mapping is not provided

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

Data Loading via Data Management (FDMEE)
 Flat file only
 Load Planning only
 Any file format
– Fixed width
– Delimited
 All data must be mapped from
source to target
 Robust features provided to manage
the data loading workflow process
 Drill-through to source possible if
HTTP:// landing page available and
security permitted
 Use log files available from Process
Details to investigate issues
18 Copyright © 2014, Oracle and/or its affiliates. All rights reserved.
Drill-through Considerations

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

Enabling Drill-Through to Source ERP
 Source system must have an HTTP
enabled landing page
 Current known landing pages
– Oracle EBS and Fusion
– Peoplesoft
– JD Edwards
– SAP
 Data file must contain all attributes
required for drill through
 Drill-through URL split between
server and parameter components
– Server details defined in Source System
– Parameters defined in Import Format

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

EBS Example – Data File and Import Format
 Source file fields
– Account
– Entity
– Amount
– Code Combination ID (CCID)
 Code Combination ID is required
to find account details in EBS
– Extract routine must reference the
GL_CODE_COMBINATION table
 Map CCID to Attribute1 in Import
Format
 Similar process applies to Fusion

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

EBS Example – URL Definition
 Define server URL in the source system details
– For example http://<server>:<port>
 Define the URL parameters in the Import Format
– Function, Responsibility, Set of Books and Ledger ID
– Period
– CCID
– Currency
– Balance Type
 Oracle Support will need to explain how to get
Function ID
 EBS DBA will need to provide Responsibility, SOB
and Ledger ID
 Responsibility ID of -1 will prompt user to select
 Reference the CCID that was loaded from the file
into the ATTR1 column in the TDATASEG table

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

EBS Drill-Through – Initiate from Planning
 Open Planning or Smart
View
 Select cell for drill-
through with right click
 Proceed to next step to
select source account

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

EBS Drill-Through – Select Detailed Account
 Drill Through page is
opened
 Accounts that comprise
cell from Planning are
shown
 In this example, 7 source
accounts were mapped to
the cell in Planning
 Select individual account
for drill through

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

EBS Drill-Through – Open GL Summary Page
 GL Summary Page for
specified account is
opened
 Review details, or drill
further as needed
 After initial authentication,
user will navigate directly
to page without needing to
re-authenticate
 Closing browser will
prompt user to re-
authenticate

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

Additional Drill-Through Considerations
 Drill-through URL details are provided in the Data Management
Documentation
 Columns from TDATASEG or the Import Format may be referenced
in the drill URL
 Contact Oracle Support for the Peoplesoft URL details
 Contact Oracle Support for instructions to get the Function ID for
Oracle EBS
 User must have network access to source system to successfully
drill-through.

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

Contacts
 PBCS Functionality – Shankar Viswanathan
– shankar.x.viswanathan@oracle.com

 PBCS Demo Pod Availability – Hackey Weinberger

– hackey.weinberger@oracle.com

 Data Loading and Drill-Through – Mike Casey

– mike.casey@oracle.com

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

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