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

Similar Messages

ASN from vendor and inbound delivery creation

hi
I have a scenario where vendor sends ASN via EDI to R/3.
This inbound ASN should create an inbound delivery.
Can you please help me knowing the idoc type, message type etc which will serve my purpose.
Also the FM / Badi for inbound delivery creation.
thanks in advance,
Jo

Hi,
Use DESADV Message type and basic type DESADV01
Use function module IDOC_INPUT_DESADV
Edited by: Chandra Shekhar Singh on Jul 5, 2011 12:39 PM

Inbound delivery creation using VL31N

Hi All,
I could find that the message type DESADV, IDoc type DELVRY01 and process code DELS is used for creation of this.
Let me know if this is correct. When i checked in my system I could not find process code DELS. Do i need to do some additional settings to get this.
What is difference between IDOC type DELVRY01 and DELVRY03. Which one should be used.
Here the ASN received is triggering inbound delivery creation.
Please let me know on this.
Regards,
Shahu

Hi,
Where did you check that process code in WE64?
Check in the correct set(Inbound messages).
DELVRY03 is the latest one. You should use it only.
Regards,
Ravi

Auto Inbound delivery creation

Hi Sapgurus,
I am trying to create Inbound delivery from Outbound delivery after it has been PGI'ed. These both are related to Intracompany STO. We have WM implemented so both of these deliveries result in TO creation and can be closed only after TO confirmations. I used SAP notes which stated to use SPED output type in output determination procedure for outbound delivery and then assign output determination procedure to delivery type. But I was not successful in getting the desired results.
Can anyone please provide me with the steps of this configuration, I may be doing wrong something somewhere.
Appreciate the help.
Thanks in advance
Manav Anand

Hi,
I think you are talking about stock transfer between two plants. I assume your requirement is after PGI of the replenishment delivery system should create automatic inbound delivery in second warehouse,right?
You can create inbound delivery automatically for second warehouse.I had such scenario in my previous client.I believe through some user exit you can initiate inbound delivery creation immediately.
Please check with your technical person.
Regards,
PRashant

Check amount of transition stock during inbound delivery creation

I want to move stock between plans, therefore I have the following steps:
1. Stock Transfer Order (STO), e.g. 500 pieces
2. Sending plant: MIGO (GI for STO) with MT 351 to post to transition stock, e.g. 100 pieces
3. Receiving plant: Inbound Delivery with reference to STO VL31N
4. process Inbound delivery in warehouse (SAP-WM)
The question is:
During step 3, when accessing VL31N the system proposes the full order quantity (e.g. 500 pc.)
I can change the amount to any amount I like, e.g 240 pieces.
How can I tell SAP, that Inbound delivery creation is only possible for the amount
which has been posted to stock in transition (100 pieces)
I want an error/warning message in case user wants to create Inbound delivery quantity higher than the amount that has been posted to transition stock.
Any ideas?

MIGO in sending Plant?
How it is possible? MIGO means, Goods receipt. This should be in Receiving plant.
Sending plant should do the PGI
MIRO in receiving plant
Billing in sending plant
Payment from Receiving palnt and clearing in sending plant
Correct me if i am wrong
Thanks

Issue with Message Type Triggering during Inbound Delivery Creation

Hi Experts,
Hi Experts,
Currently we are facing issue with message type triggering during inbound delivery creation:
In NACE transaction for Inbound delivery we have 3 custom output types:
Pricing Procedure Used is standard one -> E10001
Z140 Inbound Delivery Create (This should get triggered when IB delivery is created)
Z141 Inbound Delivery Change (This should get triggered when IB Delivery is changed)
Z142 Inbound Delivery Delete(This should get triggered when IB Delivery is deleted).
At present if i check delivery in VL33 -> Extras -> Delivery Output
Both Z140 and Z141 are being triggered during IB delivery creation. While it should be only Z140.
Could you please suggest that are we missing any configuration in SPRO or we need to create any custom routine (requirement) to handle this?
Thanks

