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

Similar Messages

Problem sending IDOC DESADV /AFS/DELVRY03 to XI

Hi Gurus,
I have problems sending IDOCs DESADV (basic type /AFS/DELVRY03) created by function LSEND_IDOC to XI system. IDOC is correctly created by R3 system (AFS ECC 5.0) and correctly sent on the XI port (Status: Data passed to port OK - 03), but XI system doesn't receive IDOC.
If I resend the same IDOC by WE19 tcode goes ok!!
In R3 sending system nothing warnings/errors in syslog or sm58.
Any suggests? Thanks in advance.

Issue solved! It is necessary close the master idoc with a commit

EDI / Idoc DESADV Inbound Delivery

Hello,
we send IDocs (DELVRY03,DESADV) as shipping notifications to another R/3 system. The inbound deliveries in the receiving system, generated automatically, are also containing the handling units as delivery positions, which are specified in the IDOC.
How can we prevent this, so that only the actual delivery positions are listed in the inbound delivery? Customizing?
Thanks you in advance.

Hello Mario,
I assume that you have plant and item category filled in your HUs. In this case a delivery item is generated although the corresponding flag at the item category is switched off (this is the 'old' logic of item generation).
Therefore if you want to prevent the item generation you could prevent the determination of an item category (see trx. 0184, entries for EL, PACK).
If you need a more detailed control of the item generation e.g. only for some special packing materials, you might also use the 'ItemRequirement' at the delivery type (in standard 202), which specifies if an item without reference can be added to an delivery (can be maintained by using transaction VOFM - Copy requirements - Delivery).
Best regards,
Ulrich

CIDX ShipNotice to IDOC DESADV.DELVRY03 mapping

Hi,
SAP BP CIDX 1.0 delivers standard mapping between ShipNotice (CIDX msg) and SAP IDOC Interface DESADV.DELVR03 (inbound to SAP, used for shipment notification against which GI occurs then in SAP).
In my OTC scenario it means Delivery Confirmation happens currently via Phone call. After this call manually in SAP they update Delivery Outbound document and do GI posting.
Can I use DESADV for updating Delivery Document?
I believe SHPCON message is used for updating Delivery documents.
As far as I know DESADV and SHPCON use the same structures of DELVRY03 IDoc only the msg type from IDOC adapter is set differently. I would not like to use SHPCON since Ive standard mapping for DESADV.
Of course I could manuall define mapping template for SHPCON.DELVRY03 based on standard mapping to DESADV.DELVRY03. But before going for this just wanna know if I could use straigh away standard mapping to DESADV.DELVRY03.
Any advice welcome?
cheers,
Mariusz
(Max)

A message type is an implementation using an IDoc type. for instance ORDRSP, and ORDCHG message types all are based on the ORDERS05 IDoc type. In other words, the layout of the possible segments and fields are the same in all of these. so in ur implementation u wud not have any issues in using DESADV.DELVR03

Create idoc DESADV when POST GOODS ISSUE

Hi everybody!!
I have a problem and I donu2019t know how to solve it, my question is the following:
What can I do to make an outbound idoc type DELVRY03, message:
DESADV doesnu2019t go off until the outbound delivery getu2019s post it, with the fact of creating it going off.
Thank for your comments.

Hello There,
The functionnality you can use for your process is described in notes 340238 and 421276.
I am afraid that the process to create an inbound delivery via DELVRY-IDOC for a stock transfer is not possible as it´s not designed for this.
For the DELVRY-IDOC scenario for inbound deliverys the preceeding document has to be a SD document and not a MM document.
The DELVRY process is designed for purchase orders for your customer:
e.g. CUSTOMER SIDE               YOUR SIDE
     purchase order         - >        sales order
           ^
Y
     inbound delivery       < -        outbound delivery
The outbound delivery does not fill the purchase order number in the IDOC as a check is looking for a SD document wich does not exist.
If you need the DELVRY process for stock transfer then you need a USER-EXIT or a modification in the outbound function module to fill the PO number and the purchase order item number in segment E1EDL41.
We only read out the PO number and the item number if the subsequent document on the vendor side was an sales order.
I hope this helps,
Elaine.

ASN IDOC (DESADV)

Hi
I'm trying to get an outbound IDOC from SAP 4.7 which I can use to map into an EDI mesage to send an ASN to our customer. I've been playing with DESADV (basic idoc type DESADV01, process code SD05) but can't seem to pull out the SSCC(i.e storage number/pallet ID). It only seems to handle Handling units.
Has anybody done this, or tell me how I can get the SU (storage unit) number into the idoc?
Thanks
Rob

Try working with a Z extension,

How can I change an IDOC (desadv-asn-inbound)

Please let me know how can I change a value within the IDOC (ASN)? I remembered that I have done this before but I can't remember how.
I don't want to ask the vendor to resend the asn again.
tks
Eduardo

Go to the Idoc segment for which you want cahnge the value than double click on the paper icon of the segment
this will take you to the display data reocrd
here from Data record menu at the header
hit display --> change
and this will open in change mode
change the value and save
also you can copy same idoc in WE19 and reprocess the newly created via BD87 if you don;t want to change
but if it is production system than better to change the original and process.

Batch split in Idoc DESADV.DELVRY01

Hi,
my scenario is non-SAP --> xi --> SAP for dispatch notifications. The sender system provides batch information on line item level, sometimes with batch split.
I am looking for a possibility to post the dispatch advice in R/3 with batch split. I already tried with multiple E1EDL24 segments and with E1EDL15, but with no success.
Does anybody have experience with batch splits in SAP Idocs or can anybody help me with a documentation?
Thanks a lot,
Philipp

