So how do we set it up. It is quite simple. Let us say we have a report that shows the internet sales orders by country as shown in the report below.

Now I want to create a publication such that the sales administrators for each of the regions get the report for their respective territories. So first I set up another report (called recipient report) which list all the users and their email addresses as shown below.

Instead of hardcoding the users I have decided to make it very parameterized by using the database and crystal reports. In a database table I maintain the contact details for each of sales administrator and the territories that they manage.

This approach allows me to change the distribution at any time without having to worry about modifying any of the reports or scheduled jobs. Now using Crystal reports I have developed the report shown above, which is what I am going to use as the input for the scheduled job.

Now comes the process of setting up the scheduled job. In CMC (or Infoview) right click on the folder where you want to save the job and create a new publication job.

Now give the job a name and also select the report that you want to send to your users.

The next step is setting up the recipients of this report. You would use Enterprise Recipients if you wanted to send the report to the users of the BusinessObjects system. However this is not mandatory. As shown below you can also email the report to other users who do not have access to your BusinessObjects server. These could be your employees or even your customers/business partners.

With Dynamic recipients I can email reports to anyone as long as the mail server information is setup correctly in my BOE system. You would need to set this up in a couple places and I will cover this in a later post. For now assuming it is setup we can use the recipient report created earlier and map the user name and emails from that report.

The next step is personalization. I want the sales administrator for Australia to only get the orders from Australia. This is setup in the personalization section of the job. In this case the report is grouped by DimGeography.EnglishCountryRegionName and I use that split the report.

As shown above I can use the country name from the report and mapping to the country name for the recipient I am instructing the job to split the report by  DimGeography.EnglishCountryRegionName and use the Recipient Mapping column to deliver to the right user.

After setting the other aspects such as format and schedule, you can go ahead and test this publication job. You can either deploy it directly or you can test it first. I would recommend testing it, whereby you can give your email address and the job would run but instead of emailing the reports to the users it would be delivered to you.

That’s all there is to setting up publications. Now coming to setting up the mail servers, there are a couple of services for which we would need to set the email servers. The easiest way to get it to work is to first use a local email server to test the functionality and then moving to the corporate mail server. You would need to setup email as a destination for the following

• Adaptive Job Server
• Destination Job Server
• Program Job Server
• Publication Job Server
• Crystal Reports Job Server

For each of the service right click and select destination as shown below

And set the details for the email server.

Click here to download the video

So how can you build something like this. It is actually quite simple as you can see in the video below.

Click here to download the video

Combining this with the live office functionality discussed in the last post should allow you to build really powerful and interactive dashboards. You can download a more complete example from here.

1. It is only available as part of BusinessObjects Edge/Enterprise (BOE). Crystal reports server (CRS) users do not have access to it.
2. Can be confusing for the end user

Live Office is a great utility that comes as part of CRS and BOE and allows embedding reports or report parts within Microsoft Office documents. It is compatible with excel, word and PPT and allows creating live refreshable documents directly within MS Office.

Click here to download video

As shown in the video above the process of creating a live document is quite straightforward. Now we know that XCelsius works with excel documents and using live office we can create a live excel documents. So putting these together we can now create a live dashboard which uses an existing crystal reports to fetch data from the database.

Click here to download video

Using this technique it becomes quite easy for end users to pickup existing reports that already contain the data needed by the dashboard and quickly create live dashboards.

To download HD videos of this post please vi

Let’s get started. The first pre-requisite for map content to work is the spatial data. In 11g, this is available from NAVTEQ in the form of the file SampleApp_Navteq_dmp.zip (approx 127MB). This file contains an Oracle Database export file name obiee_navteq.dmp

We’ll have to start with creating a navteq user in the Oracle Database and loading the dmp file.

Start a SQL*Plus session to the Oracle Database as a user with system or DBA privileges.
Run the script OBIEE_NAVTEQ_USER.SQL located in the unzipped folder. 
For example, SQL> @OBIEE_NAVTEQ_USER.SQL;
Once the script has executed, verify that you can successfully connect to the newly created user
obiee_navteq/obiee_navteq.

Note: The OBIEE_NAVTEQ user creation scripts defaults to the password ‘obiee_navteq’. If this needs to be set to a different value then the script would need to be modified. I would recommend keeping the password as-is.

