topic Re: Syntax error in BAPI_PS_PRECOMMIT in Application Development and Automation Discussions

Syntax error in BAPI_PS_PRECOMMIT

former_member378040 — Thu, 29 Jun 2006 17:10:51 GMT

When I use this BAPI I get a syntax error as follows -

"WA_BAPI_TE_PROJ" and "EXTENSIONIN+30(960)" are not mutually convertible in Unicode program.

We are at PI 2004_1_470 plug in.

The syntax error is in FM CJ2001_CREATE which is being called from the BAPI_PS_PRECOMMIT. Even though if go into the FM CJ2001_CREATE and try to generate, I get the same error message.

Thanks

Amit.

Re: Syntax error in BAPI_PS_PRECOMMIT

RichHeilman — Thu, 29 Jun 2006 17:14:29 GMT

I would check OSS on this.

Regards,

Rich Heilman

Re: Syntax error in BAPI_PS_PRECOMMIT

Former Member — Fri, 24 Nov 2006 20:01:39 GMT

Hi,

I have the exactly the same Problem (we are on MySap ERP 2004).

I looked for SAP OSS notes, but didn't find any.

Somebody knowing more about it?

ThanX

Holger

Re: Syntax error in BAPI_PS_PRECOMMIT

Former Member — Mon, 08 Jan 2007 15:51:43 GMT

Any news about this problem? I have the same and there is no OSS message.

Re: Syntax error in BAPI_PS_PRECOMMIT

Kimmo_from_Finland — Tue, 24 Apr 2007 12:38:51 GMT

If working with Unicode system, check OSS note 509898.

Sorry, I am not familiar with your BAPI in question but maybe I refer a purchase order bapi BAPI_PO_CREATE1 while the problem is the same with any bapi.

Basically you have adjusted a customizing include in table EKKO. Withing the BAPI prosessing these fields should be populated with value that you import in EXTENSIONIN tables parameter. But your include in EKKO contains also non-character fields. The EXTENSIONIN tables parameter however only contains character type fields. In your program that calls the BAPI you will populate first an structure that is of same type as include in EKKO table. This structure thus contains non-character fields. Now when you want to insert the whole structure to EXTENSIONIN table, you should get a warning the types are not compatible. This happens especially in Unicode environment! You cannot assign a structure that contains non-character fields to a target structure that contains only character fields.

This thread is rather old, but maybe my advise is not too late and at least others can review it. I actually just today encountered this very same problem myself and was looking help from SDN and found that note I am now passing to you as well.

Maybe this helps to understand.

Br: Kimmo