Spend 30 mins per day and earn $300/ daily.

Easy and outstanding online earning jobs. No need to work every day, work only in spare time. Earn $300 /day. Click here for more info.

World is moving online, the number of peoples who are making money online are also increasing day by day. As with any task that generates revenue it is not as easy at it sounds like because if it had been so, it would have been tried out by too many people.It is not simple and neither is it uncomplicated. However there is some easier ways of making money online that we have been trying to help our viewers. It is also which you might have already guessed like blogs, Online Surveys, Data entry jobs, etc.Here we tried to show some money making tips, which are easy and helps in making more money with less effort.

Implementing OSS Notes Using the Transaction Code SNOTE

In this document we will see how to implement an OSS note using the SNOTE transaction code.
The transaction code SNOTE is used to implement OSS Notes. With the SNOTE transaction, it is no longer necessary to register ABAP objects such as report function modules etc. manually. But data dictionary objects such as screens, tables need to be modified manually by registering them in OSS system.
In order to use the transaction code SNOTE, the relevant transport which implement this transaction in the system need to be transported. Please refer to the SNOTE guide available at http://service.sap.com
Execute the Transaction code SNOTE

One of the first steps to do is to upload the note into your system.
Follow Goto - >SAP Note Download

You can also use the SAP Note upload if the note has been saved in your local
Machine.

Enter the note number in the box displayed.

By double clicking on -> or on the note number you can display the OSS note.
You can also check the Status of the note by clicking on the Check SAP Note icon

Select the note and click on Check SAP Note icon

To implement the OSS note click on the Implement OSS Note icon. You will get a confirmation box. Click on Yes.

Click on the Continue icon

You will be prompted to enter a change request number. Click on the Create Request icon.

Enter a brief description of for the note and click on the continue icon

A change Request number is created for the change that you are making.

Click on the continue icon
The system will display the objects that are going to be modified during the process
of note application.

1 You can also check the logs of the activities performed during the OSS note implementation by clicking on the Logs icon on the application toolbar. The log information will contain all the steps that were performed from the point of downloading the note will its implementation is completed.

2 If there are any pre-requisite notes for the note that is being applied, the system will prompt you to load those notes too into the system. Depending on their applicability to your system, the system will prompt you accordingly to apply the pre-requisite notes.

Click on the Execute icon. You will get the note number displayed in the list of the OSS notes

Applying a SAP Note

Not all SAP Notes can be applied via the SNOTE transaction. Some are information only, providing no code corrections. Others entail corrections that can only be done manually. This latter type of SAP Note should be applied to your SAP system in conjunction with a trained ABAP programmer. Also, SAP recommends that SNOTE change requests NOT be transported into other systems. Use the SNOTE transaction in each SAP system that needs the correction, and delete the generated change requests since they should never be transported and could lock resources during application of other SAP Notes and support package application.

If you do not have a working OSS connection, you can download an OSS note from the SAP Marketplace using the SAP Download Manager and use the upload feature in SNOTE to load it into the SAP instance instead.

1. Log on to client 000 in the appropriate SAP system.
2. Go to transaction SNOTE.
3. On the Note Assistant - Version XXX/XXXX: Worklist screen, on the top-most menu bar click Goto → SAP Note download.
4. On the Note Assistant: Download Note popup, type the number of the SAP note in the Note number box and click the clock picture-icon. A SAP Note XXXXXX is being downloaded message will appear in the bottom status bar. If you get a communications error message, verify that saprouter is up and try again.
5. Once the SAP Note has been downloaded, it will appear on the Assistant - Version XXX/XXXX: Worklist screen under the SAP Notes → New navigation tree. The SAP Note can only be applied if there is a blue box with a black arrow to the left of the note number. If there is a gray diamond instead, the downloaded note cannot be applied or is not application for this SAP system.
6. To apply the SAP Note, on the Note Assistant - Version XXX/XXXX: Worklist screen double click on the downloaded SAP Note number.
7. On the Note Assistant – Display Note XXXXXX screen, read the note text to see if there are any necessary manual tasks to be performed after the note is applied. When you are ready to apply the note, click on the clock picture-icon.
8. If there are any prerequisite SAP Notes which need to be applied to the SAP system before the downloaded SAP Note can be applied, a list will appear in a Load the following notes into your SAP system popup will appear. Click the clock picture-icon to download these prerequisite SAP Notes as well. If any of the prerequisite SAP Notes must be applied in parallel with the original downloaded SAP Note, a list will appear in a SAP Note queue to be Imported popup. Click the clock picture-icon to apply all the listed SAP Notes.
9. Before applying any SAP Notes to your SAP system, a Confirmation: SAP Note read popup will appear. Once you have read the information contained in this popup, click the Yes button.
10. A standard Make repairs in foreign namespaces... popup will appear. Click the green √ to continue.
11. On the Prompt for transportable Workbench request popup, click the blank page picture-icon to create a new change request. On the Create Request popup, fill in the Short description and click the Save picture-icon. You will be returned to the Prompt for transportable Workbench request popup which contains the generated change request number for this system change. Click the green √ to continue.
12. On the Confirm changes popup, click the green √ to continue.
13. After the SAP Note has been applied to the SAP system, you will be returned to the Note Assistant - Version XXX/XXXX: Worklist screen. There is no completion message. Click the green √ and pencil picture-icon.
14. On the Set Processing Status for Note XXXXXX popup, click on the Completed line to turn “on” the radio button. Click the green √. You can now leave the SNOTE transaction. Modified programs, functions, etc. may require recompilation.If the OSS note you applied changed a ABAP program, you must go to the SE38 transaction and manually recompile the program. If it changed a function, go to transaction SE37 and click the Single Test button – this is enough to force the function to rebuild and you can back out of the SE37 transaction.

Stopping saprouter

1. Log on to the appropriate server as adm.
2. Click Start → Administrative Tools → Services to open a Services window.
3. Right-click on the SAPROUTER service and click Stop.
4. You may now log off the server.

Backup and recovery for a SAP instance is best handled along with the other
backup and recovery needs of your company’s computer systems. But for those company’s who do not yet possess a solid backup and recovery solution, or who simply want to segragate the SAP landscape from all other internal IT solutions, here are a few things you need to know.

Online versus offline, high availability, frequency, are all decisions your IT staff need to make based on their history with similar procedures at your company, the recommendations of SAP, and the guidance of your implementation Basis consultant. Enforced backups, and detailed and tested recovery procedures should be part of any Disaster Recovery plan, and a documented part of any SAP implementation project.

If your company falls into the latter category, SAP does supply tools for your uses which can be used in either line command form or from within the SAP instance. If you SAP server contains a tape drive or has access to the network tape unit, transaction DB13 can be used to schedule periodic backups. This is the same transaction where weekly statistics, log cleanup, and database verification jobs are scheduled in the post-installation work after installation of a new SAP instance. DB13 scheduled BRCONNECT runs which can also be CRONed in command line form by the IT staff.

For more information, please see the SAP Online Documentation for DB13 by going to the DB13 transaction and clicking Help -> Application Help or referring to the section Creating Database Statistics, Index Rebuilds, and Log Backup Jobs – Oracle. More information regarding BRCONNECT can be found in the SAP BRCONNECT Guide which can be found at http://service.sap.com/instguides.