49
UP116 SAP NetWeaver Visual Composer – Case Study: CATS Time Entry at the Montreal Airport

Up116 Vc Case Study

Embed Size (px)

DESCRIPTION

SAP Visual Composer

Citation preview

Page 1: Up116 Vc Case Study

UP116SAP NetWeaver Visual Composer – Case Study: CATS Time Entry at the Montreal Airport

Page 2: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 2

Contributing Speaker

Vincent DesrochersNetweaver Consultant, The Createch Group

Page 3: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 3

Learning Objectives

As a result of this workshop, you will be able to:Use Visual Composer to build SAP user interfaces that are simple and powerful with a development technology that is as easy as drag and dropIntegrate point technologies within the Portal using Visual Composer Avoid the pitfalls of Visual Composer Adapt the portal configuration to a touch screen UIObserve that a Single Sign-On was set-up between Windows and the PortalEvaluate Project costing and resource allocation for a project that involves a Visual Composer element and the Back-end system using a secure Airport Pass

Page 4: Up116 Vc Case Study

Technical elements of Visual Composer/Portal

Costing & Resource considerations

CATS Time Entry Project – Business Context

Presentation of the application

Page 5: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 5

Montreal Airports in a Few Words

Non profit corporationManagement of two airports (Dorval and Mirabel)11 million passengers235 000 aircraft movementsComplex similar to a small city– Police and fire services– Building, electrical, plumbing,

grounds/road, vehicle fleetmaintenance

– 600 employees

Page 6: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 6

The Project

Goal of the project :Implementation of a solution enabling blue collar workers to enter theirown time

Particularity of the project :Since users are maintenance employees whorarely use a computer, reduce validation stepsby simplifying time entry screen

Targeted number of users:Pilot project – 7 employeesDeployment to up to 200 employees

Page 7: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 7

Context And Business Needs

Time entry context :Maintenance and project management employees enter hours workedon work orders (PM) and on projects (PS), as well as exceptionsAll other employees enter only exceptions

Business needs :CATS used for time entry Two existing CATS reports used:– Time display– Hour bank balance

No modification to HR-CATS configuration

Page 8: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 8

The Required Solution

The solution must facilitate use of the following functions :User authentificationAutomatic booting of ADM applicationEntering appropriate information – time entryConsulting time and hour bank balance information Automatic log off, if required

Page 9: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 9

Employeewrites down

hours worked

Supervisorvalidatesand signstime card Clerk enters

data intoSAP-HR

(trx:CAT2 )

Data getsvalidated by

CAT2 trx

Old Process

Employeeforwards histime card to

supervisor for approval

Supervisorhands over time card to

clerk

Page 10: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 10

Data getsvalidated by

CAT2 trx

New Process

Page 11: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 11

New ProcessData gets

validated by the new front-

end

Page 12: Up116 Vc Case Study

Technical elements of Visual Composer/Portal

Costing & Resource considerations

CATS Time Entry Project – Business Context

Presentation of the application

Page 13: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 13

Page 14: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 14

Time Entry Screen Cam

Page 15: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 15

Time Entry Screen Cam With Error Message

Page 16: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 16

Time Entry Screen

Page 17: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 17

Time Entry Screen Shots

Page 18: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 18

Time Entry Report

Page 19: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 19

Time Entry Report

Page 20: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 20

Time Quota Report

Page 21: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 21

Time Quota Report

Page 22: Up116 Vc Case Study

Technical elements of Visual Composer/Portal

Costing & Resource considerations

CATS Time Entry Project – Business Context

Presentation of the application

Page 23: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 23

Time Entry – Technical Summary

Time entry system for blue collar employees at Montreal Airport

Virtual keyboard software installed on the workstation but controlled by the portalReplacement of the R/3-HR CAT2 transaction with a simplified Web version using NetWeaver Visual Composer as the development toolIn real-time with R/3 (CATSDB table) using standard BAPIS which automatically applies HR and PM configuration as well as ADM user-exitsUse of SAP Netweaver Portal, more specifically to control window and NetWeaver Visual Composer display for the development of the banner and time entry screenNo modifications required to the configuration and user-exits

Page 24: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 24

SAP Netweaver Enterprise Portal – 1

