Extraction error in OrgChart 3.0 SP1

[Former Member]

Hi Experts,

We are implementing the OrgChart 3.0 SP1 for staged environment. after configuring the extractor when I run the extract it shows the following error.....and extraction is fail.

4167. 15 Jul 2011 11:24:17 ERROR com.nakisa.Logger - SAPExtractorProcessor.processOutputTables() : Table source 'PA0001' not found in output tables

Can anyone help to resolve this?

Thanks

Dave

[Former Member]

Hi Dave,

Just as an FYI

There was a problem with the extractor for SP1.

This has been fixed in SP1 build number 377.

Hope this helps,

Kind Regards,

Matthew

[lukemarson]

Hi Dave,

My work around was to change

<dll>Nakisa.SAP.Custom.OTFProcessor</dll>
<class>Nakisa.SAP.Custom.OTFProcessor.BAPI_SAP_OTFProcessor_Report_Lite</class>

to

<dll>Nakisa.SAP.SAPeProcessor</dll>
<class>Nakisa.SAP.SAPeProcessor.RfcReadTable</class>

If you can get build 377 then all the better.

Good luck!

Luke

[StephenBurr]

I recently installed and tested 3.0 SP1 build 377 and still got an error (admittedly different to last build!) when running the extractor.

Missing class file still - this time in reference to:

com/nakisa/framework/data/utility/CommandLineParser

Hopefully soon this issue will be resolved!

[lukemarson]

Frustrating! I understand the next build will contain a full fix for the scheduled extractor - hopefully this will contain a full fix for the "standard" extractor too.

[StephenBurr]

To be clear ... I was (and I think Matthew from SAP was) referring to the scheduling of the extractor.

Dave - any progress on your extraction issue? Did you find an incorrect reference to PA0001? Have you tried to configure/customise the extraction process?

[lukemarson]

The issue is related to the Report_Lite function. If you change it to the RfcReadTable function it works okay.

[Former Member]

Hi Steve, Matthew and Luke,

Thanks very much for your inputs. My apologies for not responding in time as I was on vacation.

Still I have the issue with extraction. Unfortunately I can't change the build as this build was suggested by Nakisa for the language pack roll out for my project.

I would try the changes you guys suggested and update the thread by this weekend.

Best Regards

D

[StephenBurr]

Search the file "functionconfiguration.xml" for PA0001.

In my 3.0 SP1 (SQL Staged) build, there is only 1 reference to it in this file in this table:

<outputTable name="EmpOrgAssgn" critical="True" encoding="">

But you could have amended. Basically check that within the same

<function ...

the sourcetable in the <params> section

<param name="SOURCETABLE"><![CDATA[PA0001]]>

should match the source in the <outputtables> section

<source>PA0001</source>

e.g. Here is the standard code:

		<function name="RfcReadTable" critical="True" encoding="UTF8">
			<download>True</download>
			<desc>Nakisa.SAP.Custom.OTFProcessor</desc>
			<dll>Nakisa.SAP.Custom.OTFProcessor</dll>
			<class>Nakisa.SAP.Custom.OTFProcessor.BAPI_SAP_OTFProcessor_Report_Lite</class>
			<params>
				<param name="FIELDLIST"><![CDATA[PERNR,ENAME,SNAME,BUKRS,ORGEH,KOKRS,KOSTL,PERSG,PERSK,PLANS,STELL,WERKS,BTRTL,BEGDA,GSBER,ABKRS,FKBER
				

[lukemarson]

Hi Dave,

A few questions:

1. What extract function is this for?

2. Have you modified it?

3. What DB are you using?

4. Do you have the ABAP Add-on in the backend?

Cheers,

Luke