Summary of Supported Standards

of SAP NetWeaver PI 7.1

1
SAP AG 2007

Objectives

After viewing this document, you will be able to:

Specify the supported standards of SAP NetWeaver
PI 7.1

SAP AG 2007

2
SAP AG 2007

Summary of Supported Standards

Consortium/Org
anization

Standard
Specification

Supported
Version

Implementation

W3C

WS-Security

1.0

Message Header

W3C

WS-Policy

1.2

WSDL document

W3C

MTOM

1.0

Integration Engine

OASIS

WS-BPEL

2.0

Integration Processes

OASIS

WS-RM

1.1

Integration Engine

OASIS

UDDI

3.0

Service Registry

UN/CEFACT

CCTS

2.01

SAP Global Data Types

SAP AG 2007

This is the list of most important supported standards versions in SAP NetWeaver PI 7.1.
Considering W3C Recommendations, we will be supporting WS-Security 1.0, WS-Policy 1.2 and MTOM 1.0.
OASIS WS-BPEL 2.0 was very recently released and just a preview of these functionalities are going to be
included, but both the forthcoming WS-Reliable Messaging 2.0 and also UDDI 3.0 will be fully covered and
there are additional features developed both for Reliable Messaging (like the TU&C/C pattern) and the
additional functionalities and APIs for the Services Registry.
Regarding UN/CEFACT CCTS 2.01 and considering that SAP is a technology leader with a strong
knowledge of business processes, it is quite natural for the company to take the lead and drive the adoption
of this standard.

3
SAP AG 2007

Usage Summary

Standard /
Specification /
Recommendation

Benefits

WS-Security

Design Time: Interoperability at security level

WS-Policy

Design time: Interoperability at several levels

WS-BPEL 2.0

Design Time: Simplify user interaction in the Integration Processes

Runtime: Increase support for user interaction (PI 7.10)

WS-RM

Design time: Provides abstraction from communication layer.

Runtime: Standard communication layer

UDDI

Discovery: Support Governance and reuse/Interoperability

Runtime: Dynamic Configuration

CCTS
MTOM

Design and modeling times: Interoperability at data level and business

semantics
Runtime: Optimize SOAP message size to boost performance

SAP AG 2007

Now you see summarized in a single slide the most remarkable benefits that you get from each one of these
standards:
WS-Security, WS-Policy, UDDI and CCTS basically increase interoperability at several levels.
BPEL2.0 specifically extended the original reach for automated process execution, and opened the door to
human interactions.
WS-Reliable Messaging specification defined a standard layer for dependable messages transmission,
which is enriched by:
A set definitions on the security arena (provided by the WS-Security standard),
The interoperability rules (provided by the WS-Policy standard),
And also a improvement in runtime performance (provided by MTOM),
Defining a comprehensive standard way to securely and effectively exchange information.

4
SAP AG 2007

WS-RM Summary

SAP Process Integration and the application platform now support the WS-RM
open standard protocol.
The WS-RM protocol is the basis of the Enterprise Service Protocol.
SAP Process Integration tools allow you to centrally develop and configure the
integration scenarios.
The configuration is automatically propagated to the application systems!

At runtime, the communication among the application systems can be direct or

mediated via SAP Exchange Infrastructure.
The framework provides automatic information compensation services to guarantee
that information is properly replicated.
Application systems have to correctly design the replication process.

SAP AG 2007

5
SAP AG 2007

Reliable Messaging Model

Delivery Assurances as Described by WS-RM
Source Reliable Message Layer

Target Reliable Message Layer

Message 1

AtMostOnce
Source Reliable Message Layer

AtLeastOnce

Target Reliable Message Layer

Message 1

Message 1

Source Reliable Message Layer

ExactlyOnce

Message 1

Target Reliable Message Layer

Message 1

Message 1

InOrder
AtMostOnce inOrder
AtLeastOnce inOrder
ExactlyOnce inOrder

SAP AG 2007