Universal access to all SAP and Non-SAP systemsBased on WAS ABAP (such as ECC, CRM, BI, SRM)Based on a Windows-type access such as file systems, Outlook, external website using Microsoft Active DirectoryWebsite with authorization (web mail, for instance)

Document management platform (KM)A unique view on an assorted collection of documents supported by a powerful and flexible search engine (TRex)

Synchronous and asynchronous collaboration platform

Almost everything is done through configurationHowever, multiple development methods (NetWeaver Visual Composer,WebDynpro, Java)

Safe, flexible and integrated with surrounding systems

Page 25: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 25

SAP Enterprise Portal – 2

Roles – PCDDetermines who has access to the application – determination of roles and groupsAllows integration of NetWeaver Visual Composer, HTML and Webguicomponents (R/3 transactions)Controls display Manages SAP access (single sign-on)

Page 26: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 26

NetWeaver Visual Composer – 1

Graphical tool for the development of time entry screen and banner – Requires almost no programmingIs an integral part of NetWeaver 2004s Enterprise Portal– Minimal prerequisites for developer seats

Can interface either SQL, RFC (BAPI) or Web service, BI requesttransactionsGenerates packages (executable files) and iViews (portal windows) and deploys them on the portalExtremely rapid for prototyping, demos and proofs of concept Screen can be modified in real time with clientGenerates Webdynpro or Flash UI (Adobe)

Page 27: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 27

Architecture Summary

WAS 7.0 Portal Server :HTML Pages (at WAS level)NW04s Enterprise Portal

RolesDisplayiViews PageNetWeaver Visual Composer

- Entry screen- Banner

ITSWebgui

MS-ADSEnterpriseDirectory

CATSDB

Client workstationVirtual keyboardCard readersoftware -SphinxInternet ExplorerWindows

TRXCATS_DAPT_QTA10

BAPIS & RFC

R/3 4.7

Page 28: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 28

Single Sign-on Between Windows And Portal

The Airport security card contains a number that ismatched with the sphinx server

Time entry terminals are within restricted areaEmployees do not need to change or modify their access passThe sphinx server contains user names/passwords to access WindowThe same user name and password is provided to the portal login screen applications at logon time

Page 29: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 29

Single Sign-on Between Portal And R/3 Back-end

Single Sign-On between Portal and back-end R/3 (4.7)Based on User mapping

Once back-end is migrated to WAS 7.0 :Phase II project will implement SP nego with Kerberos infrastructure –as recommended by SAP for optimum performance – to allow user names that are compatible between R/3 and MS-ADS infrastructure which also supplies user names and passwords for the portal

Page 30: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 30

Main Page Technical Details

Execute a javascript which in turncalls a local (on the terminal) Vbscript to close the session

Visual Composer application screen

URLs Pointing on Portal pages (portal object) for the variousfunctions

HTML located on the portal WAS, called by an iview

Page 31: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 31

Entry Screen – NetWeaver Visual Composer Model

Page 32: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 32

Entry Screen – NetWeaver Visual Composer Model

Containscalendar to select date

Script displayingvirtualkeyboard

Hide virtualkeyboard

Printingpop-up

Pop-upList of activity

Operationcode (based on order)

Messages table

BAPI to obtainemployee’stime sheet

Table containingtime sheet

BAPI to post time sheet

Cancelconfirmpop-upPrint &

Save Button

Page 33: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 33

A Pop-up in Detail

Page 34: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 34

A Pop-up in Detail

Page 35: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 35

Virtual Keypad Element – How We Integrated Into VC

// This script called by Visual composer and located and the WAS server will // move the virtual keypad inside the main screen

<script language="javascript" type="text/javascript">

function runCmd(cmd)

{

var shell = new ActiveXObject("WScript.shell");

shell.run(cmd, 1);

}

runCmd('C:\\BAB\\utilitaires\\MOVEWMTS.exe x:465 y:342')

</script>

Page 36: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 36

How To Exit The Time Entry Application And Go Back to The Main Portal Framework Page (Main Menu)

<script language="JavaScript">

if (window.top != self)

{window.top.location.replace(self.location);}

window.location.replace('/irj/portal')

</script>

Page 37: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 37

CATS BAPIS – BACK - END

Use to fill pick list of activity type and operations

