2018

BISP Solutions Inc.

Ashima Rajput

[ORACLE FDMEE IMPORT SCRIPT EXAMPLE]

The below example of import script demonstrate another scenario of using import script. In the below example
nested if condition is used to load data using multiple conditional expressions.

0
 Import Script

Purpose
The below example demonstrate import script example. In the below script, one needs
to load all the accounts and their reporting type which start from GL 6xxxxxx. However,
if GL account not doesn’t start with 6 than load only if they have reporting type as RF21.

Source System

Target System
Essbase Application :Cube Name : demo_cpy

Steps for Loading Data into essbase application.

In First step we login into workspace and open FDMEE Environment.

Navigate >Administer > Data Management

In First step we login into workspace and open FDMEE Environment.

Navigate >Administer > Data Management

Go to setup Tab Register Source system.

Setup>Register > source system

Here you can see File (source system) is registered already.

Go to setup Tab Register Target Application.

Setup>Register > Target Application

You will see this window from there select your target application.

Some of the Target applications are already registered. In order to register any other Target, click
on Green plus icon and add New Target Application.

To add new Target application

Setup>Register>Target application>add
Scroll down below all the details comes automatically related to dimension mapping this refers to
staging table.

In next step repare Import format for file.

Click on Green add button and add new import format.

Go to Setup > Integration Setup select Import Format

Fill all the details in Details section, like Name of import format; source Type as ERP, Source as
File. Select Target Type as EPM and Select Target system. File Delimiter means your source file
contains which type of delimiter.

Location: Once define Import Format create Location, Click on add Icon and fill details.

Setup > Integration Setup >Location

To specify new Location, provide name to Location search Import Format Name. System automatically
fetch all other details related to source and Target, click on save.
Period Mapping: Define global mapping for period Jan.

Setup > Integration Setup >Period Mapping> Source Mapping

Category Mapping: If category exist under category list which you want to load into target
dimension than select it or otherwise create them.

Setup >Integration Setup > Category Mapping

Now for creating script.

Setup > Scripts > Script Editor >Import > New

In script window write script, remember in Import script, the script name should be same as
function name.

Strfield: strfield keeps value of the those source column dimension on which we assign Import
script.

Strrec: strrec keeps whole row or record of source.

Fdmskip: fdmskip used when we want to skip the row as return result.
Add this script in import format Expression field.

For adding script click on add expression. Choose script as Expression type. And choose script
name form dropdown in Expression value.

Data Load Mapping:

Data Load Mapping for map source dimension member to their target Application Dimension
member. We need to specify mapping for each dimension.

Setup - Data Load -- Data Load Mapping

Dimension- Account
Dimension- Market

Dimension- Product

Dimension- Reporting Type

Dimension- Scenario

Data Load Rule: Last step for load data, DLR Specify process of Data Load and validation of
data and finally how we export data from ERP to EPM system.

Choose File name in Source options. File Type as single period if loading data for a month. And in last
choose Import Format,

Click on save , Execute it.

See output in workbench

All the GL accounts which not started from 6xxxxx got loaded with reporting type as “RF21”
and others which are started from 6 has any type of reporting types get loaded into target.
Output in essbase: