Life Cycle Management in SAP Planning and Consolidation 10.0 Version for Netweaver

8/9/2019 Life Cycle Management in SAP Planning and Consolidation 10.0 Version for Netweaver

1/32

Life Cycle Management in SAP Planning andConsolidation 10.0, version for Netweaver

© 2012 SAP AG Page 1

White paper:

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 forSAP Planning and Consolidation 10.0, version for Netweaver (PC10NW). Areas addressed include: thetransport mechanism, transport tools, and approaches for managing changes in the specific context ofPC10NW.

Version:Issued: 07/05/2012


2/32



Table of Contents1. Transport Concepts ................................................................................................................................... 3

1.1 SAP Planning and Consolidation version for Netweaver (PC10NW) 10.0 Architecture ..................... 3

1.2 Main Concepts .................................................................................................................................... 4

1.3 Creating a Transport .......................................................................................................................... 5

1.4 Project Management Considerations ............................................................................................... 13

1.5 Retention of object’s technical id ..................................................................................................... 14

2. File Service Objects ................................................................................................................................. 15

3. Data Manager Objects ............................................................................................................................ 17

3.1 Custom Process Types and Custom Process Chains ......................................................................... 17

3.2 Transformation and Conversion files ................................................................................................ 18

3.3 Data Manager Data Files ................................................................................................................... 19

3.4 Data Manager Selection Prompt Files .............................................................................................. 20

3.5 Data Manager Packages .................................................................................................................... 21

4 Reports, Books, Distributions, and Workbooks ....................................................................................... 22

5 Journals .................................................................................................................................................... 23

6 Administration Parameters ...................................................................................................................... 24

7. Transport tools ........................................................................................................................................ 26

7.1 Transaction Codes SE10 / SE09: ........................................................................................................ 26

7.2 UJT_CHECK_TABLE_ENTRIES ............................................................................................................. 27

7.3 UJS_ACTVIATE_CONTENT ................................................................................................................. 28

7.4 UJA_DATA_CHECKER......................................................................................................................... 29

7.5 UJT_AFTER_FAIL_PROCESS ............................................................................................................... 30

8.0 Resources and Help ............................................................................................................................... 31

8.1 Service Marketplace – Administrator’s Guide .................................................................................. 31

8.2 SAP Notes .......................................................................................................................................... 31

Copyright 2012 SAP AG ............................................................................................................................... 32


3/32



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 logicallygrouped for storage under a specified environment. The PC10NW application can consist of one or manyPC10NW environments. The configuration of these individual environments can be transported from oneBW system to another (for example from Dev to QA to Prod) through the Netweaver Change andTransport System.


4/32



1.2 Main ConceptsThe purpose of a PC10NW transport is to move the configuration of a PC10NW environment across asystem landscape. The new PC10NW transports allow the selection of specific PC10NW configurationobjects at a granular (i.e.: object) level. In the past, PC10NW transports required each transport to includeall PC10NW environment objects. By allowing the transport of specific PC10NW objects, the transportprocess can be precisely controlled.Main changes from earlier Planning and Consolidation versions:

The PC10NW transport is fully integrated with the standard NW CTS (Netweaver Change andTransport System).

Normal and Delete modes of transports are supported. Standard NW based transport transactions and debugging tools can now be used.

Important Tip:

Not all objects necessary for PC10NW are included in a PC10NW transport. Some objects that may needto be added to a transport (or manually recreated in the target system) include:

Custom Process ChainsBADIsSome IMG settings

Released Transport

Objects arecreated /modified/deleted

Objects areselected fortransport

Target SystemSource System

Environment

Objects

Environment

Objects


5/32



1.3 Creating a Transport

Logon to Source System via SAP GUI and enter transaction code RSA1 and select Transport

Connection.In the left column, choose SAP Transport > Object TypesIn the middle column, choose More Types > Environment and double-click Select Objects (select theEnvironment for which you will be creating a transport):


6/32



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 willcollect all objects required for the selected environment):

Collection Mode:

The system can automatically identify and add the necessary objects to the transport collection, or youand manually select specific objects.

The recommendation is to allow the system to collect all of the objects automatically, then manuallyselect/deselect specific objects as required:


7/32



Display Mode:

You can choose to display the objects in Hierarchical format or List format.

Selection of the Environment:

Use drag and drop to move the selected environment to the collection screen

Drag and Drop


8/32



Selection of Objects to be included in the transport:

The column labeled TRANSPORT indicates if the object has been selected to be included in thetransport. Right click on a parent node and you can include/exclude all objects associated with theselected node:

Important Tip:

Right Click on any collection node to view the context menu. The menu will provide options to assist withobject selection, documentation, and version control.


9/32



Create the Transport:

Once all objects that are to be included in the transport are identified, click the Transport Objects buttonto create the transport request:


10/32




