Enterprise Inventory and Service-Level Optimization Analytics

Transcription

1 Enterprise Inventory and Service-Level Optimization Analytics Installation Guide version 6.10SP3P3

2 2016 SAP SE, All Rights Reserved. This manual, as well as the software described herein, is furnished under license and may be used or copied only within the terms of such license. The content of this manual is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by SAP SE. SAP assumes no responsibility or liability for any errors or inaccuracies that may appear in this documentation. Except as permitted by license, no part of this document may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recorded, or otherwise, without the prior written permission of SAP. Revision

3 Table of contents Introduction Prerequisites About this guide Chapter 1: Installing the Data Mart Data Mart Installation Chapter 2: Installing and configuring EIS Analytics files Installing the EIS Analytics components Configuring Data Services for EIS Analytics Data Mart Importing EIS Analytics files into the Business Objects Universe Creating a Business Objects User Set up server and sender for EIS Analytics alerts Setup whether to consider batch size in replenishment workflow Setup whether to have the ROP in the replenishment workflow consider unshifted merchandising stock Setup for replenishment workflow Configuring Dashboard access to EIS Configuring EIS Analytics for the EIS portal Setting up supply chain-specific attributes in the EIS Analytics universe Configuring an external data source

4 SAP Enterprise Inventory and Service-Level Optimization Analytics Installation Guide Trigger ELT to complete the Data Mart Transfer EIS Analytics batch jobs Scheduling batch jobs to run on a periodic basis Troubleshooting ETL jobs Updating EIS MIPO scenario names to ensure dashboards display properly InfoView preference update (browsers using JRE7 only) Accessing EIS Analytics with SAP Business Objects Mobile app Chapter 3: Maintaining EIS Analytics Dashboards Customizing the EIS Analytics dashboards Changing the Minimum Inventory Target calculation Changing the Maximum Inventory Target calculation Changing the Bias calculation Changing the Demand Analytics dashboard gauge thresholds Changing the Demand Analytics dashboard graph colors Changing the Demand Analytics Sales-Forecast Numerical Spinner value Changing the Performance Overview dashboard gauge thresholds Changing the Performance Overview colors Changing the Supply Analytics dashboard gauge thresholds Changing the Threshold for Planned Lead Time Changing the Supply Analytics colors Changing the dashboard slicer attributes Chapter 4: User Group Privileges SOPS Reader SOPS Writer SOPS Administrator Chapter 5: Reject Message Definitions Reject Message Definitions

5 Introduction The SAP Enterprise Inventory and Service-Level Optimization (EIS) Analytics Module lets you monitor supply chain performance through intuitive visualizations of key product indicators and metrics derived from Enterprise Inventory and Service-Level Optimization. This document describes how to install the EIS Analytics application. It includes information about the prerequisites required to use the EIS Analytics application with Enterprise Inventory and Service- Level Optimization. Prerequisites Before installing this release, the following software components must be installed and configured: Server: SAP EIS 6.10, using Oracle 11g (EE or SE) SAP BusinessObjects 4. 1(BOBJ 4.1 ) SAP BusinessObjects Web Intelligence (WebI) SAP Data Services (DS) 4.2 SAP Live Office Client: Adobe Flash 11, compatible with BOBJ Oracle Java JRE, compatible with BOBJ 5

6 SAP Enterprise Inventory and Service-Level Optimization Analytics Installation Guide Note: For installation of the SAP Enterprise Inventory and Service-Level Optimization (EIS) application server, refer to the EIS Installation and Upgrade Guide for supported stacks and installation details. For installation on a non-sap Enterprise Inventory and Service-Level Optimization application server, refer to the SAP Business Objects XI Enterprise documentation for supported stacks and installation details. About this guide The SAP Enterprise Inventory and Service-Level Optimization Analytics Installation Guide describes the installation procedures and configuration settings needed to enable the Analytics and Intelligence Module, and a data dictionary detailing the Data Mart tables. This guide contains the following chapters: Chapter 1: Installing the Data Mart tables Chapter 2: Installing and configuring the EIS Analytics application Chapter 3: Maintaining the EIS Analytics application Chapter 4: User Group Privileges Chapter 5: Reject Message Definitions Intended audience The primary audience for this guide are IT personnel, Business Intelligence administrators, and database administrators (DBAs) at customer sites. Their focus is installing, configuring, and maintaining the third-party analysis software used to interface with the EIS Analytics application. In addition, IT staff and DBAs may be responsible for configuring and maintaining a data loading process that occurs on a regularly scheduled basis. The Data Store and its associated EIS Analytics Data Mart can be configured to update automatically whenever MIPO scenario data gets updated. SAP Support can guide you in setting up automated processes, based on your company s infrastructure. 6

7 Introduction Notation conventions This section describes notation and formatting conventions used throughout the documentation. These conventions have been defined and are used to provide consistency and clarity as well as to aid visual recall of information. Convention Any item that appears literally on the computer screen such as a text field label, a menu name, or a button label is printed in boldface. Information that should be entered exactly as shown is also printed in boldface. Keyboard keys are indicated by the text of the key face displayed in upper case and small caps. Key combinations include multiple keys. A plus sign connects names of keys that should be pressed simultaneously. Information you enter that is specific to your own circumstances, such as your user name or a specific unit cost, is designated by an italic variable name. Italic text is also used to indicate a new term or concept. Example click Go click LOGOUT Type 2 in the Factor by text box. ALT SHIFT CTRL+ALT+DELETE SHIFT+S Type User Name and press ENTER. lead time, also called total lead time This symbol indicates information that emphasizes or supplements important points of the main text. This symbol indicates a note of caution. Items that warrant a note of caution include warnings that could protect against a loss of data or other undesired behavior. Table 1: Notation conventions used in this document 7

