Using Factors in Data Management Import Formats

Import expressions can be added to an FDMEE import format to alter the data being imported from a file in several valuable ways. In this blog, I will focus on using the ‘Factor’ import expression, which allows you to multiply your data by any whole number or decimal factor. This means that you can scale the file data effortlessly by any numeric factor. 

The syntax for this expression is Factor=Value, where the value is the user-defined whole or decimal number you wish to multiply your data by. The import expression should be entered in the 'Expression' field for the 'Amount' source column. 

Listed below are a few things to consider when applying a factor to your data:
  • Factors are only applied when the import format Data Type is set to one of the following 
    • Delimited–Numeric data 
    • Fixed–Numeric data
    •  Multi-Column–Numeric Data 
  • The factor will be applied to all data amounts in the file. 
  • When importing a multi-column file with Account members in the columns, all columns of data will be factored by the user-defined value – you cannot specify a singular column to apply the factor to.
Factor Example

 
Note: To stack this expression, i.e. to include more than one expression for a single import format, separate each expression with a semi-colon. E.g. below, where expression NZP is added to stop the suppression of zeros when importing data.


In the past, I have used a Factor expression to allow the loading of percentages into Accounts that are set to Percentage Data Type. This is necessary because, if your data file contains percentages as whole numbers, e.g. 20%, rather than the decimal 0.2, then the loaded number will be 100 times larger than you require. To get around this, we use a Factor=0.01 expression in the import format to divide all data values by 100.



Comments

Post a Comment

Popular posts from this blog

Executing Smart View Retrievals using VBA

Image
When working with Hyperion systems, Smart View is a key tool used for reporting, as well as inputting data. It provides a valuable link between Hyperion and Excel, which allows users to retrieve data from the database straight into Excel with ease. Smart View functions are available through the Smart View toolbar and can be used with Essbase, HFM, Planning or Cloud connections. Occasionally, it is necessary to perform Smart View functions behind the scenes using VBA code, rather than manually using the Smart View toolbar. For example, a spreadsheet which will refresh all the Essbase retrieval sheets on opening, so that users can view the most up to date data, without having to remember to refresh each of the retrieval sheets themselves. This blog will be cover how to retrieve data using a Smart View refresh function in VBA. For more information about Smart View Excel VBA functions, go to the Oracle Hyperion Smart View Developers Guide .  System Requirements T
Read more

Loading Actuals from Fusion ERP Cloud to PBCS

Image
If you’re looking to set up a data load of Actuals from ERP to PBCS and have heard this is an “Out of the box” integration, then good news! Not only is the OOTB connector included within PBCS Data Management but the integration is simple to setup and to schedule using EPM Automate. This blog will detail how to setup the ERP to PBCS connector in Data Management and some of the common errors found when running the data load. The first thing to know about this integration is that the data source is actually the ASO Essbase cube which sits underneath the Fusion ERP tables, holding the period Actuals values. This ERP Essbase cube is created using job ‘Create General Ledger Balances Cube’ when configuring the ERP system. This cube must be created before the integration can be set up correctly and can be accessed directly via Smart View for reconciliations. Set up the Source System As this is an Oracle built connector, it’s as simple as providing a name for the source system
Read more

Loading multi-period row data files using Data Management

Image
The ability to load multi-period data with the Period and/or Year in the rows is not particularly new (since release 16.10), however it is something that most people seem to forget is possible in Data Management. This really is something worth remembering as it eliminates the need to either split the data files into one file per month or try to pivot the month into the columns. In order to set this up, let’s firstly look at how to add the Period and Year columns to the import format. Add the Period and Year columns using the Add -> Source Period Row dropdown, and input: The Source Column name – e.g. PERIOD The Field Number (file column) – e.g. 3 Any required expressions for that field  As these are Period/Year dimensions, the mappings are not held in the usual Data Load Mappings area. Instead they are configured in the Period Mappings , under the Source Mapping tab. Select the Source System as File to add a new mapping calendar for loading the data file
Read more