11/32


12/32



Deletion Transport:

All the steps are the same as with Normal Mode transports except you will select the Deletion modeinstead.

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, d o 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 transportthese objects at a later date.


13/32



1.4 Project Management Considerations

A decision should be made early in the project to determine how change management for the PC10NWapplication will conducted. PC10NW was designed to allow maintenance independently from acentralized IT process. Each customer should evaluate and determine effective change control for theirlandscapes.

PC10NW allows two significant change control paths that may be followed:

1 - Allow the business users to make changes directly in the production environment via the PC10NW Admin interface. Changes to security and reports are two examples of configuration that may be electedto be controlled directly in the productive environment.

2 - Follow a transport controlled system, using the typical Dev>QA>Prod development landscape. In thisscenario, configuration is first created in the Development system, and then the new configuration istransported in the QA system for detailed testing. Eventually the new configuration is transported into theProduction system, but only when the reliability of the new configuration has been established.

The PC10NW transport process can be configured to allow either option or a combination of theseoptions. A typical example: the PC10NW data model may be strictly controlled using option 2 (the datamodel is under strict transport control), while the control of reports may be less restrictive and option 1(business users are given the ability to create/modify reports directly in Production) is desired.

Important Tip:

It is relatively easy to move from a transport dominated process control system to a system that allowsdirect change.

It is a lot more difficult to move from allowing direct change into a more controlled Dev>QA>Prodtransport control process. Once the production system configuration is no longer in sync with Dev systemthe transport process can become unusable.


14/32



1.5 Retention of object’s technical id Section 6.6 in the SBOP Plan & Consol 10.0 NW Administrator's Guide provides guidance on thechangeability of a technical object’s id.

DIMENSIONSPC10NW transports do not change the technical name of the BW info object associated with a particularPC10NW Dimension

PROPERTIES

PC10NW transports do not change the technical name of the BW info object associated with a particularPC10NW 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 Cube’s technical name in the modeling process “, PC10NWparameters (activate model level parameter ENABLE_FIXED_CUBENAME) can be specified in such away 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 nameof the model may change during transport and/or the full optimization process. In this case, it is importantnot 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 thetarget BW system. This includes objects such as environment (InfoArea), model (Multiprovider andInfoCube), dimensions (InfoObjects), and properties (InfoObjects). This may cause subsequent transports tofail.

http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000735401&_SCENARIO=01100035870000000202&_OBJECT=011000358700000483512011Ehttp://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000735401&_SCENARIO=01100035870000000202&_OBJECT=011000358700000483512011Ehttp://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000735401&_SCENARIO=01100035870000000202&_OBJECT=011000358700000483512011Ehttp://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000735401&_SCENARIO=01100035870000000202&_OBJECT=011000358700000483512011E


15/32



2. File Service ObjectsPC10NW needs to store various files (such as EPM10 reports & schedules, Books, Web reports, scriptlogic files, Data Manager load files, and various log files) that are generated by the system and/or users.These files are stored in a BW structure called the File Service and can be accessed using transaction

UJFS :

Data Manager Load Files

Transformation Files

Reports and Schedule Files

Conversion Files


16/32



Previous version of Planning & Consolidation used the configuration table UJT_TRANS_FIL to controlwhich files were to be included in the transport. This table based configuration is no longer used byPC10NW. Instead, the objects themselves are automatically collected into the transport proposal andthe transport administration can select any, or all, of the components to be included into the transport:

Data Manager Load Files

Script Logic Files

Transformation Files

Reports and Schedule Files

Conversion Files


17/32



3. Data Manager Objects

3.1 Custom Process Types and Custom Process Chains

PC10NW offers, through the data manager, a series of packages in order to execute specific operationslike importing data from a flat file or an excel file into a cube. The Data Manager packages executepreconfigured BW process chains delivered with your PC10NW installation.

However, the need for more complex packages might arise. In this case, SAP offers the ability to createyour own BPC specific process types (tasks) and process chains (which can be maintained throughtransaction RSPC ).

Important Tip:

Custom developed process chains (linked into a data manager package) will not be collected fortransport via the PC10NW transport process. You must create a separate standard BW transport tomove 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 theBPC objects.


18/32



3.2 Transformation and Conversion files

The PC10NW transport can collect all transformation and conversion files stored in the file service.

Specific file selections can be made from the collected objects under the Environment > Model >Business Unit> Team Folder> Data Manager:

Important Tips:

Deletion of transformation files is not supported with transports, and must be done manually ineach system.Deletion of conversion files is also not supported with transports, and must be done manually ineach system.


19/32



3.3 Data Manager Data FilesUploaded Data Manager data files can also be collected into a transport (this is a new feature forPC10NW):