AtMostOnce: Messages will be delivered at most once without duplication or an error will be raised on at
least one endpoint. It is possible that some messages in a sequence may not be delivered.
AtLeastOnce: Every message sent will be delivered or an error will be raised on at least one endpoint.
Some messages may be delivered more than once.
ExactlyOnce: Every message sent will be delivered without duplication or an error will be raised on at least
one endpoint. This delivery assurance is the logical "and" of the two prior delivery assurances.
InOrder: Messages will be delivered in the order that they were sent. This delivery assurance may be
combined with any of the above delivery assurances. It requires that the sequence observed by the ultimate
receiver be non-decreasing. It says nothing about duplications or omissions.

6
SAP AG 2007

Sequencing Support: SAP Design Criteria

Offer abstraction from the Technical (WS-RM) Sequences

Application works with a "Logical Sequence" (ID) and WS Runtime maps this to WS-RM
Sequences.
Transactional behavior.
On consumer-side either all or none of collected calls are sent to the provider.
On provider-side each call is executed in a separate transaction.

Restrictive model to work with "Logical Sequences"

Sequences ID is generated by WS runtime
Sequences have to be explicitly
Created
Opened & closed
Activated
Terminated (in case of Persistent Sequences)

SAP AG 2007

Logical Sequence = SOAP Sequence

Technical Sequence = WS-RM Sequence

7
SAP AG 2007

Relationship Between Logical and Technical

Sequences
On consumer side, each logical sequence is exactly one to one related to a
technical (WS-RM) Sequence.
The technical sequence is the same on Client and Server Side (same means same
key).
On provider side, a technical sequence is exactly one to one related to a provider
logical sequence.
Consumer and provider sequence are different sequences with different keys
(sequence ID).

SAP AG 2007

The technical (WS-RM) sequence is being transferred with the SOAP message and therefore is identical on
both sides. The logical (SOAP) sequence is not being transferred, thus on the provider-side a new
sequence-ID is being pulled and assigned to the technical sequence.

8
SAP AG 2007

Logical Sequences: General Details

Is a container for all SOAP messages created within one application transaction (LUW)
Supports transactional sending
Does not preserve the LUW at the receiver
A logical sequence could be created w/o a proxy

Keeps the chronological order of the messages

A messages is not only the SOAP XML message on the wire but all associated objects (runtime state).
A message exists in three states:
Object state ready to send the SOAP message
Serialized all objects a serialized but may not jet be stored
Persists the serialized message is backuped to the data base

Is a container, which can be passed to persistency layer

Rollback All messages will be discarded
Commit work
All messages will be hand over to the reliable messaging infrastructure

May have an associated WS-RM sequence

Late binding of logical sequence to WS-RM sequence

SAP AG 2007

9
SAP AG 2007

Logical Sequences Persistency: Persistent &

Transient
A Transient Sequence (TS) may have 0..1 WS-RM sequence:
The WS runtime will terminate the sequence after receiving the last ACK
Applications can not continue TS after Commit work
Framework managed sequence

A Persistent Sequence (PS) may have 0..1 WS-RM sequences:

The WS runtime will not terminate the sequence by itself
Applications may continue PS after Commit work
For each PS only one related active WS-RM sequence exists per time
Application managed sequence

SAP AG 2007

General aspects
Sequence (object) can only be used for one begin/end cycle
Sequences are created internally by sequence manager
A sequence must be
Created
Usage must be bracketed with begin/end to avoid sequencing problems in case of unexpected
commits
Activated before usage
Transient Sequence
No reuse possible
Sequence termination is done by Sequence Manager when all WS-RM acks were received (triggered by
WS-RM)
Short life-span: Lifetime controlled by WS runtime
Persisted state for sequence must be hold only for a short period
Persistent Sequence
Sequence termination has to be done by application
Possibly long life-span: Lifetime controlled by application
Persistent state for sequence must be hold for a longer period.
Mechanism necessary to remove sequences with a long period of inactivity to avoid collections of
persisted state.
Active sequence can be determined if current environment was not responsible for creation and activation
of a given sequence.

10
SAP AG 2007

TU&C/C: Design "Consumer"-Side

The Service Interface is stateless

The Service Interface must contain:
One "Compensate"-Operation
QoS "ExactlyOnce" must be ensured
"Compensate" call must be registered in consumer ESP Runtime
This registration must survive rollbacks, system crashes, etc.

