iVIEW of MSS-Launchpad

38
© SAP AG 1 ©SAP AG 2005 SAP Manager Self-Service Ramp-Up Knowledge Transfer mySAP ERP 2005 SAP AG Launchpad iView in SAP MSS - Advanced Enhance MDT Reporting Scenario and include it in the Launchpad iView/Integrate HCM BW Web Templates

description

iview

Transcript of iVIEW of MSS-Launchpad

Page 1: iVIEW of MSS-Launchpad

© SAP AG 1

©SAP AG 2005

SAP Manager Self-Service

Ramp-Up Knowledge TransfermySAP ERP 2005

SAP AG

Launchpad iView in SAP MSS -Advanced Enhance MDT Reporting Scenario and include it in the Launchpad iView/Integrate HCM BW Web Templates

Page 2: iVIEW of MSS-Launchpad

© SAP AG 2

©SAP AG 2005

End-User and Business Perspective

System Administrator Perspective

sample for a picture in the title slide

Integrate Manager’s Desktop Reports into LaunchpadLaunchpad iView

Integrate Manager’s Desktop Reports into LaunchpadLaunchpad iViewIntegrate BW queries into the Launchpad iView

Page 3: iVIEW of MSS-Launchpad

© SAP AG 3

© SAP AG 2006

End-User and Business Perspective

Folder

Application link (e.g. link to report)

Explanatory text for an application (optional)

The Launchpad iView works as a launchpad to launch reports from it.

The iView is part of the mySAP ERP 2005 delivery for SAP Manager Self-Service in order to offer manager one single access to a report launch application.

As in mySAP ERP 2005, the worksets have been re-arranged, SAP MSS from mySAP ERP 2005 on contains only one Reports workset in its standard delivery.

In the standard delivery, a manager can access the Launchpad iView by choosing the following path in the Top Level Navigation (TLN) part of the SAP Enterprise Portal: Manager Self-Service -> Reports.

For the end-user, the Reports iView presents reports under so called (application) categories that the system administrator sets up. This allows the manager to identify a business related report easily and to launch it.

The Reports iView can contain several kinds of reports coming from different business areas, such as financial and personnel management related reports. There is no need that a manager accesses financial reports in a different way than he/she accesses the personnel management/Human Capital Management related reports. Alos, several typyes of reports can be integrated in the Launch Pad, For example, you can include SAP Business Information Warehouse queries. In the standard delivery, also SAP BW queries are dilvered and arranged that way that four BW queries appear on one Portal page (i.e. Headcount and Overtime/Illness).

A manager can

Click on a report link to launch it

Change the launchpad

Page 4: iVIEW of MSS-Launchpad

© SAP AG 4

© SAP AG 2006

End-User and Business Perspective

Assume, a manager would like to start the Birthday report using the Lauchpad iView. Under the category Employee Data, he/she finds a Birthday link and clicks on it.

A next window opens and shows a selection screen to the manager. It allows the manager to select:

A selection period

An organizational view (e.g. Direct Reports).

Launch HCM report

Page 5: iVIEW of MSS-Launchpad

© SAP AG 5

© SAP AG 2006

End-User and Business Perspective

The manager makes his/her choices and selects the objects (in this case employees) for which he/she wants to show the report result list.

The manager clicks on Report Result.

Page 6: iVIEW of MSS-Launchpad

© SAP AG 6

© SAP AG 2006

End-User and Business Perspective

A next window opens and shows the result list. The result list shows reports as Web GUI result list.

To show the result list, the internal Internet Transaction Server (ITS) is needed. The integrated ITS is part of the the SAP Web Application Server 7.0.

Page 7: iVIEW of MSS-Launchpad

© SAP AG 7

© SAP AG 2006

End-User and Business Perspective

A manager can also launch SAP Business Information Warehouse Reports. SAP pre-delivers two example pages with four queires on each in oder to offer the managers a kind of dashboard view on a set of queries that support managers in analyzing situations like the headcount development in specific organizational units and identifying reasons for a certain development.

The examples delivered are:

Headcount

Overtime/Illness

Page 8: iVIEW of MSS-Launchpad

© SAP AG 8

©SAP AG 2005

End-User Perspective

System Administrator Perspective

sample for a picture in the title slide

Integrate Manager’s Desktop Reports into LaunchpadLaunchpad iViewIntegrate BW queries into the Launchpad iView

Page 9: iVIEW of MSS-Launchpad

