Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

BAPI_ENTRYSHEET_CREATE

Former Member
0 Likes
1,049

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

7 REPLIES 7
Read only

Former Member
0 Likes
996

Any expert suggestion?

Read only

0 Likes
996

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

Read only

0 Likes
996

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

Thanks

Read only

Former Member
0 Likes
996

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.

Read only

0 Likes
996

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.

Read only

0 Likes
996

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 ***.

Read only

Former Member
0 Likes
996

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.