If the transaction is finished successfully the registered "compensate" call is delete

without sending it

If the transactions fails (rollback, system crash, ) the "compensate" call must be send
via WS-RM "EO"
At least one "Confirm"-Operation

This is a "normal" asynchronous operation with QoS "EO"

At least one "TentativeUpdate"-Operation
This is a "normal" synchronous operation

SAP AG 2007

11
SAP AG 2007

TU&C/C: Design "Provider"-Side

The Service Interface is stateless

The Service Interface must contain:
One "Compensate"-Operation
This is a "normal" asynchronous operation with QoS "EO"
At least one "Confirm"-Operation
This is a "normal" asynchronous operation with QoS "EO"
At least one "TentativeUpdate"-Operation
This is a synchronous operation
BUT: The "COMMIT-Handling" is handled automatically by the ESP Runtime

If the operation is successful, the ESP Runtime makes a COMMIT

If the operation fails, the ESP Runtime makes a ROLLBACK

SAP AG 2007

12
SAP AG 2007

TU&C/C Pattern Considerations 1/2

The TU&C/C pattern must be supported and handled by the consumer and provider
applications!!
XI at runtime executes message transmission, but the messaging framework cannot
differentiate from standard messages!

Client rollback will automatically trigger the previously registered "compensate"

operation asynchronously.

SAP AG 2007

13
SAP AG 2007

TU&C/C Pattern Considerations 2/2

"Tentative Update" operations are synchronous.

QoS BE not BE + EO (or EOIO).
It does not handle sequences, so in case of software errors (client, middleware, network,
etc.), the provider could receive the message duplicated or even miss a message. It should
be handled by the applications.
To make sure that information is properly replicated, you have to:
Save the information to the database in such a way that it is not considered as "tentative"
business information,
Design the confirmation procedure to make sure that all the previous interactions have
been successful and then change the information status to real business information.
Example:

Create sales order in draft mode (TUO

Retrieve sales order number (TUO

BE Response)
Update sales order status to "released" (Confirm
EO).

SAP AG 2007

14
SAP AG 2007

BE)

Enterprise Service Protocol (ESP) Runtime

Layers

Business Application
Sequencing Handling Layer
WS-RM Layer
SOAP Processing Layer

15

HTTP Transport Layer

Network & Middleware

HTTP Transport Layer

SOAP Processing Layer
WS-RM Layer

SAP AG 2007

Sequencing Handling Layer

Business Application

SAP AG 2007

Provider
Reception
Transmission
Consumer

System B
System A

ESP-Adapter on Integration
Server

Integration Server
XI P ipeline: P rocessing II

X I Pipeline: Processing I

Transactional Boundary

ID oc
XI

SOAP Runtim e
X I SO AP
A pp

PostP rocessing

M essage Persistence
Inbound
Transactional Boundary

resume

hibernate

W S-A dapter
X I SO AP
A pp

qR FC

Http-R equest

qRF C

Http-Re quest

ICF

SAP AG 2007

16
SAP AG 2007

Integ ration Se rvice uses

configuration info to
instantia te SOAP runtime
together with X I SOAP App

qRFC

Transactional Boundary

Http-R esp onse

XI

PostProcessing

IDoc

M essage
P ersistence

Message Persistence
Inbound

ESP

WS
Service

P reProcessing

Technical
Receiver

SO AP Runtim e

Mapping

E SP
P rotocol

Message
Split

XI S OAP A pp:
use of SOAP-protocols to
transform SOAP-conte xt into
XI-m essage object

Interface
Determination

Receiver
Determination

XI Pipeline

ES P
Protocol

PI Addressing

Integration Engine
Pipeline
Business
Partner
Standard
WS-Stack

XI 3.0

ESP Core
Protocol

WS
Adapter
Web AS

XI 3.0

Business
Partner

WS
Adapter

Standard
WS-Stack

ESP Core
Protocol

Option "SAP"
URL: http://host:port/sap/bc/srt/xip/<interface>/<namespace>/<client>/<Channel>
SOAP Header (Sender, Receiver)
Option "GUID"
URL: http://host:port/sap/bc/srt/xip/<GUID>

