DESADV Idoc + duplicated Inbound deliveries

Hello.
I am using DESADV to create inbound deliveries in ECC6. For the Item category ELN (item categ. for inb. delivery), I have prevented to created zero quantity delivery item => via VL31N it is impossible to create a second delivery items for the same PO items if the first one gets the fully PO qty.
The issue is that when we try to do it with an DESADV Idoc, SAP allows it => 2 delivery items in 2 diff. deliveries having qty=PO qty.
Is there someone faced the same issue ?

Hi
I am bit confused with your posting, Data u were passing is not updated in the Field or what ....
VFDATA is Shelf Life Expiration or Best-Before Date ..correct
With regard
Bhargava

Similar Messages

Creation of Inbound Deliveries through IDOC

Hello All,
I have a scenario wherein through SPRO the configuration has been set to throw an error message in case a new delivery is getting created through VL31N and the total quantity of the inbound deliveries created till now(including the one getting created now) exceeds the PO quantity , but the same is not applicable for deliveries created through IDOC.
For example : I have a PO with order quantity of 2pc's
I create 2 inbound deliveries each of quantity 1 . Now if i try to create a new inbound delivery through VL31N system throws a error message.
But through an IDOC i am able to create any number of deliveries though the total of all the inbound deliveries exceeds the order quantity in PO.
Is there any way that the same SPRO setting can be made active for Inbound deliveries created through IDOC also.
Helpful answers would definitely be rewarded.
Thanks in Advance,
Sowmya.

IDocs and BAPIs sometimes behave differently than transactions. You might need to add a user exit specifically for IDoc processing. Otherwise send a message to SAP and have them look at it.

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

Grouping of inbound deliveries

Hi there,
We are running ECC6 and EWM.
We have a situation where we create different orders against different vendor numbers, however the supplying vendor is the same. We only use the different vendor numbers to allow for different pricing, currency, inforecords, etc.
Out vendor would supply the all the parts of all the PO's all packed into the same case.
We process the inbound delivery via a DESADV.DELVRY03 IDoc. When we process the inbound delivery, we automatically pack it as well as defined in the IDoc, but because the items contained in the inbound delivery IDoc is for different PO's and for different vendors, SAP splits the idoc and creates an inbound delivery per vendor, but still using the same HU number for each when doing the packing.
In EWM the system sees these deliveries as duplicates because of the HU number that gets used between the inbound deliveries are the same.
My question is if there is a way in this process to re-pack the separate inbound deliveries into a single HU, or if there is a way to create an inbound delivery that does not reference the PO vendor?
Thanks and regards,
Johan

This is the ABAP forum, but it looks like this question is more for a functional Purchasing expert.
IMHO you might need go back to the drawing board with this and reconsider the design. I'm not a PTP expert, but it usually works as a "reverse SD". In SD you can't combine orders for different customers in one delivery (which kind of makes sense). However, deliveries may be combined into an outbound shipment. And there is a concept of inbound shipment as well.
In SD it's possible to create a delivery without a reference to order, it's very likely possible for inbound. But it's not an ABAP question.

Inbound deliveries with STO

Hi,
I am currently designing an interface with an external WMS and I am thinking to use inbound deliveries but it seems inbound deliveries with stock transport order have important restrictions :
1. inbound deliveries are created with the quantity from the STO and not from the outbound delivery => risk on stock in transit
2. The batch numbers are not copied from the outbound delivery to the inbound delivery (it is done in GR with MIGO if you post from outbound delivery)
3. I haven't (yet) found a way to create automatically an inbound delivery when you post the goods issue from the outbound delivery. (it seems SAP is providing special development for that ?)
Does anyone experienced the use of inbound deliveries with STO and what are your recommendation?
Thanks a lot,
JP

