Upload
wdalbi
View
186
Download
41
Embed Size (px)
Citation preview
HR Business Content
- Technical Aspects -
mySAP ERP HR, SAP AG
- customer -
Business Content Basics
How to enhance BW HR Content
Tips & Tricks
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 3
SAP BW Data Warehousing, Reporting & Analysis
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 4
SAP BW - What does Business Content mean ?
Query /View
Workbook / WebTemplate
Mapping rules
InfoObject Overtime HoursOvertime HoursEmployeeEmployee
InfoSource
DataSource / Extractor
Individualizatio
n
Standardizatio
n
InfoProvider
Role
Application view
User view
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 5
Extraction, Transformation and Loading
Integration to mySAP on application levelOpen for any sourceFlexible set of ETL capabilities Open to third-party toolsSupport of open standards
…to get a complete view of your business
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 6
SAP BW Data Flow: Extraction & Data Staging
InfoCube
Transfer Rules
Update rules
Communication StructureCommunication Structure
transfer structuretransfer structure
Master Data
Transfer Rules
Communication StructureCommunication Structure
AttributesTexts
transfer structuretransfer structure
Extraction Source StructureExtraction Source Structure
Infotype
ClusterTransaction Data
transfer structuretransfer structure
transfer structuretransfer structure
Extraction Source StructureExtraction Source Structure
Empl.NameMaster Data
Texts
Tools for genericdata extraction
Transaction RSO2OLTP
BW
DataSourceDataSource
InfoSource
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 7
What is an InfoObject ?
The various OLTP data models are unified for BW. A unique name containing technical information and business logic
Business objects / data elements become InfoObjects (BW term for Business Evaluation Object´)
InfoObject “0COSTCENTER”
InfoObjects are unique across application components!
R/3 OLTP
COCOControllingControlling
HRHRHuman Human
ResourcesResources
KOSTL ...
Table of cost centers
Table of employeesEMPLO COST_CENTER ...
BW Extractor
DataSourcefor
Cost Center
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 8
Types of InfoObjects
Characteristics: evaluation groups like “Cost Center”, “Product group”, “Material”
Have discrete values stored in their master data tables(e.g. the characteristic “Region” has the values “North”, “South”, .. )
Special types of characteristics:
Time characteristics like “Fiscal period”, “Calendar year”
Unit characteristics which comprise currencies and units of measure like “Local currency” or “Sales quantity”
Key figures: continuously valued numerical fields like amounts and quantities (e.g.: “Revenue” and “Sales quantity”)
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 9
Example: InfoObject Employee
Employee
Technical Description
Data Type NUMCSize 8
Attributes
OrgunitCostCenter.....
TextLanguageMedium
Hierarchies
Reporting Properties
DisplayText Selection.... “External”
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 10
HR Personnel Administration - Master Data
Employee (0EMPLOYEE) : IT 0, 1, 7, 8, 31
0PERSON Person0PERS_AREA Personnel area0PERS_SAREA Personnel subarea0CO_MST_AR Master cost center controlling area0MAST_CCTR Master cost center0EMPLGROUP Employee group0EMPLSGROUP Employee subgroup0ORGUNIT Organizational unit0JOB Job0HRPOSITION Position0COMP_CODE Company code
...
where can I investigate mapping between fields in HR-Content BW and fieldsin HR?... Regular Online documentation is really helpful...
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 11
HR Personnel Administration - Master Data
Employee (0EMPLOYEE)
...
0ANSALARY Annual salary0CURRENCY Currency key0EMPLSTATUS Employment status0EMPLPCT Employment percentage0PAYPCT Capacity utilization level0PAYRL_AREA Accounting area0PAYSCALEAR Pay scale area0ESGFORCAP ES grouping for payscale provision0PAYSCALEGR Pay scale group0PAYSCALELV Pay scale level0PAYSCALETY Pay scale type0COUNTRY_ID Country grouping
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 12
HR Personnel Administration - Master Data
Employee (0EMPLOYEE)
...0ENTRYDATE Entry date to calculate len.of service0SALARYAR Grade Region0SALARYGR Pay Grade0SALARYLV Grade Level0SALARYTY Salary Structure
Grade Level (0SALARYLV)0SALLVMIN Lower limit of pay grade level0SALLVMAX Upper limit of pay grade level
Pay Scale Level (0PAYSCALELV)0PAYLVAMT Amount for pay scale level
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 13
HR Personnel Administration - Master Data
Person (0PERSON ) : IT 2, 6
0DATEBIRTH Date of birth0GENDER Gender0NATION Nationality0PERSLANGU Language0COUNTRY Country key0COUNTY_CDE County code0POSTAL_CD Postal code0REGION Region (State, Province, County)0CITY Location...
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 14
InfoCubes as typical InfoProvider
InfoCubesData stored in Star Scheme
A combination of a fact table and dimension tables: Join of relational tablesOptimized for multidimensional reportingShared link to Master data tables
Transaction data
Supports partitioning
Special typesMultiCubesRemote Cubes
InfoCubes
MultiCubes
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 15
InfoCube - Characteristics
Central data stores for reports and evaluations
Contains two types of data Key Figures Characteristics
1 Fact Table and 16 Dimension Tables3 Dimensions are predefined by SAP
TimeUnitInfo Package
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 16
InfoCube - Data Model
One “business process” is modeled at a time
Data storage optimized for reporting by a “Star Schema”
Characteristics are structured together in related branches called “Dimensions”
The key figures, KPI's, and other calculations form the “Facts”
This structure is the same for all R/3 application areas
Dimension 2
Facts
Dimension 1 Dimension 3
Dimension 4Dimension n
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 17
InfoCube - Dimensions
Dimension tables are groupings of related characteristics.
A dimension table contains a generated primary key and characteristics.
The keys of the dimension tables are foreign keys in the fact table.
Customer dimension
C Customer # Region …
13970522 West ...
Product dimension Time dimension
P Product # Product group …
2101004 Displays ...
T Period Fiscal year …
10 1999 ...
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 18
InfoCube - Data Granularity
Data Granularity is defined as the ‘detail’ of the database, the characteristics which describe our key figures.
Fundamental atomic level of data to be represented
The ‘by’ words - for example, headcount by cost center, by nationality
It determines how far you can ‘drill down’ on the data.
Example: Time GranularityDay versus Month
A customer buys the same product 2 to 3 times a month
With time granularity of Day: 2 or 3 fact table entries
With time granularity of Month: 1 record in the fact table but aloss of information (i.e., number of orders on different weekdays).
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 19
InfoCube - Performance versus Disk Space
The decision on granularity has the biggest impact on space and performance
Reducing granularity means losing information
With ‘normal’ star schemas (i.e. big fact table and small dimension tables) the design of dimensions is primarily guided by analytical needs.
Large dimension tables have a big impact on performance
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 20
HR Personnel Administration - InfoSources
• Employees (0HR_PA_0):
0CALMONTH Calendar year / month 0EMPLOYEE Personnel number
• Actions (0HR_PA_1): IT 0
0CALDAY Calendar day 0EMPLSTATUS Employment status 0ACTIONREAS Reason for action 0ACTIONTYPE Action type 0EMPLOYEE Personnel number
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 21
HR Personnel Administration - InfoCube
Headcount and Personnel Actions (0PA_C01)• updated by InfoSources 0HR_PA_0 and 0HR_PA_1
• Key figures: 0HDCNT_LAST Number of employees 0HDCNT_FTE Number of FTE‘s 0ACTION_CNT Number of actions 0AGE_KYF Age in years 0PAYPCT Capacity utilization level 0SRVCLENKYF Length of Service
• Time characteristics:0CALDAY Calendar day 0CALMONTH Calendar year / month 0CALQUARTER Calendar year / quarter0CALYEAR Calendar year
• Characteristics:InfoSources + attributes of 0EMPLOYEE, 0PERSON
+ 0AGE, 0AGE_RANGEno navigational attributes due to challenges of time dependency !
Business Content Basics
How to enhance BW HR Content
Tips & Tricks
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 23
Generic data extraction
Transactional Data / Master DataTransactional Data / Master Data
Transparent Table, Database ViewDomain Values
Transparent Table, Database ViewDomain Values
Transparent table / DB-view
Application specific Standard extractorsApplication specific Standard extractors Generic extractionGeneric extraction
InfoSet of SAP QueryInfoSet of SAP Query
Logical data base
Table joins (ABAP Select)
EnhancementsEnhancements
Function moduleFunction module
Extraction of data to complement the standard extractors
Extraction without ABAP scripting (Query, views, domains)
Modification of existing dataSource (not recommended by SAP)
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 24
Delta extraction for generic extractors
Support delta extraction for generic extractors on monotonic attributes like
Timestamp
Calendar day
Numeric pointer (e.g. document number)
Current status of delta attribute can be monitored in delta queue (RSA7)
especially use of time stamp could make sense (date of change)
could be meaningful for transactional data in HR area (cause we have mostly time dependent master data)
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 25
Enhancement with Generic Extractor
Creating new DataSources and using generic data extraction
available with BW Extractors since BW 2.0, Plug-in ‘99delta extraction available in BW 3.0, plug-in 2001Function module interface available in BW 3.0
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 26
Generic extractor: database infoset
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 27
Definition of infoset (time dependent master data)
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 28
Definition of DataSource
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 29
Definition of DataSource
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 30
Benefit of use of logicial database PNP /PNPCE
all selection criteria of logicial database can be used as selection criteria without
additional coding
"Provide-statment" will be done automatically in BW
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 31
Result in extractor checker (RSA3)
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 32
Enhancement with additional fields
R
OLTP
BW InfoSource
Define Append
Extraction structure
Transfer structure
Replicate DataSources
Transfer structure
1
2
3 Load data
4Fill Extractstructure during Load
Customer ExitCustomer Exit
Customer AppendCustomer Append
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 33
Three steps to customize from SAP sources
Appending to existing Sources
Customizing for Business Information Warehouse in Source Systems tree (transaction ‚SBIW‘ within the source system)
1. Create append to existing extract structure of the Source2. Use customer exit within SAP enhancement (RSAP0001):
1. EXIT_SAPLRSAP_001 for Transaction Data enhancements 2. EXIT_SAPLRSAP_002 for Master data and Text enhancements3. EXIT_SAPLRSAP_004 for existing Hierarchy enhancements. 4. New Hierarchy can be extracted from Flat file or create new
Data Source using hierarchy data structure
3. Use CMOD to implement ABAP code to fill the new fields
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 34
1. BW R/3 Customizing: Create Append Structure
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 35
2. BW R/3 Customizing: Enhancement
Transaction: CMOD
Technical name of Enhancement
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 36
3. BW R/3 Customizing: Implement ABAP Code
Integrated in Customizing Technical name of enhancement: ‚RSAP0001‘
transaction data EXIT_SAPLRSAP_001 master data + texts EXIT_SAPLRSAP_002 hierarchies EXIT_SAPLRSAP_004
Use unique naming convention for Prod. vs. Dev. for „Includes“
Business Content Basics
How to enhance HR Business Content
Tips & Tricks
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 38
Top 13 Tips to a Successful BW Implementation
1. Ensure you have a project sponsor
2. Exact reporting requirements before projects start are the key
3. Follow ASAP (with well defined blueprint phase)
4. If you have to work in a fixed price project: distinguish the estimated efforts in analysis phase and realization phase
For analysis phase you are able to estimate before finishing BBPRealization can be serios estimated after BBP
5. Let customer review and sign off every single phase of your project
6. Activate and use Standard Business Contents (especially dataflow often is reusable, rest is a valuable template for your own objects)
Paradigm ShiftGap Analysis
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 39
Top 13 Tips to a Successful BW Implementation
7. Test: let the keyuser test the solution after realisation (complete that phase carefully)
8. Refer Business Content documentation in SAP Help Portal
9. Have a Sound Stress Test Plan For High Volume Customer8. Query runtime9. Extraction runtime
10. Involve customer in every project phase as an active part
11.Be Aware that parallel R/3 and BW Implementation require intense coordination
12.Need Management vision and Commitment -> check the expected added value
13.Project plan should have milestones with clear responsible persons and distance between milestones must be short(maximum 4 weeks --> drill down your milestones
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 40
Project Resources roles
BW Project Team ( Roles and Responsibilities)
Project Sponsor (mandantory)
Project Manager (on customer side and own side)
Application Architect (can be the project manager from consulting side)
BW Data Extraction Developer (ABAP Resource for enhancing extraction, transfer & update rules)
Authorization Expert (reporting authorizations are working a little bit different as application authorizations)
BW Data Access & Query Developer (Web Reporting Designer)
Training Developer & Instructor (mostly on customer side)Each Project is Different; Adjust Accordingly (one person usually has more than one role)Experiences: in big projects you need approximately 3 -4 consultants and you should demand 4 FTE on customers side
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 41
BW R/3 Customizing
Transaction: SBIW
Install Business Content
Maintain generic DataSources
Maintain DataSources
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 42
HR Structural Authorization in BW
RSSMTrans
PSA PSAPSA PSA
R/3 Org. StructureR/3 Org. Structure
T77UAT77UA
UserUserAssignmentAssignment
T77UUT77UU
UserUser
T77PRT77PR
ProfileProfile
INDXINDXClusterCluster
0HR_PA_30HR_PA_3
InfoInfoSourceSource Struc Auth
0PA_DS02
PSAPSA
ODSsODSs
UpdateRules
R/3 OLTPR/3 OLTP BWBW
Security Security CheckCheck
0HR_PA_20HR_PA_2
InfoInfoSourceSource
Struc Auth
0PA_DS03
ORFunction
Modules
RSSB_Generate_Authorizations
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 43
BW/HR Authorization
Bring Structural Authorization into BW EnvironmentSelectively or bring all R/3 Structural AuthorizationsRestrictions
Active Plan version only without time-dependencyDataSource supports all Object types from R/3, but additional customized update rules required in BWsupports not determination of hierarchy node with function module in T77PR (structural profile maintenance)
Accelerator (How to guide) is available to guide implementationDelivery since PI 2001.1 and 2001.2 / BW 3.0a
Authorization for Display Attributes Available in BW 2.0B since patch 7Attention: we talk here about structural authorization, that's not the same like authorization in profile generator..........
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 44
Sample Scenario - Steps to Install Structural Authorization (in BW 2.x)
Create Structural Authorization Profile (IMG or TR-OOSP)1
Assign User to Profile (IMG or TR-OOSB)2
3 Update T77UU table to include User Name
4 Execute program RHBAUS00 to create INDX
Activate 0HR_PA_2/3 Datasource in R/3 and BW5
Activate 0HR_PA_2/3 Infosource & Comm Structure6
Activate ODS objects and load data from R/3 7
Activate Target InfoObjects “Authorization Relevant8
Execute RSSB Function Modules to generate BW Authorization (Report RSSB_GENERATE_AUTHORIZATIONS)
9
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 45
Personalization based on Structural Authorizations
Data flow for ODS object Personalization Data
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 46
Five Steps to Activate BW/HR Business Content
1. Select and Activate HR DataSource in R/3 system :
Install & Transfer BW/HR DataSources (TA:SBIW)
2. Business Content Activation in BW system :
1. MetaData Replications
2. Activate the relevant business content (InfoProviders, InfoSources, Queries, Web Reports, Roles etc.)
Activate in Background
Activate in small chunks ( “grouping”- avoid choosing in data flow before and after)
Repeat process for all desired InfoProviders
3. Data Transfer from Source System (setup & schedule Infopackages)
4. Upload Business Packages (content for the portal) from www.iviewstudio.com into Portal.
5. Assign Imported Role to User Ids.
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 47
Tips & Hints for Installing BW/HR Business Content
Configure Payroll and Time Business ContentPlanning Time type and Quote type assignment
Evaluate and grouping for reporting purpose
Create External Hierarchy
Configure T557 series & T554R Tables
Setup in OLTP (OSS note 184266)
Maintain V_T569R for Retroactive category to avoid long running delta extraction (OSS note 353177)
Payroll AccountingExtracted at Monthly Time Dimension
PI 2004.1 will contain new payroll extractor (selection logic)
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 48
hint: extention of transactional data
Try so often as possible to extend master DataSources insteadof transactional DataSources
Update characteristics in update rules from master data attributes
-->It will reduce the traffic between OLTP and OLAP
-->Master data are reusable for further transactional datasources
-->Master data attributes can be used as navigational/display attributes (then they are outside the dataProvider)
Select the same time stamp in update rule for every characteristic to avoid diverse time relations
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 49
hint - time dependent master data
Special Considerations for BW/HR:- Create new (master data) DataSources rather than extending existingDataSources because of extraction performance reasons
- If you're extending existing datasource to provide data from additional time dependent tables, you have to take validity of records into account by using the ABAP PROVIDE statement to create new time splits, otherwise validity of data provided in user exit might not be correct
- Up to OLTP Release 4.6B, the RFPNR field of datasource0EMPLOYEE_ATTR is filled with the employee's lowest reference personnel number, which is taken from infotype 0031 Reference Personnel Numbers. As of OLTP Release 4.6C, the RFPNR field is filled with the personnel number which is related via the central person and which has the oldest entry date. The RFPNR field is the link to 0PERSON. This information can be used to count contracts and/or physical persons. If you want to have a different assignment of the person id, please implement that logic in the user exit of master data extraction.
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 50
Tips & Hints for Installing BW/HR Business Content
System Maintenance PerspectivesKeep your system up to date
Apply & Activate latest content/system patches at first possible chance for needed enhancements and Improvements (most actual patch - 1)
Review notes periodically; apply as appropriate
Upgrade ConsiderationReview changes from both Basis and application perspectives and adopt new improvements wherever is appropriate.
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 51
Tips when Bring in HR Data from non-SAP source
General ConsiderationsData Conversion
When Integration with SAP data is a requirement, convertnon-SAP to SAP-like, so that you can take advantage of all avaialbe master from R/3Historical Data consideration:
Since HR Master Data is mostly “Time Dependent”, historical data must be sorted in a “Begda” and “Endda” format without overlappingIf non-R/3 system will not be retired, determine where the master data to be maintained – preferrable in R/3
Review and incorporate the necessary Master data (ie. Orgunit, Personnel Areas etc.) from non-R3 system
Data CleansingEliminate dirty data via conversion or build in logic in transfer/update rules (former is preferable)
Multiple source systemsClarify before projects start if more then 1 source system will be connected or will be planned for the future -->otherwise other consultants as You will have a migration project in future :-)
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 52
useful hint: InfoObject person (0person)
use infoObject Person (0person) in transfer structureof transactional infosource
--> it will provide and offer automaticially attributes ofperson in update rules --> makes the update logic much easier
1. expand communication structure
2. assign 0EMPLOYEE to 0PERSON intransfer rule
3. use atributes in update rules without programing
4. Attention: only usable when relation0EMPLOYEE = 0PERSON
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 53
hint: InfoCube - Data Model
modelling under aspect performance vs. thematic order
try to create so much dimensions as possible and try to distribute the charateristics with context among each other
--> that will reduce the number of DIM-id's
--> performance will be increased
optimum will be to have the same number of DIM-id's in every dimension
but: often that will be inopposition to order the characteristics under thematicorder
Dimension 2
Facts
Dimension 1 Dimension 3
Dimension 4Dimension n
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 54
Tips & Hints for Installing BW/HR Business Content
6. Helpful OSS NotesOrg. management
543324 Performance extraction DataSource 0ORGUNIT_ATTR313215 Performance BW master data extraction 0HRPOSITION
(performance note for 0HR_PA_OS_1 in process)
Pers. Administration381239 HR BW: Counting leavings using actions
General HR397208 BW: Authorizations for HR data extraction
General BW529789 Different BW extraction / extractor checker + enter date selection
as internal format for RSA3, esp. for time dep. master data310304 DATETO/DATEFROM:Extracting time-depdnt master data324684 Selections for language and time-dependence
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 55
Questions?
Q&A
© SAP AG 2004, HR Business Content - customer / Oliver Kunowsky / 56
Copyright 2004 SAP AG. All Rights ReservedNo 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 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.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.