Inbound Delivery DELVRY03 Segment E1EDT13

I am able to create an Inbound Delivery using the Basic IDoc type DELVRY03 with correct Delivery Date in Segment E1EDT13 qualifier '007'.
However I am not able to populate the correct Document Date (LIKP-BLDAT) with qualifier '015' Document Date? The Delivery creates but the Document Date is todays date. Basically nothing is happening with the date in this segment.
Is there something else needed to get the Document Date to post from the IDoc?
Thanks in advance,
Craig

Thank you again for your input!
See below for Function Module code that appears to call out this Segment and should be processing the different qualifiers. Include I56IDOVA (pertinent extract below) appears to have the qualifiers present but doesn't process? Is it your belief that we will need to make changes to the processing code to correctly populate the Document Date?
Inbound function module IDOC_INPUT_DESADV1
      WHEN 'E1EDT13'.
        s_dt13 = idoc_data-sdata.
        CASE s_dt13-qualf.
          WHEN e1edt13_qualf-lfdat.
            mv s_dt13-ntanf t_dlgn-lfdat.
            mv s_dt13-ntanz t_dlgn-lfuhr.
            PERFORM field_check USING s_dt13-ntanf 'NTANF'.
            PERFORM date_syntax_check USING s_dt13-ntanf.
            PERFORM date_syntax_check USING s_dt13-ntanf.
            PERFORM TIME_SYNTAX_CHECK USING S_DT13-NTANZ.   "n_947083
          WHEN OTHERS.
        ENDCASE.
Include I56IDOVA
deadlines on delivery header
CONSTANTS: BEGIN OF e1edt13_qualf,
             tddat      LIKE e1edt13-qualf   VALUE '001', "shipm.plang.
             lddat      LIKE e1edt13-qualf   VALUE '003', "loading
             wadat      LIKE e1edt13-qualf   VALUE '006', "goods issue
             lfdat      LIKE e1edt13-qualf   VALUE '007', "delivery
             ankft      LIKE e1edt13-qualf   VALUE '008', "arrival
             abfrt      LIKE e1edt13-qualf   VALUE '009', "departure
             kodat      LIKE e1edt13-qualf   VALUE '010', "picking
<<< START_OF_INSERTION_HP_204779 >>>
             bldat      LIKE e1edt13-qualf   VALUE '015', "doc date
<<< END_OF_INSERTION_HP_204779 >>>
             frei       LIKE e1edt13-qualf   VALUE '499', "others
           END OF   e1edt13_qualf.

Similar Messages

Inbound processing of segment E1EDT13 - QUALF 499 in SHPMNT idoc

Dear all,
we are currently facing the problem, that we want to send customized deadline dates in a SHPMNT 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 SHPMNT using qualifier 499 in segment E1EDT13?
Kind regards
Harry
PS: We are using a ECC 6.0 release.
PPS: I posted the wrong idoc type in a previous message.

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

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

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

Idoc DELVRY03/DESADV for Inbound delivery with serial number

Hi,
We have set up am EDI process between our vendors ERP system and our SAP. We will send purchase order Idocs to our vendor, once our vendor has shipped the goods (to our customer) he send an DESADV/DELVRY03 Idoc back to our system. This Idoc will create a statistical inbound delivery and a statistical goods receipt will be automatically created in our SAP system.
This process runs fine as long as we use materials without serial numbers. Unfortunately we have some materials which need to have a serial number assigned by our vendor and we want to keep track of this information in our SAP system.
The only place where I found a serial number field in the Idoc is in the 'E1EDL46 : Serial Numbers HU' segment in the DELVRY03 Idoc, but unfortunately we don't have handling units activated in our SAP system. So if we fill this information the Idoc processing fails.
Is there any other way to create an inbound delivery containing serial number information without activating handling units?
Thanks for your help,
Frank

Hi,
is there anyone who has experience with EDI inbound delivery postings containing serial number information?
Thank you,
Frank

Post Goods Receipt for Inbound Delivery via IDoc SHPCON (DELVRY03)

hi all,
I'm using IDoc SHPCON (Delvry03) for posing goods receipt for inbound delivry.
Can anyone give a sample IDoc or tell which segments must be filled.
Thanks!
Regards,
Hui

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

Trigger internal serial nos creation for inbound delivery using DELVRY03

