2077553 SAP OSS Note - Obsolete version Implemented notes - Automatic adjustment fo

SAP OSS Note 2077553 version 0002 contains details of a know issue related to Obsolete version Implemented notes - Automatic adjustment fo . 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 2077553 Details:

When does this problem occur

In SPAU when we have obsolete notes and these notes have manual

activities, then after reset of the note, manual activities are not ad

justed. Hence, after reset in SPAU, note status is green i.e. it is

adjusted properly but in SNOTE the status of the note is shown as

"Obsolete version Implemented" which is incorrect. After this we need to

click on "De-implement" button in SNOTE to confirm the cancel

lation of manual activity. This is an extra step which needs to be


With this note correction, obsolete notes containing manual activities

will be adjusted properly including the manual activities as we


Status of the note in SPAU is also calculated incorrectly in SPAU where
in some notes are shown with Yellow traffic light instead of G

rey traffic lights. This is also fixed with this note.

Cause of the problem and Pre-requisites

This is due to program error.

Solution instructions

Implement the corrections of this note. After this manual activities

will also be adjusted automatically when the note is reset in SPA


Re-start the SPAU transaction after implementing this note. In order to
correct the status of notes, execute with the "Corrections in

SAP Note". Then click on Goto menu and click on "Determine Adjustment

Modes" and execute again. This will calculate the status again c

orrectly after the correction of this note is implemented.

Description of problem


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 2077553 has been released as well as see if the note is valid for your current SAP system landscape.

Check if SAP OSS note 2077553 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 2077553 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 2077553 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)