TZBPC2

<Course Number and Course Title FSC123 Overiew>

SAP Business Planning and Consolidation 7.0, version for SAP NetWeaver

2008/Q4

© SAP 2008 / Page 1

Copyright 2008 SAP AG All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other 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 Hotlinks zugreifen, 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 2008 / Page 2

SAP Business Planning and Consolidation 7.0, version for SAP NetWeaver Technical Solution Changes

New Version Functions

New Version Functions: Lesson Objectives

After completing this lesson, you will be able to:
Understand and explain architectural concepts Begin planning for technical requirements Plan for language support Understand SAP’s maintenance strategy

© SAP 2008 / Page 2

including: Gaining insight into system architecture Understanding technical requirements. Learning to consider Version Lifecycle Planning while taking into account SAP’s maintenance strategy © SAP 2008 / Page 3 .Benefits of New Version Functions There are several benefits related to learning this topic.

NET 1.1 A/S Web Server (IIS) File Share © SAP 2008 / Page 4 . version for Microsoft Platform Server-side Requirements MS SQL Server MS Analysis Services MS Reporting Services MS DTS (or SSIS) .Architecture of SAP Business Planning and Consolidation.

Architecture SAP Business Planning and Consolidation. version for SAP NetWeaver © SAP 2008 / Page 5 .

Server-Side Requirements for SAP Business Planning and Consolidation Server-side requirements SAP NetWeaver BI Enhancement Pack1 SAP NetWeaver BI for Add-on SAP Business Planning and Consolidation for SAP NetWeaver Any RDBMS SAP NetWeaver Supports .1 and 2.NET application server (both .0 are required) Web Server (IIS) © SAP 2008 / Page 6 .NET 1.

version for Microsoft platform)? Microsoft Reporting Services Microsoft DTS/SSIS Microsoft Analysis Services Additional Technical Differences Database agnostic (use an RDBMS) Processing shifted to SAP NetWeaver platform Files stored in database © SAP 2008 / Page 7 .SAP Business Planning and Consolidation General Technical Notes What was removed (as compared to SAP Business Planning and Consolidation.

NET 1.NET Web Server Tier (. .0) Thus.NET 1.NET Web Server connects to the ABAP Web Application Server using the SAP . each RFC (Remote Function Call) is a wrapper around an objectoriented class within the UJ package (also known as development class) Metadata is stored in BPC-specific tables Master data (aka: dimension members) and transactional data (aka :fact data) are stored in NetWeaver BI objects and tables © SAP 2008 / Page 8 .1) The .NET 2.NET Connector (v2.0 are required Internally.SAP Business Planning and Consolidation Architecture Notes Multi-tier architecture of the SAP Business Planning and Consolidation BPC for Office and BPC Admin Clients use Web services to connect to the .1 and .

High Level Feature Delta What’s In Integration 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) BPFs Books What’s Out 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.SAP Business Planning and Consolidation . reduce the length of a property Custom Menus © SAP 2008 / Page 9 .

Windows Server 2003.SAP Product Availability Matrix Information SAP NetWeaver Application Server Installed as an add-on to SAP NetWeaver BI EhP1 (Enhancement Package 1). Microsoft Office: 2003 and 2007.NET versions 1. Microsoft IIS 6. Database Systems: Any RDBMS (Relational Database Management System) supported by SAP NetWeaver. Enterprise Edition (32-bit x86). Only the AS-ABAP usage type is required for SAP Business Planning and Consolidation. Client Operating System: Windows XP.0.NET Application Server / Web Server Operating systems: Windows Server 2003. Enterprise x64 Edition. . ASJAVA usage type is not required. .sap. More information: see the product availability matrix at http://service.com/pam © SAP 2008 / Page 10 .1 and 2. Operating systems: Any operating system supported by SAP NetWeaver.0.

x Planned Languages (SP1) Slovakian Czech Danish Dutch Planned Languages (SP2) Finnish Norwegian Polish Swedish © SAP 2008 / Page 11 . Portuguese (Brazilian). Chinese (Simplified). Italian. Same as SAP BPC 5. Russian.SAP Business Planning and Consolidation Language Support Currently Supported Languages English. Japanese. Spanish. Korean. German. French (Standard).

Maintenance Strategy Maintenance Strategy – SAP Business Planning and Consolidation has the same maintenance strategy as the underlying SAP NetWeaver platform.com/releasestrategy © SAP 2008 / Page 12 . Maintenance information as of time of RKT material development: For the most up-to-date information on the SAP maintenance strategy.sap. see http://service.

of the NetWeaver release. version for SAP NetWeaver To be used when you need to refer to specific functionality/architecture/etc. SAP Business Planning and Consolidation.NET release. SAP Business Planning and Consolidation. of the Microsoft . © SAP 2008 / Page 13 . version for the Microsoft platform To be used when you need to refer to specific functionality/architecture/etc.One Voice: Product Names The official product names: SAP Business Planning and Consolidation To be used whenever possible.

New Version Functions: Lesson Summary You should now be able to: Explain architectural concepts Begin planning for technical requirements Plan for language support Understand SAP’s maintenance strategy © SAP 2008 / Page 14 .

SAP Business Planning and Consolidation 7.0. version for SAP NetWeaver Technical Solution Changes File Service .

File Service: Lesson Objectives After completing this lesson. Download and Delete a document to the SAP Business Planning and Consolidation File Service Configure Virus Scanning for files contained within the SAP Business Planning and Consolidation File Service Configure the SAP Business Planning and Consolidation File Service with WebAdmin parameters © SAP 2008 / Page 2 . 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 Service Upload.

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 component Using and configuring the SAP Business Planning and Consolidation File Service © SAP 2008 / Page 3 .

downloaded and deleted from the 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.

File Service Overview All files are stored in the database Most stored as BLOB’s Data Manager files stored in generated DB tables – – – Row by Row As String .csv files Gzip (GNU zip) compression is supported ZIP archive format is supported Virus Scanning is supported (configurable) Store ANY file types Transaction UJFS – File Service User Interface © SAP 2008 / Page 5 .

File Service Overview Directory structure differences between SAP Business Planning and Consolidation 5. version for SAP NetWeaver “Data” Folder is now referred to as “Root” in File Service Each AppSet has its own “Root” folder “AdminTemplates” folder is now AppSet specific © SAP 2008 / Page 6 .x and SAP Business Planning and Consolidation.

File Service Overview: How Files Are Stored Document Table .UJF_DOC Stores data for all documents Documents are stored as binary stream Data Manager files are stored in generated DB table Blob Generated Table © SAP 2008 / Page 7 .

File Service Overview: UJF_DOCTREE Document Tree Table .UJF_DOCTREE Stores the directory structure of SAP Business Planning and Consolidation File Service DIR_DOC field specifies if record is a Folder or Document PARENT_DOC field defines previous node in structure © SAP 2008 / Page 8 .

UJF_DOCMAP Used to map files/directories to specific modules API available which passes relative path and fills the placeholder values © SAP 2008 / Page 9 .File Service Overview: UJF_DOCMAP File Map Table .

UJF_APPSERV_DIR Used to select files from an application server directory At least one entry is required © SAP 2008 / Page 10 .File Service Overview: UJF_APPSERV_DIR Application Server Directory Table .

for Data Manager. from FTP Lock/Unlock Document Rename Document Copy Document Delete Document © SAP 2008 / Page 11 .File Service Overview: Available Functions UJFS Supported Functions Directory Functions Create Directory Copy Directory Change Directory Delete Directory Download All Documents (as ZIP) Document Functions Upload/Download Document – From PC.