Hi,
We want to create inbound delivery in order to interface with an external WMS (Warehouse Management). We are not using standard SAP "decentralized WMS" interface.
By using inbound deliveries for the interface, we can initiate the GR in SAP and then wait for confirmation from WMS. The WMS can then confirm different quantities if some discrepancies are identified during unloading.
Also, creating inbound deliveries allow planning for receiving (i.e yard management).
=> We do not want to post the GR first in SAP and then send it to the WMS as they can find some differences during unloading
=> We do not want warehouse operators to work in SAP
=> We need a document in the WMS which will trigger task creation for GR for warehouse operators.
=> We want to use same solution for GR for external purchase orders and STO. So if we use inbound deliveries for PO, we want to use it for STO.
Does anyone has experienced to create inbound delivery for STO from outbound delivery with Idoc (i.e ASN with DESADV) or specific development ?
Thanks for your help,
JP

Creating Inbound deliveries

Hi,
We are getting ASN's in a file. And using these we need to create Inbound deliveries in SAP. The transaction thru which the Inbound delivery is created is VL31n. But we need to create the Deliveries using Idocs. Im not sure which Idoc type to use whether DELVRY01 or DELVRY05. Or is there some other way of doing the same. Please let me know on the same.
Thanks
Albina

Hi Albina,
it depends very much which data should be transmitted. So first of all you need to identify a message type which you must define in trx. WE20 as an inbound communication. I recommend DESADV. Now you need to choose a process code:
DELS Delivery advice (DESADV with DELVRY01)
DESA Delivery advice (DESADV with DESADV01)
I recommend DELVRY* (check which one suits you best in trx. WE60). For example: Do you need Handling units in the ASN? So you have to choose an IDoc type which has segments for handling units.
Now you need a sending application (which can be even your system) that feeds the inbound communication setup.
Gunter

Sending out changes made to inbound deliveries

Hello,
We are sending out inbound deliveries as IDocs using Message type DESADV and IDoc type DELVRY03. We are not able to send the changes made to the delivery. Though change pointers are created we do not see any standard process to process the change pointers. Is there any way of sending the changes to the delivery instead of the whole delivery?
Regards
Indu Shekar

Hi,
You mentioned you tested with your own account, did you try to enable the Automatic reply for yourself or enable it for someone else?
If you tried to enable the Automatic reply for User B and it succeeded, I suspect there's something wrong with the permission granted for User A. Please remove Full Access and then re-add it, then check the result.
Since this issue is more about the mailbox permission in my opinion, you can also post the question in Office 365 Community:
http://community.office365.com/en-us/f/default.aspx
Regards,
Melon Chen
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

IDOC for inbound delivery

Hi Gurus,
Pls help me to understand this functionality:
Shipments destined for a Distribution Center will generate ASNu2019s(advance shipping notification) to alert the Distribution Center to the upcoming receipt.
There are two variations of the transaction that will initiate the ASN:
u2022 Receipt of an ASN from a vendor to a Distribution Center will result in the creation of an Inbound Delivery. That Inbound Delivery must be sent to WM via IDOC.
u2022 Shipments from Distribution Center to DC will create an Outbound Delivery from the u201CClose Loadu201D process in Warehouse M. Creation of the Outbound Delivery to another DC is the trigger for the IDOC to WM.
The IDOC to be used could be a variation of the DELVRY03.
My doubts includes:
1. can I use one idoc for both the scenarios?
2. both are outbound idocs or not?
3. Any suggestions how to do this?
Thanks..
SD

>
Shibu David wrote:
> My doubts includes:
> 1. can I use one idoc for both the scenarios?
Yes you can use IDOC DELVRY03 for both scenarios
>
Shibu David wrote:
> 2. both are outbound idocs or not?
No.
ASN sent to DC will be outbound message.
ASN received by DC, which creates Inbound delivery is inbound message.
>
Shibu David wrote:
> 3. Any suggestions how to do this?
As far as I know message type used in SAP for ASN is DESADV.
For inbound ASN use process code DELS and for outbound use DELV

DESADV idoc