Now let’s import the dmp file. The obiee_navteq.dmp needs to be imported into obiee_navteq schema using the user created above. The command line would be:

Drive:\>imp obiee_navteq/obiee_navteq@connectString file=obiee_navteq.dmp FULL=Y

Once this process is complete, we would need to validate that the login to the schema is successful and schema tables are visible (and have data). Post successful creation of tables, some extra Spatial metadata would also need to be imported.

Start a SQL*Plus session to the Oracle Database and connect as user obiee_navteq
Drive:\>sqlplus obiee_navteq/obiee_navteq@connectString
Run the OBIEE_NAVTEQ_INSERT.SQL file located in the unzipped folder.
SQL> @OBIEE_NAVTEQ_INSERT.SQL; 

Now we need to configure Map Viewer. OBIEE 11g delivers map content using Map Viewer. There are certain settings that need to be verified/configured for Map Viewer to function.
Note: Map Viewer would need to be installed on the server. OBIEE 11g installation includes this component.

1. Configure mapViewerConfig.xml
Open the Map Viewer console. It’s available at http://[server]:9704/mapviewer. Click on Admin link. Login with the userid and password provided during the installation. Click on configuration. This will launch the mapViewerConfig.xml file. The following needs to be updated:

In the <security_config> property of the file, the following changes need to be made:
Change <proxy_enabled_hosts> property to hostname, IP address and port to correct values. [Note]. There are 4 entries here. 2 pointing to hostname and 2 pointing to ip address of BI server. Make sure all 4 entries point to the right server.

<proxy_enabled_hosts>
  http://localhost:9704/mapviewer,http://localhost:9704/,http://10.10.10.10:9704/,http://10.10.10.10:9704/mapviewer 
</proxy_enabled_hosts>

The following entries would also need to be updated/added:
<disable_direct_info_request> true </disable_direct_info_request>
<disable_info_request> true </disable_info_request>
<disable_csf>true</disable_csf>
<enforce_security_role> true </enforce_security_role>

At the end of the file, in the section ‘Predefined Data Sources’ the following entry would need to be added:
<map_data_source name="OBIEE_NAVTEQ_Sample"
                   jdbc_host="10.10.10.11"   (use your db ip)
                   jdbc_sid="orcl"       (use your db sid)
                   jdbc_port="1521"      (use your db port)
                   jdbc_user="obiee_navteq"                   
                   jdbc_password="!obiee_navteq"  (use your selected password if different from OOB)
                   jdbc_mode="thin"
                   number_of_mappers="3"
                   allow_jdbc_theme_based_foi="false"
   />

[Very Important]. Make sure that all xml tags have been properly closed. Any tags not closed will cause an error on the next restart.

Let’s save and restart. One it is restarted, when we click on Data sources, we should be able to see OBIEE_NAVTEQ as a data source.

For maps to work, we would also need to create Map Tile Layers. These are the layers through which OBIEE enables the drilling functionality on the map. Different layers allow different levels of detail. Each Map Tile Layer could have a different co-ordinate/country/zoom factor.

Click on Manage Map Tile Layers Link, and Use the Create Link to create the following Map Tile Layers ONLY IF YOU DO NOT see the entries already under ‘Existing map tile layers’. 
   
    OBIEE_WORLD_MAP
        Select type of map source : Choose Internal
        Name : OBIEE_WORLD_MAP
        Data Source : OBIEE_NAVTEQ_SAMPLE
        Base map : WORLD_MAP
        # Zoom Levels : 16
        Minimum Map Scale:9999
        Maximum Map Scale : 250000000
        Min X:-180.0
        Max X:180.0
        Min Y:-90.0
        Max Y:90.0  

Leave the other options as default and click on Submit. This will create a Map Tile Layer called OBIEE_WORLD_MAP. 
   
    OBIEE_WORLD_MAP_FAST
        Select type of map source : Choose Internal
        Name : OBIEE_WORLD_MAP_FAST
        Data Source : OBIEE_NAVTEQ_SAMPLE
        Base map : WORLD_MAP_FAST
        # Zoom Levels : 10
        Minimum Map Scale:9999
        Maximum Map Scale : 300000000
        Min X:-180.0
         Max X:180.0
         Min Y:-90.0
        Max Y:90.0

