EDI Inbound delivery DESADV delvry03

I'm waiting on a translator for the mapping the above to create inbound deliveries but while I wait I'd like to set up a few scenarios on our system. Does anyone have a mapping documnet I could have a look at? If so could you send it to the e-mail address below.
Thanks for your help, Mark
[email protected]

Hai Mark,
Check this mapping template for delvry03 ...
http://www.sapgenie.com/sapgenie/docs/o856v4010_template.xls
Hope it will surely help u...
Regards,
Sridhar

Similar Messages

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

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 (DESADV): How to transmit SLED/BBD and Manufacture Date?

Hello
We have another challenging task to solve. Here is the scenario (SAP Release ERP 6.0):
One Lindt company (supplier) sends an outbound DESADV IDoc to another Lindt company (Purchaser). Here the inbound DESADV should create an inbound delivery. Finally, the inbound delivery is replicated to the external WHS partner who does the Goods Receipt against this inbound delivery.
The outbound DESADV contains all logistical data including SSCC. In particular, the batches have a manufacture date (LIPS-HSDAT) and a SLED/BBD (LIPS-VFDAT).
SLED = Shelf Life Expiration Date
BBD = Best-Before Date
In the outbound DESADV the SLED/BBD is mapped by default into segment E1EDL24/VFDAT. For the manufacture date we implemented an user-exit.
How does the inbound delivery look like? The batch number appears as "Vendor batch". The SLED/BBD does NOT show up even though the inbound DESADV contains the date in E1EDL24/VFDAT. This inbound DESADV did NOT contain any controlling segment E1EDL19. Adding this segment (QUALF = 'VDT' = Shelf Life Expiration or Best-Before Date) had no effect.
Here is my assumption why the SLED/BBD does not show up in the inbound delivery created by the inbound DESADV:
Because we do not yet have the "real" batch (just the "Vendor batch") the system ignores any SLED/BBD. As soon as the external WHS partner sends the GoodsReceipt message (as inbound WHSCON ) the inbound delivery is updated with the "real" batch as well as the SLED/BBD.
QUESTIONS:
(1) Why does the SLED/BBD not show up in the inbound delivery created by an inbound DESADV?
(2) Do we need another user-exit to map the manufacture date into the inbound delivery?
Once again thank you for sharing your time and expertise with us.
Regards
   Uwe

Apply SAP Note
Note 1576788 - Transfer of exp. date
(IDOC_INPUT_DESADV1) to inb. delivery
Here are the correction instructions for your reference:
=========================================
FORM DESADV_IDOC_PARSE
Delta001Context Block
        IF NOT t_dlgn-vbelv IS INITIAL.
          t_dlgn-posnv = s_dl24-posex.
        ENDIF.
Delete Block
        mv s_dl24-brgew t_dlgn-brgew.
Insert Block
        mv s_dl24-vfdat t_dlgn-vfdat.                         "n_1576788
        mv s_dl24-brgew t_dlgn-brgew.
Have fun!
- Joemil

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

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

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

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

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

How to skip the Inbound Delivery while updating LA confirmations via EDI

Hi Experts,
I have a requirement wherein I dont want to create Inbound Delivery automatically when updating the LA (or a copied Conf Cat of LA) confirmation via EDI. When we are using the message type DESADV, LA confirmations are being updated, but simultaneously, the Inbound delivery also being created. My client desires that Inbound Delivery should not happen and only LA confirmation should be updated via EDI.
Is there anyway, by which we can skip the Inbound Delivery while updating the LA confirmations in the PO?
Thanks in advance
Regards
Radha Krishna

Hi Prabhaharan,
Thanks for your quick response.
My requirement is to have both AB and LA confirmations. I have included these two in a new the conf control So, your suggestion will not work.
Is there any other way out to fulfill my requirement?
Thanks & Regards
Radha Krishna

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 w/o packing the HUs (idoc status is 'yellow' instead of 'red'). To avoid this OSS #912470 is the solution.
Kind Regards
Kay

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.

Inbound DESADV doesn't pack inbound delivery

I'm using in inbound IDOC (basic type DESADV01 / message type DESADV) to create Inbound deliveries. This IDOC contains packing information in segment(s) E1EDP08. This packing information however is not processed; the resulting inbound delivery is not packed.
In the partner profile I used process code DESA to process the IDOC. This process code is linked to Function Module 'IDOC_INPUT_DESADV'. If I look in this FM all code regarding segment E1EDP08 is commented. That must be the reason why the inbound delivery is not packed. Does anybody know if there is any other standard SAP functionality to create inbound deliveries that are packed.
Kind regards, Dick.

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

EDI Inbound delivery DESADV delvry03

Similar Messages

Maybe you are looking for