Errors extracting from Essbase to flat file

New to ODI, I have the environment working - so I think
Using ODI 11.1.1.6.0 Studio, no web services, just the studio.
Essbase 9.3.3 is source
Target is flat file on C:\ drive of PC
PC is Windows 7, 32 bit
running an interface to extract from Essbase outline (metadata) to a flat file (csv) the integration step (4) "Extract Metadata" fails. The first 3 steps are sucessful (drop work table, create work table, begin essbase metadata extract).
The error messages in the 4th step are:
org.apache.bsf.BSFException: exception from Jython:
Traceback (most recent call last):
File "<string>", line 1, in <module>
 at com.hyperion.odi.essbase.ODIStagingLoader.loadData(Unknown Source)
 at com.hyperion.odi.essbase.AbstractEssbaseReader.extract(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)
com.hyperion.odi.essbase.ODIEssbaseException: com.hyperion.odi.essbase.ODIEssbaseException: Loading the data into staging area failed.
 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:561)
 at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:464)
 at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:2093)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:366)
 at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:216)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:300)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:292)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:855)
 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 1, in <module>
 at com.hyperion.odi.essbase.ODIStagingLoader.loadData(Unknown Source)
 at com.hyperion.odi.essbase.AbstractEssbaseReader.extract(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)
com.hyperion.odi.essbase.ODIEssbaseException: com.hyperion.odi.essbase.ODIEssbaseException: Loading the data into staging area failed.
 at org.python.core.PyException.fillInStackTrace(PyException.java:70)
 at java.lang.Throwable.<init>(Throwable.java:181)
 at java.lang.Exception.<init>(Exception.java:29)
 at java.lang.RuntimeException.<init>(RuntimeException.java:32)
 at org.python.core.PyException.<init>(PyException.java:46)
 at org.python.core.PyException.<init>(PyException.java:43)
 at org.python.core.Py.JavaError(Py.java:455)
 at org.python.core.Py.JavaError(Py.java:448)
 at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:177)
 at org.python.core.PyObject.__call__(PyObject.java:355)
 at org.python.core.PyMethod.__call__(PyMethod.java:215)
 at org.python.core.PyMethod.instancemethod___call__(PyMethod.java:221)
 at org.python.core.PyMethod.__call__(PyMethod.java:206)
 at org.python.core.PyObject.__call__(PyObject.java:381)
 at org.python.core.PyObject.__call__(PyObject.java:385)
 at org.python.pycode._pyx6.f$0(<string>:1)
 at org.python.pycode._pyx6.call_function(<string>)
 at org.python.core.PyTableCode.call(PyTableCode.java:165)
 at org.python.core.PyCode.call(PyCode.java:18)
 at org.python.core.Py.runCode(Py.java:1204)
 at org.python.core.Py.exec(Py.java:1248)
 at org.python.util.PythonInterpreter.exec(PythonInterpreter.java:172)
 at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:144)
 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:2472)
 at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:47)
 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:558)
 at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:464)
 at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:2093)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:366)
 at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:216)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:300)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:292)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:855)
 at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:126)
 at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:82)
 ... 1 more
Caused by: com.hyperion.odi.essbase.ODIEssbaseException: Loading the data into staging area failed.
 at com.hyperion.odi.essbase.ODIStagingLoader.loadData(Unknown Source)
 at com.hyperion.odi.essbase.AbstractEssbaseReader.extract(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:175)
 at org.python.core.PyObject.__call__(PyObject.java:355)
 at org.python.core.PyMethod.__call__(PyMethod.java:215)
 at org.python.core.PyMethod.instancemethod___call__(PyMethod.java:221)
 at org.python.core.PyMethod.__call__(PyMethod.java:206)
 at org.python.core.PyObject.__call__(PyObject.java:381)
 at org.python.core.PyObject.__call__(PyObject.java:385)
 at org.python.pycode._pyx6.f$0(<string>:1)
 at org.python.pycode._pyx6.call_function(<string>)
 at org.python.core.PyTableCode.call(PyTableCode.java:165)
 at org.python.core.PyCode.call(PyCode.java:18)
 at org.python.core.Py.runCode(Py.java:1204)
 at org.python.core.Py.exec(Py.java:1249)
 at org.python.util.PythonInterpreter.exec(PythonInterpreter.java:173)
 at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:144)
 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:561)
 at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:464)
 at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:2093)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:366)
 at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:216)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:300)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:292)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:855)
 at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:126)
 at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:83)
 ... 1 more
