SAP OSS Note

[pnagar]

Hi,

As sap Note implementation is client independent then How can we check in which client SAP Note was implemented originally ?

[dasistdochscheisse · Accepted solution]

there is a complicated way to check the client:

1. Open the Note in SNOTE

2. Double-Click on 'Note Log'

3 now you see a log of what happend during the processing of this note (who has downloaded it, who has implemented it and so on). In the log is also the transport request which was used to transport the objects.

4. In SE01, switch to tab 'display', enter the transport request, click display, double click the transport request and switch to tab 'Properties'. Here you can see the source client.

[Sriram2009]

Hi Prashant.

SAP Note implementation means you are going to do correct the SAP standard program bug fixes which takes place in all clients on your development system and then create the transport request(Change request) to QAS & PRD systems.to my understanding it will not client dependent, since you might have create the request in dev client number.

You can check, In your dev client xxx implement the SAP Note correction, and then check the same note in client 000 it will be available.

Regards

SS

[sthitapragnya_mahanty]

Hi Prashant,

There will be few SAP notes which are client dependent and they need to be installed at 000 client first and then rest of the clients. The same would be mentioned in the SAP note itself. Majority of SAP notes implemented are not client dependent.

You can go to SNOTE and check the status of OSS note. If it is active they are already implemented else you need to implement the same.

Regards

Sthita

[former_member644293]

Generally there are 2 types of OSS notes.

1. Note which involve source code program/object changes applied using SNOTE is visible in all clients. This can be checked in SNOTE transaction.

2. Customizing/Report/steps to execute the programs for a particular fix etc., are usually one time task and to be executed in a specific client based on the OSS note instructions. This is not visible in SNOTE.

Example - 2776560 - bgRFC Supervisor destination not usable in SRT_LOG

This need to be implemented in 000 client first and later in each client.

Hope this helps.

Regards,