Inbound Delivery Index Table

Hi,
I tried to retrieve the delivery number with vendor code(LIFNR) in VLKPA-KUNDE. But, nothing is returned. Is there any other index table that provide the same information.
Regards,
Kit

Hello,
please refer to following thread:
[handling unit |handling unit;
[inbound delivery |inbound delivery;
Andrzej

Similar Messages

Confirmation control key check for inbound delivery creation

Hi,
Currently, in the Client's company, the process of receiving goods from purchase orders looks like that (SAP-wise):
- create a purchase order,
- receive goods using MIGO and automatically create an inbound delivery,
- pack the delivery and post goods receipt.
Recently, some patches have been installed, including one described by note 1602047 (which basically enforces checking confirmation control keys if goods receipt assignment and goods receipt relevance are activated for inbound deliveries). Note says that it only affects two-step stock transfer and creation of automatic inbound deliveries using SPED output but it seems it also affects other basic processes like PO receipt in MIGO.
Now, when using the old control key (that had MRP-Relevant and GR-Relevant fields checked), the system is unable to automatically create an inbound delivery after the goods receipt is posted with MIGO (with message VL148 - Not possible to create an inbound delivery). I learned that this is because the "GR Assignment" field must be checked in the confirmation control key so it's possible to automatically create aninbound delivery after receiving a purchase order in MIGO.
After changing the confirmation control key to have the missing field checked it's not possible anymore to receive goods from PO in MIGO as the PO requires shipping notification in order to be processed in MIGO thus requiring of manual creation of an inbound delivery.
Is there any way to skip this check so the process would remain the same (this model has been working fine for few years in the Client's system) and the inbound delievery would be created automatically after posting the receipt in MIGO?
Thanks in advance,
Piotr

Hi,
don't know if you found a solution, but we received the following message from SAP:
The advent of the new version requires some attention to the users. It
was necessary to avoid inconsistencies which in the past version the
system was susceptible.
Main Program SAPMM07M
Source code of MM07MLVS
sy-msgid VL sy-msgty E sy-msgno 148
I have checked the process and through debugged I could confirm the
following information SAP is providing to all similar incidents reportedfor us:
Error message VL 148 is issued if in the confirmation control key used
in the purchase order, the fields for MRP-relevance (T163G-KZDIS),
GR relevance (T163G-WEREL) and GR assignment indicator (T163G-WEZUO)
are not set.
The correction of note 1602047 was necessary to avoid inconsistencies
(table EKES) in the purchase order. Without having the GR assignment
(T163G-WEZUO) set, there is no unique reference created between the
purchase order history (table EKBE) and the inbound delivery
confirmation (table EKES) at goods receipt which leads to a problem if
several inbound deliveries exist for the same purchase order.
If you set T163G-WEZUO to 'X', this assures that, for an inbound
delivery, the confirmation record (EKES) belonging to this inbound
delivery (EKES-VBELN) is also accurately updated at goods receipt.
How to solve the issue?
Use a confirmation control key with the GR assignment indicator set
and then create the inbound delivery with VL31N. If you want to be able
to create the inbound delivery with reference to a certain line item in
the PO, use transaction VL34.
If you still want to use transaction MIGO, there is the following
workaround:
- Create a purchase order without any confirmation control key
- Create a goods receipt (GR) in transaction MIGO with reference to this PO and post the GR to a non-HU-managed storage location
- Create a transfer posting with MIGO using movement type 311 to
transfer the goods from the non-HU-managed storage location to the
HU-managed storage location.
As the transfer posting is an additional step for the user, the whole
process could be automated using a partner storage location
(T001l-PARLG) for the GR which then triggers (through a modification)
the BAPI 'BAPI_GOODSMVT_CREATE' to create the transfer posting without
user interaction.
I hope to have satisfied you on the reason why it is now happening and
also I believe you can explain to business that it is a new behavior
necessary done from SAP side to avoid worse situations, we are aware of
potential dissatisfaction it might cause. SAP Support is always
available to clarify any issue.
Sorry for not having a more positive answer.
I hope it helps!
Leentje

New Condition TAble for Inbound Delivery

Hello
i want to maintain a new Condition table for the Inbound delivery picking with the combination of _Delivery type/Plant
so that the Inbound created for the particular plant alone uses the particular output type.
Where in IMG can i configure the new Condition table for this combination for the Inbound delivery ?

Hi,
Go to SPRO > Logistics Execution > Shipping > Basic Shipping Functions > Output Control > Output Determination > Maintain Output Determination for Inbound Deliveries > Here perform following;
- Define Condition Table for Inbound Delivery
- Define Output Types for Inbound Delivery
- Define Access Sequence for Inbound Delivery
- Maintain Output Determination Procedure
- Assign Output Determination Procedures

Need help on Inbound Delivery - Mapping from IDoc to LIKP Table

Hi,
For the DESADV IDoc (Inbound Delivery) we are currently mapping data to the LIKP table for a subset of fields via function module INPUT_IDOC_DESADV. If I wanted to map the ABLAD - Unloading Point field from the IDoc to the LIKP - ABLAD - Unloading Point field is this possible and if yes, what work would be required?
And could you please let me know how to find out an user exit for the message type? (message type = desadv)

Hi Murphy,
Try this custom function '002'.
CALL CUSTOMER-FUNCTION '002'
       EXPORTING
            xekko     = ekko
            xlfa1     = lfa1
            xlfb1     = lfb1
            dobject   = object
       TABLES
            int_edidd = int_edidd
            xekpo     = xekpo
            xeket     = xeket
            dvbak     = xvbak
            dvbap     = xvbap
            dvbkd     = xvbkd
       EXCEPTIONS
            error_message_received        = 1
            data_not_relevant_for_sending = 2.
Hope this will help.
Regards,
Ferry Lianto

Error :Inbound Delivery "No item category exists (Table T184L DIG NORM V )"

Dear Guru's,
When I try to create an inbound Delivery for an SA i am getting the following error "No item category exists (Table T184L DIG NORM V )" . My problem is, it suppose to look for Delivery Type: EL instead of DIG. I dont know why its look for DIG, can some one point where i am making the mistake?
I am sure that i should be looking for Delivery Type : EL and Item Category : ELN (for Delivery)
Please advice...
Regards,
Kumar

Dear Kumar ,
Please check the itemcategory determination for the delivery type DIG in 0184 transaction for combination.
Delivert type+Norm -
>Itemcategory
For Example :- DIG + NORM---->DIGN
I hope this will help you,
Regards,
Murali.

What is the table for inbound delivery and PO

Hello,
I did one inbound delivery with reference to PO, the SD Documnet Category:7(Shipping Notification/Delivery)
I tried in LIKP,EKBE tables for Inbound delivery and PO relation.
I didnot find, Can i have the table name for findinh the PO and Inbound delivery in one table.
I want to fetch these two documents in to reports.
With regards
Lakki

I am sorry. I misunderstood your requirement. Please ignore my earlier post on this.
But do consider the below option :
You can get both Purchase Order as well as Inbound Delivery details in LIPS.
LIPS-VGBEL = Reference Document ( In this case it would be PO )
Hope this time it helps you.

Inbound delivery no to GRN linking tables and fields

hi guys,
can u help me tofind out list of GRNs for a particulaar inbound delivery no.
which tables and fields used for the same.
my MKPF / MSEG table doesnot contain any inbound delivery no - reference, if it is configuration issue , please provide me some tips to find solution.
regards,
Giri

SAP doesnot save the inbound delivery if u do pgr from migo. For this u have to do the development and can update the delivery number in delivery note field . for this use implement the badi MB_MIGO_BADI . In this there is structure GOITEM use in methods in this field VLIEF_AVIS contains the delivery number . I also faced same problem and i have to do this development for one of my client.

Inbound delivery no - GRN linking tables

hi guys,
can u help me tofind out list of GRNs for a particulaar inbound delivery no.
which tables and fields used for the same.
my MKPF / MSEG table doesnot contain any inbound delivery no - reference, if it is configuration issue , please provide me some tips to find solution.
regards,
Giri

THANKX FOR YOUR RESPONSE.
But as i mentioned earlier.... there is no inbound delivery no...stored in both the fields which you have mentioned.
1.xblnr = stored with some lorry nos.
2.le_vbeln is empty

Inbound delivery item deleted is not deleted from BI DSO?

Hi All
An Inbound deliver created and pushed to BI..
Source PSA is FULL UPDATE and DTP is DELTA UPDATE
Ex: 800000 10   10000
                    20 10000
This is what pushed to ODS..Later next day,
they deleted the to 800000 10 10000
So PSA is refreshed with one item .
800000 10 10000
whereas DSO still shows as follows:
800000 10 10000
              20 10000
I have following options:
1. convert DTP to FULL update, so the data gets refreshed..
2. ELse delete the only one record..
But user sometimes need to delete the inbound delivery....based on item required..
we cannot go and delete everytime for this issue..
What are the best solutions that you experts can suggest.??

HI...
This is a known problem in ECC-BI.   Deliveries can only be deleted from ECC system but can not be cancelled. So the extractor is not able to provide a deleted image for the record.
Two solution can be there,
1. Full Load of all BI target every day ---this solution is practical only when your data volume is less and full load does not take much time. But if your data volume is huge and flow is complex one then this is not the solution.
2. Second solution is to identify which Delivery Doc - Item combination got deleted from ECC system and then you can just put a flag against those documents.
You can easily find which doc- item got deleted from CDPOS and CDHDR entry. In our project we created one DataSource based on InfoSet Query ( SQ02) on CDPOS ( item level) and CDHDR ( header level) and pulling all the documents which got deleted in ECC system. For all those Delivery-Item we put a deletion flag and restrict the query accordingly.
in CDPOS following fields are important.
a) CHNGIND: Change Type (U, I, S, D) u2013 This field shows whether the entry is deleted, updated or inserted. We are here interested in the value: D (Deleted).
b) OBJECTCLAS: Object class u2013 This field is used to get the data related to Deliveries, Sales etc. For deliveries, value is LIEFERUNG; For Sales, value is VERKBELEG
c)TABNAME: Table Name u2013 This field contains the table name from which the value is deleted. The tables for Deliveries are LIKP and LIPS. To get the item level data, keep the value as LIPS.
d) TABKEY is 18 characters long field, in which first 3 numbers is the client number, next 10 shows the document number and next 5 shows the item number. E.g.: 750001099999900010, where 750 is client, 0010999999 is document number and 00010 is item number
Also have a look at How to Guide below
Link [CDPOS-CDHDR|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50dd3fb9-0dad-2d10-0ea7-cbb0bb8b391b?QuickLink=index&overridelayout=true]
how to view deleted delivery
Regards
Anindya

