An Oracle White Paper

January 2018

Oracle Enterprise Performance Management Cloud

Extracting YTD balances from FCCS using Data Management

 Oracle Enterprise Performance Management

Disclaimer

This document is provided for information purposes and should not be relied upon in
making a purchasing decision. The contents hereof are subject to change without
notice. This document is not warranted to be error-free, nor subject to any other
warranties or conditions, whether expressed orally or implied in law, including
implied warranties and conditions of merchantability or fitness for a particular
purpose.

THIS DOCUMENT IS NOT PART OF A LICENSE AGREEMENT NOR CAN IT BE

INCORPORATED INTO ANY CONTRACTUAL AGREEMENT WITH ORACLE
CORPORATION OR ITS SUBSIDIARIES OR AFFILIATES.

We specifically disclaim any liability with respect to this document and no

contractual obligations are formed either directly or indirectly by this document. This
document may not be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without our prior written permission.
 Oracle Enterprise Performance Management

Introduction

Oracle provides market leading EPM cloud applications, including the Financial
Consolidation and Close Cloud Service (FCCS). At this time, period to date (PTD) balances
may be extracted from FCCS, but year to date (YTD) amounts are not directly supported
when extracting data using Data Management. This white paper explains a technique to
extract YTD balances from FCCS using Data Management.

1
 Oracle Enterprise Performance Management

Overview
Data Management may be used as a method to extract data from each of the EPM cloud
services, including FCCS. Data is stored in FCCS as PTD balances, and YTD balances
are computed as part of the consolidation process. To pull YTD balances using Data
Management, there are specific setup steps that may be used:

1) Define a custom target application.

2) Define target application period mappings that includes multiple periods that the
user desires to represent the YTD balances.
3) Execute a data load rule that filters on the PTD balances for the custom period
that combines the multiple source periods.
4) Download the extract file and use as needed.

The remainder of this document explains the specific setup steps in Data Management for
this process. Please note that it is assumed that the reader of this document is familiar
with Data Management, and specific details in regards to defining artifacts like Locations
or Import Formats will not be explained.

Document References
Data Management Administration Guide
https://docs.oracle.com/cloud/latest/epm-common/ERPIA/toc.htm

Custom Application Setup

Create a custom application that can be used as the target for the extracted data.
Here’s an example of a custom application that can be used for this process:

2
 Oracle Enterprise Performance Management

This is a basic application with just entity, account, period and year. Other
dimensions may be included in the output file as needed.

Application Period Mapping

The Application Period Mapping is the artifact that allows the extract of the YTD
data by defining a date range that can be used to combine PTD data. For
example, if you want to pull YTD data for February, you need to add up the PTD
amounts for January and February. In the Application Period Mapping screen,
you define the period for February with the prior period for December of the prior
year so that all PTD data for January and February will be extracted. Here is an
example of the Application Period Mapping:

To pull YTD for an entire calendar year, the user should define an application
period mapping with the prior period key of December, and the Period key of
December in the current year.

Import Format, Location and Member Mapping

Define an Import Format with the FCCS application as the source, and the custom
application as the target. Create a Location and any necessary member mappings
for the data extract. Once completed, define a data load rule that provides the
filter for the desired data.

Data Load Rule

Define a data load rule that includes a filter for the data to be extracted, and
specify FCCS_Periodic for the View dimension in the filter. When executing the
rule, select the period for the desired YTD data based on the Application specific
period mappings entered for the target custom application. In this example, the

3
 Oracle Enterprise Performance Management

user will select Feb-19 as the period for the YTD data. The data load rule may
look something like the following:

The data load rule will extract all of the FCCS_Periodic data for the date range
specified, and then when creating the export file, the system will summarize the
data for each intersection for all source periods. So in this example, the user will
see data for Jan-19 and Feb-19 in the workbench, but the export file will contain
the combined amounts for Jan-19 and Feb-19.

Conclusion
Users can easily extract YTD balances from FCCS using Data Management
through the use of application specific period mappings that define the date range
for the YTD data. The user will select FCCS_Periodic in the data load rule filter,
and then select the desired period when running the data load rule. The system
will extract the PTD amounts for the specified date range in the period mapping,
and then summarize the data at YTD data when creating the export file.

4
Oracle Enterprise Perofrmance Management Copyright © 2018, Oracle and/or its affiliates. All rights reserved.
Cloud
January 2018 This document is provided for information purposes only, and the contents hereof are subject to change without notice. This
Author: Mike Casey and Margaret Reed document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in
law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any
Oracle Corporation
liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This
World Headquarters
document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our
500 Oracle Parkway
prior written permission.
Redwood Shores, CA 94065
U.S.A.

Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200

oracle.com