Creation of Inbound Deliveries via DESADV using EAN's

Hi all,
I've tried to get an answer/feedback on this in the SCM Logistics Execution, but didn't get a bite, so I'm trying this forum as the type of question seems more aligned to the content in it...
I am trying to simulate an inbound delivery creation process using DELVRY06/DESADV for a PO. The issue I have is that the EDI provider will not be sending the material number in either the E1EDL24 (delivery line item) or E1EDL44 (HU item) segments - only the barcode (which causes a second issue).
E1EDL24 has a field EAN11 which I have populated with the relevant EAN/UPC code and removed the MATNR and KDMAT values for the R/3 material. However I cannot get the inbound delivery to create without populating the material number.
Also for the HU, we have the scenario of having multiple materials (E1EDL44) packed into a HU (E1EDL37). The DL44 segment only has material fields and no corresponding EAN field to identify the materials to be packed.
If anyone has experience with this issue then I would love to hear what I can do. If there is something that is 'out of the box' i.e. SAP standard then that will be first prize for sure, but if I have to, then an enhancement may be required - hopefully not.
Kind regards and many thanks,
Paul...

Hi Alex - I was hoping you wouldn't say that! It just seems a bit odd that an EAN being a universal product identifier isn't utilised within the inbound delivery process as they are supposed to unique.
Thanks for the input. Much appreciated...

Similar Messages

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

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

  • Automatic TO Creation for Inbound Deliveries

    I would like to have TO created automatically for Inbound delivery for PO.
    1)  I have set the Automatic TO = A in Mvmt Type 101 for my warehouse in transaction OMKZ. 
    2)  I have set Immediate TO Creation and Mail Control = A for Mvmt Type 101, Mvmt Indicator =B, Mvmt Type 101, TR Create =X for my warehouse in transaction OMKX
    3)  I have assigned Routine #32 to Application E1 in transaction VOFM
    4)  I have created output conditon WMTA for delivery type EL with Medium =8 and Date/Time =4.
    Tranfer order is not created when the delivery is created via transaction VL34.  The output determination analysis indicates that WMTA was ignored because requirement 032 not fulfilled.  What am I missing?
    Thank you.

    Hi Julie Simonds
    I believe you are working with Inbound delivery with Item catagory as ELN.
    Please check if Relevant for putaway is checked.
    Path for your refernce :
    SPRO > LE > Shipping > Deliveries > Define Item catagory for deliveries.
    Thanks,
    Mahesh

  • Urgent !!!!! Updating Inbound deliveries via Idoc type DELVRY05

    Hi,
      Is there a way to update an existing inbound delivery through the Idoc type DELVRY05. I'm able to create an Inbound delivery using this Idoc type. But im not able to update the same. There is a field VBELN, in segment E1EDL20. But whenever i pass the Inbound delivery in this field, it takes this field as a reference and creates a new Inbound delivery. And then the referenced Delivery is updated in the field LIFEX in table LIKP.
    Thanks for your help. This is a little urgent.
    Thanks
    Albina

    Hi Ganesh,
    Sorry, I was referring to BAdI /SAPSLL/ECC_INBOUND, but got the name slightly wrong.  As you say, the BAdI Method doesn't have a suitable parameter for making the updates - you would have to make the updates yourself in some asynchronous way (and I don't recommend it).
    Yes, I understood your technical requirement, but you have not explained WHY you want to do it.  I wonder which Customs Authority you are dealing with?  I don't know of any that return additional document codes.  Normally the inbound iDoc is used to convey error messages or status changes from the authority to the GTS Declaration.  Here, it sounds like you are intending to use it for quite a different purpose.
    Probably you should create your own Message Type, Process Code and Function Module to handle the updates.  You could copy much of the code from the standard /SAPSLL/IDOC_INPUT_CCECUS, but it would be a substantial development.
    Regards,
    Dave

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

  • 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

  • Convert PO's into Inbound Deliveries using a batch job?

    HI Experst,
    Can we create inbound deliveries for PO's through scheduled batch jobs? Or some custom development will be needed?
    Any responce is greatly appreciated.
    Thanks,
    KHAN

    >
    Dominik Modrzejewski wrote:
    > Check transaction VL34.
    > Maintain your variant there and setup a job for this program RM06EANL with your variant.
    >
    > Regards,
    > Dominik Modrzejewski
    Wouldn't VL34 require manual entry for the document numbers to process?
    I know VL10G variant run via batch job works perfectly for outbound deliveries so I assume VL10G would be the transaction to create variant/batch job even for inbound deliveries.

  • Delivery date issue in the ASn inbound process via IDOC

    HI
    we want to start with ASN and we ´re already receiving IDOC´s
    DESADV Delvry03
    we are using Fm /SPE/IDOC_INPUT_DESADV1 and we have tried IDOC_INPUT_DESADV1 but teh reesult was the same.
    The segment E1EDT13 Qualifier 007/009/006  exist and we are able to create a inbound delivery. The problem we have is that we are not able to calculate the delivery date in the inbound delivery.
    The idea was that the vendors sends us the GI date (Qualifier 007) and our SAP calculates based on the plannend delivery time in the SA/PO the expected GR date 8what we see in MD04). But at the moment we only the creation date as delivery date.
    what do we miss?
    thanks for the help
    regards
    Alex

    Hi,
    Firstly, for DESADV processing delivery date field (LFDAT) is taken from qualifier '007' while goods issue is from '006'.
    As far as I understood you would like to get delivery date based on data from given delivery schedules. But note that inbound delivery items are not related specifically to delivery schedules. Instead, those are referenced to purchasing document items only. Therefore it is not exactly specified what delivery date should be selected for which inbound delivery.
    Alternative could be to perform scheduling for inbound deliveries based on route transit times etc.But in standard inbound delivery types are not available for SD scheduling and thus it is not directly available.
    If you need to get such functionality, you would need to use one of the DESADV processing u-exits available and include your own logic for lfdat calculations.
    Regards,
    Dominik Modrzejewski

  • 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

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

    Hey 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

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

  • Creation of Inbound delivery without Order acknowledgment

    Hi,
    We have a scenario where we raise Purchase order to Vendor. The Vendor sent the confirmation (Delivery date, qty, etc) via IDOC. This updates the Order acknowledgement and also the confirmation information in PO.
    When the Vendo creates a Outbound delivery in this system, it sends another IDOC which creates a Inbound delivery automatically in my system.
    In some cases the confirmation IDoc fails. We want that in such case the Inbound delivery should be created unless we get the correct confirmation.
    In other words, system should not create Inbound delivery if order acknowledgement fails.
    Is this possible in standard SAP

    Hi,
    What is the reason for not generating inbound delivery without a confirmation? Wouldn't the business on receiving plant be interested in getting inbound delivery asap, so that they can plan their operations based on the incoming goods details?
    I don't think you can control that simply from confirmation control key. There is the 'expected sequence' but it does not stop the process if you proceed without confirmation.
    Note that there are lots of other complications if there was such a requirement. What if first item is fully confirmed, but another is not. Would you like to create inbound delivery only for the confirmed item?
    And what for Scheduling Agreements? The confirmations/inbound deliveries are at item level only (and not at delivery schedule line). So you don't fully control what quantities were confirmed and which are still 'open' for confirmation.
    If you want to apply such a logic, then most probably custom solution at inb. delivery creation would be required.
    Regards,
    Dominik Modrzejewski

  • 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

Maybe you are looking for