BAPI_GOODSMVT_CREATE & Acknowledgment on EKES - Note 906314

[Former Member]

Hi Experts,

I have a request to do Good Issue from Purchase Order.

BAPI BAPI_GOODSMVT_CREATE can GI to item level, but customer requires to GI to the acknowledgment level (vendor confirmation - table EKES).

I found a note regarding my question Note 906314. But our system is not Release 600, and this Note doesn't make any sense to us.

Someone suggests make modification on this BAPI, anyone can help how to make the change on that BAPI?

Thanks.

Legend.

[Former Member]

Hi Experts,

I have a request to do Good Issue from Purchase Order.

BAPI BAPI_GOODSMVT_CREATE can GI to item level, but customer requires to GI to the acknowledgment level (vendor confirmation - table EKES).

I found a note regarding my question Note 906314. But our system is not Release 600, and this Note doesn't make any sense to us.

Someone suggests make modification on this BAPI, anyone can help how to make the change on that BAPI?

Thanks.

Legend.

[Former Member]

the note in question is not about the BAPI but about a BADI which is a new kind of enhancement in higher releases. you can look at it as a kind of add-on to BAPI_GOODSMVT_CREATE. if you modify that BAPI according to the note this will most likey not work since in releases < 610 the relevant classes/methods have not been implemented (as far as i can remember in retrospective).

and anyway: modification is not an option (and especially not here). how about the 'old' program SAPMM07M? could you implement that there? in an exit?

[Former Member]

Thanks a lot.

I'm thinking using BDC for that, but not sure whether that's a good option.

[Former Member]

Below is the feedback from SAP. We are using option 2) to do this.

Hope it can help those who have the similar questions.

The BAPI_GOODSMVT_CREATE does not have the field ETENS where we can

specify which confirmation you will update. This field is necessary for

the function module ME_READ_ITEM_GOODS_RECEIPT (called from

MM07MFB7_BESTELLUNG_PRUEFEN) who will bring back the structure XEBEFU

(including field ETENS) with the confirmations we will update for this

item.

In transaction MIGO we do not have this problem as therefor MIGO

proposes us the confirmations and you can decide interactively for wich

confirmation you want to post the goods receipt.

There are the following solution options:

1.) You create and process the inbound deliveries via LE-transactions

(VL31N, VL32N) and post the GR with BAPI_GOODSMVT_CREATE in connection

to the inbound delivery

2.) You define a new confirmation control key with a confirmation

category of the WE-Relevant, but without WE assignment. You use this newcontrol key in new purchase orders then. If you post now a GR over

BAPI_GOODSMVT_CREATE in connection to apurchase order, the confirmationsare cancelled out successively according to the delivery date.

You would have to post the old purchase orders with MIGO.

Thanks.

Legend.