Skip to Content

Output type NEU / NEW ends in errors by external send - no processing log

Dear experts,

by creating a purchase order using ME21N ouotput type NEU / NEW will be determined using condition records.

Condition record is maintained as external send (5) with communication strategy and send immediately (4).

Output type will be determined but ends up in error after saving. There is no processing log. So no hint for the error.

After saving I enter again the PO and repeat the message. Now no error occurs.

I checked this Link.

No issue in SM13 and conncetion for SMTP established (SCOT).

Does anybody have an idea what the issue could be?

Many thanks in advance.

Best regards


Add comment
10|10000 characters needed characters exceeded

  • You are saying it "ends up in error after saving".

    What is this error? How is it shown to you?

  • Hello Jürgen,

    this is exactly the problem. Output type appears with red traffic light (error) and no information within processing log.

    There is also not error message coming up.

    I know that this is basically nothing to start from for analysis.

    My first thought was the SMTP note within SCOT is inactive, but after reprocessing it works without any issue.

    Seems to be problematic for only one vendor.

    First of all. There are no user exits / modifications within output determination etc.

    print program is Z* program.

    Is there any frequent mistake I can check or any frequent root cause?

    Many thanks in advance.

    Best regards


  • Get RSS Feed

3 Answers

  • Best Answer
    Feb 06, 2018 at 09:55 AM

    SAP recommends in several OSS notes to avoid 4 immediate processing for external sending.

    If you go into your purchase order after your created it then you are actually in a change process, which makes some difference.

    But overall you can only reset your customizing to SAP standard form and routines and see if the problem still occurs. If not then you can be sure it is your Z-development and you need to compare it with the standard to see what you missed.

    Start from this OSS note: 111062 - Printing problems in Materials Management

    Add comment
    10|10000 characters needed characters exceeded

  • Feb 06, 2018 at 11:25 AM

    Hi Jürgen,

    thanks for the hint. I was not aware of the issue with immediate processing.

    Planning a job to send mails is a very good workaround.

    Thanks Patrick

    Add comment
    10|10000 characters needed characters exceeded

  • Feb 13, 2018 at 08:31 AM

    Dear Experts,

    after deep analysis we found some kind of bug inside SAP Standard.

    Problem occurs as soon as PR will be transferred into PO and delivery address will be changed in PO.

    Root cause is that the update process is starting in parallel to the print program. This is causing the error.

    As the problem is somewhere within SAP Standard we have following solutions / workarounds:

    1. change condition types tom Dispatch time 4 into 1 or 3 and plan an output job using even report RSNAST00 or TCode ME9F

    2. Enhance print program with waiting time at the beginning.

    Best regards


    Add comment
    10|10000 characters needed characters exceeded