8 SAP Enterprise Inventory and Service-Level Optimization Analytics Installation Guide 8

9 Chapter 1: Installing the Data Mart This chapter describes the specific configuration items related to the Data Mart data module. The Data Mart contains a subset of EIS MIPO data and resides in the Data Store schema. Additional Data Mart information resides on the MIPO schema. The Data Mart configuration includes the following: Data Mart data model on Data Store schema Data Mart procedure and synonym updates on MIPO schema Note: For information on the Data Store setup and configuration requirements, refer to the EIS Installation and Upgrade Guide. 9

10 Enterprise Inventory and Service Level Optimization Analytics Installation Guide Prerequisites: Before installing the Data Mart, ensure that Oracle 11g software has been installed on the database server. It is also recommended that all servers in a customer s environment support reverse DNS lookup. Data Mart Installation The Data Mart tables reside as part of the Data Store schema. Data Store consists of an Oracle database schema that is installed as part of the MIPO database instance. Note: For information on Oracle setup and requirements related to EIS applications, refer to the EIS Installation and Upgrade Guide. Installing EIS Analytics Data Mart tables on the Data Store schema This section describes how to install the EIS Analytics Data Mart tables to the Data Store database schema (SOPS_DATASTORE) from a Windows or UNIX machine connected to the Oracle database server. Prerequisites: Gather the following information in preparation for the schema installation process: Name of the database instance created for the MIPO schema Full path name of the directory containing the schema installation files (e.g., /temp/ datastore) Password for the user SYSTEM Step 1: Copy Installation files to database server Copy the EIS Analytics Data Mart installation files from the installation media to the database server. These files are located under the \AnalyticsAndIntelligenceModule<version>\Database\Datamart directory (where <version> represents the release number for the software application). Make sure you maintain the directory structure under the \Database directory. Step 2: Update the Installation SQL script Use a text editing tool to open the install.sql script you copied onto the database server. You will see the following configuration settings: DEFINE DATASTORE_SCHEMA='SOPS_DATASTORE' DEFINE MIPO_SCHEMA='SOPS_MIPO' 10

