SAP BUSINESSOBJECTS FINANCIAL CONSOLIDATION 7.

5 STARTER KIT FOR US GAAP SP1

Installation Guide

Copyright

2009 SAP BusinessObjects. All rights reserved. SAP BusinessObjects and its logos,

BusinessObjects, Crystal Reports, SAP BusinessObjects Rapid Mart, SAP BusinessObjects Data Insight, SAP BusinessObjects Desktop Intelligence, SAP BusinessObjects Rapid Marts, SAP BusinessObjects Watchlist Security, SAP BusinessObjects Web Intelligence, and Xcelsius are trademarks or registered trademarks of Business Objects, an SAP company and/or affiliated companies in the United States and/or other countries. SAP is a registered trademark of SAP AG in Germany and/or other countries. All other names mentioned herein may be trademarks of their respective owners.

2010-04-28

LEGAL DISCLAIMER No part of this starter kit 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. The information in this starter kit is proprietary to SAP. No part of this starter kits content may be reproduced, copied, or transmitted in any form or for any purpose without the express prior permission of SAP AG. This starter kit is not subject to your license agreement or any other agreement with SAP. This starter kit contains only intended content, and pre-customized elements of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this starter kit is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this starter kit. SAP does not warrant the accuracy or completeness of the information, text, pre-configured elements, or other items contained within this starter kit. SAP DOES NOT PROVIDE LEGAL, FINANCIAL OR ACCOUNTING ADVISE OR SERVICES. SAP WILL NOT BE RESPONSIBLE FOR ANY NONCOMPLIANCE OR ADVERSE RESULTS AS A RESULT OF YOUR USE OR RELIANCE ON THE STARTER KIT. THIS STARTER KIT 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 THIS STARTER KIT. THIS LIMITATION SHALL NOT APPLY IN CASES OF INTENT OR GROSS NEGLIGENCE. The statutory liability for personal injury and defective products (under German law) is not affected. SAP has no control over the use of pre-customized elements contained in this starter kit and does not endorse your use of the starter kit nor provide any warranty whatsoever relating to third-party use of the starter kit.

Contents
Chapter 1 Chapter 2 Chapter 3 Contents .................................................................................................................................. 3 Objectives ................................................................................................................................ 5 Requirements .......................................................................................................................... 5 SAP BusinessObjects Financial Consolidation requirements .................................................. 5 Database server requirements ................................................................................................. 5 Requirements FAQ ................................................................................................................... 5 Installing the Starter Kit ................................................................................................................................... 8 Configuring SAP BusinessObjects Financial Consolidation ..................................................... 8 Receiving the configuration .................................................................................................... 11 Changing the site to a TOP site .............................................................................................. 13 Appendix 1: Query MSSQL database ........................................................................................................... 15 Appendix 2: Query Oracle database ............................................................................................................. 17

Contents

Objectives

Objectives
This document explains: The technical requirements to perform the starter kit setup; How to install this configuration by transfer.

Requirements
This first section describes requirements allowing the setup of the starter kit.

SAP BusinessObjects Financial Consolidation requirements

The version of SAP BusinessObjects Financial Consolidation must be 7.5 SP7 or higher to use the starter kit.

Database server requirements

The configuration can be installed on a MSSQL or Oracle database engine supported by SAP BusinessObjects Financial Consolidation (see SAP BusinessObjects Financial Consolidation Installation guide). The database has to be a child and initialized database (see BusinessObjects Financial Consolidation Installation guide).

Requirements FAQ
What is the version of SAP BusinessObjects Financial Consolidation installed ? In the installation directory, select Finance.exe, select the File / Property Version tab. Is the database initialized ?

Launch CtAdmin.msc from the installation directory of the application server; Under the root node Business Objects Administration (local), expand the node of the data source corresponding to the database; Right-click on the Operation node, and select All tasks / Start Data Source from the popup menu as shown in the screenshot below.

Requirements

If no error message shows up, the database schema was already created and the data source is started. However, if the following error message appears, the database schema was not created or not up to date with the version of the software. In this case, the database must be migrated before trying to start the data source.

How to migrate a database ? Launch CtAdmin.msc from the installation directory of the application server; Under the root node Business Objects Administration (local), expand the node of the data source corresponding to the database; Right-click on the Operation node, and select All tasks / Migrate from the popup menu as shown in the screenshot below.

Requirements

Once the migration is completed, a window shows the migration report indicating success or failure.

Is the data base a child one ? In SAP BusinessObjects Financial Consolidation, click on the Tools / General Options Transfer tab. If no information is available, then this is a child database, which has never received any object.

The database will take values of the recipient of objects received at the first execution of the scan task.

Requirements

Installing the Starter Kit

Configuring SAP BusinessObjects Financial Consolidation
STARTING THE DATA SOURCE IN EXCLUSIVE MODE 1. Launch CtAdmin.msc from the installation directory of the application server; 2. Under the root node Business Objects Administration (local), expand the node of the data source corresponding to the database; 3. Right-click on the Operation node, and select All tasks / Start Data Source in Exclusive Mode from the popup menu as shown in the screenshot below.

SETUP THE TRANSFER VECTORS 4. In SAP BusinessObjects Financial Consolidation, click on the Tools / General Options Transfer tab;

