BAPI Item translation problem

[smeliot]

Using Mercator 6.7 (still mercator, as WS TX is only 8.0...), and creating BAPI call to SAP. The type tree was generated automatically.

There are two fields that are translating what I would call incorrectly.

SCALBASVAL is defined in Mercator as a Packed, Signed Binary Number, length of 15. It is defined in SAP as Decimal 28, with 9 decimals. There are other fields defined the same way (CONDVALUE is one of them), and they are translating fine.

FACTBASVAL is defined in Mercator as a Floating Binary Number, length of 8. It is defined in SAP as FLTP 16 with 16 decimals.

Has anyone seen anything like this before? I will elaborate if needed, but thought I'd put the beginnings out there first.

Thanks.

 

[OllyC]

Is the problem that they inpt type tree doesn't match the data? Whats does the data actually look like?

cheers,
Olly.

 

[BocaBurger]

What version of SAP libs are you using? What SAP Pack version?



BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!

 

[smeliot]

Okay, I'll delve into this a bit more deeply...

1. The type tree actually does match the SAP data definition - a floating binary length of 8 is the same as a FLTP 16 with 16 decimals.

2. We are actually sending no data - the rule is "=NONE"

3. SAP 4.7, SAP Pack 7.2

We've tried the following with no success:

-Sending nothing (=NONE) with the auto-generated type tree as is (floating binary length of 8)

-Sending 0 (=0) with the auto-generated type tree as is (floating binary length of 8)

-Sending nothing (=NONE) changing the type tree so that item is now TEXT.

-Sending absolutely nothing (rule of =NONE) by changing the type tree to have those fields optional - this way the tags don't even get sent.

All of these scenarios result with wonky data being received in SAP.

While this sounds like there's something wrong on the SAP side, there is a Web application and a DataStage EE application that both send data using the same BAPI and they don't have the problem.

And, yes, we have opened a ticket for this. I just wanted to see if anyone else out there has seen anything like this before.