Caused by: java.sql.SQLException: ODI-40400: Invalid format description
 at com.sunopsis.jdbc.driver.file.impl.metadata.MetaDataExtractor.buildTableDescFromRequestSQLExceptionOnly(MetaDataExtractor.java:479)
 at com.sunopsis.jdbc.driver.file.SQLManager.buildCommand(SQLManager.java:437)
 at com.sunopsis.jdbc.driver.file.FileStatement.buildCommand(FileStatement.java:95)
 at com.sunopsis.jdbc.driver.file.FileStatement.executeQuery(FileStatement.java:62)
 ... 40 more
The "Code" tab of the errored session step has "stats=essbaseAppReader.extract()" in the Target Code, nothing in the Source Code
In the integration, the "Staging area different from Target" is NOT checked (flat file target).
The log file shows the outline was read and the members retreived, the log for this execution show:
2012-06-14 10:36:49,873 INFO [SimpleAsyncTaskExecutor-5]: ODI Hyperion Essbase Adapter Version 9.3.1.1
2012-06-14 10:36:49,873 INFO [SimpleAsyncTaskExecutor-5]: Connecting to Essbase application [A_USRDFD] on [prodbpm1]:[1423] using username [admin].
2012-06-14 10:36:52,275 INFO [SimpleAsyncTaskExecutor-5]: Successfully connected to the Essbase application.
2012-06-14 10:36:52,275 INFO [SimpleAsyncTaskExecutor-5]: Essbase Metadata extract LKM option ALIAS_TABLE = null
2012-06-14 10:36:52,275 INFO [SimpleAsyncTaskExecutor-5]: Essbase Metadata extract LKM option MEMBER_FILTER_CRITERIA = IDESCENDANTS
2012-06-14 10:36:52,275 WARN [SimpleAsyncTaskExecutor-5]: Invalid value specified [ ] for member filter value. Using default value [TC Codes].
2012-06-14 10:36:52,275 INFO [SimpleAsyncTaskExecutor-5]: Essbase Metadata extract LKM option MEMBER_FILTER_VALUE = TC Codes
2012-06-14 10:36:52,275 INFO [SimpleAsyncTaskExecutor-5]: Essbase Metadata extract LKM option DIMENSION = TC Codes
2012-06-14 10:36:52,322 INFO [SimpleAsyncTaskExecutor-5]: Executing essbase member selection to fetch the metadata
2012-06-14 10:36:52,572 INFO [SimpleAsyncTaskExecutor-5]: Total number of metadata records fetched from essbase : [574].
2012-06-14 10:36:52,572 DEBUG [SimpleAsyncTaskExecutor-5]: Constructing iterator for the extracted data
2012-06-14 10:36:52,572 INFO [SimpleAsyncTaskExecutor-5]: Loading the staging area with the extracted records
2012-06-14 10:36:52,572 INFO [SimpleAsyncTaskExecutor-5]: Logging out and disconnecting from the essbase application.
2012-06-14 10:49:45,408 INFO [SimpleAsyncTaskExecutor-6]: ODI Hyperion Essbase Adapter Version 9.3.1.1
2012-06-14 10:49:45,408 INFO [SimpleAsyncTaskExecutor-6]: Connecting to Essbase application [A_USRDFD] on [prodbpm1]:[1423] using username [admin].
2012-06-14 10:49:47,748 INFO [SimpleAsyncTaskExecutor-6]: Successfully connected to the Essbase application.
2012-06-14 10:49:47,748 INFO [SimpleAsyncTaskExecutor-6]: Essbase Metadata extract LKM option ALIAS_TABLE = null
2012-06-14 10:49:47,748 INFO [SimpleAsyncTaskExecutor-6]: Essbase Metadata extract LKM option MEMBER_FILTER_CRITERIA = IDESCENDANTS
2012-06-14 10:49:47,748 WARN [SimpleAsyncTaskExecutor-6]: Invalid value specified [ ] for member filter value. Using default value [TC Codes].
2012-06-14 10:49:47,748 INFO [SimpleAsyncTaskExecutor-6]: Essbase Metadata extract LKM option MEMBER_FILTER_VALUE = TC Codes
2012-06-14 10:49:47,748 INFO [SimpleAsyncTaskExecutor-6]: Essbase Metadata extract LKM option DIMENSION = TC Codes
2012-06-14 10:49:47,795 INFO [SimpleAsyncTaskExecutor-6]: Executing essbase member selection to fetch the metadata
2012-06-14 10:49:47,951 INFO [SimpleAsyncTaskExecutor-6]: Total number of metadata records fetched from essbase : [574].
2012-06-14 10:49:47,951 DEBUG [SimpleAsyncTaskExecutor-6]: Constructing iterator for the extracted data
2012-06-14 10:49:47,966 INFO [SimpleAsyncTaskExecutor-6]: Loading the staging area with the extracted records
2012-06-14 10:49:47,966 INFO [SimpleAsyncTaskExecutor-6]: Logging out and disconnecting from the essbase application.
Only the file name being written to in the Target exists, it is updated with the column headings:
C1_SORTID,C2_PARENTNAME,C3_MEMBERNAME,C4_ALIAS,C5_DATASTORAGE,C6_TWOPASSCALC,C7_CONSOLIDATION,C8_UDA,C9_FORMULA,C10_COMMENT
There are no other files in the the Target flat file folder
I did have to add a primary key to the target datastore, added as PK_Sortid on the "SortID" column in order to get the flow to run. The LKM used is "LKM Hyperion Essbase METADATA to SQL.GLOBAL", the CKM is "CKM SQL.GLOBAL" ( the only one showing from the drop down).
I don't know what else to check or change.
thanks

