What is the exact procedure of SNOTE implementation(step by step)

[Former Member]

Hello Friends,

I have 2 system landscape (DEV/QAS and PRD)

DEV.100/QAS.200 are in one system and PRD is as separate system..

Now want to implement SNOTE in two system landscape.

If you implement SNOTE, is it implemented in all clients..????

Above two systems are Solution Manager 4.0. SP16.

Please give me step by step...

regards,

gandalf.

[JPReyes · Accepted solution]

Read the SAP Note Assistant (SNOTE) Guide.

Everything is in there.

http://help.sap.com/saphelp_nw04s/helpdata/EN/b8/3cf839fd35384de10000000a11402f/frameset.htm

Regards

Juan

[Former Member]

If i want to implement SNOTE, i need SAP transport layer ..????

Because my DEV/QAS are in same system and PRD is separate system....

If DEV client /QAS client are in same system and PRD is separate system, you need SAP transport layer. for this two system landscape ??????????????????????

What is the exact use SAP transport layer

( i know that SAP transport layer is used only for SAP standard objects and also it is configured between DEV system and QAS system, if both systems are different)

IF DEV/QAS are in same system there is no need of configuring SAP transport layer between DEV client and QAS client.

Please advice.

regards,

gandalf.

[Former Member]

Hi,

Through NOTE SAP delivers correction for standard SAP program. So this are repository objects in sense would be client independent. As your QAS/DEV are in the same system you dont need to transport it.

But for moving it to prd you need a delivery route.Transport route is nothing but the path in which the objects are transported.

Regards,

Vamshi.

[Former Member]

Yes, its implemented in all the clients. Ind Dev system from transaction SNOTE

goto--> downloand SAP note, give the note number and click execute (clock icon), after its downloaded it will be under New drop down.

Select the note and click on implement Note (clock Icon), it will ask for a transport request, click on Create icon and give proper discription. Move this change to QAS test the changes and forward it production.

Note: before implementing the note read the note for any manual corrections, check if the note is valid or not for your release.