Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

How to test/Verify SAP Notes

Former Member
0 Kudos

Hi Gurus,

Appreciate if you could share on how to test/verify the following sap notes:-

1) 1330776

2) 1143177

3) 1271688

4) 1302928

5) 1329090

Thank you,

Green Choc

5 REPLIES 5

Former Member
0 Kudos

now, that's not a good way to proceed.

first: don't implement notes, if you don't have an issue. notes are not maintenance, but corrections for errors. so to implement a note without an issue will always present you with exactly the questions you are asking a forum now (which is not a way to go about your job).

second: look closely at the first note you want us to come up with a test-scenario for. how are we supposed to know the setup of your system - let's start with your release.

third: do you actually expect us to come up with follow-up notes of the ones you wrote down here and develop a test-scenario for them, too? for example: 1329090 has a predecessor, 888889. how are we to know whether you already implemented this or not? how are we to suggest how to test that one?

if you insist implementing notes without having the issue that the note is about, setup a sandbox system, apply them one by one, and between applying them, test all your scenarios that might be affected by the note. only you can judge, which scenarios those are - we cannot help you there ...

0 Kudos

I generally agree with Mylene here, however this is also a special case.

If you read SAP note 888889 then you will see that it is an intentional "heads-up" from SAP to take a look into the related notes, and (as was before) not the case that you have to find the problem first to need to fix the program error in your system.

The related notes of 888889 are to my knowledge designed in such a way that you can install them using SNOTE without any manual corrections required, and they fix only undesirable SAP standard system behaviour without any reasonable chance of customer specific use of it being impacted.

Basically, it blocks a known (and published) security error.

> do you actually expect us to come up with follow-up notes of the ones you wrote down here and develop a test-scenario for them, too?

This is true. It would go on forever... Just dumping note numbers into the forum is not the intention of them.

I think the thread can be closed and more specific questions about the content of individual notes or risk rating of them etc can be asked, if required. Generally, if you look at the correction blocks you can anyway work out what's going on and would probably want to implement them as a result.

Cheers,

Julius

0 Kudos

why, thanks Julius

actually, note 888889 was just meant as an example. i fished that out just to make my case, i did not really read the thingy

0 Kudos

Well, if you had read the thingy then you will see that it is just the needle in the haystack of notes which you do not want to sit on...

I would say that it is an exception to the generally correct principle you have outlined.

Cheers,

Julius

Former Member
0 Kudos

This message was moderated.