SAP AG 2007

17
SAP AG 2007

Direct Connection and Mediated Scenarios

For some scenarios, at runtime it is possible to establish a direct connection between

the sender and receiver.

Application

Application
Process
Integration

SAP AG 2007

Direct connections were formally named "Peer to Peer" connections.

Read the direct connection documentation for more details.

18
SAP AG 2007

Inside-Out and Outside-In Development and

Configuration
Inside-Out:
Development either already exists or starts in the application systems
The configuration is performed also in the application systems

Outside-In (also referred to as "Central"):

Development starts in the Enterprise Services Builder
Precisely in Enterprise Services Repository
Later the SAP Application Systems are able to access and automatically create proxies
for the service interface operations
Similar to PI 3.0/7.0
The configuration is carried out, using the Integration Directory

SAP AG 2007

19
SAP AG 2007

Example Scenario PI 7.1 and Proxy Design

Objects
Service Consumer
Online
Store
[BXT_200]

SAP Process Integration

Outbound TU&C/C
Service Interface

Proxy:
ot_SalesData_Replicate
co_ot_salesdata_replicate
Compensate

Service Provider

Compensate

[XI_BXT_100]

Inbound TU&C/C
Service Interface
it_SalesData_Replicate

Operations Mapping
OnlineStoreCompensate_to_SalesSystemCompensate

Sales
System
[BXT_300]
Proxy:
ii_ot_salesdata_replicate

Compensate
Compensate

Replicate_SalesOrder

Operations Mapping
Replicate_Sales_Order

Replicate_Sales_Order

OnlineStoreSalesOrder_to_SalesSystemSalesOrder

SalesOrder

SalesOrder
OnlineStoreSalesOrderReturn_to_SalesSystemSalesOrderReturn

SalesOrderResponse

SalesOrderResponse

Replicate_SalesOrder

Operations Mapping
Replicate_Invoice

Replicate_Invoice
Invoice

OnlineStoreInvoice_to_SalesSystemInvoice

Replicate_Invoice
Invoice

OnlineStoreInvoiceReturn_to_SalesSystemInvoiceReturn

InvoiceResponse

InvoiceResponse

Replicate_Invoice

Operations Mapping
Confirm

OnlineStoreConfirm_to_SalesSystemConfirm

Confirm

Confirm

Confirm

SAP AG 2007

20
SAP AG 2007

Example Scenario Implementation Steps

(ABAP Outside-In)
Steps:
Create Basic Component is ESR
Create Service Interfaces
Create the Operations Mappings
Update SLD
Check Business Systems configuration in the Integration Directory
Perform Configuration in the Integration Directory
Create Consumer Proxy
Create Consumer Program
Create Provider Proxy
Implement Provider methods
Other Configuration Steps:
WS-RM /SOAP configuration
Configure users authorizations
Configure WS runtime in
application systems
Configure RBAM authorization
at provider side
C:\Documents and
Set tings\i008253\Deskto

C:\Documents and
Set tings\i008253\Deskto

C:\Documents and
Set tings\i008253\Deskto

C:\Documents and
Set tings\i008253\Deskto

C :\Documents and
Settings\i008253\Desk to

SAP AG 2007

21
SAP AG 2007

C:\Documents and
Settings\i008253\Deskto

TU&C/C Consumer Sample Program

To perform a mediated
communication, use the
virtual receiver configured in
the Integration Directory as
destination service.

SAP AG 2007

22
SAP AG 2007

Consumer Example Sequence Creation +

Compensation

SAP AG 2007

23
SAP AG 2007

Consumer Example Tentative Update +

Confirmation

This example applies to direct and mediated connections.

SAP AG 2007

24
SAP AG 2007

RBAM: Role-Based Access Management

Check SAP note 948275 for details.

SAP AG 2007

25
SAP AG 2007

Configuration

Using a Outside-In approach, the Integration Directory replicates all the required Web
service and cache configuration to every SAP Business System.

WS Provider
WS Consumer

WS Consumer

Integration
Directory

WS Provider

WS Provider
WS Consumer

SAP AG 2007

26
SAP AG 2007

