Oracle Integration Cloud - Business Rules in Planning Cloud

 If you want to automate business rules to execute in sequence or part of any process, you can use Oracle Integration Cloud.

For example: If you want to execute business rule to load data every month, based on the substitution variable and also wants to run calculation using another business rule. you can do all these steps using OIC, where you can pull substitution variable, execute business rules and good part is, if any step is failed, you will get notification with email, which is not available in general scheduling options.

I will try to document and update in next posts about OIC Automation, this is mainly about PBCS, FCCS.

Thanks,

Mady

Event Scripts in FDMEE

 Event Scripts in FDMEE

Event Scripts, located in the Script Editor within FDMEE, are used to execute a task when certain events are carried out during the data load process. Each of the Event Scripts are customizable – users can use the scripts to perform a wide variety of tasks, such as send emails, run calculations, or execute a consolidation. There are nine different events and users can run the scripts before or after the event is executed, which makes a total of eighteen Event Scripts. The nine types of events are: Import, Calculate, ProcLogicGrp, ProcMap, Validate, ExportToDat, Load, Consolidate, and Check, with a Bef and Aft for each event. To create an Event Script, Select the type of event, whether the script will be run before or after that event, and click ‘New’.

Here are descriptions of each of the Event Scripts:

BefImport – This script runs before the Location is processed.

AftImport – Runs after the Location is processed and the data table is populated.

BefCalculate – Only for a Validation run and takes place before the Validation.

AftCalculate – Only for a Validation run and takes place after the Validation.

BefProcLogicGrp – Runs before Logic Accounts are processed.

AftProcLogicGrp – Runs after Logic Accounts are processed.

BefProcMap – Called before the mapping process for the data table begins.

AftProcMap – Called after the mapping process for the data table has finished.

BefValidate – Checks if the mapping process has been completed.

AftValidate – Runs after the BefValidate Script.

BefExportToDat – Called before the data file is created for Export.

AftExportToDat – Called after the data file is created for Export.

BefLoad – Called before the data file is loaded to the Target Application.

AftLoad – Called after the data file is loaded to the Target Application.

BefConsolidate – Called when a check rule is included in the location that is being processed. Can only be used if the Target Application is Hyperion Financial Management or Essbase.

AftConsolidate – Runs after the BefConsolidate Script.

BefCheck – Runs before the Check Rule.

AftCheck – Runs after the Check Rule.

One final thing, when creating an Event Script, make sure that there is a Script Folder within the Application Root Folder. Event Scripts are application specific, so they need to be kept in the Script Folder for the corresponding Application’s folder system.

Collected from https://hollandparker.com/blog/2016/04/21/event-scripts-in-fdmee/

Thanks,

Mady

Data Management - same combination of all dimensions showing different data

 In Data Management, we found one issue today.

For same combination of all dimensions we were getting different numbers. for example, Dec-23 of all dimensions of same combination getting multiple records with different data. When we are checking other months with same combination, we were getting only one record. 

We verified Source file records, cleared data and loaded again, still same issue.

Loaded only one records for Dec-23, still getting 12-15 records with different data.

We didn't understand the issue, so we did  same steps in other environment with same source, there we were getting only one record.

So, Finally after checking all steps one by one we found one thing.

We verified Period Mapping where prior period key mentioned as 30-11-2022(by mistake) instead of 30-11-2023

Once we are update with this prior period key, we got results as expected only one record.

Thanks,

Mady

Data Management - Error in initializeFsGLCloudSource

In Data Management, we enabled drill through option and we were using that option using forms, smartview in our demo app. Drill through we are using to connect to ERP Cloud demo app, to check drill though. But ERP Team refreshed app and given another url (for example changed from DEV to Test URL)

Now, We updated Source System with URL, username and password. Test connection is successful.

But in Target application, we tried to refresh members that is also failed, 

2023-08-24 05:52:47,534 INFO  [AIF]: getOlapserver() :: <Essbase Server Host:port> = XXX.oracleoutsourcing.com:11448

