IDoc - Inbound delivery

Hi Experts,
Inbound EDI message order acknowledgments:
When we cancel a purchase order item with IDoc message 'ORDRSP', this leads to an error message in the IDoc inbound processing.
There is note 890812, but i guess it is till release 5.0
Can anybody please guide me for the solution.
Thanks,
Sourabh Kothari

Hi Experts,
When we tested for the note, it is giving the status that this cannot be implemented.
Could any one give me the alternate solution for the IDoc inbound processing.
When the vendor sends the quantity 0 against any of the line items, the other line items are also not posted. There error message is ME794.
As per the above note implementing the corrections & when the item is deleted in PO, again processing the idoc would be successful. But the note is not valid for ECC 6.0
Please guide.
Thanks,
Sourabh Kothari

Similar Messages

  • IDOC inbound: delivery confirm - set storage location at position

    Hi all,
    I have the issue to set with an inbound IDOC for shipping confirmation the storage location on item level. We are working with an external logistic provider so the final storage location where the goods are taken from is not not at creation time of the delivery. We have two possible storage locations.
    EDI message type SDPICK cannot be used, there is no place for the storage location information LGORT.
    So we tried SHPCON with process code DELV. FM: IDOC_INPUT_DELVRY
    The field is in the IDOC type DELVRY03 but it is not used.
    Do you have any idea how we could set the storage location on item level in the delivery with an incoming shipping / picking confirmation idoc?
    Thanx a lot
    regards
    Hans

    used a userexit in the inbound function module to get the IDOC field to the internal tables.

  • 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

  • Goods Receipt reversal posing for Inbound delivery

    Hi Gurus,
    There is an interface running which create, IDOC, Inbound delivery, HU and material received (material document created - 521mvt type) to stock.
    Now there is some problem in the HU weight and I need to reverse the Material docuement with 522 mvt type.
    As the GR is created through VL32n, I can not reverse the GR using MBST or MIGO cancellation. I am also not allowed to reverse through VL09. I am getting error This is not possible with movement type 522.
    Kindly inform me if you have any suggestion to reverse this material document.
    Best Regards,
    Mohan

    Hi,
    VL09 is the correct transaction.
    I doubt if this will work but try looking at theconfig of the 521 and 522 movement types and check the "allowed transactions" see if VL09 is linked to it, if not then link it and try VL09 again.
    It is a longshot but VL09 shouldwork (although my HU knowledge is not good).
    Steve B

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

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

  • Error message while creating an inbound delivery to generate an idoc

    hi,
    i am getting the following error message while creating an inbound delivery(vl31n) where the message has to be sent ot decentralized warehouse mangament using idoc .
    ." No recipient could be determined for object BUS2015 method SAVEREPLICA"
    Procedure for System Administration
    The system attempts to determine a recipient for object BUS2015 method SAVEREPLICA using the filter object types WHSE_NO. The system cannot determine a recipient. Define a filter object type WHSE_NO with a valid filter value for recipient determination for object BUS2015 method SAVEREPLICA.
    need help
    regards
    leo

    Inbound delivery is not part of Sales and Distribution. You might want to move your post to either the Logistics Materials Management (MM) forum or the Workflow forum.
    Also sometimes search for OSS notes by the message class and number helps.

  • Error in IDOC creation of Inbound Delivery (VL31N) with  Error Message Number VL561

    H,
      I'm getting an error message when generating a test IDOC of Message type DESADV and IDOC type DELVRY03 to create Inbound delivery with reference to a standard purchase order.
    Essential transfer parameters are missing in record: PO Number and Item
    Could you one help me out in solving this.
    Thanks,
    Raj

    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 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,

  • IDOC for inbound delivery

    Hi Gurus,
    Pls help me to understand this functionality:
    Shipments destined for a Distribution Center will generate ASNu2019s(advance shipping notification) to alert the Distribution Center  to the upcoming receipt.
    There are two variations of the transaction that will initiate the ASN:
    u2022  Receipt of an ASN from a vendor to a Distribution Center  will result in the creation of an Inbound Delivery.  That Inbound Delivery must be sent to WM via  IDOC.
    u2022  Shipments from Distribution Center to DC will create an Outbound Delivery from the u201CClose Loadu201D process in Warehouse M.  Creation of the Outbound Delivery to another DC is the trigger for the IDOC to WM.
    The IDOC to be used could be a variation of the DELVRY03.
    My doubts includes:
    1. can I use one idoc for both the scenarios?
    2. both are outbound idocs or not?
    3. Any suggestions how to do this?
    Thanks..
    SD

    >
    Shibu David wrote:
    > My doubts includes:
    > 1. can I use one idoc for both the scenarios?
    Yes you can use IDOC DELVRY03 for both scenarios
    >
    Shibu David wrote:
    > 2. both are outbound idocs or not?
    No.
    ASN sent to DC will be outbound message.
    ASN received by DC, which creates Inbound delivery is inbound message.
    >
    Shibu David wrote:
    > 3. Any suggestions how to do this?
    As far as I know message type used in SAP for ASN is DESADV.
    For inbound ASN use process code DELS and for outbound use DELV

  • Inbound Idoc with T-code: BORGR ( Inbound delivery create) EDI cannection

    Dear all,
    Kindly help me to create inbound delivery with BORGR transaction.
    Here the we have to create the inbound delivery in the system with the help of vendor number and material without using Scheduling agreement number in BORGR
    Please suggest the processing code and the function module required for the BORGR document posting.
    I have done the following steps u2026but not able to post the dummy idoc through WE19 .
    1.     Use standard message Type DESADV (T code: WE81).
    2.     Use standard IDOC type DELVRY05 (T code: WE30).
    3.     Assign message type  to IDOC Type ( Tcode: WE82).Message Type:-DESADV, Basic Type:-DELVRY05,Release 700
    4.     Use standard assignment of process code DELS with the message type DESADV ( Tcode: WE42)
    5.     Inbound Function Module :  IDOC_INPUT_DESADV1 ( T code : WE57)
    6.     Define Port type File (Tcode: WE21) Port u2013 EDI_ASN Inbound Delivery.
    7.      Define Partner Profile (Tcode: WE20) Inbound Parameters.
    8.     Enhancement can be done in inbound IDOC as per the business requirement. Business has confirmed Field name wise Inbound IDOC data which will be received from vendor and all fields are available in the standard IDOC type DELVRY05.
    Please help if anything more required for posting dummy idoc .
    Thanks and regards,
    koshti

    Hi Dick,
    just one additional hint as we had recently such problems :
    It my happen that DESADV creates an inb.del <b>w/o</b> packing the HUs (idoc status is 'yellow' instead of 'red'). To avoid this OSS #912470 is the solution.
    Kind Regards
    Kay

  • Creating inbound delivery without reference to PO - from inbound idoc

    Hi guys,
    I have a scenario wherein I need to create inbound delivery from inbound Idoc from external system without reference of PO. There is no PO created in SAP and this inbound delivery will be used just to receive material (purely for logistic purpose).
    I have identified DELVRY03 or 05 as Idoc type but I am not sure whether system will create inbound delivery without having reference PO. I have two questions here -
    1. Can we create inbound delivery without reference to PO?
    2. If yes, which Idoc type should I use to create such inbound delivery?
    Please help.
    Thanks,
    Parimal.

    Dear Parimal,
    In standard, An inbound delivery can be created as follows:
    With reference to a purchase order
    With collective processing for several purchase orders
    With reference to a stock transport order
    With reference to a customer return

  • Post Goods Receipt for Inbound Delivery using WHSCON IDoc

    Dear All
    Currently I am working on a big project dealing with EDI connections to our logistics partner for the Export business. The entire message flow between Lindt and our partner should be via EDI. Our SAP release is (still) 4.6c.
    We will create two kinds of despatch advice messages, one for inbound deliveries and one for outbound deliveries for customers.
    I would appreciate your support in the following problem that I am facing with the inbound delivery scenario:
    We create stock transport orders (purchase orders, POs) for the goods intended to be delivered into the plant at our partner
    We create a delivery (type NL = replenishment delivery) for this POs
    As soon as we post the goods issue we send the despatch advice (as EANCOM D96A DESADV message) to our partner.
    At this point the delivery is basically completed, i.e. packing status (PS) and goods movement status (GM / GS) are equal to 'C' (= completed).
    Our logistics partner uses the same EDI message to send us the goods receipts data, e.g.:
    We dispatched 50 units of a product => QTY:50:12
    The partner received indeed 50 units => QVR:50:66
    Please note that we do not use the QVR segment for the quantity difference (between despatched and received quantity) but it contains the received units. This way we avoid negative values in the QVR segment.
    When the logistics partner sends back the DESADV message containing the received quantities (QVR segment) we want to make
    the goods receipts for the products in the original stock transport order and
    upate the message flow in the delivery
    My idea was to transform the incoming DESADV message into a WHSCON.DELVRY03 IDoc based on the documentation in: [Delivery Interface|http://help.sap.com/saphelp_crm40/helpdata/en/e2/654b15a9f411d184ec0000e81ddea0/content.htm]
    In the delivery header control E1EDL18 I used QUALF = 'PGI' (Post goods issue).
    I prepared an inbound WHSCON IDoc according to the documentation mentioned below. I managed to get some feedback from the Idoc processing implying that the system tried to do the goods receipt in the PO but failed.
    To make a long story short here are my questions:
    Can an inbound WHSCON IDoc used for doing both the goods receipt in the PO and the update of the message flow in the delivery?
    Does anybody have an example on how to fill the WHSCON IDoc?
    Or is my approach a cul-de-sac ?
    Kind Regards
       Uwe
    PS: A related question can be found here: Goods Receipt in PO AND Message Flow Update in Inb. Delivery using WMMBXY

    Hi Uwe,
    Can an inbound WHSCON IDoc used for doing both the goods receipt in the PO and the update of the message flow in the delivery?
    The binary answer would be no. You should use WMMBXY or MBGMCR instead.
    But if we are doing goods receipt against Inbound delivery then answer is YES with additionally E1EDL18-QUALF = 'PIC' populated. But please remember no partial receipt is possible against Inbound Delivery.
    We should populate E1EDL20-VBELN with our Inbound delivery number and line item info should go to E1EDL24.
    I have done a similar interface recently where we are doing receipt against Inbound delivery. But our case was a bit complex because we had to support against Inbound delivery. So we had to go for a custom solution on top of IDOC_INPUT_DELVRY.
    Hope this helps. Let me know if you have more questions.
    Regards,
    Rudra

  • 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

Maybe you are looking for