ICM Service

Internet Control Framework services are automatically generated by the Integration

Directory

SAP AG 2007

27
SAP AG 2007

SAP NetWeaver Process Integration and

Application Systems Cache
Both SAP NetWeaver Process Integration and Application systems cache are
automatically refreshed.

SAP AG 2007

28
SAP AG 2007

New Queues for Web Services

SAP AG 2007

There are new queues to handle the WS-RM requests.

The CSRT* queues must be registered in order to able to process WS-RM messages.

29
SAP AG 2007

Sequence Processing Steps

SAP AG 2007

Application sends some asynchronous reliable messages

A logical sequence is created to store the messages
(messages are identified by their persist ids)
Due to a Commit, the logical sequence and the messages are stored persistently.
The logical sequence is queued
The queue scheduler (another process), receives the logical sequence and
hands over the logical sequence to the Reliable Messaging Layer.
This is done by performing the following steps on each message:
Read the serialized message from the DB
Restore message to object state
Resume message processing (send messages)
The Reliable Messaging Layer maps logical sequence to WS-RM sequences
If no WS-RM sequence exists, a new one will be created
All messages will be numbered following the WS-RM rules
7.-10. Normal synchronous SOAP processing
Mapping of WS-RM sequences to logical sequences
Analogous to 3
Analogous to 4
13.-17. Returning WS-RM ACKs
Analogous to 5, but instead of sending the messages, the associated service proxy is called.
If this call failed due to some temporary error conditions (locks),
the message will be rescheduled due to a given retry counter
If automatic rescheduling does not solve the error situation,
interactive error solving mechanisms are necessary
30
SAP AG 2007

TU&C/C: Successful Completion Steps

SAP AG 2007

First, a "compensate" message is stored locally.

Later, normal or update operations are executed.
Finally, a confirm message and a commit work is triggered to guarantee the operations.

31
SAP AG 2007

TU&C/C: Error Handling

SAP AG 2007

If a rollback is triggered (either at application level or framework level), the system replicates the
compensate operation.

32
SAP AG 2007

Scenario: EOIO Call with Transient Sequence

Code Example:
DATA: l_seq_prot
DATA: l_seq
DATA: l_proxy
DATA: l_seq_id
DATA: l_request

TYPE REF TO if_wsprotocol_sequence.

TYPE REF TO if_ws_client_sequence.
TYPE REF TO co_my_service_out.
TYPE REF TO srt_seq_id.
TYPE REF TO my_request_type.

CREATE OBJECT l_proxy EXPORTING logical_port_name = 'MY_LP'.

l_seq_prot = l_proxy->get_protocol( if_wsprotocol=>sequence ).
l_seq = l_seq_prot->create_transient_sequence( ).
l_seq_id = l_seq->get_id( ).
l_seq->begin( ).
l_seq_prot->set_client_sequence( l_seq ). "without this statement you get an EO call !!
CALL METHOD l_proxy->my_operation1 EXPORTING output = l_request.
CALL METHOD l_proxy->my_operation2 EXPORTING output = l_request.
l_seq->end( ).
l_seq->begin( ).
l_seq_prot->set_client_sequence( l_seq ).

"exception is raised!
"exception is raised!

<<commit>>

Sequence (object) can only be used for one begin/end cycle

No reuse of sequence allowed
Sequence terminated by Sequence Manager and not by application
after all WS-RM acks were received

SAP AG 2007

33
SAP AG 2007

Scenario: EOIO Call with Persistent Sequence

Create & (Re)use in One Context
Code Example:
DATA: l_seq_prot
DATA: l_seq
DATA: l_proxy
DATA: l_seq_id
DATA: l_request

TYPE REF TO if_wsprotocol_sequence.

TYPE REF TO if_ws_persistent_sequence.
TYPE REF TO co_my_service_out.
TYPE REF TO srt_seq_id.
TYPE REF TO my_request_type.

CREATE OBJECT l_proxy EXPORTING logical_port_name = 'MY_LP'.

