Oracle DRM – Classic HFM Integration Process

Posted on Leave a commentPosted in Informative

Oracle Hyperion Financial Management is a financial consolidation and reporting application built with advanced Web technology and designed to be used and maintained by the finance team. It provides financial managers the ability to rapidly consolidate and report financial results, meet global regulatory requirements, reduce the cost of compliance and deliver confidence in the numbers.

Oracle Data Relationship Management is a Master Data Management tool where master data is maintained, analyzed, and validated before moving throughout enterprise. It is the recommended tool of choice for organizing the financial views of financial chart of accounts, cost centers and legal entities that are then used to govern on-going financial management and consolidations for an enterprises.

Some main features of DRM maintaining Master Data than creating in HFM, DRM is compatible in integrating with all the Hyperion and Non-Hyperion Systems like HFM, ESSBASE, PLANNING, Planning and budgeting cloud service (PBCS) and has a roadmap to integrate to all upcoming Oracle Cloud EPM applications. DRM Integrates with both HFM Classic and HFM EPMA.

HFM1

STEP 1 : Initial Load of metadata into DRM:

When DRM is integrated with HFM for the first time, along with metadata load we also need to create Metadata objects like Property Definitions, Property Categories, Node Types, Validations etc.. These metadata objects can be loaded into DRM using epma-app-template.xml through Migration Utility. Along with this we may also need to create certain custom properties as per business requirement.

STEP 2: Importing Dimensions using Import Profile.

After loading metadata objects through migration utility into DRM ,Create import profiles to import data into DRM. After import profiles create custom properties ,property categories, validations and node types which are used to export data into HFM.

HFM2

STEP 3:   Exporting Metadata from DRM.

DRM Export in the form of Hierarchy Export is done and then a book of all related export are created by combining all the dimensions containing individual exports into a single file.

HFM3

STEP 4: DRM Export Automation

DRM Export Process can be automated using DRM-Batch Client

DRM Batch Client is a command line utility that allows access to various arm operations in batch mode including: Actionscript, Import, Blender, Export(Individual Export and Book Export),Opening and closing versions.

HFM4

STEP 5: Importing Data into HFM Applicaiton.

Once the metadata is exported into a flat file or DB Tables from DRM next step is to import Metadata into HFM Application using Load Task.

Create an Application Profile in the Client of HFM and create an Application on the Workspace. Dimension are loaded in HFM Application using Load Metadata option in Load Task.

 

STEP6:

This Process of Loading Metadata in HFM application can be automated using Task Automator and then scheduling the task using schedulers in the Workspace.

 

Oracle DRM – Creating Derived Properties Using Javascript

Posted on Leave a commentPosted in Informative

Property define the characteristics of the Node. Property Type “Derived” allows you to build dynamic business logic into your properties. Derived properties can simplify application maintenance and reduce the overall storage of your application by reducing or eliminating the need to store (override) additional values.

When you select “Derived” as Property Type, a new drop down will appear with the available options “Formula” or “Script”. Prior to 11.1.2.3 release of DRM, using the legacy formulas was the only option.

Oracle introduced Dynamic Scripting in DRM 11.1.2.3. Dynamic scripting enables Data Relationship Management administrators to develop business logic for derived properties and validations using JavaScript. Dynamic scripts provide a more robust and better-performing alternative to formulas, using a standard scripting language. Scripts allow for better organization and less complexity of logic through the use of multiple statements, variables, and in-line comments. Dynamic scripts also provide support for advanced concepts such as looping and regular expressions. JavaScript offers significant performance improvement over the legacy formulas.

Jav1

Fig: 1. Sample JavaScript Which returns “Hello”.

Jav2

Fig: 2 Sample JavaScript to Add Two Strings

//JavaScript to add two strings

var myNodeDescr; //Declare variables
var myVersionDescr;

myVersionDescr=node.Version.PropValue(“Core.VersionDescr”); //Assigning variables
myNodeDescr=node.PropValue(“Core.Descr”);

//Declare Function
function add() {
return myNodeDescr + ” ” +myVersionDescr
}
return add();

Oracle DRM – Assigning validations through Action Script

Posted on Leave a commentPosted in Informative

Today we are going to see how we can assign validations through action scripts. Validations enable us to enforce business rules on versions, hierarchies, nodes, and properties. We can run validations in either real time or batch mode, or in both modes. Real-time validations are run at the time of modification and prevent changes from being saved if the action violates the rules being enforced. We explicitly run batch validations. Validations can also be run using Action Scripts

 Action Script

