cancel
Showing results for 
Search instead for 
Did you mean: 

OrgAudit 4.0 - Extraction is sucessful but data is not shown in user level

Former Member
0 Kudos

Dear Experts,

I am using OrgAudit 4.0 SP01, with SQL Server 2008. SAP Extraction is done successfully ,

I have seen some data in HRP1001_O_O and HRP1001_S_S tables.,

I not seen any data in PositionToPositionMain and CompanyCodeHierarchy tables.,

I do understand that Data is picking from HRP1001_O_O for Organization Structure ,

PositionToPositionMain for Position Hierarchy ,

CompanyCodeHierarchy for Company Code Hierarchy ,

But we have enough data in R3 side. We really don't know what is the issue behind. When we Saved & Publish the Build with required configuration(Set the Root for OrgUnit, Position and Company Code),,

then open the default.jsp in the browser we are getting the error messages Root not found Error in Organization Structure, Position Structure and Company Code Hierarchy. please help me on this issue.

Best Regards ,

Dileep P

Accepted Solutions (0)

Answers (1)

Answers (1)

StephenMillard
Active Contributor
0 Kudos

Have you set the root ID for the extract and the chart (I think they are separate)?

Also what do you see in terms of errors in the CDS.LOG for when you run the extract job?

Former Member
0 Kudos

Dear Stephen,

YES!! I have maintained the Root ID while taking the Extraction.

Also I have seen SAP Extraction Successfully. But some errors are shown in the CDS.log file.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

5. 19 Aug 2014 09:16:01 WARN com.nakisa.Logger - : org.springframework.dao.DataAccessResourceFailureException: StatementCallback; SQL [DROP TABLE PositionsCompanyCode]; Connection reset by peer: socket write error; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error

6. 19 Aug 2014 09:16:01 ERROR com.nakisa.Logger - : org.springframework.dao.DataAccessResourceFailureException: StatementCallback; SQL [CREATE TABLE PositionsCompanyCode(OBJID varchar(8),OTYPE varchar(2),BUKRS varchar(4),BEGDA datetime,ENDDA datetime)]; Connection reset by peer: socket write error; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error

7. 19 Aug 2014 09:16:01 ERROR com.nakisa.Logger - org.springframework.dao.DataAccessResourceFailureException: StatementCallback; SQL [CREATE TABLE PositionsCompanyCode(OBJID varchar(8),OTYPE varchar(2),BUKRS varchar(4),BEGDA datetime,ENDDA datetime)]; Connection reset by peer: socket write error; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error

92. 19 Aug 2014 09:16:35 ERROR com.nakisa.Logger - class com.nakisa.framework.data.commandProcessor.base.SqlBatchReadWriteCommandProcessor : createRows : Error creating rows

93. 19 Aug 2014 09:16:35 ERROR com.nakisa.Logger - java.lang.NullPointerException: while trying to invoke the method java.lang.Integer.intValue() of a null object returned from java.util.Map.get(java.lang.Object)

19 Aug 2014 09:21:23 ERROR com.nakisa.Logger  - executeFunctionDirect : FunctionRunner.executeFunctionDirect: HRWPC_RFC_EP_READ_PHOTO_URI threw an Exception of type AbapException, took: 8ms

19 Aug 2014 09:21:23 ERROR com.nakisa.Logger  - com.sap.mw.jco.JCO$AbapException: (126) INTERNAL_ERROR: INTERNAL_ERROR

19 Aug 2014 09:23:21 ERROR com.nakisa.Logger  -  : org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [select a.Pernr, a.ComnId, a.ComnLongId as Email, b.ComnLongId as Phone, c.COMNID as Cell,  d.COMNID as Fax INTO TempEmpCommn from (select * from EmpCommn where ComnType= '0010') a left join (select * from EmpCommn where ComnType= '0020') b on a.Pernr = b.Pernr                                 left join (select * from EmpCommn where ComnType= 'CELL') c on a.Pernr = c.Pernr left join (select * from EmpCommn where ComnType= '0005') d on a.Pernr = d.Pernr]; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'ComnType'.

