topic Re: BAPI_ENTRYSHEET_CREATE Problem in Application Development and Automation Discussions

BAPI_ENTRYSHEET_CREATE Problem

Former Member — Thu, 14 Aug 2008 22:11:32 GMT

Hello everybody,

I have the next problem: I'm using the bapi BAPI_ENTRYSHEET_CREATE, and is working fine the problem is when I call BAPI_PO_CHANGE, BAPI_PO_RELEASE and BAPI_ENTRYSHEET_CREATE one after the other in that order, when I do this call BAPI_ENTRYSHEET_CREATE gives a dump cause ITAB_DUPLICATE_KEY in the function module ME_STATISTICS_WE_EKBE_LIS routine xmcekpo_cut_lis in the line aux_xmcekpo[] = xmcekpo[]., so it somewhow has in memory changes for the positions made bye one of the other bapi's, I'v already called a BAPI_TRANSACTION_COMMIT after BAPI_PO_RELEASE, any other suggestions thanks in advance.

Regards

Julio Cesar

Re: BAPI_ENTRYSHEET_CREATE Problem

Former Member — Wed, 20 Aug 2008 17:03:05 GMT

thanks, I soloved it refreshing PO data from logical databases and buffers.

Re: BAPI_ENTRYSHEET_CREATE Problem

Former Member — Tue, 29 May 2012 12:32:29 GMT

Hi.

I know that this is a 2008 post, but I have the same problem now.

could you explain what FM or Bapis do you use to clear-refresh the PO buffers?

thank you

Re: BAPI_ENTRYSHEET_CREATE Problem

Former Member — Mon, 29 Oct 2012 18:32:59 GMT

Hi Programador,

Greetings for the day!

May be you have figured out a way to do this already, but just in case, try using Function Module ME_STATISTICS_TABLES_REFRESH just after the PO Creation / Release FM Call. Do not forget a COMMIT WORK AND WAIT after calling the above mentioned FM.

The SAP Note 750440 lists this as a bug when we do a PO Create / PO Change and then in the same process try to execute a Goods Movement. The bug has been rectified by calling the above mentioned function module at the "Cleanup" section of code within the BAPI_PO_CREATE1 or BAPI_PO_CHANGE. I guess the PO Release BAPI FM BAPI_PO_RELEASE does not use this cleanup section, and hence the statistics buffers remain filled, causing a dump during LIS update while posting the goods movement. I hope SAP will analyze and correct this, if necessary.

Regards,

Sid