deltainfo sap bcmehp4

Ramp Up Knowledge Transfer SAP Bank Communication Management in

Enhancement Package 4 for SAP ERP 6.0

Delta Presentation

Christian MnichSolution Manager Suite Solution ManagementSAP AG

October, 2008

SAP AG 2009. All rights reserved. / Page 2

Legal Disclaimer

This presentation 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.

1. Overview

2. Activation of SAP Bank Communication Management

3. Functional enhancements

4. Enhancements SAP Integration PAckage for SWIFT

5. ES Bundle Bank Communication Management

6. Important notes

7. Further information

Content

SAP 2008 / Page 4

SAP Enhancement Packages & SAP ERP 6.0

Delivering Continuous Innovation Around a Stable Core

Quick facts about SAP ERP 6.0 Launched in June 2006

Built on SAP NetWeaver 7.0

More than 5,000 productive systems (as of December 2007)

Platform upon SAP will deliver future software innovations

Software innovations delivered via SAP Enhancement Packages

SAP Enhancement Package 3 for SAP ERP 6.0 in ramp-up since December 7th 2007BUSINESS SUITE Stable core

SAP NetWeaver

SAP ERP 6.0

Enhancement packages

2006 2008 2010 2012+

What are Enhancement Packages?

Optionally installed and activated software innovations for SAP ERP 6.0

Software innovations include

UI simplifications

Functional enhancements

Enterprise services

Cumulative in nature: current enhancement packages contain all previous packages

Enhancement packages are not support packages

SAP 2008 / Page 5

Improved Software Lifecycle

Preamble

SAP enhancement packages are shipped as a delta shipment to SAP ERP 6.0

Selective Installation

Each SAP Enhancement Package contains

new versions of existing software components

You only update software components, which

are related to the functionality you want to use.

After installation:

No UI or process change until a business function is activated

No implications on the underlying NetWeaver platform, however SAP Enhancement

Packages require defined ERP support package stack

Selective Activation

New functionality must be explicitly

switched on to become active in the system.

If activated:

Changes are predictable, only well described changes in the activated areas.

Testing is simplified with templates, provided for every business function

Mandatory

Optional

EnhancementPackages

Selective update - Example

Support Packages

Installation of New Functionality Separated From Activation via Switch Framework

SAP 2008 / Page 6

Benefits of SAP Enhancement Packages

Versus Release Upgrades

No upgrade of hardware and SAP NetWeaver

Selective component-wise installation

No migrations of data / customizing

No table conversions / XPRAs

Only changed and new objects delivered (delta shipment)

No upgrade customizing

All innovations can be activated with switches

Explicit activation separately for each business function

Schedule for activation independent from schedule of IT activities

Well-documented test scope for each business function

UI changes only occur in activated parts

No further modification clearing after activation

LEAN INSTALLATION OPTIONAL ACTIVATION

Lower hardware cost

Lower manual effort

Lower risk through unchanged system behaviour

Faster installation

Less effort for modification adjustment

Time of adoption is driven by business

Adoption of innovations in digestible portions

No disruption of the running business.

Flexibility to satisfy innovation needs from different business areas in a decoupled way.

Easier integration and acceptance testing

Less end-user training

F

A

C

T

S

F

A

C

T

S

B

E

N

E

F

I

T

S

B

E

N

E

F

I

T

S

Clear separation of new functionality

in enhancement packages and

corrections in support packages

Reduced effort for testing and no end-

user training required when applying

SAP enhancement packages

Adding new functionality predictable

and controllable

Improvement Benefits

SAP NetWeaver 7.0

SAP ERP 6.0

BUSINESS SUITE - Stable Core

EHP EHPEHP

EHP EHP

New With SAP Enhancement Package 4 for SAP ERP:

SAP Enhancement Packages for SAP NetWeaver

EHP 4 components for SAP ECC

Server 6.0 always require SAP

enhancement package 1 for SAP

NetWeaver 7.0

Optional deployment of SAP enhance-

ment package 1 for SAP NetWeaver

7.0 usage types, e.g. Portal

SAP 2008 / Page 7 / EHP Technology Facts 3.0 / Christian Oehler

Comparing SAP Enhancement Packages for

SAP ERP and SAP NetWeaver

SAP ERP

Installation Procedure Impact of Installation Selective Activation

Efficient and fast installation with EHP

installer based on

proven SAP software

