SD Delivery Update via Inbound IDoc

[Former Member]

My company is beginning a project with a 3PL for logistics services however we will be managing the SD and IM processes in our SAP 4.6C system. I have setup a LAVA output for the DELVRY03 IDoc upon the creation of a Delivery for a customer sales order to send to the 3PL, to which the 3PL will pick/pack in there WMS system and send an IDoc back to us to pick/pack/post the delivery in the SAP system. I'm struggle to find the correct IDoc, message type and process code for this inbound update. Any help on getting started in the right direct would be appreciated.

[ferry_lianto · Accepted solution]

Hi Joseph,

The serial numbers process and post good issue the delivery are beyond the scope of the DESADV/DELS processing.

Perhaps you can have post processing after the inbound update delivery process completed.

Hope this will help.

Regards,

Ferry Lianto

Please reward points if helpful.

[ferry_lianto]

Hi Joseph,

Interesting?

Did you populate S_DL20-VBELN, S_DL24-POSNR and S_DL11-SERNR segments correctly?

Perhaps you need to fill up with zero for VBELN and POSNR and SERNR values. For example, '0001234567' instead of '1234567'.

WHEN 'E1EDL11'.
  CLEAR S_SERNR.
  S_DL11 = IDOC_DATA-SDATA.
  S_SERNR-RFBEL = S_DL20-VBELN.
  S_SERNR-RFPOS = S_DL24-POSNR.
  S_SERNR-SERNR = S_DL11-SERNR.
  APPEND S_SERNR TO T_SERNR.

Regards,

Ferry Lianto

[Former Member]

I found a note relevant to this issue and my SAP release 46.C.

SAP Note: 777853

Symptom

Serial numbers in the E1EDL11 segment of a DELVRY03 type IDoc (Message category WHSCON or SHPCON) are not transferred to the delivery.

Other terms

DELVRY01, DELVRY02, WHSCON, SHPCON, IDOC_INPUT_DELVRY

Reason and Prerequisites

This function is only available as of Release 4.70, however, to date this is only available for the connection of a decentralized WMS. The IDoc inbound processing for the DELVRY03 message types WHSCON and SHPCON was not yet adjusted appropriately.

Solution

With the following correction you can also transfer the serial number via WHSCON- and SHPCON IDocs.

This function cannot be made available for releases < 4.70.

So this doesn't look so good for me, WHSCON works in that it picks and packs my delivery, I only need the serial number update in order to PGI the delivery.

When using DESADV/DELS on the inbound is that geared towards creating inbound delivery against a PO rather then updating a customer order delivery?

[ferry_lianto]

Hi Joseph,

You may want to use message type WHSCON/WHSORD, IDoc type DELVRY03 and process code DELV instead.

Regards,

Ferry Lianto

[Former Member]

I believe we are on the right path as I discovered using DELVRY03 IDoc with Message WHSCON and process code DELV with allow me to pick and pack my customer SD delivery as long as specify PIC in the E1EDL18 segment, in this model we are using only inventory management and not warehouse management (no TO). However, my hurdle is the serial numbers for the materials line items, I'm including valid serial numbers E1EDL11 segment however they are not being recognized in the processing routine.

[ferry_lianto]

Hi Joseph,

Apologies for early replied.

Process code DELS should be able to update the serial number from segment E1EDL11 but not do the post good issue.

How did you polulate segment E1EDL11?

You need to have the following information in order to update with serial number..

*Serial numbers  
 WHEN 'E1EDL11'.
   CLEAR S_SERNR.
   S_DL11 = IDOC_DATA-SDATA.
   S_SERNR-RFBEL = S_DL20-VBELN.    <- Need this info
   S_SERNR-RFPOS = S_DL24-POSNR.    <- Need this info
   S_SERNR-SERNR = S_DL11-SERNR.    <- Need this info
   APPEND S_SERNR TO T_SERNR

   ...

then at the end it will call this FM to update the delivery.

CALL FUNCTION 'WS_DELIVERY_UPDATE_2'
   EXPORTING
     VBKOK_WA        = S_KOKO
     DELIVERY        = S_KOKO-VBELN_VL
     UPDATE_PICKING  = F_PUPD
     IT_SERNR_UPDATE = T_SERNR     <- Serial number info
   TABLES
     VBPOK_TAB     =  T_KOPO
     PROT          =  T_PROT
     VERKO_TAB     =  T_VSEK
     VERPO_TAB     =  T_VSEP
     IT_VERPO_SERNR = T_VERPO_SERNR
     IT_REPACK     =  T_REPACK
     TVPOD_TAB     =  T_POD
   EXCEPTIONS
     ERROR_MESSAGE = 1
     OTHERS        = 2. 

So you do not need to create custom BDC solution.

Hope this will help.

Regards,

Ferry Lianto

[Former Member]

Just realized something.. I was using process code DELV and not DELS, when I used DELS I receive the following error.

Function module not allowed: IDOC_INPUT_DESADV1

Message no. B1 252

Diagnosis

The function module IDOC_INPUT_DESADV1 and the application object type BUS2015 which were determined are not valid for this IDoc.

I'm using the DELVRY03 IDOC to update existing deliveries with pick/pack information (with serial numbers).

Any further thoughts?

[Former Member]

I also just realized after going through the FM IDOC_INPUT_DESADV1 associated with DESADV/DELS that it does a check for the a purchase order from table EKKO. I need to update a delivery create by sales order to be shipped to customer and not a delivery of materials to be received against a purchase order. Is there something I'm missing?

[Former Member]

Judging by the OSS note regarding the serial number updates, it looks as though I will use the WHSCON with DELS to pick/pack the delivery. Now I must write an application to pull the serials from the IDoc tables then update the deliveries via an FM. I'm using READ_IDOC_COMPLETELY to get the serial numbers from the E1EDL11 segments. Do you know of good FM or BAPI to use to update the serial numbers in an existing delivery, perhaps WS_DELIVERY_UPDATE? Any sample code?

[Former Member]

Joseph,

I'm doing exactly the same you're doing. I found out the the E1EDL11 is useless in the serial numbers. How did you fix this problem? Did you go a different route?

[Former Member]

I did resolve this by using a work around. I used the DELVRY03 IDoc with WHSCON message type to pick/pack the SD delivery then I had to have a custom ABAP routine run to read the serial numbers from the IDoc and post into the delivery. We had two options to do this, one was to copied WHSCON to a Z message type and add in the custom ABAP code or we could have just had the Z program run after the IDoc processing via scheduling.

[Former Member]

Do you know if there are alternate message types and process codes that I could use to update the serial numbers on a delivery via an inbound DELVRY03 IDoc?

I have a potential solution but I would need to create an ABAP application to read in the DELVRY03 IDocs then update the delivery in a BDC.

Thanks!

[ferry_lianto]

Hi Joseph,

Welcome to SDN.

You can use message type <b>DESADV</b>, IDoc type <b>DELVRY03</b> and process code <b>DELS</b> to update the delivery.

Hope this will help.

Regards,

Ferry Lianto

Please reward points if helpful.

[Former Member]

Thank you for the quick response.

I tried this and it does pack the delivery however it does not take the serial numbers from the E1EDL11 segment and process them or post good issue the delivery. Do think this goes beyond the scope of the DESADV/DELS processing?