MV50AFZ1 inbound delivery

hi all,
I am using the user exit MV50AFZ1 for transaction VL31N, but in some cases internal tables ekko & ekpo are empty. Some body have any idea about it. Is it depend of the purchase order ??
Thanks in advance.
regards marisol

Would you be kind enough to tell us how you solved it?
Greetings,
Blag.

Similar Messages

  • Making Order Acknowledgement (AB) a mandatory for Inbound delivery

    Dear All
    Kindly let me know wether is it possible to make the order acknowledgement a mandatory  before creating an Inbound Delivery.
    I.e., with OA the inbound delivery is not tpo be created by user.
    If it is possible please revert your answer
    Regards
    Chaitanya

    It is not possible to make the 'AB' as mandetory in confimation in PO before creating inbound delivery but while creating inbound delivery u can check whether AB is created in PO in userexit of delivery  mv50afz1 and control user to create the inbound del if there is no ab created.

  • Save STO in inbound delivery

    Hi Gurus,
    Requirement is to save Stock transfer order number in Inbound delivery line item when STO is created in SAP.STO will be captured in purchase order level as reference field.
    ME_PROCESS_PO_CUST is this BADI can be used.Pls suggest
    Regards
    Ravi

    U can use Program MV50AFZ1
    and code can be written  in
    FORM userexit_save_document.
    ENDFORM.

  • Dump during inbound delivery creation with VL34

    Hi,
    when I try to create a inbound delivery for a Purchase order item with account assignment Q (project stock) I get the following dump
    Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
    Except.                CX_SY_OPEN_SQL_DB
    Date and Time          28.07.2010 17:37:10
    Short text
         The ABAP/4 Open SQL array insert results in duplicate database records.
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "SAPLV05I" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
          in
         procedure "SD_PARTNER_UPDATE" "(FUNCTION)", nor was it propagated by a RAISING
          clause.
         Since the caller of the procedure could not have anticipated that the
         exception would occur, the current program is terminated.
         The reason for the exception is:
         If you use an ABAP/4 Open SQL array insert to insert a record in
         the database and that record already exists with the same key,
         this results in a termination.
         (With an ABAP/4 Open SQL single record insert in the same error
         situation, processing does not terminate, but SY-SUBRC is set to 4.)
    Missing RAISING Clause in Interface
         Program                                 SAPLV05I
         Include                                 LV05IU15
         Row                                     1
         Module type                             (FUNCTION)
         Module Name                             SD_PARTNER_UPDATE
    Trigger Location of Exception
      Program                                 SAPLV05I
        Include                                 LV05IU15
        Row                                     480
        Module type                             (FUNCTION)
        Module Name                             SD_PARTNER_UPDATE
    When I try to create the inbound delivery with VL31N it works fine. I also tried a couple of BAPIs/FMs which gave me the same dump as VL34.
    Thanks in advance!!
    br
    Walter

    I also failed to find any OSS note relevant to this.
    If you are not using any exits / BADI, there's no standard modification, you should contact SAP AG and their responsibility is to correct the error.
    But it may happen that you are using your own logic (via user exit, BADI, standard modification), in this case you have to find out what causes the problem. If the error is becasue of your develoments, then you cannot ask SAP AG to correct the error, if the error is not caused by your developments then it's SAP AG's responsibility.
    Please read OSS note 575667 which says that:
    The most common cause for this runtime error is an incorrect logic in USEREXIT_SAVE_DOCUMENT_PREPARE or USEREXIT_SAVE_DOCUMENT in include MV50AFZ1.
    For this, read also notes 178328 and 415716.
    Edited by: Csaba Szommer on Nov 3, 2010 8:49 AM
    Edited by: Csaba Szommer on Nov 3, 2010 8:50 AM

  • Creation of inbound delivery without reference to a PO

    Dear gurus,
    Let's say that a normal inbound flow is something like this:
    PO > Create inbound delivery with reference to PO > inbound shipment > Transfer Order > Confirm Transfer Order > Post Goods Receipt > Putaway
    Issue:
    My client does not want to create the PO because the PO serves no purpose to them. They want the process to start from inbound delivery.
    Question:
    1. Can a standalone inbound delivery be created WITHOUT reference to a PO ? If yes, please tell me the configuration and transaction code involved in order to create this standalone inbound delivery.
    2. Based on standard configuration, can an inbound delivery be created automatically with reference to a material document (for eg MIGO Mvt Type 501). Once again, for this scenario, no PO should be involved. If yes, please tell me the configuration and transaction code involved in order to trigger the creation of this inbound delivery (I'm not looking for the answer of an inbound delivery creation BAPI to being triggered directly after the creation of the Material Document).
    3. Based on standard configuration, can an inbound delivery be created manually with reference to a material document (for eg MIGO Mvt Type 501). Once again, for this scenario, no PO should be involved. If yes, please tell me the configuration and transaction code involved in order to create this inbound delivery.
    Thanks.

    Hi Peter,
    Actually, my intention is not really to create an inbound delivery based on a goods receipt. Since my client is not keen on the idea of creating a PO, I'm actually trying to provide alternatives and workarounds. From what I have gathered, I already know this much
    -> An inbound delivery must be created with reference to PO unless Handling Unit Management is activated. If Handling Unit Management is activated, the creation of a Material Document will trigger the creation of an inbound delivery (I havent tested this out yet). Therefore, a PO will not be necessary in this case.
    I was kind of expecting answers along this line, unless of course, something better pops up. Maybe someone out there may know something more.
    As for Handling Units, I'm not familiar with it. Hopefully somebody can give me a good configuration guideline on what to do in order to activate it so that I can simulate the scenario of a Material Document triggering the creation of an inbound delivery (I'm not looking for the kind of answers which simply cuts and pastes the SAP HELP URL, 4.6C Handling Unit PDF, Best Practice Document and etc). Hopefully somebody out there can really give me a good guideline on how to do this.
    Thanks..

  • Creation of Inbound delivery mandatory for ASN process in classic scenario?

    Dear Experts,
    We are going for classic scenario for our green field SRM implementation process. Our client is not using  ASN process in their existing MM process. However, they are now looking for an oppurtunity to enable Suppliers to trigger ASN using SUS. In such case, is creation of inbound delivery from Buyer side a mandatory process?
    Is the below the process correct?
    PO -> ASN (Supplier using SUS) -> Inbound delivery (Optional) -> Goods Receipt (Mandatory) -> Invoicing.
    Here, I understand that Goods receipt can be verified against the PO or via Inbound delivery to PO. ASN will inform the store keeper in advance about impending goods receipt and smoothen the confirmation process.
    Could you please comment on the above process? Could you please suggest the best practices followed here?
    Thanks and regards,
    Ranjan
    Ranjan Sutradhar

    Hey Ranjan!,
    You are on track.
    The process flow you have shown is true. ASN is available as a standard as part of the MM-SUS process. It makes the buyer aware of any delays in delivery or to make arrangements on shipping docks to receive goods on a said date etc.
    Regards,
    Nikhil

  • ASN creation based on ECC inbound delivery

    Hi All,
    I have a scenario in which we are creating an inbound delivery in ECC and corresponding ASN should be created in supplier system.
    In order to achieve this functionality of ECC to supplier system is there any way to map this functionality through any custom development ?
    Kindly suggest
    Thanks
    Gaurav Gupta

    Hi,
    What I understand from the requirement is - The Supplier dispatches the material to Purchasing company & informs about the same via ASN. This ASN triggers inbound delivery in ECC. When the material reaches the Purchasing Company, GRN is posted with reference to the Inbound Delivery.
    Is this correct?
    If so, you can achieve this through RFC function, which can be called from vendor ERP system or through Vendor Portal by directly calling the RFC or by using Web Service.
    Regards,
    Prashant

  • Error in creation of inbound delivery

    hi
    When I tried to create inbound delivery against schedule agreement
    1) Following warning message is coming when I enter the quantity for each and every line item
       u201CAcknowledgment for PO item contains data varianceu201D
    2)Following error message is coming when I saved the delivery
    u201CTermination during purchase order updateu201D
    So I am unable to create the inbound delivery
    Note: this error is coming for a particular vendor only

    Hi ,
    Goto SM13 .
    Find the terminations based on user and creation date.
    Get the same analysed by ur ABAP team.
    Also check the confirmations in PO at Item level.
    Regards
    Ramesh Ch

  • Inbound Delivery: Inbound WHSCON IDoc with Batch Split - HowTo...?

    Hello
    We have another tricky problem to solve on our ERP 6.0 system.
    My colleagues of Lindt UK create manually inbound deliveries (VL33N) which are replicated to the warehouse (DESADV IDoc -> TRADACOMS.ORDHDR).
    When the goods arrive at the warehouse they send back a good receipts message (TRADACOMS.DLCHDR -> WHSCON IDoc).
    In some cases we have a batch split because the goods have been put into different storage locations. Example:
    - item 10: 200 Cases of product 4711, batch 10-2011,  in storage location '0001' (free available for Sale)
    - item 10:     5 Cases of product 4711, batch 10-2011, in storage location '0004' (damaged)
    I am aware that in the inbound WHSCON item 10 is a main position and the two actual batch split positions are sub-items (900001 & 900002 with HIPOS = '10'). I tried to used E1EDL19-QUALF = 'BAS' (= batch split) with the sub-items but failed so far to update the inbound delivery that I can see the batch split.
    I have managed to get one sub-item but not 2 of them. Somehow the system aggregates the quantities for both sub-items into the single item that shows up in the inbound delivery.
    When we send the inbound delivery to the warehouse the item looks like this:
    - item 10: 200 Cases (no batch yet, Putaway quantity = 0, because these data are coming from the warehouse).
    QUESTION: Has anybody else been faced with a similar (if not identical) problem and how did you solve it?
    Thanks a lot in advance for your valuable input.
    Regards
      Uwe

    Hello Finbarr
    I assume that you do NOT send any (suggested) batches to your warehouse. Otherwise you would have the same problem like we have that the WHSCON cannot overwrite a (suggested) batch.
    However, if you just send the quantity per item then the batch split is much simpler than you suggested:
    "First E1EDL24 segment:
    POSNR     50
    MATNR     000000000000602006
    MATWA     000000000000602006
    CHARG     L1519   " <<< first batch
    LFIMG     37.000
    VRKME     CT
    "Second E1EDL24 segment:
    POSNR     50
    MATNR     000000000000602006
    MATWA     000000000000602006
    CHARG     L1880   " <<< second batch
    LFIMG     37.000
    VRKME     CT
    Well, and as qualifier we use: E1EDL19-QUALF = 'XYZ'  " a dummy
    The SAP system is smart enough the realize that these two E1EDL24 segment belong to the same item yet have different batches and, therefore, yield a batch split in the delivery. The system generated the 9xxxxx numbers for this sub-item lines automatically.
    Although I believe that it is not possible to change a batch in the delivery using an inbound WHSCON I would appreciate to have a final proof of this assumption. I could imagine that if you first delete the item containing the suggested batch and then add a new item with the actual batch from the warehouse it might works. However, this would require to implement a user-exit which I do not prefer.
    Regards
      Uwe
    PS: It seems I gave an answer to the wrong question (should be EDI (DESADV): Can batches be overwritten by an inbound WHSCON (pick conf)? )

  • Reg: How to capture the Excise Invoice with respect to Inbound delivery

    Hi All,
    Please give the process follow for capturing the excise invoice with respect to inbound delivery.
    Thanks & Regards
    Siva

    Hi Siva,
    Please check this link
    CIN with Example..?
    Regards,
    Bijoy Kumar

  • SAP System inconsistency for Inbound delivery / MIGO and a "sap note"

    Hello Friends ,
    After following SAP instruction on how to remove the inconsistency between posting GR through MIGO (Inv. mang.) and the reflection of the goods movement status in the inbound delivery document - done that using sap note 570991
    the problem is that the system start behaving in a weird way throwing unjustified Error messages for any suggested goods receipt using MIGO with reference to inbound
    for example after creating an inbound delivery document and trying to post it via migo , an error will pop up
    - Inbound delivery storage location cannot be changed to here Message no. VLA316
    the thing is i didn't even maintain any storage location entry up to that point and yet i cannot post any stock !!
    also another error  like
    - Inbound delivery batch cannot be changed to *** here
    which doesn't make any sense because there is not batches in the inbound document !!
    i think this behavior is coming from the "Document Flow Update for Stock Postings" inbound  indicator  at the shipping parameter at client level customization
    i need help on  how to overcome this annoying SAP Bug/Problem specially i am in a post go live critical situation

    Hi,
       The messages you mentioned were introduced to avoid inconsistency between inbound delivery and IM, through the note:  1050944 - GR for inbound delivery using inventory mgmt as of ECC 6.00
       If the messages are issued incorrectly, then you may check for SAP notes (I couldnt find anything relevant) or raise an OSS ticket to SAP.
    Regards,
    AKPT

  • 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.

  • Purchase order and Inbound delivery

    Hi gurus,
    Im trying to create an inbound delivery with reference to purchase order. In the configuration i've created a new delivery type similar to EL and said Yes to all the copy controls that system asks. When im creating the inbound delivery with reference to the PO it is picking up the standard EL delivery type instead of the one that i created. What did i miss here? I want the inbound delivery type that i created be the default inbound delivery type for that particular order type.. pls suggest
    cheers
    Joseph

    Hi Joseph,
    Just check whether the newly created delivery type is assigned to the Confirmation Category LA under the below path:
    SproMaterials ManagementPurchasingConfirmationsDefine Internal Confirmation Categories
    Regards
    Ramesh Ch

  • PO qty and Value with Inbound Delivery qty

    Dear all
    i have a report requirement, client wants to have a report on the basis of Inbound delivery qty. for eg.
    If Po qty is 100 @ $10.00 each Total Po value = $1000
    if he makes a inbound delivery of 20 qty Report should display outstanding delivery qty as 80 and with reduced value .of $800
    Pl tell me how to get these details.
    Regards
    Manoj

    Hi Manoj,
    I think you should should copy ME2M and change the output.
    Sanjeev

  • 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

Maybe you are looking for