Leave the other options as default and click on Submit. This will create a Map Tile Layer called OBIEE_WORLD_MAP_FAST.

    OBIEE_SF_MAP1
        Select type of map source : Choose Internal
        Name : OBIEE_SF_MAP1
        Data Source : OBIEE_NAVTEQ_SAMPLE
        Base map : WORLD_MAP
        # Zoom Levels : 8
        Minimum Map Scale:1000
        Maximum Map Scale : 500000
        Min X:-123.0
         Max X:-122.0
         Min Y:37.0
        Max Y:38.0

Leave the other options as default and click on Submit. This will create a Map Tile Layer called OBIEE_SF_MAP1.

    OBIEE_SYDNEY_MAP 
        Select type of map source : Choose Internal
        Name : OBIEE_SYDNEY_MAP
        Data Source : OBIEE_NAVTEQ_SAMPLE
        Base map : WORLD_MAP
        # Zoom Levels : 8
        Minimum Map Scale:1000
        Maximum Map Scale : 250000
        Min X:150.937
         Max X:151.504
         Min Y:-34.13
        Max Y:-33.67
 
Leave the other options as default and click on Submit. This will create a Map Tile Layer called OBIEE_SYDNEY_MAP.

    OBIEE_LONDON_MAP
        Select type of map source : Choose Internal
        Name : OBIEE_LONDON_MAP
        Data Source : OBIEE_NAVTEQ_SAMPLE
        Base map : WORLD_MAP
        # Zoom Levels : 8
        Minimum Map Scale:1000
        Maximum Map Scale : 250000
        Min X:-0.33
         Max X:0.11
         Min Y:51.37
        Max Y:51.64 

Leave the other options as default and click on Submit. This will create a Map Tile Layer called OBIEE_LONDON_MAP.

To confirm that the Map Viewer configuration is working, we choose the Map Tile Layer called OBIEE_WORLD_MAP and click on ‘View Map / Manage tiles’ option. In the window that opens up, we click on the ‘Show Map’ button. This should display the world map.  We would need to repeat the steps for all the other layers as well.

Now we need to restart OBIEE services via OPMN (Oracle Process Manager) or EM (Enterprise Manager).

Post restart, let’s login into Answers. Click Administration -> Manage Map Data. Click Layers tab. Click ‘Add Layer’ link.

The dropdown should have an entry ‘OBIEE_NAVTEQ_Sample’ at this point, meaning the configuration of datasource is successful. Clicking the OBIEE_NAVTEQ_Sample entry should populate the listbox with all map tile layers that we configured. We would also need to confirm that "OBIEE_NAVTEQ_Sample" entry is visible under "Layers", "Background Maps" & "Images" tab as well.

Configuration of Map Viewer for OBIEE is now complete.

Next post: Creating Maps through OBIEE 11G.

Before we begin the upgrade process, a couple of key points to note. As part of the OBIEE 11g upgrade, the following gets upgraded:

1. RPD including users and groups

2. Webcat

3. Scheduler Schema (Delivers)

4. BI Publisher Repository

5. BI Publisher Schema

The following will NOT get upgraded:

1. Configuration files

2. Custom style sheets

3. Custom javascripts

While the RPD & Webcat upgrade is one-to-one, there are some minor differences in BI Publisher upgrade. The original .xdo now is split into two components – .xdm and .xdo as illustrated:

Now, let’s start with the upgrade. To begin with let’s identify a 10g RPD and webcat that we want to upgrade. OBIEE 11g services would need to up and running.

On the Deployment tab, we can verify which RPD and webcat is currently online:

Important: We need to make a copy of the the rpd and webcat currently loaded in OBIEE. After a successful upgrade, OBIEE switches the upgraded RPD & Webcat to be the online copy. We need to switch these back after a successful upgrade.

Hint: You may need to ‘Lock and Edit’ the configuration in order to see the webcat location.

Navigate to ?:\<installfolder>\instances\instance1\bifoundation\OracleBIServerComponent\coreapplication_obis1

Let’s create a new folder, then copy the ‘sample’ folder with all subfolders into the new folder:

This folder will provide the data for the rpd we are about to upgrade.

Now let’s start the Upgrade Assistant and run through the prompts.

?:\<installfolder>\Oracle_BI1\bin\ua.bat

1. Browse to the rpd that we want to upgrade.

2. Enter the credentials for this RPD.

3. We need to create a password to secure the upgraded RPD.

4. We need to browse to the folder that contains the 10g webcat.

