You are on page 1of 48

Ramp Up Knowledge Transfer –

SAP Bank Communication Management in Enhancement Package 4 for SAP ERP 6.0 Delta Presentation

Christian Mnich
Solution Manager Suite Solution Management SAP AG

October, 2008

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.

© SAP AG 2009. All rights reserved. / Page 2

Content

1. 2. 3. 4. 5. 6. 7.

Overview Activation of SAP Bank Communication Management Functional enhancements Enhancements SAP Integration PAckage for SWIFT ES Bundle Bank Communication Management Important notes Further information

SAP Enhancement Packages & SAP ERP 6.0
Delivering Continuous Innovation Around a Stable Core
2006 2008 2010 2012+

Quick facts about SAP ERP 6.0

 

Enhancement packages

SAP ERP 6.0

 

SAP NetWeaver

BUSINESS SUITE – Stable core

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 2007

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 4

Testing is simplified with templates. only well described changes in the activated areas. however SAP Enhancement Packages require defined ERP support package stack Selective Activation  Support Packages  New functionality must be explicitly switched on to become active in the system. After installation:   Selective update .Improved Software Lifecycle Installation of New Functionality Separated From Activation via Switch Framework Preamble Optional SAP enhancement packages are shipped as a delta shipment to SAP ERP 6. If activated:    Changes are predictable. which are related to the functionality you want to use.0 Selective Installation   Enhancement Packages  Each SAP Enhancement Package contains new versions of existing software components You only update software components.Example No UI or process change until a business function is activated No implications on the underlying NetWeaver platform. provided for every business function Mandatory © SAP 2008 / Page 5 .

Benefits of SAP Enhancement Packages Versus Release Upgrades LEAN INSTALLATION        OPTIONAL ACTIVATION F A C T S      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 F A C T S      Lower hardware cost Lower manual effort Lower risk through unchanged system behaviour Faster installation Less effort for modification adjustment B E N E F I T S     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 B E N E F I T S © SAP 2008 / Page 6 .

g.New With SAP Enhancement Package 4 for SAP ERP: SAP Enhancement Packages for SAP NetWeaver Improvement Benefits EHP EHP EHP SAP ERP 6.0 / Christian Oehler . e.0 always require SAP enhancement package 1 for SAP NetWeaver 7.Stable Core   EHP 4 components for SAP ECC Server 6.0 BUSINESS SUITE .0 Optional deployment of SAP enhancement package 1 for SAP NetWeaver 7. Portal Clear separation of new functionality in enhancement packages and corrections in support packages Reduced effort for testing and no enduser training required when applying SAP enhancement packages Adding new functionality predictable and controllable    © SAP 2008 / Page 7 / EHP Technology Facts 3.0 EHP EHP SAP NetWeaver 7.0 usage types.

but does not replace existing functionality  Switching procedure between old and new UI screens is provided © SAP 2008 / Page 8 / EHP Technology Facts 3.0 / Christian Oehler .Comparing SAP Enhancement Packages for SAP ERP and SAP NetWeaver SAP Enhancement Packages for Installation Procedure Impact of Installation Selective Activation SAP ERP  Efficient and fast installation with EHP installer based on proven SAP software lifecycle management tools  No UI or process change for end users after installation of EHP  New functions are switched on selectively (ABAP switch framework)  SAP provides an impact analyzer tool and test case templates SAP  Efficient and fast installation with EHP NetWeaver installer based on proven SAP software lifecycle management tools  No UI or process change for end users after installation of EHP  NW EHP adds new functionality.

1 SAP NetWeaver PI 7.1  Increasing flexibility through composition Continuous Innovation Non-SAP EhP EhP EhP EhP CRM SRM SAP Business Suite EhP EhP SCM PLM EhP EhP  One active repository for co-innovation and governance ERP SAP NetWeaver 7.Outlook Accelerated Innovation Composite Applications … CE 7.0 (foundation for the SAP Business Suite)  Deploying business innovation with SAP enhancement packages across the SAP Business Suite © SAP 2008 / Page 9 / EHP Technology Facts 3.0 / Christian Oehler .

