Skip to Content

Do not execute function issue

Jan 09 at 11:42 PM


avatar image

The user Closed the wrong order with Do not execute function, but the order still has a plan cost and that is messing up the hierarchical project reporting. Now the order is "cut in stone" with no changes allowed.

How the plan cost can be cleaned up from such PM order?

Thank you,


10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Peter Atkin Jan 10 at 08:23 AM
Show 2 Share
10 |10000 characters needed characters left characters exceeded

Hi Peter,

The note is basically discussing how to prevent the function execution and/or implement additional validations.

In my case it is almost useless as we need to clean up plan cost from such PM order to avoid wrong figures in reporting.

At the moment I am looking for corrective procedure and not for future preventive measures... :)

Thank you,




  1. The system status NCMP set by function 'do not execute' cannot be reversed. It is advised to archive the order if necessary and replace with a new order.
  2. Exit IWO10026 can be used to implement custom validation to prevent this function being executed.
  • In the exit you can use the data from import data structure CAUFVD_IMP to check if function should be allowed.
  • To prevent the status being activated, set and return parameter NO_DO_NOT_EXECUTE.


This note explains that NCMP is not reversible, and also states how you could stop it in the future.

The only way you can get around this is with some ABAP help, by forcing the system-statuses - which is not recommended.