5. Now we specify an empty folder for deliveries.

     6.We specify the location and credentials to login to your Weblogic Admin Server.

   7.Select ‘Upgrade’

We refresh the Deployments tab in Enterprise Manager

Let’s check that we are now using the 10g rpd and webcat (upgraded to 11g).

Let’s login to BI and view the updated dashboard.

The Upgrade is complete. We now need to switch back to the original Application. This step is very important as the upgraded rpd and webcat is now the one loaded in OBIEE. As part of the upgrade, the security has also been migrated to the weblogic layer.

Next week: Security in OBIEE 11g.

In BusinessObjects Enterprise XI 3.1, Edge XI 3.1 and Crystal Reports Server 2008 v1, the new Interportlet Communication (IPC) feature in Dashboard Builder allows the transfer of information between distinct analytics. Now you can pass parameters from an Xcelsius dashboard to another XCelsius dashboard or to Crystal Reports and Web Intelligence. Using this framework, I will show 2 simple ways to link between:

1. Two XCelsius dashboards
2. Between an XCelsius dashboard and Web Intelligence/Crystal Reports

XCelsius to XCelsius linking

An XCelsius dashboard used as a source document has to be configured with a Portal Provider Connection. The target analytic also has to be configured with the Portal Consumer Connection. We will send parameter data between two analytics with the use of a simple example: sending information from a list box selector in one analytic to drive a chart in another dashboard. The steps are

Create the provider analytic

1. Create the list box control for the years: As you can see below I have created a simple list box control with the years.

The selected item from the list box is placed in cell B2 in my example (marked in yellow). I have also set the size of the canvas to fit the component.

2. Create a new portal data connection as shown below.

Choose provider as the Connection Type and give a name to the range (in my example Year). Since we are passing a single cell of data, select Cell  as the range type and the cell B2 which is the target of the list box selection. Also go to the usage tab and instruct the data connection to communicate with the consumers when the value in the target cell (B2) changes.

This will ensure that whenever the user makes any selection on the list box, the label will be passed to the target/consumer of the portal connection.

Create the target analytic

1. In the target dashboard I have created a simple dashboard where I have a chart combo box.

In the properties of the combo box I have set the combo to read the current selection from a cell. When the selection in the cell changes it will read the row of the data corresponding to the selected year and place it in the target row which drives the chart.

2. Define the portal data connection of type consumer as shown below.

Keep in mind that the Range name has to be the same for both the provider and the consumer. Also since the provider is going to pass a single cell I have selected the range type as Cell and have it update cell B2 which drives my drop down and chart.

Combine them in the dashboard

Now log on to InfoView and create a new Corporate Dashboard. Drag your “Provider” and “Consumer” analytics onto the dashboard. Also activate “Content Linking”.  This can be done by setting the properties of the Provider analytic. Choose the Provider analytic as the “Source Analytics”, and Consumer as the “Target Analytics” as shown below.

XCelsius to WEBI/CR linking

An XCelsius dashboard used as a source document for Crystal Reports and Web Intelligence has to be configured with the FS Command connectivity. The parameters are then assembled in an OpenDocument URL by the Dashboard Builder framework. For more information about the OpenDocument syntax, see the documentation:
http://help.sap.com/businessobject/product_guides/boexir31/en/xi3-1_url_reporting_opendocument_en.pdf

To illustrate this example I have a summary report in XCelsius and use WEBI to show the detailed month wise breakdown.

Create the provider analytic

The steps to create the provider are the same. In fact I have used the same analytic that I used in the previous example. The only difference is that since the dashboard builder framework uses the OpenDoc URL format to pass the parameters I need to massage the parameter so that it can sent to WEBI as shown below.

In cell D2, I take the selection from B2 and use excel formula (="&lsSYear="&B2) to create the parameter for the data connection.

Now go to the data connections and add a new FS Data connection as shown below.

The trigger also has to be set in the usage tab, so that the data connection sends the new value whenever the value in the cell D2 changes.

Now export this to SWF and save it in the infoview portal.

Create the WEBI Report

The steps to create the WEBI Report is fairly simple. As shown below I have created a simple WEBI report which takes in the year as the prompt.

The only thing to keep in mind is the name of the prompt should correspond to the formula set in the provider analytic. For example in my case the open doc param formula in the provider analytics is ="&lsSYear="&B2 which corresponds to the Year prompt in WEBI.