Enhancement Package Infocenter http://service.com/erp-ehp 1 SAP Enhancement Package Strategy for SAP ERP 2 6 SAP Enhancement Packages Frequently Asked Questions What IT professionals must know about SAP Enhancement Packages SAP EHP Info Center 3 5 ERP@BPX & EHP Forum & Wiki in SDN 4 Lifecycle of SAP Enhancement Packages SAP EHP Technology Facts .sap.Get Started .

Treasury Applications From SAP Treasury applications from SAP SAP Treasury and Risk Management Manage Financial Risks Manage Financial Instruments Risk Analyzer Credit Risk Market Risk Portfolio Analyzer Transaction Manager Hedge Mgt MM FX DER Exposure Mgt DEB SEC COM SAP Cash & Liquidity Management Cash Management Liquidity Planning Manage Cash SAP In-House Cash SAP Bank Communication Management SAP Bank Communication Management is a part of Treasury Applications from SAP .

Enhancement Package 2 SAP Bank Communication Management 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 .0.SAP Bank Communication Management  SAP Bank Communication Management 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.

Enhancement Package 2 Status Monitor SAP ERP  GL  Payroll  Treasury  In house Aggregate Payments Exception Handling Approval Workflow Digital Signatures Transmit Payment Payment Run cash SAP Integration Package for SWIFT Workflow © SAP 2008 / Page 13 .SAP Bank Communication Management New since SAP ERP 6.0.

Authorization .Approval workflow .Bank Communication Process Flow SAP ERP SAP Bank Communication Management SAP NetWeaver Process Integration Execute Payment Program Create Payment Order Create Batch Routing Payment Approval Work List Security .Digital signature Mapping Security Encryption Digital Signature SWIFTNet Import Bank Statement Receive Status Messages SAP Integration Package for SWIFT SWIFT Alliance Access / Gateway Post/Processing and Clearing Bank Statement Resource Adapter .

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 . Utilities. 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).SAP ERP 6.0. Telecommunication and Public Sector (PS-CD) in standard* The connection to non SAP Systems or SAP systems on earlier releases than SAP ERP 6.Prerequisites and Limitations Preconditions    Minimum release .

signature. and an overall lack of transparency into payment flows Missing straight-through processing . and encryption are often not part of the solution) High levels of manual processing. excessive exception handling. productivity losses.Simplified and Enhanced Bank Communication Management with EhP4 Delivered by Business Function FIN_FSCM_BNK        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) Invoice Initiate payments * Batch payments *       Approve payments * Send payment media Update status monitor * * Improvements Customer business challenges  Business value 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 endto-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    Payment data is highly sensitive and requires sophisticated security processes to meet ever-increasing regulatory mandates Security gaps during payment file transfer (authorization.

0 Simplification  Functional  Update Cash Management  Indicate urgent payments in the payment monitor Automated triggering of follow up activities Enhanced reporting capabilities Reversal of a merge run   ENTERPRISE SOA   Security  Improved Service Enabling New Interfaces for credit and debit advice Capability to assign additional approval users for dual control Enhanced encryption capabilities  .Overview Enhancement Package 4 for SAP ERP 6.

Overview Activation of SAP Bank Communication Management Functional enhancements Enhancements SAP Integration PAckage for SWIFT ES Bundle Bank Communication Management Important notes Further information . 7. 2. 4. 3. 5. 6.Content 1.

EhP2 or EhP3 using SAP Bank Communication Management select FIN_FSCM_BNK in addition . already on SAP ERP.Activation of SAP Bank Communication Management    Access SFW5 – Switch Framework Expand ENTERPRISE_BUSINESS_FUNCTIONS Activate Business Function (BF) FIN_ FSCM_ BNK For customers using EhP4 For customers on EhP2 or EhP3 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.

7. 2.Content 1. 4. 3. 5. Overview Activation of SAP Bank Communication Management Functional enhancements Enhancements SAP Integration PAckage for SWIFT ES Bundle Bank Communication Management Important notes Further information . 6.

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 Cash management after payment … … after rejection/ resubmission .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.

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). Yellow: All other batches . Red: Batches in the middle of the approval process.

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 . 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.Different User ID for Signature  In some systems.

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 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   Now:   .

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.Status Management -> Batch and Payment Monitor . is needed  The current selection-screen does not exactly meet this requirement and is now improved with EhP4 BNK_MONI . with the most important selections on top and the rest below. or hidden.

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 . 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. 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. due to sick leave…).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).g. nobody can take over  Solution: Keeping the ‘Current Processor’ label.

