Introducing Business Script Language (BSL) in HFM 11.2.22: A Native Alternative to VBScript

In one of prior blog, we talked about that Microsoft’s plan to deprecate the VB scripting language and how VBScript will be retired and eliminated from future versions of Windows.

Hyperion Financial Management uses Microsoft VB Script as a scripting language for writing business logic against any application created on Financial Management System. In response to Microsoft’s deprecation of VBScript, HFM is introducing a native scripting language called as Financial Management Business Script Language (BSL) to maintain continuity.

What is BSL?

Business Script Language (BSL) uses the same syntax as VBScript, supporting most built-in VBScript functions and several key objects within a defined scope. It serves as the scripting language for writing business logic in any application built on the Financial Management System.

Here –

• Starting with 11.2.22 release, Financial Management includes the Native Script Engine as an option to use. The default engine is still Microsoft VB Script Engine.
• Business Script Language (BSL) is same as Microsoft VB Script language within the defined scope.
• Starting with 11.2.22 release, user have option to switch between the VBScript engine and the new Native Script Engine.

To switch between script engines:

Parameter - ScriptEngineType:

• 0 - Native Engine
• 1 - Microsoft Engine (Default)

Verify if the ScriptEngineType parameter is present on the Settings page. If the parameter is missing, you must add it by executing the appropriate SQL scripts on the corresponding database.

Oracle Database

INSERT INTO XFM_PARAMETERS_DEFAULTS (Name,Type,Hidden,Validation,Description,DefaultValue) VALUES ('ScriptEngineType','1','0','','Set Native or Microsoft Script Engine','1');

INSERT INTO XFM_PARAMETERS (ParameterName, ClusterName, ServerName, ApplicationName, CategoryName, CreatedOn, UpdatedOn, CreatedBy, UpdatedBy, Value) SELECT Name, 'ALL','ALL','ALL','ALL', SYSDATE, SYSDATE, 'system', 'system', DefaultValue FROM XFM_PARAMETERS_DEFAULTS WHERE NOT EXISTS ( SELECT * FROM XFM_PARAMETERS WHERE Name = ParameterName );

SQL Server Database

INSERT INTO XFM_PARAMETERS_DEFAULTS (Name,Type,Hidden,Validation,Description,DefaultValue) VALUES ('ScriptEngineType','1','0','','Set Native or Microsoft Script Engine','1');

INSERT INTO XFM_PARAMETERS (ParameterName, ClusterName, ServerName, ApplicationName, CategoryName, CreatedOn, UpdatedOn, CreatedBy, UpdatedBy, Value) SELECT Name, 'ALL','ALL','ALL','ALL', GETDATE(), GETDATE(), 'system', 'system', DefaultValue from XFM_PARAMETERS_DEFAULTS  WHERE NOT EXISTS ( SELECT * FROM XFM_PARAMETERS WHERE Name = ParameterName );

Note

• Ensure that no ofmserver.exe processes are running before switching the script engine.
• After switching, launch the HFM application to proceed.

Thank you!

Created on Aug 10, 2025

Data Integration Pipeline Extended to Account Reconciliation

From Aug 2025 monthly patch release, the Pipeline in Data Integration is now available to Account Reconciliation environments.  The Pipeline is used to orchestrate a series of routine tasks within Cloud EPM Platform as a single process.

Below is the sample example of Pipeline in ARCS where we are performing below tasks - 

• Open the Period
• Load Rate
• Import Pre-mapped Balance
• Create Reconciliation
• Close period

Below are the sample screen shots while creating job in pipeline -

New Pipeline job types specific to Account Reconciliation include:

• Create Reconciliation: (Reconciliation Compliance) Copies all selected profiles to a period and return success or failure status.
• Generate Report for Account Reconciliation: Generates either a single predefined Reconciliation Compliance report, predefined Transaction Matching report or a custom report.
• Import Attribute Values: Imports attribute values into an existing list attribute or group attribute. In Transaction Matching, only group attributes can be imported.
• Import Balances: (Reconciliation Compliance) Imports balances data using Data Integration from a previously created integration definition and returns a success or failure status.
• Import Pre-Mapped Balances: (Reconciliation Compliance) Imports pre-mapped balances and returns the success or failure status.
• Import Pre-Mapped Transactions: (Transaction Matching) Imports a file of pre-mapped transactions into Transaction Matching and returns the success or failure status.
• Import Rates: (Reconciliation Compliance) Imports rates for a particular period and rate type, and returns the success or failure status.
• Run Auto Match: (Transaction Matching) Runs the auto match process in Transaction Matching.
• Run Auto Alert: (Transaction Matching) Runs the auto alert process for the specified match type in Transaction Matching. This job processes the alert rules defined for the match type and then automatically creates alerts for unmatched transactions. Status of an Auto Alert job can be monitored through the Job History tab in Account Reconciliation.
• Set Period Status:  (Reconciliation Compliance) Changes the status of a period (open, closed, pending, locked) and returns the success or failure status. 

Applied to: ARCS

Business Benefit: 

The Pipeline functionality allows users to conduct a sequence of Account Reconciliation focused operations such as importing balances, pre-mapped balances and transactions, rates and so on, streamlined in one location and executed then in serial or parallel mode.

Updated on: Aug 02, 2025

New consolidation setting for Translation Rules to skip the Translation in FCCS

Consolidation Setting for Translation Rules

In Aug 2025 monthly release for FCCS, a new Consolidation Setting called Skip Translation Rules if Entity Currency Equals Parent Currency is now available for multiple-currency applications. When you enable this setting, the translation-based configurable calculation (insertion) rules are skipped during the translation process for those Entities whose Base Currency property matches their Parent’s Base Currency property. The rules include:

• FCCS_25_Before Foreign Exchange (FX) Calculations
• FCCS_30_After Opening Balance Carry Forward
• FCCS_40_Final_Calculations

By default, the Consolidation Setting is not enabled.

To manage consolidation settings:

1. On the Home page, click Application, then Consolidation Settings.
2. From the Setting Type dropdown, select the type of setting as Consolidation/Translation.

1. To enable or disable the setting (Skip Translation Rules if Entity Currency Equals Parent Currency), use the slider icon  next to the setting.
2. To save the setting selection, click Save. When you receive the saved confirmation message, click Close.

Applied to: FCCS

Business Benefit: 

This consolidation setting enables you to decide whether to skip these calculation rules, which improves overall Consolidation performance, in addition to making the translation process more efficient.

Updated on: Aug 2, 2025