SAPTechno

Note 1612314 - Planning and Consolidation 7.5M SP06 Central Note

Header
Version / Date 3 / 2011-08-16
Priority Recommendations/additional info
Category Installation information
Primary Component EPM-BPC-MS Microsoft Version
Secondary Components

Summary
Symptom

Central Note: SAP BusinessObjects Planning and Consolidation 7.5 SP06, version for the Microsoft platform

Other terms

Planning and Consolidation 7.5M SP06, resolved issues, installation instructions, upgrade instructions, central note

Reason and Prerequisites

SAP BusinessObjects Planning and Consolidation 7.5 SP06, version for the Microsoft platform (Planning and Consolidation 7.5 SP06 for Microsoft) is available as a full installation for new customers as well as an upgrade to existing installations (depending on previous version and system landscape considerations).

Install .Net Framework 2.0 SP1 if running Windows XP + Excel 2003.

Solution

This note contains essential information about the implementation of Planning and Consolidation 7.5 SP06.

Before proceeding with the installation, read the Related Notes.

What's New
  • Export/Import Data between CTS+ and BPC. See SAP Note 1582525.
  • Amyuni PDF Converter version 4.5 package is included from SP6 and it is now support 64bit environment. See SAP Note 1613756.
  • Supports an Excel template file as a default start page in Planning and Consolidation for Excel. See SAP Note 1590770.


Download and Installation Instructions

To download and install Planning and Consolidation 7.5 SP06, perform the following steps:

    1. Go to the Service Marketplace Software Distribution Center at http://service.sap.com/swdc and follow this path:

              Software Downloads > Support Packages and Patches > Support Packages and Patches : A - Z Index > B > SAP BPC FOR MICROSOFT > SBOP PC 7.5 FOR MICROSOFT > Comprised Software Component Versions > SAP CPM BPC 7.5 M > #OS independent.

    2. Select the ZIP file for Planning and Consolidation 7.5 SP06 and download it.
    3. Uncompress the ZIP file on the Planning and Consolidation Application Server.
    4. Locate the Planning and Consolidation Setup folder on the Application Server.
    5. From the Consolidation and Planning Setup folder, run Setup.exe.
    6. Click the Upgrade link and follow the instructions.

Installation-related Information

You need to provide the System Admin ID, Admin ID, User ID, and corresponding passwords that you set during the initial setup of the system.

If a previous version of the Planning and Consolidation Office or Administration client has been installed on client machines, you can automatically upgrade them by turning on the Client Auto Update option in Server Manager.

Migration of Applications and Application Sets from version 7.5 M

Prerequisites

If all previous support packages of Planning and Consolidation 7.5 and the ODBO client have been installed, perform the following operations:

  • Uninstall the previous support package version of the ODBO client.
  • Install the ODBO client SP06.


During the upgrade process, the new ApShell overwrites the previous version of ApShell without deleting it. If you want to keep and refer to the previous version of ApShell, back it up before upgrading to 7.5, and then restore it with a different name after upgrading. If you want to use the pure version of ApShell in 7.5, rename the existing ApShell WebFolder and FileDB directories before upgrading. See SAP Note 1382866.

The upgrade program prompts you for a newer version of AntiXssLibrary.dll than earlier versions of Planning and Consolidation used. Download the following versions of these files:

  • AntiXssLibrary.dll version 3.0


For more information about how to download these files, see the installation guide.

Procedure

The Windows AD authentication type of SAP BusinessObjects Enterprise does not allow you to use a user account that contains Unicode (non-ASCII) characters, as the relevant Java Kerberos library does not support Unicode compatibility. If you want to use the account in Planning and Consolidation, modify the account name in the Central Management Console before assigning the user to Planning and Consolidation. See SAP Note 1383674.

Planning and Consolidation does not allow you to use the characters  \ / : * ? " < > | ; , in an account name (User ID) in CMS authentication mode because the Microsoft Windows file system does not support those characters for file names and folder names.
           NOTE: If an account name contains those characters, the account name should be modified in CMS console in advance by an administrator before assigning users to Planning and Consolidation.


