Inbound Delivery: Output

Hi Gurus,
I am encountering problems with the initial display of Inbound delivery (VL33). The output does not appear in the header portion.
Here's the scenario:
1. Inbound delivery created using the PO with output details (VL31).
2. But when I initially display the inbound delivery (VL33), there is no output (Path: Header Menu > Output)
3. When I change the inbound delivery (VL32) and go to Header > Output, there are values.
Everything is working fine on VL31N.
Can someone shed some light on this please. Points will be rewarded if found helpful.
Thanks in advance

Hi,
I think the situation is the following:
You create the document with VL31 -> before saving the outputs are visible -> when you save -> function module MESSAGING is run -> here the output records get deleted from XNAST (necessary condition field are empty, requirements ?)
-> after saving the document check if there are really no entries in table NAST -> then you enter TA VL32 -> now the condition fields necessary to find the output condtion records are filled (and remain filled during saving) -> outputs are saved -> entries in NAST exist -> outputs can displayed with TA VL33.
Conclusion: set a breakpoint in FM MESSAGING (during VL31 saving) in order to determine which and why some fields that are necessary to find the output condition record are not filled or still not available duing VL31 saving process.
Regards,
Andreas

Similar Messages

  • Inbound Delivery: Output Missing

    Hi Gurus,
    I am encountering problems with the initial display of Inbound delivery (VL33). The output does not appear in the header portion.
    Here's the scenario:
    1. Inbound delivery created using the PO with output details (VL31).
    2. But when I initially display the inbound delivery (VL33), there is no output (Path: Header Menu > Output)
    3. When I change the inbound delivery (VL32) and go to Header > Output, there are values.
    Everything is working fine on VL31N.
    Can someone shed some light on this please. Points will be rewarded if found helpful.
    Thanks in advance

    Hi,
    I think the situation is the following:
    You create the document with VL31 -> before saving the outputs are visible -> when you save -> function module MESSAGING is run -> here the output records get deleted from XNAST (necessary condition field are empty, requirements ?)
    -> after saving the document check if there are really no entries in table NAST -> then you enter TA VL32 -> now the condition fields necessary to find the output condtion records are filled (and remain filled during saving) -> outputs are saved -> entries in NAST exist -> outputs can displayed with TA VL33.
    Conclusion: set a breakpoint in FM MESSAGING (during VL31 saving) in order to determine which and why some fields that are necessary to find the output condition record are not filled or still not available duing VL31 saving process.
    Regards,
    Andreas

  • External mail using output types in inbound delivery.

    Hi Experts,
    I want to send an external mail to vendor after creating inbound delivery.  for this i want to use only output types in messages.  Can somebody help me step-by-step how to configure the output type to send mail to external ID.
    Thanks in advance!
    Machindra Jogdand

    we can have print out from delivery from header output & item output.
    ok now for output ypu need to go to T.code: NACE, Take V2 -shipping and click on output types tab at the top most u will get a output type standard "MAIL"
    For the MAIL output type u assign a access sequence of your own.
    Maintain condition records in VV2.
    Select the output type in delivery
    GO to Vl02n enter the delivery no: take extras from the menu and take delivery output header /item enter the output type MAIL.

  • Trigger output on Inbound Delivery Type

    Hello,
    I'd like to know if it's possible to trigger output on Inbound Delivery Item in SAP ERP. Reason I ask is that we want to trigger a label printout for every delivery item during goods receipt of the inbound delivery.
    I know I can trigger output on Inbound Delivery Header, but not sure how to get a printout per delivery item.
    Can anyone let me know if it's possible, and if so, how to set this up?
    Regards,
    Oliver

    Hi,
    I am not experienced in printing, and at first glance this does look difficult...
    Because in customizing you have two separate paths...
    The path given above from Warren, and then it splits:
    - Maintain Output Determination for Outbound Deliveries
      - Assign Output Determination Procedure
    - Maintain Output Determination for Inbound Deliveries
      - Assign Output Determination Procedure
    Now the difference in these two paths is that:
    - if you select the first one, you get a pop-up giving you a choice to "Assign Deliveries (header)" and "Assign delivery items",
    - if you select the second one, there is no further selection, you only see delivery types, and this is also filtered, only inbound deliviery types are shown.
    So it seems not possible.
    BUT: if you select the "Assign delivery item" option in the first path, you see ALL item types; also for inbound. So test it there, hope it works. (I suppose now that you know how to print, have all the determination, etc - yes, you wrote that you know it for outbound).
    Brgds
    Juergen

  • Requirement output inbound delivery

    We have developed a requirement on a output for inbound delivery, which only should trigger the output when the inbound delivery has overall status completed (C). That means that all transfer orders for the inbound delivery is confirmed.
    The problem we see is that the output is not triggered automatically when the last transfer order is confirmed and overall status for inbound delivery is changed to C.
    The output is triggered when we manually go into transaction VL32N and save.
    Anyone have any suggestion of how to trigger this output automatically?
    Best regards,
    Terje

    Of course I have set up the condition record in transaction MN24.
    The problem is that I have to go into the inbound delivery to get the ouput triggered.
    BR
    Terje

  • Create an output for Inbound Delivery

    Hello,
    How do I generate an output (print output or IDoc) when an Inbound Delivery is created in my ECC system using Output Control?
    I need an output to be generated when Inbound Delivery is created/ changed/ deleted.
    What are the standard configurations available to achieve this?
    Thanks and Regards,
    Ashwin Bhat

    Hi,
    Go thru these links:
    [Maintain Output Determination for Inbound Deliveries|http://help.sap.com/saphelp_470/helpdata/en/6f/c5a3f28d7711d5b2c80050dadf6bf7/content.htm]
    [Assigning Output Determination Procedures|http://help.sap.com/saphelp_crm60/helpdata/en/9d/af3e429bc2aa04e10000000a1550b0/content.htm]
    Hope this helps!
    Reetesh

  • Output type not trigerring Automatically for inbound delivery

    Hi all
    We have created a custom output type for Delivery idoc processing ZPOD copy of OPOD and maintained all the settings also condition record for the same has been maintained.
    But when we are creating inbound delivery the output type ZPOD is not coming automatically.
    In the Delivery document and in the Output screen i have checked  Determine analysis for output(VL32N -> Enter IBD No -> Select menu option Extras -> Delivery output -> Header
    Go to menu option GoTo -> Determin.Analysis.)
    It is showing me ->Message 502-Output ignored (requirement 017 not fulfilled)
    Can u please throw some light so that in output message determination the Output type should come automatically for Proof of delivery
    Thanks and regards
    shailesh

    Um... I think the message is pretty clear on this - the reason is "requirement 017 not fulfilled".
    Requirements for output control may be found in VOFM transaction, under Requirements -> Output control. 017 is the standard one, the description says 'POD on goods issue'. According to the comments, the output is not issued if  "POD status is initial" or "No output, if no goods receipt".
    Either correct the document or remove this requirement in output configuration, if it's not applicable.

  • Item Level Details in Output Requirements Control during Inbound Delivery

    Hello Experts,
    I have a requirement to access item level details of an inbound delivery at the time of processing the output requirement. The output requirement is defined for application E1 and has a related communication structure KOMKBE1. However, this structure does not have item details (Material, Plant, Batch is what is needed) . Is there another global communication structure that stores this data when the output requirement is called? If not, is there any other way to access that data during runtime?
    It is not possible to fetch it from the database tables because the delivery creation process is not yet complete and thus it is not stored in the database, as the output requirement is called when the SAVE button is clicked in VL31N.
    Thanks,
    - Neeraj
    EDIT: Found a solution: Using field symbols, I picked up the value of the needed details from the structures available in the calling program SAPMV50A. In this case, I did not use KOMKBE1 at all.
    Edited by: NeerajAngal on Oct 6, 2010 12:28 PM

    Hi
    As per my understanding you can try se63 option ..

  • Smartform for output type CHKL (count list ) as Inbound Delivery(E1)

    At this moment, I know the Sapscript form RT_CHECK_LIST & program RTCHECKL for count list (output type CHKL) as inbound delivery (E1), but I need  the PROGRAM and SMARTFORM for this output?!
    Thanks in advanced

    I don't think we have a similar print program and smartform available, if you want to use it in Smartfrom.. copy SAPscript and migrate to smartform using SF_migrate and copy the print program of SAPscript and make necessary changes.
    Regards,
    SaiRam

  • Triggering output upon GR in inbound delivery

    Hi all,
    I want to trigger HU label as soon as i do GR on inbound delivery and on (ii)GI on outbound delivery.
    For this i set condition records in VV61 and then i assign requirement 1(Delivery GI posted) in SPRO->LOGISTICS GENERAL->HANDLING UNIT MANAGEMENT->OUTPUT->MAINTAIN OUTPUT DETERMINATION PROCEDURE->assign requirement 1
    HU label output is triggering automatically upon GI in outbound delivery (VL02N)...but upon GR in inbound delivery(VL32N) HU label output is not triggering
    as soon as i remove assignment of requirement 1, HU output is triggering on inbound delivery creation...means my other settings are fine..only thing is that i want output upon GR in inbound delivery...which is not happening..
    i tried will all other combination like changing the application from V2 to E1 for requirment 1, keeping application blank for requirment 1. i also tried requirement 35
    what can be the problem..
    Regards
    Rahul

    Check the below config also..
    SPRO - Logistics Execution - Shipping - Basic Shipping Functions - Output Control - Maintain Output Determination for Inbound Deliveries.
    Also not sure, if we have a requirement for goods receipt. But certainly requirement 1 will not work, as that is for PGI of outbound.
    Create a new requirement for Application E1, let's say 901 and put the code like below and attach to the output condition.
    FORM KOBED_901.
       if komkbe1-wbstk <> 'C'.
        sy-subrc = 4.
        exit.
      endif.
    ENDFORM.

  • PO qty and Value with Inbound Delivery qty

    Dear all
    i have a report requirement, client wants to have a report on the basis of Inbound delivery qty. for eg.
    If Po qty is 100 @ $10.00 each Total Po value = $1000
    if he makes a inbound delivery of 20 qty Report should display outstanding delivery qty as 80 and with reduced value .of $800
    Pl tell me how to get these details.
    Regards
    Manoj

    Hi Manoj,
    I think you should should copy ME2M and change the output.
    Sanjeev

  • Delivery Date in inbound delivery doc not accurate

    Dear all,
    I have a question with regards to the wrong delivery date appear in our inbound delivery.
    Our inbound delivery is created via a message output in the outbound delivery of a standard SAP cross company stock transport order. The delivery date in the inbound delivery is not correct from a business point of view.
    +The correct delivery date in the inbound delivery document should be [the Actual GI date field in the outbound delivery] + [transport time (i.e. route field) in the outbound delivery].+
    Either way (i.e. the Actual GI date field is later/earlier than the planned GI in the outbound delivery), the delivery date in the inbound delivery is also wrong.
    Do you have any idea? We have tried to change the inbound delivery type EL by setting a flag (i.e. X) in the rescheduling (TVLK-NEUTE), and it still doesnu2019t work.
    Please help.
    Thanks.
    Tuff

    implements SAP Note 1316614

  • Delivery Date in Inbound delivery document not correct

    Dear all,
    I have a question with regards to the wrong delivery date appear in our inbound delivery.
    Our inbound delivery is created via EDI output in the outbound delivery of a standard SAP cross company stock transport order. The delivery date in the inbound delivery is not correct from a business point of view.
    +The correct delivery date in the inbound delivery document should be [the Actual GI date field in the outbound delivery] + [transport time (i.e. route field) in the outbound delivery].+
    Either way (i.e. the Actual GI date field is later/earlier than the planned GI in the outbound delivery), the delivery date in the inbound delivery is also wrong.
    Do you have any idea?  We have tried to change the inbound delivery type EL by setting a flag (i.e. X) in the rescheduling (TVLK-NEUTE), and it still doesnu2019t work.
    Please help.
    Thanks.
    Tuff

    Does anyone know this problem?
    appreciate some feedback.

  • New Condition TAble for Inbound Delivery

    Hello
    i want to maintain a new Condition table for the Inbound delivery picking with the combination of _Delivery type/Plant
    so that the Inbound created for the particular plant alone uses the particular output type.
    Where in IMG can i configure the new Condition table for this combination for the Inbound delivery ?

    Hi,
    Go to SPRO > Logistics Execution > Shipping > Basic Shipping Functions > Output Control > Output Determination > Maintain Output Determination for Inbound Deliveries > Here perform following;
    - Define Condition Table for Inbound Delivery
    - Define Output Types for Inbound Delivery
    - Define Access Sequence for Inbound Delivery
    - Maintain Output Determination Procedure
    - Assign Output Determination Procedures

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

Maybe you are looking for