Best practices for code correction note implementation

[Former Member]

Hi,

We recently faced one issue where a code correction note UAT was successful in the quality system,but when we move the same change in production system it didn't made any change.

later we realized that some code correction note was missing in production system while it was present in quality system as a solution note through another issue which was being resolved in parallel and that note let the UAT passed.

I would like to know following points for experts :

1. Suppose,we implemented a note provided by SAP but that didn't resolved the issue in quality system,do i need to back out that note before implementing the new one.
2. If we back out notes,I know that a specific note may be prerequisite of many other notes and if we back out main note, the notes that may be prerequisite for other main notes will also get back out and hence making system unstable.
3. Can't we implement solution notes(code correction) for all ARM related issue in parallel.

Just looking for the best practice we should follow while implementing code correction notes as we know that code correction is common activity in GRC AC.

Thanks,

Mukesh

[former_member631876]

is there any sap notes without valid releases section ? is there any note relevant for any system ? thank you