I think I saw somewhere in your post that Staging different from target is NOT checked, probably why you are getting lots of 'loading to staging area errors'. Your staging area has to be able to support relational operations i.e a relational database such as SQL Server or Oracle or the SUNOPSIS Memory Engine. In your interface make sure you check the staging differnet from target and for example select the SUNOPSIS Memory Engine as your staging area. Resave the interfece and re-run.

Similar Messages

How to extract data from Essbase to Flat File using ODI

Hi,
Anyone know how to extract data from Essbase to Flat File using ODI?
Thanks in advance.
Regards,
Sumardi

Hi,
Have you read through :-
Oracle Data Integrator Adapter for Hyperion Essbase Getting Started - http://download.oracle.com/docs/cd/E10530_01/doc/epm.931/odiess_getting_started.pdf
Oracle Data Integrator Adapter for Hyperion Essbase User's Guide - http://download.oracle.com/docs/cd/E10530_01/doc/epm.931/odiess_users.pdf
If you have read them and are still have a problem at what stage are you having the issues?
Cheers
John
http://john-goodwin.blogspot.com/

How to extract data From Hyperion Essbase to Flat Files

Hi ,
Can anyone tell me how to extract data from Hyperion essbase to Flat file(e.g. .csv , .txt ,...) or Oracle Table using ODI.
Regards,
Avneet