Requirements

5. Select Network then Configure from the section Transfer Vectors;

6. Select the directory where objects will be received, for example C:\Install;

Requirements

CREATE THE SCAN TASK 7. In the Tasks view of SAP BusinessObjects Financial Consolidation, click on File / New / Scan objects;

8. In the General tab, enter Code = SCAN (for example);

9. In the Tasks tab, select Active then save and close the task;

10

Requirements

Receiving the configuration

1. Extract all files from the self-extractable archive SK_FOR_USGAAP_SP1.exe in the directory where objects will be received (see 3.1 Setup the transfer vectors)

2. In SAP BusinessObjects Financial Consolidation, from the Tasks view, launch the scan task created (see. 3.1 Create the scan task)

11

Requirements

After the successful execution of the SCAN task, 5 new receive tasks are created

3. From the Tasks view, display the Long description column. To do so, right click in the list and choose the Columns command in the contextual menu

In the List properties dialog box, select the View tab and expand the node General in the Available columns pane. Then select the Long description item and click the button with the right arrow to add it to the Visible columns pane.

The task list will now display a long description for all receive tasks

12

Requirements

4. Launch first the receive task Software configuration containing the software configuration and then, if desired, all the receive tasks containing sample data sets. To do so, select the receive task in the list, right-click and choose the Start command in the contextual menu

Changing the site to a TOP site

In order to set up the project database, a SQL query has to be run. The syntax is different for a MSSQL or an Oracle database. Afterwards, the database becomes the owner of the configuration, which means that it becomes independent and objects can be modified. STOPPING THE DATA SOURCE 1. Close SAP BusinessObjects Financial Consolidation; 2. Launch CtAdmin.msc from the installation directory of the application server; 3. Under the root node Business Objects Administration (local), expand the node of the data source corresponding to the database; 4. Right-click on the Operation node, and select All tasks / Stop Data Source from the popup menu as shown in the screenshot below.

13

Requirements

CHANGING THE SITE 1. Launch the query tool of the database engine (Query Analyzer for MSSQL, SQL+ for Oracle); 2. Connect to the database server and select the database; 3. Paste the query corresponding to the database engine (cf. appendix) and run it.

REMINDER In order to finalize the set up of the Starter Kit, it is required to validate and distribute the Category Scenario in the Category Builder view, and then, to synchronize the hierarchy for all Reportings in the Reporting Organizer view.

14

Appendix 1: Query MSSQL database

Appendix 1: Query MSSQL database

For a MSSQL database, run the following query:
--============================================================================= --Aim: Modify the present site as a TOP site in the database -- Date: 09/2005. -- ============================================================================ --============================================================================= --Statement and allocation of the user variables. -The new code has to exist in the table ct_site -(Column name) and cannot be longer than 17 characters. -- ============================================================================ DECLARE @strName AS VARCHAR(17) SET @strName = '0000.TOP' -- ============================================================================ -- Update the signature of the site. --============================================================================= UPDATE ct_config SET name = (SELECT signature FROM ct_site WHERE name = @strName) WHERE id = 1 -- ============================================================================ -- Update the name of the site. --============================================================================= UPDATE ct_config SET name = @strName WHERE id = 2 -- ============================================================================ -- Update of the type of site. -The possible types of site are: -1: simple site. -2: collection site. -3: consolidation site. -4: setup site. -- ============================================================================ UPDATE ct_config SET name = (SELECT type FROM ct_site WHERE name = @strName) WHERE id = 4 -- ============================================================================ --Update the site status. -The present site can be: -1: not initialized. -2: initialized. --============================================================================ UPDATE ct_config SET name = 2 WHERE id = 5 -- ============================================================================ --Clean ct_identifier_pool and ct_recycled_identifier. --============================================================================ DELETE FROM ct_identifier_pool DELETE FROM ct_recycled_identifier

15

Appendix 1: Query MSSQL database

16

Appendix 2: Query Oracle database

Appendix 2: Query Oracle database

For an Oracle Database, run the following query:
DECLARE SITENAME VARCHAR(17); /* Statement and allocation of the user variables*/ /* The new code has to exist in the table ct_site (Column name) */ /*and cannot be longer than 17 characters. */ BEGIN SITENAME := '0000.TOP'; /* Update the signature of the site in the table ct_config */ UPDATE ct_config SET name = (SELECT signature FROM ct_site WHERE name = SITENAME) WHERE id = 1; /* Update the name of the site in the table ct_config */ UPDATE ct_config SET name = SITENAME WHERE id = 2; /* Update of the type of site in the table ct_config */ /*--The possible types of site are: */ /*-1: simple site. */ /*-2: collection site. */ /*-3: consolidation site. */ /*-4: setup site. */ UPDATE ct_config SET name = (SELECT type FROM ct_site WHERE name = SITENAME) WHERE id = 4; /* Update the site status in the table ct_config. */ /* --The present site can be: */ /* -1: not initialized. */ /* -2: initialized.*/ UPDATE ct_config SET name = 2 WHERE id = 5; /* Clean ct_identifier_pool and ct_recycled_identifier */ DELETE CT_IDENTIFIER_POOL; DELETE CT_RECYCLED_IDENTIFIER; END;

17

Appendix 2: Query Oracle database

18