TZBPC2 en Col84 Presentation

© SAP 2008 / © SAP 2008 / Page 1

<Course Number and Course Title FSC123 Overiew>TZBPC2SAP Business Planning and Consolidation 7.0, version for SAP NetWeaver

2008/Q4

© SAP 2008 / © SAP 2008 / Page 2

Copyright 2008 SAP AGAll 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 software vendors.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge 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 in several other countries all over the world. All other product and service names mentioned and associated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.

SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.

Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinkszugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab.

Alle Rechte vorbehalten.

SAP Business Planning and Consolidation 7.0, version for SAP NetWeaverTechnical Solution Changes

New Version Functions

© SAP 2008 / Page 2

New Version Functions: Lesson Objectives

After completing this lesson, you will be able to:Understand and explain architectural conceptsBegin planning for technical requirementsPlan for language supportUnderstand SAP’s maintenance strategy

© SAP 2008 / Page 3

Benefits of New Version Functions

There are several benefits related to learning this topic, including:Gaining insight into system architectureUnderstanding technical requirements.Learning to consider Version Lifecycle Planning while taking into account SAP’s maintenance strategy

© SAP 2008 / Page 4

Architecture of SAP Business Planning and Consolidation, version for Microsoft Platform

Server-side Requirements

MS SQL Server

MS Analysis Services

MS Reporting Services

MS DTS (or SSIS)

.NET 1.1 A/S

Web Server (IIS)

File Share

© SAP 2008 / Page 5

Architecture SAP Business Planning and Consolidation, version for SAP NetWeaver

© SAP 2008 / Page 6

Server-Side Requirements for SAP Business Planning and Consolidation

Server-side requirementsSAP NetWeaver BI Enhancement Pack1SAP NetWeaver BI for Add-on SAP Business Planning and Consolidation for SAP NetWeaverAny RDBMS SAP NetWeaver Supports.NET application server (both .NET 1.1 and 2.0 are required)Web Server (IIS)

© SAP 2008 / Page 7

SAP Business Planning and Consolidation General Technical Notes

What was removed (as compared to SAP Business Planning and Consolidation, version for Microsoft platform)?

Microsoft Reporting ServicesMicrosoft DTS/SSISMicrosoft Analysis Services

Additional Technical DifferencesDatabase agnostic (use an RDBMS)Processing shifted to SAP NetWeaver platformFiles stored in database

© SAP 2008 / Page 8

SAP Business Planning and Consolidation Architecture Notes

BPC for Office and BPC Admin Clients use Web services to connect to the .NET Web Server Tier (.NET 1.1)The .NET Web Server connects to the ABAP Web Application Server using the SAP .NET Connector (v2.0)Thus, .NET 1.1 and .NET 2.0 are requiredInternally, each RFC (Remote Function Call) is a wrapper around an object-oriented class within the UJ package (also known as development class)Metadata is stored in BPC-specific tablesMaster data (aka: dimension members) and transactional data (aka :fact data) are stored in NetWeaver BI objects and tables

Multi-tier architecture of the SAP Business Planning and Consolidation

© SAP 2008 / Page 9

What’s InIntegration with NetWeaver BI

Increased dimensionality

New Validations engine

Integration with BI Accelerator

Improved dynamic templates

Lifecycle Management (transports)

Statistics framework for monitoring

64-bit ABAP A/S support

Database neutrality

Debugging capabilities (ABAP only)

What’s OutBPFs

Books

Drill-Through

Dynamic Hierarchy Editor

Insight

SQL-Logic in K2 Script Logic

Some EV functions

Ability to rename a member, delete a member being used, reduce the length of a property

Custom Menus

SAP Business Planning and Consolidation - High Level Feature Delta

© SAP 2008 / Page 10

SAP Product Availability Matrix Information

SAP NetWeaver Application Server Installed as an add-on to SAP NetWeaver BI EhP1 (Enhancement Package 1).Only the AS-ABAP usage type is required for SAP Business Planning and Consolidation, AS-JAVA usage type is not required.Database Systems: Any RDBMS (Relational Database Management System) supported by SAP NetWeaver.Operating systems: Any operating system supported by SAP NetWeaver.

.NET Application Server / Web ServerOperating systems: Windows Server 2003, Enterprise Edition (32-bit x86), Windows Server 2003, Enterprise x64 Edition..NET versions 1.1 and 2.0.Microsoft IIS 6.0.

ClientOperating System: Windows XP.Microsoft Office: 2003 and 2007.

More information: see the product availability matrix at http://service.sap.com/pam

© SAP 2008 / Page 11

SAP Business Planning and Consolidation Language Support

Currently Supported LanguagesEnglish, German, French (Standard), Japanese, Spanish, Italian, Korean, Russian, Chinese (Simplified), Portuguese (Brazilian).Same as SAP BPC 5.x

Planned Languages (SP1)SlovakianCzechDanishDutch

Planned Languages (SP2)FinnishNorwegianPolishSwedish

© SAP 2008 / Page 12

Maintenance Strategy

Maintenance Strategy – SAP Business Planning and Consolidation has the same maintenance strategy as the underlying SAP NetWeaver platform.

Maintenance information as of time of RKT material development:

For the most up-to-date information on the SAP maintenance strategy, see http://service.sap.com/releasestrategy

© SAP 2008 / Page 13

One Voice: Product Names

The official product names:

SAP Business Planning and ConsolidationTo be used whenever possible.

SAP Business Planning and Consolidation, version for SAP NetWeaverTo be used when you need to refer to specific functionality/architecture/etc. of the NetWeaver release.

SAP Business Planning and Consolidation, version for the Microsoft platformTo be used when you need to refer to specific functionality/architecture/etc. of the Microsoft .NET release.

© SAP 2008 / Page 14

New Version Functions: Lesson Summary

You should now be able to:Explain architectural conceptsBegin planning for technical requirementsPlan for language supportUnderstand SAP’s maintenance strategy


File Service

© SAP 2008 / Page 2

File Service: Lesson Objectives

After completing this lesson, you will be able to:Describe the differences between the SAP Business Planning and Consolidation 5.x file share and the SAP Business Planning and Consolidation File ServiceUpload, Download and Delete a document to the SAP Business Planning and Consolidation File ServiceConfigure Virus Scanning for files contained within the SAP Business Planning and Consolidation File ServiceConfigure the SAP Business Planning and Consolidation File Service with WebAdmin parameters

© SAP 2008 / Page 3

Benefits of SAP Business Planning and Consolidation File Service

There are several benefits related to learning this topic, including:

Understanding a new SAP Business Planning and Consolidation componentUsing and configuring the SAP Business Planning and Consolidation File Service

© SAP 2008 / Page 4

Function

The SAP Business Planning and Consolidation File Service is a central service for storing files related to the SAP Business Planning and Consolidation, version for SAP NetWeaver application

Files can be uploaded, downloaded and deleted from the file service

© SAP 2008 / Page 5

File Service Overview

All files are stored in the databaseMost stored as BLOB’sData Manager files stored in generated DB tables– Row by Row– As String– .csv files

Gzip (GNU zip) compression is supportedZIP archive format is supportedVirus Scanning is supported (configurable)Store ANY file typesTransaction UJFS – File Service User Interface

© SAP 2008 / Page 6

File Service Overview

Directory structure differences between SAP Business Planning and Consolidation 5.x and SAP Business Planning and Consolidation, version for SAP NetWeaver

“Data” Folder is now referred to as “Root” in File ServiceEach AppSet has its own “Root” folder

“AdminTemplates” folder is now AppSet specific

© SAP 2008 / Page 7

File Service Overview: How Files Are Stored

Document Table - UJF_DOC Stores data for all documentsDocuments are stored as binary streamData Manager files are stored in generated DB table

Blob Generated Table

© SAP 2008 / Page 8

File Service Overview:UJF_DOCTREE

Document Tree Table - UJF_DOCTREEStores the directory structure of SAP Business Planning and Consolidation File ServiceDIR_DOC field specifies if record is a Folder or DocumentPARENT_DOC field defines previous node in structure

© SAP 2008 / Page 9

File Service Overview:UJF_DOCMAP

File Map Table - UJF_DOCMAP Used to map files/directories to specific modulesAPI available which passes relative path and fills the placeholder values

© SAP 2008 / Page 10

File Service Overview:UJF_APPSERV_DIR

Application Server Directory Table - UJF_APPSERV_DIRUsed to select files from an application server directoryAt least one entry is required

© SAP 2008 / Page 11

File Service Overview: Available Functions

UJFS Supported FunctionsDirectory Functions

Create DirectoryCopy DirectoryChange DirectoryDelete DirectoryDownload All Documents (as ZIP)

Document FunctionsUpload/Download Document– From PC, for Data Manager, from FTPLock/Unlock DocumentRename DocumentCopy DocumentDelete Document

© SAP 2008 / Page 12

Uploading Documents via UJFS

Select a directory in which to upload the document.

Right-click and select the upload method from the context menu.

Upload from PC, file will be stored as blob in the DB table.Upload for DM, file will be stored row by row in a generated DB table.Upload from FTP, file will be pulled from FTP site.– FTP site must be inside the firewall.

Select the file location using the dialog, choose “Open”

© SAP 2008 / Page 13

Downloading Documents via UJFS

Select the document in which to download.Right-click on this document and choose the action from the context menu.Download options

As its associated file typeOr as a ZIP file

Choose file location

© SAP 2008 / Page 14