Hi,
There is no fine-tuned control for inbound delivery messages as for Purchase order. Hence I guess to meet your above requirement, you have to go for a custom solution similar to the PO fine tune control settings.
Thanks,

User exit to change partner for inbound delivery creation

Hello,
I have a requirement to change the partner number for
the inbound delivery creation.
I only see the USEREXIT_MOVE_FIELD_TO_LIKP but I am not sure if this is
the right user exit for this requirement.
Is there the user exit for modifying partner in the inbound delivery?
Thanks in advance,

HI
There is a program with which you can find the available exits as per your requirement. You have to execute the same and give your transaction code. Hope this helps...
*& Report ZFINDUSEREXIT
report zfinduserexit.
tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
tables : tstct.
data : jtab like tadir occurs 0 with header line.
data : field1(30).
data : v_devclass like tadir-devclass.
parameters : p_tcode like tstc-tcode obligatory.
select single * from tstc where tcode eq p_tcode.
if sy-subrc eq 0.
select single * from tadir where pgmid = 'R3TR'
and object = 'PROG'
and obj_name = tstc-pgmna.
move : tadir-devclass to v_devclass.
if sy-subrc ne 0.
select single * from trdir where name = tstc-pgmna.
if trdir-subc eq 'F'.
select single * from tfdir where pname = tstc-pgmna.
select single * from enlfdir where funcname =
tfdir-funcname.
select single * from tadir where pgmid = 'R3TR'
and object = 'FUGR'
and obj_name eq enlfdir-area.
move : tadir-devclass to v_devclass.
endif.
endif.
select * from tadir into table jtab
where pgmid = 'R3TR'
and object = 'SMOD'
and devclass = v_devclass.
select single * from tstct where sprsl eq sy-langu and
tcode eq p_tcode.
format color col_positive intensified off.
write:/(19) 'Transaction Code - ',
20(20) p_tcode,
45(50) tstct-ttext.
skip.
if not jtab[] is initial.
write:/(95) sy-uline.
format color col_heading intensified on.
write:/1 sy-vline,
2 'Exit Name',
21 sy-vline ,
22 'Description',
95 sy-vline.
write:/(95) sy-uline.
loop at jtab.
select single * from modsapt
where sprsl = sy-langu and
name = jtab-obj_name.
format color col_normal intensified off.
write:/1 sy-vline,
2 jtab-obj_name hotspot on,
21 sy-vline ,
22 modsapt-modtext,
95 sy-vline.
endloop.
write:/(95) sy-uline.
describe table jtab.
skip.
format color col_total intensified on.
write:/ 'No of Exits:' , sy-tfill.
else.
format color col_negative intensified on.
write:/(95) 'No User Exit exists'.
endif.
else.
format color col_negative intensified on.
write:/(95) 'Transaction Code Does Not Exist'.
endif.
at line-selection.
get cursor field field1.
check field1(4) eq 'JTAB'.
set parameter id 'MON' field sy-lisel+1(10).
<b>Do reward if useful...</b>
Regards
Dinesh

Inbound delivery creation through IDOC

Dear Experts,
I have scenaris like one STO with multiple deliveries with same materials and the same assigned to shipment, through the shipment out put IDOC will generate and created the inbound delivery, the same hace to updated the STO.
in the above scenario, inbound delivery is creating base don the outbound delivery items through IDOC (in case the same material is available in the different deliveries it is getting copied)
by in my case inbound deliveri has to created bbased on the STO items. can you please let us know how to develop the logic for the same and is there any function modules for the same.
Please keep in mind if the same materila with same batch is in outbound delivery we have to cosolidate the same and create one line item in inbound delivery.
awaiting your response soon. please help me out with IDOC programe and tables and fields with function modules.
Thanks & ragrds
Raju.