Call transaction 'VL33N' on click of Inbound delivery number in ALV List.

Hi,
My ALV output is having Inbound delivery number.
If user clicks on one of the Inbound delivery it has to call transaction VL33N and display the user selected document.
Code:
WHEN '&IC1'.
IF rs_selfield-fieldname = 'VBELN'.
        READ TABLE gt_final INTO wa_final INDEX rs_selfield-tabindex.
        if wa_final-vbeln is not initial.
          FREE MEMORY ID 'VL'.
          SET PARAMETER ID 'VL' FIELD WA_FINAL-VBELN.
          CALL TRANSACTION 'VL33N' AND SKIP FIRST SCREEN.
        ENDIF.
      ENDIF.
I am setting the parameter id 'VL' by passing Inbound Delivery number.After that it is calling VL33N Screen but the Inbound delivery number is blank.In debugging i can see the SAP memory for 'VL' as the selected document number.
Why VL value is not transferred to Inbound Delivery number field in VL33 Eventhough Parameter id having value.
VL (10) <0180000057>
Thanks
Bhuvana
Edited by: Pulibhuvana on Nov 22, 2010 8:20 AM

Hi,
Removed Free statement.
      IF rs_selfield-fieldname = 'VBELN'.
        READ TABLE gt_final INTO wa_final INDEX rs_selfield-tabindex.
        if wa_final-vbeln is not initial.
          SET PARAMETER ID 'VL' FIELD rs_selfield-value.
          CALL TRANSACTION 'VL33N' AND SKIP FIRST SCREEN.
        ENDIF.
      ENDIF.
