Installation Guide COGNOS (R) ENTERPRISE BUSINESS INTELLIGENCE COGNOS ANALYTIC APPLICATIONS INSTALLATION GUIDE FOR J.D.

Transcription

1 COGNOS (R) ENTERPRISE BUSINESS INTELLIGENCE COGNOS ANALYTIC APPLICATIONS FOR J.D. EDWARDS (R) INSTALLATION GUIDE Installation Guide e-apps 1.4A Type the text for the HTML TOC entry Type the text for the HTML TOC entry Type the text for the HTML TOC entry Type the Title Bar text for online help Cognos Analytic Applications for J. D. Edwards 1.4A Version 1.4A Installation Guide THE NEXT LEVEL OF PERFORMANCE TM

2 Product Information This document applies to Cognos Analytic Applications for J. D. Edwards 1.4A and may also apply to subsequent releases. To check for newer versions of this document, visit the Cognos support Web site ( Copyright Copyright (C) 2003 Cognos Incorporated 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. Cognos does not accept responsibility for any kind of loss resulting from the use of information contained in this document. This document shows the publication date. The information contained in this document is subject to change without notice. Any improvements or changes to either the product or the document will be documented in subsequent editions. U.S. Government Restricted Rights. The software and accompanying materials are provided with Restricted Rights. Use, duplication, or disclosure by the Government is subject to the restrictions in subparagraph (C)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS , or subparagraphs (C) (1) and (2) of the Commercial Computer Software - Restricted Rights at 48CFR , as applicable. The Contractor is Cognos Corporation, 15 Wayside Road, Burlington, MA This software/documentation contains proprietary information of Cognos Incorporated. All rights are reserved. Reverse engineering of this software is prohibited. No part of this software/documentation may be copied, photocopied, reproduced, stored in a retrieval system, transmitted in any form or by any means, or translated into another language without the prior written consent of Cognos Incorporated. Cognos and the Cognos logo are trademarks of Cognos Incorporated in the United States and/or other countries. All other names are trademarks or registered trademarks of their respective companies. Information about Cognos Products and Accessibility can be found at

3 Table of Contents Welcome 5 Chapter 1: Cognos Analytic Applications 7 Analytic Applications Console 7 DecisionStream 7 Data Warehouse 8 Reporting Components 8 Chapter 2: Installing Cognos Analytic Applications 9 System Requirements 9 Creating the Databases 10 Enable the Translation Setting on DB2 11 Obtain Connection Information 12 Install Cognos Analytic Applications 12 Configure Data Connections 13 Test the Impromptu Connection to the Data Warehouse 13 Insert an Application 14 Prepare the DecisionStream Environment 14 Chapter 3: Configuring Cognos Analytic Applications 17 Analytic Applications Console Interface 17 Set Configuration Parameters 18 Chapter 4: Configuring the Reporting Environment 19 Series 7 Web BI Compressed Files 19 Configure Access to Cognos Analytic Applications Help 20 Add a New Applications Theme 21 Unpack the Web Application Using Deployment Manager 21 Appendix A: Configuration Parameters 23 Internal Variables 23 Accounts Payable Analysis 23 Accounts Receivable Analysis 23 General Ledger Analysis 24 Inventory Analysis 24 Procurement Analysis 24 Production Analysis 25 Sales Analysis 25 Data Warehouse Defaults 26 Accounts Payable Analysis 26 Accounts Receivable Analysis 27 General Ledger Analysis 28 Inventory Analysis 29 Procurement Analysis 30 Production Analysis 31 Sales Analysis 32 Installation Guide 3

4 Scaling Factors 33 Accounts Payable Analysis 33 Accounts Receivable Analysis 33 General Ledger Analysis 34 Inventory Analysis 34 Procurement Analysis 34 Production Analysis 35 Sales Analysis 38 Category Codes 39 Accounts Payable Analysis 39 Accounts Receivable Analysis 43 General Ledger Analysis 46 Inventory Analysis 48 Procurement Analysis 53 Production Analysis 58 Sales Analysis 61 Selection Criteria 64 Accounts Payable Analysis 64 Accounts Receivable Analysis 65 General Ledger Analysis 66 Inventory Analysis 68 Procurement Analysis 72 Production Analysis 72 Sales Analysis 76 Stored Procedures 77 Accounts Payable Analysis 77 Accounts Receivable Analysis 77 General Ledger Analysis 77 Inventory Analysis 78 Procurement Analysis 79 Production Analysis 79 Sales Analysis 80 J.D. Edwards OneWorld Users 80 Index 81 4 Cognos Analytic Applications for J.D. Edwards (R) for J.D. Edwards (R)

5 Welcome What Is in This Document This document explains how to install Cognos Analytic Applications. This document contains an overview of Cognos Analytic Applications and its components details about the personnel, software, and other requirements that must be met before the installation begins steps to install Cognos Analytic Applications steps to set required database connections steps to prepare the DecisionStream environment What You Need to Know to Use This Document Effectively You should be a Windows user and have some experience installing software on Windows computers. Other Information Our documentation includes user guides, tutorial guides, reference books, and other pieces to meet the needs of our varied audience. The information is available in online book format (PDF). Use online books when you want a printed version of a document or when you want to search the whole document. You can print selected pages, a section, or the whole book. Cognos grants you a non-exclusive, non-transferable license to use, copy, and reproduce the copyright materials, in printed or electronic format, solely for the purpose of providing internal training on, operating, and maintaining the Cognos software. In Windows products, online books are available from the Windows Start menu (Cognos) and from the product Help menu (Books for Printing). You can also read the product readme files and the installation guides directly from the Cognos product CDs. The following documents contain related information, and may be referred to in this document. Topic How to modify configuration parameters How to install DecisionStream Location Developer Guide DecisionStream Installation Guide Because Cognos Analytic Applications works closely with DecisionStream, you may need to consult the DecisionStream documentation as you work with the product. Questions or Comments? For additional technical information about using Cognos Analytic Applications, visit the Cognos support Web site ( Installation Guide 5

6 Welcome 6 Cognos Analytic Applications for J.D. Edwards (R) for J.D. Edwards (R)

7 Chapter 1: Cognos Analytic Applications Cognos Analytic Applications are prepackaged analysis and reporting solutions that help businesses understand forces affecting key operational areas. Cognos Analytic Applications extracts data from corporate data sources and loads it into a data warehouse. The data warehouse facilitates analysis and information sharing over the Internet, intranets, and extranets. Cognos Analytic Applications uses the following components to provide a complete, cross-functional view of corporate data: the Analytic Applications Console DecisionStream a data warehouse reporting components (catalogs, models, and reports) Cognos Analytic Applications Analytic Applications Console source database PowerPlay Cognos DecisionStream Data warehouse Predefined catalogs, models, and reports Impromptu Analytic Applications Console The Analytic Applications Console is the hub of all configuration and administration aspects of an Application. Information supplied to the Console provides data processing information to DecisionStream. Use the console to set up database connections to the source system, the target data warehouse, and the DecisionStream catalog to create the DecisionStream catalog and modify the schema for the target data warehouse to install the reporting components to set up parameters to control how the target data warehouse is loaded and structured to specify parameters for the jobs that load data into the target data warehouse to perform controlled data reextractions, for exception handling DecisionStream Cognos Analytic Applications uses DecisionStream to extract and load source data into a data warehouse for analysis and reporting. Installation Guide 7

8 Chapter 1: Cognos Analytic Applications DecisionStream Catalog Each Application comes with a DecisionStream catalog containing the extraction model (source-to-target mappings, business rules, and so on) and a DecisionStream JobStream for each table to be created in the data warehouse. The predefined JobStreams employ the Cognos best warehousing practices, including changed data capture, which provides incremental updates support for slowly changing dimensions, for history preservation Data Warehouse Extracting data from source systems and loading it into a data warehouse facilitates analysis. The data warehouse supplies the data to the reporting components. Each Application in the data warehouse is a star schema containing facts and dimensions, with the fact tables surrounded by satellite dimension tables. Users can drill down quickly into the data to uncover correlations between dimensions and elements in the fact table. Conformed Dimensions Cognos Analytic Applications use conformed dimensions that are shared throughout the data warehouse. Conformed dimensions build an information backbone that ties together the functional areas of the business. This structure provides consistent, cross-functional data for business reporting. Reporting Components Impromptu catalogs and PowerPlay models, from which you build cubes, supply all required information to the predefined reports. Report administrators can modify these catalogs, models, and reports, or create additional ones to meet enterprise reporting needs. The reporting components provide proven business content and best practices shown through captured business metrics key performance indicators (KPIs) and analyses To open these reports, you need Impromptu and PowerPlay, which are sold and installed separately. 8 Cognos Analytic Applications for J.D. Edwards (R) for J.D. Edwards (R)

9 Chapter 2: Installing Cognos Analytic Applications Cognos Analytic Applications may require different administrators in an organization to install and configure parts of it. Administrator EBI administrator Database or data warehouse administrator J.D. Edwards administrator Tasks Install and configure DecisionStream, Impromptu, and PowerPlay Create RDBMS databases and accounts and set appropriate roles and privileges Prepare the J.D. Edwards environment To install Cognos Analytic Applications, follow this process. Detailed instructions follow for each of these tasks: Verify system requirements. Create databases for the DecisionStream catalog and the target warehouse. Enable the translation setting on DB2 Obtain connection information. Install Cognos Analytic Applications. Configure data connection. Insert an application. Prepare the DecisionStream environment. System Requirements The following table lists the minimum hardware and software requirements for each Cognos Analytic Applications computer. Requirement Operating system Disk space Storage for temporary files RAM Specification Windows NT Workstation 4.0 with Service Pack 3 or higher Windows GB 105 MB 1 GB CD-ROM driver Supports long file names Installation Guide 9

10 Chapter 2: Installing Cognos Analytic Applications Requirement Web browser Databases Specification Microsoft Internet Explorer 4.0 or higher Netscape Navigator 4.0 or higher Required for the front end of the reporting environment If the data source is J.D. Edwards on DB2, IBM AS/400 client software (V5R2 with service pack SI07675) and an ODBC connection for the database RDBMS client software (and a SQL editor) to create databases for the DecisionStream catalog and the target data warehouse, either SQL Server 2000 or Oracle 8. If you want to perform bulk data transfers to Oracle, you also require the Oracle bulk loader utility. See your Cognos Analytic Applications license agreement for supported data source and target combination Cognos Software The following Cognos software must be installed: DecisionStream 7.1 For information about how to install DecisionStream, see the DecisionStream Installation Guide. Impromptu 7.0 MR2 Part of the reporting environment. Administrator privileges are required to change report designs. PowerPlay 7.0 MR2 Part of the reporting environment. Administrator privileges are required to change report designs. Creating the Databases You must create databases for the DecisionStream catalog and the target data warehouse. Whether to create them in Oracle or Microsoft SQL Server depends on your Cognos Analytic Applications license agreement. For information about how to create the databases and define user accounts, roles, and privileges, see your database or data warehouse administrator. Before you can create a database for the DecisionStream catalog, ensure that you have at least 20 MB of free space. Also, check your system requirements. Oracle Databases Follow this process to create Oracle databases: On the Oracle server, create databases for the DecisionStream catalog and the target data warehouse, scaled to the data source volume. 10 Cognos Analytic Applications for J.D. Edwards (R) for J.D. Edwards (R)

11 Chapter 2: Installing Cognos Analytic Applications Set up Oracle accounts for the databases with at least the following privileges: create session alter session create trigger create procedure create synonym create table create sequence create view The data warehouse database also requires the following grants: GRANT EXECUTE ON DBMS_PIPE TO <USER ACCOUNT> GRANT SELECT ON V_$DB_PIPES TO <USER ACCOUNT> If these parameters are granted through a role, then grant CREATE TABLE explicitly to the user. Use the Oracle Net8 Easy Config utility to set up database alias names for the DecisionStream catalog and target data warehouse. Confirm that the Oracle client software is installed on the workstation where Cognos Analytic Applications will be installed. Confirm that the Oracle account can access the database using SQL Plus. Set up user accounts for the target data warehouse so that users can connect and select data for reporting purposes. If you intend to bulk load data into the data warehouse, create a directory to store the data files. Microsoft SQL Server Databases Follow this process to create Microsoft SQL Server databases: On the server that contains Microsoft SQL Server, create databases for the DecisionStream catalog and the target data warehouse, scaled to the data source volume. Ensure that the SQL Server account is defined to be the database owner (dbo) of the Microsoft SQL Server database. Confirm that the Microsoft SQL Server client software is installed on the workstation where Cognos Analytic Applications will be installed. Confirm that the SQL Server account can access the database using isql. Set up user accounts for the target data warehouse so that users can connect and select data for reporting purposes. Enable the Translation Setting on DB2 If the data source is J.D. Edwards, the Translation setting must be enabled for the ODBC connection. Steps 1. From the Start menu, click Settings, Control Panel. 2. Double-click ODBC Data Sources. 3. On the User DSN tab, double-click the Client Access ODBC Driver Data Source. 4. Click the Translation tab. 5. Under Translation, click Translate CCSID, and click OK twice. Installation Guide 11

12 Chapter 2: Installing Cognos Analytic Applications Obtain Connection Information To help you install and configure Cognos Analytic Applications, obtain the following information from the appropriate administrator. J.D. Edwards Database ODBC data source name (DB2): Database alias (Oracle): Database server name (MS SQL Server): Database name (MS SQL Server): User name: Password: DecisionStream Catalog RDBMS type: Database alias (Oracle): Database server name (MS SQL Server): Database name (MS SQL Server): User name: Password: Database size: Backup schedule: Target Data Warehouse RDBMS type: Database alias (Oracle): Database server name (MS SQL Server): Database name (MS SQL Server): User name: Password: Database size: Bulk load directory: Backup schedule: Install Cognos Analytic Applications This installation includes Cognos Analytic Applications and its components. Before you install, ensure you check your system requirements and create the databases. Steps 1. On the computer where DecisionStream is installed, insert the Cognos Analytic Applications CD. The Autorun should appear. If it doesn t, double-click the setup.exe file in the root folder of the CD. 2. Click Install application_name 1.4A and follow the instructions. 3. In the Installation Type page, click Typical to install all components or Custom to install only some components, and then click Next. 12 Cognos Analytic Applications for J.D. Edwards (R) for J.D. Edwards (R)

13 Chapter 2: Installing Cognos Analytic Applications 4. If you click Custom, select the components you want to install, and then click Next. Tip: If you are installing Cognos Analytic Applications for the first time on this computer, all components are selected by default and cannot be cleared. 5. Complete the installation. Note: Installing the Accounts Payable, Accounts Receivable, General Ledger, or Production Analysis application installs the Chart of Accounts Multiplier tool. This tool is used only by the General Ledger Analysis application. Configure Data Connections Use the Cognos Analytic Applications Console to set database connections for the data warehouse, the DecisionStream catalog, and the source database. Before you install, ensure you check your system requirements and create the databases. Steps for the Data Warehouse Database 1. From the Start menu, click Programs, Cognos Analytic Applications, Analytic Applications Console. 2. In the Mart Locations box, click New. 3. In the Connection Name box, type a meaningful name. 4. Choose a connection type and enter the required information for the connection. 5. Click Close. 6. In the Mart Locations box, select the data warehouse location and click OK. The Applications Manager window appears. Steps for the DecisionStream Catalog Database 1. In the left pane of the Applications Manager window, right-click Connections and click Insert Connection. 2. In the Connection Name box, type a meaningful name. 3. Choose a connection type and enter the required information for the connection. 4. Click Test. If a window appears with the message "Connection Succeeded," click OK. Otherwise, check the connection information to ensure that it is correct and repeat steps 2 to Click Close. Steps for the Source Database 1. In the left pane of the Applications Manager window, right-click Connections and click Insert Connection. 2. In the Connection Name box, type a meaningful name. 3. Choose a connection type and enter the required information for the connection. 4. Click Test. If a window appears with the message "Connection Succeeded," click OK. Otherwise, check the connection information to ensure that it is correct and repeat steps 2 to Click Close. Test the Impromptu Connection to the Data Warehouse After installing Cognos Analytic Applications, the Analytic Applications Console updates the logical database connection from the sample Impromptu catalog to the data warehouse. Ensure that the connection is successful. Installation Guide 13

14 Chapter 2: Installing Cognos Analytic Applications Steps 1. Open the sample Impromptu catalog. 2. If the catalog cannot find the source data, change the catalog schema name to correspond to the database schema that stores the data warehouse. 3. If any changes were made to the data warehouse, such as changed data types or deleted columns or tables, change the catalog to match. Insert an Application You can now create an application in Cognos Analytic Applications by running the New Application wizard. Cognos Analytic Applications loads the data warehouse schema and completes the installation. You must already have installed Cognos Analytic Applications and configured a data connection. Steps 1. In the left pane of the Applications Manager window, right-click Cognos Analytic Applications and click Insert Application. The New Application wizard appears. 2. Click Browse to find the package file for the application you want to install, and click Next. The location is installation_location\cpmf 1.4\Application Packages\application_name 1.4A JDE.cab. 3. In the Mart Database Connection Name box, click the connection you defined for the data warehouse. 4. In the Source Database Connection Name box, click the connection you defined for the source database. 5. In the Catalog Database Connection Name box, click the connection you defined for the DecisionStream catalog. 6. In the Report Location box, enter the location where you want to install the reporting environment. 7. Choose how to handle new catalog components that have the same name as existing components: To overwrite, select the Overwrite Existing Catalog Components check box. To maintain your existing components, clear the Overwrite Existing Catalog Components check box. If the Drop Tables window appears, clear all the check boxes to install the application without altering the existing contents of the data warehouse, or select check boxes for any tables you want to drop. 8. Click Finish. Prepare the DecisionStream Environment Specify where the database alias file is located and where to store data, log, and reject files generated by DecisionStream when executing JobStreams. Steps 1. In the DecisionStream Console, click Tools, Options. 2. Click the Environment tab. 3. In the DBAlias File box, enter the location where you want to store the text file for the database connection information. DecisionStream reads this file to find the source, target, and catalog databases. 14 Cognos Analytic Applications for J.D. Edwards (R) for J.D. Edwards (R)

15 Chapter 2: Installing Cognos Analytic Applications 4. In the Reject File Directory box, enter the location where you want to create reject files. Reject Files are text files in which DecisionStream stores rejected records. 5. In the Data Delivery Directory box, enter the location where you want DecisionStream to put text data files and metadata files. If you leave this box blank, DecisionStream puts the files in the data subdirectory of the DecisionStream directory. 6. In the Log File Directory box, enter the location where you want to create log files. If you leave this box blank, Cognos Analytic Applications puts the files in the same location as DecisionStream log files. 7. Click OK. Installation Guide 15

16 Chapter 2: Installing Cognos Analytic Applications 16 Cognos Analytic Applications for J.D. Edwards (R) for J.D. Edwards (R)

17 Chapter 3: Configuring Cognos Analytic Applications Configuring Cognos Analytic Applications involves setting configuration parameters that define the structure of the target data warehouse, what data is loaded, and the source table fields used for the data extraction. You perform these operations using the Analytic Applications Console (p. 7). Analytic Applications Console Interface You use the Console to configure the application for your environment. The left pane organizes the applications installed in the target data warehouse in a hierarchy. The right pane shows properties and components of the item selected in the left pane. Cognos Analytic Applications The Cognos Analytic Applications node is the root node of the Cognos Analytic Applications Console. Installed Applications The Installed Applications node is the root node for all installed applications. Application_name 1.4A for J.D. Edwards This is the name of an installed application. Parameters The Parameters node contains configuration parameters that define the structure of the data warehouse, what data is loaded into the target data warehouse, and the source table fields used for the data extraction. Parameters are grouped into two folders, system and user. System Parameters System parameters are common to all applications. Some of these parameters must be confirmed or modified prior to running jobs. In the Console, system parameters are identified by the domain value SYSTEM. User Parameters User parameters are specific to an application. Some of these parameters must be confirmed or modified prior to running jobs. In the Console, user parameters are identified by the domain value USER. JobFlows The JobFlows node is the location from which you execute jobs to load data into the target data warehouse. You can execute jobs individually or define a sequence of jobs to be executed by the Console. Predefined JobFlow By default, a Predefined JobFlow folder exists in the JobFlows folder for each application. This folder contains all jobs for all installed applications and the recommended order in which they should be executed. Any load dependencies that exist between jobs are respected. Note that the individual jobs do not appear in execution order in the left pane. Installation Guide 17

18 Chapter 3: Configuring Cognos Analytic Applications In addition, the configuration parameters that directly affect each job are organized in a Parameters subfolder. This reminds you what parameters must be set before you execute the job. application_name This JobFlow contains the individual jobs for the application_name application. If only one application was installed, this is the same as the Predefined JobFlow. Connections The Connections node shows the database connections defined for the source and target databases and the location where the DecisionStream catalog will be stored. Event Monitor The Event Monitor node stores historical data about the installation and activities of the Console. You can double-click an item in one of the Event Monitor nodes to view more information about the event. Installation History The Installation History node shows information about the installation of the Console, as well as the results of inserting an application. Extraction History The Extraction History node shows the results of running jobs in previous sessions. Current Activity The Current Activity node shows the results of activity during the current session. Set Configuration Parameters Configuration parameters for Cognos Analytic Applications are grouped into two folders: System Parameters and User Parameters. Modify these parameters as required to reflect the source system. If you use different source tables than those specified in DecisionStream builds, you must modify the builds to reflect your source system. For example, Cognos Analytic Applications assumes that business unit categories are stored in the source table F0006. If these categories are stored in a different table in your source system, you must modify the appropriate DecisionStream build before this data can be extracted. You can also modify configuration parameters prior to executing a specific job. Tip: Click the Parameters node of the job to see which parameters need to be set before running the job. For more information, see the Developer Guide. Steps 1. Expand the Parameters node. 2. Click either the System Parameters node or the User Parameters node. The configuration parameters contained in the node appear in the right pane of the Console. 3. Right-click the parameter you want to set and click Properties. 4. Click the value of the parameter to highlight it and to enter into edit mode. 5. Change the value. 6. Repeat steps 3 to 5 as required. 7. Click OK when you are finished. 18 Cognos Analytic Applications for J.D. Edwards (R) for J.D. Edwards (R)

19 Chapter 4: Configuring the Reporting Environment You must also configure the Cognos Series 7 BI components that are included with Cognos Analytic Applications. For information about Impromptu, PowerPlay, Transformer and PowerPlay for Windows, see the online help and the documents provided with Cognos Series 7. Cognos Series 7 Configuration Manager User Guide Access Manager Administrator Guide Impromptu Web Reports Administrator Guide PowerPlay Enterprise Server Guide Upfront Cognos Web Portal User Guide Deployment Manager User Guide Installed Locations The Cognos Analytic Applications reporting environment uses the following folders in installation_location\bi7: Catalogs FrontEnd Models Queries Reports Web Packages Series 7 Web BI Compressed Files The Series 7 BI folder on the Analytic Applications CD contains the Series 7 BI package compressed files. The names of these files are Series 7 BI or Series 7 Web BI and the name of the functional area and ERP that the items refer to. Examples are Sales Analysis Series 7 BI for ORF and Inventory Analysis Series 7 Web BI for SAP. Series 7 BI We recommend that you unzip these files to installation_location:\program Files\Cognos\CPMF1.5\Series7BI. The required folders will be created as follows. Folder Catalogs Frontend Models Contents The Impromptu catalog for the application Supporting help documentation, including area of analysis definitions and report descriptions in HTML format The Transformer models used to create all PowerPlay cubes Installation Guide 19

20 Chapter 4: Configuring the Reporting Environment Folder Queries Reports Contents The source queries used in the Transformer models The Impromptu and PowerPlay reports Series 7 Web BI The following folders must be unzipped to the location installation_location\program Files\Cognos\cer2. It may be necessary to move the Documentation, Templates, and Webcontent folders to the Upfront server machine. Ensure that the Templates and Webcontent folders remain in the same folder structure. The contents of the Packages and Packlets folders must also be accessible from the server where Deployment Manager is installed. The following describes the contents of each of these folders. Folder Packages Packlets Templates Webcontent Contents The package components required to unpack the Web application using Deployment Manager The packlets for the Deployment Manager package The template files for the applications Upfront theme The content files for the applications Upfront theme Configure Access to Cognos Analytic Applications Help After the compressed files are extracted, you must provide a point of entry into the Analytic Applications online help directory. In doing so you will also provide a starting point for rolling out the BI components within your organization. This release of the Series 7 business intelligence package may contain references to previous versions of Impromptu, Transformer, and PowerPlay. Where this occurs, the documentation is still relevant and can be used with your Series 7 tools. Steps 1. Create a shortcut to the file named indexfront.htm, located in the Frontend folder that was created with the Series 7 BI extraction. 2. Place this shortcut in a location that can be accessed by your users. Links to all reports, cubes, and detailed descriptions appear on this page. Tip: Set the file directories in Impromptu, Transformer, and PowerPlay to correspond to the installed location. You will easily find the required reporting items, and cube generation will be more efficient. 3. Generate the PowerCubes from the Transformer models provided, and place them in the desired location or create a reference to them in PowerPlay Enterprise Server for access by your end users. 4. Ensure that the database connection information was entered in Impromptu or use Access Manager to grant access to users and user classes. 20 Cognos Analytic Applications for J.D. Edwards (R) for J.D. Edwards (R)

21 Chapter 4: Configuring the Reporting Environment Add a New Applications Theme After the files containing the theme components are added to the server where Upfront is installed, the new theme must be added to Upfront for selection. Steps 1. In the Cognos EP Series 7 Server Administration window click the Portal button. 2. Logon using your user ID and password. 3. From the Edit menu, click Properties and then click the Display tab. 4. Under Available themes, click Add and then type applications This is the name of the folder containing the template and content files that were included with the application. 5. Click OK and exit the Upfront Server Administration area. You may have to restart the Upfront server and Upfront services for the new theme to be available for selection in Upfront. Unpack the Web Application Using Deployment Manager You must unpack the Web application to make the Analytic Applications NewsBox and NewsItems visible in Upfront. To unpack the PowerPlay reports successfully, you must first generate the PowerCubes and place them in a location where they can be accessed by both Deployment Manager and PowerPlay Enterprise Server. It is not necessary, however, to add these cubes to PowerPlay Enterprise Server before unpacking the application. After the Application is unpacked, PowerPlay Enterprise Server is automatically updated with these items. Before generating the PowerCubes, ensure that the database connection was configured in Impromptu and that Access Manager is closed. This database connection will be added to Access Manager later when the Deployment Manager package is unpacked. Conflict Resolution Policy The conflict resolution policy specifies which entity is preserved when merging the content of the package into the target environment and a conflict occurs between identical entities. Selecting Keep Target preserves the existing entity in the target environment. Keep Source replaces the entity in the target environment with the entity from the package. Because a new user class Applications Administrator and a new user named Analytic Applications are included with the Series 7 Web BI package, there should not be a conflict with any users defined in your existing namespace. However we recommend that you select Keep Target. Select all entries in the menu. The Autofill can assist in setting these mappings if the default directories were used. Steps 1. In Deployment Manager, click Unpack and open the.dmp file located two levels down in the Packages folder structure and required functional area. 2. Select the target environment by providing the connection information to Upfront running on the target server. 3. In the Package Editor window, specify the data to be unpacked. By default, all Impromptu Web Reports, PowerPlay Enterprise Server, Access Manager, and Newsbox components are included. 4. In the Properties window, modify the unpacking policies as you select the items available in the Package Editor pane. 5. Set the cube mappings to point to the PowerPlay cubes that were already created. 6. In the Unpack Roadmap, click Validate. Installation Guide 21

22 Chapter 4: Configuring the Reporting Environment 7. Resolve all errors revealed by the Validate function. 8. Unpack the application. 9. Ensure that a new set of reports and cubes are registered in Impromptu Web Reports and PowerPlay Enterprise Server. 10. Change the logon information for the new Applications Administrator in the Analytic Applications user class to that of your Applications Administrator. By default, this user has exclusive access to the Analytic Applications components. New users may be added as required. By default the logon is: User ID: Apps Admin Password: <blank> 11. Using Access Manager, configure the new data source that was added as part of the Applications package and that corresponds to the database that will be used by the Impromptu catalog. Ensure that a test results in a successful connection. 12. In Upfront Server Administration, click Portal. 13. From the Tools menu, click Security, Themes, Set Security and grant access to the Analytic Applications user class. 14. From your Web browser, start Upfront and logon using the Applications Administrator user ID. The applications theme can now be selected on the General tab of the Personalize screen. 22 Cognos Analytic Applications for J.D. Edwards (R) for J.D. Edwards (R)

23 The following default configuration parameters provided with the application are organized by type. Internal Variables Accounts Payable Analysis GL_ACCT_TYPE_CD GMR001 JDE column name from F0901 that is the source for the account type code. INCLUDE_ZERO_DATES Y Specifies whether to include records when UPMJ = 0. Set to Y to include these records. USE_SRC_CUR Y Determines whether to populate the target data warehouse with source currency data. If set to N, you must manually populate the Currency Rate and Currency Lookup tables in the data warehouse, which are used to populate the Financial Currency Conversion table. Accounts Receivable Analysis CUST_ADD_BOOK_HIER N Indicates how the Customer table is populated. If set to Y, the table will be populated using the address book. If set to N, then the parent/child table will be used. CUST_FAX_CD F A user-defined code (system 01/ type PH) that identify the fax number. CUST_PHN_CD ' ','B' A user-defined code (system 01/ type PH) that identify the phone number. GL_ACCT_TYPE_CD GMR001 JDE column name from F0901 that is the source for the account type code. INCLUDE_ZERO_DATES Y Specifies whether to include records when UPMJ = 0. Set to Y to include these records. USE_SRC_CUR Y Determines whether to populate the target data warehouse with source currency data. If set to N, you must manually populate the Currency Rate and Currency Lookup tables in the data warehouse, which are used to populate the Financial Currency Conversion table. Installation Guide 23

24 General Ledger Analysis GL_ACCT_TYPE_CD GMR001 JDE column name from F0901 that is the source for the account type code. INCLUDE_ZERO_DATES Y Setting to include dates that are equal to zero. USE_SRC_CUR Y Lets you modify the content of CURRENCY_LOOKUP and prevents the FINANCIAL_CURRENCY job from overwriting these changes. Inventory Analysis COST_LEDGER_MOV 02 Identifies the cost method used to calculate the Stock Opening Balance Moving Price. For example, 2 = Weighted Average. Valid values are in System 40, type CM. COST_LEDGER_STD 07 Identifies the cost method used to calculate the Stock Opening Balance Standard Price. For example, 7 = Standard. Valid values are in System 40, type CM. INCLUDE_SPECIAL_STO CKS Y Determines whether special stocks, stored in the Special Stock work table, are to be included in the Movement Class, Stock Class and Stock Overview tables. This parameter is not in use. INCLUDE_ZERO_DATES Y Specifies whether to include records when UPMJ = 0. Set to Y to include these records. INV_CST_SLCT_CD I Identifies the inventory cost selection code versus the purchasing cost selection code. This identifies the costs in F4105 that are used for inventory. UOM_SALE_CD LB Represents the default unit of measure code when converting all other unit measures for analysis of an item in a common unit of measure. USE_SRC_CUR Y Determines whether to populate the target data warehouse with source currency data. If set to N, you must manually populate the Currency Rate and Currency Lookup tables in the data warehouse, which are used to populate the Financial Currency Conversion table. Procurement Analysis APPROVAL_STATUS ('OP*B*240', 'OP*J*240', 'OP*S*280', 'OR*B*120', 'OR*J*120', 'OR*N*120', 'OR*S*120', 'OR*T*120') Unique combination of document type, line type, and status code, where the status code is the approval status value. Multiple entries are allowed using comma separation. CNTRCT_DOC_TYPE OB Contract document type code. Multiple entries are allowed using comma separation. CUST_ADD_BOOK_HIER N Indicates how the Customer table is populated. If set to Y, the table will be populated using the address book. If set to N, then the parent/child table will be used. 24 Cognos Analytic Applications for J.D. Edwards (R) for J.D. Edwards (R)

25 CUST_FAX_CD F A user-defined code system 01, type PH, indicating the location or use of a phone number. For example, F is for fax, C for car, and H for home. GL_ACCT_TYPE_CD GMR001 JDE column name from F0901 that is the source for the account type code. INCLUDE_ZERO_DATES Y Specifies whether to include records when UPMJ = 0. Set to Y to include these records. PO_DOC_TYPE OP Purchase order document type code. Multiple entries are allowed using comma separation. QUOTN_DOC_TYPE OQ Quotation document type code. Multiple entries are allowed using comma separation. RQSTN_DOC_TYPE OR Requisition document type code. Multiple entries are allowed using comma separation. UOM_SALE_CD LB Represents the default unit of measure code when converting all other unit measures for analysis of an item in a common unit of measure. USE_SRC_CUR Y Determines whether to populate the target data warehouse with source currency data. If set to N, you must manually populate the Currency Rate and Currency Lookup tables in the data warehouse, which are used to populate the Financial Currency Conversion table. Production Analysis GL_ACCT_TYPE_CD GMR001 JDE column name from F0901 that is the source for the account type code. INCLUDE_ZERO_DATES Y This parameter specifies whether to include records when UPMJ = 0. Set to Y to include these records. USE_SRC_CUR Y This parameter is used in FINANCIAL_CURRENCY and determines whether to populate the target data mart with source currency data. If set to N, you must manually populate the Currency Rate and Currency Lookup tables in the data mart, which are used to populate the Financial Currency Conversion table. Sales Analysis CUST_ADD_BOOK_HIER N Indicates how the Customer table is populated. If set to Y, the table will be populated using the address book. If set to N, then the parent/child table will be used. CUST_FAX_CD F A user-defined code system 01, type PH, indicating the location or use of a phone number. For example, F is for fax, C for car, and H for home. INCLUDE_ZERO_DATES Y Specifies whether to include records when UPMJ = 0. Set to Y to include these records. Installation Guide 25

26 UOM_SALE_CD LB Represents the default unit of measure code when converting all other unit measures for analysis of an item in a common unit of measure. USE_SRC_CUR Y Determines whether to populate the target data warehouse with source currency data. If set to N, you must manually populate the Currency Rate and Currency Lookup tables in the data warehouse, which are used to populate the Financial Currency Conversion table. Data Warehouse Defaults Accounts Payable Analysis CONFIG_DB MSSQL Database type used to store the DecisionStream catalog. DATE_FORMAT YYYYMMDD Default date format. DEFAULT_COUNTRY_CD US Default country code. J.D. Edwards populates the default country code with a blank space, so this must be defined if the company is in Germany, for example. DEFAULT_COUNTRY_NM United States of America Default country name. J.D. Edwards populates the default country name with a blank space, so this must be defined if the company is in Germany, for example. DEFAULT_DATE Default value of date types in the target table when source date values are null. DEFAULT_LONG_CHAR «Unknown» Default value of large varchar (nine or more characters) data types in the target table when source large varchar types are null. DEFAULT_NUMBER 0 Default value of numeric types in the target table when source numeric values are null. DEFAULT_SHORT_CHAR - Default value of short varchar (less than eight characters) data types in the target table when source short varchar types are null. DEFAULT_VARIANT R Default value of the fiscal variant type in the target table if it cannot be determined from the source tables. GROUP_CURRENCY_CD USD Default value of the group currency type. Group currency code identifies the currency of the data warehouse. If a document is sold in local currency and needs to be converted to the data warehouse currency, this value is used as the To Currency Code. JDCOMLIB CLTCOM The library (DB2)/schema (Oracle)/user (SQL Server) that stores the J.D. Edwards com files (that is, F0005). JDDATALIB CLTDTA The library (DB2)/schema (Oracle)/user (SQL Server) that stores the J.D. Edwards data files. JDSECLIB CLTSEC The library (DB2)/schema (Oracle)/user (SQL Server) that stores the JDE Security Library. LOCAL_CURRENCY_CD USD Default value of the local currency code. Local currency code identifies the currency of the company and is used as the From Currency Code for currency conversion. If the multi-currency option is not set, then this is the default for the local currency. MART_BEGIN_DATE Data warehouse begin date. This date is used in the stored procedure of the All Time table to identify the beginning of the calendar dates. 26 Cognos Analytic Applications for J.D. Edwards (R) for J.D. Edwards (R)

27 MART_END_DATE Data warehouse end date. This date is used in the stored procedure of the All Time table to identify the ending of the calendar dates. SEPARATOR_CHAR * Default value that is used by DecisionStream to concatenate fields. Used to build natural keys for lookups and for DIM_ID values. MONTHSTOHOLDMANUA LTABLES 60 Default value in months to hold manual tables. SOURCE_DB DB2 Source database type. TARGET_DB MSSQL Target database type. Accounts Receivable Analysis CONFIG_DB MSSQL Database type used to store the DecisionStream catalog. DATE_FORMAT YYYYMMDD Default date format. DEFAULT_COUNTRY_CD US Default country code. J.D. Edwards populates the default country code with a blank space, so this must be defined if the company is in Germany, for example. DEFAULT_COUNTRY_NM United States of America Default country name. J.D. Edwards populates the default country name with a blank space, so this must be defined if the company is in Germany, for example. DEFAULT_DATE Default value of date types in the target table when source date values are null. DEFAULT_LONG_CHAR «Unknown» Default value of large varchar (nine or more characters) data types in the target table when source large varchar types are null. DEFAULT_NUMBER 0 Default value of numeric types in the target table when source numeric values are null. DEFAULT_SHORT_CHAR - Default value of short varchar (less than eight characters) data types in the target table when source short varchar types are null. DEFAULT_VARIANT R Default value of the fiscal variant type in the target table if it cannot be determined from the source tables. GROUP_CURRENCY_CD USD Default value of the group currency type. Group currency code identifies the currency of the data warehouse. If a document is sold in local currency and needs to be converted to the data warehouse currency, this value is used as the To Currency Code. JDCOMLIB CLTCOM The library (DB2)/schema (Oracle)/user (SQL Server) that stores the J.D. Edwards com files (that is, F0005). JDDATALIB CLTDTA The library (DB2)/schema (Oracle)/user (SQL Server) that stores the J.D. Edwards data files. JDSECLIB CLTSEC The library (DB2)/schema (Oracle)/user (SQL Server) that stores the JDE Security Library. LOCAL_CURRENCY_CD USD Default value of the local currency code. Local currency code identifies the currency of the company and is used as the From Currency Code for currency conversion. If the multi-currency option is not set, then this is the default for the local currency. MART_BEGIN_DATE Data warehouse begin date. This date is used in the stored procedure of the All Time table to identify the beginning of the calendar dates. Installation Guide 27

28 MART_END_DATE Data warehouse end date. This date is used in the stored procedure of the All Time table to identify the ending of the calendar dates. MONTHSTOHOLDMANUA LTABLES 60 Default value in months to hold manual tables. SEPARATOR_CHAR * Default value that is used by DecisionStream to concatenate fields. Used to build natural keys for lookups and for DIM_ID values. SOURCE_DB DB2 Source database type. TARGET_DB MSSQL Target database type. General Ledger Analysis CONFIG_DB MSSQL Database type used to store the DecisionStream catalog. DATE_FORMAT YYYYMMDD Default date format. DEFAULT_COUNTRY_CD US Default country code. J.D. Edwards populates the default country code with a blank space, so this must be defined if the company is in Germany, for example. DEFAULT_COUNTRY_NM United States of America Default country name. J.D. Edwards populates the default country name with a blank space, so this must be defined if the company is in Germany, for example. DEFAULT_DATE Default value of date types in the target table. DEFAULT_LONG_CHAR «Unknown» Default value of large varchar types in the target table. DEFAULT_NUMBER 0 Default value of numeric types in the target table. DEFAULT_SHORT_CHAR - Default value of short varchar (less than ten characters) data types in the target table. DEFAULT_VARIANT R Default value of the fiscal variant type in the target table. GROUP_CURRENCY_CD USD Default value of the group currency type. JDCOMLIB CLTCOM The library (DB2)/schema (Oracle)/user (SQL Server) that stores the J.D. Edwards com files (that is, F0005). JDDATALIB CLTDTA The library (DB2)/schema (Oracle)/user (SQL Server) that stores the J.D. Edwards data files. JDSECLIB CLTSEC The library (DB2)/schema (Oracle)/user (SQL Server) that stores the JDE Security Library. LOCAL_CURRENCY_CD USD Default value of the local currency code. Local currency code identifies the currency of the company and is used as the From Currency Code for currency conversion. If the multi-currency option is not set, then this is the default for the local currency. MART_BEGIN_DATE Data warehouse begin date. MART_END_DATE Data warehouse end date. MONTHSTOHOLDMANUA LTABLES 60 Default value in months to hold manual tables. SEPARATOR_CHAR * Default value that is used by DecisionStream to concatenate fields. Used to build natural keys for lookups and for DIM_ID values. SOURCE_DB DB2 Source database type. TARGET_DB MSSQL Target database type. 28 Cognos Analytic Applications for J.D. Edwards (R) for J.D. Edwards (R)