l_seq_prot = l_proxy->get_protocol( if_wsprotocol=>sequence ).
l_seq = l_seq_prot->create_persistent_sequence( ).
l_seq_id = l_seq->get_id( ).
l_seq->begin( ).
l_seq_prot->set_client_sequence( l_seq ). "without this statement you get an EO call !!
"has effect at most until l_seq->end( ) !!
CALL METHOD l_proxy->my_operation1 EXPORTING output = l_request.
CALL METHOD l_proxy->my_operation2 EXPORTING output = l_request.
l_seq->end( ).
l_seq = l_seq_prot->reuse_persistent_sequence( sequence_id = l_seq_id )

"enable sequence again

l_seq->begin( ).
"appending calls to the above sequence
l_seq_prot->set_client_sequence( l_seq ). "without this statement you get an EO call !!
CALL METHOD l_proxy->my_operation3 EXPORTING output = l_request.
CALL METHOD l_proxy->my_operation4 EXPORTING output = l_request.
l_seq->end( ).
<<commit>>

l_seq->terminate( ).

"no more messages will be sent on this sequence

Sequence (object) can only be used for one begin/end cycle

Reuse of sequence allowed
Sequence must be terminated by application

SAP AG 2007

34
SAP AG 2007

Scenario: EOIO Call with Persistent Sequence

Create & Use in Different Contexts (2/2)
Code Example:
DATA: l_seq_prot
DATA: l_seq
DATA: l_proxy
DATA: l_seq_id
DATA: l_request

TYPE REF TO if_wsprotocol_sequence.

TYPE REF TO if_ws_persistent_sequence.
TYPE REF TO co_my_service_out.
TYPE REF TO srt_seq_id.
TYPE REF TO my_request_type.

DATA: l_seq_persist

TYPE REF TO cl_SOAP_sequence_manager.

*context B (seq_id is transferred from context A to context B somehow)

CREATE OBJECT l_proxy EXPORTING logical_port_name = 'MY_LP'.
l_seq_prot = l_proxy->get_protocol( if_wsprotocol=>sequence ).
l_seq = l_seq_prot->reuse_persistent_sequence( sequence_id = l_seq_id ).

"enable sequence again

l_seq->begin( ).
"appending calls to the above sequence
l_seq_prot->set_client_sequence( l_seq ). "without this statement you get an EO call !!
CALL METHOD l_proxy->my_operation3 EXPORTING output = l_request.
CALL METHOD l_proxy->my_operation4 EXPORTING output = l_request.
l_seq->end( ).
<<commit>>

l_seq->terminate( ).

"no more messages will be sent on this sequence

Sequence has to be terminated by application

SAP AG 2007

35
SAP AG 2007

Scenario: TU&C/C

Code Example:
DATA: l_seq_prot
DATA: l_seq
DATA: l_proxy
DATA: l_seq_id
DATA: l_request

TYPE REF TO if_wsprotocol_sequence.

TYPE REF TO if_ws_persistent_sequence.
TYPE REF TO co_my_TU&C/C_service_out.
TYPE REF TO srt_seq_id.
TYPE REF TO my_request_type.

CREATE OBJECT l_proxy EXPORTING logical_port_name = 'MY_LP'.

l_seq_prot = l_proxy->get_protocol( if_wsprotocol=>sequence ).
l_seq = l_seq_prot->create_transient_sequence( on_failure = X ).
*register compensate message
l_seq->begin( ).
l_seq_prot->set_client_sequence( l_seq ).
CALL METHOD l_proxy->my_compensate EXPORTING output = .
l_seq->end( ).
*synchronous tentative update calls
CALL METHOD l_proxy->my_tentative_update1 EXPORTING output = .
CALL METHOD l_proxy->my_tentative_update2 EXPORTING output = .
*send confirm message
CALL METHOD l_proxy->my_confirm EXPORTING output = .
<<commit>>

Dependent on the use case, the compensate message can be sent on failure or triggered by
commit
The runtime does not know the TU&C/C type of an operation
Only the scheduling kind of a sequence and derived design-time features are known
(e.g. CommitHandling, Blocking, TransactionHandling, ReliableMessaging,
MessageExchangePattern)

SAP AG 2007

36
SAP AG 2007

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 noninfringement.
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.

SAP AG 2007

37
SAP AG 2007