SAP BusinessObjects Profitability and Cost Management ... · 5. Check that all prerequisites...

PUBLICSAP BusinessObjects Profitability and Cost ManagementDocument Version: 10.0 – 2019-04-09

SAP BusinessObjects Profitability and Cost Management Database Administrator's Guide

© 2

019

SAP

SE o

r an

SAP affi

liate

com

pany

. All

right

s re

serv

ed.

THE BEST RUN

Content

1 About this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.1 Supported Software Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52.2 Important Restriction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.3 Installation Script Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.4 Pre-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

SAP Adaptive Server Enterprise Pre-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Microsoft SQL Server Pre-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Oracle Pre-Installation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

3 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.1 Setting up a New Microsoft SQL Server Database Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

To create the EPOACCESS role for Microsoft SQL Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3.2 Setting up a New Oracle Database Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.3 Setting up a New SAP Adaptive Server Enterprise Database Structure. . . . . . . . . . . . . . . . . . . . . . . 14

4 Data Loader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164.1 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Generating a Load Identifier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Running Data Loader Remotely. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.2 Data Loader Procedures and Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Data Loader Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Structural Procedures and Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Value Procedures and Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

4.3 Performing a Data Load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36Execute Data Loader Routines Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39Transforming Data from an Existing Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Refreshing the Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

4.4 Follow-up Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Data Loader Completion Checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Stage Table Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

4.5 Troubleshooting Data Loader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Data Loader Activity Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Loadstatus Field Values and Constant Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Data Loader Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

5 Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

2 P U B L I CSAP BusinessObjects Profitability and Cost Management Database Administrator's Guide

Content

5.1 Restoring the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515.2 Data Files and Disk Space. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Autogrow Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .525.3 Rebuilding Database Indexes and Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .525.4 Microsoft SQL Server Data Compression. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565.5 Data Loader Parallel Processing Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585.6 Log Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

6 Database Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606.1 About Data Loader Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Management Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62Structural Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Value Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

6.2 About Results Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Results Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Dimension Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Results Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Exporting Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

6.3 About Audit Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Framework Audit Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Assignment Audit Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180Value Audit Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

7 Organizing an Update Using Data Bridge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2347.1 Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Building Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235The ParentChild Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

SAP BusinessObjects Profitability and Cost Management Database Administrator's GuideContent P U B L I C 3

1 About this Guide

This document is designed for experienced Database Administrators and Data Bridge users who are familiar with the database and the SAP BusinessObjects Profitability and Cost Management software, and who may neeed to perform the following tasks:

● Install a Microsoft SQL Server, Oracle or SAP Adaptive Server Enterprise (SAP ASE) database system for first time use with the SAP BusinessObjects Profitability and Cost Management software.

● Carry out routine database maintenance, including a rebuild of indexes● Execute Data Loader procedures and analyze results - This tool uses a series of SQL loading procedures

that enable preprocessed data to be made available to the software via exposed loading tables. It includes details of the tables that are incorporated into Data Loader, the logic behind the procedures and how to install and load them. It is preferable that you are at least familiar with the software import and export tables, and that you have the appropriate SQL skills to populate the loading tables and to execute stored procedures. A description of the loading tables is provided along with relevant field mappings to existing Data Bridge tables to enable database-literate Data Bridge users to use the Microsoft SQL and Oracle loading procedures and packages.

● Configure and analyze database auditing● Troubleshoot error messages

In this document, you can find detailed steps about how to install the database software for use with SAP BusinessObjects Profitability and Cost Management, an extensive tabulation of management, structural, value and results database schemas, how to load data into the database with the use of Data Loader procedures for execution on Microsoft SQL Server, Oracle or SAP Adaptive Server Enterprise database systems, and how to maintain your database environment with the help of procedural tasks and re-indexing scripts.


About this Guide

2 Preparation

2.1 Supported Software Versions

The database server can be configured with any operating system that supports the database technology. Please refer to the latest version of the SAP BusinessObjects Profitability and Cost Management Master Guide for which versions of the database software we currently support.

2.2 Important Restriction

Users may not alter, insert or remove data from any core tables.

NoteCore tables refers to all tables not listed in this document.

Users may not make changes to the following:

● SAP Adaptive Server Enterprise

TablesViewsStored ProceduresFunctionsTriggers

.● Microsoft SQL Server:

TablesViewsStored ProceduresFunctionsTriggersTable views

● Oracle:

TablesViewsPackagesProceduresFunctionsTriggers

SAP BusinessObjects Profitability and Cost Management Database Administrator's GuidePreparation P U B L I C 5

Sequences

Direct access to core tables is not supported by SAP, and all access to data and results within the RDBMS should be through the views. This approach is recommended as it enables custom database references to be isolated from changes made to the internal schema as part of new software releases and support packs.

2.3 Installation Script Location

The scripts that perform the database schema installation are stored in the PCM_100_SQL folder in the downloaded source installation folder.

Prior to installation, the scripts must be copied from the installation folder to a folder to which the user performing the installation has full read and write access rights. The script file locations for each database system are listed in the table below:

Database System Script Location

Microsoft SQL Server \PCM_100_SQL\MSSchema.cmd

SAP Adaptive Server Enterprise \PCM_100_SQL\ASESchema.cmd

Oracle \PCM_100_SQL\support\OracleCreateObjects.sql

\PCM_100_SQL\OracleSchema.cmd

2.4 Pre-Installation Tasks

Before you start to install and manage the software, an understanding of the basic administration tasks is required for creating and loading a database, and providing users with appropriate security privileges. The pre-installation tasks in this section must be performed before the SAP Business Objects Profitability and Cost Management database can be installed.

NoteUpgrading the database follows much of the same procedure as installing a new database. Upgrade instructions can be found in the SAP BusinessObjects Profitability and Cost Management Upgrade Guide.


Preparation

2.4.1 SAP Adaptive Server Enterprise Pre-Installation Tasks

Context

Perform the following tasks before the database schema is installed:

Procedure

1. Install the latest recommended version of SAP Adaptive Server Enterprise and check that the installation is working correctly (refer to the SAP BusinessObjects Profitability and Cost Management Master Guide).

2. Configure the character set as UTF-8, the default sort order of nocase and the default unicode sort order of nocase.

3. Check that the database is new and unused.4. Ensure that you have administrator access to your machine and access to the database.5. Check that all prerequisites detailed in the SAP BusinessObjects Profitability and Cost Management

Master Guide document are installed, and restart the machine when necessary.

2.4.2 Microsoft SQL Server Pre-Installation Tasks

Prerequisites


Procedure

1. Install the latest recommended version of Microsoft SQL Server and check that the installation is working correctly (refer to the SAP BusinessObjects Profitability and Cost Management Master Guide).

2. Configure the character set as Latin1_General_CI_AS.3. Check that the database is new and unused.4. Ensure that you have administrator access to your machine and dbo access to the database.5. Check that all prerequisites detailed in the SAP BusinessObjects Profitability and Cost Management Master

Guide document are installed, and restart the machine when necessary.


2.4.3 Oracle Pre-Installation Tasks

Prerequisites


Procedure

1. Install the latest recommended version of Oracle and check that the installation is working correctly (refer to the SAP BusinessObjects Profitability and Cost Management Master Guide).

2. Ensure that you have the required access to the database to be able to set up the tablespace and user access.

3. Check that all prerequisites detailed in the SAP BusinessObjects Profitability and Cost Management Master Guide document are installed, and restart the machine when necessary.

2.4.3.1 Preparation of the Database Area

Using the Oracle Database Configuration Assistant, create your Oracle database with the following options:

● Custom build● Warehouse● Dedicated Server mode● The Character Set and National Character on, but should be set to AL32UTF8 and AL16UTF16 respectively.● GDN (Global Database Name) = SID name (typically EPO).

For legacy reasons many of the tables in an SAP BusinessObjects Profitability and Cost Management database are prefixed with EPO and much of its associated logic uses this mnemonic.

The database should now be set up ready for creating the database schema and assigning relevant roles and access rights.

2.4.3.1.1 Tablespace Setup and User Rights

Tablespace setup can be performed manually, using the SQLPlus utility and the script below, or by running the script OracleCreateObjects.sql found in the PCM_100_SQL\support folder in the installation source folder.


Preparation

2.4.3.1.1.1 Creating the Tablespace and Users

Procedure

1. Login to SQLPlus as system user (system).2. To use the OracleCreateObjects.sql file, open it from the File menu. To create the tablespace in

another location, you must edit the path before running it, otherwise manually create the tablespace by typing the lines of code as they appear below.

3. Start by creating a tablespace (called EPO in the example below), which is the disk space that holds the database.Example: Create Tablespace

CREATE TABLESPACE EPO_DATA DATAFILE 'D:\oracle\oradata\EPO\epo_data.DBF' SIZE 250MEXTENT MANAGEMENT LOCAL AUTOALLOCATE;ALTER DATABASE DATAFILE'D:\oracle\oradata\EPO\epo_data.DBF'AUTOEXTEND ON;

4. Create a user (for example, Username = adminepo, Password = manager) with access to your EPO Tablespace by entering the details below where adminepo is the user you wish to use as the database administrator.Example: Create Administrator user

Create user adminepo identified by managerdefault tablespace epo_datatemporary tablespace temp;Create Role EPOACCESS;Grant create session to adminepo; Grant unlimited tablespace to adminepo; Grant create table to adminepo;Grant create procedure to adminepo;Grant create view to adminepo; Grant create trigger to adminepo; Grant create sequence to adminepo;Grant EPOACCESS to adminepo with admin option; Grant query rewrite to adminepo;Grant create materialized view to adminepo;

5. Next, create another user with restricted database access for the SAP BusinessObjects Profitability and Cost Management services via SAP BusinessObjects Profitability and Cost Management Configure to connect to the database.Example: Create restricted user

Create user usrepo identified by passworddefault tablespace epo_datatemporary tablespace temp;Grant create session to usrepo;Grant unlimited tablespace to usrepo;Grant create synonym to usrepo;

6. Exit from SQL Plus.


The tablespace is now ready to create the tables and other structures for the software.


Preparation

3 Installation

A database schema installation script is provided with the software for each supported database system. These scripts create the required schemas in a new database and are executed by manually running the appropriate command file.

Problems can occur if database collation is case-insensitive when the server collation is set to case-sensitive. To resolve this problem for Oracle and SQL databases, the script to create the database schema, OracleSchema.cmd, or MSSchema.cmd validates whether character sets are configured correctly for the database. If they are not correct, the script stops executing.

3.1 Setting up a New Microsoft SQL Server Database Structure

Prerequisites

Before you start, ensure the character set is configured as “Latin1_General_CI_AS” as described in the “Pre-Installation Tasks” section. Also ensure that you have downloaded the correct version of the software from the SAP Support Portal at SAP Support Portal . Instructions for downloading the software can be found in the following SAP Note: 772755 .

Context

Configuring the initial database structure involves creating a new blank database, running the provided SQL script to create the software database schema, and assigning a role to the database user.

Procedure

1. Log into the Microsoft SQL Server Management Studio as a user with administration rights.2. Create a database on the server without any spaces in the name.3. Ensure an administrative user exists who is a member of the db_owner role.

This user name is used when executing database creation scripts.4. Unzip the downloaded software zip file and copy the PCM_100_SQL folder into a location on the hard drive

where you have read and write access.5. Open a command prompt window:

SAP BusinessObjects Profitability and Cost Management Database Administrator's GuideInstallation P U B L I C 11

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fen%2Findex.html

http://help.sap.com/disclaimer?site=https%3A%2F%2Fwebsmp130.sap-ag.de%2Fsap%28bD1lbiZjPTAwMQ%3D%3D%29%2Fbc%2Fbsp%2Fspn%2Fsapnotes%2Findex2.htm%3Fnumm%3D772755

a. Click Start Run on the Windows Start menu.b. Type CMD in the Open text box.c. Click OK or press Enter .

6. At the command prompt change directory to where the PCM_100_SQL folder has been copied. For example:cd\PCM_100_SQL

7. Run the SQL script batch files to set up the database structures. The MSSchema.cmd must be run with the following parameters:<Database Server Name> <Database Name> <Admin User Name> <Admin Password>

For the current release, type the command below supplying the specific parameters in place of the specified terms:

MSSchema.cmd SERVER DATABASE ADMINUSER PASSWORD

NoteAlternatively you can use Windows NT authentication in which case SSPI may be entered in place of the database administrator name and password, providing that the NT user has dbo access:

MSSchema.cmd SERVER DATABASE SSPI

Once this is created, we recommend that you check the file MSSchema.log in the PCM_100_SQL folder for any possible errors. Any error messages are normally identified by the following string; msg.

8. If you are using SSPI and a Windows user account instead of a Microsoft SQL Server login, you can create the EPOACCESS role to be the user role that is used to access the database during configuration. To do this, follow the steps in “To create the EPOACCESS role for Microsoft SQL Server”.

3.1.1 To create the EPOACCESS role for Microsoft SQL Server

Context

If you are using SSPI and a Windows user account instead of a Microsoft SQL Server login, you can create the EPOACCESS role to be the user role that is used to access the database during configuration.

This requires you to add a user to the PCM database that uses the PCM Login and give it access to the EPOACCESS role. Then you set the EPOACCESS role to be the user logon for PCM Services, and if you are using DCOM, also apply the EPOACCESS role to the DCOM Identity settings.

Procedure

1. Create a Windows user with Administrator rights.2. Create the EPOACCESS role in SQL Server Management Studio and assign a user to it:

a. Open SQL Server Management Studio and navigate to Security Logins and select New Login.


Installation

b. Enter the newly created Windows user in Login name, select the PCM database as the Default database and click OK.

c. In Databases, navigate to the PCM database, and then Security Users , and select New User.d. Enter a name for the PCM user in User name, enter the Windows user in Login name, select the

EPOACCESS checkbox in both Owned Schemas and Role Members and click OK.This adds the user to the PCM database, using the PCM Login, and assigns it to the EPOACCESS role.

3. For each PCM service that is enabled, set the Log On parameter to the Windows user defined as the SSPI Login for Microsoft SQL Server:

a. In the Start menu, select Control Panel Administrative Tools Services .b. For every PCM service that is not set to Disabled, open the Properties dialog, and select the Logon tab:

select This account and enter the Windows user, then click OK.4. For each PCM service listed in the DCOM setting, change the Identity to the Windows user defined as the

SSPI Login for Microsoft SQL Server:

NoteIgnore this step if Sockets has been selected.

a. In the Start menu, select Control Panel Administrative Tools Component Services .

b. Navigate to Console Root Component Services Computers My Computer DCOM Config .c. For every PCM service, open the Properties dialog, and select the Identity tab: select This user and

enter the Windows user, then click OK.

Next Steps

Check that the EPOACCESS role has been set up correctly by doing the following:

1. Open a model in Model Builder.2. In SQL Server Management Studio, run the following query:

SQLQuery1.sql - lo…t.master (sa (52))* Sp_who2;

3. Confirm that all Logins referencing the PCM database are now using the specified Windows user via the EPOACCESS role.

3.2 Setting up a New Oracle Database Structure

Prerequisites

Before you start, ensure that you have downloaded the correct version of the software from the SAP Support Portal at SAP Support Portal Instructions for downloading the software can be found in the following SAP Note: 772755 .


http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com%2Fen%2Findex.html

http://help.sap.com/disclaimer?site=https%3A%2F%2Fwebsmp130.sap-ag.de%2Fsap%28bD1lbiZjPTAwMQ%3D%3D%29%2Fbc%2Fbsp%2Fspn%2Fsapnotes%2Findex2.htm%3Fnumm%3D772755

Procedure

1. Unzip the downloaded software zip file and copy the PCM_100_SQL folder into a location on the hard drive where you have read and write access.

2. Open a Command Prompt window by selecting Run from the Windows Start menu, and type CMD in the Open text box. Click OK or press Enter to continue.

3. At the command prompt change to the directory where the PCM_100_SQL folder has been copied.

4. Run the SQL script batch files to set up the database structures.5. Run OracleSchema.cmd with the following parameters:

<Database Alias> <Admin User Name> <Admin Password> <Restricted Username> <Restricted User Password>

For example, for the current release, type the command below supplying the specific values in place of the parameters: OracleSchema epo adminepo password usrepo password

TipTo configure the “Database Alias”, use the Net Manager utility on the server from where the scripts are to be executed to create a Network Service Name (NSN) entry in the local TNSNames.ORA file. The entry effectively creates a local database alias point at either a local or remote server which can be utilized via SQLPlus for script execution.

Once this is created, it is recommended that you check the file OracleSchema.log in the PCM_100_SQL folder for errors. Any error messages are normally identified by the following strings; ora- and pls-.

3.3 Setting up a New SAP Adaptive Server Enterprise Database Structure

Prerequisites

Before you start, ensure the character set is configured as UTF-8 as described in the

Pre-Installation Tasks section. Also, ensure that you have downloaded the correct version of the software from the SAP Support Portal . Instructions for downloading the software can be found in the 772755 .

Context

Configuring the initial database structure involves creating a new blank database, running the provided SQL script to create the software database schema, and assigning a role to the database user.


Installation

http://help.sap.com/disclaimer?site=https%3A%2F%2Fsupport.sap.com

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/772755

Procedure

1. Log into the Interactive SQL application, connected to the database server as a user with administration rights.

2. Create a database on the server without any spaces in the name.3. Ensure an administrative user exists who has been assigned the role sa_role. This user name will be used

when executing database creation scripts.4. Unzip the downloaded software zip file and copy the PCM_100_SQL folder into a location on the hard drive

where you have read and write access.5. Open a command prompt window:

6. Click Start Run on the Windows Start menu.7. Type CMD in the Open text box.

8. Click OK or pressEnter.9. At the command prompt change directory to where the PCM_100_SQL folder has been copied. For

examaple: cd\PCM_100_SQL.

10. Run the SQL script batch files to set up the database structures. The ASESchema.cmd must be run with the following parameters: <Database Server Name> <Database Name> <Admin User Name> <Admin Password>. For the current release, type the command below supplying the specific parameters in place of the specified terms ASESchema.cmd SERVER DATABASE ADMINUSER PASSWORD. The command file should report if any errors have occurred, but once this has completed execution, we recommend that you check the file ASESchema.log in the PCM_100_SQL folder for any possible errors. Any error messages are normally identified by the following string: msg.


4 Data Loader

The Data Loader utility is designed for use by Database Administrators, and can be carried out directly at the database server or via a database link (Oracle only). If the utility is used via a database link, certain additional packages must be used when scripting.

Related Information

Refreshing the Model [page 40]Running Data Loader Remotely [page 17]

4.1 Preparation

Prerequisites

When loading data, you must either ensure that users are not logged into the SAP BusinessObjects Profitability and Cost Management application and all models are closed, or that you use the Refresh Model Data functionality provided. Failure to do so causes a conflict between the application server cache and the data held in the database, and therefore could result in data corruption. The Data Loader utility bypasses the software, and therefore the application server does not have an indication that data is being inserted into the database.

If you choose not to use the Refresh Model Data option, ensure that the models are completely closed before re-opening. When the models are opened after the load has completed, the application server refreshes the cache and displays the loaded data ready for continued modeling. All required logic is implemented via procedures stored within Oracle packages or via SQL stored procedures in Microsoft SQL Server or SAP Adaptive Server Enterprise.

The following tasks must be completed before data loading can start:

Procedure

1. Create a model in the Model Builder application.2. Generate a load identifier (ID).3. Populate the relevant PPLOAD_ tables with data.


Data Loader

4.1.1 Generating a Load Identifier

To generate a new load ID for a model, you must execute the relevant procedure or package listed in the table below:

Stored Procedure (Microsoft SQL Server/ SAP Adaptive Server Enterprise) Oracle Package

PP_FASTLOADINIT pkgEPOProcs.initialise_fastload

Each of these methods generates a load ID in the PP_FASTLOAD table for whichever model ID is specified as a parameter.

ExampleMicrosoft SQL Server: Generating a Load ID

EXEC PP_FASTLOADINIT @INAUDITUSERID,@INMODELID,@INLOADID output;

ExampleOracle: Generating a Load ID

l_loadid := pkgEPOProcs.initialise_fastload(ModelID, UserID);

ExampleSAP Adaptive Server Enterprise: Generating a Load ID

EXEC PP_FASTLOADINIT @INAUDITUSERID, @INMODELID, @OUTLOADID output go

4.1.2 Running Data Loader Remotely

A distributed transactions function is available in Oracle to enable Data Loader to be run remotely to the database.

RestrictionThis applies to Oracle database systems only. The distributed transactions function is not available or required for Microsoft SQL Server database systems.

Before Data Loader for Oracle can be remotely managed through a database link, all commits and/or rollbacks in Oracle packages must be disabled to prevent the loss of data. This is achieved by calling the Set_DistTranState function with a parameter value of True, for a specific model and load ID combination.

SAP BusinessObjects Profitability and Cost Management Database Administrator's GuideData Loader P U B L I C 17

It is the calling script or procedure that must issue a Commit (or Rollback) command. Also, because this is keyed on ModelID and LoadID, every time a new load ID is used, a call must be made to the Set_DistTranState function to enable remote transaction.

ExampleRunning the Set_DistTranState function

pkgEPOProcs.Set_DistTranState@epolink(ModelID, LoadID, True)

4.2 Data Loader Procedures and Packages

The Data Loader procedures and packages are designed to load structural and value related data into the physical software tables. The structural type of data that can be loaded is typically dimension, alias, property and assignment level data, and value data refers to the actual values that can be loaded into the tables.

The “Structural Procedures and Packages” and “Value Procedures and Packages” sections provide detailed information about the different packages and procedures that can be executed to load these data types, along with allowed parameters and coded examples.

TipUse the “Data Loader Parameters” reference section as a guide for which parameters can be used in conjunction with the procedures or packages.

Loading Model Security

Security descriptors cannot be specified as a data type to be loaded into a model. The Data Loader method relies on database security to load only structural and value types of data into the model, and any required model security must be configured manually in the Model Builder application after a successful data load has taken place.

Loading Data Alias Values

All Default Alias and personalized data alias group values for dimension items can be loaded from staging tables into the value tables. The data alias value that is used to load data is resolved at the model level in conjunction with the use of the Data Loader Alias Resolution model calculation option in Model Builder. Further information about model calculation options can be found in the SAP BusinessObjects Profitability and Cost Management Modeling User Guide.


Data Loader

Data Loader Loadstatus Values

The following table outlines the default Loadstatus values for all loading tables:

Loadstatus Description

1 This value signifies that a record has not been processed, and the property data contained within the staging table record is to be added into the relevant model.

70 This value also signifies that a record has not been processed, but refers to the deletion of any property data from the model, where the keys of the data in the staging tables matches the keys of an existing data record.

Related Information

Data Loader Parameters [page 19]About Data Loader Tables [page 61]

4.2.1 Data Loader Parameters

All procedures and packages can be called from a procedure with associated parameters. The parameters and descriptions along with the types of procedures and packages they can be used with are listed in the tables below:

Microsoft SQL Server, Oracle & SAP Adaptive Server Enterprise Parameters

Parameter

Data Type

Procedure/Package Type Description

Microsoft SQL Server/SAP Adaptive Server Enterprise Oracle

inAUDITUSERID Int Number All User identifier from the EPO_USERS table.

inLOADDELTA Bit Boolean Value Load delta data: True / False. This is only applicable to staging tables that write delta values to base data tables.

inLOADID Int Number All Load Identifier from the PP_FASTLOAD table.

inLOADTARGET Bit Boolean Value Load target data: True / False. This is only applicable to staging tables that write target values to base data tables.

inMODELID Int Number All Model Identifier from the EPO_MODELS table.


Parameter

Data Type



inREPLACE Bit Boolean All Dimension The parameter inREPLACE refers to loading attribute hierarchy mappings. For dimension type procedures and packages:

● 0 (False) = This is the default value. Appends new data items and overwrites any existing data in the model with the values from the load table without removing any. Non-matching data is left unchanged.

● 1 (True) = If values exist, all existing attribute mapping data is replaced, by removing it and appending the new data into the model.

● Assignment● Value

Replace data values for <Version> and <Period>:

● 0 (False) = Add new data items and overwrite any existing data in the model with the values from the load table. Non-matching data is left unchanged.

● 1 (True) = If data already exists in the model for the same <Version> and <Period> as in the load table, the data values in the model for this <Version> and <Period> combination are removed and replaced with the load table data.

inSTATS Bit Boolean All Generate statistical information (Oracle uses the DBMS_STATS package). The executing user must be a member of the sysadmin, dbcreator, db_owner roles. If inStats is set to true, statistics are generated for relevant tables before and after execution.

NoteThe default setting for Microsoft SQL Server is to automatically generate statistics, and it is strongly advised that you keep this setting, as it enables Microsoft SQL Server to consistently generate updated, accurate statistics on the available data. The inSTATS parameter creates additional statistics on the available data.

Statistics are automatically generated by Oracle data loading packages that are greater than version 10.2.0.2.


Data Loader

Parameter

Data Type



inSUM Bit Boolean Value Sum data for corresponding values:

● 0 (False) = Add new data items and overwrite any existing data in the model with the values from the load table. Non-matching data is left unchanged. Duplicate key items are marked as duplicates and not loaded.

● 1 (True) = If the load table contains duplicate records for a data value, then the values are summed together with any values already existing in the model, and this new total value is loaded into the model.

Microsoft SQL Server, Oracle and SAP Adaptive Server Enterprise Parameters specific to Execute Data Loader Routines (PP_EXECUTEDLROUTINES) Procedure

Parameter

Data Type

Description


inERASE Int Number Replace data values for <Version> and <Period>:

● 0 = (Default) Add new data items and overwrite any existing data in the model with the values from the load table. Non-matching data is left unchanged.

● 1 = If data already exists in the model for the same <Version> and <Period> as in the load table, the data values in the model for this <Version> / <Period> combination are removed and replaced with the load table data.

● 2 = If data for this load table already exists in the model, then the data values are all removed for all <Versions> and <Periods>, before the load table values are inserted.

TipIf an unprocessed record in the load table contains an invalid <Version> or <Period>, note that all the data values will be removed if the inERASE parameter is set to 1, without being replaced by anything. This can be a useful technique if you simply wish to clear down the model data for this load table.


Parameter

Data Type

Description


