You are on page 1of 57

Advanced Features of SAP BW Reporting Authorizations

Session 709 Amelia Lo
Platinum Consultant, SAP NetWeaver RIG SAP Labs, LLC

Learning Objectives

As a result of this workshop, you will be able to:
„ Have a good handle of the most misunderstood features of

the BW Reporting Authorization
‹ Understand ‹ Understand

how authorizations variable works how hierarchy node variable works

„ Learn the new functionality and new BW Authorizations

Objects in BW3.0
„ Learn the basics of Planning and Strategize BW

Authorizations
„ Know the dos and don’ts on BW Authorizations

© SAP AG 2003 ASUG BITI Forum Session 709, Amelia Lo / 2

SAP NetWeaver™

The integration and application platform for lower TCO

SAP NetWeaver™
People Integration
Multi-Channel Access Composite Application Framework Portal Collaboration Life Cycle Management

Unifies and aligns people, information and business processes
„ Integrates across technologies and organizational boundaries „ A safe choice with full .NET and J2EE interoperability

Information Integration
Business Intelligence Knowledge Management

Master Data Management

Process Integration
Integration Broker Business Process Management

The business foundation for SAP and partners
„ Powers business-ready solutions that reduce custom integration „ Its Enterprise Services Architecture increases business process flexibility

Application Platform
J2EE ABAP

DB andOS OS Abstraction Abstraction DB and


© SAP AG 2003 ASUG BITI Forum Session 709, Amelia Lo / 3

.NET

WebSphere

Don’t Miss the SAP Business Solutions Tour!
Your chance to see SAP NetWeaver in action – see live demonstrations of: „ SAP Enterprise Portal „ SAP Business Information Warehouse „SAP Exchange Infrastructure „ SAP Web Application Server „ SAP Mobile Infrastructure „ SAP Master Data Management 30-minute tour timeslots available
„ Monday „ Tuesday 10:30 – 5:10 9:40 – 5:30

„ Wednesday 8:00 – 12:00

Located at Wyndham Hotel Parking Lot

© SAP AG 2003 ASUG BITI Forum Session 709, Amelia Lo / 4

Agenda

Special Topics on BW Reporting Authorizations Planning & Strategize BW Authorizations What’s New in BW 3.0 The Dos and Don’ts

© SAP AG 2003 ASUG BITI Forum Session 709, Amelia Lo / 5

Amelia Lo / 6 .0 The Dos and Don’ts © SAP AG 2003 ASUG BITI Forum Session 709.Agenda Special Topics on BW Reporting Authorizations Planning & Strategize BW Authorizations What’s New in BW 3.

Amelia Lo / 7 .Special Topics of BW Reporting Authorizations A Quick Review of BW Reporting Authorizations A few most misunderstood Features „ Variable filled Authorizations „ Important parameter when use Global Variable Customer Exit „ Hierarchy Authorizations with Compound Characteristics Tracing Authorizations in BW © SAP AG 2003 ASUG BITI Forum Session 709.

Amelia Lo / 8 .Open Data Warehouse Architecture © SAP AG 2003 ASUG BITI Forum Session 709.