Virus Scanning

Standard NetWeaver Virus ScanningSAP NetWeaver is shipped with virus scanning deactivated.Transaction Codes for Virus Scan Interface

VSCAN Configuration of the Virus Scan ProviderVSCANGROUP Configuration of the Virus Scan GroupsVSCANPROFILE Configuration of the Virus Scan ProfilesVSCANTEST Test for the Virus Scan InterfaceVSCANTRACE Memory Trace for the Virus Scan Server

Should be done by an SAP NetWeaver (Basis) Administrator.

http://help.sap.com/saphelp_nw70/helpdata/EN/b8/e6e540c1848131e10000000a1550b0/frameset.htm

© SAP 2008 / Page 15

Data Manager: Accessing the File Service

Get Document For Data Manager APISupports multiple access

File Service TablesFTPApplication Server– Local or Remote

© SAP 2008 / Page 16

Data Manager: Additional Considerations

If a file is to be read by Data Manager, row by row, you must upload the file using the correct upload method: “Upload Document for Data Manager”This will write the file to the generated database table

If Data Manager tries to read a file which has been incorrectly uploaded, then the caller will simply not get a result set

At some point, data manager files are no longer needed and can be deletedProgram UJF_FILE_SERVICE_DLT_DM_FILES is used to delete these files

© SAP 2008 / Page 17

Technical Considerations

Restrictions from clientAssociated WebAdmin Parameters– ALLOW_FILE_SIZE value = 100mb– ALLOW_EXTENSIONS value = ALL– DEFAULT_EXTENSIONS value = XLS,XLT,DOC,DOT,PPT,XML (etc)

No restrictions from transaction UJFS500mb file tested successfully, but not recommended.Any file types, any extensions

ZIP archives can be spliced into individual folders/filesRAR is not supported by NetWeaver

© SAP 2008 / Page 18

File Service: Lesson Summary

You should now be able to:Describe the differences between the SAP Business Planning and Consolidation 5.x file share and the SAP Business Planning and Consolidation File ServiceUpload, Download and Delete a document to the SAP Business Planning and Consolidation File ServiceConfigure Virus Scanning for files contained within the SAP Business Planning and Consolidation File ServiceConfigure the SAP Business Planning and Consolidation File Service with WebAdmin parameters


Logging

© SAP 2008 / Page 2

Logging: Lesson Objectives

After completing this lesson, you will be able to enable logging and tracing on the .NET Client, the .NET Server and the ABAP NetWeaver system.

© SAP 2008 / Page 3

Benefits of Logging

There are several benefits related to learning this topic, including:Insight into how the system is functioningExpeditious responses to support casesInformation key to performing root cause analysis should an issue arise

© SAP 2008 / Page 4

Function

SAP Business Planning and Consolidation Logging locations:SAP Business Planning and Consolidation .NET Log filesIIS (Internet Information Services ) Log filesWindows Event ViewerTracing (ABAP Tier)

© SAP 2008 / Page 5

Logging - The .NET Client Tier: Windows Event Viewer

Logging on the .NET Client Tier is available in:The Windows Event Viewer

Ev4Excel50.log

© SAP 2008 / Page 6

Logging - The .NET Middle Tier

The .NET Middle Tier offers three primary logging mechanismsSAP Business Planning and Consolidation .NET Server LogsMicrosoft IIS Server LogsMicrosoft Windows Event Viewer

Each of these logs Gives different informationCan be used to troubleshoot issues

© SAP 2008 / Page 7

Logging - The .NET Middle Tier: Server Logs

The SAP Business Planning and Consolidation Server Logs:Located in “\BPC\Logging”One subfolder for each moduleOnly errors are loggedLogs are time-stamped by day. A new file is created for each day.

The contents of the log can viewed in your favorite text editor:

© SAP 2008 / Page 8

Logging - The .NET Middle Tier: Windows IIS Logs

To troubleshoot Microsoft IIS (Internet Information Services ), there are numerous way to approach this. See the following documentation:

http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/676400bc-8969-4aa7-851a-9319490a9bbb.mspx?mfr=trueThere are 2 common traces for IIS:

Currently Executing Requests Tracing – Use this for long running processes.Request-Based Tracing – Used for most common problem tracing - see details here:– http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/b0aef644

-7b19-418d-b658-fde4a93678a9.mspxStandard IIS log files

Default location is “%systemroot%\system32\LogFiles\W3SVC1”

© SAP 2008 / Page 9

Logging - The .NET Middle Tier: Windows Event Viewer

The Windows Event ViewerThe Log Event Viewer area should display much of the same information as in the <BPC_SERVER>\BPC\Logging area

© SAP 2008 / Page 10

Tracing with SAP NetWeaver (ABAP)

SAP NetWeaver offers tracing capabilities as well as debugging capabilitiesDebugging can be used if Tracing and Logging don’t solve your issueTracing and Logging should be used as the first option to troubleshoot ABAP issues within SAP Business Planning and Consolidation, version for SAP NetWeaver

© SAP 2008 / Page 11

Tracing - The ABAP Tier: ST22 - Check for ABAP Dumps

Use transaction ST22 to see if any ABAP dumps occur.

© SAP 2008 / Page 12

Tracing - The ABAP Tier:SM21 - Check RFC Transactions

SAP Business Planning and Consolidation communication with the .NET Middle Tier occurs through RFCUse Transaction SM21 when checking system connections

© SAP 2008 / Page 13

Tracing - The ABAP Tier:ST05 - RFC Connection Tracing

SAP Business Planning and Consolidation Services Accounts are setup as communications users

Communications users do not allow debugging as dialog connectionsRFC (Remote Function Call) trace in ABAP can be set in ST05

© SAP 2008 / Page 14

Tracing - The ABAP Tier:SLG1 - Analyse Application Log (1 of 5)

The logs within SLG1 can show different types of information:Error MessageWarning MessageDebug Message

To view all logs related to SAP Business Planning and Consolidation, enter object “UJ” and execute SLG1.

© SAP 2008 / Page 15

Tracing - The ABAP Tier:SLG1 - Display Logs (2 of 5)

The output of the logs is as follows:

Date, Time, and User

AppSet-Application

Module Issues the Log

Internal Program orBPC API (Function

Module) issuing the log

© SAP 2008 / Page 16

Tracing - The ABAP Tier:SLG1 - Log Detail (3 of 5)

To see detailed logs, you can double click on the log item.

© SAP 2008 / Page 17

Tracing - The ABAP Tier:SLG1 - SQE Logs (4 of 5)

The SQE logs all details based on the type of call. You can see all the MDX (MultiDimensional eXpressions) statements executed within the system logs as well.

© SAP 2008 / Page 18

Tracing - The ABAP Tier:SLG1 - SubObjects (5 of 5)

View LogsTo view all logs related to SAP Business Planning and Consolidation, enter object “UJ” and execute SLG1The SubObject also allows you to only see logs for a specific SAP Business Planning and Consolidation Module.

© SAP 2008 / Page 19

Tracing - The ABAP Tier:SLG2 - Maintenance of System Logs

Use transaction SLG2 to maintain system logs.

© SAP 2008 / Page 20

Tracing - The ABAP Tier:ST01 - Other Traces Available

All other traces can be executed through ST01:Authorization Check (for ABAP auth objects, not SAP Business Planning and Consolidation authorizations)Kernel FunctionsGeneral KernelDB Access (SQL Trace)Table Buffer TraceRFC CallsLock Operations

© SAP 2008 / Page 21

Logging: Lesson Summary

You should now be able to enable logging and tracing on the .NET Client, the .NET Server and the ABAP NetWeaver system.


Transports

© SAP 2008 / Page 2

Transports: Lesson Objectives

After completing this lesson, you will be able to:Understand the SAP Business Planning and Consolidation transportapproachLearn what objects are transportedConfigure transports in SAP Business Planning and ConsolidationGain access to an overview of the SAP transport process for those new to SAP Business Planning and ConsolidationUnderstand how standard SAP methodologies have been appliedUse the standard TMS transaction to monitor the request, and view logs

© SAP 2008 / Page 3

Benefits of SAP Business Planning and Consolidation Transports

There are several benefits related to learning this topic, including:Understanding a new component in SAP Business Planning and ConsolidationUsing and configuring the SAP Business Planning and Consolidation Transports

© SAP 2008 / Page 4

Function

SAP Business Planning and Consolidation Transports is a central service for migrating development of SAP Business Planning and Consolidation applications in a controlled fashion after testing.

© SAP 2008 / Page 5

SAP Business Planning and Consolidation Transports Overview

SAP Business Planning and Consolidation transports leverage the existing BI transports framework

BPC TLOGO Object = APPSConfigured in transaction code SOBJ (delivered)

Entries from two shadow tables are transportedUJT_TRANS_HDRUJT_TRANS_OBJ– This table contains ALL of the metadata from the UJ* tables

© SAP 2008 / Page 6


The AppSet must be offlineIn order to create a requestIn target

Transporting of Data Manager files in File Service is NOT supportedSubObjects (similar to TLOGO objects) are used to manage

Meta-data tables (table UJT_TRANS_TAB) that are transported Changeability (table UJT_TRANS_CHG)Changeability can be maintain via transaction SM30

Configuration allows the user to choose which SubObjects are changeable in development systemsIf a SubObject is not set as “D” (Development), changes for the SubObject will not be transportedAll SubObjects are delivered as changeable in Development

© SAP 2008 / Page 7


