FDM Error : Loading ERP Data

Quick Solution::
Add Application Root Folder and Save.

Application Root

Read below for Problem Summary.

Importing ERP data into Target Hyperion Planning or Essbase Application is primary usage of FDM Application setup.

There are sometimes small elements which we might ignore, and lead to unprecedented errors. One such error occurs, while importing Data after initializing the Source system.

This error comes after ODI fetches data from source system, and puts this data in the FDM Staging Table.

The error is because of the absence of FDM Application root directory, which has inbox/outbox folders, which will be used to store the Flat file to be imported into Essbase.

Error Summary:

FDMEE Data extraction Error
The Value for Profile option ‘PROFILE_APP_ROOT_DIRECTORY’ is invalid: NULL 

‘PROFILE_APP_ROOT_DIRECTORY’ is invalid: NULL, 683 FATAL [AIF]: Error in COMM Pre Import Data

Additional ODI Logs:
[2015-10-14T19:47:38.082+04:00] [EPMServer0] [ERROR] [ODI-1134] [] [tid: 125] [userId: <anonymous>] [ecid: 0000L1b2G4EEOP15zvg8yW1M6bzc0004dm,1:24283] [APP: oraclediagent] Agent OracleDIAgent encountered an error: ODI-1217: Session COMM_LOAD_BALANCES (37501) fails with return code 7000. Caused by: ODI-1226: Step FAILED – Invalid Source System fails after 1 attempt(s).[[
ODI-1217: Session COMM_LOAD_BALANCES (37501) fails with return code 7000.
ODI-1226: Step FAILED – Invalid Source System fails after 1 attempt(s).
ODI-1232: Procedure COMM Finalize Process execution fails.
Caused By: org.apache.bsf.BSFException: exception from Jython:
Traceback (most recent call last):
File “<string>”, line 13, in <module>
File “<string>”, line 162, in finalizeProcess
RuntimeError: ODI-1226: Step COMM Pre Import Data fails after 1 attempt(s).
ODI-1232: Procedure COMM Pre Import Data execution fails.
Caused By: org.apache.bsf.BSFException: exception from Jython:
Traceback (most recent call last):
File “<string>”, line 7, in <module>
File “<string>”, line 4578, in preImportData
File “<string>”, line 455, in executeScript
File “<string>”, line 394, in doScriptInit
RuntimeError: The value for Profile Option ‘PROFILE_APP_ROOT_DIRECTORY’ is invalid: NULL

AIF Web Log

[2015-10-12T11:42:03.746+04:00] [EPMServer0] [ERROR] [] [oracle.apps.erpi.model] [tid: 22] [userId: <anonymous>] [ecid: 0058UDr854hEOP15zvg8yW0005Ji0001XQ,0:1] [APP: AIF#11.1.2.0] [SRC_CLASS: com.hyperion.aif.util.RegistryUtil] [SRC_METHOD: getProductParams] An unexpected error has occurred.[[
oracle.epm.fm.common.exception.HFMException: EPMHFM-65536: An unexpected error has occurred.

Log pointing to the exact Exception:

 

ODI-1226: Step COMM Export Data fails after 1 attempt(s).
ODI-1232: Procedure COMM Export Data execution fails.
Caused By: org.apache.bsf.BSFException: exception from Jython:
Traceback (most recent call last):
File “<string>”, line 9, in <module>
File “<string>”, line 5040, in exportData
RuntimeError: java.io.IOException: No such file or directory

at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.execInBSFEngine(SnpScriptingInterpretor.java:322)
at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.exec(SnpScriptingInterpretor.java:170)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java:2473)
at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:48)
at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:1)
at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:50)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2913)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2625)
at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:580)
at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:468)
at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:2128)
at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1931)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$2.doAction(StartScenRequestProcessor.java:580)
at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:216)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.doProcessStartScenTask(StartScenRequestProcessor.java:513)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$StartScenTask.doExecute(StartScenRequestProcessor.java:1073)
at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:126)
at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:83)
at java.lang.Thread.run(Thread.java:662)
Caused by: Traceback (most recent call last):
File “<string>”, line 9, in <module>
File “<string>”, line 5040, in exportData
RuntimeError: java.io.IOException: No such file or directory

Advertisements

Posted on March 15, 2016, in FDM, Oracle Essbase, Oracle Hyperion Planning. Bookmark the permalink. Leave a comment.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: