1. Place the cursor on a day to which you want to add a new action. Double-click an empty line or choose Create action. The system displays a dialog box listing the actions supported by the Planning Calendar.
2. In the dialog box, enter the start time for the action.
   You can trigger an action immediately for the current day by choosing Start immediately. This allows you to start an action manually if, for example, the planned action was unsuccessful.
3. Optionally, enter the repeat interval, in weeks, for an automatic repeat of an action. Without a repeat period, the action is run only once.
4. Optionally, enter the ID of the factory calendar to use for the action The action will not be executed on public holidays.
5. Finally, select the activity you want to schedule. Choose from the following activities:

Full database offline + redo log backup
Full offline backup (level 0) of the database using BRBACKUP, as well as archiving of any offline redo log files not yet archived, using BRARCHIVE. BRARCHIVE is automatically started from BRBACKUP. After the offline redo log files have been successfully backed up, you can delete them from the redo log archiving directory according to the BRARCHIVE function you have selected.

Full database offline backup
Full offline backup (level 0) of the database using BRBACKUP

Full database online + redo log backup
Full online backup (level 0) of the database using BRBACKUP, and then archiving of the offline redo log files, using BRARCHIVE. BRARCHIVE is automatically started from BRBACKUP. After the offline redo log files have been successfully backed up, you can delete them from the redo log archiving directory according to the BRARCHIVE function you have selected.

Full database online backup
Full online backup (level 0) of the database using BRBACKUP

Redo log backup
Backup of the redo log files from the archiving directory, using BRARCHIVE After the offline redo log files have been successfully backed up, you can delete them from the redo log archiving directory according to the BRARCHIVE function you have selected.

Partial database offline backup
Offline backup of the specified tablespaces using BRBACKUP

Partial database online backup
Online backup of the specified tablespaces using BRBACKUP

Check optimizer statistics
Determines whether new optimizer statistics are needed ( sapdba -checkopt )

Update optimizer statistics
Analyzes either the tables in table DBSTATC or the specified tablespaces, using SAPDBA ( sapdba -analyze )
For more information, see SAPDBA Command Mode

Adapt next extents
Adaptation of the values for the NEXT extent of the tables in a specified tablespace using SAPDBA ( sapdba -next ).

Check database
Checks the database system using SAPDBA ( sapdba -check ) For more information, see Using the Database System Check: Oracle

Incremental offline + redo log backup
Incremental offline backup (level 1) of the database using BRBACKUP, as well as archiving of any offline redo log files not yet archived, using BRARCHIVE. BRARCHIVE is automatically started from BRBACKUP. After the offline redo log files have been successfully backed up, you can delete them from the redo log archiving directory according to the BRARCHIVE function you have selected.

Incremental database offline backup
Incremental offline backup (level 1) of the database using BRBACKUP

Incremental online + redo log backup
Incremental online backup (level 1) of the database using BRBACKUP, as well as archiving of any offline redo log files , using BRARCHIVE. BRARCHIVE is automatically started from BRBACKUP. After the offline redo log files have been successfully backed up, you can delete them from the redo log archiving directory according to the BRARCHIVE function you have selected.

Incremental database online backup
Incremental online backup (level 1) of the database using BRBACKUP

6. Define parameters for the particular action
7. Choose Continue to finish scheduling the action. The system checks for conflicts with previously-scheduled activities. If any are found, the conflict are displayed and the action is not scheduled. Otherwise the action is added to the Planning Calendar and the required background job is scheduled.

For more information, see SAP Backup Utilities