inLOADDELTA Int Number Load delta data: True / False. This is only applicable to staging tables that write delta values to base data tables.

inLOADTARGET Int Number Load target data: True / False. This is only applicable to staging tables that write target values to base data tables.

inREPLACE Int Number For information relating to the values that are replaced, please see the dimension procedure/package description for this parameter above.

Replace data values for <Version> and <Period>:

● 0 (False) = Add new data items and overwrite any existing data in the model with the values from the load table. Non-matching data is left unchanged.

● 1 (True) = If data already exists in the model for the same <Version> and <Period> as in the load table, the data values in the model for this <Version> and <Period> combination are removed and replaced with the load table data.

inSUM Int Number Sum data for corresponding values:

● 0 (False) = Add new data items and overwrite any existing data in the model with the values from the load table. Non-matching data is left unchanged. Duplicate key items are marked as duplicates and not loaded.

● 1 (True) = If the load table contains duplicate records for a data value, then the values are summed together with any values already existing in the model, and this new total value is loaded into the model.

OUTSUCCESS Int Number Output: 0 = success

Parameters Dedicated to Oracle

Parameter Data Type Package Type Description

inATTRIBUTEMERGE Boolean Dimension, some Assignment, and some value

Refers to the loading attribute hierarchy mappings and is designed to be used when inReplace has been set to false.

● 0 (False) = (default value) the package appends the new data as dictated by the value of the inReplace parameter.

● 1 (True) = the package appends new data and updates existing data where relevant.

This parameter is specifically useful for changing the childsort order of hierarchical structures.


Data Loader

Parameter Data Type Package Type Description

inAUDITUSERNAME Varchar2 Value User name from the EPO_USERS table. This parameter enables you to load the corresponding name rather than the identifier. Please refer to the example at the end of this section for further details.

inDELETEMATCHINGKEYS

Boolean Property This parameter refers to the deletion of any property data from the model where the keys of the data in the staging tables match the keys of an existing data record. The following values are allowed:

● 0 (False) = This default value updates any data with matching keys.

● 1 (True) = This value deletes any data with matching keys.

inDELETEZEROVALUES

Boolean Value NoteThe preferred method for removing data is to use load status 70.

Delete value data from the model (see additional example below for further information relating to the PPLOAD_REVENUE and PPLOAD_SERVICEFACTOR tables):

● 0 (False) = The package ignores any zero value records found in the load data (Default).

● 1 (True) = Any zero value records found in the load data that match a record found in the model are processed and the matching model data is deleted. All other non-zero records are processed and model values are appended or updated accordingly.

inMODELNAME Varchar2 Value Model name from the EPO_MODELS table. This parameter enables you to load the corresponding name rather than the identifier. Please refer to the example at the end of this section for further details.

TipSome assignment and value type procedures and packages are designed to write data to multiple physical tables. In this scenario, extra parameters are available to use specifically for that procedure or package. The names of these parameters can be obtained by running either an SQL sp_help or Oracle desc command against the procedure or package in question.

ExampleMicrosoft SQL Server/SAP Adaptive Server Enterprise Dimension Procedure Header

This example shows which parameters can be used in the header of a value type loading procedure:

@INAUDITUSERID INT @INMODELID INT@INLOADID INT@INREPLACE BIT


@INSTATS BIT

ExampleOracle Value Package Header

Oracle value package headers can contain functions that enable you to load the corresponding names rather than the identifiers (inMODELNAME and inAUDITUSERNAME). The code example below shows how to load identifiers only:

FUNCTION Main( inMODELID IN NUMBER,inLOADID IN NUMBER,inAUDITUSERID IN NUMBER,inDELETEZEROVALUES IN BOOLEAN, inSTATS IN BOOLEAN) RETURN NUMBER;

The following example shows how to load a mixture of identifiers and names by using inMODELNAME and inAUDITUSERNAME parameters:

FUNCTION Main( inMODELNAME IN VARCHAR2,inLOADID IN NUMBER,inAUDITUSERNAME IN VARCHAR2,inDELETEZEROVALUES IN BOOLEAN, inSTATS IN BOOLEAN) RETURN NUMBER;

ExampleinDELETEZEROVALUES Parameter

The majority of the tables contain a single value populating a single destination table, or multiple values populating multiple tables. The value fields referenced are the fields analyzed during the data load. The PPLOAD_REVENUE and PPLOAD_SERVICEFACTOR staging tables differ to this rule and have multiple values populating one table and therefore are analyzed differently.

● The PPLOAD_SERVICEFACTOR table has two value fields - SERVICEVARIABLEFACTOR and SERVICEFIXEDUNITRATE. For the record to be removed from the model, both of these values need to be set to zero and INDELETEZEROVALUES needs to be set to True. If both values are set to zero and INDELETEZEROVALUES is set to False, the record in the staging table is ignored.

● The PPLOAD_REVENUE table has three value fields - UNITPRICE, UNITSSOLD, and VALUE. For the record to be removed from the model, the VALUE field needs to be set to zero and INDELETEZEROVALUES needs to be set to True. If all three values are set to zero and INDELETEZEROVALUES is set to False, the record in the staging table is ignored. Any other combination of zero and non-zero values can be loaded if INDELETEZEROVALUES is set to False.

NoteThe preferred method for removing data is to use load status 70.


Data Loader

4.2.2 Structural Procedures and Packages

Each procedure or package requires a model, load and user ID, and some additional parameters are also required (listed in the “Data Loader Parameters” section) depending on the type of procedure or package being called.

4.2.2.1 Dimension Procedures and Packages