Specific files and directories within File Service are transportedThis is based off the transports config table UJT_TRANS_FIL This table can be modified via table maintenance, transaction code SM30.Transport of DM files is NOT supported

File/Directories under sub-object NFIL, are only transported to target system, when there is a new application being created in the target systemPattern field can be specific or generic

© SAP 2008 / Page 8


TLOGO APPS also has its own after import method function module, RS_APPS_AFTER_IMPORT

Called by the BI transports frameworkCalls the after import logic in the SAP Business Planning and Consolidation transports framework

After import method is based on steps (table UJT_TRANS_STP)

Order of these steps is driven by this table– Steps ALWAYS executed:

– UPDDTAB– UPDPTAB– ADMIN_DEF_UPD– FILE_SERV_UPD– DATA_TABLE_UPD

– All other steps are only executed when required

© SAP 2008 / Page 9

Create Transport Request per AppSet

Transaction UJBPCTRChoose Request TypeEnter AppSet Id Execute the request

This is a customizing requestDefault request descriptionDefault Target layerSave to create request

© SAP 2008 / Page 10


View the request using standard TMS transaction codes such as SE10 or SE09Customizing request is created with one task underneath itAn AppSet is transported as a single transportable object

© SAP 2008 / Page 11


Request objects include the two SAP Business Planning and Consolidation transports shadow tablesWhen the request is released, all data from these tables for the specific AppSet is transported as one object.\

© SAP 2008 / Page 12

Importing the Request

SAP Business Planning and Consolidation transport requests must be promoted from one system to anotherImporting a request will overwrite objects in the target systemView logs

© SAP 2008 / Page 13

Setup and Prerequisites

Transport System must be configured correctly (done by SAP NetWeaver Administrator) that is creating Transport Domains, routes, and other critical aspectsImporting Client-Dependent Objects

All SAP Business Planning and Consolidation Data is client-dependentUser ALEREMOTE (BI Background User) must be createdAn RFC destination must be created in order for the after import method to be fired in the correct client, otherwise it will be executed in client 000Use transaction RSTPRFC to create the destination for this client

© SAP 2008 / Page 14

What not to Do with Objects and Transports

Do Not Transport table entries without using SAP Business Planning and ConsolidationInternal programs may be missed

Do Not Transporting BI objects without using SAP Business Planning and ConsolidationWill cause issues using standard BI transport methods

© SAP 2008 / Page 15

Additional Transport Information

This is a necessary prerequisite to be able to transport SAP Business Planning and Consolidation Application Sets.

http://help.sap.com/saphelp_nw70/helpdata/en/45/b517e0ed2f52f5e10000000a1553f7/content.htm

Use ABAP Program: UJT_CRT_BPC_TR

© SAP 2008 / Page 16

TLOGO Framework

BI metadata framework.Transport of SAP Business Planning and Consolidation as well as Dependent BI ObjectsTransport available in SAP Business Planning and Consolidation by AppSet only

OBJID Text Changeability

ASET Appset DEVAPPM Administration( Dimension, InfoArea, InfoCube ) DEVK2SC Scripts DEVTDLO Table Driven Logic/StoredProcedure DEVWORK Workbooks PRODREPT Reporting DEV/PRODJOUR Journal DEVSECU Security PRODWSTA Work Status PRODLREP Live Reports PROD

COMM Comments PRODAUDI Audit PRODPACK Package PRODFTRA Transformation Files DEVFCON Conversion Files DEV

© SAP 2008 / Page 17

Transports: Lesson Summary

You should now be able to:Understand the SAP Business Planning and Consolidation transportapproachLearn what objects are transportedConfigure transports in SAP Business Planning and ConsolidationGain access to an overview of the SAP transport process for those new to SAP Business Planning and ConsolidationUnderstand how standard SAP methodologies have been appliedUse the standard TMS transaction to monitor the request, and view logs


Case Sensitivity

© SAP 2008 / Page 2

Case Sensitivity: Lesson Objectives

After completing this lesson, you will be able to:Understand and explain the issues arising with case sensitivity differences.Take case sensitivity issues into account on your project.Develop a strategy for effectively managing case sensitivity.

© SAP 2008 / Page 3

Benefits of Case Sensitivity

There are several benefits related to learning this topic, including:Gaining knowledge of case sensitivity issues.Having the know-how to develop a strategy to manage case sensitivity.

© SAP 2008 / Page 4

Case Sensitivity – What Is the Issue?

Microsoft SQL Server and SAP NetWeaver have different behavior in relation to case sensitivity that must be taken into account.

Microsoft allows data to be stored in any case, however it does not allow duplicate values to be accepted in any case.

ExampleIf you have the string “Cash”, this is exactly how it will be stored in the MS-SQL DB If you try to save a value “CASH”, the MS-SQL DB treats this value as being equal to “Cash”, and will prevent you from creating “duplicate” entries

SAP NetWeaver is fully case sensitive. That means by default, SAP NetWeaver would treat “cash” and “CASH” as a completely separate values.

You can change this behavior in SAP NetWeaver, to be come case insensitive, so that it will convert everything to UPPERCASE. However, if you do this when you save the value “Cash”, it would be stored as “CASH”.

© SAP 2008 / Page 5

Case Sensitivity –How It Is Addressed

In SAP Business Planning and Consolidation a hybrid approach has been taken to deal with the case sensitivity issues:

Metadata (for example, AppSet or Application names) behaves the same way as in SAP Business Planning and Consolidation, version for the Microsoft platform (i.e. “cash” and “CASH” are considered the same value)Master data (for example, “CASH” or “SalesUSNEast”) is case sensitive, including members and propertiesFile Service - behaves the same way as SAP Business Planning and Consolidation, version for the Microsoft platform

© SAP 2008 / Page 6

Case Sensitivity: User Management

A special consideration for case sensitivity should be noted for user logon – user name and domain value must be specified in the same case in which they are stored.

© SAP 2008 / Page 7

Case Sensitivity: Metadata

SAP Business Planning and Consolidation will check to ensure that duplicate values can not be created in any caseApplies to: AppSet names, application names, dimension names, property names, work states, script logic file names, team names, task/member profile names

© SAP 2008 / Page 8

Case Sensitivity: Internal Handling for Metadata

Internally, metadata descriptions store two versions of the same valueTypically, the field “Caption” stores the value in the case that should be presented to the userThe other field (in this example, “Dimension”) stores it in UPPERCASE to ensure duplicate values are not allowed

© SAP 2008 / Page 9

Case Sensitivity: Master Data (1)

Master data is fully case sensitive in SAP Business Planning and Consolidation. You can now create duplicate member ID’s in different cases.

© SAP 2008 / Page 10

Case Sensitivity: Master Data (2)

That means everywhere the user refers to a member (master data value), you must use the specific case. This includes Workbooks (such as EVGET formulas, as well as submitting data), in Script Logic, in Work Status, and in Member Access Profiles.

Invalid Member returns no data

Valid Member returns data

© SAP 2008 / Page 11

Case Sensitivity: Master Data Properties

Property values in a dimension are also case sensitive.There are some “technical properties” that do not have case sensitive values. For example, the “CALC” property only accepts “Y” and “N” values…we do not distinguish between “Y”and “y”.You can see which technical, required properties are flagged as “Uppercase only” in table UJA_DMTYP_REQATT. Specifically, if the property has the field F_UPPERCASE = ‘X’, then it is uppercase only.

© SAP 2008 / Page 12

Case Sensitivity: File System

It is not supported to create files or folders that contain the same value in a different case than the one stored in the SAP NetWeaver system.Some of these files are cached on the end-user’s PC. Since Microsoft Windows does not support full case sensitivity, we would get in errors when downloading these files.It is for this reason that it is not supported to have dimensions/applications/etc to have the same name in a different case.

© SAP 2008 / Page 13

Case Sensitivity during Migration

When Migrating from SAP Business Planning and Consolidation 5.x to SAP Business Planning and Consolidation, version for SAP NetWeaver, there are several aspects to consider:

Master Data, Transactional Data and Other Data (Work Status, Member Access Profiles, Content Library Application Context etc.).Workbooks, K2 Script Files and Data Manager Files.Training/EducationNote: Be aware that choosing “Mixed Case” has a performance impact, in that the runtime of the migration tool will likely be significantly longer than if you choose “lower case” or “upper case”

© SAP 2008 / Page 14

Case Sensitivity: Summary

The platforms cause SAP Business Planning and Consolidation 5.x and SAP Business Planning and Consolidation, version for SAP NetWeaver handle case sensitivity differentlyMetadata and File Service behave the same way with respect to case sensitivity as SAP Business Planning and Consolidation 5.xDimension Members and Properties are case sensitive in SAP Business Planning and Consolidation, version for SAP NetWeaver Using the wrong case can cause errors

Administrators as well as users need to be mindful of the implications of case sensitivity, especially for dimension members

Always have dimension members in UPPERCASE

© SAP 2008 / Page 15

Case Sensitivity: Lesson Summary

You should now be able to:Understand and explain the case sensitivity issuesTake case sensitivity issues into account on your projectDevelop a strategy for effectively approaching case sensitivity


Custom Process Types

© SAP 2008 / Page 2

Custom Process Types: Lesson Objectives

After completing this lesson, you will be able to:Explain the concept of the Data Manager and building custom Process TypesList terminology related to Data ManagerList delivered Process TypesList keywords supported in RuntimeUnderstand how Data Manager relates to Process ChainsGet started in developing and implementing custom Process Types