19 Aug 2014 09:23:21 ERROR com.nakisa.Logger  - org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [select a.Pernr, a.ComnId, a.ComnLongId as Email, b.ComnLongId as Phone, c.COMNID as Cell,  d.COMNID as Fax INTO TempEmpCommn from (select * from EmpCommn where ComnType= '0010') a left join (select * from EmpCommn where ComnType= '0020') b on a.Pernr = b.Pernr                                 left join (select * from EmpCommn where ComnType= 'CELL') c on a.Pernr = c.Pernr left join (select * from EmpCommn where ComnType= '0005') d on a.Pernr = d.Pernr]; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'ComnType'. Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'ComnType'.

19 Aug 2014 09:23:21 ERROR com.nakisa.Logger  -  : org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [Drop table INHE_MANAGER2,INHE_MANAGER2Temp]; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: Cannot drop the table 'INHE_MANAGER2', because it does not exist or you do not have permission.

19 Aug 2014 09:23:21 ERROR com.nakisa.Logger  - org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [Drop table INHE_MANAGER2,INHE_MANAGER2Temp]; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: Cannot drop the table 'INHE_MANAGER2', because it does not exist or you do not have permission.

19 Aug 2014 09:23:21 ERROR com.nakisa.Logger  -  : org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [SELECT     Temp2.Pernr, Temp2.Racky, EmpRaceEthen.Sprsl, EmpRaceEthen.Ltext, Temp2.PersonnelArea, Temp2.MOLGA into Temp3 FROM         Temp2 LEFT OUTER JOIN                       EmpRaceEthen ON Temp2.MOLGA = EmpRaceEthen.Molga AND Temp2.Racky = EmpRaceEthen.Racky]; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'Temp2'.

19 Aug 2014 09:23:21 ERROR com.nakisa.Logger  - org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [SELECT     Temp2.Pernr, Temp2.Racky, EmpRaceEthen.Sprsl, EmpRaceEthen.Ltext, Temp2.PersonnelArea, Temp2.MOLGA into Temp3 FROM         Temp2 LEFT OUTER JOIN                       EmpRaceEthen ON Temp2.MOLGA = EmpRaceEthen.Molga AND Temp2.Racky = EmpRaceEthen.Racky]; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'Temp2'. 45460.

19 Aug 2014 09:23:22 ERROR com.nakisa.Logger - : org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [SELECT DISTINCT

-----------------------------------------------------------------------------------------------------------------------------------------------------------------

Can you please help  me on this issue.

Best Regards

Dileep P

StephenMillard
Active Contributor
0 Kudos

Ok, I see... Network/database connection errors, user account permissions errors and some others for objects failing to be created.

I'd start with checking your database user account. Is it the database owner? Try rerunning some of the failed SQL statements in the log via a database client to see more details for what is going on.

StephenBurr
Active Contributor
0 Kudos

I would try to run this statement directly against the DB using SQL Server Mgmt Studio or something similar:

CREATE TABLE PositionsCompanyCode(OBJID varchar(8),OTYPE varchar(2),BUKRS varchar(4),BEGDA datetime,ENDDA datetime);

Does this work?

Former Member
0 Kudos

Dear Burr,

YES!!! we are able to create the table in DB.

Then what is issue?

Best Regards

Dileep P

StephenMillard
Active Contributor
0 Kudos

So that proves your account has the permissions to create database tables which was one of the things that had an error earlier.

Have you just tried the one run for the job?  If that's the case, perhaps run just the extract stage again and monitor the log as it runs to see if it is failing early in the process again or if it was maybe just a temporary connectivity glitch in your first run.

Former Member
0 Kudos

Dear Stephen,

This issue is resolved - this is issue because of DB Collation issue.

I am using SQL Server 2008 - as default setting DB collation is : SQL_Latin1_General_CP850_BIN2

But I changed this DB collation Setting to : SQL_Latin1_General_CP850_CI_AI


Then my issue got solved. Thanks for your support.

Best Regards

Dileep P