Error when loading metadata into Custom Dimension(Planning)

Hi all,
We are using text files to load metadata into Hyperion Planning. This works fine for standard dimensions. But it doesn't seem to work well for custom dimensions.
I have reversed the model for the custom dimension, and also set the staging area as different from target.
Error:
com.hyperion.planning.InvalidMemberException: The member <membername> does not exist or you do not have access to it.
How does ODI realize a custom dimension load(as opposed to a standard dimension load)?
Thanks.

Hi,
Please try this
1. Go to Designer and select the Interface
2. Go to Flow tab
3. Select your target
4. Go to target properties windows
5. Now you can find option called "LOAD_ORDER_BY_INPUT" and "SORT_PARENT_CHILE"
6. Please select the different values "YES" or "NO" and try to load the values.
Thanks and Regards,
Vikram.

Similar Messages

  • Alias when loading metadata into Planning

    Hi all,
    We are trying to load metadata into Planning 11.1.2 using the outline load utility. We have the dimension name, parent, data storage, and alias.
    We get this error when doing the dry run(with /N):
    Unrecognized Column header value: Alias
    Does this mean we cannot load aliases using the outline load utility? Unfortunately, all the examples in the hp-admin document only talks about loading data. Where in the 'cmd' do we specify that we are loading metadata(and not data itself)?
    Thanks,
    Sujani

    If you are loading to the default alias table the header should be Alias: Default
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Error when loading data into Planning

    Unable to load data into planning 11.1.2.3.200 using ODI 11.1.1.7
    Please find the errors from below logs:
    INFO  [SimpleAsyncTaskExecutor-2]: Oracle Data Integrator Adapter for Hyperion Planning
    INFO  [SimpleAsyncTaskExecutor-2]: Connecting to planning application [xxxxxxx] on [xxxxxxxxxxx]:[xxxx] using username [admin].
    INFO  [SimpleAsyncTaskExecutor-2]: Successfully connected to the planning application.
    INFO  [SimpleAsyncTaskExecutor-2]: The load options for the planning load are
      Dimension Name: Account Sort Parent Child : false
      Load Order By Input : false
      Refresh Database : false
    INFO  [SimpleAsyncTaskExecutor-2]: Begining the load process.
    DEBUG [SimpleAsyncTaskExecutor-2]: Number of columns in the source result set does not  match the number of planning target columns.
    INFO  [SimpleAsyncTaskExecutor-2]: Load type is [Load dimension member].
    ERROR [SimpleAsyncTaskExecutor-2]: Record [[A603010, null, null, null, null, null, null, null, null, null, null, null, xxxxx, -100, F3E0,C011,E7172_93275,FY17,Stage 1,Current Service Level,Jul, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null]] was rejected by the Planning Server.
    ERROR [SimpleAsyncTaskExecutor-2]: Record [[A601060, null, null, null, null, null, null, null, null, null, null, null, xxxxx, -250, F3E0,C011,E7172_93275,FY17,Stage 1,Current Service Level,Jul, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null]] was rejected by the Planning Server.
    log.err
    Account,Data Load Cube Name,Budget,Point-of-View,Error_Reason
    A603010,xxxxx,-100,F3E0,C011,E7172_93275,FY17,Stage 1,Current Service Level,Jul,Cannot load dimension member, error message is: RemoteException occurred in server thread; nested exception is:
      java.rmi.UnmarshalException: unrecognized method hash: method not supported by remote object
    A601060,xxxxx,-250,F3E0,C011,E7172_93275,FY17,Stage 1,Current Service Level,Jul,Cannot load dimension member, error message is: RemoteException occurred in server thread; nested exception is:
      java.rmi.UnmarshalException: unrecognized method hash: method not supported by remote object
    FDMEE log:
    ERROR [AIF]: Error: No records exist for Period 'Pd 2 - 2014-08-01'
    ERROR [AIF]: Error: No records exist for Period 'Pd 3 - 2014-09-01'
    FDMEE Logging Level is set to 5

    Are you sure that you haven't got Planning 11.1.2.3.500 in your environment? This sounds spookily similar to the issue described in note 1678759.1 which was seen after applying Planning 11.1.2.3.500. If it's definitely Planning 11.1.2.3.500 is there any chance that someone has applied ODI patch 18687916 to the ODI home (C:\Oracle\Middleware\odi)?
    If you /*are*/ running Planning 11.1.2.3.500 then you might need to apply patch 18687916 to C:\Oracle\Middleware\odi - you might need note 1683307.1 to take some of the pain out of applying this patch though.
    Given the error that you're seeing though there's a mismatch in versions of JAR files between ODI and the Planning server somewhere.
    Regards
    Craig

  • Error while loading metadata into planning using ODI

    Hi John,
    While trying toload members into planning using ODI the following error occurred. Please suggest
    java.lang.Exception
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
         at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand(DwgCommandSession.java)
         at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
         at com.sunopsis.dwg.cmd.e.i(e.java)
         at com.sunopsis.dwg.cmd.h.y(h.java)
         at com.sunopsis.dwg.cmd.e.run(e.java)
         at java.lang.Thread.run(Unknown Source)

    Hi John,
    While trying toload members into planning using ODI the following error occurred. Please suggest
    java.lang.Exception
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
         at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand(DwgCommandSession.java)
         at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
         at com.sunopsis.dwg.cmd.e.i(e.java)
         at com.sunopsis.dwg.cmd.h.y(h.java)
         at com.sunopsis.dwg.cmd.e.run(e.java)
         at java.lang.Thread.run(Unknown Source)

  • Error when Loading Metadata for IDOC Adapter

    Everybody,
    I know this should be pretty straight forward and that there are a few posts about it.  But following the Demo 3.0 guide and the posts I can't seem to load the data into the IDOC Adapter.  I did every step in the guide and when I try to execute IDX2 for the source port I previously created I get the error "No RFC Destination is maintained  for the port".
    Following the guide I have my XI host
    ID:ABC
    Instance:01
    Client:700
    Executed IDX1 and got port SAPABC_107 with RFC Dest-ABC_107, which I defined previously with transaction sm59 and the test came back ok.
    When I try to execute IDX2 I get the error message...
    What am I missing ?????
    Thanks!
    Diego

    Everything was setup before (by following the XI 3.0 Demo guide) here are the steps I did:
    1. Setup an RFC R/3 Destination on my client 107 (American Airlines) to client 700 (my XI): ABC_700
    2. Setup an RFC R/3 Destination on my client 700 to client 107: ABC_107
    3. Setup the IDOC processing port "SAPABC" on client 107 with RFC Destination ABC_700.
    4. Define partner type LS for logical system ABCCLNT105 (Airline Lufthansa)
    5. Define partner type LS for logical system ABCCLNT700 (XI)
    6. Specified the ALE distribution model in client 107.
    7. Execute IDX1, I input the SAPABC port created in step 3, input the client number 107 and the RFC destination ABC_107 created in step 2 and save.  The result is port SAPABC_107.
    AND..!! where the error occurs:
    8. Execute IDX2 input port SAPABC_107 and idoc type and get the error message "No RFC Destination is maintain for SAPABC_107"
    Any ideas !?
    Thanks
    D
    The client 107 represents the Airline American Airlines and has a R/3 RFC Destination to client 700, my XI.  The same way my XI has an R/3 RFC Destination to client 107.

  • ABAP short dump when loading data into Infocube

    Hello All,
    I am getting an ABAP short dump error when loading data into Infocube. I tried to load data from PSA and ODS.
    I ran the code to compress the Infocube, no improvement still getting the same error.
    Error Analysis:
    A raise statement in the program "SAPLRSDU_PART" raised in the exception.
    Internal Notes:
    The termination occured in the function "ab_i fune" of the SAP Basis system. Specifically in the line 2316 of the module "//bas/620/src/krn/runt/abfunc. C#18".
    The internal operation just processed is "FUNE"
    Advance thanks !!!
    Siv

    Hello Siv,
    try to run program SAP_DROP_EMPTY_FPARTITIONS to display existing partitions. Then compare it to the number of uncompressed requests. Maybe there's a mismatch.
    SAP notes that might help: 385163, 590370
    Regards,
    Marc
    SAP NetWeaver RIG, US BI

  • ODI Error when trying to Load Metadata into Essbase

    Hi - I get the following error when I try to Load Metadata into Essbase.
    org.apache.bsf.BSFException: exception from Jython:
    Traceback (innermost last):
    File "<string>", line 23, in ?
    com.hyperion.odi.essbase.ODIEssbaseException: Cannot build dimension. Essbase Error(1030100): Cannot open file: [D:\Hyperion\HYPERION_ODI_FILES\MGD\SCEN.err]
         at com.hyperion.odi.essbase.ODIEssbaseMetaWriter.loadData(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java)
         at org.python.core.PyMethod.__call__(PyMethod.java)
         at org.python.core.PyObject.__call__(PyObject.java)
         at org.python.core.PyInstance.invoke(PyInstance.java)
         at org.python.pycode._pyx1.f$0(<string>:23)
         at org.python.pycode._pyx1.call_function(<string>)
         at org.python.core.PyTableCode.call(PyTableCode.java)
         at org.python.core.PyCode.call(PyCode.java)
         at org.python.core.Py.runCode(Py.java)
         at org.python.core.Py.exec(Py.java)
         at org.python.util.PythonInterpreter.exec(PythonInterpreter.java)
         at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:144)
         at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.execInBSFEngine(SnpScriptingInterpretor.java:345)
         at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.exec(SnpScriptingInterpretor.java:169)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java:2375)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java:1616)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java:1581)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java:2755)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSqlI.treatTaskTrt(SnpSessTaskSqlI.java:69)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2515)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:537)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:449)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1954)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:322)
         at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:224)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:246)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:237)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:794)
         at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:114)
         at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:83)
         at java.lang.Thread.run(Thread.java:662)
    Caused by: com.essbase.api.base.EssException: Cannot build dimension. Essbase Error(1030100): Cannot open file: [D:\Hyperion\HYPERION_ODI_FILES\MGD\SCEN.err]
         at com.essbase.server.framework.EssOrbPluginDirect.ex_olap(Unknown Source)
         at com.essbase.server.framework.EssOrbPluginDirect.essMainBuildDimension(Unknown Source)
         at com.essbase.api.session.EssOrbPlugin._invokeMainMethod(Unknown Source)
         at com.essbase.api.session.EssOrbPlugin._invokeMethod2(Unknown Source)
         at com.essbase.api.session.EssOrbPlugin._invokeMethod(Unknown Source)
         at com.essbase.server.framework.EssOrbPluginDirect._invokeProtected(Unknown Source)
         at com.essbase.api.session.EssOrbPluginEmbedded.invokeMethod(Unknown Source)
         at com.essbase.api.session.EssOrbPluginEmbedded.invokeMethod(Unknown Source)
         at com.essbase.api.session.EssOrbPlugin.essMainBuildDimension(Unknown Source)
         at com.essbase.api.datasource.EssCube.buildDimension(Unknown Source)
         at com.hyperion.odi.essbase.wrapper.EssbaseApplication.buildDimension(Unknown Source)
         at com.hyperion.odi.essbase.ODIEssbaseMetaWriter.loadData(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java)
         at org.python.core.PyMethod.__call__(PyMethod.java)
         at org.python.core.PyObject.__call__(PyObject.java)
         at org.python.core.PyInstance.invoke(PyInstance.java)
         at org.python.pycode._pyx1.f$0(<string>:23)
         at org.python.pycode._pyx1.call_function(<string>)
         at org.python.core.PyTableCode.call(PyTableCode.java)
         at org.python.core.PyCode.call(PyCode.java)
         at org.python.core.Py.runCode(Py.java)
         at org.python.core.Py.exec(Py.java)
         at org.python.util.PythonInterpreter.exec(PythonInterpreter.java)
         at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:144)
         at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.execInBSFEngine(SnpScriptingInterpretor.java:345)
         at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.exec(SnpScriptingInterpretor.java:169)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java:2374)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java:1615)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java:1580)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java:2755)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSqlI.treatTaskTrt(SnpSessTaskSqlI.java:68)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2515)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:534)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:449)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1954)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:322)
         at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:224)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:246)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:237)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:794)
         at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:114)
         at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:82)
         ... 1 more
    com.hyperion.odi.essbase.ODIEssbaseException: com.hyperion.odi.essbase.ODIEssbaseException: Cannot build dimension. Essbase Error(1030100): Cannot open file: [D:\Hyperion\HYPERION_ODI_FILES\MGD\SCEN.err]
         at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
         at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.execInBSFEngine(SnpScriptingInterpretor.java:345)
         at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.exec(SnpScriptingInterpretor.java:169)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java:2375)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java:1616)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java:1581)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java:2755)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSqlI.treatTaskTrt(SnpSessTaskSqlI.java:69)
         at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2515)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:537)
         at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:449)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1954)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:322)
         at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:224)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:246)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:237)
         at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:794)
         at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:114)
         at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:83)
         at java.lang.Thread.run(Thread.java:662)
    Any help on this greatly appreciated.
    Thanks
    Sundeep

    com.hyperion.odi.essbase.ODIEssbaseException: com.hyperion.odi.essbase.ODIEssbaseException: Cannot build dimension. Essbase Error(1030100): Cannot open file: [D:\Hyperion\HYPERION_ODI_FILES\MGD\SCEN.err]
    Does the folder D:\Hyperion\HYPERION_ODI_FILES\MGD exist
    Is there a lock on the SCEN.err file if it exists, can you delete it
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • ODI: Load metadata into EPMA ("non-classic") Planning app

    Hi all, I know about loading metadata to classic planning/essbase application, but tell me please if its possible to load metadata to non-classic planning app (I mean created in Architect (in application library) and see it in dimension library?
    maybe there is some workaround for this situation
    thanks in advance

    Version 11.1.1.0.0. We have successfullly used EPMA Interface Tables to manage our planning metdata. We went this direction to avoid introducting another ETL/ELT tool (ODI) into our clients infrastructure. At the time, we didn't realize that ODI was not supported for EPMA (only Classic). I'm thinking of logging an SR to confirm if this limitation will be addressed in a later version of planning. The EPMA administrators guide provided enough detail to help us get started with Interface tables. The one area that created an issue for us was how EPMA ordered the load of members in the EPMA Interface Hierarchy table. Parent members need to be loaded before children. If this ordering is not followed , you will get "Orphan" errors. We could not find a documented process to control the load order, so we need to devise a workaround. Our workaround involved creating a view against the EPMA Interface table to order the retrieval of members so that parents appeared before their children. The Oracle CONNECT BY clause works well to handle this requirement. To make this view visible to EPMA you'll need
    to replace the base hierarchy table with the view by updating the EPMA IM_DIMENSION table. EX:
    update IM_DIMENSION set C_HIERARCHY_TABLE_NAME = 'HS_Entity_Hierarchy_VW' where C_DIMENSION_NAME = 'Entity';
    Alternate hierarchies also require separate EPMA Import profiles. Since only one set of EPMA Interface tables can be used to load a single dimension, you'll need a process that does the following for each alternate hierarchy.
    1) Clear EPMA Interface Tables
    2) Load EPMA Interface Tables
    3) Execute EPMA Import Script
    Finally, it's not clear how the I_LOAD_ID column (i.e. load id) is initialized in EPMA Interface tables (by default it's NULL). A load id is somehow assigned each time a Import profile is executed. A load id can be used (among other critiera) to clear EPMA interface tables. However, when I execute a Import profile, EPMA did not assign a load id (I_LOAD_ID was still null). Not sure if I_LOAD_ID is user assigned and is static? Again, very little documentation on how to manage the load id (what is user defined verses what is managed by EPMA).
    Edited by: user486561 on Jul 18, 2009 10:44 AM

  • Can FDM be used to load Metadat into Planning 9 and 11

    Hi John,
    Can we use FDM to load Metadata into Planning versions 9 and 11.
    Looking forward for your response
    Thanks,
    Sravan

    Not that I am aware of, you can use it to load data into planning essbase database.
    You may read about FDM loading metadata in version 11 but this is using the ERP integrator which sits on top of ODI.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Unable to see IKM Hyperion to Planning when loading metadata from File/Tabl

    Hello,
    I am unable to view the IKM SQL to Hyperion Planning Knowledge Module in the flow tab. I reverse engineered the KM and I see the KM in my Project(Have only 1 project). I am trying to load metadata from file to planning and selected staging area different from target. I was able to reverse engineer the planning cube successfully to ODI Models.
    ODI Version: 11.1.1.6.3
    Planning Version: 11.1.2.2
    Any help will be appreciated.
    -Kash

    932916 wrote:
    Hello,
    I am unable to view the IKM SQL to Hyperion Planning Knowledge Module in the flow tab. I reverse engineered the KM and I see the KM in my Project(Have only 1 project). I am trying to load metadata from file to planning and selected staging area different from target. I was able to reverse engineer the planning cube successfully to ODI Models.
    What is your staging area pointing to ? Make sure it is pointing to a RDBMS schema or SUNOPSIS MEMORY
    ODI Version: 11.1.1.6.3
    Planning Version: 11.1.2.2
    Any help will be appreciated.
    -Kash

  • Loading metadata from Essbase to Planning.

    Hi,
    I want to know what are the methods to load metadata into planning from essbase cube. I tried outline extractor to make a csv file, then I've used ODI to reverse the file and create a datasource. Then I reversed the planning application, created the interface and mapped the dimensions. I have more dimensions in planning target than the file datasource and when I execute the interface I always having some problem.
    Do i need to create a sql table from the csv file and then reversed and map it to planning? Is there an easy way I can load the members without using ODI?
    Thanks in advance,
    -Hussain

    Hi John,
    I have tried the essbase to planning series. There were no errors in the operator but I dont see any members in planning after database refresh. I checked the log file and it says:
    2010-06-01 08:56:22,494 INFO [DwgCmdExecutionThread]: Oracle Data Integrator Adapter for Hyperion Planning - Release 9.3.1.1
    2010-06-01 08:56:22,494 INFO [DwgCmdExecutionThread]: Connecting to planning application [PLAN1] on [bms-pc]:[11333] using username [admin].
    2010-06-01 08:56:22,644 INFO [DwgCmdExecutionThread]: Successfully connected to the planning application.
    2010-06-01 08:56:22,654 INFO [DwgCmdExecutionThread]: The load options for the planning load are
         Dimension Name: Account Sort Parent Child : true
         Load Order By Input : false
         Refresh Database : false
    2010-06-01 08:56:22,694 INFO [DwgCmdExecutionThread]: Begining the load process.
    2010-06-01 08:56:22,704 DEBUG [DwgCmdExecutionThread]: **Number of columns in the source result set does not match the number of planning target columns.**
    2010-06-01 08:56:22,714 INFO [DwgCmdExecutionThread]: Load type is [Load dimension member].
    2010-06-01 08:56:22,714 INFO [DwgCmdExecutionThread]: Load process completed.
    The number of columns in the source result set does not match the number of target colums. I have more columns in planning than temp table.
    Thanks,
    Hussain

  • Bex Report Designer: Error while loading metadata

    hi experts,
    I am working with BI7 Bex Report Designer and we are using SP9. when i tried to load the Query in Report Designer its giving below error.
    Error while loading metadata.
    Check the Query and portal settings.(but the query is working fine in Analyzer).
    and its giving message class RSBOLAP, message number 018 and Description is java system error: incoming call is not authorized.
    when i double click the error its giving below error details.
    Diagnosis
    An error occurred in the BI components on the SAP J2EE Engine.
    System Response
    Procedure
    Contact your system administrator to have the error analyzed in detail.
    Procedure for System Administration
    Start the Visual Administrator, log on to the SAP J2EE Engine and choose "<J2EE_SID>" ->"Server" -> "Services" -> "Log Viewer".
    The file "defaultTrace.trc" includes detailed information about the error that occurred. In Windows, you can find this file in the Log Viewer under "Cluster <computer name>" -> "Server <server number>" -> "<drive>:\usr\sap\<SID>\JC<INSTANCE>\j2ee\cluster\server<NUMBER>\log". ". In Unix, the file is located under "/usr/sap/<SID>/JC<INSTANCE>/j2ee/cluster/server<NUMBER>/log".
    If the file does not include enough detail about the error, you can increase the log level to obtain more information. To do this, choose "<J2EE_SID>" -> "Server" -> "Services" -> "Log Configurator". On the "Locations" tab page, choose "com" -> "sap" -> "ip" -> "bi" -> "webapplications". Using the selection list on the right side of the screen, you can increase the log level, whereby "DEBUG" represents the log level with the most information. You can save your settings by choosing the "Save" icon. The change to the log level is active immediately. Once you have successfully analyzed the error, you should set the log level back to its default value using the appropriate pushbutton; continuous writing to the log file negatively affects the overall performance of the system.
    could you plz suggest me how to rectify the problem.
    regards
    vadlamudi

    Hi vadlamudi
    The error message RSBOLAP 018 means, that the ABAP stack can't communicate with the Java Stack.
    1) Please ensure, that the user, used for the Report Designer, is valid in the Portal too. Depending on the user management setup this means that there either needs to be the same user or an assigned user in the Portal.
    2) In case the user is valid, it means a basic misconfiguration according to note 937697. In this case please run the Support Desk Tool and ensure, that all checks are green. Please ensure, that the latest version of the Support Desk Tool is used.
    Regards,
    Janine

  • Error while load data into Essbase using ODI

    Hi ,
    I'm getting the following error while loading measures into Essbase using ODI, I used the same LOG nd Error file and file path for all my Dimensions , this worked well but not sure why this is not working for measures....need help.
    File "<string>", line 79, in ?
    com.hyperion.odi.common.ODIHAppException: c:/temp/Log1.log (No such file or directory)
    Thanks
    Venu

    Are you definitely running it against an agent where that path exists.
    Have you tried using a different location and filename, have you restarted the agent to make sure there is not a lock on the file.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Error when Writing Metadata to Files in Bridge (Mac) but not in Bridge (PC)

    We get an error when writing metadata to files in Bridge (Mac) but not in Bridge (PC). In the same drive and folder, the PC can successfully write a keyword to a file on the PC, where the Mac returns an error. I have researched this at the Adobe Knowledgebase, but their answer seemed to indicate it was a global issue, and we don't see that behavior on the PC.
    The client is a Mac of course, and the server volume is a Windows share volume. The Mac is bound to AD, and the domain\username and username formats have both been tried when logging in, but you receive the error in both.
    Any help would be appreciated.
    Thanks!
    Rich Oliver

    Hi, I'm having the same problem using FreeNAS (which uses Samba and Netatalk in the backend), but I tried with both AFP and SMB on Mavericks and Yosemite, I still have the same issue.  I think it might be a timing issue with how lightroom interact with a slower write delay using network shares.  I suggest you also chime into this thread:  Lightroom 5 can't write metadata to DNG files   I really hope this is resolved as this is impacting my productivity as I moved my workflow to my Macbook with a shared NAS.

  • Report Designer - Error when Loading Report

    Hi,
    We have created a report in Report Designer (7.0) and saved it. When we execute it runs fine. After closing the report and trying to reopen it, the report does not open. It gives an error "Error when Loading Report". Our BI frontend patch is 14.
    Did anyone encounter this issue and is there a solution to this.
    Thanks
    Hemant

    Hello,
    Please go to SE38 -> RS_REPORT_MAINTAIN,
    Type your report name, and DT als "Report Type".
    Goto edit mode, copy&paste this XML into txt file and send it to me ([email protected]). I will check whats going on with this report. Loading should be always possible.
    Regards, Karol Kalisz, BI Development

Maybe you are looking for