© SAP 2008 / Page 3

Benefits of Custom Process Types

There are several benefits related to learning this topic, including:Learning the new terminology used with SAP Business Planning and Consolidation custom Process TypesKnowing which Data Manager packages are available when you implement custom Process Types with SAP Business Planning and ConsolidationLearning a powerful feature which provides you with the ability to perform operations that are not delivered with the standard process types

© SAP 2008 / Page 4

Context: Data Manager Overview

Data Manager is an SAP Business Planning and Consolidation module that helps you manage loading, transforming, and manipulating data.Data Manager is delivered with a set of packages to import, copy, clear and move data within and across applications.Data Manager supports mapping and complex transformations of transactional data files as well as master data files.

© SAP 2008 / Page 5

Object: Acronym DescriptionData Manager DM The module to transform and load and manipulate dataPackage The operational unit that user can execute for a data process, like

import, export, etc.Task / Process Type

The module to deal with specific functionality. E.g. load helps to transfer data from file to cube, from cube to cube, from cube to file. Package is built on Process Chains which include task(s).

Process Chain PC PC is a framework, which is provided by BW, that helps to schedule packages, maintain status of running packages, wrap tasks into packages and so on. PC is the foundation of a package.An SSIS package is roughly equivalent to a NW BI Process Chain.

InfoCube The Multi Dimensional Data Cube in BW. (ROLAP)DTS (SQL 2000)SSIS (SQL 2005)

DTS or SSIS Data Transfer Service or SQL Server Integration Services, provided by Microsoft. These are no longer relevant for SAP Business Planning and Consolidation.

Dimension Is a BI InfoObject that contains dimension members (Master Data)Measure Is a BI Object that stores the value (Key Figure)

Transformation File This is an Excel Workbook that defines mappings for data transformations

Conversion File This is an Excel Workbook that defines conversions within data transformations.

Context: Data Manager –Delta Terminology

© SAP 2008 / Page 6

Context: Data Manager Packages

Data Manager packages are implemented as process chains and allow you to do common data manipulation activitiesThe packages that come with SAP Business Planning and Consolidation are designed to be dynamic so that you do not need to modify the packages in order for them to work with your applications and dimensions.

You might want to modify packages to behave differently or to perform additional tasks.You can make modifications to the packages supplied with SAP Business Planning and Consolidation , version for SAP NetWeaver (not best practice) or use those packages as templates to build package, as per your requirements

© SAP 2008 / Page 7

Context: Package Type

In SAP Business Planning and Consolidation, only one package type is available (called “Process Chain”)

You can then choose which process chain to use for Data ManagerOnly Process Chains in the /CPMB/ namespace are displayed

You can then name your SAP Business Planning and Consolidation Data Manager Package Example, “Import into Financial Application”

© SAP 2008 / Page 8

Context: Delivered Process Chain Templates

There are four broad types of delivered Process Chain Templates which can be used to build SAP Business Planning and Consolidation Packages:

Standard Data Loading PackagesFinancial PackagesAdministrative PackagesExample Packages

These process chain templates can be displayed and edited in ABAP transaction RSPC.

© SAP 2008 / Page 9

Context: Standard Data Manager Delivered Packages (1)

PROCESS CHAIN TEMPLATE

DESCRIPTION TECH NAME

BPC: Import Master Data This package allows you to load dimension member data directly into a SAP Business Planning and Consolidation Dimension's Member Table (BW InfoObject's master data table)

/CPMB/IMPORT_MASTER

BPC: Import Master Data Description

