DESADV idoc

Hello,
I have a question regarding DESADV idoc.
DESADV idoc creates and inbound delivery.
We have this problem : we need to create our inbound delivery right after the PO creation.
Do you know if the DESADV idoc can update an existing inbound delivery ?
Thanks,
Regards,
PYR

how can system up date the same inbound delivery in different PO ............as inbound delivery is created with reference to the PO and it gets updated automatically in the PO.
If you want the DESDAV should update the PO right after the creation of the PO then  its possible but you need to write a Z program for that  because DESDAV means vendor has informed you that he has shipped the goods and the thing is that if the PO is created then at any point of time DEDAV can update the confirmation in PO.
If you want that the moment you save PO system should trigger the DESDAV then i have some question
1. for what quantity system should update the PO thru DESDAV
2. from where will the DEDAV would be getting all the required information

Similar Messages

  • Auxiliary Packaging missing from DESADV IDOC

    Hi Experts,
    I have a delivery attached to a shipment, when the output for the shipment triggers an outbound DESADV IDOC, the segment E1EDP08 and E1EDP06 contain normal packaging material information, BUT Auxiliary packaging material information (which do not have a handling unit number) is missing.
    How to get this aux pack info into E1EDP08 and E1EDP06 segments of DESADV IDOC? any configuration, user exit, coding?
    maximum points would be rewarded, if the solution is helpful.
    Br,
    Ankur

    I have checked these field available in DESADV original message in WE19 transaction.You need to add in Functional module program if the packing material has AUXilary packing then system should populate these fiels.Check why the current program it is not populating?.If the logic is not written in existing program then you need to modify the code.

  • Idoc error mapping error for segment "E1EDT13 006" in DESADV idoc

    Hi SAP Gurus,
    DESADV IDOC for few articles is not getting passed from SAP to legacy system. It is missing one segment"E1EDT13 006" for goods issue.
    Why is this mapping error happening. How can this be resolved.
    Regards.
    Sumi

    Hi Nsangle/SAP gurus,
    Thanks for  that. But, I have already compared the failing idoc with the successful one. It's the segment E1EDT13 006 missing in the wrong idoc. I have already added that idoc and reprocessed it.
    But, I wanted to know why such kind of idoc segment missing/ mapping error happens.
    Regards.
    Sumi

  • Inbound processing of segment E1EDT13 - QUALF 499 in DESADV idoc

    Dear all,
    we are currently facing the problem, that we want to send customized deadline dates in a DESADV idoc into our system.
    I set up the customizing accordingly, maintained the data in a outbound delivery and created an idoc out of it. I saw, that the segment E1EDT13 is filled using QUALF 499.
    I took this idoc modified a few fields and sent it back as an inbound delivery.
    This works, but E1EDT13 with qualifier 499 doesn't appear in the created inbound delivery.
    I checked the coding of the inbound function modules concerning qualifier 499 and detected, that this qualifier is never considered in the coding.
    Does SAP support the inbound posting of qualifier 499? If yes, how? Which function module will be used?
    If no, does anyone have an idea/experience concerning inbound DESADV using qualifier 499 in segment E1EDT13?
    Kind regards
    Harry
    PS: We are using a ECC 6.0 release.

    Posted the wrong idoc type. Sorry
    Moderator Message: I will lock this thread, just in case someone feels tempted to answer it :-). Next time please use the EDIT option to edit your post.
    Edited by: kishan P on Nov 4, 2010 5:53 PM

  • Desadv idoc processing issue

    Hi All,
      We are facing issue, when vendor send a two desadv idoc for packing delivery.
    First idoc correctly pack the delivery and change the packing status to completely packed.
    Processing second Idoc get fails but create a dummy handling unit. It delete one handling unit from the handling unit table VEKP but the trace remains in document flow table VBFA.
    This does not happen in all the cases and we are not able to reproduce in Quality system to debug.
    Does anybody faced the same issue earlier, and what could be the possible root cause and solution for this.
    Please help.
    Thanks in Advance
    Ankit Gupta

    Hi,
    As you have mentioned that you are using custom defined iDoc, you might be using a custom defined BAPI to receive the data from the iDoc.
    As you have said that the status is 64, your iDoc has entered the system & it has failed only when the data being sent to the application.
    kindly, check if the custom defined BAPI or RFC is working fine & whether it updates the status record or not? because you custom BAPI will be receiving the data from the iDoc.
    Also, test the scenario using the transaction WE19.
    or else you can use manual processing of iDoc using T.code - BD87.
    kind regards,
    Thangesh

  • DESADV Idoc + duplicated Inbound deliveries

    Hello.
    I am using DESADV to create inbound deliveries in ECC6. For the Item category ELN (item categ. for inb. delivery), I have prevented to created zero quantity delivery item => via VL31N it is impossible to create a second delivery items for the same PO items if the first one gets the fully PO qty.
    The issue is that when we try to do it with an DESADV Idoc, SAP allows it => 2 delivery items in 2 diff. deliveries having qty=PO qty.
    Is there someone faced the same issue ?

    Hi
    I am bit confused with your posting, Data u were passing is not updated in the Field or what ....
    VFDATA is Shelf Life Expiration or Best-Before Date ..correct
    With regard
    Bhargava

  • ASN user exit, before posting DESADV IDOC.

    Hi
    I have a requirement to compare the sales order quantity and delivery quantity before posting the outbound DESADV IDOC to the external system. Can anyone tell me which use exit to be used.
    If there is no exit, can anyone please tell me the alternative way to achieve the same functionality.
    Regards
    Rinku

    If you use NW 7.0, you may use an implicit enhancement option at the end of the FM, to set status 68 (it's an export parameter)
    Otherwise, create your own FM which calls idoc_input_delvry, and set status 68 in your FM. You must customize transaction WE57 to call your FM instead of idoc_input_delvry.

  • Tcode for triggering DESADV idoc

    Hi Gui's,
    I have to trigger the idoc type DESADV will  you please any body provide the tcode.
    Thanks,
    Santosh
    Moderator message: please do more research before asking.
    Edited by: Thomas Zloch on Mar 28, 2011 9:09 AM

    Hi,
    To trigger a event, u shld use the Tcode SWUE.
    Here u have to specify
    1) Object category = Bus. obj Type
    2) Object Type = ur BUs. obj
    3) Object Event = which event u wan to trigger
    4) Click on Object Key button & enter the key field value(s)
    5) There is a butoon 'Event Parameters' . Click on tht to enter the event parameter values.
    6) If u click on 'Event Receiver' button, u can c which WFs r linked to this event
    7) Now click on 'Create Event' to trigger the event
    Regareds,
    Sivagami

  • Seeburger help required for 850, 810, Dispatch Advice (DESADV IDOC)

    Hi All,
    Pls let me know for below 4 points:
    1. Please let me know blogs which clearly shows settings for Seeburger components for 850 or 810.
    --- Seeburger Workbench
    --- Seeburger Mapping Designer (BIC)
    --- Seeburger Counter and Varaibles
    --- Seeburger AS2 Spoke
    --- Any other Seeburger Component setting required
    I have understand blog for 850 -- /people/rajeshkumar.pasupula/blog/2009/08/05/wanna-implement-seeburger-for-edi-find-the-booster
    2. Anybody has blog for 810 or Dispatch Advice (IDOC type DESADV).
    3. Can anybody provide me Mapping Logic (at field level) done in XI/PI for 850, 810 , Dispatch Advice (IDOC type DESADV) .
    4.  I have heard that Seeburger now provides standard mappings for PI/XI  for 850, 810 , DESADV etc. so we do not require to do mappings in PI/XI now as it is already done. Any one knows about it.
    Regards

    > Pls let me know for below 4 points:
    >
    > 1. Please let me know blogs which clearly shows settings for Seeburger components for 850 or 810.
    > --- Seeburger Workbench
    > --- Seeburger Mapping Designer (BIC)
    > --- Seeburger Counter and Varaibles
    > --- Seeburger AS2 Spoke
    > --- Any other Seeburger Component setting required
    Hello Rickk,
                          There is no blog for the 810 scenario ...
    you need to configure the partner related stuff in seeburger workbench if it is inbound only like 850,852,860..
    not for outbound like 810,856...i.e no need to configure the partner data in seeburger workbench for this..
    You need to look for developing mappings if EDI message is other than Version 4010 by default there are mappings available for
    810,856,850,997..if your edi messages are other than this then you need to look for BIC tool for developing mappings.
    There is no need to set anything for counter and varaibles
    ..no idea about AS2 spoke,,,
    Apart from thjis no need to do anythings in seeburger ...
    HTH
    Rajesh

  • Error BORGR 027 and 093 on DESADV Idoc

    Hi experts, I have a problem wit the Idoc for message type DESADV.
    I get errors BORGR 027 and 093 (status 51) on ibound Idoc.
    It seems that something in the delivery is missing, cause it seems to look for a PO with POSNR 00000, and clearly can't find it.
    Similarly it seems impossible to get a supplier.
    Segment E1EDL24 is red-colored, as if an information is missing.
    Function modue is BORES_IDOC_INPUT_DESADV1.
    We are running release 4.6C.
    Thanks for your kind help!!
    GR

    Hi,
       Reprocess the idoc with "RBDMANI2" and get the exact error text.

  • Inbound DESADV IDoc Reciever port issue

    Hi,
    We are receiving inbound idoc from gentran and the reciever port is empty when the idoc comes in. This is setting idoc to error status. We checked gentran and confirmed gentran is sending reciever port but on SAP side the port is missing. Is there any way we can verify on SAP side on why the port is missing?

    I figured out where the problem is and I fixed it.

  • DESADV IDoc using EAN's

    Hi all,
    A bit of guidance if you could. I am trying to simulate an inbound delivery creation process using DELVRY06/DESADV for a PO. The issue I have is that the EDI provider will not be sending the material number in either the E1EDL24 (delivery line item) or E1EDL44 (HU item) segments - only the barcode.
    E1EDL24 has a field EAN11 which I have populated with the relevant EAN/UPC code and removed the MATNR and KDMAT values for the R/3 material. However I cannot get the inbound delivery to create without populating the material number.
    Also for the HU, we have the scenario of having multiple materials (E1EDL44) packed into a HU (E1EDL37). The DL44 segment only has material fields and no corresponding EAN field to identify the materials to be packed.
    If anyone has experience with this issue then I would love to hear what I can do. If there is something that is 'out of the box' i.e. SAP standard then that will be first prize for sure, but if I have to, then an enhancement may be required - hopefully not.
    Kind regards,
    Paul...

    Hi,
    I worked with EAN Numbers however I dont think EANs can be used for Nested packing etc.
    However please check the link below it might be helpful to you
    http://help.sap.com/saphelp_afs60/helpdata/en/afs.htm
    Regards
    Shrinivas Betageri

  • How to trigger a workflow for DESADV when the IDOC reaches status 51

    Hi,
    A notification to the a user should be sent when DESADV goes to a error status 51.
    I'm in SAP6.0 :
    Basic type: DELVRY05
    Message type: DESADV
    Idoc: IDOCDESADV
    Event: inputErrorOccurred
    Task to be linked for the event : TS00008178
    In SWETYPV the event is active, still this event is not getting triggered when the Idoc goes to 51 status.
    What am I missing? Is there any configurations that I'm missing?
    Can anyone please help me to fix this?
    Thank you,
    Renu

    Hi Renu
    There is two way to find the task and workflow....
    In pftc tcode, you can check the task and where it is used by giving the task type as standard and task as 00008178.Display the task,then check where it is used.
    Another way is:
    1.Goto swdm tcode.
    2.Select the Object tab.
    3.Choose catagory as BOR object type and give the Object type as IDOCDESADV.
    4.Then it'll display the task which is refering the method of the IDOCDESADV object.
    5.Click on that task.It'll come to right window.Now select the where used icon...
    6.If there is any workflow,then It'll display the workflow template number,name,step, and client.
    Regards,
    Hemalatha

  • IDoc parallel posting for message type of DESADV

    The DESADV (Delivery Advice) logic is complex and it takes long time than expected. We want to improve its performance by posting DESADV IDocs in parallel.
    Currently, the "Input type" of DESADV's function module is 1, which means parallel run is not enabled. (In tcode BD51). In addition, DESADV is configed as "Immediately" instead of "collected run". We will trigger DESADV every 30 mins, about 500-1000 IDocs will be created automatically and then be posted.
    I want to know:
    Is it possible to enable DESADV IDocs posting in parallel, how?
    Dialog or background is recommended, especially from workload/performance point of view?
    Any other concern? such as will data duplicated posting or data lose?
    In BD20 (or program RBDAPP01), I noticed there was "Parallel Proc." option which can be selected. Can I just simply change the message type to "collected run" and schedule another background to post those IDocs in parallel?
    Any comments is appreciated.
    TIA
    James

    no answer

  • IDOC DESADV CHANE

    Hy Experts!
    I have the following problem:
    When I'm creating an outbound delivery with DESADV msg.type then an inbound delivery has been created in an other system. If I want to change the otubound delivery (vl02n), than I always creating a new inbound delivery, altough I really dont want, because I just want to change it.
    If you check the PO history, you can see, that after changing the outbound delivery, I was creating 2 inbound delivery, for the same PO....
    Can you help me please?
    Thanks in advance!
    Marco

    Hi Marco,
    Are you sending this DESADV to yourself (the same system or some other system that you also manage) ?
    If yes, you can try to connect SHP_IBDLV_CHANGE idoc to carry changes to inbound delivery, instead of DESADV.
    If you have automotive solution activated you might also play with settings in
    SPRO -> LE -> Goods Receipt Automotive -> General Settings for Inbound Delivery Processing
    -there you can force the uniqueness of External Delivery ID, so the "change" DESADV idocs won't create another Inb Delivery, same as the first one.
    Good luck
    Tomek

Maybe you are looking for