Content 1. 6. 4. 5. 7. 3. 2. Overview Activation of SAP Bank Communication Management Functional enhancements Enhancements SAP Integration PAckage for SWIFT ES Bundle Bank Communication Management Important notes Further information .

Overview and Architecture 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 Backend-Signature for Payment Medium   SWIFTNet FileAct Transaction Count Customer-Specific Status Message Processing .

Store-and-Forward is an ideal way to send individual instructions. confirmations and reports to large numbers of correspondents. and for other purposes. closed user groups and financial institutions. securities value-added information and reporting. FileAct is available in two different quality of service levels. . one is Store-and-Forward mode the other Real-time mode. Messages are delivered when the recipient is ready to receive it. some of which may be in different time zones. This makes it ideal for sending files to a few large correspondents or market infrastructures. FileAct is particularly suitable for bulk payments. SWIFTNet FileAct’s store-and-forward capability ensures that your correspondents whether receive your message or they are online at the time of transmission.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. such as central-bank reporting and intra-institution reporting. 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. New Functionality: SWIFTNet FileAct Real-time mode will be supported according to the SCORE standard.

amount. 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).Backend-Signature for Payment Medium Business Background End-to-end security is enhanced by means of a checksum or digital signature of critical message elements like e. currency or bank details.g. Prerequisite: Component FIN-FSCM-BNK FIN-FSCM-BNK Number 1144603 1153053 Short text BCM: Backend-Signature for Payment Medium BCM: Backend-Signature for Payment Medium Status Released for Customer In Process . Certificates are exchanged between the ERP backend system and SAP NeWeaver Process Integration and a parameter can be set accordingly (VerifyBackendSignature).

0 enhancement package 4 3 SAP NetWeaver Process Integration 7.Backend-Signature for Payment Medium SAP ERP 6.0 SSFA 1 Visual Administrator SAP Integration Package for SWIFT STRUST 2 File 4 SWIFTAlliance Gateway Creation and export Import to PI system to ensure trusted of ERP system connection specific certificate HMAC-SHA 256 key-hashed message authentication code Message wrapped into technical SWIFT-compliant envelope End-to-end Security .

.Backend-Signature for Payment Medium Configuration of ERP (ABAP) 1 Within the ERP system and transaction SSFA the SSF Application „Digital Signature for Bank Relationship Management“ needs to be added to the list (FINBRM). 2 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.

Backend-Signature for Payment Medium Configuration of PI via Visual Administrator (JAVA) 3 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. .

.Backend-Signature for Payment Medium Screenshots of Integration Directory 4 The verification of the transmitted messages can be switched on and of via the FileActConversionToSWIFTModule parameter „VerifiyBackendSignature“.

Prerequisite: Component FIN-FSCM-BNK FIN-FSCM-BNK Number 1084448 tbd Short text BNK: Support of FileAct Request Type BCM: Support of FileAct TtlNbOfTxs Status Released for Customer In Process .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 <TtlNbOfTxs> and Request Type Overwrite <Request Type> will be supported according to the SWIFTNet FileAct Implementation Guide (SW4CORP_FAIMPGUIDE_May2008_V9.pdf).

