SAP Standard INbound Delivery IDOC

Hi All,
Pease let me know the
Messahe type,Process Code and Basic Type, Function Module for Inbound Delivery
as well as which message type do i need to setup in NACR
Regards
Amey

Hello,
there is nothing to maintain in NACR for inbound delivery (MM).
FM creates Inbound delivery via IDOC.
Please refer to help.sap.com [EDI Inbound Processing of a Shipping Notification  |http://help.sap.com/erp2005_ehp_05/helpdata/EN/11/dcbd10bd9211d188ef0000e8216438/content.htm]
Andrzej

Similar Messages

  • Inbound delivery Idoc to create Batch with Characteristics

    Hi Experts,
    Need your help...
    We have the scenario where the inbound delivery in ECC is created by an external Idoc (DESADV). However the batch field is blank.
    Requirement is to create a batch per line item (as per the number range in ECC) during inbound idoc posting and assign the batch to the inbound delivery line item. This batch will also need to be populated with characteristics. (DESADV Idoc segments will carry these characteristics)
    Is there a way to achieve this..?
    Thanks,
    Krishna

    Thanks for the reply..
    Do you mean to say that its a standard functionality..? We are already using DESADV with DELS. However, we have modified our inbound idoc with Z Segments. These segments carry the characteristic values. No where in the idoc we have the batch number, as we want the batch number to be created automatically based on the number range in ECC.
    In such kind of cases, how to achieve this..?
    Thanks,
    Krishna

  • GR against Inbound Delivery (IDoc)

    Hi All,
    I am trying to post Goods Receipt against Inbound Delivery. What is the IDoc/Message Type I need to use for this and what segments I should populate?
    So far I have tried using...
    <i><b>MBGMCR02</b> - has serial numbers (errors out with a short dump and says "Cannot be processed with this transaction." Application VL and message Number 143. I don't know how to proceed further
    and <b>SHP_IBDLV_CONFIRM_DECENTRAL01</b>(this does not have serial numbers). IDoc was processed, but I am not sure what it updated. When I looked at the PO History it did not have a record for GR Inbound Delivery like you would see when you do the GR for Inbound delivery using MIGO.</i>
    Any help would be appreciated.
    Thanks,
    Sneha

    See the below link :
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    Reward Points if it is helpful
    Thanks
    Seshu

  • Inbound Delivery Idoc- Create ... help required

    Hi,
    I'm using DELVRY01 idoc to create deliveries. when i execute using test tool, the idoc gets created with error status 51 with following errors:
    Field EXIDV empty
    Message no. VL243
    Diagnosis
    A required field in the intermediate document (IDoc) is not filled. This is the field EXIDV in segment 000042.
    Field VHILM empty
    Message no. VL243
    Diagnosis
    A required field in the intermediate document (IDoc) is not filled. This is the field VHILM in segment 000039
    But these errors reflect to handling unit from segment E1EDL37 and its sub nodes which are really NOT required in my case.
    Now confused if i'm using a wrong reference of creating inbound delivery. Pls shre some thoughts on it on troubleshooting this issue.

    Hi Prabhu
    these two fields are mandatory .. fill below details
    E1EDL37-Handling unit header
    EXIDV     <XXXXXXXXXXXXX>     External Handling Unit Identification
    GWEIT     <LB>             Weight Unit Tare
    BRGEW     <000XX>                             Total Weight of Handling Unit
    VHILM     <Dummy Packing Material>     Packaging Materials
    E1EDL44-IDoc: Handling Unit Item (Delivery)
    VBELN     <Delivery nO>     Sales and Distribution Document Number
    POSNR     <900004>     Item number of the SD document
    EXIDV     <XXXXXXXXXXXXX> External Handling Unit Identification
    VEMNG     <00001>     Base Quantity Packed in the Handling Unit Item
    Dont forget to create Dummy packing material no...
    i think above mapping helps you...
    Thanks
    Ramesh

  • Inbound delivery idoc error in segment e1eld20

    we are receiving delivery idoc from the vendor, so this is delivery will be created as inbound delivery in our system, so in the segment E1EDL20 field VBELN(let say 'ABCD') is the outbound delivery number of the vendor ( i believe), but when is try to process this idoc it gives the error as 'delivery ABCD does not exist' ( it's obvious that the delivery 'ABCD'  will not be in our system because it's a vendor delivery number), can some body please let me know whats wrong with this E1EDL20-VBELN.
    Thanks,
    Kashif

    HI,ALL
    Thanks for your replies and documents.
      Now I find the problems lies in the error connection between R/3 and BW. IF the autoconfiguration is completelly correct , the table RSBASIDOC in both system should be added one record.But now when the source system is activated successfully ,the table in R/3 side has no entry while the BW side has one entry .juding from this ,there is no BW system connected to the R/3 ,which is proved when I fill the setup table for LO datasource an error message shows that there's no BW system is connected to the OLTP system.
      How can i figure this issue out ?If I want to do an automatic configuration ,what shall I do ?

  • Inbound Delivery Idoc

    We are trying to create a Inbound Delivery for purchase order.  We are using idoc basic type DELVRY03. 
    When we are processing this Idoc we are constantly getting error :
    <b>Item 00000 of purchasing document does not exist
    Message no. ME706
    Diagnosis
    Purchase order 00000 with item  was not found.
    Procedure
    Enter a different purchase order.</b>
    We have mapped the PO and PO Item fields to Idoc segment fields E1EDL24-VGBEL and VGPOS respectively.
    Let me know if anyone came across or know the reason for this message and remdy.
    Thanks in advance.

    hi,
    below is the structure I had used in my project for creating inbound delivery through ASN
    E1EDL20- LIFEX
    E1EDT13- QUALF (007)
    E1EDT13-NTANF
    E1EDL24- POSNR
    E1EDL24- KDMAT  Should be repeated for multiple Items
    E1EDL24- LFIMG
    E1EDL24- VRKME
    E1EDL41-QUALF(001)
    E1EDL41- BSTNR
    E1EDL41- POSEX
    E1EDL37- EXIDV
    E1EDL37- VHILM_KU
    here please check the documentation in WE60. hope it helps
    regards
    Seema

  • Inbound Delivery Idoc processing for Purchase Order

    We are trying to create a Inbound Delivery for purchase order. We are using idoc basic type DELVRY03.
    When we are processing this Idoc we are constantly getting error :
    Item 00000 of purchasing document does not exist
    Message no. ME706
    Diagnosis
    Purchase order 00000 with item was not found.
    Procedure
    Enter a different purchase order.
    We have mapped the PO and PO Item fields to Idoc segment fields E1EDL24-VGBEL and VGPOS respectively.
    Let me know if anyone came across or know the reason for this message and remdy.
    Thanks in advance.

    Hi Milind,
    Did you get this to work?
    Thanks,
    Finbarr

  • Inbound Delivery Idoc for PO

    We are trying to create a Inbound Delivery for purchase order. We are using idoc basic type DELVRY03.
    When we are processing this Idoc we are constantly getting error :
    Item 00000 of purchasing document does not exist
    Message no. ME706
    Diagnosis
    Purchase order 00000 with item was not found.
    Procedure
    Enter a different purchase order.
    We have mapped the PO and PO Item fields to Idoc segment fields E1EDL24-VGBEL and VGPOS respectively.
    Let me know if anyone came across or know the reason for this message and remdy.
    Thanks in advance.

    Pls check if the GR has already happened manually.
    Hope this helps.

  • LS System for Inbound delivery idoc

    Hi,
    I am able to define transfer the master data between ECC and EWM system, however i have an issue for transactional data e.g. inbound delivery.
    When I create inbound delivery then system generates an IDOC but it picks up a different logical system as against the one defined for my system. When I generated my distribution model, i got a message that it is successfully created and I can see my message type and filter details(my warehouse etc) on the message type.
    Can someone kindly suggest how EWM picks up LOgical system, my understanding is that it is based ont he configurtion(WM to EWM location definition and distribution model). But I am confused now and trying to understand why system is not finding my LS system?
    Any link to supporting documentation would really help.
    Thanks and regards,
    Bhaskar

    I found the root cause, there was another LS system model was there in my system, I regenerated partner profiles and that resolved the issue.

  • Mandatory fields for inbound delivery idocs

    hi all
    i want to generate inbound idocs for inbound delivery ASN
    i am using message type DESADV and idoc type /AFS/DELVRY03
    in order to generate inbound idoc what are mandatory values i have to pass to the idocs
    thanks
    Anil

    HI,
    I created inbound idoc for ASN Inbound delivery in test mode we19
    i got idoc with status 62, when i am trying to process the idoc in bd87, its allowing me
    is there any other way to process the idocs , so that status will be 53
    thanks

  • Inbound Delivery Idoc not update PIC and PGI with split batch.

    Dear Experts,
    Delivery outbound with split batch send to third party Warehouse to PIC and PGI from SAP, then receive the delivery inbound IDOC to update the PIC and PGI in SAP from third party. Basic Idoc DELIVERY03 it's works fine with out split batch, with split batch it's not updating PIC and PGI at the same time no error. Please advice on this
    E1EDL24-HIPOS = "HIGHER LEVEL ITEM NUMEBR"
    E1EDL24-HIEVW = "VALUE 1"
    E1EDL19-QALF = "BAS"
    Thanks and Regards,
    Thiru.

    Hi,
    You also have to create a segment with following data as well (for batches).
    E1EDL19-QUALF = "QUA".
    Cheers,

  • Inbound Delivery Idoc with batch split then PIC and PGI using DELIVERY03

    Dear Experts,
    Requirement to split the delivery item then PIC and PGI, while Processing Inbound Idoc using basic Idoc type DELIVERY03
    I have searched forum already but it vain. Please advice.
    Thanks and Regards,
    Thiru.
    Moderator message : Spec/requirements dumping not allowed, show the work you have already done.  Thread locked.
    Edited by: Vinod Kumar on Nov 16, 2011 5:09 PM

    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)? )

  • Inbound Delivery IDOC-DELVRY03; Right User Exit? WMTC1D01 IDOC for STOs??

    Hi Experts,
    The scenario is:
    As soon as the user saves the DELIVERY in external_system, flat file is sent to Gentran, where its transfrred to IDOC and then, this IDOC is directed to SAP.
    So, this Inbound_Delivery_IDOC- - DELVRY03 will be received by SAP system and updates the delivery related stuff in SAP system.
    So, here, AT THIS POINT,
    1)I need to capture this IDOC of Inbound_Delivery_IDOC - DELVRY03,
    2) Need to check its(Inbound_Delivery_IDOC) MESSAGE CODE for TOA
    3) If its TOA, I need to UPDATE the associated Stock Transfer Order/STO(record in LTAK, LTAP tables) stuff through IDOC of WMTCID01
    so, let me know that,
    1) Wht is the User Exit, I need to look, Which User Exit is correct? I mean, At Wht point I need to add my code in this whole process?
    2) How to execute the UPDATED WMTC1D01 IDOC of Stock Transfer Order-STO?
    thanq

    no reply

  • Using Different inbound delivery type?

    Dear experts,
    In the goods receipts process we currently are using the standard inbound delivery type "EL" with the standard item category ELN, which is not "Relevant for putaway".
    We are assessing the possibility of start using WM in one of our plants. So, I found out that the we should be using a item category (in the inbound delivery) with the field "Relevant for putaway" flagged. Like, for example, the standard WIDN (maybe together with the standard inbound delivery type WID). But only at those plants with WM!
    The issue is that as far as I know the inbound delivery type determination depends on the "Internal Confirmation Categories":
    So for the type "2 Shipping Notification" only one delivery type can be chosen, how are we suppose to do it plant dependent?
    It looks like a unique delivery type should be used in the client?
    Thanks in advanced,
    Fortian
    P.S.: I already read SAP notes 214604 & 201655 but they are not being helpful so far... Maybe I'm missing something.

    From your post I understand that the current plants are IM managed.
    So for these plants the put away relevancy will not have any effect so if you enable the put away relevancy for the EL delivery type there will be no impact on the IM plants and for the WM plant the put away will be relevant.
    Now the usage of the put away relevancy will also depend on which transaction you are using for posting a goods receipt. If you post via VL32N then you will first have to perform the put away step and then the GR posting. If you use the MIGO/MIGO_GR transaction then the goods receipt in WM will also be posted before the put away happens.

  • 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

Maybe you are looking for