11 Chapter 1: Installing the Data Mart DEFINE DATASTORE_DATA_TS='DATASTORE_DATA' DEFINE DATASTORE_INDEX_TS='DATASTORE_INDEX' DEFINE TEMP_TS='TEMP' Edit any configuration settings to match your current MIPO settings and save your changes. Step 3: Run the Installation SQL script Start the Command Prompt application and use the Change Directory command (cd) to access the database server and go to the location where you copied the installation files. Log on the SQL*Plus as system administrator with system ID (e.g., and password. If you are installing the Data Store, run the Data Store Installation script by typing the following at the command If you are upgrading the Data Store, run the Data Store Upgrade script by typing the following at the command The script will notify you when the Data Mart install or upgrade is complete. For any error messages displayed during installation, see the datastore_install.log or datastore_upgrade.log file for more information. Exit SQL*Plus by typing exit at the command prompt. Note: If the log files contain unknown errors, contact SAP Support. Errors can be generated when the installation script attempts to drop tables, sequences, indexes, or views that do not exist. It is safe to ignore these errors. 11

12 Enterprise Inventory and Service Level Optimization Analytics Installation Guide 12

13 Chapter 2: Installing and configuring EIS Analytics files T his chapter provides instructions for installing the EIS Analytics application on an SAP Business Objects server. For more information about SAP Business Objects requirements see the SAP Help Portal. Prerequisites: Before installing the EIS Analytics application, ensure that the following software versions have been installed on the SAP Business Objects web server: SAP BusinessObjects Enterprise (BOE) XI 3.1 SP3 or BOE 4.0 SAP Data Services (DS) Professional 4.1 SP1 Additionally, EIS 6.10 must be installed and configured on the application server. It is also recommended that all servers in a customer s environment support reverse DNS lookup. Note: You can import the EIS Analytics 3.1 BIAR file into SAP Business Objects 4.X. For more information, see Importing the BIAR File to Business Objects 4.X on page

14 Enterprise Inventory and Service-Level Optimization Analytics Installation Guide Installing the EIS Analytics components The EIS Analytics application consists of customized files designed to push EIS data from the Data Store into the EIS Data Mart, so it can be transformed into the EIS Analytics Business Objects Universe for analysis through customized business intelligence tools. These files include SQL objects, ETL files, and business intelligence archive (BIAR) files containing the EIS Analytics Universe, dashboards and web intelligence (WebI) reports. Prerequisites: An Oracle user account must be created and configured to own the EIS Analytics repository before the installation. Refer to the SAP Business Objects and Oracle documentation for permissions/roles associated with an Oracle account connected to the SAP Business Objects environment. To install the EIS Analytics components: 1. Access the installation media and go to the AIM<version>/ directory (where <version> is the EIS Analytics version number). 2. The EIS Analytics application is contained in a.zip file. Unzip the file and copy the associated EIS Analytics files to the EIS directory on the web application server. The files should be organized by the following sub-directories: AIM<version>/BOBJ/EIS.biar AIM<version>/Webserver/launch_dashboard.jsp AIM<version>/Webserver/crossdomain.xml AIM<version>/DataServices/DataMart-ETL.atl AIM<version>/DataServices/DM_Control.xls Configuring Data Services for EIS Analytics Data Mart The SAP Data Services Management Console lets you create a local repository associated with the Data Mart in order to provide a connection between the Universe Designer and the Data Mart tables, as well as manage batch jobs, real-time jobs, and profile tasks. Creating a local repository in Data Services 4.X To create a local repository for the EIS Analytics application, log on to the Data Services Management Console and perform the following steps: 1. Start the Data Services Repository Manager. 2. Log on as an administrator. 3. In the Data Services Repository Manager dialog box, set the following information: Repository type Local Database type Oracle 14

15 Chapter 2: Installing and configuring EIS Analytics files Database version Oracle 11g Hostname SID User name Password 4. Click Create. 5. If the repository already exists, you ll be given the option to upgrade the existing repository. Click Upgrade to upgrade. Register the Repository in Central Management Console for DS 4.X To register the repository in the Central Management Console, perform the following steps: 1. Log onto the SAP BusinessObjects Central Management Console using an administration account. 2. From the drop-down menu, select Data Services. 3. Right-click on the Repositories folder and select Configure repository. 4. Enter the following information for the Analytics repository: Repository Name Database Type (Oracle) Database Server Name SID (same that you entered when creating the repository) User Name (same that you entered when creating the repository) Password (same that you entered when creating the repository) 5. Click Save. Creating a local repository in Data Services 3.2 To create a local repository for the EIS Analytics application, log on to the Data Services Management Console and perform the following steps: 1. Start the Data Services Management Console. 2. Log on as an administrator. 3. From the Home page, select Administrator. 4. From the Administrator directory tree on the left side of the screen, select Management > Repositories. 5. Click Add. 6. Enter the following information: 15

16 Enterprise Inventory and Service-Level Optimization Analytics Installation Guide Repository Name that identifies its association with the EIS Analytics application. Database type > Oracle. Machine name identifying the database server. Database port for Oracle server connectivity. Service name/.sid identifying EIS database. Enter the Oracle username and password for the repository schema. 7. Click Apply. The new repository should appear on Repositories screen. Add the EIS Analytics repository to the Job server To add the EIS Analytics repository to the Job server, log on to the Data Services Server Manager and perform the following steps: 1. Start the Data Services Server Manager. 2. Click Configuration Editor. 3. From the Job Server Configuration Editor, select JobServer record and click Edit. 4. To add a repository, click Add. a. Select Oracle as the Database type b. Enter the database connection name c. Enter the Oracle username and password for the repository schema d. click Apply. 5. Click OK to exit Job Server Properties dialog box. 6. Click OK to exit the Job Server Configuration Editor dialog box 7. Click Restart to exit Job Server Configuration Editor and restart the Data Service. The repository should now be available on the batch job schedule. Importing EIS Analytics files into the Business Objects Universe The EIS Analytics application includes customized files designed for the Business Objects Universe. These files must be imported into the Business Objects Enterprise and Data Services respectively. Prerequisite: When upgrading from a previous installation of the EIS Analytics application, you must first delete the AIM Dashboard.swf file before performing the import process, as this file will not be overwritten by the import. The Dashboard file can be deleted through the InfoView web application. 16

17 Chapter 2: Installing and configuring EIS Analytics files Importing the the LCMBIAR Override File in Business Objects 4.X If you re upgrading to EIS Analytics , you must override the LCMBIAR file: 1. Log on to the Central Management Console (CMC). 2. Under Manage, click Promotion Management. The Promotion Jobs tab opens. 3. Click Settings and choose Manage Systems. The Promotion Management for SAP Business Objects Enterprise-Manage Systems window displays. 4. Click Add and enter the Host Name, Port Number, Display Name, and, optionally, Description of your system. Verify that the Mark as Origin box is not selected. 5. Click OK. 6. From the Import drop-down, click Override File. 7. Select either the EIS_Override.lcmbiar file, then click OK. 8. Click Override Settings. 9. If the window indicates that the system is logged into the CMS system (or the Type is not Destination), click Log Off and log onto the Destination system. 10. Click Connection Override, select the checkbox for smartopsdb data connection, then click Edit. The Edit Connections Properties dialog box displays. 11. Enter all of the connections properties for your system and click Done. 12. Click Status next to the smartopsdb data connection and select Active. 13. Click Save. 14. Click the QaaWS Override tab, select the smartops qaaws override checkbox, and click Edit. 15. In the QaaWS Properties Service URL dialog box, enter the web service address, port, and web service provider access URL, and click Done. Note: If the access URL is not known, go to the CMC Home window, select Applications from Manage tasks. From the Applications window double click the Web Service application name. The Access URL is found on the Properties tab. 16. Click Status next to the smartops qaaws override and select Active. 17. Click Save. 18. Click Close. 17

18 Enterprise Inventory and Service-Level Optimization Analytics Installation Guide Importing the LCMBIAR File to Business Objects 4.X If you re installing or upgrading EIS Analytics or higher, you will need to import an LCMBIAR file to BOBJ 4.X: 1. Log on to the Central Management Console (CMC). 2. Under Manage, click Promotion Management. The Promotion Jobs tab opens. 3. From the Import drop-down, click Import file. 4. Select either the EIS_LCMBIAR (for installing as a new customer) or EIS_Upgrage.LCMBAIR (for upgrading) file, then click OK. 5. Log on to your destination CMC and then click Create. The promotion job is created. 6. In the Promotion Jobs tab, select the checkbox next to the new job and click Promote. The status must be Success. 7. When the Promote screen displays, click Test Promote on the left-hand side, then click the Test Promote button. 8. Once the test promote has run, click on the Promote button. Importing the BIAR File to Business Objects 4.X You can run EIS Analytics on Business Objects 4.x, although EIS Analytics does not take advantage of the newer features available in the 4.x releases. To import the BIAR file into BusinessObjects 4.X: Step 1: Choose the source and destination and select objects to import 1. Log on to BI Launch Pad on the Business Objects 4.x server and delete any EIS Analytics-related SWF files. There are multiple SWF files located under Public Folders -> SmartOps -> AIM - Analytics and Intelligence Module -> Dashboards and Public Folders -> SmartOps -> AIM - Analytics and Intelligence Module --> Dashboards Support Materials. 2. Log into the Business Objects 4.x server 4.x Server using local administrator credentials. 3. Copy the BIAR file to 4.x server. 4. Launch the Business Objects Upgrade Management Tool. 5. Click Incremental Upgrade. 6. Click Next. 7. Choose a BIAR to Live upgrade. 8. In the Source section, use the Browse [...] button to enter a location for the file. 18

19 Chapter 2: Installing and configuring EIS Analytics files 9. In the Destination section, enter the following information: CMS Name: Your Business Objects server name. Username: The administrator username used to access the Business Objects server. Password: The administrator password to access the Business Objects server. 10. Click Next. 11. Verify the following are selected in the list box: Corporate Categories Custom Access Levels Folders and Objects, including the sub-folder SmartOps Universes, including the sub-folder SmartOps Universes (information design tool), including the sub-folder SmartOps Users and User Groups. 12. Click Next. 13. Click Start. 14. Click Close. Step 2: Assign security 1. Log onto the SAP BusinessObjects Central Management Console using an administration account. 2. From the Organize column, select Folders. 3. From the left side of the Folders screen, right-click on All Folders and select Properties. 4. In the User Security: Root Folder screen, click User Security. 5. Click Everyone, and then click the Assign Security button. 6. On the Assign Security screen, ensure that the Inherit from Parent Folder and the Inherit From Parent Group boxes are checked and that the View is available in the Available Access Levels list. 7. Click OK. 8. Click Close. 9. Right-click on the SmartOps folder and select User Security. 10. In the User Security: Smartops screen, click Everyone, and then click the Assign Security button. 11. Click the Remove Access button, and then click OK. 12. Click OK in the confirmation dialog box. 13. Click Close. 19

20 Enterprise Inventory and Service-Level Optimization Analytics Installation Guide 14. From the tabs on the left, click on the Universes icon (a multi-colored starburst). 15. In the Universes screen, right-click on the SmartOps folder and select User Security. 16. In the User Security: Smartops screen, click Everyone, and then click the Assign Security button. 17. Click the Remove Access button, and then click OK. 18. Click OK in the confirmation dialog box. 19. In the User Security: Smartops screen, click Universe Designer Users, and then click the Assign Security button. 20. Click the Remove Access button, and then click OK. 21. Click OK in the confirmation dialog box. 22. Click Close. 23. From the tabs on the left, click on the Connections icon (green pipes). 24. On the Connections screen, right-click on smartopsdb, and select User Security. 25. In the User Security: smartopsdb screen, click Everyone, and then click the Assign Security button. 26. Click the Remove Access button, and then click OK. 27. In the User Security: smartopsdb screen, click Universe Designer Users, and then click the Assign Security button. 28. Click the Remove Access button, and then click OK. 29. Click OK in the confirmation dialog box. 30. Click Close. Step 3: Remove SmartOps user access to other Universes 1. Log onto the SAP BusinessObjects Central Management Console using an administration account. 2. Click Universes. 3. Right-click a non-smartops folder or Universe, and select User Security. 4. On the User Security screen for that folder or Universe, click SOPS Reader, and then click the Assign Security button. Note: If SOPS Reader does not appear, you ll need to manually add the user groups. See Step 1: Setting up Security on page 28 for more information. 5. Click the Remove Access button, and then click OK. 6. Click OK in the confirmation dialog box. 20

21 Chapter 2: Installing and configuring EIS Analytics files 7. Click Close. 8. Repeat steps 3 through 6 for all other non-smartops folders and Universes. Importing BIAR file into BusinessObjects 3.1 To import the BIAR file, perform the following steps: Step 1: Choose source and destination 1. Start the Import Wizard. (Start --> All Programs --> BusinessObjects XI > BusinessObjects Enterprise --> Import Wizard). 2. Click Next to get to the Source Environment step. 3. For the Source Environment, enter the following: Source: select Business Intelligence Archive Resource (BIAR) file from the dropdown BIAR file: Use the Browse [...] button to enter a location for the file. 4. Click Next. 5. For the Destination Environment, enter the following information: CMS Name: Your Business Objects server name and port number (i.e., server_name:6400). Username and Password: The administrator username and password to access the Business Objects server. Authentication: Select Enterprise from the dropdown. 6. Click Next. You will now be on the Select objects to import step. Step 2: Select objects to import 1. On the Select objects to import dialog box, click Clear All. 2. Individually select the following items in the list box: Import users and user groups -->Import application rights Import users and user groups -->Import root folder rights Import Corporate Categories Import Folders and objects --> Import application folders and objects. Import universes Import custom access levels 3. Click Next 4. On the Import scenario dialog box, ensure that the following is selected: Use the object's unique identifier to determine whether it already exits in the destination system. 21

22 Enterprise Inventory and Service-Level Optimization Analytics Installation Guide Update the destination object. In case of name conflict, rename it. 5. Click Next. 6. On the Incremental import dialog box, UNCHECK the following: Overwrite Connection Contents. 7. Click Next. 8. On the Users and groups dialog box, click Clear All. 9. Deselect the Show groups hierarchically check box. 10. Shift-Click the following: SOPS Reader SOPS Writer SOPS Administrator 11. Click Next. 12. On the Custom Access Levels dialog box, ensure that the following are selected: SOPS Administrator SOPS Reader SOPS Writer 13. Click Next. 14. On the Categories dialog box, click Next. 15. On the Folders and objects dialog box: Check the SmartOps folder (everything under should be selected it as well). Leave the Import all instances of each selected object checkbox un-checked. 16. Click Next. 17. On the Select application folders and objects dialog box, click Clear All. 18. Click Next. 19. On the Import options for universes and connections dialog box, click the radio button for the third Import option (it has the text Import the universes and connections that the selected Web Intelligence... ). 20. Uncheck the Keep universe overloads... option. 21. Click Next. 22. On the Universe folder and universes dialog box: Check the SmartOps folder (everything under should be selected it as well). 23. Click Next. 22

23 Chapter 2: Installing and configuring EIS Analytics files 24. On the Import options for publications dialog box, select the Do not import recipients option. 25. Click Next. 26. Click Next again on the A note on importing reports dialog box. 27. Click Finish. 28. A popup appears when the import is completed. Click Done. Step 3: Assign security 1. Log onto the SAP BusinessObjects Central Management Console using an administration account. 2. From the Organize column, select Folders. 3. From the left side of the Folders screen, right-click on All Folders and select Properties. 4. In the User Security: Root Folder screen, click User Security. 5. Click Everyone, and then click the Assign Security button. 6. On the Assign Security screen, ensure that the Inherit from Parent Folder and the Inherit From Parent Group boxes are checked and that the View is available in the Available Access Levels list. 7. Click OK. 8. Click Close. 9. Right-click on the SmartOps folder and select User Security. 10. In the User Security: Smartops screen, click Everyone, and then click the Assign Security button. 11. Click the Remove Access button, and then click OK. 12. Click Close. 13. From the tabs on the left, click on the Universes icon (a multi-colored starburst). 14. In the Universes screen, right-click on the SmartOps folder and select User Security. 15. In the User Security: Smartops screen, click Everyone, and then click the Assign Security button. 16. Click the Remove Access button, and then click OK. 17. In the User Security: Smartops screen, click Universe Designer Users, and then click the Assign Security button. 18. Click the Remove Access button, and then click OK. 19. Click Close. 20. From the tabs on the left, click on the Connections icon (green pipes). 21. On the Connections screen, right-click on smartopsdb, and select User Security. 23

24 Enterprise Inventory and Service-Level Optimization Analytics Installation Guide 22. In the User Security: smartopsdb screen, click Everyone, and then click the Assign Security button. 23. Click the Remove Access button, and then click OK. 24. In the User Security: smartopsdb screen, click Universe Designer Users, and then click the Assign Security button. 25. Click the Remove Access button, and then click OK. 26. Click Close. Step 4: Remove SmartOps user access to other Universes 1. Log onto the SAP BusinessObjects Central Management Console using an administration account. 2. Click Universes. 3. Right-click a non-smartops folder or Universe, and select User Security. 4. On the User Security screen for that folder or Universe, click SOPS Reader, and then click the Assign Security button. 5. Click the Remove Access button, and then click OK. 6. Click Close. 7. Repeat steps 3 through 6 for all other non-smartops folders and Universes. Editing Universe Connections To edit the EIS Analytics universe connections, perform the following steps: 1. Start the Universe Design Tool. 2. Log on as an administrator. 3. From the main menu, click File > Import. 4. From the Import Universe dialog box, click Browse to locate the \SmartOps\ folder, then click OK. 5. Hightlight AIMTemplate under Available Universes, then click OK. Universe successfully imported message appears. 6. From the main menu, click Tools > Connections. 7. On the Wizard Connection dialog box, highlight smartopsdb and click Edit. 8. On the Edit smartopsdb Connection dialog box, enter the following information: Oracle username and password for the Data Store schema. Service name/.sid identifying EIS database. 9. Click Next. 10. Click Next. 24

25 Chapter 2: Installing and configuring EIS Analytics files 11. Click Finish. 12. Click Finish to go back to Universe Design Tool. 13. Click File > Export. 14. Click OK to save it back to the Universe server. Deleting existing jobs before importing the new ATL Before you import the ATL, you must delete any existing jobs. Note: If you have jobs scheduled, you must unschedule the jobs before you delete them. To delete existing jobs, perform the following steps: 1. Start the Data Services Designer. 2. Use an account with administrator privileges to log on to the EIS Analytics repository. 3. From the main menu, click Tools > Object Library. 4. Click the Jobs tab at the bottom of the screen. 5. Expand Batch Jobs. 6. Select all the jobs that begin with J_Smartops (hold the shift key to select multiple jobs). 7. Right click on a selected job and select Delete. 8. In the dialog box, click Yes. Deleting the previous ETL before importing new ATL Before you import the Data Services ATL file, you should delete the ETL of the previous version. Note: If you have a custom ETL for loading the Inventory History Table, export the ETL and re-import the ETL after upgrading. 1. Start the Data Services Designer. 2. Use an account with administrator privileges to log on to the EIS Analytics repository. 3. Click the Projects tab at the bottom of the screen. 4. From the main menu, click Tools > Project Area. 5. Right-click on Smartops_Senario_Load. 6. Click Delete. 25

26 Enterprise Inventory and Service-Level Optimization Analytics Installation Guide 7. In the dialog box, click Yes. Importing Data Services ATL file To import the ATL file, perform the following steps: 1. Start the Data Services Designer. 2. Use an account with administrator privileges to log on to the EIS Analytics repository. 3. From the Tools menu, select Import From File. 4. Navigate to the location of the DataMart-ETL.atl file. 5. If you are using Data Services 4.X, when prompted for a password, type password and click OK. 6. Accept the standard warning by clicking OK. 7. There is a message indicating that the import has succeeded. Note: You can see the objects in the lower left portion of the window as they are loaded (called the Local Object Library). These objects are located in the Projects tab, Jobs tab, Workflows tab, Dataflows tab, Transforms tab, Datastores tab, Formats tab, and Custom Functions tab. Configuring the ETL for use Once the ATL file has been imported into the Data Services Designer, do the following: 1. From the Data Services Designer, click the Datastores tab located at the bottom of the Local Object Library area. 2. From the Tables directory tree, right click on DataMart and select Edit. 3. From the Edit Datastore dialog box, click Advanced >>. 4. Click Edit. 5. From the Configurations for Datastore dialog box, Click the Create New Configuration icon. 6. Enter the configuration name. 7. Select the database type. 8. Select the database version as Oracle 11g. 9. Click OK. 10. Under Connection, do the following: a. Set the Default configuration to Yes. b. Enter the User name of the database (the same as used for the DataStore schema). 26

27 Chapter 2: Installing and configuring EIS Analytics files c. Enter the Password of the database (the same as used for the DataStore schema). 11. Under Aliases, enter the Alias Name. 12. Click Apply. 13. Click OK. Repeat steps 1-13 for the Internal tables, but point to your MIPO schema. Setting up the attribute configurations for Data Services Once the ATL file has been imported into the Data Services Designer, you can set up the attribute configurations for your supply chain s items and locations. These attribute settings are used to populate the dashboard slicers that provide drill-down capability through filtering data. Step 1: Add attribute information to DM Control spreadsheet 1. Navigate to the EIS Analytics installation files to locate the following: AIM<version>/DataServices/DM_Control.xls 2. Open DM_Control.xls with MS Excel. 3. Click on the CTRL_Item_Attrib tab. 4. Enter up to 10 item attribute names in the ATTRIB_NAME column. 5. Click on the CTRL_Loc_Attrib tab. 6. Enter up to 10 location attribute names in the ATTRIB_NAME column. 7. Save your changes. Step 2: Associate DM Control spreadsheet to Data Services 1. Log on to the Data Services Designer as an administrator. 2. From the main menu, select Tools > Substitution Parameter Configurations Use the Substitution Parameters editor to add the DM Control spreadsheet file path to the substitution variable called $$Control_Directory_src (e.g., C:/DataMart). Step 3: Setup the System Configurations 1. Log on to the Data Services Designer as an administrator. 2. From the main menu, select Tools > Editing the System Configurations. 3. Click on the Title bar of the Edit System Configurations window and type thr name for the system. 4. Select the system name from the drop-down menu for each of the following that corresponds to that system: Substitution Parameter, DataMart, and Internal. 5. Click OK. 27

28 Enterprise Inventory and Service-Level Optimization Analytics Installation Guide Step 4: Copy DM Control spreadsheet to BusinessObjects server 1. Copy the DM Control spreadsheet to the local file system on the Data Services server. Step 5: Run J_SmartOps_Setup_Ctrl job You must run the J_SmartOps_Setup_Ctrl job to load the attribute configurations. 1. Log on to Data Services Management Console as an administrator. 2. Click Administrator. 3. From the Administrator directory tree, click to expand Batch. 4. Click on the EIS Analytics repository node. 5. Under the Batch window, click the Batch Job Configuration tab. 6. Locate the J_SmartOps_Setup_Ctrl job, then click Execute. 7. Under Execute Batch Job, click Execute. Creating a Business Objects User If you do not already have Business Object Users created, you will need to create users to access the EIS Analytics application. Step 1: Setting up Security Before you create users, you need to add the SmartOps user groups to the universe and folders. 1. Log onto the SAP BusinessObjects Central Management Console using an administration account. 2. Either choose Folders from the drop-down, or click the Folders icon. 3. Right-click on All Folders and select Properties. 4. Click User Security. 5. If the SOPS Administrator, SOPS Reader, and SOPS Writer are not on the list, click Add Principals. 6. Click Group List. 7. Add the SOPS Administrator to the Selected users/groups column by clicking the arrow button. 8. Click Add and Assign Security. 9. Click SOPS Administrator and move it to the Assign Access Levels column by clicking the arrow button. 10. Click Apply, then OK. 11. Repeat steps 7 to 10 for SOPS Writer and then SOPS Reader. 12. Click Close. 28

29 Chapter 2: Installing and configuring EIS Analytics files 13. Right-click on the SmartOps folder and select Properties. 14. Repeat steps 4 to 12 for the SmartOps folder. 15. From the drop-down, select Connections, right-click on the Connections folder and repeat steps 4 to 12 for the Connections folder and the smartopsdb connection. 16. From the drop-down, select Universes. 17. Right-click on SmartOps and select Universe Security. 18. Click Add. 19. Click Group List. 20. Click SOPS Administrator and move it to the Selected users/groups column by clicking the arrow button, and click OK. 21. Close the window. 22. Right-click on Smartops again, and select User Security. 23. Repeat steps 5 to 12. Step 2: Creating Business Object Users To create a Business Object user: 1. Log onto the SAP BusinessObjects Central Management Console using an administration account. 2. Select Users and Groups either via the drop-down menu or by clicking the Users and Groups icon. 3. Click Manage > New > New User. 4. Enter an Account Name (this is the User ID). 5. Enter a Password and Confirm Password, then select the appropriate password option checkboxes for your organization s security policy. 6. Optionally, enter the Full Name, and Description for the account. 7. Click Create & Close. 8. Click User List. 9. Right-click on the user you just created, and select Join Group. 10. Select the appropriate user group (SOPS Administrator, SOPS Writer, or SOPS Reader), then click the arrow to move the selected User Group to the Destination Groups column. Set up server and sender for EIS Analytics alerts To set up for the Job server, log on to the Data Services Server Manager and perform the following steps: 29

30 Enterprise Inventory and Service-Level Optimization Analytics Installation Guide 1. Start the Data Services Server Manager. 2. In the SMTP settings for smtp_to function section, type the following: In the Server field, type the name of the SMTP server. In the Sender field, type the address to use as the sender of the s. 3. Click Apply. 4. Click Restart to exit Job Server Configuration Editor and restart the Data Service. Setup whether to consider batch size in replenishment workflow As part of the replenishment workflow, the J_SmartOps_Replenishment job can consider batch size when making recommendations for replenishment. To configure whether to consider batch size, you must configure a substitution variable: 1. Log on to the Data Services Designer as an administrator. 2. From the main menu, select Tools > Substitution Parameter Configurations Use the Substitution Parameters editor to add whether you want to enable batch size to the substitution variable called $$SmartOps_Is_Replenishment_Batch_Size_Enabled (i.e., YES or NO) Include YES if you want to consider batch size and NO if you do not. 4. Click OK. Note: If you have replenishment configured, you MUST set this variable. If you do not wish to consider batch size, set the variable to NO. Setup whether to have the ROP in the replenishment workflow consider unshifted merchandising stock As part of the replenishment workflow, the J_SmartOps_Replenishment job can consider unshifted merchandising stock when calculating the reorder point (ROP), which has an impact on replenishment orders. To configure whether to consider unshifted merchandising stock when calculating ROP, you must configure a substitution variable: 1. Log on to the Data Services Designer as an administrator. 2. From the main menu, select Tools > Substitution Parameter Configurations Use the Substitution Parameters editor to add whether you want to consider unshifted merchandising stock when calculating ROP to the substitution variable called $$SmartOps_use_Merc_in_ROP (i.e., YES or NO) If you include YES, then the 30

31 Chapter 2: Installing and configuring EIS Analytics files reorder point is the reorder point plus unshifted merchandising stock. If you include NO, then the reorder point does not include unshifted merchandising stock. 4. Click OK. Note: If you have replenishment configured, you MUST set this variable. If you do not wish to consider unshifted merchandising stock when calculating the ROP, set the variable to NO. Setup for replenishment workflow As part of the replenishment workflow, the J_SmartOps_Replenishment job sends when the job succeeds or fails. To configure to whom to send these s, you must configure two substitution variables: 1. Log on to the Data Services Designer as an administrator. 2. From the main menu, select Tools > Substitution Parameter Configurations Use the Substitution Parameters editor to add the addresses to which you want to send success s to the substitution variable called $$SmartOps_Replenishment_Success_ (i.e., To include more than one address, separate the addresses with a comma (but no spaces). 4. Use the Substitution Parameters editor to add the addresses to which you want to send failure s to the substitution variable called $$SmartOps_Replenishment_Failure_ (i.e., name@mycompany.com) To include more than one address, separate the addresses with a comma (but no spaces). 5. Click OK. 6. Set the replenishment job to run periodically (every five minutes is recommended). For more information about configuring batch jobs to run, see EIS Analytics batch jobs on page 35. Configuring Dashboard access to EIS To configure dashboard access to EIS, perform the following steps: Step 1: Create SmartOps account in Business Objects server Note: Refer to the SAP Business Objects CMC documentation for creating administration accounts. Step 2: Set up external access for EIS Analytics dashboard 1. Log on to the Infoview portal with an administrator account. 2. Under Navigate, click Document List. 3. Expand the Public Folders. 31

32 Enterprise Inventory and Service-Level Optimization Analytics Installation Guide 4. Expand the SmartOps folder. 5. Expand the AIM - Analytics and Intelligence folder. 6. Select the Dashboards folder. 7. Right click the SAP Enterprise Inventory and Service-Level Optimization Dashboard and select Properties. 8. Copy the CUID of the SWF file. CUID looks like: ATNrWyHSbMpPnUXelSa.7DY. 9. On the BOBJ instance for the dashboard, navigate to the location of the launch_dashboard.jsp; for example: c:\program Files (x86)\business Objects\Tomcat55\webapps\InfoViewApp\ launch_dashboard.jsp). 10. Open launch_dashboard.jsp in a text editor. 11. Toward the bottom of the page find the line that starts as follows: String Path = "../../OpenDocument/opendoc/openDocument.jsp?token=" +enterprisesession.getlogontokenmgr().getdefaulttoken()+ "&idocid=aevwcav7r6rjmbwhzhmuxfi&sidtype=cuid&stype=swf" 12. Replace the text between "idocid=" and "&sidtype" to point to the CUID of the SWF file from step Towards the top of the jsp file there is a line "String cms =..."; replace vs-test1 with the cms server name. 14. Save the file. 15. Copy the updated jsp file to the following directory: <BOBJ Install>\Tomcat55\webapps\InfoViewApp 16. Copy the crossdomain.xml file to the following directory: <BOBJ Install>\Tomcat55\webapps\ROOT 17. Restart the Tomcat55 server. Configuring EIS Analytics for the EIS portal The Module Settings feature contains the configuration settings used by the EIS Analytics application to launch from the EIS portal. You can access this module by doing the following: 1. Log on to the EIS application. 2. Select Module Settings under the Settings menu. 3. Select Analytics from the dropdown list. 4. Fill out the appropriate EIS Analytics parameters. A list of the parameters and their functions is provided below. 32

33 Chapter 2: Installing and configuring EIS Analytics files Content Display Parameter: Content Display Required: Yes Behavior: Determines the behavior of launching EIS Analytics through the EIS portal. The EIS Analytics application can either appear in the EIS portal frame or else appear as a separate window. Default: In the Frame Link Parameter: Link Required: Yes Behavior: Defines the location path of the EIS Analytics dashboard (e.g., <localservername>:8080/infoviewapp/launch_dashboard.jsp) Default: N/A Link Type Parameter: Link Type Required: Yes Behavior: Defines whether the link points to an HTML, URL, or JavaScript file. Default: URL When you are finished with your configuration, click OK. If you decide not to implement the changes you made, click Cancel. If the configuration parameter change requires a restart (indicated in the first column), you must stop and restart the application server for your change to take effect. Clients connected to the EIS system must also stop and restart the EIS application for the change to take effect. Setting up supply chain-specific attributes in the EIS Analytics universe At installation time, there are two tasks to be performed in the universe in order to set up attributes for WebI and Dashboard users: 1. Create new, named objects in the AIMTemplate universe so that users can easily understand and use the attributes in reports. 2. Set up the dashboard slicer objects so that the dashboard correctly reflects the six attributes that will be used for filtering. Creating named objects in the AIM template To create the named objects: 1. From the Universe directory tree, click to expand the Item, Location, Node, or Stocking Point folder, depending on which attribute you are currently defining. 2. If some or all of the default attributes packed in EIS Analytics are not going to used, highlight each one and press Delete on the keyboard. 33

34 Enterprise Inventory and Service-Level Optimization Analytics Installation Guide 3. To create a new object in the selected folder, right-click on the folder and select Object. 4. In the Edit Properties dialog box: a. Enter a name for the object in the Name field. This should be the name of the attribute. b. Enter a description of the attribute in the Description field. This will available to any user who uses the universe fields in a WebI report. c. Select the >> button to the right of the Select field. d. Under columns navigate to the field you want to map the attribute to. For example, For the Item attribute listed in position 1 of the spreadsheet you will select DM_ITEM_ATTRIBUTE_N01? ITEM_ATTRIBUTE_NAME. Setting up the dashboard slicer objects To set up the dashboard slicer objects: 1. Open the AIM Template Universe. 2. Navigate Class list to SmartOps DM Dashboard? Slicers. 3. Double click on Slicer Click >> and point is to the Attribute that you want this slicer to point to. 5. To customize the slicer name in the dashboard expand the (+) next to the Slicer X and double click on Slicer X Name. 6. Replace the text under the Select portion of the screen with what you want to display as the slicer name in the dashboard. This value must be inclosed in ( ) tick marks. Configuring an external data source Along with EIS MIPO data, the EIS Analytics Data Mart can also be configured to include data from a secondary external source. To configure the Data Mart for external data, you must log on to the Data Services Designer application and open the EIS Analytics Template. See the SAP Business Objects Data Services Designer documentation for more information about the application. To configure the Data Mart for an external data source: 1. Log on to Data Services Designer with your EIS Analytics administration account. 2. Under the Local Object Library, select the Data Flow tab. 3. Click to expand the Data Flows folder. 4. Double click the DF_Stg_Inventory_History object to open the blank data flow node in the Deisgner workspace. 34