Prerequisite: Component FIN-FSCM-BNK Number tbd Short text SIPS: Customer-specific Status Message Processing Status 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. 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. There is an example implementation of a bank-specific status message mapping to highlight the usage of the Enterprise Service „CollectivePaymentOrderNotification (CPON)“.

6.Content 1. 5. 2. Overview Activation of SAP Bank Communication Management Functional enhancements Enhancements SAP Integration PAckage for SWIFT ES Bundle Bank Communication Management Important notes Further information . 4. 7. 3.

Enterprise Service Bundles for Financials Status Monitor = Enterprise Services Enterprise Service Bundle for Bank Communication Management Settle & Pay SAP Bank Communication Management Payment Run Grouping & Merging Approval Request Payment Order Set Status “Payment Medium Created” Set Status “Payment Received by SWIFT” Set Status “Payment Received by Bank” Set Status “Accepted by Bank” Request Request payment order payment order as bulk Maintain payment order confirmation SAP NetWeaver SWIFT File creation /conversion Process End-of-Day Bank Statement Create bank account statement SWIFT Alliance Access / Gateway SWIFTNet Payment acknowledged Payment acknowledged Transfer Process Payment Advice House Bank Create payment advice (Incoming. from bank) .

Overview Activation of SAP Bank Communication Management Functional enhancements Enhancements SAP Integration PAckage for SWIFT ES Bundle Bank Communication Management Important notes Further information . 3. 5. 7. 2.Content 1. 4. 6.

sap.Important Notes SAP Notes search via SAP Service Marketplace Access and download via http://service.com/notes Number 1041016 1065383 1072573 Short text Workflow setup in new installations for BRM Lost Workflow Attachments and Problems with Resubmit BNK: Shortdump when saving Batching Rule Status Released for Customer Released for Customer Released for Customer 1073120 1094184 1095118 1100254 Wrong message BNK_General213 when processing a batch No status change when batch is approved Release of many batches produces many Payment Media pop-ups Resubmission: Factory calendar 99 does not exist (T0209) Released for Customer Released for Customer Released for Customer Released for Customer 1105027 1107851 1124930 1132478 1257147 SAPSQL_ARRAY_INSERT_DUPREC on final approval Shortdump when saving Batching Rule 2 Batches get lost after first approval Undo Cross-Payment Run Payment Media creation Checks in Bank Communication Management Released for Customer Released for Customer Released for Customer Released for Customer Released for Customer .

sap.com/rkt Select Business Suite  SAP ERP SAP ERP 6. Access via service.0 Enhancement Packages  FI:Treasury .Ramp Up Knowledge Transfer How to access the Learning Maps for Bank Communication Mgt.