Hello,
I have a question regarding DESADV idoc.
DESADV idoc creates and inbound delivery.
We have this problem : we need to create our inbound delivery right after the PO creation.
Do you know if the DESADV idoc can update an existing inbound delivery ?
Thanks,
Regards,
PYR

how can system up date the same inbound delivery in different PO ............as inbound delivery is created with reference to the PO and it gets updated automatically in the PO.
If you want the DESDAV should update the PO right after the creation of the PO then its possible but you need to write a Z program for that because DESDAV means vendor has informed you that he has shipped the goods and the thing is that if the PO is created then at any point of time DEDAV can update the confirmation in PO.
If you want that the moment you save PO system should trigger the DESDAV then i have some question
1. for what quantity system should update the PO thru DESDAV
2. from where will the DEDAV would be getting all the required information

Tracking Number for Inbound Deliveries

We are trying to get ASNs from our suppliers for their shipments. We would like to capture the carrier tracking number (e.g. the Fedex number) from the supplier. I'm using segment E1EDL47-TRACKN in the DELVRY03.DESADV idoc. I'm not able to get the tracking number in this segment to populate into the inbound delivery.
Does anyone have any experience here? Are there some pre-requisites or config that I'm missing? Can anyone point me in the right direction?
Thanks

Thank you for the help...I think we are getting closer with the FM you mentioned. Let me provide some further information on this....we are using the FM IDOC_INPUT_DESADV1 which states the following for E1EDL47 and 48 (still not too sure which we have to use). Not too sure where to go from here to decipher what is currently being used. Any further direction would be helpful
express ship interface - delivery --> t_vlbldlgn
      WHEN 'E1EDL47'.
        PERFORM at_vlbl USING idoc_data s_dl20-vbeln space.
      WHEN 'E1EDL48'.
        PERFORM at_vlbl USING idoc_data s_dl20-vbeln space.
Clicking on at_vlbl LV55KF04
FORM at_vlbl USING    p_edidd           STRUCTURE edidd
                      p_rfbel           LIKE      likp-vbeln
                      p_exidv           LIKE      vekp-exidv.
STATICS: l_xsitd     TYPE xsitd.
STATICS: l_xsitd_ext TYPE xsitd,
           s_spdnr     TYPE spdnr,
           s_vbtyp     TYPE vbtyp,
           s_vbeln     TYPE vbeln.
STATICS: l_xsitd_rc LIKE sy-subrc.
    0.. ok
    4.. not unique -->gn_delivery_create
    8.. not found
DATA: l_xsitd_test       TYPE xsitd.
DATA: l_xsitd_domestic   TYPE xsitd.
DATA: l_xsitd_export     TYPE xsitd.
DATA: l_e1edl47   LIKE e1edl47.
DATA: l_e1edl48   LIKE e1edl48.
DATA: l_e1edl49   LIKE e1edl49.
DATA: l_e1edl50   LIKE e1edl50.
DATA: l_vlbltd    LIKE vlbltd.

Split inbound deliveries are not getting saved .

Hi,
I have implemented an enhancement for splitting the inbound deliveries with multiple storage locations.
But on save it saves only one document and other inbound delivery documents need to be saved manually.Hence those do not get distributed to EWM.
Please let me know if there is any badi or some enhancement that can be done to carry out the saving of other split douments that get created internally .
Thanks,
Richa .

Hi,
It comes from Idoc as well as can be created manually from the transaction VL31N trasaction.
I have placed my code in the include FV50C201.
likp-zukrl+4(4) = xkomdlgn-werks.
likp-zukrl+8(4) = xkomdlgn-lgort.
This helps to create first but rest is kept as it is.Till we go and save it explicitly.And then it gets distributed to EWM system which is our requirement. This should have happened without manually opening the created ones and saving it again .
Thanks,
Richa

When Inbound deliveries split no quantity found to pack

