Embed Size (px)
Citation preview
1
Enhanced Change and TransportSystem (CTS+) in a SAP NetWeaverPortal landscape
January 2008
2
© SAP 2007 / Page 2
Agenda
1. Transports in the Portal2. What is CTS+3. Transports in the Portal with CTS+
Agenda
The first chapter ‘Transports in the Portal’ provides an overview on the transportmechanisms which are available in the SAP NetWeaver Portal today
In the second chapter, you can find some explanations about what CTS+ is in general.
The third chapter will explain, how CTS+ can be used within a portal landscape.
This presentation assumes that you are using a portal landscape with at least two systemswhere you want to make sure that the content and the look and feel etc is the same bytransporting configurations and content from one system into the other. Some of the slidesrefer to different SP stacks. If this is the case, you will find a hint in the header of the slides.Please take a look.
3
© SAP 2007 / Page 3
Disclaimer
This presentation outlines our general product direction and should not be reliedon in making a purchase decision. This presentation is not subject to your licenseagreement or any other agreement with SAP. SAP has no obligation to pursue anycourse of business outlined in this presentation or to develop or release anyfunctionality mentioned in this presentation. This presentation and SAP's strategyand possible future developments are subject to change and may be changed bySAP at any time for any reason without notice. This document is provided withouta warranty of any kind, either express or implied, including but not limited to, theimplied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in thisdocument, except if such damages were caused by SAP intentionally or grosslynegligent.
4
© SAP 2007 / Page 4
What requires a Transport? (1/2)
My Sales Figures
CorporateBranding
CorporateBranding
Navigation (Roles)Navigation (Roles)
Portal ContentPortal Content
When you look at a portal screen, there are several elements or components which mightrequire a transport
Corporate Branding: the branding of the portal consists of a theme, a framework page, adesktop and rule collections. These objects have to be transported to provide the samelook&feel in the target system
Navigation (Roles): Content in the portal is assigned to a user by the help of roles. Theroles consist of iViews, pages and worksets.
Portal Content: the content displayed within an iView requires a transport as well.Depending on the type of content, different transport mechanisms have to be used. Insome cases, it might be sufficient, to transport only the role with all its dependent objects, inother cases, it might be required to perform additional transports on the backend systemlandscape that is used.
5
© SAP 2007 / Page 5
Transporting Portal Content
The Transport Package Editor
Is used to transport Portal Content as epa-files
Is an export tool – it does not provide any transport logistics ortransport routes
The Package Export Editor is used to transport portal content (including roles, iViews,pages etc). This tool is provided to portal administrators via the system administration role.After having chosen the objects that require an export, a transport package named<name>.epa is created. It can be downloaded to your client and is stored on the server.This epa-file can be imported on the target system.
To learn more about transporting portal content, please have a look athttp://help.sap.com/saphelp_nw70/helpdata/en/c5/56599164d0c04cb566ba0e2d7ed55c/frameset.htm
6
© SAP 2007 / Page 6
What Requires a Transport? (2/2)
KM ContentKM Content
KM ConfigurationsKM Configurations
In addition to the portal content, KMC (Knowledge Management and Collaboration) objectsand configurations require a transport.
7
© SAP 2007 / Page 7
Transporting in Knowledge Management
KM documents
Since SPS 13, a new tool for transporting KM Content is available
WebDAV (Web-based Distributed Authoring and Versioning ) tocopy files in a way similar to file-system copy
ICE (Information and Content Exchange) as online and offlinetransporting mechanism
KM Configurations
A transport option is provided by KM
Collect Configuration objects. Download *.configarchive
Import configarchive via a KM administration
There are three options to transport KM content.Starting with SPS 13, you can use a transport mechanism for KM Content. Thefollowing slide shows a screenshot and explains some details.Transporting via WebDAV is an online procedure that needs to be done manually bycopying files from one folder into another.KM provides the option to use ICE as an online or an offline mechanism. The onlinemechanism requires that you set up one portal as syndicator and one as subscriber.In this setup, folders can be synchronized on a timely basis. To transport contentoffline, a file needs to be created which contains the KM Content that shall betransported. This file can be imported into the target portal by the help of a specialimport screen which is provided by KM. You can find more information about ICEtransports on help.sap.com:http://help.sap.com/saphelp_nw70/helpdata/en/35/4cf72bfe18455e892fc53345f4f919/frameset.htm
KM Configurations can be transported by the help of configarchives. These files arecreated via the KM Administration. You can find more information on help.sap.com:http://help.sap.com/saphelp_nw70/helpdata/en/e1/029c414c79b25fe10000000a1550b0/frameset.htm
8
© SAP 2007 / Page 8
Transporting KM documents
New menu entries have been added tothe Content Administration Role that
allow transporting KM documents
New menu entries have been added tothe Content Administration Role that
allow transporting KM documents
This slide shows a sample screenshot of the transport tool for KM Content that is providedwith SAP NetWeaver 7.0 SPS 13. The tools are part of the Content Administration role andprovide exporting mechanisms as well as screens for importing KM Content.
More information about this tool is provided on help.sap.com:http://help.sap.com/saphelp_nw70/helpdata/en/46/7649426fd759dbe10000000a1553f6/frameset.htm
9
© SAP 2007 / Page 9
Transporting Collaboration Room Templates
Collaboration Room templates consist of worksets and KMconfigurations
To transport worksets, please use the Package Export Editor – asportal content is transported
To transport the KM configurations, please use the mechanism forKM configarchives
Collaboration Rooms can not be transported
Transporting Collaboration Room Templates requires two transports:The workset containing the pages and iViews needed to create a room based on thetemplate have to be transported via the Package Export EditorThe additional configurations like e.g. Room Extensions have to be transported via aconfigarchive.
Rooms that have been created in one system based on a template can not be transported
More information is provided on help.sap.com.http://help.sap.com/saphelp_nw70/helpdata/en/c6/31934259a5cb6ae10000000a155106/frameset.htm
10
© SAP 2007 / Page 10
Sample Process
NW Portal
Exportcontent…
Source Portal Target Portal
…FileShare
..to..
Mark for import
Assign content touser
import
Manual work / Custom tool
Track andplan imports
…FileShare
Store forimport in thenext system
Move File
Enter in list
To simplify things, only portal content is considered on this slide. KM content andconfigurations require a similar process
Looking at the current situation in a portal landscape, there is no tracking tool for portaltransports available. Therefore a special solution needs to be created for portal projects.You could use mounts to avoid moving files around (mount the export folder of the dev-system as the import folder of the Q-system…). In addition some tracking needs to be doneto monitor, which transports are already done, which one can already be imported intowhich system, which one needs to wait for some additional development to finish and whichtransport has already been performed. This results in different tasks and challenges:
For a portal administratorUnderstand what needs to be transportedKeep KM- and Portal-transports synchronized (know about dependencies)Track transports: make sure everything is transported to all systems in a landscape andmaintain the status of transports in a separate place
For setting up business processesFind mechanisms to automate transports for very different file types to simplify theprocess as much as possibleIntegrate tools or requirements for tracking into the applications
11
© SAP 2007 / Page 11
Agenda
1. Transports in the Portal2. What is CTS+3. Transports in the Portal with CTS+
12
© SAP 2007 / Page 12
The Idea
DevelopmentLandscape
QualityLandscape
ProductionLandscape
.
.
.
Transport Transport
Check outs/Deployment
Check outs/Deployment
NetWeaver Change & Transport System
Check in
……EP SystemEP System
AS Java SystemAS Java SystemXI SystemXI System
……EP SystemEP System
AS Java SystemAS Java SystemXI SystemXI System
……EP SystemEP System
AS Java SystemAS Java SystemXI SystemXI System
Deployment
MultipleDevelopmentWorkbenches
Strategic DecisionEnhancement of existing ABAP Change &Transport System to transport multiple objecttypes, including check in / check outprocedures
CTS+ is an extension to the existing Change and Transport System of the ABAP stack. It isnow possible to transport Java-objects by the help of CTS. This extension is representedby the ‘+’ in CTS+.
The idea is to provide all the transport logistics and monitoring options that are well knownfrom the ABAP stack to the Java transports as well.
Transport routes can be set up and can be used for Java transports
Deployment to a development landscape is not part of CTS+. Every developer isresponsible for the deployment from his development system to the central developmentsystem that is used as the first system in a row in the system landscape.
Changes and developments can only be checked in to the transport system after thechanges and developments have become part of the central development landscape (havebeen deployed and are tested by the developer).
For more information, please have a look at help.sap.com:http://help.sap.com/saphelp_nw70/helpdata/en/45/ec25370fdc3481e10000000a1553f6/frameset.htm
13
© SAP 2007 / Page 13
What is CTS,What are the Enhancements of CTS+
Change and TransportOrganizer (CTO)
Transaction: SE09/Se10/SE01
Transport Management System(TMS)
Transaction: STMS
Transport Tools(tp, R3trans, …)
Transport Tools – Java CTS Deploy Web Service
Transport OrganizerWeb UI
Enhanced Change and Transport System
This slides shows the basic elements of CTS+. The more colorful ones have been added toallow the transport of java objects. The other elements are available in CTS.
The Transport Organizer Web UI is an ABAP Web Dynpro Application, which is used withinCTS+ e.g. to create transport requests, attach objects to a transport and monitor the statusof a transport. As this application is displayed in a browser window, the java developer oradministrator doesn’t have to go to the system that performs transports to create atransport request but can use a web interface e.g. as a link from within the portal.
In addition, some transport tools for java objects have been created. The CTS Deploy WebService connects the ABAP transport tools to the deployment tools in the non-ABAPapplications.
Detailed explanations for the elements can be found on help.sap.com.http://help.sap.com/saphelp_nw70/helpdata/en/14/94fc3f8fc2c542e10000000a1550b0/frameset.htm
14
© SAP 2007 / Page 14
TaskABAP-Objects Transport Request
Portal Content Transport via TransportRequests
Portal ContentObjects
iViews, Roles,Pages, Worksets, …
TransportPackage
EPA
Export&
Attach
Add manually
EPA+
Metadata
Portal transport packages can be attached to transport request. During attachment metadata is included that describes the deployment method.
15
© SAP 2007 / Page 15
Landscape - Facts
Two possibilities in general
CTS+ runs on a Dual Stack System (Solution Manager recommended)CTS+ system needs to have NetWeaver 7.0 SPS 13 at leastContent of SAP NetWeaver Portal Systems using older SP Stacks can be transported
CTS+ runs on an ABAP and a separated Java StackCTS+ system needs to have NetWeaver 7.0 SPS 13 at least for both stacksOne Java Stack on NetWeaver 7.0 SPS 13 at least is neededRecommendation: if the Java Stack of a Portal system that is part of the transportroutes is used, all Portals should be on SPS 13.
In general, there are two options concerning the landscape and the location of CTS+:CTS+ can run a dual stack system that has SPS 13 (or up) installed. SPS 12 also offersCTS+ mechanisms, but we recommend to start with SPS 13 as a lot of improvementshave been introduced.CTS+ can be divided between two servers: one providing the ABAP stack and anotherone that has the Java stack installed.
If you decide to use a dual stack system, a good option would be to use the SolutionManager. If you decide to use single stack systems, please be aware of some additionalconfiguration effort.
16
© SAP 2007 / Page 16
Agenda
1. Transports in the Portal2. What is CTS+3. Transports in the Portal with CTS+
17
© SAP 2007 / Page 17
Transporting Possibilities
What you have What to use
Content createdin the PCS
Self-developedapplications
Epa-File viaPackageExport inthe Portal
NWDI
TransportRequest
Download &Attach
Download &Attach
The process for transporting portal content consists of the following steps:1. Choose the content that you want to transport and add it to an epa-file2. Export the epa-file3. Attach the epa-file to a transport order. It depends on the SPS of your portal if you
are able to attach the epa-file to the transport order directly from within the packageexport editor or whether you have to attach it manually afterwards (see followingslides).
Concerning self developed portal applications (par-files) you can choose between twooptions:
Configure the pcd startup properties in a way that par files are included in the epafile when exporting the appropriate iView. The details are described onhelp.sap.com:http://help.sap.com/saphelp_nw70/helpdata/en/10/082840f3ddee01e10000000a155106/frameset.htmUse the NWDI for transporting portal applications. NWDI provides integration withCTS+ as well.
18
© SAP 2007 / Page 18
Transport Landscape (Basic)
NW PortalLandscape
CTS+
Q- Portal
Assign contentto user
Auto-maticimport
viaSDM
StartImport approve
P- Portal
Assign contentto user
Auto-maticimport
viaSDM
StartImport
Dev- Portal
ExportContent
TransportRequest
CreateTrans-portRe-
quest
release
One transport system
Transport Portal ContentEpa-files can be added to a transport request and will be deployed via SDM.In addition, par, ear, sca and sda-files can be transported and deployed.Other file types can be transported. They will be deployed to a specified folder on the filesystem.As soon as the import for a certain transport order is started, the SDM is used to deploythe files on the target system
Landscape ConfigurationThe transport routes for the landscape (e.g. Development-, QA- and Production- system)are configured within the ABAP Stack as known for ABAP Systems. It is now possible toconfigure transport routes for non-ABAP systems.
Support for ‘old’ releases:It is possible to include systems from SAP NetWeaver 04 SPS 09 onwards (SDMavailable to deploy epas) into the transport routes if this system is not used forperforming the transports. Please have a look at SAP note 906120.No functionality within the portal required. (direct integration of CTS+ functionality into thepackage export editor starting with SAP NetWeaver 7.0 SPS 13).
Logging and tracingLogging and tracing mechanisms known from ABAP can be used.
19
© SAP 2007 / Page 19
Transporting withCTS+ SPS 13 and Portal SPS 12
NW Portal
CTS+
Exportcontent…
Source Portal Target Portal
…FileShare
..to..
Transport System
checkinfile
StartImportrelease
Assign content touser
Auto-maticimport
viaSDM
TransportRequestOne transport
system
If the CTS+ system is on SAP NetWeaver 7.0 SPS 13 or up and the portal system on anySPS lower than SAP NetWeaver 7.0 SPS 13, the process for transporting portal content isthe following:
1. Export Content: create epa-file in the source Portal via ‘System Administration’ ->’Transport’ -> ‘Export’
2. Download the epa-file to a file-share.3. Create a transport order in the CTS+ system.4. Attach the epa-file (and any other file that you would like to transport) to a transport
order by the help of the Transport Organizer Web UI (You could include it as an iViewinto one of your portal administration roles)
5. release the transport order6. Start import of the queue via the Transport Management System (transaction STMS)
20
© SAP 2007 / Page 20
The Transport Organizer Web UIFacts
The Transport Organizer Web UI is…
…based on Web Dynpro for ABAP
…delivered with the standard ABAP Stack
…can be integrated into the portal as an iView
CTS+ provides a Web UI for the Transport Organizer. This Web Dynpro application is usedto create transport orders, view them and attach objects. The screenshot is taken from SAPNetWeaver 7.0 SPS 13. In SPS 14 some enhancements are provided to show e.g. moreinformation on the transport orders, their status and the attached objects.
A detailed description on the Transport Organizer Web UI can be found on help.sap.com.http://help.sap.com/saphelp_nw70/helpdata/en/46/028ec7469204abe10000000a114a6b/frameset.htm
The Web Dynpro Application to be used with SPS 13 and up is named ‘cts_browser’ (inSPS 12 ‘sodis_core_wbo’)
21
© SAP 2007 / Page 21
The Transport Organizer Web UIFeatures in SPS 14
Can be used to create transport request
Can be used to attach non-ABAP objects to a transport request
Can be used to view objects within a transport request
Can be used to release transport request
Can be used to monitor transports
Can not be used to start the import of a transport requestUse transaction STMS_QUEUES
The Transport Organizer Web UI is THE TOOL to be used as singleentry point for none ABAP-users to connect to CTS+.
The features described on this slide refer to SAP NetWeaver 7.0 SPS 14. Most of thefeatures are also available in SPS 13.
22
© SAP 2007 / Page 22
Please Consider
What CTS+ does not
Provide Collision Management
Automate Change Recording
Change Request Management
Transport UWL configuration, Users, Groups, User-Role assignments
This slides reflects the current status of transporting portal objects with CTS+ and tries to explain, what CTS+does not.
Provide Collision ManagementEpa-files are imported without any respect to creation date of the epa-file.This means that iViews etc are imported without any respect to change date etc of already existing content.If changes have been done in the target system, they might be overwritten by an import.No version management for single items
Automate Change RecordingYou still have to create epa-files. There is no mechanism that tracks the changes that you do e.g. in theportal content studioYou have to create transport request and attach the epa-files to this transport request. This is done via theTransport Organizer Web UI. (direct integration into the Package Export Editor available from SAPNetWeaver SPS 13 onwards to attach epa directly to Transport Requests).
Change Request ManagementNo link between a transport request and a change request that might have been posted by a userNo control mechanisms that all the content that is needed for a certain change is included in a transportrequest
Transport UWL configuration, Users, Groups, User-Role assignmentsNo automatic deploymentNo special mechanism to attach objects to a transport request
There might be additional things that you know from your current transporting mechanisms which are notprovided by CTS+ and the portal transport mechanisms. In addition, there might be other objects that mightrequire a transport and that are not listed on this slide.
23
© SAP 2007 / Page 23
With at least SPS 13 for CTS+ and Portal
CollectContent…
Source Portal(NW 7.0 SPS13)
Target Portal(NW 7.0 SPS13)
Transport System(Dual Stack NW 7.0 SPS13)
attach
StartImport
Assign content touser
Auto-maticimport
viaSDM
TransportRequest release
One transportsystem
If the CTS+ system and the portal landscape are on NW 7.0 SPS 13, the process fortransporting portal content is the following:
1. Export Content: create epa-file in the source Portal via ‘System Administration’ ->’Transport’ -> ‘Export’ and add what you want to transport
2. Choose the ‘CTS’-Option before exporting – a transport request is suggested by thebackend. The epa-file is automatically attached to the suggested transport request
3. release the transport order4. Start import via Transport Management System (transaction STMS)
ImprovementsCTS+ is integrated into the Package Export Editor – no need to change the tool forexporting content and choosing the right transport request.A Transport Request is provided automatically in the Package Export EditorThe request taken from the backend is the one that is marked as default request. Ifyou don’t want to use this request, you can go to the transport organizer Web UI andcreate another one.For NW 7.0 SPS 13, you could create your own role containing the Package ExportEditor, create a related link for the Transport Organizer and use this link to create yourown transport request.In NW 7.0 SPS 14, the integration is even tighter and a link to the TransportOrganizer is provided directly within the package export editor.
24
© SAP 2007 / Page 24
Terms
Loose CouplingNo direct integration of CTS+ mechanisms into existing portal toolsAdditional tool needed to create transport requests, attach files and releasetransport ordersNeeds to be used for existing portal landscapes (< NW7.0 SPS13)
Close CouplingIs what we are aiming forCTS+ mechanisms are available via additional buttons, links and input-fieldswithin the existing portal transport tools
This slide explains the terms ‘loose coupling’ and ‘close coupling’ which are used on thefollowing slides
25
© SAP 2007 / Page 25
Close Coupling for……Transporting Portal Content (SPS 13 / 14)
Transport Mode CTS providesinformation about the transport
request used
Transport Mode CTS providesinformation about the transport
request used
New fields have been introduced in the Package Export Editor for NW 7.0 SPS 13 / 14. Thescreenshot is taken from SPS 14.
If a CTS+ system is configured in the visual administrator, the user can choose whether hewants to use the ‘classical’ way of transporting via the file system or the CTS+. Thereforethe Drop Down Box ‘Transport Method’ has been introduced.
The data for the fields transport request, owner and description is read from the CTS.There are different transport strategies that can be configured on the CTS system:
SmartThe system creates a transport request (if not already available) and flags it as thestandard request.TaggedThis is configured as the default value in the system. You must have created a transportrequest already in Transport Organizer Web UI and flagged it as the standard request.
The field ‘File name’ can only be edited if ‘File system’ is chosen as a transport method. Ifyou used the file name for information purposes for the administrator, you would now beable to use the field ‘Note’ instead.
The field ‘note’ can be used to add some comments concerning the specific file. The inputfield is only available if ‘CTS’ is chosen as transport method. The text that you enter herewill be added to the Transport Request documentation in the CTS system.
A more detailed description can be found on help.sap.com:http://help.sap.com/saphelp_nw70/helpdata/en/62/117d0cb40145d6bfc655dac7deb9c1/frameset.htm
26
© SAP 2007 / Page 26
Close Coupling for……Transporting KM Documents (SPS 14)
In NW 7.0 SPS 14, the transport for KM documents and folders has been enhanced. Whenexporting documents, you can now also choose a transport request directly from within theexport screen. The mechanisms and the meaning of the input fields is the same asdescribed on the previous slide about the package export editor.
In SPS 13, you can transport KM Documents via CTS+ as well. In SPS 13, loose couplinghas to b used which means that you have to download the exported file and attach itmanually to a transport order.
In both cases (SPS 13 and 14), the file is deployed to the import folder. You can view itunder ‘Pending Imports’ and start the import whenever it fits.
A detailed description can be found on help.sap.com:http://help.sap.com/saphelp_nw70/helpdata/en/46/77da3bb8036ef0e10000000a1553f6/frameset.htm
27
© SAP 2007 / Page 27
Close Coupling for……Transporting KM Configurations (SPS 14)
Alternative mechanism when finalizing a KM Export! No checking whether a restart is required !
In NW 7.0 SPS 14, the transport for KM configurations (configarchives) has beenenhanced. When finalizing an export, you can now also choose the option ‘Finalize viaCTS’. On the following screen, a transport request can be chosen directly from within theexport screen. The mechanisms and the meanings of the input fields are the same asdescribed on the previous slide about the package export editor.
Please be aware that the import of a configarchive requires a restart. CTS+ does notperform this restart automatically and it does not check whether a transport requestrequires a restart.
A detailed description can be found on help.sap.com:http://help.sap.com/saphelp_nw70/helpdata/en/e1/029c414c79b25fe10000000a1550b0/frameset.htm
28
© SAP 2007 / Page 28
Summary
If you already know CTS:Creation of transport routes is very similar (create a non-ABAP-System)Transport Organizer: Use ABAP Web Dynpro Application CTS_BROWSER. Do notuse SE09 for non-ABAP systems like e.g. the portal
If you already know Portal TransportsExisting Transport Tools are used
Transport Package Editor for EPAKM Administration for configarchivesKM Export Tool for KM Documents
CTS+ is (to become) part of existing transport toolsCTS+ needs to be configured in the Visual Admin
CTS+ is the strategic Transport Tool for all SAP Business Suitecustomers to transport all kind of ABAP, non-ABAP and non-SAP
objects
For details about the configuration in the Visual Administrator, please have a look athelp.sap.com:http://help.sap.com/saphelp_nw70/helpdata/en/37/dd368da16f476fad78ca8b51f9b75c/frameset.htm
29
© SAP 2007 / Page 29
Copyright 2007 SAP AGAll 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 changedwithout 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 theirrespective 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 andassociated 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 documentcontains 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, orother 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 ofmerchantability, 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 limitationshall 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 thesematerials 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, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durchSAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können 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 erwähnte SAP-Produkte und Servicessowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken. Produkte können länderspezifische Unterschiede aufweisen.
Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmtenGeschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht dieRichtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, wederausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zwecksowie für die Gewährleistung der Nichtverletzung geltenden Rechts.SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendungdieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinkszugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen überInternetseiten Dritter ab.Alle Rechte vorbehalten.
