A field type of fixed p.0 when present in an RFC/BAPI causes the adapter to throw BADMSGFORMAT error when used along with BW.

A field type of fixed p.0 when present in an RFC/BAPI causes the adapter to throw BADMSGFORMAT error when used along with BW.

book

Article ID: KB0091633

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix BusinessWorks Plug-in for SAP Solutions -
Not Applicable -

Description

Description:
A field type of fixed p.0 when present in an RFC/BAPI causes the adapter to throw BADMSGFORMAT error when used along with BW.

Symptom:
=======
A field type of fixed p.0 when present in an RFC/BAPI causes the adapter to throw an error when used along with BW.

Cause:
=====
This issue happens with EMS transport since the representation of fixed p.0 in BW is represented with a decimal followed by a zero whereas the adapter expects a number with no decimal or following values.

Impact:
======
Loss of functionality

Workaround:
=========
The following workaround may be implemented to mitigate these issues:-

Change the schema of the RFC field of type ‘fixed p.0’ to a scalar of type ‘fixed (p+1).1’.

Now the adapter schema and the schema it receives from BW via EMS would match and the error would be overcome.

Resolution:
=========
This issue has been resolved in hotfix 8 of SDK 5.4.1. This fix has been rolled out in SDK 5.6 and higher versions as well.
Symptoms:

Cause:

Issue/Introduction

A field type of fixed p.0 when present in an RFC/BAPI causes the adapter to throw BADMSGFORMAT error when used along with BW.