topic Re: Error using Bapi_PO_Change for update custom fields in Application Development and Automation Discussions

Error using Bapi_PO_Change for update custom fields

Former Member — Fri, 05 Mar 2010 09:03:57 GMT

Dear Expert,

I have requirement for update custom field in table ekko. I used BAPI_PO_CHANGE with PO_number as a key. Then i put the value of custom field in segment TABLES - EXTENSIONIN.

But I get error : "ERROR TRANSFERING EXTENSIONIN DATA FOR ENHANCEMENT CI_EKKODB".

When I checked, I found the difference between data type the value for BAPI_PO_CHANGE (Usinf structure BAPIPAREX) and data type for custom field in table EKKO.

Data Type in BAPI_PO_CHANGE is CHAR (you can see in structure BAPIPAREX). And data type for the custom field is DECIMAL.

I found the note '1124803', but the correction note was not applicable for us because our released system is 500.

Is there any suggestion or solution for resolve our problem?

Really appreciate your help.

Thanks.

Re: Error using Bapi_PO_Change for update custom fields

Former Member — Fri, 05 Mar 2010 09:42:57 GMT

Hi Leni,

Tables: EXTENSIONIN is used for custom fields at item level (i.e.EKPO)

for custom fields at header level (i.e. ekko) i dont think SAP has provided any structure similar to EXTENSIONIN at header level in BAPI_PO_CHNAGE

u can give a try appending the same field in MEPOHEADR & MEPOHEADERX structures and try changeing the fields.

hope this helps.

Re: Error using Bapi_PO_Change for update custom fields

Former Member — Mon, 08 Mar 2010 02:08:58 GMT

Hi Laxmikanth Bethi ,

I tried with BAPI_PO_CHANGE in level header, and SAP was support the BAPI. And also i tried to appending the same fields in MEPOHEADR & MEPOHEADERX structures, but the problem is the type of my custom fields are DECIMAL, then the type MEPOHEADR & MEPOHEADERX structures are CHARACTER. So i got the error : "ERROR TRANSFERING EXTENSIONIN DATA FOR ENHANCEMENT CI_EKKODB".

Because the types are difference.

Have you any suggestion to solve this problem?

Really appreciate for your input.