topic Re: BAPI_INB_DELIVERY_CONFIRM_DEC - Parameter documentation? in Application Development and Automation Discussions

BAPI_INB_DELIVERY_CONFIRM_DEC - Parameter documentation?

Former Member — Thu, 09 Feb 2012 08:25:07 GMT

Hi,

I'm trying to set up a decentral warehouse scenario. I created an inbound delivery that successfully sent out an IDOC SHP_IBDLV_SAVE_REPLICA02 to a PI system that is currently acting as a data sink - e.g. just testing the ERP side of things.

Now I want to confirm the inbound delivery in ERP to continue the process - i.e. act as if a decentral warehouse is sending a confirmation. Documentation says to use method InboundDelivery.ConfirmDecentral of object BUS2015 which is basically FB BAPI_INB_DELIVERY_CONFIRM_DEC.

I run above FB and according to documentation I only need to set

HEADER_DATA-DELIV_NUMB = '8020000000'

HEADER_CONTROL-DELIV_NUMB = '8020000000'

HEADER_CONTROL POST_GI_FLG = 'X'

DELIVERY = = '8020000000'

Hm - but - delivery does not get confirmed. Nothing happens and I'm stuck...

Where is the documentation of the parameters - which need to be set, with which value????

Any help appreciated.

Thanks

Wolf

Re: BAPI_INB_DELIVERY_CONFIRM_DEC - Parameter documentation?

Former Member — Thu, 09 Feb 2012 09:12:38 GMT

hi,

please check the bapi doc to undersstand the parameters

Re: BAPI_INB_DELIVERY_CONFIRM_DEC - Parameter documentation?

Former Member — Thu, 09 Feb 2012 10:38:57 GMT

Thanks for the quick reply.

But - that's what I did:

========================================

Three examples of how to use the BAPI are explained below:

1. Reporting back of an unpacked inbound delivery without changes

2. Reporting back of an unpacked inbound delivery with changes

3. Reporting back of an packed inbound delivery without changes

For each of the segment types reported back, there follows a list of particular example fields.

1. The item data of the delivery is reported back unchanged, and the delivery contains no packaging data.

DELIVERY - Document number of the inbound delivery

Field DELIV_NUMB - Delivery number

HEADER_DATA - Header data of the inbound delivery

Field DELIV_NUMB - Delivery number

HEADER_CONTROL - Header control data

Field DELIV_NUMB - Delivery number

Feld POST_GI_FLG - Indicator: Post automatic goods movement

========================================

BUT this does not work...

If you go further down you get the follow - not really helpful "documentation":

===========================================

Header Data

Description

The general header data of the inbound delivery is passed on to this table.

==============================================

Just asking whether

- someone maybe encountered a similar situation where (s)he had to add other data or

- whether anybody has a clue where to see what went wrong.

I created the delivery with MB1C and movement type 561 in ERP.

GS_DLV_BAPI_CONTROL-DB_COMMIT is ' '.... Not really an ABAP pro I can only see that in LV50SU16 WS_DELIVERY_UPDATE_2, line 511 I see that variable commit is inital and thus no COMMIT WORK is exercised. IF I manually set the variable to 'X' then I get two identical material movements, about one minute apart which is also not really what I want...

Don't know the logic and the purpose of DB_COMMIT - but it "smells" to me...

Wolf

Re: BAPI_INB_DELIVERY_CONFIRM_DEC - Parameter documentation?

Former Member — Mon, 03 Sep 2012 21:33:30 GMT

Hello, Wolf

Did you advance on your research/ solution?

I´m trying to understand your scenario - because I have a similar situation and I´m not the developer but the infrastructure guy...

You mentioned that there is a PI/XI system between the Decentralized WM and the ERP, is it correct?

You successfully sent an IDoc from D-WM to ERP using PI (ok, this is the purpose of the IDoc Adapter on PI middleware).

But something does not make sense. Are you trying to call a method of an BAPI/ function on the ERP side using (through) the PI system?

Regards,

Rodrigo

Re: BAPI_INB_DELIVERY_CONFIRM_DEC - Parameter documentation?

Former Member — Tue, 05 Mar 2013 07:44:48 GMT

Hi Wolf,

I'm setting up the same scenario as you, I however have issues with the IDOC not even arriving in XI and my consistency check if also showing errors.

Would you please be able to help me out quickly? I see the IDOC's created in SAP, however nothing shows in XI, and in SM58 I have errors on these IDOC's showing 'Function Module L_WMS_DEC_CHECK does not exist'.

Regarding your question to do an inbound delivery confirmation, or at least 'fake' one. I'm doing the following...

I got to WE19 and get IDOC 'SHP_IBDLV_CONFIRM_DECENTRAL'.

Then all I fill in is:

E1SHP_IBDLV_CONFIRM_DECENTRAL - DELIVERY (with leading 0's)

E1BPIBDLVHDRCON - DELIV_NUMB (with leading 0's)

E1BPIBDLVHDRCTRLCON - DELIV_NUMB (with leading 0's)

E1BPIBDLVCONTROL - all fields empty

E1BPIBDLVITEMCON - DELIV_NUMB (with leading 0's) / DELIV_ITEM (with leading 0's)

/ MATERIAL / BATCH / DLV_QTY / FACT_UNIT_NOM

/ FACT_UNIT_DENOM

E1BPIBDLVITEMCTRLCON - DELIV_NUMB / DELIV_ITEM / CHG_DELQTY

Show these should then correspond really to the fields you have to fill in for your BAPI.

Thanks for your help, you can reply to robbert.oortman @ federalmogul.com if you are willing to help me out. Since this is a generic S-user we use.

Thanks a lot in advance.