This package allows you to load dimension member texts directly into a EVDESCRIPTION (BW InfoObject's text table)

/CPMB/IMPORT_DESCRIPT

BPC: Import Transaction Data

This package imports one or more ASCII files into the current application. You are prompted for one or more import file and associated transformation files. The signs of the amounts are reversed based on the Account type.You can use the import.xls transformation file with this package.

/CPMB/IMPORT

BPC: Load Transaction Data from Other Cube

This package allows you to load data from one BI Cube (EDW or BPC) into a SAP Business Planning and Consolidation Application. You can associate a transformation file to do the mapping.

/CPMB/LOAD_INFOPROVIDER

© SAP 2008 / Page 10

Context: Standard Data Manager Delivered Packages (2)

PROCESS CHAIN TEMPLATE

DESCRIPTION TECH NAME

BPC: Move Transaction Data in one cube

This package lets you move any selection of data within an application. You are prompted for source and destination data selections for all dimensions. The destination selection's fact table records are cleared before the source's records are moved. The source's fact table records are cleared after they are moved to the destination.

/CPMB/MOVE

BPC: Clear Transaction Data in One Cube

This package clears the data in the SAP Business Planning and Consolidation Application by importing zero values. The optimize process removes the zero values, which clears all values from the table. Running this package also clears comments from the comments table. You can use the import.xls transformation file with this package. You must select at least one dimension in order to run this package. If you select [All], the package will not run.

/CPMB/CLEAR

BPC: Copy Transaction Data in One Cube

This package copies data between dimensions within an application.

/CPMB/COPY

BPC: Append Transaction Data

This package imports data into the application by appending the data to the fact table, and then runs default logic against the imported data set.You can use the import.xls transformation file with this package.

/CPMB/APPEND

© SAP 2008 / Page 11

Context: Delivered Process Types

SAP Business Planning and Consolidation delivers the following process types:Admin TaskAudit ArchiveClear BPC TableClear CommentsClear CubeConvertConvert for Copy and MoveCreate DimensionDynamic ModifyEmailFTPFinalize OptimizeJournalsLoadMaster Data LoadMaster Data Description LoadOptimize CubeOwnership CalcRun LogicOnLine Status

© SAP 2008 / Page 12

Custom Process Types: Building Custom Instructions using UI Script

© SAP 2008 / Page 13

Custom Process Types: Parameters Available

The following types of Parameters are available:Process Type.NetDynamic ConstantKey wordsProcess Chain

© SAP 2008 / Page 14

Custom Process Types: More on Parameters

Parameters are maintained in the SAP Business Planning and Consolidation client.

The two type of parameters are:Process ChainProcess Type

Each process type has a variant.

© SAP 2008 / Page 15

Custom Process Types: Supported Keywords for Runtime

FUNCTION NAME DESCRIPTIONTASK A Process Chain Template includes one or more tasks;

each task defines a work item to be performed as part of the Data Manager runtime process. Example:

TASK(EXPORT_ZERO,APPSET,%APPSET%)

INFO Administrator can define fixed package values. Variables are evaluated:

Prompt Info (get_info) Package

Example:INFO(%TEMPFILE3%,%TEMPPATH%%RANDOMFILE%)

Examples:

INFO(DELIMETER, “,”) or

INFO(PACKAGESIZE, “50000”)

These are package parameters.PROMPT() command

Generates customized dialog boxes for users to enter information for package. This will not change.

© SAP 2008 / Page 16

Keywords from SAP Business Planning and Consolidation 5.x That Are not Supported

FUNCTION NAME DESCRIPTION

CONNECTIONEstablishes a connection to a data source. This is an executable instruction that can be entered in the EvDTSModifyPkg task script.

STEPCoordinates the flow of control and execution of tasks in a DTS package. This is an executable instruction that can be entered in the EvDTSModifyPkg task script.

GLOBAL

Global is used in MS to pass parameters form one custom task to another.In NetWeaver we have a global table UJD_PRCPARA. All the process type parameters are stored in this table.We will provide two methods (get_para and set_para) so every process type can get all process chain parameters.

© SAP 2008 / Page 17

Dynamic Constants (1 of 2)

NAME DESCRIPTION EXAMPLE%Account_DIM% dimension type A [Account]%App% application name Finance%App_List% application list Finance,LegalApp,LRate,OwnerShip,Rate%APPPATH% application path C:\BPC\DATA\WEBFOLDERS\APSHELL\FINANCE\

Will be the DB File server path%CATEGORY_DIM% dimension type C [CATEGORY]%CONVERSIONPATH% conversion file

pathC:\BPC\DATA\WEBFOLDERS\APSHELL\FINANCE\DATAMANAGER\CONVERSIONFILES\

%CURRENCY_DIM% dimension type R [RPTCURRENCY]%DATAPATH% data file path C:\BPC\DATA\WEBFOLDERS\APSHELL\FINANCE\

DATAMANAGER\DATAFILES\Will be the DB File server path

%DATAROOTPATH% data root path C:\BPC\DATA\WEBFOLDERS\Will be the DB File server root path

%DEFAULT_MEASURE% Default measure value

PERIODIC

© SAP 2008 / Page 18

Dynamic Constants (2 of 2)

NAME DESCRIPTION EXAMPLE%DIMS% dimension list [ACCOUNT],[CATEGORY],[DATASRC],[ENTITY],[INTCO],

[RPTCURRENCY],[TIME]%ENTITY_DIM% dimension type E [ENTITY]%FACTDIMS% fact dimension

list[ACCOUNT],[CATEGORY],[DATASRC],[ENTITY],[INTCO],[RPTCURRENCY],[TIMEID]

%LOGICPATH% logic path C:\BPC\DATA\WEBFOLDERS\APSHELL\FINANCE\ADMINAPP\FINANCE\Will be the DB File server path

%MEASURES% measure list SIGNEDDATA,PERIODIC,QTD,YTD%SELECTIONPATH% Selection file

pathC:\BPC\DATA\WEBFOLDERS\APSHELL\FINANCE\DATAMANAGER\SELECTIONFILES\

%SQLSERVER% SQL server name

SOLDEVHWK01

%TIME_DIM% dimension type T [TIME]%TRANSFORMATIONPATH% transformation

pathC:\BPC\DATA\WEBFOLDERS\APSHELL\FINANCE\DATAMANAGER\TRANSFORMATIONFILES\Will be the DB File server path

%TMP_PATH% Temp file path \Root\WEBFOLDERS\DEV7D\FINACE\PRIVATEPUBLICATIONS\SAP_ALL\I045795\TEMPFILES\

%USER% User ID SOLDEVHWK01\HWKIM

© SAP 2008 / Page 19

Points to Note While Creating Custom Process Types

Custom process types must implement following interfaceIF_RSPC_EXECUTEIF_RSPC_GET_VARIANTIF_RSPC_MAINTAIN

IF_RSPC_TRANSPORT (this is needed in our delivered process type, and if the customprocess type does not need transport, it can miss this interface)Each process type must have a type name no longer than 10, and it has to implement a static method SET_PC_TYPE to set the type nameWhen the process type class is create, we need to add logical codeThe class must inherit from class cl_ujd_actor or its derived class, usually there is no need to overload base class methodsYou must create a new class to implement the interface IF_UJD_TASK, which contains your specific logic code

© SAP 2008 / Page 20

Custom Process Types: Lesson Summary

You should now be able to:Explain the concept of the Data Manager and building custom Process TypesList terminology related to Data ManagerList delivered Process TypesList keywords supported in RuntimeUnderstand how Data Manager relates to Process ChainsGet started in developing and implementing Custom Process Types


Technical Parameters and Internal Programs

© SAP 2008 / Page 2

Technical Parameters and Internal Programs: Lesson Objectives

After completing this lesson, you will be able to:Identify and use new additional Technical Parameters of SAP Business Planning and Consolidation system.Identify and use new additional Internal Programs of SAP Business Planning and Consolidation system.

© SAP 2008 / Page 3

Benefits of Technical Parameters and Internal Programs

There are several benefits related to learning this topic, including:A chance for the server administrator to influence the server configuration and the behavior of the server.An opportunity to do the server maintenance work.A possibility to test the data quality, script logic, and SQE logs of the SAP Business Planning and Consolidation application.

© SAP 2008 / Page 4

Where Is It Performed?

se38 transaction for programs

se11 transaction for tables

© SAP 2008 / Page 5

Technical Parameters

SAP Business Planning and Consolidation has some hidden technical parameters that can be set internally (not exposed in Web Admin).

These parameters are in addition to the already existing SAP NetWeaver parameters, such as RSADMIN, and RZ10 parameters.These parameters are stored in ABAP tables: UJ(X)_PARAM where (X) is the SAP Business Planning and Consolidation module (see UJ Package overview for this value).

© SAP 2008 / Page 6

SAP Business Planning and Consolidation Parameters – Write Back

Table UJR_PARAM stores parameters for write-back. These values are maintained at the individual application level, and they are:

PACKAGE_SIZE (default = 40,000) RECLEVEL_NR (default = 10)MULTIPLY_COEF (default = 50)INTERVAL_NR (default = 10)

Entries with default values are inserted into table UJR_PARAM when not present

© SAP 2008 / Page 7

BPQ Parameters –Shared Query Engine

Table UJQ_PARAM stores parameters for shared query engine. These values are maintained at the individual application level, and they are:

SPARSITY_COEF (default = 5).Entries with default values are inserted into table UJQ_PARAM when not present

© SAP 2008 / Page 8

Program UJ0_STATISTICS_DELETE

Program UJ0_STATISTICS_DELETE will allow you to delete old statistical records.

© SAP 2008 / Page 9

Program UJ_MEMACS_MAINTAIN

Program UJ_MEMACS_MAINTAIN will rebuild the member access cache for security checks.

© SAP 2008 / Page 10

Program UJA_COPY_APPLICATION

Program UJA_COPY_APPLICATION will allow you to copy an application.

© SAP 2008 / Page 11

Program UJA_COPY_APPSET

Program UJA_COPY_APPSET will allow you to copy an AppSet (Application Set).

© SAP 2008 / Page 12

Program: UJA_DATA_CHECKER Metadata Validation

Program UJA_DATA_CHECKER will check if the AppSet has any corrupt metadata.

© SAP 2008 / Page 13

Program: UJA3_WRITE_SYS_ADMIN_NO_CHECK

Program UJA3_WRITE_SYS_ADMIN_NO_CHECK will allow you to update the SYS_ADMIN, ADMIN, and SAP Business Planning and Consolidation User.

© SAP 2008 / Page 14

Program: UJA_REFRESH_DIM_CACHE

Program UJA_REFRESH_DIM_CACHE will allow you to refresh the dimension cache for all users of an AppSet.

© SAP 2008 / Page 15

Program: UJK_SCRIPT_LOGIC_TESTER

Program UJK_SCRIPT_LOGIC_TESTER will allow you to test and debug script logic.

© SAP 2008 / Page 16

Program: UJF_FILE_SERVICE_UI

Program UJF_FILE_SERVICE_UI will allow users to update the File Service.

© SAP 2008 / Page 17

Program: UJF_FILE_SERVICE_DLT_DM_FILES

Program UJF_FILE_SERVICE_DLT_DM_FILES will allow you to delete file service data manager files to clear up space.

© SAP 2008 / Page 18

Program: UJQ_SQE_TEST

Allows you to test SQE calls if you find issues within the logs.

© SAP 2008 / Page 19

Program: UJS_ACTIVATE_CONTENT

Program UJS_ACTIVATE_CONTENT will allow you to activate Business Content objects that are delivered for SAP Business Planning and Consolidation .

© SAP 2008 / Page 20

Program: UJT_CHECK_TABLE_ENTRIES

Program UJT_CHECK_TABLE_ENTRIES will allow you to check table entries for transports.

© SAP 2008 / Page 21

Program: UJT_CRT_BPC_TR

Program UJT_CRT_BPC_TR will allow you create a request for transports.

© SAP 2008 / Page 22

All SAP Business Planning and Consolidation Programs

All SAP Business Planning and Consolidation Internal Programs are in package UJ*.

© SAP 2008 / Page 23

Technical Parameters and Internal Programs: Lesson Summary

You should now be able to:Identify and use new additional Technical Parameters of SAP Business Planning and Consolidation system.Identify and use new additional Internal Programs of SAP Business Planning and Consolidation system.

SAP Business Planning and Consolidation 7.0, version for NetWeaverTechnical Solution Changes

BPC Performance Statistics

© SAP 2008 / Page 2

BPC Performance Statistics: Lesson Objectives

After completing this lesson, you will be able to:Monitor the performance of the SAP Business Planning and Consolidation modules in the NetWeaver layer.Turn the statistics on and off.Use the BPC Performance Statistics report and analyze the output(Transaction UJSTAT).Delete old statistic records.

© SAP 2008 / Page 3

What is Different from SAP Business Planning and Consolidation 5.1?

This is new functionality which is available only with SAP Business Planning and Consolidation.

© SAP 2008 / Page 4

SAP Business Planning and Consolidation Statistics Overview (1)

The Statistics Framework in SAP Business Planning and Consolidation is a central, generic framework designed to help monitor performance for SAP Business Planning and Consolidation modules (such as SQE, Write-Back, etc).The target user of the Statistics Framework will be Consultants and Support staff trying to analyze performance problems. The statistics allow you to very quickly and easily identify the most time consuming part of a request.

Note: that SAP Business Planning and Consolidation Statistics only measures the ABAP portion of the total runtime. The .NET server and client code is not measured in this framework.

© SAP 2008 / Page 5

SAP Business Planning and Consolidation Statistics Overview (2)

SAP Business Planning and Consolidation Statistics is somewhat similar to NetWeaver BI statistics.It operates on the concept of “Actions” and “Events”.

When Statistics are recorded, they are separated into Header and Line Item records.A “header” record contains information about the whole request, and includes information such as, the user, and the Action being performed.A “line item” record contains information on each individual Event, including the start date/time and the total runtime. The total runtime of the request is calculated by adding up the runtime on each line item record.

© SAP 2008 / Page 6

Turning Statistics On/Off

By default, no statistics will be collected, but you can turn them on at the individual Application level

This is controlled by a new Application Web Admin parameter called “BPC_STATISTICS”

You must change the value using Web Admin for this change to be triggered automatically

SAP Business Planning and Consolidation Statistics will store a link (UUID) to the associated NetWeaver BI Statistics record so that it is possible to see the complete flow from SAP Business Planning and Consolidation through to NW BI, and continue to keep drilling into more detail

Screenshot of Web Admin interface to be added here.

© SAP 2008 / Page 7

Analyzing the Output

A new transaction (UJSTAT) has been created specifically to view SAP Business Planning and Consolidation Statistics records.

The intention of this transaction is to provide a UI to view the details of one (or several) statistics records.

This transaction is also not intended to perform statistical analysis on the informationExamples:

The average write-back time experiencedThe number of reads per day

For this type of analysis, the data must be extracted into a SAP NetWeaver BI cube

© SAP 2008 / Page 8

Using Transaction UJSTAT (1)

When you run transaction UJSTAT, you are asked to apply some filters to select the Statistics records you wish to display.

Select by:Statistics GUID value

It is not expected that the GUID would always be known

BPC UserStart DateStart TimeAction being performedAppSetApplication

© SAP 2008 / Page 9


After you have applied your filters and executed, you will see the statistics records matching your criteria.

© SAP 2008 / Page 10


Expanded record (parent, number 3) with individual events (child number 4 and 5)

The events have been sorted in the order in which they occurred, as indicated in the “Seq Number” column.

In this case, the total runtime of this request was 1.400955 seconds.

The longest running event was the “RSDRI_INFOPROV_READ”, taking 1.367427 seconds.

© SAP 2008 / Page 11


Runtime

Total Runtime

Cumulative Runtime

Nr of Recs

© SAP 2008 / Page 12


This example also shows nested events, where you can see events 4 and 5 are children of event 3.

Nested events occur when one module calls another module. For example, in a K2 script, it will likely call both SQE and Write-Back (and potentially other modules, such as Parameter Driven Logic).

Nested events show the dependency/sequencing of nested calls.

© SAP 2008 / Page 13


You can double click on the “Header” record in the UJSTAT transaction to bring up any additional information that was recorded on the header.

© SAP 2008 / Page 14


You can also double click on an individual event to bring up additional details on the record.

The “NWBI Statistics UUID” is used when a SAP Business Planning and Consolidation event calls a NetWeaver BI function (e.g. when the SQE executes an MDX statement).

The Supporting Detail field can contain additional text (for example, the MDX statement executed).

© SAP 2008 / Page 15

Example Records

If extracting data from the detail table, it is important to note that:

The Runtime column can be summed for all events, to get the complete runtime for the request. There are no overlapping requests with parent/child events.

The hierarchical relationship of events you see in transaction UJSTAT is built at runtime, not stored in the underlying tables. It must be determined programmatically (and is quite complicated, using the EVENT_ID, PARENT_EVENT_ID and ACTUAL_CALLER fields).

© SAP 2008 / Page 16

Deleting Records

Records, once written to the statistics tables, will not be deleted.

Delete records ff statistics are being used extensively or you are extracting the records out (to replicate the data into a SAP NetWeaver BI cube)

Program UJ0_STATISTICS_DELETE has been provided for this purpose (can be run ad-hoc in transaction SE38).

For now, the only options to delete statistics records are to delete all records for a given AppSet and/or Application.

© SAP 2008 / Page 17

Use of Statistics Within SAP Business Planning and Consolidation

This framework as of today, has only been implemented for:Shared Query EngineWrite-BackK2 Script Logic

Including other more detailed modules into this framework is planned for future versions.

The original reason for statistics was predominantly for analysis of read and write performance, and to be able to quickly and easily identify if the performance bottleneck is in the SAP Business Planning and Consolidation application or at the SAP NetWeaver BI layer.

© SAP 2008 / Page 18

Statistics Summary

Statistics can be used to analyze the performance of individual requests.

By default, no statistics records will be recorded.

Statistics will only record the ABAP portion of the total runtime.

Transaction UJSTAT can be used to analyze performance.

Events can be nested, based on the dynamic sequence of calls made at runtime (both inter and intra module).

The framework has only been implemented by SQE, Write-Back and K2 at this stage.

© SAP 2008 / Page 19

BPC Performance Statistics: Lesson Summary

You should now be able to:Monitor the performance of the SAP Business Planning and Consolidation modules in the NetWeaver layer.Turn the statistics on and off.Use the BPC Performance Statistics report and analyze the output(Transaction UJSTAT).Delete old statistic records.

SAP Business Planning and Consolidation 7.0, version for SAP NetWeaverInstallation

Understanding the UJ Package with SAP Business Planning and Consolidation

© SAP 2008 / Page 2

Understanding the UJ Package: Lesson Objectives

After completing this lesson, you will be able to:Understand the high level package conceptLearn how to navigate SAP Business Planning and Consolidation package ‘UJ‘

© SAP 2008 / Page 3

Benefits of SAP Business Planning and Consolidation UJ Package

There are several benefits related to learning this topic, including:

Understanding the UJ package, that comes with SAP Business Planning and Consolidation, will help technical users (programmers and technical administrators) to further understand SAP Business Planning and Consolidation system functionalityThe UJ Package allows you to view the organization of the SAP Business Planning and Consolidation add-on to the SAP BI NetWeaver system from a technical, programmatic perspective

© SAP 2008 / Page 4

Function

Packages are designed to help developers modularize, encapsulate, and decouple units in the SAP System. They are a further development of the concept of the development class used today and contain additional semantics. The emphasis is on technically decoupling resources from the Core SAP System, so that different products can follow different release cycles.

Every development object must belong to a package. Packages organize development objects and handle their connection to the AS ABAP software. That is, a package is like a folder in a way.

You can view a package, plus all its elements in transaction SE80. Just choose the entry Package in the object list of the Repository Browser, enter the name of the relevant package in the input field below and press "Enter". Then all the objects of that package are displayed.

SAP Business Planning and Consolidation Objects can be found in the ‘UJ’ package.

© SAP 2008 / Page 5

UJ Package Overview

Use transaction code SE80 to view UJ PackageLooking at the UJ Package in SE80

This information is only meant for technical users in the systemBusiness users would not need to look at or understand this concept. (As with the entire BI backend)

The following objects can be found browsing the UJ Package

Data Dictionary ObjectsClass Library, Programs, Function GroupsMessage ClassTransactionsOthers

© SAP 2008 / Page 6

UJ Package Navigation

Example navigation with the UJ package in SE80

Sometimes developers and technical users need to understand tables related to specific functionality – by using the UJ package hierarchy one can find such information.

The example to the right shows tables related to the SAP Business Planning and Consolidation security concept.

© SAP 2008 / Page 7

Understanding the UJ Package: Lesson Summary

You should now be able to:Understand the high level package conceptLearn how to navigate SAP Business Planning and Consolidation package ‘UJ‘


Service Accounts

© SAP 2008 / Page 2

Service Users: Lesson Objectives

After completing this lesson, you will be able to:Understand the difference between SAP Business Planning and Consolidation 5.x and SAP Business Planning and Consolidation, version for SAPNetWeaver Service AccountsDescribe the purpose of Service AccountsKnow the different Roles available for Service AccountsConfigure accounts with the appropriate Roles during installationUpdate the BPC.NET account information after installation

© SAP 2008 / Page 3

Benefits of Understanding Service Accounts

There are several benefits related to learning this topic, including:Understanding how security is implemented in SAP Business Planning and ConsolidationProper functioning of SAP Business Planning and ConsolidationSuccessful installation and configuration of SAP Business Planning and Consolidation

© SAP 2008 / Page 4

What Do Service Accounts Do?

Service Accounts:Are users in the ABAP systems that provide authentication from the .NET Tier to the ABAP backendABAP users must be assigned the appropriate Role(s) during installation to allow the .NET Tier to communicate with the ABAP Application Server Tier successfully

© SAP 2008 / Page 5

Preliminary Steps

Install SAP NetWeaver 7.0 SPS16Install SAP NetWeaver 7.0 EHp1Install the BPC Add-onCreate BPC Admin Dialog User assigned to the roles

S_RS_ALL SAP_ALL SAP_BPC_ADMIN Note – This dialog user must be used for configuring service accounts.

Install SAPGUI

© SAP 2008 / Page 6

How to Configure Service Accounts

Configuring Service AccountsLog into SAPGUI as the BPC Admin Dialog user you created (see Preliminary Steps)Perform this step during installation after completing the Preliminary StepsGeneral Steps:

Create three ABAP Users: a System Administrator, an Administrator and a User– Assign the System Administrator the “SAP_BPC_SYSADMIN” role– Assign the Administrator the “SAP_BPC_ADMIN” role– Assign the User the “SAP_BPC_USER” role

– Note: ABAP Users are assigned these roles by using the PFCG transaction.

© SAP 2008 / Page 7

What Did We Accomplish?

Configuring Service Accounts:

The ABAP service accounts used during the SAP Business Planning and Consolidation 7.0 .NET Tier installation are created

Communication between .NET and ABAP tiers is enabled

© SAP 2008 / Page 8

How to Configure Service Accounts on the .NET Tier

Configuring Service Accounts on the .NET TierRun SAP Business Planning and Consolidation Server Manager on each .NET application serverPerform this step after a change (i.e. password change) to any service accountGeneral Steps:

Select Server -> Reset Credentials

Make the appropriate modifications to the service account(s)

© SAP 2008 / Page 9

What Did We Accomplish?

Configuring Service Accounts:

The service user’s account information on the SAP Business Planning and Consolidation .NET Tier is modified

© SAP 2008 / Page 10

Service Users: Lesson Summary

You should now be able to:Understand the difference between SAP Business Planning and Consolidation 5.x and SAP Business Planning and Consolidation, version for SAP NetWeaver Service AccountsDescribe the purpose of Service AccountsKnow the different Roles available for Service AccountsConfigure accounts with the appropriate Roles during installationUpdate the BPC.NET account information after installation


Connectivity

© SAP 2008 / Page 2

Connectivity: Lesson Objectives

After completing this lesson, you will be able to:Understand and explain the basic concepts of connectivityUnderstand the different types of users involved in the internal interfacesGet started with troubleshooting issues related to connectivity

© SAP 2008 / Page 3

Benefits of Connectivity

There are several benefits related to learning this topic, including:Understanding the inner workings of the interfaces between the different layers in the architecture of SAP Business Planning and ConsolidationPossessing the know-how to troubleshoot issues that may arise in the connection between the different parts of SAP Business Planning and Consolidation

© SAP 2008 / Page 5

Server Manager Users

All users who can access the operating system of the .NET server can logon to Server Manager . . . but only the user specified in SYSADMIN in table UJA_SVR_DEFAULT can maintain the values…this is the SYSADMIN user specified during installation.

© SAP 2008 / Page 6

Server Manager: Server Diagnostics

Server Diagnostics help troubleshoot common connection problems.

To view the diagnostics log in a text editor, you can open up file: <BPC Server>\Server Management\OsoftDiagnostic.txt.

This file can be viewed on the .NET server file system.

© SAP 2008 / Page 7

Connectivity

SAP Business Planning and Consolidation Service Users are used, to connect to SAP NetWeaver. The 3 User IDs are:

System Administrator – used by the server manager to connect to SAP NetWeaverAdministrator – used by the Administrator Console to connect to SAP NetWeaver (also used by SAP Business Planning and Consolidation Web Admin)UserID – Used by the SAP Business Planning and Consolidation for Office and SAP Business Planning and Consolidation for Web clients to connect to SAP NetWeaver

Create users with “Communications Data” in the “User Type” field

© SAP 2008 / Page 8

Server Manager: Server Login Credentials

Server login credentials are connection users that the IIS Web Server uses to connect to the ABAP NetWeaver Server

The connection tests are tested from the .NET web server to the SAP NetWeaver

© SAP 2008 / Page 9

Server Manager: Client Options

Client AutoUpdate functionality is out of scope in Support pack 0, but is planned for Support pack 1.

Select Enable server to be Sarbane-Oxley compliant if you want all front-end clients that access the server to require users to enter a User ID and Password.

The XML version is displayed, but it is recommended not to change this value.

© SAP 2008 / Page 11

SAP NetWeaver Delivered Roles for Service Users

SAP Business Planning and Consolidation Service Users have required SAP NetWeaver roles that are delivered with SAP Business Planning and Consolidation (assigned using transaction PFCG).

System Administrator – Must be assigned the “SAP_BPC_SYSADMIN” role.Administrator – Must be assigned the “SAP_BPC_ADMIN” role.UserID – Must be assigned the “SAP_BPC_USER” role.

© SAP 2008 / Page 12

Limiting Access with System User Groups – 1

You may want to limit the users in the Active Directory who can access Business Planning and Consolidation to a subset of all users.

Add the specific User IDs to a particular group and then configure, so that only the users in that group can access SAP Business Planning and Consolidation.

To limit Business Planning and Consolidation access:

From Server Manager, select Options > Define system user groups.

In the System user group name field, enter a unique name for this group. This name will be displayed in the Add Users assistant in the Admin Console.

In the Group description field, enter a meaningful description for the user group. (This value is for future use).

© SAP 2008 / Page 13

Limiting Access with System User Groups – 2

From the Domain type field, select Active Directory or Local Windows. (These are the only domain types supported at this time).

In the Domain Name field, enter (or modify) the name of the fully qualified domain name. This must be a domain already set up by a system administrator. For a local user, enter a local computer name.

In the User group filter field, enter (or modify) a filter that gets user names from the specified domain and server. Here are some examples:

© SAP 2008 / Page 14

System User Groups: Considerations

It is very important to note that you should create a system user group for your Active Directory tree.

This is a requirement of the Active Directory "tree”:– If you try to select a user from the entire Active Directory, this will typically time out.

Therefore, you need this to limit where SAP Business Planning and Consolidation searches in the Active Directory for potential SAP Business Planning and Consolidation users.

It is also recommended that all SAP Business Planning and Consolidation users reside within a single domain.

It is possible to use multiple domains, however the following considerations must be taken into account:– User authentication so users can access accounts– Identify users from trusted domains– Provide installation users rights to browse users from all domains

© SAP 2008 / Page 15

Connectivity: Lesson Summary

You should now be able to:Understand and explain the basic concepts of connectivityUnderstand the different types of users involved in the internal interfacesGet started with troubleshooting issues related to connectivity


Debugging

© SAP 2008 / Page 2

Debugging: Lesson Objectives

After completing this lesson, you will be able to:Explain the process for debugging debug code within the ABAP tierDescribe general configuration points to configure an Active Directory use to use SAP Business Planning and Consolidation for debuggingDescribe the steps for setting the breakpointList exceptions to debugging code within the ABAP tier

© SAP 2008 / Page 3

Benefits of Debugging

There are several benefits related to learning this topic, including:Ensuring a more stable systemEnabling more expedient problem resolution

© SAP 2008 / Page 4

Function of Debugging

SAP Business Planning and Consolidation Debugging provides:

More expedient problem resolutionA way of enabling users to actively debug API’s in the ABAP tier

© SAP 2008 / Page 5

Capabilities for Solution Experts Using

The way that SAP Business Planning and Consolidation Debugging allows solution experts to:

Actively debug problems should issues ariseUse new debugging technology within SAP Business Planning and Consolidation.

© SAP 2008 / Page 6

How to Debug the ABAP Tier

Level 1 DebuggingWhen you need to Debug the ABAP system

Ensure that a Debug user has been configured for your Active Directory accountGeneral Steps in Task

Set a breakpoint in your APIRun a process that executes the API you want to debug

© SAP 2008 / Page 7

Configure the .NET Tier Debugging

To configure an Active Directory user to use SAP Business Planning and Consolidation Debugging:

Log into the .NET Application Server and launch Server Manager.Select Server -> Maintain Debug UsersEnter your BPC User ID, Debug User ID and Debug Password.Click Update.

© SAP 2008 / Page 10

ABAP Debugging Exceptions

To aide in debugging make note of the following:Since the SAP Business Planning and Consolidation application is not driven from SAPGUI– APIs are all called from the .NET TIER– As a result, SAP Business Planning and Consolidation does not use classic exception

(e.g. RAISE IOBJ_NOT_FOUND).All function modules for SAP Business Planning and Consolidation have the following exporting parameters:– ET_SUCCESS ( UJ_FLG)– ET_MESSAGE (UJ0_T_MESSAGE)ET_SUCCESS should always be set as “Y” for all successful calls to ABAPFor all SAP Business Planning and Consolidation APIs, sy-msg is set if there is an error in function moduleBusiness Planning and Consolidation has a central class to log errors:– CL_UJ_UTL_MESSAGE=>SET_SY_MSG.

© SAP 2008 / Page 11

Debugging: Lesson Summary

You should now be able to debug code within the ABAP tier.Explain the process for debugging debug code within the ABAP tierDescribe general configuration points to configure an Active Directory use to use SAP Business Planning and Consolidation for debuggingDescribe the steps for setting the breakpointList exceptions to debugging code within the ABAP tier


Installation

© SAP 2008 / Page 2

Installation: Lesson Objectives

After completing this lesson, you will be able to:Understand and explain the basic concepts of installation.Begin to prepare for installation.

© SAP 2008 / Page 3

Benefits of Installation

There are several benefits related to learning this topic, including:Installation of SAP Business Planning and Consolidation softwareConfiguration of SAP Business Planning and Consolidation software

© SAP 2008 / Page 4

SAP Education Curriculum Related to Installation

Installation of SAP Business Planning and Consolidation should be performed by qualified individuals with the appropriate technical know-how and experience. Typically, an experienced SAP basis (systems) consultant leads installation tasks.

Source: Curriculum TechnologyAssociate/ProfessionalPlatform TechnologySAP NetWeaver 7.0

© SAP 2008 / Page 5

Installation Support Documents

The controlling sources of information are the:

SAP NetWeaver Master Guide, Installation Guide:

http://service.sap.com/instguides >SAP NetWeaver > SAP NetWeaver 7.0 (2004s) Installation

SAP Business Planning and Consolidation Master Guide, Installation Guide, Configuration Guide:

http://service.sap.com/instguidescpm-bpc > Release 7.0 NW

Product Availability Matrix:http://service.sap.com/pam

© SAP 2008 / Page 6

Architecture SAP Business Planning and Consolidation: Installation View

Perform normal SAP NetWeaver BI 7.0 Installation –including Database, application server(s)

Perform installation of Web Server (IIS) & .NET Application server components

Perform installation of Front-end client tools

Important Note: SAP NetWeaver typically runs on a 64-bit server; Web Server (IIS) & .NET Application server components run on a 32-bit Windows server

© SAP 2008 / Page 7

SAP Business Planning and Consolidation: Installation Scenarios

The SAP Business Planning and Consolidation Installation has a standalone .NET Server, a SAP Business Planning and Consolidation Add-on, as well as a Client installation.

You can install the ABAP Add-on for SAP Business Planning and Consolidation in one of two configurations:

On a pre-existing NetWeaver BI 7.0 system (that meets minimum prerequisites)

OR

On a completely new NetWeaver BI 7.0 system.

© SAP 2008 / Page 8

Basic Server Installation Sequence

Basic steps for the server installation

1. Acquire (or verify) hardware.

2. Verify and install prerequisites.

3. Acquire installation media.

4. Verify/upgrade/install SAP Business Planning and Consolidation, version for SAP NetWeaver.

5. Install SAP Business Planning and Consolidation ABAP Add-on.

6. Perform post-installation steps for SAP Business Planning and Consolidation ABAP.

7. Install BPC .NET server.

8. Configure the BPC .NET server.

© SAP 2008 / Page 9

Basic Client Installation Sequence

Basic steps for the client installation

1. Verify and install client prerequisites.

2. Uninstall any previously installed version of SAP Business Planning and Consolidation clients.

3. Install new SAP Business Planning and Consolidation clients (Admin or Office).

© SAP 2008 / Page 11

Client Installation Prerequisites

Microsoft Windows XPInternet Explorer 6.0 (or above)Office 2003 or Office 2007Visual Basic 6 & Visual C++ Runtimes*MSXML 3.0 SP 7MSXML 4.0 SP 2.NET 1.1.NET 2.0Xceed Zip**

* 3rd party components installed during SAP Business Planning and Consolidation installation.** Must be installed prior to running the installation – available on SAP SWDC.

© SAP 2008 / Page 12

.NET Server Preparation Sequence

Verify Windows Server 2003 32bit Support Pack 2.

Install IIS (5.1 or 6.0).

Install .NET Framework 1.1 and 2.0.

Ensure Microsoft XML 3.0 SP1 and 4.0 SP2 are installed.

Install Dundas, Farpoint, and Amyuni.

© SAP 2008 / Page 13

SAP NetWeaver Installation Sequence

SAP Business Planning and Consolidation installation sequence (not installing on a preexisting SAP NetWeaver BI system)

Install Database (depending on RDBMS type this may happen prior to application server installation, defer to installation guide).

Install SAP NetWeaver 7.0 SR3 (Usage Type: AS-ABAP).

Upgrade support pack version to SAP NetWeaver 7.0 SPS15.

Install SAP NetWeaver 7.0 EHp1.

Run Standard NetWeaver post installation steps.

Optimize the SAP NetWeaver ABAP for SAP NW BI usage.

Install SAP Business Planning and Consolidation Add-on.

© SAP 2008 / Page 14

Sequence for Installation on an Existing SAP NetWeaver BI 7.0 System

SAP Business Planning and Consolidation sequence (when installing on a preexisting SAP NetWeaver BI 7.0 system)

Upgrade support pack version to SAP NetWeaver 7.0 SPS15.

Install SAP NetWeaver 7.0 EHp1.Note: Set the appropriate basis parameters e.g. abap/buffer size to at least 1000000 to avoid swapping.

Install SAP Business Planning and Consolidation Add-on.

© SAP 2008 / Page 15

Configure SAP Business Planning and Consolidation ABAP (1)

To set the /CPMB/ namespace to changeable, go to transaction SE06 and choose System Change Option. Check that the BPC Add-on is set to Restricted Modifiability, and then set the /CPMB/ namespace to Modifiable.

To set the /B28/ namespace to changeable, go to transaction SE06 and choose System Change Option. Check that the SAP Business Planning and Consolidation Add-on is set to Restricted Modifiability, and then set the /B28/ namespace to Modifiable.

Install SAPGUI 7.10 on the .NET server (or librfc32.dll manually). SAP Business Planning and Consolidation uses the SAP Connector, which relies on the librfc32.dll. You can install the DLL without installing SAP GUI. See SAP note 182805.

© SAP 2008 / Page 16


Using transaction PFCG, create the three SAP Business Planning and Consolidation users (BPC_ADMIN, BPC_SYSADMIN, and BPC_USER) and assign them to the provided SAP Business Planning and Consolidation roles.

If not already created, create the ALEREMOTE user and assign it to the roles S_BI-WHM_RFC and S_BI-WX_RFC. These roles allow the user to load data from an external system. (If SAP NetWeaver has been configured appropriately, this user is already defined.)

Using the transaction RSTPRFC, set up transports by creating the RFC destination for the After Import method. Save the password, then assign the BW client. For more information, see the information at help.sap.com http://help.sap.com/saphelp_nw70/helpdata/en/45/b517e0ed2f52f5e10000000a1553f7/content.htm

© SAP 2008 / Page 17


Assign authorization to activate business content (i.e. default BI objects) to the BPC_SYSADMIN user.

Assign role S_RS_ALL to the BPC_SYSADMIN user. We recommend that you also assign the SAP_ALL role during the installation process of ApShell. You can remove the SAP_ALL role after the installation of ApShell.

Using transaction SE38, run program UJA3_WRITE_SYS_USERS and assign the three service users (BPC_ADMIN, BPC_SYSADMIN, BPC_USER).

© SAP 2008 / Page 18


Create entries in the SAP Business Planning and Consolidation Transports table by doing the following:

Go to transaction SM30.Enter the table name UJT_TRANS_CHG, then click Maintain.Choose New Entries.From the TLogo Object column, select one of the available entries, then select Development in the adjacent column.Repeat step 10d for each available item in the table.After all entries have been added, click the Save pushbutton.

© SAP 2008 / Page 19


To install ApShell, run the program UJS_ACTIVATE_CONTENT, which runs the several post-installation steps.

In the Content Activation window, set the AppSet ID as ApShell and the Content Version as 1. It is important that you run this program run twice. The first time, choose all options except for the Load Data Into AppSet option. Once this is complete, run this program again and choose only the Load Data Into AppSet option. Then take the following steps:

a) Select Program Execute in background.