Dear,
so for no updates , can you let us know your possible solution to take up this challange.
Thanks
Raju.

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/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 through VL01N

Hello,
I wud like to create inbound(return) delivery through VL01N t-code with reference of sales/repair order.
following things i am passing to VL01N screen:
1. Shipping point
2.delivery date = current date
3.repair / sales order number
4.delivery type
suggest me any FM / BAPI
Edited by: anilpat1 on Apr 7, 2009 8:39 AM

Hi,
Did you mean VL31N for Inbound delivery as VL31N is the transaction for Inbound delivery not VL01N.
Try this function module below if it is a collective processing.
function module GN_DELIVERY_CREATE.
let me know if it worked.
R,
Srini

IDoc or BAPI for inbound delivery creation with reference to PO.

Hi
I have requirement to create a inbound delivery, I will get a ASN from external system with PO, Vendor Material number & batch. I want to know is there any BAPI or IDoc that can be used to create inbound delivery in R/3. I used BBP_INB_DELIVERY_CREATE to create inbound delivery and I was successful but problem is that inbound delivery was not updated with Vendor Material number & Batch. Can some one suggest me any other BAPI or IDoc ?
Thanks in advance
Nagendra P Boggarapu
Edited by: Nagendra P Boggarapu on May 6, 2010 4:06 PM

Use Delvry0* IDOC.
Reddy

Error during Inbound Delivery creation by Idoc DELVRY05

Hi,
We are trying to consolidate ASNs and creating an inbound delivery for the same. Thus we have more than one PO information in the idoc.
It processes fine and creates an inbound delivery if all the line item nos are different.
But the issue is, when there are articles which have the same line item no. even if the articles are different and they are on different POs. It gives the following errors.
1) "Delivery item cannot be exactly determined
Message no. HUFUNCTIONS313"
I tried to debug the above error and found that while packing it looks to the lips-vbeln/posnr & not the PO nr./PO item.
I am not sure if this could be handled by some config. Please advice.
2) "V51VP - item was not found - process cancelled
Message no. HUGENERAL056"
Any hints or comments on the above would be appreciated.
Thanks & Regards,
Akshay

Hi Raghavendra,
It has been a long time. But, as far as I can remember we had made coding adjustments in the customer-exit EXIT_SAPLV55K_004, include ZXTRKU12 to fetch the correct item and fill the idoc segment fields.
This resolved the issue.
Best Regards,
Akshay

Return(inbound delivery) creation through VL01N

Hello,
I wud like to create Return(Inbound) delivery through VL01N transaction. Following is the process i' m following.
1. create notification through IW51
2. create repair order through IW52
3.create return delivery ( automatically) through VL01N with reference to repair order created in step no.2.
I have searched for Function module & BAPI, but it seems there are no FM & BAPI's for such requirement.
Can any one suggest me the Functional solution for above problem.
Thanks,
Anil

Normally from the Notifications, We create a Return Order ( Document Type RE) automatically. We need to the necessary configurations.
We can create the Return Delivery from VL01n. when you mention the return sales orde there the system automatically pulls the return Delivery type LR from the configuration of the sales document type RE.
otherwise you have to mention explicitly the document type = LR in the selection screen of Vl01n.
You Can use the same BAPI or FM ( the one used to create the Outbound Delivery ) and mention the document type as LR.

Inbound delivery creation using shipment Idoc details

Hi,
   My requirement is that I need to create inbound delivery using SHPMNT05 idoc sending from a different plant.