lifecycle management

tools

New functions are switched on selectively

(ABAP switch

framework)

SAP provides an impact analyzer tool and test

case templates

No UI or process change for end

users after

installation of EHP

Efficient and fast installation with EHP

installer based on

proven SAP software

lifecycle management

tools

Switching procedure between old and new

UI screens is provided

No UI or process change for end users

after installation of

EHP

NW EHP adds new functionality, but does

not replace existing

functionality

SAP

NetWeaver

SAP

Enhancement

Packages for


SAP NetWeaver 7.0(foundation for the SAP Business Suite)

EhP EhPEhP

SAP Business Suite

Continuous Innovation

ERPCRM SCM

PLMSRM

EhP EhPEhP

Increasing flexibility through composition

Deploying business innovation with SAP

enhancement packages

across the SAP

Business Suite

One active repository for co-innovation and

governance

No

n-S

AP

Outlook

EhP EhP

Composite Applications

SAP NetWeaver

Accelerated Innovation

PI 7.1 CE 7.1


Get Started - Enhancement Package Infocenter

http://service.sap.com/erp-ehp

What IT professionals must know

about SAP Enhancement PackagesSAP Enhancement Packages -

Frequently Asked Questions

Lifecycle of SAP

Enhancement Packages

SAP EHP Technology Facts

SAP Enhancement Package

Strategy for SAP ERP

ERP@BPX & EHP Forum

& Wiki in SDN

SAP EHP Info Center

1

2

3

4

5

6

Treasury Applications From SAP

SAP Bank Communication Management is a part of Treasury Applications from SAP

Treasury applications from SAP

SAP Treasury and Risk Management

Risk Analyzer

Transaction Manager

SAP Bank Communication Management

SAP Cash & Liquidity Management

SAP In-House Cash

Cash Management Liquidity Planning

Credit Risk Market Risk Portfolio Analyzer

Hedge Mgt Exposure Mgt

MM FX SEC COMDER DEB

Manage Financial

Risks

Manage Financial

Instruments

Manage Cash



enables corporate customers connecting

via SAP NetWeaver Process Integration to

the SWIFT Net Interface

SAP Bank Communication Management is

part of SAP ERP Core and is available since

SAP ERP 6.0, Enhancement Package 2


includes SAP Integration Package for

SWIFT

Functionalities of SAP Bank Communication Management

Logical structuring of payments into batches

Multiple approval levels for outgoing payments

Audit trail for payment approval decisions along with digital signatures for internal

audit

Analysis of payment status information and full payment-flow transparency

SWIFTNet interface integration using SAP Integration Package for SWIFT


New since SAP ERP 6.0, Enhancement Package 2

Payment

Run

Status Monitor

SAP ERP

GL

Payroll

Treasury

In house

cash

SAP

Integration

Package for

SWIFT

SAP 2008 / Page 13

Aggregate

Payments

Exception

Handling

Approval

Workflow

Digital

SignaturesTransmit Payment

Workflow

Bank Communication Process Flow

Execute

Payment

Program

Create

Payment

Order

Import

Bank

Statement

Post/Processing

and

Clearing

SAP Integration

Package for

SWIFTSWIFTAlliance

Access /

Gateway

SAP NetWeaver

Process Integration

SAP Bank

Communication

Management

SAP ERP

Create Batch

Payment Approval

Work List

Security

- Approval workflow

- Authorization

- Digital signature

Receive Status

Messages

Bank Statement

Routing

Mapping

Security

Encryption

Digital Signature

Resource

Adapter

SWIFTNet

Prerequisites and Limitations

Preconditions

Minimum release - SAP ERP 6.0, Enhancement Package 2 or Enhancement Package 4

The usage of the SAP Payment Program (F110 or F111)

The usage of Payment Medium Workbench and their formats

Limitations

Currently no IDoc support in standard*

Currently no support of Payment Engine and SAP for Banking

Currently no support of industry solutions using Financial Accounting (FI-CA) such as

Insurance (FS-CD), Utilities, Telecommunication and Public Sector (PS-CD) in standard*

The connection to non SAP Systems or SAP systems on earlier releases than SAP ERP 6.0

can be established via the implementation of SAP In-House Cash

* File based solution (per upload) can be established on project based via SAP Consulting

Simplified and Enhanced Bank Communication

Management with EhP4

Standardization and automation of corporate to bank

communication