To complete the migration, perform the following operations, as necessary:

  • In the Administration Console, choose Modify Application without check options. This applies several fixes related to Stored Procedure.
  • Copy AuditClear.dts and AuditRestore.dts from the previous version of ApShell to your application sets after installing Planning and Consolidation 7.5. See SAP Notes 1355574 and 1357279.

           Copy from: \\<FileServer>\.. \WebFolders\ApShell\Finance\DataManager\ PackageFiles\Examples

           Copy to: \\<FileServer>\..\WebFolders\<ApplicationSet>\<Application>\ DataManager\PackageFiles\Examples

  • If you have an SQL Server 2005 environment, you should copy 'Copy from fact table.dtsx' from ApShell to your application sets. See SAP Note 1377518.

           Copy from: \\<FileServer>\.. \WebFolders\ApShell\Finance\DataManager\ PackageFiles\Examples

           Copy to: \\<FileServer>\..\WebFolders\<ApplicationSet>\<Application>\ DataManager\PackageFiles\Examples

  • Planning and Consolidation 7.5 has new tasks. To apply the new tasks, go to the Admin console and run Modify Task Profile without any changes to the existing task profile (reprocess), or create new task profiles for each task and assign appropriate users. See SAP Note 1382583.

           If you choose to reprocess existing task profiles:

    • If the task profile type is System Admin, the OfflineAccess and ManageDrillThrough tasks are applied.
    • If the task profile type is Primary Admin, the RemoveBPFInstances, ResetBPFInstances, ManageDrillThrough and ManageEVDREDefaultStyle tasks are applied.
    • If the task profile type is Secondary Admin, the EndUserDrillThrough task is applied.
    • The administrator must add the ReOpenBPFStep and PackageExecute tasks to the appropriate task profile.
  • The ApShell in 7.5 includes the Import SQL and Import SQL into Fact packages that prompt you to enter the SQL database. (In versions 5.1 and 7.0, the prompt was missing.)

           To apply the packages, copy the packages from ApShell to your application after upgrading to 7.5. Then, modify the package script for your application dimensions. See SAP Note 1355877.

           Copy from:  <FileServer> \WebFolders\ApShell\Planning\DataManager\ PackageFiles\Examples

           Copy to: <FileServer>\WebFolders\<AppSet>\< App>\DataManager\PackageFiles\ Examples

  • In Planning and Consolidation 7.5, dynamic reports and schedules are provided in EvDRE format. They work in any application. To use new dynamic reports and schedules templates, copy the changed templates from the following location:

           \\<FileServer>\.. \WebFolders\ApShell\Planning\eExcel\Input Schedules (and Reports)\Wizard

           For more ApShell information, see SAP Note 1349656.

  • In case of restore Application Set after BPC 7.5M has been upgraded to this version, you must recreate the partition if an application has a custom OLAP partition. See SAP Note 1395795.


For information on migration steps to apply to support packages before SP02, see the Planning and Consolidation 7.5 M Upgrade Guide, available on SAP Service Marketplace at http://service.sap.com/instguidesEPM-BPC > 7.5, version for the Microsoft platform.