Hi sutirtha,
I have make one column as key column now i am getting this error,
org.apache.bsf.BSFException: exception from Jython:
Traceback (innermost last):
File "<string>", line 1, in ?
com.hyperion.odi.essbase.ODIEssbaseException: The number of columns returned by script [10] is less than the source data columns exposed [12]
at com.hyperion.odi.essbase.ODIEssbaseDataReader.getAppData(Unknown Source)
at com.hyperion.odi.essbase.AbstractEssbaseReader.extract(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
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._pyx7.f$0(<string>:1)
at org.python.pycode._pyx7.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.k.a(k.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSqlC.treatTaskTrt(SnpSessTaskSqlC.java)
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.k(e.java)
at com.sunopsis.dwg.cmd.g.A(g.java)
at com.sunopsis.dwg.cmd.e.run(e.java)
at java.lang.Thread.run(Unknown Source)
Caused by: com.hyperion.odi.essbase.ODIEssbaseException: The number of columns returned by script [10] is less than the source data columns exposed [12]
at com.hyperion.odi.essbase.wrapper.EssbaseReportDataIterator.validateColumns(Unknown Source)
at com.hyperion.odi.essbase.wrapper.EssbaseReportDataIterator.init(Unknown Source)
... 33 more
com.hyperion.odi.essbase.ODIEssbaseException: com.hyperion.odi.essbase.ODIEssbaseException: The number of columns returned by script [10] is less than the source data columns exposed [12]
at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
at com.sunopsis.dwg.codeinterpretor.k.a(k.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSqlC.treatTaskTrt(SnpSessTaskSqlC.java)
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.k(e.java)
at com.sunopsis.dwg.cmd.g.A(g.java)
at com.sunopsis.dwg.cmd.e.run(e.java)
at java.lang.Thread.run(Unknown Source)

Data Extraction or IDOC to flat file

hi,
I have a project to create a flat file from SAP, for an external legacy system. There are 3 requirement.
What approach should I take. Simple data extraction OR Idoc to flat file.
There are 4 requirements:
1. first time extract all data.
2. on subsequent run, extract only changed & new records
3. if in SAP table, a record is deleted, then marked deleted in flat file.
What approach should I take if I use data extraction.
Thanks.

I read your question, my first thought would be to look at where the data is going?
What are the data requirements of the legacy system. IDOCs can speed up the development related to pushing the data out from SAP. Using ALE and change pointers you can automatically pass out the delta with a limited amount of development.
However, the receiving system then needs to parse the IDOC data. depending on the IDOC you are working with this can be a challenge especially if the legacy developer doesn't get IDOCs.
Sometimes its easier to collect and write the data from SAP using "simple data extraction". The data is more readily organized into a format the receiving system is expecting.
You can also pass the idoc to a middleware maping application if one is available and do the SAP to legacy mapping there.
Cheers

Error message while uploading the flat file

Hi Experts,
I am getting the error message while uploading the flat file.
Message class: MG
Number: 147
The message is: Several descriptions exist for the language JA.
Please guide me why this error is occuring.
Regards
Akshay

hi,
how are you uploading the file and where ?
u can use open dataset , read dataset or gui_upload
check this link
http://help.sap.com/saphelp_nw04/helpdata/en/c8/e92637c2cbf357e10000009b38f936/frameset.htm

Export security-Info from planning to flat file

In planning there's the possibility of importing security information (assignedaccess) by the utility ImportSecurity.exe. Is there the possibility of exporting this information (e.g. access todimensions or forms) from planning to flat file. Note: In shared services there's another utility for import andexport of provisioning information (command-line tool) but thisdoesn't comprise import/export of security info of anapplication. RegardsGeri

Hello Geri, Currently, Planning 3.5.1 does not have any utility to export security out of planning. What you can do is this that generated PDF files through the application itself and then convert it in to text files and so on to load security via importsecurity.exe. Thanks, Scorpio

Extraction of procedure from DB to flat file

I have recently moved from using Informix to Oracle and I am trying to find a way to extract a procedure from the Oracle database to a flat file on my system. Informix has utility dbschema which allowed me to do that, what does Oracle have that can do the same thing.
Thanks,
Bret.

Bret,
You can do the same using SQL*PLUS. To output a stored procedure, function or package to a flat file, you will have to query the user_source view. You need to know the procedure name.
These are the steps:
1) Log in to SQL*PLUS
2) Issue the following statement:
SET HEADING OFF
SET FEEDBACK OFF
spool file_name
SELECT text from user_source
WHERE name = 'PROCEDURE_NAME';
spool off
where file_name is the output file name the source code will be generated into. PROCEDURE_NAME is the name of the procedure, function or package.
NOTE: The name of the procedure must be in upper case.
Regards,
John

Error Loading data from oracle to flat file in oracle data integrator

Hi All,
I m trying to load data from oracle database to flat file.But I am getting the error at step "Insert new row"(integration)
Error Message is:
7000 : null : com.sunopsis.jdbc.driver.file.b.i
com.sunopsis.jdbc.driver.file.b.i
     at com.sunopsis.jdbc.driver.file.b.d.setDate(d.java)
     at com.sunopsis.sql.SnpsQuery.updateExecStatement(SnpsQuery.java)
     at com.sunopsis.sql.SnpsQuery.addBatch(SnpsQuery.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execCollOrders(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSqlI.treatTaskTrt(SnpSessTaskSqlI.java)
     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.g.y(g.java)
     at com.sunopsis.dwg.cmd.e.run(e.java)
     at java.lang.Thread.run(Unknown Source)
I m nt able to find out the exact reason.Can anyone help me in that.

yes...I got the mistake which i was doing.Actually the target file data type should be string and I was defined it diffrent for each column.
When I chnged the data type to string,data get loaded to target table.
Thanks for your reply.

How to Extract data to a Flat File?

Hello,
Im using OWB 10g and Oracle 9.2 version of database. I want to know the complete steps of creating the flat file as my target module. I need to extract the data (source) from the oracle tables and load it into the flat files. Pls let me know your suggestions. Pls note except the flat files, I do not have any oracle tables as my targets.
Thanks,
Kishan

Hi, here's an excerpt from some notes I wrote a few months ago, they shpoud be clear enough.
0) the file will be created on the server using the utl_file package. So the path where the file will be created must be added to the utl_file_dir Oracle Server parameter. Request your DBA to complete this step.
-In OWB client:
1) create a file location (or use existing one) under "Files/Locations" in project tree
2) create a new Flat File module (or use existing one) under "Files" ; associate it with the desired location (not really necessary)
3) create a new mapping in an Oracle module
4) add to mapping a table operator bound to the table to dump
5) add to mapping un unbound Flat File (FF) Operator, give it a meaningful name
6) drag the desired attributes from table to FF Operator. This will instruct OWB to feed the file with comma-separated values from the source table using the utl_file package. Be careful to format attributes accordingly to the format you want.
7) reconcile outbound the FF Operator, creating a new flat file in the module created during step 2
8) close mapping, right-click on it an from menu "Configure..."->"Sources&Targets"-><YOURTARGETFILE>, specify the desired output location and the output file name
9) Open deployment manager and connect to runtime rep. If the FF location is new, register it by right-clicking+menu "Register" and specify parameters: operating system user/passawrd of the DB server, host and path where the file will be stored (must be the same added to utl_file_dir). ATTENTION: path info is stored in the generated mapping so be sure to redeploy mappings if changes occur
10) deploy mapping, test execution
11) OPTIONAL you can specify a different delimiter (TAB,etc) for the target file directly in its editor. But be careful then to reconcile inbound the FF op in the mapping before deploying.
Cheers, Antonio

