Erpi Admin
Erpi Admin
Erpi Admin
Enterprise Edition
Administrator's Guide
Release 11.1.2.4.00
Updated: September 2015
Contents
Documentation Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Chapter 1. Using FDMEE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Supported Source Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
File-Based Data Loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Supported EPM Target Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Key FDMEE Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
FDMEE Application Folder Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
FDMEE Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Drilling Through . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Drilling Through to the FDMEE Landing Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Configuring Oracle Data Integrator With FDMEE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Set up the Data Server Based on the Enterprise Resource Planning (ERP) Source
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Setting up Physical Schemas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Setting up the ODI Context Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Setting up ODI to Integrate with JD Edwards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Integration Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Extracting General Ledger Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Writing Back Data from EPM Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Extracting Human Resource Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Navigating FDMEE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Task Pane Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Working with Data in Grids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
FDMEE User Interface Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Advanced Search Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Using the POV Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
iii
Administration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Predefining a List of Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Setting Up Source Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Working with Source Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Registering Target Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Selecting Source Accounting Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Assigning General Ledger Responsibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Working with Source Accounting Entity Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Working with Import Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Defining Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Defining Period Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Defining Category Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Chapter 2. Loading Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Understanding General Ledger Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Required Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Member Properties Sourced from the Enterprise Resource Planning (ERP) System . . . . . 125
Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Entity and Intercompany . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Year and Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Custom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
How Dimensions Are Processed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
How Languages Are Processed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
How Currencies are Processed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Loading Source System Hierarchies into EPM Dimensions . . . . . . . . . . . . . . . . . . . . . . 131
Defining Metadata Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Defining the Metadata Rule Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Defining Dimension Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Managing Metadata Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Chapter 3. Data Load, Synchronization and Write Back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Loading Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Creating Member Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Defining Data Load Rules to Extract Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
iv
vi
vii
viii
ix
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
11
12
Documentation Feedback
13
14
Using FDMEE
In This Chapter
Supported Source Systems ...............................................................................16
File-Based Data Loads ....................................................................................16
Supported EPM Target Applications......................................................................17
Key FDMEE Benefits .......................................................................................17
FDMEE Architecture........................................................................................20
Drilling Through.............................................................................................23
Configuring Oracle Data Integrator With FDMEE ........................................................24
Security .....................................................................................................30
Integration Process Overview .............................................................................31
Extracting General Ledger Data...........................................................................32
Writing Back Data from EPM Applications...............................................................32
Extracting Human Resource Data ........................................................................33
Navigating FDMEE .........................................................................................33
Administration Tasks.......................................................................................40
Oracle Hyperion Financial Data Quality Management, Enterprise Edition enables you to
perform the following tasks:
l
Integrate metadata and data from an Enterprise Resource Planning (ERP) source system,
data from a file, or an Open Interface table into an Enterprise Performance Management
(EPM) target application.
Drill through from the EPM target application and view data in the Enterprise Resource
Planning (ERP) source system.
Data Synchronization between EPM applicationsMoves data between EPM applications,
for example, copying data from Financial Management to Essbase for reporting.
Write back budget data to the source system from any Oracle Hyperion Planning, Oracle
Essbase aggregate storage, or Essbase block storage application.
Write back data from Oracle Hyperion Financial Management to Oracle E-Business Suite.
For information on supported EPM System versions, see the Oracle Hyperion Enterprise
Performance Management System Certification Matrix.
For FDMEE issues and workarounds, see the Oracle Hyperion Financial Data Quality
Management Readme.
15
File-based data loads that enable users to import balances from delimited or fixed-width
text files.
FDMEE supports human resource data load for PeopleSoft Human Capital Management 9.
Integration includes data load and drill through. The integration is supported for the following
SAP ERP Financial modules as well:
l
Profit Center
Cost Center
Vendor Balances
Customer Balances
In addition FDMEE provides support for Open Interface Adapter. The Open Interface Adapter
enables you to import data from any source system using the interface table.
For information on supported technologies for each source system, see the Oracle Hyperion
Enterprise Performance Management System Certification Matrix.
You can also define data load rules which determine how you want to extract or write back data
from an EPM system to a file system. For example, you may want to write back budget data.
Planning
The Planning module, Oracle Hyperion Public Sector Planning and Budgeting
Essbase aggregate storage and Essbase block storageIf Essbase has been deployed in
standalone mode, it must be registered with Shared Services because it does not work directly
with FDMEE. Planning applications that rely on the standalone Essbase application cannot
work directly with FDMEE either.
Data synchronization that enables you to easily move data between the EPM applications
irrespective of the dimensionality of the application without having to create a data file from
the EPM source application. You specify the source and target EPM application, and then
map the data. Given the powerful mapping features already available, the data can be easily
17
transformed from one application to another application. For example, synchronizing data
enables you to move data from Financial Management to Essbase for reporting.
l
Write-back support from all EPM applications (except the Accounts Reconciliation
Manger) to Enterprise Resource Planning (ERP) applications. This feature offers significant
advantages, such as writing back budgets created in Planning to Peoplesoft or E-Business
Suite ERP GL, or moving adjustment journals from Financial Management to ERP Systems
like Oracle E-Business Suite or Peoplesoft. Other target systems still need to use a custom
application framework.
18
Table 1
Folder
Descriptions
data
The data folder contains a copy of each file that is loaded by the system, and is also the root folder
for the scripts directory. Each file in this folder is assigned a unique name, and can be opened from
the Data Load Workbench by clicking an amount or from the Drill-through screen.
scripts
This is the top folder for the custom, event, and import folders. Scripts of these types are stored
in these folders.
19
Folder
Descriptions
custom
event
import
inbox
When you select the option to create a folder for every location created by the user, they are created
in the inbox. The inbox includes the batches and archivestore directory.
archivestore
batches
batches is a top level folder only and not used to store files.
openbatches
openbatches is the location where openbatch files are stored by the system. Openbatch files contain
the Point of View in the file name so that one or more files can be picked up by the system and
loaded without needing to set the POV in the user interface. This is very useful if there are a large
number of files that need to be loaded at a single time.
openbatchesml
outbox
Similar to the openbatches folder; however, these files contain multiple periods in a single file.
The outbox folder stores export files created by FDMEE, any error log files from a target application,
drill region load files, and drill load logs from the target.
archivestore
logs
Stores logs generated by the load processes in the format EPM-APPLICATION-NAME_PROCESSID.log. These logs can be viewed using the Show Log link in the Process Details page of FDMEE.
reports
The reports folder stores report output generated by the batch reporting process in PDF, HTML or
XLS. Also includes output from reports run in offline mode.
Note: To create the folder structure for applications, define the root folder in the Application
Settings screen, and then select the Create Application folders option. For example, to
run a set of scripts for a specified application, then the use of the application folders is
required.
FDMEE Architecture
FDMEE is the key application for integrating Enterprise Resource Planning (ERP) systems with
Oracle's Hyperion EPM applications. FDMEE is accessed through Oracle Hyperion Enterprise
Performance Management Workspace, which uses Shared Services to authenticate users. The
key to its integration lies within its underlying engine, Oracle Data Integrator.
FDMEE sits on top of Oracle Data Integrator and orchestrates the movement of metadata and
data into EPM applications. The application server can be deployed on multiple platforms (See
the Oracle Hyperion Enterprise Performance Management System Certification Matrix) and
20
connects with EPM applications such as Financial Management, Planning, Profitability, Account
Reconciliation Manager, and Essbase.
The ODI Agent installed and used by FDMEE is exclusively for processes launched as part of
FDMEE processing, including the FDMEE user interface, FDMEE batches, or FDMEE jobs
executed by way of a Windows or Linux batch. The FDMEE repository is for exclusive use of
FDMEE objects shipped by Oracle, or for customizations made by the customer to these objects.
The ODI agent or repository used by FDMEE cannot be used for any other purpose by the
customer. Any other ODI work needs to use a separate agent and repository.
The following diagram shows the technical architecture structure of FDMEE:
21
22
Drilling Through
FDMEE provides the framework to drill through from the EPM applications back to the general
ledger source. Drill through is not supported for human resource data. Users can drill through
to detail in the source system through FDMEE from the following products:
Note: If the source system is E-Business Suite/PeopleSoft and you have metadata rules, then the
drill region is created based on the metadata rule. Otherwise, it is created based on the
target members in the data load mappings. For Year, Period, and Scenario, FDMEE uses
audit information to create the drill region.
Note: Drill through is not supported for Financial Management journals and intercompany
transactions.
Planning
Financial Management
Note: In Smart View and Financial Reporting, you can drill through only if the data source is
23
Note: Drill through is not supported for Financial Management journals and intercompany
transactions.
When you drill through, if data was loaded by FDMEE, a landing page is displayed in a new EPM
Workspace tab or a new window. The landing page is a gateway to the data in the source system.
See Drilling Through to the FDMEE Landing Page on page 24.
based data loads work out of the box without additional ODI configurations.
1. Set up the data server based on the Enterprise Resource Planning (ERP) source system.
2. Set up the Physical Schemas.
24
SAP_SERVERSAP FICO
Expand Topology.
Select the operating data server to update, and then click Edit.
In Edit Data Servers, under JDBC Details, enter the JDBC driver in JDBC Driver.
Click Save.
Expand Schemas.
25
Click Save.
Caution!
Extensive problems can occur if you switch the Enterprise Resource Planning (ERP)
system connection information for the Physical Schema in the Oracle Data Integrator
Topology Manager after you have completed initial configuration. For example,
extensive problems can occur if you start using one physical schema (ERPTEST)
pointing to ERP Test Instance1 in the Oracle Data Integrator Topology Manager,
and then change to a connection information in this physical schema to point to
ERP Test Instance2 without first creating a new context in Oracle Data Integrator.
The correct procedure is to create two physical schemas (ERPTEST1 and ERPTEST2)
each pointing to a different ERP instance. Then, create two contexts and associate
the appropriate physical schema to the logical schema in the context.
Expand Contexts.
Enter the word GLOBAL in uppercase characters only, that is, enter GLOBAL.
Click Save.
26
b. Select the Patches and Updates tab, and then select JD Edwards Patches.
c. From JDEdwards, enter EnterpriseOne Tools Releases.
d. In Release, select All Releases.
e. In Platform, select Multiplatform.
f.
i.
Click the plus sign (+) to add Tools 9.1,* Data Access Driver to the Download Basket.
j.
Click the Item(s) hyperlink and download the tools release specific item.
Request that the JD Edwards system administrator provide you with the following files:
l
jdbj.ini
jas.ini
jdelog.properties
These files are generated when you register the JD Edwards EnterpriseOne Data Access
Driver using the JD Edwards Server Manager.
Copy the jas.ini, jdbj.ini, and jdelog.properties files from the JDE Application
Server to the EPM_MIDDLEWARE_HOME\odi\odi_misc directory.
Ensure that the security server of the jas.ini file is set up correctly.
27
c. Modifications to the .INI file password encryption can be accomplished using the
Server Manager.
d. Set the value of the following parameters under [JDBj-RUNTIME PROPERTIES] stanza
to:
resultSetTimeout=-1
transactionTimeout=-1
usageExecutionThreshold=20000
usageResultSetOpenThreshold=120000
usageTracking=false
msSQLQueryTimeout=1800000
Edit the jdelog.properties file, and set the log level as needed in all references in the file.
In a production environment, set the log level to SEVERE so that only severe errors are
reported in the log file.
Ensure that you can access the server specified in the jdbj.ini file from the ODI Server.
You can do so from the command line by issuing a ping to the server.
10 Make sure that environmental variables JAVA_HOME and TEMP are set up correctly.
JAVA_HOME is an environmental variable and points to java.exe under C:\Oracle
\Middleware\jdk160_35\bin
TEMP is a user variable and points to %USERPROFILE%\AppData\Local\Temp.
11 If you use JDE Tools 9.1.2 or 9.1.3, run the script copyfilesJDE912.bat / sh from the following
directory:
EPM_ORACLE_HOME \products\FinancialDataQuality\bin
28
If you use JDE Tools 9.1.4 or later, run the script: copyfilesJDE914.bat / sh from the
EPM_ORACLE_HOME \products\FinancialDataQuality\bin directory.
When you run the script, the following is displayed:
C:\Users\hitinstall>C:\Oracle\Middleware\EPMSystem11R1\products\FinancialDataQua
lity\bin\copyfilesJDE914.bat
"Copy required JAR Files"
1 file(s) copied.
1 file(s) copied.
"Script completed successfully"
12 If JD Edwards uses Microsoft SQL Server or IBM databases, then download the JDBC driver and copy it
to the DOMAIN HOME/lib directory.
13 Look for the following information in jdbj.ini and verify that it is in the tnsnames.ora file.
databaseType=O
serverPort=1530
name=System - 910
database=jra91dl
server=dene1lx7
physicalDatabase=
owner=SY910
lob=true
unicode=true
14 In Oracle Data Integrator, perform a JDE Test Connection with the ODI Agent.
a. From the ODI Studio, launch the Oracle Data Integrator.
b. From Physical Architecture, then Technologies, and then Oracle, select JDE_Data_Server.
Test the JDE Test Connection with the ODIAgent and not the local Agent.
c. Click Test Connection.
d. From Test Connection for, select OracleDIAgent, and then click Test.
e. From Physical Architecture, then Agents, then OracleDIAgent, right click, and select
Test.
An Information window displays when the test is successful.
f.
Search for environment in the jdbj.ini file and note the environment values:
[JDBj-BOOTSTRAP SESSION]
user=EOSVM
password=ACHCJKEBHCJKBKEEGLDDFKBCLBCDBCGBDCMJMBPGKLNO
role=*ALL
environment=PY910
29
g. From ODI Studio, then Topology, then Technologies, and then Oracle, select
JDE_DATA_SERVER.
i.
j.
i.
ii.
ii.
Security
FDMEE supports the following roles:
FDMEE Roles
Administrator
Manages applications and performs any action in FDMEE. When you log in with the Administrator role, all links are
visible in the Tasks pane.
30
FDMEE Roles
Create
Integration
Creates FDMEE metadata and data rules. If you have the Create Integration role, you can:
l
Note: You cannot run rules, view, create, edit, or delete source system registrations, target system registrations, or
source accounting entities.
When you log in with the Create Integration role, these links are visible in the Tasks pane: Data Load, Member Mapping,
HR Data Load, Metadata, and Process Detail.
Drill Through
Run Integration
Runs existing FDMEE metadata and data rules. If you log in with the Run Integration role, you can:
l
Note: You cannot view, create, edit, or delete source system registrations, target system registrations or source
accounting entities.
FDMEE users who need to extract data from Oracle or PeopleSoft Enterprise Financial Management must be granted
this role to run data rules.
When you log in with the Run Integration role, links are visible in the Workflow tasks: Data Load Workbench, Data Load,
Member Mapping, HR Data Load, Metadata, and Process Detail.
HR Integration
Runs Human Resource data rules and fills out runtime parameters. Can view transaction logs.
Intermediate 2-9
Note: FDMEE users are enabled to define mappings only to target applications to which they
have access.
Note: Planning and Essbase do not use member-level security at this time.
31
32
Note: Write-back from Financial Management is limited only to E-Business Suite General
Ledger. To write back data from an EPM to legacy or any other unsupported
Enterprise Resource Planning (ERP) systems, Oracle suggests that you extract data
to a custom target application. After extracting the data, convert the data files to a
format acceptable to those Enterprise Resource Planning (ERP) systems and import
them there.
4. Load the data into E-Business Suite or PeopleSoft Enterprise Financial Management by
running a process in Oracle General Ledger or PeopleSoft General Ledger.
Navigating FDMEE
Subtopics
l
l
l
l
l
l
l
Toolbars
Help Menu
Task Pane Options
Working with Data in Grids
FDMEE User Interface Elements
Advanced Search Options
Using the POV Bar
From EPM Workspace, you can access FDMEE from the Navigate menu. (Navigate,
Administer, Data Management)
33
Toolbars
Use the Standard toolbar is used for common Oracle Hyperion Enterprise Performance
Management Workspace features. For additional information, see the Oracle Enterprise
Performance Management Workspace Users Guide.
Help Menu
Use the Help menu to access FDMEE online help, Oracle technical support, the EPM
documentation located on the Oracle Technology Network, Oracle website, and information
about FDMEE.
Workflow Tasks
From the Workflow tab, you can integrate metadata and data from an Enterprise Resource
Planning (ERP) source system into an Enterprise Performance Management (EPM) target
application:
You can also load data from a file and other source systems.
l
Data Load
m
MetadataMetadata Rule
Other
Batch Execution
Report Execution
Script Execution
MonitorProcess Details
Setup Tasks
From the Setup tab you can administer source and target systems, specify report and batch
definitions, and manage application settings.
Available tasks:
34
Configure
m
System Settings
Application Settings
Security Settings
User Settings
Register
m
Source System
Target Application
Source Adapter
Integration Setup
m
Import Format
Location
Period Mapping
Category Mapping
Excel Interface
Logic Group
Scripts
m
Script Editor
Script Registration
Reports
m
Query Definition
Report Definition
BatchBatch Definition
35
To edit a record, click within its cell, and start typing. When applicable, you can also select
To search items in a column, enter the search value in the blank field above the column of
the value, and then press Enter. If the value is matched, it is displayed as the first item.
To cancel all changes made to a row, select the row, and then click Cancel.
Button
ColumnsYou can choose Show All to display all columns or choose individual columns to display.
DetachUse to detach the column grid. When you detach the grid, the columns display in their own window. To return
to the default view, select View, and then click Attach or click Close.
Reorder ColumnsUse to change the order of the columns that are displayed. You can select a column, and then
use the buttons on the right to change the column order.
Use to detach the column grid. When you detach the grid, the columns are displayed in their own window. To return to
the default view, select View, and then click Attach or click Close.
Refreshes the data. For example, if you submit a rule, refresh to see if the status changes from Running to Complete.
Note: Refresh does not display on the FDMEE setup screens.
Use to toggle the filter row. You can use the filter row to enter text to filter the rows that are displayed for a specific column.
You can enter text to filter on, if available, for a specific column, and then press [Enter]. For example, on the Process
Details page, to view only processes that failed, enter FAILED in the Status text box.
The Query by Example button displays on the following FDMEE setup screens: Target Application, Source Accounting
Entities, Import Format, Location, Data Load Workbench, and Process Details.
To clear a filter, remove the text to filter by in the text box, and then press [Enter].
All text is case sensitive.
Use to select an artifact on a page, such as a target application, member, or general ledger responsibility. When you click
the Search button, the Search and Select dialog box is displayed. In some cases available advanced search options
enable you to enter additional search conditions. See Advanced Search Options on page 36.
Starts with
Ends with
Equals
Less than
Greater than
Between
Not between
Contains
Is blank
Is not blank
Location
Period
Category
Data Rule
By default only the data rule assigned to the Category POV is displayed.
The Source System and Target Application are displayed as context information.
On the Workflow tab, under Data Load, select Data Load Workbench.
37
In Select Point of View, in Location, enter a full or partial string for the new location, and then click
OK.
Optional: To search on another location, from the Location drop-down, click More, navigate to the
location on the Search and Select: Location screen, and then click OK.
Optional: In Select Point of View, select Set as Default to use the new location as the default location.
When a POV selection is set as a default, the user profile is updated with the default selection.
Click OK.
On the Workflow tab, under Data Load, select Data Load Workbench.
From Select Point of View, in Period, enter a full or partial string for the new period, and then click
OK.
Optional: To search on another period, from the Period drop-down, click More, navigate to the period
on the Search and Select: period screen, and then click OK.
Optional: In Select Point of View, select Set as Default to use the new period as the default period.
38
When a new POV selection is set as a default, the user profile is updated with the default
selection.
Click OK.
On the Workflow tab, under Data Load, select Data Load Workbench.
In Select Point of View, in Category, select the new category, and then click OK.
Select Set as Default to use the new category as the default category.
When a POV is set as a default, the user profile is updated with the default selection.
Click OK.
Data in a locked POV can only be loaded when the locked POV is unlocked.
The POV Lock options include:
l
Lock POV
Unlock POV
Batch Execution
39
To lock a POV:
1
On the Workflow tab, under Data Load, select Data Load Workbench.
The POV bar is also displayed on the Data Load Rule screen and Batch Execution screen
The message: Are you sure you want to lock selected POV? Data cannot be loaded to a
locked POV. is displayed.
Administration Tasks
Subtopics
l
l
l
l
l
l
l
l
l
l
l
40
In System Settings, in Profile Type, select the specific profile to list on the System Settings screen.
All
File In addition to file-specific system settings, selecting the File profile type displays
the Create Application Folders button. This feature instructs the system to create a
folder structure in the path specified in the Application Root Directory setting.
ODIUse to set ODI password and repository connection information. When this
information gas been added or changed, you can click Check ODI Connection to view if
connection to the ODI agent was made successfully.
OtherUse to set profiles associated with an EPMA data source, User Language, User
Interface Theme, and Default Check Report.
Point-of-View
The profile type that you select determines the settings that you can add or modify on the
screen.
If
installed and configured for you. The database for Oracle Data Integrator is in the
same database as FDMEE and the Oracle Data Integrator agent deployed to the
FDMEE Managed Server. You should be familiar with Oracle Data Integrator and
review the Oracle Data Integrator documentation set before specifying or changing
the installation defaults.
Click Save.
Table 3
Profile
Type
Profile Option
All
Profile Description
41
Profile
Type
Profile Option
Profile Description
File
Application Root
Folder
Note: The Application Root Directory must be set up on the server, specified in this field, and the Create
Application Folder options must be executed as first steps when using FDMEE.
The Application Root folder identifies the root directory of the FDMEE application. This folder is located
on the FDMEE server and functions as the root folder for all FDMEE activities. Based on this parameter,
FDMEE saves log files, generated files and reports to the appropriate folder under this root directory.
Parameters must be set up on the server separately from this setup step.
When you select the File profile type, the System Setting screen displays the Create Application Folders
button. This features instructs the system to create a folder structure in the path specified in this field.
The folder structure is (with sub-folders in each):
data
inbox
outbox
Within the inbox, locations are created when they are created in the Locations option. See also FDMEE
Application Folder Architecture on page 18.
When you specify a folder at the application level, and select the Create Application Folders option, a
set of folders is created for the application that includes a scripts folder. Create scripts specific to an
application in this folder. This is especially important for event scripts that are different between
applications. If you do not set up an application level folder, then you cannot have different event scripts
by application.
If you specify an Universal Naming Convention (UNC) path, share permissions on the folder must allow
access to the DCOM user for read/write operations. Use an Universal Naming Convention (UNC) path for
the application root folder when Financial Management and FDMEE are on separate servers. Contact your
server administrator to define the required UNC definition.
If an UNC path is not entered, then you must enter the absolute path. For example, specify C:\WinOvu31e2bfie\fdmee
File
Create Location
Folder
This setting instructs the system to create a location folder in the inbox when a location is created.
Available values are Yes or No. Set this option once and do not change it. This setting is optional but
recommended.
File
Archive Mode
Specifies whether archived files are copied or moved to the archive location. Enter Copy, Move, or
None.
If you select Copy, then the file is left in the inbox.
If you select Move, then the file is copied to the archive folder and deleted from the inbox.
The folder named data is the archive folder.
When the file is moved to the archive location, it is renamed as follows:
<Process ID><Year><Month><Day>.<Original Extension>
For example, if the source file name is BigFile.csv, and it was loaded for period Mar-07 with a period
key of 03/01/2007, and if the process id was 983, then the resulting file name is 98320070301.
csv.
File
42
Excluded File
Upload Wild Cards
Specify file extensions that cannot be uploaded. Enter *.* to disallow all file uploads.
Profile
Type
Profile Option
Profile Description
File
Batch Size
Specify the number of rows read at a time from the file to memory. This parameter is mainly used for
performance. When data is loaded, this settings determines how many records are stored in the cache.
For example, when 1000 is specified; the system stores 1,000 records in cache. Similarly, when 5000
is specified, the system stores 5,000 records in cache and commit. Determine this setting by Server
Memory, and adjust as needed.
File
Specify the method for mapping bit combinations to characters for creating, storing, and displaying text.
Each encoding has a name; for example, UTF-8. Within an encoding, each character maps to a specific
bit combination; for example, in UTF-8, uppercase A maps to HEX41.
Click
Encoding refers to mapping bit combinations to characters for creating, storing, and displaying text.
Convert the encoding to UNICODE if your source file is not in one of the supported formats.
File
ODI
Encrypted
Password Folder
Specify the directory where the files that store passwords in encrypted form is located.
Specifies the Oracle Data Integrator user name used to access the Oracle Data Integrator master
repository. For example, enter Supervisor.
This encrypted password folder is used with the Update Configuration File button. See Working with
Batch Scripts on page 289.
This setting is defined automatically when ODI is configured, but you can customize it if necessary.
ODI
ODI Password
Specifies the Oracle Data Integrator database schema used to access the Oracle Data Integrator master
repository. For example, enter Master.
This setting is defined automatically when ODI is configured, but you can customize it if necessary.
ODI
ODI
ODI Execution
Repository
ODI Work
Repository
Specifies the repository where all scenarios are stored. For example, enter ERPI_REF.
This setting is defined automatically when ODI is configured, but you can customize it if necessary.
Specifies the (execution) repository which contains runtime objects (for example, scenarios). The work
repository can be linked with only one Master Repository.
For example, enter FDMEE_WORK_REF
ODI
ODI
ODI Master
Repository Driver
ODI Master
Repository URL
Specifies the URL of the server where the Oracle Data Integrator master repository is installed.
This setting is defined automatically when ODI is configured, but you can customize it if necessary.
This setting is defined automatically when ODI is configured, but it can be customized if necessary.
For example, enter jdbc:oracle:thin:@serverdatabase.oracle.com:1521:orcl.
ODI
ODI
Other
ODI Master
Repository User
ODI Master
Repository
Password
EPMA Data
Source Name
Specifies the EPMA Data Source name for the EPMA Interface Data Source.
This setting is defined automatically when ODI is configured, but you can customize it if necessary.
This setting is defined automatically when ODI is configured, but you can customize it if necessary.
43
Profile
Type
Profile Option
Profile Description
Other
User Language
Other
User Interface
Theme
The default theme contains all the colors, styles, and general-use icons that are displayed in the user
interface. FDMEE uses BLAF+ as the default value.
Other
Default Check
Report
Specify the type of Check Report to use as the default check report. The following are pre-seeded check
reports, but you can create a new one and specify it here:
l
Check Reportdisplays the results of the validation rules for the current location (pass or fail status).
Check Report Period Range (Cat, Start per, End per)Displays the results of the validation rules for
a category and selected periods.
Check Report by Val. Entity Seq.Displays the results of the validation rules for the current location
(pass or fail status); sorted by the sequence defined in the validation entity group.
Check Report with WarningsDisplays the results of the validation rules for the current location.
Warnings are recorded in validation rules and shown if warning criteria are met. This report does not
show rules that passed the validation.
Other
Default
Intersection
Report
Specify the type of Intersection Check Report to use as the default intersection check report at the system
level. Intersection reports identify data load errors and are generated as part of the data validation step
in the Data Load Workbench. The reports are available in two formats: Dynamic Column or Fixed
Column format. The Fixed Column displays up to four custom dimensions.
Other
Batch Timeout in
Minutes
When a batch job is run in sync mode (immediate processing), specify the maximum time the job can
run. In sync mode, FDMEE waits for the job to complete before returning control.
Other
Enable Event
Script Execution
Select Yes to enable the execution of application events such as before loading data (BefLoad) or after
validation (AftValidate). Select No to disable the execution of application events.
Other
SQL Server
Database Provider
Log Level
Specify the level of detail displayed in the logs. A log level of 1 shows the least detail. A log level of 5
shows the most detail.
Other
Check Report
Precision
Specify the total number of decimal digits for rounding numbers, where the most important digit is the
left-most nonzero digit, and the least important digit is the right-most known digit.
Other
Display Data
Export Option
Override All Data
Specify Yes to display the Override All Data option from the Export Mode drop-down on the Execute
Rule screen.
POV
Default POV
Location
Default POV
Period
POV
These preferences take precedence when no equivalent settings are in Application Settings or User
Settings
These preferences take precedence when no equivalent settings are in Application Settings or User
Settings.
screen.
44
Profile
Type
Profile Option
Profile Description
POV
Default POV
Category
Specifies the default POV Category. These preferences take precedence when no equivalent settings are
in Application Settings or User Settings.
POV
When this is set to Yes, other POVs (Application Level and User Level POVs) are ignored.
In Application Settings, in the Target Application drop-down, select the target application to which
the application profile applies.
Optional: To clear a setting, select the value, and then click Delete.
The value is removed but is deleted only when you save it.
Click Save.
Table 4
Option
Description
Application
Root Folder
The Application Root folder is the root folder for storing all files used to load data to this EPM application. You can use
a separate root folder for each EPM application.
Based on this parameter, FDMEE saves log files, generated files and reports to the appropriate folder under this root
directory. Parameters must be set up on the server separately from this setup step.
Selecting the Create Application Folder button instructs the system to create a folder structure in the path specified
in this field. The folder structure is (with sub-folders in each):
data
inbox
outbox
When you specify a folder at the application level, and select the Create Application Folders option, a set of folders
is created for the application that includes a scripts folder. Create scripts specific to an application in this folder. This
is especially important for event scripts that are different between applications. If you do not set up an application level
folder, then you cannot have different event scripts by application.
If you specify an Universal Naming Convention (UNC) path, share permissions on the folder must allow access to the
DCOM user for read/write operations. Use an Universal Naming Convention (UNC) path for the application root folder
when Financial Management and FDMEE are on separate servers. Contact your server administrator to define the required
UNC definition.
If an UNC path is not entered, then you must enter the absolute path. For example, specify C:\Win-Ovu31e2bfie
\fdmee
45
Option
Description
File Character
Set
Specify the method for mapping bit combinations to characters for creating, storing, and displaying text.
Each encoding has a name; for example, UTF-8. Within an encoding, each character maps to a specific bit combination;
for example, in UTF-8, uppercase A maps to HEX41.
Click
Encoding refers to mapping bit combinations to characters for creating, storing, and displaying text.
Convert the encoding to UNICODE if your source file is not in one of the supported formats.
Default POV
Location
Default POV
Period
Default POV
Category
User Language
User Interface
Theme
Set the Oracle design pattern for the applications. FDMEE uses BLAF+ as the default user interface value.
Default
Intersection
Report
Specify the type of Intersection Check Report to use as the default intersection check report at the application level.
Intersection Check reports identify data load errors and are generated as part of the data validation step in the Data
Load Workbench. The reports are available in two formats Dynamic Column or Fixed Column format. The Fixed Column
displays up to four custom dimensions.
Default Check
Report
Specify the type of Check Report to use as the default check report at the application level. The following are pre-seeded
check reports, but you can create a new one and specify it here:
l
Check ReportDisplays the results of the validation rules for the current location (pass or fail status).
Check Report Period Range (Cat, Start per, End per)Displays the results of the validation rules for a category and
selected periods.
Check Report by Val. Entity Seq.Displays the results of the validation rules for the current location (pass or fail
status); sorted by the sequence defined in the validation entity group.
Check Report with WarningsDisplays the results of the validation rules for the current location. Warnings are
recorded in validation rules and shown if warning criteria are met. This report does not show rules that passed the
validation.
Enable Event
Script
Execution
Select Yes to enable the execution of application events such as before loading data (BefLoad) or after validation
(AftValidate). Select No to disable the execution of application events.
Log Level
Specify the level of detail displayed in the logs. A log level of 1 shows the least detail. A log level of 5 shows the most
detail.
Logs are displayed in Process Details by selecting the Log link.
Check Report
Precision
46
Specify the total number of decimal digits for rounding numbers, where the most important digit is the left-most nonzero
digit, and the least important digit is the right-most known digit.
An Unlock All Location button is also available so that you can unlock all locked location. The
Lock All Locations feature is referenced in the:
l
Batch Execution
For information on locking and unlocking an individual POV, see Locking and Unlocking a
POV on page 39
In Application Settings, from the Target Application drop-down, select the target application to which
the application profile applies.
Click OK.
In Application Settings, from the Target Application drop-down, select the target application to which
the application profile applies.
Click OK.
47
Note: When the Global mode is defined, then user level profiles for the POV are not applicable.
Optional: To clear a setting, select the value and from your keyboard, and then click Delete.
The value is removed, but it is deleted only when you save it.
Click Save.
Table 5
Option
Description
File Character
Set
Specify the method for mapping bit combinations to characters for creating, storing, and displaying text.
Each encoding has a name; for example, UTF-8. Within an encoding, each character maps to a specific bit combination;
for example, in UTF-8, uppercase A maps to HEX41.
Click
Encoding refers to mapping bit combinations to characters for creating, storing, and displaying text.
You should convert the encoding to UNICODE if your source file is not in one of the supported formats.
Default POV
Location
Default POV
Period
Default POV
Category
User Language
Select the default language of the user version FDMEE user interface.
User Interface
Theme
Specify the default theme of the user version of the FDMEE user interface.
Default Check
Report
Specify the type of Check Report to use as the default check report at the user level. The following are pre-seeded
check reports, but you can create a new one and specify it here:
Default
Intersection
Report
48
Check ReportDisplays the results of the validation rules for the current location (pass or fail status).
Check Report Period Range (Cat, Start per, End per)Displays the results of the validation rules for a category and
selected periods.
Check Report by Val. Entity Seq.Displays the results of the validation rules for the current location (pass or fail
status); sorted by the sequence defined in the validation entity group.
Check Report with WarningsDisplays the results of the validation rules for the current location. Warnings are
recorded in validation rules and shown if warning criteria are met. This does not show rules that passed the validation.
Specify the type of Intersection Check Report to use as the default intersection check report at the user level. Intersection
reports identify data load errors and are generated as part of the data validation step in the Data Load Workbench.
The reports are available in two formats: Dynamic Column or Fixed Column format. The Fixed Column displays up to
four custom dimensions.
Option
Description
Log Level
Specify the level of detail displayed in the logs. A log level of 1 shows the least detail. A log level of 5 shows the most
detail.
Logs are displayed in Process Details by selecting the Log link.
Role level securityControls access to components of the user interface that each user can
access.
Report securityControls the reports that can be executed based on the report groups
assigned to a role.
Batch securityControls the batches that can be executed based on the batch groups
assigned to a role.
Custom scripts securityControls the custom scripts that can be executed based on the
custom script groups assigned to a role.
Location securityControls access to locations.
Security levels apply to users. Role and Location security levels assigned to users are compared
at runtime. If an user is assigned a level that is equal to the level assigned to the feature that the
user is trying to access, the feature is available to the user.
Click Save.
49
Table 6
Role
Description
Administrator
Create Integration
Run Integration
Runs FDMEE metadata and data rules and fills out runtime parameters. Can view transaction logs.
Drill Through
Controls whether you can drill to the FDMEE landing page, which controls drilling to the source system.
HR Integration
Runs Human Resource data rules and fills out runtime parameters. Can view transaction logs.
Intermediate 2-9
In Function, select the user interface function to which to assign user interface security.
Click Save.
In Report Group, select the report group to which to assign report security.
Click Save.
50
Click Save.
From Role, select the role to which to assign custom script security.
From Custom Script Group, select the custom script group to which to assign custom script security.
Click Save.
51
3. When the user logs in, FDMEE determines the groups assigned to the user.
Based on the name of the group, FDMEE determines the accessible locations.
4. The POV region filters the locations based on the user access.
Note: If the web services and batch scripts are used, then location security is still maintained
and enforced.
A LOCATION name row is added. When the group is saved, the Group name is in the form
of Prefix_Location_Suffix, for example, FDMEE_LOCATION_DATA.
The prefix and suffix help identify groups in Common Shared Services (CSS).
In the Security Setting Details grid, enter a description of the user group in the Description field.
When the group is saved, the prefix is prepended to the group name.
In the Suffix field, select the name of the function or rule that the user is provisioned to access.
Create Integration
Drill Through
When the group is saved, the suffix is appended to the group name.
52
Select the list of roles provisioned for the user group by selecting the appropriate roles:
l
Create Integration
Drill Through
Run Integration
HR Integration
Intermediate 2-9
The list of roles is described in Table 6, Role and Descriptions, on page 50.
Click Save.
To create users groups in mass for the location, click Maintain User Groups.
Click Save.
In some cases, you have multiple general ledger or human resource source systems. You can use
FDMEE to extract data and metadata from any instance.
For information on the source systems that FDMEE supports, see the Oracle Hyperion Enterprise
Performance Management System Certification Matrix.
Before you begin using FDMEE, you must register your source systems. Follow this process:
1. Register a source system. See Registering Enterprise Resource Planning (ERP) Source
Systems on page 53.
2. Edit source system settings as necessary. See Editing Registered Source System Details on
page 56.
For information on removing a registered source system, see Deleting Registered Source
Systems on page 55.
Note: For information on viewing FDMEE processes or jobs, see Viewing Process Details on
page 202.
53
DescriptionThe description that you entered when the source system was registered.
Drill URLThe drill URL you entered when the source system was registered.
Fusion Applications
File
Others
54
Note: Drill through is not supported for Financial Management journals and
intercompany transactions.
e. In ODI Context Code, enter the context code.
The ODI context code refers to the context defined in Oracle Data Integrator. A context
groups the source and target connection information.
The default context code is GLOBAL.
Optional: If you use PeopleSoft's Commitment Control functionality, select Enable Commitment
Control.
Click Save.
After you add a source system, you can select the source system in the table, and the details
are displayed in the lower pane.
After you register a source system, you must initialize the source system. Initializing the
source system fetches all metadata needed in FDMEE, such as ledgers, chart of accounts,
and so on. It is also necessary to initialize the source system when there are new additions,
such as chart of accounts, segments/chartfields, ledgers, and responsibilities in the source
system.
DescriptionThe description that you entered when you registered the source system.
Drill URLThe drill URL you entered when you registered the source system.
Click Save.
After you add a source system, you can select the source system in the table, and the details
are displayed in the lower pane.
55
Caution!
Use caution when deleting registered source systems! Part of the procedure for
deleting a source system is to delete the target application. When you delete the target
application, other artifacts are deleted. When you delete a registered source system,
the source system is removed from the Source System screen, and all import formats,
locations, metadata rules, and data rules associated with the source system are
removed.
Use the Target Application page to remove all target applications that have rules or mappings
to the source system.
In Source System, select the source system to remove, and then click Delete.
Tip: To undo a deletion, click Cancel.
Click OK.
Click Save.
If you make metadata changes in the source system, (for example, you add a new segment,
chartfield values, or hierarchies), you must initialize the source system.
Click Initialize.
56
a. In Source System Name, enter the file-based data load system name.
b. In Source System Description, enter a description.
c. In Source System Type, select File.
d. In Drill Through URL, specify the URL that identifies the URL to use for drilling through.
e. In ODI Context Code, enter the context code.
The ODI context code refers to the context defined in Oracle Data Integrator. A context
groups the source and target connection information.
Click Save.
After you add a file-based data load system, select the source system in the table. The details
of the system are displayed in the lower pane.
Oracle Data Integrator (ODI) ProjectContains the code to extract and load the data from
the source system to the FDMEE staging tables.
Adapter Definition XMLContains the definition of the integration. It contains three
components: source columns, parameters and the drill URL.
JD Edwards
57
Use the ODI Console to import the Project & Model definitions into the Work Repository setup for
FDMEE.
Copy the Adapter Definition XML to a location under the directory that has been set up as the Application
Root directory in System Settings.
Use the Source Adapter screen to import the Adapter XML file.
To import a file:
a. On the Setup tab, under Configure, select Source Adapter.
b. In the Source Adapter, select Import.
c. In Select file to import, navigate to the file to import, and then click OK.
The file name depends on the adapter desired. For example, select:
l
SAP_GLNew_Adapter.xml
SAP_GLClassic_Adapter.xml
SAP_PC_Adapter.xml
SAP_CC_Adapter.xml
SAP_AP_Adapter.xml
SAP_AR_Adapter.xml
Create an import format of new type Source Adapter that defines the mapping between the source
columns (identified in the source adapter) and the target application dimensions.
When you execute the data rule, the new ODI Scenario associated with the import format
is used to extract the data from the source and stage it in the FDMEE staging table
(TDATASEG).
58
Source adapter information summary. See Defining Source Adapter General Information
on page 59.
Source adapter detail. See Defining Source Adapter Detail on page 62.
Three sub-tabs from which you select: source columns information, parameters to pass to
the ODI scenario, and URLs for drill through.
See:
m
In Source Adapter, from the Source Adapter summary task bar, click Add.
Blank entry rows are added to the Source Adapter summary section.
Complete the following steps in the Source Adapter details section.
For example, for an Open Interface source adapter, enter OPENINT. You cannot modify the
value in this field after it has been created.
In ODI Object Project code, enter the template ODI project code.
Click Save.
59
In the Source Adapter summary grid, select the source adapter and click Delete.
Click OK.
To export a file:
1
In Source Adapter, on the Source Adapter summary task bar, in Export, select Export Current or Export
All.
l
Export CurrentExports a selected source adapter from the Source Adapter Summary
list.
Export AllExports all source adapters from the Source Adapter summary list.
To export a selected file, in Specify file location, navigate to the file to export, and then click OK.
You can enter the full path name and file name in the File Name field.
Optional: From Open File, save the file to a local directory on the desktop.
Optional: To browse for a file to export, select Upload, and then browse to the file to export. When the
File Upload screen is displayed, navigate to the file to upload, and then click Open.
Click OK.
In Source Adapter, on the Source Adapter summary task bar, select Import.
In Specify file to import, navigate to the file, and then click OK.
in Open File, open the XML file or save it to a directory of your choice.
60
Optional: To browse to a file, select Upload. When the File Upload screen is displayed, navigate to the
file, and then click Open.
Click OK.
In Source Adapter, on the Source Adapter summary task bar, select Copy.
In Copy, enter the name of the new adapter key, and then click OK.
In Source Adapter, on the Source Adapter summary task bar, click Add.
Blank entry rows are added to the Source Adapter summary section.
In the Source Adapter details grid, in Adapter Key, enter a user defined identifier for the adapter.
For example, for an SAP BW source adapter, enter NK_SAP. The value in this field cannot
be modified after it is created.
In Adapter Name, enter a user defined name for the SAP BW adapter.
In ODI Project Code, enter the template ODI project code name.
The ODI Object Project code identifies an object within the project.
61
The SAP BW cube information is imported into FDMEE, which creates the source columns
in the Source Column tab.
10 In the Source Column grid, map each SAP BW cube column in the Column Name field to the type of
data column in Classification.
Fact
Year
Period
Period Number
14 Click Save.
15 Define the import format and generate the process.
Defining URLs for drill through. See Defining URLs for Drill Through on page 64.
62
Entry fields are displayed for the Column Name, Table Name, and Display Name columns.
For example, enter SEGMENT1. The source column name must have a corresponding column
name in the ODI model.
For example, enter LOGICAL_BALANCES. The table name must have a corresponding table
name in the ODI model.
In Display Name, enter the display name used for the import format.
Defining Parameters
Use the Parameters tab to specify the list of parameters for a ODI Scenario. The parameter
definition includes a non-translated parameter name and a translated prompt. The prompt is
used for display on the data rule page.
This section includes information on:
l
Adding Parameters
When you add a parameter for the source adapter, a definition is created, which includes a nontranslated parameter name and a translated prompt.
Entry fields are displayed for the Parameter Name, Parameter Data Type, and Parameter
Prompt columns.
For example, enter p_actual_flag. This is the name of the parameter in the ODI project.
Char
Number
Date
63
set the browser locale to the appropriate language and edit the prompts as needed in
that language.
Deleting Parameters
To delete a parameter:
1
On the Parameters task bar, select the parameter, and then click Delete.
Click OK.
Entry fields are displayed for the Drill URL Name, Drill URL, Request Method, and Drill
URL Prompt columns.
In Drill URL Name, enter a user defined name for the drill through URL.
In Drill URL, enter the URL used for the drill through.
Enter the URL without the server and port information. The URL must contain the
parameter name and column name from the TDATASEG table enclosed in the symbol $.
For example, enter: LEDGER_ID=$ATTR1$&GL_PERIOD=$ATTR2$.
In the above example the value of ATTR1 is passed as a value for the LEDGER_ID parameter,
and ATTR2 is passed as the value for the GL_PERIOD parameter. Parameters are separated
by the & character.
64
To specify the request-response between a client and server for the drill URL format, enter
either:
l
GETForm data is encoded into the URL. For example, specify: GET@http://
www.oracle.com/. If no method is specified, then GET is the assumed requestresponse.
POSTForm data is displayed in the message body. For example, specify:
POST@http://www.oracle.com/.
Note: A JavaScript specification can also be used for the drill-through. See Drill Through
In the Drill URL Prompt, enter a user-defined prompt for the drill-through prompt.
Select the source system file for the JavaScript based drill through.
Click Save.
From the Create Script Options window, in Script Type, select Drill.
Note: The Technology drop-down is JavaScript because drill through scripts can only be
Click OK.
10 In Target Application, select the target application for this drill through script.
11 Write the code for the custom in the Script Editor.
Ensure the name of the JavaScript function is same as the file name.
65
For example,
function main($ATTR1$,$ATTR2$){
var ledger_id = $ATTR2$;
var currency = $ATTR1$;
var resp_id = 300;
if(ledger_id==1)
resp_id = 100
else if(ledger_id ==2)
resp_id = 200
alert('Currency:' + $ATTR1$);
alert('ledger_id:' + ledger_id);
var url = 'http://machinename.us.oracle.com:6362/OA_HTML/RF.jsp?
function_id=1045073&CALLING_PAGE=FDM_DRILLDOWN&resp_appl_id=&resp_id=&SOB_ID=1&LED_I
D='+ledger-id+'&fdm_per=Jan-03&fdmccid=13098&fdm_currency+'+currency
+'fdm_balance_type=A
alert('url:' + url);
window.open(url);
}
12 Click Save.
13 On the Setup tab, under Register, select Source Adapter.
See Working with Source Adapters on page 57.
66
16 In Drill URL Name, enter a user defined name for the drill through URL.
17 In the Drill URL, enter the Function name of the drill through.
The Function name should be same as the file name.
For example, enter: main($ATTR1$,$ATTR2$).
18 In Drill URL Prompt, enter a user-defined prompt for the drill-through prompt.
19 Click Save.
When you drill down from the workbench, a new window is launched with the specified
URL.
Deleting Drill URLs
From the Drill URL summary area, select the drill-through URL, and then click Delete.
You must register target applications for use with FDMEE. When you register target applications,
you select the target application that requires metadata and/or data from one or more source
systems.
67
Planning
Essbase
Custom Applications
Click OK.
For Financial Management, Planning, and Essbase, the Deployment Mode (the metadata
load) is automatically detected when you select the application. The metadata load methods
are:
l
Optional: Click Refresh Metadata to synchronize the application metadata from the target application
and display any new dimension.
Once the new dimensions are displayed, then you can navigate to Import Format and map
any new dimensions to a source column in Import Format. If necessary, the Metadata rule
can be updated to bring in new metadata to a new application dimension.
Optional: Click Refresh Members to synchronize members from the target dimension.
This feature enables you to see new members in a dimension for target members in a
mappings.
Once the new members in the dimensions are displayed, then you can navigate to Import
Format and map any new dimensions to a source column in Import Format. If necessary,
the Data Load Rule can be updated to bring in new members to a new application dimension.
68
Note: Do not modify dimensions in the EPMA application after you have registered the
target application in FDMEE. Any action such as sharing or removing the dimension,
and then re-adding it, alters the dimensions ID and creates a mismatch between
EPMA and FDMEE.
Data is written to the file in the following predefined order: Account, Entity, UD1,
UD2,..UD20, AMOUNT.
The sequence that is specified when you create the custom app definition is used to order
the dimensions for mapping processing. Note the sequence in case you have scripts that have
an order of processing dependency.
Metadata RuleMetadata load is not applicable from custom target applications. The
Location associated with a custom application is filtered in the metadata load POV.
Data RuleThe POV category is not validated. Plan types are unavailable.
Data Load MappingTarget values are not validated for custom applications.
Data Load ExecutionWhen the option to export the data file is enabled, FDMEE creates
an output data file using the AIF_HS_BALANCES view. The name of the data file is
<Target App Name>_<Process ID>.dat, and it is written to the <APPL ROOT
FOLDER>/outbox directory. In addition the OUTPUT_FILE column in the
AIF_PROCESSES table is updated. The data file can be accessed from the Process Details
page from the OUTPUT file column.
Check Rules can be created from a custom target applications. Check rules cannot be based
on target values.
Write-back is not applicable from custom target applications.
69
From Select Application, select Custom Application, and then click OK.
The dimension class is a property that is defined by the dimension type. For example, if you
have a Period dimension, the dimension class is also Period. For Essbase applications, you
must specify the appropriate dimension class for Account, Scenario, and Period. For Public
Sector Planning and Budgeting applications, you must specify the dimension class for
Employee, Position, Job Code, Budget Item, and Element.
In Data Table Column Name, specify the table column name of the column in the staging table
(TDATASEG) where the dimension value is stored.
Click
For example when Account is set to 1, Product is set to 2, and Entity is set to 3, then FDMEE
first processes the mapping for Account dimension, followed by Product, and then by Entity.
11 In Enable export to file, select Yes to have FDMEE create an output data file for the custom target
application.
A file is created in the outbox folder on the server with the following name format:
<LOCATION>_<SEQUENCE>.dat. For example when the location is named Texas and
70
the next sequence is 16, then the file name is Texas_15.dat. The file is created during the
export step of the workflow process.
When the Enable export to file option is set to No, then the Export to Target option is
unavailable in the execution window.
13 In Column Delimiter, select the character to use for delimiting columns in the output file.
Available column delimiters are:
l
14 In File Name to Download, enter the file name to copy to the LCM folder.
You can then use the EPM Automate to download the file. The EPM Automate Utility
enables Service Administrators to remotely perform Oracle Planning and Budgeting Cloud
Service tasks.
15 Click Save.
Click Add.
Blank dimension name and data table column name entry fields are displayed.
In Data Table Column Name, select the data column from which to base the lookup dimension.
Click OK.
71
The lookup dimension is added to the dimension detail list with the target dimension class
name of LOOKUP.
The dimension class is a property that is defined by the dimension type. For example, if you
have a Period dimension, the dimension class is also Period. For Essbase applications, you
must specify the appropriate dimension class for Account, Scenario, and Period. For Public
Sector Planning and Budgeting applications, you must specify the dimension class for
Employee, Position, Job Code, Budget Item, and Element.
Optional: Click Refresh Metadata to synchronize the application metadata from the target application.
In Data Table Column Name, specify the table column name of the column in the staging table
(TDATASEG) where the dimension value is stored.
Click
For example when Account is set to 1, Product is set to 2, and Entity is set to 3, then FDMEE
first processes the mapping for Account dimension, followed by Product, and then by Entity.
For Essbase applications and Profitability and Cost Management only: Select the Create Drill Region.
The selection of the dimensions to create a drill-region defines the granularity for the
drillable region. For example, if you only select the year dimension, you can drill on a cell
that at least does not have a null for year.
10 Click Save.
The target application is ready for use with FDMEE.
Tip: To edit the dimension details, select the target application, then edit the application or
72
to toggle
In the Target Application summary grid, select a Planning target application or Essbase target
application.
After defining the application details and dimension details in Application Detail, select the Application
Options tab.
Click Save.
Table 7
Option
Description
When a file based data load to Essbase is successful, specify whether to delete the data file from the application
outbox directory. Select Yes to delete the file, or No to retain the file.
Prefix
Dimension for
Duplicate
Members
When set to Yes member names are prefixed by the Dimension Name. The member name that is loaded is in the format
[Dimension Name]@[Dimension Member]. The prefixed dimension name is applied to all dimensions in the application
when this option is enabled. You cannot select this option if there is a dimension in the target that has duplicate
members. That is, only select this option when the duplicate members cross dimensions.
If the application supports Duplicate Members and Prefix is set to No, then the user must specify the fully qualified
member names. Refer to Essbase documentation for the fully qualified member name format.
Note: Planning does not support duplicate members.
Option to override the Single Sign-On logon to the Essbase and the Planning applications.
When a user name is specified for this option, this user name is used to access Essbase/Planning applications instead
of the FDMEE sign-on user name.
Specify the user name of a user who has administrator access to the Planning application, and/or Application/Database
Manager access to the Essbase applications.
Batch Size
Specify the batch size used to write data to file. The default size is 10,000.
73
Option
Description
Load Method
Specify the method for loading data from the TDATASEG staging table to Essbase.
Available methods:
l
FileData is written to a data file in the outbox directory of the application (defined in System Settings). The file
name is in the format <APPLICATION NAME>_<PROCESS_ID>.dat. It is then loaded to Essbase.
The file load method creates an application file type of ESSFILE.
SQLUses SQL Method to load data. The SQL load method is the default.
The SQL method creates an application file type of ESSSQL.
Check Entity
Calculation
Method
Source
Language for
Member
Description
Drill Region
Select Yes, to create a drill region. A drillable region is created to use the drill through feature.
To understand how languages are processed, see How Languages Are Processed on page 130.
Note: FDMEE does not support drilling through to human resource data.
The drill region URL allows Essbase, Smart View, and Financial Reporting to drill to the proper landing page.
When loading data from FDMEE, the drill region is loaded to Planning data.
A drill region includes the Entity/Account/Scenario/Year/Period for Planning, a URL to get back to FDMEE, and a region
name. For Essbase, you select the dimension to use for the drill region.
Select Yes to enable or No to disable.
Scenario
Example
[DimensionMember].[DuplicateMember]
[Year].[Jan]
[DimensionMember]@[DuplicateMember]
[Year]@[Jan]
[ParentMember].[DuplicateMember]
[East].[New York]
[DimensionMember].[ParentMember].[DuplicateMember]
[Products].[Personal Electronics].
[Televisions]
74
Scenario
Example
DimensionMember]@[GenLevelName]|[DuplicateMember]
[2006]@[Gen1]|[Jan]
DifferentiatingAncestor].[Ancestors...].[DuplicateMember]
[2006].[Qtr1].[Jan]
Scripts can be parameterized so that you can specify a parameter for each script.
Scripts are assigned a scope of applicability. The scope can be at the Application, Category,
Location, and Data Rule level. If scripts are assigned at the lowest level, then they take
precedence over script at higher level. Data Rule is the lowest level and Application is the
highest level. Only scripts at one level are executed.
Click
For Planning applications only, select the Plan Type to retrieve the parameters defined in the calculation
script.
Select the parameter that has been defined for the script.
You can also click Browse, select the parameter, and click OK. You can also manually type in
the parameter name.
In Script Value select a predefined parameter value, or select Custom to specify your own script value.
Optional: If you selected Custom in the Script Value field, enter the value in Custom.
Click OK.
75
Category
Location
Data Rule
13 In Scope Entity, select the specific value associated with the script scope.
For example, if the script scope is Location, select the location associated with the
application.
The Application script scope is disabled for the scope entity.
Before Check
After Check
16 Click Save.
Adding Calculation Script Parameters
You parameterize calculation scripts by identifying and defining the list of values in the scripts.
Parameter values can be predefined for a list of values, for example, the POV Period, POV
Location, POV Category, Check Group Entity, and all data load entities.
You can also specify custom parameters, in which case, you can enter any Essbase filter syntax.
Additionally, you can reference values stored in the Integration Option 1-4 fields in the Location
table to drive calculation logic. Location Option 1, Location Option 2, Location Option 3, and
Location Option 4 values can be referenced. In this case, the exact string that is passed as a
parameter has to be stored in the Integration Option field of the Location table.
76
Similarly, you can reference four option fields in the Data Rule for parameters. These fields are
Data Rule Option 1, Data Rule Option 2, Data Rule Option 3, and Data Rule Option 4. The
column added to the Data Rule is called RULE_OPTION1, RULE_OPTION2, RULE_OPTION3
and RULE_OPTION4.
Click
For Planning applications only: select the Plan Type for Accounting and Entity dimensions.
In Script Parameters, select the parameter that has been defined for the script.
You can click the Browse icon, select the parameter, and click OK.
77
In Script Value, select the value to which to apply the calculation script and click OK.
Click
In Script Parameters, select the parameter that has been defined for the script.
You can click the Browse icon, select the parameter, and click OK.
From Name, select the Profitability and Cost Managementa application and click OK.
After defining the application details and dimension details in Application Detail, select the Application
Options tab.
Click Save.
78
Table 9
Property
Value
Drill Region
Select Yes, to create a drill region. A drillable region is created to use the drill through feature for Profitability and Cost
Management data.
Note: FDMEE does not support drilling through to human resource data.
The drill region URL allows Essbase, Smart View, and Oracle Hyperion Financial Reporting to drill to the proper landing
page.
When loading data from FDMEE, the drill region is loaded to Planning data.
A drill region includes the Entity/Account/Scenario/Year/Period for Planning, a URL to get back to FDMEE, and a region
name. For Essbase, you select the dimension to use for the drill region.
Select Yes to enable or No to disable.
Source
Language for
Member
Description
Batch Size
Specify the batch size used to write data to file. The default size is 10,000.
Check Entity
Calculation
Method
To understand how languages are processed, see How Languages Are Processed on page 130.
If the calculation method is set to dynamic, the default calculation is performed during Essbase consolidation. If the
method is set to calculation script, then the script name given on check entity screen is used to perform the
consolidation in target system.
Prefix
Dimension for
Duplicate
Members
When set to Yes member names are prefixed by the Dimension Name. The member name that is loaded is in the format
[Dimension Name]@[Dimension Member]. The prefixed dimension name is applied to all dimensions in the application
when this option is enabled. You cannot select this option if there is a dimension in the target that has duplicate
members. That is, only select this option when the duplicate members cross dimensions.
If the application supports Duplicate Members and Prefix is set to No, then the user is responsible to specify the fully
qualified member names. Refer to Essbase Documentation for fully qualified member name format.
Note: Planning does not support duplicate members.
Load Method
Specify the method for loading data from the TDATASEG staging table to Essbase.
Available methods:
l
FileData is written to a data file in the outbox directory of the application (defined in System Settings). The file
name is in the format <APPLICATION NAME>_<PROCESS_ID>.dat. It is then loaded to Essbase.
The file load method creates an application file type of ESSFILE.
SQLUses SQL Method to load data. The SQL load method is the default.
The SQL method creates an application file type of ESSSQL.
When a file based data load to Essbase is successful, specify whether to delete the data file from the application
outbox directory. Select Yes to delete the file, or No to retain the file.
79
To define application options for Public Sector Planning and Budgeting Applications
1
In the Target Application summary grid, select a Public Sector Planning and Budgeting application.
After defining the application details and dimension details in Application Detail, select the Application
Options tab.
Public Sector Planning and Budgeting application options are described in Table 10 on page
80.
Click Save.
The target Public Sector Planning and Budgeting application is ready for use with FDMEE.
Table 10
Option
Description
Budget Model
Type
Enter the Public Sector Planning and Budgeting model. (For Employee only, enter EMPLOYEE. For Position only, enter
POSITION, or for both Employee and Position, enter Total Existing Positions).
Parent Member
for all Positions
Enter the parent member for all positions imported from your human resource source system. For example, enter
Total Existing Positions.
Parent Member
for all Entities
Enter the parent member for all departments imported from your human resource source system. For example, enter
Total Entity.
Parent Member
for all
Employees
Enter the parent member for all employees imported from your human resource. For example, enter Existing
Employees.
Parent Member
for Salary
Elements
Enter the parent member for salary grades imported from your human resource source system. For example, enter
Salary Grades.
Parent Member
for Earnings
Elements
Enter the parent member for earnings codes imported from your human resource source system. For example, enter
Additional Earnings.
Parent Member
for all Job
Enter the parent member for all job codes imported from your human resource source system. (The parent member for
job is applicable only to Employee Only models.)
Parent Member
for Benefit
Elements
Enter the parent member for benefit codes imported from your human resource source system. For example, enter
Benefit Defaults.
80
Specifying parent members for earnings and benefit elements is optional. If you do not specify a parent member, the
corresponding elements are not loaded into the application when you run the human resource data load rule.
Option
Description
Source
Language for
Member
Description
Drill Region
To understand how languages are processed, see How Languages Are Processed on page 130.
In the Target Application summary grid, select a Financial Management target application.
After defining the application details in Application Detail, select the Application Options tab.
Click Save.
Table 11
Option
Description
Check
Intersection
Enables the checking of Financial Management data intersections (account, entity, and so on) during the Validation step
in the Data Load Workbench. The default setting is Yes.
Specify whether line item detail or summary data is loaded for cells. The default is Load Detail, which displays details
for the selected cell. (Specifies whether an account can have line items.) If this option is Load Summarized, cells show
summarized information.
Load Summarized
Load Detail
Enable Data
Load
Load Process
Select the process for loading data. Select Scan to scan the file for invalid records before loading it to the application.
Select Load to load the file only.
ScanValidates data and lists invalid records into the Log. When this option is selected, data is not loaded to the
target application.
81
Option
Description
Load Method
Select the method for loading a data file into an application. Available load methods:
l
ReplaceReplaces the data in the application with the data in the load file. For each unique combination of Scenario,
Year, Period, Entity, and Value in the data file, the Replace option clears all account values from the application,
then loads the value from the data file.
Note: You may need to create several small files to load a data file using the Replace mode, especially if the data
is very large or if the file contains ownership data. An error message is displayed if the file is too large when you try
to load it.
MergeOverwrites the data in the application with the data in the load file. For each unique point of view that exists
in the data file and in the application, the value in the data file overwrites the data in the application.
Data in the application that is not changed by the data load file remains in the application.
If you select the Accumulate In File option in conjunction with the Merge option, the system adds all values for the
same point of view in the data file, and overwrites the data in the application with the total.
For each unique point of view that is in the data file but does not have a value in the application, the value from the
data file is loaded into the application.
AccumulateSelect the Accumulate option to accumulate the data in the application with the data in the load file.
For each unique point of view in the data file, the value from the load file is added to the value in the application.
Note: Data for system accounts is not accumulated.
Replace by SecurityPerforms a data load in Replace mode in which only the members to which you have access
are loaded. This option enables you to perform a data load in Replace mode even if you do not have access to all
accounts. When you perform the Clear operation for a period in a sub-cube, only the cells to which you have access
are cleared. Data, cell text, and line item detail are cleared, but cell attachments are not cleared.
Accumulate in
File
You use the Accumulate in File option in conjunction with the Merge and Replace options. When a data load file contains
multiple lines of data for the same point of view, this option first accumulates the data in the file, and then loads the
totals into the application based on the selected load option. For each unique point of view in the data file, the value
from the load file is added to the value in the application. For example, if you have 10,20 and 30 in the file, 60 is
loaded. Select Yes to enable or No to disable.
Has Ownership
If the file that you are loading contains ownership data, you must indicate this option. If you do not select this option
and the data file contains ownership or shares data, an error occurs when you load the file.
Select Yes to enable or No to disable.
Enable Data
Protection
Enables FDMEE to protect target-system data from being overwritten during data loads; is based on a specified protection
value. Use this option when data is entered into the target system through a method other than FDMEE.
Select Yes to enable or No to disable.
Protection
Value
The value that is to be protected during the Load step when Enable Data Protection is enabled. The value in this field is
to be a dimension value inside of Financial Management across any dimension.
For example, enter Protect This.
Protection
Operator
82
Select operator (= or <>). This is used only when the Enable Data Protection option is enabled. The option enables you
to state that the data to be protected is equal (=) or not equal (<>) to the Protection Value.
Option
Description
Enable Journal
Load
Drill Region
Display Name (for cell context menu) and URL (to drill to)
Enables the loading of text and documents to a data cell. FDMEE archives documents in the EPM_ORACLE_HOME/
products/FinancialDataQuality/data directory.
Select Yes to enable or No to disable.
Note: FDMEE does not load multiple cell text to an intersection in Financial Management. If a load using an append
mode is run and new cell text is added to an intersection that already has cell text, the old cell text is replaced by the
new cell text and not appended.
Enable
Consolidation
83
Option
Description
Consolidation
Type
ImpactedThe Consolidate (Impacted Consolidation) option is available for any parent entity with a calculation
status of CN or CN ND. When you select this option for a parent entity, the system performs calculations (Calculate,
Translate, Consolidate) for any dependent entity within the consolidation path of the selected parent that has a
calculation status of CN, CN ND, CH, TR, or TR ND, on the current period or on any prior period in the current year.
Consolidate is the most efficient option because only entities that require consolidation are updated.
Process units with a status of NODATA on the current period and all prior periods are skipped. Process units with a
status of OK or OK SC on the current period are not recalculated, retranslated, or reconsolidated. If the selected
parent has a status of CN or CN ND in the prior period, consolidation runs for all periods from the first period in the
current year where the parent is impacted until the current period.
All with DataThe Consolidate All with Data option is available for any parent entity, regardless of its status. When
you select this option for a parent entity, the system consolidates every dependent entity within the consolidation
path of the selected parent that contains data, regardless of its status, in the current period or in any of the prior
periods. The system also runs calculation rules for the dependent entities. It does not perform a consolidation on
entities that contain zeroes or no data. This option is useful for updating system status from OK SC to OK after
metadata changes.
Process units with a status of NODATA on the current period and all prior periods are skipped. Consolidation Options
units with a status of OK or OK SC on the current period are recalculated, retranslated, and reconsolidated. If the
selected parent has a status of CN or CN ND in the prior period, consolidation runs for all periods from the first period
in the current year where the parent is impacted until the current period.
AllThe Consolidate All option is available for any parent entity, regardless of its status. When you select this option
for a parent entity, the system performs calculations for every process unit within the consolidation path of the
selected parent, regardless of its status. It consolidates all entities whether they contain data or not. This option is
useful when an update from prior periods is required, or when an entity with no data needs to be populated using
allocations. This option should be used sparingly because the system does not omit entities with no data, which can
have a significant impact on consolidation performance.
Process units with a status of NODATA on the current period are calculated, translated, and consolidated. Process
units with a status of OK or OK SC on the current period are recalculated, translated, and reconsolidated. If the
selected parent has a status of CN or CN ND in the prior period, consolidation runs for all periods from the first period
in the current year where the parent is impacted until the current period.
EntityCalculates the contribution of each entity to its parent, and then totals all contributions to arrive at the
consolidated numbers.
Force Entity OnlyForces calculation to run for all selected contribution values to arrive at the consolidation numbers.
Enable Force
Calc
Enables the execution of the default calculation call prior to a consolidation run.
Enable Force
Translate
84
Option
Description
Translation
Level
Determines the translation level (levels to include for translation) of rows and columns when loading data. Available
levels:
l
<Entity Currency>
Journal Status
To load journals with a specific status, select the status. The journal status indicates the current state of the journal.
Available journal statuses:
Journal Default
Value
Journal Enable
JV ID per Entity
1Working: Journal is created. It has been saved, but it can be incomplete. For example, a label or single entity may
need to be assigned.
Specify the default value of the journal. The default setting for this option is <Entity Curr Adjs>.
Available values are:
l
[Contribution Adjs]
[Parent Adjs]
Journal
Balancing
Attribute
BBalanced
UUnbalanced
EBalanced By Entity
This option is only used when loading journals to Financial Management. The default setting is U-Unbalanced.
85
Option
Description
Source
Language for
Member
Description
Indicates the source language for the description when members are loaded.
Available languages are shown on the drop-down.
Attr1 Transaction ID
Attr3 Reference ID
Attr11 - Comment
When the Refresh Metadata Confirmation window is displayed, click Continue and Save Later to add
the ICP transactions.
In this case, to save the ICP transactions, you need to click Save to save the transactions with
the dimension details.
To add and save the ICP transactions immediately, click Save.
Click Save.
In Target Application, select the target application, and then click Delete.
Click OK.
When you delete a target application, the application is marked for deletion and is
unavailable for any metadata or data rule processes, including the import format and
location creation options. All the existing rules involving the target application are removed.
Note: After a target application is deleted and the process has run successfully, use the Target
Application screen to set up the same application and redefine the rules.
Click Save.
87
The source accounting entities are displayed in a grid. You can click the column header to
sort any column. The Entities tab displays the following columns:
For Fusion and E-Business Suite source systems:
l
SelectA check mark indicates that the accounting entity (ledger) is available.
CalendarThe Fusion and E-Business Suite ledger calendar. The Fusion and E-Business
Suite ledger is a collection of chart of accounts, currency, and calendar. For example,
445, Weekly, Accounting, and so on.
Responsibility NameDisplays the general ledger drill-through responsibility. The drill
through responsibility must be set in FDMEE to enable users to drill through to EBusiness Suite. The responsibility selected must have the authority to view summary
journals and journal details for the selected ledger in the E-Business Suite.
For Fusion and E-Business Suite source systems, select the general ledger Responsibility Name. See
Assigning General Ledger Responsibility on page 88.
For each ledger or business unit that you want to make available in FDMEE, select the check box.
Click Save.
Tip: To filter by the business unit or accounting entity, ensure that the filter row is displayed
88
to select a General
The Responsibility Name is the Responsibility ID the user is logged in under when drilling
through to the source system. Select the responsibility name only if you want to drill through:
otherwise, leave it blank.
Repeat the above process as necessary for all selected ledgers in the source system.
Click Save.
You view and maintain accounting entity groups using the Entity Groups tab in the Source
Accounting Entities feature. The Entity Groups tab consists of two regions: Entity Groups, to
which you can add a new group, and the Entity Groups Entities, from which you can add
accounting entities.
89
Blank Name and description rows are added at the top of the grid.
In the Entity Group Entities grid, select the accounting entities to add.
The source accounting entities are displayed in the Entity Group Entities grid. You can click
the column header to sort any column. The Entity Group Entities grid displays the following
columns:
For Fusion and E-Business Suite source systems:
l
SelectA check mark indicates that the accounting entity (ledger) is available.
CalendarThe Fusion and E-Business Suite ledger calendar. The Fusion and E-Business
Suite ledger is a collection of chart of accounts, currency, and calendar. For example,
445, Weekly, Accounting, and so on.
Responsibility NameDisplays the general ledger drill-through responsibility. The
drill-through responsibility must be set in FDMEE to enable users to drill through to
E-Business Suite. The responsibility selected must have the authority to view summary
journals and journal details for the selected ledger in the E-Business Suite.
90
SelectSelect the check box to make the business unit available for the accounting entity
group.
Click Save.
Import Formats determine which fields (columns) are extracted from the source system and
how the data is stored in the FDMEE staging table. Import Formats are created for a single
accounting entity. However, if you are importing data from multiple accounting entities that
have the same Chart of Accounts, you can define one Import Format using a representative
accounting entity, and then use it for importing data for all accounting entities with the same
Chart of Accounts.
You define import formats to map source segments or chartfields to target dimensions. You can
create import formats to:
l
Define the import format mapping between the source system segments or chartfields and
the dimensions (used in the metadata load and data load process).
Define the import format mapping between the EPM dimensions and the source system
segments or chartfields (used in the write-back process).
Define and maintain import format mapping information for source adapter based
integrations
Define and maintain import format mapping information between source and target EPM
dimensions for data synchronization.
Note: You do not need to define import mappings for use with human resources source systems.
Import Format SummaryDisplays common information relevant to the source and target
applications.
Import Format DetailEnables you to add and maintain import format information.
Import Format MappingsEnables you to add and maintain import format mapping
information.
91
View Option
Description
Customizes views. Options include:
l
Show All
Name
Source System
Accounting Entity
Source Adapter
Target Application
Reorder Columns-Use to change the order of the columns. When you select this option, the Reorder Columns screen
is displayed. You can select a column, and then use the scroll buttons on the right to change the column order.
Detach/Attach-Detaches columns from the data grid. Detached columns are displayed in their own window. To return
to the default view, select View, and then click Attach or click Close.
Query by Example-Use to toggle the filter row. You can use the filter row to enter text to filter the rows that are displayed
for a specific column. To clear a filter, remove the text to filter by in the text box, and then the press [Enter] key. All text
that you enter is case sensitive.
Source ERP
File
Source TypeEPM
m
Source EPM for Data SynchronizationIf you select EPM, then you are presented with
the list of registered EPM applications. Using a source of EPM lets you target another
EPM application, or enables you to write back to a registered Enterprise Resource
Planning (ERP) system that has an available interface table. The standard data load to
write back is only supported for E-Business Suite and Peoplesoft.
Source EPM for data load to write back to the Enterprise Resource Planning (ERP)
system
When adding import formats, note that specific import format detail fields are available or
unavailable based on the source type.
92
Note: For the Enterprise Resource Planning (ERP) source type you can select an Enterprise
Resource Planning (ERP) source or a file. If the Enterprise Resource Planning (ERP)
source is E-Business Suite or Peoplesoft, you can select an accounting entity.
You cannot modify value in this field after a mapping is created for this import format.
In Source Type, select ERP, and then select the ERP type as the source.
For example, you can select Fusion Financials, E-Business Suite, or PeopleSoft.
In Target Type, select EPM, and then select any EPM application as a target.
Optional: In Concatenation Character, specify the character to use for concatenating two segments
when multiple segments are specified for sources.
For Fusion and E-Business Suite source systems, the accounting entity is the ledger. For
PeopleSoft source systems, the accounting entity is the business unit.
You cannot modify the value in this field after mapping is created for this import format.
93
Note: Do use non-ASCII characters in an import format name when the import source is
an adapter.
In Source Type, select ERP, and then select the source for the source adapter.
In Target Type, select EPM and select any EPM application as a target.
In Drill URL, enter the URL that identifies the URL to use for drilling through when using this import
format.
Define the import mappings from source to target. See Defining the Import Format Mappings on page
98.
You cannot modify the value in this field after a mapping has been created for this import
format.
In Source Type, select ERP, and then select File for the source.
Fixed
DelimitedIndividual data values use delimiters, such as quotation marks or commas,
to separate two names of data,
MultiperiodDelimited text or Excel files that can contain multiple periods.
If the file type is delimited, in the File Delimiter field, select a type of delimiter.
94
comma (,)
exclamation (!)
semicolon (;)
colon (:)
pipe (|)
tab (~)
In Target Type, select EPM and select any EPM application as a target.
URL Name
URL Prompt
URLEnter the URL without the server and port information. The URL must contain
the parameter name and column name from the TDATASEG table enclosed in the symbol
$.
Enter the URL without the server and port information. The URL must contain the
parameter name and column name from the TDATASEG table enclosed in the symbol $.
For example, enter: LEDGER_ID=$ATTR1$&GL_PERIOD=$ATTR2$
In the above example the value of ATTR1 is passed as a value for the LEDGER_ID parameter,
and ATTR2 is passed as a value for the GL_PERIOD parameter. Note that parameters are
separated by the & character.
In some cases, the you may want to refer to the column name in the FDMEE staging table
based on the source mapping that is defined in the import format. When this is the case,
you specify the source column name as the parameter for the URL, and this instructs the
system to translate the source column name to the related column in TDATASEG when the
URL is parsed. To specify a source column from the import format as the value for a
parameter in the URL, enclose the value with $$ on each side
For example, enter COMPANY_CODE=$$RBUKRS$
In the above example, the value for COMPANY_CODE parameter is determined using the
import format. If RBUKRS is mapped to the ENTITY dimension, then the value of the
ENTITY column is passed as the parameter.
To specify the request-response between a client and server for the drill URL format, type
either:
l
GETForm data is encoded into the URL. For example, specify GET@http://
www.oracle.com/. If no method is specified, then GET is the assumed requestresponse.
Note: A JavaScript specification can also be used for the drill-through. See Drill Through
10 Click Save.
To define import formats for file-based mappings, see Defining Import Formats for filebased Mappings on page 103.
95
Source Type
Target Type
ERP
EPM
Table 14
Write-Back Rule
Target Type
Source Type
EPM
ERP
Table 15
Data Synchronization
Source Type
Target Type
EPM
EPM
In Import Format, from the Import Format summary grid, select the import format, and then click
Delete.
Querying by Example
You can filter the import formats in the Import Format summary section using the Query by
Example feature. To filter by Import Format Name, ensure that the filter row is displayed above
the column headers.
To query by example:
1
96
Define a simple one-to-one mapping between source segments and target dimension
members.
Pull all members from the source value set as members into the target dimension.
Note: Each member in the source is created as a single member in the target dimension.
Note: When importing a mapping file that has maps for one dimension, the dimension
Segment/Chartfield
EPM Dimension
Company
Entity
Department
Product
Product
97
Segment/Chartfield
EPM Dimension
Account
Account
Concatenations of any number of source segments for Enterprise Resource Planning (ERP)
sources like E-Business Suite and PeopleSoft.
To define the Enterprise Resource Planning (ERP) system import format mappings:
1
From Source Column, specify the source column from which to map.
For Fusion and E-Business Suite source systems, you can concatenate segments to map
multiple segments from the source into a single EPM target dimension. The drop-down list
displays all of the source system segments for the accounting entity that you selected when
you defined the import format details.
Note: Verify your entries and ensure that, if you enter Segment 1, Segment 2, and Segment
3 that, the segments are displayed in sequence. For example, Segment 3 should not
come before Segment 1. Entering segments out of sequence can cause an error.
For Financial Management applications, concatenate segments are not available if your
target dimension is an Entity dimension type. Typically, the intercompany segment in
Fusion and E-Business Suite or affiliate in PeopleSoft is related to a company or business
unit. If concatenation was enabled, you could not determine the ICP dimension value.
For PeopleSoft source systems, select chartfields as necessary. The drop-down list displays
the source system chartfields for the Accounting Entity (business unit) that you selected for
the import format.
When the target applications is an ARM data load type: you can set the concatenation
member by specifying the concatenation character.
For non- ARM data and metadata loads, the underscore character _ is used to concatenate
two segments. For ARM data loads, you cannot use an underscore character with a mapping
that uses the Like method. Therefore, for ARM mappings, specify a different
concatenation character for the data load mapping details.
98
For EPM and file-based source systems, you can add expressions in the Expression field. See Adding
Import Expressions on page 100.
Click Save.
In the Import Format summary task bar, select the import format.
In the Import Format Detail section, from the Concatenation Character, select the concatenation
character.
For non-ARM data loads and metadata loads, the underscore character _ is used to
concatenate two segments. For ARM data loads, you cannot use an underscore character
with a mapping that uses the Like method.
In Source Column, select the first source column to concatenate to the target.
For example, to have two source columns (Company and Account separated by a dash),
select the Company source columns.
In Source Column, select the second source column to concatenate to the target.
Note: Only EPM source types enable you to specify a value in the Expression field.
99
10 Click Save.
In Import Format, from the Import Format Mapping grid, select the file-based source column.
Optional: You can also specify the expression type and value on the Add Expression field.
a. Click
100
Account Number
Description
Debit
1000-000-00
Cash-Operating Account
68,603.91
1010-000-00
Cash-FANB-AP
Credit
177,216.16
DRCRSplit, which enables FDMEE to interpret left-right positioning and to assign the correct
sign, follows the format DRCRSplit=Mid Point of the DR and CR columns.
When the file is imported, credit amounts are assigned negative signs (and thus are interpreted
as positive), and debit amounts are unchanged (and thus are interpreted as negative).
Converting from European to U.S. Notation
The Fill=EuroToUS expression is used with the Amount field to trigger a number format
conversion from (.,) to (,.) format.
Padding Fields with Leading Fills
The FillL=LeadingFill expression is used to fill fields with leading characters. Text values
that are shorter than the specified fill expression are padded, as directed by the fill expression.
101
Processing Order
For all fields except the Amount field,FDMEE processes stacked expressions in the following
order:
1. Script
2. Fill or FillL
For the Amount field, FDMEE processes stacked expressions in the following order:
102
1. DRCRSplit
2. Fill=EuroToUS
3. Script
4. Sign
5. Scale
6. NZP
Skip
Currency
Attribute
Description
Dimension Row
Table 17
Import
Definition
Option
Description
Skip
The skip option is used to indicate rows in the input file that should be skipped. For example, rows with no data, negative
numbers, or for specific accounts. The specification for a skip row is defined in the same way as that for a data row, and
the system looks for the exact textual match for text entered in the expression field in the indicated location in the input
file.
The system automatically skips rows in the input file that have spaces and non-numeric characters in the amount
location, so a skip specification is only needed when non-amount data is present in a row of the input file in the same
location as the amount. For example, the input file may contain a label named date. Add an entry for a skip row to
indicate the starting column of the text date, the length of the text, and the exact text to match.
The Skip row option is only available when the file type is fixed, and not delimited.
Attribute
The TDATASEG table includes 13 attribute columns that you can load from the selected input file. You can provide the
location of the attribute in the input file by specifying the starting location and length, or plug the value during processing
by entering the value for the attribute in the expression field. If the value for the attribute is entered in the expression
field, then a starting location and length are not needed.
The attribute fields are generally used to help compose a drill-through URL or for history or documentation needs. You
may want to populate the attribute field to support searching and filtering in the Data Load Workbench.
Description
The TDATASEG table includes two description columns, and you can load these columns in the same way as the attribute
columns. You can specify the location in the input row that contains a description, or specify an explicit value by entering
it in the expression field in the mapping table.
103
Import
Definition
Option
Description
Currency
FDMEE supports the ability to load data that is of a currency different from the default currency of the selected location.
This option enables you to specify the location in the input line that specifies the currency for the related amount field.
For the file import format, specify a currency on each row of data, or make sure that a currency is specified in the location
that uses the selected import format.
Note: You may encounter issues with loading data if the currency is not specified correctly.
Dimension
FDMEE supports multiple entries for a dimension in the import format when the dimension specification is spread between
multiple locations on the same line. This feature enables you to concatenate fields for file-based data. To use this option,
select the dimension, start and end positions, and the expression.
In Import Format, from the Import Format summary grid, select the file.
In the Import Format Detail grid, select the type or row to add from the Add drop-down.
Available options:
l
Skip Row
Currency Row
Attribute Row
Description Row
Dimension Row
In the Start field, specify where on the file the column starts.
In the Expression field, enter the expression that overwrites the contents of the column.
When entering a constant, enter a starting position and length. Use a start position of 1
and a length of 1.
See Adding Import Expressions on page 100.
Click Save.
In Import Format, from the Import Format summary grid, select a file.
In the Data Load Mappings section, click Add, and select the type or row to add.
104
Currency Row
Attribute Row
Description Row
Dimension Row
The Expression field ignores the Field Number value when you provide a column expression
for a multiple period data load.
In the Expression field, enter the expression that overwrites the contents of the field.
Click Save.
In the Import Format summary task bar, select the import format of the file.
Source columns for both fixed and file delimited files can be concatenated.
In Field NUMBER, enter the field number from the file to import (defaults to the field number from the
file when text is selected).
Select Dimension Row, and then specify the same target dimension as in step 4.
10 Repeat steps 5-6 for each source column to add to the concatenation.
11 To use a concatenation character between source columns:
a. Click Add, and then specify the target dimension.
b. In Source Column field, enter a name to identify the concatenation character.
For example, enter Delimited.
c. In Field Number, enter 1 or greater.
Do not enter 0 when specifying the field number for the concatenation character column
d. In Expression field, enter the concatenation character used to separate concatenated
source columns.
For example, enter a , (comma) or a . (period).
12 Click Save.
105
In the Import Format summary grid, select a file based source system.
In Select file to Load, locate and choose the file to import, and then click OK.
The file contents are shown on the Import Format Builder screen.
In Assign selected text as Source Dimension Name, select N to specify the source dimension name
on the Enter Dimension Mapping Detail screen.
Select Y to use the selected text as the source dimension name and to use the one-to-one
mapping between the source dimension and target dimension members.
106
You must add or change dimension details if you selected N in Assign selected text as Source
Dimension Name.
On Enter Dimension Mapping Details, from Source Dimension Name, specify the name of source
dimension to which to assign the selected text.
In Select Target Dimension, select the target dimension to which to map the source dimension.
10 In Selection Field Number, specify the field number from the file to import (defaults to the field number
from the file when text is selected).
11 Click OK.
When you assign or change source dimension information, the information is shown in the
Add New Mapping summary grid.
12 Click OK.
Write-Back Mappings
When you are setting up an integration to pull from an EPM application and write back to EBusiness Suite or PeopleSoft, consider the following:
l
Before you create a data load rule to write back, create the write-back mappings. Write-back
mappings occur at the member level. (For example, loading data from a Planning application
to your Enterprise Resource Planning (ERP) source system.)
You create write-back mappings to replace outgoing dimension members with source
segment members. More specifically, during budget write-back, the write-back mapping is
referred to when replacing outgoing dimension members with segment values.
The following interface tables require write security privileges for the data load to write-back
process:
E-Business Suite
107
GL_INTERFACE
GL_INTERFACE_CONTROL
GL_BUDGET_INTERFACE
Standard PeopleSoftPS_HPYPB_ACCT_LN
PeopleSoft Commitment Control
l
PS_HYP_KK_BD_HDR
PS_HYP_KK_BD_LN
In Source Dimension, select the source dimension to map to the source dimension.
Optional: To have FDMEE create the write back mapping automatically, click Auto Create.
Click Save.
The value in this field cannot be modified after a mapping is created for this import format.
Depending on your selection in this field, the Source fields shows only registered Enterprise
Resource Planning (ERP) sources and file for an ERP source type; or registered EPM
applications (for example Financial Management or Planning, for an EPM source type.
For an EPM source system, select the EPM source application or file from which to move
data.
108
For an Enterprise Resource Planning (ERP) source system, select the ERP source application
(for example E-Business Suite, Peoplesoft Financials, Fusion) from which to move data.
For an EPM target system, select the EPM target application to which to move data.
For an Enterprise Resource Planning (ERP) target system, select the ERP target application
to which to move data.
When you use an E-Business Suite and Fusion target system, you must enter the Chart of
Accounts. The Accounting Entity is captured at the Location or Data Rule level.
10 Define the import mappings from the EPM or Enterprise Resource Planning (ERP) application.
To add an import mapping for an EPM source application to an EPM target application.
1
In Import Format, from the Import Format summary grid, select an EPM source application.
In the Import Format Detail grid, and then in Source Column, select the dimension to map.
Optional: Add other dimensions as needed by selecting a dimension type from the Add drop-down.
Available options:
Currency Row
Attribute Row
Description Row
Dimension Row
In the Expression field, enter an expression or import script to the import format.
When entering a constant, you must still enter a starting position and length. Use a start
position of 1 and a length of 1.
See Adding Import Expressions on page 100.
Click Save.
In Import Format, from the Import Format summary grid, select an Enterprise Resource Planning (ERP)
source application.
109
Depending on your selection in this field, the Source fields shows only registered Enterprise
Resource Planning (ERP) sources and file for an ERP source type; or registered EPM
applications.
For example, the Source field may be anFinancial Management or Planning for an EPM
source type.
In the Import Format Detail grid, select the dimension to map from the Source Column drop-down.
Optional: Add other dimensions as needed by selecting a dimension type from the Add drop-down.
Available options:
Currency Row
Attribute Row
Description Row
Dimension Row
In the Expression field, enter an expression or import script to the import format.
When entering a constant, you must still enter a starting position and length. Use a start
position of 1 and a length of 1.
See Adding Import Expressions on page 100.
Click Save.
In Import Format, from the Import Format summary grid, select an EPM source application.
Choose the type of mapping by selecting either the Explicit tab, Between tab, Multi-Dimension, or Like
tab.
l
110
ExplicitThe source value is matched exactly and replaced with the target value. For
example, the source value, ABC is replaced with the target value, 123. Explicit
write-back mappings are created the same for data load and data write-back rules. See
Creating Mappings Using the Explicit Method on page 144.
BetweenThe range of source values are replaced with one target value. For example,
a range from 001 to 010 is replaced as one value: 999. Between write-back
mappings are created the same for data load and data write-back rules. See Creating
Mappings Using the Between Method on page 145.
InIn mappings enable a list of nonsequential source accounts to be mapped to one
target account. In this case, multiple accounts are mapped to one account within one
rule, eliminating the need to create multiple rules (as is required for an Explicit map).
LikeThe string in the source value is matched and replaced with the target value. For
example, the source value, Department is replaced with the target value, 'Cost Center
A. See Creating Mappings Using the Like Method on page 147.
Write-back mappings provide a means to remove or strip characters that were added
during the data load process. Like write back mappings are created similar to, but
reverse from the data load.
l
Tip: You can click Refresh Values to refresh the list of segment or chartfield values that
appear in the drop-down list from the source system. This is especially helpful when
creating Explicit, Between, Like, and Multi-Dimension mappings for data
write-back data loads.
In Source Type select EPM, and then select Planning or Essbase as the source.
In Target Type, select ERP, and then select EBS or PeopleSoft as a target.
Click Save.
Defining Locations
You define locations to specify where to load data to a target system. That is, a location is the
level at which a data load is executed in FDMEE. A location is associated with one source system,
but you can import data from multiple ledgers from that system. Each location is assigned an
import format, one or more Data Load Rules, and a Data Load Mapping. Additionally, locations
enable you to use the same import format for more than one target application where the
dimensionality of the target applications is the same.
The Location feature also enables you to specify free form text or a value using the integration
option feature. Text or values entered for a location can be used with your FDMEE scripts.
Note: You can create duplicate locations with the same source system and application
combination.
111
In Accounting Entity, specify the source system accounting entities (business units or ledgers) to use
for the location.
For Fusion and E-Business Suite source systems, the Accounting Entity is the ledger. For
PeopleSoft source systems, the Accounting Entity is the business unit.
If the accounting entity is selected here, then in the Data Load Rules, accounting entity
populates automatically.
If the accounting entity is not specified here, you can specify the accounting entity in data
rules. Doing so enables you to load data from multiple ledgers to business units from one
location.
You can use locations with multiple import formats. For example, you can define the import
format for the first location, Ledger 1. Then, define another import format for Ledger 2. In
this case, you would create multiple locations with the same import format. You can also
define multiple locations for target applications that are the same. In this case, you can define
multiple locations for each business unit or ledger and reuse the import format.
In Target Application, specify the target application associated with this location.
system, the Functional Currency column displays NA. Unlike PeopleSoft Enterprise
Financial Management source systems, when FDMEE human resources data loads
occur, there is no break out of amount by functional, entered, or translated currencies.
Parent mapping are used to share mappings with other locations. Enter mappings at the
parent location, and the related locations can use the same mappings. Multiple locations
can share a parent. This feature is useful when multiple locations use one chart of accounts.
Changes to a child or parent mapping table apply to all child and parent locations.
10 In Data Value, specify the extra dimension that is used only for integration with multiple dimension
target systems.
112
This dimension is associated with a data load location. In Financial Management, the data
value is the value dimension. WhenFDMEE creates the load file, the dimension value is
entered for every data line that is loaded by the location. For example, the Data Value
dimension is associated with the Value dimension in Financial Management. By default, if
no value is entered in this field, for integration with Financial Management, the Data Value
<EntityCurrency> is the default value.
When Search is selected, FDMEE connects to the Financial Management to get a list of valid
data values. FDMEE takes the values from Financial Management and adds rows created by
FDMEE that are a concatenation of the original value and Adjustment Data Values.
FDMEE uses these newly created rows to manage journal loading to Financial Management.
The rows that FDMEE creates in the Data Value selection screen are:
l
11 Optional: In Logic Account Group, specify the logic account group to assign to the location.
A logic group contain one or more logic accounts that are generated after a source file is
loaded. Logic accounts are calculated accounts that are derived from the source data.
The list of values for a logic group is automatically filtered based on the Target Application
under which it was created.
12 Optional: In Check Entity Group, specify the check entity group to assign to the location.
When a check entities group is assigned to the location, the check report runs for all entities
that are defined in the group. If no check entities group is assigned to the location, the check
report runs for each entity that was loaded to the target system. FDMEE check reports
retrieve values directly from the target system, FDMEE source data, or FDMEE converted
data.
The list of values for a check entity group is automatically filtered based on the Target
Application under which it was created.
13 Optional: In Check Rule Group, specify the check rule group to assign to the location.
113
System administrators use check rules to enforce data integrity. A set of check rules is created
within a check rule group, and the check rule group is assigned to a location. Then, after
data is loaded to the target system, a check report is generated.
The list of values for a check rule group is automatically filtered based on the Target
Application under which it was created.
14 Click Save.
15 Optional: Perform these tasks:
l
To edit an existing location, select the location to modify, and then make changes as
necessary. Then, click Save.
To delete a location, click Delete.
When a location is deleted, the location is removed from all other FDMEE screens, such
as Metadata, and Data Load.
Tip: To filter by the location name, ensure that the filter row is displayed above the column
headers. (Use
From Integration Option, in Integration Option 1-4, specify the free form text or value, and then click
OK.
The information is accessible from the Integration Option fields in the Location table.
Global Mappings
Application Mappings
Source Mappings
You have the flexibility to use various kinds of calendars (for example, monthly, weekly, or daily)
based on your business and statutory requirements. In your EPM system, you can also use
different calendars, based on your application requirements (for example, different levels of
periods). Because FDMEE extracts the Enterprise Resource Planning (ERP) source system data
to the target EPM application, establish the mapping relationship by defining a period mapping
between the source ERP source system periods and the target EPM application periods.
Before you can define data rules, define the period mappings. Period mappings define the
mapping between Enterprise Resource Planning (ERP) calendars and the EPM application year
or periods. You can define period mappings in three ways:
114
Global MappingYou define a global mapping in cases where you do not have many target
applications getting data from multiple source systems with different types of source
calendars. Use a global mapping to ensure that various periods are accommodated in the
individual mapping. As a first step, define a global mapping.
Application MappingIf you have multiple target applications, getting data from various
source systems with complex period types, you can create application mappings in addition
to global mappings. When you define an application mapping, you can modify the Target
Period Month as necessary.
Source MappingSpecifies source period mapping for adapter based integrations.
monthly calendar and a weekly calendar, define your global mapping at the lowest level
of granularity. In this case, the period keys are at the week level. and you map weeks to
months. You can create application mappings for the higher-level periods.
Table 18
Period Key
Prior Period
Key
Period Name
Target Period
Month
Target Period
Quarter
Target Period
Year
Target Period
Day
Year Target
Jan 1 2010
Dec 1 2009
January 1, 2010
Jan
Q1
FY10
Feb 1 2010
Jan 1 2010
February 1,
2010
Feb
Q1
FY10
Mar 1 2010
Feb 1 2010
March 1, 2010
Mar
Q1
FY10
April 1 2010
March 1 2010
April 1, 2010
Apr
Q2
FY10
May 1 2010
April 1 2010
May 1, 2010
May
Q2
FY10
Period Key
Prior Period
Key
Period Name
Target Period
Month
Target Period
Quarter
Target Period
Year
Target Period
Day
Year Target
Jan 26 2009
Jan 19 2009
January 26,
2010
Jan
Q1
FY09
Feb 2 2009
Jan 26 2009
February 2,
2010
Feb
Q1
FY09
115
Period Key
Prior Period
Key
Period Name
Target Period
Month
Target Period
Quarter
Target Period
Year
Target Period
Day
Year Target
Feb 9 2009
Feb 2 2009
February 9,
2010
Feb
Q1
FY09
Feb 16 2009
Feb 9 2009
February 16,
2010
Feb
Q1
FY09
Period Key
Year Target
Jan 1 2009
Jan
Q1
FY09
Feb 1 2009
Feb
Q1
FY09
Mar 1 2009
Mar
Q1
FY09
Period Key
Jan 26 2009
Jan
Q1
FY09
Feb 2 2009
Feb
Q1
FY09
Feb 9 2009
Feb
Q1
FY09
Feb 16 2009
Feb
Q1
FY09
Note: To avoid double counting on Income Statement accounts, be sure not to define a mapping
where the adjustment period of one year goes into the period of the next fiscal year.
Adjustment Period MappingMapping the Period Key to the Adjustment Period
Note: If YTD is selected as the Enterprise Resource Planning (ERP) source, then the adjustment
period becomes the ending balance (replaces the period 12). If PTD, then the adjustment
period gets added to period 12.
116
Year Target
Table 22
Period Key
Calendar
Adjustment Period
Description
Dec-2003
Accounting 13
13-03
Dec-2004
Accounting 13
13-04
Dec-2005
Accounting 13
13-05
Dec-2007
Accounting 13
13-07
Note: If the source is PeopleSoft General Ledger, set the adjustment period mapping with the
Global Mappings
You can define one global mapping to map various periods to the individual mapping.
Click Add.
Year Target
Note: Period dimension members in Performance Management Architect that have the
Click Save.
Application Mappings
You can define application mappings in cases where you want to define a special period mapping
for a specific target application. The mappings that you create here apply to an individual target
application.
117
Click Add.
Click Save.
Source Mappings
Source mappings include explicit and adjustment period mappings. You can create explicit
period mappings to ensure that the FDMEE periods map correctly to the source system calendar
periods. An adjustment period mapping is used only when you select the Include Adjustment
Periods option when creating the data load rule.
The Source Mapping tab consists of two areas:
l
For (E-Business Suite, Fusion, and PeoplesSoft) source systems, you can select explicit or
adjustment systems. For all other systems, you can select only an explicit mapping.
Note: In Data Rules, you can choose between Default period mapping and Explicit Period
mapping. If you choose Period mapping, then source periods are mapped based on the
period key and previous period.
For SAP and JD Edwards source systems, you must select Explicit period mappings.
118
For all other systems (for example, file based and Fusion), you can select Explicit or
Adjustment.
Click Add.
Enter the source system Period Name, and then click OK.
Note: Period names cannot include spaces if used in a batch script.
Enter the source system Period Key, and then click OK.
Click Add.
Click
to select the source system Period Key, and then click OK.
Click
Click
to select the source system Adjustment Period, and then click OK.
For PeopleSoft source systems only: In GL Period Year, enter the general ledger period year.
The general ledger period year is required for PeopleSoft source systems because PeopleSoft
Adjustment Periods definitions do not include a Year value. To properly map adjustment
period data from PeopleSoft, define the source accounting period and fiscal year
intersections for all PeopleSoft adjustment periods.
10 Click Save.
Click Add.
119
Note: From PeopleSoft Commitment Control, only Budget Period data can be extracted.
The source calendar/period are based on the control budget definition in PeopleSoft.
Enter the source system GL Period, and then click OK. You can also or click
the GL period name.
Click Save.
Tip: To delete a mapping, select the mapping, and then click Delete.
Global Mappings
Application Mappings
You define category mappings for categorizing and mapping source system data to a target EPM
Scenario dimension member. For example, in a Financial Management application, you may
have a Scenario dimension member called Actuals for storing actual balances from a source
system. In a Planning application, the same source system data is stored using the Scenario
dimension member Current. In FDMEE, you can create one category mapping to give both
one name to represent their respective scenarios.
Global Mappings
You can define one global mapping to map various Scenario dimensions to the individual
mapping.
The global category mappings lets you define mappings that cross multiple applications. For
example, you may have a case where a source category of an actual may map to a target of an
actual in the majority of the cases. But you may have a case where you have a target application
where the actual may map to current. In this case, it provides the ability to override the global
mapping on an application basis.
120
Click Add.
The category indicates the frequency defined in the period mapping, for example, Daily,
Monthly, Quarterly, or Yearly.
Click Save.
To edit a mapping, select the mapping, make changes as necessary. and then click
Save.
To delete a mapping, click Delete.
Application Mappings
Unlike global mappings, application mappings can be defined for a target application.
Click Add.
Click Save.
To edit an mapping, select the mapping, and then make changes as necessary. Then,
click Save.
To delete a mapping, click Delete.
121
122
Loading Metadata
2
In This Chapter
Loading data from the General Ledger source systemFDMEE supports loading data from
general ledger source systems. FDMEE can load both metadata (dimension members and
hierarchies from E-Business Suite, Oracle Fusion Financials and PeopleSoft Enterprise
Financial Management only) and data from the Enterprise Resource Planning (ERP) source
systems.
Writing back data to the General Ledger source systemFDMEE enables you to extract data
from Planning, Essbase aggregate storage, Essbase block storage, Financial Management,
and then load it into the General ledger source system.
Data load to write-back is unavailable for SAP and JD Edwards. The suggested approach to
write back to these Enterprise Resource Planning (ERP) systems and other legacy
applications is to extract data to a custom application (data file) and converting them to a
format acceptable to ERP systems and importing them as journals.
Requirements
Before you begin using FDMEE, consider the following:
l
123
You can build EPM applications with any combination of dimensions. The combination
must include required dimensions for the selected application. Member Properties Sourced
from the Enterprise Resource Planning (ERP) System on page 125 describes how member
properties are sourced from the Enterprise Resource Planning (ERP) source system.
l
Duplicate MembersTo avoid issues with duplicate member names, as a best practice,
include a unique prefix or suffix for each dimension so each member is always unique.
Duplicate Alias MembersIf your application has duplicate alias members, it is
important to remove any duplicates in the target application or validation errors occur
when you deploy the application in Performance Management Architect.
Note: Source descriptions must be unique to avoid alias validation errors with
Required Dimensions
You can build EPM applications with any combination of dimensions, as long as the
combination includes those required for the selected application. For example, Planning requires
different dimensions to be present in an application than in Financial Management.
For detailed information on dimensions required and properties for Performance Management
Architect applications, see the Oracle Hyperion Enterprise Performance Management Architect
Administrator's Guide. For Classic Planning applications, see the Oracle Hyperion Planning
Administrator's Guide. For Classic Financial Management applications, see the Oracle Hyperion
Financial Management Administrator's Guide. For Classic Essbase, see the Oracle Essbase
Database Administrator's Guide.
The following dimensions require special considerations when integrating with FDMEE:
l
Account
Currency
Entity
Scenario
Version
View
Year
Period
124
In addition to the above list, review properties set by FDMEE in the Custom dimension. See
Custom on page 128.
For information on special considerations and requirements for Public Sector Planning and
Budgeting, see Chapter 6, Loading Human Resources Data.
Account
Entity and Intercompany
Scenario
Version
View
Year and Period
Alias
Custom
For each required dimension, specific properties must be defined. The required dimension
properties relate to Planning, Financial Management, or Essbase applications, and in some cases
both.
Note: FDMEE sets some of the required properties, but not all.
Account
The Account dimension represents a hierarchy of natural accounts. Accounts store financial
data for entities and scenarios in an application. Each account has a type, such as Revenue or
Expense, that defines its accounting behavior. The Account dimension is mapped from the
source accounting entity to the EPM Account dimension as defined in the dimension mapping
definition for the selected chart of accounts or business unit. The properties set by FDMEE are
shown below. (Any properties not set are defaulted by the application or Performance
Management Architect).
Property
Application Type
Population Method/Value
Consolidation
Account Type
Consolidation
Populated from the account type in the source accounting entity with the domain of
revenue, expense, asset, or liability. If source type is equity, it is changed to liability for
use by Financial Management applications.
Account Type
Planning
Populated from the account type in the source accounting entity with the domain of
revenue, expense, asset, liability or equity.
125
Property
Application Type
Population Method/Value
Variance Reporting
Planning, Essbase
aggregate storage,
and Essbase block
storage
Description, Display
String
System
Time Balance
Planning, Essbase
aggregate storage,
Essbase block
storage
For income statement accounts, (revenue and expenses) set to Flow for Planning
applications.
For Essbase aggregate storage and block storage applications, set to Last.
For balance sheet accounts (asset, liability, and equity), set to Balance.
These properties can be set when you create metadata rules. See Defining Metadata
Rules on page 132.
Application Type
Population Method/Value
Name
Consolidation,
System
Description
System
126
Property
Application Type
Population Method/Value
IsICP
Consolidation
If the intercompany segment exists in the source, then this flag is set automatically per the rules defined.
If the intercompany segment does not exist, then you specify how this property is set. See Entity and
Intercompany on page 126.
Note: For ICP transaction data to load correctly, you must manually set the property ISICP=Y for those
accounts participating in ICP. In Performance Management Architect, you can use the Property Grid to
modify the property. If using Financial Management Classic application administration, extract the
metadata, update, and then re-import it back. After modifying the property, you can load data correctly
for ICP transactions.
Currency
Consolidation,
Essbase,
Planning
Note: These are the only properties that are set as part of the FDMEE integration, all others are
defaults when you create new members. If a property was originally set by FDMEE, and
you change it later, the property is overridden.
Scenario
The Scenario dimension represents a set of data, such as Budget, Actual, or Forecast. For example,
the Actual scenario can contain data from a general ledger, reflecting past and current business
operations. The Budget scenario can contain data that reflects the targeted business operations.
The Forecast scenario typically contains data that corresponds to predictions for upcoming
periods. A Legal scenario can contain data calculated according to legal GAAP format and rules.
Version
The Version dimension is specific to EPM applications and usually does not have a source in
the source accounting entity. Since it is required, you must specify the necessary default value
in the member mapping by using the Like mapping type. When defining the data rule in
FDMEE, select the desired Version to include with the extracted data. Since the Version
dimension is not extracted from the source system, it is not necessary to define specific properties.
View
The View dimension represents various modes of calendar intelligence; for example, Periodic,
Year-to-Date, and Quarter-to-Date frequencies. FDMEE extracts only data that is below the
quarter level. You select the view as part of the data rule definition, and when the data is extracted,
it includes the View selection as the value for the dimension on each row. See Defining Data
Load Rules to Extract Data on page 161. Since the View dimension is usually not extracted
from the source system, it is not necessary to define specific properties. However, before the data
extraction process, you must create all members in the View dimension manually.
127
in each branch of the Period dimension. For example, Q4 has October, November,
December children and an adjustment period in Performance Management Architect.
Alias
For Planning and Essbase, the Alias dimension or table is required to support languages. Keep
in mind these special considerations:
The Alias dimension must include a member named Default.
If the dimension name is not the same as the Alias name in a Performance Management
Architect Planning application, the drill through landing page does not return any data.
When creating Alias table members in a dimension, define them with the same name that
is displayed in Oracle Fusion, E-Business Suite, or PeopleSoft. This is the value of the
NLS_LANGUAGE column.
Custom
The properties set by FDMEE are shown below. (Any properties not sets defaults in the
application or in Performance Management Architect.)
Property
Application Type
Population Method/Value
Name
System
Description
System
process populates dimension members directly into the application based on the mapping rule
details created in FDMEE.
As part of the extract process, the dimension members are directly loaded into the target
Performance Management Architect dimension, with specific properties defined as described
in Member Properties Sourced from the Enterprise Resource Planning (ERP) System on page
125. In addition to loading dimension members, the related alias entries are also loaded to
provide the appropriate language support.
Shared dimensions from EPMA are not selected directly from the shared library for loading.
FDMEE presents the dimensions in the target application for inclusion in a metadata rule, and
then updates the shared library automatically when updating the target application. Dimensions
in the shared library cannot be directly loaded, but must be included in a target application to
enable loading from an Enterprise Resource Planning (ERP) source.
The FDMEE dimension extract process:
1. Extracts the general ledger segment or chartfield value sets from the source system.
l
Only general ledger segment value set members or chartfield members that are relevant
to the source chart of account segments or chartfields mapped to Classic Financial
Management, or Planning are extracted.
The members are loaded into a staging table on the target instance. Before loading them
into the staging table, FDMEE assigns the segment values a prefix defined for the
corresponding EPM application dimension.
129
concatenated segment, the new dimension is created based on a user-defined traversal order
of the source hierarchies into the concatenated member target hierarchy.
The languages displayed in the Default Language drop-down list are FDMEE supported
languages. These languages are mapped behind the scenes to the Enterprise Resource
Planning (ERP) source system languages.
The Alias dimension in Essbase and Planning applications has a required Default member.
The FDMEE language that you select when registering a target application is automatically
mapped to the Default member. Because the FDMEE language is mapped to the source
language for the member description, you map the base or enabled source language in the
source system to the Default alias member. During processing, all other languages are
mapped to the other alias members as long as the alias member exactly matches the FDMEE
source language for the member description.
Note: Language processing is the same for Essbase and Planning applications.
Note: Financial Management languages are processed based on the default language that you
130
All rates are extracted and inserted into the AIF_HS_EXCHANGE_RATES table. This table is
populated using the ISO currency code for each currency from the source system. The ISO
numeric code is not used in this processing.
Exchange rates are pushed into Planning based on a match between the ISO currency code in
the AIF_HS_EXCHANGE_RATES table and the currencies defined in the multi-currency
Planning application. (It is important to set up the currencies in the Planning application with
ISO currency codes.) Then, perform any currency conversions with those rates, as nothing is
recalculated as part of this process.
Any data that is coming in with the default currency of the Planning application is loaded to
locale.
For Financial Management, data is loaded to value dimension specified in the Location. Typically
it is set to <Entity Currency>.
Note: Exchange rates are not interfaced directly into Financial Management. You should
manually access them from the AIF_HS_EXCHANGE_RATES table and insert them into
Financial Management.
The only operations between hierarchy management in the source system and target
application are creating and updating the hierarchies by merging in the target. FDMEE never
deletes hierarchies or members in a target application. If additional members or hierarchies
are not specified, FDMEE ignores them.
When you integrate a hierarchy from the source system to the target system, select the node
from the source that serves as the root node in the target.
The integration pushes the hierarchy into the target system and reports any errors
encountered during the process.
You can use the Process Details page to view errors logged in FDMEE. You can also select
the Log link to review the Oracle Data Integrator log file. For Performance Management
Architect applications, you can also view profile creation errors in the Job Console. See
131
Viewing Process Details on page 202 or the appropriate product documentation for
additional information.
l
A hierarchy selection in the dimension mapping is optional; however, you must at least
determine how to handle members not in a hierarchy. For example, you can create children
of a selected node as orphans, or you can choose not to carry over orphans. (This option
applies only to Performance Management Architect).
You can create metadata rules once and rerun the rules as necessary.
For general ledger source systems:
l
For Fusion and E-Business Suite source systems, the chart of accounts is the collection of
general ledger segments with various value sets, which are mapped to the dimensions to pull
the dimension members and hierarchies.
Similarly for PeopleSoft Enterprise Financial Management, the chartfields are mapped to
the dimensions to pull the dimension members and hierarchies.
Note: Metadata rules are not used in FDMEE integrations with human resources source systems.
Ensure that your source system data does not include special characters, which are not
supported in Financial Management target applications.
Register your source systems and target applications for use with FDMEE. See Registering
Enterprise Resource Planning (ERP) Source Systems on page 53 and Registering Target
Applications on page 67.
Select the source accounting entities in the registered source system. See Selecting Source
Accounting Entities on page 87.
Define the import format. See Working with Import Formats on page 91.
Note: Performance Management Architect supports Shared and Local dimensions. FDMEE also
132
From the POV bar, select the location to use for the metadata rule.
Click Add.
A blank line is displayed at the top of the Dimension Mappings summary grid.
Define the mapping details for each dimension that you select.
Click Save.
133
Member prefixes are inserted before the source member code. Although optional, it is
important to prefix the segment values with a prefix defined for the corresponding
dimension when those members do not exist in the target application.
Member suffixes are inserted after the source member code.
Note: When you perform the next steps to define the hierarchy region starting parent,
consider that Planning, Essbase, and Financial Management do not allow members
to roll up to the parent under the same root. When extracting, specify hierarchies
where every node has one parent. Fusion and E-Business Suite support instances
where a segment value can roll up to two parents.
Merge as PrimaryMerge as Primary processes all sections and adds new dimensions,
members, relationships, properties and associations that exist in the source, but do not
exist in the Shared Library or target application. No dimensions, members,
relationships, properties, or associations are removed. If a dimension, relationship,
member, or property specified in the source exists in the Shared Library or target
application it is overwritten with the value specified in the source. (Members are not
moved, but overwritten.) Properties not included in the source are unchanged in the
Shared Library or target application.
Note: If a member has multiple instances in a dimension, the IsPrimary column
specifies which instance is primary and which instances are shared. The IsPrimary
parameter is optional; however, Oracle strongly recommend that you use it. If
left undefined, it defaults to True, which assumes that the member is primary.
If you do not define the IsPrimary parameter or when there are duplicate
members defined as primary, a warning is displayed in the Import Results file.
l
Merge as MoveThis mode processes only members with IsPrimary set to true, and
ignores any others. During processing, the first line specifying a primary location for a
member is executed, any subsequent lines specifying a different primary location are
ignored, and a warning message is displayed.
ReplaceAll new elements are added and all property updates are made. Then, any
members or member relationships that are not specified in the source are deleted from
the Shared Library or target application. You can also use replace mode to reorder
members under a parent. Properties not included in the source are unchanged in the
Shared Library or target application.
This mode does not create Shared members unless they are defined in the import file
(IsPrimary=false). This mode can detect a primary member under a new parent and
process it as a move.
Note: The Replace option does not display the Reorder Type and Reorder Existing
Members options.
134
a. For Planning and Essbase applicationsAccount dimension mapping details. Select the
Time Balance Property for Balance Sheet Accounts and Time Balance Property for
Income Statement Accounts.
The time balance property specifies how the value of summary time periods is calculated.
If set to Flow, it is an aggregate of all values for a summary time period as a period total.
If the time balance property is set to Balance, it is considered an ending value in a
summary time period for the period total.
b. From the Hierarchy Region tab, click Add to define the hierarchy region.
c. Click
a. From the Hierarchy Region tab, click Add to define the hierarchy region tree.
b. In Tree, enter the tree name for the hierarchical structure.
Trees depict hierarchical structures that represent a group of summarization rules for
a particular database field. For example, a tree can specify how your manufacturing
locations should be summarized, or rolled up, for reporting purposes. Or a tree can
show the reporting relationships within an organization by specifying how the
individual department should be summarized into territories, territories into regions,
and regions into countries. Similarly, a tree can categorize items in a catalog.
c. in Effective Date, specify the effective date of the tree.
Using effective dates with trees enables you to specify new objects, departments,
reporting relationships, or organizational structures in advance and have them take
effect automatically. You can also use trees with past, present, or future effective dates
when reporting on current or historic data.
d. Click
135
f.
Select a prefix or suffix for the hierarchy, and then enter a prefix/suffix value.
The parent prefix is applied only to the parent. To enable alternate rollup hierarchies,
the Prefix/Suffix value applies only to parent members. Parent members cannot be
shared and must have a unique name. In addition, parent members do not store data.
g. From Select how to process source orphan members, select the method for handling
orphan members:
IgnoreNo orphan members from the source are extracted.
Create as Root MemberRoot members are created, and orphan members are
not. All members are created at the top level of the hierarchy.
Planning only: Select the Plan Type for the Accounting and Entity dimensions.
Financial Management only: If you are mapping an Entity dimension, enter the following details for
intercompany segments, depending on your source system:
l
In the scenario where the Intercompany segment is defined, the Intercompany transactions
are identified based on the Intercompany segment. Typically, one set of natural accounts is
required for accounting the receivable and payable among the Intercompanies.
In the scenario where there is no Intercompany segment, identify the Intercompany
transactions based explicitly on the natural account segment. Typically, all combinations of
receivable and payable accounts exist among the transacting partner companies. Only with
these natural accounts are the receivable and payable position between the Intercompanies
known.
Click Save.
values.
Table 23
Application Type
Dimension
Attribute
Planning
Account
136
Application Type
Dimension
Attribute
Time Balance for Income Statement
Data Storage Parent (sets the default for a parent node that you want to make different from the child
node. In some cases, the child and parent data storage attributes are not the same, and this lets you
specify the appropriate default for this attribute for a parent.)
Data Storage
Expense Reporting
Account Type
HFM
Account
HFM
Entity
IsICP
Currency
Essbase
Account
In Time Balance for Balance Sheet, Time Balance for Income Statement, and Expense Reporting,
specify how the value of the summary time periods is calculated.
Flow it is an aggregate of all values for a summary time period as a period total. If the time
balance property is set to Balance, then it is considered an ending value in a summary time
period for the period total.
To use the system default, click Use System Default.
To use the custom default value, clear the Use System Default field.
Click Save.
137
Check the metadata rule process detailsSee Deleting Metadata Rules on page 138.
Click Save.
138
Click Delete.
139
140
In This Chapter
Overview .................................................................................................. 141
Loading Data ............................................................................................. 142
Synchronizing and Writing Back Data .................................................................. 218
Overview
FDMEE supports a variety of ways for importing data from a range of financial data sources,
and then transforming and validating the data:
l
Data Loadingdefine the mappings from a source system to a target system; drill through
and view data in the ERP source system from an EPM target application; load data from
file-based source systems to an EPM target application; and define data load rule, which
describes how to extract and push data from source to target systems.
Synchronizingmove data between the EPM applications irrespective of the dimensionality
of the application without having to create a data file from the EPM source application.
Write-backwrite-back budget data to the source system from all EPM applications to ERP
applications. This feature offers significant advantages, such as writing back budgets created
in Planning to Peoplesoft or theE-Business Suite ERP GL, or moving adjustment journals
from Financial Management to ERP systems like E-Business Suite or Peoplesoft. Write-back
budget data is also available to a file-based source system from an Planning, Oracle Essbase
ASO, and Essbase ESO applications.
Watch this tutorial video to learn more about loading data in Oracle Planning and Budgeting
Cloud using Data Management.
Watch this tutorial video to learn about extracting data from Oracle Planning and Budgeting
Cloud using Data Management.
141
Loading Data
Subtopics
l
l
l
l
l
l
l
l
l
You use member mappings to derive the target members for each dimension based on source
values. Member mappings are referenced during the data load, enabling FDMEE to determine
how to dimensionalize the data that is loaded to the target application. They define relationships
between source members and target dimension members within a single dimension. You must
create a member mapping for each target dimension.
The five types of member mappings:
l
ExplicitThe source value is matched exactly and replaced with the target value.
142
The following table is an example of a member mapping, where three segment members,
Cash-101, Cash-102, and Cash-103 map to one EPM member Cash.
Segment/Chartfield Member
EPM Member
Cash-101
Cash
Cash-102
Cash
Cash-103
Cash
Expense-1
Expense
Expense-2
Expense
You can use special characters for the source and target values. See Using Special Characters in
the Source Value Expression for Like Mappings on page 148 and Using Special Characters in
the Target Value Expression on page 151.
On the Workflow tab, under Data Load, select Data Load Mapping.
Choose the type of mapping by selecting the Explicit tab, Between tab, Multi-Dimension tab, or Like
tab.
Note: If you defined a metadata mapping for the dimension, FDMEE automatically creates
a Like member mapping. If you entered a member prefix, the same member prefix
is automatically entered as the target value in the member mapping. DEFAULT
displays in the rule name and description field for system-generated mappings. When
data is extracted, user-defined mappings are extracted first, and then system generated
mappings.
Type options:
l
ExplicitThe source value is matched exactly and replaced with the target value. For
example, source value "ABC" is replaced with target value "123." See Creating Mappings
Using the Explicit Method on page 144.
BetweenThe range of source values are replaced with one target value. For example,
a range from 001 to 010 is replaced as one value: 999. See Creating Mappings
Using the Between Method on page 145.
InIn mappings enable a list of nonsequential source values to be mapped to one target
value. In this case, multiple values are mapped to one value within one rule, eliminating
143
the need to create multiple rules (as is required for an Explicit map). For example, you
could have source accounts 1503, 1510, and 1515 map to the target account 15000010.
l
LikeThe string in the source value is matched and replaced with the target value. For
example, the source value Department is replaced with the target value Cost
CenterA. See Creating Mappings Using the Like Method on page 147.
When processing the source values for transformations, multiple mappings may apply to a
specific source value. The order of precedence is Explicit, Between, In, Multi-Dimension,
and Like. Within Between and Like types, mappings can overlap.
The rule name determines precedence within a mapping type. Rules are processed in
alphabetical order of the rule name within a mapping type. Numbers may also be used to
help with ordering. For example, if numbering by tens or one hundreds, you can insert new
rules between existing ones. So if rules are numbered 10,20,30, you can add a rule that starts
with 25 and need not rename other rules.
Tip: You can click Refresh Values to refresh the list of segment or chartfield values that are
On the Workflow tab, under Data Load, select Data Load Mapping.
Click Add.
to select a value.
See Using Special Characters in the Source Value Expression for Like Mappings on page
148.
144
to select a member.
See Using Special Characters in the Target Value Expression on page 151.
To reverse the sign of the target account specified, select Change Sign.
10 Select Apply to Rule to apply the mapping only to the specific data rule in the location.
For other data rules in the location the mapping are not applied.
By default, mappings specified at a location are applicable to all data rules in a location.
11 Click Save.
On the Workflow tab, under Data Load, select Data Load Mapping.
Click Add.
to select a member.
The target value is the dimension member name. See Using Special Characters in the Target
Value Expression on page 151.
To reverse the sign of the target account specified, select Change Sign.
10 Select Apply to Rule to apply the mapping only to the specific data rule in the location.
For other data rules in the location the mapping are not applied.
By default, mappings specified at a location apply to all data rules in a location.
11 Click Save.
145
To create an In mapping:
1
On the Workflow tab, under Data Load, select Data Load Mapping.
The source value is the Enterprise Resource Planning (ERP) segment value. In mappings
enable you to specify nonsequential source values. Separate source values with a comma.
For example 100,199.
To reverse the sign of the target account specified, select Change Sign.
Select Apply to Rule to apply the mapping only to a specific data rule in the location.
to select a member.
For other data rules in the location the mapping are not applied.
By default, mappings specified at a location apply to all data rules in a location.
10 Click Save.
On the Workflow tab, under Data Load, select Data Load Mapping.
146
To reverse the sign of the source account value, select Change Sign.
Explicit
Between
Like
In
15 Click Save.
On the Workflow tab, under Data Load, select Data Load Mapping.
Click Add.
147
The source value is the Enterprise Resource Planning (ERP) segment value. Like source
write-back mappings support special characters. See Using Special Characters in the Source
Value Expression for Like Mappings on page 148.
to select a member.
The target value is the EPM dimension member name. Like target write-back mappings
support special characters. See Using Special Characters in the Target Value Expression
on page 151.
To reverse the sign of the target account specified, select Change Sign.
10 Select Apply to Rule to apply the mapping only to a specific data rule in a location.
For other data rules in the location the mapping are not applied.
By default, mappings specified at a location apply to all data rules in a location.
11 Click Save.
Using Special Characters in the Source Value Expression for Like Mappings
The Source and Target Value expressions can have one or more special characters. Special
characters are supported for Like mappings only.
l
Asterisk (*)
An asterisk (*) represents the source value. The asterisk (*) can be prefixed or suffixed by
one or more characters, which filters the source value by that prefix or suffix. The wild card
or strips (data load to write back) takes whatever is present in the source and puts it in the
target column, usually adding a prefix.
148
Note: <1>, <2>, <3>, <4>, <5> can be used with a question mark (?) but cannot be used
Special
Character(s) Used
Mapping
Type
Source
Value
Target
Value
Result
Notes
Data Load
1000
Data Load
Stripping
A*
Stripping
*_DUP
Stripping
?*
Stripping
*????
Data Load
<1>
01_420 returns 01
Data Load
<2>
149
Special
Character(s) Used
Mapping
Type
Source
Value
Target
Value
Result
Data Load
<3>
01_420_AB_CC1_001
returns AB
Stripping
?<1>
A01_420 returns 01
<BLANK>
Data Load
<BLANK>
[None]
Notes
Automap Wildcarding
FDMEE enables target-account or target-entity derivation by permitting wildcard characters (*
and ?) in source and target members. Mapping-table records that have wildcard characters in
the source and target column are considered automapped.
FDMEE does not validate the target value.
Example Automap
Rule Name
Rule Description
Source Value
Target Account
w0011--
Cash Accts
0011??
Cash.??
Center
Description
Amount
001100
0160000
Cash In Bank
1000.00
001101
0000000
Cash Corp LB
2000.00
001116
0001000
Petty Cash
1000.00
223500
0160000
AP
5000.00
Hyperion Account
001100 0160000
Cash.00
001101 0000000
Cash.01
001116 0160000
Cash.16
150
Conditional Mapping
With conditional mapping, source members are mapped to script expressions rather than to
hard-coded target members. Conditional mapping is valid only for rule-based mapping
(Between, In, and Like). You can activate conditional mapping by placing #SCRIPT or #SQL in
the Target value column. Use #SCRIPT for Jython Script and #SQL for SQL script. Conditional
mapping, in conjunction with dimension processing order, enables mapping that is based on
the results of dimension mappings. That is, dimension mappings that have already been
processed. See Using Mapping Scripts on page 310.
Result:
1000 = A1000
Target Value:
*_DUP
Result:
1000 = 1000_DUP
Note: <BLANK> is supported in the target value expression in data mappings and can be used
in all mapping types (Like, Between, and Explicit). When writing data to an Enterprise
Resource Planning (ERP) GL interface table, the <BLANK> notation may be used for a
target dimension mapping in order to successfully pass the validation step in the workflow
process. For example, when writing back to the Peoplesoft journal interface table, the
specification of <BLANK> can be used when the user does not want to provide a value
for a chart field value, but needs to successfully validate the write-back data.
151
Component
Description
#FORMAT
<format mask>
User defined format mask with the following characters used to define the format:
l
?Include a character from a specific position in the source member or segment within a member.
#Skip or drop a character from the source when creating the target member.
characterInclude the user defined character on the target as- is. Used for prefixing, suffixing or any fixed string
or required character. This can be used in conjunction with the special format mask characters.
*Include all characters from the source segment or source. When * is used as the only format mask character
in a segment, then the entire segment value is copied from the source.
When * is used in conjunction with # or the ? character, then all remaining and unused characters are brought
over.
* is a wildcard character that takes the remaining characters not specified by ? or #. For example, when the
source is abcd and * is used, then the target is abcd. When the target is ?#*, then the result is acd.
If FDMEE encounters a * within a segment, then anything specified after the * is ignored other than the character
specified on the format.
<segment
delimiter>
The optional segment delimiter defines the character that is used to delimit the segments in the source and target
member. For this rule type, the source and target delimiter must be the same. When the segment delimiter is not specified,
then the format mask is applied to the entire member independent of any segment specification or delimiter.
152
Table 26
Source
Target
Result
12345-6789-012-3456ABC-001
#FORMAT(???-*-GROUP-AA##?#*X-GROUP,-)
123-6789GROUPAA5ABCXGROUP
Explanation: Take the first three characters of the first segment, take the entire second
segment, replace the third segment with the text GROUP, prefix the fourth segment
with AA, drop the third and fourth characters, keep the fifth character, drop the sixth
character, keep ABC and add suffix X, replace the fifth segment with the text
GROUP.
Replacing Segments
You may want to use the format of the source member as the definition of the target member,
but replace some of the source segments rather than reuse the values from the source. For
example, you may have a requirement to filter the source by the value of the 4th segment, replace
the 7th segment with an explicit value, and then retain the values of the other segments as in the
following:
Source:
??????-??????-?-012000000-??????-???-???????-??????-??????-??????-???
Target:
??????-??????-?-012000000-??????-???-GROUP-??????-??????-??????-???
Ignore the first two characters and provide the result: 002293. Use #FORMAT(##*).
Truncate the last three characters provide the result: 11002. Use #FORMAT(?????).
Ignore the first two and truncate the last three with the result: 002. Use #FORMAT(##???).
153
On the Workflow tab, under Data Load, select Data Load Mapping.
Click Add.
For example, on the Like tab, enter: 12345-6789-012-3456ABC-001 in the Source Value
field.
Select the format map for the target member using the #FORMAT(<format mask>, <segment delimiter>).
To reverse the sign of the target account specified, select Change Sign.
10 Select Apply to Rule to apply the mapping only to a specific data rule in a location.
By default, mappings specified at a location apply to all data rules in a location.
11 Click Save.
The result of applying format map created in steps 5 and 6: 123-6789-GROUP-AA5ABCXGROUP.
On the Workflow tab, under Data Load, select Data Load Mapping.
For example, assume that a business user does not require extraction of data relating to
Departments 101, 103 and 105. You specify an In mapping with the source values, 101, 103,
and 105, and then in Target, you specify IGNORE. In this way, data relating to
Departments 101, 103 and 105 is extracted, but not written to the application in the Import
Format option.
154
On the Workflow tab, under Data Load, select Data Load Mapping.
Current Dimension
All Dimensions
Optional: If necessary, click Upload to navigate to the file to import, and then click OK.
MergeOverwrites the data in the application with the data in the data load file.
ReplaceClears values from dimensions in the data load file and replaces it with values
in the existing file.
155
Click OK.
In the member mapping import files, FDMEE supports one of the following characters as column
separators:
l
source value
target value
rule name
rule description
Note: If you add a minus sign in front of a target account value, then it is imported with the
Column
Mapping
Explicit Mapping
Source values are enclosed with and separated by a comma (,) for the
In mapping. For example IN 10, 20 is defined as 10,20 in the source
column of the import file.
On the Workflow tab, under Data Load, select Data Load Mapping.
A Maploader.xls file is downloaded. Copy or save the file to your hard drive.
Enter the FDMEE Location name in cell B1 and the Location ID in cell B2.
548??98
??82???
??81*
RangeUse commas (,) to denote ranges (no wildcard characters are allowed).
For example, specify a range as 10000,19999.
(this evaluates all values from 10000 to 19999 inclusive of both start and end values)
In this case, FDMEE considers all values from 10000 to 19999 to include for both
start and end values.
In mapUse commas (,) to separate entries (no wildcard are characters allowed).
You must have at least three entries or the map shows as a between map. For
example, specify an In map as 10,20,30.
Multi-Dimension mapUse #MULTIDIM to indicate its multidimensional
mapping. Enter the DIMENSION NAME=[VALUE] and the value. The Value
157
follows the logic as Wildcard, Range, and In map. In the following example the
search criteria is all ACCOUNT starting with 77 and UD1 = 240. For example,
#MULTIDIM ACCOUNT=[77*] AND UD1=[240].
b. In Source Description, enter a description of the source value.
c. In Target, enter the target dimension value.
Note: FDMEE does not support #SQL and #SCRIPT for Excel mappings.
d. In Change Sign, enter True to change the sign of the Account dimension. Enter False to
keep the sign of the Account dimension. This setting is only used when mapping the
Account dimension.
e. In Data Rule Name, enter the data rule name when the mapping applies to a specific data
rule name.
mapping script.
On the Workflow tab, under Data Load, select Data Load Mapping.
In Select a file to import, select the Excel file to import, and then click OK.
Optional: If necessary, click Upload to navigate to the file to import, and then click OK.
158
MergeOverwrites the data in the application with the data in the Excel data load file.
ReplaceClears values from dimensions in the Excel data load file and replaces it with
values in the existing file.
Click OK.
10 Click OK.
The mapping inherits the default data load rule, and shows the description of System
Generated Mappings.
On the Workflow tab, under Data Load, select Data Load Mapping.
Select Export.
Export options:
Current Dimension
All Dimensions
Export to Excel
From the Specify file location for Current Dimension and All Dimensions export methods, specify the
file name in File Name , or navigate to the file to export, and then click OK.
For the Export to Excel method, mappings are exported to a Microsoft Excel spreadsheet.
Open or save the XSL file as desired.
159
Optional: Click Upload or Download and navigate to the file to export, and then click OK.
On the Workflow tab, under Data Load, select Data Load Mapping.
For example, select the Explicit tab to view explicit type mappings.
To view all mappings, select the All Mappings tab.
To delete multiple mappings, use the Shift key to select multiple mappings.
To delete all mappings, use Ctl+A key.
In Are you sure you want to delete the selected data load mapping(s), click OK.
Click Save.
On the Workflow tab, under Data Load, select Data Load Mapping.
160
After you define member mappings for the data load rule, define data load rules for ledgers or
business units in your source system. Data load rules are defined for locations that you have set
up. Data load rules are specific to:
l
locations
You can create multiple data load rules for a target application so that you can import data from
multiple sources into a target application. Use the following high-level process to create a data
load rule:
1. Create the data load rule.
2. Define data load rule details.
3. Execute the data load rule.
Source Filters (which consists of three tabs: Source Options, Target Options, and Custom
Options)
See Working with Target Options on page 189 (by location) and Registering Target
Applications on page 67.
See Creating Custom Options on page 189.
Note: Before you create data load rules, ensure that your source system data does not include
special characters, which are not supported in Financial Management target applications.
On the Workflow tab, under Data Load, select Data Load Rule.
Select a Category.
The categories listed are those that you created in the FDMEE setup. See Defining Category
Mappings on page 120.
In Period Mapping Type, select the period mapping type for each data rule.
Valid options:
l
DefaultThe Data Rule uses the Period Key and Prior Period Key defined in FDMEE
to determine the Source General Ledger Periods mapped to each FDMEE period
included in a Data Rule execution.
ExplicitThe Data Rule uses the Explicit period mappings defined in FDMEE to
determine the source GL Periods mapped to each FDMEE Period included in a Data
Rule execution. Explicit period mappings enable support of additional GL data sources
where periods are not defined by start and end dates.
NoneWith source adaptors use this option to ignore source period mappings. Thus,
all imported data rows are mapped to the FDMEE period selected in a Data Rule
execution.
Location Type
Import Format
Type
Period Mapping
Default
Explicit Period
Mapping
Period Mapping
Include Adjustment
Periods
Explicit
With Accounting
Entity
Standard
Yes
Yes
N/A
Yes
Without Accounting
Entity
Standard
Yes
Yes
N/A
Yes
With Accounting
Entity
Source Adapter
N/A
N/A
Yes
Without Accounting
Entity
Source Adapter
N/A
N/A
Yes
The following options may appear in the Details section or the Source Options section
depending on the source system.
l
Plan Type (Planning and Essbase)Select the plan type which contains only the
dimensions, members, and data values relevant to that plan type. The plan type applies
to the source or target system depending on the POV location for this data load rule.
Zero BalancesFor SAP and JDE, select the zero balances option:
m
162
For example when there is a debit of 5 and a credit of 5, then the zero amount is
included.
m
Exclude No ActivityZero balances are excluded when the beginning balance debit,
beginning balance credit, period debit and period credit equal 0 (begin_bal_dr,
begin_bal_cr, period_dr, period_cr all have 0 for the YTD balance type, or the period
debit and the period credit have a period for the period balance type (period_dr,
period_cr equals 0 for the Periodic balance type).
Exclude Zero Net BalanceZero net balances are excluded when the beginning
balance debit minus the beginning balance credit plus the period debit minus the
beginning credit plus period debit minus the period credit equals 0 for the Year to
Data balance type (begin_bal_dr begin_bal_cr + period_dr period_cr = 0 for
the YTD balance type, or the period debit minus the period credit equals zero
(period_dr period_cr = 0 for the Periodic balance type).
The following example shows how each include zero balance option affects account
balances.
Table 29
Amount
Opening Balance
Transaction Debit
Transaction Credit
Closing Balance
4000
40000
40000
5000
50000
25000
75000
6000
7000
35000
35000
When the Zero Balance is Include, Accounts 4000, 5000, 6000 and 7000 qualify for
this condition because all zero balanced accounts are included.
Note: The Include Zero Balance option is not applicable when pulling data from
Peoplesoft.
When the Zero Balance is Exclude No Activity is selected, only Account 6000 is
excluded because the Opening, Transaction and Closing balances are all zero and there
is no activity. Accounts 4000, 5000, 7000 are extracted.
When the Zero Balance is Exclude Net Zero is selected, Accounts 4000, 5000, 6000
and 7000 are excluded because their closing balance is zero.
l
For Planning and Essbase, select the Source Parameters tab, and specify any parameters.
See Defining Source Parameters for Planning and Essbase on page 181.
On the Workflow tab, under Data Load, select Data Load Rule.
Complete the source options or source filter options based on the source system:
For Fusion and E-Business Suite source systems, see Defining Source Filter Options
for E-Business Suite Source Systems on page 164.
For PeopleSoft Enterprise Financial Management source systems, see Defining Source
Filter Options for PeopleSoft Enterprise Financial Management Source Systems on
page 168.
For PeopleSoft human resource source systems, see Defining Human Resource Data
Load Rules on page 266.
For JD Edwards GL, seeDefining Source Filter Options for JD Edwards GL Source
Systems on page 170.
For SAP, seeDefining Source Filter Options for SAP Adapters on page 171.
For the Open Interface Adapter, see Defining Source Filter Options for the Open
Interface Adapter on page 179.
For file-based source systems, see Defining Data Load Rule Details for a File-Based
Source System on page 179
Click Save.
The amount typeOnly monetary, statistical, or both, monetary and statistical amounts
Zero balance accounts where the debits and credits for an account total zero and there is
not period activity.
164
chart of accounts to the Scenario dimension, so you choose a default member as part of the
data rule definition.
You can extract functional balances, which are stored in the base currency of the selected ledger
or business unit. For example, when transactions are entered in multiple currencies, the total of
all transaction balances is expressed in the functional currency.
You can also extract entered balances, which are balances associated with a currency attached
to a primary ledger other than functional/local currency.
Additionally, FDMEE can import the data in a currency specified by the user. In this case, the
balances must be translated to the specified currency in the source system. This can be achieved
by running the Currency Translation process in the source Enterprise Resource Planning (ERP)
system. (FDMEE does not perform any currency translations.)
To define the data load source filter for Fusion and E-Business Suite source systems:
1
On the Workflow tab, under Data Load, select Data Load Rule.
In Accounting Entity, specify the accounting entity from the list of values of the source system.
You can select the accounting entity in this field, or when entering location detail. Data rules
in locations without an accounting entity require you to select an Accounting Entity.
This functionality applies only to data rules in a location using a standard import format.
You cannot modify the accounting entity once the Data Rule has been executed.
In Accounting Entity Group, specify the accounting entity group name if the location is associated with
an accounting entity group.
When a data rule in a location includes an accounting entity, then the rule is constrained by
the accounting entity in the definition. In this case, the data rule in the location cannot use
an accounting entity group.
Adjustment periods ensure that FDMEE adjustment periods map correctly to the source
system adjustment periods.
When you explicitly map period 13 to December/Period 12, and select the Include
Adjustment Period option, then the following occurs:
Monetary
From Currency Type, select the currency type by which to extract balances:
165
Exclude No ActivityZero balances are excluded when the beginning balance debit,
beginning balance credit, period debit and period credit equal 0 (begin_bal_dr,
begin_bal_cr, period_dr, period_cr all have 0 for the YTD balance type, or the period
debit and the period credit have a period for the period balance type (period_dr,
period_cr equals 0 for the Periodic balance type).
Exclude Zero Net BalanceZero net balances are excluded when the beginning balance
debit minus the beginning balance credit plus the period debit minus the beginning
credit plus period debit minus the period credit equals 0 for the Year to Data balance
type (begin_bal_dr begin_bal_cr + period_dr period_cr = 0 for the YTD balance
type, or the period debit minus the period credit equals zero (period_dr period_cr =
0 for the Periodic balance type).
The following example shows how each include zero balance option affects account balances.
Table 30
Amount
Opening Balance
Transaction Debit
Transaction Credit
Closing Balance
4000
40000
40000
5000
50000
25000
75000
6000
7000
35000
35000
When the Zero Balance is Include, Accounts 4000, 5000, 6000, and 7000 qualify for this
condition because all zero balanced accounts are included.
When the Zero Balance is Exclude No Activity is selected, only Account 6000 is excluded
because the Opening, Transaction, and Closing balances are zero and there is no activity.
Accounts 4000, 5000, 7000 are extracted.
When the Zero Balance is Exclude Net Zero is selected, Accounts 4000, 5000, 6000, and
7000 are excluded because their closing balance are zero.
10 In Signage Method, select the method for flipping the sign of amounts when data is loaded.
Available methods:
l
166
Account Type
GL (GAAP)
EPM (Absolute)
Revenue
naturally negative
signage flipped
Liability
naturally negative
signage flipped
Account Type
GL (GAAP)
EPM (Absolute)
Equity
naturally negative
signage flipped
Expense
naturally positive
signage unchanged
Asset
naturally positive
signage unchanged
Reverse from sourceLoads the reverse of the sign as recorded in the source system.
11 Select the Amount for Balance Sheet Accounts and Amount for Income Statement Accounts:
l
12 From Currency Type, select the currency type by which to extract balances:
l
FunctionalBalances stored in the base currency of the selected ledger or business unit
(local currency)
EnteredBalances associated with a currency attached to primary ledger other than the
functional/local currency that you specify in the Currency Code field.
TranslatedFDMEE can import the data in a currency specified by the user. In this
case, the balances must be translated to the specified currency in the source system. This
task can be achieved by running the Currency Translation process in the Enterprise
Resource Planning (ERP) system. (FDMEE does not perform any currency
translations.) Additionally, you need to specify the translated currency code in the
Currency Code field.
13 From Currency Code (Entered and Translated currency types only), select the ISO 4217 currency code
to use with an entered or translated currency type.
StandardIn Oracle General Ledger, accounting transaction balances are stored as-is,
also known as standard balances.
AverageAverage balances only contain balance sheet data. If you selected Statistical
as the amount type, the Balance Method is ignored.
Actual
BudgetIf you select the Budget source balance type, click Add to select budget types
to include in the extraction.
EncumbranceIf you select the Encumbrance source balance type, click Add to select
encumbrance types to include in the extraction.
167
All
Selected
In Oracle E-Business Suite, the balancing segment ensures that at this level, balancing
debits equal credits. When you create a data load rule, you can extract the general ledger
balances relating to all the members of the balancing segment or for specific members
of it.
To select the balancing segment values, click
then click OK.
Note: For Account Reconciliation Manager applications, you must not choose multiple rate
options.
18 Click Save.
19 Define the target filter options.
After you define the target filter options, run the data rule. See Running Data Load Rules
on page 183.
Defining Source Filter Options for PeopleSoft Enterprise Financial Management Source
Systems
When defining data load rule details, you can specify various data extraction options as described
below.
168
To define the source filter options for PeopleSoft Enterprise Financial Management source
systems:
On the Workflow tab, under Data Load, select Data Load Rule.
Monetary
In Signage Method, select the method for flipping the sign of amounts when data is loaded.
Available methods:
l
Account Type
GL (GAAP)
EPM (Absolute)
Revenue
Naturally negative
Signage flipped
Liability
Naturally negative
Signage flipped
Equity
Naturally negative
Signage flipped
Expense
Naturally positive
Signage unchanged
Asset
Naturally positive
Signage unchanged
Reverse from sourceLoads the reverse of the sign as recorded in the source system.
Select the Amount for Balance Sheet Accounts and Amount for Income Statement Accounts:
l
From Currency Type, select the currency type by which to extract balances:
l
Functional Balances stored in the base currency of the selected ledger or business unit
(local currency)
EnteredBalances associated with a currency attached to primary ledger other than the
functional/local currency that you specify in the Currency Code field.
169
Note: The default when FDMEE pulls from PSFT is POSTED_TOTAL_AMT. If you select
From Currency Code, select the ISO 4217 currency code to use with an entered currency type.
. Then, in the Select Book Code dialog box, clear book codes,
You specify the budget values when the ledger that you selected has the data table
Ledger_Budg.
To deselect budget values, click
and then click OK.
13 Click Save.
14 Define target filter options.
After you define target filter options, run the data rule. See Running Data Load Rules on
page 183.
On the Workflow tab, under Data Load, select Data Load Rule.
Select PTD for Period to Date, or YTD for Year to Date balances.
Specify the company code in four characters or less using alphanumeric characters.
170
Specify the ledger in two characters or less using alphanumeric characters from the JD
Edwards source system. For example, ledger types include:
AAActual
BABudget
Click Save.
171
PTDPeriod to Date
YTDYear to Date
In Company Code, specify the company code in four characters or less using alphanumeric characters.
00Transaction currency
30Group currency
In Language, specify the language code in two characters or less, using uppercase characters.
In Ledger, specify the ledger code in two characters or less using alphanumeric characters.
0Actual
1Plan
172
PTDPeriod to Date
YTDYear to Date
In Company Code, specify the company code in four characters or less using alphanumeric characters.
00Transaction currency
30Group currency
40Hard currency
In Language, specify the language code in two characters or less, using uppercase characters.
In Ledger, specify the ledger code in two characters or less using alphanumeric characters.
0Actual
1Plan
173
In Activity Type Description, select whether to include or exclude the activity type description:
l
In Controlling Area, specify the controlling area in four characters or less using alphanumeric characters.
In Include Cost Element Description, select whether to include the cost element description:
l
00Transaction currency
(blank)leave blankwhen the Quantity filter is Yes or the Activity Type filter is Yes.
174
In Language Code, specify the language code in two characters or less, using uppercase characters.
In Ledger Code, specify the ledger code in two characters or less using alphanumeric characters.
04Actual
01Plan
175
00Transaction currency
In Language, select the language code in two characters or less, using uppercase characters.
In Ledger, select the ledger code in two characters or less using alphanumeric characters.
0109Account Group
176
0Actual
1Plan
In Company Code, specify the company code in four characters or less using alphanumeric characters.
00Transaction currency
In Customer, select the customer code in ten characters when the balance is required for a specific
customer.
In Company Code, specify the company code in four characters or less using alphanumeric characters.
00Transaction currency
178
In Vendor, specify the vendor code in ten characters when the balance is required for a specific vendor.
In Batch Name, enter the name of the batch used to identify the data in the interface table.
In Record Type, specify whether to delete data after importing the data by selecting Y (for yes) or N.
Click Save.
The categories listed are those that you created in the FDMEE setup, such as Actual. See
Defining Category Mappings on page 120.
179
Optional: From the Target Plan Type drop, select the plan type of the target system.
Optional: In Import Format, if the file type is a multiple period text file (with contiguous periods, or
noncontiguous periods), select the import format to use with the file, so you can override the import
format. For example, specify an import format for single and multiple period data rules, which enables
you to load single or multiple period files from the same location. In this case, the import format selected
must have the same target as the location selected in the POV. If the import format is unspecified, then
the import format from the location is used.
The starting and ending period selected for the rule determine the specific periods in the file
when loading a multiple period text file.
In the file, when amounts are unavailable for contiguous periods, then you can explicitly
map the respective amount columns to required periods in the data rule in Data Load
Mapping. When you execute the rule, the data is loaded to the periods as specified in the
explicit mapping.
10 In the File Name field, enter the static name of the file.
When only the file name is provided, then data must be entered for a single period on the
Rules Execution window.
To load multiple periods, create a file for each period and append a period name or period
key to the file name. When the rule is executed for a range of periods, the process constructs
the file name for each period and uploads it to the appropriate POV.
Note: If used in a batch script, period names cannot include spaces.
To navigate to a file located in a FDMEE directory, click Select, and then choose a file on
the Select screen. You can also select Upload on the Select screen, and navigate to a file on
the Select a file to upload screen.
If you do not specify a file name, then FDMEE prompts you for the file name when you
execute the rule.
11 To load data into multiple periods, in the File Name Suffix Type drop-down, select Period
Description or Period Key.
180
A suffix is appended to the file name, and FDMEE adds the file extension after adding the
suffix. If you leave the file name blank, then FDMEE looks for a file with Suffix. When the
file name suffix type is provided, then the file name is optional in this case, and it is not
required on the Rule Execution window.
If the file name suffix type is a period key, the suffix indicator and period date format are
required (as the suffix set) in the file name, and must be validated as a valid date format.
For example, specify:
a. 1_Jan-2013.txt
b. 1_Feb-2013.txt
c. 1_Mar-2013.txt
In this case, when you run the rule, enter 1_.txt in the file name field and select Period
Name for the suffix indicator. Then run the rule for the January to March periods.
12 In Period Key Date Format, specify the data format of the period key that is appended to the file name
in JAVA date format (SimpleDateFormat).
13 Click Save.
On the Workflow tab, under Data Load, select Data Load Rule.
In Data Load Rule, select a data load rule for an Planning and Essbase source, and then click Add.
In Data Precision, specify the number of decimal places displayed in numbers to be exported.
Data precision refers to numeric data with the emphasis on precision (accuracy). Depending
on the size of a data value and number of decimal positions, some numeric fields may be
written in exponential format; for example, 678123e+008. You might consider using data
precision when data ranges from very large to very small values. The output files typically
are smaller and data values are more accurate.
The default value for this option is 16.
In Data Number of Decimal, specify the maximum number of decimal positions to be exported.
181
Specify a value between 0 and 16. If no value is provided, the number of decimal positions
of the data to be exported is used, up to 16 positions, or a value determined by Data Precision
option if that value is specified.
This parameter is used with an emphasis on legibility; output data is in straight text format.
Regardless of the number of decimal positions in the data, the specified number is output.
Note that it is possible the data can lose accuracy, particularly if the data ranges are from
very large values to very small values, above and below the decimal point.
By default, 16 positions for numeric data are supported, including decimal positions. If both
the Data Precision option and the Data Number of Decimal option are specified, the Data
Precision option is ignored.
Click Save.
Edit data load rulesSee Editing Data Load Rules on page 182.
Run data load rulesSee Running Data Load Rules on page 183.
Delete data load rulesSee Deleting Data Load Rules on page 188.
View data load rules before executing themSee Using the Data Load Workbench on
page 190.
Check the data rule process detailsSee Viewing Process Details on page 202.
On the Workflow tab, under Data Load, select Data Load Rule.
Click Save.
182
Running a batch script. See Working with Batch Scripts on page 289.
When a data load rule is run, it loads the data, and a drill region (optional) is created to enable
users to drill through to the source data.
When you run a data load rule, you have several options.
l
Import from SourceFDMEE imports the data from the source system, performs the
necessary transformations, and exports the data to the FDMEE staging table.
Select this option only when:
m
You are running a data load rule for the first time.
Your data in the source system changed. For example, if you reviewed the data in the
staging table after the export, and it was necessary to modify data in the source system.
In many cases, source system data may not change after you import the data from the source
the first time. In this case, it is not necessary to keep importing the data if it has not changed.
When the source system data has changed, you need to recalculate the data.
l
Note: Select both options only when the data has changed in the source system and to export
On the Workflow tab, under Data Load, select Data Load Rule.
From Execute Rule, to extract data and/or metadata from the source system and push it into target
applications, select Import from Source.
183
Tip: You can use a utility outside of FDMEE to view the data in the staging table. After you
review the exported data, you can return to FDMEE, make modifications, and rerun
the rule. If you are sure that the information in the staging table is what you want to
export to the target application, rerun and select Export to Target. See Staging Table
Used for Import from Source on page 391.
Select Recalculate to remap all imported source data using the current mapping table and to recreate
all logic accounts.
Select Execute Check to generate the date, and then run the Check Report.
For a file-based source system, in File Name Suffix Type, select to affix the period name or period key
after the file name.
l
184
Period KeyA unique identifier for the period. The period key is a date value. When
the file name suffix type is the period key, specify the date format in the Period Key Data
Format field.
Period NameA secondary identifier for the period. The value is unique, and may
contain alpha-numeric characters.
In Period Key Data Format, specify the date format when a period key suffix is selected.
For a file-based source system, in Import Mode, select the method for loading data.
AppendExisting rows for the POV remain the same, but new rows are appended to
the POV (that is, appends the new rows in TDATASEG).
For example, a first time load has 100 rows and second load has 50 rows. In this case,
FDMEE appends the 50 rows to TDATASEG. After this load, the row total for the POV
is 150.
ReplaceReplaces the rows in the POV with the rows in the load file (that is, replaces
the rows in TDATASEG).
For example, a first time load has 100 rows, and a second load has 70 rows. In this case,
FDMEE first removes the 100 rows, and loads the 70 rows to TDATASSEG. After this
load, the row total for the POV is 70.
Store DataInserts the data from the source or file into the target application. This
replaces any value that currently exists.
Add DataAdds the value from the source or file to the value that exists in the target
application. For example, if you have 100 in the source, and 200 in the target, then the
result is 300.
Subtract DataSubtracts the value in the source or file from the value that exists in the
target application. For example, if you have 300 in the target, and 100 in the source, then
the result is 200.
Override All DataClears all data in the target, and then loads from the source or file.
For example, if you have a year of data in your Planning application, but are only loading
a single month, this option clears the entire year before performing the load.
Note: The Override All Data option is defined in Setting System-Level Profiles on
11 Click Run.
After you click Run, the rule is locked from any updates to ensure that the drill through path
is intact. See Checking the Data Load Rule Status on page 188.
To submit the data load rule for a Planning General Ledger or Enterprise Resource Planning
(ERP):
On the Workflow tab, under Data Load, select Data Load Rule.
185
Click Execute.
When the data rule is run for Financial Management target applications, the Exchange Rates
from the source are populated only up to the FDMEE interface table
AIF_HS_EXCHANGE_RATES. The Core Exchange Rates table in Financial Management
is not updated.
From Execute Rule, to extract data, metadata or both from the source system and push it into target
applications, select Import from Source, and then select the Start Period and End Period.
Tip: You can use a utility outside of FDMEE to view the data in the staging table. After you
review the exported data, return to FDMEE, make modifications, and run the rule
again. If you are sure that the information in the staging table is correct, run the rule
again and select Export to Target.
Select Recalculate to remap all imported source data using the current mapping table and to recreate
all logic accounts.
Select Execute Check to generate the date, and then run the Check Report.
In Start Period, select the beginning period of the POV from which to import the data from the source
system.
In End Period, select the ending period of the POV to which to import the data from the source system.
10 In Import Mode, select the mode to extract data all at once for an entire period or incrementally during
the period.
Note: The snapshot import mode is the only way data can be extracted from a SAP and JD
SnapshotExtracts everything for the selected source set for an entire period
m
When source data for the selected period has never been run, FDMEE extracts the
data from the source.
When the source data for the selected period has been run, FDMEE extracts the data
from the FDMEE staging tables and not from the source.
When you have locations that extract from the same Enterprise Resource Planning
(ERP) source, FDMEE extracts the data once. When you load data to Financial
Management from the E-Business Suite for a selected period, and then run the
integration to ARM for the same source and period, FDMEE does not pull again
from E-Business Suite, but uses the data in the interface tables. This results in a
significant performance gain for any subsequent data loads. The first extraction
takes take the longest, but any other subsequent extractions are faster.
186
IncrementalExtracts the records that were added after the previous data extract
Full RefreshPerforms a clean extraction from the source system, thereby clearing any
existing data rows in the appropriate FDMEE staging tables for a given source Ledger
(or Business Unit) and source period.
Note: The import mode options (Snapshot, Incremental, and Full Refresh) apply only
Store DataInserts the data from the source or file into the target application, replacing
any current value.
Add DataAdds the value from the source or file to the value that exists in the target
application. For example, if you have 100 in the source, and 200 in the target, then the
result is 300.
Subtract DataSubtracts the value in the source or file from the value that exists in the
target application. For example, if you have 300 in the target, and 100 in the source, then
the result is 200.
Override All DataClears all data in the target, and then loads from the source or file.
For example, if you have a year of data in your Planning application, but are loading
only a single month, this option clears the entire year before performing the load.
MergeOverwrites the data in the application with the data in the load file. For each
unique point of view that exists in the data file and in the application, the value in the
data file overwrites the data in the application.
Note: If the data load file includes multiple values in the file for the same point of view,
application.
l
Accumulateaccumulate the data in the application with the data in the load file. For
each unique point of view in the data file, the value from the load file is added to the
value in the application.
ReplaceReplaces the data in the application with the data in the load file. For each
unique combination of Scenario, Year, Period, Entity, and Value in the data file, the
Replace option clears all account values from the application, then loads the value from
the data file.
187
Replace by SecurityPerforms a data load in Replace mode in which only the members
to which you have access are loaded. This option enables you to perform a data load in
Replace mode even if you do not have access to all accounts. When you perform the
Clear operation for a period in a sub-cube, only the cells to which you have access are
cleared. Data, cell text, and line item detail are cleared, but cell attachments are not
cleared.
On the Workflow tab, under Data Load, select Data Load Rule.
Click Schedule.
On the Workflow tab, under Data Load, select Data Load Rule.
When you cancel a job from the FDMEE user interface, all instances of a schedule for the
object selected are cancelled. To cancel a specific instance of a schedule, cancel the job from
the ODI studio or ODI console.
188
Note: After you delete data load rules, you can delete a source system. After you execute a
deletion, users cannot drill through to an Enterprise Resource Planning (ERP) source.
On the Workflow tab, under Data Load, select Data Load Rule.
Click Delete.
On the Workflow tab, under Data Load, select Data Load Rule.
Click Save.
On the Workflow tab, under Data Load, select Data Load Rule.
In Integration Option 1-4, specify the free form text or value, and click OK.
The information that you specify is accessible from the Integration Option fields of the
Location table.
189
Interactive Load Process with options for Import, Validate, Export, and Check.
Note: When you log in with the Run Integration role, these links are visible in the Tasks pane:
Data Load Workbench, Data Load, Member Mapping, HR Data Load, Metadata, and
Process Detail.
The Data Load Workbench consists of four sections:
l
Workflow Grid
Status
Data Grid
Workflow Grid
The Workflow grid enables users to process data from start to finish in FDMEE. The Workflow
grid items are displayed as headers in the FDMEE Workspace display and correspond to a
Workflow step. The steps consists of Import (loading data from source), Validate (ensures that
all members are mapped to a valid account), Export (loads the mapped members to the target
application), and Check (verifies accuracy of data by processing data with user-defined check
rules).
When you select a Workflow step, the following occurs:
l
190
CheckDisplays the Check report for the current POV (if there is no check report data for
the current POV, a blank page is displayed.)
FDMEE uses fish icons to indicate the status of each step. When a Workflow step is completed
successfully, the fish is orange. If the step is unsuccessful, the fish is gray .
Note: You can customize the icons that show a successful process and a failed process by
replacing the ProcessSucceeded and ProcessFailed icons in the %EPM_ORACLE_HOME%
\epmstatic\aif\images\general folder.
Processing Data
FDMEE process flow consists of four main operations:
1. ImportImports the source data against a General Ledger or uploads a flat file.
2. ValidateEnsures that all data in the imported GL has a corresponding mapping.
Unmapped items must be assigned to a target account before proceeding to the Export step.
In addition you have the option to view mapping errors and fix them instantly when mapping
errors have occurred.
3. ExportLoads the mapped GL data to the target application.
4. CheckValidates the data loaded to the target application using the validation rules (if
applicable).
191
Data in the source system has changed. For example, if you reviewed the data in the staging
table after the export, and it was necessary to modify data in the source system.
In many cases, source system data may not change after you import the data from the source
the first time. You don't need to keep importing unchanged data.
On the Workflow tab, under Data Load, select Data Load Workbench.
Optional: When you import a source file, FDMEE uses the current POV to determine location, category,
and period.
To import another source file, you must change the POV. For information on changing the
POV, see Using the POV Bar on page 37.
to navigate to the Process Detail page to monitor the ODI job progress.
Click OK.
On the Workflow tab, under Data Load, select Data Load Workbench.
Select Validate.
192
shows the number of dimension members that are not mapped (that are, therefore, undefined).
You must correct any unmapped dimension members before running the validation again.
In the top region of the Validation screen, highlight a row that requires correction.
In the top region of the Validation Error screen, the unmapped item is inserted into the
Source value, and the bottom region shows all row with that source value. For example if
the top region displays a value of Entity dimension with Source Value 01, then bottom region
should show all rows where ENTITY = 01.
See Defining the Import Format Mappings on page 98.
Source data that passes the validation process can be loaded to the target system.
Fixing the Mapping Errors
In the Data Load Workbench, you can view mapping errors and fix them instantly when mapping
errors have occurred.
193
In the top region of the Validation screen, click Generate Intersection Check Report.
194
When exporting data for Planning and Essbase, you can store, add, and subtract data. For
Planning and Essbase, you can override all data.
For Financial Management, you can merge, accumulate, replace, and replace by security data.
When you use Lifecycle Management to export mapping rules, any related mapping scripts are
included.
The export of mapping rules to a CSV or Excel format does not include any scripting.
On the Workflow tab, under Data Load, select Data Load Workbench.
Optional: When you import a source file, FDMEE uses the current POV to determine location, category,
and period and conducts the following process: To import another source file, you must change the POV.
See Using the POV Bar on page 37.
In Execution Mode drop-down, select the mode for exporting the source data to the target application.
l
to navigate to the Process Detail page to monitor the ODI job progress.
Click OK.
195
Load Data/Load POVUse to import, view and verify and export data from source systems.
You perform tasks on the data grid by selecting options on the Table Action including:
l
Viewing Data
The following View drop-down options provides multiple ways to view data.
196
Table 33
View Option
Description
Customizes views. Options include:
l
Source (All)Shows both mapped and unmapped source dimensions (ENTITY, ACCOUNT, UD1, UD2, AMOUNT).
Source and TargetShows both source and target dimensions (ENTITY, ENTITYX, ACCOUNT, ACCOUNTX, UD1, UD1X,
AMOUNT, AMOUNTX).
Show All
Entity
Account
Version
Product
Department
STAT
Amount
Source Amount
Note: For E-Business Suite and PeopleSoft, the Account Descriptions is also available for viewing.
l
Freeze/UnfreezeLocks a column in place and keeps it visible when you scroll the data grid. The column heading
must be selected to use the freeze option. To unfreeze a column, select the column and from the shortcut menu, select
Unfreeze.
Detach/AttachDetaches columns from the data grid. Detached columns display in their own window. To return to
the default view, select View, and then click Attach or click Close.
SortUse to change the sort order of columns in ascending or descending order. A multiple level sort (up to three levels
and in ascending and descending order) is available by selecting Sort, and then Advanced. From the Advanced Sort
screen, select the primary sort by column, and then the secondary then by column, and then the third then by
column.
The search fields that are displayed in the advanced search options differ depending on what artifact you are selecting.
Reorder ColumnsUse to change the order of the columns. When you select this option, the Reorder Columns screen
is displayed. You can select a column, and then use the scroll buttons on the right to change the column order.
Query by ExampleUse to toggle the filter row. You can use the filter row to enter text to filter the rows that are displayed
for a specific column. You can enter text to filter on, if available, for a specific column, and then press [Enter]. To clear
a filter, remove the text to filter by in the text box, then press [Enter]. All text you enter is case sensitive.
Formatting Data
You can resize the width of a column by the number pixel characters or a percentage. You can
also wrap text for each cell automatically when text exceeds the column width.
197
From the table action bar, select Format, and then Resize.
In the second Width field, select pixel or percentage as the measure to resize by.
Select OK.
From the table action bar, select Format, and then Wrap.
Showing Data
You can select the type of data to display in the data grid including:
l
Valid DataData that was mapped properly and is exported to the target application.
Invalid DataOne or more dimensions that was not mapped correctly and as a result, the
data is not exported to target.
Ignored DataUser defined explicit IGNORE maps to ignore while exporting to target.
IGNORE maps are defined in the member mapping by assigning a special target member
of IGNORE.
All DataShows all valid, invalid and ignored data.
Select Show.
Valid Data
Invalid Data
Ignored Data
All Data
drill region is created based on the metadata rule. Otherwise, it is created based on the
target members in the data load mappings. For Year, Period, and Scenario, FDMEE uses
audit information to create the drill region.
198
Click the source amount link and select Drill through to source.
199
Querying by Example
Use the Query by Example feature to filter rows that are displayed for a specific column. You
can enter text to filter on, if available, for a specific column, and then press [Enter]. To clear a
filter, remove the text to filter by in the text box, then press [Enter]. All text you enter is case
sensitive.
To query by example:
1
The filter row must appear above the columns to use this feature.
Enter the text by which to filter the values in the column and press [Enter].
Note: When entering text to filter, the text or partial text you enter is case-sensitive. The
case must match exactly. For example, to find all target applications prefixed with
HR, you cannot enter Hr or hr.
Freezing Data
Use the Freeze feature to lock a column in place and keeps it visible when you scroll the data
grid.
To freeze a column:
1
To unfreeze a column:
1
Detaching Data
Use the Detach feature to detach column from the data grid, When you detach the grid, columns
display in their own window. To return to the default view, select View, and then click Attach or
click Close.
To detach columns:
1
200
To reattach columns:
1
From the table action bar, select View, and then Attach.
Wrapping Text
You can wrap text for each cell automatically when text exceeds the column width.
Click
load using an append mode is run and new cell text is added to an intersection that already
has cell text, the old cell text is replaced by the new cell text and not appended.
On the Workflow tab, under Data Load, select Data Load Workbench.
On the Select screen, browse and select an attachment, and then click OK.
201
Click Update.
10 Click Close.
11 Optional: To remove an attachment, click Remove (to the right of an Attachment field).
The Process Details page is displayed, showing processes for all source systems. The following
columns are displayed for each process:
l
202
ODI Session NumberThe session number in Oracle Data Integrator. You can use this
to look up a session in Oracle Data Integrator.
Note: The ODI Session number is present in Process Details only when the data is
LinkShows the log information for the process step. In the case of File Import, it shows
skipped rows, and in the case of export to Planning, it shows rejected rows and so on.
Reset StatusResets the status to failed if a process continues to stay in a running status
for a long period of time.
StatusFor each process step, the status is displayed. You can troubleshoot a problem
by viewing at which point the process failed.
LogIf a log is available, you can click Show to display the log contents.
Optional: To filter the rows that are displayed, ensure that the filter row appears above the column
headers. (Use the
203
Process ID
Location
Rule Name
Source System
Accounting Entity
Target Application
Note: When entering text to filter, the text or partial text that you enter is case sensitive. For
example, to find all target applications prefixed with HR, you cannot enter Hr or
hr. For additional information on filtering, see FDMEE User Interface Elements
on page 36.
On the Workflow tab, under Data Load, select Data Load Workbench.
From the Open screen, open or save the template and click OK.
204
Valid Tags
Account (Required)
A, Account, SrcAcctKey
Center (Required)
C, Center, SrcCenterKey
Description (Optional)
D, Description, SrcAcctDesc
I, IC, ICCoParty
Amount (Required)
V, Amount, SrcAmount
In the template that is provided with FDMEE, some of the rows are hidden. To update the
columns and the column tags, you need to unhide these rows. To do this, select the row above
and below the hidden rows, and then update the cell height. A setting of 12.75 is the standard
height for cells, and this should show all of the hidden rows for the selected range in the sheet.
You may want to re-hide the rows after you have made the necessary changes.
205
script.
On the Workflow tab, under Data Load, select Data Load Mapping.
From Select a file to import, select the Excel file to import, and then click OK.
From Select mode and validation, in Import mode, select the import mode.
MergeOverwrites the data in the application with the data in the Excel data load file.
Replace-Clears values from dimensions in the Excel data load file and replaces them
with values in the existing file.
Click OK.
206
The mapping inherits the default data load rule, and the description of System Generated
Mappings.
Transformations of gross balance accounts into roll-forward accounts (Beg, Add, Del, End)
Journal Status
207
For information on setting up any of the above options, see Defining Application Options for
Financial Management on page 81.
Data Values
Data value is an extra dimension that is only used when integrating with a Financial Management
multi-dimension target system. The name of the dimension is Value. The members in this
dimension are: [Contribution Adjs], and [Parent Adjs]. When data is loaded to Financial
Management, specify a member of the value dimension to indicate where the data is loaded. In
the Location definition in FDMEE, specify an entry for the value dimension in the Data Value
field. The Data Value is set on the Location screen by selecting the Search link.
When FDMEE creates the load file, this dimension value is entered for every data line loaded by
this location. You must enter a value in this field to integrate with Financial Management, or
else the validation fails. The default value is Data Value <Entity Currency>.
If you load journals to Financial Management, you can specify the value dimension member for
data loads and for journal loads. The first ; is the value member used for data loads, and the
second field by ; is the value member for journal loads.
When using the template, the system picks up the value member by looking for the second field
delimited by ; in the value member field in the location
When Search is selected, FDMEE connects to the Financial Management to get a list of valid
data values. FDMEE takes the values from Financial Management and adds rows created by
FDMEE that are a concatenation of the original value and Adjustment Data Values. FDMEE
uses these newly created rows to manage journal loading to Financial Management.
The rows that FDMEE creates in the Data Value selection screen are:
l
208
On the Workflow tab, under Data Load, select Data Load Workbench.
On the Open screen, open or save the template, and then click OK.
Metadata Structure
The metadata header (Row 1-5) instructs FDMEE on how to find the relevant segments of data
that it handles in this template. The following Row 1-5 topics explain how each piece of metadata
is used by FDMEE.
Row 1 (Journal ID and Location Tag)
The tag in row 1 is used to set the Journal ID and the FDMEE location that the data should be
loaded into. The Journal ID must be placed in row 1 of the Account column. Place the Location
tag in row 1 of the Amount column.
Note: Limit the journal ID to ten characters.
209
Valid Tags
Append Journal
A, Append
R Replace
AZ
RZ
Valid Tags
Account (Required)
A, Account, SrcAcctKey
Center (Required)
C, Center, SrcCenterKey
Description (Optional)
D, Description, SrcAcctDesc
I, IC, ICCoParty
Amount (Required)
V, Amount, SrcAmount
210
Processing Journals
The process for processing journals is:
1. Load the journal file in Excel format from the inbox directory.
2. Check whether the POV entered in the journal matches the current POV in FDMEE. The
ups range is also checked.
211
When a journal is checked in, FDMEE examines the template for all ranges with names
beginning with ups. It then examines and validates the metadata tags found in each ups
range. FDMEE does not check in metadata segments that include an invalid range.
3. Post the journal.
Loading Journals
To load a journal:
1
On the Workflow tab, under Data Load, select Data Load Workbench.
Optional: When you load a journal, FDMEE uses the current POV to determine location, category, and
period. To use another POV, select another POV. For information on changing the POV, see Using the
POV Bar on page 37.
When a journal has been successfully loaded, the Check button is enabled. Complete the
steps described in the Checking In Journals on page 213.
212
Optional: On the Load Journal screen, to browse for a journal file, click Select.
Make sure that a successfully loaded journal file is in the File field.
213
Click Check,
Online checking runs immediately, and offline checking runs in the background.
Click Check.
When a journal is checked in, FDMEE examines the journal file for all ranges with names
beginning with ups. It then examines and validates the metadata tags found in each ups
range. FDMEE does not check in metadata segments that include an invalid range.
Posting Journals
After a journal has been checked in successfully, you can post the journal. Posting a journal
appends or replaces the data displayed in the Import Format screen (as determined by the load
method specified in the journal).
Click Post.
Journal Security
If the POV Lock option is enabled, FDMEE administrators and end users are restricted to posting
journals to the FDMEE global POV.
214
Download to ExcelSelect an entity and download the data from the corresponding table
to an Excel spreadsheet.
Upload from ExcelImport source data representing one more ranges from an Excel
speadsheet.
Caution!
When loading data using this method, FDMEE does not validate the data. It is the
responsibility of the user to validate the date using this method.
Downloading to Excel
You can select a FDMEE entity and download the data from the corresponding table to an Excel
spreadsheet.
When downloading to Excel, note that the format of the Excel file must include:
l
table name
From Excel Interface, then Download to Excel, and then from Entity Type, select the FDMEE entity from
which to download data.
Batch Definition
Batch Groups
Batch Jobs
Category Mapping
Data Rule
215
Location
Period Mapping
User Setting
Optional: If you selected an Other entity type, enter the name of the table in the Table Name field.
In File, enter the name of the Excel file towhich to download the data.
You can also download a file by clicking Select, navigating to the file on the Select screen,
entering the new file name, and then clicking Download.
Click Download.
When the Excel spreadsheet is uploaded. the names of the tables and columns that have been
downloaded are shown, and the message: File imported successfully is displayed.
Optional: To open the downloaded Excel file, next to the File name field, click Select.
From the Select screen, choose the Excel spreadsheet and click Download.
Save or open the Excel spreadsheet.
216
From Excel Interface, and then Upload from Excel, in File, enter the name of the Excel file to upload.
You can also select a file by clicking Select, navigating to the file on the Select screen, and
clicking OK.
Click Upload.
Optional: To open the downloaded Excel file, next to the File name field, click Select.
Optional: You can also click Upload and browse to and select an Excel spreadsheet from an alternate
directory.
When the Excel spreadsheet is uploaded correctly, the Status pane shows the processed
ranges, and the message: File imported successfully is displayed.
217
povLocationLocation
povCategoryCategory
povPeriodNamePeriod
When the URL is defined in Oracle Hyperion Financial Close Management, note the following:
l
Data Synchronization
Write-Back
Data rules must be defined to load from an Enterprise Resource Planning (ERP) to an EPM
application, synchronize data between two EPM applications, or write back from an EPM to an
ERP system.
l
Data Synchronization
Data synchronization enables you to synchronize and map data between EPM source to target
applications irrespective of the dimensionality of the application simply by selecting the source
and target EPM application, and then mapping the data. Given the powerful mapping features
already available, the data can be easily transformed from one application to another application.
For example, synchronizing data enables you to take the data loaded from your General Ledger
to Planning, and then transformed into budget information, back to the General Ledger.
Tasks enabled by the data synchronization:
218
Copy consolidated data from Financial Management to Planning for future planning.
Write data from EPM System to Enterprise Resource Planning (ERP) applications.
Validate synchronizations.
Execute synchronizations.
Financial Management
Planning
Essbase (ASO)
Essbase (BSO)
Specify the source filter option to select a dimension, and then enter the filter criteria for
each dimension.
Browse and select members within a dimension.
219
To define the data load details for a target EPM or Enterprise Resource Planning (ERP)
system (file-based source system):
The categories listed are those that you created in the FDMEE setup, such as Actual. See
Defining Category Mappings on page 120.
Click Save.
fiscal year. When data ranges cross fiscal years, duplicate data results.
The source periods to be extracted are determined by the period mapping type.
Default Period Mapping
Default period mappings default to the list of source application periods using the application
or global period mappings based on the period key. The list of source periods is added as Year
and Period filters. For example, you can load data loading from Financial Management to
Essbase.
In the following example, Financial Management Application Period Mapping are loaded to
Essbase Application Period Mapping for the period Jan-14 to Mar-15:
Table 34
Period
Year
Month
1/1/2014
2014
Jan
220
Period
Year
Month
2/1/2014
2014
Feb
3/1/2014
2014
Mar
Table 35
Period
Year
Month
1/1/2014
FY14
January
2/1/2014
FY14
February
3/1/2014
FY14
March
target Essbase period when the target application has a larger time frame (for example,
Quarter) than the source period (for example, by Month).
3. Adds 2014 as a Year filter and Jan, Feb, Mar as Period filters.
Explicit Period Mapping
The Explicit method for loading data is used when the granularity of the source periods and
target application periods are not the same.
For example, you need to load data from a Financial Management application with monthly
periods and a Planning with quarterly periods.
In the following example, Financial Management Application Period Mapping are loaded to
Essbase Application Period Mapping for the period Jan-14 to Mar-15:
Table 36
Period
Year
Month
1/1/2014
2014
Jan
2/ 1/2014
2014
Feb
3/1/2014
2014
Mar
4/1/2014
2014
April
5/1/2014
2014
May
221
Period
Year
Month
6/1/2014
2014
June
Table 37
Period
Year
Month
1/1/2014
FY14
Q1
4/1/2014
FY14
Q2
Result of loading Financial Management Application Period Mapping to Planning Application Period Mapping
Period
Year
Month
Fiscal Year
Quarter
1/1/2014
2014
Jan
FY14
Q1
2/1/2014
2014
Feb
FY14
Q1
3/1/2014
2014
Mar
FY14
Q1
4/1/2014
2014
April
FY14
Q2
5/1/2014
2014
May
FY14
Q2
6/1/2014
2014
June
FY14
Q2
222
Enter a member name or filter condition in the Filter Condition text box.
For example, enter a member name or filter condition using Essbase syntax. Depending
on the dimension, you can select one or more members as a filter condition used for
extracting the budget data. For example, for the Entity dimension, you may select the
following members: E1, E5, E6. For information on Essbase syntax, see the Oracle Essbase
Database Administrator's Guide.
Click
to display the Member Select screen and select a member using the member
selector. Then, click OK.
The Member Selector dialog box is displayed. The member selector enables you to view and
select members within a dimension. Expand and collapse members within a dimension using
the [+] and [-].
The Selector dialog box has two panesall members in the dimension on the left and
selections on the right. The left pane, showing all members available in the dimension,
displays the member name and a short description, if available. The right pane, showing
selections, displays the member name and the selection type.
You can use the V button above each pane to change the columns in the member selector.
You can also click Refresh Members to show the latest member list.
Note: Assign filters for dimensions. If you do not assign filters, numbers from the summary
In the member options, I indicates inclusive. For example, IChildren adds all
children for the member, including the selected member, and IDescendants adds all
the descendants including the selected member. If you select Children, the selected
member is not included and only its children are included.
The member is moved to the right and displays the option you selected in the Selection
Type column. For example, Descendants displays in the Selection Type column.
Tip: To clear all members from the list of selections, click
223
Click Save.
Click Save.
to make selections:
a. Budget Scenario
b. Ledger Group
c. Ledger
Click Save.
Data Import
The data import process imports the data file created during the extraction process. The import
process evaluates the import format based on the header record in the file and mapping of the
source to target dimension.
224
When the number and order of columns is determined, the column position is stored in the
import format tables. File import expressions and scripts remain available during import.
Exports data from the FDMEE staging table to a general ledger interface table.
You use the mapping to format data in journal import tables.
For Financial Management, FDMEE extracts data and ICP transactions. FDMEE does not
extract cell text or line-item detail.
After a successful execution of the data load rule used to write back data, log in to the general
ledger source system and run the budget import process in the general ledger.
Drill-Through to Source
FDMEE provides the framework to drill through from the EPM System applications back to the
general ledger from the Oracle Enterprise Performance Management System source. Drill
through works only for data loaded through FDMEE.
For example, you can drill through from where data was loaded from E-Business Suite to
Financial Management, and then from Financial Management to Essbase. When you viewing
Essbase data in Oracle Smart View for Office, you can drill from the Essbase data cell and go to
the FDMEE landing page.
Write-Back
Financial budgeting information often must be compared with and controlled with actuals and
stored in the general ledger system. In FDMEE, write-back functionality is available with the
Export step of the data load process. In this way both loading to the Planning application and
write-back to General Ledger are performed in as a single consistent process.
225
For E-Business Suite, multiple ledgers can be used for the data load to write back with the
following criteria:
l
Budget is associated with one ledger. One ledger can be posted from only one data load
rule.
For Peoplesoft, Actuals can be posted without specifying the Budget Scenario. In addition, the
write-backs can be made to multiple business units.
226
Data load to write back is supported only for Planning, Essbase aggregate storage, and
Essbase block storage 11.1.2.x applications only. Applications created in earlier releases are
not supported.
For BSO Essbase applications, FDMEE requires that the Period dimension be designated as
Dense. Other dimensions can be Dense, but Period must be designated as dense to write
back.
Data load rules to write back are not supported for EPMA deployed aggregate storage Essbase
cubes.
For E-Business Suite source systems, you can post to budgets with or without budget
journals.
Only monetary and statistical amounts can be written back to the general ledger.
You cannot create data load rules to write back to PeopleSoft Human Capital Management
source systems.
FDMEE loads data into the specific data interface table. You must then run the budget load
routines provided by Oracle Fusion, E-Business Suite, or PeopleSoft Enterprise Financial
Management.
Allocation from a source amount to multiple target amounts is not provided.
Data Load rules to write-back can be performed without first loading data from a GL source
to an EPM target.
The category assigned to upgraded and write back rules is randomly assigned and plays no
role in the function of the rule. To view an upgraded rule, select Show All Categories, which
may reveal "hidden" rules.
When specifying a period range, make sure the start and ending periods are within a single
fiscal year. When data ranges cross fiscal years, duplicate data results.
E-Business
Suite Actual
PeopleSoft
Budget
PeopleSoft
Commitment
Control
PeopleSoft
Actual
SAP
JD Edwards
Planning
Out of Box
Out of Box
Out of Box
Out of Box
Custom
Use custom
application.
Use custom
application.
Essbase
Out of Box
Out of Box
Out of Box
Not supported
Custom
Use custom
application.
Use custom
application.
Financial
Management
Out of Box
Out of Box
Out of Box
Not supported
Custom
Use custom
application.
Use custom
application.
Profitability and
Cost
Management
Out of Box
Out of Box
Out of Box
Not supported
Custom
Use custom
application.
Use custom
application.
ARM
Not
supported
Not
supported
Not supported
Not supported
Not supported
Not supported
Not supported
GL_INTERFACE
GL_INTERFACE_CONTROL
GL_BUDGET_INTERFACE
Standard PeopleSoftPS_HPYPB_ACCT_LN
227
PS_HYP_KK_BD_HDR
PS_HYP_KK_BD_LN
On the Workflow tab, under Data Load, select Data Load Rule.
Choose the type of mapping by selecting one of the following tabs: Explicit tab, Between tab, In MultiDimension, or Like tab.
l
ExplicitThe source value is matched exactly and replaced with the target value. For
example, the source value, ABC is replaced with the target value, 123. Explicit
write-back mappings are created the same for data load and data load to write back rules.
See Creating Mappings Using the Explicit Method on page 144.
BetweenThe range of source values is replaced with one target value. For example, a
range from 001 to 010 is replaced with 999. Between write-back mappings are created
the same for data load and data load to write back rules. See Creating Mappings Using
the Between Method on page 145.
InIn mappings enable a list of nonsequential source accounts to be mapped to one
target account. In this case, multiple accounts are mapped to one account within one
rule, eliminating the need to create multiple rules (as is required for an Explicit map).
Multi-DimensionDefine member mapping based on multiple source column values.
LikeThe string in the source value is matched and replaced with the target value. For
example, source value Department is replaced by Cost Center A. See Creating
Mappings Using the Like Method on page 147.
Write-back mappings provide a means to remove or strip characters that were added
during the data load process. "Like" write-back mappings are created like a reverse data
load.
Tip: You can click Refresh Values to refresh the list of segment or chartfield values that
appear in the drop-down list from the source system. This is especially helpful when
creating Explicit, Between, Like, and Multi-Dimension mappings for data load
rules to write back.
228
Defining Data Load Rules for Write-Back Scenarios (Data from EPM
Planning/Essbase to Oracle Enterprise Resource Planning (ERP) Sources)
You create a data load rules to write back to extract budget data from application to a general
ledger instance and ledger source.
You can create data load rules to write-back in these ways:
l
Choose the Essbase aggregate storage (ASO) or Essbase block storage application (BSO).
Choose the Essbase aggregate storage (ASO) or Essbase block storage application (BSO).
For Public Sector Planning and Budgeting applications where you have consolidated
personnel (HR) and non-personnel expenses in the aggregate storage cube, you pull
information from the aggregate storage application. For nonpersonnel-related expenses you
see only the total number (combination) in the aggregate storage application.
Note: Public Sector Planning and Budgeting require that you combine the regular planning
results from an Essbase block storage cube, with the personnel position budget
information in an Essbase aggregate storage cube to a new aggregate storage cube.
When performing the data load rule to write back for a Public Sector Planning and
Budgeting application, you select the aggregate storage cube that you created in Public
Sector Planning and Budgeting. You can also select a Planning application as the
source for the write-back.
The process at a high level:
1. FDMEE imports data from Planning and writes it to a FDMEE staging table.
2. FDMEE applies the necessary transformation in the staging table.
3. Data is exported from the FDMEE staging table to a file based application.
4. After a successful execution of the data load rule to write back, view the results of the balances
transfer from Planning to the file using the Data Load Workbench.
On the Workflow tab, under Data Load, select Data Load Rule.
Click Save.
229
On the Workflow tab, under Data Load, select Data Load Rule.
From the Data Load Summary, select the data load rule.
Enter a member name or filter condition in the Filter Condition text boxThe selection
syntax is based on the source type.
For example, if Essbase is the source type, enter the member name or filter condition
using Essbase syntax. Depending on the dimension, you can select one or more members
as a filter condition used for extracting the budget data. For example, for the Entity
dimension, you may select the following members: E1, E5, E6. For information on
Essbase syntax, see the Oracle Essbase Database Administrator's Guide.
Click
to select a member using the member selector, and then click Browse.
The Selector dialog box is displayed. The member selector enables you to view and select
members within a dimension. Expand and collapse members within a dimension using the
[+] and [-].
The Selector dialog box has two panesall members in the dimension on the left and
selections on the right. The left pane, showing all members available in the dimension,
displays the member name and a short description, if available. The right pane, showing
selections, displays the member name and the selection type.
You can use the Menu button above each pane to change the columns in the member
selector.
Note: Assign filters for dimensions. If you do not assign filters, numbers from the summary
230
In the member options, I indicates inclusive. For example, IChildren adds all
children for the member, including the selected member. If you select Children, the
selected member is not included, only its children are included.
The member is moved to the right and displays the option you selected in the Selection
Type column. For example, Descendants displays in the Selection Type column.
Tip: To clear all members from the list of selections, click
Click Save.
Balance Type
Budget Option
Required data load rule Peoplesoft target options are in the table below.
Table 41
PeopleSoft Target
Option
Peoplesoft Budget
Peoplesoft Actual
Click Save.
to make selections:
a. Budget Scenario
b. Ledger Group
c. Ledger
Click Save.
After you run the rule, perform required tasks in Fusion, E-Business Suite, and PeopleSoft
Enterprise Financial Management.
To define Financial Management to E-Business Suite data load rules to write back:
1
On the Workflow tab, under Data Load Rule, select Data Load Rule.
From the Data Load Summary, select the data load rule.
10 Click Save.
232
Make sure that the PS_HYP_KK_BD_HDR and PS_HYP_KK_BD_LN interface tables have write
privileges.
When writing back to PeopleSoft Commitment Control, in Data Load Rule, define a data load rule to
write back by selecting parameters for the following:
l
Ledger Group
Ledger
Accounting Date
As of Date
Transaction TypeSelect check to validate the rules or post to validate and post
the rules.
In Data Load Rule, define the source filters that identify the portions of budget data to load to
PeopleSoft.
Optional: Delete previous data load rules to write back by selecting Delete on the Execute Rules
Options screen.
Run the PeopleSoft Commitment Control data load rule to write back.
If you have selected a transaction type of post, the rules are validated, the budget is written
to Commitment Control interface tables and the posting process is initiated after writing
the data. Any errors are forwarded to Public Sector Planning and Budgeting.
Click Execute.
After the extraction process is successful, you must log in to Oracle General Ledger or
PeopleSoft General Ledger and import the budget data.
To load data from the source EPM application, select Import from Source.
Select this option to review the information in a staging table, before exporting directly to
the target general ledger system.
233
When you select Import from Source, FDMEE imports the data from the EPM target
application, performs the necessary transformations, and exports the data to the FDMEE
staging table.
To export data to the target general ledger system, select Export to Target.
Click Run.
Note: After the rule runs successfully, view the information in the staging table. See Staging
After the rule runs, perform the required tasks in your general ledger system.
Exporting to Target
Use the Export to Target feature to export data to a target application, which is the Enterprise
Resource Planning (ERP) application. Select this option after you have reviewed the data in the
data grid and need to export it to the target application.
Export options:
l
Current Dimension
All Dimensions
Export to Excel
When exporting data for Essbase, you can store, add, and subtract data.
When exporting data for Planning, the following options are available:
l
Store DataInserts the data from the source or file into the target application, replacing
any value that currently exists.
Add DataAdds the value from the source or file to the value in the target application. For
example, when you have 100 in the source, and 200 in the target, then the result is 300.
Subtract DataSubtracts the value in the source or file from the value in the target
application. For example, when you have 300 in the target, and 100 in the source, then the
result is 200.
Override All DataClears all data in the target, and then loads from the source or file. For
example, when you have a year of data in your Planning application but are only loading a
single month, this option clears the entire year before performing the load.
From the table action bar, in Data Rule, and choose the data load rule.
Click
Execution modes:
234
to navigate to the Process Detail page to monitor the ODI job progress.
Export options:
Current Dimension
All Dimensions
Export to Excel
For Current Dimension and All Dimensions export methods, in Select file location, navigate to the file
to export, and then click OK.
For the Export to Excel method, mappings are exported to a Microsoft Excel spreadsheet.
Click OK.
After you exported data to the target, the status of the export is shown in the Status field for
the data load rule in the Data Load Summary.
To complete the data load to write back process, you must perform required tasks in your
supported source system.
235
TemplateSelect HYP_STDBUD
The data is staged in the PS_HPYPB_ACCT_LN interface table. FDMEE stores the process
ID in the JRNL_LN_REF table. You can check the data that was created by filtering on the
process ID.
4. Run the process.
If the process runs without errors, the journals are created.
5. Review the journal, create balancing entries, and then post the journal.
236
Logic Accounts
4
In This Chapter
On the Setup tab, under Data Load Setup, select Logic Group.
In Target Applications, select the target application for this logic group.
237
Click Save.
On the Setup tab, under Data Load Setup, select Logic Group.
From the Logic Group summary grid, select the logic group.
The logic accounts currently contained in with the selected logic group are listed.
Item
Description
Criteria Type
Criteria Value
Operator
Value/Expression
Seq
Export
Item
Specify the name of the logic account using the item field. The logic account that is named in
the item field is displayed in the Workbench grid as the source account. This same account can
be used as a source in a mapping rule. Oracle recommends that you prefix the names of logic
accounts with an L or some other character to indicate that an account came from a source
file, or was generated from a logic rule. Logic accounts can only be loaded to a target application
when they are mapped to a target account.
238
Description
The description that you enter in the Description field is displayed in the Account Description
field in the Workbench.
Between
Like
In
Type Field
Between
1000,1999
Like (Criteria Type)Used when the source accounts in the Criteria Value field contain
wildcard characters. Use question marks (?) as placeholders and asterisks (*) to signify
indeterminate numbers of characters.
Type Field
Like
1??0
Like
10*
Type Field
In
1000
In
1000,1005,2001
239
Math Operator
Math Operators (+, -, x, /)If a math operator is selected, then the new logic records has an
amount that equals the original amount is calculated with the specified Value/Expression. For
example, when the operator x was selected and 2 is entered in the Value/Expression field, then
the new record has an amount two times the original amount.
Use a numeric operator to perform simple mathematical calculations:
l
NA (no operator)
+ (addition)
- (subtraction)
X (multiplication)
/ (division)
In this example, one logic account is created because one Entity had a row meeting the account
criteria.
240
Functions enable the use of simple logic with if/else using Jython syntax. Jython commands can
be used in a function and can be more complex than an expression.
Exp
Use Expression operators to execute custom logic expressions, which are defined in the Value/
Expression field. Logic expressions, which cannot use variables or If statements, are simpler
than logic functions. Except for |CURVAL|, expressions do not have built-in parameters. For
expressions, you do not need to assign a value to RESULT.
Expressions execute faster than logic functions. You can use the FDMEELookup function within
expressions, as it is used within logic functions. To write a custom expression, double-click the
Value/Exp field to open the expression editor.
|CURVAL| + |810| + |238|
The function above uses the FDMEE Lookup function to add two source accounts to the value
of the logic account. Notice that the CURVAL parameter can be used within expressions, as it can
within logic functions, except that, with expressions, CURVAL must be enclosed in pipes.
(|CURVAL| + |000,10,09/30/01,810|) * 100
The function above uses the FDMEE Lookup function to add a source account (810) and a source
account from a specified center, FDMEE category, and FDMEE period to the value of the logic
account, and then multiplies the resulting sum by 100.
Function
Use function operators to execute a custom logic function defined in the Value/Expression field.
To write a function, select Function from the Operator drop-down list in the Logic Item line,
and then click the edit icon to open the edit window. Logic functions are usually used for
conditional mapping and other complex operations that involve multiple source accounts. Logic
functions enable the use of Jython commands including variables, if/elif/else statements,
numeric functions, and other Jython constructs.
The logic function enable the use of predefined function parameters, and also requires that you
assign a value to the RESULT variable so that a value can be updated for the newly created logic
account. The following function parameters can be used in a logic function, and these do not
require using the | notation:
241
Table 42
Function Operator
Description
CURVAL
StrLocation
StrCenter
StrCatKey
Active category key, not the name. You need too lookup the category key in the database to use this
parameter.
StrPerKey
Active period
Lookup notation may be used in a logic function. This is the same notation provided in the logic
expression.
Skip
If Skip is assigned to the keyword RESULT, then the logic account is not created.
You can define function parameters in uppercase, lowercase, or mixed case letters. However,
the keyword RESULT must be in uppercase letters.
Note: You must use the Jython notation and indentation for the logic function.
The following function only assigns the result of the logic account calculation to the logic account
when 10 is the active FDMEE category key.
if StrCatKey == 10:
RESULT = CURVAL
else:
RESULT=Skip
This function assigns the result of the logic account calculation to the logic account only when
the Criteria Account Entity is 000.
if StrCenter == 000:
242
This function uses the FDMEE Lookup function to add a source account (810) to the value of
the logic account if the current FDMEE period is Dec 2013.
if StrPerKey == 12/31/2013:
RESULT = CURVAL + |810|
else:
RESULT=Skip
This function uses the FDMEE Lookup function to add another source account from a different
Entity, FDMEE category, and FDMEE period to the value of the logic account when the active
location is Texas.
If StrLocation == Texas:
RESULT = CURVAL + |000,10,09/30/13,810|
else:
RESULT=Skip
Value/Expression
To perform calculations and thereby, to derive values for a logic account, you select an operator,
from the Operator field, to work with the Value/Expression value.
Seq
This field specifies the order in which the logic accounts are processed. Order specification
enables one logic account to be used by another logic account, provided that the dependant
account is processed first.
Export
A Yes-No switch determines whether a logic account is considered an export account and
therefore is subjected to the conversion table validation process. If the switch is set to Yes, then
you must map the logic account.
center name. The source center assigned to account 12300 is the four characters that start at
position 1. In addition, when the value in the Criteria Value field is 12300;3;4, the result is a
summarized account that includes all source centers that have the same three characters in the
source center, starting at position 4. The source center assigned to account 12300 is the three
characters that start at position 4.
To create a logic account that summarizes all source centers by, in the Criteria Value field, place
a semicolon after the account name and enter a text value. This hard-coded text value becomes
the center for the summarized logic account. For example, when the value in the Criteria Value
field is 12300;Dept100, then the result is a summarized account that includes all source centers.
The source center assigned to account 12300 is Dept100.
Criteria Value
To enter criteria for each dimension, click the Criteria Value icon to open the criteria form. The
logic item is created only from the source line items that meet the specified criteria for each
dimension. Descriptions of each complex logic criteria field is as follows:
Dimension
This field enables the selection of any enabled source dimension. You can select each dimension
only once.
Criteria Type
This field works in conjunction with the Source Dimension and Criteria Value fields to
determine from which source values the logic items are derived. Criteria types available are In,
Between, and Like. The Criteria Type determines how the criteria value is interpreted.
Criteria Value
The criteria type uses this field to determine to determine what members to include in the logic
calculation for any given logic dimension.
244
Group By
When viewing the derived logic item in the Workbench, the Group By field enables the logic
item to override the displayed member in the appropriate dimensions field. You can override
to group the dimension based on the value entered in the Group By field. Use this field to hard
code the returned member, or append hard-coded values to the original members by entering
a hard-coded member and an asterisk (*) in the Group By field.
For example, by placing the word Cash in the row with account selected for dimension, the
Import form displays Cash in the Account field for the logic item. If you place L-* in the
Group By field, the import form displays L-1100 where 1100 is the original account that passed
the logic criteria.
If you enter no value in the Group By field, no grouping occurs for this dimension, and a separate
logic item is created for each unique dimension member.
Group Level
When viewing the logic item in the Workbench, the Group Level field works with the Group By
field to override the displayed member in the appropriate dimensions field. This field accepts
only numeric values.
When you enter a value of 3 in the Group Level field, the left three characters of the Group By
field are returned. If no value is entered in the Group By field, then when you specify 3 in the
Group Level field, first three characters of the original source dimension member are returned.
The logic items displayed on the Import form can be grouped to the desired level.
For example, when you enter L-* in the Group By field, the logic item displays in the Import
form as L-1100, where 1100 is the original account that passed. When viewing the logic item
in the Workbench, the Group Level field works with the Group By field to override the displayed
member in the appropriate dimensions field. This field accepts only numeric values.
+ displays L-11. If you enter the Group level1 for this row, then the Import form displays
L-1.
Include Calc
If it meets the logic item criteria, the Include Calc field enables the logic item to include previously
calculated FDMEE values in its calculations.
Note: Each logic item has a sequence attached, and the logic items are calculated in this sequence.
If the second, or later, logic item has this field enabled, then any previously calculated
logic items are included, provided they meet the logic criteria.
245
Dimension
Criteria Type
Criteria Value
Group By
Group Level
Account
Like
11*
Cash
Entity
Like
Tx
Texas
ICP
Between
00,99
ICP
UDI
In
00,01,02
UD1
The first row specifies that any accounts that begin with 11 are included in the calculated result
for Calc Item: CashTx.
The second row further qualifies the results by specifying that the source record must also have
the entity like TX.
The third line reduces the results to only those source records that have an ICP value between
00 and 09.
The last line reduces the results to only those source records that have a Custom 1 (UD1) of
either: 00, 01 or 02. Imported lines that do not meet the listed criteria are excluded from the
calculated results.
In the following table, only one new logic item is derived from multiple source records. Using
the preceding graphic example as the logic criteria, and the first grid that follows as the source
line items, you can see how FDMEE derives the value of a single logic item. Note the Group By
field. Each Group By field includes a hard-coded value. Therefore, for every line that passes the
specified criteria, the original imported member is replaced with the member listed in the Group
By field.
Entity
ICP
UD1
Amount
Include or Exclude
1150
Tx
07
01
50,401.07
Include
1176
Tx
04
02
10,996.00
Include
1201
Tx
01
00
500.00
Exclude
Entity
ICP
UD1
Amount
Cash
Texas
ICP
UD1
50,401.07
Cash
Texas
ICP
UD1
10,996.00
246
FDMEE groups and summarizes the rows that include identical member combinations and thus
creates the following result:
Final Result
Account
Entity
ICP
UD1
Amount
Cash
Texas
ICP
UD1
61,397.07
Dimension
Criteria Type
Criteria Value
Group By
Group Level
Account
Like
11*
Cash
Entity
Like
Tx
Texas
ICP
Between
000,100
UDI
In
00,01,02
UD1-*
The first row in the preceding table specifies accounts that begin with 11 are to be included in
the calculated result for Calc Item: CashTx.
The second row further qualifies the results by specifying that the source record must also have
the entity like TX.
The third line reduces the results to only those source records that have an ICP value between
000 and 100.
The last line reduces the results to only those source records that have a Custom 1 (UD1) of
either: 00, 01. or 02. Any imported line that does not meet all of the listed criteria is
excluded from the calculated results.
In the following tables, two logic items are derived from the source records because of the values
entered in the Group By and Group Level fields. Two of the Group By fields have hard-coded
values listed and two have an asterisk. Therefore, for every line that passes the specified criteria,
the original imported members for the Account and Entity dimensions are replaced with the
member listed in the Group By field. The other dimensions return all or part of the original
members based on the Group Level entered.
Entity
ICP
UD1
Amount
Include or Exclude
1150
Tx
070
01
50,401.07
Include
247
Account
Entity
ICP
UD1
Amount
Include or Exclude
1176
Tx
040
02
10,996.00
Include
1121
Tx
045
02
9,050.41
Include
1201
Tx
100
00
500.00
Exclude
Logic Members
Account
Entity
ICP
UD1
Amount
Cash
Texas
07
UD1-01
50,401.07
Cash
Texas
04
UD1-02
10,996.00
Cash
Texas
04
UD1-02
9,050.41
FDMEE groups and summarizes the rows that include identical member combinations and thus
creates the following result.
Final Result
Account
Entity
ICP
UD1
Amount
Cash
Texas
07
UD1-01
50,401.07
Cash
Texas
04
UD1-02
20,046.41
248
Check Rules
5
In This Chapter
On the Setup tab, under Data Load Setup, select Check Rule Group.
In Check Rule Group Details, enter a name for the group in the Name field.
249
Click Save.
On the Setup tab, under Data Load Setup, select Check Rule Group.
Optional: In Check Rules, select the POV Location, POV Period, or POV Category.
In the Check Rule Group summary grid, select the check rule group.
Click Save.
Display Value
The Display Value field, which controls how FDMEE formats the data rows of check reports, is
used to select target accounts or report format codes, or to create custom expressions.
Rules used to process Display Value field:
l
For fields that contain report format codes, no value lookup is attempted.
For fields that contain data other than report format codes, the result of the custom
expression (rule logic) is displayed in the Value column. The Value column is limited to 75
characters.
250
#ModeList
Sets the report to display the Display Value, Description, and Amount column values. The system defaults to #ModeRule
if nothing is specified.
#ModeRule
(Default) Sets the report to display the Rule Name, Rule Text, and Amount column values.
The report evaluates each expression of the Rule Logic column and tests the True or False condition of each rule. The
status of each rule (OK or Error) is displayed in the report.
#Title
Inserts the text of the associated Description field as a title line on the check report.
#Subtitle
Inserts the text of the associated Description field as a subtitle line on the check report.
Description
Displayed only for check reports in #ModeList mode, the Description column displays account
descriptions (which may be designated as titles or subtitles).
ExampleDescription
Out-of-Balance Account
Rule Name
Displayed only for check reports in #ModeRule mode, the Rule Name column, stores identifiers
for check rules. Rule Name values should be unique and easy to identify.
ExampleRule Name
Out-of-Balance Check
Rule Text
Displayed only for reports in #ModeRule mode, the Rule Text column defines the logic behind
rules. In check reports, the primary statement for a rule is the text of the Rule Text field associated
with the rule.
ExampleRule Text
This account must be between [+10 and 10].
Category
In the Category column, select an FDMEE category to restrict a check rule to one FDMEE
category. The rule is displayed in the check report only when the FDMEE category that is selected
251
in the Category field associated with the rule is the FDMEE category set in the POV. To display
the check rule in the check report regardless of the category set in the POV, you must select All.
Sequence
Sequence column values (numbers) determine the order in which format codes and rules are
processed. It is good practice to increment sequence numbers by 10to provide a range for the
insertion of format codes and rules.
Rule Logic
The Rule Logic column is used to create multidimensional lookups and check rule expressions.
Rule Logic columns are processed for reports only in #ModeRule or #ModeList mode. After a
rule logic is processed for a rule in the check report, FDMEE flags the rule as passing or failing.
In this example, the check rule expression returns true (OK) when the value of Cash (a target
account) plus $1000 is greater or equals the value of AccruedTax (another target account), and
false (Error) when it does not:
|,,,YTD,<Entity Currency>,,Cash,[ICP None],[None],[None],[None],
[None],,,,,,,,,,,,,,,,|+1000>=|,,,YTD,<Entity Currency>,,AccruedTax,
[ICP None],[None],[None],[None],[None],,,,,,,,,,,,,,,,|
252
On the Setup tab, under Data Load Setup, select Check Rule Group.
From Check Rules, in the Check Rule Group summary grid, select a check rule group.
Click
253
Optional: Click
From Rule Logic in the Intersection Type field, select the intersection type for the multidimensional
lookup.
254
Click OK.
Rule and DisplayAreas that, respectively, display the rule and the display rule that are
being created.
Intersection TypeEnables you to select the type of retrieval format for the target
dimensions.
255
FDMEE uses the intersection type when multidimensional lookups are selected for a rules
logic statement. The multidimensional lookup retrieves account values from the target
system, FDMEE source data, target data or FDMEE source converted data. See
Multidimensional Lookup on page 256.
Multidimensional Lookup
The multidimensional lookup retrieves account values from the target system, FDMEE source
data, or FDMEE converted data. You can use multidimensional lookups in Rule Logic columns
and in the Display columns of check rules forms.
Rule Data Sources
FDMEE can retrieve data from three sources:
l
Target-system data
The following examples illustrate ways that target-system values can be retrieved. In each
example, Balance is a target account. For dimensions that are not referenced, you must use
commas as placeholders.
Example 1
Look up the value of Balance for the target period and scenario (category) set in the POV and
for each entity of the FDMEE check entity group that is assigned to the location. The example
rule passes the check when the target account is less than $10.
|,,,,,Balance,,,,,,,,,,,,,,,,,,,,,,| > -10.00 and |,,,,,Balance,,,,,,,,,,,,,,,,,,,,,,| <
10.00
Example 2
Look up the value of Balance for the specified dimensions.
|Actual,March,2002,YTD,Ohio,Balance,Michigan,Engines,Ford,Trucks,
[None],,,,,,,,,,,,,,,,,USD| > 0
Example 3
Look up the value of Balance for the specified dimensions and the previous period.
256
|Actual,-1,2002,YTD,Ohio,Balance,Michigan,Engines,Ford,Trucks,
[None],,,,,,,,,,,,,,,,,USD| > 0
Example 4
Look up the value of Balance for the target scenario (category) set in the FDMEE POV, the
previous target period, and each entity of the FDMEE check entity group that is assigned to the
location.
All missing custom dimensions default to [None]. The ICP dimension defaults to [ICP-None].
The Year dimension defaults to the year set in the POV. The Currency dimension defaults to 0.
The View dimension defaults to YTD.
|,-1,,,,Balance,,,,,,,,,,,,,,,,,,,,,,| > 0
Math Operators
Math Operators (+, -, x, /)If you select a math operator, then the check rule has an amount
that equals the original amount calculated with the specified expression. For example, when you
select the operator x and enter 2 in the rule field, then the new record is an amount two times
the original amount. The math operators available in the expressions:
l
+ (addition)
- (subtraction)
* (multiplication)
/ (division)
math.abs ()
257
If/Then/Else
Check rules accept If/Then/Else statements after you perform a multidimensional lookups.
This statement provides a primary path of execution when the if statement evaluates to true,
and a secondary path of execution when the if statement evaluates to false.
Using the If/Then/Else statement, you can use custom-field values within reports as warning
messages and flags.
In the following example, when the Result is between 100 to 1500, the Check Report with
Warning prints Amount between 100 and 1500. The example references three data accounts:
1. 24000050: 1000
2. 24000055: 500
3. 24000060: 10
This calculation for this example is 1000 + 500/10, with the result of 1050.
The script is written using Jython code:
def runVal():
dbVal=abs((|,,,,,BERLIN,24000050,[ICP None],[None],[None],[None],
[None],,,,,,,,,,,,,,,,|)+(|,,,,,BERLIN,24000055,[ICP None],[None],[None],[None],
[None],,,,,,,,,,,,,,,,|)/(|,,,,,BERLIN,24000060,[ICP None],[None],[None],[None],
[None],,,,,,,,,,,,,,,,|))
PstrCheckMessage1=''
msg2=''
msg3=''
if(dbVal<100):
RESULT=True
PstrCheckMessage1='Amount < 100.'
elif(dbVal>100 and dbVal<=1500):
RESULT=True
PstrCheckMessage1='Amount between 100 and 1500.'
elif(dbVal>1500 and dbVal<=9999):
RESULT=True
PstrCheckMessage1='Amount between 1501 and 9999.'
else:
RESULT=False
PstrCheckMessage1='Amount greater than 9999!'
return [RESULT,PstrCheckMessage1,msg2,msg3]
Note: You must include three message parameters with the return statement to write data to
the status table. Regardless you are only writing a single message, the other two message
parameters are required.
The result of running this script is shown in the Check Report with Warnings:
258
259
On the Rule Logic Editor, select the Rule Logic Add/Edit as Text tab.
Do not use a semicolon (;) in check rules. The semicolon is a reserved as the separator
between the rule value and the display value.
When using the equal sign for evaluating amounts, use double equal signs (==) instead of
the single equal sign (=). For example, use a b == 0, and not a - b=0.
Click OK.
Running Check Reports for Profitability and Cost Management BSO Essbase
Cube
Before running a Check Report for a Oracle Hyperion Profitability and Cost Management BSO
Essbase cube, make sure that a fully qualified name is used to differentiate any duplicate members
used within dimensions or across dimensions. To construct a fully qualified name from a
duplicate member name, add the fully qualified name as a rule logic statement on the Rule Logic
Add/Edit as Text screen (see Adding a Rule Logic Statement as Free Form Text on page 259).
260
Note that a fully qualified member name comprises the duplicate member or alias name and all
ancestors up to and including the dimension name. Each name must be enclosed in brackets
([ ]) and separated by a period (.). The syntax is as follows:
[DimensionMember].[Ancestors...].[DuplicateMember]
For example:
[Market].[East].[State].[New York]
[Market].[East].[City].[New York]
Check Entity Group SummarySummary area that lists the names of the check entity
group, and enables you to create a new check entity group.
Check Entity Group DetailsDetail area where you can name and describe the check entity
group.
Entity DetailsDetail area where you can add information about the entity.
On the Setup tab, under Data Load Setup, select Check Entity Group.
From the Check Entity Group Detail area, enter the check entity group name in the Name field.
Optional: In the Description field, enter a description of the check entity group.
Click Save.
Parent
261
Entity
Consolidate
On Report
Sequence
Click Save.
Table 45
Option
Description
Parent
Specify the organization in which the entity is consolidated. For other target systems, you select the parent of the entity.
If the Consolidate option is not selected, the selection is irrelevant.
Script Name
For Planning and Essbase calculation scripts, specify the calculation script name to execute.
This field is only available when the Check Entity Calculation method is set to calculation script in the Essbase or
Planning application options.
Calc Script
Parameters
Click
to browse and set the script for the calculation script on the Set Calculation Script Parameters screen. You
can also add a calculation script on the Set Calculation Script Parameters screen.
As part of the check rule process, FDMEE references any calculation script parameters included in custom calculation
scripts. A calculation script is a series of calculation commands, equations, and formulas that enable you to define
calculations other than those defined by the database outline. Calculation scripts are defined in Essbase and Planning
target application options, see Using Calculation Scripts on page 75.
This field is only available when the Check Entity Calculation method is set to calculation script in the Essbase or
Planning application options.
If the Check Entity Calculation method is set to dynamic, this field is unavailable.
Entity
Specify the target entity to consolidate and display in the check report. If the Consolidate option is selected, the entity
is consolidated before it is displayed in the check report.
Consolidate
On Report
The option selected in the On Report column determines whether an entity is displayed in the check report. If On Report
is not selected and Consolidate is selected, the entity is consolidated but not displayed.
Sequence
Specify the order in which entities are consolidated and displayed in the check report.
It is good practice to increment the sequence number by 10, to provide a range for the insertion of entities.
262
In This Chapter
Understanding Human Resource Data Integration.................................................... 263
Requirements............................................................................................. 264
Public Sector Planning and Budgeting Dimensions .................................................. 265
Smart Lists................................................................................................ 266
Using Loaded Data in Public Sector Planning and Budgeting ....................................... 266
Defining Human Resource Data Load Rules........................................................... 266
Managing Human Resource Data Load Rules......................................................... 271
Employee
Position
For a high-level process overview of the human resource integration, see Extracting Human
Resource Data on page 33.
263
Requirements
Before you begin your human resource integration, you must complete the following
prerequisites:
l
Run specific processes in PeopleSoft Human Capital Management. See Running Processes
in PeopleSoft Human Capital Management on page 264.
Specify parameters in Planning to enable data to be loaded into Essbase. See Defining the
Data Load Settings in Planning on page 264.
264
Position
Employee
Element
Job Code
Entity
Database Table
Position
AIF_PS_POSITION_DATA_STG
Employee
AIF_PS_JOB_STG
Job Code
AIF_PS_JOBCODE_TBL_STG
Element
AIF_PS_SAL_PLAN_TBL_STG
AIF_PS_SAL_GRADE_TBL_STG
AIF_PS_SAL_STEP_TBL_STG
AIF_PS_EARNINGS_TBL_STG
AIF_PS_BENEF_PLAN_TBL_STG
Entity
AIF_PS_DEPT_TBL_STG
For a complete list of Public Sector Planning and Budgeting tables, see Appendix D, Staging
Tables.
265
Smart Lists
Human Resource data such as salary information, union codes, and status are Smart Lists in
Public Sector Planning and Budgeting applications. FDMEE automatically recognizes Smart
Lists and populates the data accordingly.
FDMEE enables you to assign a prefix to Smart Lists in the Compensation Allocation point of
view (POV). For general ledger integrations, you create metadata mappings and can optionally
define member prefixes. For human resource integrations, you can optionally assign a Smart
List prefix in the rule line mapping definition. You should ensure that member prefixes (used
in a general ledger metadata mapping) are identical to Smart List prefixes (used in a human
resource data rule mapping). For information on human resource rule mappings, see Creating
Mapping Definitions on page 269. For information on general ledger metadata mappings, see
Defining Metadata Rules on page 132.
For information about using Smart Lists in Planning and Public Sector Planning and Budgeting,
see the Oracle Hyperion Planning Administrators Guide and the Oracle Hyperion Public Sector
Planning and Budgeting Users Guide.
For Classic Planning applications, in Planning, refresh the application database as required.
See the Oracle Hyperion Planning Administrators Guide.
For Planning applications administered in Enterprise Performance Management Architect,
navigate to the Application Library and redeploy the application. See the Oracle Hyperion
Enterprise Performance Management Architect Administrators Guide.
To view the data and use it as part of Public Sector Planning and Budgeting, see the Oracle
Hyperion Planning Administrators Guide and the Oracle Hyperion Public Sector Planning and
Budgeting Users Guide.
At a high level, creating human resource data load rules that enable you to populate metadata
and in Public Sector Planning and Budgeting applications involves these steps:
266
Create the human resource data rule and define the rule details. See Defining the Rule
Details on page 267.
Create the rule line definitions and mappings manually or by running a script. See Creating
Rule Line Definitions by Using a Template Mapping on page 268 and Creating Rule Line
Definitions on page 269.
Creating Mapping Definitions on page 269.
Before you begin, ensure that you have performed all required tasks described in Chapter 6,
Loading Human Resources Data.
l
Enter or click
Enter or click
to select the value of the Scenario dimension you identified when you registered
the application. This enables you to classify and collect time-specific data.
Select the Salary Assignment Option to specify the salary assignment details to load by the database
table.
267
Note: To use this option, perform these steps in Running Processes in PeopleSoft
Standard - Include Future DatedLoad data from PS_JOB table that is live on a given
As of Date or is later than it.
Enter or click
Click Save.
In the Rule Definition area of the HR Data Load page, select Create Mapping, and then Copy from
another rule.
Click Copy.
Click OK.
The POV rules and their mapping details are displayed in the Rule Line area.
Edit the mappings as necessary. See Creating Mapping Definitions on page 269.
Click OK.
Click OK.
The Rule Line Definition area is populated with POVs from the template.
Edit the rule line definitions or add new rule line definitions, as necessary. See Editing Human Resource
Data Load Rules on page 271.
Run the data load rule. See Running Human Resource Data Load Rules on page 271.
Salary GradeRates for Element dimension members that correspond to salary grades.
Salary StepRates for Element dimension members that correspond to salary steps.
Define the mappings for the POV. See Creating Mapping Definitions on page 269.
Repeat steps 1 - step 3 through for each POV you want to define.
269
Budget ItemFor Budget Item dimensions, you may want FDMEE to automatically
create the budget item values. This option is available only for the Unspecified Budget
Member. You must select a parent member if you plan to select the optional Auto create
flag setting.
Note: The parent member that you select must match what you selected in the Planning
Data Load Settings window. See Defining the Data Load Settings in Planning
on page 264.
l
Year
Period
Selecting a member for all other dimensions is optional. If you do not select a member for
a dimension, FDMEE loads the values as-is from the source system.
In the Rule Line Mapping area, define the source column to account mappings. To add a mapping, click
.
Enter or click
You select the source column in the PeopleSoft Human Capital Management table that
contains the human resource data to load. For example, if you are creating a rule line
mapping for Salary Grade, select the source column Grade in the PeopleSoft human
resource table. The source columns are specific to the POV Type that you selected when you
created the rule line definition.
Enter or click
You select the Public Sector Planning and Budgeting account into which to load the extracted
human resource data. For example, to load employee names and IDs, select Employee Name
and Employee Number. For a list of all tables and columns, see Appendix D, Staging
Tables.
The Data Type and Smart List Name fields are automatically populated based on the Account
you selected.
270
Note: Several Smart Lists in Public Sector Planning and Budgeting applications are paired
(for example, Account Segment and Account Segment Description). When you map
from the source system to a paired Smart List, map one of the paired Smart List
members (for example, Account Segment, but not Account Segment Description).
Click Save.
Next, run the data load rule. See Editing Human Resource Data Load Rules on page 271.
Edit data load rulesTypically, if you used a script to create the rule line definitions, you
may want to add or edit the mappings. See Editing Human Resource Data Load Rules on
page 271.
Run data load rules. See Editing Human Resource Data Load Rules on page 271.
Delete data load rules. See Deleting Human Resource Data Load Rules on page 273.
Check the data rule process details. See Checking the Human Resource Data Load Rule
Status on page 273.
Enter or click
Select the rule to modify and change the rule details, rule line definition, and mapping settings. See
Editing Human Resource Data Load Rules on page 271.
Click Save.
Import from SourceFDMEE imports the data from the source system, performs the
necessary transformations, and loads the data to the FDMEE staging table.
Select this option only in these situations:
m
You are running a data load rule for the first time.
271
Your data in the source system changed. For example, if you reviewed the data in the
staging table after the export and it was necessary to modify data in the source system.
In many cases, your source system data may not change after you import the data from the
source the first time. Therefore, you need not import the data.
l
Note: Select both options only in cases where you want to load the data directly into the target
application.
Click Execute.
Enter or select the As of Date from which to load data from the human resource source system.
To extract data from the source system, select Import from Source.
For information on staging tables, see Staging Table Used for Import from Source on page
391.
To seed loaded data into your target Public Sector Planning and Budgeting application, select Export
to Target.
a. To load data and/or metadata into a Classic Public Sector Planning and Budgeting
application: Select the Load Type:
l
272
i.
ii.
After the rule runs successfully, in Oracle Hyperion EPM Architect, deploy the
application.
iii.
iv.
Click Execute to run the data load rule, and then select Data.
c. Select the Department Load Option to indicate whether to load all or specific departments
and department data in the business unit:
l
application.
Click Run.
Data is loaded into your Oracle Hyperion Public Sector Planning and Budgeting accounts.
From the Workflow tab, under HR Data Load, select HR Data Load.
Enter or click
Click Yes.
Note: See the aif_<process_id>.log in the java.io.tmpdir folder (for example, C:\Oracle
\Middleware\user_projects\epmsystem1\tmp\aif_2548.log) to view details of
273
274
Batch Processing
7
In This Chapter
Combine one or more load rules in a batch and execute it at one time.
Create a master batch that includes multiple batches with different parameters.
For example, you can have one batch for metadata rules run in serial mode, and a second
batch for the data rule run in parallel mode.
Associate a batch with a batch group for ease of use and security.
Instruct the batch to submit included jobs in parallel mode and return control.
Instruct the batch to submit included jobs in parallel mode and return control only when
all jobs are complete.
Batch processing options are available on the FDMEE task pane, or by executing batch scripts.
If you process batches from the FDMEE task pane, use the Batch Definition option to create a
batch, and specify its parameters and tasks included in the batch. See Working with Batch
Definitions on page 276. Use the Batch Execution option to execute batches. See Executing
Batches on page 281.
Note: FDMEE batch load features are unavailable to the Account Reconciliation Manager. For
Accounts Reconciliation Manager load and scheduling features, see the Oracle Hyperion
Financial Close Management User's Guide.
275
metadata
data
batch
open batch
Batch Definition detailEnables you to add and delete a batch definition. If adding or
modifying a definition, specify the definition name, target application, process method,
return control method, and wait parameters.
Batch Definition parametersEnables you to derive period parameters based on the Import
to Source, Export to Target, POV period, and to indicate data extract parameters. The
parameter definition is unavailable for the batch types batch and metadata (rules).
Batch Definition jobsEnables you to add and delete jobs to a batch. Based on the type of
batch, specific types of rules are allowed.
Use the blank Name and Target Application fields in the Batch Definition summary grid to
enter a batch name or target application on which to search.
The name must contain only alpha, numeric or underscore characters. Do not enter spaces
or any other character.
276
metadata
data
batch
open batch Multi-Periodfile based data sources that include starting and ending
periods.
The Open Batch type is used only for file-based data sources and does not contain any batch
jobs. When you run this type of batch, the process reads the files automatically from the
openbatch directory and imports them into the appropriate POV based on the file name.
When the open batch is run, the master folder is emptied.
SerialProcesses files sequentially, requiring that one file complete its process before
the next file starts its process.
ParallelProcesses files simultaneously.
For batch processing run in parallel mode, complete the following fields
l
Wait for CompletionSelect Wait to return control only when the batch has finished
processed.
Select No Wait to run the batch in the background. In this case, control is returned
immediately.
TimeoutSpecify the maximum time the job can run. FDMEE waits for the job to
complete before returning control.
The Timeout can be in seconds or minutes. Enter a number followed by a S for seconds
or M for minutes.
In Open Batch Directory for an open batch type, specify the folder under inbox\batches
openbatch where the files to be imported are copied. If this field is blank or null, all files under
inbox\batches\openbatch are processed.
10 In File Name Separator for an open batch, select the character to use when separating the five segments
of an open batch file name.
Options:
l
11 Select Auto Create Data Rule to create the data rule automatically for file-based data loads.
Note: The Auto Create Data Rule option is available when the rule type is open batch.
When FDMEE assigns the data rule name, it checks when a data rule with the name
Location_Category exists. If this name does not exist, FDMEE creates the data rule using
the following file naming conventions:
l
Rule NameLocation_Category
277
CategoryCategory
File NameNull
ModeReplace
16 Optional: In After Batch Script, enter the name of the custom script to run after the batch.
You can browse and select, or upload a custom script on the Select screen by clicking
17 Click Save.
In Batch Definition, under Batch Definition Detail, select the Parameter tab.
In Parameters, select Import From Source to import the data from the source system, perform the
necessary transformations, and export the data to the FDMEE staging table.
Select POV Period to derive the period parameters based on POV settings.
If the POV period is selected, the period key start and end period fields are disabled.
This field is only available for a data load batch.
When setting up a batch, you can choose the POV to drive the period, or enter the periods
explicitly. If you select the POV, it is pulled from the Default POV Period setting in System/
Application, or User settings.
Specify dates in the Start Period and End Period to derive period parameters through which the data
is processed.
Use the date format based on the locale settings for your locale. For example, enter the date
using the format MM/DD/YY.
If the Start Period and End Period fields are selected, the POV Period field is disabled.
This field is only available for a data load batch.
In the Import Mode drop-down, select the mode to extract data all at once for an entire period or
incrementally during the period.
Option are:
278
SnapshotExtracts everything for the selected source set for an entire period.
Note the following behavior of Snapshot mode:
m
When the source data for the selected period has never been run, data is extracted
from the source.
When the source data for the selected period has been run, data is extracted from
the FDMEE staging table, and not from the source. This means that if a user has
two locations that extract from the same Enterprise Resource Planning (ERP)
source, data is extracted from the source only once (and the first time only).
For example, if you load data to Financial Management from the E-Business Suite
for a selected period, but you run the integration to ARM for the same source and
period, use what is in the interface tables since data is only extracted the first time
from the source. This result in a significant performance gain for any subsequent
data loads. The first extraction take the longest, but any other subsequent extractions
are fast.
IncrementalExtracts those records that were added after the prior data extract
Full RefreshPerforms a clean extraction from the source system, thereby clearing any
existing data rows in the appropriate FDMEE staging tables for a given source Ledger
(or Business Unit) and source period.
When defining the file name for an open batch that uses multi-periods, specify the
starting and ending periods in the file name, for example,
10~Filerule~Jan03~Mar03~FR.txt.
When defining the file for an open batch that uses a single period, specify the period in
the file name, for example, 10-OBFilerule-Jan03-FR.txt.
Note: The import mode options (Snapshot, Incremental and Full Refresh) are only
are only applicable to Data Rules in a Location using a Standard Import Format. Data
Rules in a Location with a Source Adapter Import format always perform a full data
extraction (similar to Full Refresh) directly into the TDATASEG_T table.
Note: E-Business Suite and FUSION source imports require a full refresh of data load rules
279
For Essbase and Planning applications, in the Export Mode drop-down, select the mode of exporting
data.
For Planning applications, in the Export Mode drop-down, select the mode of exporting data.
Options for Essbase and Planning applications:
l
STORE_DATA
ADD_DATA
SUBTRACT_DATA
OVERRIDE_ALL_DATA
10 For Essbase and Planning applications, in the Export Mode drop-down, select the mode of exporting
data.
For Planning applications, in the Export Mode drop-down, select the mode of exporting data.
Options for Essbase and Planning applications are:
l
STORE_DATA
ADD_DATA
SUBTRACT_DATA
OVERRIDE_ALL_DATA
Accumulate
Replace
Merge
11 Click Save.
In Rule Name, specify the rule name associated with the batch job.
Click Save.
280
Click Add.
Click Save.
Executing Batches
Use the Batch Execution feature to show all batches that you have accessed based on the batch
group assigned. You can also use the Batch Execution feature to select a batch and execute a rule
after parameters passed with the rule have been validated.
Batch Exec shows all batches you have access based on batch group assigned.
Note: The Batch Execution option is only accessible to a user with a Run Integration role.
To execute a rule:
1
In the Batch Execution summary area, select a batch name, and then click Execute.
Optional: You can also schedule a job (see Scheduling Jobs on page 287) and check the status of
the batch (see Viewing Process Details on page 202).
281
loading large number of files. Open batches cannot contain jobs. Additionally, open batches can
be scheduled to run periodically.
The high-level process overview of the Open Batches function consists of:
1. In Batch Definition, create an openbatch folder in the application inbox\batches
subdirectory where the files to be imported are copied.
2. Select the File Name Separator character.
This character is used to separate the five segments of an open batch file name.
3. Select the Auto Create Data Rule option.
4. Stage the open batch files by copying files to the inbox\batches\openbatch folder using
the name format for batch files.
5. In Batch Execution, process the batch.
After a batch is processed, a directory is created, all files within the openbatch directory are
moved into the new directory, and the new directory is assigned a unique batch ID
Use the blank Name and Target Application fields in the Batch Definition summary grid to
enter a batch name or target application on which to search.
From the Target Application drop-down, select the name of the target application.
The serial execution mode processes files sequentially, requiring that one file complete its
process before the next file starts its process.
In Open Batch Directory, specify the folder under inbox\batches\openbatch subdirectory where
the files to be imported are copied. If this field is blank or null, all files under inbox\batches
\openbatch are processed.
In File Name Separator, for an open batch type, select the character to use when separating the five
segments of a batch file name.
Options:
282
10 Select Auto Create Data Rule to create the data rule automatically for file-based data loads.
When FDMEE assigns the data rule name, it checks whether a data rule with
the Location_Category name exists. If the name does not exist, FDMEE creates the data
rule using the following file naming conventions:
l
Rule NameLocation_Category
CategoryCategory
File NameNull
ModeReplace
To use predefined data rules that load data based on specific categories, leave this field blank.
Predefined Data Load RuleTo use a predefined data rule that loads data based on
specific categories, leave the Auto Create Data Rule field blank on the Batch Definition
screen and create the data load rule (see Defining Data Load Rules to Extract Data on
page 161).
Next, create the open batch file name using the following format:
FileID_RuleName_Period_LoadMethod. The file id is a free-form field that you can
use to control the load order. Batch files load in alphabetic order by file name.
The load method is defined using two-character code identifying the load method where
the first code represents the append or replace method for the source load, and second
character represents the accumulate or replace method for the target load.
For the source load method, available values are:
m
AAppend
RReplace
AAccumulate
RReplace
Auto-Created Data Load RuleTo load data to any location category and have FDMEE
create the data load rule automatically, create the open batch file name using the
following format: FileID_Location_Category_Period_LoadMethod. In this case
283
FDMEE looks for the data rule with the name Location_Category. If it does not exist,
FDMEE creates the data rule automatically with the name Location_Category
File IDA free-form field used to control load order. Batch files load in alphabetic order
by file name.
Location
Category
Start Period
End Period
284
and
b_TexasDR1_ Jan-2004_ Jun-2004_RR.txt (Data Rule, Start Period, End
Period)
Use the blank Name and Target Application fields in the Batch Definition summary grid to
enter a batch name or target application on which to search.
The serial execution mode processes files sequentially, requiring that one file complete its
process before the next file starts its process.
In File Name Separator, for an open batch type, select the character to use when separating the five
segments of a batch file name.
Options:
l
10 Select Auto Create Data Rule to create the data rule automatically for file-based data loads.
When FDMEE assigns the data rule name, it checks whether a data rule with the
Location_Category name exists. If the name does not exist, FDMEE creates the data rule
using the following file name convention:
l
Rule NameLocation_Category
CategoryCategory
File NameNull
ModeReplace
285
To use predefined data rules that load data based on specific categories, leave this field blank
Predefined Data Load RuleTo use a predefined data rule that loads data based on
specific categories, leave the Auto Create Data Rule field blank on the Batch Definition
screen and create the data load rule (see Defining Data Load Rules to Extract Data on
page 161).
If you have to load to noncontiguous periods in the open batch, create the data rule in
which the source period mapping are defined, and use this option.
Next, create the open batch file name using the following format:
FileID_RuleName_Period_LoadMethod. The file id is a free-form field that you can
use to control the load order. Batch files load in alphabetic order by file name.
The load method is defined using two-character code identifying the load method where
the first code represents the append or replace method for the source load, and second
character represents the accumulate or replace method for the target load.
For the source load method, available values are:
m
AAppend
RReplace
AAccumulate
RReplace
Auto-Created Data Load RuleTo load data to any location category and have FDMEE
create the data load rule automatically, create the open batch file name using the
following format: FileID_Location_Category_Period_LoadMethod. In this case
FDMEE looks for the data rule with the name Location_Category. If it does not exist,
FDMEE creates the data rule automatically with the name Location_Category.
Auto-create data rule is only applicable for contiguous period loads. If you have to load
to noncontiguous periods, create the data rule in which the source period mapping are
defined.
286
After an open batch is processed, a directory is created, all files within the openbatch
directory are moved into the new directory, and the new directory is assigned a unique batch
ID.
Note: The Open batch feature is unavailable for the Account Reconciliation Manager.
Scheduling Jobs
The scheduling jobs feature provides a method to orchestrate the execution times of metadata
load rules and data load rules.
Note: When you cancel a job from the FDMEE user interface, all instances of a schedule for the
object selected are cancelled. To cancel a specific instance of a schedule, cancel the job
from the ODI studio or ODI console.
To schedule a job:
1
From the Batch Execution screen, Metadata screen, or Data Load Rule screen, select the batch name
(from the Batch Execution screen) or rule (from the Metadata screen or Data Load Rule screens) to
schedule and click Schedule.
For example, if you select the Schedule option from the Data Load Rule screen, specify the
Import from Source, Recalculate, Export to Target, and so on options.
For Data Load Rule scheduling specific options, see Running Data Load Rules on page
183.
Specify the type of scheduling and select the associated date and time parameters.
Click OK.
287
Table 46
Schedule
Type
Simple
Submits the job for execution at a specific day and time, but does not repeat:
Options are:
Hourly
Daily
Weekly
Monthly (day
of month)
288
Timezone
Date
Hour(s)
Minute(s)
Second(s)
Select (AM/PM)
Executes at the specified minutes and seconds after the top of the hour every hour until cancelled. Options are:
l
Timezone
Minute(s)
Second(s)
Timezone
Hour(s)
Minute(s)
Second(s)
Select (AM/PM)
Executes at the specific time for each day selected. Options are:
l
Timezone
Monday-Sunday
Hour(s)
Minute(s)
Second(s)
Select (AM/PM)
Execute at the specific time for the day of the month selected. Also enables you to select the Last Day of Month or Day
Before End of Month. Options are:
l
Timezone
Monthly Date
Hour(s)
Minute(s)
Second(s)
Select (AM/PM)
Schedule
Type
Monthly
(week day)
You can select the first, second, third, fourth, fifth, last, and then the specific day or the week on which to execute the
job. Options are:
l
Day of Month
Day
Hour(s)
Minute(s)
Second(s)
Select (AM/PM)
Note: The Timezone option is unavailable for the Monthly (week day) schedule type.
FDMEE provides a set of Windows batch/UNIX shell scripts that enable users to execute data
load rules from a command line or schedule loads from any scheduler without writing Java code.
Batch scripts can be invoked from the command line. In turn, scripts call the data load and
metadata load API in the FDMEE application server that execute the rules using the normal
process used in data rule and workbench. Batch scripts are located under
a<EPM_ORACLE_INSTANCE>/FinancialDataQuality directory
(<EPM_ORACLE_INSTANCE> is typically is located at: C:\Oracle\Middleware
\user_projects\epmsystem1)
289
Executing the batch script for data load rules. See Executing the Batch Script for Data Load
Rules on page 290.
Executing the batch script for metadata rules.
To encrypt a password:
1
Replace the [file] with the actual file name, and do not include the brackets.
The script encrypts the password and writes it to the file provided as a parameter.
For information on running a data load rule batch script with a password from a file,
see Executing the Batch Script for Data Load Rules on page 290.
For information on running a metadata load rule batch script with a password from a
file, see Executing the Batch Script for Metadata Rules on page 292.
290
Paste and run the following command: loaddata USER PASSWORD RULE_NAME
IMPORT_FROM_SOURCE EXPORT_TO_TARGET EXPORT_MODE IMPORT_MODE
LOAD_FX_RATE START_PERIOD_NAME END_PERIOD_NAME SYNC_MODE
To run the data load rule batch script with a password from a file:
1
Paste and run the following command: loaddata USER -f:PASSWORD_FILE RULE_NAME
IMPORT_FROM_SOURCE EXPORT_TO_TARGET EXPORT_MORE IMPORT_MODE
LOAD_FX_RATE START_PERIOD_NAME END_PERIOD_NAME SYNC_MODE
Parameter
Value
User
Username
Password
IMPORT_FROM_
SOURCE
Y or N
EXPORT_TO_
TARGET
Y or N
EXPORT_MODE
STORE_DATA
ADD_DATA
SUBTRACT_DATA
REPLACE_DATA
OVERRIDE_ALL_DATA
Accumulate
Replace
Merge
Replace_By_Security
291
Parameter
Value
IMPORT_MODE
Snapshot
Incremental
Full Refresh
Append
Replace
Note: E-Business Suite and FUSION source imports require a full refresh of data load rules before export after
upgrading from a 11.1.2.2 release.
START_PERIOD_
NAME
Period Name or POV if the POV specified period value is retrieved from the period profile.
END_PERIOD_
NAME
Period Name or POV if the POV specified period value is retrieved from the period profile.
SYNC_MODE
SYNC/ASYNC
l
ASYNCWhen the ODI job is submitted, control returns. The load process continues to execute in ODI.
At a Windows command window or UNIX shell, paste and run the following command:
loadmetadata USER PASSWORD LOCATION_NAME SYNC_MODE
To run the metadata load rule batch script with a password from a file:
1
At a Windows command window or UNIX shell, paste and run the following command:
loadmetadata USER -f:PASSWORD_FILE LOCATION_NAME SYNC_MODE
Parameter
Value
User
Username
Password
292
Parameter
Value
Location
Location Name
SYNC_MODE
SYNC/ASYNC
l
SYNCProcess run immediately and control returns when the process completes.
ASYNCWhen ODI job is submitted, control returns. The load process continues to execute executed in ODI.
Paste and run the following command: loadhrdata USER PASSWORD LOCATION_NAME
SYNC_MODE
To run the HR data d rule batch script with a password from a file:
1
Parameter
Value
User
Username
Password
Rule Name
IMPORT_FROM_SOURCE
Y or N
EXPORT_TO_TARGET
Y or N
As of Date
Date used to determine applicable effective date. Date must be in the YYYY-MM-DD format.
Load Type
293
To run the import mapping rule batch script with a password from a file:
1
Parameter
Value
USER_NAME
Username
ENCY_PASS
LOCATION_NAME
Location Name
DIMENSION_NAME
File_PATH
Replace
AAppend
RReplace
Validate
Y or N
SYNC_MODE
SYNC/ASYNC
l
ASYNCWhen the ODI job is submitted, control returns. The load process continues to execute in ODI.
Executing the Batch Script for Data Load Rules to Write Back
Use the Loaddata script to extract data from source EPM applications to target Enterprise
Resource Planning (ERP) systems. See Executing the Batch Script for Data Load Rules on page
290.
Running a Batch
To run the batch with a plain text password:
1
294
Paste and run the following command: runbatch USER PASSWORD LOCATION_NAME
SYNC_MODE.
Parameter
Value
User
Username
Password
Rule Name
Batch Name
295
296
8
In This Chapter
Overview
FDMEE offers a powerful extensibility framework by providing Jython and Visual Basic based
scripting. Using the rich set of the API library, users can extend and customize the product to
best fit their needs. FDMEE supports four types of scripts:
l
Import scriptsExecuted as source files are imported. Uses Jython script only.
Mapping scriptsUsed to build mapping logic to derive target members based on multiple
source column and IF THEN logic. Uses Jython and SQL script.
Event scriptExecuted in response to FDMEE such as before or after an import. Uses Jython
and Visual Basic script.
Custom scriptEnables manual execution of scripts. Uses Jython and Visual Basic script.
FDMEE provides a set of Java APIs that enable you to look up frequently used data load properties
or to perform a common action. FDMEE also supports Visual Basic based event scripts.
Code Indentation
www.jython.org
www.python.org
298
Import scripts must be created using Jython functions only. The format is def
<name>(parm1, parm2) and a return value.
Import script pass two parameters by FDMEE:
m
For example, when the account column is defined as position 2 to position 4 characters,
then this value gets passed as the value for the field, and the whole input line is passed as the
second parameter. In the sample script (see Import Script Sample on page 309) these
parameters are specified by the StrField and StrRec values, but can be any names as long as
you remember that the first parameter is the field, and the second one is the entire record.
l
The file name and the function name must be the same.
The return value from the function populates the source column in the TDATASEG table for
the specified dimension. You can only return a single value.
It is recommended that you use a text editor to edit your script, and then copy and paste it
into FDMEE.
Import scripts are not handled in Lifecycle Management.
Click OK.
299
Write the code for the custom script in the Script Editor.
Click Save.
strFieldThe values of the source-file column that is defined in the import format (For
example, for import scripts assigned to the Amount column, strField contains amount
values, and, for import scripts assigned to the Account column, strField contains account
values.
strRecordThe source-file line (record) that is being scanned.
In following example, the script concatenates the account code with the account description
from the source file. For example, the first data line of the file is account code 1110 with a
description of Cash. This script concatenates 1110 with Cash and creates a source account
in the TDATASEG table named 1110-Cash. (See TDATASEG Table Reference on page
419). In the script, you select the field that is defined by the import format, and then the field
defined by places 14 through 34 in the current record. (Jython starts numbering columns with
0 rather than 1.)
300
From the Import Format summary grid, select the import format name.
Note: Use non-ASCII characters in an import format name when the import source is an
adapter.
From the Import Format detail grid, select the Add Expression icon.
You can also type the value directly in the field rather than use the Expression editor.
301
From Add Expression, and then from Expression Type, select Script.
Click OK.
The script is assigned to the import field. The name of the import script is displayed in the
Expression column.
302
Solution: In the Import Scripts screen, assign the following script to the Expression field of the
Account row. The script assigns the first four digits of each account number (the first four digits
on the left) to Parse_Account:
def Parse_Account (strfield, strrecord):
return strField[:4]
Result: The import file displays only the first four digits of each account number.
303
Solution: In the Import Formats screen, assign the following script to the Expression field of the
Account row. : In the Import Formats screen, assign the following script to the Expression field
of the Account row. The script extracts and returns the characters of the account strings (the
characters from positions 7 to 10 of the string):
def Parse_Account (strfield, strrecord):
return strField[6:10]
Result: Account strings are separated from cost center and account description strings.
Result: In the Account column of the import file, only account numbers are displayed.
304
Solution: In the Import Formats screen, assign the following script to the Expression field of the
Account row. The script extracts and returns the account numbers (the last four characters of
the account fields):
def Parse_Account (strfield, strrecord):
return strField[-4:]
Result: In the Account column of the import file, only account numbers are displayed.
Solution: In the Import Formats screen, assign the following scripts, each of which uses the split
function, to the Expression fields of the Entity, Account, and Account Description rows (first
script to Entity, second script to Account, and third script to Account Description). The first
script returns the set of characters before the first hyphen (a cost center value), the second script
305
returns the set of characters after the first hyphen (an account value), and the third script returns
the set of characters after the second hyphen (an account description value).
def NY_ParseCenter (strfield, strrecord):
seglist = strfield.split(-)
return seglist[0].strip()
def NY_ParseAccount (strfield, strrecord):
seglist = strfield.split(-)
return seglist[1].strip()
def NY_ParseDesc (strfield, strrecord):
seglist = strfield.split(-)
return seglist[2].strip()
Result: In the import file, cost center, account and account description strings are presented in
three separate fields.
Solution: In the Import Scripts screen, you assign the following script to the Expression field of
the Entity row. The script parses the entity column and uses a local variable that is discarded
after the script executes:
def NY_Skip06Center(strField, strrecord):
if strfield.count(-) > 0:
seglist = split(strField, -)
strEntity = seglist[0]
if strEntity[:2] == 06:
return fdmSkip
else:
return strEntity
Result: No line that contains entity values that begin with 06 is imported.
306
307
Then, in the Import Formats screen, you assign the script to the Expression field of the Entity
row and, thus, assign the values of the global variables to the Entity fields. In this case, entity
values are not read from the source file.
Because the Georgia file includes subtotal lines that must not be imported, the Skip function
is required.
To direct FDMEE to skip lines without account numbers, you configure a Skip Row in the Import
Format to recognize blank Account fields (15 blank spaces) by defining appropriate start and
length fields for the expression.
308
309
if strrec[14:27] == "Organization:" :
global globalorg
globalorg = strrec[29:32]
if strrec[42:47].strip() == 'Total' or strrec[29:34].strip() == 'Total' :
return fdmSkip
return strfield
#---------------------------------------------------------------# Sample to return the global variable set during amount process
#---------------------------------------------------------------def getCurrfromGlobal(strfield, strrec) :
return globalcur
Mapping scripts are unavailable for Explicit and Multi-dimension mapping types.
Value. For this reason, this field cannot be used to specify a value of "IGNORE",
which is otherwise used to set the VALID_FLAG to Yes or No. For SQL based
mappings, you must include the VALID_FLAG in the SQL script and specify the
value of "I" based on the user selected criteria.
6
310
In Rule Name, enter the data rule name for the mapping.
Click Save.
) is enabled.
For example the following Jython based mapping script checks when the first two characters
of the account equals 11 and the entity equals 01. When a match occurs, then the target is
set to Cash2 and the target amount is set to 0. In addition, the script also updates the
attribute1 column in the TDATASEG table. (See TDATASEG Table Reference on page
419). This script uses the fdmResultMap object (see Using Jython Objects with Mapping
Scripts on page 312).
In the next example, use the SQL script where logic is implemented in a SQL CASE statement.
The CASE statement is used in the SET command of the internal UPDATE statement. he
mapping statement below is converted to the UPDATE statement listed
UPDATE TDATASEG
SET ACCOUNTX =
CASE
WHEN ACCOUNT LIKE L% AND ICP = 000 THEN A4140
WHEN ACCOUNT IN (110,120,130) THEN A100
ELSE A || ACCOUNT
END
,DESC1 = COALESCE(DESC1, ACCOUNT || . || ICP)
311
WHERE ACCOUNT ..
Jython Object
Description
fdmRow
fdmRow id used to access any column in the current row being processed by the mapping process. You can access
any column in the TDATASEG table. To access a value in a column you specify the following: fdmRow.
getString[<COLUMN NAME>]. For example, to get the value of the ENTITY column you specify fdmRow.
getString[ENTITY].
fdmResult
fdmResult is used to return the value from the mapping function. You can set the value as follows fdmResult
= Cash. The fdmResult is used to update the value for the target dimension, which is also referred to as the X
column.
For every dimension in the TDATASEG table there are two columns, one for source and another for target. For example,
ENTITY provides the source value, and ENTITYX provides target value that is the result of the mapping process.
fdmResultMap
fdmResultMap is used to update any column in the TDATASEG table. The column name in the TDATASEG table is
used as the key in the map. For example, to update the ATTR1 column use fdmResultMap[ATTR1] =
Asset Acct. To set the target amount to 0 use fdmResultMap[AMOUNTX] = 0.
312
THEN '6110'
THEN '6120'
FDMEE Events
Event
Description
BefImport
This event is the initial state of the system before any processing for the selected location has begun. If the user defines
import scripts, they are run between the BefImport and AftImport events. This step in the processing loads data into
the TDATASEG_T table.
AftImport
BefCalculate
Called for a validation run only, and called before the validation process.
AftCalculate
Called for a validation run only, and called after the validation process.
BefProcLogicGrp
AftProcLogicGrp
BefProcMap
Called before the mapping process is started in the TDATASEG_T table. Mapping scripts are executed between the
BefProcMap and AftProcMap events. Data is moved from the TDATASEG_T table to the TDATASEG table between these
events after all data has been mapped. Updates to audit tables are also included as part of this process.
313
Event
Description
AftProcMap
Called after all the mapping has been completed. When this event runs, the data has already been moved from the
TDATASEG_T table to the TDATASEG table.
BefValidate
AftValidate
BefExportToDat
Called before you write to the file for export. It is also executed for Essbase in the export to file mode feature.
Note: This event is unavailable for the Accounts Reconciliation Manager.
AftExportToDat
BefLoad
AftLoad
Called after data is sent to the target application, but does not wait for the target application to complete the load
process.
Note: This event is unavailable for the Accounts Reconciliation Manager.
BefConsolidate
Oracle Hyperion Financial Management and Oracle Essbase only: This event executed when a check rule is included in
the location that is being processed.
Note: This event is unavailable for the Accounts Reconciliation Manager.
AftConsolidate
BefCheck
AftCheck
314
Note: Before creating event scripts, make sure you check the Application Root Folder setting in
Application Settings. When you specify a folder at the application level , then select the
Create Application Folders option. A set of folders is created for the application that
includes a scripts folder. Create scripts specific to an application in this folder. This is
especially important for event scripts that are different between applications. When you
do not set up an application level folder, then you cannot have different event scripts by
application.
For example,
if (categoryName == ""):
raise RuntimeError, "Category name is invalid"
315
infilename = fdmContext["INBOXDIR"]+"/InputFile.txt"
outfilename = fdmContext["INBOXDIR"]+"/DataFile.txt"
infile = open(infilename, "r")
outfile = open(outfilename, "w")
for line in infile:
column = line.rsplit(',',2)
if column[2].strip() != "Sales" :
outfile.write(column[0] + ",UnitsSold," + column[1] + "\n")
outfile.write(column[0] + ",Sales," + column[2])
outfile.close()
316
?
,?
,?
,?
,?
)
"""
sourceConn = sql.DriverManager.getConnection("jdbcUrl", "user", "password");
# Limiting number of rows to 5 during the test runs.
selectStmt = "SELECT * FROM orders WHERE rownum < 6"
stmt = sourceConn.prepareStatement(selectStmt)
stmtRS = stmt.executeQuery()
while(stmtRS.next()):
params = [ batchName, stmtRS.getBigDecimal("Customer_Id"),
stmtRS.getString("Ship_Country"),
stmtRS.getBigDecimal("Freight"), stmtRS.getString("Ship_Name") ]
fdmAPI.executeDML(insertStmt, params, False)
fdmAPI.commitTransaction()
stmtRS.close()
stmt.close()
sourceConn.close()
#-----------------------------------------------------------------------------# Sample to send email messages using Jython SMTP library
------------------------------------------------------------------------------import smtplib
sender = "[email protected]"
receivers = "[email protected]"
message = """ This is a test e-mail message.
This is a test e-mail message. """
try:
smtpServer = smtplib.SMTP('smtp.gmail.com:587')
smtpServer.starttls()
smtpServer.login("user", "password")
smtpServer.sendmail(sender, receivers, message)
print "Successfully sent email"
smtpServer.quit()
except Exception, e:
print "Error: unable to send email: " + str(e)
Note: See the online Jython documentation at the following link that explains the list of Jython
exceptions, and the syntax to use when trapping exceptions in your scripts: http://
www.jython.org/jythonbook/en/1.0/ExceptionHandlingDebug.html
This note applies to all script types.
FDMEE supports custom scripts in Jython and Visual Basic. To execute a custom ODI process,
then use a Jython script. FDMEE stores custom scripts in the <APP DIR>/data/scripts/
custom folder.
Note: Custom scripts are not handled in Oracle Hyperion Enterprise Performance Management
Scripts created in Jython are saved with a .py extension. Scripts created in Visual Basic are
saved with a .vbs extension.
Click OK.
Write the code for the custom script in the Script Editor.
Click Save.
Click Add.
In Sequence, enter the display order used when custom script groups are shown during registration and
execution.
318
Click Save.
Registering Scripts
Registered scripts are associated with a script file (which consists of Jython or Visual Basic script)
and a target application. When the custom script is executed, you are prompted with a list of
values from which to complete the parameters of the script.
To register a script:
1
DetailsShows the script name, associated target application, and script file.
ParametersShows the parameter name and type, display name, sequence, parameter
value, and any query definition used to supply a list of values for a given custom script.
In the Details grid, in Name, enter the name of the custom script.
In Target Application, select the target application associated with the custom script.
To associate the custom script with a custom script group, in Custom Script Group, select the group.
In Script File, select the script file to associate with the custom script.
To search on a script file, click Select and choose a script file from the Select Script File
screen.
To upload a script file, click Select. On the Select Script File. click Upload. Then click
Browse to navigate to the script file to upload and click OK.
Click Save.
319
From the Summary grid, select the name of the custom script to which to add parameters.
In Parameter Name, enter the name of the parameter that you reference in the script.
For example, enter POVLOC, for the POV location, POVPeriod for the POV period,
POVCAT for POV category, or POVTARGET for the target category.
The parameter name is user-defined. You can select a prefix or suffix to distinguish them in
the custom script.
Available types:
l
POVPrompts for the POV location, period, category or rule. The POV values default
from the users' POV when the custom script is executed.
QueryThe Query type enables you to create a query that populates a list of values that
a user can select from when the custom script is executed.
StaticA Static type indicates that the parameter is a constant or a predefined value,
and the parameter value is supplied by the user. When the custom script is executed,
you can supply a different value to the parameter.
You can use any name for the parameter and also use a prefix or suffix with the name to
distinguish them in the custom script.
The parameter name must exactly match what is provided in the script registration
In Display Name, enter the name to display for the parameter for the Execute Script screen.
In Parameter Value, enter the value for the Static parameter type.
The parameter value must be retrieved in the custom script using the following API:
fdmAPI.getCustomScriptParameterValue("PARAMETER NAME"))
In Sequence, enter the display order of the parameter on the Execute Script screen.
In Query, specify the query definition that provides a list of values for the parameter.
For example, to show a list of data rules for the user to select on the Generate Report screen,
specify the query definition to define these queries.
Click Save.
In Script Execution, and then in Custom Script Group, select a custom script group.
320
Click Execute.
# Get all script parameters and log their names and values at the DEBUG level
fdmAPI.logDebug("Custom script parameter values by name: begin")
fdmAPI.logDebug("The value of parameter CUSTOM_LOCATION is = " +
fdmAPI.getCustomScriptParameterValue("CUSTOM_LOCATION"))
fdmAPI.logDebug("The value of parameter CUSTOM_YEAR is = " +
fdmAPI.getCustomScriptParameterValue("CUSTOM_YEAR"))
fdmAPI.logDebug("Custom script parameter values by name: end")
# Example submitting a data rule
import os
import subprocess
os.chdir("C:/Oracle/Middleware/user_projects/epmsystem1/FinancialDataQuality")
myScriptName = "C:/Oracle/Middleware/user_projects/epmsystem1/FinancialDataQuality/
loaddata.bat"
command = '%s "%s" "%s" "%s" "%s" "%s" "%s" "%s" "%s" "%s" "%s" "%s"' % (myScriptName,
"admin", "password", "SRESBA1_DR1", "Y", "N", "STORE_DATA", "SNAPSHOT", "N", "Jan-2003",
"Jan-2003", "ASYNC")
fdmAPI.logDebug("Submitting a data rule via a script using the following command: " +
command)
retcode = subprocess.Popen(command)
fdmAPI.logDebug("Data rule submitted fine.")
321
# Close the connection and log the end of the script, at INFO level
fdmAPI.closeConnection()
fdmAPI.logInfo("======================================================================")
fdmAPI.logInfo("Custom Script: end")
fdmAPI.logInfo("======================================================================")
APPID
BATCHSCRIPTDIR
CATKEY
322
CATNAME
CHKSTATUS
EPMORACLEHOME
EPMORACLEINSTANCEHOME
EXPORTFLAG
EXPORTMODE
EXPSTATUS
FILEDIR
FILENAME
IMPORTFLAG
IMPORTFORMAT
IMPORTMODE
IMPST
IMPSTATUS
INBOXDIR
LOADID
LOCKEY
LOCNAME
MULTIPERIODLOAD
OUTBOXDIR
PERIODNAME
PERIODKEY
PROCESSSTATUS
RULEID
RULENAME
SCRIPTSDIR
SOURCENAME
SOURCETYPE
TARGETAPPDB
TARGETAPPNAME
VALSTATUS
323
API
Description
Returns the Period Key of the start period based on the LOADID.
Returns the Period Key of the end period based on the LOADID when
loading a single period, and the start period and end period are the
same.
324
API
Description
getBatchJobDetails
BATCH_ID
BATCH_NAME
APPLICATION_ID
BATCH_TYPE
BATCH_EXECUTION_MODE
BATCH_WAIT_TIMEOUT
USER_POV_PERIOD
OPEN_BATCH_FOLDER
PLAN_TYPE
FILENAME_SEPARATOR
BATCH_GROUP_ID
BEF_PROCESS_BATCH_SCRIPT
AFT_PROCESS_BATCH_SCRIPT
EXECUTION_DATE
EXECUTED_BY
LOADID
BATCH_LOADID
PARENT_BATCH_LOADID
PARTITIONKEY
CATKEY
START_PERIODKEY
END_PERIODKEY
IMPORT_FROM_SOURCE_FLAG
EXPORT_TO_TARGET_FLAG
RECALCULATE_FLAG
CHECK_FLAG
JOURNAL_FLAG
IMPORT_MODE
EXPORT_MODE
IMPGROUPKEY
PROCESS_NAME
RULE_TYPE
LOG_FILE
OUTPUT_FILE
EPM_ORACLE_INSTANCE
ODI_SESSION_NUMBER
STATUS
Execute any DML Statement. Provide the query and parameter. The
parameter is provided as a list.
325
API
Description
logFatal(String pLogMessage)
logError(String pLogMessage)
logWarn(String pLogMessage)
logInfo(String pLogMessage)
logDebug(String pLogMessage)
Returns the value for given custom script parameter name and loadID.
Object getCustomScriptParameterValue(String
pParameterName)
Returns the value for given custom script parameter name and context
initialized loaded,
ResultSet getBatchDetails()
ResultSet getCategoryList()
326
API
Description
ResultSet getCheckEntityForGroup
ResultSet getCustomDBLog()
ResultSet getCustomScriptParameters()
Returns the list of custom script parameters in a result set for the
context initialized loadID.
Returns the list of custom script parameters in a resultset for the given
loadID
ResultSet getPeriodList()
Execute any SQL Query Statement. The query results are returned in a
result set. Provide the query and parameter. The parameter is provided
as a list.
Return the Import Format details in a result set based on the Import
Format key.
Return the Import Format Mapping details in a result set for a given
Import Format key. This currently supports only file based import
formats.
Return the Location details in a record set for a given Location key.
Returns the Data Rule details in a record set for a given Data Rule ID.
showCustomDBLog()
showCustomFile(String filePath)
Show a custom file (log file, report file) in the user interface after
completion of a process. Message can be displayed at the end of a
data load workflow step like import, validate, export, check or at the
end of a custom script execution. Note messages are displayed only
when the process are run in online mode.
showCustomMessage(String message)
String getCustomMessage()
Retrieves the last custom message raised for the current process.
327
API
Description
Retrieves the last custom message raised for the given loadid.
String getCustomFile()
Returns the value set for an option. Options can be set at the System
Setting, Application Setting, and User Setting. The order of precedence
is: User, Application, and System. The API determines the appropriate
applicable value and returns the value.
Writes the log information to the Data Load Process log file. The logs
is written based on the process log level. Logs can be created only from
a data load workflow process.
Note: It is recommended that you use the logging API, for example
logDebug or, logInfo API, instead of using the writeToProcessLogsFile
API.
void closeConnection()
Update the import format for the current run. This is applicable only for
File-based import formats.
328
The scripts above uses the u prefix for the user defined strings. You can optionally specify the
u prefix for English/ASCII strings (that is, you can use "1110" or u"1110"). The following shows
the result of the mapping applied on the workbench.
329
fdmAPI.initializeDevMode(conn);
print "SUCCESS CONNECTING TO DB"
fdmContext = fdmAPI.initContext(BigDecimal(1720))
#End Initialize Code Required for Dev Mode. Not required in production script
#Code
print
print
print
Execute RegisterVBAPI.vbs.
The RegisterVBAPI.vbs script requires one parameter to be passed to it. The parameter must
be the path (wrapped in quotes) to the Oracle Instance Path.
For example, RegisterVBAPI.vbs "C:\Oracle\Middleware\user_projects\epmsystem1"
330
API Call
Method/
Property/
Object
Reference
Description
fInitializeMainAPI
Method
Initialize the VB API. This function must be called first in order to use the VB API.
Input: ByVal LoadID As String, ByVal Token As String, ByVal OracleInstancePath As String, ByVal
JavaHomePath As String, ByVal DatabaseProvider As String
Output: True or False
URLDecodeString
Method
Dispose
Method
Initiates the .Net garbage collection process to destroy the API object.
API Call
Method/Property/Object Reference
Description
PstrConnInfoCacheFile
Property
Returns the path to the ccs file stored in the user projects directory
under the FDM folder. This file contains the connection information
returned by COMJNI. This file is encrypted.
PstrConnInfoTempFilePath
Property
PstrDatabaseName
Property
Database name
PstrDatabasePassword
Property
Database password
PstrDatabaseServer
Property
Database server
PstrDatabaseUserName
Property
PstrDataDir
Property
PstrDBConnectionString
Property
PstrDBPort
Property
DB port
PstrDBProvider
Property
DB provider
331
API Call
Method/Property/Object Reference
Description
PstrInboxDir
Property
PstrJavaHomePath
Property
PstrLoadID
Property
Load ID
PstrOracleHomePath
Property
Oracle Home
PstrOracleInstancePath
Property
PstrOutboxDir
Property
PstrScriptsDir
Property
PstrToken
Property
Token
PstrTopLevelDir
Property
API.DataWindow.Connection
API Call
Method/Property/Object Reference
Description
GlngErrNo
Property
GstrError
Property
PblnEncodingUnicode
Property
PblnUseTrans
Property
PobjApp
Object Reference
PstrConnection
Property
PstrDatabase
Property
PstrDatabaseUserID
Property
PstrDirData
Property
PstrDirInbox
Property
PstrDirOutbox
Property
PstrDirReport
Property
PstrDirScripts
Property
332
API Call
Method/Property/Object Reference
Description
PstrLanguageCode
Property
PstrProvider
Property
PstrQueryDateMask
Property
Get/Set Query Date mask which is used through the API for queries
involving date fields. The default is yyyMMdd.
PstrResourceFileDirectory
Property
PstrServer
Property
fGenerateRnd
Method
fGetOSUserID
Method
DataManipulation Class
fdmAPI.API.DataWindow.DataManipulation.API Call
Table 58
DataManipulation Class
API Call
Method/Property/Object
Reference
Description
fExecuteDML
Method
PlngRecordsAffected
Property
API Call
Method/
Property/
Object
Reference
Description
fParseString
Method
Extract a substring from a delimited string based on its field position within the total number of
fields.
Inputs: ByVal strRecord As String, ByVal intFldCount As Integer, ByVal intFldToReturn As Integer,
ByVal strDelimiter As String
Output: String
333
API Call
Method/
Property/
Object
Reference
Description
fGetRandomNumber
Method
API Call
Method/
Property/
Object
Reference
Description
farsFireHose
Method
Open an ADO forward only/read only recordset for fast data streaming.
Inputs: ByVal strSQL As String, Optional ByVal blnServerCursor As Boolean, Optional ByVal
lngMarshalType As Long
l
Method
Open an ADO keyset type recordset based on the specified lock type.
Inputs: Inputs: ByVal strSQL As String, Optional ByVal lngLockType As Long, Optional ByVal
blnServerCursor As Boolean, Optional ByVal lngMarshalType As Long
l
lngLockTypeADO LockTypeEnum
(adLockReadOnly=1;adLockPesimistic=2;adLockOptimistic=3;adLockBatch Optimistic=4)
Output: ADODB.Recordset
334
API Call
Method/
Property/
Object
Reference
Description
farsPage
Method
Open an ADO BatchOptimistic recordset limited to the records found on the specified page. The
record set returned is programmatically created and is disconnected.
Inputs: ByVal strSQL As String, ByVal lngPageSize As Long, ByVal lngPage As Long,
lngOPRecordCount As Long, Optional ByVal lngMarshalType As Long
l
Output: ADODB.Recordset
farsPageFind
Method
Open an ADO BatchOptimistic recordset limited to the records found on the specified page and for
the specified criteria. The recordset returned is programmatically created and is disconnected.
Inputs: ByVal strSQL As String, ByVal strCriteria As String, ByVal lngStartPosition As Long, ByVal
lngPageSize As Long, lngOPRecordCount As Long, lngOPFindPostion As Long, Optional ByVal
lngMarshalType As Long
l
Output: ADODB.Recordset
335
API Call
Method/
Property/
Object
Reference
Description
farsPageFindFromKey
Method
Open an ADO BatchOptimistic recordset limited to the records found on the specified page and for
the specified criteria. The recordset returned is programmatically created and is disconnected.
Inputs: ByVal strSelect As String, ByVal strFrom As String, ByVal strWhere As String, ByVal strGroupBy
As String, ByVal strHaving As String, ByVal strOrderBy As String, ByVal strKeyFieldName As String,
ByVal strFindFieldName As String, ByVal strCriteria As String, ByVal lngStartPosition As Long, ByVal
lngPageSize As Long, lngOPRecordCount As Long, lngOPFindPostion As Long, Optional ByVal
l
lngMarshalTypeAs Long
Output: ADODB.Recordset
336
API Call
Method/
Property/
Object
Reference
Description
farsPageFromKey
Method
Open an ADO BatchOptimistic recordset limited to the records found on the specified page. This
method is optimized for high volume queries. The recordset returned is programmatically created
and is disconnected.
Inputs: ByVal strSelect As String, ByVal strFrom As String, ByVal strWhere As String, ByVal strGroupBy
As String, ByVal strHaving As String, ByVal strOrderBy As String, ByVal strKeyFieldName As String,
ByVal lngPageSize As Long, ByVal lngPage As Long, lngOPRecordCount As Long, Optional ByVal
lngMarshalType As Long
l
Output: ADODB.Recordset
farsSnap
Method
Outputs:ADODB.Recordset
farsTableAppend
Method
Open an ADO keyset type recordset based on the specified lock type using the ADO Table
Direct command directive and with the Append-Only Rowset property set to true.
Inputs: ByVal strTableName As String, Optional ByVal lngMarshalType As Long
l
Outputs: ADODB.Recordset
337
API Call
Method/
Property/
Object
Reference
Description
fImpFieldsForGroup
Method
Returns a recordset containing all of the records ("Mappings") for the Import Format name (string)
passed in at runtime.
Inputs: ByVal strGroupKey As String, Optional ByVal blnReadOnly As Boolean = False, Optional
ByVal blnSQLOnly As Boolean = False, Optional ByVal lngMarshalType As Integer = 0
fImpGroup
Method
Returns a recordset containing all records in TBHVIMPGROUP table for the Import Format name
(string) passed in.
Inputs: ByVal strGroupKey As String, Optional ByVal blnReadOnly As Boolean = False, Optional
ByVal blnSQLOnly As Boolean = False, Optional ByVal lngMarshalType As Integer = 0
fImpGroupList
Method
Returns a recordset containing all import format groups based on group type.
Inputs: ByVal lngGroupType As Integer, Optional ByVal blnIncludeNone As Boolean = False,
Optional ByVal blnReadOnly As Boolean = False, Optional ByVal blnSQLOnly As Boolean = False,
Optional ByVal lngMarshalType As Integer = 0
Output: ADODB.Recordset
fIntDimensionList
Method
fLoadDetails
Method
338
API Call
Method/
Property/
Object
Reference
Description
fPartition
Method
Returns a recordset containing all of the properties of the location passed into the function.
ByVal strLoc As String, Optional ByVal blnReadOnly As Boolean = False, Optional ByVal
blnSQLOnly As Boolean = False, Optional ByVal lngMarshalType As Integer = 0
Output: ADODB.Recordset
fPartitionList
Method
fPeriodKeyList
Method
Returns a recordset containing the list of period keys for the loadid passed to the function.
Inputs: ByVal strLoadID As String, Optional ByVal blnReadOnly As Boolean = False, Optional ByVal
blnSQLOnly As Boolean = False, Optional ByVal lngMarshalType As Integer = 0
Output: ADODB.RecordsetOutput: ADODB.Recordset
fPOVDataValue
Method
fProcessBalImpFile
Method
Return a recordset containing the name of the imported file for a given load id. For all non-file
based imports, this function returns an empty string.
Inputs: ByVal strLoadID As String, Optional ByVal blnReadOnly As Boolean = False, Optional ByVal
blnSQLOnly As Boolean = False, Optional ByVal lngMarshalType As Integer = 0
Output: ADODB.Recordset
fProcessLogForPOV
Method
Return a single process status record for the specified POV value/intersection.
Inputs: ByVal strLoc As String, ByVal strCat As String, ByVal strPer As String, ByVal strRuleID As
String, Optional ByVal blnReadOnly As Boolean = False, Optional ByVal blnSQLOnly As Boolean
= False, Optional ByVal lngMarshalType As Integer = 0
Output: ADODB.Recordset
fTrialBalanceConverted
Method
Returns a recordset containing all records pulled from: tDataSeg based on LoadID, Loc, Scenario,
and Period.
Inputs: ByVal strLoadID As String, ByVal strLoc As String, ByVal strCat As String, ByVal strPer As
String, Optional ByVal blnExcludeIgnore As Boolean = False, Optional ByVal blnSQLOnly As
Boolean = False, Optional ByVal lngPageSize As Integer = 0, Optional ByVal lngPage As Integer
= 0, Optional ByRef lngOPRecordCount As Object = Nothing, Optional ByVal lngMarshalType As
Integer = 0
Output: ADODB.Recordset
339
API Call
Method/
Property/
Object
Reference
Description
fTrialBalanceLite
Method
Return a recordset listing the DataKey field from the data segment table assigned to the specified
location. The data is returned based on the specified POV values and calculation types. The
purpose of this recordset is to create a fast/light weight recordset that you can use to execute a
looping cursor delete.
nput: ByVal strLoadID As String, ByVal strLoc As String, ByVal strCat As String, ByVal strPer As
String, ByVal strCalcTypes As String, Optional ByVal lngStartCalcType As Integer = 0, Optional
ByVal lngEndCalcType As Integer = 0, Optional ByVal strJournalID As String = "", Optional ByVal
blnSQLOnly As Boolean = False, Optional ByVal lngMarshalType As Integer = 0
Output: ADODB.Recordset
fValEntGroupList
Method
fValEntitiesForGroup
Method
Return a recordset containing validation entity specifications for the specified validation entity
group.
Inputs: ByVal strGroupKey As String, Optional ByVal blnReadOnly As Boolean = False, Optional
ByVal blnSQLOnly As Boolean = False,Optional ByVal lngMarshalType As Integer = 0
Output: ADODB.Recordset
fValGroup
Method
fValGroupList
Method
340
API Call
Methods/
Properties/
Object
Reference
Description
fGetAppID
Method
fGetLanguageCode
Method
fGetTopLevelDirectory
Method
fOptionLIstForKey
Method
Returns a recordset containing one record with values for the specified option name.
Inputs: ByVal strOptionName As String, Optional ByVal blnReadOnly As Boolean = False,
Optional ByVal blnSQLOnly As Boolean = False, Optional ByVal lngMarshalType As Integer =
0, Optional ByVal blnTranslateCaptions As Boolean = False
Output: ADODB.Recordset
API Call
Methods/
Properties/
Object
Reference
Description
fGlobalOptionExists
Method
fGlobalOptionGet
Method
Retrieve a global system option as a string containing the current value of the option.
Inputs: ByVal strOptionName As String
Output: String
341
API Call
Methods/
Properties/
Object
Reference
Description
mLog
Method
mLogError
Method
Write an error to a user runtime error log. The log is located in the outbox directory of the
application under the file name "LoadID_FDM_API.log".
Inputs: ByVal lngErrorCode As Integer, ByVal strErrorDesc As String, ByVal strErrorSource As String
Output: None
342
API Call
Methods/
Properties/
Object
Reference
Description
fProcessStatus
Method
Retrieve the current workflow process status for the specified POV values. The process status is returned
as a COM object of the type "objProcessStatus". The best way to determine the current status is to check
the lngStatus property of the return object, which contains a value that can be checked against the
enumeration "enmProcessState".
Inputs: ByVal strLoc As String, ByVal strCat As String, ByVal strPer As String, ByVal strRuleID As String
Output: objProcessStatus object
objProcessStatus Properties:
l
strLoc
strCat
strPer
blnImp
strImp
blnTBVal
strTBVal
blnExp
strExp
blnEntLoad
strEntLoad
blnEntVal
strEntVal
lngStatus
dteLastActive
blnCert
strCert
blnAsses
strAsses
blnChildDone
strChildDone
blnUD1
strUD1
blnUD2
strUD2
blnUD3
strUD3
343
API Call
Methods/
Properties/
Object
Reference
Description
blnUD4
strUD4
blnValDirty
blnWCDirty
blnLogicDirty
intLockState
API Call
Methods/
Properties/
Object
References
Description
fCategoryKey
Method
Return the numerical category key for the specified category name.
Inputs: ByVal strCat As String
Output: Integer
fCategoryName
Method
Return the text name of a category for the specified category key.
Inputs: ByVal lngCatKey As Integer
Output: String
fCheckLocParent
Method
Check when the requested location is assigned as the MAPPING parent to any other location.
Inputs: ByVal strLoc As String
Output: Boolean
344
API Call
Methods/
Properties/
Object
References
Description
fCheckLocProf
Method
Return all behavior attributes for the specified location as a COM object of type objLocProfile. This
object also contains the key information of the location and the data segment assignment.
Inputs: ByVal strLoc As String
Output: objLocProfile
objLocProfile Properties:
fGetLocationName
Method
blnAdapterImport
blnChild
blnExists
blnScriptImport
blnSeq
lngControlsType
lngLocKey
lngParentLocKey
lngRedFlagLevel
lngSegKey
lngType
strAdaptor
strCLogicGrp
strControlsApprover
strControlsApproverProxy
strControlsGrp1
strControlsGrp2
strControlsParent
strCurrency
strDataValue
strImportGrp
strIntgConfig1
strIntgConfig2
strIntgConfig3
strIntgConfig4
strLogicGrp
strNotes
strParent
strValEntityGrp
strValRuleGrp
345
API Call
Methods/
Properties/
Object
References
Description
fPeriodKey
Method
Return attributes associated with the specified period value as a COM object of type "objPeriod".
Use this procedure to return the prior period of a location by setting the optional parameter
"blnPriorPer" to true. By default the procedure returns the target period associated with the 'M' or
'Monthly' frequency, but the optional parameter "strFreq" can be used to retrieve a target value
associated with a different frequency.
Inputs: ByVal strPer As String, Optional ByVal blnPriorPer As Boolean = False, Optional ByVal strFreq
As String = ""
Output: objPeriod
objPeriod Properties:
l
dblSerialKey
dteDateKey
strDateKey
strSerialKey
strTarget
strTargetYear
API Call
Methods/Properties/Object Reference
Description
AppID
Property
bstMaintenanceMgr
Object Reference
bstSQLMgr
Object Reference
CatKey
Property
CatName
Property
DataValue
Property
dstConnection
Object Reference
dstDataAccess
Object Reference
dstDataManipulation
Object Reference
dstDBTools
Object Reference
dstSQL
Object Reference
346
API Call
Methods/Properties/Object Reference
Description
dstUtilities
Object Reference
EndPeriodKey
Property
ExportFlag
Property
ExportMode
Property
FileDir
Property
FileName
Property
Returns a string containing the name of the file that was imported.
GstrDateMask
Property
ImportFlag
Property
ImportFormat
Property
Returns the Import Format used for the Load ID being processed.
ImportMode
Property
LoadID
Property
LocKey
Property
Returns the Location Key for the Location being processed for the
LoadID.
LocName
Property
Returns the Location Name for the location being processed for the
LoadID.
MultiPeriodLoad
Property
Returns True or False. This property is True if multiple periods are being
processed. Otherwise, returns False.
PeriodKey
Property
RuleID
Property
RuleName
Property
Returns the Rule Name for the Data Rule being processed.
SourceName
Property
SourceType
Property
TargetAppDB
Property
Returns "NA" for HFM. If the target application type is HPL then this
property returns the PLAN_TYPE. If the target application type is
ESSBASE this property returns the ESSBASE_DB_NAME.
TargetAppName
Property
347
348
'Send an email
SendEmail("[email protected]", "[email protected]", "Subject",
"Import was successful"
End If
End If
'************************************************************************************
'************************************************************************************
'Destroy objects
'************************************************************************************
objFDMAPI.Dispose
Set objFDMAPI = Nothing
'************************************************************************************
Sub SendEmail(strFromAddress, strToAddress, strSubject,strEmailMsgLine)
'Declare local variables
Dim strFromAddress
Dim strToAddress
Dim strSubject
Dim strEmailMsgLine
Dim objMsg
Dim objConfig
Dim intSendUsing
Dim strSMTPServer
Dim intSendPort
'Initialize Mail Server variables
'SMTP server name
strSMTPServer = "YourMailServer"
'CdoSendUsing enumeration-1=use smtp on local machine, 2=use smtp over network
intSendUsing = 2
'SMTP port on server
intSMTPPort = 25
'Create CDO configuration object
Set objConfig = CreateObject("CDO.Configuration")
'Set Config object settings
With objConfig.Fields
.Item("http://schemas.microsoft.com/cdo/configuration/sendusing") =
intSendUsing
.Item("http://schemas.microsoft.com/cdo/configuration/smtpserver") =
strSMTPServer
.Item("http://schemas.microsoft.com/cdo/configuration/smtpserverport")=
intSMTPPort
.Item("http://schemas.microsoft.com/cdo/configuration/smtpconnectiontimeout") = 10
.Update
End With
'Create CDO message object
Set objMsg = CreateObject("CDO.Message")
'Assign config object to configuration property of message object
Set objMsg.Configuration = objConfig
'Set Message object settings and send mail
With objMsg
.To = strToAddress
.From = strFromAddress
.Subject = strSubject
.TextBody = strEmailMsgLine
349
.Send
End With
'Destroy message objects
Set objMsg = Nothing
Set objConfig = Nothing
End Sub
350
351
'*********************************************************************************
***
'************************************************************************************
'Destroy objects
'************************************************************************************
objFDMAPI.Dispose
Set objFDMAPI = Nothing
WScript.Echo "FDMEE VB API destroyed."
'************************************************************************************
352
353
354
FDMEE Reports
9
In This Chapter
FDMEE provides prebuilt reporting tools that capture business-critical operations and revenuegenerating activities within your organization. These reports provide key information on how
metadata and data are integrated from the source to the target.
The FDMEE reporting framework represents a unified solution that incorporates source and
target data, templates, and user-defined SQL queries. Templates, created in Oracle Business
Intelligence Publisher, consume data in XML format and generate reports dynamically. You can
add SQL queries to extract data from tables, or couple them with the report parameters to extend
the definition of a standard report.
The FDMEE reporting framework has the following components:
FDMEE reports can be generated as PDF, Excel, Word, or HTML output.
l
Query Definition
Report Group
Report Definition
Report Execution
FDMEE Reports
The standard FDMEE report groups are described below. For information on the subcategories
of each report, see FDMEE Detail Reports on page 365.
355
Table 67
Report Group
Description
Audit Reports
An audit report displays all transactions for all locations that comprise the balance of a target account. The data returned
in these reports depends on the location security assigned to the user.
The subcategories of the Audit Reports:
Base Trial
Balance
Reports
356
Account Chase
The base Trial Balance reports represent account balance source data in a General Ledger system. You use a base Trial
Balance report to validate and compare balances as data is loaded from the source system to the target applications.
The subcategories of base Trial Balance reports:
l
Report Group
Description
Check
Reports
Check reports provide information on the issues encountered when data load rules are run. Check reports return target
system values that include aggregation or calculations from the target system.
The subcategories of Check reports:
Listing
Reports
Location
Analysis
Reports
Process
Monitor
Reports
Check ReportDisplays the results of the validation rules for the current location (pass or fail status).
Check Report Period Range (Cat, Start per, End per)Displays the results of the validation rules for a category and
selected periods.
Check Report by Validation Entity SequenceDisplays the results of the validation rules for the current location (pass
or fail status); sorted by the sequence defined in the validation entity group.
Check Report with WarningsDisplays the results of the validation rules for the current location. Warnings are recorded
in validation rules and shown if warning criteria are met. This report does not show rules that passed the validation.
Listing reports summarize metadata and settings (such as the import format, or check rule) by the current location.
The subcategories of Listing reports:
l
Location Listing
Location Analysis reports provide dimension mapping and system log information by the current location.
The subcategories of Location Analysis reports:
l
A Process Monitor report displays, for the current report, a list of locations and their positions within the data conversion
process. You can use the process monitor report to monitor the status of the closing process. The report is time-stamped.
Therefore, it can be used to determine to which locations and at which time data was loaded.
The subcategories of Process Monitor reports:
Variance
Reports
A Variance report displays source/trial balance accounts for one target account, showing over two periods or categories.
The subcategories of Variance reports:
l
357
The parameter SQL query enables you to run a query against the parameters in the report
definition. For example, use the query to select the Location, Period, Category, or Account.
For information on the tables and joins you can use to build your SQL queries, see TDATASEG
Table Reference on page 419 andTLOGPROCESS Table Reference on page 423 in Appendix
G. The TDATASEG table is used to store the data loaded by the user, the transformation between
the source dimension members, and the results of the mapping process. The TLOGPROCESS
table is used to store the workflow process status for a location, category, and period.
You can save a query definition as an XML file, which, in turn, you can use to create custom
templates using BI Publisher or the BI Publisher desktop addin for Microsoft Word.
Oracle recommends that you assign a name that corresponds to the report definition in
which the SQL is embedded.
In Select Clause, specify the SQL Select clause used to query the database and return the data that
corresponds to your selected criteria.
In Where Clause, specify the SQL Where clause used to restrict the data that is returned to only the
specific criteria that you specify.
The ORDER BY clause sorts the records in the result set. The ORDER BY clause can be used
only in SQL SELECT statements.
The GROUP BY clause fetches data across multiple records and returns the results grouped
by one or more columns.
If the query definition is validated, FDMEE returns the message: Query validation
successful.
If the query definition is not validated, FDMEE indicates that an error was found in the SQL.
You must fix the error before validating the query again.
Click Save.
Optional: To save the query definition to an XML file, click Generate XML.
358
In the blank Name field, enter the title of the report group.
In Sequence, enter a numeric value that identifies the display order of the report group on the Report
Definition screen.
For example, to display the Check Report group before the Location Listing group, enter
1 in the Sequence field for the Check Report group, and 2 for the Location Listing group.
Click Save.
359
In the detail grid, in Name, enter the name of the report definition.
In Group, select the report group name associated with the definition.
Report groups are created on the Report Group tab. See Adding Report Groups on page
359.
In Query, select the name of the query definition to associate with the report definition.
Query definitions are defined in the Query Definition option. See Working with Query
Definitions on page 357.
In Template, select the RTF template to associate with the report definition.
FDMEE report templates are saved with a Rich Text Format (RTF) file type. The RTF file
type is a specification used by common word processing applications, such as Microsoft
Word. The templates available to the FDMEE report are created in BI Publisher. See the
Report Designer's Guide for Oracle Business Intelligence Publisher. To download the Oracle
BI Publisher Desktop for Microsoft Office, see http://www.oracle.com/technetwork/
middleware/bi-publisher/downloads/index.html.
Note: You can view report descriptions and parameters in the language selected for your
user interface. Language templates are available at: \Oracle\Middleware
\EPMSystem11R1\products\FinancialDataQuality\templates for you to
360
Click Save.
From the summary grid, select the name of the report definition to which to add parameters.
In Parameter Name, enter the POV category to which the parameter belongs.
For example, enter POVLOC, for the POV location, POVPeriod for the POV period,
POVCAT for POV category, and POVTARGET for the target category.
Available types:
l
POVPrompts for the POV location, period, category or rule. The POV values default
from the users POV when they run the report parameter.
QueryThe Query type enables you to create a query that populates a list of values that
a user can select from when running the report. The parameter name entered by the
user must match a parameter used in the assigned query. For example, if the parameter
name is California, a corresponding parameter in the query must be named California.
The name in the query must have a ~ character as a prefix so that the system can parse
the query correctly.
StaticA Static type Indicates that the parameter is a constant or a predefined value,
and the parameter value is supplied by the user. When the parameter is supplied and
the report is executed, the query uses this parameter as part of the Select statement.
Title (indicates the header part of column title)
In Display Name, enter the name to display for the parameter on the Generate Report screen.
In Parameter Value, enter the value for the Static parameter type. For example, if you have an aging
report for 30 days, enter 30 in this field.
In Sequence, enter the display order of the parameter on the Generate Report screen.
In Query, specify the query definition that provides a list of values for the parameter. For example, to
show a list of data rules for the user to select in the Generate Report screen, specify the query definition
to define these queries.
Click Save.
To copy a report:
1
361
The copied report is added to the list of reports. The name of the report takes the original
report name appended with _copy.
362
e. In Where Clause, specify the SQL Where clause used to restrict the data that is returned
to only the specific criteria that you specify.
f.
Running Reports
To run reports:
1
To filter the display listing by a report name within a report group, enter the name of the
report in the blank entry line above the Name field and press Enter. For example, to view
only reports beginning with Account, enter Account and press Enter.
To filter the display listing by a base query name within a report group, enter the query name
in the blank entry line above Query.
Click Execute.
HTML
EXCEL (.XLS)
c. From Execution Mode, select the online method of running the report.
The online method processes the report immediately.
d. Optional: To create a report batch script that generates a report when the scripts are
executed, click Create Report Script.
e. Click OK.
To filter the display listing by a report name within a report group, enter the name of the
report in the blank entry line above the Name field and press Enter. For example, to view
only reports beginning with Account, enter Account and press Enter.
To filter the display listing by a base query name within a report group, enter the query name
in the blank entry line above Query.
Click OK.
A Report Batch Script window is displayed showing the parameters of the reports script.
364
Copy the script that FDMEE generates, and on a Window command window or UNIX shell, paste the
script, and then run it.
Note: When passing program arguments for a batch file execution, Jython removes double
quotes () unless arguments have a leading space in them. Jython uses double quotes
for escaping. To avoid conflicts, add a leading space in the argument. For example,
instead of passing Period=Mar-2003, pass Period=Mar-2003.
Note: You can use a file with an encrypted password when executing reports from batch
report scripts, for example, runreport.bat <username><password> file
Audit Reports
An audit report displays all transactions for all locations that compose the balance of a target
account. The data returned in this report depends on the location security assigned to the user.
Runs for
All FDMEE locations
Parameters
Target account, Period, Category
Query
Account Chase Wildcard
Template
Account Chase WildCard.rtf
365
Runs for
All FDMEE locations
Parameters
Target account, Period, Category
Query
Account Chase Freeform
Template
Account Chase Free Form.rtf
Runs for
Current FDMEE location
Parameters
Period, Category
Query
Intersection Drill Down
Template
Intersection Drill Down.rtf
366
Check Reports
Check reports provide information on the issues encountered when data load rules are run. Note
that Check reports return target system values that include aggregation or calculations from the
target system.
Note the following when using check reports:
l
When the check report is run and opened from the Workbench, it is not saved to the FDMEE
folder on the server.
When you run a data rule, a check rule report is not generated automatically. In this case,
run the data rule before executing the check report.
If you run the report in offline mode, the report is saved to the outbox on the FDMEE
server.
To run a data rule and report in batch mode, run the data load rule from a BAT file, and
then the report from a BAT file. In this case, you can put each in the same BAT file, or call
each of them from a BAT file.
Check Report
Shows the results of the validation rules for the current location (indicates pass or fail status).
Runs for
Current FDMEE location
Parameters
Period, Location and Category
Query
Check Report
Template
Check Report.rtf
Runs for
Current FDMEE location
367
Parameters
Category, Start Period, End Period
Query
Check Report Within Period Query
Template
Check Report With Period Range.rtf
Runs for
Current FDMEE location
Parameters
None
Query
Check Report With Warning
Template
Check Report With Warning.rtf
Runs for
Current FDMEE location
Parameters
None
368
Query
Check Report By Validation Entity
Template
Check Report By Validation Entity Sequence.rtf
Trial Balance reports has access to the location associated with the report. (See Defining
Location Security on page 51).
Runs for
Current FDMEE location
Parameters
Category, Period
Query
Current Trial Balance With Location with Targets
Template
TB Location With Targets.rtf
369
Runs for
Current FDMEE location
Parameters
Category, Period
Query
TB Location With Query
Template
TB Location with Rules.rtf
Runs for
Current FDMEE location
Parameters
Category, Period
Query
Trial Balance Current Location with Targets
Template
TB/(All Dimensions with Targets) by Target Entity Account.rtf
Runs for
Current FDMEE location
370
Parameters
Category, Period
Query
Trial Balance Location All Dimension.
Template
TB with Transaction Currency.rtf
Runs for
Current FDMEE location
Parameters
Category, Period
Query
Trial Balance Current Location Sorted By Target Account
Template
TB With Target Account.rtf
Runs for
Current FDMEE location
Parameters
Category, Period
371
Query
Trial Balance Base Transaction Currency
Template
Base Trial Balance (All Dimensions with Targets).rtf
Runs for
Current FDMEE location
Parameters
Category, Period
Query
Trial Balance Converted by Target Entity/Account Query
Template
TB Converted Current Location by Target Entity Account.rtf
Listing Reports
Listing reports summarize metadata and settings (such as the import format, or check rule) by
the current location.
Runs for
N/A
Parameters
None
372
Query
Import Format By Location
Template
Import Format by Location.rtf
Location Listing
Shows a list of all mapping rules for a selected period, category, or dimension.
Runs for
Current FDMEE location
Parameters
Any FDMEE Dimension, Period, Category
Query
Location Listing Query
Template
Location Listing.rtf
Location Analysis
Location Analysis reports provide dimension mapping by the current location.
Runs for
Current FDMEE location
Parameters
Current FDMEE dimension
373
Query
Dimension Map
Template
Dimension Map.rtf
Runs for
Current FDMEE location
Parameters
Any FDMEE Dimension, Period, Category
Query
Dimension Map for POV
Template
Dimension Map.rtf
Runs for
All FDMEE locations
374
Parameters
Category, Period
Query
Process Monitor
Template
Process Monitor.rtf
Runs for
All FDMEE locations
Parameters
Category, Period
Query
ProcessMonitorwithLock
Template
ProcessMonitorwithlock.rtf
Runs for
All FDMEE locations, period range
Parameters
Category, Start Period, End Period
375
Query
PMPeriodRange
Template
PMPeriodRange.rtf
Runs for
All FDMEE categories and locations
Parameters
Period
Query
Process Monitor All Categories
Template
Process Monitor All Category.rtf
Variance Reports
The Variance reports display source and trial balance accounts for one target account, showing
data over two periods or categories.
Runs for
All FDMEE locations
Parameters
Target Account, Category 1, Period 1, Category 2, Period 2.
376
Query
Account Chase Variance
Template
Account Chase Variance.rtf
Runs for
Current FDMEE location
Parameters
Category 1, Period 1, Category 2, Period 2
Query
Trial Balance Variance
Template
TB Variance.rtf
377
378
A
In This Appendix
executeDataRule
The executeDataRule method executes a data rule after validating the parameters passed with
the rule. If the parameter is invalid, error messages are displayed.
Parameter Name
String pUserName
String pPassword
String pSSOToken
Valid Values
Comments
AIF_ERR_00001:Invalid Token
379
Parameter Name
Valid Values
String pImportFromSource
Y/N
String pExportToTarget
Y/N
String pRuleName
Comments
String pExecutionMode
INCREMENTAL/SNAPSHOT
String pLoadExchangeRateFlag
Y/N
String pStartPeriodName
String pEndPeriodName
String pSyncMode
TRUE/FALSE
executeMetaDataRule
The executeMetaDataRule method executes a metadata rule after validating the locationName
parameter. If the parameter is invalid, error messages are displayed.
Parameter Name
Valid Values
Comments
String pUserName
AIF_COMMON_ERR_00001:Invalid token.
String pPassword
String pSSOToken
String locationName
String pSyncMode
380
TRUE/FALSE
getDataRuleNames
The getDataRuleNames method retrieves a list of data rule names for the location. If no location
is passed, an empty array is returned.
Parameter Name
Valid Values
Comments
String pUserName
String pPassword
AIF_COMMON_ERR_00001:Invalid token.
String pSSOToken
String locationName
getLocationNames
Provides a list of locations for the executeMetaDataRule web service.
Parameter Name
Valid Values
String pUserName
String pPassword
AIF_COMMON_ERR_00001:Invalid token.
Comments
String pSSOToken
getPeriodNames
Provides a list of period names for the pStartPeriodName and pEndperiodName parameters of
the executeDataRule service.
Parameter Name
Valid Values
String pUserName
String pPassword
AIF_COMMON_ERR_00001:Invalid token.
Comments
String pSSOToken
lockPOV
Returns true if this POV is locked, otherwise returns false for the RuleService web services.
381
Parameter Name
Valid Values
String pLocationName
String pPeriodName
Comments
String pCategoryName
unlockPOV
Returns true if this POV is unlocked, otherwise returns false for the RuleService web services.
Parameter Name
Valid Values
String pLocationName
String pPeriodName
String pCategoryName
382
Comments
B
In This Appendix
This section lists the source system tables used by FDMEE. FDMEE reads all tables listed and
writes to GL_BUDGET_INTERFACE and GL_TRACK_DELTA_BALANCES.
It also describes how to create synonyms for E-Business Suite tables.
Table/View Name
Schema
Object Type
Privilege
FND_FLEX_VALIDATION_
QUALIFIERS
APPLSYS
Table
Read only
FND_FLEX_VALIDATION_TABLES
APPLSYS
Table
Read only
FND_FLEX_VALUES
APPLSYS
View
Read only
FND_FLEX_VALUES_TL
APPLSYS
View
Read only
FND_FLEX_VALUE_CHILDREN_V
APPS
View
Read only
FND_FLEX_VALUE_NORM_
HIERARCHY
APPLSYS
Table
Read only
FND_FLEX_VALUE_SETS
APPLSYS
Table
Read only
FND_FORM_FUNCTIONS
APPLSYS
Table
Read only
Comments
383
Table/View Name
Schema
Object Type
Privilege
FND_ID_FLEXS
APPLSYS
Table
Read only
FND_ID_FLEX_SEGMENTS
APPLSYS
Table
Read only
FND_ID_FLEX_SEGMENTS_TL
APPLSYS
Table
Read only
FND_ID_FLEX_STRUCTURES
APPLSYS
Table
Read only
FND_ID_FLEX_STRUCTURES_TL
APPLSYS
Table
Read only
FND_KF_LABELED_SEGMENTS
FUSION
Table
Read-only
FND_KF_SEGMENT_LABELS_B
FUSION
Table
Read-only
FND_LANGUAGES
APPLSYS
Table
Read only
FND_MESSAGES_TL
FUSION
Table
Read-only
FND_NEW_MESSAGES
APPLSYS
Table
Read only
FND_NUMBER
APPLSYS
PL/SQL Package
Execute
FND_RESPONSIBILITY
APPLSYS
Table
Read only
FND_RESPONSIBILITY_TL
APPLSYS
Table
Read only
FND_SEGMENT_ATTRIBUTE_
VALUES
APPLSYS
Table
Read only
GL_BALANCES
GL
Table
Read only
GL_BALANCES_DELTA
GL
Table
Read only
GL_BUDGETS
GL
Table
Read only
GL_BUDGET_ENTITIES
GL
Table
Read only
GL_BUDGET_INTERFACE
GL
Table
GL_BUDGET_VERSIONS
GL
Table
Read only
GL_CODE_COMBINATIONS
GL
Table
Read only
GL_CODE_COMBINATIONS_KFV
APPS
View
Read only
GL_DAILY_BALANCES
GL
Table
Read only
GL_DAILY_CONVERSION_TYPES
GL
Table
Read only
GL_DAILY_CONVERSION_TYPES_V
APPS
View
Read only
GL_DAILY_RATES
GL
Table
Read only
384
Comments
Table/View Name
Schema
Object Type
Privilege
GL_ENCUMBRANCE_TYPES
GL
Table
Read only
GL_INTERFACE
GL
Table
Read/Write
GL_JE_CATEGORIES
GL
Table
Read only
GL_JE_CATEGORIES_TL
GL
Table
Read only
GL_JE_SOURCES_TL
GL
Table
Read only
Table
Read only
GL_LEDGERS
Comments
GL_PERIODS
GL
Table
Read only
GL_PERIOD_SETS
GL
Table
Read only
GL_PERIOD_STATUSES
GL
Table
Read only
GL_PERIOD_TYPES
GL
Table
Read only
GL_PERIOD_TYPES_V
APPS
View
Read only
GL_SETS_OF_BOOKS
GL/APPS
View
Read only
GL_STAT_ACCOUNT_UOM
GL
Table
Read only
GL_TRACK_DELTA_BALANCES
GL
Table
Read/Write
Table/View Name
Table/View Name
Table/View Name
Table/View Name
PS_AFFILIATE_LANG
PS_CHARTFIELD1_TBL
PS_LEDGER
PSDBFLDLABL
PS_AFFILIATE_VW
PS_CHARTFIELD2_TBL
PS_LEDGER_BUDG
PSDBFLDLABLLANG
PS_AFFINTRA1_LANG
PS_CHARTFIELD3_TBL
PS_LOCATION_TBL
PSKEYDEFN
PS_AFFINTRA1_VW
PS_CLASS_CF_LANG
PS_NAMES
PSOPTIONS
PS_AFFINTRA2_LANG
PS_CLASS_CF_TBL
PS_OPER_UNIT_LANG
PSRECDEFN
PS_AFFINTRA2_VW
PS_DEPT_TBL
PS_OPER_UNIT_TBL
PSRECFIELD
PS_ALTACCT_LANG
PS_DEPT_TBL_LANG
PS_PAYGROUP_TBL
PSTREEDEFN
385
Table/View Name
Table/View Name
Table/View Name
Table/View Name
PS_ALTACCT_TBL
PS_EARNINGS_TBL
PS_PC_BU_GL_VW
PSTREEDEFNLANG
PS_BD_SCENARIO_TBL
PS_FS_CF_TEMPLATE
PS_PC_INT_TMPL_GL
PSTREELEAF
PS_BOOK_CODE_TBL
PS_FS_FLD_PROMPT
PS_POSITION_DATA
PSTREENODE
PS_BU_BOOK_TBL
PS_FUND_LANG
PS_PROD_TBL_LANG
PSTREESTRCT
PS_BU_LED_GRP_TBL
PS_FUND_TBL
PS_PRODUCT_TBL
PSXLATITEM
PS_BUD_REF_LANG
PS_GL_ACCOUNT_LANG
PS_PROGRAM_LANG
PSXLATITEMLANG
PS_BUD_REF_TBL
PS_GL_ACCOUNT_TBL
PS_PROGRAM_TBL
PS_BUS_UNIT_LANG
PS_PROJECT
PS_BUS_UNIT_TBL_FS
PS_PROJECT_TBL
PS_BUS_UNIT_TBL_GL
PS_REC_GROUP_REC
PS_BUS_UNIT_TBL_HR
PS_JOB
PS_REC_GROUP_TBL
PS_CAL_ADJP_TBL
PS_JOBCODE_TBL
PS_RT_DFLT_VW
PS_CAL_DEFN_TBL
PS_LED_DEFN_LANG
PS_RT_INDEX_TBL
PS_CAL_DETP_TBL
PS_LED_DEFN_TBL
PS_RT_TYPE_TBL
PS_CAL_SUMP_TBL
PS_LED_GRP_LANG
PS_SET_CNTRL_REC
PS_CF1_LANG
PS_LED_GRP_LED_TBL
PS_SET_CNTRL_TBL
PS_CF2_LANG
PS_LED_GRP_TBL
PS_SET_CNTRL_TREE
PS_CF3_LANG
PS_LED_TMPLT_TBL
PS_SETID_TBL
Table/View Name
Table/View Name
Table/View Name
PS_ACCT_CD_TBL
PS_CHARTFIELD3_TBL
PS_JOB_EARNS_DIST
PS_SAL_PLAN_TBL
PS_AFFILIATE_VW
PS_CLASS_CF_TBL
PS_JOBCODE_TBL
PS_SAL_STEP_TBL
PS_ALTACCT_TBL
PS_DEPT_BUDGET_ERN
PS_LOCATION_TBL
PS_SET_CNTRL_REC
386
Table/View Name
Table/View Name
Table/View Name
Table/View Name
PS_BENEF_PLAN_TBL
PS_DEPT_CF_TBL
PS_NAMES
PS_UNION_TBL
PS_BP_JOB
PS_DEPT_TBL
PS_OPER_UNIT_TBL
PSOPTIONS
PS_BUD_REF_TBL
PS_EARNINGS_TBL
PS_PAYGROUP_TBL
PSRECFIELD
PS_BUS_UNIT_TBL_FS
PS_FREQUENCY_TBL
PS_POSITION_DATA
PSXLATITEM
PS_BUS_UNIT_TBL_GL
PS_FUND_TBL
PS_PRODUCT_TBL
PSXLATITEMLANG
PS_BUS_UNIT_TBL_HR
PS_GL_ACCOUNT_TBL
PS_PROGRAM_TBL
PS_CHARTFIELD1_TBL
PS_GL_ACCOUNT_VW
PS_PROJECT_TBL
PS_CHARTFIELD2_TBL
PS_JOB
PS_SAL_GRADE_TBL
387
Note: Synonyms are required for a PeopleSoft setup since PeopleSoft administrators typically
Create synonyms for the E-Business Suite tables listed in this appendix.
GL_Interface
GL_Budget_Interface
GL_Track_Delta_Balances
In ODI Topology for EBS_Data_Server, you can use the synonym for both the user and the
schema.
388
Prebuilt integrations to an Enterprise Resource Planning (ERP) source system in FDMEE use a
basic filter for data extraction, and assume that appropriate security has been defined to enable
access by FDMEE. In some environments, direct access to the source systems tables is prohibited
because of system policies, or you want to define a source system filter that is more detailed than
what is provided in the FDMEE user interface.
For example, in the Account Reconciliation Manager (ARM) you want to extract balance sheet
accounts or active accounts only from the source system. To do this, create an alternate schema
in the source system. This method provides a desired level of security, a different source system
filter, or both.
To create an alternate hierarchy for E-Business Suite and Peoplesoft (PSFT) systems:
1
Grant SELECT or SELECT/INSERT access to the list of source tables used by FDMEE to the new schema.
Refer to the source table list provided in Appendix B, Source System Tables Used by
FDMEE.
For E-Business Suite systems, create a new view named GL_CODE_COMBINATIONS, which includes
the desired source filter.
Create synonyms for all remaining source tables that FDMEE references from the source system in the
new schema.
Update Oracle Data Integrator (ODI) to use the new schema in the physical schema for the related
data server.
For example, the view created on the EBS GL_CODE_COMBINATIONS table may look
like:
CREATE VIEW GL_COMBINATIONS (SEGMENT1, SEGMENT2,....)
SELECT SEGMENT1, SEGMENT2,..
FROM APPS.GL_CODE_COMBINATIONS
WHERE ADD FILTERS
Any views created in the new schema or synonyms must use the exact same name as specified
in Appendix B, Source System Tables Used by FDMEE. Because the table and view names are
389
the same as the core schema, FDMEE can access the updated contents with a change to the
schema specification in ODI.
For SAP or JDE source systems, change the filter definition in the adapter rather than creating
an alternate schema.
Before making any changes, it is recommended that you contact Oracle support to review the
process to ensure a smooth update to the system.
390
Staging Tables
D
In This Appendix
Description
TDATASEG_T
Temporary data table used for transforming data from source to target in a data rule execution. To ensure read
consistency, data is extracted from the corresponding staging table (for example, AIF_EBS_GL_BALANCES_STG, AIF_
EBS_GL_DAILY_BAL_STG, or AIF_PS_LEDGER) and copied to TDATASEG_T (partitioned by LOADID), which is then
used for transforming source data to target data based on the data mappings specified in TDATAMAP_T.
Description
TDATASEG
Audit table describing the data transformations in a data rule execution. Only in a successful data rule execution
data transformations stored in TDATASEG_T be copied over to TDATASEG.
391
Description
AIF_HS_BALANCES
Interface view used for exporting data to a target application in a data rule execution. This view queries the
TDATASEG_T table directly by summarizing the target amounts across the unique target dimension member
combinations.
AIF_EBS_GL_INTERFACE_V
Interface view used for exporting data back to the Fusion and E-Business Suite general ledger system in a
data load to write back rule execution. This view queries the TDATASEG table directly by summarizing the
target amounts across the unique target segment value combinations.
AIF_PS_GL_INTERFACE_V
Interface view used for exporting data back to the PeopleSoft Enterprise Financial Management system in
a data load rule to write back rule execution. This view queries the TDATASEG table directly by summarizing
the target amounts across the unique target ChartField value combinations.
l
l
The following sections describe the columns in each PeopleSoft Human Capital Management
staging table used by FDMEE.
PS90HCM
Table 68
AIF_PS_POSITION_DATA_STG Table
Column Name
Column Description
DESCR
Position Description
Table 69
AIF_PS_JOBCODE_TBL_STG Table
Column Name
Column Description
COMP_FREQUENCY
Compensation Frequency
DESCR
Description
EFFDT
Effective Date
EFF_STATUS
Status
STD_HOURS
Standard Hours
392
Table 70
AIF_PS_JOB_STG Table
Column Name
Column Description
ABSENCE_SYSTEM_CD
Absence System
ACCDNT_CD_FRA
ACCT_CD
Account Code
ADDS_TO_FTE_ACTUAL
ANNL_BENEF_BASE_RT
APPT_TYPE
Appointment Type
ASGN_END_DT
ASGN_START_DT
AUTO_END_FLG
BARG_UNIT
Bargaining Unit
BAS_ACTION
BAS_GROUP_ID
BENEFIT_SYSTEM
Benefits System
BORDER_WALKER
CHANGE_AMT
Change Amount
CHANGE_PCT
Change Percent
CLASS_INDC
Classified/Unclassified Indicator
COBRA_ACTION
COBRA Action
COMPANY
Company
COMPRATE
Compensation Rate
COMP_FREQUENCY
Compensation Frequency
CONTRACT_NUM
Contract Number
CTG_RATE
Category Rate
CURRENCY_CD1
Currency Code 1
CUR_RT_TYPE
DAILY_RT
Daily Rate
DEPT_ENTRY_DT
DIRECTLY_TIPPED
Directly Tipped
393
Column Name
Column Description
EARNS_DIST_TYPE
EEO_CLASS
EEO Class
ELIG_CONFIG1
ELIG_CONFIG2
ELIG_CONFIG3
ELIG_CONFIG4
ELIG_CONFIG5
ELIG_CONFIG6
ELIG_CONFIG7
ELIG_CONFIG8
ELIG_CONFIG9
EMPL_CTG
Employee Category
EMPL_CTG_L1
Employee Subcategory
EMPL_CTG_L2
Employee Subcategory 2
ENCUMB_OVERRIDE
Encumbrance Override
ENTRY_DATE
Entry Date
ESTABID
Establishment ID
EXEMPT_HOURS_MONTH
EXEMPT_JOB_LBR
Exempted
EXPECTED_END_DATE
EXPECTED_RETURN_DT
FLSA_STATUS
FLSA Status
FORCE_PUBLISH
Force Publish
FUNCTION_CD
Function Code
GL_PAY_TYPE
GL Pay type
GP_ASOF_DT_EXG_RT
Use Rate As Of
GP_DFLT_CURRTTYP
GP_DFLT_ELIG_GRP
394
Column Name
Column Description
GP_DFLT_EXRTDT
GP_ELIG_GRP
Eligibility Group
GP_PAYGROUP
Pay Group
GRADE_ENTRY_DT
HIRE_DT
Hire Date
HOLIDAY_SCHEDULE
Holiday Schedule
HOURLY_RT
Hourly Rate
HOURLY_RT_FRA
HR_STATUS
HR Status
INTERCTR_WRKS_CNCL
JOB_DATA_SRC_CD
JOB_ENTRY_DT
JOB_INDICATOR
Job Indicator
LABOR_AGREEMENT
Labor Agreement
LABOR_FACILITY_ID
Labor Facility ID
LABOR_TYPE_GER
LASTUPDDTTM
LASTUPDOPRID
LAST_DATE_WORKED
LAST_HIRE_DT
LAYOFF_EXEMPT_FLAG
LAYOFF_EXEMPT_RSN
LBR_FAC_ENTRY_DT
LDW_OVR
LST_ASGN_START_DT
LUMP_SUM_PAY
MAIN_APPT_NUM_JPN
MATRICULA_NBR
Matricula Number
395
Column Name
Column Description
MONTHLY_RT
Monthly Rate
OFFICER_CD
Officer Code
PAID_FTE
Paid FTE
PAID_HOURS
Paid Hours
PAID_HRS_FREQUENCY
PAYGROUP
Pay Group
PAY_SYSTEM_FLG
PAY_UNION_FEE
PERFORM_GROUP_GER
PER_ORG
Organizational Relationship
POI_TYPE
POSITION_ENTRY_DT
POSITION_OVERRIDE
Position Override
POSN_CHANGE_RECORD
PRORATE_CNT_AMT
REG_REGION
Regulatory Region
REPORTS_TO
Reports To
SETID_DEPT
SetID Department
SETID_JOBCODE
SETID_LBR_AGRMNT
SETID_LOCATION
SetID Location
SETID_SALARY
SetID Salary
SETID_SUPV_LVL
SHIFT
Shift
SHIFT_FACTOR
Shift Factor
SHIFT_RT
Shift Rate
SOC_SEC_RISK_CODE
SPK_COMM_ID_GER
Spokesman Committee ID
396
Column Name
Column Description
STD_HRS_FREQUENCY
STEP_ENTRY_DT
SUPERVISOR_ID
Supervisor ID
SUPV_LVL_ID
Supervisor Level ID
TARIFF_AREA_GER
TARIFF_GER
Tariff Germany
TAX_LOCATION_CD
TERMINATION_DT
Termination Date
UNION_FEE_AMOUNT
UNION_FEE_END_DT
UNION_FEE_START_DT
UNION_FULL_PART
Union Participation
UNION_POS
Union Position
UNION_SENIORITY_DT
VALUE_1_FRA
Value 1
VALUE_2_FRA
Value 2
VALUE_3_FRA
Value 3
VALUE_4_FRA
Value 4
VALUE_5_FRA
Value 5
WORK_DAY_HOURS
WPP_STOP_FLAG
WRKS_CNCL_FUNCTION
WRKS_CNCL_ROLE_CHE
Table 71
AIF_PS_POSITION_DATA_STG Table
Column Name
Column Description
ADDS_TO_FTE_ACTUAL
BARG_UNIT
Bargaining Unit
CLASS_INDC
Classified/Unclassified Indicator
397
Column Name
Column Description
COMPANY
Company
CONFIDENTIAL_POSN
Confidential Position
COUNTRY_CODE
Country Code
DESCRSHORT
EG_ACADEMIC_RANK
Academic Rank
EG_GROUP
ENCUMBER_INDC
Encumbrance Indicator
ENCUMB_SAL_AMT
ENCUMB_SAL_OPTN
FLSA_STATUS
FLSA Status
FRI_HRS
Friday Hours
GRADE_FROM
Grade From
GRADE_TO
Grade To
GVT_AUDITED_BY_ID
Position Audited By
GVT_COMP_AREA
Competitive Area
GVT_COMP_LEVEL
Competitive Level
GVT_DRUG_TEST_REQ
GVT_DT_POSN_ESTAB
GVT_EXEC_FIN_DISCL
GVT_FUND_SOURCE
Fund Source
GVT_INTEL_POSN
Intelligence Position
GVT_LAST_AUDIT_DT
GVT_LEO_POSITION
LEO/Fire Position
GVT_MAINT_REVIEWCD
Maintenance Review
GVT_MANTREV_RESULT
GVT_MOB_POSN_IND
Mobility Position
GVT_NFC_FUNCTN_CD
GVT_NFC_PI_IND_OVR
398
Column Name
Column Description
GVT_NTE_DATE
GVT_OBLIGATED_TO
Obligated To ID
GVT_OBLIG_EXPIR_DT
Obligation Expiration
GVT_OCC_SERIES
Occupational Series
GVT_ORG_NUMCD1
Numeric Code 1
GVT_ORG_NUMCD2
Numeric Code 2
GVT_ORG_NUMCD3
Numeric Code 3
GVT_ORG_NUMCD4
Numeric Code 4
GVT_ORG_NUMCD5
Numeric Code 5
GVT_ORG_NUMCD6
Numeric Code 6
GVT_ORG_NUMCD7
Numeric Code 7
GVT_ORG_SUBAGENCY
Organizational Structure
GVT_ORG_TTL_CD
GVT_ORG_TTL_DESCR
GVT_PAREN_TITLE
Parenthetical Title
GVT_PAR_NBR
GVT_PAY_PLAN
Pay Plan
GVT_PERF_PLAN
Performance Plan
GVT_PI_UPD_IND
PI Update Indicator
GVT_POI
Personnel Office ID
GVT_POSN_LOC
Position Location
GVT_POSN_OCCUPIED
Position Occupied
GVT_POSN_SENS_CD
Sensitivity Code
GVT_PRESIDENT_APPT
GVT_PROC_INTEG_PSN
GVT_STAFF_LINE
Staff/Line Position
GVT_STATUS_TYPE
Status Type
GVT_SUB_AGENCY
Sub-Agency
399
Column Name
Column Description
GVT_TARGET_GRADE
Target Grade
GVT_VACY_REVW_CD
GVT_WIP_STATUS
Work-In-Progress Status
GVT_WORK_SCHED
Work Schedule
HEALTH_CERTIFICATE
Health Certificate
INCLUDE_SALPLN_FLG
JOB_SHARE
Job Share
KEY_POSITION
Key Position
LANGUAGE_SKILL
Language Skill
LASTUPDDTTM
LASTUPDOPRID
LOCATION
Location
MAIL_DROP
Mail Drop
MANAGER_LEVEL
Manager Level
MILITARY_SERVICE
Military Service
MIL_RANK
Military Rank
MIL_SVC_COMP_CD
MON_HRS
Monday Hours
ORGCODE
ORGCODE_FLAG
PHONE
Phone
PKG_RULE_ID
Package Rule ID
PKG_TEMPLATE_ID
Package Template ID
POSITION_POOL_ID
Position Pool ID
REG_REGION
Regulatory Region
REPORTS_TO
Reports To
REPORT_DOTTED_LINE
SAT_HRS
Saturday Hours
400
Column Name
Column Description
SEASONAL
Seasonal
SEC_CLEARANCE_TYPE
SHIFT
Shift
SIGN_AUTHORITY
Signing Authority
STATUS_DT
Status Date
STD_HRS_FREQUENCY
STEP_FROM
Step From
STEP_TO
Step To
SUN_HRS
Sunday Hours
SUPV_LVL_ID
Supervisory Level ID
THURS_HRS
Thursday Hours
TRN_PROGRAM
Training Program
TUES_HRS
Tuesday Hours
UPDATE_INCUMBENTS
Update Incumbents
WED_HRS
Wednesday Hours
Table 72
AIF_PS_SAL_GRADE_TBL_STG Table
Column Name
Column Description
DESCR
Grade Description
DESCRSHORT
EFFDT
Effective Date
EFF_STATUS
Effective Status
ELIGIBILITY_POINTS
Eligibility Points
EMPL_CTG
Employee Category
EMPL_CTG_L1
Employee Subcategory
EMPL_CTG_L2
Employee Subcategory 2
GRADE
Grade
GRADE_TITLE_JPN
GVT_MAX_RT_BIWK
401
Column Name
Column Description
GVT_MID_RT_BIWK
GVT_MIN_RT_BIWK
LABOR_AGREEMENT
Labor Agreement
MAX_YRS_GRADE
MIN_GRD_AGE
MIN_YRS_GRADE
REG_REGION
Regulatory Region
REVIEW_COUNT
Review Count
SALARY_MATRIX_CD
SAL_ADMIN_PLAN
SETID
SetID
STEP_INCREM_ACCUM
STEP_INCREM_TYPE
Table 73
AIF_PS_SAL_STEP_TBL_STG Table
Column Name
Column Description
APS_MAX_CLS_AUS
Maximum Classification
APS_MIN_CLS_AUS
Minimum Classification
CLASSN_CURRENT_AUS
Job Classification
DAILY_RT
Daily Rate
EFFDT
Effective Date
GRADE
Grade
GVT_BIWEEKLY_RT
Bi-weekly Rate
GVT_INCREM_DAYS
GVT_INCREM_WEEKS
GVT_STEP
US Federal Step
GVT_WGI_ADJ
INCREM_HOURS
Increment Hours
INCREM_MONTHS
Increment Months
402
Column Name
Column Description
SAL_ADMIN_PLAN
SETID
SetID
STEP_DESCR
Step Description
Table 74
AIF_PS_BP_JOB_STG Table
Column Name
Column Description
ACCDNT_CD_FRA
ACCT_CD
Account Code
ACTION
Action
ACTION_DT
Action Date
ACTION_REASON
Action Reason
ADDS_TO_FTE_ACTUAL
ANNL_BENEF_BASE_RT
ANNL_BEN_BASE_OVRD
ANNUAL_RT
Annual Rate
APPT_TYPE
Appointment Type
BARG_UNIT
Bargaining Unit
BAS_ACTION
BAS_GROUP_ID
BENEFIT_PROGRAM
Benefit Program
BENEFIT_SYSTEM
Benefit System
BEN_STATUS
Benefit Status
BORDER_WALKER
BUSINESS_UNIT
Business Unit
CHANGE_AMT
Change Amount
CHANGE_PCT
Change Percent
CLASS_INDC
Classified/Unclassified Indicator
COBRA_ACTION
COBRA Action
COMPANY
Company
403
Column Name
Column Description
COMPRATE
Compensation Rate
COMP_FREQUENCY
Compensation Frequency
CONTRACT_NUM
Contract Number
CTG_RATE
Category Rate
CURRENCY_CD
Currency Code
CURRENCY_CD1
Currency Code 1
CUR_RT_TYPE
DAILY_RT
Daily Rate
DEPTID
Department
DEPT_ENTRY_DT
DIRECTLY_TIPPED
Directly Tipped
EARNS_DIST_TYPE
EEO_CLASS
EEO_Class
EFFDT
Effective Date
EFFSEQ
Effective Sequence
ELIG_CONFIG1
ELIG_CONFIG2
ELIG_CONFIG3
ELIG_CONFIG4
ELIG_CONFIG5
ELIG_CONFIG6
ELIG_CONFIG7
ELIG_CONFIG8
ELIG_CONFIG9
EMPLID
Employee ID
EMPL_CLASS
Employee Classification
EMPL_CTG
Employee Category
EMPL_CTG_L1
Employee Subcategory
404
Column Name
Column Description
EMPL_CTG_L2
Employee Subcategory 2
EMPL_RCD
EMPL_STATUS
Employee Status
EMPL_TYPE
Employee Type
ENCUMB_OVERRIDE
Encumbrance Override
ENTRY_DATE
Entry Date
ESTABID
Establishment ID
EXEMPT_HOURS_MONTH
EXEMPT_JOB_LBR
Exempted
FICA_STATUS_EE
FICA Status
FLSA_STATUS
FLSA Status
FORCE_PUBLISH FTE
FULL_PART_TIME
Full or Part-Time
FUNCTION_CD
Function Code
GL_PAY_TYPE
GL Pay type
GP_ASOF_DT_EXG_RT
Use Rate As Of
GP_DFLT_CURRTTYP
GP_DFLT_ELIG_GRP
GP_DFLT_EXRTDT
GP_ELIG_GRP
Eligibility Group
GP_PAYGROUP
Pay Group
GRADE
Grade
GRADE_ENTRY_DT
GVT_ANNL_RT_NO_LOC
Annuity Rate
GVT_ANNUITY_OFFSET
Annuity Offset
GVT_ANNUIT_COM_DT
Annuity Date
GVT_ANN_IND
Annuity
GVT_BASIC_LIFE_RED
405
Column Name
Column Description
GVT_BIWEEKLY_RT
Biweekly Rate
GVT_BW_RT_NO_LOC
GVT_CHANGE_FLAG
Change Flag
GVT_COMPRATE
Compensate Rate
GVT_CONT_EMPLID
Contract Employee ID
GVT_CSRS_FROZN_SVC
GVT_DAILY_RT
Daily Rate
GVT_DED_PRORT_DT
GVT_DETL_POSN_NBR
Position Number
GVT_DLY_RT_NO_LOC
GVT_EFFDT
Effective Date
GVT_EFFDT_PROPOSED
GVT_ELIG_FEHB
Eligibility FEHB
GVT_FEGLI
FEGLI Code
GVT_FEGLI_BASC_PCT
GVT_FEGLI_LIVING
GVT_FEGLI_OPT_PCT
GVT_FEHB_DT
FEHB Date
GVT_FEHB_PCT
FEHB Percent
GVT_FERS_COVERAGE
FERS Coverage
GVT_HRLY_RT_NO_LOC
GVT_LEG_AUTH_1
Legal Authority 1
GVT_LEG_AUTH_2
Legal Authority 2
GVT_LEO_POSITION
GVT_LIVING_AMT
Living Amount
GVT_LOCALITY_ADJ
Locality Adjustment
GVT_MNLY_RT_NO_LOC
GVT_NID_CHANGE
NID Change
406
Column Name
Column Description
GVT_NOA_CODE
NOA Code
GVT_OTH_PAY_CHG
GVT_PAR_AUTH_D1
GVT_PAR_AUTH_D1_2
GVT_PAR_AUTH_D2
GVT_PAR_AUTH_D2_2
GVT_PAR_NTE_DATE
NTE Date
GVT_PAY_BASIS
Pay Basis
GVT_PAY_FLAG
Pay Flag
GVT_PAY_PLAN
Pay Plan
GVT_PAY_RATE_DETER
GVT_PI_UPD_IND
PI Update Indicator
GVT_POI
Personnel Office ID
GVT_POSN_OCCUPIED
Position Occupied
GVT_PREV_RET_COVRG
GVT_RETIRE_PLAN
Retire Plan
GVT_RETRO_BSE_FLAG
GVT_RETRO_DED_FLAG
GVT_RETRO_FLAG
Retrospective Flag
GVT_RETRO_JOB_FLAG
GVT_ROUTE_NEXT
Route to Next
GVT_RTND_GRADE
Retained Grade
GVT_RTND_GVT_STEP
GVT_RTND_PAY_PLAN
GVT_RTND_SAL_PLAN
GVT_RTND_STEP
Retained Step
GVT_S113G_CEILING
S113G Ceiling
GVT_SF52_NBR
SF52 Number
407
Column Name
Column Description
GVT_STATUS_TYPE
Status Type
GVT_STEP
Step
GVT_SUB_AGENCY
Sub Agency
GVT_TRANS_NBR
Transaction Number
GVT_TRANS_NBR_SEQ
GVT_TSP_UPD_IND
TSP Status
GVT_TYPE_OF_APPT
Type of Appointment
GVT_WIP_STATUS
WIP Status
GVT_WORK_SCHED
Work Schedule
GVT_XFER_FROM_AGCY
GVT_XFER_TO_AGCY
Transfer To Agency
HOLIDAY_SCHEDULE
Holiday Schedule
HOURLY_RT
Hourly Rate
HOURLY_RT_FRA
INTERCTR_WRKS_CNCL
JOBCODE
Job Code
JOB_DATA_SRC_CD
JOB_ENTRY_DT
JOB_INDICATOR
Job Indicator
LABOR_AGREEMENT
Labor Agreement
LABOR_FACILITY_ID
Labor Facility ID
LABOR_TYPE_GER
LAYOFF_EXEMPT_FLAG
LAYOFF_EXEMPT_RSN
LBR_FAC_ENTRY_DT
LOCATION
Location
LUMP_SUM_PAY
MAIN_APPT_NUM_JPN
408
Column Name
Column Description
MATRICULA_NBR
Matricula Number
MONTHLY_RT
Monthly Rate
OFFICER_CD
Officer Code
PAID_FTE
Paid FTE
PAID_HOURS
Paid Hours
PAID_HRS_FREQUENCY
PAYGROUP
Pay Group
PAY_SYSTEM_FLG
PAY_UNION_FEE
PERFORM_GROUP_GER
POSITION_ENTRY_DT
POSITION_NBR
Position Number
POSITION_OVERRIDE
Position Override
POSN_CHANGE_
RECORD
PRORATE_CNT_AMT
REG_REGION
Regulatory Region
REG_TEMP
Regular or Temporary
REPORTS_TO
Reports To
SAL_ADMIN_PLAN
SETID_DEPT
SetID Department
SETID_JOBCODE
SETID_LBR_AGRMNT
SETID_LOCATION
SetID Location
SETID_SALARY
SetID Salary
SHIFT
Shift
SHIFT_FACTOR
Shift Factor
SHIFT_RT
Shift Rate
SOC_SEC_RISK_CODE
409
Column Name
Column Description
SPK_COMM_ID_GER
Spokesman Committee ID
STD_HOURS
Standard Hours
STD_HRS_FREQUENCY
Standard Hours
STEP
Frequency Step
STEP_ENTRY_DT
SUPERVISOR_ID
Supervisor ID
TARIFF_AREA_GER
TARIFF_GER
Tariff Germany
TAX_LOCATION_CD
UNION_CD
Union Code
UNION_FEE_AMOUNT
UNION_FEE_END_DT
UNION_FEE_START_DT
UNION_FULL_PART
Union Participation
UNION_POS
Union Position
UNION_SENIORITY_DT
UPDATE_PAYROLL
Update Payroll
VALUE_1_FRA
Value 1
VALUE_2_FRA
Value 2
VALUE_3_FRA
Value 3
VALUE_4_FRA
Value 4
VALUE_5_FRA
Value 5
WORK_DAY_HOURS
WPP_STOP_FLAG
WRKS_CNCL_FUNCTION
WRKS_CNCL_ROLE_CHE
410
CHARTFIELD
Table 75
Table TypeCHARTFIELD
Table Name
Column Name
Column Description
AIF_PS_GL_ACCOUNT_TBL_STG
ACCOUNT
Account
AIF_PS_AFFILIATE_VW_STG
AFFILIATE
Affiliate
AIF_PS_ALTACCT_TBL_STG
ALTACCT
Alternate Account
AIF_PS_BUD_REF_TBL_STG
BUDGET_REF
Budget Ref
AIF_PS_CHARTFIELD1_TBL_STG
CHARTFIELD1
Chartfield 1
AIF_PS_CHARTFIELD2_TBL_STG
CHARTFIELD2
Chartfield 2
AIF_PS_CHARTFIELD3_TBL_STG
CHARTFIELD3
Chartfield 3
AIF_PS_CLASS_CF_TBL_STG
CLASS_FLD
Class
AIF_PS_DEPT_CF_TBL_STG
DEPTID_CF
Department
AIF_PS_FUND_TBL_STG
FUND_CODE
Fund Code
AIF_PS_OPER_UNIT_TBL_STG
OPERATING_UNIT
Operating Unit
AIF_PS_PRODUCT_TBL_STG
PRODUCT
Product
AIF_PS_PROGRAM_TBL_STG
PROGRAM_CODE
Program
AIF_PS_PROJECT_TBL_STG
PROJECT
Project
411
412
E
In This Appendix
ODI
SQL Loader
anything
You configure this adapter using FDMEE to populate the staging table with the related data from
the open interface table. You load the open interface table with the tool of your choice like a pl/
sql routine, a sql loader script or a custom program. When you use ODI to load the open interface
table, you can customize the Open Interface Adapter ODI package shipped with FDMEE to call
a custom ODI interface to load the open interface table as a step in the data load process.
Column Name
Data Type
Comment
BATCH_NAME
VARCHAR2(200 BYTE)
YEAR
NUMBER(15,0)
PERIOD
VARCHAR2(30 BYTE)
PERIOD_NUM
NUMBER(15,0)
413
Column Name
Data Type
Comment
CURRENCY
VARCHAR2(10 BYTE)
Required.
DATAVIEW
VARCHAR2(8 BYTE)
Used for HFM applications. Assign value of YTD or Periodic. Default value is YTD
DESC1
VARCHAR2(75 BYTE)
DESC2
VARCHAR2(75 BYTE)
AMOUNT
NUMBER(29,12)
AMOUNT_YTD
NUMBER(29,12)
AMOUNT_PTD
NUMBER(29,12)
COL01
VARCHAR2(75 BYTE)
COL02
VARCHAR2(75 BYTE)
COL03
VARCHAR2(75 BYTE)
COL30
VARCHAR2(75 BYTE)
ATTR1
VARCHAR2(20 BYTE)
ATTR2
VARCHAR2(20 BYTE)
ATTR13
VARCHAR2(20 BYTE)
ATTR14
VARCHAR2(20 BYTE)
414
For the Source system Type, select Others, and for the ODI Context Code, enter the
default GLOBAL. If the ODI has been set up differently from the defaults, enter the
appropriate ODI Context Code if it is not GLOBAL.
From Source Adapter, copy the Open Interface Adapter to a new adapter.
a. Select the source system created in Step 3 and the adapter from Step 4.
b. Map the source columns to the appropriate target dimensions.
When the import format mappings are complete, select Regenerate ODI Scenario.
This step generates the ODI Scenario based on the import format mappings.
On the Locations screen, define a new location using the import format.
Workbench
415
In the FDMEE repository, export the Open Interface Adapter Model and ERPI Target Model folders.
Use a repository ID of 900 or higher to avoid conflicts with Oracle shipped components.
This is your development repository when performing customization. It is referred to as the
custom repository in the following steps.
In the custom repository, import the model folders named: Open Interface Adapter Model and ERPI
Target Model.
When customizing objects, do not modify FDMEE seeded objects imported from the
FDMEE repository. Instead, copy needed objects, use the Custom suffix in names to
identify them, and then modify them.
For example, copy the Open Interface Balances package as Open Interface Balances
Custom, and make any edits to it.
Export customized objects (for example, Project, Packages, Interfaces) from the custom repository and
import them into the FDMEE repository.
Using the FDMEE Source Adapter user interface, copy the Open Interface Adapter to a new adapter
and complete the following:
l
For the new adapter, provide a new adapter key. The adapter key can be ten characters
long. Once it has been created, it cannot be modified.
Make any necessary modifications to the Display Names. Display Name are shown in
the Import Format and Data Load Workbench.
Specify the ODI Package Name and ODI Project Code as specified in the custom project.
Import the model and project into the target FDMEE repository (using the Synonym Mode
INSERT_UPDATE as the Import Type).
416
PeopleSoft Commitment
Control
To use Commitment Control within the context of FDMEE, complete the following:
1. In Source System, register your General Ledger and HRMS source systems.
2. In Source System, to use PeopleSoft Commitment Control, select Enable Commitment
Control.
3. In Target Application, register the target application.
4. In Import Format, define an import format that specifies how to map PeopleSoft chart fields
to dimensions in the Public Sector Planning and Budgeting applications.
5. In Data Load Rule, define a location that identifies the PeopleSoft accounting entity (business
unit) from which to load data.
6. In Data Load Rule, specify a period mapping type of Budget.
7. In Data Load Rule define global, application, and source mappings that specify how period
keys in the PeopleSoft calendar and time periods correspond to periods in your Public Sector
417
Planning and Budgeting budget application such as months, quarters, and years. Options
include:
l
Select an As of Date.
The As of Date to determine effective dated records, for example, Budget Definition.
Select a Target for Blank Period if the budget is based on a project period.
Optionally, in Period Mappings, map a budget period by mapping a calendar and period
to an FDMEE period.
Commitment Control enables different calendars to be used for different rules. The
calendar can be of different granularity and duration. For example, you can map the
Chartfield used for rule ranges to the Hyperion Planning Entity dimension. When you
specify an explicit period mapping, you can map a Budget period by pointing to a
calendar and period to an FDMEE period. The same FDMEE period can be mapped to
multiple source periods from different calendars.
418
G
In This Appendix
When creating reports, you can use a base SQL query and a parameter SQL query to enhance
the data shown in the report. The base SQL query can be used to pull data from various tables
and display the data as report output. For example, using one query definition, you can show
different columns or groupings. In one report, you can list amounts by account and group by
entity, and in another list amount by entity and group by account.
The parameter SQL query enables you to run a query against the parameters in the report
definition. For example, the query can be used to select the Location, Period, Category, or
Account groupings. In one report, you can list amounts by account and group by entity, and in
another list amount by entity and group by account.
The FDMEE tables that are used in the base and parameter SQL query are:
l
TDATASEG
TLOGPROCESS
Column Name
Definition
Description
DATAKEY
PARTIONNKEY
CATKEY
PERIODKEY
419
Column Name
Definition
Description
DATAVIEW
Hard coded to YTD for file, and set to YTD for balance sheet and
PTD for income statement when pulling data from an Enterprise
Resource Planning (ERP) system.
CURKEY
CALCACCTTYPE
9=Imported
0=No Change
1=Reverse Sign
CHANGESIGN
JOURNALID
AMOUNT
AMOUNTX
DESC1
DESC2
ACCOUNT
ACCOUNTX
ACCOUNTR
1=Exception
3=Between
4=Range
ACCOUNTF
ENTITY
ENTITYX
ENTITYR
ENTITYF
420
1=Exception
3=Between
4=Range
Column Name
Definition
Description
ICP
ICPX
ICPR
1=Exception
3=Between
4=Range
ICPF
UD1
UD2
UD3
UD4
UD5
UD6
UD7
UD8
UD9
UD10
UD11
UD12
UD13
UD14
UD15
UD16
UD17
UD18
UD19
UD20
UD1X
421
Column Name
Definition
Description
UD1R
1=Exception
3=Between
4=Range
UD1F
ARCHIVEID
Future use
HASMEMOITEM
Future use
STATICDATAKEY
Future use
ATTR1
ATTR2
ATTR3
ATTR4
ATTR5
ATTR6
ATTR7
ATTR8
ATTR9
ATTR10
ATTR11
ATTR12
ATTR13
422
Column Name
Definition
Description
ATTR14
CODE_COMBINATION_ID
VARCHAR2(155 CHAR)
AMOUNT_YTD
NUMBER(29,12)
AMOUNT_PTD
NUMBER(29,12)
LOADID
NUMBER(15,0)
RULE_ID
NUMBER(15,0)
STAT_BALANCE_FLAG
VARCHAR2(1 CHAR)
Y=Stat
N=Balance
VALID_FLAG
VARCHAR2(1 CHAR)
Y=Valid
N=Not Valid
I=Ignore
Column Name
Definition
Description
PARTITIONKEY
CATKEY
PERIODKEY
RULE_ID
PROCESSIMP
NUMBER(1,0) DEFAULT 0
NOT NULL ENABLE
1=Successful
423
Column Name
Definition
Description
PROCESSIMPNOTE
VARCHAR2(50 CHAR)
DEFAULT NULL
PROCESSVAL
PROCESSVALNOTE
PROCESSEXP
PROCESSEXPNOTE
PROCESSENTLOAD
PROCESSENTLOADNOTE
PROCESSENTVAL
424
NUMBER(1,0) DEFAULT 0
NOT NULL ENABLE,
VARCHAR2(50 CHAR)
DEFAULT NULL,
NUMBER(1,0) DEFAULT 0
NOT NULL ENABLE,
VARCHAR2(50 CHAR)
DEFAULT NULL
NUMBER(1,0) DEFAULT 0
NOT NULL ENABLE
VARCHAR2(50 CHAR)
DEFAULT NULL
NUMBER(1,0) DEFAULT 0
NOT NULL ENABLE,
Import Successful
Recalculated OK
Import Error
Recalculate Failed
MultiLoad
BypassDataLoad
1=Successful
Validate Successful
Error= x records (Where X = how many members did not have map rules)
BypassDataLoad
1=Successful
Export -B Successful
Export Successful
BypassDataLoad
1=Successful
Load Error
BypassDataLoad
1=Successful
Column Name
Definition
Description
PROCESSENTVALNOTE
VARCHAR2(50 CHAR)
DEFAULT NULL
PROCESSCERT
PROCESSCERTNOTE
PROCESSASSES
PROCESSASSESNOTE
PROCESSCHILDDONE
PROCESSCHILDDONENOTE
NUMBER(1,0) DEFAULT 0
NOT NULL ENABLE,
VARCHAR2(50 CHAR)
DEFAULT NULL,
NUMBER(1,0) DEFAULT 0
NOT NULL ENABLE,
VARCHAR2(50 CHAR)
DEFAULT NULL,
NUMBER(1,0) DEFAULT 0
NOT NULL ENABLE
VARCHAR2(50 CHAR)
DEFAULT NULL
Check Successful
Check Error
BypassDataLoad
1=Submitted
Controls Submitted
Controls Cleared
Not Submitted
1=Submitted
Controls Submitted
Controls Cleared
Not Submitted
Children Submitted
No Children
PROCESSUD1
NUMBER(1,0) DEFAULT 0
NOT NULL ENABLE
Not used
PROCESSUD1NOTE
VARCHAR2(50 CHAR)
DEFAULT NULL
Not used
PROCESSUD2
NUMBER(1,0) DEFAULT 0
NOT NULL ENABLE
Not used
425
Column Name
Definition
Description
PROCESSUD2NOTE
VARCHAR2(50 CHAR)
DEFAULT NULL
Not used
PROCESSUD3
NUMBER(1,0) DEFAULT 0
NOT NULL ENABLE
Not used
PROCESSUD3NOTE
VARCHAR2(50 CHAR)
DEFAULT NULL
Not used
PROCESSUD4
NUMBER(1,0) DEFAULT 0
NOT NULL ENABLE
Not used
PROCESSUD4NOTE
VARCHAR2(50 CHAR)
DEFAULT NULL
Not used
PROCESSENDTIME
BLNWCDIRTY
NUMBER(1,0) DEFAULT 0
NOT NULL ENABLE
Flag used to indicate that maps (WC = WildCard) must be recalculated prior
to validating:
l
0=OK
1=Re-caculate location
Map rules have changed after data was imported. This causes the Calculate
flag to be displayed
BLNLOGICDIRTY
NUMBER(1,0) DEFAULT 0
NOT NULL ENABLE
BLNVALDIRTY
NUMBER(1,0) DEFAULT 1
NOT NULL ENABLE
0=OK
1=re-process validations
Map rules have changed after data was imported. This causes the Calculate
flag to be displayed.
INTLOCKSTATE
PROCESSSTATUS
426
NUMBER(6,0) DEFAULT 50
NOT NULL ENABLE
NUMBER(10,0) DEFAULT 0
NOT NULL ENABLE
50=open
60=locked
This appendix explains how to set up Jython, Eclipse and PyDev for use with the FDMEE
scripting component.
This section is specific to the 11.1.2.3.100 release of Oracle Hyperion Financial Data Quality
Management, Enterprise Edition. Because Jython, Eclipse and Python are not Oracle products,
always refer to these products' documentation for the latest updates and changes. Also see http://
pydev.org/manual_101_root.html.
To set up Jython:
1
English Language
Standard Install
http://pythonfiddle.com site to write and test scripts. Pythonfiddle is a good site for
writing event scripts, and the Chrome browser is recommended for pythonfiddle. For
more advanced scripts, Eclipse or Jdeveloper are recommended
Select the directory and select a default location for your Workspace.
If the Welcome page is displayed, skip it by selecting the Workbench link in the top right corner.
427
i.
Select Install/Update, then select Available Software Sites, and then click Add.
ii.
iii.
To do this:
a. Select General, then select Editors, and then select Text Editors.
b. For the Displayed tab width, enter 2.
c. Enable the Insert spaces for tabs option.
d. Enable the Show print margin option.
e. Enable the Show line numbers option.
To do this:
a. Select Help, and then select Install New Software...
b. In Work with, select PyDev.
c. From PYDev available software list, select the PyDev node, and then click Next.
d. Confirm the PyDev for Eclipse installation, and then click Next.
e. Accept the licensing terms, and then click Finish.
f.
Once the install starts, you are prompted about Aptana PyDev; and PyDev; Aptana
certificates. Make sure you select the certificates, and then click OK.
ii.
Click New.
iii.
Click Browse.
iv.
Select C:\FDMEE\jython2.5.1\jython.jar
v.
Click OK.
vi.
When prompted to select the folders to add to the SYSTEM python path, do not
change any selection, and then click OK.
428