Optimization of processes and increased payment flow

transparency through status monitoring

Enhanced straight-through-processing (STP) rates with end-

to-end SWIFTNet integration

Reduced maintenance costs by using global payment

standards

Includes ES bundle for the creation and status tracking of

payment orders as well as bank statements

Readiness for SEPA and ISO20022

Improved integration with cash management Automated triggering of follow-up activities via BAdI Indication of urgent payments in the payment monitor New services for payment advice Enhanced SEPA support Enhanced reporting capabilities Capability to assign additional approval users for dual control (Security)

Payment data is highly sensitive and requires

sophisticated security processes to meet ever-increasing

regulatory mandates

Security gaps during payment file transfer (authorization,

signature, and encryption are often not part of the

solution)

High levels of manual processing, productivity losses,

excessive exception handling, and an overall lack of

transparency into payment flows

Missing straight-through processing

Delivered by Business Function FIN_FSCM_BNK

** Improvements

*Customer business challenges Business value

* Improvements

Initiate

payments

Batch

payments

Send

payment

media

Update

status

monitor

Approve

paymentsInvoice * * *

Overview

Enhancement Package 4 for SAP ERP 6.0

Improved Service Enabling

New Interfaces for credit

and debit advice

ENTERPRISE SOA

Capability to assign

additional approval users

for dual control

Enhanced encryption

capabilities

Security

Update Cash Management

Indicate urgent payments in

the payment monitor

Automated triggering of

follow up activities

Simplification

Enhanced reporting

capabilities

Reversal of a merge run

Functional

1. Overview





6. Important notes


Content

Activation of SAP Bank Communication

Management

Access SFW5 Switch Framework

Expand ENTERPRISE_BUSINESS_FUNCTIONS

Activate Business Function (BF) FIN_ FSCM_ BNK

Please note:

The new BF (FIN_FSCM_BNK) includes the functionality already delivered with EhP2

(FIN_FSCM_Integration) plus the enhancements delivered with EhP4

Customers on EhP2 or EhP3 need to activate BF FIN_FSCM_Integration

Customers on EhP4, already on SAP ERP, EhP2 or EhP3 using SAP Bank Communication

Management select FIN_FSCM_BNK in addition

For customers on

EhP2 or EhP3

For customers

using EhP4

1. Overview





6. Important notes


Content

Update of Cash Management after

Rejection/Resubmission of Documents

Cash Management impact is usually affected in case the payment is resubmitted or rejected

With Enhancement Package 4, the impacts of a resubmission or a rejection of a payment are

automatically updated in Cash Management

Rejected Payments:

value date is set to 31.12.9999 Documents will not appear in Cash Management Reports / Payment should be manually reversed (FBRA)

Resubmitted payments:

value date is set to resubmission date Cash Management data are adjusted accordingly

after rejection/ resubmissionCash management after payment

Urgent Payments

EhP4 enables now:

indicating of urgent payments in Batch and Payment Monitor (TA BNK_Moni) and in Approval Monitor (BNK_APP)

changing of instruction key (and thus indirectly: urgent and cost assignment) in Batch and Payment Monitor (TA BNK_Moni) and in Approval Monitor (BNK_APP)

Item Level:

Header Level:

Reversal of a Merge Run

EhP4 enables reversing of a merge run created by SAPFPAYM_MERGE (TA FBPM1)

TA: BNK_MERGE_RESET offers test run mode and strict check

RBNK_MERGE_RESET lists all batches belonging to a given merge run with a traffic light

depending on status:

The traffic light in the first column is:

Green: New batches (just entered in the approval process but not processed yet), and no batch (if there

was an error during creation).

Red: Batches in the middle of the approval process.

Yellow: All other batches

Different User ID for Signature

In some systems, normal users are only allowed to log on by single-sign-on (not

even have a password)

For the approval of a payment batch a signature (Password) is required without a password the user can not approve payment batches in SAP Bank

Communication Management

In addition, from a compliance perspective it is necessary to distinguish between

system password and release password

Since Enhancement Package 4 every logon user can be assigned to a specific

signature user password of signature user must be entered

Approval Reporting

In the Batch Monitor transaction BNK_MONI drill down into release history for every

individual batch possible plus display of users that approved it

Up to now no simple list reporting is available that shows directly which user

approved which batches

New Report (BNK_MONIA) for approver reporting available

Drilldown into the monitor BNK_MONI for the chosen batch possible