Save WEBI report in the infoview portal and test the content linking as shown earlier.

If you want more details you can check out the user guides at

OpenDocument User Guide: http://help.sap.com/businessobject/product_guides/boexir31/en/xi3-1_url_reporting_opendocument_en.pdf
Dashboard Builder User Guide: http://help.sap.com/businessobject/product_guides/boexir31SP3/en/xi31_sp3_dashboard_user_en.pdf

QAAWS is a web service generator. It uses the query builder to essentially to build a query and publish the query to the platform and makes it available as a web service. Here is how you can use it.

Create the Query and Publish to the platform

1. Launch QAAWS and create a new query. Give it a name that is user friendly.

2. You can set additional parameters such as authentication mode and timeout at this stage. Usually we would keep them as default.

3. As you can see in the steps the next step is to select a universe. Based on your security setting you will be presented with a list of universes that you can use for building the query. The process of selecting the universe and building the query is the same as you would do when using WEBI.

In my example I have purposefully chosen a query which has a prompted filter. I can drive this prompt using a drop down box or other selectors from the dashboard.

As you can see my query has 1 input parameter and 4 output parameters. Now all I need to do it click on the publish button to publish the webservice to the platform.

The URL shown above is the URL for the webservice and I can use this in XCelsius to build my dashboard.

Using the Query in XCelsius

In the data connections dialog of XCelsius you can add a new live office connection. Here you need to enter the URL that we got from QAAWS.

We also need to bind the cells to both the input and output parameters. For the input parameter I have bound it to cell C3 of the spreadsheet as shown below.

The same way you need to bound the output to your spreadsheet. The only thing to keep in mind is that if your query will return multiple rows of data you would need to select a range of cells bigger than the maximum possible range as shown below.

For debugging purposes you can also get the number of rows returned by the query and bind it to a cell as shown below.

And after all of this voila you have a live dashboard…

Please note that LCM is a separate installation and requires the following Services:

1. Central Management Server: LCM job itself is an object which is saved in CMC.
2. Adaptive Processing Server: The LCM job server is added to the Adaptive processing server
3. Web Application Server: LCM is a web application
4. Input FRS : This is a server you need available after installing, as jobs that you create in LCM are saved in the Input FRS and CMS repository.

Administrative Settings

Access to the LCM application is set by managing the security for the application in CMC as shown below.

Also before creating new jobs you need to add the source and target BOE systems in the LCM application using the administration options shown below.

Creating the LCM Job

To migrate objects, you have to first have to specify which content you want to promote. This is done in LCM tool with 3 main steps:

1. Create a Job: A job is collection of objects that can be moved from one BOE environment to another.

When you create a new job you must logon to the source system and an Input FRS should be running and enabled as the Job is saved as an Object in the CMS database and as a file in the Input FRS.

In the example above I am migrating objects from my BOE environment as the source to a BIAR file.

2. Add Objects: Add the required objects from the CMS repository that should be migrated. In this example I am migrating all the reports related to the sales and finance department.

3. Add the dependent objects : Objects such as universes, connections, images and other dependencies on which the primary objects depend on also have to be added to the job. LCM will automatically compute the dependents when you click on “Manage Dependencies”.

And now all the objects and their dependents are selected in the job as shown below.

Now my job is ready for the next step which is promotion. You can promote content when deployments are connected and also when they are isolated. When deployments are connected you can directly migrate to the destination. When they are isolated you use a LCMBIAR file to transport the content.

Promoting to target

But before promoting you need to set a bunch of options.

1. Map Connections: You need to map all the universe, QWAAS URL and Crystal report database connection mappings to the target.

2. Schedule: To set how often the job should run.

3. Security: You can specify to promote the security of the objects in the job as a best practice only promote security when changes have been made, typically with a significant revision of the application.

4. Test: As the last step you can test what would happen when promoting the job, without committing the objects to destination

To promote a job you can schedule it or you can run it manually. The figure below shows the 2 scenarios of connected and isolated environments.

• Create objectives
• Assign KPIs to objectives
• Create Strategy Hierarchy
• Define Relationships between Objectives/KPIs

To begin with, let’s create a scorecard. From the OBI menu, expand “New” and select “Scorecard”. Let’s call this scorecard “MyScorecard”.

Let’s save in a folder called “working” for now. Clicking “OK” creates an empty Scorecard template.