file will be pulled from FTP site. Select the file location using the dialog. Upload from PC. choose “Open” © SAP 2008 / Page 12 . Upload from FTP. file will be stored row by row in a generated DB table. Right-click and select the upload method from the context menu. Upload for DM.Uploading Documents via UJFS Select a directory in which to upload the document. file will be stored as blob in the DB table. – FTP site must be inside the firewall.

Right-click on this document and choose the action from the context menu.Downloading Documents via UJFS Select the document in which to download. Download options As its associated file type Or as a ZIP file Choose file location © SAP 2008 / Page 13 .

Transaction Codes for Virus Scan Interface VSCAN VSCANGROUP VSCANPROFILE VSCANTEST VSCANTRACE Configuration of the Virus Scan Provider Configuration of the Virus Scan Groups Configuration of the Virus Scan Profiles Test for the Virus Scan Interface Memory Trace for the Virus Scan Server Should be done by an SAP NetWeaver (Basis) Administrator.Virus Scanning Standard NetWeaver Virus Scanning SAP NetWeaver is shipped with virus scanning deactivated.com/saphelp_nw70/helpdata/EN/b8/e6e540c1848131e10000000a155 0b0/frameset.sap. http://help.htm © SAP 2008 / Page 14 .

Data Manager: Accessing the File Service Get Document For Data Manager API Supports multiple access File Service Tables FTP Application Server – Local or Remote © SAP 2008 / Page 15 .

Data Manager: Additional Considerations If a file is to be read by Data Manager. 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. row by row. data manager files are no longer needed and can be deleted Program UJF_FILE_SERVICE_DLT_DM_FILES is used to delete these files © SAP 2008 / Page 16 .

DOT.XLT.PPT.XML (etc) No restrictions from transaction UJFS 500mb file tested successfully. Any file types. but not recommended.Technical Considerations Restrictions from client Associated WebAdmin Parameters – – – ALLOW_FILE_SIZE ALLOW_EXTENSIONS DEFAULT_EXTENSIONS value = 100mb value = ALL value = XLS.DOC. any extensions ZIP archives can be spliced into individual folders/files RAR is not supported by NetWeaver © SAP 2008 / Page 17 .

Download and Delete a document to the SAP Business Planning and Consolidation File Service Configure Virus Scanning for files contained within the SAP Business Planning and Consolidation File Service Configure the SAP Business Planning and Consolidation File Service with WebAdmin parameters © 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 Service Upload.

0.SAP Business Planning and Consolidation 7. version for SAP NetWeaver Technical Solution Changes Logging .

NET Server and the ABAP NetWeaver system.Logging: Lesson Objectives After completing this lesson. you will be able to enable logging and tracing on the .NET Client. the . © SAP 2008 / Page 2 .

including: Insight into how the system is functioning Expeditious responses to support cases Information key to performing root cause analysis should an issue arise © SAP 2008 / Page 3 .Benefits of Logging There are several benefits related to learning this topic.

Function SAP Business Planning and Consolidation Logging locations: SAP Business Planning and Consolidation .NET Log files IIS (Internet Information Services ) Log files Windows Event Viewer Tracing (ABAP Tier) © SAP 2008 / Page 4 .

Logging .log © SAP 2008 / Page 5 .The .NET Client Tier is available in: The Windows Event Viewer Ev4Excel50.NET Client Tier: Windows Event Viewer Logging on the .

NET Middle Tier The .Logging .NET Server Logs Microsoft IIS Server Logs Microsoft Windows Event Viewer Each of these logs Gives different information Can be used to troubleshoot issues © SAP 2008 / Page 6 .NET Middle Tier offers three primary logging mechanisms SAP Business Planning and Consolidation .The .

NET Middle Tier: Server Logs The SAP Business Planning and Consolidation Server Logs: Located in “\BPC\Logging” One subfolder for each module Only errors are logged Logs are time-stamped by day.The . A new file is created for each day.Logging . The contents of the log can viewed in your favorite text editor: © SAP 2008 / Page 7 .

Request-Based Tracing – Used for most common problem tracing .The . See the following documentation: http://www. there are numerous way to approach this.NET Middle Tier: Windows IIS Logs To troubleshoot Microsoft IIS (Internet Information Services ).microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/676400bc8969-4aa7-851a-9319490a9bbb.mspx?mfr=true There are 2 common traces for IIS: Currently Executing Requests Tracing – Use this for long running processes.see details here: – http://www.microsoft.Logging .mspx Standard IIS log files Default location is “%systemroot%\system32\LogFiles\W3SVC1” © SAP 2008 / Page 8 .com/technet/prodtechnol/WindowsServer2003/Library/IIS/b0aef644 -7b19-418d-b658-fde4a93678a9.

Logging .NET Middle Tier: Windows Event Viewer The Windows Event Viewer The Log Event Viewer area should display much of the same information as in the <BPC_SERVER>\BPC\Logging area © SAP 2008 / Page 9 .The .

Tracing with SAP NetWeaver (ABAP) SAP NetWeaver offers tracing capabilities as well as debugging capabilities Debugging can be used if Tracing and Logging don’t solve your issue Tracing 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 10 .

Tracing .Check for ABAP Dumps Use transaction ST22 to see if any ABAP dumps occur. © SAP 2008 / Page 11 .The ABAP Tier: ST22 .

Check RFC Transactions SAP Business Planning and Consolidation communication with the .The ABAP Tier: SM21 .NET Middle Tier occurs through RFC Use Transaction SM21 when checking system connections © SAP 2008 / Page 12 .Tracing .

RFC Connection Tracing SAP Business Planning and Consolidation Services Accounts are setup as communications users Communications users do not allow debugging as dialog connections RFC (Remote Function Call) trace in ABAP can be set in ST05 © SAP 2008 / Page 13 .The ABAP Tier: ST05 .Tracing .

The ABAP Tier: SLG1 . enter object “UJ” and execute SLG1. © SAP 2008 / Page 14 .Tracing .Analyse Application Log (1 of 5) The logs within SLG1 can show different types of information: Error Message Warning Message Debug Message To view all logs related to SAP Business Planning and Consolidation.

Tracing . and User © SAP 2008 / Page 15 .The ABAP Tier: SLG1 . Time.Display Logs (2 of 5) The output of the logs is as follows: Internal Program or BPC API (Function Module) issuing the log Module Issues the Log AppSet-Application Date.

Log Detail (3 of 5) To see detailed logs. © SAP 2008 / Page 16 . you can double click on the log item.Tracing .The ABAP Tier: SLG1 .

You can see all the MDX (MultiDimensional eXpressions) statements executed within the system logs as well.SQE Logs (4 of 5) The SQE logs all details based on the type of call. © SAP 2008 / Page 17 .Tracing .The ABAP Tier: SLG1 .

enter object “UJ” and execute SLG1 The SubObject also allows you to only see logs for a specific SAP Business Planning and Consolidation Module.Tracing .The ABAP Tier: SLG1 .SubObjects (5 of 5) View Logs To view all logs related to SAP Business Planning and Consolidation. © SAP 2008 / Page 18 .

Maintenance of System Logs Use transaction SLG2 to maintain system logs.Tracing . © SAP 2008 / Page 19 .The ABAP Tier: SLG2 .