Hi,
My client is using the DELVRY03 Idoc to create inbound deliveries for purchases from vendors. The materials being purchased are batch managed and HU managed. Currently the set up runs without issue provided that there is no delivery split when for items with batch splits. If a delivery split occurs and the items on the second delivery have split batches then the second delivery is incorrectly copied.
Since the current configuration for the copy control does not copy the line item number that is populated on PO, the main item of the second delivery gets a new number but the batch split lines have the PO reference number populated in UECHA. So if the delivery split occurs between the first 2 main items, then the second PO item is copied to the new delivery with item 10 as the line item number the batch sub item lines are created with a reference to line item 20 in UECHA. In this case the delivery gets created. Line 10 is packed. But there are no batch sub items for line 10. Additionally there is no line 20 but when you look at LIPS the batch sub items are all created with the line 20 reference. In short the second delivery is a mess.
I would like to change the copy control so that the line number for PO item 20 copies in to the second delivery as line item 20. Then all my batch sub items would be correctly linked. Unfortunately, when I turn on copy line number in the copy control the IDOC still fails. This time it fails with the message no quantity to be packed.
I looked at OSS notes 380657, 678464, and 682506 which were all applied in our system. In these notes it states that the second delivery can be created when batch splits occur providing that the IDOC is maintained with the correct data. This comment leads me to wonder if there is something being populated incorrectly in the IDOC. For instance, should the IDOC be populated with the actual PO item in POSNR and HIPOS or is there some form of wild card that should be used that lets the system determine the correct line numbers?
Has anyone had an experience similar to this that can provide some insight?
Thanks,
Paul

