cancel
Showing results for 
Search instead for 
Did you mean: 

SAP PI JDBC receiver adapter: truncated data on some fields

0 Kudos

Hi gurus,

I have a proxy to JDBC sync scenario in our PI single stack 7.31 version.

When the proxy is executed, PI goes to a DB and do 2 sentences:

1) SQL_QUERY action (SELECT...)

2) SQL_DML action (UPDATE...)

It first goes to the DB and do a SELECT with condition flag = empty so we are sure that the data was not read in the past by PI. Once done, it do an UPDATE sentence to put an R so we know that the data was read and it will not be duplicated the next time PI runs for the same interface.

Recently, we faced a data issue in production. PI read a few records from the DB, and in a field with seven characters (let's call it 1234567) we are missing the last one, as it comes to PI as 123456 after and before mapping.

In our mapping, all fields are string so there is no length restriction. But there was something strange: the previous fields to the one mentioned, have some blank spaces after the data. For example, 1234 , 2343 , etc. Could this be an issue? I am not sure how PI is working the data when read from the DB.

Is anyone able to let me know why I am missing characters while looking in the DB the data is good?

Thanks!

Accepted Solutions (1)

Accepted Solutions (1)

Andrzej_Filusz
Contributor
0 Kudos

Hi,

I had a similar situation once. My scenario was working fine for several months. Then I could find additional spaces in messages. I stopped and started my communication channel. The issue disappeared...

Best Regards,

Andrzej Filusz

Answers (0)