Tracing . not SAP Business Planning and Consolidation authorizations) Kernel Functions General Kernel DB Access (SQL Trace) Table Buffer Trace RFC Calls Lock Operations © SAP 2008 / Page 20 .Other Traces Available All other traces can be executed through ST01: Authorization Check (for ABAP auth objects.The ABAP Tier: ST01 .

Logging: Lesson Summary You should now be able to enable logging and tracing on the . © SAP 2008 / Page 21 .NET Client. the .NET Server and the ABAP NetWeaver system.

version for SAP NetWeaver Technical Solution Changes Transports .SAP Business Planning and Consolidation 7.0.

Transports: Lesson Objectives After completing this lesson. and view logs © SAP 2008 / Page 2 . you will be able to: Understand the SAP Business Planning and Consolidation transport approach Learn what objects are transported Configure transports in SAP Business Planning and Consolidation Gain access to an overview of the SAP transport process for those new to SAP Business Planning and Consolidation Understand how standard SAP methodologies have been applied Use the standard TMS transaction to monitor the request.

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 Consolidation Using and configuring the SAP Business Planning and Consolidation Transports © SAP 2008 / Page 3 .

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 4 .

SAP Business Planning and Consolidation Transports Overview SAP Business Planning and Consolidation transports leverage the existing BI transports framework BPC TLOGO Object = APPS Configured in transaction code SOBJ (delivered) Entries from two shadow tables are transported UJT_TRANS_HDR UJT_TRANS_OBJ – This table contains ALL of the metadata from the UJ* tables © SAP 2008 / Page 5 .

changes for the SubObject will not be transported All SubObjects are delivered as changeable in Development © SAP 2008 / Page 6 .SAP Business Planning and Consolidation Transports Overview The AppSet must be offline In order to create a request In target Transporting of Data Manager files in File Service is NOT supported SubObjects (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 systems If a SubObject is not set as “D” (Development).

SAP Business Planning and Consolidation Transports Overview Specific files and directories within File Service are transported This is based off the transports config table UJT_TRANS_FIL This table can be modified via table maintenance. Transport of DM files is NOT supported File/Directories under sub-object NFIL. when there is a new application being created in the target system Pattern field can be specific or generic © SAP 2008 / Page 7 . are only transported to target system. transaction code SM30.

SAP Business Planning and Consolidation Transports Overview
TLOGO APPS also has its own after import method function module, RS_APPS_AFTER_IMPORT Called by the BI transports framework Calls 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 8

Create Transport Request per AppSet
Transaction UJBPCTR Choose Request Type Enter AppSet Id Execute the request

This is a customizing request Default request description Default Target layer Save to create request

© SAP 2008 / Page 9

Create Transport Request per AppSet
View the request using standard TMS transaction codes such as SE10 or SE09 Customizing request is created with one task underneath it An AppSet is transported as a single transportable object

© SAP 2008 / Page 10

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

© SAP 2008 / Page 11

Importing the Request SAP Business Planning and Consolidation transport requests must be promoted from one system to another Importing a request will overwrite objects in the target system View logs © SAP 2008 / Page 12 .

otherwise it will be executed in client 000 Use transaction RSTPRFC to create the destination for this client © SAP 2008 / Page 13 . routes. and other critical aspects Importing Client-Dependent Objects All SAP Business Planning and Consolidation Data is client-dependent User ALEREMOTE (BI Background User) must be created An RFC destination must be created in order for the after import method to be fired in the correct client.Setup and Prerequisites Transport System must be configured correctly (done by SAP NetWeaver Administrator) that is creating Transport Domains.

What not to Do with Objects and Transports Do Not Transport table entries without using SAP Business Planning and Consolidation Internal programs may be missed Do Not Transporting BI objects without using SAP Business Planning and Consolidation Will cause issues using standard BI transport methods © SAP 2008 / Page 14 .

Additional Transport Information This is a necessary prerequisite to be able to transport SAP Business Planning and Consolidation Application Sets.htm Use ABAP Program: UJT_CRT_BPC_TR © SAP 2008 / Page 15 .sap. http://help.com/saphelp_nw70/helpdata/en/45/b517e0ed2f52f5e10000000a1553f 7/content.

TLOGO Framework BI metadata framework. InfoCube ) Scripts Table Driven Logic/StoredProcedure Workbooks Reporting Journal Security Work Status Live Reports Comments Audit Package Transformation Files Conversion Files Changeability DEV DEV DEV DEV PROD DEV/PROD DEV PROD PROD PROD PROD PROD PROD DEV DEV . Transport of SAP Business Planning and Consolidation as well as Dependent BI Objects Transport available in SAP Business Planning and Consolidation by AppSet only OBJID ASET APPM K2SC TDLO WORK REPT JOUR SECU WSTA LREP COMM AUDI PACK FTRA FCON © SAP 2008 / Page 16 Text Appset Administration( Dimension. InfoArea.

and view logs © SAP 2008 / Page 17 .Transports: Lesson Summary You should now be able to: Understand the SAP Business Planning and Consolidation transport approach Learn what objects are transported Configure transports in SAP Business Planning and Consolidation Gain access to an overview of the SAP transport process for those new to SAP Business Planning and Consolidation Understand how standard SAP methodologies have been applied Use the standard TMS transaction to monitor the request.

SAP Business Planning and Consolidation 7.0. version for SAP NetWeaver Technical Solution Changes Case Sensitivity .

Case Sensitivity: Lesson Objectives After completing this lesson. you will be able to: Understand and explain the issues arising with case sensitivity differences. © SAP 2008 / Page 2 . Take case sensitivity issues into account on your project. Develop a strategy for effectively managing case sensitivity.

including: Gaining knowledge of case sensitivity issues. Having the know-how to develop a strategy to manage case sensitivity.Benefits of Case Sensitivity There are several benefits related to learning this topic. © SAP 2008 / Page 3 .

however it does not allow duplicate values to be accepted in any case. to be come case insensitive. this is exactly how it will be stored in the MS-SQL DB If you try to save a value “CASH”. if you do this when you save the value “Cash”. Microsoft allows data to be stored in any case. SAP NetWeaver would treat “cash” and “CASH” as a completely separate values.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. the MS-SQL DB treats this value as being equal to “Cash”. That means by default. © SAP 2008 / Page 4 . Example If you have the string “Cash”. so that it will convert everything to UPPERCASE. and will prevent you from creating “duplicate” entries SAP NetWeaver is fully case sensitive. However. it would be stored as “CASH”. You can change this behavior in SAP NetWeaver.

including members and properties File Service . “CASH” or “SalesUSNEast”) is case sensitive.behaves the same way as SAP Business Planning and Consolidation. version for the Microsoft platform © 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. “cash” and “CASH” are considered the same value) Master data (for example. AppSet or Application names) behaves the same way as in SAP Business Planning and Consolidation.e. version for the Microsoft platform (i.

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 6 .

application names. property names. script logic file names.Case Sensitivity: Metadata SAP Business Planning and Consolidation will check to ensure that duplicate values can not be created in any case Applies to: AppSet names. dimension names. work states. task/member profile names © SAP 2008 / Page 7 . team names.

metadata descriptions store two versions of the same value Typically. the field “Caption” stores the value in the case that should be presented to the user The other field (in this example. “Dimension”) stores it in UPPERCASE to ensure duplicate values are not allowed © SAP 2008 / Page 8 .Case Sensitivity: Internal Handling for Metadata Internally.

You can now create duplicate member ID’s in different cases.Case Sensitivity: Master Data (1) Master data is fully case sensitive in SAP Business Planning and Consolidation. © SAP 2008 / Page 9 .

as well as submitting data). and in Member Access Profiles. This includes Workbooks (such as EVGET formulas. in Work Status. in Script Logic.Case Sensitivity: Master Data (2) That means everywhere the user refers to a member (master data value). Invalid Member returns no data Valid Member returns data © SAP 2008 / Page 10 . you must use the specific case.

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

Some of these files are cached on the end-user’s PC.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. we would get in errors when downloading these files. © SAP 2008 / Page 12 . Since Microsoft Windows does not support full case sensitivity. It is for this reason that it is not supported to have dimensions/applications/etc to have the same name in a different case.

). K2 Script Files and Data Manager Files. Training/Education Note: Be aware that choosing “Mixed Case” has a performance impact. there are several aspects to consider: Master Data. Transactional Data and Other Data (Work Status. Workbooks. version for SAP NetWeaver. Member Access Profiles.Case Sensitivity during Migration When Migrating from SAP Business Planning and Consolidation 5. 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 13 .x to SAP Business Planning and Consolidation. Content Library Application Context etc.

Case Sensitivity: Summary The platforms cause SAP Business Planning and Consolidation 5. version for SAP NetWeaver handle case sensitivity differently Metadata and File Service behave the same way with respect to case sensitivity as SAP Business Planning and Consolidation 5.x Dimension Members and Properties are case sensitive in SAP Business Planning and Consolidation. especially for dimension members Always have dimension members in UPPERCASE © SAP 2008 / Page 14 .x and 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.

Case Sensitivity: Lesson Summary You should now be able to: Understand and explain the case sensitivity issues Take case sensitivity issues into account on your project Develop a strategy for effectively approaching case sensitivity © SAP 2008 / Page 15 .

0.SAP Business Planning and Consolidation 7. version for SAP NetWeaver Technical Solution Changes Custom Process Types .

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 Types List terminology related to Data Manager List delivered Process Types List keywords supported in Runtime Understand how Data Manager relates to Process Chains Get started in developing and implementing custom Process Types © SAP 2008 / Page 2 .

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 Types Knowing which Data Manager packages are available when you implement custom Process Types with SAP Business Planning and Consolidation Learning a powerful feature which provides you with the ability to perform operations that are not delivered with the standard process types © SAP 2008 / Page 3 .

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

PC is a framework.Context: Data Manager – Delta Terminology Object: Data Manager Package Task / Process Type Process Chain PC Acronym DM Description The module to transform and load and manipulate data The operational unit that user can execute for a data process. E. An SSIS package is roughly equivalent to a NW BI Process Chain. that helps to schedule packages. The Multi Dimensional Data Cube in BW. export. load helps to transfer data from file to cube.g. like import. These are no longer relevant for SAP Business Planning and Consolidation. etc. PC is the foundation of a package. which is provided by BW. Is a BI InfoObject that contains dimension members (Master Data) Is a BI Object that stores the value (Key Figure) This is an Excel Workbook that defines mappings for data transformations This is an Excel Workbook that defines conversions within data transformations. InfoCube DTS (SQL 2000) SSIS (SQL 2005) Dimension Measure Transformation File Conversion File DTS or SSIS © SAP 2008 / Page 5 . (ROLAP) Data Transfer Service or SQL Server Integration Services. provided by Microsoft. wrap tasks into packages and so on. Package is built on Process Chains which include task(s). from cube to cube. from cube to file. maintain status of running packages. The module to deal with specific functionality.

as per your requirements © SAP 2008 / Page 6 . You might want to modify packages to behave differently or to perform additional tasks. version for SAP NetWeaver (not best practice) or use those packages as templates to build package.Context: Data Manager Packages Data Manager packages are implemented as process chains and allow you to do common data manipulation activities The 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 can make modifications to the packages supplied with SAP Business Planning and Consolidation .

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 Manager Only 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 7 .

© 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 Packages Financial Packages Administrative Packages Example Packages These process chain templates can be displayed and edited in ABAP transaction RSPC.

Context: Standard Data Manager Delivered Packages (1) PROCESS CHAIN TEMPLATE BPC: Import Master Data DESCRIPTION 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) This package allows you to load dimension member texts directly into a EVDESCRIPTION (BW InfoObject's text table) This package imports one or more ASCII files into the current application. You can use the import.xls transformation file with this package. The signs of the amounts are reversed based on the Account type. 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. TECH NAME /CPMB/IMPORT_MASTER BPC: Import Master Data Description /CPMB/IMPORT_DESCRIPT BPC: Import Transaction Data /CPMB/IMPORT BPC: Load Transaction Data from Other Cube /CPMB/LOAD_INFOPROVIDER © SAP 2008 / Page 9 . You are prompted for one or more import file and associated transformation files.

The destination selection's fact table records are cleared before the source's records are moved. The optimize process removes the zero values. You are prompted for source and destination data selections for all dimensions.xls transformation file with this package. Running this package also clears comments from the comments table.Context: Standard Data Manager Delivered Packages (2) PROCESS CHAIN TEMPLATE BPC: Move Transaction Data in one cube DESCRIPTION This package lets you move any selection of data within an application. TECH NAME /CPMB/MOVE BPC: Clear Transaction Data in One Cube This package clears the data in the SAP Business Planning and /CPMB/CLEAR Consolidation Application by importing zero values. which clears all values from the table. and then runs default logic against the imported data set. the package will not run. If you select [All].xls transformation file with this package. You can use the import. /CPMB/COPY BPC: Copy Transaction Data in One Cube BPC: Append Transaction This package imports data into the application by appending the /CPMB/APPEND Data data to the fact table. The source's fact table records are cleared after they are moved to the destination. This package copies data between dimensions within an application. You can use the import. © SAP 2008 / Page 10 . You must select at least one dimension in order to run this package.

Context: Delivered Process Types SAP Business Planning and Consolidation delivers the following process types: Admin Task Audit Archive Clear BPC Table Clear Comments Clear Cube Convert Convert for Copy and Move Create Dimension Dynamic Modify Email FTP Finalize Optimize Journals Load Master Data Load Master Data Description Load Optimize Cube Ownership Calc Run Logic OnLine Status © SAP 2008 / Page 11 .

Custom Process Types: Building Custom Instructions using UI Script © SAP 2008 / Page 12 .

Custom Process Types: Parameters Available The following types of Parameters are available: Process Type .Net Dynamic Constant Key words Process Chain © SAP 2008 / Page 13 .

© 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 Chain Process Type Each process type has a variant.

%APPSET%) INFO Administrator can define fixed package values. “50000”) These are package parameters. © SAP 2008 / Page 15 . “.APPSET. Example: TASK(EXPORT_ZERO.%TEMPPATH%%RANDOMFILE%) Examples: INFO(DELIMETER.”) or INFO(PACKAGESIZE. Variables are evaluated: Prompt Info (get_info) Package Example: INFO(%TEMPFILE3%. each task defines a work item to be performed as part of the Data Manager runtime process.Custom Process Types: Supported Keywords for Runtime FUNCTION NAME TASK DESCRIPTION A Process Chain Template includes one or more tasks. This will not change. PROMPT() command Generates customized dialog boxes for users to enter information for package.

© SAP 2008 / Page 16 . We will provide two methods (get_para and set_para) so every process type can get all process chain parameters. This is an executable instruction that can be entered in the EvDTSModifyPkg task script. All the process type parameters are stored in this table. CONNECTION STEP Coordinates the flow of control and execution of tasks in a DTS package.Keywords from SAP Business Planning and Consolidation 5. GLOBAL In NetWeaver we have a global table UJD_PRCPARA. Global is used in MS to pass parameters form one custom task to another.x That Are not Supported FUNCTION NAME DESCRIPTION Establishes a connection to a data source. This is an executable instruction that can be entered in the EvDTSModifyPkg task script.

OwnerShip.Rate C:\BPC\DATA\WEBFOLDERS\APSHELL\FINANCE\ Will be the DB File server path [CATEGORY] C:\BPC\DATA\WEBFOLDERS\APSHELL\FINANCE\ DATAMANAGER\CONVERSIONFILES\ [RPTCURRENCY] C:\BPC\DATA\WEBFOLDERS\APSHELL\FINANCE\ DATAMANAGER\DATAFILES\ Will be the DB File server path %DATAROOTPATH% %DEFAULT_MEASURE% data root path Default measure value C:\BPC\DATA\WEBFOLDERS\ Will be the DB File server root path PERIODIC © SAP 2008 / Page 17 .Dynamic Constants (1 of 2) NAME %Account_DIM% %App% %App_List% %APPPATH% %CATEGORY_DIM% %CONVERSIONPATH% %CURRENCY_DIM% %DATAPATH% DESCRIPTION dimension type A application name application list application path dimension type C conversion file path dimension type R data file path EXAMPLE [Account] Finance Finance.LegalApp.LRate.

[INTCO].Dynamic Constants (2 of 2) NAME %DIMS% %ENTITY_DIM% %FACTDIMS% %LOGICPATH% DESCRIPTION dimension list EXAMPLE [ACCOUNT].[INTCO].[TIME] [ACCOUNT].[TIMEID] C:\BPC\DATA\WEBFOLDERS\APSHELL\FINANCE\ ADMINAPP\FINANCE\ Will be the DB File server path %MEASURES% %SELECTIONPATH% %SQLSERVER% %TIME_DIM% measure list Selection file path SQL server name SIGNEDDATA.YTD C:\BPC\DATA\WEBFOLDERS\APSHELL\FINANCE\ DATAMANAGER\SELECTIONFILES\ SOLDEVHWK01 dimension type E [ENTITY] fact dimension list logic path dimension type T [TIME] C:\BPC\DATA\WEBFOLDERS\APSHELL\FINANCE\ DATAMANAGER\TRANSFORMATIONFILES\ Will be the DB File server path \Root\WEBFOLDERS\DEV7D\FINACE\PRIVATEPUBLICA TIONS\SAP_ALL\I045795\TEMPFILES\ SOLDEVHWK01\HWKIM %TRANSFORMATIONPATH% transformation path %TMP_PATH% %USER% © SAP 2008 / Page 18 Temp file path User ID .[DATASRC].[ENTITY]. [RPTCURRENCY].QTD.[DATASRC].PERIODIC. [RPTCURRENCY].[CATEGORY].[ENTITY].[CATEGORY].

which contains your specific logic code © SAP 2008 / Page 19 .Points to Note While Creating Custom Process Types Custom process types must implement following interface IF_RSPC_EXECUTE IF_RSPC_GET_VARIANT IF_RSPC_MAINTAIN IF_RSPC_TRANSPORT (this is needed in our delivered process type. it can miss this interface) Each process type must have a type name no longer than 10. and if the custom process type does not need transport. we need to add logical code The class must inherit from class cl_ujd_actor or its derived class. and it has to implement a static method SET_PC_TYPE to set the type name When the process type class is create. usually there is no need to overload base class methods You must create a new class to implement the interface IF_UJD_TASK.

Custom Process Types: Lesson Summary You should now be able to: Explain the concept of the Data Manager and building custom Process Types List terminology related to Data Manager List delivered Process Types List keywords supported in Runtime Understand how Data Manager relates to Process Chains Get started in developing and implementing Custom Process Types © SAP 2008 / Page 20 .

0.SAP Business Planning and Consolidation 7. version for SAP NetWeaver Technical Solution Changes Technical Parameters and Internal Programs .

© SAP 2008 / Page 2 . Identify and use new additional Internal Programs of SAP Business Planning and Consolidation system. you will be able to: Identify and use new additional Technical Parameters of SAP Business Planning and Consolidation system.Technical Parameters and Internal Programs: Lesson Objectives After completing this lesson.

A possibility to test the data quality. © SAP 2008 / Page 3 . script logic. and SQE logs of the SAP Business Planning and Consolidation application. An opportunity to do the server maintenance work. including: A chance for the server administrator to influence the server configuration and the behavior of the server.Benefits of Technical Parameters and Internal Programs There are several benefits related to learning this topic.

Where Is It Performed? se38 transaction for programs se11 transaction for tables © SAP 2008 / Page 4 .

such as RSADMIN.Technical Parameters SAP Business Planning and Consolidation has some hidden technical parameters that can be set internally (not exposed in Web Admin). © SAP 2008 / Page 5 . These parameters are in addition to the already existing SAP NetWeaver parameters. 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).

These values are maintained at the individual application level.SAP Business Planning and Consolidation Parameters – Write Back Table UJR_PARAM stores parameters for write-back. 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 6 .

BPQ Parameters – Shared Query Engine Table UJQ_PARAM stores parameters for shared query engine. Entries with default values are inserted into table UJQ_PARAM when not present © SAP 2008 / Page 7 . and they are: SPARSITY_COEF (default = 5). These values are maintained at the individual application level.

Program UJ0_STATISTICS_DELETE Program UJ0_STATISTICS_DELETE will allow you to delete old statistical records. © SAP 2008 / Page 8 .

© SAP 2008 / Page 9 .Program UJ_MEMACS_MAINTAIN Program UJ_MEMACS_MAINTAIN will rebuild the member access cache for security checks.

Program UJA_COPY_APPLICATION Program UJA_COPY_APPLICATION will allow you to copy an application. © SAP 2008 / Page 10 .

© 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.

ADMIN.Program: UJA3_WRITE_SYS_ADMIN_NO_CHECK Program UJA3_WRITE_SYS_ADMIN_NO_CHECK will allow you to update the SYS_ADMIN. © SAP 2008 / Page 13 . 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.

Program: UJK_SCRIPT_LOGIC_TESTER Program UJK_SCRIPT_LOGIC_TESTER will allow you to test and debug script logic. © SAP 2008 / Page 15 .

© 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.

Program: UJQ_SQE_TEST Allows you to test SQE calls if you find issues within the logs. © SAP 2008 / Page 18 .

© 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 .

Program: UJT_CHECK_TABLE_ENTRIES Program UJT_CHECK_TABLE_ENTRIES will allow you to check table entries for transports. © SAP 2008 / Page 20 .

Program: UJT_CRT_BPC_TR Program UJT_CRT_BPC_TR will allow you create a request for transports. © SAP 2008 / Page 21 .

© SAP 2008 / Page 22 .All SAP Business Planning and Consolidation Programs All SAP Business Planning and Consolidation Internal Programs are in package UJ*.

Identify and use new additional Internal Programs of SAP Business Planning and Consolidation system.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. © SAP 2008 / Page 23 .

version for NetWeaver Technical Solution Changes BPC Performance Statistics .0.SAP Business Planning and Consolidation 7.

© 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. Delete old statistic records. Use the BPC Performance Statistics report and analyze the output (Transaction UJSTAT). Turn the statistics on and off.

© SAP 2008 / Page 3 .1? This is new functionality which is available only with SAP Business Planning and Consolidation.What is Different from SAP Business Planning and Consolidation 5.

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. The . The target user of the Statistics Framework will be Consultants and Support staff trying to analyze performance problems. Write-Back. Note: that SAP Business Planning and Consolidation Statistics only measures the ABAP portion of the total runtime.NET server and client code is not measured in this framework. The statistics allow you to very quickly and easily identify the most time consuming part of a request. © SAP 2008 / Page 4 . etc).

