Inbound Delivery Idoc for PO
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 :
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.
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.
Pls check if the GR has already happened manually.
Hope this helps.
Similar Messages
-
Tracking of Inbound Delivery reference for a Goods Receipt/GR line item
Hi,
We are posting goods receipt with reference Inbound delivery. We need to track Inbound delivery reference for a Goods Receipt/Goods Receipt line item.
Is it possible? What will be correct way to do this?
Regards,
MakarandHi Makarand ,
You may try with Table MKPF.
Goto SE16 and enter the above table to get the required data.
Regards
Ramesh Ch -
How to create a Inbound delivery type for a special purchase order type
Hi,
I try to create a special Inbound delivery type for a special purchase order type (a transfer purchase order).
In SD module, I can créate a special outbound delivery and precise the sale order type, but I don't manage to do it for a Inbound delivery type.
Do you know if i can do it without specifiq?
Regards,
RoselyneHi Roselyne,
What you experienced is standard system behavior. Inbound delivery type is uniquely assigned to confirmation control key. You can only specify confirmation control key on item level in PO. The assignment of Delivery type can be seen in the following table:
T163D
IBTYP EBTYP LFART RETDLV
1 AB X
2 LA EL X
3 GW EG
The field T163D-IBTYP is checked in different programms. For example in programm RM06ENAB (TA: ME92F). If you insist to customize the determination of delivery type by PO type, I strongly suggest you discuss with the Application consultants before making the modifications to ensure it won't impact other areas. -
Inbound Delivery Idoc processing for Purchase Order
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 :
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.
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 Milind,
Did you get this to work?
Thanks,
Finbarr -
LS System for Inbound delivery idoc
Hi,
I am able to define transfer the master data between ECC and EWM system, however i have an issue for transactional data e.g. inbound delivery.
When I create inbound delivery then system generates an IDOC but it picks up a different logical system as against the one defined for my system. When I generated my distribution model, i got a message that it is successfully created and I can see my message type and filter details(my warehouse etc) on the message type.
Can someone kindly suggest how EWM picks up LOgical system, my understanding is that it is based ont he configurtion(WM to EWM location definition and distribution model). But I am confused now and trying to understand why system is not finding my LS system?
Any link to supporting documentation would really help.
Thanks and regards,
BhaskarI found the root cause, there was another LS system model was there in my system, I regenerated partner profiles and that resolved the issue.
-
Mandatory fields for inbound delivery idocs
hi all
i want to generate inbound idocs for inbound delivery ASN
i am using message type DESADV and idoc type /AFS/DELVRY03
in order to generate inbound idoc what are mandatory values i have to pass to the idocs
thanks
AnilHI,
I created inbound idoc for ASN Inbound delivery in test mode we19
i got idoc with status 62, when i am trying to process the idoc in bd87, its allowing me
is there any other way to process the idocs , so that status will be 53
thanks -
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,
KrishnaThanks 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 -
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,
KashifHI,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 ? -
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 -
GR against Inbound Delivery (IDoc)
Hi All,
I am trying to post Goods Receipt against Inbound Delivery. What is the IDoc/Message Type I need to use for this and what segments I should populate?
So far I have tried using...
<i><b>MBGMCR02</b> - has serial numbers (errors out with a short dump and says "Cannot be processed with this transaction." Application VL and message Number 143. I don't know how to proceed further
and <b>SHP_IBDLV_CONFIRM_DECENTRAL01</b>(this does not have serial numbers). IDoc was processed, but I am not sure what it updated. When I looked at the PO History it did not have a record for GR Inbound Delivery like you would see when you do the GR for Inbound delivery using MIGO.</i>
Any help would be appreciated.
Thanks,
SnehaSee the below link :
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
Reward Points if it is helpful
Thanks
Seshu -
SAP Standard INbound Delivery IDOC
Hi All,
Pease let me know the
Messahe type,Process Code and Basic Type, Function Module for Inbound Delivery
as well as which message type do i need to setup in NACR
Regards
AmeyHello,
there is nothing to maintain in NACR for inbound delivery (MM).
FM creates Inbound delivery via IDOC.
Please refer to help.sap.com [EDI Inbound Processing of a Shipping Notification |http://help.sap.com/erp2005_ehp_05/helpdata/EN/11/dcbd10bd9211d188ef0000e8216438/content.htm]
Andrzej -
Creation of Inbound delivery mandatory for ASN process in classic scenario?
Dear Experts,
We are going for classic scenario for our green field SRM implementation process. Our client is not using ASN process in their existing MM process. However, they are now looking for an oppurtunity to enable Suppliers to trigger ASN using SUS. In such case, is creation of inbound delivery from Buyer side a mandatory process?
Is the below the process correct?
PO -> ASN (Supplier using SUS) -> Inbound delivery (Optional) -> Goods Receipt (Mandatory) -> Invoicing.
Here, I understand that Goods receipt can be verified against the PO or via Inbound delivery to PO. ASN will inform the store keeper in advance about impending goods receipt and smoothen the confirmation process.
Could you please comment on the above process? Could you please suggest the best practices followed here?
Thanks and regards,
Ranjan
Ranjan SutradharHey Ranjan!,
You are on track.
The process flow you have shown is true. ASN is available as a standard as part of the MM-SUS process. It makes the buyer aware of any delays in delivery or to make arrangements on shipping docks to receive goods on a said date etc.
Regards,
Nikhil -
Inbound Delivery Idoc- Create ... help required
Hi,
I'm using DELVRY01 idoc to create deliveries. when i execute using test tool, the idoc gets created with error status 51 with following errors:
Field EXIDV empty
Message no. VL243
Diagnosis
A required field in the intermediate document (IDoc) is not filled. This is the field EXIDV in segment 000042.
Field VHILM empty
Message no. VL243
Diagnosis
A required field in the intermediate document (IDoc) is not filled. This is the field VHILM in segment 000039
But these errors reflect to handling unit from segment E1EDL37 and its sub nodes which are really NOT required in my case.
Now confused if i'm using a wrong reference of creating inbound delivery. Pls shre some thoughts on it on troubleshooting this issue.Hi Prabhu
these two fields are mandatory .. fill below details
E1EDL37-Handling unit header
EXIDV <XXXXXXXXXXXXX> External Handling Unit Identification
GWEIT <LB> Weight Unit Tare
BRGEW <000XX> Total Weight of Handling Unit
VHILM <Dummy Packing Material> Packaging Materials
E1EDL44-IDoc: Handling Unit Item (Delivery)
VBELN <Delivery nO> Sales and Distribution Document Number
POSNR <900004> Item number of the SD document
EXIDV <XXXXXXXXXXXXX> External Handling Unit Identification
VEMNG <00001> Base Quantity Packed in the Handling Unit Item
Dont forget to create Dummy packing material no...
i think above mapping helps you...
Thanks
Ramesh -
FM / BAPI Inbound delivery creation for a Purchase Order without material
Dear All,
I have a requirement to create a Inbound Delivery for a Purchase order without material number. The Purchase Order has only Material text and no material number. Please let me know a BAPI or FM to create inbound delivery in this case where there is no material defined on PO. I require BAPI / FM since I have to make a web-service for the same.
Thanks in advance!
AbhishekHi I did a coding in one of the userexit. If ekpo-matnr is empty then fill
KOMDLGN-UMVKZ = 1
KOMDLGN-UMVKN = 1
KOMDLGN-MEINS = EKPO-MEINS
This parameters i.e. Qty conversion are necessary and since MATNR does not exists it has to be filled. -
Error during inbound delivery creation for some times not always
Hi,
I'm getting the following error when i'm trying to create an inbound delivery for PO.
Diagnosis
The system attempted to find the reference movement type for
the Warehouse Management system. A corresponding entry is
missing in table 156S with the argument 101/X/X/ / /X/.
The argument consists of:
o IM movement type
o Indicator: Value update
o Indicator: Quantity update
o Special stock
o Movement indicator
o Access indicator
o Indicator: Consumption
Can someone help me to resolve it? as it is not happening always
Appreciates everyone time and help.
Thanks and regards,
SivaHi,
Thanks for the response and yes i did maintained IM/WM mvt types for 101 in both places.
If the movement type is maintained well why SAP says it is not?
SPRO > LE > WM > Interfaces > IM > Define Movement Types - "Assign WM Movement Type References to IM Movement Types'
Related tabel is V_156S_WM
If you check your configuration you will see that there are many entries with 101, and there are several other parameters...
First you should check what you are doing in IM, what parameters that mvt has (qty, value update, special stock, etc) > after that you should check whether it is maintained well in WM customizing - see steps in my previous email.
Regards,
Csaba
Maybe you are looking for
-
Need to make app appear on iPhone screen; previously, wasn't enough pages, but now have created folders. Still app won't show up unless I search for it.
-
Windows on powerbook for games- What's the best program
Hey guys I need help with some Info I'm trying to install windows XP Pro and I hear bootcamp is the best but I have a 1.5Ghz (17" Powerbook- 64mb graphics) and I don't think it will run! Anyone knows about this for sure? Second, I have virtual pc ins
-
Brand New MacBook - what's wrong???
I am on my third MacBook in the last 6 weeks. I upgraded to the MacBook Pro yesterday from the black MacBook. All of my information was copied to the new book, but now when I try to import photos I get the following error message: An error occurred w
-
Create Business Action : Document Type Error
I am trying to create Create Business Action for X12 over Generic In the Document Definition block, I have entered Name : 850 Definition Definition : 850.xsd Document Type Parameters Functional Group Identifier Code : PO Transaction Set ecs File : 85
-
Contacted MSI tech support, my motherboard only supports Gen. 2, this seems to be the problem.