Hi all,
I am working in ECC 6.0 I need to update serial nos in the inbound delivery. The internal serial nos. that will be generated by the system, I have to trap them for a given delivery and map it to a set of external serial nos.(length is 40 chars) and update in a Z table.
For changing the delivery, I am using idoc DELVRY03 (message SHPCON). Within the idoc I am not able to find any such field which will trigger the automatic creation of internal serial nos. In case of idoc MBGMCR03 (goods movement), there is a field E1BP2017_GM_ITEM_CREATE-SERIALNO_AUTO_NUMBERASSIGNMENT which when set to 'X', the internal serial nos are automatically generated and can be found in table SER03.
I want a similar thing for the DELVRY03 idoc. Can anyone help me on this?
If not possible through Idoc, then whats the other option?
My aim is to just get the internal serial nos created through delivery change activity.
Note - The serial no. profile cannot have the option of serial no. usage set to '04 - automatic' in SPRO as per the client's business process.
Thanks,
Shoma

Hi Shoma,
copy the FM which is assigned to your processcode and copy to ZFM and write your modifications on that ZFM.
It will resolves your problem.
Regards,
Venkat.

Inbound Delivery changes DELVRY03.

Hi ,
Iam facing a problem in my inbound Delivery changes   interface.
Message Type: DESADV
Basic type:        DELVRY03 are using for the interface .
This interface is working fine for creation .
we are using the same interface for in bound delivery change also by the help of FM    IDOC_INPUT_DELVRY.
it is successfullu posted with a message " Delivery <no> changed.
But the quantity values iam changing is not reflecting .
I tried with E1EDL18-Qualifier as ORI as well as CHG.
Is there anything else to do...
please help
Thanks ,
Sarath P

hi,
Still issue is not solved.
the interface i created internally using the FM    WS_DELIVERY_UPDATE_2 to update the delivery .
i changed the quantity , but its not reflectiong in vl33n .
Experts , please help
Sarath

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

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 ?

Issue using DELVRY03 to update wieghts in inbound delivery

Hi All,
I am trying to use DELVRY03 to update netweight of inbound delivery. when I do that, its creating a new delivery and net weight is getting fetched from PO automatically instead of the entered one. Can anyone help?
I have also added qualifier in E1EDL18 as CHG.
Thanks in advance,
Kalyan Venigalla.
Edited by: Kalyan Mohan Venigalla on May 25, 2009 9:32 AM

hi,
see code of FM: IDOC_INPUT_DELVRY, maybe qal = 'GWT' from E1EDL18
will be better?

Trigger IDoc DELVRY03 after Inbound Delivery create

Hi,
Inbound delivery is created through an Inbound IDoc and I want to trigger an outbound DELVRY03 IDoc when the Inbound Delivery is created.
How do I trigger this?
Regards,
Sneha

You have to setup output control,let me say one example
when you create delivery ,then immeditely output type will trigger LD00,you need to set up partner profile ,according to that outbound idoc will trigger.

IDoc type "DELVRY03" for INBOUND delivery confirmation and Outbound Deliver

Hi ,
We have a requirement where we have to send Inbound delivery confirmation as well as outbound delivery notification to our same customer. (3PL case)
We have a EDI partner who is receiving our messages and transforming them before sending it to customer.
Now my problem is , since I am using same idoc type (DELVRY03) for both cases therefore wondering how my EDI partner will differentiate whether received message is a INBOUND delivery confirmation or OUTBound delivery notification.
regards
Shrey

Thx for your reply ...
Wondering about the impacts , if I create a new message type like ZDESADV and attach it to DELVRY03.
In this i could have two message types DESADV and ZDESADV.
Will it impact anywhere ?
Regards
Shrey

Inbound Delivery via IDoc DELVRY03

Does anyone have a template of what fields to fill in for the DELVRY03 IDoc in order to create an inbound delivery in SAP? I am looking to create an inbound delivery document based on a DELVRY03 including packing info, tracking and serial numbers.
Thanks
Kevin

Check out following link, it provides some sample mappings for delivery IDOC -
http://www.sapgenie.com/sapedi/ansi.htm
http://www.sapgenie.com/sapgenie/docs/o856v4010_template.xls
Cheers,
Sanjeev

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 DELVRY03 Segment E1EDT13

Similar Messages

Maybe you are looking for