Action scripts enable us to process bulk sets of incremental changes in an automated fashion. Each record within a script represents a separate action to be performed and processed separately from other actions. We can group actions of different types in the same script. Action scripts are particularly useful when we need to perform the same set of actions for multiple versions, hierarchies, or nodes. We can load action scripts from flat files, generate them from transaction logs, or create them from node models. In the Script task group, we can load and run only one action script at a time.

 

Types

AssignVersionValidations Ver Validation List ResultDescr  
AssignHierValidations Ver Validation List ResultDescr  

 

Version validation using action script syntax

AssignVersionValidations Ver Validation List ResultDescr

 

Example:

AssignVersionValidations;Sob_Ess_Year;Essbase.MemberNameLength;Result

Selecting Validation

After creating validations, we can assign them to versions, hierarchies, domains, and nodes. Multiple validations can be assigned at the same time. We can assign using Action Scripts as well. Select the related validation which we want to perform on a version.

Load Action Script

In the Script task group, we load the flat file that contains the action scripts. After loading, edit rows that display warning symbols to ensure proper processing.

Let’s take an example for loading the script, below is the script

 

AssignVersionValidations;Sob_Ess_Year;Essbase.MemberNameLength;Result in DRM script.

Val1

Run the Script

When we run the script of assigning validation at version level by using action script validations are inherited by all hierarchies and nodes within the version.

Val2

Check Assign Validations for Version

 This is how we can check by clicking version then right click assign validations tab

Val4

 

 

DRM – External Connections

Posted on Leave a commentPosted in Master Data Management

DRM External Connections:

A new feature for the 11.1.2 release in DRM is External Connections.

External Connections are used to access server file locations, FTP locations, and database tables.

We can create and apply default connections and we can apply connections individually. After We create a file connection, it can be referenced by any object that requires a file connection.

We have three built-in providers: Oracle, SQL Server, and OLEDB.

Data can be imported or exported by creating External Connections. We can use three instances to create External Connections in DRM.

  • Client File.
  • Server File.
  • Database

 

Server File

Ext1

For Connection Type, select Server File.

Enter the UNC path to the server file.UNC (Universal Naming Convention) is a standard for identifying servers, printers and other resources in a network, which originated in the UNIX community. A UNC path uses double slashes or backslashes to precede the name of the computer. (Example:-C: \Newfolder\Data).

In UNC path we define the Server path where we want to Export the file or From Where we want to import the file.

Click Test connection icon to test the server connection. Click OK.

 

Database

We need to configure the Database External Connections Tab. Below is the sample file

Ext2

External connections to relational databases can be used to import and Export data from database tables into Data Relationship Management. An import profile can source data from tables in a single database. Each section of an import profile can be mapped to a single database table. A query filter can be configured to import a subset of data from the source database tables.

Sample Database Table:

Ext3

IMPORTING DATA FROM DATABASE:

Sample Import Profile:

Ext4

About how to select Source to import data from Database into DRM.

Setting up import wizard to Importing Data From Database :

   Import files are organised into sections and columns. We are having five sections in import profile Version, Hierarchy, Node, Relationship and Hierarchy Node. We can create imports in the import wizard, which consist of source, style, columns, filters, target tabs. We can start the import wizard in the import task group.

For Importing the data from database we have to configure all these tabs in import wizard, In source we have to select device as Database and select the sections which we want to import. Configure columns tab by mapping each column in import profile in DRM with Database table Columns (the number and order of the columns must match). To import data from Database we have to configure an additional option that is Database options in columns tab. In target tab give version name you want to create and description.

Setting up Source tab: Set up a DRM import that loads the tables. We will need to set up an external connection to point to the tables. Once We have selected the external connection, We will see that the import tabs change, a little bit. Each source object will need to point to a table that associates to that section. set up the sections by pointing to the right source tables:

Sample Source tab:

Ext5png

 

Setting up a columns tab:

     Configure the columns according to the sections map each column in import profile in DRM with Database table Columns (the number and order of the columns must match).After setting up the appropriate properties for the import sections, We will notice that there is a new section in the Columns tab, called Database Options:

 Ext6

On this tab, you will be able to set up the property to source column relationships.

Ext7