In background VL is passing to VL03N Transaction instead of VL33N.
Outbound delivery and Inbound Delivery both are assigned to same paramer id.
Don't undestand if i'm calling VL33N Why the paramer value is passed to Outbound delivery transaction VL03N.
Please suggest me.
Thanks
Bhuvana

BAPI for VL31N:Create Inbound Delivery

Hi all,
Please give the BAPI for VL 31N: Create Inbound delivery transaction
thanks

No bapi but you can use this function module GN_DELIVERY_CREATE
Select the data required - see below
select ebeln ebelp menge meins matnr werks lgort bstae loekz elikz
         lmein umrez umren insmk pstyp sobkz knttp kzfme kzvbr
         ematn mfrnr mfrpn emnfr cuobj uebto untto uebtk bwtar idnlf
         txz01 mfrgr gewei voleh ntgew brgew volum ean11 aktnr abeln
         abelp aurel matkl upvor uptyp uebpo wepos
          into corresponding fields of table xekpo_short
          from ekpo
           where ebeln = i_ebeln
             and ebelp = i_ebelp.
if sy-subrc ne 0.
    e_rc = 4.
else.
    read table xekpo_short index 1.
    call function 'ME_EKKO_SINGLE_READ'
      exporting
        pi_ebeln         = xekpo_short-ebeln
      importing
        po_ekko          = ekko
      exceptions
        no_records_found = 1
        others           = 2.
    if sy-subrc ne 0.
      e_rc = 4.
    elseif ekko-bstyp ne 'F' and ekko-bstyp ne 'L'.
      e_rc = 4.
    endif.
