Consolidation process in IBM Cognos Controller using Batch Processing

Transcription

1 Guideline Consolidation process in IBM Cognos Controller using Batch Product(s): IBM Cognos Controller Area of Interest: Financial Management

2 2 Copyright and Trademarks Licensed Materials - Property of IBM. Copyright IBM Corp IBM, the IBM logo, and Cognos are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at While every attempt has been made to ensure that the information in this document is accurate and complete, some typographical errors or technical inaccuracies may exist. IBM does not accept responsibility for any kind of loss resulting from the use of information contained in this document. The information contained in this document is subject to change without notice. This document is maintained by the Best Practices, Product and Technology team. You can send comments, suggestions, and additions to [email protected].

3 3 Contents 1 INTRODUCTION PURPOSE APPLICABILITY EXCLUSIONS AND EXCEPTIONS CONSOLIDATION PROCESS AND BATCHING CONSOLIDATION BY STATUS AND BATCH PROCESSING BATCH QUEUE SINGLE BATCH PROCESSOR PERIOD LOCKED DURING CONSOLIDATION SERVER PREFERENCE ISSUES...9

4 4 1 Introduction 1.1 Purpose This document provides guidelines on using batch processing as part of running the consolidation process in IBM Cognos Controller. There are additional details around the best approaches to running different consolidations in IBM Cognos Controller. 1.2 Applicability IBM Cognos Controller 1.3 Exclusions and Exceptions There are no known exclusions and exceptions. The processes described are what is currently recommended for IBM Cognos Controller and are subject to change.

5 5 2 Consolidation Process and Batching 2.1 Consolidation by status and batch processing Consolidation status is the recommended practice when running consolidations within IBM Cognos Controller. There is an option to submit the consolidation process in batch: You can also schedule the date and time you would like the process run in the Consolidation With Status window. 2.2 Batch Queue Once the batch is submitted it can be reviewed by looking at the batch queue.

6 6 You have the option to run the batch immediately. You can also review the status of any open batches. 2.3 Single Batch Processor You can have several batch processors work at once to expedite various processes in IBM Cognos Controller. However, it should be noted that it is a best practice to run only one processor. There can be issues with IBM Cognos Controller if you try to run several consolidations at the same time. The potential errors that could occur include: Problems can occur if a group code appears in two (or more) different consolidation structures. For a regular company it will not be a problem. If the consolidations are made in different periods make sure that any possible dependency is set when scheduling the batches. Otherwise the batches can be started randomly and the consolidated data could appear to be wrong. Remember also to set dependencies if using linked actualities. The dependencies could be based on the order of the batches, so consider which consolidation you want to run first. This can be important if you are using step by step consolidation versus consolidation with status.

7 7 2.4 Period Locked During Consolidation A new server preference CONSOLOCKPERIOD=YES is created to avoid any changes in data during the consolidation process. If this server preference is used, the following menus are locked when the consolidation is run for the actuality/period/consolidation type/group (and companies belonging to this consolidation type/group) selected in consolidation with status or by steps: Company/Data Entry-Reported Values: the data entry (all forms) is locked for the actuality/period and companies belonging to the consolidation type and group selected, but the forms can be opened in read-only mode. Company/Data Entry-Company Journals: the data entry is locked for the actuality/period and companies belonging to the consolidation type and group selected but the journals can be opened in read-only mode. Company/Copy-Reported Values Between Periods: the copy is locked for the actuality/period (in To ) and companies or group belonging to the consolidation type and group selected. Company/Copy-Reported Values Between Companies: the copy is locked only for the actuality/period and companies (in To ) belonging to the consolidation type and group selected. Company/Copy-Company Journals Between Periods: the copy is locked only for the actuality/period (in To ) and companies or group belonging to the consolidation type and group selected. Company/Copy-Company Journals Between Companies: the copy is locked only for the actuality/period and companies (in To ) belonging to the consolidation type and group selected.