and includes information such as. the user. they are separated into Header and Line Item records. and the Action being performed. The total runtime of the request is calculated by adding up the runtime on each line item record. including the start date/time and the total runtime. It operates on the concept of “Actions” and “Events”. © 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. A “line item” record contains information on each individual Event. When Statistics are recorded. A “header” record contains information about the whole request.

© SAP 2008 / Page 6 . no statistics will be collected.Turning Statistics On/Off By default. and continue to keep drilling into more detail Screenshot of Web Admin interface to be added here. 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.

This transaction is also not intended to perform statistical analysis on the information Examples: The average write-back time experienced The number of reads per day For this type of analysis. the data must be extracted into a SAP NetWeaver BI cube © 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.

Using Transaction UJSTAT (1) When you run transaction UJSTAT. Select by: Statistics GUID value It is not expected that the GUID would always be known BPC User Start Date Start Time Action being performed AppSet Application © SAP 2008 / Page 8 . you are asked to apply some filters to select the Statistics records you wish to display.

© SAP 2008 / Page 9 .Using Transaction UJSTAT (2) After you have applied your filters and executed. you will see the statistics records matching your criteria.

© SAP 2008 / Page 10 . In this case. 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. taking 1.400955 seconds. the total runtime of this request was 1.367427 seconds. The longest running event was the “RSDRI_INFOPROV_READ”.Using Transaction UJSTAT (3) Expanded record (parent.

Using Transaction UJSTAT (4) Runtime Total Runtime Cumulative Runtime Nr of Recs © SAP 2008 / Page 11 .

where you can see events 4 and 5 are children of event 3. Nested events show the dependency/sequencing of nested calls.Using Transaction UJSTAT (5) This example also shows nested events. For example. it will likely call both SQE and Write-Back (and potentially other modules. Nested events occur when one module calls another module. © SAP 2008 / Page 12 . such as Parameter Driven Logic). in a K2 script.

Using Transaction UJSTAT (6) 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 13 .

when the SQE executes an MDX statement). the MDX statement executed). The “NWBI Statistics UUID” is used when a SAP Business Planning and Consolidation event calls a NetWeaver BI function (e. © SAP 2008 / Page 14 . The Supporting Detail field can contain additional text (for example.g.Using Transaction UJSTAT (7) You can also double click on an individual event to bring up additional details on the record.

not stored in the underlying tables. © SAP 2008 / Page 15 . PARENT_EVENT_ID and ACTUAL_CALLER fields). The hierarchical relationship of events you see in transaction UJSTAT is built at runtime. to get the complete runtime for the request. using the EVENT_ID.Example Records If extracting data from the detail table. It must be determined programmatically (and is quite complicated. There are no overlapping requests with parent/child events. it is important to note that: The Runtime column can be summed for all events.

For now. the only options to delete statistics records are to delete all records for a given AppSet and/or Application. 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). once written to the statistics tables. will not be deleted. © SAP 2008 / Page 16 .Deleting Records Records.

© SAP 2008 / Page 17 .Use of Statistics Within SAP Business Planning and Consolidation This framework as of today. 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. has only been implemented for: Shared Query Engine Write-Back K2 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.

Statistics will only record the ABAP portion of the total runtime. Write-Back and K2 at this stage. © SAP 2008 / Page 18 . Events can be nested. The framework has only been implemented by SQE. Transaction UJSTAT can be used to analyze performance. By default.Statistics Summary Statistics can be used to analyze the performance of individual requests. no statistics records will be recorded. based on the dynamic sequence of calls made at runtime (both inter and intra module).

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. Delete old statistic records. © SAP 2008 / Page 19 . Turn the statistics on and off. Use the BPC Performance Statistics report and analyze the output (Transaction UJSTAT).

version for SAP NetWeaver Installation Understanding the UJ Package with SAP Business Planning and Consolidation .SAP Business Planning and Consolidation 7.0.

you will be able to: Understand the high level package concept Learn how to navigate SAP Business Planning and Consolidation package ‘UJ‘ © SAP 2008 / Page 2 .Understanding the UJ Package: Lesson Objectives After completing this lesson.

will help technical users (programmers and technical administrators) to further understand SAP Business Planning and Consolidation system functionality The 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. including: Understanding the UJ package. programmatic perspective © SAP 2008 / Page 3 . that comes with SAP Business Planning and Consolidation.Benefits of SAP Business Planning and Consolidation UJ Package There are several benefits related to learning this topic.

You can view a package. SAP Business Planning and Consolidation Objects can be found in the ‘UJ’ package. © SAP 2008 / Page 4 . so that different products can follow different release cycles.Function Packages are designed to help developers modularize. encapsulate. plus all its elements in transaction SE80. The emphasis is on technically decoupling resources from the Core SAP System. That is. and decouple units in the SAP System. Just choose the entry Package in the object list of the Repository Browser. Then all the objects of that package are displayed. a package is like a folder in a way. They are a further development of the concept of the development class used today and contain additional semantics. enter the name of the relevant package in the input field below and press "Enter". Packages organize development objects and handle their connection to the AS ABAP software. Every development object must belong to a package.

Function Groups Message Class Transactions Others © SAP 2008 / Page 5 . Programs. (As with the entire BI backend) The following objects can be found browsing the UJ Package Data Dictionary Objects Class Library.UJ Package Overview Use transaction code SE80 to view UJ Package Looking at the UJ Package in SE80 This information is only meant for technical users in the system Business users would not need to look at or understand this concept.

The example to the right shows tables related to the SAP Business Planning and Consolidation security concept. © 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.

Understanding the UJ Package: Lesson Summary You should now be able to: Understand the high level package concept Learn how to navigate SAP Business Planning and Consolidation package ‘UJ‘ © SAP 2008 / Page 7 .

0. version for SAP NetWeaver Installation Service Accounts .SAP Business Planning and Consolidation 7.

x and SAP Business Planning and Consolidation.NET account information after installation © 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. version for SAP NetWeaver Service Accounts Describe the purpose of Service Accounts Know the different Roles available for Service Accounts Configure accounts with the appropriate Roles during installation Update the BPC.

including: Understanding how security is implemented in SAP Business Planning and Consolidation Proper functioning of SAP Business Planning and Consolidation Successful installation and configuration of SAP Business Planning and Consolidation © SAP 2008 / Page 3 .Benefits of Understanding Service Accounts There are several benefits related to learning this topic.

NET Tier to communicate with the ABAP Application Server Tier successfully © 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 backend ABAP users must be assigned the appropriate Role(s) during installation to allow the .

Preliminary Steps

Install SAP NetWeaver 7.0 SPS16 Install SAP NetWeaver 7.0 EHp1 Install the BPC Add-on Create 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 5

How to Configure Service Accounts

Configuring Service Accounts
Log into SAPGUI as the BPC Admin Dialog user you created (see Preliminary Steps) Perform this step during installation after completing the Preliminary Steps General 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 6

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 7

How to Configure Service Accounts on the .NET Tier
Configuring Service Accounts on the .NET Tier
Run SAP Business Planning and Consolidation Server Manager on each .NET application server Perform this step after a change (i.e. password change) to any service account General Steps: Select Server -> Reset Credentials

Make the appropriate modifications to the service account(s)

© SAP 2008 / Page 8

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 9 .

NET account information after installation © SAP 2008 / Page 10 . version for SAP NetWeaver Service Accounts Describe the purpose of Service Accounts Know the different Roles available for Service Accounts Configure accounts with the appropriate Roles during installation Update the BPC.x and SAP Business Planning and Consolidation.Service Users: Lesson Summary You should now be able to: Understand the difference between SAP Business Planning and Consolidation 5.

version for SAP NetWeaver Installation Connectivity .0.SAP Business Planning and Consolidation 7.

you will be able to: Understand and explain the basic concepts of connectivity Understand the different types of users involved in the internal interfaces Get started with troubleshooting issues related to connectivity © SAP 2008 / Page 2 .Connectivity: Lesson Objectives After completing this lesson.

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 Consolidation Possessing 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 3 .

Context: Server Manager Overview Server Manager © SAP 2008 / Page 4 .

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

you can open up file: <BPC Server>\Server Management\OsoftDiagnostic. © SAP 2008 / Page 6 . This file can be viewed on the .NET server file system.txt. To view the diagnostics log in a text editor.Server Manager: Server Diagnostics Server Diagnostics help troubleshoot common connection problems.

Connectivity SAP Business Planning and Consolidation Service Users are used. The 3 User IDs are: System Administrator – used by the server manager to connect to SAP NetWeaver Administrator – 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 7 . to connect to SAP NetWeaver.

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 8 .

© SAP 2008 / Page 9 . The XML version is displayed. but is planned for Support pack 1.Server Manager: Client Options Client AutoUpdate functionality is out of scope in Support pack 0. 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. but it is recommended not to change this value.

Server Manager: Server Options © SAP 2008 / Page 10 .

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). Administrator – Must be assigned the “SAP_BPC_ADMIN” role. System Administrator – Must be assigned the “SAP_BPC_SYSADMIN” role. © SAP 2008 / Page 11 . UserID – Must be assigned the “SAP_BPC_USER” role.

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. select Options > Define system user groups. (This value is for future use). Add the specific User IDs to a particular group and then configure. To limit Business Planning and Consolidation access: From Server Manager. In the System user group name field. © SAP 2008 / Page 12 . In the Group description field. so that only the users in that group can access SAP Business Planning and Consolidation. enter a meaningful description for the user group. This name will be displayed in the Add Users assistant in the Admin Console. enter a unique name for this group.