endif.
clear xvbsk.
xvbsk-mandt = sy-mandt.
xvbsk-ernam = sy-uname.
xvbsk-erdat = sy-datum.
xvbsk-uzeit = sy-uzeit.
xvbsk-smart = 'L'.
*- Nummer VBSK vergeben -
select single * from tvsa where smart = xvbsk-smart.
if sy-subrc = 0.
    call function 'NUMBER_GET_NEXT'
      exporting
        nr_range_nr = tvsa-numki
        object      = 'RV_SAMMG'
      importing
        number      = xvbsk-sammg
      exceptions
        others      = 01.
    if sy-subrc ne 0.
      message e700(me) with tvsa-numki text-007.
    endif.
else.
    message e700(me) with space text-007.
endif.
data: h_grkor like lips-grkor,         "Liefergruppe         "386409
       h_bsmng like ekpo-menge.         "Bestellmenge übergeordnete Pos.
if not ekko-lifnr is initial.
    call function 'VENDOR_MASTER_DATA_SELECT_12'
      exporting
        pi_lifnr       = ekko-lifnr
        pi_ekorg       = ekko-ekorg
      importing
        pe_lfm1        = lfm1
      exceptions
        no_entry_found = 1
        others         = 2.
    xkomdlgn-vsbed = lfm1-vsbed.
else.
    clear xkomdlgn-vsbed.
endif.
xkomdlgn-lifnr = ekko-lifnr.
xkomdlgn-inco1 = ekko-inco1.                              "363954
xkomdlgn-inco2 = ekko-inco2.                              "363954
xkomdlgn-exnum = ekko-exnum.                              "363954
xkomdlgn-bukrs_best = ekko-bukrs.                         "363954
xkomdlgn-matnr = xekpo_short-matnr.
xkomdlgn-werks = xekpo_short-werks.
xkomdlgn-lgort = xekpo_short-lgort.
xkomdlgn-charg = ?
xkomdlgn-vrkme = xekpo_short-meins.
xkomdlgn-meins = xekpo_short-lmein.
xkomdlgn-umvkz = xekpo_short-umrez.
xkomdlgn-umvkn = xekpo_short-umren.
if xekpo_short-matnr eq space.                            "386409
    xkomdlgn-meins = xekpo_short-meins.
    xkomdlgn-umvkz = 1.
    xkomdlgn-umvkn = 1.
