Pre-Requisite Checks before Implementing A SAP Note

Pre-Requisite Checks before Implementing A SAP Note

Introduction

          The SAP Notes are implemented through the Transaction SNOTE. Though the process of executing the SAP note is simple, there are a few Pre-requisite checks which have to be satisfied before implementing the note.  This BOK details the information on the various Pre-Requisite checks which needs to be carried out before implementing the note and the action associated with the pre-requisite checks.

Illustration

The following are the list of pre-requisite checks which are to be performed before implementing the SAP note,

• Implementation Status
• Release Validation
• Pre-Requisite Notes
• Manual Correction
• Side-Effects

• Implementation Status:

SAP note mainly have 3 implementation statuses,

-->  Can be implemented

-->  Cannot be implemented

-->  Obsolete Version Implemented

If the status is “Can be implemented” then the Note doesn’t have any conflict with the current system and can be implemented through the SNOTE transaction.

If the status is “Cannot be implemented”, then there could be two cases,

     --> The note has got only manual changes involved OR

     --> There is a release conflict.

So in either case, the Note cannot be implemented through the SNOTE transaction.

If the status of the note is “Obsolete Version Implemented” it means that SAP has updated the note with a new version and our system had been implemented with an older version. This also means that the Note is Implementable through SNOTE.

• Release Validation:

Release Version of the SAP note has to be in line with the Current release of our system.

For instance, the SAP note 1617097 has the affected release SAP_HRCGB as 604. So our system should have the same release corresponding to the component.

(Above is the extract from the PDF extract of the SAP note from Marketplace)

         To verify that follow the MENU path in your SAP screen as SYSTEMàSTATUS: And click on the highlighted button in the below

          displayed dialog box.

In the next window, scroll through the components to locate SAP_HRCGB. From the below screenshot it is evident that the release in our system is 604 too. So this note is in line with the system’s status. So Release validation is trough.

Further Highest support of the component of our system is SAPK-60438IN, so the correction information’s release should be in this range.

To check this, open the Correction Instruction related to the note (from SAP market place) and check its release.

In this case the correction is valid from SAPK-60415IN to SAPK-60438IN. Our systems component falls in the range. So Correction Release validation is through.

(Above is an extract of the correction instruction involved in the note)

Let us consider another note 1594617, the correction instruction 1007760’s Correction Validity states the Correction is valid only from SAPK-60425 to SAPK-60437.

Checking on the current release available for the particular package in our system shows the correction is valid for the release SAPK-60438 which doesn’t fall in the validity range of the Correction Information’s Validity. So this Correction Information is not implementable as to our current system’s release.

• Pre-Requisite Notes

Some of the SAP notes have pre-requisite notes, which will be implemented when the main note is implemented.

For instance consider SAP note 1381901, the correction instruction of the Note displays the Pre-Requisite Notes, if any.

In this case the note has plenty of pre-requisite notes as displayed. So all the prerequisite checks needs to be carried out for these Pre-Requisite notes before implementing the main note.

• Manual Corrections

Some SAP notes do have manual correction which needs to be implemented manually by the user apart from the Correction Instructions which will be implemented automatically when the Note is implemented through SNOTE.

There are two types of Manual corrections,

     --> Pre – Manual Implementation:  These needs to be implemented before the implementation of the Note through 

     SNOTE transaction.

     --> Post –Manual Implementation: These needs to be implemented after the  implementation of the Note through

     SNOTE Transaction.

The SAP Note 1498575 has both Pre and Post manual implementations,

(Extracts of the note from SAP marketplace)

Note: These manual corrections are to be implemented only when the Release Validation is successful (as per the 2^nd pre-requisite check), if the release validation is not successful then the manual correction are not meant for our current system and they can be ignored.

Some SAP notes have manual correction information as create a new program or update a current existing program.

For instance, SAP note 647424 has instructions to create two new Programs and include the code provided attached inside the SAP note.

These processes cannot be carried out through the SNOTE transaction and has to be manually executed by the SAP User.

• Side Effects

Implementing a SAP note does create side effects in some cases.

If a SAP note has a side effect it will be specified in the PDF extract of the Note from SAP Marketplace as shown below.

As shown above, when the SAP note 1553430 is implemented it causes an unwanted side effect, which can be rectified by implementing the Side Effect Solution Note 1572662. So implementing the Note 1572662 becomes mandatory.

When a SAP note with side effect is implemented through SNOTE, SAP pops out a warning message as displayed below making us aware of a side effect.

          When all these pre-requisite checks are satisfied for a SAP note, the Note can be implanted through the SNOTE transaction.