Error Loading Data into a flat file

I am recieving the following error when loading data into a flat file from a flat file. SQL 2005 is my back end DB. If I cut the file iin half approx 500K rows my ODI interface works fine. Not sure what to look at.. I rebuit the interface which before was just dying giving no error and now I am getting this.
Thanks
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.g.y(g.java)
     at com.sunopsis.dwg.cmd.e.run(e.java)
     at java.lang.Thread.run(Unknown Source)

Figured it out, found similar post that stated changing the HEAP size
Increase the page size in odiparams.bat in the bin folder and restart Designer.
For eg:
set ODI_INIT_HEAP=128m
set ODI_MAX_HEAP=1024m

'File is not open' error when running DTP for flat file upload in BI

Dear Sir,
We are trying to upload master data from flat file for which we have
created respective DTPs. When we are running the DTPs we are getting an
error saying 'The file '&&filepath&&' is not open'. We also checked
that the file is not open, but still we are getting this error. Could
anyone please suggest what we have to do to solve this problem.
Many Thanks
Narendra

Hi,
I am currently facing the same error "Error in Source system". "The file 'path' is not open".
Could you please let me know how you resolved this issue.
many thanks.
Regards,
Madhusudhan

Error while loading data through flat files

Hi,
I am laoding data through flat files
I loaded the data in development & then transported it to Quality system for doing Integration testing & loaded the data in Quality system & data loading was successful
But we do the regression testing in one more Quality system where the objects get transported from Quality system ,here when I try to the load the data to any of the cube in this system I am getting the following error
Error 'The argument 'US' cannot be interpreted as a number' on assignment field /BIC/ZIFBCOCTR record 1 value US
Generally we get this error when there is the data of one field is going to the other field
But one thing I am unable to understand is it was working fine in the Quality system and all the objects got transported from Quality to Regression testing system
Could any one help me out
Thanks
Maya