Steffen,
What I understand from the code:
If your stock is specified exactly (=as much as it is possible) you can pack your materials, if not, you will get error message.
If material is split valuated and not batch managed and valuation type is defined in the delivery then you won't get error message since the stock is specified as much as possible ("ls_lips-bwtar <> space" is TRUE) .
If the valuation type is not given for this material in the delivery, you will get message HUDIALOG102; "ls_lips-bwtar <> space" is FALSE)
If your material is batch managed and batch is specified then the stock is specified as much as possible (with quantity of course; ("ls_lips-charg <> space" is TRUE).
If batch is not sepcified for the same (batch managed) material, then again you will get message HUDIALOG102 (ls_lips-charg <> space is FALSE)
If material is neither batch managed nor subject to split valuation then "ls_lips-xchar <> 'X'" is TRUE and you won't get any message.
If your material is batch managed AND also split valuated, then you always specify the stock via the batch and from the batch valuation type comes. So, if batch is given for the (main) item then "ls_lips-charg <> space" is TRUE --> you won't get error message.
If you use batch split then neither batch nor valuation type are defined for the item, so all of these are false...:
ls_lips-xchar '<' '>' 'X'
ls_lips-charg '<' '>' space
ls_lips-bwtar '<' '>' space
...and system will try to read whether batch is defined for batch split items / whether batch split items exist:
READ TABLE it_lips WITH KEY uecha = ls_lips-posnr
TRANSPORTING NO FIELDS.
and if there are such batch split items then it means the stock is specified and you can pack the goods.
(using serial number management we can specify the stock more exactly but from this point of view serial numbers don't play any role):
Edited by: Csaba Szommer on Aug 23, 2010 9:25 PM

SD:Create Billing Wrt Inbound Deliveries - third party Order

Customer sends his Order forecast, From Interface it comes to SAP System through IDocs SO will be generated,that SO triggers purchase requistion and we have a batch job runs every hour to create purchase orders for Vendor. When the Vendor Sends goods to Customer and the same has notified to the Company, based on that we create Inbound Deliveries(VL31N) and Goods Receipt(MIGO or VL32N PGR) in our SAP System.
We have batch jobs running every hour to create Goods Receipt for inbound deliveries and Billing due(RV60SBAT) list to generate Billing documents.This Billing is created based on the sales order quantity(Since it is Order Related Billing).Now the Customer wants billing based on the delivery quantity they received from vendor.Here we are not doing any Outbound Delivery.
We used one Data Transfer Routine from Order to Billing in item category TAS at data VBRK/VBRP level(We copied the standard routine 003 and done modifications to get the inbound delivery no) This routine navigates from the sales document table(vbep) to the Purchase Requisition table(eban) to the Purchase Order history table (ekbe) and to the Material Document no to obtain Inbound Delivey Number
We are successful to some extent in creation of billing document.but the problem is when there are 3 inbound deliveries for one purchase order, it is creating only one invoice for 1 of 3 inbound deliveries.but we need 3 different invoices for 3 inbound deliveries.
For example
Previous scenario: SO quantity is 100. Delivey quantity is say 20,30,50. Billing Quantity is 100
Present scenario : SO quantity is 100. Delivey quantity is say 20,30,50. Billing Quantity is 20,30,50
Customer wants billing for the quantitiies 20,30,50 not for 100

Pradeep,
Whats is your billing qty based on Order- GR qty? or Order - Inbound delv qty. How did you get this?.
The problem lies because it is an order related billing.
Try this make it a Delv related billing w/o any movement type.
The moment you create an inbound delivery and O/P should be send which in turn will create a delivery document and PGI.(you can use this O/p type to do the dirty work)
And after this complex process life becomes simple.
Ravi

How to Close PO relate Inbound Deliveries w/o posting goods issue?

Hello,
Recently someone helped me in trying to find the status in the ABAP Dictionary of an Inbound Delivery. So thanks!
I have another question, is there a way to close the Inbound Delivery without posting to goods issue or while its still open in the document flow.
I want to ask because the business requirment needs to clsoe these Inbound Delivery Documents for archiving purposes and in SAP they are never closed since the Material Document is created (via MB01) w/o SAP referncing it to the Delivery Document.
I was thinking maybe I can tag a field somewhere or use a BAPI/FM to do this.
I hope to hear from you soon.
Thank you and good day.

You might want to define what exactly do you mean by "close".
As far as I understand, if there has been no goods movement ("goods issue" is for the outbound deliveries, inbound deliveries create "goods receipt", just FYI) or TOs created against a delivery, it can be simply permanently deleted from the database. The corresponding purchase order would then have to be also deleted or somehow rejected (not sure if there is something similar to the SD "rejection reason" in PTP). As an alternative, the PO quantity could probably be changed to 0.
Also it might be an option to change both the received and delivery quantity to 0 and then do "post goods receipt". This should not create any goods movement, but will most likely set the delivery status to 'complete".
Unfortunately, I don't have a system with the deliveries right now to verify these theories...

Automatic creation of Inbound deliveries per HU

Hi Guys
I am looking for any information on how to automatically create inbound deliveries based on Handling units.
The process is
Create PO
Receive ASN with packing details (e.g. one box = i HU)
Auto creation of one Inbound delivery per HU
Any assistance would be appreciated.
Cheers

Steve
I don't know how you figured out it was me.
The answer you have given believe it or not was what I was expecting as I thought it would need development.
As for the value of this the logistics service provider believe that they can control the out away better with one ID per HU per box etc and also we are putting away in WM first and then 'post goods receipt' to update IM. We have a bespoke transaction where they scan the barcodes from the putaway tags in to a copy of LT11 and they can scan up to 100 lines and then save. When the save is activated the transaction checks first how many Transfer order/Lines are on each inbound and then are all of them confirmed when eventually the answer is Yes the system will then go to the Inbound delivery and post goods receipt automatically.
This is so that the Sales office does not see the stock until it is located as backorder processing runs regularly and we do not want orders and deliveries appearing whilst the putaway process is being carried out, However they do want the stock available ASAP. Therefore it is better for them to have the HU-ID as one to one so that in theory materials become available quicker as if one ID had say 100 materials on it none of them would be available until the last one was put away and confirmed.
I hope this explains it and thanks for your assistance.

DESADV Idoc + duplicated Inbound deliveries

Similar Messages

Maybe you are looking for