endif.
xkomdlgn-insmk = xekpo_short-insmk.
xkomdlgn-kzfme = xekpo_short-kzfme.
xkomdlgn-kzvbr = xekpo_short-kzvbr.           "note 384051
xkomdlgn-lfimg = p_lfimg.
xkomdlgn-lfdat = p_eindt.
xkomdlgn-vgbel = xekpo_short-ebeln.
xkomdlgn-vgpos = xekpo_short-ebelp.
xkomdlgn-lfart = gf_dlv_type.
xkomdlgn-vgtyp = 'V'.
xkomdlgn-kzazu = 'X'.                "??? what's that for ????
xkomdlgn-knttp = xekpo_short-knttp.
xkomdlgn-sobkz = xekpo_short-sobkz.
if xekpo_short-matnr is initial or xekpo_short-pstyp = '6'.
    xkomdlgn-posar = 'B'.
endif.
xkomdlgn-ematn = xekpo_short-ematn.
xkomdlgn-mfrnr = xekpo_short-mfrnr.
xkomdlgn-mfrpn = xekpo_short-mfrpn.
xkomdlgn-emnfr = xekpo_short-emnfr.
xkomdlgn-cuobj = xekpo_short-cuobj.
xkomdlgn-uebto = xekpo_short-uebto.
xkomdlgn-untto = xekpo_short-untto.
xkomdlgn-uebtk = xekpo_short-uebtk.
xkomdlgn-bwtar = xekpo_short-bwtar.
xkomdlgn-kdmat = xekpo_short-idnlf.
xkomdlgn-arktx = xekpo_short-txz01.
xkomdlgn-mfrgr = xekpo_short-mfrgr.
xkomdlgn-gewei = xekpo_short-gewei.
xkomdlgn-voleh = xekpo_short-voleh.
xkomdlgn-ntgew = xekpo_short-ntgew * xkomdlgn-lfimg.
xkomdlgn-brgew = xekpo_short-brgew * xkomdlgn-lfimg.
xkomdlgn-volum = xekpo_short-volum * xkomdlgn-lfimg.
xkomdlgn-ean11 = xekpo_short-ean11.
xkomdlgn-aktnr = xekpo_short-aktnr.
xkomdlgn-abeln = xekpo_short-abeln.
xkomdlgn-abelp = xekpo_short-abelp.
xkomdlgn-aurel = xekpo_short-aurel.
xkomdlgn-idnlf = xekpo_short-idnlf.
xkomdlgn-matkl = xekpo_short-matkl.
Leergut-Stückliste übernehmen
clear xkomdlgn-grkor.
clear xkomdlgn-kmpmg.
clear xkomdlgn-uepos.
if xekpo_short-upvor ca '3X'.
    h_grkor = h_grkor + 1.
    xkomdlgn-grkor = h_grkor.
    h_bsmng = xekpo_short-menge.
endif.
if not xekpo_short-uebpo is initial and
         xekpo_short-uptyp ca '3X'.
    xkomdlgn-uepos = xekpo_short-uebpo.
    xkomdlgn-grkor = h_grkor.
    if h_bsmng ne 0.
      xkomdlgn-kmpmg = xekpo_short-menge / h_bsmng.
    endif.
endif.
*- Konsignation - SOBKZ 'K' hart reinsetzen, da von Pstyp abhäng......
if xekpo_short-pstyp eq '2'.
    xkomdlgn-sobkz = 'K'.