2023-08-24 05:52:47,534 INFO  [AIF]: ExtractCubeMembers:Error::Cannot get olap application Information. Essbase Error(1051030): Application XXXXXXX does not exist

So, I tried to Initialize, there also it is giving error.

Log file:
2023-08-23 18:07:47,983 ERROR [AIF]: Error in initializeFsGLCloudSource.
2023-08-23 18:07:47,984 FATAL [AIF]: Error in initializeFsGLCloudSource
Traceback (most recent call last):
    File "<string>", line 83, in initializeFsGLCloudSource
    File "<string>", line 487, in executeFusionService
Exception: java.lang.Exception: Unable to find text data file for essRequestId: xxxxxxxx

When I am searching with Error in initializeFsGLCloudSource, I found below article in Oracle support.

Fusion GL Source System Initialization Fails with the "Error: java.lang.Exception: Unable to find txt data file for essRequestId: xxxxx" in EPM Cloud Data Management (Doc ID 2587854.1)

In this article it is saying to search for Chart of Accounts in scheduled processes and submit the cube once again. So ERP Team submitted one job Created General Ledger XXXXXX Cube, where we can see our Target application as cube. Once that job submitted, I did Initialize, it is completed. Refresh members also done. Drill through working fine using forms and smartview.

Thanks,

Mady

Data Export to File using Data Management - In old versions

 To export data to file using data management, we can follow below steps

Select in Target as Custom Application, and select Data Export to File

Once you select Data Export to File, it will ask for Data export file name, browse that file in which format you want export.

All Dimensions list will be shown as mentioned in the list. Check Target Dimension Class will be as Generic and update Account and remaining as UD1, UD2 etc.

Once we are done with other settings of how we need file, we can run the data load rule.

We will output with name whatever we mentioned in the settings.

we can validate the file by downloading it to local.

Thanks,

Mady

Data Management - Errors and solutions

 In Data Management, we will face below errors frequently. Check the errors, and find the solutions to check to trace the error and resolve the same. We may have different solutions, which I found is the below:

Data Management Issues:

BLANK:

Is log file mentioned as BLANK, check Import format File Type and Delimited. Check file and set as per file.

Amount=NN

Is log file mentioned as Amount=NN, NN - stands for Non-Numeric

check Import Format - File Type. Depends on file we can change this option form Numeric, All data type, Multi-column data etc.

Error: 3303

If log file mentioned as Error: 3303, If so, member mentioined is not there in outline or might be mentioned in Mapping.

Unmapped Dimensions in the file

Check the Workbench tab for validation error where you can find which members mapping is not correct.

Error Invalid Period:

Check the period mapping in file and data mapping, import format and also if period name in file is different than application, we need to check period mapping.

If the period is not picking up from POV, we need to setup file with period and year, depends on period format we can select explicit option to pick the period mapping with same format of file from Period Mapping - Source Mapping.

Thanks

Mady

EPBCS - Data Management - Period Mapping update

 In Data Management Period Mapping, we don't have option to update bulk periods at a time. We have export option to export to excel but do not have option to import. Manually we have to update each period.

But we can do bulk update using Migration option in EPBCS, may be in On-premise also. I do not have On-premise environment to check that. So, steps to update in EPBCS as follows:

Go to Tools à Migration

Click on Data Management in the list

In Artifacts list, Select Global Setup Artifacts, Uncheck and select Period Mapping only.

Before this step, Try to add at least 2 periods in the list.

Click on Export to complete the migration.

Unzip the exported file, and go to FDMEE-FDM Enterprise Edition à resource à Global Setup Artifacts à Period Mapping.xml

Open Period Mapping.xml file in excel, It will list data as below

Use EOMONTH(date,0) function to get last date of each month. Drag the list up to year which we have in the application. we can prepare sheet in excel easily. 

Bind back zip file with Period Mapping.xml file. Upload the file and import the same.

You can find the periods updated in the Data Management.

Thanks,

Mady