Skip to Content
author's profile photo Former Member
Former Member

Problem with output of Outbound Delivery

Hello All,

I have a problem: when deliveries are posted via VL02N, the output determination works correctly - YPDF position is created in NAST

and possible to use. Unfortunately, when goods issue is posted via VT02N, outputs determination is different, and no YPDF output is

determined. It is possible to create it manually (via Extras - Delivery Output - Header) but it not acceptable for every document.

What can possibly be wrong and where shoud I check to make this VT02N path correct?

Thanks in advance

Best Regards,

Maciej

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Posted on Aug 24, 2015 at 11:39 AM

    1. Check the requirement for the output type in the output procedure and the dispatch time in the condition record. When the output should be determined (is there a check for goods movement status) and how it should be processed (immediately, application own transaction etc.)?

    2. If you process the output at shipment completion, please check what is set in RV56ABST and the corresponding variant for your shipment type - is the output type specified in the variant, is 'Carry out goods issue posting during save' specified. To process delivery outputs via VT02N, they should be already determined in the delivery in the previous steps (before goods movement is posted).

    3. What do you see in the determination analysis for the output in the delivery after processing it via VT02N?

    Add a comment
    10|10000 characters needed characters exceeded

    • If YPDF is not some kind of valuated delivery note (for valuated delivery notes you need to generate a proforma to fetch pricing data), then there are basically two ways to process the delivery outputs in case you have shipment processing:

      • The first one is by using activity profiles for the shipment, which fetch the outputs and process them.
      • The second one is without using activity profile, but relying only on the output determination and processing in shipping. For the second option you need a way to tell the system to process the output. Since you do not use activity profile, you can set the condition record to immediate and after it is determined (posting goods issue is a change in the delivery), the output is determined and with processing 4 it should go to green.

      In case you need to print valuated delivery notes, the situation is a bit different - there you rely on a collective shipment output, to which you assign the delivery outputs. You do not set the delivery outputs in the activity profiles, just the shipment output. In this case you have to set the processing time to 3, otherwise the main program, that is used for DSDP will result in error.

      In case you have a user exit for output determination - e.g. redirecting to a different printer, then setting the delivery output to immediate processing might not work as well.

      I would suggest that you try the option with immediate delivery output and with requirement 1 (without activity profile usage) and see whether it works for your scenario.

      In some cases the root cause for output determination and processing can be incorrectly developed print requirement, but since you stated that you use a SAP standard one, I believe that this is not the case.

      If you decide to use the source tcode as a criteria in a new print requirement - you may need to evaluate a number of possible ways to print/reprint a delivery output (VL03n, VL02N, VT70, VL71 are the first that come to mind). It is not impossible, but could be a challenging task.

      Edit:

      You might want to check the explanation and the possible solutions in this SAP note - 509475 - Delivery output: Behavior during GI posting via shipment .

  • Posted on Aug 24, 2015 at 03:04 PM

    Moved from SAP ERP Sales and Distribution (SAP SD) to Output Management

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.