(These are the only domain types supported at this time). In the Domain Name field. This must be a domain already set up by a system administrator. In the User group filter field. Here are some examples: © SAP 2008 / Page 13 . select Active Directory or Local Windows. enter a local computer name. For a local user. enter (or modify) a filter that gets user names from the specified domain and server.Limiting Access with System User Groups – 2 From the Domain type field. enter (or modify) the name of the fully qualified domain name.

System User Groups: Considerations It is very important to note that you should create a system user group for your Active Directory tree. It is possible to use multiple domains. this will typically time out. Therefore. It is also recommended that all SAP Business Planning and Consolidation users reside within a single domain. 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 14 . This is a requirement of the Active Directory "tree”: – If you try to select a user from the entire Active Directory. you need this to limit where SAP Business Planning and Consolidation searches in the Active Directory for potential SAP Business Planning and Consolidation users.

Connectivity: Lesson Summary You should now be able to: Understand and explain the basic concepts of connectivity Understand the different types of users involved in the internal interfaces Get started with troubleshooting issues related to connectivity © SAP 2008 / Page 15 .

0.SAP Business Planning and Consolidation 7. version for SAP NetWeaver Installation Debugging .

Debugging: Lesson Objectives After completing this lesson. you will be able to: Explain the process for debugging debug code within the ABAP tier Describe general configuration points to configure an Active Directory use to use SAP Business Planning and Consolidation for debugging Describe the steps for setting the breakpoint List exceptions to debugging code within the ABAP tier © SAP 2008 / Page 2 .