InfoArea. InfoObject. Query…) „ Unique SAP BW Authorization Tool to administer BEx Reporting data security „ It is possible to use variable security runtime parameters „ It is possible to generate profiles from datasources © SAP AG 2003 ASUG BITI Forum Session 709.SAP R/3 vs. Amelia Lo / 9 . BW Authorizations What’s the same „ Role Based Security Authorizations ‹ ‹ ‹ ‹ ‹ Users are assigned roles Roles contain profiles Profiles contain authorizations Roles are maintained using same tool (“PFCG” transaction) Can be administered via CUA (Central User Administration) „ Authorization objects define specific permissions „ There are standard authorization objects available in the system What’s different „ Unique BW Objects (InfoProvider.

Amelia Lo / 10 Production Production Data Data Extractor Extractor OLTP OLTP Reporting Reporting R/3 R/3 OLTP OLTP Applications Applications .Authorization Concept Overview Bex Bex Browser Browser Bex Analyzer Bex Bex Analyzer Analyzer Query Query Designer Designer Web Web Appl Appl Designer Designer Web Web Report Report Analyzer 3rd 3rd party party OLAP OLAP client client Bex Query Designer 3 2 Administrator Workbench Administration Administration Scheduling Scheduling Monitor Monitor Meta Data Repository OLAP OLAP Processor Processor Business Explorer Meta Meta Data Data Manager Manager Data Data Manager Manager InfoCubes Business Information Warehouse Server Staging Staging Engine Engine BAPI ODS 1 Non Non R/3 R/3 Production Production Data Extractor Data Extractor Non Non R/3 R/3 OLTP OLTP Applications Applications © SAP AG 2003 ASUG BITI Forum Session 709.

Types of BW Authorizations Systems Communication Authorizations Administration „ Concept very close to standard R/3 „ all authorization relevant objects are delivered by SAP „ Pre-defined Templates can be used as a starting point „ Administration of authorizations like in R/3 Reporting „ no authorization relevant object definition is delivered „ set of tools to define customer specified concept embedded in SAP BW administration © SAP AG 2003 ASUG BITI Forum Session 709. Amelia Lo / 11 .

REPORTING Object Object Object Object Field Field Field Field Value Value © SAP AG 2003 ASUG BITI Forum Session 709. Amelia Lo / 12 Value Value .SAP BW Authorization Overview User User Role Role Profile Profile Authorization Authorization Profile Profile Generator Generator AUTHORIZATION OBJECT CLASS: BUSINESS INFORMATION WAREHOUSE-Administration WAREHOUSE WAREHOUSE-Administration AUTHORIZATION OBJECT CLASS: BUSINESS INFORMATION WAREHOUSEWAREHOUSE.

..n 1.10 Key Figure Object (1KFYNM) Authorization Relevant Characteristic Hierarchy Node • Only “one” 0TCTAUTHH per Reporting Authorization Object • Many Hierarchy Authorizations can be entered characteristic 0...10 0TCTAUTHH 0ORGUNIT 0Costcenter 0Profitcenter <.SAP BW Reporting Authorizations Objects 0.m 0...1 < Authorization Object > <field 1> <field 2> <..> SAP BW InfoProviders SAP BW Objects © SAP AG 2003 ASUG BITI Forum Session 709.. Amelia Lo / 13 .n 0..> 0..

Include 0TCTAUTHH and leaf Characteristics. 4 Create Authorizations with the values © SAP AG 2003 ASUG BITI Forum Session 709. • If Hierarchy authorization required. 3 Create Hierarchy Authorizations • Define a description of a hierarchy authorization.Steps to Create Reporting Authorizations 1 2 Mark characteristics as "Authorization Relevant” Create an Authorization Object for Reporting (Transaction: RSSM) • Include required “Authorization Relevant Characteristics” • If key figure authorization required. Amelia Lo / 14 . include 1KYFNM. Enter the technical name of the description of a hierarchy authorization as value for field 0TCTAUTHH. • Create an authorization for the new authorization object.

Amelia Lo / 15 .Mark InfoObject Authorization Relevant 1 © SAP AG 2003 ASUG BITI Forum Session 709.

Authorizations 2 © SAP AG 2003 ASUG BITI Forum Session 709. Amelia Lo / 16 .

Create Authorization Object for Reporting 2 © SAP AG 2003 ASUG BITI Forum Session 709. Amelia Lo / 17 .

Amelia Lo / 18 .Authorization Definition for Hierarchy 3 © SAP AG 2003 ASUG BITI Forum Session 709.

Amelia Lo / 19 .BW Reporting Object in a Profile & Assign Value < Authorization Object > 4 0EMPLOYEE 0ORGUNIT 0TCTAUTHH © SAP AG 2003 ASUG BITI Forum Session 709.

Amelia Lo / 20 .Special Topics of BW Reporting Authorizations A Quick Review of BW Reporting Authorizations A few most misunderstood Features „ Variable filled Authorizations „ Important parameter when use Global Variable Customer Exit „ Hierarchy Authorizations with Compound Characteristics Tracing Authorizations in BW © SAP AG 2003 ASUG BITI Forum Session 709.

Create Authorizations Variables VARIABLE WIZARD IN BEx Hierarchy Node Variable Characteristic Variable © SAP AG 2003 ASUG BITI Forum Session 709. Amelia Lo / 21 .

Amelia Lo / 22 .Authorization Variables of Customer Exit type 1 Create Variable z 2 Assign Variable to Query © SAP AG 2003 ASUG BITI Forum Session 709.

..> < RA_OBJ2 > Orgunit <. RA_OBJ2 contains HR_US & HR_ASIA • Both Reporting Authorization Objects are assigned to User Amelia’s Profile RESULT: Amelia have authorization to view “HR_US” ONLY !!! < RA_OBJ1 > Orgunit <.> HR_EMEA HR_US OSS note 653383 HR_ASIA © SAP AG 2003 ASUG BITI Forum Session 709..Use of Variable filled Authorizations Scenario 1 SCENARIO: • You defined two Reporting Authorization Objects with same authorization relevant characteristic (0ORGUNIT) • RA_OBJ1 contains values HR_EMEA & HR_US. Amelia Lo / 23 ..

Amelia Lo / 24 .Use of Variable filled Authorizations – Scenario 1 Possible Approach: Define one Reporting Authorization Object and populate the values in one of the following ways: • • • Manually populated in the profile Automated authorizations generation from the authorizations ODSs Derive the values via the authorizations Users Exit (RSR000001) < RA_OBJ > Orgunit <.> HR_EMEA HR_US HR_ASIA OSS notes 653383 557924 © SAP AG 2003 ASUG BITI Forum Session 709...

4. Use transaction “CMOD” to develop User Exit “RSR00001”. Function Module: EXIT_SAPLRRS0_001 Maintain Customer Authorization Return Table as required Result Create Authorization Variable Include Variable in your query Authorization Check Query with authorizations varaible 2. 3. Amelia Lo / 25 . $VAR $VAR initiates User exit Read Customer AUTH Table User Exit “RSR00001” Structure: RRRANGEEXIT ZAUTH © SAP AG 2003 ASUG BITI Forum Session 709.Maintain Global Variable for Authorization: via User Exit 1.

Variable appears once more © SAP AG 2003 ASUG BITI Forum Session 709.Be Aware Your Import Parameter Specification I_Step Values: „ I_Step = 0 -> Enhancement is not called (Default) „ I_Step = 1 -> Enhancement is called up before Variable Entry „ I_Step = 2 -> Enhancement is called up after Variable Entry „ I_Step = 3 -> Called up to check the Variable Value. Amelia Lo / 26 .

Compounded Hierarchy Authorizations .Scenario 2 SCENARIO: • You defined a Reporting Authorization Objects for a Hierarchy with Compounded characteristics (0CO_Area and 0CostCenter) • You filled the authorizations variable with “Flat Values” for 0Costcenter RESULT: Brain 804 “no authorization” Solution: Define and use Hierarchy Node Variable < Authorization Object > 0CO_Area 0Costcenter 0TCTAUTHH © SAP AG 2003 ASUG BITI Forum Session 709. Amelia Lo / 27 .

Special Topics of BW Reporting Authorizations A Quick Review of BW Reporting Authorizations A few most misunderstood Features „ Variable filled Authorizations „ Important parameter when use Global Variable Customer Exit „ Hierarchy Authorizations with Compound Characteristics Tracing Authorizations in BW © SAP AG 2003 ASUG BITI Forum Session 709. Amelia Lo / 28 .

Amelia Lo / 29 .Tracing Authorizations ST01 SU53 RSSM © SAP AG 2003 ASUG BITI Forum Session 709.

Tracing Authorization: Overview Trace functionality embedded in SAP R/3 basis „ Recording of authority checks for system (Transaction ST01) „ Display the last failed authority check of user (Transaction SU53) SAP BW reporting authority trace* „ set up user related trace recording for OLAP authority checks Transaction RSSM *Authorizations checked against Reporting Objects are not supported with standard trace functionality's © SAP AG 2003 ASUG BITI Forum Session 709. Amelia Lo / 30 .

Recording of Authority Checks 1 2 3 4 5 Start Transaction ST01 Configure detail of trace recording Activate trace Perform actions on system Analyze trace using transaction ST01 Note: Trace ST01 can be used either in BW and R/3 source system. Amelia Lo / 31 . © SAP AG 2003 ASUG BITI Forum Session 709.

Amelia Lo / 32 .Recording of Authority Checks 3 2 5 © SAP AG 2003 ASUG BITI Forum Session 709.

SAP BW Reporting Authority Trace 1 2 3 4 5 Start transaction RSSM in SAP BW Choose Authorization trace from Authorization object reporting menu or locate it from the bottom of the screen. Insert user Perform reporting activity Analyze trace 5 3 2 © SAP AG 2003 ASUG BITI Forum Session 709. Amelia Lo / 33 .

0 The Dos and Don’ts © SAP AG 2003 ASUG BITI Forum Session 709.Agenda BW Authorizations Overview Planning & Strategize BW Authorizations What’s New in BW 3. Amelia Lo / 34 .

Amelia Lo / 35 .Guiding Principals Integrate in your Development Life Cycle „ Plan Authorizations Early on in your Development Life Cycle „ Authorizations requirement collection at Blue Print Phase „ Identify and Assign Data Ownership KISS Principal (Keep it Simple and Small) „ A balance act among Granularity vs. Performance „ Design for simplicity and Ease of Maintenance without compromising “Mandatory” data security „ Divide user into Groups and manage security at InfoArea or InfoProvider level Thorough Authorizations Testing „ Must be a part of system Integration Test plan „ Performance testing is a essential part of test plan Staffing for BW Authorizations „ R/3 Authorization expert does not equivalent to BW Authorizations Experience „ Segregation of Duties among BW Users and Administrator © SAP AG 2003 ASUG BITI Forum Session 709. Maintenance vs.

12. 11. 4. 7. 6. consider using Authorizations Variable to ease maintenance © SAP AG 2003 ASUG BITI Forum Session 709. Amelia Lo / 36 . 2. 14. Define BW Reporting Objects for InfoObjects per step 6 Consider using Hierarchy node authorization based on user access pattern For complex & detailed authorizations needs. 3.BW Authorizations Roadmap (I) Develop Authorizations Strategy 1. Consider company policy: Consider Legal requirements Classify types of users & required roles Consider Proof of Concept phase to valid complex authorization model Define Data Ownership and Responsibility Develop questionnaire for blue print Document requirements in Matrix Develop naming convention for Authorization Design the Roles – consider segregate Activities from Data Access roles Use SAP delivered templates as the baseline Revise to meet your requirements Develop Authorizations Matrix to collect authorization requirement for blue print phase 5. 8. Define BW reporting authorizations 13. 9. Define BW Authorization for Admin workbench 10.

Develop BW User Security request and approval processes Consider a Web-based authorization request workflow and user guide Develop a BW Security Administration checklist Define Periodic BW Security Reviews and Assessment Process Conduct BW Authorization Training 22. © SAP AG 2003 ASUG BITI Forum Session 709. 20. Develop performance test plan and establish the test environment and data volume 17. BW Authorizations Training for Security Administrators Include BW Authorizations impact on data access as a part of the BW user training. Amelia Lo / 37 . 21. 23. Incorporate BW Authorizations testing in the overall SAP System Tests (R/3 and non R/3). 19.BW Authorizations Roadmap (2) Testing BW Authorizations Testing 15. Develop Administrative and Monitoring Process for BW Authorizations 18. Develop detailed test scenarios and plan Involve Business in authorizations testing 16.

Amelia Lo / 38 .0 The Dos and Don’ts © SAP AG 2003 ASUG BITI Forum Session 709.Agenda BW Authorizations Overview Planning & Strategize BW Authorizations What’s New in BW 3.

New in Authorization Objects. Frontend (3. Amelia Lo / 39 .0) S_RS_COMP „ New Authorizations Check for Variables in Query Definition „ Object type is ‘VAR’ S_RS_COMP1 „ Is checked additionally with S_RS_COMP „ Checks for authorizations on query components dependent on the owner (creator RSZOWNER) „ Authorizations are necessary. for creating queries S_RS_FOLD „ Suppress InfoArea view of BEx elements „ Specify ‚X‘ (true) in the authorization maintenance for suppressing © SAP AG 2003 ASUG BITI Forum Session 709. e.g.

New Authorization Objects. Amelia Lo / 40 . Add the activity 60 (upload) © SAP AG 2003 ASUG BITI Forum Session 709. Backend (3.0) S_RS_IOBJ „ Authorization object for working with InfoObjects „ Is checked if authorization is not available via S_RS_ADMWB „ Additional checks for update rule authorizations S_RS_ISET „ For displaying / maintaining InfoSets (new object in BW) S_RFC „ Authorization for GUI activities „ Add following RFC_NAMEs with RFC_TYPE ‚FUGR‘ and ACTVT ‚16‘ ‹ RRXWS: BW Web Interface ‹ RS_PERS_BOD: Personalization of Bex Open Dialog ‹ RSMENU: Roles and Menus S_GUI „ Authorization forGUI activities.

Automated Authorization Generator Sourced from Two types of ODS Objects „ Authorization Value ODS „ Hierarchy ODS ODS Population „ From R/3: HR Structural Authorizations „ From R/3: Cost Center (BW 3.1 content) „ From Flat Files New RSSM User Interface © SAP AG 2003 ASUG BITI Forum Session 709. Amelia Lo / 41 .

Automated Authorization Generation: the Architecture < Auth Object > Tcode: Tcode: RSSM RSSM – – Generate Generate Authorization Authorization BW Metadata 0TCTAUTHH 0ORGUNIT 0EMPLOYEE Value 0TCA_DS01 Hierarchy 0TCA_DS02 Text 0TCA_DS03 User Assign 0TCA_DS04 ODS-Objects Update Rules Value Value InfoSource Mapping & Transfer Rules DataSource Mapping & Transfer Rules DataSource SAP BW Server replicated Metadata BW S-API File File © SAP AG 2003 ASUG BITI Forum Session 709. Amelia Lo / 42 Other Other R/3 R/3 .

HR Structural Authorizations © SAP AG 2003 ASUG BITI Forum Session 709. Amelia Lo / 43 .

Amelia Lo / 44 .BW/HR Structural Authorizations What’s BW/HR Structural Authorizations „ Bring R/3 Structural Authorizations to BW via Standard Extraction „ Associate with BW Authorizations via execution of special Module „ Full Refresh on a Customer Selected Frequency Key Benefits „ Reduced the Redundant Security Setup „ Provide Cross System Consistency © SAP AG 2003 ASUG BITI Forum Session 709.

Structure T77PR Profile R H B A U S 0 0 Transfer Rules Struc Auth Security Check INDX Cluster (0HR_PA_2 & 0HR_PA_3) Data Sources T77UA Assignment 0HR_PA_2 Data Source Update Rules 0HR_PA_3 Data Source T77UU User Struc Auth ODSs RSSM Trans OR Program Modules RSSB_Generate _Authorizations PSA PSA 0PA_DS02 0PA_DS03 R/3 OLTP © SAP AG 2003 ASUG BITI Forum Session 709.Structural Authorization in BW PSA R/3 Org. Amelia Lo / 45 BW .

Amelia Lo / 46 .12 Steps to Install Structural Authorizations 1 2 Create Structural Authorization Profile (IMG or TR-OOSP) Assign User to Profile (IMG or TR-OOSB) Update T77UU table to include User Name Execute program RHBAUS00 to create INDX Activate 0HR_PA_2 & 3 DataSource in R/3 and BW Activate or Create 0HR_PA_2 & 3 InfoSource & Communication Structure 3 4 5 6 © SAP AG 2003 ASUG BITI Forum Session 709.

12 Steps to Install Structural Authorizations 7 Activate and load ODS from R/3 8 Activate Target InfoObjects “Authorization Relevant” 9 Create Authorization Object (Transaction Code: RSSM) 10 Use Transaction code: RSSM or Execute RSSB Function Modules to generate BW Authorization Create Authorization Variables Create Query with Authorization Variables 11 12 © SAP AG 2003 ASUG BITI Forum Session 709. Amelia Lo / 47 .

Relevant • Define Reporting Auth Object via RSSM • Use 0TCA_DS01 as template • ODS name must be xxxx_DS01 • Use 0TCA_DS02 as template • ODS name must be xxxx_DS02 •The data format = yyyymmdd or per Your Default Format •Several Objects can define as constant • RSSM: Find your ODSs & Mark Auth Obj • Exec RSSB_Generate_Authorizations • Define Variables for Auth InfoObjects • Include Variables in your Queries Define Reporting Object Create Authorization Value Infosoure & ODS Create Authorization Hier Infosoure & ODS Create Update Rules for ODS Loads Generate Profiles via RSSM or RSSB program Create Authorizations Variable in Query Def.Steps to Create Authorization from Flat Files 0 1 2 3 4 5 6 Planning & Mapping • Determine what you want to secure • Mapping Objects & create Flat file • Mark InfoObjects Auth. © SAP AG 2003 ASUG BITI Forum Session 709. Amelia Lo / 48 .

000 checking Alternatives „ For top executives: setup a role to give full authorizations „ Use Hierarchy variables for queries initial view with Hierarchy „ Use RSR00001 User exit against the populated ODSs How To Paper „ HTTP://WWW.Tips & Hints for Automatically Generated Authorizations Performance „ If you have very large number of values in your user master record.000 EE X 5 objects = 1. Amelia Lo / 49 .000. the query performance will be significantly impacted „ It is a multiplication effect of: # authorization objects X # values X „ Ex: 20 orgunits X 10.SAP.Service.com/BW -> Service & Implementation -> How to Papers ‹ ‹ BW/HR Authorizations Generate Authorizations Profile from Flat File © SAP AG 2003 ASUG BITI Forum Session 709.

0 The Dos and Don’ts © SAP AG 2003 ASUG BITI Forum Session 709.Agenda BW Authorizations Overview Planning & Strategize BW Authorizations What’s New in BW 3. Amelia Lo / 50 .

Dos and Don’ts Dos „ „ „ Keep the four guiding principals in mind when planning BW authorizations Consider a Proof of Concept phase for complex authorizations model Check out OSS Notes on Authorizations „ Apply BW 3. Amelia Lo / 51 .0B SP15 for performance enhancement & corrections „ Note 625049: Improved performance „ Note 315094: Authorization recommendation „ „ Check out the BW Online document on Security with Scenarios Use caution when request of user query publishing in Production „ Limit number of users authorized „ Setup specific user published reporting roles with administrative process (clean-up) and alert users as “Uncertified Reports” © SAP AG 2003 ASUG BITI Forum Session 709.

names.Dos and Don’ts Dos „ Create an effective OSS Message for authorizations „ Prepare a query which is as simple as possible and still reproduces the error „ Prepare a SAP_ALL user and a restricted user. Don’ts „ Don’t setup Field level specific security just because you’ve been asked – Challenge the requester for legal or policy requirements © SAP AG 2003 ASUG BITI Forum Session 709. „ open the system. Amelia Lo / 52 . „ don't forget to give all the necessary information: usernames. passwords. System. „ If you use variables (customer exits) replace their content into profile of the restricted user „ (we do not support customer code) „ explain clearly what you expect to see and what the error is.

VP SAP NetWeaver Consulting Practice (r. Business Information Warehouse Authorizations Î Related Workshops/Lectures at ASUG BITI Forum 2003 © SAP AG 2003 ASUG BITI Forum Session 709.sap.service.com/solutions/bi/ SAP Customer Services Network: www.com/usa/education/ BW 365.com) Î Related SAP Education Training Opportunities http://www.sap.Further Information Î Public Web: www.com/BW Î Consulting Contact Roy Wood. Amelia Lo / 53 .wood@sap.sap.

Amelia Lo / 54 .Questions? Q&A © SAP AG 2003 ASUG BITI Forum Session 709.

and do not take the handouts for the following session.Feedback Please complete your session evaluation and drop it in the box on your way out. © SAP AG 2003 ASUG BITI Forum Session 709. Amelia Lo / 55 . Be courteous — deposit your trash.

OSF/1®.. WINDOWS®. pSeries. XML. EXCEL®. © SAP AG 2003 ASUG BITI Forum Session 709. MVS/ESA. Intelligent Miner. Inc. MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems. „ IBM®. iSeries.Copyright 2003 SAP AG. X/Open®. „ Citrix®. 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. AFP. DB2 Universal Database. Inc. „ UNIX®. Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries. WinFrame®. „ ORACLE® is a registered trademark of ORACLE Corporation. R/3. Word®. „ JAVASCRIPT® is a registered trademark of Sun Microsystems. NT®. mySAP. „ MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. S/390®. „ Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. OS/390®. Parallel Sysplex®. z/OS. „ Microsoft®. DB2®. XHTML are trademarks or registered trademarks of W3C®. DHTML. OS/400®. „ SAP. used under license for technology invented and implemented by Netscape. WebSphere®. VideoFrame®. The information contained herein may be changed without prior notice. World Wide Web Consortium. PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. Program Neighborhood®. xSeries. zSeries. „ JAVA® is a registered trademark of Sun Microsystems. Tivoli®. and Motif® are registered trademarks of the Open Group. Massachusetts Institute of Technology. the Citrix logo. mySAP. AIX®. xApp 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. AS/400®. All other product and service names mentioned are the trademarks of their respective companies.com. ICA®. Amelia Lo / 56 . MetaFrame®. OS/2®. Inc. xApps. Netfinity®. „ HTML.

R/3. MultiWin® und andere hier erwähnte Namen von Citrix-Produkten sind Marken von Citrix Systems. OS/400®. zSeries. NT®. OS/390®. XML. das Citrix-Logo. MetaFrame®. DB2 Universal Database. DB2®.com. Inc. „ UNIX®.Copyright 2003 SAP AG. ohne die aus-drückliche schriftliche Genehmigung durch SAP AG nicht gestattet. AS/400®. „ HTML. „ Citrix®. Inc. „ IBM®. World Wide Web Consortium. iSeries. AFP. © SAP AG 2003 ASUG BITI Forum Session 709. xApp und weitere im Text erwähnte SAP-Produkte und –Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderen Ländern weltweit. Tivoli®. VideoFrame®. Massachusetts Institute of Technology. PowerPoint® und SQL Server® sind eingetragene Marken der Microsoft Corporation. MVS/ESA. EXCEL®. „ JAVA® ist eine eingetragene Marke der Sun Microsystems. „ Microsoft®.. z/OS. OSF/1® und Motif® sind eingetragene Marken der Open Group. Informix und Informix® Dynamic ServerTM sind Marken der IBM Corporation in den USA und/oder anderen Ländern. xApps. mySAP. „ Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten. Word®. OS/2®. „ JAVASCRIPT® ist eine eingetragene Marke der Sun Microsystems. X/Open®. verwendet unter der Lizenz der von Netscape entwickelten und implementierten Technologie. Intelligent Miner. DHTML. „ MarketSet und Enterprise Buyer sind gemeinsame Marken von SAP AG und Commerce One. In dieser Publikation enthaltene Informationen können ohne vorherige Ankün-digung geändert werden. Parallel Sysplex®. „ ORACLE® ist eine eingetragene Marke der ORACLE Corporation. „ SAP. Alle Rechte vorbehalten „ Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind. XHTML sind Marken oder eingetragene Marken des W3C®. WebSphere®. mySAP. S/390®. WINDOWS®. Amelia Lo / 57 . Inc. Program Neighborhood®. pSeries. Netfinity®. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen. xSeries. ICA®. AIX®. WinFrame®. zu welchem Zweck und in welcher Form auch immer.