Generally, the dimension loading procedures and packages are all identical, but they also each have an associated staging table and dimension table. The packages and procedures for loading dimension data specifically follow the naming conventions listed in the table below (where # represents the dimension name):

RDBMSDimension Loading Procedures/Packages Staging Tables Writes to Physical Tables

Microsoft SQL Server/SAP Adaptive Server Enterprise

● PP_#_DIMENSION_LOADMAIN

● OM_#_DIMENSION_LOADMAIN

● PPLOAD_#_DH● OMLOAD_#_DH

● PP_#● PP_#_NAME● PP_AT_#● OM_#● OM_#_NAME● OM_AT_#

Oracle ● pkgPP_#_DIMENSION

● pkgOM_#_DIMENSION

Use the dimension names listed below to replace the # in the standard naming convention to obtain the full name of each procedure/package or table:

Procedures/packages that are prefixed with PP:

● ACTIVITY● ACTIVITYDRIVER● CAPACITYRULE● COSTOBJECT1● COSTOBJECT2● COSTOBJECT3● COSTOBJECT4● COSTOBJECT5● CURRENCY● DTCOSTOBJECT1● DTCOSTOBJECT2● DTCOSTOBJECT3● DTCOSTOBJECT4● DTCOSTOBJECT5● EMPLOYEE● LINEITEM


● LINEITEMDETAIL● PERIOD● RESOURCEDRIVER● RESPCENTER● REVENUETYPE● SERVICE● SPREAD● USERRULE● VERSION● WORKSHEET1● WORKSHEET2

Procedures/packages that are prefixed with OM:

● BOUNDARY● ICON● METRIC● OBJECTIVE

NotePlease be aware of the limitations imposed by the reserved names in software. For more information, refer to the note on reserved names in Structural tables.

ExampleMicrosoft SQL/SAP ASE Data Loading Flow

The PP_ACTIVITY_DIMENSION_LOADMAIN procedure transforms data from the PPLOAD_ACTIVITY_DH staging table and writes to the PP_ACTIVITY, PP_ACTIVITY_NAME and PP_AT_ACTIVITY physical tables.

ExampleOracle Data Loading Flow

The pkgPP_ACTIVITY_DIMENSION package transforms data from the PPLOAD_ACTIVITY_DH staging table and writes to the PP_ACTIVITY, PP_ACTIVITY_NAME and PP_AT_ACTIVITY physical tables.

4.2.2.1.1 Dimension Data Load

The dimension procedures and packages access the PPLOAD_#_DH or OMLOAD_#_DH tables for all staging data where # represents the dimension name.

Where source data passes validation, the results are written across the PP_#, PP_#_NAME, and PP_AT_# tables, depending on the attribute flag setting.

Pre-validation steps:

1. Check that the supplied model identifier is valid.


Data Loader

2. Check that the supplied load identifier is valid.3. Check that the supplied user identifier is valid.4. Gather statistics if the INSTATS parameter is set to one (true).5. Remove existing attribute mappings if the INREPLACE parameter is set to one (true). Attribute mappings

are removed regardless of the loadstatus value.6. Flag any invalid attribute flags where the load status is 1.7. Flag any names in the load dataset that are duplicates, and leave just the one copy.8. Flag any names starting with an EPO code as invalid, where the load status is 1.9. Flag any names which already exist in this dimension where the loadstatus is 1 for later use.10. Flag any names that are already used elsewhere in the system where the loadstatus is set to 1.11. Flag any root node items.

Write steps:

1. Add all new dimension items that have passed validation at root level.2. Restructure the dimension.3. If the INREPLACE option is set, then clear down the associated attribute table.4. Add attribute mappings.5. Update the loadstatus for processed records.

Related Information

Structural Tables [page 64]

4.2.2.2 Alias Procedures and Packages

The alias loading procedures and packages are all identical, but they each also have an associated staging table and dimension table. The packages and procedures for loading alias data specifically follow the naming conventions listed in the table below (where # represents the dimension name):

RDBMSAlias Loading Procedures/Packages Staging Tables Writes to Physical Tables


● PP_#_ALIAS_LOADMAIN

● OM_#_ALIAS_LOADMAIN

● PPLOAD_#_AL● OMLOAD_#_AL

● PP_#_NAME● OM_#_NAME

Oracle ● pkgPP_#_ALIAS● pkgOM_#_ALIAS

Use the alias names listed below to replace the # in the standard naming convention to obtain the full name of each procedure/package or table:

Procedures/packages that are prefixed with PP:


● ACTIVITY● ACTIVITYDRIVER● CAPACITYRULE● COSTOBJECT1● COSTOBJECT2● COSTOBJECT3● COSTOBJECT4● COSTOBJECT5● CURRENCY● DTCOSTOBJECT1● DTCOSTOBJECT2● DTCOSTOBJECT3● DTCOSTOBJECT4● DTCOSTOBJECT5● EMPLOYEE● LINEITEM● LINEITEMDETAIL● PERIOD● RESOURCEDRIVER● RESPCENTER● REVENUETYPE● SERVICE● SPREAD● USERRULE● VERSION● WORKSHEET1● WORKSHEET2


● BOUNDARY● ICON● METRIC● OBJECTIVE

NotePlease be aware of the limitations imposed by the reserved names in software. For more information, refer to the note on reserved names in Structural tables.


The PP_ACTIVITY_ALIAS_LOADMAIN procedure transforms data from the PPLOAD_ACTIVITY_AL staging table and writes to the PP_ACTIVITY_NAME physical table.


Data Loader


The pkgPP_ACTIVITY_ALIAS package transforms data from the PPLOAD_ACTIVITY_AL staging table and writes to the PP_ACTIVITY_NAME physical table.

4.2.2.2.1 Alias Data Load

When an alias load is started, and sub procedures or functions are executed, entries are written to the PPLOAD_LOG table.

All procedures and packages transform data from the PPLOAD_#_AL or OMLOAD_#_AL staging tables.

Where source data passes validation, the results are written into the PP_#_NAME table depending on the attribute flag setting.


1. Check that the supplied model identifier is valid.2. Check that the supplied load identifier is valid.3. Check that the supplied user identifier is valid.4. Gather statistics if the INSTATS parameter is set to one (true).5. Check that the supplied data alias name exists. if it does not exist, create it in the EPO_DATA_ALIAS table.6. Flag any aliases in the load dataset that are duplicates, and leave just the one copy.7. Flag any alias name starting with EPO as invalid, where the loadstatus is 1.8. Flag any alias names which already exist in this dimension where the load status is 1 for later use.9. Flag any names that are already used elsewhere in the system where the load status is set to 1.

Write steps:

1. Add any new alias names for the supplied data alias name.2. Update any existing alias names.3. Update the loadstatus for processed items.

4.2.2.3 Property Procedures and Packages

The property loading procedures and packages are all identical, but they each also have an associated staging table and dimension table. The following table lists the names of the property procedures and packages that are available for loading purposes:


RDBMSProperty Loading Procedures/Packages Staging Tables Property Physical Tables


● EPO_PROPERTY_LOADMAIN

● EPO_PROPERTYITEM_LOADMAIN

● EPOLOAD_PROPERTY● EPOLOAD_PROPERTY

ITEM

● EPO_MODEL_PROPERTY

● EPO_MODEL_PROPERTY_VALUE

Oracle ● pkgEPO_PROPERTY● pkgEPO_PROPERTYI

TEM

4.2.2.3.1 Property Data Load


1. Check that the supplied model identifier is valid.2. Check that the supplied load identifier is valid.3. Check that the supplied user identifier is valid.4. Gather statistics if the INSTATS parameter is set to one (true).5. Flag any property items in the load dataset that are duplicates, and leave just the one copy.6. Identify records with matching keys, then remove the matching records from the schema where the

loadstatus is 70.7. Flag any property names that do not exist where the loadstatus is 1 for later use.

Write steps:

1. Add all new property items that have passed validation at the root level.2. Update any existing property items for the supplied default value.3. Update the load status for processed items (apart from status 70).

4.2.2.3.2 Property Item Value Data Load

Pre-validation Steps:

1. Check that the supplied model identifier is valid.2. Check that the supplied load identifier is valid.3. Check that the supplied user identifier is valid.4. Gather statistics if the INSTATS parameter is set to one (true).5. Flag any property items in the load dataset that are duplicates, and leave just the one copy.6. Identify records with matching keys then remove matching records from the schema where the loadstatus

is 70.7. Flag any property names that do not exist where the loadstatus is 1.8. Flag any dimensions types that do not exist where the loadstatus is 1.9. Flag any dimension item names that do not exist where the loadstatus is 1.

Write steps:


Data Loader

1. Update any existing property item values for the supplied value.2. Add all new property item values that have passed validation at the root level.3. Update the loadstatus for processed items, apart from status 70.

4.2.2.4 Assignment Procedures and Packages

All assignment procedures and packages enable you to load assignment level data. The packages and procedures for loading assignments specifically follow the naming conventions listed in the table below (where # represents the assignment name):

RDBMSAssignment Loading Procedures/Packages Staging Tables Writes to Physical Tables


● PP_#_LOADMAIN● OM_#_LOADMAIN

● PPLOAD_# ● OMLOAD_#

● PP_#● OM_#

Oracle ● pkgPP_#● pkgOM_#

Use the assignment names listed below to replace the # in the standard naming convention to obtain the full name of each procedure/package or table:

NoteProcedures/packages marked with an asterisk DO NOT use the @INREPLACE parameter

Procedures/packages that are prefixed with PP and write to one physical table:

● ACTIVITYREASSIGN● LINEITEMDIRECT_ACTIVITY● LINEITEMRESOURCEDRIVER● SERVICEDIRECT_ACTIVITY● SERVICERESOURCEDRIVER● ASSRESPCENTERACTIVITY *● RESPCENTERSERVICE *

The following two assignment procedures/packages write to multiple tables:

● COSTOBJECTASSIGNMENT - writes to the following tables:○ PP_COSTOBJITEM○ PP_COSTOBJECTASSIGNMENT

RestrictionCost Object Drivers must be loaded before Cost Object Assignments. This means that data must exist in the PP_COSTOBJECTDRIVER table before the Cost Object Assignments can be loaded into the PP_COSTOBJECTASSIGNMENT table.

● COSTOBJECTDRIVER - writes to the following tables:


○ PP_COSTOBJITEM○ PP_COSTOBJECTDRIVER○ PP_HVCOSTOBJECTDRIVER (For Transactional Costing model types)


● ASSMETRICEMPLOYEE *● ASSMETRICRESPCENTER *● ASSOBJECTIVEEMPLOYEE *● ASSOBJECTIVELOBJECTIVE *● ASSOBJECTIVEMETRIC *● ASSOBJECTIVERESPCENTER *● OVRMETRICEMPLOYEE● OVROBJECTIVEEMPLOYEE


The PP_ACTIVITYREASSIGN_LOADMAIN procedure transforms data from the PPLOAD_ACTIVITYREASSIGN staging table and writes to the PP_ACTIVITYREASSIGN physical table.


The pkgPP_ACTIVITYREASSIGN package transforms data from the PPLOAD_ACTIVITYREASSIGN staging table and writes to the PP_ACTIVITYREASSIGN physical table.

4.2.2.4.1 Assignment Data Load

In addition to the actual dimensions, model structure can also be defined by assignments. Due to the nature of assignments, there is a dependency on the pre-existence of a dimension structure. The validation for assignment load(s) centers around the pre-existence of supplied names in the model.

When assignments are loaded, a direct one to one mapping exists between the source load table and the destination physical assignment table. However, there are two exceptions to this rule; these are the Cost Object Driver (PP_COSTOBJECTDRIVER) and Cost Object Assignment (PP_COSTOBJECTASSIGNMENT) tables. When these two types of assignments are loaded, drivers must be loaded before assignments.

All assignment procedures generally follow a similar format. Initially the model, load and user details are validated, and then each dimension that makes up the value key (and all other values), is checked to ensure that the item exists in the relevant model dimension. If an item is found that does not exist, the record is flagged with the relevant loadstatus code, and the procedure is moved on to the next record in the staging table.


1. Check that the supplied model identifier is valid2. Check that the supplied load identifier is valid.


Data Loader

3. Check that the supplied user identifier is valid.4. Flag any records in the load dataset that are duplicates, and leave just the one copy.5. Identify records with matching keys, and then remove matching records from the schema where the

loadstatus is 70.

Write steps:

1. Add all new assignment items that have passed validation at the root level.2. Update any existing assignment items for the supplied default value.3. Update the load status for processed items (apart from status 70).

4.2.3 Value Procedures and Packages

All value procedures and packages enable you to load values directly into the software tables. The procedures and packages for loading values specifically follow the naming conventions listed in the table below (where # represents the value name):

RDBMSValue Loading Procedures/Packages Staging Tables Writes to Physical Tables


● PP_#_LOADMAIN● OM_#_LOADMAIN

● PPLOAD_# ● OMLOAD_#

● PP_#● OM_#

Oracle ● pkgPP_#● pkgOM_#

Use the value names listed below to replace the # in the standard naming convention to obtain the full name of each procedure/package or table:

NoteProcedures marked with one asterisk (*) DO NOT use the @INREPLACE parameter, and those procedures marked with two asterisks (**) do not use either @INREPLACE or @INSUM parameters.

Procedures/packages that are prefixed with PP and write to one physical table:

● BOMMAKEUP● BOMPRODUCTION● BOMUNITSSOLD● CURRENCYRATES● DEFAULTBOMMAKEUP *● EMPLOYEERDS● HVEXTACTCOUNITRATE● EXTERNALACTIVITYVALUE● EXTERNALBOMUNITRATE● EXTERNALCOSTOBJECTVALUE● HVACTIVITYDRIVERVOLUME● LINEITEMDETAILVALUE


● LINEITEMFIXEDVALUE● LINEITEMVARVALUE● REVENUE● SERVICEFACTOR● SPREADVALUE● WORKSHEETVALUE

The following set of value procedures/packages write to multiple tables:

● ACTIVITYDRIVERVALUE - writes to the following tables:○ PP_ACTIVITYDRIVERVALUE○ PP_ACTIVITYDRIVERDELTA○ PP_ACTIVITYDRIVERTARGET

● LINEITEMVALUE - writes to the following tables:○ PP_LINEITEMVALUE○ PP_LINEITEMDELTA

● RESOURCEDRIVERSPLIT - writes to the following tables:○ PP_RESOURCEDRIVERSPLIT○ PP_RESOURCEDRIVERDSPLIT○ PP_RESOURCEDRIVERTARSPLIT

● RESOURCEDRIVERVALUE - writes to the following tables:○ PP_RESOURCEDRIVERVALUE○ PP_RESOURCEDRIVERDELTA○ PP_RESOURCEDRIVERTARGET

● SERVICEDRIVERVALUE - writes to the following tables:○ PP_SERVICEDRIVERVALUE○ PP_SERVICEDRIVERDELTA○ PP_SERVICEDRIVERTARGET

Procedures/packages that are prefixed with OM and write to one physical table :

● BOUNDARYINFO **● EMPLOYEEB **● EMPLOYEEBOUNDARY● ICONVALUE **● METRICADJUSTMENT● METRICADJUSTTARGET● METRICBASEPOINT● METRICACTUAL● METRICTARGET● METRICBOUNDARY● METRICB **● OBJECTIVEADJUSTMENT● OBJECTIVEADJUSTTARGET● OBJECTIVEACTUAL● OBJECTIVEBOUNDARY


Data Loader

● OBJECTIVEBASEPOINT● OBJECTIVETARGET● OBJECTIVEWEIGHTING● OBJECTIVEB **● OBJMETRICWEIGHTING

ExampleMicrosoft SQL Server/SAP Adaptive Server Enterprise: PP_ACTIVITYDRIVERVALUE_LOADMAIN

The staging tables contain either a single or multiple value(s) populating a single destination table, or multiple values populating multiple tables. For the tables populating multiple tables, there are additional parameters in the procedure header.

For example, the PP_ACTIVITYDRIVERVALUE_LOADMAIN procedure extracts its source data from the PPLOAD_ACTIVITYDRIVERVALUE staging table and loads it into the following tables:

1. PP_ACTIVITYDRIVERVALUE2. PP_ACTIVITYDRIVERDELTA3. PP_ACTIVITYDRIVERTARGET

The procedure header therefore also contains parameters to indicate if you wish to load data into tables (2) and (3) as shown above in addition to the default table (1). The additional parameters use the following naming convention @INLOAD# where the # refers to the type of data value. The parameter must be set to either one (true) or zero (false), depending on the data contained within the staging table.

The parameters for the PP_ACTIVITYDRIVERVALUE_LOADMAIN procedure are:

@INAUDITUSERID INT @INMODELID INT@INLOADID INT@INACTIVITYDRIVERDELTA BIT@INACTIVITYDRIVERTARGET BIT @INSTATS BIT

Related Information

Value Tables [page 79]

4.2.3.1 Value Data Load

These are data only related procedures and generally, validation centers on ensuring that the supplied names exist in the model being loaded. Cases exist where one loading table can supply more than one database table. An example of this is the Line Item Value procedure, where one record can potentially create two rows in the software schema, one in PP_LINEITEMVALUE and the other in PP_LINEITEMDELTA, assuming that the VALUE and the DELTAVALUE fields in the staging table are not zero.

The following sections detail the validation steps taken for the value procedures. All value procedures generally follow a similar format. Initially the model, load and user details are validated, and then each dimension making


up the value key is checked to ensure that the item exists in the relevant model dimension. If an item is found that does not exist, the record will be flagged with the relevant loadstatus code, and the procedure is moved on to the next record in the staging table.


1. Check that the supplied model identifier is valid.2. Check that the supplied load identifier is valid.3. Check that the supplied user identifier is valid.4. Flag any records in the load dataset that are duplicates, and leave just the one copy.5. Identify records with matching keys, and then remove matching records from the schema where the

loadstatus is 70.6. The relevant dimension checks will be carried out.

Write steps:

1. Add data into the value table.2. Update the load status for processed items (apart from status 70).

4.3 Performing a Data Load

The load procedures for structural and value data must be executed in the following order:

1. Dimension2. Alias3. Property4. Assignment5. Value

Example scripts are provided below that illustrate how a data load is performed.

Alternatively, the Execute Data Loader Routines procedure automatically performs the Structural, Alias, Assignment and Value Load procedures in the correct order, so that they do not need to be run individually. This can be run by executing the stored procedure or as a console command (for further information on console commands, refer to the SAP BusinessObjects Profitability and Cost Management Console User Guide).

ExampleSAP Adaptive Server Enterprise Data Loader Script

A sample script to load Cost Object dimension data and associated Activity Driver values:

BEGIN -- Declare variablesDECLARE @INAUDITUSERID INTDECLARE @INREPLACE BITDECLARE @INSTATS BITDECLARE @INPCMODELID INTDECLARE @INPCLOADID INTDECLARE @INLOADDELTA INTDECLARE @INLOADTARGET INTDECLARE @RETCODE INT-- Assign variable valuesSET @INAUDITUSERID = 1


Data Loader

SET @INREPLACE = 0SET @INSTATS = 0SET @INLOADDELTA = 0SET @INLOADTARGET = 0---- Get ModelID--SELECT @INPCMODELID = ID FROM EPO_MODELS WHERE MODELNAME = 'PCMainID'---- Get LoadID--SELECT @INPCLOADID = MAX(LOADID) FROM PP_FASTLOAD WHERE MODELID = @INPCMODELID------ Call procedures to load data from PPLOAD_COSTOBJECT1_DH, PPLOAD_COSTOBJECT1_AL,-- PPLOAD_COSTOBJECT2_DH/AL and PPLOAD_ACTIVITYDRIVERVALUE----EXEC @RETCODE = [DBO].[PP_COSTOBJECT1_DIMENSION_LOADMAIN] @INAUDITUSERID, @INPCMODELID, @INPCLOADID, @INREPLACE, @INSTATSEXEC @RETCODE = [DBO].[PP_COSTOBJECT1_ALIAS_LOADMAIN] @INAUDITUSERID, @INPCMODELID, @INPCLOADID, @INSTATSEXEC @RETCODE = [DBO].[PP_COSTOBJECT2_DIMENSION_LOADMAIN] @INAUDITUSERID, @INPCMODELID, @INPCLOADID, @INREPLACE, @INSTATSEXEC @RETCODE = [DBO].[PP_COSTOBJECT2_ALIAS_LOADMAIN] @INAUDITUSERID, @INPCMODELID, @INPCLOADID, @INSTATSEXEC @RETCODE = [DBO].[PP_ACTIVITYDRIVERVALUE_LOADMAIN] @INAUDITUSERID, @INPCMODELID, @INPCLOADID, @INLOADDELTA, @INLOADTARGET, @INSTATS ENDGO

ExampleMicrosoft SQL Server Data Loader Script


BEGIN -- Declare variablesDECLARE @INAUDITUSERID INT;DECLARE @INREPLACE BIT;DECLARE @INSTATS BIT;DECLARE @INPCMODELID INT;DECLARE @INPCLOADID INT;DECLARE @INLOADDELTA INT;DECLARE @INLOADTARGET INT;DECLARE @RETCODE INT;-- Assign variable valuesSET @INAUDITUSERID = 1;SET @INREPLACE = 0;SET @INSTATS = 0;SET @INLOADDELTA = 0;SET @INLOADTARGET = 0;---- Get ModelID--SELECT @INPCMODELID = ID FROM EPO_MODELS WHERE MODELNAME = 'PCMainID';---- Get LoadID--SELECT @INPCLOADID = MAX(LOADID) FROM PP_FASTLOAD WHERE MODELID = @INPCMODELID;----


-- Call procedures to load data from PPLOAD_COSTOBJECT1_DH, PPLOAD_COSTOBJECT1_AL,-- PPLOAD_COSTOBJECT2_DH/AL and PPLOAD_ACTIVITYDRIVERVALUE----EXEC @RETCODE = [DBO].[PP_COSTOBJECT1_DIMENSION_LOADMAIN] @INAUDITUSERID, @INPCMODELID, @INPCLOADID, @INREPLACE, @INSTATS;EXEC @RETCODE = [DBO].[PP_COSTOBJECT1_ALIAS_LOADMAIN] @INAUDITUSERID, @INPCMODELID, @INPCLOADID, @INSTATS;EXEC @RETCODE = [DBO].[PP_COSTOBJECT2_DIMENSION_LOADMAIN] @INAUDITUSERID, @INPCMODELID, @INPCLOADID, @INREPLACE, @INSTATS;EXEC @RETCODE = [DBO].[PP_COSTOBJECT2_ALIAS_LOADMAIN] @INAUDITUSERID, @INPCMODELID, @INPCLOADID, @INSTATS;EXEC @RETCODE = [DBO].[PP_ACTIVITYDRIVERVALUE_LOADMAIN] @INAUDITUSERID, @INPCMODELID, @INPCLOADID, @INLOADDELTA, @INLOADTARGET, @INSTATS;ENDGO

ExampleOracle Data Loader Script


SET LINES 1000 SET PAGES 1000SPOOL D:\DATALOADER_ORACLE\RESULTS\P1RunLoadID.txtSET SERVEROUTPUT ONBEGINDBMS_OUTPUT.ENABLE (BUFFER_SIZE => 1000000);END;/-- Declare and assign variable valuesDECLAREINAUDITUSERID NUMBER := 1;INREPLACE BOOLEAN := FALSE;INATTRIBUTEMERGE BOOLEAN := FALSE;INDELETEMATCHINGKEYS BOOLEAN := FALSE;INDELETEZEROVALUES BOOLEAN := FALSE;INSTATS BOOLEAN := FALSE;INPCLOADID NUMBER;INPCMODELID NUMBER;RETCODE NUMBER;BEGIN---- Get ModelID--SELECT ID INTO INPCMODELID FROM EPO_MODELS WHERE MODELNAME = 'PCMainID';---- Get LoadID--SELECT MAX(LOADID) INTO INPCLOADID FROM PP_FASTLOAD WHERE MODELID = INPCMODELID;------ Call procedures to load data from PPLOAD_COSTOBJECT1_DH, PPLOAD_COSTOBJECT1_AL,-- PPLOAD_COSTOBJECT2_DH/AL and PPLOAD_ACTIVITYDRIVERVALUE----RETCODE := PKGPP_COSTOBJECT1_DIMENSION.MAIN(INPCMODELID, INPCLOADID, INAUDITUSERID, INREPLACE, INATTRIBUTEMERGE, INSTATS);RETCODE :=PKGPP_COSTOBJECT1_ALIAS.MAIN(INPCMODELID, INPCLOADID, INAUDITUSERID, INSTATS);RETCODE :=PKGPP_COSTOBJECT2_DIMENSION.MAIN(INPCMODELID, INPCLOADID, INAUDITUSERID, INREPLACE, INATTRIBUTEMERGE, INSTATS);


Data Loader

RETCODE :=PKGPP_COSTOBJECT2_ALIAS.MAIN(INPCMODELID, INPCLOADID, INAUDITUSERID, INSTATS);RETCODE := PKGPP_ACTIVITYDRIVERVALUE.MAIN(INPCMODELID, INPCLOADID, INAUDITUSERID, INDELETEZEROVALUES, INSTATS);COMMIT;END;/SPOOL OUTEXIT

4.3.1 Execute Data Loader Routines Procedure

For users setting up a large model, the Execute Data Loader Routines procedure automatically performs the dimension, alias, property, assignment and value load procedures and packages in the correct order, so that they do not need to be run individually.

Refer to the “Data Loader Parameters” section for which parameters can be used with the PP_EXECUTEDLROUTINES stored procedure.

Example

SET SERVEROUTPUT ON DECLARE outID INT;BEGIN PP_EXECUTEDLROUTINES (1,1,10001,0,0,0,1,outID); DBMS_OUTPUT.PUT_LINE(outID);END;/

Related Information

Data Loader Parameters [page 19]

4.3.2 Transforming Data from an Existing Model

A Microsoft SQL/SAP ASE procedure procedure and an Oracle exposed function is available to enable you to build the staging tables with data from an existing model. Each of these requires the ID of the source data model, the ID of the destination model (the model must have been created before running this procedure), a load ID and a User ID. Both methods for each database system are shown in the examples below:


ExampleMicrosoft SQL/SAP ASE: ExportToLoad Procedure

Each dimension, alias, property assignment and value procedure has a function called ExportToLoad. This procedure has the following associated parameters:

@INAUDITUSERID INT @INSOURCEMODELID INT@INDESTINATIONMODELID INT @INLOADID INT

ExampleOracle: ExportToLoad Function

Each dimension, alias, property, assignment and value package has a function called ExportToLoad. This function has the following associated parameters:

FUNCTION exporttoload ( inSourceModelID IN NUMBER,inDestinationModelID IN NUMBER,inLOADID IN NUMBER,inAUDITUSERID IN NUMBER) RETURN NUMBER;

4.3.3 Refreshing the Model

Once data loading is complete, the EPO_REFRESHMODELDATA procedure must be called to ensure that the loaded data appears in the model. The model ID and load ID parameters must be included in the command as shown in the example below.

On successful execution of this command, a record is written to the EPO_DBCONFIG table, that signifies that a data refresh is required by the middle tier. The middle tier periodically polls this table, and on finding such a record refreshes all data.

ExampleMicrosoft SQL: EPO_REFRESHMODELDATA

EXEC EPO_REFRESHMODELDATA @INMODELID, @INLOADID;

ExampleOracle: EPO_REFRESHMODELDATA

pkgEPOProcs.refreshModelData (MODELID LOADID);

ExampleSAP ASE: EPO_REFRESHMODELDATA

EXEC EPO_REFRESHMODELDATA @INMODELID, @INLOADID


Data Loader

go

4.4 Follow-up Activities

After a data load has completed, there are various tasks that can be performed, including housekeeping to clear data out of the staging tables that were used during the data loading procedure, and to check for any possible errors that may have occurred.

4.4.1 Data Loader Completion Checks

There are two methods of checking the completion status of the data load:

1. Database Loadstatus codes:On successful procedure completion, a code of zero is returned from the main function. If the code is not zero, check the returned error code and look in the error tables for any additional information.The load tables may also be checked via the Loadstatus, this gives an indication as to the state of a given record.

2. Model Alerts:1. Microsoft SQL Server/SAP Adaptive Server Enterprise:

When loading data, an additional set of procedures is provided to populate alerts in the application for any records that failed validation. Each dimension and alias has a procedure called PP_#_DIMENSION_WRITEALERTS or PP_#_ALIAS_WRITEALERTS and if used, it is called after running the relevant dimension or alias load. All writealert procedures contain the following parameter list:

@INAUDITUSERID INT @INMODELID INT@INLOADID INT@INCLEARLOADING BIT @OUTROWCOUNT INT OUTPUT

In addition to the standard model, load and user details, there are two additional parameters:○ If the INCLEARLOADING parameter is set to one (true), which is the default, the records from the

staging table are cleared down from the staging table after processing has completed. If the INCLEARLOADING parameter is set to zero (false), the records remain in the staging table.

○ The OUTROWCOUNT parameter value is generated during the procedure processing and returns the number of alerts produced during the load.

2. Oracle:When loading data, an additional method is provided that populates alerts in the application for any records that failed validation. Each dimension and alias package contains a function called WriteAlerts, and if this is used, it is called after running the relevant dimension or alias load.

FUNCTION WriteAlerts ( inModelID IN NUMBER,inLoadID IN NUMBER,inAuditUserID IN NUMBER,outAlertCount OUT NUMBER,


inClearLoading IN BOOLEAN := TRUE ) RETURN NUMBER;

In addition to the standard model, load, and user details, there are two additional parameters:○ The outAlertcount parameter value is generated during the package processing and returns the

number of alerts produced during the load.○ If the inClearLoading parameter is set to True, which is the default, the records from the staging

table are cleared down from the staging table after processing has completed. If the inClearLoading parameter is set to False, the records remain in the staging table.

Related Information

Loadstatus Field Values and Constant Names [page 44]

4.4.2 Stage Table Management

An additional set of Microsoft SQL/SAP ASE procedures and Oracle exposed functions are available for removing data from staging tables, and you may wish to manage this via another script.

The CLEAR function removes all data from the associated stage table for the supplied model and load combination.

The DELETE function removes all data from the associated stage table for the supplied model and load combination for any record combination where the value of the date is less than the supplied date.

ExampleMicrosoft SQL/SAP ASE: Clear and Delete Procedures and Parameters

The naming conventions for the Microsoft SQL procedures are listed below, where # refers to a structural type and ## refers to a value type:

● PP_#_DIMENSION_CLEAR● PP_#_DIMENSION_DELETE● PP_#_ALIAS_CLEAR● PP_#_ALIAS_DELETE● PP_##_CLEAR● PP_##_DELETE

For example:

PP_#_DIMENSION_CLEAR associated parameters:

@INAUDITUSERID INT @INMODELID INT @INLOADID INT

PP_#_DIMENSION_DELETE associated parameters :

@INAUDITUSERID INT @INMODELID INT


Data Loader

@INLOADID INT @INDATE DATETIME

ExampleOracle: Clear and Delete functions

All packages include additional exposed methods for removing data from staging tables, and this may be managed via another script. The following two method calls are available:

FUNCTION clear ( inModelID IN NUMBER,inLOADID IN NUMBER, inAUDITUSERID IN NUMBER) RETURN NUMBER;FUNCTION delete (inModelID IN NUMBER, inLOADID IN NUMBER,inDate IN DATE,inAUDITUSERID IN NUMBER) RETURN NUMBER;

4.5 Troubleshooting Data Loader

The following information is available for troubleshooting Data Loader:

● Data Loader logging - The PPLOAD_LOG table contains information about when the data load started and finished.

● Table of Loadstatus field values and constant names - The Constant name is a variable in a Data Loader script. A Loadstatus value is passed into the constant for each record as it is processed, and the value is then recorded into the relevant table to check after the load has finished.

● Error Codes - Exception errors that may be displayed during a data load for a particular error code.

4.5.1 Data Loader Activity Logging

As each procedure, package or function is called, an entry is written to the PPLOAD_LOG table detailing when the procedure or package was called and when it ended. The following scripts format the output into a more legible format:

ExampleMicrosoft SQL/SAP ASE script

select id, description, dateentered from ppload_log

ExampleOracle script

COLUMN description FORMAT a30 wrap;


select id,description, to_char(dateentered,'hh:mi:ss')from ppload_log

Related Information

PPLOAD_LOG [page 63]

4.5.2 Loadstatus Field Values and Constant Names

The following table lists all of the current values for the LOADSTATUS field, that appears in all staging table definitions, and the actual constant names.

LOADSTATUS Field Value Description

Constant Names


0 Self-referencing parent-child relationship. selfRefParChild c_ls_selfrefparchild

1 Record is unprocessed. udfUNPROCESSED c_ls_unprocessed

2 Name starts with “EPO” this is not allowed. udfISEPOCODE c_ls_isepocode (bar any name beginning with “EPO”)

3 A duplicate key set has been found in the load dataset.

udfDUPLICATE c_ls_duplicate

4 The name already exists in one of the software dimensions.

udfALREADYEXISTS c_ls_aleadyexist

5 The name exists in the dimension being loading into.

udfEXISTSINTHISDIM c_ls_existinthisdim

7 The attribute flag number supplied is invalid.

udfINVALIDATTRIBUTEFLAG

c_ls_invalid_attribute_flag

8 A duplicate key set has been found in the load dataset.

udfDUPLICATEKEY c_ls_duplicatekey

9 The record has been processed. udfPROCESSED c_ls_processed

10 The Version name does not exist (Values). udfVERSIONNAMENOTEXIST c_ls_version_name

11 The Period name does not exist (Values). udfPERIODNAMENOTEXIST c_ls_period_name

12 The Responsibility Center name does not exist (Values).

udfRESPCENTERNAMENOTEXIST

c_ls_respcenter_name

13 The Line Item name does not exist (Values).

udfLINEITEMNAMENOTEXIST

c_ls_lineitem_name

14 The Activity name does not exist (Values). udfACTIVITYNAMENOTEXIST

c_ls_activity_name


Data Loader


Constant Names


15 The Costobject1 name does not exist (Values).

udfCOSTOBJECT1NAMENOTEXIST

c_ls_costobject1_name













20 The Revenue Type name does not exist (Values).

udfREVENUETYPENAMENOTEXIST

c_ls_revenuetype_name

21 The Currency name does not exist (Values).

udfCURRENCYNAMENOTEXIST

c_ls_currency_name

22 The Resource driver name does not exist (Values).

udfRESOURCEDRIVERNAMENOTEXIST

c_ls_resourcedriver_name

23 The Activity Driver name does not exist (Values).

udfACTIVITYDRIVERNAMENOTEXIST

c_ls_activitydriver_name

24 The Service name does not exist (Values). udfSERVICENAMENOTEXIST c_ls_service_name

25 The Spread name does not exist (Values). udfSPREADNAMENOTEXIST c_ls_spread_name

26 The Worksheet1 name does not exist (Values).

udfWORKSHEET1NAMENOTEXIST

c_ls_worksheet1_name

27 The Worksheet2 name does not exist (Values).

udfWORKSHEET2NAMENOTEXIST

c_ls_worksheet2_name

28 The Capacity name does not exist (Values). udfCAPACITYRULENAMENOTEXIST

c_ls_capacityrule_name

29 The User Rule name does not exist (Values).

udfUSERRULENAMENOTEXIST

c_ls_userrule_name

30 The Icon name does not exist (Values). udfICONNAMENOTEXIST c_ls_icon_name

31 The Boundary name does not exist (Values).

udfBOUNDARYNAMENOTEXIST

c_ls_boundary_name

33 The Line Item Detail name does not exist (Values).

udfLINEITEMDETAILNAMENOTEXIST

c_ls_lineitemdetail_name

35 The Objective name does not exist (Values).

udfOBJECTIVENAMENOTEXIST

c_ls_objective_name

36 The Metric name does not exist (Values). udfMETRICNAMENOTEXIST c_ls_metric_name



Constant Names


37 The Initiative name does not exist.

38 The Employee name does not exist (Values).

udfEMPLOYEENAMENOTEXIST

c_ls_employee_name

40 The Detail Cost Object 1 name does not exist (Values).

udfDTCOSTOBJECT1NAMENOTEXIST

c_ls_dtcostobject1_name













50 The Property name does not exist (Properties).

udfPROPERTYNAMENOTEXIST

c_ls_property_name_not_exist

51 The dimension name does not exist (Properties).

udfDIMENSIONNAMENOTEXIST

c_ls_dim_name_not_exist

52 The dimension item name does not exist (Properties).

udfDIMENSIONITEMNAMENOTEXIST

c_ls_dim_item_name_not_exist

53 The default alias does not exist (Alias). udfDEFAULTALIASNOTEXIST

c_ls_default_alias_not_exist

54 The item name is a software reserved name.

udfRESERVEDNAME c_ls_reserved_name

55 The attribute mapping parent does not exist (attribute mappings).

udfATTRIBUTEPARENTNOTEXIST

c_ls_attrib_parent_not_exist

56 The attribute mapping child does not exist (attribute mappings)

udfATTRIBUTECHILDNOTEXIST

c_ls_attrib_child_not_exist

57 The dimension does not allow hierarchical structures (Currency and Boundary)

udfSTRUCTURENOTALLOWED c_ls_structure_not_allowed

59 The consolidation type is not valid. udfCONSOLTYPENOTEXIST c_ls_invalid_consol_type

60 The version/period combination has been locked (Values).

udfVERSIONPERIODLOCKED c_ls_version_period_locked

61 Component does not exist in the model. udfComponentNameNOTEXIST

c_ls_component_name

62 Null values are not allowed. udfNullNotAllowed c_ls_null_not_allowed


Data Loader


Constant Names


70 For flagging records to delete (Properties). udfUNDELETEMATCHINGKEYS

c_ls_delete_matching_keys

85 The Measure name does not exist (Values). udfMEASURENAMENOTEXIST c_ls_measure_name

86 Data not allowed at Detail Cost object 1 udfDATANOTALLOWEDATGROUPDC01()

c_ls_DataNotAllowedAtGrDC01









91 Record containing a zero value cannot be loaded. Not a valid action. This primarily applies to the External Activity Cost Object Unit Rate table.

udfDISALLOWZEROVALUE c_ls_DisallowZeroValue

92 The Transactional Costing detail volume data cannot be loaded against an Activity Driver that is not marked as a Transactional Costing Activity Driver.

udfNOTHVACTIVITYDRIVER c_ls_NotHVactivityDriver

93 The Default Bill Of Materials Makeup Cost Object 1 item must exist as a leaf level item, not a group level item.

udfBOMMAKEUPCO1 c_ls_BOMMakupCo1

94 The Default Bill Of Materials Makeup component item must exist as a leaf level item, not a group level item.

udfBOMMAKEUPCOMP c_ls_BOMMakupComp

95 Any Version and Period based Bill Of Materials Makeup must already exist as a Default Bill Of Materials Makeup.

udfNOTEXISTASDEFAULTBOM

c_ls_NotExistAsDefaultBOM

100 Version name supplied for the Version/Period deletion does not exist.

101 Period name supplied for the Version/Period deletion does not exist.

102 The Version/Period deletion failed. udfVPDELETEFAILED c_ls_vp_delete_fail

110 The Actual Resource Driver item does not exist in the model.

udfARESOURCEDRIVERNAMENOTEXIST

c_ls_AResourceDriver_Name

111 The Target Responsibility Center item does not exist in the model.

udfTARGETRESPCENTERNAMENOTEXIST

c_ls_TargetRespCenter_Name



Constant Names


112 The Target Activity item does not exist in the model.

udfTARGETACTIVITYNAMENOTEXIST

c_ls_TargetActivity_Name

113 The Line Item type for Cost Object Assignments is not set correctly.

udfLINEITEMTYPENOTCORRECT

c_ls_LIType_InCorrect

114 The Cost Object type for Assignments is not set correctly.

udfCOSTOBJECTTYPENOTCORRECT

c_ls_CO1Type_InCorrect

115 The Cost Object for Assignment does not exist.

udfCOSTOBJECTASSNOTEXIST

c_ls_COASS_not_exist

116 Line Item, Service, or Activity for an Assignment does not exist.

udfLINEITEMACTIVITYASSNOTEXIST

c_ls_LIASS_not_exist

120 Activity Driver 1 does not exist in the model for the current Cost Object Driver.

udfACTIVITYDRIVER1NAMENOTEXIST

c_ls_AD1Name_not_exist













125 The specified type for Volume Responsibility Center 1 is incorrect. (0 - All, 1 - Parent, 2 - Current, 3007 - RC Unassigned)

udfVOLRESPCENTER1NAMEINCORRECT

c_ls_VOLRespcenter1_not_valid













130 The specified order for Cost Object 1 is out of range. Valid range is 1 - 5.

udfDRIVERORDER1NAMENOTVALID

c_ls_DrOr1_not_valid





Data Loader


Constant Names











4.5.3 Data Loader Error Codes

The following table lists the error codes and corresponding exception messages that may occur during the use of Data Loader:

Error Code

Description


50001 20001 When calling a procedure/package, a model identifier has been supplied that is not valid.

50002 20002 When calling a procedure/package, a load identifier has been supplied that is not valid.

50003 20003 When calling a procedure/package, a user identifier has been passed that is not valid.

Not supported 20004 When calling a package, a model name has been passed that is not valid.

Not supported 20005 When calling a package, a user name has been passed that is not valid.

Not supported 20006 An exception has occurred when calling the bulk collect method.

50007 20007 An exception has occurred because the model status is not valid.

50008 20008 An exception has occurred because the user status is not valid.

50010 20010 An exception has occurred because the audit table name does not exist.

50030 20030 Please re-check credentials, there has been a problem.

50112 20112 The supplied version name (version_name) does not exist as a default alias.

50113 20113 The supplied period name (period_name) does not exist as a default alias.

50114 20114 The supplied version period table name (table_name) does not exist in the lookup table.

50115 20115 The supplied table name (table_name) does not exist in the lookup table.


Error Code

Description


50116 20116 Not possible to remove all version period combinations for ModelID: (modelID), and LoadID: (LoadID). Please check Loadstatus.

50117 20117 Remove all set incorrectly.

50118 20118 Unsupported name (name).


Data Loader

5 Maintenance

To ensure optimum database performance, routine maintenance is required as part of a regular schedule for any database. The purpose of the following recommendations is to ensure that you have a stable and reliable system that is properly maintained and is able to return online as soon as possible in the event of unforeseen circumstances.

The Database Administrator (DBA) is typically responsible for the maintenance of the databases and ensuring that robust backup and recovery plans are in place.

It is recommended that a DBA is allocated to the database server following the initial installation, to ensure a robust environment for your development project and migration to a production environment.

5.1 Restoring the Database

Prerequisites

Firstly, you must ensure that all users are logged out of the software before the system can be restored from backup. Use the SAP BusinessObjects Profitability and Cost Management User Monitor and/or the SAP BusinessObjects Profitability and Cost Management System Information tools on the application server to monitor user logon activity.

Context

To restore the system from the backup files, perform the following steps:

Procedure

1. Click Start Programs SAP BusinessObjects Profitability and Cost Management Tools Service Manager , and double-click the PCMServer icon in the system tray.

2. In the SAP BusinessObjects Service Manager window, click Stop All.Wait until the status of all running software services changes to “Stopped”.

3. Restore the database from the appropriate database backup files by following your standard database restore procedures.

4. When the database is restored successfully, execute the EPO_RESET_SESSIONS stored procedure on the database server(s).This procedure does not require any additional parameters.

SAP BusinessObjects Profitability and Cost Management Database Administrator's GuideMaintenance P U B L I C 51

The procedure deletes any records that may exist in the EPO_SESSION_INFO table, effectively closing any user sessions that may have been open when the original backup was performed.

Any cached model results become invalid after the procedure is executed on the restored database. When a model is opened, automatic calculations start again for that model and new results are produced.

5. Inform the users that the system is available.

5.2 Data Files and Disk Space

As with any database environment, disk space and table space need to be managed carefully to gain the most from the performance of the software environments. Table fragmentation and potential database file fragmentation can both have a significant impact on performance.

Table fragmentation can be effectively managed through systematic rebuilding of the indexes and statistics inherent within the database. Database file fragmentation however, requires file system defragmentation.

5.2.1 Autogrow Setting

The DBA is responsible for setting the initial size for a tablespace, and how much to autogrow a table by. Your system may benefit from adjustments to the default autogrow setting.The following problems could arise if the setting is not appropriate for the level of database usage:

● Disk space wastage if the setting is too large.● Table fragmentation if the setting is too small, and large amounts of data are being loaded.

We recommend that the autogrow setting is amended by the DBA to optimise performance for local conditions.

5.3 Rebuilding Database Indexes and Statistics

All of the tables within the database are strategically indexed to maximize performance. These indexes need to be maintained as part of a regular maintenance schedule.

The indexes have an impact on the overall system performance, and it is recommended that they are regularly rebuilt, typically after loading data (using Data Bridge or Data Loader).

The same maintenance tasks also need to be applied to database statistics, and in this section you can find several examples of rebuild scripts that can be applied to your environment.

NoteAutostatistical generation is set to “on” by default in a Microsoft SQL database. We recommend that this remains configured to the default setting.


Maintenance

ExampleMicrosoft SQL Server Rebuild Indexes Script

The following script is an example Microsoft SQL Server script that may be used for regular rebuilding of the indexes and statistics on the core database. It can be executed either within SQL Query Analyzer, or DTS as an interim task, or as a maintenance plan.

PRINT 'Rebuild of PCM Indexes is Starting'; DECLARE @FRAGMENTATION_THRESHOLD float = 30; -- percentage above which indexes should be defragmented (set to NULL to defrag ALL indexes)DECLARE @table_name sysname, @index_name sysname;DECLARE @index_id int, @frag_pc float, @rebuild_sql varchar(200);DECLARE cur_index_rebuild CURSOR FORSELECT a.index_id, o.name as table_name, b.name as index_name, avg_fragmentation_in_percent,'ALTER INDEX ' + b.name + ' ON [' + s.name + '].[' + o.name + '] REBUILD PARTITION = ALL' as RebuildSQLFROM sys.dm_db_index_physical_stats (DB_ID(), NULL, NULL, NULL, NULL) AS aJOIN sys.indexes AS b ON a.object_id = b.object_id AND a.index_id = b.index_idjoin sys.objects as o on o.object_id = a.object_idjoin sys.schemas as s on s.schema_id = o.schema_idwhere avg_fragmentation_in_percent >= ISNULL(@FRAGMENTATION_THRESHOLD, avg_fragmentation_in_percent)and a.index_id != 0;OPEN cur_index_rebuild;FETCH NEXT FROM cur_index_rebuild INTO @index_id, @table_name, @index_name, @frag_pc, @rebuild_sql;WHILE @@FETCH_STATUS = 0BEGINIF @index_id <> 255 BEGINPRINT 'Defragmenting index ' + @index_name + ' of the ' + rtrim(@table_name) + ' table';exec(@rebuild_sql);ENDFETCH NEXT FROM cur_index_rebuild INTO @index_id, @table_name, @index_name, @frag_pc, @rebuild_sql;ENDCLOSE cur_index_rebuild;DEALLOCATE cur_index_rebuild;PRINT 'Rebuild of PCM Indexes is Complete';

ExampleOracle Rebuild Indexes Script

This is an example re-index script that may be implemented on any system. The script needs to be executed before the “Rebuild Statistics” script.

Log on as the schema owner, for example; adminepo, and then run the script.

SET LINE 80; SET PAGES 1000;SET FEEDBACK OFF;SET SERVEROUTPUT ONCOLUMN MODELNAME FORMAT a20 WRAP;COLUMN TABLE_NAME FORMAT a40 WRAP;PROMPT ---------------------------------------------------------------------;PROMPT ---------------------------------------------------------------------;PROMPT ---------------------------------------------------------------------;PROMPT - DB Maintenance script (REBUILD INDEXES);PROMPT - (1/2)


PROMPT ---------------------------------------------------------------------;PROMPT ---------------------------------------------------------------------;PROMPT ---------------------------------------------------------------------;SELECT ID, MODELNAMEFROM EPO_MODELS;SPOOL c:\REBUILDINDEX.OUTDECLARECURSOR CUR_INDEX_LIST ISSELECT OBJECT_NAME, CREATED, LAST_DDL_TIME FROM USER_OBJECTS WHERE OBJECT_TYPE = 'INDEX'ORDER BY OBJECT_NAME;l_DDL_cmd VARCHAR(200);l_last_DDL_time DATE;BEGINDBMS_OUTPUT.ENABLE(buffer_size => 1000000);FOR REC_TAB_LIST IN CUR_INDEX_LISTLOOPDBMS_OUTPUT.PUT_LINE ('Preparing to rebuild index: '||REC_TAB_LIST.OBJECT_NAME);DBMS_OUTPUT.PUT_LINE (' '||to_char(REC_TAB_LIST.CREATED,'DD:MM:YYYY HH24:MI:SS')||' (Created)');DBMS_OUTPUT.PUT_LINE (' '||to_char(REC_TAB_LIST.LAST_DDL_TIME,'DD:MM:YYYY HH24:MI:SS')||' (Last DDL Time)');l_DDL_cmd := 'ALTER INDEX '||REC_TAB_LIST.OBJECT_NAME||' REBUILD';BEGINEXECUTE IMMEDIATE(l_DDL_CMD);EXCEPTIONWHEN others THENBEGINDBMS_OUTPUT.PUT_LINE(l_DDL_CMD);END;END;SELECT LAST_DDL_TIME INTO l_last_DDL_time FROM USER_OBJECTSWHERE OBJECT_NAME = REC_TAB_LIST.OBJECT_NAMEAND OBJECT_TYPE = 'INDEX';DBMS_OUTPUT.PUT_LINE (' ------------------------------------');DBMS_OUTPUT.PUT_LINE (' '||to_char(l_last_DDL_time,'DD:MM:YYYY HH24:MI:SS')||' (Last DDL Time)');DBMS_OUTPUT.PUT_LINE (' ------------------------------------');DBMS_OUTPUT.PUT_LINE ('');DBMS_OUTPUT.PUT_LINE ('');DBMS_OUTPUT.PUT_LINE ('');END LOOP; EXCEPTIONWHEN NO_DATA_FOUND THENBEGINDBMS_OUTPUT.PUT_LINE(SQLCODE);DBMS_OUTPUT.PUT_LINE(SQLERRM);END;WHEN OTHERS THENBEGINDBMS_OUTPUT.PUT_LINE(SQLCODE);DBMS_OUTPUT.PUT_LINE(SQLERRM);END;END;/SPOOL OUT


Maintenance

ExampleOracle Rebuild Statistics Script

The integrated DBMS_STATS package that is bundled with Oracle databases is a powerful series of internal measures that controls how well your Oracle database performs and provides statistics for the entire database. Keeping the database statistics up to date is vital, especially before and after the data loading process, as it assists in minimizing the load and calculate processes. If your data load process is using Data Bridge, it is recommended that the database statistics are kept properly maintained to ensure the best performance from the Data Bridge application.

This is an example script to rebuild the database statistics, that can be implemented on any system. This script must be executed after the “Re-Index” script.

The script prompts for a schema name, so when prompted just type in the schema owner, for example: adminepo.

SET LINE 80; SET PAGES 1000;SET FEEDBACK OFF;SET SERVEROUTPUT ON;COLUMN MODELNAME FORMAT a20 WRAP;COLUMN TABLE_NAME FORMAT a40 WRAP;PROMPT ---------------------------------------------------------------------;PROMPT ---------------------------------------------------------------------;PROMPT ---------------------------------------------------------------------;PROMPT - DB Maintenance script (REBUILD TABLE STATS);PROMPT - (2/2)PROMPT ---------------------------------------------------------------------;PROMPT ---------------------------------------------------------------------;PROMPT ---------------------------------------------------------------------;SELECT ID, MODELNAMEFROM EPO_MODELS;SPOOL c:\REBUILDSTAT.OUTDECLARECURSOR CUR_TAB_LIST ISSELECT TABLE_NAME, LAST_ANALYZEDFROM TABSORDER BY TABLE_NAME;l_DDL_cmd varchar(200);l_lastAnalyzed DATE;BEGINDBMS_OUTPUT.ENABLE(buffer_size => 1000000);FOR REC_TAB_LIST IN CUR_TAB_LISTLOOPDBMS_OUTPUT.PUT_LINE('Rebuild table stats for: '||REC_TAB_LIST.TABLE_NAME);DBMS_OUTPUT.PUT_LINE (' '||to_char(REC_TAB_LIST.LAST_ANALYZED,'DD:MM:YYYY HH24:MI:SS')||' (last analyzed)');DBMS_STATS.gather_table_stats(ownname => '&&SCHEMA_OWNER', tabname => REC_TAB_LIST.TABLE_NAME, estimate_percent => DBMS_STATS.AUTO_SAMPLE_SIZE,cascade => TRUE);SELECT last_analyzed INTO l_lastAnalyzedFROM TABSWHERE TABLE_NAME = REC_TAB_LIST.TABLE_NAME;DBMS_OUTPUT.PUT_LINE (' ------------------------------------');DBMS_OUTPUT.PUT_LINE (' '||to_char(l_lastAnalyzed,'DD:MM:YYYY HH24:MI:SS')||' (last analyzed)');DBMS_OUTPUT.PUT_LINE (' ------------------------------------');DBMS_OUTPUT.PUT_LINE ('-');DBMS_OUTPUT.PUT_LINE ('-');


DBMS_OUTPUT.PUT_LINE ('-');END LOOP; EXCEPTIONWHEN NO_DATA_FOUND THENBEGINDBMS_OUTPUT.PUT_LINE(SQLCODE);DBMS_OUTPUT.PUT_LINE(SQLERRM);END;WHEN OTHERS THENBEGINDBMS_OUTPUT.PUT_LINE(SQLCODE);DBMS_OUTPUT.PUT_LINE(SQLERRM);END;END;/SPOOL OUT

5.4 Microsoft SQL Server Data Compression

In a Microsoft SQL Server database, data compression can be used to give considerable savings, particularly in the amount of data that can be cached. However, this saving in I/O might be offset by CPU overheads, depending on the architecture deployed in your installation. Below are various considerations that should be taken into account, and you should also consult the Microsoft documentation to achieve best practices and results.

Row compression or page compression?

● Row compression often produces less space savings than page compression, but the CPU impact is minimal.

● Page compression utilizes row compression and can result in much higher space savings (depending on the table/index).

● Page compression requires sufficient available CPU as the reads require more CPU than for uncompressed tables.

● The CPU overhead associated with page compression can be worthwhile when compared against the I/O savings.

● Page compression can be very useful for Data Warehouse tables, as they contain a lot of repeat values.● Page compression may not be a good option for tables that have a lot of writes.● Row compression takes on average, 1.5 times the CPU time taken to rebuild an index.● Page compression takes on average, between twice and five times the CPU time taken to rebuild an index.

Offline or online compression?

● Online compression requires about twice as much CPU overhead as offline compression.● Offline compression locks the particular table that is being compressed.● With offline compression, non-clustered indexes are rebuilt one by one.● With online compression, non-clustered indexes are rebuilt simultaneously.

Sufficient CPU capacity to avoid bottlenecks?

● If CPU capacity is running at a premium or CPU bottlenecks already exist, then embarking upon data compression without upgrading CPU power might be unwise.


Maintenance

● Data compression reduces I/O but increases CPU consumed.● Rebuilding a compressed index involves decompressing the index pages and then rebuilding the index with

compression.● Bulk loading data into a compressed table involves compressing the data while performing the load.

Therefore, bulk inserts on a compressed table take longer.

Other considerations:

● Compression cannot be utilised on tables that have rows greater than 8060 bytes.● Tables with clustered indexes need only the indexes to be compressed as the clustered index is effectively

the table data in an ordered state.● Tables with unclustered indexes (heap tables) need to have both table and indexes compressed.● You are strongly advised to update statistics before and (particularly) after a table is compressed.

ExampleTable Compression Syntax Examples

Page compression:

ALTER TABLE PP_REVENUE REBUILD WITH(DATA COMPRESSION = PAGE)

Row compression:

ALTER TABLE PP_REVENUE REBUILD WITH(DATA COMPRESSION = ROW)

Uncompress the table:

ALTER TABLE PP_REVENUE REBUILD WITH(DATA COMPRESSION = NONE)

ExampleIndex Compression Syntax Examples

Page compression:

ALTER INDEX ALL ON PP_REVENUE REBUILD WITH(DATA COMPRESSION = PAGE)

Row compression:

ALTER INDEX ALL ON PP_REVENUE REBUILD WITH(DATA COMPRESSION = ROW)

Uncompress the index:

ALTER INDEX ALL ON PP_REVENUE REBUILD WITH(DATA COMPRESSION = NONE)

Related Information

Rebuilding Database Indexes and Statistics [page 52]


5.5 Data Loader Parallel Processing Scripts

The default setting for parallel processing is determined by the RDBMS engine, and is usually switched on by default to enable queries to run in parallel. Performance may be improved if parallel processing is turned off for running Data Loader procedures so that each query is run individually. Two scripts are provided in the installation folder that allow parallel processing to be switched on or off for the flagduplicate pre-validation steps during data loading.

The scripts provided in the installation folder are as follows:

● PCM_100_SQL\SUPPORT\MSSQLParallelQuery_ON.SQL● PCM_100_SQL\SUPPORT\MSSQLParallelQuery_OFF.SQL

All SAP BusinessObjects Profitability and Cost Management systems are unique, so we recommend that you test whether switching parallel processing on or off improves performance for your particular system.

ExampleMSSQLParallelQuery_ON.SQL

-- -- Execute Following to activate parallel query for flagduplicate-- OR just run delete - does same thing.--DELETE FROM EPO_DBCONFIG WHERE MODELID = -1 AND LOADID = -1 AND CONFIGID = 1000GOINSERT INTO dbo.EPO_DBCONFIG(MODELID, LOADID, CONFIGID, VALUE)VALUES (-1,-1,1000,1)GO

ExampleMSSQLParallelQuery_OFF.SQL

-- -- Execute Following to deactivate parallel query for flagduplicate--DELETE FROM EPO_DBCONFIG WHERE MODELID = -1 AND LOADID = -1 AND CONFIGID = 1000GOINSERT INTO dbo.EPO_DBCONFIG(MODELID, LOADID, CONFIGID, VALUE)VALUES (-1,-1,1000,0) GO

5.6 Log Tables

Specific logging functions within the software generate files that are an integral requirement for auditing capabilities. Other log files are created for operational indication of security, file load status, and model calculation.


Maintenance

These tables need to be monitored regularly. If they become too large, they must be archived and deleted. They can be archived as a flat file or as an Archive table.

The application log tables are described in the following list:

● EPO_ALERT● EPO_M_ALERT (This has a sister table EPO_M_ALERT_ARCHIVE to which the alerts need to be moved.)● PP_FASTLOAD_LOG● PPHV_LOG● PPLOAD_LOG (Log table for Data Loader)


6 Database Tables

In this section, the database tables are classified in terms of the type of data contained in them, for example; “Data Loader Tables”, “Results Tables” etc.

In Microsoft SQL Server/SAP Adaptive Server Enterprise and Oracle database systems, the database field types are different, so in order to allow one set of tables to be listed in this document, various generic definitions are provided to describe the field types. The following reference table describes the generic field types (that are listed in each section of database tables), and the distinct field types and field sizes they relate to in each supported relational database management system (RDBMS):

Generic Field Type DefinitionsUse this table to look up field types and sizes for a specific database system.

Generic Field Type


Field Type Size Field Type Size

Activity Driver Identifier Int 4 Number 22

Audit Identifier Int 4 Number 22

Child Member Identifier Char 1 Char 1

Combination Identifier Int 4 Number 22

Consolidation Type Identifier Int 4 Number 22

Date Datetime 8 Date 7

Date Value Numeric (38,10) Number 22

Identifier Int 4 Number 22

Index Identifier Nvarchar 256 Varchar2 256

Member Identifier Int 4 Number 22

Member Name Nvarchar 256 Varchar2 256

Memo Text 16 Clob 4000

NMemo Ntext 16 Clob 4000

Order Identifier Int 4 Number 22

Other Text Nvarchar Various lengths Varchar2 Various lengths

Status Value Int 4 Number 22

Value Numeric (38,10) Number 22

NoteMost of the Microsoft SQL Server and SAP Adaptive Server Enterprise database tables contain an Ident field that is populated by the database server itself with an automatically generated unique identifier value.


Database Tables

The same tables in an Oracle database do not contain this field, and therefore the Ident field is not documented in this guide.

6.1 About Data Loader Tables

Data Loading Methods

Data Loader and Data Bridge are two completely separate tools for loading data into the software. Historically, the Data Bridge application is the preferred method for loading data into the software, so for identification purposes, some of the Data Loader tables contain identically named fields to those contained in Data Bridge tables. In this section, these fields are denoted by an asterisk (*) for information only.

Furthermore, several Data Loader staging tables write to multiple physical tables, and where this occurs, the physical tables are numbered and are mapped to the corresponding Data Loader staging table field to identify which values are processed into which table. For example; the PPLOAD_ACTIVITYDRIVERVALUE staging table writes to three separate tables that are numbered (1), (2) and (3). The relevant fields listed in the table also have one of these numbers next to the field description to emphasize that the field values are written to a physical table with the corresponding number.

The Data Loader tables are available specifically for use by the loading procedures and packages. These are comprised of the following tables:

● Management tables – for the storing of error messages and for progress monitoring● Structural tables – for identification of dimension, alias, item property and assignment data● Value tables - for loading values into the physical data tables in the software schema

About Data Loader Tables

All tables include a model identifier, that may be attained via the EPO_MODELS table. Model creation can only be achieved by using the Model Builder application. In addition, most tables include a load identifier, which must also be unique. A load identifier is stored in the PP_FASTLOAD table and a new identifier must be created using the fastload procedure functions.

Some types of Data Loader tables contain a LOADSTATUS field. This determines the status of the actual load record. All newly loaded records should be assigned a value of 1 (or 70 for property and value tables), which signifies that a record has not been processed. On procedure execution and validation, the value of the field changes from 1 to another value. A value of 9 signifies the record was successfully processed. This field exists in the following tables:

All structural tablesAll value tables

SAP BusinessObjects Profitability and Cost Management Database Administrator's GuideDatabase Tables P U B L I C 61

ExampleEPO_MODELS Table

Field Name Type Allow Nulls Description

ID (Key) Identifier No Unique ID number relating to the model

MODELTYPE Identifier No Refers to the type of model. Valid options are:

● 1 - Profitability and Costing model● 4 - Objectives and Metrics model● 8 - Transactional Costing model● 16 - Bill of Materials model

MODELNAME Member Name

Yes Name of model

MEMO Other Text Yes Memo text for the model

NEXTUNIQUEID Identifier No Next available EPO code for model

MODELSYNC Status Value No Not currently used

MODELSTATUS Status Value Yes Current status of model. Valid options are:

● 0 - model disabled● 1 - model enabled

AUDITUSERID Identifier No User ID of last user to amend model

DATEALTERED Date No Date of last amendment to model

Related Information

PPLOAD_ACTIVITYDRIVERVALUE Activity Driver Value [page 79]

6.1.1 Management Tables

The management tables record the loading activities, and any errors that may occur during the loading process.

6.1.1.1 EPO_DBCONFIG

The EPO_DBCONFIG table contains the internal configuration data for Data Loader.

The structure is defined in the following table:


Database Tables


MODELID Identifier No ID number for the model

LOADID Identifier No ID number for the load

CONFIGID Identifier No ID number for the configuration

VALUE Identifier No Value of the configuration ID

6.1.1.2 EPO_ERRORLOG

All errors generated by the load routines have an entry written to the EPO_ERRORLOG table to provide traceability on any unforeseen issues that may occur.




ERRCODE Identifier No Error code

ERRMSG Other Text No Error message

DESCRIPTION Other Text No Description

CREATED_ON Date No Date created

AUDITUSERID Identifier No User ID of last user to amend record

6.1.1.3 PPHV_LOG

This table is used to log activity when the Transactional Costing packages or procedures are executed.




ID Identifier No ID log number for the row


DATEENTERED Date No Date entered

6.1.1.4 PPLOAD_LOG

This table records every load procedure execution start and finish along with a time stamp. This table may be used to observe loading for a given import.


The structure is defined in the table below:




ID Identifier No ID log number for the row


DATEENTERED Date No Date entered

6.1.2 Structural Tables

The loading procedures can load four types of structural data; dimension, alias, property and assignments. The parent child data and alias data each reside in their own table(s) for every single dimension defined at the schema level.

The following list shows the data dimension tables for each available dimension:

● VERSION● PERIOD● RESPCENTER● LINEITEM● ACTIVITY● COSTOBJECT1● COSTOBJECT2● COSTOBJECT3● COSTOBJECT4● COSTOBJECT5● DTCOSTOBJECT1● DTCOSTOBJECT2● DTCOSTOBJECT3● DTCOSTOBJECT4● DTCOSTOBJECT5● EMPLOYEE● INITIATIVE● REVENUETYPE● CURRENCY● RESOURCEDRIVER● ACTIVITYDRIVER● SERVICE● SPREAD● WORKSHEET1● WORKSHEET2


Database Tables

● CAPACITYRULE● USERRULE● LINEITEMDETAIL● ICON● BOUNDARY● OBJECTIVE● METRIC

Each dimension table holds the dimension data and another table exists to hold the alias data.

The structural tables listed above are supplemented by two more tables that record item properties. These can exist across most of the dimensions listed.

CautionModels contain a number of reserved names (refer to the SAP BusinessObjects Profitability and Cost Management Reference Guide for a list of reserved names). Some of these are the names of items in the structural skeleton required by a model and cannot be duplicated. Any use of these names in load data causes the existing default name to be referenced. If you attempt to use any of these names to define new structural items, then misleading results may be obtained. Other reserved names that MUST be avoided include alternative language equivalents for the English reserved names, scripting keywords and some legacy names carried over from earlier versions of the software.

6.1.2.1 PPLOAD_#_DH

Table: PPLOAD_#_DH

The purpose of these tables is to hold dimension data. Substitute the hash (#) character for the dimension name.

Fields denoted by an asterisk map directly to Data Bridge fields.

Field Name Type Allows Nulls Description



PARENTNAME* Member Name

No Default Alias name of item

CHILDNAME* Member Name

No Default Alias name of item

CHILDSORT Identifier No CHILDSORT parameter - this determines the order in which dimensional items appear within a grouping in a hierarchy.

ATTRIBUTEFLAG* Identifier No Attribute flag - this determines the type of dimensional item that is being loaded. Valid values are:

● 10 - Create a main hierarchy


Field Name Type Allows Nulls Description

● 12 - Define the attribute assignments● 15 - Build an attribute hierarchy

To understand how to apply these values correctly, read the topics on building hierarchies in the Organizing an Update with Data Bridge section.

CONSOLIDATIONTYPE* Member Name

No Consolidation type - this is the type of consolidation. Valid values include (~, +, -, OR, AND, NOR). To understand how to apply these values correctly, read the topics on building hierarchies in the Organizing an Update with Data Bridge section.

LOADSTATUS Status Value No Load status (Default 1)

ISROOTNODE Identifier No For internal use only (Default 0) - This traps a special case where an item appears only as a parent, and hence this is the root node. It is added under the top level item in this particular scenario.

DATESTAMP Date Yes (Default current date/time)

Related Information

Organizing an Update Using Data Bridge [page 234]Building Hierarchies [page 235]Attribute Flags [page 239]Consolidation Types [page 240]

6.1.2.2 PPLOAD_#_AL

Table: PPLOAD_#_AL

The purpose of these tables is to hold Alias data.

Fields denoted by an asterisk map directly to Data Bridge fields. Substitute # for the data dimensions.




DATAALIASNAME* Member Name

No User defined Alias name. This is the name of the data alias, and by default is stored in the EPO_DATA_ALIAS table.


Database Tables


ALIAS* Member Name

No Item name under Data Alias. This is the actual name of the alias being loaded, and validation occurs against this item.

DEFAULTALIAS* Member Name

No Default Alias name. This is the name of the default alias, which is stored against a language id (LANGID) of 0 in the schema. This is required to perform the lookup to return the existing internal EPO code for the default alias, so the new alias can be stored against the supplied data alias name.

LOADSTATUS Status Value No Load status (Default 1)


6.1.2.3 EPOLOAD_PROPERTY

Table: EPOLOAD_PROPERTY

The purpose of this table is to hold Property data.




NAME Other Text No Name of the property item

DEFAULTVALUE Other Text No Default property item value

LOADSTATUS Status Value No Load status (Default 1 or 70)


6.1.2.4 EPOLOAD_PROPERTYITEM

Table: EPOLOAD_PROPERTYITEM

The purpose of this table is to hold Property Item data.




NAME Member Name

No Name of the property item



DIMENSION Member Name

No Dimension type

ITEMNAME Member Name

No Name of dimension item

VALUE Other Text No Property item value



6.1.2.5 Assignment Tables

The following set of loading tables are available to enable assignment data to be loaded into a model.

6.1.2.5.1 PPLOAD_ACTIVITYREASSIGN Activities Reassignment

Table: PPLOAD_ACTIVITYREASSIGN

This single load table is responsible for writing information to the following table:

1. PP_ACTIVITYREASSIGN




VERSIONNAME* Member Name

No Name of the Version

PERIODNAME* Member Name

No Name of the Period

RESPCENTERNAME* Member Name

No Name of the Responsibility Center

ACTIVITYNAME * Member Name

No Name of the Activity

RESOURCEDRIVERNAME* Member Name

No Name of the Resource Driver

ARESOURCEDRIVERNAME * Member Name

No Name of the Activity Allocation Driver

TARGETRESPCENTERNAME * Member Name

No Name of the Target Responsibility Center


Database Tables


TARGETACTIVITYNAME * Member Name

No Name of the Target Activity



6.1.2.5.2 PPLOAD_ASSRESPCENTERACTIVITY Responsibility Centers Activities Assignment

Table: PPLOAD_ASSRESPCENTERACTIVITY


1. PP_ASSRESPCENTERACTIVITY










6.1.2.5.3 PPLOAD_COSTOBJECTASSIGNMENT Cost Object Assignment

Table: PPLOAD_COSTOBJECTASSIGNMENT

This single load table is responsible for writing information to the following tables:

1. PP_COSTOBJITEM2. PP_COSTOBJECTASSIGNMENT












LINEITEMACTIVITYNAME * Member Name

No Name of the Line Item Activity or Service (1)

LINEITEMACTIVITYTYPENAME* Member Name

No Name of the Line Item, Activity, or Service Type (1)

COSTOBJECTNAME * Member Name

No Name of the Cost Object (Cost Object 1 - 5) (2)

COSTOBJECTTYPENAME * Member Name

No Name of the Cost Object Type (Cost Object 1 - 5) (2)



6.1.2.5.4 PPLOAD_COSTOBJECTDRIVER Cost Object Driver

Table: PPLOAD_COSTOBJECTDRIVER


1. PP_COSTOBJITEM2. PP_COSTOBJECTDRIVER3. PP_HVCOSTOBJECTDRIVER





VERSIONNAME Member Name



Database Tables


PERIODNAME Member Name




LINEITEMACTIVITYNAME* Member Name

No Name of the Line Item, Activity or Service (1)

LINEITEMACTIVITYTYPENAME* Member Name

No Line Items, Activities, or Services (1)

ACTIVITYDRIVER1NAME* Member Name

No Name of the Activity Driver for Cost Object 1 (2)









VOLUMERESPCENTER1TYPE* Activity Driver Identifier

No Activity Drivers Values for Cost Object 1 (0 - All, 1 - Parent, 2 -Current, 3007 - RC Unassigned) (2)









ORDER1* Order Identifier

No Numeric order that Cost Object 1-5 Drivers are applied (2)











HVACTIVITYDRIVERNAME* Member Name

Yes Name of the Transaction Activity Driver (for Transactional Costing models only) (3)



6.1.2.5.5 PPLOAD_LINEITEMDIRECT_ACTIVITY Line Item Direct Activity Overrides

Table: PPLOAD_LINEITEMDIRECT_ACTIVITY


1. PP_LINEITEMDIRECT_ACTIVITY




VERSIONNAME * Member Name


PERIODNAME * Member Name


RESPCENTERNAME * Member Name


LINEITEMNAME * Member Name

No Name of the Line Item


Yes Name of the Activity



6.1.2.5.6 PPLOAD_LINEITEMRESOURCEDRIVER Resource Drivers Line Items Assignment

Table: PPLOAD_LINEITEMRESOURCEDRIVER


1. PP_LINEITEMRESOURCEDRIVER


Database Tables










LINEITEMNAME * Member Name


RESOURCEDRIVERNAME * Member Name

Yes Name of the Line Item Activity Type



6.1.2.5.7 PPLOAD_SERVICERESOURCEDRIVER Resource Drivers Services Assignment

Table: PPLOAD_SERVICERESOURCEDRIVER


1. PP_SERVICERESOURCEDRIVER










SERVICENAME* Member Name

No Name of the Service


Yes Name of the Resource Driver




6.1.2.5.8 PPLOAD_SERVICEDIRECT_ACTIVITY Direct Services Assignment Overrides

Table: PPLOAD_SERVICEDIRECT_ACTIVITY


1. PP_SERVICEDIRECT_ACTIVITY










SERVICENAME * Member Name



Yes Name of the Direct Activity



6.1.2.5.9 PPLOAD_RESPCENTERSERVICE Services Responsibility Centers

Table: PPLOAD_RESPCENTERSERVICE


1. PP_RESPCENTERSERVICE






SERVICENAME * Member Name




Database Tables



6.1.2.5.10 OMLOAD_ASSMETRICEMPLOYEE Metric Employees Assignment

Table: OMLOAD_ASSMETRICEMPLOYEE


1. OM_ASSMETRICEMPLOYEE




METRICNAME* Member Name

No Name of the Metric

EMPLOYEENAME* Member Name

No Name of the Employee



6.1.2.5.11 OMLOAD_ASSMETRICRESPCENTER Metric Responsibility Centers Assignment

Table: OMLOAD_ASSMETRICRESPCENTER


1. OM_ASSMETRICRESPCENTER




METRICNAME * Member Name







6.1.2.5.12 OMLOAD_ASSOBJECTIVEEMPLOYEE Objectives Employees Assignment

Table: OMLOAD_ASSOBJECTIVEEMPLOYEE


1. OM_ASSOBJECTIVEEMPLOYEE




OBJECTIVENAME * Member Name

No Name of the Objective

EMPLOYEENAME * Member Name




6.1.2.5.13 OMLOAD_ASSOBJECTIVELOBJECTIVE Objectives Linked Objectives Assignment

Table: OMLOAD_ASSOBJECTIVELOBJECTIVE


1. OM_ASSOBJECTIVELOBJECTIVE




OBJECTIVENAME* Member Name


LINKEDOBJECTIVENAME* Member Name

No Name of the Linked Objective




Database Tables

6.1.2.5.14 OMLOAD_ASSOBJECTIVEMETRIC Objectives Metrics Assignment

Table: OMLOAD_ASSOBJECTIVEMETRIC


1. OM_ASSOBJECTIVEMETRIC










6.1.2.5.15 OMLOAD_ASSOBJECTIVERESPCENTER Objectives Responsibility Centers Assignment

Table: OMLOAD_ASSOBJECTIVERESPCENTER


1. OM_ASSOBJECTIVERESPCENTER











6.1.2.5.16 OMLOAD_OVRMETRICEMPLOYEE Metric Employees Assignment Override

Table: OMLOAD_OVRMETRICEMPLOYEE


1. OM_OVRMETRICEMPLOYEE












COSTOBJECT1NAME* Member Name

No Name of Cost Object 1 (Object 1)







6.1.2.5.17 OMLOAD_OVROBJECTIVEEMPLOYEE Objectives Employees Assignment Override

Table: OMLOAD_OVROBJECTIVEEMPLOYEE


1. OM_OVROBJECTIVEEMPLOYEE







Database Tables
















6.1.3 Value Tables

There are tables included in the software that facilitate the loading of data values.

Validation occurs against name for all value loading procedures. If the validation of the name fails, for example, the item does not already exist in the software schema, then the reason for the failure is recorded in the LOADSTATUS field of the given record, and the record is not loaded into the model. For a list of LOADSTATUS values, refer to the section on Exception Messages.

NoteBefore being processed, records have a LOADSTATUS value of 1, and if successfully processed have a value of 9.

Related Information

Data Loader Error Codes [page 49]

6.1.3.1 PPLOAD_ACTIVITYDRIVERVALUE Activity Driver Value

Table: PPLOAD_ACTIVITYDRIVERVALUE

This single load table is responsible for supplying data to the following tables:


1. PP_ACTIVITYDRIVERVALUE2. PP_ACTIVITYDRIVERDELTA3. PP_ACTIVITYDRIVERTARGET

The load table structure is defined as follows:










ACTIVITYDRIVERNAME* Member Name

No Name of the Activity Driver


No Name of Cost Object 1









VALUE* Value Yes Activity Driver value (1)

DELTAVALUE* Value Yes Activity Driver delta value (2)

TARGETVALUE* Value Yes Activity Driver target value (3)



6.1.3.2 PPLOAD_BOMMAKEUP Bill of Materials Makeup

Table: PPLOAD_BOMMAKEUP

This single load table is responsible for writing data to the following table:

1. PP_BOMMAKEUP


Database Tables










COMPONENTNAME* Member Name

No Name of the product/sub-product/component that is the part

CURRENCYNAME* Member Name

No Name of a unit of measure item

VOLUME* Value Yes The component makeup volume for the product (Cost Object 1) (1)



6.1.3.3 PPLOAD_BOMPRODUCTION Bill of Materials Production

Table: PPLOAD_BOMPRODUCTION


1. PP_BOMPRODUCTION











No Name of a Currency item

VALUE* Value Yes The component production volume (1)





6.1.3.4 PPLOAD_BOMUNITSSOLD Bill of Materials Units Sold

Table: PPLOAD_BOMUNITSSOLD


1. PP_BOMUNITSSOLD






















VALUE* Value Yes The product/sub-assembly units sold value (1)



6.1.3.5 PPLOAD_CURRENCYRATES Currency Rate

Table: PPLOAD_CURRENCYRATES


Database Tables


1. PP_CURRENCYRATES









No Name of the Currency item

RATE* Value Yes Currency rate (1)



6.1.3.6 PPLOAD_DEFAULTBOMMAKEUP Bill of Materials Default Makeup

Table: PPLOAD_DEFAULTBOMMAKEUP


1. PP_DEFAULTBOMMAKEUP






COMPONENTNAME* Member Name

No Name of the product/sub-product/component that is the part



VOLUME* Value Yes The component makeup volume for the product (Cost Object 1) (1)




6.1.3.7 PPLOAD_EMPLOYEERDS Employee Resource Driver Split

Table: PPLOAD_EMPLOYEERDS


1. PP_EMPLOYEERDS











No Name of an Employee



ACTIVITYNAME* Member Name

No Name of an Activity

VALUE* Value No EmployeeResourceDriverSplit (1)



6.1.3.8 PPLOAD_EXTERNALACTIVITYVALUE External Activity Value

Table: PPLOAD_EXTERNALACTIVITYVALUE


1. PP_EXTERNALACTIVITYVALUE






Database Tables









No Name of an Activity Driver

LINEITEMNAME* Member Name

No Name of a Line Item



VALUE* Value No External activity value (1)

FIXEDVALUE* Value No External fixed value



6.1.3.9 PPLOAD_EXTERNALBOMUNITRATE Bill of Materials External Unit Rate

Table: PPLOAD_EXTERNALBOMUNITRATE


1. PP_EXTERNALBOMUNITRATE




















VALUE* Value Yes Bill of Materials external unit rate value (1)



6.1.3.10 PPLOAD_EXTERNALCOSTOBJECTVALUE External Cost Object Value

Table: PPLOAD_EXTERNALCOSTOBJECTVALUE


1. PP_EXTERNALCOSTOBJECTVALUE
























Database Tables






VALUE* Value No External Cost Object value (1)

FIXEDVALUE* Value No External fixed Cost Object value *



6.1.3.11 PPLOAD_HVACTIVITYDRIVERVOLUME Activity Driver Volume

Table: PPLOAD_HVACTIVITYDRIVERVOLUME


1. PP_HVACTIVITYDRIVERVOLUME









RESPCENTERNAME Member Name



No Name of Activity Driver

DETAILCOSTOBJECT1NAME* Member Name

No Name of Detail Cost Object 1











VALUE* Value Yes Activity Driver volume (1)



6.1.3.12 PPLOAD_HVEXTACTCOUNITRATE External Activity Cost Object Unit Rate

Table: PPLOAD_HVEXTACTCOUNITRATE


1. PP_HVEXTACTCOUNITRATE

























UNITRATE* Value No Unit Rate value

FIXEDUNITRATE* Value No Fixed Unit Rate value


Database Tables




6.1.3.13 PPLOAD_LINEITEMDETAILVALUE Line Item Detail Value

Table: PPLOAD_LINEITEMDETAILVALUE


1. PP_LINEITEMDETAIL










LINEITEMDETAILNAME* Member Name

No Name of a Line Item detail





VALUE* Value Yes Line Item detail value (1)



NoteThe Data Bridge export table contains an additional field called LineItemdetailValueNC which is used internally to store values that are not currency specific.

6.1.3.14 PPLOAD_LINEITEMFIXEDVALUE Line Item Fixed Value

Table: PPLOAD_LINEITEMFIXEDVALUE



1. PP_LINEITEMFIXEDVALUE

The load table is defined as follows:














VALUE* Value Yes Fixed Line Item value (1)



6.1.3.15 PPLOAD_LINEITEMVALUE Line Item Value Data

Table: PPLOAD_LINEITEMVALUE


1. PP_LINEITEMVALUE2. PP_LINEITEMDELTA












Database Tables






VALUE* Value Yes Line Item value (1)

DELTAVALUE* Value Yes Line Item delta value (2)



NoteData Bridge export contains an additional field called LineItemCalculatedFixedValue which is calculated internally and hence is not available for import.

6.1.3.16 PPLOAD_LINEITEMVARIABLE Line Item Variable

Table: PPLOAD_LINEITEMVARIABLE


1. PP_LINEITEMVARVALUE













VALUE* Value Yes Line Item variability (1)




6.1.3.17 PPLOAD_RESOURCEDRIVERSPLIT Resource Driver Split

Table: PPLOAD_RESOURCEDRIVERSPLIT


1. PP_RESOURCEDRIVERSPLIT 2. PP_RESOURCEDRIVERDSPLIT3. PP_RESOURCEDRIVERTARSPLIT














SPLIT* Value Yes Resource Driver Split (1)

DELTASPLIT* Value Yes Resource Driver delta Split (2)

TARGETSPLIT* Value Yes Resource Driver target Split (3)



NoteThe original Data Bridge table contains the percentage value ResourceDriverPctSplit that is calculated, and as a result is not implemented.

6.1.3.18 PPLOAD_RESOURCEDRIVERVALUE Resource Driver Value

Table: PPLOAD_RESOURCEDRIVERVALUE


1. PP_RESOURCEDRIVERVALUE


Database Tables

2. PP_RESOURCEDRIVERDELTA3. PP_RESOURCEDRIVERTARGET












VALUE* Value Yes Resource Driver value (1)

DELTAVALUE* Value Yes Resource Driver delta value (2)

TARGETVALUE* Value Yes Resource Driver target value (3)



6.1.3.19 PPLOAD_REVENUE Revenue

Table: PPLOAD_REVENUE


1. PP_REVENUE










REVENUETYPENAME* Member Name

No Name of the Revenue Type















UNITPRICE* Value Yes Unit Price value (1)

UNITSSOLD* Value Yes Units Sold value (1)

VALUE* Value Yes Revenue (1)



6.1.3.20 PPLOAD_SERVICEDRIVERVALUE Service Driver Value

Table: PPLOAD_SERVICEDRIVERVALUE

This table holds the actual value associated with the Service Driver.


1. PP_SERVICEDRIVERVALUE2. PP_SERVICEDRIVERDELTA3. PP_SERVICEDRIVERTARGET











No Name of a Service


Database Tables


VALUE* Value Yes Service Driver value (1)

DELTAVALUE* Value Yes Service Driver delta value (2)

TARGETVALUE* Value Yes Service Driver target value (3)



6.1.3.21 PPLOAD_SERVICEFACTOR Service Factor

Table: PPLOAD_SERVICEFACTOR

This table holds the cost ratio associated with the Service, as defined by a variable or fixed unit rate.


1. PP_SERVICEFACTOR












VARIABLEFACTOR* Value Yes Variable Service factor (1)

FIXEDUNITRATE* Value Yes Fixed Unit Rate value (1)



NoteThe original Data Bridge table contains a unit rate value (UnitRate) that is calculated, and as a result is not implemented. The export table also contains a Responsibility Center - this is not stored against the base table, and so it is not available for import.


6.1.3.22 PPLOAD_SPREADVALUE Spread Value

Table: PPLOAD_SPREADVALUE


1. PP_SPREADVALUE








SPREADNAME* Member Name

No Name of the Spread

VALUE* Value Yes Spread value (1)

LOADSTATUS Status Value No Load status(Default 1 or 70)


6.1.3.23 PPLOAD_WORKSHEETVALUE Work Sheet Value

Table: PPLOAD_WORKSHEETVALUE


1. PP_WORKSHEETVALUE










WORKSHEET1NAME* Member Name

No Name of Work Sheet 1

WORKSHEET2NAME* Member Name

No Name of Work Sheet 2

VALUE* Value Yes Work Sheet value (1)


Database Tables




6.1.3.24 OMLOAD_BOUNDARYINFO Boundary info

Table: OMLOAD_BOUNDARYINFO


1. OM_BOUNDARYINFO


MODELID Identifier No ID number for thte model


GROUPBOUNDARYNAME* Member Name

No Name of the Boundary Group (1)

BOUNDARYNAME* Member Name

No Name of the Boundary

ICONNAME* Member Name

No Name of an Icon

RANGECOLOR* Identifier No Range color

DATACOLOR* Identifier No Data color



6.1.3.25 OMLOAD_EMPLOYEEBOUNDARY Employee boundary

Table: OMLOAD_EMPLOYEEBOUNDARY


1. OM_EMPLOYEEBOUNDARY


















COSTOBJECT3NAME Member Name








MEASURENAME* Member Name

No Name of a Measure

VALUE* Value No MetricBoundaryValue(1)



6.1.3.26 OMLOAD_EMPLOYEEB Employee Boundary Measure

Table: OMLOAD_EMPLOYEEB


1. PP_EMPLOYEEB









No Name of a Measure


Database Tables




6.1.3.27 OMLOAD_ICONVALUE Icon Value

Table: OMLOAD_ICONVALUE


1. OM_ICONVALUE


MODELID Identifier No ID number for model

LOADID Identifier No ID number for load

ICONNAME Member Name

No Name of an Icon

CATEGORY Other Text Yes Property (1)

VALUE NMemo Yes Icon value (encoded)



6.1.3.28 OMLOAD_METRICACTUAL Metric Actual Value

Table: OMLOAD_METRICACTUAL


1. OM_METRICACTUAL




















VALUE* Value No Metric actual value (1)



6.1.3.29 OMLOAD_METRICADJUSTMENT Metric Actual Adjustment Value

Table: OMLOAD_METRICADJUSTMENT


1. OM_METRICADJUSTMENT











No Name of a Metric







VALUE* Value No Metric actual adjustment value (1)



Database Tables



6.1.3.30 OMLOAD_METRICADJUSTTARGET Metric Target Adjustment Value

Table: OMLOAD_METRICADJUSTTARGET


1. OM_METRICADJUSTTARGET











No Name of a Metric







VALUE* Value No Metric Target adjustment value (1)



6.1.3.31 OMLOAD_METRICB Metric Boundary Measure

Table: OMLOAD_METRICB


1. OM_METRICB










No ID of table field e.g. MetricActualBoundaryValueID or MetricPercentBoundaryValueID



6.1.3.32 OMLOAD_METRICBASEPOINT Metric Base Point Value

Table: OMLOAD_METRICBASEPOINT


1. OM_METRICBASEPOINT


















VALUE* Value No Metric basepoint value (1)



Database Tables



6.1.3.33 OMLOAD_METRICBOUNDARY Metric Boundary Value

Table: OMLOAD_METRICBOUNDARY


1. OM_METRICBOUNDARY



















No ID of table field e.g. MetricActualBoundaryValueID or MetricPercentBoundaryValueID

VALUE* Value No Value (1)



6.1.3.34 OMLOAD_METRICTARGET Metric Target Value

Table: OMLOAD_METRICTARGET



1. OM_METRICTARGET


















VALUE* Value No Metric Target value (1)



6.1.3.35 OMLOAD_OBJECTIVEACTUAL Objective Actual Value

Table: OMLOAD_OBJECTIVEACTUAL


1. OM_OBJECTIVEACTUAL









No Name of the Responsibility Ccenter




Database Tables






VALUE* Value No Objective actual value (1)



6.1.3.36 OMLOAD_OBJECTIVEADJUSTMENT Object Actual Adjustment Value

Table: OMLOAD_OBJECTIVEADJUSTMENT


1. OM_OBJECTIVEADJUSTMENT
















VALUE* Value No Objective actual adjustment value (1)




6.1.3.37 OMLOAD_OBJECTIVEJUSTTARGET Objective Target Adjustment Value

Table: OMLOAD_OBJECTIVEADJUSTTARGET


1. OM_OBJECTIVEADJUSTTARGET
















VALUE* Value No Objective Target adjustment value (1)



6.1.3.38 OMLOAD_OBJECTIVEB Objective Boundary Measure

Table: OMLOAD_OBJECTIVEB


1. OM_OBJECTIVEB









Database Tables



No ID of table field e.g. ObjectiveActualBoundaryValueID or ObjectivePercentBoundaryValueID



6.1.3.39 OMLOAD_OBJECTIVEBASEPOINT Objective Base Point Value

Table: OMLOAD_OBJECTIVEBASEPOINT


1. OM_OBJECTIVEBASEPOINT
















VALUE* Value No Objective basepoint value (1)



6.1.3.40 OMLOAD_OBJECTIVEBOUNDARY Objective Boundary Value

Table: OMLOAD_OBJECTIVEBOUNDARY



1. OM_OBJECTIVEBOUNDARY



















No ID of table field e.g. ObjectiveActualBoundaryValueID or ObjectivePercentBoundaryValueID

VALUE* Value No Value (1)



6.1.3.41 OMLOAD_OBJECTIVETARGET Objective Target Value

Table: OMLOAD_OBJECTIVETARGET


1. OM_OBJECTIVETARGET







Database Tables












VALUE* Value No Objective Target value (1)

LOADSTATUS Status Value No Load status (Default 1 or 70


6.1.3.42 OMLOAD_OBJECTIVEWEIGHTING Objective Weighting Value

Table: OMLOAD_OBJECTIVEWEIGHTING


1. OM_OBJECTIVEWEIGHTING












LINKEDOBJECTIVE* Member Name

No Name of the linked Objective







WEIGHTING* Value No Objective weighting value (1)



6.1.3.43 OMLOAD_OBJMETRICWEIGHTING Objective Metric weighting value

Table: OMLOAD_OBJMETRICWEIGHTING


1. OM_OBJMETRICWEIGHTING


















WEIGHTING* Value No Objective Metric weighting value (1)



6.2 About Results Tables

A set of results tables are available to allow the export of both input data and calculated results from a model directly to the database.


Database Tables

The layout details for dimension tables are referred to from within the results tables. The dimension data sent to the results tables contains EPO Codes rather than the dimension item names.

The results tables are created when the initial table build scripts are run. Most of these begin with the prefix PPR_, followed by the type of result the table holds. The Objectives and Metrics results tables are prefixed by OMR_.

ExampleThe table PPR_ACTIVITYVALUE holds any calculated activity values that have been exported via the export routine within the application.

NoteThe results tables are not indexed in a new installation or upgrade of version 10. If the \PCM_100_SQL\SUPPORT\Sample\MSSQLCreateResultIndexandPrimaryKeys.SQL script is run to apply indexes and keys to the results tables, there may be a noticeable decrease in speed when model results are exported, and the indexes cannot be removed again if you choose to run this script. When indexed, all results tables use a star schema where all IDs make up the primary key.

Results Views

A set of views are also available to allow the default alias dimension item names to be viewed in the results, rather than the EPO Codes.

TipIf an alias other than the default is required, then custom views can be written linking in the EPO_DATA_ALIAS table (as long as alias data exists). This is achieved by linking the alias table ID to the Lang ID of the relevant dimension table, which in turn links in to the relevant results table.

Related Information

Results Views [page 160]

6.2.1 Results Tables

6.2.1.1 PPR_ACTCOSTOBJECTVALUE

Table: PPR_ACTCOSTOBJECTVALUE

This table holds the dimension item IDs and results produced by calculating the activity cost object value (see description below to see the relevant dimension table).



MODELID Identifier No ID number for the model (links to EPO_MODELS)

EXPORTID Identifier No ID number for the export (links to EPO_USEREXPORTLOG)

VERSIONID Member Identifier

No ID number for the Version (links to PP_VERSION_NAME)

PERIODID Member Identifier

No ID number for the Period (links to PP_PERIOD_NAME)

ACTIVITYID Member Identifier

No ID number for an Activity (links to PP_ACTIVITY_NAME)

COSTOBJECT1ID Member Identifier

No ID number for Cost Object 1 (links to PP_COSTOBJECT1_NAME)









VALUE Value No Activity Cost Object value

FIXEDVALUE Value No Fixed Activity Cost Object value

VARIABLEVALUE Value No Variable activity cost object value

6.2.1.2 PPR_ACTIVITYLINEITEMVALUE

Table: PPR_ACTIVITYLINEITEMVALUE

This table holds the dimension item IDs and results produced by calculating the activity line item values (see description below to see the relevant dimension table).









Database Tables


RESPCENTERID Member Identifier

No ID number for the Responsibility Center (links to PP_RESPCENTER_NAME)

LINEITEMID Member Identifier

No ID Int for the Line Item (links to PP_LINEITEM_NAME)


No ID Int for the Activity (links to PP_ACTIVITY_NAME)

VALUE Value No Activity Line Item value

FIXEDVALUE Value No Fixed Activity Line Item value

VARIABLEVALUE Value No Variable Activity Line Item value

6.2.1.3 PPR_ACTIVITYVALUE

Table: PPR_ACTIVITYVALUE

This table holds the dimension item IDs and results produced by calculating the activity values.











No ID number for the Line Item (links to PP_LINEITEM_NAME)


No ID number for the Activity (links to PP_ACTIVITY_NAME)

RESOURCEDRIVERID Member Identifier

No ID number for the Resource Driver (links to PP_RESOURCEDRIVER_NAME)

VALUE Value No Activity value

FIXEDVALUE Value No Fixed Activity value

VARIABLEVALUE Value No Variable Activity value

UNITRATE Value No Activity Unit Rate value


6.2.1.4 PPR_ACTREASSIGNSPLITVALUE

Table: PPR_ACTREASSIGNSPLITVALUE

This table holds the dimension item IDs and results produced by calculating the activity reassignment split values (see description below to see the relevant dimension table).












TARGETRESPCENTERID Member Identifier


TARGETACTIVITYID Member Identifier


VALUE Value No Activity reassignment split value

POSTVALUE Value No Activity reassignment post value

INVALUE Value No Activity reassignment in value

OUTVALUE Value No Activity reassignment out value

6.2.1.5 PPR_APRIMARYACTIVITYDRIVER

Table: PPR_APRIMARYACTIVITYDRIVER

This table holds the dimension item IDs and results produced by calculating the activity primary activity driver volumes.





Database Tables



No ID number for the Version (links to PP_VERSIONNAME)









ACTIVITYDRIVERID Member Identifier

No ID number for the Activity Driver (links to PP_ACTIVITYDRIVER_NAME)

VOLUME Value No Activity primary Activity Driver volume

UNITRATE Value No Activity primary Activity Driver unit rate

6.2.1.6 PPR_BOMRESULT

Table: PPR_BOMRESULT

This table contains the dimension item IDs and results of product unit rates.















No ID number of Cost Object 1

COMPONENTID Member Identifier

No ID number of the Component for the Product/Part



COMPONENTVOLUME Value No The accumulated makeup volume of a component in the product

COMPONENTUNITRATE Value No The unit rate value of the component

COMPONENTFIXEDUNITRATE Value No The fixed unit rate value of the component

COMPONENTEXTERNALUNITRATE Value No The external unit rate value of the component

PRODUCTUNITRATE Value No The accumulated component unit rates of the product. This is calculated as: PRODUCTUNITRATE = (COMPONENTUNITRATE + COMPONENTEXTERNALUNITRATE ) * COMPONENTVOLUME

PRODUCTFIXEDUNITRATE Value No The accumulated component fixed unit rates of the product. This is calculated as: PRODUCTFIXEDUNITRATE = COMPONENTFIXEDUNITRATE * COMPONENTVOLUME

6.2.1.7 PPR_BOMUNITRATE

Table: PPR_BOMUNITRATE

This table contains the dimension item IDs and results of Component Unit Rates.

















Database Tables


VALUE Value No The calculated value of the Bill of Materials activity cost divided by the Bill of Materials production volume.

FIXEDVALUE Value No The calculated value of the Bill of Materials fixed activity cost divided by the Bill of Materials production volume.

6.2.1.8 PPR_RBBOMMAKEUP

Table: PPR_RBBOMMAKEUP

This table contains the dimension item IDs and results of rule based Version and Period Bill Of Materials Makeup volumes.











No ID number of the component for the product/part

VOLUME Value No The component makeup volume for the product (Cost Object 1)

6.2.1.9 PPR_RBBOMPRODUCTION

Table: PPR_RBBOMPRODUCTION

This table contains the dimension item IDs and results of rule based Bill Of Materials Production volume.











No ID number of Cost Object 1 (the product)

VALUE Value No The component production volume

6.2.1.10 PPR_RBBOMUNITSSOLD

Table: PPR_RBBOMUNITSSOLD

This table contains the dimension item IDs and results of rule based Bill Of Materials units sold.











No ID number for the <Cost Object 1> (the product - links to PP_COSTOBJECT1_NAME)









VALUE Value No The product/sub-assembly units sold value


Database Tables

6.2.1.11 PPR_CONTRIBUTION

Table: PPR_CONTRIBUTION

This table holds the dimension item IDs and results produced by calculating the contribution value (see description below to see the relevant dimension table).















No ID numbr for Cost Object 3 (links to PP_COSTOBJECT3_NAME)





CONTRIBUTION Value No Contribution value

6.2.1.12 PPR_COSTOBJECTVALUE

Table:PPR_COSTOBJECTVALUE

This table holds the dimension item IDs and results produced by calculating the cost object values (see description below to see the relevant dimension table).












LINEIITEMID Member Identifier














VALUE Value No Cost Object value

FIXEDVALUE Value No Fixed Cost Object value

VARIABLEVALUE Value No Variable Cost Object value

6.2.1.13 PPR_DCOSTOBJECTVALUE

Table: PPR_DCOSTOBJECTVALUE

This table holds the dimension item IDs and results produced by calculating the direct cost object values (see description below to see the relevant dimension table).









Database Tables
















VALUE Value No Direct Cost Object value

FIXEDVALUE Value No Fixed direct Cost Object value

VARIABLEVALUE Value No Variable direct Cost Object value

6.2.1.14 PPR_#DIMENSION_NAME#_BRIDGE

Table: PPR_#DIMENSION_NAME#_BRIDGE

This table is used in conjunction with universe files to enable SAP BusinessObjects Enterprise to query the results of hierarchical data contained within SAP BusinessObjects Profitability and Cost Management dimensions for reporting and analysis.

Each dimension has a PPR_#DIMENSION_NAME#_BRIDGE table, where #DIMENSION_NAME# is the name of that dimension. The primary use of this table is to express data as a vertical association of parent/child data to allow report querying and analysis. The table also contains NodeIndex data as a textual representation of the hierarchical structure.

For example, the first top level node item (Grandparent) is assigned a node index of 1, the Parent items are assigned a node index of 1.1, 1.2 and so on, and the Child items in the hierarchy are assigned a node index of 1.1.1, 1.1.2 and so on.

RestrictionThe functionality to report on SAP BusinessObjects Profitability and Cost Management hierarchical data by using this table is currently not available in the software.






DIMENSIONID Member Identifier

No ID number for the Dimension (links to PP_DIMENSION_NAME)

DIMENSIONHIERARCHYID Identifier No ID number for hierarchies within a dimension, including attribute hierarchies.

NoteThere must always be a main hierarchy in a dimension and its DIMENSIONHIERARCHYID is always 0.

DIMENSIONLEVELID Identifier No Position of the dimension item in the hierarchy

NODEID Identifier No Internal dimension item identifier

CHILDNODEID Identifier No Internal dimension identifier for the Child item

NODENAME Member Name

No Name of the node item

CHILDNODENAME Member Name

No Child node name

NODEISLEAF Identifier No The NODEID leaf item in hierarchy

CHILDNODEISLEAF Identifier No The CHILDNODEID leaf item in hierarchy

NODEINDEX Index Identifier

No Index to represent the position of the node in the hierarchy

CHILDNODEINDEX Index Identifier

No Child index to represent the position of the node in the hierarchy

ORIGINALDIMENSIONLEVELID Identifier No Original Dimension Level ID (See Note below)

ISBALANCED Status Value No Determines original flattened dimension item

NoteIn SAP BusinessObjects Profitability and Cost Management, dimensions in the Main and Attribute hierarchies can contain multiple hierarchies that can be unbalanced or of varying depths. As part of the Export to Database function, the SAP BusinessObjects Profitability and Cost Management middle tier analyses all the hierarchies contained within a given dimension for a particular export, to determine which is the deepest. All hierarchies are then vertically flattened to the maximum depth for reporting purposes.


Database Tables

6.2.1.15 PPR_#DIMENSION_NAME#_NODEITEMS

Table: PPR_#DIMENSION_NAME#_NODEITEMS

This table is used in conjunction with universe files to enable SAP BusinessObjects Enterprise to query the results of hierarchical data contained within SAP BusinessObjects Profitability and Cost Management dimensions for reporting and analysis.

Each dimension has a PPR_#DIMENSION_NAME#_NODEITEMS table, where #DIMENSION_NAME# is the name of that dimension. The primary use of this table is to create a node index of the dimension hierarchy items to allow report querying and analysis on this textual representation of the hierarchical structure.

For example, the first top level node item (Grandparent) is assigned a node index of 1, the Parent items are assigned a node index of 1.1, 1.2 and so on, and the Child items in the hierarchy are assigned a node index of 1.1.1, 1.1.2 and so on.

RestrictionThe functionality to report on SAP BusinessObjects Profitability and Cost Management hierarchical data by using this table is currently not available in the software.








DIMENSIONlEVELID Identifier No Position of the dimension item in the hierarchy

NODEID Identifier No Internal dimension item identifier

PARENTNODEID Identifier No Internal dimension identifier for the parent item

NODENAME Member Name

No Name of the node item

PARENTNODENAME Member Name

No Parent node name

NODEISLEAF Identifier No The NODEID leaf item in hierarchy



NODEINDEX Index Identifier

No Index to represent the position of the node in the hierarchy

PARENTNODEINDEX Index Identifier

No Parent index to represent the position of the node in the hierarchy

ORIGINALDIMENSIONLEVELID Identifier No Original Dimension Level ID (See Note below)

ISBALANCED Status Value No Determines original flattened dimension item

NoteIn SAP BusinessObjects Profitability and Cost Management, dimensions in the Main and Attribute hierarchies can contain multiple hierarchies that can be unbalanced or of varying depths. As part of the Export to Database function, the SAP BusinessObjects Profitability and Cost Management middle tier analyses all the hierarchies contained within a given dimension for a particular export, to determine which is the deepest. All hierarchies are then vertically flattened to the maximum depth for reporting purposes.

6.2.1.16 PPR_DPRIMARYACTIVITYDRIVER

Table: PPR_DPRIMARYACTIVITYDRIVER

This table holds the dimension item IDs and results produced by calculating the direct primary activity driver volumes (see description below to see the relevant dimension table).













No ID number for the Activity (links to PP_ACTIVITYDRIVER_NAME)

VOLUME Value No Direct primary Activity Driver volume

UNITRATE Value No Direct primary Activity Driver unit rate


Database Tables

6.2.1.17 PPR_DSERVICECOSTOBJECTVALUE

Table: PPR_DSERVICECOSTOBJECTVALUE

This table holds the dimension item IDs and results produced by calculating the direct service cost object value.










SERVICEID Member Identifier

No ID number for the Service item (links to PP_SERVICE_NAME)











VALUE Value No Direct Service Cost Object value

6.2.1.18 PPR_DSPRIMARYACTIVITYDRIVER

Table: PPR_DSPRIMARYACTIVITYDRIVER

This table holds the dimension item IDs and results produced by calculating the direct service primary activity driver values.
















VOLUME Value No Direct Service primary Activity Driver value

UNITRATE Value No Direct Service primary Activity Driver unit rate

6.2.1.19 PPR_EXTERNALACTIVITYVALUE

Table: PPR_EXTERNALACTIVITYVALUE

This table holds the dimension item IDs and results entered in the model for External Activity Values.














CURRENCYID Member Identifier

No ID number for a Currency item (links to PP_CURRENCY_NAME)

EXTERNALACTIVITYVALUE Value No External Activity value


Database Tables


EXTERNALACTIVITYFIXEDVALUE Value No Fixed external Activity value

6.2.1.20 PPR_EXTERNALCOSTOBJECTVALUE

Table: PPR_EXTERNALCOSTOBJECTVALUE

This table holds the dimension item IDs and results entered in the model for External Cost Object Values.













No ID number for Line Item (links to PP_LINEITEM_NAME)











EXTERNALCOSTOBJECTVALUE Value No External Cost Object value

EXTERNALCOSTOBJECTFIXEDVALUE Value No Fixed external Cost Object value

6.2.1.21 PPR_HVACTIVITYDRIVERMAPPING

Table: PPR_HVACTIVITYDRIVERMAPPING


This internal table holds mapping between the detailed transaction drivers and the required consolidation points.










No ID number for the Activity driver (links to PP_ACTIVITYDRIVER_NAME)

DETAILCOSTOBJECT1ID Member Identifier

No ID number for the Detail Cost Object 1 (links to PP_DTCOSTOBJECT1ID)


No ID number for Cost Object 2 (links to PP_DTCOSTOBJECT2ID)

















ACTIVITYDRIVERVOLUME Value Yes Activity Driver volume

6.2.1.22 PPR_HVBREAKDOWN

Table: PPR_HVBREAKDOWN

This table contains a summary of unit costs from the PPR_HVUNITRATE table that are grouped by Responsibility Center and Activity level. The costs are derived from the calculatetransactionalcosts PCMConsole command for a Transactional Costing model type.


Database Tables







HVLOOKUPID Identifier No Links to the PPR_HVBREAKDOWNDETAILCOST table




No ID number for an Activity (links to PP_ACTIVITY_NAME)

FACTOR Value No Sum of the unit rate

FIXEDFACTOR Value No Sum of the fixed unit rate

6.2.1.23 PPR_HVBREAKDOWNDETAILCOST

Table: PPR_HVBREAKDOWNDETAILCOST

This table contains a summary of unit costs from the PPR_HVUNITRATE table that are grouped by Detailed Cost Object. These are derived from the calculatetransactionalcosts PCMConsole command for a Transactional Costing model type.







TRANSACTIONALRESPCENTERID Member Identifier

No The Responsibility Center ID for the transaction part of the cost

HVLOOKUPID Identifier No Links to the PPR_HVBREAKDOWN table


No ID number for Detailed Cost Object 1 (links to PP_DETAILCOSTOBJECT1_NAME)











VALUE Value No Sum of the original input volume multiplied by the calculated unit rate from the PPR_HVUNITRATE table

FIXEDVALUE Value No Sum of the original input volume multiplied by the calculated fixed unit rate from the PPR_HVUNITRATE table

6.2.1.24 PPR_HVDETAILCOST

Table: PPR_HVDETAILCOST

This table holds the final costs at transaction level from a Transactional Costing model type.









TRANSACTIONALRESPCENTERID Member Identifier

No The Responsibility Center ID for the transaction part of the cost




No ID number for Detail Cost Object 1 (links to PP_DTCOSTOBJECT1ID)









VALUE Value No Detail cost value


Database Tables


FIXEDVALUE Value No Detail cost fixed value

6.2.1.25 PPR_HVLIUNITRATE

Table: PPR_HVLIUNITRATE

This table holds the unit rates by line item activity that are applied to the transaction level drivers to create the detail costs.












No ID number for the Activity (links to PP_LINEITEM_NAME)


No ID number for the Activity Driver(links to PP_ACTIVITYDRIVER_NAME)











HVLOOKUPID Identifier No Links to the PPR_HVBREAKDOWN and PPR_HVBREAKDOWNDETAILCOST tables

UNITRATE Value No Line item activity unit rate value

FIXEDUNITRATE Value Yes Line item activity fixed unit rate value


6.2.1.26 PPR_HVUNITRATE

Table: PPR_HVUNITRATE

This table holds the unit rates that are applied to the transaction level drivers to create the detail costs.












No ID number for the Activity Driver(links to PP_ACTIVITYDRIVER_NAME)











HVLOOKUPID Identifier No Links to the PPR_HVBREAKDOWN and PPR_HVBREAKDOWNDETAILCOST tables

UNITRATE Value No Unit Rate value

FIXEDUNITRATE Value Yes Fixed Unit Rate value

6.2.1.27 PPR_LICOSTOBJECTVALUE

Table: PPR_LICOSTOBJECTVALUE

This table holds the dimension item IDs and results produced by calculating the line item cost object values.


Database Tables




















VALUE Value No Line Item Cost Object value

FIXEDVALUE Value No Fixed Line Item Cost Object value

VARIABLEVALUE Value No Variable Line Item Cost Object value

6.2.1.28 PPR_NODE_LEVEL

Table: PPR_NODE_LEVEL

This table is used in conjunction with universe files to enable SAP BusinessObjects Enterprise to query the results of hierarchical data contained within Profitability and Cost Management dimensions for reporting and analysis. Reporting is achieved by using external reporting tools such as SAP BusinessObjects Web Intelligence to consume universe files. The table contains data about the number of levels that are present in the hierarchy of a dimension, which can contain up to a maximum of three levels.

RestrictionThe functionality to report on Profitability and Cost Management hierarchical data by using this table is currently not available in the software (version 10.0 Support Package 01).









DIMENSIONLEVELID Identifier No Position of the dimension item in the hierarchy.

LVL Identifier No Additional indicator of the position of a dimension in a hierarchy, used for reporting purposes.

DESCRIPTION Level description

No Textual description of a dimension level

6.2.1.29 PPR_POSTREASSIGNLINEITEMVALUE

Table: PPR_POSTREASSIGNLINEITEMVALUE

This table contains the dimension item IDs and results of Line Item values after reassignments.













Database Tables




VALUE Value No Post re-assigned Activity Line Item value

FIXEDVALUE Value No Fixed component of the post re-assigned Activity Line Item value

VARIABLEVALUE Value No Variable component of the post re-assigned Activity Line Item value

6.2.1.30 PPR_RBACTIVITYDRIVERVALUE

Table: PPR_RBACTIVITYDRIVERVALUE

This table holds the dimension item IDs and results produced by calculating the Rule Based Activity Driver values.




















COSTOBEJCT5ID Member Identifier


VALUE Value No Activity Driver value


6.2.1.31 PPR_RBCURRENCYRATES

Table: PPR_RBCURRENCYRATES

This table holds the dimension item IDs and results produced by calculating the rule based currency values.









No ID number for a Currency item (links to PP_CURRENCY_NAME)

RATE Value No Currency rate

6.2.1.32 PPR_RBEMPLOYEERDS

Table: PPR_RBEMPLOYEERDS

This table holds the dimension item IDs and results produced by calculating the rule based Employee Resource Driver Split values (see description below for the relevant dimension table).










EMPLOYEEID Member Identifier

No ID number for the Employee (links to PP_EMPLOYEE_NAME)






Database Tables


VALUE Value No Employee Resource Driver Split value

6.2.1.33 PPR_RBHVEXTACTCOUNITRATE

Table: PPR_RBHVEXTACTCOUNITRATE

This table holds the results for calculated rules based unit rates from a Transactional Costing model type.













No ID number for Activity Driver (links to PP_ACTIVITYDRIVER_NAME )











UNITRATE Value No External Unit Rate

FIXEDUNITRATE Value No Fixed Unit Rate

6.2.1.34 PPR_RBEXTERNALBOMUNITRATE

Table: PPR_RBEXTERNALBOMUNITRATE


This table contains the dimension item IDs and results of rule based external Bill Of Materials unit rates.
















VALUE Value No The Bill of Materials external unit rate value

6.2.1.35 PPR_RBLINEITEMDETAILVALUE

Table: PPR_RBLINEITEMDETAILVALUE

This table holds the dimension item IDs and results produced by calculating the rule based Line Item Detail values.







No ID number for Period (links to PP_PERIOD_NAME)



LINEITEMDETAILID Member Identifier

No ID number for the Line Item Detail (links to PP_LINEITEMDETAIL_NAME)


Database Tables




VALUE Value No Line Item Detail value

6.2.1.36 PPR_RBLINEITEMFIXEDVALUE

Table: PPR_RBLINEITEMFIXEDVALUE

This table holds the dimension item IDs and results produced by calculating the rule based Line Item Fixed values.












FIXEDVALUE Value No Fixed Line Item value

6.2.1.37 PPR_RBLINEITEMVALUE

Table: PPR_RBLINEITEMVALUE

This table holds the dimension item IDs and results produced by calculating the rule based Line Item values.














VALUE Value No Line Item value

FIXEDVALUE Value No Fixed Line Item value

VARIABLEVALUE Value No Variable Line Item value

6.2.1.38 PPR_RBLINEITEMVARVALUE

Table: PPR_RBLINEITEMVARVALUE

This table holds the dimension item IDs and results produced by calculating the rule based Line Item Variability values.












VARIABILITY Value No Line Item Variability value

6.2.1.39 PPR_RBRESOURCEDRIVERSPLIT

Table: PPR_RBRESOURCEDRIVERSPLIT

This table holds the dimension item IDs and results produced by calculating the rule based Resource Driver Split values.


Database Tables










RESOURCECENTERID Member Identifier




VALUE Value No Resource Driver split value

PCT_VALUE Value No Resource Driver percentage split value

6.2.1.40 PPR_RBRESOURCEDRIVERVALUE

Table: PPR_RBRESOURCEDRIVERVALUE

This table holds the dimension item IDs and results produced by calculating the rule based Resource Driver values.












VALUE Value No Resource Driver value


6.2.1.41 PPR_RBREVENUE

Table: PPR_RBREVENUE

This table holds the dimension item IDs and results produced by calculating the rule based Revenue Type values.










REVENUETYPEID Member Identifier

No ID number for a Revenue Type (links to PP_REVENUETYPE_NAME)











UNITPRICE Value No Unit Price value

UNITSSOLD Value No Units Sold value

REVENUE Value No Revenue value

6.2.1.42 PPR_RBSERVICEDRIVERVALUE

Table: PPR_RBSERVICEDRIVERVALUE

This table holds the dimension item IDs and results produced by calculating the rule based Service Driver values.


Database Tables












VALUE Value No Service Driver value

6.2.1.43 PPR_RBSERVICEFACTOR

Table: PPR_RBSERVICEFACTOR

This table holds the dimension item IDs and results produced by calculating the rule based Service Factor values.












VARIABLEFACTOR Value No Variable Factor value

FIXEDUNITRATE Value No Fixed Unit Rate value



6.2.1.44 PPR_RBSPREADVALUE

Table: PPR_RBSPREADVALUE

This table holds the dimension item IDs and results produced by calculating the rule based spread values.








SPREADID Member Identifier

No ID number for the Spread (links PP_SPREAD_NAME)

VALUE Value No Spread value

6.2.1.45 PPR_RBWORKSHEETVALUE

Table: PPR_RBWORKSHEETVALUE

This table holds the dimension item IDs and results produced by calculating the rule based Worksheet values.










WORKSHEET1ID Member Identifier

No ID number for Work Sheet 1 (links to PP_WORKSHEET1_NAME)


No ID number for Work Sheet 2 (links to PP_WORKSHEET2_NAME)

VALUE Value No Worksheet item value


Database Tables

6.2.1.46 PPR_REASSACTLINEITEMVALUE

Table: PPR_REASSACTLINEITEMVALUE

This table holds the dimension item IDs and results produced by calculating the Reassigned Activity Line Item value.


MODELID Identifier No ID number for he model (links to EPO_MODELS)














VALUE Value No Reassigned Activity Line Item value

6.2.1.47 PPR_REASSACTSERVICEVALUE

Table: PPR_REASSACTSERVICEVALUE

This table holds the dimension item IDs and results produced by calculating the Reassigned Activity Service value.













No ID number for the Line Item (links to PP_SERVICE_NAME)





VALUE Value No Reassigned Activity Service value

6.2.1.48 PPR_REASSIGNTRACE

Table: PPR_REASSIGNTRACE

This table holds the dimension item IDs and results produced by calculating the reassigned traceback values.


















INVALUE Value No Reassigned traceback in value

OUTVALUE Value No Reassigned traceback out value

FINALVALUE Value No Reassigned traceback final value

MOVEVALUE Value No Reassigned traceback move value


Database Tables

6.2.1.49 PPR_SERVICEACTIVITYVALUE

Table: PPR_SERVICEACTIVITYVALUE

This table holds the dimension item IDs and results produced by calculating the Service Activity values.
















VALUE Value No Service Activity value

UNITRATE Value No Service Activity Unit Rate value

6.2.1.50 PPR_SERVICECOSTOBJECTVALUE

Table: PPR_SERVICECOSTOBJECTVALUE

This table holds the dimension item IDs and results produced by calculating the Service Cost Object value.


























VALUE Value No Service Cost Object value

6.2.1.51 PPR_SERVICEVALUE

Table: PPR_SERVICEVALUE

This table holds the dimension item IDs and results produced by calculating the Service Cost values.












COST Value No Service Cost value

INCOME Value No Service Income value


Database Tables

6.2.1.52 PPR_SCOSTOBJECTVALUE

Table: PPR_SCOSTOBJECTVALUE

This table holds the dimension item IDs and results produced by calculating the source cost object values.






















VALUE Value No Cost Object value

FIXEDVALUE Value No Fixed Cost Object value

VARIABLEVALUE Value No Variable Cost Object value

6.2.1.53 PPR_SOURCEACTLINEITEMVALUE

Table: PPR_SOURCEACTLINEITEMVALUE

This table holds the dimension item IDs and results produced by calculating the source Activity Line Item values.

















VALUE Value No Source Activity Line Item value

FIXEDVALUE Value No Fixed source Activity Line Item value

VARIABLEVALUE Value No Variable source Activity Line Item value

6.2.1.54 PPR_SPRIMARYACTIVITYDRIVER

Table: PPR_SPRIMARYACTIVITYDRIVER

This table holds the dimension item IDs and results produced by calculating the Services primary Activity Driver values.













Database Tables






VOLUME Value No Services primary Activity Driver value


6.2.1.55 PPR_SUMACTIVITYVALUE

Table: PPR_SUMACTIVITYVALUE

This table holds the dimension item IDs and results produced by calculating the summary Activity values.












VALUE Value No Summary Activity value

FIXEDVALUE Value No Fixed summary Activity value

VARIABLEVALUE Value No Variable summary Activity value

6.2.1.56 PPR_SUMCOSTOBJECTVALUE

Table: PPR_SUMCOSTOBJECTVALUE

This table holds the dimension item IDs and results produced by calculating the summary Cost Object values.





















VALUE Value No Summary Cost Object value

FIXEDVALUE Value No Fixed summary Cost Object value

VARIABLEVALUE Value No Variable summary Cost Object value

6.2.1.57 PPR_SUMMARYMOVEMENTVALUE

Table: PPR_SUMMARYMOVEMENTVALUE

This table holds the dimension item IDs and results produced by calculating the summary movement value.









Database Tables










VALUE Value No Summary movement value

6.2.1.58 PPR_SUMSERVICEACTIVITYVALUE

Table: PPR_SUMSERVICEACTIVITYVALUE

This table holds the dimension item IDs and results produced by calculating the summary Service Activity value.














VALUE Value No Summary Service Activity value

6.2.1.59 PPR_TARGETCOSTOBJECTVALUE

Table: PPR_TARGETCOSTOBJECTVALUE

This table holds the dimension item IDs and results produced by calculating the target Cost Object value.



























VALUE Value No Target Cost Object value

6.2.1.60 PPR_TOTCOSTOBJECTVALUE

Table: PPR_TOTCOSTOBJECTVALUE

This table holds the dimension item IDs and results produced by calculating the total Cost Object values.





Database Tables
















VALUE Value No Total Cost Object value

FIXEDVALUE Value No Fixed total Cost Object value

VARIABLEVALUE Value No Variable total Cost Object value

6.2.1.61 PPR_TRACEBACKVALUE

Table: PPR_TRACEBACKVALUE

This table holds the dimension item IDs and results produced by calculating the traceback value.











No ID number for the Activity (links to PP_LINEITEM_NAME)






No ID number for Activity (links to PP_ACTIVITY_NAME)











VALUE Value No Traceback value

FIXEDVALUE Value No Fixed traceback value

VARIABLEVALUE Value No Variable traceback value

6.2.1.62 OMR_EMPLOYEERESULTVALUE

Table: OMR_EMPLOYEERESULTVALUE

This table holds the dimension item IDs and results produced by calculating the Employee Results values (see description below for the relevant dimension table).











No ID number for the Employee (links to PP_EMPLOYEE_NAME)






Database Tables


RESULTVALUE Value No Employee result value

RESULTICON Value No Employee result Icon

RESULTRANGECOLOR Value No Employee result Range color

RESULTDATACOLOR Value No Employee result Data color

6.2.1.63 OMR_METRICRESULTVALUE

Table: OMR_METRICRESULTVALUE

This table holds the dimension item IDs and results produced by calculating the metrics results.










METRICID Member Identifier

No ID number of the Metric (links to PP_METRIC_NAME)





TOTALACTUALVALUE Value No Metric total actual value

TOTALTARGETVALUE Value No Metric total target value

TOTALACTUALICON Value No Metric total actual Icon

TOTALACTUALRANGECOLOR Value No Metric total actual Range color

TOTALACTUALDATACOLOR Value No Metric total actual data color

VARIANCEVALUE Value No Metric variance value

ACHIEVEMENTVALUE Value No Metric achievement value

ACHIEVEMENTICON Value No Metric achievement Icon

ACHIEVEMENTRANGECOLOR Value No Metric achievement Range color



ACHIEVEMENTDATACOLOR Value No Metric achievement data color

6.2.1.64 OMR_OBJECTIVERESULTVALUE

Table: OMR_OBJECTIVERESULTVALUE

This table holds the dimension item IDs and results produced by calculating the objectives results.










OBJECTIVEID Member Identifier

No ID number of the Objective (links to PP_OBJECTIVES_NAME)





TOTALACTUALVALUE Value No Objective total actual value

TOTALTARGETVALUE Value No Objective total target value

ACHIEVEMENTVALUE Value No Objective achievement value

LINKEDRESULTVALUE Value No Objective linked result value

METRICRESULTSVALUE Value No Objective Metric results value

RESULTVALUE Value No Objective result value

TOTALACTUALICON Value No Objective total actual Icon

TOTALACTUALRANGECOLOR Value No Objective total actual Range color

TOTALACTUALDATACOLOR Value No Objective total actual Data color

RESULTICON Value No Objective result Icon

RRSULTRANGECOLOR Value No Objective result Range color

RESULTDATACOLOR Value No Objective result Data color


Database Tables


ACHIEVEMENTICON Value No Objective achievement Icon

ACHIEVEMENTRANGECOLOR Value No Objective achievement Range color

ACHIEVEMENTDATACOLOR Value No Objective achievement Data color

METRICACHIEVEMENTICON Value No Objective Metric achievement Icon

METRICACHIEVEMENTRANGECOLOR Value No Objective Metric achievement Range color

METRICACHIEVEMENTDATACOLOR Value No Objective Metric achievement Data color

LINKEDRESULTICON Value No Objective linked result Icon

LINKEDRESULTRANGECOLOR Value No Objective linked result Range color

LINKEDRESULTDATACOLOR Value No Objective linked result Data color

6.2.2 Dimension Tables

All dimension tables referred to in the “Results Tables” section contain the following fields:


ID (Key) Identifier No Unique ID relating to dimension item

LANGID (Key) Identifier No Language ID relating to data alias

MODELID (Key) Identifier No ID number of model

NAME Member Name

Yes Name of the dimension item

MEMO Other Text Yes Memo text for a dimension item

CHANGEREVISION Audit Identifier

No Number of times the dimension item has been amended

AUDITUSERID Identifier No User ID of last user to amend the model

DATEALTERED Date No Date of last amendment to the model

The dimension tables are listed below:

● PP_ACTIVITY_NAME● PP_ACTIVITYDRIVER_NAME● PP_BOUNDARY_NAME● PP_COSTOBJECT1_NAME● PP_COSTOBJECT2_NAME● PP_COSTOBJECT3_NAME● PP_COSTOBJECT4_NAME● PP_COSTOBJECT5_NAME● PP_DTCOSTOBJECT1_NAME● PP_DTCOSTOBJECT2_NAME


● PP_DTCOSTOBJECT3_NAME● PP_DTCOSTOBJECT4_NAME● PP_DTCOSTOBJECT5_NAME● PP_EMPLOYEE_NAME● PP_LINEITEM_NAME● PP_ICON_NAME● PP_METRICS_NAME● PP_OBJECTIVE_NAME● PP_PERIOD_NAME● PP_RESOURCEDRIVER_NAME● PP_RESPCENTER_NAME● PP_SERVICE_NAME● PP_VERSION_NAME

6.2.3 Results Views

A set of views are available to provide a more user friendly view of the results tables. The views use the EPO Codes in the PPR_ and OMR_ results tables and join to the relevant dimension tables to display the default alias dimension item names for the associated calculated values. The names for standard views have a prefix of “V”, so for example, for PPR_COSTOBJECTVALUE the view name is VPPR_COSTOBJECTVALUE. (Exceptions to the usual method for constructing view names are detailed in a note at the end of this topic.)

Additionally, for each view there are further equivalent views available that can be used in different circumstances as appropriate:

● The “SM” view is available for Microsoft SQL Server & SAP Adaptive Server Enterprise databases. This executes a different structured query plan with a merged join, which may return results more efficiently. The view name is constructed by adding a suffix of “SM” to the name. For example, VPPR_COSTOBJECTVALUE has an equivalent view called VPPR_COSTOBJECTVALUESM.

● The “BW” views have the column names shortened and the dimension item names shortened to 32 characters. These views can be used for systems that have naming conventions with character restrictions. They have been added to the product to simplify the integration of results into SAP Netweaver® Business Warehouse through DBConnect. The view name is constructed by replacing the prefix of “V” with “BW”. For example, VPPR_COSTOBJECTVALUE has an equivalent view called BWPPR_COSTOBJECTVALUE.

The “SM” and “BW” views both return the same data, but they are optimized differently. In summary, data may be returned more efficiently from either view depending on your environment and the volume of data. Because each SAP BusinessObjects Profitability and Cost Management implementation is unique, we do not recommend a specific view, but suggest that each view type is tested to determine which one works the most efficiently in your particular environment.

TipCustom views can be written if an alias other than the default is required. This can be achieved by linking in the EPO_DATA_ALIAS table. The alias table ID can be linked to the Lang ID of the relevant dimension table, which in turn links to the relevant results table.


Database Tables

NoteExceptions exist for the formatting of certain view names where necessary, to restrict the name length. These are detailed below:

● View names for ppr_rbexternalcostobjectvalue:○ vppr_rbexternalcovalue○ vppr_rbexternalcovaluesm○ bwppr_rbexternalcovalue

● View names for ppr_rbexternalactivityvalue:○ vppr_rbexternalactvalue○ vppr_rbexternalactvaluesm○ bwppr_rbexternalactvalue

● View names for ppr_postreassignlineitemvalue:○ vppr_postrelineitemvalue○ vppr_postrelineitemvaluesm○ bwppr_postrelineitemvalue

Related Information

About Results Tables [page 110]

6.2.4 Exporting Results

Results are exported from the Model Builder application, and the Export to Database option is available to export calculated results to the results tables. The usage of this option is detailed in the SAP BusinessObjects Profitability and Cost Management Modeling User Guide.

6.2.4.1 Export to Database

When an Export to Database is performed, each export of calculated results to the database has an export ID associated with it, which groups the data for different report types that may be required. From a database perspective, this allows the extraction of data from the results tables by export_id.

For example, when two sets of Cost Object results are exported to support different reports, they are each given a separate export ID. If either set of data needs to be replaced, then the data can be re-exported with the same ID.


6.3 About Audit Tables

A set of tables is provided to hold auditing data. These tables, are created when running the initial table build scripts, and each are associated with an equivalent table in the database that supports the software application. They fall into two categories; those that record alterations to data tables in the software framework, and those that record changes to the tables that represent your specific software application.

Almost all of the records in these tables start with fields called AUDITID and OPERATIONID that are fundamental to the auditing process.

The table below provides a description for these fields:

Field Name

AUDITID This is the first field in most audit records and is an identifier that is unique within each audit table. It allows the auditing process to identify and order the alterations that have been performed to a specific database table used to support the software application. The nature of the performed alteration is signified by the OPERATIONID field.

OPERATIONID This is the second field in most audit records. Within each audit table, it identifies the alteration that was made to the equivalent database table that supports the software application. The following identifiers signify the type of change:

● 1 - New record inserted.● 2 - Existing record updated.● 3 - Snapshot. When auditing is off, and is then turned

on the audit state of the database is indeterminate and a snapshot is taken of all existing records. These are signified with this ID value.

NoteWhen a record is deleted, the existing audit records relating to the deletion candidate are updated with user and date in the DELETEUSERID and DELETEDATE fields.

The list below details the different types of audit tables and the type of data that is recorded into them:

● EPO_AU_ - The audit tables for recording software framework changes are prefixed with these characters. These tables contain auditing data for views, books, security, dimension structure, data alias and rules.

● PP_AU_ - The Profitability and Costing, Bill of Materials and Transactional Costing audit tables are prefixed with these characters.

● OM_AU_ - The prefix for the Objectives and Metrics audit tables.

These prefixes are followed by the name of the table that has been altered, for example: EPO_AU_BOOK_INFO and PP_AU_ACTIVITYREASSIGN.


Database Tables

NoteAudit is switched on/off for core framework tables via the Configuration Wizard. The user who performs the configuration MUST be a member of the database DBO user group for Audit to function correctly. If restricted user access is required, and Audit needs switching on, you must run the Configuration Wizard first as a user who is a member of the DBO group, then a second time as the restricted user.

6.3.1 Framework Audit Tables

6.3.1.1 EPO_AU_BOOKS

Table: EPO_AU_BOOKS

This table contains audit data for EPO_BOOKS table.


AUDITID (Key) Identifier No Unique ID number relating to audit item

OPERATIONID Identifier No ID number relating to type of audit operation

ID Identifier No ID number for the book


PARENTID Identifier No ID number for the parent book

SECURITYID Identifier No ID number for the security record

AUDITUSERID Identifier No User ID of the last user to amend record

DATEALTERED Date No Date of the last amendment to record

DELETEUSERID Identifier Yes User ID of the user who deleted record

DELETEDATE Date Yes Date of deleted

6.3.1.2 EPO_AU_BOOK_PROPERTY

Table: EPO_AU_BOOK_PROPERTY

This table contains audit data for EPO_BOOK_PROPERTY table.


AUDITID (Key) Identifier No Unique ID relating to audit item






CATEGORY Other Text Yes Category

VALUE NMemo Yes Value




DELETEDATE Date Yes Date deleted

6.3.1.3 EPO_AU_BOOK_NAME

Table: EPO_AU_BOOK_NAME

This table contains audit data for EPO_BOOK_NAME table.


AUDITID (Key) Identifier No Unique ID relating toaudit item




LANGID Identifier No ID number for the language

NAME Other Text Yes Name of the book





6.3.1.4 EPO_AU_BOOK_INFO

Table: EPO_AU_BOOK_INFO

This table contains the audit data for the EPO_BOOK_INFO table.


AUDITID (Key) Identifier No Unique ID number relating to the audit item




Database Tables



BOOKTYPE Identifier No Book type

XML NMemo Yes XML representation of the book

AUDITUSERID Identifier No User ID of the last user to amend the record


DELETEUSERID Identifier Yes User ID of the user who deleted the record


6.3.1.5 EPO_AU_CELLMEMO

Table: EPO_AU_CELLMEMO

This table contains audit data for EPO_AU_CELLMEMO table.





TABLEFIELDID Identifier No ID of table field

REFERENCE Other Text No String containing unique IDs for dimension items making up key set for a value

MEMO Memo No Memo text for the model


No Number of times the item has been amended





6.3.1.6 EPO_AU_CURRENCY_PROPERTY

Table: EPO_AU_CURRENCY_PROPERTY

This table contains audit data for EPO_CURRENCY_PROPERTY table.





NAME Member Name

No Name of the Currency item

ID Identifier No ID number for the Currency item item

VALUE Other Text Yes Currency formatting





6.3.1.7 EPO_AU_DATA_ALIAS

Table: EPO_AU_DATA_ALIAS

This table contains audit data for EPO_DATA_ALIAS table.




ID Identifier No ID number for the Data Alias

NAME Member Name

No Name of the Data Alias







6.3.1.8 EPO_AU_DEFAULT_BOOK

Table: EPO_AU_DEFAULT_BOOK

This table contains audit data for EPO_DEFAULT_BOOK table.


Database Tables






GROUPID Identifier No ID number for the user group


DATEALTERED Date No Date of last amendment to record

DELETEUSERID Identifier Yes User ID of user who deleted record


6.3.1.9 EPO_AU_DIMENSION_AT

Table: EPO_AU_DIMENSION_AT

This table contains audit data for all of PP_AT_<dimension> tables, like PP_AT_VERSION. In the software, each dimension has its own attribute table. Changes to all of these are recorded through this audit table.


AUDITID (Key) Identifier No Unique ID number relating toaudit item


DIMENSIONID Identifier No ID number for the Dimension

MODELID Identifier No ID number for the Model

ID Identifier No ID number for the Attribute item

PARENTATTRIBID Identifier No ID number for the parent Attribute

CONSOLTYPE Identifier No Consolidation type

CHILDSORT Order Identifier

No CHILDSORT parameter

CHANGEREVISION Identifier No Number of times the item has been amended

LATEST Order Identifier

Yes LATEST parameter






6.3.1.10 EPO_AU_DIMENSION_NAME

Table: EPO_AU_DIMENSION_NAME

This table contains audit data for all of PP_<dimension>_NAME tables, like PP_VERSION_NAME. In the software, each dimension has its own name table. Changes to all of these are recorded through this audit table.






ID Identifier No ID number for the Dimension item


NAME Member Name

No Name of the Dimension item







6.3.1.11 EPO_AU_DIMENSION_RULE

Table: EPO_AU_DIMENSION_RULE

This table contains audit data for all of PP_<dimension>_RULE tables, like PP_VERSION_RULE. In the software, each dimension has its own rules table. Changes to all of these are recorded through this audit table.




DIMENSIONID Identifier No ID number for the dimension item

ID Identifier No ID number for the rule


RULENUMBER Identifier No Rule number

WIZARDNUMBER Identifier No WIZARD number parameter

RULETEXT NMemo Yes Rule script


Database Tables




RULEDESC Other Text Yes Rule description







6.3.1.12 EPO_AU_DIMENSION_STRUCTURE

Table: EPO_AU_DIMENSION_STRUCTURE

This table contains audit data for all of PP_<dimension> tables, like PP_VERSION. In the software, each dimension has its own table. Changes to all of these are recorded through this audit table.





MODELID Identifier Yes ID number for the model


PARENTID Identifier No ID number for the parent item


CONSOLTYPE Consolidation Type Identifier

No Consolidation type

ATTRIBUTEINFO Other Text Yes Attribute type

CHILDSORT Order Identifier

No CHILDSORT parameter

ITEMSTATUS Member Identifier

No Dimension item status











6.3.1.13 EPO_AU_DV_INFO

Table: EPO_AU_DV_INFO

This table contains audit data for EPO_DV_INFO table.




ID Identifier No ID number for the layout

APP_TYPE Identifier No Model type

SRC_MODEL_ID Identifier No ID number for the model that layout originates from

VIEW_NAME Other Text No Name of the layout


DATEALTERED Date No Date of the last amendment torecord



6.3.1.14 EPO_AU_GROUP_INFO

Table: EPO_AU_GROUP_INFO

This table contains audit data for EPO_GROUP_INFO table.





CATEGORY Other Text Yes Group category

VALUE NMemo Yes Group value


Database Tables






6.3.1.15 EPO_AU_GROUP_ROOT

Table: EPO_AU_GROUP_ROOT

This table contains audit data for EPO_GROUP_ROOT table.






DIMID Identifier No ID number for the Dimension






6.3.1.16 EPO_AU_GROUPS

Table: EPO_AU_GROUPS

This table contains audit data for EPO_GROUPS table.




ID Identifier Yes ID of the user group

NAME Other Text Yes Name of the user group







6.3.1.17 EPO_AU_METADATA_VERSION

Table: EPO_AU_METADATA_VERSION

This table contains audit data for EPO_METADATA_VERSION table.




MAJOR Identifier Yes Major release number

MINOR Identifier Yes Minor release number

PATCH Identifier Yes Patch number





6.3.1.18 EPO_AU_MODEL_GROUPS

Table: EPO_AU_MODEL_GROUPS

This table contains audit data for EPO_MODEL_GROUPS table.










Database Tables



6.3.1.19 EPO_AU_MODEL_PARTITION

Table: EPO_AU_MODEL_PARTITION

This table contains audit data for EPO_MODEL_PARTITION table.






Yes ID number for the Version


Yes ID number for the Period


Yes ID number for the Responsibility Center

PRECEDENCE Identifier Yes Partition precedence

PARTITION Identifier Yes Partition number

SERVER Other Text Yes Server name





6.3.1.20 EPO_AU_MODEL_PROPERTY

Table: EPO_AU_MODEL_PROPERTY

This table contains audit data for EPO_MODEL_PROPERTY table.







ID Identifier No ID number for the property

NAME Other Text No Name of the property

DEFAULTVALUE Other Text No Default property item value





6.3.1.21 EPO_AU_MODEL_PROPERTY_VALUE

Table: EPO_AU_MODEL_PROPERTY_VALUE

This table contains audit data for EPO_MODEL_PROPERTY_VALUE table.





PROPERTYID Identifier No ID number for the property

DIMENSIONITEMID Identifier No ID number for the Dimension item

VALUE Other Text No Property value





6.3.1.22 EPO_AU_MODEL_SERVERS

Table: EPO_AU_MODEL_SERVERS

This table contains audit data for EPO_MODEL_SERVERS table.





Database Tables



SERVER Other Text No Server name





6.3.1.23 EPO_AU_MODELS

Table: EPO_AU_MODELS

This table contains audit data for EPO_MODELS table.


AUDITID (Key) Identifier No Unique ID relating to audit item

OPERATIONID Identifier No ID relating to type of audit operation

ID Identifier No ID number for the model

MODELTYPE Identifier No Model type

MODELNAME Other Text No Name of the model


NEXTUNIQUEID Identifier Yes Next available EPO code for the model

MODELSYNC Identifier Yes MODELSYNC parameter

MODELSTATUS Identifier No Model status





6.3.1.24 EPO_AU_REPORTS

Table: EPO_AU_REPORTS

This table contains audit data for EPO_REPORTS table.





REPORT_ID Identifier Yes ID number for the report

NAME Other Text Yes Name of the report

SECURITY_ID Identifier Yes ID number of the security record





6.3.1.25 EPO_AU_SECURITY

Table: EPO_AU_SECURITY

This table contains audit data for EPO_SECURITY table.





ID Identifier No ID number for the security record

SECURITYTYPE Identifier Yes Security type





6.3.1.26 EPO_AU_SECURITY_INFO

Table: EPO_AU_SECURITY_INFO

This table contains audit data for EPO_SECURITY_INFO table.




Database Tables






SECURITYCONTEXT Identifier Yes Security context





6.3.1.27 EPO_AU_SECURITY_NAME

Table: EPO_AU_SECURITY_NAME

This table contains audit data for EPO_SECURITY_NAME table.




ID Identifier No ID number for the security record



NAME Other Text Yes Security name



Yes Number of times the item has been amended





6.3.1.28 EPO_AU_SERVERS

Table: EPO_AU_SERVERS

This table contains audit data for EPO_SERVERS table.





SERVER Other Text No Name of the server

COMPONENT_ID Identifier No ID number for the component





6.3.1.29 EPO_AU_USER_GROUP

Table: EPO_AU_USER_GROUP

This table contains audit data for the EPO_USER_GROUP table.





USERID Identifier No ID number for the user





6.3.1.30 EPO_AU_USER_INFO

Table: EPO_AU_USER_INFO

This table contains audit data for EPO_USER_INFO table.




USERID Identifier No ID number of the user


Database Tables


CATEGORY Other Text Yes User category

VALUE NMemo Yes Value





6.3.1.31 EPO_AU_USERS

Table: EPO_AU_USERS

This table contains audit data for EPO_USERS table.


AUDITID (Key) Identifier No Unique ID number relating toaudit item


ID Identifier No ID number for the user

USERNAME Other Text Yes Name of the user

PASSWORD Other Text Yes User password

STATUS Identifier Yes User status





6.3.1.32 EPO_AUDIT_MESSAGES

Table: EPO_AUDIT_MESSAGES

This table contains all the messages produced by auditing (in different languages)


ID (Key) Identifier No ID of Audit table procedure


MESSAGE Other Text Yes Message string


6.3.1.33 EPO_AUDITLOG

Table: EPO_AUDITLOG

This table describes changes made to auditing.



MESSAGEID Identifier No ID number for the audit message

DESCRIPTION Other Text Yes Free text reason for auditing change



6.3.2 Assignment Audit Tables

6.3.2.1 PP_AU_ACTIVITYREASSIGN

Table: PP_AU_ACTIVITYREASSIGN

This table contains audit data for PP_ACTIVITYREASSIGN table.






No ID number for the Version


No ID number for the Period


No ID number for the Responsibility Center


No ID number for the Activity


No ID number for the Resource Driver for reassignment

ARESOURCEDRIVERID Member Identifier

No ID number for the Resource Driver for allocation


No ID number for the Target Responsibility Center


No ID number for the Target Activity


Database Tables








6.3.2.2 PP_AU_ASSRESPCENTERACTIVITY

Table: PP_AU_ASSRESPCENTERACTIVITY

This table contains audit data for PP_ASSRESPCENTERACTIVITY table.















6.3.2.3 PP_AU_COSTOBJECTASSIGNMENT

Table: PP_AU_COSTOBJECTASSIGNMENT

This table contains audit data for PP_COSTOBJECTASSIGNMENT table.







COSTOBJID Member Identifier

No ID number for the Cost Object assignment

COSTOBJECTID Member Identifier

No ID number for the Cost Object

COTYPE Member Identifier

No Cost Object type i.e Activity, Line Item or Service







6.3.2.4 PP_AU_COSTOBJECTDRIVER

Table: PP_AU_COSTOBJECTDRIVER

This table contains audit data for PP_COSTOBJECTDRIVER table.






No ID number for the Cost Object assignment


No ID number for the Activity Driver

VOLUMERESPCENTERTYPE Activity Driver Identifier

No Location of the Activity Driver values. (0 – All, 1 – Parent, Current, 3007 – RC Unassigned)

COTYPE Identifier No Cost Object type i.e Activity, Line Item or Service

DRIVERORDER Order Identifier

No Numeric order in which the Activity Driver is applied (for example, first is 1 and second is 2)





Database Tables





6.3.2.5 PP_AU_COSTOBJITEM

Table: PP_AU_COSTOBJITEM

This table contains audit data for PP_COSTOBJITEM table.





ID Member Identifier


LIACTID Combination Identifier

No ID number for the Activity Line Item combination

LIACTTYPE Member Identifier

No Activity Line Item type













6.3.2.6 PP_AU_LINEITEMDIRECT_ACTIVITY

Table: PP_AU_LINEITEMDIRECT_ACTIVITY

This table contains audit data for PP_LINEITEMDIRECT_ACTIVITY table.













No ID number for the Line Item


No ID number for the Direct Activity



AUDITUSERID Member Identifier

No User ID of the last user to amend the record

DATEALTERED Datetime No Date of the last amendment to the record

DELETEUSERID Member Identifier

Yes User ID of the user who deleted the record

DELETEDATE Datetime Yes Date deleted

6.3.2.7 PP_AU_LINEITEMRESOURCEDRIVER

Table: PP_AU_LINEITEMRESOURCEDRIVER

This table contains audit data for PP_LINEITEMRESOURCEDRIVER table.






Yes ID number for the Version


Yes ID number for the Period


Yes ID number for the Responsibility Center


Database Tables



Yes ID number for the Line Item


Yes ID number for the Resource Driver



AUDITUSERID Identifier Yes User ID of the last user to amend the record

DATEALTERED Date Yes Date of the last amendment to the record



6.3.2.8 PP_AU_SERVICERESOURCEDRIVER

Table: PP_AU_SERVICERESOURCEDRIVER

This table contains audit data for the PP_SERVICERESOURCEDRIVER table.












No ID number for the Service


No ID number for the Resource Driver assigned to the Service




DATEALTERED Date No Date of the last amendment to the record




6.3.2.9 PP_AU_SERVICEDIRECT_ACTIVITY

Table: PP_AU_SERVICEDIRECT_ACTIVITY

This table contains audit data for PP_SERVICEDIRECT_ACTIVITY table.












No ID number for the Service assigned directly to an Activity









6.3.2.10 PP_AU_RESPCENTERSERVICE

Table: PP_AU_RESPCENTERSERVICE

This table contains audit data for PP_RESPCENTERSERVICE table.










Database Tables






6.3.2.11 OM_AU_ASSMETRICRESPCENTER

Table: OM_AU_ASSMETRICRESPCENTER

This table contains audit data for OM_ASSMETRICRESPCENTER table.


AUDITID Identifier No Unique ID number relating to audit item




No ID number for the Metric







DELETEUSERID Identifier No User ID of the user who deleted the record


6.3.2.12 OM_AU_ASSOBJECTIVEINITIATIVE

Table: OM_AU_ASSOBJECTIVEINITIATIVE

This table contains the audit data for the OM_ASSOBJECTIVEINITIATIVE table.








No ID number for the Objective

INITIATIVEID Member Identifier

No ID number for the Initiative







6.3.2.13 OM_AU_ASSOBJECTIVELOBJECTIVE

Table: OM_AU_ASSOBJECTIVELOBJECTIVE

This table contains audit data for the OM_ASSOBJECTIVELOBJECTIVE table.







LINKEDOBJECTIVEID Member Identifier

No ID number for the linked Objective







6.3.2.14 OM_AU_ASSOBJECTIVEMETRIC

Table: OM_AU_ASSOBJECTIVEMETRIC

This table contains the audit data for the OM_ASSOBJECTIVEMETRIC table.


Database Tables


AUDITID Identifier No Unique ID relating to the audit item


MODELID Identifier No ID of the Model


No ID of the Objective


No ID of the Metric


No The number of times the item has been amended





6.3.2.15 OM_AU_ASSOBJECTIVERESPCENTER

Table: OM_AU_ASSOBJECTIVERESPCENTER

This table contains the audit data for the OM_ASSOBJECTIVERESPCENTER table.


AUDITID Identifier No Unique ID relating to the audit item


MODELID Identifier No ID of the Model


No ID of the Objective


No ID of the Responsibility Center








6.3.3 Value Audit Tables

6.3.3.1 PP_AU_ACTIVITYDRIVERDELTA

Table: PP_AU_ACTIVITYDRIVERDELTA

This table contains audit data for PP_ACTIVITYDRIVERDELTA table.














No ID number for Cost Object 1









ACTIVITYDRIVERVALUE Value No Activity Driver Delta value







6.3.3.2 PP_AU_ACTIVITYDRIVERTARGET

Table: PP_AU_ACTIVITYDRIVERTARGET


Database Tables

This table contains audit data for PP_ACTIVITYDRIVERTARGET table.























ACTIVITYDRIVERVALUE Value No Activity Driver Target value







6.3.3.3 PP_AU_ACTIVITYDRIVERVALUE

Table: PP_AU_ACTIVITYDRIVERVALUE

This table contains audit data for PP_ACTIVITYDRIVERVALUE table.

























ACTIVITYDRIVERVALUE Value No Activity Driver value







6.3.3.4 PP_AU_BOMMAKEUP

Table: PP_AU_BOMMAKEUP

This table contains audit data for PP_BOMMAKEUP table.




MODELID Member Identifier

No ID number for the model


Database Tables









No ID number for the Component that is part of the product


No ID number for the Currency item

VOLUME Value Yes







6.3.3.5 PP_AU_BOMPRODUCTION

Table: PP_AU_BOMPRODUCTION

This table contains audit data for PP_BOMPRODUCTION table.




MODELID Member Identifier

No ID number for the model









VALUE Value Yes









6.3.3.6 PP_AU_BOMUNITSSOLD

Table: PP_AU_BOMUNITSSOLD

This table contains audit data for PP_BOMUNITSSOLD table.























VALUE Value Yes





Database Tables





6.3.3.7 PP_AU_CURRENCYRATES

Table: PP_AU_CURRENCYRATES

This table contains audit data for PP_CURRENCYRATES table.




MODELID Identifier No ID number for themodel






No ID number for a Currency item

RATE Value No Currency rate







6.3.3.8 PP_AU_DAVERSION

Table: PP_AU_DAVERSION

This table contains audit data for PP_DAVERSION table.








No ID number for the Driver Analysis Version

REFVERSIONID Member Identifier

No ID number for the Source Version







6.3.3.9 PP_AU_DEFAULTBOMMAKEUP

Table: PP_AU_DEFAULTBOMMAKEUP

This table contains audit data for PP_DEFAULTBOMMAKEUP table.








No ID number for the Component that is part of the product

BOMMAKEUPID Member Identifier

No ID number for the Bill Of Materials Makeup



VOLUME Value Yes








Database Tables

6.3.3.10 PP_AU_EXTERNALBOMUNITRATE

Table: PP_AU_EXTERNALBOMUNITRATE

This table contains audit data for PP_EXTERNALBOMUNITRATE table.












No ID number for Direct Activity







VALUE Value Yes







6.3.3.11 PP_AU_HVACTIVITYDRIVERVOLUME

Table: PP_AU_HVACTIVITYDRIVERVOLUME

This table holds the audit data for the PP_HVACTIVITYDRIVERVOLUME table.














No ID number for the Detail Cost Object 1









ACTIVITYDRIVERVOLUME Value Yes Activity Driver volume







6.3.3.12 PP_AU_HVCOSTOBJECTDRIVER

Table: PP_AU_HVCOSTOBJECTDRIVER

This table holds the audit data for the PP_HVCOSTOBJECTDRIVER table.










Database Tables








6.3.3.13 PP_AU_HVEXTACTCOUNITRATE

Table: PP_AU_HVEXTACTCOUNITRATE

This table contains audit data for the PP_HVEXTACTCOUNITRATE table.



































6.3.3.14 PP_AU_EMPLOYEERDS

Table: PP_AU_EMPLOYEERDS

This table contains the audit data for the PP_EMPLOYEERDS table.












No ID number for the Employee


No ID number for the Resource Driver



VALUE Value No The value of the Split








Database Tables

6.3.3.15 PP_AU_EXTERNALACTIVITYVALUE

Table: PP_AU_EXTERNALACTIVITYVALUE

This table contains audit data for PP_EXTERNALACTIVITYVALUE table.












No ID number for the Direct Activity





EXTERNALACTIVITYVALUE Value Yes External Activity value

EXTERNALACTIVITYFIXEDVALUE Value Yes Fixed external Activity value







6.3.3.16 PP_AU_EXTERNALCOSTOBJECTVALUE

Table: PP_AU_EXTERNALCOSTOBJECTVALUE

This table contains audit data for PP_EXTERNALCOSTOBJECTVALUE table.





























EXTERNALCOSTOBJECTVALUE Value Yes External Cost Object value

EXTERNALCOSTOBJECTFIXEDVALUE Value Yes Fixed external Cost Object value







6.3.3.17 PP_AU_LINEITEMDELTA

Table: PP_AU_LINEITEMDELTA

This table contains audit data for PP_LINEITEMDELTA table.


Database Tables















LINEITEMVALUE Value No Delta value of the Line Item







6.3.3.18 PP_AU_LINEITEMDETAILVALUE

Table: PP_AU_LINEITEMDETAILVALUE

This table contains audit data for PP_LINEITEMDETAILVALUE table.













LINEITEMDETAILID Member Identifier

No ID number for the Line Item Detail item





VALUE Value No Line Item Detail value







6.3.3.19 PP_AU_LINEITEMFIXEDVALUE

Table: PP_AU_LINEITEMFIXEDVALUE

This table contains audit data for PP_LINEITEMFIXEDVALUE table.















VALUE Value No Fixed Line Item value





Database Tables





6.3.3.20 PP_AU_LINEITEMVALUE

Table: PP_AU_LINEITEMVALUE

This table contains the audit data for the PP_LINEITEMVALUE table.















LINEITEMVALUE Numeric No Line Item value







6.3.3.21 PP_AU_LINEITEMVARVALUE

Table: PP_AU_LINEITEMVARVALUE

This table contains audit data for PP_LINEITEMVARVALUE table.














VALUE Value No Variable Line Item value






DELETEDATE Date Yes Date deletion

6.3.3.22 PP_AU_LOCKRESULTS

Table: PP_AU_LOCKRESULTS

This table contains audit data for PP_LOCKRESULTS table.






No ID number for the locked Version


No ID number for the locked Period

CHANGEREVISION Member Identifier





Database Tables




6.3.3.23 PP_AU_METADATA_VERSION

Table: PP_AU_METADATA_VERSION

This table contains audit data for PP_METADATA_VERSION table.




MAJOR Identifier No Major release number

MINOR Identifier No Minor release number

PATCH Identifier No Patch number





6.3.3.24 PP_AU_RESOURCEDRIVERDELTA

Table: PP_AU_RESOURCEDRIVERDELTA















RESOURCEDRIVERVALUE Value No Resource Driver Delta value






DELETEDATE Date Yes Date of deletion

6.3.3.25 PP_AU_RESOURCEDRIVERDSPLIT

This table contains audit data for PP_RESOURCEDRIVERDSPLIT table.















RESOURCEDRIVERVALUE Value No Activity Resource Driver Delta Split value







6.3.3.26 PP_AU_RESOURCEDRIVERSPLIT

Table: PP_AU_RESOURCEDRIVERSPLIT


Database Tables

This table contains audit data for PP_RESOURCEDRIVERSPLIT table.















RESOURCEDRIVERVALUE Value No Activity Resource Driver Split value







6.3.3.27 PP_AU_RESOURCEDRIVERTARGET

Table: PP_AU_RESOURCEDRIVERTARGET

This table contains audit data for PP_RESOURCEDRIVERTARGET table.















RESOURCEDRIVERVALUE Numeric No Resource Driver Target value







6.3.3.28 PP_AU_RESOURCEDRIVERTARSPLIT

Table: PP_AU_RESOURCEDRIVERTARSPLIT

This table contains the audit data for the PP_RESOURCEDRIVERTARSPLIT table.


AUDITID (Key) Identifier No Unique ID relating to the audit item


MODELID Identifier No ID of a Model


No ID of a Version


No ID of a Period


No ID of a Responsibility Center


No ID of a Resource Driver


No ID of an Activity

RESOURCEDRIVERVALUE Value No Resource Driver Target Split Value for the Activity






DELETEDATE Date Yes Date of deletion


Database Tables

6.3.3.29 PP_AU_RESOURCEDRIVERVALUE

Table: PP_AU_RESOURCEDRIVERVALUE

This table contains audit data for PP_RESOURCEDRIVERVALUE table.






No ID number for Version


No ID number for Period


No ID number for Responsibility Center


No ID number for Resource Driver

RESOURCEDRIVERVALUE Value No Resource Driver value


No Number of times item has been amended





6.3.3.30 PP_AU_REVENUE

Table: PP_AU_REVENUE

This table contains audit data for the PP_REVENUE table.













REVENUETYPEID Member Identifier

No ID number for the Revenue Type













UNIT_PRICE Value No Unit Price value

UNITS_SOLD Value No Units Sold value

REVENUE Value No Revenue item value







6.3.3.31 PP_AU_SERVICEDRIVERDELTA

Table: PP_AU_SERVICEDRIVERDELTA

This table contains audit data for PP_SERVICEDRIVERDELTA table.








Database Tables








SERVICEDRIVERVALUE Value No Service Driver Delta value







6.3.3.32 PP_AU_SERVICEDRIVERTARGET

Table: PP_AU_SERVICEDRIVERTARGET

This table contains audit data for PP_SERVICEDRIVERTARGET table.













SERVICEDRIVERVALUE Value No Service Driver Target value









6.3.3.33 PP_AU_SERVICEDRIVERVALUE

Table: PP_AU_SERVICEDRIVERVALUE

This table contains audit data for the PP_SERVICEDRIVERVALUE table.













SERVICEDRIVERVALUE Numeric No Service Driver value







6.3.3.34 PP_AU_SERVICEFACTOR

Table: PP_AU_SERVICEFACTOR

This table contains audit data for the PP_SERVICEFACTOR table.





Database Tables











VARIABLEFACTOR Value No Variable Factor value



No Number of times the item has been the amended





6.3.3.35 PP_AU_SPREADVALUE

Table: PP_AU_SPREADVALUE

This table contains audit data for the PP_SPREADVALUE table.




MODELID Identifier No ID number relating the model


No ID number relating the Version


No ID number relating the Period

SPREADID Member Identifier

No ID number for the Spread

SPREADVALUE Value No Spread value









6.3.3.36 PP_AU_SUBSTITUTIONS

Table: PP_AU_SUBSTITUTIONS

This table contains top level names such as versions and periods data for the PP_SUBSTITUTIONS table.



OPERATIONID Identifier No ID number relating to the type of audit operation


LANGID Identifier No ID number for the Language

ID Identifier No ID number for the substitute item

SUBSTITUTION Other Text Yes Substitute name





6.3.3.37 PP_AU_USER_RULE

Table: PP_AU_USER_RULE

This table contains audit data for the PP_USER_RULE table.





RULETEXT NMemo Yes Rule script




Database Tables


RULEDESC Other Text Yes Rule description

AUDITUSERID Identifier Yes User ID of the last user to amend the record

DATEALTERED Date Yes Date of the last amendment to the record



6.3.3.38 PP_AU_WORKSHEETVALUE

Table: PP_AU_WORKSHEETVALUE

This table contains audit data for the PP_WORKSHEETVALUE table.












No ID number for Work Sheet 1


No ID number for Work Sheet 2

WORKSHEETVALUE Value No Value of Work Sheet array item







6.3.3.39 OM_AU_BOUNDARYINFO

Table: OM_AU_BOUNDARYINFO


This table contains audit data for the OM_BOUNDARYINFO table.





GROUPBOUNDARYID Member Identifier

No ID number for the Group Boundary

BOUNDARYID Member Identifier

No ID number for the Boundary

ICONID Member Identifier

No ID number for the Icon

RANGECOLOR Identifier No Range color

DATACOLOR Identifier No Data color







6.3.3.40 OM_AU_EMPLOYEEB

Table: OM_AU_EMPLOYEEB

This table contains the audit data for the OM_AU_EMPLOYEEB table.






No ID number for Employee


No ID number for Boundary

MEASUREID Member Identifier

No ID number for measure





Database Tables





6.3.3.41 OM_AU_EMPLOYEEBOUNDARY

Table: OM_AU_EMPLOYEEBOUNDARY

This table contains the audit data for the OM_AU_EMPLOYEEBOUNDARY table.












No ID number for Employee








No ID number for Measure

VALUE Value No Employee Boundary value





DELETEUSERID Identifier No User ID of user who deleted record



6.3.3.42 OM_AU_ICONVALUE

Table: OM_AU_ICONVALUE

This table contains audit data for OM_ICONVALUE table.





ICONID Member Identifier

No ID number for Icon

CATEGORY Other Text Yes Icon property

VALUE NMemo Yes An icon value (encoded)


No number of times item has been amended





6.3.3.43 OM_AU_INITIATIVE_DETAIL

Table: OM_AU_INITIATIVE_DETAIL

This table contains the audit data for the OM_INITIATIVE_DETAIL table.





INITIATIVEID Member Identifier

No ID number for the Initiative

SHORTDESCRIPTION Other Text No Initiative name

LONGDESCRIPTION NMemo No Initiative description

AREFERENCE Date Value No Internal system date for the calculation of new initiatives

CREATEUSERID Identifier No User ID of the user who created the initiative


Database Tables


LASTMODIFIEDNAME Other Text No User name of the user who last amended the initiative







6.3.3.44 OM_AU_METRICACTUAL

Table: OM_AU_METRICACTUAL

This table contains audit data for OM_METRICACTUAL table.












No ID number for Metric






No ID number for Currency

VALUE Value No Metric value









6.3.3.45 OM_AU_METRICADJUSTMENT

Table: OM_AU_METRICADJUSTMENT

This table contains audit data for the OM_METRICADJUSTMENT table.



















VALUE Numeric No Metric adjustment value







6.3.3.46 OM_AU_METRICADJUSTTARGET

Table: OM_AU_METRICADJUSTTARGET


Database Tables

This table contains audit data for OM_METRICADJUSTTARGET table.



















VALUE Value No Metric Adjustment Target value







6.3.3.47 OM_AU_METRICB

Table: OM_AU_METRICB

This table contains audit data for the OM_METRICB table.



















6.3.3.48 OM_AU_METRICBASEPOINT

Table: OM_AU_METRICBASEPOINT

This table contains audit data for the OM_METRICBASEPOINT table.



















VALUE Value No Metric basepoint value





Database Tables





6.3.3.49 OM_AU_METRICBOUNDARY

Table: OM_AU_METRICBOUNDARY

This table contains audit data for the OM_METRICBOUNDARY table.





















VALUE Value No Metric Boundary value








6.3.3.50 OM_AU_METRICTARGET

Table: OM_AU_METRICTARGET

This table contains audit data for the OM_METRICTARGET table.



















VALUE Value No Metric Target value







6.3.3.51 OM_AU_OBJECTIVEACTUAL

Table: OM_AU_OBJECTIVEACTUAL

This table contains audit data for OM_OBJECTIVEACTUAL table.





Database Tables










No ID number for Objective





VALUE Value No Objective Actual value







6.3.3.52 OM_AU_OBJECTIVEADJUSTMENT

Table: OM_AU_OBJECTIVEADJUSTMENT

This table contains audit data for the OM_OBJECTIVEADJUSTMENT table.



















VALUE Value No Objective Adjustment value







6.3.3.53 OM_AU_OBJECTIVEADJUSTTARGET

Table: OM_AU_OBJECTIVEADJUSTTARGET

This table contains audit data for the OM_OBJECTIVEADJUSTTARGET table.

















VALUE Value No Objective Adjustment Target value





Database Tables





6.3.3.54 OM_AU_OBJECTIVEB

Table: OM_AU_OBJECTIVEB

This table contains audit data for the OM_OBJECTIVEB table.

















6.3.3.55 OM_AU_OBJECTIVEBASEPOINT

Table: OM_AU_OBJECTIVEBASEPOINT

This table contains audit data for the OM_OBJECTIVEBASEPOINT table.



















VALUE Value No Objective basepoint value






DELETEDATE Date Yes Date of deleted

6.3.3.56 OM_AU_OBJECTIVEBOUNDARY

Table: OM_AU_OBJECTIVEBOUNDARY

This table contains audit data for the OM_OBJECTIVEBOUNDARY table.














Database Tables










VALUE Value No Objective Boundary value







6.3.3.57 OM_AU_OBJECTIVEMETRICWEIGHTING

Table: OM_AU_OBJECTIVEMETRICWEIGHTING

This table contains audit data for the OM_OBJECTIVEMETRICWEIGHTING table.














No ID number for the Metric







WEIGHTING Value No Objective Metric Weighting value







6.3.3.58 OM_AU_OBJECTIVETARGET

Table: OM_AU_OBJECTIVETARGET

This table contains audit data for the OM_OBJECTIVETARGET table.

















VALUE Value No Objective Target value







Database Tables



6.3.3.59 OM_AU_OBJECTIVEWEIGHTING

Table: OM_AU_OBJECTIVEWEIGHTING

This table contains audit data for the OM_OBJECTIVEWEIGHTING table.













LINKEDOBJECTIVEID Member Identifier

No ID number for the linked Objective





WEIGHTING Value No Weighting value








7 Organizing an Update Using Data Bridge

Data Bridge is an intelligent bulk data-input tool for populating the data tables in SAP BusinessObjects Profitability and Cost Management.

It provides the means to transfer data into a model from flat files, such as comma separated values (CSV) files, and external datasources, such as SAP Netweaver® Business Warehouse (SAP Netweaver BW ).

Data Bridge is primarily intended for routinely updating an existing model with Costs and Driver Values for the next Period. It can also be used in many other ways for moving data into models, although the complexity involved in data preparation can mean there are easier ways of accomplishing certain tasks. For example, if you are transferring data between models, the Export/Import features provided in the applications have been designed to cover all likely options.

When using Data Bridge you should be aware that the integrity of your model could easily be compromised by incorrect data. This means that you should be sure to create a backup before starting and you must check your model after completion. If you are updating costs and values in an existing model on a regular basis, your procedures will be well established and your data will target specific items in the model structure that are easy to verify. If, however, you are creating structures, any mistakes in your data could produce peculiarities that might take you some time to resolve.

When you build a new model, you must first build its Dimensions and their Hierarchies, then its Assignments, and finally you must input its Costs and Driver Values. The cleanest method for achieving this is through the user interface provided in your application. You can see structural items as you create them, and have views of their hierarchies and the assignments you specify. Thereafter you can use Data Bridge to set up procedures that support periodic updates of costs and values.

Database tables can be used by Data Bridge to define a model. These identify the sequence of steps involved in building a new model. Any partial update to an established model at any of these stages requires an understanding of its current state to ensure the update performs in the way you expect.

7.1 Structure

Using Data Bridge to introduce structure via a flat file to your model involves composing input files in a detailed format.

When planning how to build the dimension structures of your model, you should initially consider doing it through the user interface of your application, because this will guarantee the integrity of your database. Using Data Bridge for this purpose is a great deal more complex than typing, but if you need to follow this course you must first understand the composition of the database tables that support its dimensions.

Whereas all SAP Business Objects Profitability and Cost Management applications have a different set of dimensions; all dimensions share the same structure. Most of the dimensions have a multi-level main hierarchy and several also have an attribute hierarchy. The Currencies dimension is unusual because it has a flat structure with no attribute hierarchy. An attribute item defines a characteristic that you wish to associate with particular items in the main hierarchy. Attribute items can be groups in the same way as items in the main hierarchy, so both hierarchies are multi-level. Main hierarchy items can have several attributes, so they can


Organizing an Update Using Data Bridge

belong to several attribute groups. You can find a full description of dimension hierarchies in the SAP BusinessObjects Profitability and Cost Management Modeling User Guide or the F1 Help of the application.

Related Information

Building Attribute Assignments [page 238]

7.1.1 Building Hierarchies

Dimension structures in an application are defined through the ParentChild table.

Dimension structures are built up in a three-phase process that involves detailed preparation of ParentChild input files if you choose to use flat files to import structural data. The stages for implementing the standard import method are:

Build a Main HierarchyBuild an Attribute HierarchyBuild Attribute Assignments

7.1.1.1 Building a Main Hierarchy

This is the first stage of the recommended process for building dimension structures in a model and is only concerned with defining the structure of items in the Main Hierarchy of all the dimensions in your model.

If you are using flat files to build a structure, your main task is to create the ParentChild input data that represents your intended hierarchies. You then can use Data Bridge to create the associated Specification file and the Control file that drives the import.

Consider the Main Hierarchy for Responsibility Centers shown below:

The ParentChild CSV file that you need to construct to obtain this structure is shown below:

Dimension Parent Child Attribute Flags Consolidation Type

Responsibility Centers Group Responsibility Centers

Responsibility Center One

10 +

SAP BusinessObjects Profitability and Cost Management Database Administrator's GuideOrganizing an Update Using Data Bridge P U B L I C 235



Responsibility Center Two

10 ~


Responsibility Center Three

10 -

NoteOnly three records are required to define the four items in the hierarchy. The Group item is created automatically at the top level of the hierarchy when the first record is imported. The Attribute Flags all have the value 10 which specifies all records as:

Parent is a Main Hierarchy GroupChild is a Main Hierarchy Group

This Attribute Flag value is a static value that is suitable for all records defined at this stage. Although Child items are apparently defined as Groups, they will appear as children and only become groups if additional records specify them as Parents with a specific Child.

You should check your results after this stage to ensure you have produced the structure you wanted, because this gives the opportunity to recover from errors in your data with the minimum disruption.

The Consolidation Type applies to the Child item specified in the record. All the Main Hierarchy Consolidation Types are demonstrated by this example.

NoteThe Parent and Child names used in the input data records are defined across all Data Aliases defined in your model.

After building the Main Hierarchy, the second stage of the process for building structures is to build an Attribute Hierarchy.

Related Information

Building an Attribute Hierarchy [page 237]Building Attribute Assignments [page 238]Building Attribute Assignments [page 238]



7.1.1.2 Building an Attribute Hierarchy

This is the second stage of the recommended process for building dimension structures in a model and is solely concerned with defining the structure of items in the Attribute Hierarchy of all the dimensions in your model.

The main task you have to perform is to create the ParentChild input data that represents your intended Attribute Hierarchies. (Before building an Attribute Hierarchy, the first stage of this process is to build a Main Hierarchy.)

Consider the Attribute Hierarchy for Responsibility Centers shown below:

If you are using flat files to build the structure, the ParentChild CSV file that you need to construct to obtain this structure is shown below:


Responsibility Centers Responsibility Center Attributes

Overseas Groups 15 OR

Responsibility Centers Overseas Groups France 15

Responsibility Centers Overseas Groups US 15

The Attribute Flags all have the value 15 which specifies all records as:

Parent is an Attribute Hierarchy GroupChild is an Attribute Hierarchy Group

The Attribute Flag value of 15 is a static value that is suitable for all records defined at this stage. Although Child Attributes are apparently defined as Groups, they will appear as children and only become groups if additional records specify them as Parents with a specific Child.

Consolidation Type applies to the Child item specified in the record and is only valid for Attribute Groups in a model. As a result, Consolidation Type has been left blank for the leaf items in our example. The first record is only included to demonstrate how to set the Consolidation Type of an Attribute Group. In fact, the Consolidation Symbol shown here is the default for Attribute Groups and the record could have been omitted, but it also demonstrates how to define an Attribute Group under the root item of the Attribute Hierarchy. This is shown in the Parent Field as Responsibility Center Attributes. The other Dimension Attribute Hierarchies have root items that are named in the same manner, for example, Activities has Activity Attributes and Periods has Period Attributes.

NoteIf the first record was omitted, the Attribute Group would be created automatically by the record that follows it.


You should check your results after this stage to ensure that you have produced the structure you wanted, as this gives the opportunity to recover from errors in your data with the minimum disruption.

NoteThe Parent and Child names used in the input data records are defined across all Data Aliases defined in your model.

After building an Attribute Hierarchy, the third stage of the process for building structures is to build Attribute Assignments.

7.1.1.3 Building Attribute Assignments

This is the third and final stage of the recommended process for building dimension structures in a model and is solely concerned with defining the Attributes possessed by the Dimension Items in your model.

The main task you have to perform is to create the ParentChild input data that represents your intended Attribute Assignments. Before building Attribute Assignments, the first two stages of this process are to build a Main Hierarchy and an Attribute Hierarchy.

Consider developing further the Main and Attribute Hierarchies for Responsibility Centers that were created by the first two stages of this process into the form shown below:

If you are using a flat file to build the structure, the ParentChild CSV file that you need to construct to produce this structure is shown below:


Responsibility Centers France Responsibility Center One

12

Responsibility Centers US Responsibility Center Two

12

The Attribute Flags can all have the value 12 which specifies all records as:

Parent is an Attribute ParentChild is a Main Hierarchy item

This Attribute Flag value is a static value that is suitable for all records defined at this stage.



NoteThe Child field must specify an item and not a group. This is because Attributes cannot have Group items as children; only leaf items.

Consolidation Type applies to the Child item specified in the record and is only valid for Attribute Groups in a model. As a result, Consolidation Type has been left blank for the child items in our example.

NoteThe Parent and Child names used in the input data records can be any Data Alias names in your model.

You will now have completed the process for constructing your dimension hierarchies. You could have chosen to build all dimensions at once or alternatively could have built them individually. You should have checked your results at each stage to ensure you have produced the structure you wanted, because this gives the opportunity to recover from errors in your data with the minimum disruption.

7.1.2 The ParentChild Table

his table defines the hierarchical structure of all the dimension items in a model.

It holds the following fields:

● DimensionName – The name of a dimension as defined in your application in the Dimensions sidebar.● ParentName – The Default Alias name of an item● ChildName – The Default Alias name of an item● Attribute Flags● Consolidation Types

Related Information

Attribute Flags [page 239]Consolidation Types [page 240]

7.1.2.1 Attribute Flags

To understand the role of Attribute Flags you should consider the example below, which shows a Responsibility Centers dimension containing a Main Hierarchy and Attribute Hierarchy with simple structures. More detail on these structures can be found in the Profitability and Cost Management Modeling User Guide.


The Main Hierarchy contains one Group (or parent) and three leaf items (or children). The Attribute Hierarchy contains one Group Attribute that has two Attribute items each referencing a leaf item in the Main Hierarchy.

Attribute Flags define the relationship between a hierarchy item and its immediate parent in either the Main or Attribute Hierarchy structure. They are binary coded numbers that represent the different types of relationship in the following manner:

● 1 - Child is an Attribute—when not set, Child belongs to Main Hierarchy● 2 - Child is a Parent (subgroup)—when not set, Child is a leaf item● 4 - Parent is an Attribute—when not set Parent, belongs to Main Hierarchy● 8 - Parent is a Parent (Always true)

When you map the attribute flags in the Field Mappings screen of the Data Bridge Specification Wizard, the following options are available:

10 (Main Hierarchy) 12 (Attribute Assignment) 15 (Attribute Hierarchy only)

The numbers 10, 12, and 15 represent the sum of the binary coded attribute flags described above. So, for example, when you select a value of 12 (Attribute Assignment), you are specifying that the Parent is an Attribute (4) and that the Parent is a Parent (8) and 4 + 8 = 12.

Related Information

Building an Attribute Hierarchy [page 237]

7.1.2.2 Consolidation Types

Consolidation Types are identifiers that indicate how the value of an item should contribute to its group total. Each Consolidation Type has its own symbol or icon that is used to represent its set state.

Consolidation operates differently in the Main Hierarchy and Attribute Hierarchy and these differences are identified below:



Main Hierarchies

Add Add the value of this item to the group total.

Subtract Subtract the value of this item from the group total.

Don’t Consolidate Exclude this value from the group total.

Attribute Hierarchies

All Sum all values for all items in all sub groups.

Common Sum values for items that appear in all sub groups

Don’t Consolidate Do not sum any values that appear in sub groups.

When viewing an XML file, the Consolidation Types for Attributes will appear as follows:

Consolidation Type Consolidation Symbol

All OR

Common AND

Don’t Consolidate ~


Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related LanguageWe try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.


Important Disclaimers and Legal Information

SAP BusinessObjects Profitability and Cost Management Database Administrator's GuideImportant Disclaimers and Legal Information P U B L I C 243

www.sap.com/contactsap

© 2019 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN

https://www.sap.com/about/legal/trademark.html

SAP BusinessObjects Profitability and Cost Management ... · 5. Check that all prerequisites...

Documents

Transcript of SAP BusinessObjects Profitability and Cost Management ... · 5. Check that all prerequisites...