Benefits of Debugging There are several benefits related to learning this topic. including: Ensuring a more stable system Enabling more expedient problem resolution © SAP 2008 / Page 3 .

Function of Debugging SAP Business Planning and Consolidation Debugging provides: More expedient problem resolution A way of enabling users to actively debug API’s in the ABAP tier © SAP 2008 / Page 4 .

© 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 arise Use new debugging technology within SAP Business Planning and Consolidation.

How to Debug the ABAP Tier Level 1 Debugging When you need to Debug the ABAP system Ensure that a Debug user has been configured for your Active Directory account General Steps in Task Set a breakpoint in your API Run a process that executes the API you want to debug © SAP 2008 / Page 6 .

Configure the . Debug User ID and Debug Password.NET Tier Debugging To configure an Active Directory user to use SAP Business Planning and Consolidation Debugging: Log into the . © SAP 2008 / Page 7 .NET Application Server and launch Server Manager. Click Update. Select Server -> Maintain Debug Users Enter your BPC User ID.

Set Breakpoint (1 of 2) © SAP 2008 / Page 8 .

Set Breakpoint (2 of 2) © SAP 2008 / Page 9 .

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 . RAISE IOBJ_NOT_FOUND).g. 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 ABAP For all SAP Business Planning and Consolidation APIs. SAP Business Planning and Consolidation does not use classic exception (e. sy-msg is set if there is an error in function module Business Planning and Consolidation has a central class to log errors: – CL_UJ_UTL_MESSAGE=>SET_SY_MSG. © SAP 2008 / Page 10 .NET TIER As a result.

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 tier Describe general configuration points to configure an Active Directory use to use SAP Business Planning and Consolidation for debugging Describe the steps for setting the breakpoint List exceptions to debugging code within the ABAP tier © SAP 2008 / Page 11 .

version for SAP NetWeaver Installation Installation .0.SAP Business Planning and Consolidation 7.

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 2

Benefits of Installation

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

© SAP 2008 / Page 3

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 Technology Associate/Professional Platform Technology SAP NetWeaver 7.0
© SAP 2008 / Page 4

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/instguidescpmbpc > Release 7.0 NW Product Availability Matrix: http://service.sap.com/pam

© SAP 2008 / Page 5

0 Installation – including Database. Web Server (IIS) & .Architecture SAP Business Planning and Consolidation: Installation View Perform normal SAP NetWeaver BI 7. application server(s) Perform installation of Web Server (IIS) & .NET Application server components run on a 32-bit Windows server © SAP 2008 / Page 6 .NET Application server components Perform installation of Frontend client tools Important Note: SAP NetWeaver typically runs on a 64-bit server.

as well as a Client installation.NET Server. a SAP Business Planning and Consolidation Add-on.0 system (that meets minimum prerequisites) OR On a completely new NetWeaver BI 7. © SAP 2008 / Page 7 .0 system. 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.SAP Business Planning and Consolidation: Installation Scenarios The SAP Business Planning and Consolidation Installation has a standalone .

6.Basic Server Installation Sequence Basic steps for the server installation 1. Install BPC . Configure the BPC . 5.NET server. 3. 2. version for SAP NetWeaver. 8. 7. Verify/upgrade/install SAP Business Planning and Consolidation. Acquire installation media. Acquire (or verify) hardware. 4. Perform post-installation steps for SAP Business Planning and Consolidation ABAP. © SAP 2008 / Page 8 . Verify and install prerequisites. Install SAP Business Planning and Consolidation ABAP Add-on.NET server.

2. © SAP 2008 / Page 9 .Basic Client Installation Sequence Basic steps for the client installation 1. Uninstall any previously installed version of SAP Business Planning and Consolidation clients. 3. Install new SAP Business Planning and Consolidation clients (Admin or Office). Verify and install client prerequisites.

Server Installation Prerequisites Chart © SAP 2008 / Page 10 .

0 SP 7 MSXML 4.NET 2. ** Must be installed prior to running the installation – available on SAP SWDC.0 (or above) Office 2003 or Office 2007 Visual Basic 6 & Visual C++ Runtimes* MSXML 3. © SAP 2008 / Page 11 .Client Installation Prerequisites Microsoft Windows XP Internet Explorer 6.NET 1.1 .0 SP 2 .0 Xceed Zip** * 3rd party components installed during SAP Business Planning and Consolidation installation.

.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 12

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 13

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 14

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 15

sap.com/saphelp_nw70/helpdata/en/45/b517e0ed2f52f5e10000000a1553f 7/content. create the ALEREMOTE user and assign it to the roles S_BIWHM_RFC and S_BI-WX_RFC. (If SAP NetWeaver has been configured appropriately.sap. and BPC_USER) and assign them to the provided SAP Business Planning and Consolidation roles. then assign the BW client.Configure SAP Business Planning and Consolidation ABAP (2) Using transaction PFCG. see the information at help.htm © SAP 2008 / Page 16 . BPC_SYSADMIN.com http://help. For more information. If not already created. These roles allow the user to load data from an external system. set up transports by creating the RFC destination for the After Import method.) Using the transaction RSTPRFC. this user is already defined. create the three SAP Business Planning and Consolidation users (BPC_ADMIN. Save the password.

© SAP 2008 / Page 17 . Using transaction SE38. default BI objects) to the BPC_SYSADMIN user.e.Configure SAP Business Planning and Consolidation ABAP (3) Assign authorization to activate business content (i. We recommend that you also assign the SAP_ALL role during the installation process of ApShell. run program UJA3_WRITE_SYS_USERS and assign the three service users (BPC_ADMIN. Assign role S_RS_ALL to the BPC_SYSADMIN user. BPC_SYSADMIN. You can remove the SAP_ALL role after the installation of ApShell. BPC_USER).

then click Maintain. Development © SAP 2008 / Page 18 . select one of the available entries. click the Save pushbutton. Repeat step 10d for each available item in the table.Configure SAP Business Planning and Consolidation ABAP (4) Create entries in the SAP Business Planning and Consolidation Transports table by doing the following: Go to transaction SM30. Choose New Entries. Enter the table name UJT_TRANS_CHG. then select in the adjacent column. From the TLogo Object column. After all entries have been added.

which runs the several post-installation steps. set the AppSet ID as ApShell and the Content Version as 1. b) Check the logs by selecting System Own Jobs. © SAP 2008 / Page 19 .Configure SAP Business Planning and Consolidation ABAP (5) To install ApShell. It is important that you run this program run twice. c) Select the job and display the Spool. The first time. Then take the following steps: a) Select Program Execute in background. Once this is complete. In the Content Activation window. choose all options except for the Load Data Into AppSet option. run this program again and choose only the Load Data Into AppSet option. run the program UJS_ACTIVATE_CONTENT.

