Professional Documents
Culture Documents
Author:
Kathiravan Uthayakumar,
Priyanka Sharma, TransSys
Solutions
Creation Date: 28/05/2017
Last Updated: 14th JUN 2017
Version: Draft V0.3
Approvals:
Americana PMO
1
Oracle Enterprise Planning & Budgeting Cloud
Service Data Automation Manual
DOCUMENT CONTROL
Change Record
Reviewers
Name Position
Ankur Jain Module Lead
Vikas Basantani Project Manager
Distribution
Table of Contents
Document Control
Page | 2
Oracle Enterprise Planning & Budgeting Cloud
Service Data Automation Manual
Document Control........................................................................................................................................................ 2
1.Introduction............................................................................................................................................................... 4
Objective..............................................................................................................................4
2.Source System.......................................................................................................................................................... 5
3.Target Application.................................................................................................................................................... 8
4.Import format............................................................................................................................................................. 9
5.Location Creation.................................................................................................................................................... 11
Acceptance Signature................................................................................................................................................ 20
Document Control
Page | 3
Oracle Enterprise Planning & Budgeting Cloud
Service Data Automation Manual
1. INTRODUCTION
The purpose of this document is to guide the Admin User to use FDMEE integration with
Oracle Planning and Budgeting Cloud Service.
Objective
The objective of this document is to provide hands on to the Admin Users to understand the
FDMEE integration with Oracle Planning and Budgeting Cloud Service. This document can be
referred by any new person joining the department as a reference guide to do the
automation
Document Control
Page | 4
Oracle Enterprise Planning & Budgeting Cloud
Service Data Automation Manual
2. SOURCE SYSTEM
Document Control
Page | 5
Oracle Enterprise Planning & Budgeting Cloud
Service Data Automation Manual
Document Control
Page | 6
Oracle Enterprise Planning & Budgeting Cloud
Service Data Automation Manual
● Source System Summary window will appear. Source System, clearly explains
from where the data going to be moved in FDMEE, here for Eg: we have taken
Americana Application were already source system is created in the Name of File.
If need to create new source system click on the add and provide source system
name, source type and description then click save.
Below is the attached screenshot for user reference.
Document Control
Page | 7
Oracle Enterprise Planning & Budgeting Cloud
Service Data Automation Manual
3. TARGET APPLICATION
Target application is the option in FDMEE from where the source data going to target or sit in the
target application. Here for Our understanding we have taken Americana as the target
Application.
As we said already we have taken Americana application for explanation purpose. Once the
dimension is created in the application the same will reflect in the Dimension details in Target
application. Even we create new target application by choosing Add option and click save.
Here in above screen shot clearly explains the Target Application name as MR_TEST which is
given for Americana application and type as Planning.
Dimension Details:
In dimension Details, it reflects list of dimension created in the target application.
In Target Dimension class and data table column name option the contents will be
default no need to change or alter till if required.
Note: Even we create dimension here by choosing Add option in the dimension
details and then refresh Metadata option. But need to remember the same need
to be created in the application to make the FDMEE purpose successfully.
Document Control
Page | 8
Oracle Enterprise Planning & Budgeting Cloud
Service Data Automation Manual
4. IMPORT FORMAT
IMPORT FORMAT
Financials Data_Import
Non-Financials Data_Import_NF
Document Control
Page | 9
Oracle Enterprise Planning & Budgeting Cloud
Service Data Automation Manual
Import formats for Financials and Non-Financials snapshot for user reference ---
Document Control
Page | 10
Oracle Enterprise Planning & Budgeting Cloud
Service Data Automation Manual
5. LOCATION CREATION
5.1 Navigation to Location
In FDMEE we have Financial and Non-financial Import Locations for all the entities:
1) Financial Location: We have financial location with Entity code as prefix and Import as
suffix. For e g 01_Import
2) Non -Financial Location: We have Non- financial location with Entity code as prefix
and Import_NF as suffix. For e g 01_Import_NF
Document Control
Page | 11
Oracle Enterprise Planning & Budgeting Cloud
Service Data Automation Manual
Document Control
Page | 12
Oracle Enterprise Planning & Budgeting Cloud
Service Data Automation Manual
Document Control
Page | 13
Oracle Enterprise Planning & Budgeting Cloud
Service Data Automation Manual
We can do all types of Mapping for the application dimensions shown below in
the snapshot.
For example:
Explicit Mapping
Between Mapping
In Mapping
Multi Dimension Mapping
Like Mapping
Document Control
Page | 14
Oracle Enterprise Planning & Budgeting Cloud
Service Data Automation Manual
● Select Workflow tab and under Data Load select Data Load Rule tab as shown
below.
1) Financial Data load rule : We have financial data load rule for each location with
Entity code as prefix and Import as suffix. For e g 01_Import
Document Control
Page | 15
Oracle Enterprise Planning & Budgeting Cloud
Service Data Automation Manual
2) Non -Financial Data load rule: We have Non- financial data load rule for each location
with Entity code as prefix and suffix will be based on scenario dimension. For e g
01_Import_NF_Actual, 01_Import_NF_Budget
Document Control
Page | 16
Oracle Enterprise Planning & Budgeting Cloud
Service Data Automation Manual
9. PROCESS DETAILS
Process Details we will be able to see the log files its helpful to find out the Error when
status is failed.
Document Control
Page | 17
Oracle Enterprise Planning & Budgeting Cloud
Service Data Automation Manual
Document Control
Page | 18
Oracle Enterprise Planning & Budgeting Cloud
Service Data Automation Manual
Open Issues
Closed Issues
Document Control
Page | 19
Oracle Enterprise Planning & Budgeting Cloud
Service Data Automation Manual
ACCEPTANCE SIGNATURE
Document Control
Page | 20