Truncation of long text on BAPI_ALM_CREATE_NOTIF

[Former Member]

I am using BAPI_ALM_CREATE_NOTIF to create an M1 type notification. I have set the OBJTYP=QMEL and the OBJKEY is blank. I have set a long text of 200 characters and filled in various other header fields. The Notification is being created ok but the long text seems to be truncated to 132 characters. I can then go onto SAP, change the notification and add more characters. When I view the notification XML on MII before and after the change I don't see any difference in the XML contents except for the extra characters. Does anyone know if there is a 132 character limit on the BAPI or have any idea why I might be seeing this truncation? I am using MII v12.1 and SAP vECC 6.0.

XML_After_Change.zip

XML_Before_Change.zip

[Former Member · Accepted solution]

The TEXT_LINE data type is CHAR 132. You will need to split your long text into 132 character chunks and pass multiple rows to the LONGTEXTS table.

[agentry_src · Accepted solution]

As a general rule, you can often test the behavior of BAPI/RFC calls using ECC and t-code BAPI or SE37 (for other than BAPI calls).  It does not always behave exactly the same as in MII, but for things like data types, it should be a good tool for testing.

Regards,

Mike

[Former Member · Accepted solution]

Many thanks to both Christian and Michael. This is now working splitting the text into smaller chunks. It would be nice if the documentation on SE37 for these RFC calls was a bit more helpful.