Creating a Settings ID

To define the settings for the OutBoard for Housekeeping Household tasks, it is important to be in the Activity view to define the settings for each activity. For each activity it is possible to define activity at various levels, this of course depends on how the system landscape is defined within the Landscape editor. The settings can be created on the following hierarchical levels:

...

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 with respect to 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 with in 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 OutBoard for Housekeeping please refer to the activities section of this user documentation where it will go into more depth of the individual settings for each of the activities available in OutBoard for Housekeeping.

Inheritance

By default, anything defined from highest level will be cascaded down (settings create from sub levels cannot be cascaded up. This where Inheritance comes into play, as it provides the flexibility to set up and use different settings for specific sub levels.
 

...

• Inheritance On:
• Inheritance Off:

Execute and Scheduling of Activities

Once the settings ID's have been created, execution of OutBoard for Housekeeping tasks may be executed manually or on a scheduled basis.

_{Figure 38: Execution and Scheduling of Tasks.}

Execute

To manually execute, click on the execution button and select a settings ID in the pop menu.

...

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 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.

Scheduling

To Schedule a task to be executed on a periodic basis, click on the schedule button and choose the settings ID.

...

Depending on the level in the hierarchy, after 'Schedule' button is clicked, the inheritance settings are cascaded downwards on all of the subsystems.
The Icon on the scheduling button will display whether activities have been scheduled or not. This functionality is visible in both activity and system view.
No Activities scheduled
Activities scheduled

Calendar

The Calendar button is available in both activity and system views and provides a calendar view of all scheduled activities.

...

Task execution will be done in real times, so when scheduling any new tasks, or any task is executed, the time for next run is calculated from the next calendar entry (next scheduled task) or in case there is scheduled lock in place, the unlocking time will be taken into consideration…
Info about next run is shown in Central Scheduler Status.
Additional information is implemented into 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.

Logging

To view logs of executed tasks, the user could click on the 'Logs' button. After entering the date and time for log selection, the status, description of the tasks and when they were executed will be provided.

...

Note: To differentiate older runs from current ones that are using parallelization a new status has been defined. This status indicates that status isn't stored in OutBoard for Housekeeping table but gathered from status of task handler.

Recycle Bin

The Recycle Bin provides temporary storage of deleted entries from OutBoard for Housekeeping's housekeeping activities. The deleted entries are compressed and stored with the option for the user restore the entries back to the system should it be necessary.

...