Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
You need to determine why it cannot be implemented first. It is possible that a dependency is not in place or that a manual change was implemented and the snote cannot find the exact segment of code it is looking for in order to make the enhancement. Otherwise, it is not possible to automatically implement an snote with this message.
You need to determine why it cannot be implemented first. It is possible that a dependency is not in place or that a manual change was implemented and the snote cannot find the exact segment of code it is looking for in order to make the enhancement. Otherwise, it is not possible to automatically implement an snote with this message.
A note that has stauts "cannot be implemented" means the note is not valid for your system: the note is valid for a certain release and support packages that are different from yours.
Normally it means that the problem described in the note doesn't appear in your system.
(already corrected or doesn't appear)
But if it's present, you will have to open an OSS message to the note component and aks them to make the note valid for your SP/release.
ähhhm well, even tho SAP is not free from failjures as well, in 99% of the cases they quite KNOW what they do.
if a note is of Status "cannot be implemented", you should under no circumstances implement it.
First check out the reason why its not implementable. Maybe you just need to implement some other notes before. If thats the problem, implement the notes from which your note is dependant.
AFTER that your note should be of a good status.
Anyway, you can try to get that status good, but if you dont manage that, you never should try to implement that note.
Bluesky
