SAP BPC Systems Landscape

User Interface BPC Admin Client BPC Office Client BPC Web

Microsoft Application Server

MS IIS Application Server .NET Application Server

NetWeaver Application Server ABAP Engine SAP BW/BI OLAP Engine JAVA Engine

Relational Database

In NetWeaver BPC, Data and Files ( Ex: Logic Files ) are stored in the Database In MS BPC , Files ( Ex: Logic Files ) are stored in the File Services All these data and files are logically stored into an AppSet, which is a logical container for SAP BPC, equivalent to an SAP client.

BPC Transportation Process BPC transport is leveraging standard NetWeaver BI transport framework. All the content of the AppShell whose changeability is set to D is transported The transports in SAP BPC are done through the transport of the whole AppSet. Transport of SAP BPC objects is based on the TLOGO Framework(Transportable BI Objects). The transport operations are done in 4 steps: Step #1 : Export the Application Set content into the Staging (Shadow) tables Step #2 : Compare the difference ( Modified Objects , New Objects) staging table and the target application set Step #3 : Apply/Import Changes on the target application set Step #4 : Perform Post Import Task

QA System/ Target System Step #4

The shadow tables contain all the metadata from the UJ* tables (BPC tables).

Target Application Set Application Dimensions , etc Step #3

Development Source System

Transports - Staging/Import Table ( Objects that are modified in the source and new to the target system)

Source Application Set Application Dimensions , etc Step #1 Transports - Staging/Export Table ( Objects of Source Application Set)

Step #2

Transports Key Points/Important Tables/TCODE/ABAP Program

UJT_TRANS_HDR UJT_TRANS_OBJ UJT_CRT_BPC_TR ABAP Program - To Manage Transport Request ( add/mod/del Transport Request) UJBPCTR TCODE- To Manage Transport Request ( add/mod/del Transport Request) UJT_CHECK_TABLE_ENTRIES ABAP Program - Verify that all table entries for the appset UJT_DLT_TRANS_DATA ABAP Program - Delete all entries (source and target systems) in the tables ujt_trans_hdr and ujt_trans_obj UJS_ACTVIATE_CONTENT ABAP Program - Delete the appset in the target system by using the delivered program UJT_TRANS_STP Table , After Import tasks that should be executed will be maintained in the table RS_APPS_AFTER_IMPORT ABAP Program - After Import tasks may be executed UJT_TRANS_FIL Table-File Service information for transported UJT_TRANS_CHG Table - changeability for SAP BPC objects is maintained changeability D -- Development P -- Production

Transports Key Points/Important Tables/TCODE/ABAP Program

There are two levels of changeability: D - 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 - 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: All BPC related tables starts with UJ PLANNING cube starts with technical name /CPMB/ In some cases transports may fail and the only way to correct the issue is to delete an appset and re-import it In order to have these Custom Process Types transported, they must implement the IF_RSPC_TRANSPORT interface; otherwise they will not be picked up during the creation of the transport request Data Manager Objects Data Manager , Package , Process Type, Task , Process Chain , Transformation File , Conversion File Do we need to transport the Data File? Custom Process Type should be moved to the BPC Packages (CPMBPC namespace) to make it available for transport using SAP BPC transport tools

Transports Key Points/Important Tables/TCODE/ABAP Program

1. Use SE16 2. Use Data Browser

D - Development

P - Production

Transports Key Points/Important Tables/TCODE/ABAP Program

SAP BPC Objects

Transports Key Points/Important Tables/TCODE/ABAP Program UJFS All the files in the File Service are stored in the database, usually as BLOBs, they can be accessed using this transaction

UJFS File Service

Transports Key Points/Important Tables/TCODE/ABAP Program UJFS All the files in the File Service are stored in the database, usually as BLOBs, they can be accessed using this transaction

K , Logic File

UJT_TRANS_FIL Data Browser Table Entry

N , Data Manager and Directory

Transports Key Points/Important Tables/TCODE/ABAP Program UJFS All the files in the File Service are stored in the database, usually as BLOBs, they can be accessed using this transaction

All the files under the directory \ROOT\WEBFOLDERS\%APPSET%\%APP%\TEAMFILES\INSTALLATION\DATAMANGER\ will be transported