b) Check the logs by selecting System Own Jobs.

c) Select the job and display the Spool.

© SAP 2008 / Page 20


If you selected the Update Default Users option during the ApShell installation, run the UJA3_WRITE_SYS_USERS program again (transaction SE38), and assign the three service users (BPC_ADMIN, BPC_SYSADMIN, BPC_USER).

For the SYSADMIN user, specify a Windows domain user that you want to have initial access to APSHELL. When you specify a domain user in this field, the system does not check task security for this user, since this user is used to initially logon to ApShell.

Using the transaction SM59, run a connection test on the RFC destination MDX_PARSER.

© SAP 2008 / Page 21

Install and Configure on .NET / Web App Server

Install BPC .NET ServerUse Install shield

Update IIS PropertiesWeb Service ExtensionsAuthenticationUpdate Web.config with the port of IIS appserver URLSet IIS to run in 32 bit mode as outlined in this KB article:– http://support.microsoft.com/kb/894435

© SAP 2008 / Page 22

Client Installation (1 of 3)

Ensure Microsoft Office 2003 or Microsoft Office 2007 is installedNOTE: If full version was not installed, please install the Microsoft Interoperability Libraries: http://msdn.microsoft.com/en-us/library/kh3965hw(VS.80).aspx.

Ensure Microsoft .NET Framework 1.1 and Microsoft .NET Framework 2.0 are installed.