IMPORTANT NOTE: When collecting these objects in the transport manager, there can be aperformance hit if the objects are very large – it is always recommended to therefore only transport thenecessary Data Manager Data Files. Remember that you can unselect the files you do not wish totransport over. In general, the fewer amounts of files and objects you transport, the faster the transportcollection and execution will run. It is therefore a good idea to inspect which objects are beingtransported and perform cleanup maintenance if possible.


20/32



3.4 Data Manager Selection Prompt Files

Data Manager package prompt selections (these are .esf files that store a particular set of prompts for aspecific 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:


21/32



3.5 Data Manager PackagesData Manager packages can be individually selected for transport. Note: although the package can beselected, the underlying BW process chain supporting the package is not automatically collected by thetransport. In the event that a custom process chain, or a modified delivered process chain, is used by a

Data Manager package, then that process chain will either need to be manually added to the transport ortransported in a separate transport collection prior to the import of the corresponding linked DataManager package. Failure to adhere to this timing may result in a consistency check failure upon importof the Data Manager package into the target system (see Tip in section 3.1).


22/32


23/32



5 JournalsThe 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 causeall 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 applicationchanges that may have impacts to journal configuration using the Data Manager Journal Export/Importpackages.


24/32



6 Administration Parameters Administration parameters are used to set a variety of actions within PC10NW. Some parameters are setby clicking on a selection box in configuration (i.e.: enable Comments for a model):

and some parameters are set directly within the IMG:


25/32



The Administration Parameters are captured by the transport creation process and can be included intothe transport by item selection:


26/32



7. Transport tools

7.1 Transaction Codes SE10 / SE09:

After creation, you can then view/modify/release the transport request using standard TMS transactioncodes such as SE10, or SE09:

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 haveincluded the dimension definition in the same transport containing the model definition. Timing oftransports to ensure all dependencies are satisfied can therefore become an important projectmanagement consideration.


27/32



7.2 UJT_CHECK_TABLE_ENTRIESProgram (accessed via transaction code SE38) UJT_CHECK_TABLE_ENTRIES can be used tocheck how many records exist in the UJ* database tables for a particular Environment. This is usefulafter deleting an Environment to make sure that all data has been removed.


28/32



7.3 UJS_ACTVIATE_CONTENTProgram UJS_ACTVIATE_CONTENT (accessed via transaction code SE38) is typically used to activatean EnviromentShell installation, but can also be used to delete most entries in the UJ* database tables fora particular Environment. After entering the environment to be deleted, check the CLEAN theEnvironment selection box and execute.


29/32



7.4 UJA_DATA_CHECKERProgram UJA_DATA_CHECKER (accessed via transaction code SE38) can be used to check (andpotentially fix) the consistency of master and meta data within a specified environment:

Example Output (Message Type: W=Warning, E= Error, I= Information):


30/32



7.5 UJT_AFTER_FAIL_PROCESSThe program UJT_CHECK_TABLE_ENTRIES (accessed via transaction code SE38) can be used tocorrect the environment in t he target system after a failed transport import. This program will “roll back”the failed objects to the last consistent state. This program should only be used by expert level users,

and may be employed by SAP Global Support during troubleshooting sessions.


31/32



8.0 Resources and Help

8.1 Service Marketplace – Administrator’s Guide

Detailed information on how specific PC10NW objects are transported can be found in ServiceMarketplace at:

SBOP Plan & Consol 10.0 NW Administrator's Guide (sections 5 and 6.7)

8.2 SAP Notes

Check for SAP Notes under component: EPM-PC10NW-NW-TRA

A few selected notes:

SAP Note 1667160 - Consulting Note on BPC10 NW Granular TransportThis note summarizes the solutions and best practices to overcome common known issues duringPlanning and Consolidation 10.0 transports and will be continuously updated.

SAP Note 1724817 – Timeout when releasing transport requestThis note drastically improves the performance of releasing transport requests. It will also reduce the DBLog consumption during a large transport. It should be applied to every BPC 10 system beforeperforming a transport.

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 stablethroughout 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).

https://websmp106.sap-ag.de/~sapidb/011000358700000483512011E/SBOP_PC_10_NW_Admin.pdfhttps://websmp106.sap-ag.de/~sapidb/011000358700000483512011E/SBOP_PC_10_NW_Admin.pdfhttps://websmp106.sap-ag.de/~sapidb/011000358700000483512011E/SBOP_PC_10_NW_Admin.pdf


32/32


Copyright 2012 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. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other softwarevendors.

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 EnterpriseServer, 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 SystemsIncorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

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 registeredtrademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented byNetscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and servicesmentioned herein as well as their respective logos are trademarks or registered t rademarks of SAP AG in Germany and othercountries.

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 orregistered 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 thisdocument 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 beliable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are thosethat are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein shouldbe construed as constituting an additional warrant.

Documents

Life Cycle Management in SAP Planning and Consolidation 10.0 Version for Netweaver