8 8 Company/Copy-Opening Balances for Reported Values: the copy is locked only for the actuality/period (in To ) and companies or group belonging to the consolidation type and group selected. Company/Copy-Run Copy Table: the copy is locked only for the actuality/period and companies or group belonging to the consolidation type and group selected. Group/Data Entry-Group Journals: the data entry is locked only for the actuality/period and group belonging to the consolidation type and group selected but the journals can be opened in read-only mode. Group/Copy-Group Journals Between Periods: the copy is locked only for the actuality/period (in To ) and group belonging to the consolidation type and group selected. Group/Copy-Group Journals Between Groups: the copy is locked only for the actuality/period and group (in To ) belonging to the consolidation type and group selected. Transfer/Import Data: the import is locked if it concerns actuality/period and companies belonging to the consolidation type and group selected for the consolidation. Even if the default options Continue with Import if the Import File Contains Values for Locked Periods and Continue with Import if the Import File Contains Invalid Values are selected, the import is locked. Transfer/Import External Data: the import is locked if it concerns actuality/period and companies belonging to the consolidation type and group selected for the consolidation. Transfer/Import General Ledger Journal: the import is locked if it concerns actuality/period and companies belonging to the consolidation type and group selected for the consolidation. When the consolidation with status and by steps is run immediately (not scheduled), a check is done if any user is in: Company/Data Entry-Reported Values Company/Data Entry-Company Journals Company/Copy-Reported Values Between Periods Company/Copy-Reported Values Between Companies Company/Copy-Company Journals Between Periods Company/Copy-Company Journals Between Companies Company/Copy-Opening Balances for Reported Values Company/Copy-Run Copy Table Group/Data Entry-Group Journals Group/Copy-Group Journals Between Periods

9 9 Group/Copy-Group Journals Between Group Transfer/Import Data Transfer/Import External Data Transfer/Import General Ledger Journal, If a user is in one of these menus, the user who launched the consolidation (even if it runs in batch mode) receives a message identifying the user who is locking. Only the first ten user names are shown. By selecting the consolidation regardless of the Company Locks check box, you can continue to run the consolidation. If the check box is not selected, consolidation cannot run until all users are not locking data. When consolidation is scheduled, the consolidation runs only if there are no users in the following areas under the Period/Actuality/Group (or Companies belonging to this group) selected for the consolidation: Company/Data Entry-Reported Values Company/Data Entry-Company Journals Company/Copy-Reported Values Between Periods Company/Copy-Reported Values Between Companies Company/Copy-Company Journals Between Periods Company/Copy-Company Journals Between Companies Company/Copy-Opening Balances for Reported Values Company/Copy-Run Copy Table Group/Data Entry-Group Journals Group/Copy-Group Journals Between Periods Group/Copy-Group Journals Between Group Transfer/Import Data Transfer/Import External Data Transfer/Import General Ledger Journal, Five attempts are made every five minutes. If a user is locking, the consolidation is not launched. In the batch log, a message appears stating that the consolidation has failed due to a runtime lock, and identifies which users were locking. The same message is repeated with the name of the first 10 users who didn t allow the consolidation to run. 2.5 Server Preference issues CONSOLOCKPERIOD is not dependent on batchmode = on. Without CONSOLOCKPERIOD, there are no barriers for open periods. You can run dual consolidations while someone is entering new values. If you want to avoid the risk of double consolidation you can control the users to run consolidation in batch

10 10 mode, with one batch server only. With CONSOLOCKPERIOD = YES, it is not possible to run two consolidations at the same time, neither if you run the consolidation directly, nor if you use the batch mode. At the same time, data entry locks the possibility to consolidate. With CONSOLOCKPERIOD = YES, you allow users to consolidate, directly or batch and you can have multiple batch processes running at the same time. Problems can occur if a group code appears in two or more different consolidation structures. For a regular company it will not be a problem. Group codes are allowed to shared between consolidation structures when the companies within the group are different. Differences will occur even in one batch server mode. Consolidation Regardless of Company Locks is not always an option, for example when BATCHMODE = ON.