SAP Data Services data load

[smelcdus]

Did someone try to load data from ServiceNow by using SAP BusinessObjcects Data Services (BODS)?

I'm trying to use it with ODBC connector. The test connection works in ODBC Data Source Administrator (to SN demo server https://demoodbc.service-now.com ). I can use the ODBC even with Excel.

But once I add the ODBC connector to BODS Datastore it crashes. In the error log file (located in C:\Program Files (x86)\SAP BusinessObjects\Data Services\bin\hs_err_pidxxxx.log) exists java error:

# A fatal error has been detected by the Java Runtime Environment:

#   EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000006d9e7a74, pid=9772, tid=468

# JRE version: 6.0_24-b07

# Java VM: Java HotSpot(TM) 64-Bit Server VM (19.1-b02 mixed mode windows-amd64 compressed oops)

# Problematic frame:

# C   0x000000006d9e7a74

The Java JRE comes most probably from SN ODBC directly. The whole log is in attachment.

Environment:

• SAP BO DS 4.1 SP3 (14.1.3.515)
• ServiceNow ODBC (7.0.0) (tested both 32/64 version)
• Windows 7 64bit or Windows Server 2008 R2
• with installed Java 1.7.0.510 and without Java

[fghysens]

Hi

We are using the ODBC via SAP Data SErvices for several years now

We have build a full datamart using the technology.

The most recent release of data services is indeed not stable on the ODBC (we are on 4.2 SP1)

I advise you create a connection using generic odbc

first select any working/standard odbc connection

script the connection into ATL and then fill the proper ODBC connection (the ServiceNow one) that you want to use

you cannot import the table schemas

for extraction you should use a SQL transform

you cannot get the data schema of your SQL in the latest BODS release, it was working fine with the 3.2 version

so you need to manually add the columns and column types in the SQL transform...

As we have build the major part of our ETL on a working version this is not a big hinderance but we are opening a ticket with SAP to get these issues sorted.

The problem is getting decent support from SAP on this because they prefer to point at the ODBC driver...

Regards

f

[smelcdus]

Thanks for advice. Could you please describe more this step: "script the connection into ATL and then fill the proper ODBC connection (the ServiceNow one) that you want to use"

[fghysens]

Hello

The problem in DS is that you cannot add a new datasource if the datasource is not working properly.

By doing this via an ATL script you avoid the parsing rule to get the connection into the system.

REgards

f

[pavel_muller]

Hi,

just an idea. I am not expert in SAP but one of our customers has very similar environment. They have decided not to use the ODBC connector at all. They connect SAP BODS to an Oracle database running in their environment. They synchronize the data from ServiceNow into Oracle every hour so their reports are up to date.

To sync the data you can implement your own tool or leverage an exiting solution SnowMirror.

Regards,

Pavel