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

Similar Messages

  • Return(inbound delivery) creation through VL01N

    Hello,
    I wud like to create Return(Inbound) delivery through VL01N transaction. Following is the process i' m following.
    1. create notification through IW51
    2. create repair order through IW52
    3.create return delivery ( automatically) through VL01N with reference to repair order created in step no.2.
    I have searched for Function module & BAPI, but it seems there are no FM & BAPI's for such requirement.
    Can any one suggest me the Functional solution for above problem.
    Thanks,
    Anil

    Normally from the Notifications, We create a Return Order ( Document Type  RE) automatically.  We need to the necessary configurations.
    We can create the Return Delivery from VL01n. when you mention the return sales orde there the system automatically pulls the return Delivery type LR from the configuration of the sales document type RE.
    otherwise you have to mention explicitly the document type = LR in the selection screen of Vl01n.
    You Can use the same BAPI or FM ( the one used to create the Outbound Delivery ) and mention the document type as LR.

  • Inbound delivery creation through IDOC

    Dear Experts,
    I have scenaris like one STO with multiple deliveries with same materials and the same assigned to shipment, through the shipment out put IDOC will generate and created the inbound delivery, the same hace to updated the STO.
    in the above scenario, inbound delivery is creating base don the outbound delivery items through IDOC (in case the same material is available in the different deliveries it is getting copied)
    by in my case inbound deliveri has to created bbased on the STO items. can you please let us know how to develop the logic for the same and is there any function modules for the same.
    Please keep in mind if the same materila with same batch is in outbound delivery we have to cosolidate the same and create one line item in inbound delivery.
    awaiting your response soon. please help me out with IDOC programe and tables and fields with function modules.
    Thanks & ragrds
    Raju.

    Dear,
    so for no updates , can you let us know your possible solution to take up this challange.
    Thanks
    Raju.

  • Inbound Delivery creation in ECC6.0 through IDoc (DELVRY03.DESADV)

    Inbound Delivery creation in ECC6.0 through IDoc (DELVRY03.DESADV)
    From SCM ICH system Supplier creates ASN on the WEBUI & sends it ECC 6.0 using XI.
    This is Proxy (DespatchedDeliveryNotification) to IDOC (DELVRY03.DESAV) scenario
    But at the receiver end i.e. ECC6.0 its giving me error at Tcode WE02 as action is not supported.
    Can you suggest me how to tackle this issue.
    Thanks in Advance.
    Regards,
    N>B.Shanmukha

    hi,
    >>>giving me error at Tcode WE02 as action is not supported.
    there are many segments in delvry03 with a first field - action (like, delete, create, 001,002, etc)
    check all of them as probably you're using one which is not supported
    and this is the real cause of the error
    you can check it like this:
    open this IDOC in We19
    then open action field and F4 and see if the one you use in the idoc is in F4
    change the wrong one and it will work :for 100%
    Regards,
    Michal Krawczyk

  • Auto Inbound delivery creation

    Hi Sapgurus,
    I am trying to create Inbound delivery from Outbound delivery after it has been PGI'ed. These both are related to Intracompany STO. We have WM implemented so both of these deliveries result in TO creation and can be closed only after TO confirmations. I used SAP notes which stated to use SPED output type in output determination procedure for outbound delivery and then assign output determination procedure to delivery type. But I was not successful in getting the desired results.
    Can anyone please provide me with the steps of this configuration, I may be doing wrong something somewhere.
    Appreciate the help.
    Thanks in advance
    Manav Anand

    Hi,
    I think you are talking about stock transfer between two plants. I assume your requirement is after PGI of the replenishment delivery system should create automatic inbound delivery in second warehouse,right?
    You can create inbound delivery automatically for second warehouse.I had such scenario in my previous client.I believe through some user exit you can initiate inbound delivery creation immediately.
    Please check with your technical person.
    Regards,
    PRashant

  • Inbound delivery creation using VL31N

    Hi All,
    I could find that the message type DESADV, IDoc type DELVRY01 and process code DELS is used for creation of this.
    Let me know if this is correct. When i checked in my system I could not find process code DELS. Do i need to do some additional settings to get this.
    What is difference between IDOC type DELVRY01 and DELVRY03. Which one should be used.
    Here the ASN received is triggering inbound delivery creation.
    Please let me know on this.
    Regards,
    Shahu

    Hi,
    Where did you check that process code in WE64?
    Check in the correct set(Inbound messages).
    DELVRY03 is the latest one. You should use it only.
    Regards,
    Ravi

  • Check amount of transition stock during inbound delivery creation

    I want to move stock between plans, therefore I have the following steps:
    1. Stock Transfer Order (STO), e.g. 500 pieces
    2. Sending plant: MIGO (GI for STO) with MT 351 to post to transition stock,  e.g. 100 pieces
    3. Receiving plant: Inbound Delivery with reference to STO VL31N
    4. process Inbound delivery in warehouse (SAP-WM)
    The question is:
    During step 3, when accessing VL31N the system proposes the full order quantity (e.g. 500 pc.)
    I can change the amount to any amount I like, e.g 240 pieces.
    How can I tell SAP, that Inbound delivery creation is only possible for the amount
    which has been posted to stock in transition (100 pieces)
    I want an error/warning message in case user wants to create Inbound delivery quantity higher than the amount that has been posted to transition stock.
    Any ideas?

    MIGO in sending Plant?
    How it is possible? MIGO means, Goods receipt. This should be in Receiving plant.
    Sending plant should do the PGI
    MIRO in receiving plant
    Billing in sending plant
    Payment from Receiving palnt and clearing in sending plant
    Correct me if i am wrong
    Thanks

  • ASN from vendor and inbound delivery creation

    hi
    I have a scenario where vendor sends ASN via EDI to R/3.
    This inbound ASN should create an inbound delivery. 
    Can you please help me knowing the idoc type, message type etc which will serve my purpose.
    Also the FM / Badi for inbound delivery creation.
    thanks in advance,
    Jo

    Hi,
    Use DESADV Message type and basic type DESADV01
    Use function module IDOC_INPUT_DESADV
    Edited by: Chandra Shekhar Singh on Jul 5, 2011 12:39 PM

  • Issue with Message Type Triggering during Inbound Delivery Creation

    Hi Experts,
    Hi Experts, 
    Currently we are facing issue with message type triggering during inbound delivery creation:
    In NACE transaction for Inbound delivery we have 3 custom output types:
    Pricing Procedure Used is standard one -> E10001
    Z140  Inbound Delivery Create  (This should get triggered when IB delivery is created)
    Z141  Inbound Delivery Change (This should get triggered when IB Delivery is changed)
    Z142  Inbound Delivery Delete(This should get triggered when IB Delivery is deleted).
    At present if i check delivery in  VL33 -> Extras -> Delivery Output
    Both  Z140 and Z141 are being triggered during IB delivery creation. While it should be only Z140.
    Could you please suggest that are we missing any configuration in SPRO or we need to create any custom routine (requirement) to handle this?
    Thanks

    Hi,
    There is no fine-tuned control for inbound delivery messages as for Purchase order. Hence I guess to meet your above requirement, you have to go for a custom solution similar to the PO fine tune control settings.
    Thanks,

  • User exit to change partner for inbound delivery creation

    Hello,
    I have a requirement to change the partner number for
    the inbound delivery creation.
    I only see the USEREXIT_MOVE_FIELD_TO_LIKP but I am not sure if this is
    the right user exit for this requirement.
    Is there the user exit for modifying partner in the inbound delivery?
    Thanks in advance,

    HI
    There is a program with which you can find the available exits as per your requirement. You have to execute the same and give your transaction code. Hope this helps...
    *& Report  ZFINDUSEREXIT
    report  zfinduserexit.
    tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
    tables : tstct.
    data : jtab like tadir occurs 0 with header line.
    data : field1(30).
    data : v_devclass like tadir-devclass.
    parameters : p_tcode like tstc-tcode obligatory.
    select single * from tstc where tcode eq p_tcode.
    if sy-subrc eq 0.
    select single * from tadir where pgmid = 'R3TR'
    and object = 'PROG'
    and obj_name = tstc-pgmna.
    move : tadir-devclass to v_devclass.
    if sy-subrc ne 0.
    select single * from trdir where name = tstc-pgmna.
    if trdir-subc eq 'F'.
    select single * from tfdir where pname = tstc-pgmna.
    select single * from enlfdir where funcname =
    tfdir-funcname.
    select single * from tadir where pgmid = 'R3TR'
    and object = 'FUGR'
    and obj_name eq enlfdir-area.
    move : tadir-devclass to v_devclass.
    endif.
    endif.
    select * from tadir into table jtab
    where pgmid = 'R3TR'
    and object = 'SMOD'
    and devclass = v_devclass.
    select single * from tstct where sprsl eq sy-langu and
    tcode eq p_tcode.
    format color col_positive intensified off.
    write:/(19) 'Transaction Code - ',
    20(20) p_tcode,
    45(50) tstct-ttext.
    skip.
    if not jtab[] is initial.
    write:/(95) sy-uline.
    format color col_heading intensified on.
    write:/1 sy-vline,
    2 'Exit Name',
    21 sy-vline ,
    22 'Description',
    95 sy-vline.
    write:/(95) sy-uline.
    loop at jtab.
    select single * from modsapt
    where sprsl = sy-langu and
    name = jtab-obj_name.
    format color col_normal intensified off.
    write:/1 sy-vline,
    2 jtab-obj_name hotspot on,
    21 sy-vline ,
    22 modsapt-modtext,
    95 sy-vline.
    endloop.
    write:/(95) sy-uline.
    describe table jtab.
    skip.
    format color col_total intensified on.
    write:/ 'No of Exits:' , sy-tfill.
    else.
    format color col_negative intensified on.
    write:/(95) 'No User Exit exists'.
    endif.
    else.
    format color col_negative intensified on.
    write:/(95) 'Transaction Code Does Not Exist'.
    endif.
    at line-selection.
    get cursor field field1.
    check field1(4) eq 'JTAB'.
    set parameter id 'MON' field sy-lisel+1(10).
    <b>Do reward if useful...</b>
    Regards
    Dinesh

  • 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

  • How to restrict inbound delivery creation by incomplete log

    Guru's
    I have a requirement of not to create an Inbound delivery if the filed in the "means of trans id " in the delivery header is 'BLANK".If i create an incomplete log for the field LIKP-TRAID (Warning message enabled) for Delivery header in transcation OVA2 .Now if i create an inbound delivery  with "means of trans id " BLANK .It is giving only warning message it is not stopping me from creating an Inbound delivery .
    Can you please let me know whether we can restrict creation of inbound delivery.
    Thanks

    Try through user exit,If system does not find the means of trans id then syem stops to crete inbound delivery.Chcek this user exit V50Q0001 with your ABAPer it may help you.

  • SPED inbound delivery creation, serial num not getting copied from out delv

    We enabled SPED to create inbound delivery against outbound delivery
    We observed Serial numbers are not getting copied from outbound delivery to inbound deliver
    can some one help
    Moderator message:
    Locked. Reason: duplicate.
    The new post: STO GR against outbound delivery/inbound delivery
    Edited by: Csaba Szommer on Jan 9, 2012 4:16 PM

    Hello Mohammed,
    Go through these SAP Help Pages for Delivery Creation from SAP TM. It will help you to check where have you gone wrong is the setup.
    Creation of ERP Deliveries from SAP TM:
    ERP Logistics Integration - SAP Library
    Creation of Delivery Proposals:
    Creation of Delivery Proposals - ERP Logistics Integration - SAP Library
    Monitoring of Delivery Creation:
    Monitoring of Delivery Creation - ERP Logistics Integration - SAP Library
    Kindly let me know if it works, or else give me some more detail regarding your steps you are doing and your scenario. It might be helpful to understand and then I can provide you a solution.
    Thanks and best regards,
    Navin

  • Inbound delivery creation in STO via EDI/Idoc

    Hello experts,
    My requirement is like this:-
    Stock transfer order is created for supplying plant 2000 & receiving plant 2010.
    When the supplying plant 2000 posts an outbound delivery & PGI, at same time an Inbound delivery should be created in receiving plant 2010.
    I know theoretically that this is achieved by making confirmation settings & output types. But don't know exactly how to configure it.
    Can you please mention the process?
    I have referred the scn threads:
    Outbound Delivery to Inbound delivery by using IDOC
    how to configure the message control for DESADV
    SAP note 111903
    Receiving Vendor Confirmations via EDI - Purchasing (MM-PUR) - SAP Library
    But there is lack of clarity from my side.

    You do not need to use EDI messages to get an inbound delivery created when a PGI is done on the outbound delivery.
    Search for the config on the SPED output type. This SPED output message can be triggered during the PGI which results in the creation of an inbound delivery in the receiving plant.
    The receiving plant will have to maintain the confirmation control key 0004 at item level in the purchasing document.
    Link to SAP help Automatic Creation of Inbound Delivery - Transfer and Inventory Management - SAP Library
    Refer SAP note 1119073 point 3 and note 965176
    Regards,

  • Inbound delivery Creation(ASN) Process

    Hi All,
    Plz give end to end Process for creation Inbound delivery(ASN) No.
    why should we take conformation control key in PO and not shipment notification tab there
    thanks,
    sunil sahoo

    Config:
    go to SPRO-MM-purchasing-Confirmation-setup confirmation control
    here select the 10 and check the check box Create inb delivery
    then select the line and click on the confirmation seq and make GR relevant, MRP relevant and GR assign (all three box checked)
    Process Flow: -
    1. ME21N - In PO, Confirmation Tab, select the confirmation control key as "Shipping Notification" or "Inbound Delivery"
    2. VL31N - Create Inbound Delivery w.r.t. PO
    3. MIGO - Goods Receipt > Inbound Delivery
    If you dont select the conformation control key in the PO than system wont allow you to create the Inbound delivery agianst thePO.

Maybe you are looking for