© SAP AG 9

© SAP AG 2006

Prepare Human Capital Management Reports

Folder (i.e. MDT subcategory)

Application link (e.g. link to report; i.e. executable function code in MDT

Explanatory text for an application (optional) and could be assigned during customizing

The Launchpad View is part of SAP Manager Self-Service in order to offer a manager a single point of access to launch reports.

The system administrator can maintain applications to be displayed in the iView and maintain folders to group applications.

An administrator can maintian the following types of applications:

SAP BI Reports (Queries or Web Templates)

Report Writer reports

Transactions

URLs

Manager‘s Desktop based reports

The following application types are maintained directly in the Launchpad customizing:

SAP BI Reports (Queries or Web Templates)

Report Writer reports

Transactions

URLs

You can find the appropriate IMG activity under Integration with Other SAP Components -> Business Packages/Functional Packages -> Manager Self-Service (mySAP ERP) -> Reporting -> Set-Up Launchpad.

Page 10: iVIEW of MSS-Launchpad

© SAP AG 10

The Manager‘s Desktop based reports first need to be configured in the following Manager‘s Desktop tables:

T77MWBS (Manager‘s Desktop Scenarios)

T77MWBFCD (Function Code Definitions)

T77MWBFCO (Object-dependent Function Codes)

T77MWBBWS (BW Report System Data)

T77MWBFCH (Function Code Hierarchies)

In the MDT customizing, the reports are set up as a so called scenario. The scenario represents the total offering of reports that a customer wants to offer their managers/a group of managers within their company and allowing access via SAP Manager Self-Service. In the standard, the example scenario RPT0 is delivered.

The set up of MDT based reports also includes already subcategories (e. g. Employee Data) that will appear as folders in the Launchpad iView.

To refer to the standard scenario provided for SAP Manager Self-Service, in the SAP Reference IMG choose the following path: Personnel Management -> Manager‘s Desktop -> Enhancements of Function Codes -> Define Structure of Function Codes. In the IMG activity Define Function Code Hierarchies (i. e. Table T77MWBFCH), the standard scenario RPT0 is maintained.

Page 11: iVIEW of MSS-Launchpad

© SAP AG 11

© SAP AG 2006

Pre-delivered Manager‘s Desktop Scenario for Managers

Table T77MWBFCH

In case a customer wants to display application links from the Manager‘s Desktop based customizing in the Launchpad iView, a customer needs to perform the folowing to big steps:

1. Set up/change the MDT scenario(s) they want to offer to their managers/groups of managers.

2. Transfer the table entries form the Manager‘s Desktop based tables to the Launchpad table.

For the usage of R/3 based reports in SAP Manager Self-Service, a Manager‘s Desktop scenario is predelivered (see table T77MWBFCH). The scenario name is RPT0.

From usage/implementation point of view, there are the following scenarios possible:

A customer creates a completely new scenario

A customer re-uses an already existing scenario (from their previous implementations of Manager‘s Desktop)

A customer re-uses the pre-delivered SAP scenario (RPT0) and includes customer-specific enhancements (additional reports and new categories)

Which business scenario a customer wants to follow up with depends on the information need that the company has identified for their managers and whether a customer has already scenario(s) in use as of the previous usage of SAP Manager‘s Desktop.

Before transferring table entries from the MDT scenario to be used in the Launchpad iView, define your scenario according to your needs in the Manager‘s Desktop tables first.

As an example, let‘s assume the customer wants to enhance the existing RPT0 scenario with two more organizational reports and would like to offer it under a new folder they call Organization.

Page 12: iVIEW of MSS-Launchpad

© SAP AG 12

© SAP AG 2006

Create Function Codes to Enhanced the Report List

Table T77MWBFCD

First, the new report entries need to be maintained in the Manager’s Desktop customizing.

Reports represent so called function codes. These are defined in the table T77MWBFCD.

To create a new function code choose New Entries or make a copy of an existing entry.

Page 13: iVIEW of MSS-Launchpad

© SAP AG 13

© SAP AG 2006

Create a Function Code for New Subcategory

Name of function codeName of function code

Text will be displayed as folder in the

Launchpad iView

Text will be displayed as folder in the

Launchpad iView

Determines that this is not an executable

function but a subcategory to group executable functions

Determines that this is not an executable

function but a subcategory to group executable functions

Table T77MWBFCDTable T77MWBFCD

Example Implementation:

As a function code, in the T77MWBFCD table. enter any name that falls within the customer‘s name space.

The text that you enter later on appears in the Launchpad iView. The new function code will appear under it.

You need to classify the function code as NODE type becuae the entry here does not represent the executable function (i.e. report) itself.

Save your entries.

Page 14: iVIEW of MSS-Launchpad

© SAP AG 14

© SAP AG 2006

Create a Function Code for Report RHXFILLPOS

The Based on Organizational Structure indicator is set for all function codes that are applied to organizational objects

The Based on Organizational Structure indicator is set for all function codes that are applied to organizational objects

Create a new function code for the report RHXFILLPOS

Create a new function code for the report RHXFILLPOS

Table T77MWBFCDTable T77MWBFCD

Determines that this function code is a report

Determines that this function code is a report

The report is object type specific and can only be started with a certain object type

The report is object type specific and can only be started with a certain object type

In the example, the report RHXFILLPOS should be entered. This report is based on the organizational structure. The report can be started with certain objects (org units and positions). Along the structure the system collects all objects, org units and positions, and shows the appropriate data for the found positions. Please note: To launch that report, for the front-end side of the reporting application you need to have included an appropriate organizational view that allow you to select organizational units.

To create a new function code for a report choose New Entries or copy an existing entry.

Note: function code name must be create in customer name space.

Save your entries

You can define the report to be Object type specific: Set this indicator if you want the function only to be available for certain object types. You can specify the corresponding object types in the customizing activity Define Object-Specific Function Codes (T77TMWFCO) of the Enhancement of Function Codes chapter. Please note: For reports used in SAP Manager Self-Service it is recommended that to define them to be specific for certain objects. This allows the system to display an error message in case the user selects wrong object types to start a report with. This could happen due to the fact that the end-user selects a non-appropriate organizational view in the drop-down box that triggers the display of objects the manager can use for object selection.

Page 15: iVIEW of MSS-Launchpad

© SAP AG 15

© SAP AG 2006

Create a Function Code for Report RHSBES00

The Based on Organizational Structure indicator is set for all function codes that are applied to organizational objects

The Based on Organizational Structure indicator is set for all function codes that are applied to organizational objects

Create a new function code for the report RHSBES00

Create a new function code for the report RHSBES00

Table T77MWBFCDTable T77MWBFCD

Determines that this function code is a report

Determines that this function code is a report

The report is object type specific and can only be started with a certain object type

The report is object type specific and can only be started with a certain object type

In the example, the report RHSBES00 should be entered as the second report to be launched from the Launchpad iView. This report is based on the organizational structure. The report can only be started with object type org unit. Along the structure the system collects all objects (org units and positions) and displays the appropriate data.

To create a new function code for a report choose New Entries or copy an existing entry.

Note: function code name must be create in customer name space.

Save your entries.

You can define the report to be Object type specific: Set this indicator if you want the function only to be available for certain object types. You can specify the corresponding object types in the customizing activity Define Object-Specific Function Codes (T77TMWFCO) of the Enhancement of Function Codes chapter. Please note: For reports used in SAP Manager Self-Service it is recommended that to define them to be specific for certain objects. This allows the system to display an error message in case the user selects wrong object types to start a report with. This could happen due to the fact that the end-user selects a non-appropriate organizational view in the drop-down box that triggers the display of objects the manager can use for object selection.

Page 16: iVIEW of MSS-Launchpad

© SAP AG 16

© SAP AG 2006

Entries in Table T77MWBFCD

Table T77MWBFCDTable T77MWBFCD

ResultsResults

After you have created the new function codes, the table T77MWBFCD includes the entries as shown in the screenshot.

Page 17: iVIEW of MSS-Launchpad

© SAP AG 17

© SAP AG 2006

Define Object Types for Object Type Specific Function Codes

Table T77MWBFCOTable T77MWBFCO

ResultsResults

For some functions, only special types of organizational objects (persons, positions etc.) may be appropriate. It also may be useful, that a function stands for different function modules or reports depending on the type of the argument. These restrictions are stored in T77MWBFCO. As stated already, for the usage of reports in SAP Manager Self-Service it is recommended that you in table (T77MWBFCD) have flagged your function codes as to be object type specific.

In this step, you now define which object types should be valid for your reports.

Perform the following steps:

Enter the function code that you previously flagged as object type-specific.

Enter the object type that the function code is to apply to. If there is more than one object type per function code, you must make separate entries.

In the Function Module and Program Name fields, enter the function module or the report that is called up by the corresponding function code.

Page 18: iVIEW of MSS-Launchpad

© SAP AG 18

© SAP AG 2006

Assign Function Codes to a Scenario Used in MSS

Table T77MWBFCHTable T77MWBFCHMDT Scenario RPT0 is

used in the MSS standard delivery

MDT Scenario RPT0 is used in the MSS standard delivery

Now you need to assign the function codes you have defined into the standard Manager‘s Desktop scenario (remind, that our example wanted to re-use the standard scenario and enhance it with two more categories, orgnanized under an additional category).

Page 19: iVIEW of MSS-Launchpad

© SAP AG 19

© SAP AG 2006

Assign Executable Functions and Subcategories

IMG: Table T77MWBFCHIMG: Table T77MWBFCH

Theme categoryTheme category

Subcategories which are all assigned to the same theme category MSS_HOME

Subcategories which are all assigned to the same theme category MSS_HOME

Executable functions which are assigned to the same subcategory TRAIN

Executable functions which are assigned to the same subcategory TRAIN

Define the hierarchy for the report tree in table T77MWBFCH. The structure of the report tree is based on the function codes defined in table T77MWBFCD. The non-executable functions (categories and subcategories) are used to structure the report tree.The hierarchy is structured as follows:

A function code of type Home ( theme category) is the highest-level node (root) in the report tree. In MSS (ERP 2004) only one theme category is used. Instead of a reporting tree, a list of reports is provided in MSS. Managers can filter the reports by choosing a subcategory from the drop down list box.Subcategories, functions codes of type Node, or executable functions can be located at the second level. In MDT a subcategory can contain further subcategories or executable functions. In MSS subcategories are always assigned to the same theme category, and subcategories can only contain executable functions.In the example above, the subcategory Train contains 6 reports.

The name of the scenario is entered in the first field.The name of the theme category (type HOME) or the subcategory, that is, non-executable function codes (type NODE) are displayed in the Higher-Level FCode column. Since the category corresponds to the highest-level entry in the report tree, this category does not have an entry in the Higher-Level Function Code field.The number entry in the Nr. column enables you to specify the sequence in which the theme categories appear on the initial screen or the sequence in which the subcategories and executable functions appear within a hierarchy level in the function tree in the left screen area.Enter the name of the individual function code in the Function Code column.

Page 20: iVIEW of MSS-Launchpad

© SAP AG 20

© SAP AG 2006

Assign Organization Subcategory to Theme Category

Subcategory which shall be assigned to the theme category MSS_HOME

Subcategory which shall be assigned to the theme category MSS_HOME

Theme category MSS_HOMETheme category MSS_HOME

Scenario used in MSSScenario used in MSS

To create the fucntion code hierarchy, you need to assign the subcategory to the thme category of the RPT0 scenario. To do so, add new entry as shown in the screen shot.

In the field Function Code you have to enter the theme category to which the new category should be assigned to. Due to the fact that for the MSS scenario only one theme category is used/allowed, you have to enter the theme category MSS_HOME.

By entering a number in the Sequence field, you determine the order in which the categories are to appear on the drop down list box of Report Selection within MSS.

Page 21: iVIEW of MSS-Launchpad

© SAP AG 21

© SAP AG 2006

Enhance the Scenario RPT0 Used in MSS

Scenario used in MSSScenario used in MSS

The new subcategory to which the report should be assigned to

The new subcategory to which the report should be assigned to

Determine the order in which the reports are to appear in the Launchpad iView

Determine the order in which the reports are to appear in the Launchpad iView

Enter the function code of the new report

Enter the function code of the new report

To enhance the standard delivered scenario with the two reports and the new category Organization choose New Entry or copy an existing entry.

To assign the new subcategory to the scenario used in MSS, you have to enter RPT0 as the application scenario.

In the field Function Code you have to enter the theme category to which the new category should be assigned to. Due to the fact that for the MSS scenario only one theme category is used/allowed, you have to enter the theme category MSS_HOME.

By entering a number in the Sequence field, you determine the order in which the categories are to appear on the drop down list box of Report Selection within MSS.

Page 22: iVIEW of MSS-Launchpad

© SAP AG 22

© SAP AG 2006

Created Entries in Table T77MWBFCH

T77MWBFCHT77MWBFCH

After you have enhanced the RPT0 scneario, table T77MWBFCH shows the entries as shown in the screen above.

Page 23: iVIEW of MSS-Launchpad

© SAP AG 23

© SAP AG 2006

Transfer Table Entries to Launchpad Tables

Convert data of a Manager‘s Desktop (MDT)scenario to the Launchpad tables

Perform report initially and whenever you have created a new or changed an existing MDT scenario that you would like to use in the Launchpad iView

After you have defiend new/changed entries in the Manager‘s Desktop tables and included into your scenario, you need to transfer the entries to the Launchpad tables.

To do so, execute the report out of the Convert MDT Data to MSS Reporting Launchpad IMG activitiy.

The report is scenario based. As we have enhanced the standard scenario in our example, enter the scenario name RPT0 and run the report.

Page 24: iVIEW of MSS-Launchpad

© SAP AG 24

© SAP AG 2006

Transfer MDT Customizing Entries to Launchpad Tables

After performing the report, the entries in the Launchpad customizing will include a new Organization folder and the two reports under it.

Page 25: iVIEW of MSS-Launchpad

© SAP AG 25

© SAP AG 2006

Creating Additonal/Descriptive Texts

In order to add a descriptive text for your new reports, double-click first on one of your reports.

In the window which appears on the right side, enter a description. You etiher can enter the description directly in the Description row or in case you would like to add a longer text, choose the Editor for Description icon that opens a text box to enter your description.

Save your entries.

Page 26: iVIEW of MSS-Launchpad

© SAP AG 26

© SAP AG 2006

Result in the Launchpad iView

New Folder (Organization)

2 New Application Links

Report Descriptions

After you have converted the MDT table entries to the Launchpad customizing table entries and entered descriptions to the new reports, the Launchpad iView contains as a new folder the Organization folder and allows the manager to call two more reports.

The manager addtionally can see the descriptions that you have maintained in the Launchpad customizing.

Page 27: iVIEW of MSS-Launchpad

© SAP AG 27

© SAP AG 2006

Perform New Reports

When the manager clicks on Staff Assignment, for example, the system calls a new application (iView) and launches it in a separate window.

As the application (report) called from the Launchpad iView belongs to the Manager‘s Desktop application category, the LPA Reporting iView is called in the separate window.

Page 28: iVIEW of MSS-Launchpad

© SAP AG 28

©SAP AG 2005

End-User Perspective

System Administrator Perspective

sample for a picture in the title slide

Integrate Manager’s Desktop Reports into LaunchpadLaunchpad iViewIntegrate BW queries into the Launchpad iView

Page 29: iVIEW of MSS-Launchpad

© SAP AG 29

© SAP AG 2006

Launchpad iViews

Launchpad iViews are available with the Business Package for Common Parts and the Business Package for Manager Self-Service

The Launchpad iView is part of the Business Package for Common Parts and is called using Deltalink.

When launching a certain application out of it, the system calls another iView, depending on which type of application is to be called.

Therefore, four iViews do exist to build the Launchpad functionality:

Launchpad (com.sap.pct.erp.common.reportlaunchpadpcd)

Launchpad: SAP BI Report (com.sap.pct.erp.common.bw_dummy)

Launchpad: SAP ECC Report or Transaction (com.sap.pct.erp.common.transaction_dummy)

Launchpad: URL (com.sap.pct.erp.common.url_dummy; used for the BI reports, for example set of queries/Web templates Headcount, Headcount FTE, Entries, Leavers).

For the function codes (reports) defined in the Manager’s Desktop tables, another Launchpad iView is called from the Launchpad iView which is LPA Reporting (com.sap.pct.erp.mss.lpareporting). This iViewis part of the Business Package for Manager Self-Service.

The Launchpad iView can be used in several Portal roles (such as Business Unit Analyst or Manager Self-Service).

Page 30: iVIEW of MSS-Launchpad

© SAP AG 30

© SAP AG 2006

Reports Page in Manager Self-Service

The standard delivery of the Business Package for Manager Self-Service for the mySAP ERP 2005 release includes a Reports page (com.sap.pct.erp.mss.reports_page).

The Reports page consists of the Balanced Scorecard Elements (com.sap.pct.erp.mss.reports_page) iView and the Launchpad (com.sap.pct.erp.common.reportlaunchpadpcd_page) page.

This means that the Launchpad (com.sap.pct.erp.common.reportlaunchpadpcd) iView is included in the Reports (com.sap.pct.erp.common.reportlaunchpadpcd_page) page.

Page 31: iVIEW of MSS-Launchpad

© SAP AG 31

© SAP AG 2006

Launchpad iView/Deltalink Parameters

role=MSSinstance=REPdisplay_external=X

The iView Launchpad that is used in SAP Manager Self-Service, needs to have the following application parameters (see Application Parameter property of the Launchpad (com.sap.pct.erp.common.reportlaunchpadpcd) iView:

role=MSS

instance=REP

display_external=X

The role=MSS paramter reads out the customizing you did in the SAP Reference IMG under Integration with Other SAP Components -> Business Packages/Functional Packages -> Manager Self-Service (mySAP ERP) -> Reporting -> Set Up Launchpad.

Page 32: iVIEW of MSS-Launchpad

© SAP AG 32

©SAP AG 2005

End-User Perspective

System Administrator Perspective

sample for a picture in the title slide

Integrate Manager’s Desktop Reports into LaunchpadLaunchpad iViewIntegrate BW queries into the Launchpad iView

Page 33: iVIEW of MSS-Launchpad

© SAP AG 33

© SAP AG 2006

Integrate SAP BW Queries/Web Templates into the Launchpad (1)

The SAP BI content includes Web Templates that are used to display reports in the launchpad.

To add the Web templates to the launchpad as example entries, execute the program FPB_LP_WRITE_ENTRIES.

The report integrates those Web Templates into the Launchpad tables that are used as standard delivered Web Templates in SAP Manager Self-Service.

They are example entries to let you see how the customizing for the Launchpad works.

Page 34: iVIEW of MSS-Launchpad

© SAP AG 34

© SAP AG 2006

Integrate SAP BW Queries/Web Templates into Launchpad (2)

After the Web Templates are imported, you can adjust the entries in the Launchpad customizing.

You also can manually maintain new entries in the Launchpad customizing.

Page 35: iVIEW of MSS-Launchpad

© SAP AG 35

© SAP AG 2006

Integrate SAP BW Queries/Web Templates into Launchpad (3)

Entries for SAP BW Web template integration:

Application Category: SAP BI Report Web TemplateWeb Template BI: <Name of BI Web Template>System Alias: <Alias name of BW system>

If you want to integrate single SAP BW templates into the Launchpad, create a new entry in the Launchpad customizing with the following entries:

Application Category: SAP BI Report Web Template

Web Template BI: <Name of BI Web Template>

System Alias: <Alias name of BW system>

Page 36: iVIEW of MSS-Launchpad

© SAP AG 36

© SAP AG 2006

Integrate SAP BW Queries/Web Templates into Launchpad (4)

Entries for SAP BW Web template integration – 4 SAP BW queries on one page:

Application Category: URLURL: <Full PCD path name> whereby http:// must be replaced by ROLES://

SAP pre-delivers two Portal pages that include 4 queries each.

The pages are the following ones:

Headcount (com.sap.pct.erp.mss.headcount)

This page contains the following four SAP BW queries/iViews:

- Headcount (com.sap.pct.erp.mss.headcount_overview)

- Headcount FTE (com.sap.pct.erp.mss.headcount_fte)

- Entries (com.sap.pct.erp.mss.entries)

- Leavers (com.sap.pct.erp.mss.leavers)

Illness Overtime (com.sap.pct.erp.mss.illness_overtime)

This page contains the following four SAP BW queries/iViews:

Overtime Costs (com.sap.pct.erp.mss.overtimecosts)

Overtime Rate (com.sap.pct.erp.mss.overtimerate)

Illness Costs (com.sap.pct.erp.mss.illnesscosts)

Illness Rate (com.sap.pct.erp.mss.illnessrate)

If you would like to use these queries in SAP Manager Self-Service and to be launched from the Launchpad iView, you need to customize them the following:

Application Category: URL

URL: <Full PCD path name> whereby http:// must be replaced by ROLES:// (e.g. ROLES://portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.pages/com.sap.pct.erp.mss.hcm/com.sap.pct.erp.mss.headcount)

Page 37: iVIEW of MSS-Launchpad

© SAP AG 37

© SAP AG 2006

Integrate SAP BW Queries/Web Templates into Launchpad (5)

After you have customized the URL in the Launchpad table, the manager can call the page containing 4 queries from the Launchpad iView.

Page 38: iVIEW of MSS-Launchpad

© SAP AG 38

© SAP AG 2006

Copyright 2006 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.