Limitations
  • A dimension member ID cannot be the same name as a dimension name in an EvDRE function. See SAP note 1566755.
  • If UAC mode is turned on in Windows Vista, Windows 7, and Windows 2008, the 'Back to BPF' menus in BPC Excel, BPC Word, and BPC PowerPoint are not displayed. See SAP note 1501591.
  • After a user tries to launch BPC for Word through BPC for Web, they cannot see the Log On button in BPC for Word if Enable Protected Mode in Internet Explorer Options is turned on. See SAP note 1499865.
  • SAP BusinessObjects Planning and Consolidation does not support using client certificates, ""clientAuth= true"", in the SAP BusinessObjects Enterprise web service. A true value requires all SSL clients to present a client certificate in order to use this socket.

           A false value (which is the default) does not require a certificate chain unless the client requests a resource protected by a security constraint that uses CLIENT-CERT authentication.

           Technical information about the clientAuth option:

                    Set this value to 'true' if you want Tomcat to require all SSL clients to present a client certificate in order to use this socket. If 'true', Tomcat requests a client certificate, but does not fail if one is not presented. A 'false' value (which is the default) does not require a certificate chain unless the client requests a resource protected by a security constraint that uses CLIENT-CERT authentication.

                    For more information, see http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html.

  • As SAP BusinessObjects Planning and Consolidation supports SAP CMS authentication, this requires a component named POAFHelper for communication between the SAP BusinessObjects Planning and Consolidation application and SAP CMS. The POAFHelper refers to the common SAP BusinessObjects Enterprise web service client files (see below), which can be shared with other SAP BusinessObjects Enterprise programs and SAP CMS:
    • BusinessObjects.DSWS.dll
    • BusinessObjects.DSWS.BIPlatform.dll
    • BusinessObjects.DSWS.Session.dll

           Register the POAFHelper files manually. We recommend that you do not install the following SAP BusinessObjects Enterprise programs and components with the SAP BusinessObjects Planning and Consolidation server program:

    • SAP BusinessObjects Live Office
    • SAP BusinessObjects BI Widgets
    • Query as a Web Service
    • .NET URE

           If you want to register the files manually, copy the files to #%WINDOWS%\assembly#. You can find these files at #%PC_MS%\Websrvr\bin#.

  • If the length of a user account name exceeds 20 characters, unexpected problems can occur while accessing the file system with a long application set name and application name.
  • In script logic, if there are more than 3,025 characters in a line, the color coding may not be applied correctly because the "Rich Textbox' control has a limitation in the number of characters allowed. See SAP Note 1382497.
  • Script logic does not support a decimal point except "." (dot), which is a standard decimal symbol in English-speaking regions.
  • In Excel 2003, when the EVDRE template has multiple Row/ColKeyRange and its string length is over 255 characters, errors occur. Therefore, make the worksheet name shorter than the current worksheet name to adjust the length of the Row/ColKeyRange. See SAP Note 1382510.
  • When processing a Data Manager package with default logic or a Default Formula package, Time dimension members are now processed in chronological order rather than alphabetical order. See SAP Note 1311586.

           In the following cases, however, time dimension members are still sorted alphabetically:

    • Time type dimension is a secured dimension
    • When the following instruction is defined in default logic:

                     -  **SELECTION

                     -  iSimulation parameter value is less than 2

  • EV functions containing a year argument rather than period and year argument now correctly include all periods within the specified year. Previously, the system included only the first period of the specified year. To use the EV functions, we do not recommend using period value as a member of a dimension. For example, if the Time dimension has the 2000.Jan member, do not use Jan as a member name of any of the dimensions. See SAP Note 1330658.
  • Parallel task execution in one Data Manager package is supported, but there is a limitation to use the parallel tasks execution. See SAP Note 1311552.
    • Parallel task execution with Container is not supported.
    • Package result status in Data Manager shows the result of the last execution when two tasks in parallel are defined as final points. So users need to query task results in the package log table to know the results of both tasks.
  • In the account transformation business rule, if two rules that have different source DataSrc, for example, INPUT and MJ_RECLAS have different destination Flow members and same destination DataSrc member, and XDIM_MEMBERSET is defined to perform only for MJ_RECLAS, then the existing data of the destination flow whose source DataSrc is not defined to perform by XDIM_MEMBERS are zeroed out. See SAP Note 1338483.
  • Only report and input schedule templates with an XLT extension are supported, since these templates are hardcoded internally, such as Template1.XLT. A template with an XLTX extension cannot be opened through the Report Wizard or Input Schedule Wizard even though the template is saved under the path eExcel\Reports\Wizard or eExcel\Input Schedules\Wizard. See SAP Note 1288848.
  • If the third party component Xceedzip.dll is used by another program such as SnagIt, and the other program is installed on the Application server, there may be version or license issues regarding the file service. We recommend that you register the DLL manually to prevent the problem. See SAP Note 1281762.

           To register Xceedzip.dll manually, do the following:

    • Check that the file version is 6.5.9417.0, then go to Start\Run and execute the command [regsvr32\PC_MS\Websrvr\bin\Xceedzip.dll].
    • Shut down OSoftFileManage by doing the following:

                    1. Go to Start\Programs\Administrative Tools\Component Services on the Application server.

                    2. Expand the Component Services tree (if running Windows 2000) or COM+ application tree (if running Windows 2003).

                    3. Right-click on OSoftFileManage and choose Shut down.

  • If *SCOPE_BY and REC instructions are used together in logic and the logic is run by a Data Manager package, do not use double quotation marks to enclose the members defined in the REC instruction. See SAP Note 1284962.
  • If a large query is created in the scope range while processing script logic, an overflow error may occur. We recommend using XDIM_MAXMEMBERS to split the scope to prevent this error. See SAP Note 1268115.
  • Currently, Planning and Consolidation returns non-zero, small numbers from OLAP. The aggregated data by OLAP does not return zero value such as 0.0000000001 even though users intend the data to be zero. This affects functionality when pointing to zero values, validating data entry via work status, and clearing zero data. See SAP Note 1268768.
  • The "CategoryByTime" option of Data Manager transformations currently supports only a single-hierarchy time dimension. So, in a multiple time hierarchy, it is not working as expected. See SAP note 1302358.
  • When work status is changed with the 'include children' option, the owners of the children members cannot receive e-mail even if the APPROVALSTATUSMAIL AppSet parameter is set. See SAP note 1373600.

Resolved Issues

See the related notes listed below for information about the issues resolved in this support package.

Affected Releases
Software Component Release From Release To Release And subsequent
CPM_BPC757575

Related Notes
1618485Scheduled publish book is not working
1618483BPC for Excel download templates in non-english
1617008Park N Go and 'No connectivity'
1614143Error when processing large dimension
1614111Problem with dimension name size of more than 16 characters
1614110EVDRE expands across sheets in the wrong order
1614109Dimension property lowercase name displays in print sheet
1613829Security problem with the task profile SetWorkStatus
1613828Offline Distribution Wizard - Type Mismatch error
1613827BPC can add domain-user in a specific AD environment