Singapore www.com/treasury/singapore . partners and customers please send a email to christian.mnich@sap.sap. Interested colleagues. December 4) Due to budget freeze there is currently no confirmation on Workshops.12). Swissotel. 2008. RKT Workshop in Walldorf will take place on November 12.com SAP Asia Pacific Treasury & Real Estate Management Conference 08 December 1-3.RKT Workshops Ramp Up knowledge transfer workshops currently planned for EMEA (Walldorf. Nov. America (Newtown Square. Nov.18) and APJ (Singapore. Germany.

6. 5. 7. 4.Content 1. 2. 3. Overview Activation of SAP Bank Communication Management Functional enhancements Enhancements SAP Integration PAckage for SWIFT ES Bundle Bank Communication Management Important notes Further information .

KG Streamlines Bank Communication with SAP® ERP QUICK FACTS Company         Challenges and Opportunities  Why SAP? Name: Adolf Würth GmbH & Co.500 (Germany) Web site: www.” organization Claus Wild Project Manager Financials Adolf Würth GmbH & Co.wuerth. KG Implementation Highlights  Reduced maintenance costs by using global payment standards  Increased security and compliance  Readiness for SEPA and UNIFI/ISO20022 standard .0 Implementation partner: SAP Consulting   End-to-end integration paradigm Standardization and automation of Corporate to Bank communication  Most relevant functionality available on the market  Optimization of processes and increased payment flow transparency  High attention and support due to through status monitoring Ramp-Up program  Ease of integration with existing Objectives SAP software  Fewer bank connections and enhanced straigt-through processing Benefits rates with end-to-end SWIFTNet  Enhanced straight-through integration processing (STP) rates  Support systematic tracking during  More cash flow transparency the whole payment lifecycle and visibility of working capital “SAP Bank Communication Management and the SAP Integration  Full implementation within 6 months including SWIFT infrastructure Package for SWIFT have streamlined our banking communications into a  Complete support from SAP® single.Adolf Würth GmbH & Co. efficient channel that makes Consulting in deploying the new payments and deposits to our functionality throughout the accounts simple and direct.com SAP® solution and services: SAP Ramp-Up program. SAP enhancement package for SAP ERP 6. KG Location: Künzelsau. Germany Industry: Global trade Products and services: Fastening and assembly technology Revenue: € 814 million in 2006 Employees: 4.

asug.com/treasury SAP Service Marketplace (log-on required) https://service.Further Information Public Web www.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.sap. www.com.sap.com/erp-treasury SAP Community Network (log-on required) http://sdn.sap.com Contact Your SAP Account and Consulting Engagement Manager © SAP 2008 / Page 48 .sap.dsag.com Enterprise Services WIKI  BCM Documentation and Release Notes http://help.

The information contained herein may be changed without prior notice. R/3. Die Informationen. indirekte oder Folgeschäden im Zusammenhang mit der Verwendung dieser Unterlagen. or non-infringement. product strategy. Duet. zu welchem Zweck und in welcher Form auch immer. Dieses Dokument enthält nur vorgesehene Strategien. National product specifications may vary. weder ausdrücklich noch stillschweigend. Alle Rechte vorbehalten. graphics. Business ByDesign. R/3. a. unterliegen nicht dem Einfluss von SAP. mySAP. SAP assumes no responsibility for errors or omissions in this document. This document contains only intended strategies. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. developments. xApps. Produkte können länderspezifische Unterschiede aufweisen. Diese Publikation wird ohne jegliche Gewähr. -entwicklung einzuschlagen. The statutory liability for personal injury and defective products is not affected. fitness for a particular purpose. Grafiken.     © SAP 2007 / Page 49 . 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 Vervielfältigung dieser Publikation oder von Teilen daraus sind. PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend. xApp. or other items contained within this material. SAP does not warrant the accuracy or completeness of the information. and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business. 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. und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab. Data contained in this document serves informational purposes only. ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. xApps. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. Texte. eine Produktstrategie bzw. SAP. die Eigentum anderer Softwarehersteller sind. auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen. Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen. Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit. either express or implied. and/or development. SAP garantiert nicht die Richtigkeit oder Vollständigkeit der Informationen. Duet. ByDesign. This limitation shall not apply in cases of intent or gross negligence. hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts. mySAP. special. indirect. This document is provided without a warranty of any kind. SAP. spezielle. links. All other product and service names mentioned and associated logos displayed are the trademarks of their respective companies.com. bereitgestellt. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. aber nicht ausschließlich. einschließlich und ohne Einschränkung für direkte. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. mySAP. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. including but not limited to the implied warranties of merchantability. Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP.. Links oder anderer in diesen Materialien enthaltenen Elemente. or consequential damages that may result from the use of these materials. Alle anderen in diesem Dokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Dies gilt u. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. SAP NetWeaver. ByDesign. The information in this document is proprietary to SAP.    SAP shall have no liability for damages of any kind including without limitation direct. xApp. SAP übernimmt keine Haftung für Schäden jeglicher Art. einen bestimmten Geschäftsweg.com. Business ByDesign. mySAP. SAP NetWeaver. text.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.