Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
XAP-OSP (Application Component) Office Suite Program⤷
/OSP/CORE (Package) Office Suite Program - core functionality
IMG Activity
| ID | /OSP/IMG_ACT_MDR_MT | Define Application Metadata |
| Transaction Code | /OSP/32000012 | (empty) |
| Created on | 20051109 | |
| Customizing Attributes | /OSP/IMG_ACT_MDR_MT | Define Application Metadata |
| Customizing Activity | /OSP/IMG_MOBJ_MDR_MT | Define Application Metadata |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /OSP/IMG_DOCU_MDR_MT |
Use
In this step, you define the metadata settings for each application (scenario) of each solution. These settings control the overall flow of an application (scenario), configure its user interface, and determine how it behaves from a business point of view.
For the Mendocino solution, there are five applications (scenarios):
- Budget monitoring - alerts
This application (scenario) allows users to create rules that monitor critical postings and variances on their cost centers or the orders belonging to the cost centers. If the rules are violated, alerts and notifications ensure that they can then take action to resolve any problems.
- Budget monitoring - reports
This application (scenario) allows users to run budget-related reports on a regular basis or on request.
- Leave management
This application (scenario) allows users to create, review, approve, and monitor leave requests. They create leave requests as calendar items, which are fully integrated with SAP approval guidelines and defined business processes.
- Team management
This application (scenario) allows users to access up-to-date information about themselves and their colleagues, as well as other employees and organizational structures through Microsoft Outlook, using the contacts from the SAP system.
- Time management
This application (scenario) allows users to report and monitor their time easily and intuitively through the Microsoft Outlook calendar. Reported time is recorded directly in the SAP time recording system.
Requirements
Standard settings
Activities
For each application (scenario) within Mendocino:
- Define the flow configuration
- Define the application UI
- Define the application behavior
Define Flow Configuration
Here, you define the overall flow of the application (scenario). For example, you could set the subscription timeout for a Web service call. In that case, you would define the fields as follows:
Field Description
Object Name Leave request
Component getLeaveInfo
Type Web service call
Parameter Subscription timeout
Value Any value
Define Application UI
Here, you configure the user interface of each application (scenario).
- For each application UI, configure the containers
A container can be a task pane, tab, dialog box or toolbar.
- For each container, configure the regions
A region is an area within a container (for example, the region for related reports in a task pane).
- For each region, configure the UI components
A UI component is a text box, radio button, checkbox or other user interface element. You can only change values here.
- For each UI component, define the role-based links (if applicable)
You can define URLs based on roles, so that the links displayed in the UI are determined by the role of the person accessing that link. SAP delivers sample entries for this.
Define Application Behavior
Here, you determine the behavior of each application (scenario) from a business point of view. There are different predefined settings for each application (scenario), but you can change the type, value, and unit in each case.
The settings for each application (scenario) are as follows:
Budget Monitoring
Setting Description
CLEAR AGE OF NOTIFICATION Bookkeeping table entries older than the specified value (for example, 60 days) are deleted
RULE VIOLATION ACTIVATION Activation time on start date specified in RULE VIOLATION START DATE
RULE VIOLATION FREQUENCY Frequency of budget monitoring
RULE VIOLATION START DATE Start date of budget monitoring
RULE VIOLATION START TIME Budget monitoring starts to run after the time specified by this parameter has elapsed, starting from the current time. For example, if the current time is 04:12:00 and the specified time is 06:00:00), budget monitoring starts to run at 10:12:00. The input must be a string (that is, the format must be hhmmss).
Time Management
Setting Description
ARCHIVING Items older than the specified value are locked and cannot be changed by the user
PERIODICITY Frequency of white space recording (WSR) scheduler run
SUM Duration of display of working time summary in the task pane
WSR ACTIVATION TIME Activation time on the start date specified in WSR START DATE
WSR START DATE Start date for triggering WSR
WSR START TIME WSR triggering starts to run after the time specified by this parameter has elapsed, starting from the current time. For example, if the current time is 04:12:00 and the specified time is 06:00:00), WSR triggering starts to run at 10:12:00. The input must be a string (that is, the format must be hhmmss).
Team Management
Setting Description
COLLEAGUES SUBFOLDER Name of colleagues subfolder displayed in the UI
DEPTH Number of team management hierarchy levels for which data is displayed to the user
PLVAR Differentiates between scenarios in your organizational plan. Team management allows you to manage scenarios in parallel in various plan versions.
TEAMS SUBFOLDER Name of teams subfolder displayed in the UI
Example
Business Attributes
| ASAP Roadmap ID | 151 | Design interfaces |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
History
| Last changed by/on | SAP | 20060412 |
| SAP Release Created in | 100 |