Below are the fields I am getting from the SHPMNT05 Idoc. So I need to create Inbound delivery in Receiving plant.
SAP - Field     IDoc Segment- Position - Field Name
LIKP-LFART     E1EDL21 001 LFART
LIKP-LIFEX     E1EDT01 001 VBELN
LIKP-LIFNR     E1EDT44 009 LIFNR
LIKP-MBDAT     E1EDL24 039 = ABRDT
LIPS-LFIMG     E1EDL24 013 LFIMG
LIPS-MATNR     E1EDL24 002 MATNR
LIPS-VGPOS     E1EDL41 006 POSEX
LIPS-PSTYV     E1EDL26 001 PSTYV
LIPS-VGBEL     E1EDL41 002 BSTNR
LIPS-VRKME     E1EDL24 014 VRKME
VEKP-EXIDV     E1EDL37 001 EXIDV
VEKP-VHILM     E1EDL37 017 VHILM
VEPO-MATNR     E1EDL44 007 MATNR
VEPO-POSNR     E1EDL44 003 - POSNR
VEPO-VBELN     E1EDL44 002 - VBELN
VEPO-VELIN     E1EDL44 001 VELIN
VEPO-VEMEH     E1EDL44 006 VEMEH
VEPO-VEMNG     E1EDL44 005 VEMNG
Could you please help me to find some workaround to solve this ?
Thanks in advance.
Regards.
Ranjith

Hi Ranjith,
I guess there is a BAPI " /SPE/INB_DELIVERY_REPLACE " which can be used to create an inbound delivery.
Documentation-
FU /SPE/INB_DELIVERY_REPLACE
Short Text
Create inbound delivery
Functionality
You can use this method to distribute inbound deliveries from an ERP system to a WM system.
The following parameters are required:
HEADER_DATA Inbound delivery header data
SENDER_SYSTEM System of the sender
HEADER_PARTNER Header data of the partners
HEADER_DEADLINES Header data of the dates
ITEM_DATA Item data of the inbound delivery
ITEM_ORG Organisation data of the inbound delivery
Notes
The required parameters have the following required fields:
Import parameter HEADER_DATA
INB_DELVRY_NO
DLV_TYPE
Import parameter SENDER_SYSTEM
SENDERSYSTEM
Table parameter HEADER_PARTNER
PARTN_ROLE = 'LF'   Vendor is required partner
PARTNER_NO
Table parameter HEADER_DEADLINES
TIMETYPE = 'WSHDRLFDAT' Delivery date
Table parameter ITEM_DATA
INB_DELVRY_NO
ITM_NUMBER
MATERIAL
DLV_QTY
SALES_UNIT_ISO oder SALES_UNIT
Table parameter ITEM_DATA_ORG
PLANT
Further information
HEADER_PARTNER
Since the partners in the delivery are not managed on an item basis, the ITM_NUMBER field in the BAPIDLVPARTNER segment is left blank and not analyzed.
HANDLING_UNIT_ITEM
If the BAPI is used as an external interface for an external system, the packing hierarchy should be described as usual by using external identification numbers for shipping materials (HDL_UNIT_EXID_INTO/HDL_UNIT_EXID).
Parameters
HEADER_DATA
SENDER_SYSTEM
TECHN_CONTROL
HEADER_DATA_SPL
HEADER_CONTROL_SPL
HEADER_PARTNER
HEADER_PARTNER_ADDR
HEADER_DEADLINES
ITEM_DATA
ITEM_ORG
ITEM_STOCK_TRANS
ITEM_CODING_BLOCK
ITEM_REF_PURCHASE_ORDER
ITEM_SERIAL_NO
ITEM_DATA_SPL
TEXT_HEADER
TEXT_LINES
HANDLING_UNIT_HEADER
HANDLING_UNIT_ITEM
HANDLING_UNIT_SERNO
HANDLING_UNIT_ITEM_SPL
HANDLING_UNIT_HEADER_CROSS
HANDLING_UNIT_IDENTIFIERS
EXTENSION1
EXTENSION2
RETURN
TOKENREFERENCE
Exceptions
Function Group
/SPE/INB_DELIVERY
Check if this helps.
Reward helpful answers.
Regards
Parag

Inbound Delivery creation in ECC6.0 through IDoc (DELVRY03.DESADV)

Similar Messages

Maybe you are looking for