Rule Currency

Up-to-now:

Batch amounts and maximum payment amounts were converted on the fly and compared to

entries defined in the rules amounts in release process can differ depending on exchange rates application of different rules in release process is possible

Exchange rate type M hard-coded no opportunity to enter another exchange rate type in customizing

Amounts in rule currency not visible in batch monitor explanation of usage of 4-eye rather than 6-eye approval is missing

Now:

Definition of exchange rate type in Basic Settings

Batch amounts and maximum payment amounts converted when batch will be created only

once value fixed on database

Selection Screen of Batch and Payment

Monitor

The Batch and Payment monitor TA BNK_MONI (program BNK_PAYM_MONI_UI)

is a tool expected to be used a lot

Therefore, a user friendly selection screen, with the most important selections on

top and the rest below, or hidden, is needed

The current selection-screen does not exactly meet this requirement and is now

improved with EhP4

BNK_MONI - Status Management -> Batch and Payment Monitor

Take over from Current Processor

Current Processor is a notion in the first approval step (batches can still be edited)

As soon as a user removes payments from a batch (reject or resubmit in TA

BNK_APP), he is labeled Current Processor of that batch

Consequence: all other users loose the Work Item for this batch current processor is the only user who can process this batch (all other users do not have

the batch in TA BNK_APP; only see it in BNK_MONI)

Idea: user who started editing a batch should be the only one who completes it

Drawback: if this user is out of the office (e.g. due to sick leave), nobody can take over

Solution: Keeping the Current Processor label, but no longer with exclusive rights other users do not loose the work item for this batch other users get a warning (in the BNK_APP application log) if they touch a batch with a different current processor

New message BNK_GENERAL 215: Batch & taken over from user

1. Overview





6. Important notes


Content

Overview and Architecture

Support for SWIFTNet FileAct Real-time mode

Backend-Signature for Payment Medium

SWIFTNet FileAct Transaction Count

Customer-Specific Status Message Processing

Improvements in the integration part of SAP Bank Communication Management

and SAP Integration Package for SWIFT (with SAP ERP 6.0 enhancement

package 4):

Support for SWIFTNet FileAct Real-time mode

Business Background

FileAct allows secure and reliable transfer of files and is typically used to exchange batches of structured financial messages and large reports. FileAct supports tailored solutions for market infrastructure communities, closed user groups and financial institutions. FileAct is particularly suitable for bulk payments, securities value-added information and reporting, and for other purposes, such as central-bank reporting and intra-institution reporting.

FileAct is available in two different quality of service levels, one is Store-and-Forward mode the other Real-time mode.

SWIFTNet FileActs store-and-forward capability ensures that your correspondents whether receive your message or they are online at the time of transmission. Messages are delivered when the recipient is ready to receive it. Store-and-Forward is an ideal way to send individual instructions, confirmations and reports to large numbers of correspondents, some of which may be in different time zones.

Real-time messaging provides a lower-cost alternative to store-and-forward for files that are destined for correspondents that are online at the time of transmission. This makes it ideal for sending files to a few large correspondents or market infrastructures.

New Functionality: SWIFTNet FileAct Real-time mode will be supported according to the SCORE standard.


Business Background

End-to-end security is enhanced by means of a checksum or digital signature of critical message

elements like e.g. amount, currency or bank details. Therefore you will be able to ensure the

integrity of generated payment media from the ERP backend system via the SAP Integration

Package for SWIFT on SAP NeWeaver Process Integration until the SWIFT infrastructure

(SWIFTAlliance Access and SWIFTAlliance Gateway).

Certificates are exchanged between the ERP backend system and SAP NeWeaver Process

Integration and a parameter can be set accordingly (VerifyBackendSignature).

Prerequisite:

Component Number Short text Status

FIN-FSCM-BNK 1144603 BCM: Backend-Signature for Payment Medium Released for Customer

FIN-FSCM-BNK 1153053 BCM: Backend-Signature for Payment Medium In Process


SAP NetWeaver

Process

Integration 7.0

SAP ERP 6.0

enhancement

package 4

SSFAF

ile

SWIFTAlliance

Gateway

1

SAP

Integration

Package for

SWIFT 4

Message wrapped

into technical

SWIFT-compliant

envelope

STRUST

2

Visual

Administrator

3

HMAC-SHA 256

key-hashed

message

authentication

code