Z_BAPI used as wrapper around CATS time entry standard BAPISBAPI_CATIMESHEETMGR_INSERTBAPI_CATIMESHEETMGR_DELETEBAPI_CATIMESHEETMGR_CHANGE

CUSTOM To print the report to nearest printer (LOCL setting)

BAPI BAPI_USR01DOHR_GETEMPLOYEE use in various Z_BAPIS and by Visual Composer model directly

Page 38: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 38

Error Handling

Limited number of input fields to enterPick list used as often as possible to avoid wrong inputAll error messages handled at the configuration level for business rulesExtra messages for successful attempt are created at the BAPI level

Page 39: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 39

Technical Challenges Encountered And Solved

Limited functionnalities of NetWeaver Visual Composer in SPS08 –Upgrade to SPS09 allowedLimitation of NetWeaver Visual Composer with respect to the user interface parameters (unable to select font size)Integration of the virtual keyboard – elegant final solutionBug in the dynamic drop-down list in NetWeaver Visual Composer –Alternately used pop-up SSO Windows – PortalUser name differs from the portal to R/3 – employed user mappingKM not available at initial installation – alternate use of WAS to store html pageWhen exiting the time entry screen (a vc application), the whole main window was contain only in the portion of the time entry screen

Page 40: Up116 Vc Case Study

Technical elements of Visual Composer/Portal

Costing & Resource considerations

CATS Time Entry Project – Business Context

Presentation of the application

Page 41: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 41

Timeline of The Project

Analysis phase (beginning of Aug. 2006)Accepted proof of concept (Sept. 5, 2006)Development phase (Sept. and Oct. 2006)QA and training (beginning of Nov. 2006)Go live (Nov. 16, 2006)

Duration : 3 months

Page 42: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 42

Resources Involved in The Project

Consulting firm Montreal Airport employees

1 Portal Consultant full-time

1 Portal consultant half-time

1 ABAP Consultant part-time

1 BASIS Consultant for installation

Total : 100 days (approx.)

1 Basis @ one to two days/week

1 Functional Analyst @ one day/week for analysis, executionand QA

1 Project Leader @ one day/week

Total : 50 days (approx.)

Page 43: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 43

Benefit to ADM

Reduce delaysRelocation, payroll processing and closing work orders

Eliminate work duplicationEntry, approval, validationFree clerks and supervisors to perform more strategic tasks

Reduce costsTime card printing

Use consoles for other Portal servicesSYMDUT material safety data sheets, orders, notices

Infrastructure ready for other projectsMobile technology, portal, integration with other software

Page 44: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 44

Success Factors

Implication of the blue collar employees in definition of needs, implementation and training (they are convinced of the benefitsof the project)Maintain focus on simplicity and ease of useNo modification to business processesNo modification to HR-CATS and PM configurationInforming client of innovation risks facilitates decision makingand allows to maintain focus on the essentials

Page 45: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 45

Summary

Visual Composer is prime time ready for applications that require the simplest user interface to complex transactional data

Transactional applications become easier to develop and deploy with the addition of Visual Composer to the NetweaverEnterprise Portal

Integration of many components is possible with both the portal and Visual Composer Infrastructure

Netweaver Visual Composer opens new horizons for portal development without a steep learning curve

SAP is devoting considerable effort in this direction

Page 46: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 46

Further Information

SAP Public Web:SAP Developer Network (SDN): www.sdn.sap.comBusiness Process Expert (BPX) Community: www.bpx.sap.com

Related Workshops/Lectures at SAP TechEd ’07CE106 , Modeling with SAP NetWeaver Visual Composer – Status and Outlook ,

CE153 , Modeling in Visual Composer for SAP NetWeaverComposition Environment ,

Related SAP Education and Certification Opportunitieshttp://www.sap.com/education/

Page 47: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 47

THANK YOU FOR YOURATTENTION !

QUESTIONS – SUGGESTIONS – DISCUSSION

Q & A

Page 48: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 48

Please complete your session evaluation.

Be courteous — deposit your trash, and do not take the handouts for the following session.

Feedback

Thank You !

Page 49: Up116 Vc Case Study

© SAP AG 2007, SAP TechEd ’07 / UP116 / 49

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.

Microsoft, Windows, Excel, 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, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

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.