Ensure MSXML 3.0SP1 and MSXML 4.0SP2 are installed.

Ensure IE 6.0 or above is installed.

© SAP 2008 / Page 23


From the Launch Page, click the Client Software Center and install SAP Business Planning and Consolidation on the client.

© SAP 2008 / Page 24


To install BPC for Office or BPC Administration, go to the Software Center page, click the option to initiate the installation on the client.

© SAP 2008 / Page 25

Installation: Lesson Summary

You should now be able to:Understand and explain the basic concepts of installation.Begin to prepare for installation.

SAP Business Planning and Consolidation 7.0,version for SAP NetWeaverTechnical Solution Changes

Optimization

© SAP 2008 / Page 2

Optimization: Lesson Objectives

After completing this lesson, you will be able to:Understand the new optimization featuresUnderstand what happens during optimization effortsKnow the difference between Lite and Full optimzationsDecide when to use Lite vs. Full

© SAP 2008 / Page 3

Benefits of Optimization

There are several benefits related to learning this topic, including:Understanding a new component in SAP SAP Business Planning and Consolidation that optimizes system performanceBeing able to use the optimization options to achieve SAP Business Planning and Consolidation performance objectivesDetermining the best time to use the optimization options so that system performance is not affected when resource demands are high

© SAP 2008 / Page 4

