topic Re: BAPI_ENTRYSHEET_CREATE in Application Development and Automation Discussions

BAPI_ENTRYSHEET_CREATE

Former Member — Tue, 06 Mar 2012 19:13:35 GMT

I am facing issue using BAPI - BAPI_ENTRYSHEET_CREATE

I have 2 records identical coming from Idoc.

The first service entry is created with UOM = DA which is correct.

The second is created with UOM = ***. Not sure why this is happening.

Cannot debug as this is happening in production.

Any idea or anybody faced this issue?

Would really appreciate your help.

Pranu

Re: BAPI_ENTRYSHEET_CREATE

Former Member — Wed, 07 Mar 2012 05:10:43 GMT

Any expert suggestion?

Re: BAPI_ENTRYSHEET_CREATE

syed_ibrahim5 — Wed, 07 Mar 2012 05:47:34 GMT

hi,

The UOM in the second service entry sheet might not have been a valid unit of measurement in SAP. In such cases , *** is filled in UOM.

With Regards,

Syed Ibrahim . G

Re: BAPI_ENTRYSHEET_CREATE

Former Member — Wed, 07 Mar 2012 06:42:39 GMT

Both the records have "DA" and almost identical data.

Thanks

Re: BAPI_ENTRYSHEET_CREATE

Former Member — Wed, 07 Mar 2012 06:59:24 GMT

Hi,

Almost Identical does not mean completely identical data. Check both records completely. The function module should behave in the normal way for the second record as it did for the first one.

I assume that you are calling this Function module inside a loop. So, clear all workareas before processing the next record.

Regards,

Danish.

Re: BAPI_ENTRYSHEET_CREATE

Former Member — Wed, 07 Mar 2012 16:40:10 GMT

Thanks Danish.

I checked and no ray of light.

By almost identical I meant the exact records but the different quantity.

First has 31 DA and second has 1 DA.

Re: BAPI_ENTRYSHEET_CREATE

Former Member — Wed, 07 Mar 2012 22:09:14 GMT

It appears to be a conversion issue. Check the service number/material (PO) and the base unit associated with it.

If the base unit is not same as the passed uom maybe because of this UOM is saved as ***.

Re: BAPI_ENTRYSHEET_CREATE

Former Member — Wed, 07 Mar 2012 22:26:37 GMT

We are having an almost exact problem. Two SE lines come in, one with EA and 1 and the other with DA and 31. The DA turns into ****. We have been using a program to correct the many SAP tables affected but the situation is now happening more often.