endif.
Kontierungsfelder
if xekpo_short-sobkz eq 'E' or xekpo_short-sobkz eq 'Q'.
    call function 'MMPUR_EKKN_READ_EBELN_EBELP'
      exporting
        pi_ebeln                   = xekpo_short-ebeln
        pi_ebelp                   = xekpo_short-ebelp
      PI_BYPASSING_BUFFER        =
      PI_REFRESH_BUFFER          =
      tables
        pto_ekkn_po                = xekkn
      exceptions
        no_records_requested       = 1
        others                     = 2.
    if sy-subrc eq 0.
      read table xekkn index 1.
      xkomdlgn-ps_psp_pnr = xekkn-ps_psp_pnr.
      xkomdlgn-vbelv      = xekkn-vbeln.
      xkomdlgn-posnv      = xekkn-vbelp.
    endif.
endif.
append xkomdlgn.

How to create inbound delivery (for ASN)?

Hi,
I am looking for a Bapi or a FM to create an inbound delivery for Advance shipment notification (ASN). This function module for creating will be called in the user-exit in the invoice posting idoc program. The manual way to create this inbound delivery is by VL31N. Any help and there experience will be appreciated.
Thanks
Ramesh

Hi,
I am calling this FM after creating a PO with BAPI PO_CREATE1 and it works. I also get the delivery number.
Only create if there were no errors with the po
read table return with key type = 'E' transporting no fields.
check sy-subrc <> 0 and testrun <> 'X'.
read table poschedule into ls_schedule index 1.
ls_del_header-delivery   = lv_del_no.
call function 'CONVERT_DATE_TO_INTERNAL'
    exporting
      date_external            = ls_schedule-delivery_date
    importing
      date_internal            = ls_del_header-deliv_date
    exceptions
      date_external_is_invalid = 1
      others                   = 2.
if sy-subrc <> 0.
    clear ls_ret2.
    ls_ret2-message = 'Anlieferung Fehler bei Datumskonvertierung!'.
    append ls_ret2 to return.
endif.
ls_del_header-deliv_time = sy-uzeit.
For each position create single delivery
loop at poitem into ls_po_item.
    clear: ls_del_item.
    ls_del_item-delivery   = lv_del_no.
    ls_del_item-deliv_item = ls_po_item-po_item.
    ls_del_item-deliv_qty = ls_po_item-quantity.
    ls_del_item-unit      = ls_po_item-po_unit.
    ls_del_item-po_number = poheader-po_number.
    ls_del_item-po_item   = ls_po_item-po_item.
    ls_del_item-po_number = LV_EXPPURCHASEORDER.
    insert ls_del_item into table lt_del_items.
endloop.
Create delivery
call function 'BBP_INB_DELIVERY_CREATE'
    exporting
      is_inb_delivery_header = ls_del_header
    importing
      ef_delivery            = ls_likp-vbeln
    tables
      it_inb_delivery_detail = lt_del_items
      return                 = lt_return.
loop at lt_return into ls_return.
Convert return table to bapiret2
    call function 'BALW_RETURN_TO_RET2'
      exporting
        return_in = ls_return
      importing
        return_ou = ls_ret2.
    append ls_ret2 to return.
endloop.
commit work and wait.

Problem with HU during creation of Inbound Delivery using IDoc

Hi,
When I am creating Delivery manually and perform Packing, Handling Unit information is stored in VEKP and VEPO tables.
But when I am processing through IDoc, after passing data to Handling Unit Segments E1EDL37 (Handling unit header), E1EDL39 (Control Segment for Handling Units), E1EDL44 (IDoc: Handling Unit Item - Delivery), It is creating delivery successfully but Handling Unit information is not getting stored in VEKP, VEPO tables.
Tried most of the notes 912470, 678464, 682506 and all of them say "<i>You use the Idoc DESADV to create inbound delivery with packing data. The delivery is created, Idoc gets status 52 but the Handling Units (HUs) are missing. This is due to a program error. In case the IDoc contains segments to create HUs (E1EDL37), the IDoc processing should end in error status (51) as long as no packing data could be created</i>.".
Need your advice whether we have to maintain any customizing for this or how to proceed with it.
Thanks in advance,
Murali.

IDocs and BAPIs sometimes behave differently than transactions. You might need to add a user exit specifically for IDoc processing. Otherwise send a message to SAP and have them look at it.

