Returns Processing using Inbound delivery transaction VL31N or BORGR

Hi Experts ,
Our business Requirement is to use VL31N /BORGR to process the return deliveries .
The Standard Functionality of this transaction is restricted to manage the Inbound Processing (Deliveries from Suppliers u2013 Document Category u20187u2019 (Shipping Notification) .
My question is can we enhance the SAP code to process the retuns delivery .
Is it possible to achieve this functionality via Customizing .
If anyone had such business requirement and if you a solution for this please help << Moderator message - Everyone's problem is important >>.
Regards,
Rupa
Edited by: Rob Burbank on Oct 19, 2010 3:25 PM

Hi ,
Which kind of return delivery are you speaking about?
Yes the deivery is return to vendor .
Yes we will be create the return delivery using VL01N with reference to returns Sales Order .
But after this oulbound deilvery is created Our business requirement to use BORGR transaction to process it further.
The BORGR transaction is used for Admin Goods reciept multi GR Posting and it used to handle only the inbound deliveries only .
I want to know is it possible to completly process the oubound deliveries using an inbound dleivery transaction if we modify the SAP code .
Just want to know if i modify the SAP code using enhancements will the existing SAP code of this program support such deliveries .
Regards ,
Rupa

Similar Messages

GR Blocked stock process in Inbound delivery.

Hi All,
I want to do the GR blocked stock process through inbound delivery.
But while i create Inbound delivery, system is automatically picking 101 movement type.
How to proceed.
Thanks in advance
Regards
KK

Check in
Spro -> sd -> sales -> sales documents -> sales docu item -> define item categories
Here i think the entry for your Z item category is not done, please take the help of your SD personnel & the issue should be resolved.
Hope the above helps.
Regards,
Vivek

Goods Receipt using Inbound Delivery with reference to Outbound Delivery

Here is our scenario that we need help finding a solution:
1. Multiple Intracompany POs created
2. On the confirmations tab of the POs, we have u201CInbound Deliveryu201D Selected because the items need to be received in with Handling Unit management.
3. We have the Order Combination box checked on the shipping tab to allow 1 delivery to be created for multiple purchase orders.
4. We create only 1 Outbound Delivery for only available items on various purchase orders.
5. Due to being handling unit managed, we need to receive the items using an inbound delivery.
Problem: We need to find a solution to easily enter an outbound delivery number which will allow us to receive only the parts that were shipped (issued), via the inbound delivery process.
If we remove the confirmation control key, we can complete a Goods Receipt for Outbound Delivery in MIGO u2013 but is there a way to complete a goods receipt using an inbound delivery with reference to an Outbound Delivery?
Thank you for the help.

Hi,
You can work with Inbound delivery created via IDOC Triggered from Outbound Delivery, this will carry the HU Data as well. Please refer this wonderful note, which will explain you a lot of things, Note 1119073 - FAQ: Automatic inbound delivery creation for stock transfers
There are other notes also available for Inbound delivery creation with HU in STO, please browse the notes, if you find any difficulty.
Regards
Chandra Shekhar

BAPI_GOODSMVT_CREATE using inbound delivery with HU

I have a program that uses BAPI_GOODSMVT_CREATE to GR Post the inbound delivery. The inbound delivery is created thru ASN. But I encounter error message BORGR 637 "Inbound delivery cannot be packed". This error occurred because item packing status (VBUP-PKSTA) = 'C', the inbound delivery has HU items and is packed already. This cannot be avoided because deliveries coming from the ASN is possible to have HUs already. Is there a workaround with this or maybe the parameters used are wrong or incomplete ?
lv_grcode = '01'.
MOVE: sy-datum TO ls_header-pstng_date,
        sy-datum TO ls_header-doc_date,
        sy-uname TO ls_header-pr_uname,
        likp-vbeln TO ls_header-ref_doc_no,
        '2' TO ls_header-ext_wms.
    MOVE: gt_lips-matnr   TO lt_item-material,
          gt_lips-werks   TO lt_item-plant,
          '101'           TO lt_item-move_type,
          gt_lips-lgort   TO lt_item-stge_loc,
          likp-lifnr      TO lt_item-vendor,
          gt_lips-n_lfimg TO lt_item-entry_qnt,
          gt_lips-meins   TO lt_item-entry_uom,
          gt_lips-vfdat   TO lt_item-expirydate,
          likp-vbeln      TO lt_item-deliv_numb_to_search,
          gt_lips-posnr   TO lt_item-deliv_item_to_search,
          'B'             TO lt_item-mvt_ind.
    APPEND lt_item.
Thanks in advance

Hello Giancarla,
How you managed this situation, I mean, since you received no updates from this SCN topic how it was solved in your customer?
I am also facing the same problem and I am doing research with correction notes, additional BAPIs and reversal engineering in BORGR transaction code to find out a way to enable GR for packed materials.
Thanks in advance for your inputs.
Regards,
Luciano Ap. Souza

BAPI for Inbound Delivery(IBD - VL31N)

Hi all,
I need to create an inbound delivery with reference to PO using bapi which is retreived by an IDoc. I cannot use standard Process code to Create it because i need to do validations and convert UOM etc). In that i need to use Container No E1EDL37-EXIDV2(Idoc field).
May i know which bapi which suits for this requirement.
Thanks & regards
sreehari p

Hi Rajiv,
Please check this FM --> BAPI_DELIVERYPROCESSING_EXEC
Please check these threads
Bapi to create inbound delivery
BAPI to create inbound delivery
Hope this would help you.
Good luck
Narin