Import to PI system

to ensure trusted

connection

Creation and export

of ERP system

specific certificate

End-to-end Security


Configuration of ERP (ABAP)

Within the ERP system and transaction

SSFA the SSF Application Digital Signature for Bank Relationship Management needs to be added to the list (FINBRM).

Transaction STRUST is used to first

create the certificate according to

SAPNote 1153053 and then exported for

further handling withing the J2EE

Keystore of SAP NetWeaver Process

Integration.

1

2


Configuration of PI via Visual Administrator (JAVA)

Via the Visual Administrator and the Key Storage Service of the J2EE-Engine of SAP

NetWeaver Process Integration a new View BCM_SWIFT needs to be created and the exported certificate has to be added as described in SAPNote 1144603.

3


Screenshots of Integration Directory

The verification of the transmitted messages can be switched on and of via the

FileActConversionToSWIFTModule parameter VerifiyBackendSignature.4

SWIFTNet FileAct Transaction Count

Business Background

SWIFTNet 6.1 supports an enhanced header structure which Corporates might use to profit from

a transaction-based pricing model. The Transaction Count and Request Type

Overwrite will be supported according to the SWIFTNet FileAct Implementation

Guide (SW4CORP_FAIMPGUIDE_May2008_V9.pdf).

Prerequisite:


FIN-FSCM-BNK 1084448 BNK: Support of FileAct Request Type Released for Customer

FIN-FSCM-BNK tbd BCM: Support of FileAct TtlNbOfTxs In Process

Customer-Specific Status Message Processing

Business Background

Within Corporate-to-Bank communication Banks will be able to provide specific status messages

which need to be mapped to the Batch and Payment Monitor (BNK_MONI) of SAP Bank Communication Management.

There is an example implementation of a bank-specific status message mapping to highlight the

usage of the Enterprise Service CollectivePaymentOrderNotification (CPON). It enables the Content Conversion functionality of SAP NetWeaver Process Integration to extract the relevant

information out of the flat-file and map to the SAP standard interface.

Prerequisite:


FIN-FSCM-BNK tbd SIPS: Customer-specific Status Message Processing In Process

1. Overview





6. Important notes


Content

SWIFT Alliance Access / Gateway

SAP NetWeaver

Settle &

Pay

House Bank


= Enterprise Services

Payment

Run

Grouping &

MergingApproval

Request

Payment Order

SWIFT File

creation /conversion

SWIFTNet

Set Status

Payment Medium Created

Transfer

Payment

acknowledged

Set Status

Payment Received by

SWIFT

Set Status

Payment Received by

Bank

Payment

acknowledged

Set Status

Accepted by

Bank

Enterprise Service Bundles for Financials

Enterprise Service Bundle for Bank Communication Management

Request

payment

order

Maintain

payment order

confirmation

Create bank

account

statement

Status Monitor

Process

End-of-Day

Bank Statement

Request

payment order

as bulk

Process

Payment

Advice

Create payment

advice

(Incoming, from

bank)

1. Overview





6. Important notes


Content

Important Notes

SAP Notes search via SAP Service Marketplace

Access and download via http://service.sap.com/notes

Number Short text Status

1041016 Workflow setup in new installations for BRM Released for Customer

1065383 Lost Workflow Attachments and Problems with Resubmit Released for Customer

1072573 BNK: Shortdump when saving Batching Rule Released for Customer

1073120 Wrong message BNK_General213 when processing a

batch

Released for Customer

1094184 No status change when batch is approved Released for Customer

1095118 Release of many batches produces many Payment Media

pop-ups

Released for Customer

1100254 Resubmission: Factory calendar 99 does not exist (T0209) Released for Customer

1105027 SAPSQL_ARRAY_INSERT_DUPREC on final approval Released for Customer

1107851 Shortdump when saving Batching Rule 2 Released for Customer

1124930 Batches get lost after first approval Released for Customer

1132478 Undo Cross-Payment Run Payment Media creation Released for Customer

1257147 Checks in Bank Communication Management Released for Customer

Ramp Up Knowledge Transfer

How to access the Learning Maps for Bank Communication Mgt.

Access via service.sap.com/rkt

Select Business Suite SAP ERP SAP ERP 6.0 Enhancement Packages FI:Treasury

RKT Workshops

Ramp Up knowledge transfer workshops

currently planned for EMEA (Walldorf, Germany, Nov.12), America