Exit or Badi to prevent MIGO Goods Receipt on PO with Inbound Delivery

Hi,
I am hoping that someone can provide me with some direction on how to prevent the use of MIGO for GR when the PO being received is (or should be) linked to an inbound delivery.
For purchase orders with a confirmation control key an inbound delivery is to be created and the goods receipt needs to be done from the inbound delivery. This scenario also includes the case of stock transport orders whereby an inbound delivery is created form the outbound delivery. On the other hand for purchase orders without a confirmation control key no inbound delivery is created and the MIGO transaction is to be used to post the goods receipt.
Since both processes are possible, I would like to prevent people from posting the GR using MIGO if certain conditions pre-exist.
Can anyone suggest a means to accomplish this goal? Is there an exit or badi in MIGO that you would suggest using?
Thanks,
Paul

Hi,
The following user eixts and badis available for migo transaction:
Enhancement/ Business Add-in            Description
Enhancement
MB_CF001
Customer Function Exit in the Case of Updating a Art. Doc.
MBCF0011
Read from RESB and RKPF for print list in MB26
MBCF0010
Customer exit: Create reservation BAPI_RESERVATION_CREATE1
MBCF0009
Filling the storage location field
MBCF0007
Customer function exit: Updating a reservation
MBCF0006
Customer function for WBS element
MBCF0005
Article document item for goods receipt/issue slip
MBCF0002
Customer function exit: Segment text in article doc. item
Business Add-in
MB_RESERVATION_BADI
MB21/MB22: Check and Complete Dialog Data
MB_QUAN_CHECK_BADI
BAdI: Item Data at Time of Quantity Check
MB_PHYSINV_INTERNAL
Connection: Core Inventory and Retail AddOn
MB_MIGO_ITEM_BADI
BAdI in MIGO for Changing Item Data
MB_MIGO_BADI
BAdI in MIGO for External Detail Subscreens
MB_DOC_BADI_INTERNAL
BAdIs when Creating an Article Document (SAP Internal)
MB_DOCUMENT_UPDATE
BADI when updating article document: MSEG and MKPF
MB_DOCUMENT_BADI
BAdIs when Creating an Article Document
MB_CIN_MM07MFB7_QTY
Proposal of quantity from Excise invoice in GR
MB_CIN_MM07MFB7
BAdI for India Version exit in include MM07MFB7
MB_CIN_LMBMBU04
posting of gr
MB_CHECK_LINE_BADI
BAdI: Check Line Before Copying to the Blocking Tables
ARC_MM_MATBEL_WRITE
Check Add-On-Specific Data for MM_MATBEL
ARC_MM_MATBEL_CHECK
Check Add-On-Specific Criteria for MM_MATBEL
If it is helpful rewards points
Regards
Pratap.M

How to know that the purchase order link to which inbound delivery ?

Dear Support ,
I am looking for one way which can check which purchase order ( only for trading goods ) link to which inbound delivery ....
Now my way is use the purchase order number as a condiction to check in LIPS table , but i think this is a stupid way , right ?
In fact , i am writing one report which can show all the Open Purchase Order ( Only for trading goods and already created the inbound delivery & shipment costs ) which can do the MIGO without the problems ....
Has any way to check it ?
Many thanks .....
Best Regards
Carlos

PO and inbound delivery link.
In PO item , Conformation Tab : conf ctrl. if its is active U can GR with inbound delivery only (VL31N)
and not with MIGO.
rep
VL06I - Inbound Delivery Monitor
V_UC_7 - Incomplete Inbound Deliveries
VL06I Inbound Delivery Monitor
VL06IC Confirmation of putaway inb. deliv.
VL06ID Inbound Deliveries for Distribution
VL06IF Selection inbound deliveries
VL06IG Inbound deliveries for goods receip
VL06IP Inbound deliveries for putaway.
Go to --Information systems > General report selection > Logistics execution > shipping
REWGDS

Inbound Delivery Index Table

Similar Messages

Maybe you are looking for