BPC Transports Whitepaper

download BPC Transports Whitepaper

of 16

  • date post

    15-Nov-2014
  • Category

    Documents

  • view

    20
  • download

    3

Embed Size (px)

description

An overview of the new transport functionality introduced through SAP BPC (Business Planning and Consolidation) for NetWeaver.

Transcript of BPC Transports Whitepaper

SAP BPC for NetWeaver Transports white paper

Applies to:SAP Business Process and Consolidation for NetWeaver 7.0, based on a NetWeaver BI 7.01 platform.

SummaryThis white paper covers the main aspects that should be considered while defining a transport strategy for SAP Business Planning and Consolidation. It describes the transport mechanisms and tools and provides an approach for managing changes in the specific context of SAP BPC. Author(s): Faycal CHRAIBI Company: SAP Created on: 24 April 2009

Author BioFaycal CHRAIBI is a NetWeaver Technical Architect at SAP and has been dealing with SOA and Enterprise SOA for a few years. He is highly interested by end to end process integration, agility and efficient model driven architectures.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 1

SAP BPC for NetWeaver Transports white paper

Table of ContentsApplies to: .................................................................................................................................................................. 1 Summary.................................................................................................................................................................... 1 Author Bio .................................................................................................................................................................. 1 1. Transport concepts ............................................................................................................................................... 3 1.1 SAP BPC Architecture .................................................................................................................................... 3 1.2 Main concepts ................................................................................................................................................. 4 1.3 Changeability ................................................................................................................................................... 5 1.4 SAP BPC objects taxonomy ........................................................................................................................... 6 2. The Data Manager ................................................................................................................................................ 6 2.1 Custom Process Types................................................................................................................................... 7 2.2 The File Service in Data Manager ................................................................................................................. 8 3. The File Service .................................................................................................................................................... 8 4. SAP BPC Transport tools ..................................................................................................................................11 5. Solution Manager and Change Request Management integration .................................................................13 6. Applying support packages ................................................................................................................................15 6.1 Support packages for the .NET infrastructure .............................................................................................15 6.2 Support packages for SAP BPC (Netweaver infrastructure)......................................................................15 Copyright ..................................................................................................................................................................16

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 2

SAP BPC for NetWeaver Transports white paper

1. Transport concepts1.1 SAP BPC Architecture

SAP Business Planning and Consolidation is a four layer application composed of a client stack, a server side divided into the .NET Application front-end and the NetWeaver ABAP Application back-end, and the database server.

In the SAP BPC for NetWeaver architecture, all the data and files are stored in the database (in opposition to the Microsoft version where files were on a file server). All these data and files are logically stored into an AppSet, which is a logical container for SAP BPC, equivalent to an SAP client.

A NetWeaver Business Intelligence client can hold one or several AppSets, which are copies of an initial AppSet called ApShell. It is not recommended to make any modifications to the ApShell.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 3

SAP BPC for NetWeaver Transports white paper

1.2 Main concepts

SAP BPC for NetWeaver leverages the NetWeaver BI infrastructure for all the major features, including info-objects, extractors and the transport layer. Following this strategy, the transport of SAP BPC objects is based on the TLOGO Framework (Transportable BI Objects).

The transports in SAP BPC are done through the transport of the whole AppSet. The transport operations are done in two steps: Upon the creation of a customizing request, the content of the source AppSet are copied (snapshot) into the shadow tables UJT_TRANS_HDR and UJT_TRANS_OBJ, which contain all the meta data describing the objects on the AppSet (step 1 from the following schema). Upon the transport import, the content of the shadow tables and those of the target AppSet are compared and then a todo list is created in order to make the changes, according to the steps 2 and 3.

The shadow tables contain all the metadata from the UJ* tables (BPC tables). No BI objects are transported; they are recreated from the metadata that have been transported from the shadow tables in order to create the todo list.

The only type of transport that is supported in SAP BPC is the transport of AppSets. It is not recommended to create customizing requests using the standard BI tools. This could lead to a loss of data or leftover programs or reports.

At the end of a transport import, After Import tasks may be executed (step 4). For this purpose, the function RS_APPS_AFTER_IMPORT must be called. The tasks that should be executed will be maintained in the table UJT_TRANS_STP.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 4

SAP BPC for NetWeaver Transports white paper

1.3 Changeability

As the transport in SAP BPC is realized through the copy of the whole AppSet, SAP has set the ability to restrict the transport of certain objects through their changeability.

The changeability for SAP BPC objects is maintained through the table UJT_TRANS_CHG (accessible through transaction SE16).

There are two levels of changeability: D (Development): The objects whose changeability is set to D can be transported from one environment to the other using the BPC transport tools. Objects in non productive environment are usually set to D, unless for specific cases (exclude a specific a type of object from a transport). P (Production): Objects whose changeability is set to P cannot be transported and cannot be modified. This is usually the case for productive environments. However SAP provides the possibility to set specific types of objects changeability to D in a productive environment in order to allow their modification on the production system if needed.

The changeability for the objects can be modified by altering the property CHANGE_ID for each type of object:

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 5

SAP BPC for NetWeaver Transports white paper

1.4 SAP BPC objects taxonomy

SAP Business Planning and Consolidation brings new types of objects to complement those already existing in the TLOGO Framework. The table below lists all the objects and their TLOGO object ID and their recommended changeability.

2. The Data ManagerThe data manager in SAP BPC is a module that helps managing, loading, transforming and manipulating the data.

Data manager is delivered with a set of packages that allow import, copy and move data within and across applications. It also supports a complex mapping of transaction and master data files.

The data manager is based on the Process Chain Framework delivered in SAP NetWeaver BI.

SAP COMMUNITY NETWORK 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 6

SAP BPC for NetWeaver Transports white paper

The following table provides a description of all the components in the data manager:

Object type Data manager Package Task / Process type

Description A SAP BPC module used to load, transform and manipulate data. The operational unit that a user can execute for a data process (import, export). A module that deals with a specific functionality like load which allows to transfer data from a file to a cube, a cube to a cube or a cube to a file. These are built on the Process Chain Framework. A framework provided by BW that helps to schedule packages, maintain status of running packages, wrap tasks into packages.. The process chains are the foundations for packages An Excel workbook transformations An Excel workbook transformations that that defines defines the mappings for data data

Process chain

Transformation file Conversion file

conversions

within

2.1 Custom Process Types

SAP BPC offers, through the data manager, a series of packages in order to execute specific operations lik