topic Re: BAPI_PO_CHANGE UNICODE Customer Fields in Application Development and Automation Discussions

BAPI_PO_CHANGE UNICODE Customer Fields

Former Member — Thu, 26 Jul 2007 14:06:44 GMT

Hello,

we are migrating from 4.6C to ECC6.0. And now BAPI_PO_CHANGE doesn't work for customer fields. These fields are in structure CI_EKKODB. Three of these fields are packed (Type CURR). Although the parameter given to BAPI has another structure without packed fields structure CI_EKKODB is checked by BAPI.

How can I solve this problem without changing CI_EKKODB because this structure is include of DB structure EKKO.

Thanks in advance

Christoph

Re: BAPI_PO_CHANGE UNICODE Customer Fields

Former Member — Thu, 22 Nov 2007 02:29:50 GMT

Hi,

have u got the solution for the issue?

if so plz let me know abt it. since i am facing the same problem.

thanks

Suganya

Re: BAPI_PO_CHANGE UNICODE Customer Fields

Former Member — Mon, 31 Mar 2008 15:52:22 GMT

Hello Suganya,

sorry for the last reply.

If your problem still exists, here is my solution found by myself.

Prerequisite : The non-unicode fields are not used by BAPI call.

a) Delete non unicode fields in CI_EKKODB

b) Create new include like ZCI_EKKODB including these fields

c) Append this include to EKKO

d) Append this include to EKKO_CI

e) Append this include to MEPOHEADER

f) Generate EKKO after it and there no loss of data

Best Regards

Christoph