...
- Group Level
- Subgroup Level
- Individual system level
Settings on Group/sub-group individual level
On creating settings for each SNP OutBoard™ Housekeeping activity, a settings ID is required to be entered. SNP OutBoard™ Housekeeping will not allow the creation of a duplicate ID in the whole system landscape for the a particular task. Instead, the user could do the following:
...
In the settings screen, there is a toolbar with buttons for saving created/modified settings, for the deletion of existing settings. In addition, there is also documentation about the housekeeping activity and the option to clone settings and save them under a new Setting ID (copying functionality).
...
The Settings ID only covers settings of tasks in SNP OutBoard™ Housekeeping. There are also standard SAP Housekeeping tasks that can be found in the SNP OutBoard™ Housekeeping menu, however, they use a different approach than that of settings IDs. They follow the variant concept common for SAP reports.
...
Once the variant is specified, it is possible to transfer the variants to Settings, i.e. it can be used as a Settings ID. The user could highlight the variant and click 'Transfer variants to settings'. As In the first attempt, SNP OutBoard™ Housekeeping tries to assign a variant name to the settings ID. If it would lead to a non-unique settings ID, you are requested to insert an ID into the Settings ID screen. In case you prefer using your own Settings ID name, you can go to SNP OutBoard™ Housekeeping global settings and in the tab User Specific, mark 'Use own Settings ID' name. After Saving this setting, an insert ID pop-up appears every time variants are transferred to settings.
...
The user could highlight the variant and click 'Change variant'. The specified variant can be modified, saved, and transferred again. This action could be done concerning already scheduled runs with this variant. For cases where the variant is no longer required in the system, it can be removed using the 'Delete variant' button.
Once the variant is specified and transferred the user may run the variant from the Main menu.
Note: Should the user create a new settings ID for an activity the settings will fall into the scope of inheritance. Depending on where the settings are created from a hierarchical perspective, the settings could be cascaded down to the levels that may be below within the landscape architecture. When the current node is displayed, it is possible to see which settings are available for use by using the column 'Valid for'.
To understand more about creating the settings for the Household activities in SNP OutBoard™ Housekeeping please refer to the Activities chapter of this user documentation where it will go into more depth of about the individual settings for each of the activities available in SNP OutBoard™ Housekeeping.
...
By default, anything defined from the highest level will be cascaded down (settings created from sub-levels cannot be cascaded up. This is where Inheritance comes into play, as it provides the flexibility to set up and use different settings for specific sub-levels.
Inheritance in Activity View
...
Depending on the level in the hierarchy, if the task is executed, on all of the subsystems inheriting the settings is the task executed as well.
Note: Standard SAP reports that have a rigid limit of processed entries/objects, are from the 2.62 version automatically executed in cycles, till it is necessary to perform this report. Check the availability statement "Cyclic execution of standard report" in the task chapter header.
...
- Display scheduled tasks with additional information in the left pane
- Display scheduled tasks in the day/week/month calendar grid
- Reschedule single selected tasks
- Un-schedule one or more selected tasks
- Display scheduler logs (what task, which parameters and when was it scheduled/unscheduled)
- Display scheduler daemon logs (information about scheduled task run – license check, systems status, etc.)
- Shift the scheduled time of the run for one or more selected tasks.
...
Task execution will be done in real - time, so when scheduling any new tasks, or any task is executed, the time for the next run is calculated from the next calendar entry (next scheduled task), or in case there is a scheduled lock-in place, the unlocking time will be taken into consideration…
Info about the next run is shown in Central Scheduler Status.
Additional information is implemented into the calendar view for the expiration of content temporarily stored in RecycleBin. The yellow box indicates the date when expired content will be deleted and the tooltip shows additional info. If for various reasons a deletion is postponed, the box changes to red and is shown in the corresponding date cell.
...
The monitor provides additional information about the technical status, which can be found in the T. Status column. This status informs you of the last status that RunID reached during its execution. Technical status cannot be manually changed, unlike standard status.
Special parallel processing layout
Some of the tasks will be using a Task handler for parallelization, therefore the monitor layout is updated with extra columns that provide the following information:
...
The icon on the RecycleBin button will display whether RecycleBin contains some data, is empty, or is not accessible. 
Data are in RecycleBin
No access to RecycleBin
No data
The user may view the recycle bin for an individual activity or a complete view of all activities by clicking on the recycle bin found on the top menu under Goto -> RecycleBin. Only tasks corresponding to the selected activity profile will be displayed.
The Information on Display for the user will be the Activity name, Run ID, Table where they should see the Status, Number of Entries description, retention time (how long the Table entries should be temporarily stored), and how many days are left.
During the data load, the Run ID will have the status 'In process'. The status within the Run ID will be changed according to the table action within the run. When data is loaded into the recycle bin, the status 'Modifying the table' can be seen, followed by the status 'Deleting from DB'. After a successful run, the status of the table is changed to 'No action'.
...
On the Activity name you can drill down two or three levels (in the case of PSA and ChangeLog):
...
- The second level (within the run ID), contains the tables or objects where the entries are temporarily stored, the user could view these entries by selecting the table from the context menu and selecting 'show data'. As on the Run ID, the user could also restore the entries or permanently delete them by selecting either 'Undo Table / Object' or 'Delete Table / Object'.
- The third level exists only in case objects are in the upper level, similar to cases of PSA and ChangeLogs, in that the entries are stored in requests. As on On the second level, you can restore the entries or permanently delete them by selecting either 'Undo Object' or 'Delete Object'.
...
The status of each action can be seen on the table level as well as the overall status on the run ID level. Once there are no more tables available within the run ID (they were deleted or undone), the run ID will not be displayed in the recycle bin data.
...
Clicking the menu item on the table level opens the "Choose Fields" screen. Here the user may select which fields will be used for filtering the data to be shown.
...
- Manually by selecting the run level from the context menu and choosing choose "Delete Run" (on table level choose "Delete Table" or "Undo records" for Z*Table Cleanup. In this case it is possible to select the entries individually.)
- By scheduling the task "SNP OutBoard™ Housekeeping RecycleBin Cleanup" (see task group "SNP OutBoard™ Housekeeping System Tasks", folder "RecycleBin Tasks"), this will periodically clean RecycleBin.
...
- Shift the retention time (and thus Days left) by the days set in this dialog
- Shift the Expiry date to the selected date.
...