Professional Documents
Culture Documents
Whitepaper:
Life Cycle Management in SAP Planning and
Consolidation 10.0, version for Netweaver
Sheldon Edelstein
SAP Customer Solution Adoption
Applies to:
SAP Planning and Consolidation version for Netweaver 10.0
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:
Issued: 07/05/2012
2012 SAP AG
Page 1
2012 SAP AG
Page 2
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.
2012 SAP AG
Page 3
Source System
Objects are
selected for
transport
Target System
Environment
Environment
Objects
Objects
Objects are
created /
modified/
deleted
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:
2012 SAP AG
Page 4
2012 SAP AG
Page 5
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:
2012 SAP AG
Page 6
2012 SAP AG
Page 7
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.
2012 SAP AG
Page 8
2012 SAP AG
Page 9
2012 SAP AG
Page 10
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:
2012 SAP AG
Page 11
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.
2012 SAP AG
Page 12
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.
2012 SAP AG
Page 13
DIMENSIONS
PC10NW transports do not change the technical name of the BW info object associated with a particular
PC10NW Dimension
PROPERTIES
PC10NW transports do not change the technical name of the BW info object associated with a particular
PC10NW Dimension
MULTIPROVIDER
PC10NW transports do not change the technical name of the generated PC10NW multi info provider
MODEL
As per SAP Note 1689814 Stabilize Info Cubes 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.
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.
2012 SAP AG
Page 14
Conversion Files
Transformation Files
2012 SAP AG
Page 15
Conversion Files
Transformation Files
2012 SAP AG
Page 16
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.
2012 SAP AG
Page 17
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.
2012 SAP AG
Page 18
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.
2012 SAP AG
Page 19
2012 SAP AG
Page 20
2012 SAP AG
Page 21
Web Reports may also be transported, but their location in the transport collection tree is under the
Library node:
2012 SAP AG
Page 22
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.
2012 SAP AG
Page 23
2012 SAP AG
Page 24
2012 SAP AG
Page 25
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.
2012 SAP AG
Page 26
2012 SAP AG
Page 27
2012 SAP AG
Page 28
2012 SAP AG
Page 29
2012 SAP AG
Page 30
SBOP Plan & Consol 10.0 NW Administrator's Guide (sections 5 and 6.7)
2012 SAP AG
Page 31
2012 SAP AG
Page 32