33924 SAP OSS Note - Reversing usage decisions

SAP OSS Note 33924 version 0006 contains details of a know issue related to Reversing usage decisions . This includes any associated symptoms and instructions on how to fix it, see below for full details. Also check out the comments section to view/add related contributions, questions or screen shots, based on real life experience of this oss note and problem.

...For more information about the SAP support system known as OSS please check out the SAP OSS NOTES SECTION, whih includes how to download & implement them onto your SAP system using transaction code SNOTE.

Note 33924 Details:

When does this problem occur

You cannot reverse a usage decision which has already been made.

Cause of the problem and Pre-requisites

The usage decision triggers follow-up functions that you cannot reverse

or only with great difficulty:

stock postings

Also refer to Note 175842 here.
cost postings
of the quality level
of the QM info systems

Solution instructions

You cannot reserve usage decisions in the standard system. As a result,

you should make usage decisions carefully!

As of Release 3.0E you can, at your own risk, implement the 'Cancel
usage decision' function via User Exit QEVA0008.

Additional note for long-term characteristics:

If long-term characteristics are defined as an optional characteristic,
you must set them to 'in process' before the usage decision is

 made. As a consequence, the inspection lot receives the status

'long-term inspection'.

If long-term characteristics are defined as required characteristics

they do not have to be explicitly set to 'in process'.

Description of problem

UD, inspection lot, reversal, reverse

Solution instructions

Please import the corrections attached to this OSS note into your SAP system using SNOTE.

You can also view the full details of this OSS note and download it to your SAP system ready for implementation using transaction code SNOTE. Once it has been downloaded you can read the full details, check out any installation instructions including manual changes and see if there are any pre-requisites.

You can also check if a new version of note 33924 has been released as well as see if the note is valid for your current SAP system landscape.

Check if SAP OSS note 33924 has already been downloaded and is valid

To check if this note has already been download, what status it has and if it is valid for your system first execute t-code SNOTE and click on the SAP Note Browser icon
Icon used to execute SAP Note Browser report within SNOTE

From here you can just enter the note number 33924 and press execute. If the note already exists it's details will be displayed. See here for full step by step instructions on how to check if an SAP note has been downloaded and is valid for your system.

If note 33924 does not exist on your system you will receive the message "Unable to find SAP Note that meets specified criteria"
Icon used to execute SAP Note Browser report within SNOTE

If this is the case you will need to download the note to you SAP system also using transaction SNOTE. For further details see Download note using SNOTE. Even if it does exist you may still want to check if you have downloaded the latest version of the note.

Alternatively you can find full details of this note on the SAP service market place(SNumber / Service market place login will be required)