Now let’s add objectives to our scorecard template. Click the “Create Objective” button and let’s call it “Aligning Operations” in the Objective Name field. Let’s select the “Internal Process” perspective for now and save it.

Let’s add some KPIs to the Objective. We expand the Catalog pane in the left corner and browse where our KPIs are stored. Let’s select the KPI “Attrition Rate” and “# Employees” onto the objectives grid.

This activates the “Add KPI” window. This KPI window allows us to filter/pin our KPI to a specific dimension value.

It is important to note that if the KPI is pinned to a specific dimension value then it will “not” respond to prompts or a change in the POV bar at the top of the scorecard. I recommend that in most cases it should be left as the default. Let’s save our Objective.

We can create a strategy hierarchy in the “Strategy” window using the steps outlined above. It is possible to create multiple nested objectives and then assign KPIs to them.

The steps for creating initiatives is the same. The initiatives screen provides a few additional fields like “Start Date”, “End Date”, “Completion Date” and “Resources”.

Let’s now focus on creating a Strategy Map. We start by clicking on the “Scorecard Documents” pane. Let’s click the down-arrow next to create button and select the “Create Strategy Map” option. This would display a blank Strategy Map view.

Now we can drag and drop objectives and KPIs from the Scorecard’s Strategy Hierarchy to the Strategy Map Canvas. We would need to repeat this a couple of times to have several objects on our canvas.

By default, each time we drag an objective/KPI onto the canvas, it will get positioned into its assigned perspective as defined in that object’s detailed page. If a perspective is not assigned in the KPI/Objective, it will then get positioned where we drop it in the canvas.

We can now define a relationship between objects by clicking the “Draw a Casual Linkage Between Two Objectives” button at the top of the canvas. Then we click/drag the mouse pointer from one Objective to the Next (or KPIs) to define a relationship. We would need to repeat this for all Objectives/KPIs that are relevant.

It is also possible to describe the relationship by right clicking on the linkage arrow and selecting the “Edit Casual Linkage” option. From the casual linkage dialog we can define the strength and proportionality of the relationship.

Finally, we save the strategy map. To enhance this further, we can create a cause and effect map, by right clicking on any objective in the strategy pane and choose the view cause and effect option or a strategy tree view, by clicking on the objective in the strategy pane and selecting the “View Strategy Tree Option”.

• Creating a Simple KPI
• Setting Dimensionality
• Setting Thresholds

We’ll start by creating a KPI that compares Actual vs. Target revenue. Let’s define thresholds for the same at 80% & 90% of target. This KPI would be measured at the intersection of Year, Quarter, Month, Products & Offices. In later posts, I will setup navigation actions for each threshold & alerts for this KPI as well.

Let’s start by creating a new KPI. From the OBI Menu, expand New and select KPI. Select a subject area. I would be using the SampleApp application and “A – Sample Sales” subject area.

Select “abell” as the Business Owner. This user would have the privilege of overriding the status of this KPI. We now need to select two facts that would be used to get the actual and target values. For this, let’s select “1-Revenue” and “5-Target Revenue” from “Base Facts”. I’ll also select “enable trending” to compare values for months. For this, in the Compare to prior field, I will select “Month” to compare. This sets the grain of the KPI that will be used to compute the trend. Click next.

Now we setup the dimensionality for the KPI. Click add and in the New Dimension dialog, select “T05 Per Name Year” from Time. Leave the value cell to “Not Pinned”. Repeat the same process with “T03 Per Name Qtr”, “T02 Per Name Month” from “Time Dimension” and “Products Hierarchy” from Products and “Offices Hierarchy” from Offices. Click Next.

Now we will define thresholds for this KPI. In the goals field, we will select “High Values are Desirable”. In the first threshold field, use the down button to select "Base Facts"."5- Target Revenue" and Type * 0.90. In the second threshold field, select the same field again and type * 0.80. This indicates to the system that anything from 0-80 percent of target as Red, and from 80-90 percent of Target as Yellow and anything above 90% as Green. Click Next.

In the next screen, we attach any related documents to the KPI. I will skip this step and click Finish. Let’s save this KPI as “RevenueTarget” and click OK. In the KPI definition page, click Cancel to exit out of this screen.

Let’s open this KPI from the “Open” menu and let’s take a look.

Next Post: Linking KPIs in a Scorecard