Integrate Information from Disparate Sources Using SAP BW Consolidated InfoObjects
Jie Deng, Product Management BI,SAP AG
© SAP AG 2005, Jie Deng / 2
Agenda
What Is the Concept of Consolidated Infoobjects and When Do I Need Them?
What Are the Key Points of Data Modeling for Consolidated InfoObjects (SAP BW)?
Composed keysAttributes Key mappingFlexible update
Business Content for Consolidated InfoObjects from SAP
Product, product category and business partner
Summary
© SAP AG 2005, Jie Deng / 3
Agenda
What Is the Concept of Consolidated Infoobjects and When Do I Need Them?
What Are the Key Points of Data Modeling for Consolidated InfoObjects (SAP BW)?
Composed keysAttributesKey mappingFlexible update
Business Content for Consolidated InfoObjects from SAP
Product, product category and business partner
Summary
© SAP AG 2005, Jie Deng / 4
Status Quo Until < SAP BW 3.0B
Heterogeneous master data in SAP BW for: Products Product categories Business partner (vendor/customer)...
... from different software components:SAP R/3SRM (EBP, SUS)CRMAPONon-SAP
... represented in SAP BW with separate InfoObjects:e.g.: 0MATERIAL R/3 material
0BBP_PROD EBP product0ORA_PROD Oracle product
© SAP AG 2005, Jie Deng / 5
Current Solution Since SAP BW 3.0B
The situation up until now:There are “local” InfoObjects for every system type (e.g., for R/3, CRM, EBP)
Different SAP releases for R/3, EBP, CRM, etc., are mapped to that local object model
Low level of integration, no suitable solution for distributed systems (multiple R/3 back-end, one or more EBP or CRM system)
Ultimate integration goals:Integration of information from different system types (e.g. material in R/3 and product in SAP CRM) in a common data warehouse system
Great improvement for users with various different SAP components
Important technological prerequisite for the integration of non-SAP data (like Siebel, Oracle, etc.) into SAP BW
Current solution: “Concept of consolidated InfoObjects”
SAP BW 3.0B includes consolidated InfoObjects for productproduct, , productproduct categorycategory, andbusiness partnerbusiness partner
© SAP AG 2005, Jie Deng / 6
Concept of Consolidated InfoObjects in SAP BW
Consolidated InfoObjects (Example: 0PRODUCT)Consolidated InfoObjects (Example: 0PRODUCT)
R/3 SourcesR/3 SourcesR/3 SourcesR/3 sources
R/3 object model(namespace 0*)
Example: 0MATERIAL
InfoSource
Info-Cube
ODSobject
SAP CRM/EBP OM(namesp. 0CRM_*,
0BBP_*)Example:
0CRM_PROD
R/3 Sources
Oracle OM(namesp. 0ORA_*)
Example: 0ORA_PROD
InfoSource Info-Cube
ODSobject
Key MappingInformation
OracleSAP EBP/CRM
InfoSource
Info-Cube
ODSobject
InfoSource
Info-Cube
ODSobject
© SAP AG 2005, Jie Deng / 7
Example – Result without Consolidated InfoObjects
$ 9800$ 4955Getränke GmbH$ 34000$ 10060H-Lux GmbH
$ 15675$ 7835Thomas Erfrischung$ 7890$ 5790Shining Lights$ 80050$ 34500L.C. Kunde
$ 10780$ 8950Costa Ltd.$ 88600$ 67900C.L. Customer$ 7895$ 2690Barbara DrinksTotal order valueInvoice valueCustomer
Customers: Invoice and order valueThese
customers have the
same group ID
Cannot analyze the total order value for those customers, who have different company name but actually they belong to the same company group!
© SAP AG 2005, Jie Deng / 8
Example – Result with Consolidated InfoObjects
$ 41890$ 15850Result$ 7890$ 5790Shining Lights$ 34000$ 10060H-Lux GmbHH-Lux Ltd.$ 179430$ 111350Result$ 80050$ 34500L.C. Kunde$ 10780$ 8950Costa Ltd.$ 88600$ 67900C.L. CustomerCosta Ltd.$ 33370$ 15480Result$ 15675$ 7835Thomas Erfrischung$ 9800$ 4955Getränke GmbH$ 7895$ 2690Barbara DrinksBarbara BeverageTotal order valueInvoice valueCustomerGroup ID customer
Customers: Invoice and order value
Now I can analyze the total order value for those customers, whohave the different company name but actually they belong to the same company group!
© SAP AG 2005, Jie Deng / 9
Summary – What Are Consolidated InfoObjects and When Do I Need Them?
Consolidated InfoObjects are an important aspect of SAP BW; they allow you to integrate information from different SAP components and non-SAP systems into a standardized, consolidated data model
You need consolidated InfoObjects when youHave several productive mySAP components or non-SAP systemsThere are “local” InfoObjects for every system type (e.g., for R/3, CRM, EBP)You want to ensure a consolidated and consistent master data model for the purpose of company-wide reporting or analysis
© SAP AG 2005, Jie Deng / 10
Agenda
What is the Concept of Consolidated InfoObjects and When Do I Need Them?
What are the Key Points of Data Modeling for Consolidated InfoObjects (SAP BW)?
Composed keysAttributes Key mappingFlexible update
Business Content for Consolidated InfoObjects from SAP
Product, product category and business partner
Summary
© SAP AG 2005, Jie Deng / 11
Data Model in SAP BW
Composed keys Global and consolidated views on products,
independent on source system
0PRODUCT
SAP content
integrator
Key mapping
Key mapping
R/3 material
R/3R/3R/3
EBP product
R/3R/3EBP
IS: material IS: service IS: BBP prod
Flexible update
Attributes
CRM product
R/3R/3CRM
0CRM_PROD
IS: CRM prod
0BBP_PROD
R/3 service
R/3R/3R/3
0SERVICE0MATERIAL Local views on products,
dependent on source system
DataSources
© SAP AG 2005, Jie Deng / 12
Agenda
What is the Concept of Consolidated InfoObjects and When Do I Need Them?
What are the Key Points of Data Modeling for Consolidated InfoObjects (SAP BW)?
Composed keysAttributes Key mappingFlexible update
Business Content for Consolidated InfoObjects from SAP
Product, product category andBusiness partner
Summary
© SAP AG 2005, Jie Deng / 13
Composed Keys of Consolidated InfoObjects
Source system information - 0GN_PAR_SSY Character 2
Character 4
Character variable
Table RSSOURSYSTEMField SOURSYSIDBlank characterBack-end object type - 0GN_BWBEOTY
Transaction RS_BCT_BWBEOTYP (IMG)Combined information about the source system (SAP component or non-SAP system) and the object type (partner, product, product category) within this source system.
Predefined values will be delivered along with Business Content!e.g.: 1MAT – material, 1SER – serviceInfoObject key from local view - 0CUSTOMER....
Original local key from object in source system
© SAP AG 2005, Jie Deng / 14
Example – Composed Keys
System: EBP-1 (ID: E1) Key Obj.type DescriptionP1 Material PipesP2 Material Hammer
System: R/3-1 (ID: R1)Key Obj.type Description M1 Material PipesM2 Material Hammer
System: R/3-2 (ID: R2)Key Obj.type DescriptionM1 Material PipesM22 Material Hammer
Composed key of0PRODUCT
Source system
0MATERIALkey in R/3 system
0BBP_PRODkey in EBP-system
… Group ID(Key mapping information)
R1 1MAT M1 R/3-1 M1 -
R2 1MAT M1 R/3-2 M1 -
E1 1MAT P1 EBP-1 - P1
R1 1MAT M2 R/3-1 M2 -
R2 1MAT M22 R/3-2 M22 -
E1 1MAT P2 EBP-1 - P2
© SAP AG 2005, Jie Deng / 15
0PRODUCT: Key Concatenation in Update Rules
Building composed
keys
© SAP AG 2005, Jie Deng / 16
Agenda
What is the Concept of Consolidated InfoObjects and When Do I Need Them?
What are the Key Points of Data Modeling for Consolidated InfoObjects (SAP BW)?
Composed keysAttributes Key mappingFlexible update
Business Content for Consolidated InfoObjects from SAP
Product, product category and business partner
Summary
© SAP AG 2005, Jie Deng / 17
Attributes of Consolidated InfoObjects
Source system information
Group ID as the key mapping
information
InfoObjects in the local view
Global attributes
© SAP AG 2005, Jie Deng / 18
Attributes of Consolidated InfoObjects (cont.)
The attributes of consolidated InfoObjects are structured as follows
Source system information, InfoObject key from local views, back-end object type
All InfoObjects in the local view form the consolidated InfoObject
Key mapping information: Group ID as a navigation attribute
Global attributes (only consolidated InfoObjects, e.g., the product category as a global attribute of product and conform to generally recognized standards!!!)
More specifically, attributes of InfoObjects from the local views (for example, the R/3 material group as an attribute of R/3 material) cannot be transferred directly as global attributes into the relevant consolidated InfoObject. These local attributes are relevant only in the local views (SAP R/3, SAP CRM, and so on).
© SAP AG 2005, Jie Deng / 19
Attributes of Consolidated InfoObjects – Best Practices
Keep the consolidated InfoObjects very lean!Only attributes used for global reporting are relevant
Don‘t flood them with attributes of local views!Global attributes delivered by SAP can only be
Consolidated InfoObjects
InfoObjects with unified or standardized values in all source sytems
DUNS number, UNSPSC code, e-Class, ISO codes
Customer can add own standardized attributes depending on the master data model
© SAP AG 2005, Jie Deng / 20
Agenda
What is the Concept of Consolidated InfoObjects and When Do I Need Them?
What are the Key Points of Data Modeling for Consolidated InfoObjects (SAP BW)?
Composed keysAttributes Key mappingFlexible update
Business Content for Consolidated InfoObjectsfrom SAP
Product, product category and business partner
Summary
© SAP AG 2005, Jie Deng / 21
Key Mapping: Extraction into SAP BW System
SAP content
integrator
Key mapping
Key mapping
R/3 material
R/3R/3R/3
EBP product
R/3R/3EBP
IS: material IS: service IS: BBP prod
CRM product
R/3R/3CRM
0CRM_PROD
IS: CRM prod
0BBP_PROD
R/3 service
R/3R/3R/3
0PRODUCT
0SERVICE0MATERIAL
Other source
Key mapping
SAP BW model can be fed by arbitrary key mapping source!
© SAP AG 2005, Jie Deng / 22
Key Mapping Information from SAP Content Integrator
Import master data to SAP content integrator:SAP Master Data Management, part of SAP NetWeaver, required to run content integratorMultiple systems (R/3, EBP, non-SAP etc.)Selected master data attributes
Define matching process:Define matching rules (attributes, weighted sums etc.)Identify duplicate records (semi-automatic process)Store matching results as key mapping
Upload key mapping to SAP BWFull and initial loadsDelta load: only new and changed key mapping will be exported to SAP BWKey mapping is an iteratively improved process!SAP BW model takes this into account: changes in key mapping can be adapted/used for historical data!
© SAP AG 2005, Jie Deng / 23
Key Mapping Information from Other Sources
Key mapping information not in SAP CI
Knowledge about master data inconsistency and ID assignment may exist in customer-specific storages (files, DB-tables, etc.)
Resuse customer storage in SAP BW model
Upload this data to SAP BW (e.g., flat files, R/3 based extractor, DB-link)
Map information to SAP BW model (e.g., fill attributes of 0PRODUCT)
Reporting
Define queries based on customer global IDs
Do reporting even on historical data!
© SAP AG 2005, Jie Deng / 24
Example – Key Mapping Information
Key mapping fromcontent integrator:
System Obj.Type Key Group ID DescriptionEBP-1 1MAT P1 G1 PipesR/3-1 1MAT M1 G1 PipesR/3-2 1MAT M1 G1 PipesEBP-1 1MAT M2 G2 HammerR/3-1 1MAT M2 G2 HammerR/3-2 1MAT M22 G2 Hammer
Composed key of 0PRODUCT
Source system
0MATERIALkey inR/3 system
0CRM_PRODkey inEBP system
…. Group ID(key mapping information)
R1 1MAT M1 R/3-1 M1 - G1
R2 1MAT M1 R/3-2 M1 - G1
E1 1MAT P1 EBP-1 - P1 G1
R1 1MAT M2 R/3-1 M2 - G2
R2 1MAT M22 R/3-2 M22 - G2
E1 1MAT P2 EBP-1 - P2 G2
© SAP AG 2005, Jie Deng / 25
Agenda
What is the Concept of Consolidated InfoObjects and When Do I Need Them?
What are the Key Points of Data Modeling for Consolidated InfoObjects (SAP BW)?
Composed keysAttributes Key mappingFlexible update
Business Content for Consolidated InfoObjects from SAP
Product, product category and business partner
Summary
© SAP AG 2005, Jie Deng / 26
Flexible Update – What Does This Mean?
0CRM_PROD_ATTR0BBP_PROD_ATTR
0PRODUCT
0SERVICE_ATTR0MATERIAL_ATTR
Flexible Update
What does flexible update mean?
• Previously it is the direct connection between DataSources and InfoObjects
• Now with flexible update, master data and text tables appear as data targets
• Update rules can be used in addition to the transfer rules
What are advantages of a flexible update?
• Several different data targets can be filled using a master data or text InfoSource
• One InfoObject can be filled using different master data or text InfoSources
• More options are provided for delivering and distributing master data in SAP BW
© SAP AG 2005, Jie Deng / 27
How to Use Flexible Update?
Flexible update is an important feature which SAP has delivered to customer with SAP BW 3.0B. It is a key technology that is necessary for building the consolidated InfoObjects.
The following InfoObjects have been delivered as data targets by using flexible data updates in SAP BW 3.0B:
0CUSTOMER Customer (SAP R/3)0VENDOR Vendor (SAP R/3)0COMP_CODE Company code (SAP R/3)0MATERIAL Material (SAP R/3)0SERVICE Service number (SAP R/3)0MATL_GROUP Material group (SAP R/3)0PROD_HIER Product hierarchy (SAP R/3)0BPARTNER Business partner (SAP CRM / EBP)0CRM_PROD CRM product (SAP CRM)0BBP_PROD Product (SAP EBP)0PROD_CATEG Product category (SAP CRM / EBP)0APO_PROD APO product (SAP APO)0APO_LOCNO APO location (SAP APO)0UNSPSC UNSPSC Code (SAP EBP)0ECLASS EClass (SAP EBP)
For the setup transition from direct to flexible update with delta update, please refer to SAP note 511477
© SAP AG 2005, Jie Deng / 28
Summary – Key Points of Data Modeling
Consolidated InfoObjects have composed keys that are based on source system information, back-end object type, and InfoObject key from the local view. These three elements are combined to form the unique key in the update rule in standard business content.
Besides the source system information and local view of InfoObjects as attributes, consolidated InfoObjects have global attributes (e.g., country or region) and Group ID as attributes as well.
Group ID is the key mapping information that can identify whether local objects belong together even though they have different local keys. Group ID can be loaded from SAP Content Integrator or any other external source.
Consolidated InfoObjects should be defined as data targets by using flexible update, which is a key feature for realizing this data modeling concept.
© SAP AG 2005, Jie Deng / 29
Agenda
What is the Concept of Consolidated InfoObjects and When Do I Need Them?
What are the Key Points of Data Modeling for Consolidated InfoObjects (SAP BW)?
Composed keysAttributes Key mappingFlexible update
Business Content for Consolidated InfoObjects from SAP
Product, product category and business partner
Summary
© SAP AG 2005, Jie Deng / 30
Product: Data Flow in SAP BW
Global and consolidated views on products,
independent on source system
SAP content
integrator
Key mapping
Key mapping
R/3 material
R/3R/3R/3
EBP product
R/3R/3EBP
IS: material IS: service IS: BBP prod
CRM product
R/3R/3CRM
0CRM_PROD
IS: CRM prod
0BBP_PROD
R/3 service
R/3R/3R/3
0PRODUCT
0SERVICE0MATERIAL
Attribute: group ID product
Local views on products,
dependent on source system
DataSources
© SAP AG 2005, Jie Deng / 31
Product: Attributes
Key information0PRODUCT (Key) Product (consolidated)
0GN_PRO_SSY SAP BW System ID
0GN_BWBEOTY Object type of product (e.g., MATERIAL, SERVICE)
0GN_PRO_LID Local key (can be used for F4 or filters)
References to local view InfoObjects0MATERIAL Material (R/3)
0SERVICE Service (R/3)
0BBP_PROD Product (EBP)
0CRM_PROD Product (CRM)
0APO_PROD APO product
Key mapping information0CI_GRP_PRO Group ID from content integrator, which groups identical products
Global attributes0GN_CAT_PUR Purchase category (consolidated)
0GN_CAT_SAL Sales category (consolidated)
0UNSPSC UN-SPSC code (standard for categories/commodities)
0ECLASS e-Class code (standard for categories/commodities)
© SAP AG 2005, Jie Deng / 32
Product Category Used in Business Processes…
In SAP R/3, there are different category types:Category types build a hierarchical view on categories
0PROD_HIER → Sales view
0MATL_GROUP→ Purchase view
In CRM/SRM, there are different applications for category hierarchies:
Application 01→ Sales
Application 02→ Purchase
Idea: split 0GN_CATEGORY into:0GN_CAT_SAL→ Sales category
0GN_CAT_PUR→ Purchase category
© SAP AG 2005, Jie Deng / 33
Product Category: Data Flow in SAP BW
Global and consolidated views on prod. category,
independent on source system
R/3 material group
R/3R/3R/3
Product category
R/3R/3CRM/EBP
R/3 product hierarchy
R/3R/3R/3
IS: material group
0MATL_GROUP
IS: product category
0PROD_CATEG
IS: product hierarchy
0PROD_HIER
0GN_CAT_PUR 0GN_CAT_SAL
Local views on prod. category,
dependent on source system
DataSources
Update only if application = 02/PurchaseUpdate only if application = 01/Sales
© SAP AG 2005, Jie Deng / 34
Product Category: Attributes
Key information0GN_CAT_PUR/ 0GN_CAL_SAL (key)
Purchase/sales category
0GN_CAT_SSY BW system ID
0GN_BWBEOTY Object type of category (e.G. R/3 material group
0GN_CAT_LID Local key (can be used for F4 or filters)
References to local view InfoObjects0MATL_GROUP Material group (R/3) (only for 0GN_CAT_PUR)
0PROD_HIER Product hierarchy (R/3) (only for 0GN_CAT_SAL)
0PROD_CATEG Product category (CRM/EBP)
0UNSPCS_ID UN-SPSC code (only for 0GN_CAT_PUR)
0ECLASS_ID e-Class code (only for 0GN_CAT_PUR)
Key mapping information0CI_SPURCAT Standard category for reporting
Global attributesnone
© SAP AG 2005, Jie Deng / 35
How Does a Partner Act in a Business Process?
0GN_VENDOR 0GN_BUY_COM 0GN_BUY_ORG
0GN_CUSTOM 0GN_SELLCOM 0GN_SELL_ORG
External Internal, legal Internal entities organizational units
External vendor
Company codeCompany code Purchase
organization
Sales Organization, Distribution Channel, Other...
ProcurementSeller Buyer Buyer
SalesBuyer Seller Seller
External customer
Company codeCompany code
© SAP AG 2005, Jie Deng / 36
Partner: Composing InfoObjects
0GN_VENDOR 0GN_BUY_COM 0GN_BUY_ORG*
0GN_CUSTOM 0GN_SELLCOM 0GN_SELL_ORG *
External Internal, legal Internal entities organizational units
0VENDOR0COMP_CODE0BPARTNER (only external vendors)
0COMP_CODE0BPARTNER(only internal legal entities)
Purchase Organization
Sales Organization, Distribution Channel, Other...
ProcurementSeller Buyer Buyer
SalesBuyer Seller Seller
0CUSTOMER0COMP_CODE0BPARTNER (only external customers)
0COMP_CODE0BPARTNER (only internal legal entities)
0GN_COMPANY
Basis IO
Referencing IO
*Not covered with SAP BW 3.0B
© SAP AG 2005, Jie Deng / 37
Customer: Data Flow in SAP BW
SAP content
integrator
Key mapping
Key Mapping
R/3 customer
R/3R/3R/3
Global and consolidated views on customer,
independent on source system
Business partner
R/3R/3CRM/EBP
Local views on customer,
dependent on source system
IS: customer IS: comp. code IS: bus. partner
DataSourcesAPO location
R/3R/3APO
0APO_LOCNO
IS: APO location
0BPARTNER
Company code
R/3R/3R/3
0GN_CUSTOM
0COMP_CODE0CUSTOMER
Attribute: group ID customer
Update if business partner is a customer.
Update if APO location is a customer.
© SAP AG 2005, Jie Deng / 38
Vendor : Data Flow in SAP BW
SAP content
integrator
Key mapping
Key mapping
R/3 vendor
R/3R/3R/3
Global and consolidated views on vendor,
independent on source system
Business partner
R/3R/3CRM/EBP
Local views on vendor,
dependent on source system
IS: vendor IS: comp. code IS: bus. partner
DataSourcesAPO location
R/3R/3APO
0APO_LOCNO
IS: APO location
0BPARTNER
Company code
R/3R/3R/3
0GN_VENDOR
0COMP_CODE0VENDOR
Attribute: group ID vendor
Update, if business partner is a vendor.Update, if APO location is a vendor.
© SAP AG 2005, Jie Deng / 39
Partner: Attributes
Key information0GN_CUSTOM / 0GN_VENDOR (Key)
Customer/Vendor (consolidated)
0GN_PART_SSY SAP BW system ID0GN_BWBEOTY Object type of Partner (e.g., VENDOR, CUSTOMER, BPARTNER, APO
LOCATION, etc.)0GN_PAR_LID Local key (can be used for F4 or filters)
References to local view InfoObjects:0VENDOR / Vendor (R/3) (only for 0GN_VENDOR) 0CUSTOMER Customer (R/3) (only for 0GN_CUSTOM)0BPARTNER Business Partner (CRM / EBP)0COMP_CODE Company Code (R/3)0APO_LOCNO APO Location
Key mapping information0CI_GRP_PAR Group ID from content integrator, which groups identical objects
Global attributes0DBDUNS_NUM D&B D-U-N-S0COUNTRY standardized country info (ISO codes etc.)0REGION standardized region info (ISO codes etc.)0POSTALCODE standardized postal code
© SAP AG 2005, Jie Deng / 40
Agenda
What is the Concept of Consolidated InfoObjects and When Do I Need Them?
What are the Key Points of Data Modeling for Consolidated InfoObjects (SAP BW)?
Composed keysAttributes Key mappingFlexible update
Business Content for Consolidated InfoObjects from SAP
Product, product category and business partner
Summary
© SAP AG 2005, Jie Deng / 41
SAP Developer Network – sdn.sap.com
The central hub for the SAP technology community
Everyone can connect, contribute and collaborate- consultants, administrators and developersFocus around SAP NetWeaver and SAP xApps
High quality of technical resourcesArticles, how-to guides, weblogs, collaborative areas, discussion forums and downloads, toolkits and code-samples
A collaboration platform, not a one-way street
SAP experts from customers, partners and SAP
SDN is powered by SAP NetWeaver™Built on the SAP Enterprise PortalFeaturing collaboration capabilities of SAP Knowledge Management
© SAP AG 2005, Jie Deng / 42
Additional Resources
Public Web:www.sap.com/biSAP customer services network: www.sap.com/services/Related SAP education training opportunitieshttp://www.sap.com/usa/education/
© SAP AG 2005, Jie Deng / 43
6 Key Points to Take Home
The concept of consolidated InfoObjects allows you to integrate information from different SAP components and non-SAP systems into a standardized, consolidated data model
The data model of consolidated InfoObjects consists of a two-layer architecture: local views (source-system-dependent) and global views (data integration level)
Key mapping is crucial for the integration of data from different source systems
Consolidated InfoObjects should be kept very lean! Only global reporting attributes are relevant.
Be sure to take advantage of the flexible update feature!
Consolidated InfoObjects product, product category and business partner have been already delivered as Business Content with SAP BW 3.0B
© SAP AG 2005, Jie Deng / 45
Copyright 2005 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®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® 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®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA 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®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.HTML, DHTML, XML, XHTML 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. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.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 information purposes only. National product specifications may vary.