Professional Documents
Culture Documents
Life Cycle Management in SAP Planning and Consolidation 10.0 PDF
Life Cycle Management in SAP Planning and Consolidation 10.0 PDF
Whitepaper:
Life Cycle Management in SAP Planning and
Consolidation 10.0, version for Netweaver
Sheldon Edelstein
SAP Customer Solution Adoption
Applies to:
Summary:
This whitepaper covers the main aspects that should be considered while defining a transport strategy for
SAP Planning and Consolidation 10.0, version for Netweaver (PC10NW). Areas addressed include: the
transport mechanism, transport tools, and approaches for managing changes in the specific context of
PC10NW.
Version:
Updated: 08/08/2012
1. Transport Concepts
1.1 SAP Planning and Consolidation version for Netweaver (PC10NW) 10.0
Architecture
PC10NW is a three layer application composed of a client stack, the back-end NetWeaver ABAP
Application Server, and the database server.
In the PC10NW architecture, all the data and files are stored in the database. Data and files are logically
grouped for storage under a specified environment. The PC10NW application can consist of one or many
PC10NW environments. The configuration of these individual environments can be transported from one
BW system to another (for example from Dev to QA to Prod) through the Netweaver Change and
Transport System.
Source System
Target System
Released Transport
Important Tip:
Not all objects necessary for PC10NW are included in a PC10NW transport. Some objects that may need
to be added to a transport (or manually recreated in the target system) include:
Custom Process Chains
BADIs
Some IMG settings
Logon to Source System via SAP GUI and enter transaction code RSA1 and select Transport
Connection.
In the left column, choose SAP Transport > Object Types
In the middle column, choose More Types > Environment and double-click Select Objects (select the
Environment for which you will be creating a transport):
Grouping
The object collection process can be controlled using GROUPING settings to include only those objects
desired. Options include:
For BPC transports, it is recommended that that you use the “Only Necessary Objects” setting which will
collect all objects required for the selected environment):
Collection Mode:
The system can automatically identify and add the necessary objects to the transport collection, or you
and manually select specific objects.
The recommendation is to allow the system to collect all of the objects automatically, then manually
select/deselect specific objects as required:
You can choose to display the objects in Hierarchical format or List format.
Use drag and drop to move the selected environment to the collection screen
The column labeled TRANSPORT indicates if the object has been selected to be included in the
transport. Right click on a parent node and you can include/exclude all objects associated with the
selected node:
Important Tip:
Right Click on any collection node to view the context menu. The menu will provide options to assist with
object selection, documentation, and version control.
Once all objects that are to be included in the transport are identified, click the Transport Objects button
to create the transport request:
Important Tip:
Note that some of the objects are identified by a GUID (such as with the case of the SAP Environment
Info section above). These GUID identifiers can be interpreted by viewing the control table UJT_GUID:
All the steps are the same as with Normal Mode transports except you will select the Deletion mode
instead.
In the left column, choose SAP Transport > Object Types, in the middle column, choose More Types >
BPC Deletion and double-click > Select Objects:
Important Tip:
If a specific PC10NW object is subject to transport control, do NOT delete the PC10NW object directly from
the target system! This will cause any subsequent transports of this object to fail. Use the “BPC Delete”
transport to remove unwanted objects, this will maintain the ability for the system to find and transport
these objects at a later date.
Important Tip:
It is relatively easy to move from a transport dominated process control system to a system that allows
direct change.
It is a lot more difficult to move from allowing direct change into a more controlled Dev>QA>Prod
transport control process. Once the production system configuration is no longer in sync with Dev system
the transport process can become unusable.
DIMENSIONS
PC10NW transports do not change the technical name of the BW info object associated with a particular
PC10NW Dimension
PROPERTIES
PC10NW transports may change the technical name of the BW info object associated with a particular
PC10NW Dimension
MODEL
As per SAP Note 1689814 “Stabilize Info Cube’s technical name in the modeling process “, PC10NW
parameters (activate model level parameter ENABLE_FIXED_CUBENAME) can be specified in such a
way that transports do not change the technical name of the generated PC10NW model.
Important Note: if the ENABLE_FIXED_CUBENAME parameter is not activated then the technical name
of the model may change during transport and/or the full optimization process. In this case, it is important
not to develop configuration that is directly tied to the technical cube supporting the BPC model.
MULTIPROVIDER
PC10NW transports may change the technical name of the generated PC10NW multi info provider if SAP
Note 1689814 is not implemented and the parameter ENABLE_FIXED_CUBENAME has not been
activated.
The multi-provider technical name will not change if the parameter ENABLE_FIXED_CUBENAME is
activated.
VIRTUAL PROVIDER
The behavior of technical name of virtual provider (which may be used to establish an ODBO connection
to BPC data) acts the same as with the multi-provider, that is, the technical name is does not change if
the parameter ENABLE_FIXED_CUBENAME is enabled.
If the ENABLE_FIXED_CUBENAME is not enabled, the technical id of the virtual provider may change in
the target system.
Important Tips:
Do not change the structure or definition of Planning and Consolidation related data model objects in the
target BW system. This includes objects such as environment (InfoArea), model (Multiprovider and
InfoCube), dimensions (InfoObjects), and properties (InfoObjects). This may cause subsequent transports to
fail.
Conversion Files
Transformation Files
Conversion Files
Transformation Files
Important Tip:
Custom developed process chains (linked into a data manager package) will not be collected for
transport via the PC10NW transport process. You must create a separate standard BW transport to
move any custom process types and/or process chains. These BW objects should be transported before
the BPC objects themselves. In this way the references to the objects will still work when transporting the
BPC objects.
Important Tips:
Deletion of transformation files is not supported with transports, and must be done manually in
each system.
Deletion of conversion files is also not supported with transports, and must be done manually in
each system.
IMPORTANT NOTE: When collecting these objects in the transport manager, there can be a
performance hit if the objects are very large – it is always recommended to therefore only transport the
necessary Data Manager Data Files. Remember that you can unselect the files you do not wish to
transport over. In general, the fewer amounts of files and objects you transport, the faster the transport
collection and execution will run. It is therefore a good idea to inspect which objects are being
transported and perform cleanup maintenance if possible.
Data Manager package prompt selections (these are .esf files that store a particular set of prompts for a
specific data manager package so a user does not need to reenter the same pattern of prompt values
each time they run the same package) can be selected and added into transports:
Web Reports may also be transported, but their location in the transport collection tree is under the
Library node:
5 Journals
The Journal Template may be located under the Journal parent node and selected for transport:
Transporting any data model changes (i.e.: deleting a dimension) that impacts dimensionality will cause
all journal entries in the target system to be deleted.
Important Tip:
It is a best practice to back up all journal entries in the target system prior to transporting any application
changes that may have impacts to journal configuration using the Data Manager Journal Export/Import
packages.
Important Tip:
During the transport process the system checks multiple times for object dependencies. For example,
you cannot transport a Model unless you have already transported the dimensions of the model or have
included the dimension definition in the same transport containing the model definition. Timing of
transports to ensure all dependencies are satisfied can therefore become an important project
management consideration.
SBOP Plan & Consol 10.0 NW Administrator's Guide (sections 5 and 6.7)
SAP Note 1689814 – Stabilize Info Cube’s technical name in the modeling process
This note allows the customer to turn on a setting which keeps the Info Cube’s technical name stable
throughout the landscape. This can be of great value when using the Technical Name in customized
BPC activities (such as loading to a BPC Cube with a DTP).
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10,
z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise
Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered
trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts
Institute of Technology.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by
Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 other
countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius,
and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this
document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies
("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those
that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should
be construed as constituting an additional warrant.