(Newtown Square, Nov.18) and APJ (Singapore, December 4)

Due to budget freeze there is currently no confirmation on Workshops.

RKT Workshop in Walldorf will take place on November 12.

Interested colleagues, partners and customers please send a email to

[email protected]

SAP Asia Pacific Treasury & Real Estate Management Conference 08

December 1-3, 2008, Swissotel, Singapore

www.sap.com/treasury/singapore

1. Overview





6. Important notes


Content

Adolf Wrth GmbH & Co. KG Streamlines

Bank Communication with SAP

ERP

QUICK FACTS

Company

Name: Adolf Wrth GmbH & Co. KG

Location: Knzelsau, Germany

Industry: Global trade

Products and services: Fastening and assembly technology

Revenue: 814 million in 2006

Employees: 4.500 (Germany)

Web site: www.wuerth.com

SAP solution and services: SAP Ramp-Up program, SAP enhancement package for SAP ERP 6.0

Implementation partner: SAP Consulting

SAP Bank Communication Management and the SAP Integration

Package for SWIFT have streamlined

our banking communications into a

single, efficient channel that makes

payments and deposits to our

accounts simple and direct.

Claus Wild

Project Manager Financials

Adolf Wrth GmbH & Co. KG

Challenges and Opportunities

Standardization and automation of

Corporate to Bank communication

Optimization of processes and

increased payment flow transparency

through status monitoring

Objectives

Fewer bank connections and

enhanced straigt-through processing

rates with end-to-end SWIFTNet

integration

Support systematic tracking during

the whole payment lifecycle

Implementation Highlights

Full implementation within 6 months

including SWIFT infrastructure

Complete support from SAP

Consulting in deploying the new

functionality throughout the

organization

Why SAP?

End-to-end integration paradigm

Most relevant functionality available

on the market

High attention and support due to

Ramp-Up program

Ease of integration with existing

SAP software

Benefits

Enhanced straight-through

processing (STP) rates

More cash flow transparency

and visibility of working capital

Reduced maintenance costs by

using global payment standards

Increased security and compliance

Readiness for SEPA and

UNIFI/ISO20022 standard

Public Web

www.sap.com/treasury

Documentation and Release Notes

http://help.sap.com Documentation / SAP ERP / SAP enhancement package 2 for SAP ERP 6.0 /

SAP ERP Central Component / Financials / SAP Financial Supply Chain Management (FIN-FSCM)

/ Bank Communication Management

ASUG/DSAG: Treasury Special Interest Groups

www.asug.com, www.dsag.com

SAP Service Marketplace (log-on required)

https://service.sap.com/erp-treasury

SAP Community Network (log-on required)

http://sdn.sap.com Enterprise Services WIKI BCM

Contact

Your SAP Account and Consulting Engagement Manager

Further Information

SAP 2008 / Page 48 SAP 2008 / Page 48

Copyright 2008 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.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge 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 and associated logos displayed 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. 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. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrckliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen knnen ohne vorherige Ankndigung gendert werden.

Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte knnen Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwhnte SAP-Produkte und Services sowie die dazugehrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Lndern weltweit. Alle anderen in diesem Dokument erwhnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte knnen lnderspezifische Unterschiede aufweisen.

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthlt nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP-Produkts und ist fr SAP nicht bindend, einen bestimmten Geschftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP bernimmt keine Verantwortung fr Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollstndigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewhr, weder ausdrcklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschlielich, hinsichtlich der Gewhrleistung der Marktgngigkeit und der Eignung fr einen bestimmten Zweck sowie fr die Gewhrleistung der Nichtverletzung geltenden Rechts.

SAP bernimmt keine Haftung fr Schden jeglicher Art, einschlielich und ohne Einschrnkung fr direkte, spezielle, indirekte oder Folgeschden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschrnkung gilt nicht bei Vorsatz oder grober Fahrlssigkeit.

Die gesetzliche Haftung bei Personenschden oder die Produkthaftung bleibt unberhrt. Die Informationen, auf die Sie mglicherweise ber die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP untersttzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewhrleistungen oder Zusagen ber Internetseiten Dritter ab.

Alle Rechte vorbehalten.

SAP 2007 / Page 49

deltainfo sap bcmehp4

Documents

sap product

informationcontent sap

switch framework sap

current enhancement

enhancement packages2006

activated software innovations

activated areas

business function schedu