specify a Windows domain user that you want to have initial access to APSHELL. BPC_SYSADMIN. run the UJA3_WRITE_SYS_USERS program again (transaction SE38). For the SYSADMIN user. and assign the three service users (BPC_ADMIN. © SAP 2008 / Page 20 . the system does not check task security for this user. Using the transaction SM59. BPC_USER). since this user is used to initially logon to ApShell.Configure SAP Business Planning and Consolidation ABAP (6) If you selected the Update Default Users option during the ApShell installation. When you specify a domain user in this field. run a connection test on the RFC destination MDX_PARSER.

microsoft.com/kb/894435 © SAP 2008 / Page 21 .NET / Web App Server Install BPC .NET Server Use Install shield Update IIS Properties Web Service Extensions Authentication Update Web.Install and Configure on .config with the port of IIS appserver URL Set IIS to run in 32 bit mode as outlined in this KB article: – http://support.

1 and Microsoft .com/en-us/library/kh3965hw(VS.NET Framework 2.0 are installed.80). © SAP 2008 / Page 22 . Ensure IE 6.aspx.microsoft. please install the Microsoft Interoperability Libraries: http://msdn. Ensure MSXML 3.Client Installation (1 of 3) Ensure Microsoft Office 2003 or Microsoft Office 2007 is installed NOTE: If full version was not installed. Ensure Microsoft .0SP2 are installed.NET Framework 1.0SP1 and MSXML 4.0 or above is installed.

