Using SAP NetWeaver BI in Guided Procedures: Info Callable Object Scenario

Transkript

1 Using SAP NetWeaver BI in Guided Procedures: Info Callable Object Scenario SAP NetWeaver Product Management When processing a task within a Guided Procedure (GP) process, a user may optionally wish to access additional information to determine the proper input or response. SAP NetWeaver Business Intelligence (BI) is frequently a good source of information for this decision-making process. The Info Callable Object allows you to include the BI information in a GP process so that the runtime user can access the information as necessary, without interrupting the flow of the process. In this document, we will add a BI Info Callable Object to a GP process and execute it in the GP runtime. The document assumes that you have some knowledge of the GP design time and runtime and therefore focuses only on the steps pertinent to creating a BI Info Callable Object and its use in a process. 1

2 Staffing Request Process In our example scenario, we have a simple process in which: A user ( requestor ) requests staffing for a project from the engineering department. The engineering department manager ( manager ) approves the request. The requestor reviews the response and completes the process. To make the approval step self-contained, we want to provide the manager with the relevant information from BI necessary to assign staffing and approve the request. Since the focus of this document is creating and implementing the Info Callable Object with BI information, we will not walk through the development of the underlying process, but you can view it in the illustration below. We will add the Info Callable Object to the Approve Staffing Request action. (See Getting Started with Guided Procedures Design Time at 550b0/frameset.htm for guidelines on developing processes.) 2

3 Publish Web Template Part You can use an SAP NetWeaver BI query, enterprise report or Web template, developed with the SAP Business Explorer (BEx) tools, to create a Guided Procedures callable object. Once you have developed the BEx Web-based output, you publish it to the SAP NetWeaver Portal as an iview. In this example, we are using a Web template developed in the BEx Web Application Designer, because we can create a tab-based dashboard with a variety of visualizations (tables, charts, maps, etc.), allowing us to combine all the information the manager needs in one Info Callable Object. In any case, the publishing steps are the same as for queries and enterprise reports. 1. From the main menu, select Web Template Publish to Portal, which opens the Export to Portal dialog. 2. In the dialog, select the Selection icon to open the Select a Folder dialog, which is a list of folders in the Portal Content Directory. 3

4 Publish Web Template Part In the dialog, drill down to the folder in which you want to store your iview and select Transfer. 2. In the Export to Portal dialog, select Execute to create the BI iview in the portal. 3. In the SAP NetWeaver Portal, assign the BI iview to a role as a Delta Link. (See Adding Objects as a Delta Link in the online help at dfb33eb1b/frameset.htm.) You may also choose to assign the iview to a page and then the page to the role. Putting the BI iview in a page allows you to combine the BI information with information from other sources. See the online help for: - Creating a Portal Page 405a/frameset.htm - Adding Content to a Page 05a/frameset.htm 4

5 Create iview Callable Object Part Once the BI iview is assigned to a role, you can use it to create a callable object. 1. In the GP Design Time Gallery, drill down to the selected folder and select Create Callable Object. 2. Select the Portal iview or Page type under User Interface. Enter the desired callable object Name and Description and select Next. 5

6 Create iview Callable Object Part Select the role to which you assigned your BI iview and select the iview from the resulting list. Select Next until you can select Finish. 6

7 Assign Callable Object as Info Callable Object 1 2 After creating the BI callable object, you need to assign it as an Info Callable Object to the appropriate action in your process. 1. Select your action and select Single Edit Mode. Select the You Can tab in the action details and select Add. 2. The Browse Items dialog appears. Drill down to your BI callable object and select Select to add it to your action as an Info Callable Object. 7

8 Update Runtime View The default runtime view does not include the You Can navigator, so you need to also update the process to the appropriate generic view. 1. Select your process template and select Single Edit Mode. Select the Runtime Views tab in the process details and select Add Generic View. 2. Select Process Activities (allows to view and execute activities and access activity related information and start ad hoc items) and select Add. 3. Select the radio button for the new view option in the Runtime Views tab. At this point, you have completed the Info Callable Object configuration. Select Save All and activate your process and complete your design. For more information on runtime views, see the online help for Defining Runtime Views at 106/frameset.htm. 8

9 Staffing Request Process: Enter Staffing Request You can now initiate the process in the GP runtime. In the first task, the requestor enters the pertinent information about the project and the staffing requirement. In this example, the requestor needs a Sr. Engineer 5 days a month for 5 months, starting in August. The requestor selects Complete to submit the request. For more information on the GP runtime, see the CAF Guided Procedures at Runtime online help at 106/frameset.htm. 9

10 Staffing Request Process: Approve Staffing Request Part Control of the process now moves over to the engineering department manager for the approval activity. 1. In the Tasks view of the GP runtime, the manager finds all open tasks for which he is the processor. The manager selects the Approve Staffing Request activity from the task list. 2. In the basic process, the manager reviews the request information, enters a response, and completes this step to send the process back to the requestor. With the BI Info Callable Object, the manager can optionally select the Staff Schedule information in the You Can navigator. 10

11 Staffing Request Process: Approve Staffing Request Part The system displays the BI iview in the process application area. To obtain a better view of the information, the manager selects Open in New Window. 11

12 Staffing Request Process: Approve Staffing Request Part The manager reviews the Staff Schedule Overview exception query from BI and can easily see that Ginger Garrison and Peter McKinney are both available. The manager selects the YTD Utilization tab for more information on which to base the staffing decision. (The manager might also review the Staff Schedule Details, if necessary, for example to see each employee s job level.) 5. In the Utilization chart, the manager sees that Ginger is behind the target of 75% utilization, and therefore a higher priority for assignment than Peter. When finished reviewing the BI information, the manager closes the window to return to the process and select Back (see illustration for step 3) to return to the base process. 12

13 Staffing Request Process: Approve Staffing Request Part In the Approve Staffing Request activity, the manager enters the response, identifying the selected employee and any other pertinent information and selects Complete. 13

14 Staffing Request Process: Review Response to Staffing Request 1 2 Control of the process now returns to the requestor. 1. In the Tasks view, the requestor finds all open tasks for which he is the processor. The manager selects the Review Response to Staffing Request activity from the task list. 2. The requestor reviews the engineering department manager s response and selects Complete to finish the process. 14

15 Copyright 2007 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. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge 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 and associated logos displayed 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. 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. 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 Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen. Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP -Produkts und ist für SAP nicht bindend, einen bestimmten Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts. SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit. Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab. Alle Rechte vorbehalten. 15