Escolar Documentos
Profissional Documentos
Cultura Documentos
Corrections and
Transport System
(CTS) with SAP BW
1
Overview BEx Development Classes
2
Overview
3
Recommended System Landscape
R /3
BW
Development Consolidation Production
B1 B2 B3
4
SAP TMS - Architecture and Terms
Transport
Transport Organizer (CTO) Management
System (TMS)
CTS architecture for BW is the same as for R/3. The same tools / programs are
used.
5
CTS - Post Installation Activities
6
Create transport layers / routes
SAP provides two editors for configuring additional transport routes for more complex system
landscapes:
Hierarchical list editor - The BW Systems in the transport domain and their transport routes are
displayed in a tree structure.
Graphical editor - The BW Systems and their transport routes are displayed graphically. The BW
Systems can be positioned and linked using the mouse. To call the graphical list editor, use
Transaction code STMS. Then, choose Overview -> Transport routes.
To create transport routes, use the mouse to drag the appropriate BW Systems from the node area,
and drop them in the display area. To create a transport route between these BW Systems, from
the screen Display Transport Routes, choose Configuration -> Transport Route -> Create
Transport Route. The mouse pointer becomes a stylus. Using the stylus, draw a line connecting
the two BW Systems between which a transport route is desired. In the dialog box Create
Transport Route, enter the required information for either the consolidation or delivery route.
Save.
7
Checking TMS
All BW Systems in a transport domain communicate with each other using RFC
connections.
To check these RFC connections in the TMS overview, from the TMS initial screen
(Transaction STMS) choose Overview -> Systems -> R/3 System -> Check ->
Connection test. The connection test is performed in both directions . If you find that
there are connection problems with BW Systems having several application
servers, you can change the server configured for the TMS.
To verify the availability of the transport directories of all systems within the domain,
from the TMS initial screen (Transaction STMS) choose Overview -> Systems ->
R/3 System -> Check -> Transport directory.
To test the transport control program tp , from the TMS initial screen (Transaction
STMS) choose Overview-> Systems -> R/3 System -> Check -> Transport tool.
8
Connecting Systems
9
Connecting Systems
You must ensure that the relevant release-dependent extractors are implemented
on the R/3 systems, either the so called PI or PI-A (The BW-BCT extractors wont
work). It is recommended to use the most current version of the extractors.
Transports are only possible between R/3 systems (O1, O2 and O3) or BW
systems (B1, B2 and B3). It is not possible to transport between R/3 and BW
systems. The communication between R/3 and BW systems during the upload
process takes place via RFC.
As of BW release 2.0A the Change and Transport Organizer (CTO) component in
the BW system is always switched ON. It was possible to switch off CTO in 1.2.
There is special logic implemented for BW objects. New BW objects are created as
local objects. Transports of new objects have to be done with the Transport
connection in the AWB. Here dependent objects are collected and the user can
assign a non local dev. class and a transport request to the collected objects.
10
Maintain Source System Mapping (Target System)
During metadata upload the metadata will not be assigned to any development class, the uploaded
metadata cant be transported between BW system. The metadata upload has to be done for each
pair of systems (R/3 OLTP BW) separately.
11
Maintain Source System Mapping (Target System)
12
Transport Process
R /3
1
3
BW
Development Consolidation Production
B1 B2 B3
13
Object Versions
14
Object Versions
15
SAP BW Object Versions
Version
M(odified) 11 11 11 22 22
A(ctive) 11 11 11 22
D(elivery) 11 11 22 22 22
11 install BC
2nd install
2nd delivery (match) BC
delivery from SAP from SAP
16
Metadata: Versions and Transport
A(ctive) 33 11 11
After
import method change
17
Transports in the
source system
18
Transports in the source system
l For BW 2.0 there are only two objects (DataSource and application
hierarchy for data sources) to be transported on the source system
side
If you use business content data sources you can either transport them or activate
them in your source systems.
If you are using CO-PA please read notes 325902, 334991.
19
Manual Transport (of Several DataSources, RSA6)
is also possible
This feature can be used if you want to manually create a transport request with
several DataSources, e.g. if a new system should be provided with those
DataSources.
20
Data Source Maintenance (RSO2): Change Object
Directory Entry Manually
21
Replicate DataSources in BW (Target System)
22
Replicate DataSources
In this case only the selected DataSource will be updated from the source system.
23
Transporting
Objects in BW
24
Grouping
l The setting Save for system copy means that the source system dependent
objects are collected in a transport request. This request can be imported
after a system copy (of BW or source system) in order to map those objects
to the correct source system (with mapping table described above).
25
SAP BW Metadata Visualized: Flow of Information
26
Maintain Source system assignment for object
collector
Source system dependent objects are only collected (for transport) if the
corresponding source system is assigned here.
At least one source system needs to be assigned.
In general all source systems should be assigned that have a corresponding
source system in the target BW system, however, this is only a default for the
object collector. You can still suppress transport of such objects after they have
been collected, if you dont want to transport for all source systems.
27
Collection mode
28
Transport Object Selection
29
Transports connection
1. Select one or
3. Write to
several objects
transport request
New Objects
(Development Class
$TMP) are marked
automatically
30
Transport Information
31
Transporting BW Objects
32
Transport BW Objects For the First Time
Create and use your own development classes, dont use SAP development
classes.
33
Check Transport Status
If there are dependent objects already written to other transport requests make
sure those other requests are released in time.
34
Transporting Changes After First Transport
35
Transport of BEx
Objects
36
BEx Objects
37
Transport of BEx objects
l While making changes to the BEx objects which are no longer $TMP,
the system records the changes to a pre-assigned CTS Request.
n There is one CTS Request, for example, Standard CTS Request" where
changes to the BEx objects can be recorded.
n You can also specify the CTS Request by Development class.
38
Assigning Changes of BEx Objects
l The system has a two level process for choosing the CTS Request
for recording the changes.
n First, the system looks for the CTS Request which is assigned to the
development class of the BEx object.
n If its not found then use the Standard CTS Request.
39
Setting Up the BEx
Development
Classes
40
Maintain Request BEx
41
Change the Standard BEx transport request
To change the
Standard BEx
transport request,
select BEx
development classes
42
Reassign Standard BEx transport request
The standard transport request can be assigned here (additionally to the way
shown before).
From 3.0A on this will be the only way to assign / change the standard transport
request.
43
New transport request for BEx
Create a new
transport request, or
choose an existing
one.
44
Add a Development class
45
Request Assigned to Development class
Create a new
transport request
(Workbench), or
choose an existing
one.
The Development
class now has a
Request assigned.
46
Changing a request for a development class
Highlight the
transport request,
and then select
Change request
47
Executing the
Transport
48
Transport Organizer (SE09), Development System
Choose Workbench
requests for BW
transports
49
Releasing a Task
50
Creating Documentation
Enter any
documentation on this
transport that is
needed. Once finished
select Save and then
Back
51
Releasing the Request
52
Task and Request Released
Make sure that requests with dependent objects are released in the right order.
53
Import Transport Request (STMS), Target System
Make sure that requests with dependent objects are released in the right order.
54
Import Queues
Make sure that requests with dependent objects are released in the right order.
55
Import Queue
Make sure that requests with dependent objects are released in the right order.
56
Transporting a Role
57
Transporting Roles
l Roles that are delivered in the SAP Business Content can be transported via
the Transport connection.
58
Transporting Roles (RSOR)
59
Transporting a Customer-defined Role (PFCG)
60
Information about Transporting Roles
61
Transporting Role objects
62
Additional Information
63
Standard Transport
System (automatic
transport connection)
64
Standard Transport System Activation in BW
(note 356018)
You want to activate the standard transport system in BW. In BW, new objects first are created
automatically as local with development class $TMP. Consequently, no dialog box is displayed first when
you create a new object in which you could write the object to a transport request. When you transport
the objects for the first time, these objects and dependent objects must be collected in the transport
connection of the Administrator Workbench first. A transportable development class is assigned after this
and the objects are written to a request.
This procedure has the advantage that first you need not take care of the transport during the development
of new scenarios. After the scenario has been completed , you only have to collect the objects that are
required in the production system in the transport connection and write them to a request. The objects
not required remain there as internal objects and are not transported. If you write all objects immediately
to requests, it can happen that test objects and productive objects are mixed on one request. In this case,
it is complicated to clean up the requests.
If you activate the standard transport system you dont have to use the object collector but you still have to
take care of releasing transport requests in the right order. Authorizations can be handled by tasks in the
standard way. The users might not have the authorizations to create requests /tasks, so they can only
change objects if the administrator has created a task for them. Especially when working with different
development classes the standard transport system makes correct assignments easier because you
decide your assignment for each single object.
65
(cont.)
l CAUTION!
l Only the newly created objects are recorded from now on. You might still
have to transport the old objects via the transport connection of the
Administrator Workbench.
66
Object Alterability
67
Changing Object Types
Use these settings for system that are nod modifiable. Afterwards, the specified
objects can then be changed despite the system settings.
More details and latest information in note 337950
68
Transport Strategy
69
Transport Strategy Considerations
70
System Landscape
71
Number of Projects on a System
l You have to distinguish between common objects and project specific ones
l You may want to be prepared to split up into different systems later on (e.g.
for performance reasons)
72
Complexity of Scenarios
l The object collector helps you find the dependent objects but transport
requests may contain many objects
73
Responsibility
74
Type of System
75
Transport of BEx Objects
l All changes of BEx objects (in one development class) in a certain period
are transported together (unless standard transport system is activated)
The only way of grouping BEx objects in a transport (after first transport) is by
development class. So you have to determine the granularity you need for
transporting BEx objects and set up development classes accordingly.
No changes to BEx objects are possible if
No BEx request exists
The old BEx request is released and no new one is created
A new BEx request is already assigned but the old one has not been
released
76
Trouble Shooting
77
Transport Problem when Saving Queries
l In the BEx Analyzer, a user attempts to save a query and receives the
following error:
n "The query could not be saved due to a problem in transport
l The error only occurs for query objects which already have a
transportable development class.
78
Problems Creating Change Request
79
Activation Problems After Import
80
Problems With Transported Workbooks
81
Problem with Source System Dependencies
Replicate DataSource
82
Problems Transporting a DataSource
83
Additional Remarks
Currency exchange rates are also loaded from the source system(s),
not transported
84
Additional Remarks (2)
85
Copyright 2001 SAP AG (All rights reserved)
n 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.
n Some software products marketed by SAP AG and its distributors contain proprietary software components
of other software vendors.
n Microsoft , WINDOWS, NT , EXCEL , Word, PowerPoint and SQL Server are registered trademarks of
Microsoft Corporation.
n IBM , DB2, OS/2, DB2/6000, Parallel Sysplex, MVS/ESA, RS/6000, AIX, S/390, AS/400, OS/390, and
OS/400 are registered trademarks of IBM Corporation.
n ORACLE is a registered trademark of ORACLE Corporation.
n INFORMIX-OnLine for SAP and Informix Dynamic ServerTM are registered trademarks of Informix Software
Incorporated.
n UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
n Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and
other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
n HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web
Consortium, Massachusetts Institute of Technology.
n JAVA is a registered trademark of Sun Microsystems, Inc.
n JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology
invented and implemented by Netscape.
n SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink , SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI,
SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered
trademarks of SAP AG in Germany and in several other countries all over the world. All other products
mentioned are trademarks or registered trademarks of their respe ctive companies.
86