click the Client Software Center and install SAP Business Planning and Consolidation on the client. © SAP 2008 / Page 23 .Client Installation (2 of 3) From the Launch Page.

go to the Software Center page. © SAP 2008 / Page 24 . click the option to initiate the installation on the client.Client Installation (3 of 3) To install BPC for Office or BPC Administration.

© 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.

0. version for SAP NetWeaver Technical Solution Changes Optimization .SAP Business Planning and Consolidation 7.

Full © SAP 2008 / Page 2 .Optimization: Lesson Objectives After completing this lesson. you will be able to: Understand the new optimization features Understand what happens during optimization efforts Know the difference between Lite and Full optimzations Decide when to use Lite vs.

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 performance Being able to use the optimization options to achieve SAP Business Planning and Consolidation performance objectives Determining the best time to use the optimization options so that system performance is not affected when resource demands are high © SAP 2008 / Page 3 .

Generally speaking. The concept has not changed from SAP Business Planning and Consolidation 5. In this presentation we will review a similar process.X to SAP SAP Business Planning and Consolidation. version for SAP NetWeaver.X data was stored in the ‘writeback’ table then moved into a more optimal storage location. However the execution of this concept is quite different.Function Optimization is a process for storing data in the best fashion for performance. This process is executed based on the specific customer situations. © SAP 2008 / Page 4 . In SAP Business Planning and Consolidation 5. the frequency and quantity of data created is directly related to the optimization frequency.

This will be discussed further in the Technical details section. Optimize will run a number of technical steps on the NetWeaver BI InfoCube in an attempt to improve performance. If the data model can be improved. it is recommended to run Optimize periodically. compress and index the cube. There is no rule for how often to run optimizations. and this could take a long time to run (for cubes with large data volumes). Full Optimize will do so. but will also check the NetWeaver BI data model. typically.Application Optimization Overview When new application sets and applications are created. There are two different types of optimizations available: Light Optimize: will close the open request. Full Optimize: will perform the same operations as Light Optimize. but as data volumes increase. there will not be a lot of data available. and update database statistics for the BI Cube. © SAP 2008 / Page 5 .

Please return. © SAP 2008 / Page 6 .Application Optimization Overview – Place Holder Slide Information is to Be Added in the Future Thank you for your patience.

Optimization: Lesson Summary You should now be able to: Understand the new optimization features Understand what happens during optimization efforts Know the difference between Lite and Full optimzations Decide when to use Lite vs. Full © SAP 2008 / Page 7 .

Sign up to vote on this title
UsefulNot useful