Only the files with the extention LGF under the directory \ROOT\WEBFOLDERS\%APPSET%\SYSTEMLIBRARY\LOGIC LIBRARY will be transported.

Transports Key Points/Important Tables/TCODE/ABAP Program UJFS All the files in the File Service are stored in the database, usually as BLOBs, they can be accessed using this transaction

We only transport the directory structure to recreate it in the target system, but no file will be transported according to this pattern

Transports Key Points/Important Tables/TCODE/ABAP Program UJBPCTR and/or UJT_CRT_BPC_TR

We may then choose the appropriate AppSet which should be transported. Optionally, we may choose to release the request immediately. Before being able to create a transport request for a specific AppSet, you should turn it offline otherwise you will raise an exception. The AppSet, in the target environment, should also be set offline when importing the transports. The holder of this task must have access to SAP BPC Client in order to be able to turn the AppSet offline.

Add/Mod/Del/Release Transport Request

Transports Key Points/Important Tables/TCODE/ABAP Program UJBPCTR and/or UJT_CRT_BPC_TR

Source System Bring Application Set offline Create a Transport Request Collect the Objects Release the Request Target System Compare the Objects to look for new and modified once between source and target Import the Object Activate (RS_APPS_AFTER_IMPORT )

Add/Mod/Del/Release Transport Request

Transports Key Points/Important Tables/TCODE/ABAP Program UJBPCTR and/or UJT_CRT_BPC_TR Concurrent Transport Request
If user A makes a transport request for the Appset 1 but doesnt release it, user B makes a transport request for the Appset 1 as well The entries in the shadow tables created by User 1 are deleted and replaced by the entries from the User Bs request The transport request for user A becomes equivalent to the one created by user B In this case, there is no need to release the two transports as they are equivalent. The content in the shadow tables created by user B already includes the modifications made by user A as this content is a snapshot of the current state of the AppSet The transport manager will only need to import the latest request to avoid duplicate imports

Add/Mod/Del/Release Transport Request

SAP BPC NW - Transaction Codes

UJ00 UJBPCTR UJFS UJKT UJQ0 UJR0 UJSTAT UJUT_DATA UJ_VALIDATION

BPC Configuration Transports - Create Request File Service Script Logic Tester Query Runtime Parameters Writeback Runtime Parameters Performance Statistics Report Unit Test Data Maintain Validations Maintenance

Lite Optimize option Does not make any changes to the data model. It just closes the open request; compresses and indexes the cube updates database statistics. Does not take Application Set offline Full Optimize option Takes the Application Set offline Create a new cube with data model as needed Link the Optimal Cube to the multi provide Copy the data from the original cube to the new cube Line Item Dimension - Needs Delete the original cube to Discussed. Closes the Open Request Update the database statistics Bring the application set offline Since all the reports are created based on the Multi Provider , not based on the underlying InfoCube, so the optimization does not affect the BPC reports Criteria for Full Optimization if the size of the dimension table is less than 20% of the fact table or not and create as many line item dimensions as possible Full Optimize not inherit the DTP created on the original InfoCube. source system, data source, infosource etc will remain but the transformation that links these to the infocube will get deleted and has to be recreated If the number of BPC dimensions in the BPC application is 13 or fewer, then all of them are automatically modeled as line item dimensions in the BPC infocube

BPC Maintenance scenarios Add/remove new GL to set Add/remove a new set Changing the name of a set (technical name or set description) Add new balance dependant account/set Disaster recovery Restore data Restore report New IC elimination entry New Consolidation of investment entry Change Balance carry forward logic Add new dimension Add new property Add new member Change ownership % Change consolidation method Manual BPC JV Reload transactional data from BW into BPC (Real time data?) Reload/load master data from BW into BPC Script logic

Linked to Application ( Secured DIM)

Users

Teams

Tasks

MBR Access Profile

John Mike Lisa

Planning Reporting Admin Sales

Crate Report Create Journals Load Data

Controlled by DIM

I wanted to give read only access to all planners for Actual I wanted to give read only access to all planners for Actual

Common to user functions , independent of DIM Values.

SAP BW and BPC Security are independent , there is no connection between these 2

dependent of DIM Values. Controls Read and write ability for a Task/Users/Task Profiles