Supplier return processing with SD delivery

Hi
   I have a scenario where i have to return material to Vendor by Return PO and SD delivery .
So what are steps needed to populate shipping data in item details of Return PO.
Appreciate your help for this.
   Thanks
    Manoj

Hi,
Please refer to following thread
vendor returns
BR
Diwakar
reward if useful

Vendor return Process - Capture of delivery costs

My client has a scenario of vendor return with PO, where we indicate that the PO item is a return item. We use VL120B to create the DO and then do a PGI.
You can do the Vendor return with transaction MBRL as well. The accounting postings in this case will reverse the entire value including the delivery costs.
I do not have the same provision for PO returns. When we return the item through PO indicator, how to ensure that the item is return at WAC ?
Returning the item at Purchase Price without consideration of the deliver costs, will result in high WAC. How to resolve this issue. We cannot put negative in the condition type also, because system gives an error saying negative delivery cost is not allowed.
Could anyone advise on this?

Hi Bala,
Did you get a solution for this issue? I am facing the same problem and would be very grateful for any information.
Regards,
Nisha

Catch the inbound delivery number when VL31n is saved.

Hello Friends,
In order to get inbound delivery when VL31N is saved, i am using the BADI :
DELIVERY_PUBLISH ...this is having 2 methods.
1.PUBLISH_BEFORE_COMMIT ( having import parameter it_changed_data...this structure is having inbound delivery number)
2.PUBLISH_AFTER_SAVE (no parameters)
when i am saving ....i am able to get into <b>publish_after_save</b> ...how to get
that number into PUBLISH_AFTER_SAVE ?
With Ever Smile & Regards,
Madhu!!

I dont know about said BADI but i think you can use LE_SHP_DELIVERY_PROC which has documentation in EN also and there are several methods which can be used for delivery process.

Returns via Inbound Delivery

Hi All
If 100 items Goods are Receipted with a Purchase Order using Inbound Delivery. It is then discovered that the entire 100 items are damaged, what is the transaction to return these items
Vishnu

Hi,
You can use the normal 122 movement type.
Just because the items were received via inbound deliveries does not force you to return them via the same method.
So I would try the normal 122 option first.
Steve B

BADI for VL31N which has the Inbound Delivery Number as a parameter.

Hi,
I have a requirement that after creation of a new inbound delivery through VL31N the control should go to a custom screen. The new inbound delivery no. generated thru VL31N should be seen in this custom screen.
I am searching for a user exit or BADI for VL31N. This exit should have the Inbound delivery Number created through VL31N.
I tried many exits and BADIs. However, none of them have the Inbound Delivery No.
Please help.
Regards,
Jaya

The issue was resolved by the use of the BADI 'DELIVERY_PUBLISH'. Its method PUBLISH_AFTER_SAVE was used.
IF sy-tcode = 'VL31N' OR sy-tcode = 'VL32N'.
    DATA : v_tcode TYPE sy-tcode .
    FIELD-SYMBOLS: <i_del> TYPE likp.
    DATA: wa_likp TYPE likp,
                t_likp TYPE STANDARD TABLE OF likp.
    ASSIGN ('(SAPMV50A)LIKP') TO <i_del>.
    wa_likp = <i_del> .
    SET PARAMETER ID 'VL' FIELD wa_likp-vbeln .
ENDIF.

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.

Create inbound delivery VL31N

HI,
I have created new plant. When I make PO (UB) and then create inbound delivery in vl31n the vendor already appears and the vendor is what I entered in the PO as Supplying Plant.
Now when I do the same for the new plant the vendor does not appear automatically. What I forgot to customize ?
Thank you.

Hi ,
Greetings!
Generally, the vendor number is not populated to the PO/inbound delivery for intra company stock transfer.
However, if you to the following settings, the vendor number will be populated to the intra company stock transfer PO and subsequently to the inbound delivery.
SPRO -- > MM -- > Purchasing -- > Purchase order --> Define Document Types --> You have a check box "Stock transfer: Take vendor data into account". Check this.
Now if you create a new stock transfer PO with document type UB and create inbound delivery, you should get the vendor number.
Regards
Gobinathan G

What is inbound delivery? (Business process description required)

Hallow Experts !
Can anybody please explain the business process for inbound delivery in brief? For what we process or configure inbound delivery?
For example
we create purchase order for ordering the material from vendor.
We post Goods Receipt for purchase order or without reference to purchase order.
Like that what is the requirement or what is the prerequisite for the Inbound delivery?
Thanks in Advance !

Dear Vijay,
Please check this link:
http://help.sap.com/saphelp_46c/helpdata/en/28/1a2537a9d25f07e10000009b38f889/frameset.htm
BR
Csaba

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

Inbound delivery creation through VL01N

Hello,
I wud like to create inbound(return) delivery through VL01N t-code with reference of sales/repair order.
following things i am passing to VL01N screen:
1. Shipping point
2.delivery date = current date
3.repair / sales order number
4.delivery type
suggest me any FM / BAPI
Edited by: anilpat1 on Apr 7, 2009 8:39 AM

Hi,
Did you mean VL31N for Inbound delivery as VL31N is the transaction for Inbound delivery not VL01N.
Try this function module below if it is a collective processing.
function module GN_DELIVERY_CREATE.
let me know if it worked.
R,
Srini

Returns Processing using Inbound delivery transaction VL31N or BORGR

Similar Messages

Maybe you are looking for