Skip to Content
avatar image
Former Member

How to prevent to reuse deleted sales order

Hi Experts

I need to prevent re -use deleted sales order. Currently, user set Zero to quantity field when sales order is unnecessary. This means deleted by logically. How can I to prevent to re-use such deleted sales order?

In standard, We know that sap request to use Rejection fields when when sales order is unnecessary. But, this setting was not fit user request. In detail, VA05 and MCTE report displayed deleted sales order which set rejection.

Thanks in advance.

Add comment
10|10000 characters needed characters exceeded

  • I'm very much confused by this question as well. Kindly use the standard SAP terminology. "Deleted" means the order was physically deleted from the database. (There is Delete operation in the menu.) You seem to be confusing this with a rejection process.

    It is also not clear why do you have to retain such items to begin with and why can't you just add a filter in the reports to do not show rejected items.

  • Get RSS Feed

1 Answer

  • Apr 25, 2017 at 06:47 AM

    Could you, please, explain why you cannot use rejection reason, so that the forum members can suggest a workaround?

    Also, what is the expectation if there are two order items, the user sets the quantity for item 2 to zero and for item 1 the quantity is reduced from 5 to 4 - is it allowed later to set again the quantity of item 2 to a different value?

    The first thing, which comes to mind, is user statuses, but without knowing the reason behind this strange requirement, it is hard to suggest a suitable alternative.

    Also, what have VA05 and MCTE got to do with the rejection reason (which you are not using) and the whole business process? I am confused.

    Add comment
    10|10000 characters needed characters exceeded

    • +1 to Kıvanç for the SAP note reference.

      If you are determined to keep the current ways of working (despite that it causes more problems, than it solves), still, I would prefer to keep a workaround for the support team and explore user statuses functionality with underlying authorizations. Sometimes end users might set the wrong item to zero (this to-be process looks very unforgiving to trivial mistakes), with user statuses you could be able even to transfer the responsibility of resolving such errors to 1-2 power users per sales organization.