Function

Optimization is a process for storing data in the best fashion for performance. The concept has not changed from SAP Business Planning and Consolidation 5.X to SAP SAP Business Planning and Consolidation, version for SAP NetWeaver. However the execution of this concept is quite different.

In SAP Business Planning and Consolidation 5.X data was stored in the ‘writeback’table then moved into a more optimal storage location. In this presentation we will review a similar process.

This process is executed based on the specific customer situations. Generally speaking, the frequency and quantity of data created is directly related to the optimization frequency.

© SAP 2008 / Page 5

Application Optimization Overview

When new application sets and applications are created, typically, there will not be a lot of data available.

Optimize will run a number of technical steps on the NetWeaver BI InfoCube in an attempt to improve performance.

There is no rule for how often to run optimizations, but as data volumes increase, it is recommended to run Optimize periodically.

There are two different types of optimizations available:Light Optimize: will close the open request, compress and index the cube, and update database statistics for the BI Cube.Full Optimize: will perform the same operations as Light Optimize, but will also check the NetWeaver BI data model. If the data model can be improved, Full Optimize will do so, and this could take a long time to run (for cubes with large data volumes). This will be discussed further in the Technical details section.

© SAP 2008 / Page 6

Application Optimization Overview –Place Holder Slide

Information is to Be Added in the FutureThank you for your patience.Please return.

© SAP 2008 / Page 7

Optimization: Lesson Summary

You should now be able to:Understand the new optimization featuresUnderstand what happens during optimization effortsKnow the difference between Lite and Full optimzationsDecide when to use Lite vs. Full

TZBPC2 en Col84 Presentation

Documents

Transcript of TZBPC2 en Col84 Presentation