RFC Table IN/OUT error

[Former Member]

Dear friends,

We have a problem with comunication Adapter Tibco 7 x SAP ECC6.

We have the following data populated in the internal table before the exit of the RFC to the SAP adapter:

After communication with the Adapter, we have the following return, with the scrambled data:

TIBCO analyst told us that's enough info truncated in the adapter. Therefore, he who can't communicate with the TIBCO.

Does anyone know what could be going on between the RFC information output and the arrival in the adapter?

Thanks a lot,

GLippmann

[Former Member]

Dear friends,

We have a problem with comunication Adapter Tibco 7 x SAP ECC6.

We have the following data populated in the internal table before the exit of the RFC to the SAP adapter:

After communication with the Adapter, we have the following return, with the scrambled data:

TIBCO analyst told us that's enough info truncated in the adapter. Therefore, he who can't communicate with the TIBCO.

Does anyone know what could be going on between the RFC information output and the arrival in the adapter?

Thanks a lot,

GLippmann

[Former Member]

Anybody can help me?

[paul_bakker2]

Hi,

You probably figured this out already, but you get that 'shifting' effect when you copy from one structure to another, when the second structure has missing (or extra) fields.

So there is a mismatch with the structure/table definitions in the interface. In ABAP, this can often be fixed with a MOVE-CORRESPONDING instead of a MOVE.

cheers

Paul

[Former Member]

In SM59 we change the RFC from non-unicode to Unicode and it works.

Regards,

Gabriel