hello Philipp, all you have to do is to fill the fields CHARG, HIPOS, HIEVW, only have to fill the fields HIPOS and HIEVW in the sub-items segments, then you have to manually assign these fields to the structure that receives them, for example in the user exit "EXIT_SAPLV55K_011" the structure that receives these fields is DELIVERY_COM.
Example:
IF IDOC_SEGMENT-SEGNAM = 'E1EDL24.'
   l_es_e1edl24 = idoc_segment-sdata.
   it describes table DELIVERY_COM lines reg.
   if sy-subrc = 0 and reg> 0.
      loop at delivery_com into l_ti_delivery from reg to reg.
              l_ti_delivery-charg = l_es_e1edl24-charg.
              l_ti_delivery-lichn = l_es_e1edl24-charg.
              l_ti_delivery-chspl = 'X.'
              l_ti_delivery-uecha = l_es_e1edl24-hiccups.
              modify delivery_com from l_ti_delivery transporting charg lichn chspl uecha.
      endloop.
   endif.
endif.
i hope this information can help you.
best regards.
Cesar Becerra.

ECC6: IDoc DESADV: Status 52 instead of 53

Hi Experts,
Our system was just upgraded to ECC6 over the weekend. We have an issue similar to what is described in the OSS Note 898626, but the note doesn't help. Please give us some suggestions.
Thanks
Joanna
Edited by: Joanna Q. Shi on Feb 14, 2012 9:58 PM

Hi Joanna, we also have the same problem here. have you found solution?
Best regards,
Stone
I meant i have applied the note and I know the problem caused by warning msg however I need this to ignore the warning and the note did not help.
Message was edited by: Pen-Siri Stein

DESADV.DELVRY03 idoc to XML Mapping issue.

Hello Experts,
I am facing a problem in Mapping of an idoc DESADV.DELVRY03 with the given XML file.
Please suggest me how to map E1ADRM1/E1ADRE1/EXTEND_D with qualifiers such as RG,AG,WE.
Please help me out.
If step by step document will be provided then it would be a great help.
I will appreciate every helpful suggestion.
Thanks,
Dipen.

Hi Dipen,
Please follow the basic mapping functions and find my bellow Mapping Logic may its help you.
Regards,
Rajendar K

AII Flex Del Scenario DESADV.DELVRY03 IDOC

Hi
I am working on IDOC-TO-IDOC scenario in flexible delivery scenario.
When an ASN is sent from supplier system to customer system via XI the idoc DESADV.DELVRY03 is used to create inbound delivery against the purchase order
While executing IDOC in target system, the system gave error with error status 51.
<b>the error is POSEX field is empty.</b>
I tried to test execute this IDOC in transaction we19 by filling value of POSEX.
What should be the value of this field so that IDOC is executed properly?
Looking forward to pointers to above query.
Thanks in advance.
Amit Deshpande

Hello Amit,
There are 2 POSEX fields in the DELVRY03 Idoc,
E1EDL24-POSEX is External item number
E1EDL41-POSEX is Item Number of the Underlying Purchase Order
Go to WE60 and put in DELVRY03 and look this up.
In the IDOC it should show which segment is in error.
Regards

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.

Problem with IDoc for an outbound delivery

Dear All,
I am facing a problem with the IDoc defined for an outbound delivery.
Scenario:
Implementation of a small enhancement for an IDoc (DESADV, DELVRY01) created for an outbound delivery (in VL02N).
What I did:
I implemented the EXIT_SAPLV56K_002 exit in the V56K0001 enhancement, activated in SMOD, assigned V56K0001 component in CMOD and acivated it. Then I put a breakpoint on the ZXTRKU02 include. For me everything in SMOD and CMOD looks OK.
I have also created a partner profile, port, outbound message config. (message DESADV, basic type DELVRY01, application V2, output message type LAVA, process code DELV. function module used for this process code is IDOC_OUTPUT_DELVRY).
What I can do:
I can issue an IDoc message, it looks ok and contains the standard data.
Problem:
It seems that the enhancement does not work. Finally I put there only one line of code to avoid a program bug and just to check . The system does not stop at the breakpoint (set on the ZXTRKU02 include in the EXIT_SAPLV56K_002 exit).
Am I using the proper exit? I appreciate any suggestions.
Thanks,
Grzegorz Skorus

Hello Grzegorz
Not an expert on this, but noone is responding so I thought let me try and help you. You seem to be doing the right things as mentioned in OSS note 1498409.
Firstly since this can be called form Shipment Idoc also, you may need to make a differentiation by the interface parameter 'MESSAGE_TYPE' or segment name. See the attached OSS note, though it belongs to older releases, it may help you.
Also help says 'The callup of this function module is programmed for each enhancement of the internal table for the IDoc (in other words, when you add an extra segment'. So may be you need to add an extra segment/field to make it work.
Futher the user exits are replaced by BADIs. May be you should use exit_badi_v56k.
Hope this helps and others will pitch in.
1498409 - Valuation Type unavailable when creating deliveries using IDOC
631913 - Exit after formatting delivery IDoc type DELVRY

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

Idoc delvry03 - Create inbound delivery without ref. to purchase order?

Hello,
we want to use LES with handling-unit management. For this we have to create inbound-deliverys without any reference to an purchase-order. Manually we can do this via TA MB1C with movement type 501 for a handling-unit storage location. In this case MB1C creates an inbound-delivery with delivery-type "HID". Then we can pack handling-units with TA VL32N. Now i will do this with idoc desadv/delvry03 but the FM idoc_input_desadv1 checks the existence of an purchase order so we cannot even change an existing delivery. Has anyone done this before or any idea to do this?
regards
Andreas

Hi Andreas,
I have a similar requirement. Did you get any solution for the same?
Himanshu

IDOC DESADV CHANE

Similar Messages

Maybe you are looking for