Strange problem with dataflow between SAP and MSQL, pls.read

dataservices job design
1

Hi@all,

I have a dataflow, from SAP to MSQL, table VBAP, 417 columns.

When I limit inside ABAP Dataflow the document number for example
from 1073008000 - 1073009000 it works.

When I limit inside ABAP Dataflow the document number for example
from 1073007000 - 1073008000 it also works.

[b]BUT

When I limit inside ABAP Dataflow the document number for example
from 1073007000 - 1073009000 it does not works.[/b]

I get the following error:

ODBC data source error message for operation : <[Microsoft][SQL Server Native Client 10.0]
Invalid character value for cast specification>.

I have no idea, please help.

Data Services XI 12.2.2.2
Source SAP ECC
Target MSQL 2014

Holger

h.blum :de: (BOB member since 2008-06-16)

2

I’m speculating here, but I’ve just upgraded to DS 4.2 sp3 and found that SQL Server 2014 isn’t suported as a source or target database. Can you try modifying your compatability level to 110 and see if that has any effect?

Nemesis :australia: (BOB member since 2004-06-09)

3

Hi,

I set
compatability level to 110
and
compatability level to 100,
same result.

Then I take our Oracle database as source,
same table VBAP
limit the document number from 1073005000 - 1073009000,
that works but that is not the solution.

I need SAP as datasource for this dataflow.

:hb:

h.blum :de: (BOB member since 2008-06-16)

4

Hi
I had this issue also. After a lot of debugging finally got there.

There are two cases.
First datatype issue. The SAP DS Supported datatypes does not include data type like numeric(x,y). so when extracting from ABAP dataflow, it is best to cast it to varchar and then map it to decimal(x,y) which is a support DS datatype. in case of SQL Server this is one reason for getting the error. I tried mapping to decimal direct in the abap dataflow also and sometimes it also works. The former however is more reliable.

Second scenario I found were null values in SAP. In case of fields that you expect to have NULLs, use NVL function to handle these in earlier version of SAPDS. In version from 14.x there is a flag in the designer to handle this under options that will make it part of the jobserver parameters itself.

rbalasubramanian (BOB member since 2019-05-02)