Hi,
Can you please cross check the file structure and the transfer structure.
Cheers,
Malli....

Extracting transaction data using flat files in nw2004s

Hi BW Gurus,
I am trying to load the Infocube from flat file. flat file is in csv format with comma diliminator, when i am loading the datasource with the flat file. flat file is actually consist of 20 columns with column headings, 5 columns has no data it consist only headings.
When I am loading data to the datasource, it is reading only 15 columns which is having values, I tried to enter the values in the empty column and extracted to datasource still it is not uploading that values.
Please help me.
Thanking you,
Ravi

Hi
Please check your transfer structure should match with your flat file.
Order of fields in your flat file should be in the same order as the transfer structure..
Hope it helps you...
Teja

Getting error while reading the positional flat files

Hi,
I have a requirement to read a Positional Flat file and convert into XML through oracle B2B. I have created a positional flat file .ecs, XSD and parser .ecs file using the blog http://anuj-dwivedi.blogspot.in/2011/10/handling-positionaldelimited-flat-files.html and updated the same in the server.
I have created a agreemnt for inbound scenario But while testing the inbound scenario i am getting an error in B2B as :
Error Code     B2B-50083
Error Description     Machine Info: Description: Document protocol identification error.
Error Level     ERROR_LEVEL_COLLABORATION
Error Severity     ERROR
Error Text     Document protocol identification error.
I have tried all the possible ways but getting the same error.
Please guide me to overcome this.
Thanks,
Nishanth

Nishanth,
Have you followed the step#2 correctly -
Copying the parser ecs in the installation directory and adding an entry in XERegistry.xml (of all machines if domain is spanned across multiple machines)
Also make sure that you have provided Identification Value, Identification Start Position and Identification End Position correctly in Document Defintion. Please remember that start position starts from 1 (instead of 0)
Regards,
Anuj

Error in Data upload through Flat files in SAP BPC

Hi,
we are trying to upload data from flat files in SAP BPC but an error is coming viz Object reference not set to an instance of an object .

Hi,
Can you please cross check the file structure and the transfer structure.
Cheers,
Malli....

Errors extracting from Essbase to flat file

Similar Messages

Maybe you are looking for