Pcm 10 Database En

SAP BusinessObjects Profitability and Cost Management DatabaseAdministrator's Guide■ SAP BusinessObjects Profitability and Cost Management 10.0

2013-07-29

© 2013 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may bereproduced or transmitted in any form or for any purpose without the express permission of SAP AG.

Copyright

The information contained herein may be changed without prior notice. Some software productsmarketed by SAP AG and its distributors contain proprietary software components of other softwarevendors. National product specifications may vary. These materials are provided by SAP AG and itsaffiliated companies ("SAP Group") for informational purposes only, without representation or warrantyof any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials.The only warranties for SAP Group products and services are those that are set forth in the expresswarranty statements accompanying such products and services, if any. Nothing herein should beconstrued as constituting an additional warranty. SAP and other SAP products and services mentionedherein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and other countries. Please seehttp://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademarkinformation and notices.

2013-07-29

Contents

History of Changes.................................................................................................................5Chapter 1

About this Guide.....................................................................................................................9Chapter 2

Preparation............................................................................................................................11Chapter 3

Supported Software Versions................................................................................................113.1Important Restriction..............................................................................................................113.2Installation Script Location.....................................................................................................123.3Pre-Installation Tasks.............................................................................................................123.4Microsoft SQL Server Pre-Installation Tasks..........................................................................123.4.1Oracle Pre-Installation Tasks..................................................................................................133.4.2

Installation.............................................................................................................................15Chapter 4

Setting up a New Microsoft SQL Server Database Structure................................................154.1To create the EPOACCESS role for Microsoft SQL Server...................................................164.1.1Setting up a New Oracle Database Structure.........................................................................174.2

Data Loader...........................................................................................................................19Chapter 5

Preparation............................................................................................................................195.1Generating a Load Identifier...................................................................................................195.1.1Running Data Loader Remotely..............................................................................................205.1.2Data Loader Procedures and Packages..................................................................................205.2Data Loader Parameters........................................................................................................215.2.1Structural Procedures and Packages......................................................................................295.2.2Value Procedures and Packages............................................................................................375.2.3Performing a Data Load.........................................................................................................405.3Execute Data Loader Routines Procedure..............................................................................425.3.1Transforming Data from an Existing Model.............................................................................435.3.2Refreshing the Model.............................................................................................................435.3.3Follow-up Activities................................................................................................................445.4Data Loader Completion Checks...........................................................................................445.4.1

2013-07-293

Stage Table Management......................................................................................................455.4.2Troubleshooting Data Loader.................................................................................................465.5Data Loader Activity Logging.................................................................................................475.5.1Loadstatus Field Values and Constant Names.......................................................................475.5.2Data Loader Error Codes ......................................................................................................545.5.3

Maintenance.........................................................................................................................55Chapter 6

Restoring the Database.........................................................................................................556.1Data Files and Disk Space.....................................................................................................566.2Autogrow Setting...................................................................................................................566.2.1Rebuilding Database Indexes and Statistics...........................................................................566.3Microsoft SQL Server Data Compression..............................................................................606.4Data Loader Parallel Processing Scripts.................................................................................616.5Log Tables.............................................................................................................................626.6

Database Tables....................................................................................................................63Chapter 7

About Data Loader Tables......................................................................................................647.1Management Tables...............................................................................................................667.1.1Structural Tables....................................................................................................................687.1.2Value Tables..........................................................................................................................847.1.3About Results Tables...........................................................................................................1227.2Results Tables.....................................................................................................................1237.2.1Dimension Tables.................................................................................................................1857.2.2Results Views......................................................................................................................1877.2.3Exporting Results.................................................................................................................1887.2.4About Audit Tables...............................................................................................................1887.3Framework Audit Tables.......................................................................................................1897.3.1Assignment Audit Tables......................................................................................................2147.3.2Value Audit Tables...............................................................................................................2287.3.3

More Information.................................................................................................................291Appendix A

Index 293

2013-07-294

Contents

History of Changes

The SAP BusinessObjects Profitability and Cost Management Database Administrator's Guide isregularly updated on the SAP Help Portal (see More Information). Make sure that you have the latestversion of this document by checking the SAP Help Portal.

The current version of this document is version 1.4. The following table provides an overview of themost important changes to prior and current versions of this document:

2013-07-295

History of Changes

Important ChangesDateVersion

Initial version of the SAP BusinessObjects Profitability and CostManagement Database Administrator's Guide document for SAPBusinessObjects Profitability and Cost Management 10.0. (Previousversions of this guide are held in two separate documents entitled;SAP BusinessObjects Profitability and Cost Management DatabaseGuide for Oracle and SAP BusinessObjects Profitability and CostManagement Database Guide for Microsoft SQL Server.

The main changes to the document are detailed in the following list:• Schema and installation information about both Oracle and Mi-

crosoft SQL Server database systems can be found in this onedocument.

• All database tables listed in this document are listed withgeneric field types to encompass all supported relationaldatabase management systems (RDBMS).

• Additional Data Loader, results, audit related assignments, andBill Of Materials tables are listed in this document.

• Database upgrade instructions are located in the SAP Busines-sObjects Profitability and Cost Management Upgrade Guide.

• Details of the database software versions that we support arenow included with all system requirements in the SAP Busines-sObjects Profitability and Cost Management Master Guide.

May-10-2011Version 1.0

As part of the updated Profitability and Cost Management versionreleased in August 2011, the document contains the followingamendments or additions:• Additional text to step 5 of the “Dimension Data Load” procedure

to convey that attribute mappings are removed regardless of theloadstatus value.

• The procedure for restoring the database has been amended.The step to manually delete temporary model results has beenremoved. This step is not neccessary after running theEPO_RESET_SESSIONS procedure on a restored database.

• There are three additional results tables are designed to workin conjunction with universe files for reporting query and analysis.The additional tables are:• PPR_#DIMENSION_NAME#_BRIDGE• PPR_#DIMENSION_NAME#_NODEITEMS• PPR_NODE_LEVEL

Restriction:The functionality to report on Profitability and Cost Managementhierarchical data by using these tables is currently not availablein the software.

• The names for a number of views have been shortened; theseare now listed in the “Results Views” topic.

August-2011Version 1.1

2013-07-296

History of Changes

Important ChangesDateVersion

Version 1.2 As part of the release for Support Package 03, the document con-tains the following updates:• New topics are added to support the changing of settings for ta-

blespace and “autogrow”, and to specify database areas thatmust not be changed:• “Important Restriction”• ““Autogrow” Setting”

• Detailed information is provided on how to create the EPOAC-CESS role if you are using SSPI and a Windows user accountinstead of a Microsoft SQL Server login:• In topic “Setting up a New Microsoft SQL Server Database

Structure, Step 8 is amended.”• A new topic is added: “To create the EPOACCESS role for Mi-

crosoft SQL Server”.

May-2012

As part of the release for Support Package 04, the document con-tains the following update:• Errors are corrected in topic “PPR_HVACTIVITYDRIVERMAP-

PING”.

August 2012Version 1.3

As part of the release for Support Package 07, the document con-tains the following new topic:• “Microsoft SQL Server Data Compression”.

July 2013Version 1.4

Related Topics• Dimension Data Load• Restoring the Database

2013-07-297

History of Changes

2013-07-298

History of Changes

About this Guide

This document is designed for experienced Database Administrators and Data Bridge users who arefamiliar 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 or Oracle 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 loadingtables. It includes details of the tables that are incorporated into Data Loader, the logic behind theprocedures and how to install and load them. It is preferable that you are at least familiar with thesoftware import and export tables, and that you have the appropriate Microsoft SQL skills to populatethe loading tables and to execute stored procedures. A description of the loading tables is providedalong with relevant field mappings to existing Data Bridge tables to enable database-literate DataBridge 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 withSAP 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 ofData Loader procedures for execution on both Microsoft SQL Server and Oracle database systems,and how to maintain your database environment with the help of procedural tasks and re-indexingscripts.

2013-07-299

About this Guide

2013-07-2910

About this Guide

Preparation

3.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 MasterGuide for which versions of the database software we currently support.

3.2 Important Restriction

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

Note:“Core tables” refers to all tables not listed in this document.

Users may not make changes to the following:• Microsoft SQL Server:

• Table views• Stored procedures• Functions

• Oracle:• Tables• Views• Packages• Procedures• Functions• Triggers• Sequences

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

2013-07-2911

Preparation

3.3 Installation Script Location

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

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

Script LocationDatabase System

\PCM_100_SQL\MSSchema.cmdMicrosoft SQL Server

\PCM_100_SQL\support\OracleCreateObjects.sql

\PCM_100_SQL\OracleSchema.cmd

Oracle

3.4 Pre-Installation Tasks

Before you start to install and manage the software, an understanding of the basic administration tasksis 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 Profitabilityand Cost Management database can be installed.

Note:Upgrading the database follows much of the same procedure as installing a new database. Upgradeinstructions can be found in the SAP BusinessObjects Profitability and Cost Management UpgradeGuide.

3.4.1 Microsoft SQL Server Pre-Installation Tasks

Perform the following tasks before the database schema is installed: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 MasterGuide).

2013-07-2912

Preparation

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.

3.4.2 Oracle Pre-Installation Tasks

Perform the following tasks before the database schema is installed: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.

3.4.2.1 Preparation of the Database Area

Using the Oracle "Database Configuration Assistant", create your Oracle database with the followingoptions:• 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 Managementdatabase 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 relevantroles and access rights.

3.4.2.1.1 Tablespace Setup and User Rights

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

2013-07-2913

Preparation

Creating the Tablespace and Users1. Login to SQLPlus as system user (system).2. To use the OracleCreateObjects.sql file, open it from the Filemenu. To create the tablespace

in another location, you must edit the path before running it, otherwise manually create the tablespaceby 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 holdsthe database.Example: Create TablespaceCREATE TABLESPACE EPO_DATA DATAFILE'D:\oracle\oradata\EPO\epo_data.DBF' SIZE 250M

EXTENT 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 EPOTablespace by entering the details below where adminepo is the user you wish to use as thedatabase administrator.Example: Create Administrator userCreate user adminepoidentified 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 Profitabilityand Cost Management services via SAP BusinessObjects Profitability and Cost ManagementConfigure to connect to the database.Example: Create restricted userCreate user usrepoidentified 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.

2013-07-2914

Preparation

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 runningthe appropriate command file.

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

4.1 Setting up a New Microsoft SQL Server Database Structure

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 thesoftware from the SAP Software Distribution Center on the SAP Service Marketplace at: http://service.sap.com/swdc. Instructions for downloading the software can be found in the following SAP Note:772755.

Configuring the initial database structure involves creating a new blank database, running the providedSQL script to create the software database schema, and assigning a role to the database user.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 thehard drive where you have read and write access.

5. Open a command prompt window: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. Forexample:cd\PCM_100_SQL

7. Run the SQL script batch files to set up the database structures. The MSSchema.cmd must be runwith the following parameters:

2013-07-2915

Installation

http://service.sap.com/swdc


https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=772755

<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 thespecified terms:MSSchema.cmd SERVER DATABASE ADMINUSER PASSWORD

Note:

Alternatively you can use Windows NT authentication in which case SSPI may be entered in placeof 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_SQLfolder 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, youcan create the EPOACCESS role to be the user role that is used to access the database duringconfiguration. To do this, follow the steps in “To create the EPOACCESS role for Microsoft SQLServer”.

4.1.1 To create the EPOACCESS role for Microsoft SQL Server

If you are using SSPI and a Windows user account instead of a Microsoft SQL Server login, you cancreate 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 tothe EPOACCESS role. Then you set the EPOACCESS role to be the user logon for PCM Services, and ifyou are using DCOM, also apply the EPOACCESS role to the DCOM “Identity” settings.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 selectNew Login.b. Enter the newly created Windows user in Login name, select the PCM database as the Default

database and click OK.c. InDatabases, navigate to the PCM database, and then Security >Users, and selectNewUser.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 EPOACCESSrole.

3. For each PCM service that is enabled, set the “Log On” parameter to the Windows user defined asthe 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.

2013-07-2916

Installation

4. For each PCM service listed in the DCOM setting, change the “Identity” to the Windows user definedas the SSPI Login for Microsoft SQL Server:

Note:Ignore 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.

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 uservia the EPOACCESS role.

4.2 Setting up a New Oracle Database Structure

Before you start, ensure that you have downloaded the correct version of the software from the SAPSoftware Distribution Center on the SAP Service Marketplace at: http://service.sap.com/swdc. Instructionsfor downloading the software can be found in the following SAP Note: 772755.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 placeof the parameters: OracleSchema epo adminepo password usrepo password

Tip:To configure the “Database Alias”, use the Net Manager utility on the server from where the scriptsare 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 whichcan be utilized via SQLPlus for script execution.

2013-07-2917

Installation


https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=772755

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

2013-07-2918

Installation

Data Loader

The Data Loader utility is designed for use by Database Administrators, and can be carried out directlyat 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 Topics• Refreshing the Model• Running Data Loader Remotely

5.1 Preparation

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

If you choose not to use the Refresh Model Data option, ensure that the models are completely closedbefore re-opening. When the models are opened after the load has completed, the application serverrefreshes the cache and displays the loaded data ready for continued modeling. All required logic isimplemented via procedures stored within Oracle packages or Microsoft SQL procedures.

The following tasks must be completed before data loading can start:1. Create a model in the Model Builder application.2. Generate a load identifier (ID).3. Populate the relevant PPLOAD_ tables with data.

5.1.1 Generating a Load Identifier

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

2013-07-2919

Data Loader

Oracle PackageMicrosoft SQL Server Procedure

pkgEPOProcs.initialise_fastloadPP_FASTLOADINIT

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

Example: Microsoft SQL Server: Generating a Load ID

EXEC PP_FASTLOADINIT@INAUDITUSERID,@INMODELID,@INLOADIDoutput;

Example: Oracle: Generating a Load ID

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

5.1.2 Running Data Loader Remotely

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

Restriction:This applies to Oracle database systems only. The distributed transactions function is not available orrequired for Microsoft SQL Server database systems.

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

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

Example: Running the Set_DistTranState function

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

5.2 Data Loader Procedures and Packages

2013-07-2920

Data Loader

The Data Loader procedures and packages are designed to load structural and value related data intothe 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 intothe tables.

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

Tip:Use the “Data Loader Parameters” reference section as a guide for which parameters can be used inconjunction with the procedures or packages.

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

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

Data Loader Loadstatus ValuesThe following table outlines the default Loadstatus values for all loading tables:

DescriptionLoadstatus

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

1

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

70

Related Topics• Data Loader Parameters• About Data Loader Tables

5.2.1 Data Loader Parameters

2013-07-2921

Data Loader

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

Table 5-1: Microsoft SQL Server and Oracle Parameters

DescriptionProcedure/Pack-age Type

Data Type

ParameterOracle

Mi-crosoftSQLServer

User identifier from the EPO_USERS table.AllNumberIntinAUDITUSERID

Load delta data: True / False. This is only appli-cable to staging tables that write delta valuesto base data tables.

ValueBooleanBitinLOADDELTA

Load Identifier from the PP_FASTLOAD table.AllNumberIntinLOADID

Load target data: True / False. This is only ap-plicable to staging tables that write target valuesto base data tables.

ValueBooleanBitinLOADTARGET

Model Identifier from the EPO_MODELS table.AllNumberIntinMODELID

2013-07-2922

Data Loader


Data Type

ParameterOracle

Mi-crosoftSQLServer

The parameter inREPLACE refers to loadingattribute hierarchy mappings. For dimensiontype procedures and packages:• 0 (False) = This is the default value. Ap-

pends new data items and overwrites anyexisting data in the model with the valuesfrom the load table without removing any.Non-matching data is left unchanged.

• 1 (True) = If values exist, all existing attributemapping data is replaced, by removing itand appending the new data into the model.

All Dimension

BooleanBitinREPLACEReplace data values for Version and Period:• 0 (False) = Add new data items and over-

write any existing data in the model with thevalues from the load table. Non-matchingdata is left unchanged.

• 1 (True) = If data already exists in the modelfor the same Version and Period as in theload table, the data values in the model forthis Version and Period combination are re-moved and replaced with the load table da-ta.

• Assignment• Value

2013-07-2923

Data Loader


Data Type

ParameterOracle

Mi-crosoftSQLServer

Generate statistical information (Oracle usesthe DBMS_STATS package). The executing usermust be a member of the sysadmin, dbcreator,db_owner roles. If inStats is set to true,statistics are generated for relevant tables be-fore and after execution.

Note:

The default setting for Microsoft SQL Server isto automatically generate statistics, and it isstrongly advised that you keep this setting, asit enables Microsoft SQL Server to consistentlygenerate updated, accurate statistics on theavailable data. The inSTATS parameter createsadditional statistics on the available data.

Statistics are automatically generated by Oracledata loading packages that are greater thanversion 10.2.0.2.

AllBooleanBitinSTATS

Sum data for corresponding values:• 0 (False) = Add new data items and over-

write any existing data in the model with thevalues from the load table. Non-matchingdata is left unchanged. Duplicate key itemsare marked as duplicates and not loaded.

• 1 (True) = If the load table contains duplicaterecords for a data value, then the values aresummed together with any values alreadyexisting in the model, and this new totalvalue is loaded into the model.

ValueBooleanBitinSUM

2013-07-2924

Data Loader

Table 5-2: Microsoft SQL Server and Oracle Parameters specific to Execute Data Loader Routines(PP_EXECUTEDLROUTINES) procedure

Description

Data Type

ParameterOracleMicrosoft SQL

Server

Replace data values for Version and Period:• 0 = (Default) Add new data items and overwrite

any existing data in the model with the values fromthe load table. Non-matching data is left un-changed.

• 1 = If data already exists in the model for the sameVersion and Period as in the load table, the datavalues in the model for this Version / Period com-bination are removed and replaced with the loadtable data.

• 2 = If data for this load table already exists in themodel, then the data values are all removed forall Versions and Periods, before the load tablevalues are inserted.

Tip:If an unprocessed record in the load table containsan invalid Version or Period, note that all the datavalues will be removed if the inERASE parameter isset to 1, without being replaced by anything. This canbe a useful technique if you simply wish to clear downthe model data for this load table.

NumberIntinERASE

Load delta data: True / False. This is only applicableto staging tables that write delta values to base datatables.

NumberIntinLOADDELTA

Load target data: True / False. This is only applicableto staging tables that write target values to base datatables.

NumberIntinLOADTARGET

2013-07-2925

Data Loader

Description

Data Type

ParameterOracleMicrosoft SQL

Server

For information relating to the values that are re-placed, please see the dimension procedure/packagedescription 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 theload table. Non-matching data is left unchanged.

• 1 (True) = If data already exists in the model forthe same Version and Period as in the load table,the data values in the model for this Version andPeriod combination are removed and replacedwith the load table data.

NumberIntinREPLACE

Sum data for corresponding values:• 0 (False) = Add new data items and overwrite any

existing data in the model with the values from theload table. Non-matching data is left unchanged.Duplicate key items are marked as duplicates andnot loaded.

• 1 (True) = If the load table contains duplicaterecords for a data value, then the values aresummed together with any values already existingin the model, and this new total value is loadedinto the model.

NumberIntinSUM

Output: 0 = successNumberIntOUTSUCCESS

Table 5-3: Parameters Dedicated to Oracle

DescriptionPackage TypeData TypeParameter

Refers to the loading attribute hierarchy mappingsand is designed to be used when inReplacehas been set to false.• 0 (False) = (default value) the package ap-

pends the new data as dictated by the valueof the inReplace parameter.

• 1 (True) = the package appends new data andupdates existing data where relevant.

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

Dimension, someAssignment, andsome value

BooleaninATTRIBUTEMERGE

2013-07-2926

Data Loader

DescriptionPackage TypeData TypeParameter

User name from the EPO_USERS table. This pa-rameter enables you to load the correspondingname rather than the identifier. Please refer to theexample at the end of this section for further de-tails.

ValueVarchar2inAUDITUSERNAME

This parameter refers to the deletion of anyproperty data from the model where the keys ofthe data in the staging tables match the keys ofan existing data record. The following values areallowed:• 0 (False) = This default value updates any

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

matching keys.

PropertyBooleaninDELETEMATCHINGKEYS

Note:The preferred method for removing data is to useload status 70.

Delete value data from the model (see additionalexample below for further information relating tothe 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 themodel are processed and the matching modeldata is deleted. All other non-zero records areprocessed and model values are appended orupdated accordingly.

ValueBooleaninDELETEZEROVALUES

Model name from the EPO_MODELS table. Thisparameter enables you to load the correspondingname rather than the identifier. Please refer to theexample at the end of this section for further de-tails.

ValueVarchar2inMODELNAME

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

2013-07-2927

Data Loader

Example: Microsoft SQL Server 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

Example: Oracle Value Package Header

Oracle value package headers can contain functions that enable you to load the corresponding namesrather than the identifiers (inMODELNAME and inAUDITUSERNAME). The code example belowshows 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 inMODELNAMEand inAUDITUSERNAME parameters:

FUNCTION Main( inMODELNAME IN VARCHAR2,inLOADID IN NUMBER,inAUDITUSERNAME IN VARCHAR2,inDELETEZEROVALUES IN BOOLEAN ,

inSTATS IN BOOLEAN )RETURN NUMBER;

Example: inDELETEZEROVALUES Parameter

The majority of the tables contain a single value populating a single destination table, or multiplevalues populating multiple tables. The value fields referenced are the fields analyzed during the dataload. The PPLOAD_REVENUE and PPLOAD_SERVICEFACTOR staging tables differ to this rule andhave 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 valuesneed to be set to zero and INDELETEZEROVALUES needs to be set to True. If both values areset 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. Forthe record to be removed from the model, the VALUE field needs to be set to zero andINDELETEZEROVALUES needs to be set to True. If all three values are set to zero andINDELETEZEROVALUES is set to False, the record in the staging table is ignored. Any othercombination of zero and non-zero values can be loaded if INDELETEZEROVALUES is set to False.

Note:The preferred method for removing data is to use load status 70.

2013-07-2928

Data Loader

5.2.2 Structural Procedures and Packages

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

5.2.2.1 Dimension Procedures and Packages

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

Writes to Physical TablesStaging TablesDimension Loading Proce-dures/PackagesRDBMS

• PP_#• PP_#_NAME• PP_AT_#• OM_#• OM_#_NAME• OM_AT_#

• PPLOAD_#_DH• OMLOAD_#_DH

• PP_#_DIMENSION_LOADMAIN

• OM_#_DIMENSION_LOADMAIN

Microsoft SQL Server

• pkgPP_#_DIMENSION

• pkgOM_#_DIMENSION

Oracle

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

Procedures/packages that are prefixed with PP:• ACTIVITY• ACTIVITYDRIVER• CAPACITYRULE• COSTOBJECT1• COSTOBJECT2• COSTOBJECT3• COSTOBJECT4• COSTOBJECT5• CURRENCY

2013-07-2929

Data Loader

• 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

Note:Please 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.

Example: Microsoft SQL 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_ACTIVITYphysical tables.

Example: Oracle Data Loading Flow

The pkgPP_ACTIVITY_DIMENSION package transforms data from the PPLOAD_ACTIVITY_DHstaging table and writes to the PP_ACTIVITY, PP_ACTIVITY_NAME and PP_AT_ACTIVITY physicaltables.

5.2.2.1.1 Dimension Data Load

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

2013-07-2930

Data Loader

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.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 Topics• Structural Tables

5.2.2.2 Alias Procedures and Packages

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

2013-07-2931

Data Loader

Writes to Physical TablesStaging TablesAlias Loading Proce-dures/PackagesRDBMS

• PP_#_NAME• OM_#_NAME

• PPLOAD_#_AL• OMLOAD_#_AL

• PP_#_ALIAS_LOADMAIN

• OM_#_ALIAS_LOADMAIN


• pkgPP_#_ALIAS• pkgOM_#_ALIASOracle

Use the alias names listed below to replace the # in the standard naming convention to obtain the fullname 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

2013-07-2932

Data Loader

Procedures/packages that are prefixed with OM:• BOUNDARY• ICON• METRIC• OBJECTIVE

Note:Please 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_ALstaging table and writes to the PP_ACTIVITY_NAME physical table.


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

5.2.2.2.1 Alias Data Load

When an alias load is started, and sub procedures or functions are executed, entries are written to thePPLOAD_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 onthe attribute flag setting.

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. 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.

2013-07-2933

Data Loader

5.2.2.3 Property Procedures and Packages

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

Property Physical TablesStaging TablesProperty Loading Proce-dures/PackagesRDBMS

• EPO_MODEL_PROPERTY

• EPO_MODEL_PROPERTY_VALUE

• EPOLOAD_PROPERTY• EPOLOAD_PROPER

TYITEM

• EPO_PROPERTY_LOADMAIN

• EPO_PROPERTYITEM_LOADMAIN


• pkgEPO_PROPERTY• pkgEPO_PROPER

TYITEMOracle

5.2.2.3.1 Property 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 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).

5.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.

2013-07-2934

Data Loader

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: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.

5.2.2.4 Assignment Procedures and Packages

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

Writes to Physical TablesStaging TablesAssignment Loading Pro-cedures/PackagesRDBMS

• PP_#• OM_#

• PPLOAD_#• OMLOAD_#

• PP_#_LOADMAIN• OM_#_LOADMAINMicrosoft SQL Server

• pkgPP_#• pkgOM_#Oracle

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

Note:Procedures/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 *

2013-07-2935

Data Loader

• RESPCENTERSERVICE *

The following two assignment procedures/packages write to multiple tables:• COSTOBJECTASSIGNMENT - writes to the following tables:

• PP_COSTOBJITEM• PP_COSTOBJECTASSIGNMENT

Restriction:Cost Object Drivers must be loaded before Cost Object Assignments. This means that data mustexist in the PP_COSTOBJECTDRIVER table before the Cost Object Assignments can be loadedinto the PP_COSTOBJECTASSIGNMENT table.

• COSTOBJECTDRIVER - writes to the following tables:• PP_COSTOBJITEM• PP_COSTOBJECTDRIVER• PP_HVCOSTOBJECTDRIVER (For Transactional Costing model types)

Procedures/packages that are prefixed with OM:• 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_ACTIVITYREASSIGNstaging table and writes to the PP_ACTIVITYREASSIGN physical table.

5.2.2.4.1 Assignment Data Load

In addition to the actual dimensions, model structure can also be defined by assignments. Due to thenature of assignments, there is a dependency on the pre-existence of a dimension structure. Thevalidation 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 andthe destination physical assignment table. However, there are two exceptions to this rule; these are theCost Object Driver (PP_COSTOBJECTDRIVER) and Cost Object Assignment (PP_COSTOBJECTASSIGN

2013-07-2936

Data Loader

MENT) tables. When these two types of assignments are loaded, drivers must be loaded beforeassignments.

All assignment procedures generally follow a similar format. Initially the model, load and user detailsare validated, and then each dimension that makes up the value key (and all other values), is checkedto 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 nextrecord in the staging table.

Pre-validation steps:1. Check that the supplied model identifier is valid2. 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.

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).

5.2.3 Value Procedures and Packages

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

Writes to Physical TablesStaging TablesValue Loading Proce-dures/PackagesRDBMS

• PP_#• OM_#

• PPLOAD_#• OMLOAD_#

• PP_#_LOADMAIN• OM_#_LOADMAINMicrosoft SQL Server

• pkgPP_#• pkgOM_#Oracle

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

Note:Procedures marked with one asterisk (*) DO NOT use the @INREPLACE parameter, and thoseprocedures marked with two asterisks (**) do not use either @INREPLACE or @INSUM parameters.

2013-07-2937

Data Loader

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 :

2013-07-2938

Data Loader

• BOUNDARYINFO **• EMPLOYEEB **• EMPLOYEEBOUNDARY• ICONVALUE **• METRICADJUSTMENT• METRICADJUSTTARGET• METRICBASEPOINT• METRICACTUAL• METRICTARGET• METRICBOUNDARY• METRICB **• OBJECTIVEADJUSTMENT• OBJECTIVEADJUSTTARGET• OBJECTIVEACTUAL• OBJECTIVEBOUNDARY• OBJECTIVEBASEPOINT• OBJECTIVETARGET• OBJECTIVEWEIGHTING• OBJECTIVEB **• OBJMETRICWEIGHTING

Example: Microsoft SQL Server: PP_ACTIVITYDRIVERVALUE_LOADMAIN

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

For example, the PP_ACTIVITYDRIVERVALUE_LOADMAIN procedure extracts its source data fromthe 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 intotables (2) and (3) as shown above in addition to the default table (1). The additional parameters usethe following naming convention @INLOAD#where the # refers to the type of data value. The parametermust be set to either one (true) or zero (false), depending on the data contained within the stagingtable.

The parameters for the PP_ACTIVITYDRIVERVALUE_LOADMAIN procedure are:@INAUDITUSERID INT@INMODELID INT@INLOADID INT@INACTIVITYDRIVERDELTA BIT@INACTIVITYDRIVERTARGET BIT@INSTATS BIT

2013-07-2939

Data Loader

Related Topics• Value Tables

5.2.3.1 Value Data Load

These are data only related procedures and generally, validation centers on ensuring that the suppliednames exist in the model being loaded. Cases exist where one loading table can supply more than onedatabase table. An example of this is the Line Item Value procedure, where one record can potentiallycreate 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 proceduresgenerally follow a similar format. Initially the model, load and user details are validated, and then eachdimension making up the value key is checked to ensure that the item exists in the relevant modeldimension. If an item is found that does not exist, the record will be flagged with the relevant loadstatuscode, and the procedure is moved on to the next record in the staging table.

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. 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).

5.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

2013-07-2940

Data Loader

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 runindividually. This can be run by executing the stored procedure or as a console command (for furtherinformation on console commands, refer to the SAP BusinessObjects Profitability and Cost ManagementConsole User Guide).

Example: Microsoft SQL Server Data Loader Script

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

-- Declare variables

DECLARE @INAUDITUSERID INT;DECLARE @INREPLACE BIT;DECLARE @INSTATS BIT;DECLARE @INPCLOADID INT;DECLARE @INLOADDELTA INT;DECLARE @INLOADTARGET INT;DECLARE @RETCODE INT;

-- Assign variable values

SET @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;

END;GO

Example: Oracle Data Loader Script

A sample script to load Cost Object dimension data and associated Activity Driver values:SET LINES 1000SET PAGES 1000

SPOOL D:\DATALOADER_ORACLE\RESULTS\P1RunLoadID.txt

SET SERVEROUTPUT ON

2013-07-2941

Data Loader

BEGINDBMS_OUTPUT.ENABLE (BUFFER_SIZE => 1000000);

END;/

DECLARE

-- Declare and assign variable values

INAUDITUSERID 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);RETCODE :=PKGPP_COSTOBJECT2_ALIAS.MAIN(INPCMODELID, INPCLOADID, INAUDITUSERID,INSTATS);

RETCODE := PKGPP_ACTIVITYDRIVERVALUE.MAIN(INPCMODELID, INPCLOADID, INAUDITUSERID,INDELETEZEROVALUES, INSTATS);

COMMIT;

END;/

SPOOL OUT

EXIT

5.3.1 Execute Data Loader Routines Procedure

For users setting up a large model, the “Execute Data Loader Routines” procedure automaticallyperforms the dimension, alias, property, assignment and value load procedures and packages in thecorrect 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.

2013-07-2942

Data Loader

Example:SET SERVEROUTPUT ONDECLARE

outID INT;BEGIN

PP_EXECUTEDLROUTINES (1,1,10001,0,0,0,1,outID);DBMS_OUTPUT.PUT_LINE(outID);

END;/

Related Topics• Data Loader Parameters

5.3.2 Transforming Data from an Existing Model

A Microsoft SQL procedure and an Oracle exposed function is available to enable you to build thestaging 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), aload ID and a User ID. Both methods for each database system are shown in the examples below:

Example: Microsoft SQL: 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

Example: Oracle: 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;

5.3.3 Refreshing the Model

2013-07-2943

Data Loader

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

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

Example: Microsoft SQL: EPO_REFRESHMODELDATA

EXEC EPO_REFRESHMODELDATA @INMODELID, @INLOADID;

Example: Oracle: EPO_REFRESHMODELDATA

pkgEPOProcs.refreshModelData (MODELID LOADID);

5.4 Follow-up Activities

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

5.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 codeis 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 ofa given record.

2. Model Alerts:a. Microsoft SQL Server:

When loading data, an additional set of procedures is provided to populate alerts in the applicationfor any records that failed validation. Each dimension and alias has a procedure calledPP_#_DIMENSION_WRITEALERTS or PP_#_ALIAS_WRITEALERTS and if used, it is called after

2013-07-2944

Data Loader

running the relevant dimension or alias load. All writealert procedures contain the followingparameter 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. Ifthe INCLEARLOADING parameter is set to zero (false), the records remain in the stagingtable.

• The OUTROWCOUNT parameter value is generated during the procedure processing andreturns the number of alerts produced during the load.

b. Oracle:

When loading data, an additional method is provided that populates alerts in the application forany records that failed validation. Each dimension and alias package contains a function calledWriteAlerts, 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 theinClearLoading parameter is set to False, the records remain in the staging table.

Related Topics• Loadstatus Field Values and Constant Names

5.4.2 Stage Table Management

An additional set of Microsoft SQL procedures and Oracle exposed functions are available for removingdata 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 loadcombination.

2013-07-2945

Data Loader

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

Example: Microsoft SQL: Clear and Delete Procedures and Parameters

The naming conventions for the Microsoft SQL procedures are listed below, where # refers to astructural 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@INLOADID INT@INDATE DATETIME

Example: Oracle: Clear and Delete functions

All packages include additional exposed methods for removing data from staging tables, and this maybe 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;

5.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.

2013-07-2946

Data Loader

• Table of Loadstatus field values and constant names - The Constant name is a variable in a DataLoader script. A Loadstatus value is passed into the constant for each record as it is processed, andthe 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.

5.5.1 Data Loader Activity Logging

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

Example: Microsoft SQL script

select id, description, dateentered from ppload_log

Example: Oracle script

COLUMN description FORMAT a30 wrap;select id,description, to_char(dateentered,'hh:mi:ss')from ppload_log

Related Topics• PPLOAD_LOG

5.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 stagingtable definitions, and the actual constant names.

Constant Names

Description

LOAD-STA-TUSFieldValue

OracleMicrosoft SQL Server

c_ls_unprocessedudfUNPROCESSEDRecord is unprocessed.1

c_ls_isepocode (bar anyname beginning with “EPO”)udfISEPOCODE

Name starts with “EPO” this is not al-lowed.2

2013-07-2947

Data Loader

Constant Names

Description



c_ls_duplicateudfDUPLICATEA duplicate key set has been found inthe load dataset.3

c_ls_aleadyexistudfALREADYEXISTSThe name already exists in one of thesoftware dimensions.4

c_ls_existinthisdimudfEXISTSINTHISDIMThe name exists in the dimension be-ing loading into.5

c_ls_invalid_attribute_flag

udfINVALIDATTRIBUTEFLAG

The attribute flag number supplied isinvalid.7

c_ls_duplicatekeyudfDUPLICATEKEYA duplicate key set has been found inthe load dataset.8

c_ls_processedudfPROCESSEDThe record has been processed.9

c_ls_version_nameudfVERSIONNAMENOTEXIST

The Version name does not exist(Values).10

c_ls_period_nameudfPERIODNAMENOTEXISTThe Period name does not exist (Val-ues).11

c_ls_respcenter_nameudfRESPCENTERNAMENOTEXIST

The Responsibility Center name doesnot exist (Values).12

c_ls_lineitem_nameudfLINEITEMNAMENOTEXIST

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

c_ls_activity_nameudfACTIVITYNAMENOTEXIST

The Activity name does not exist(Values).14

c_ls_costobject1_nameudfCOSTOBJECT1NAMENOTEXIST

The Costobject1 name does not exist(Values).15









2013-07-2948

Data Loader

Constant Names

Description



c_ls_revenuetype_nameudfREVENUETYPENAMENOTEXIST

The Revenue Type name does notexist (Values).20

c_ls_currency_nameudfCURRENCYNAMENOTEXIST

The Currency name does not exist(Values).21

c_ls_resourcedriver_name

udfRESOURCEDRIVERNAMENOTEXIST

The Resource driver name does notexist (Values).22

c_ls_activitydriver_name

udfACTIVITYDRIVERNAMENOTEXIST

The Activity Driver name does not ex-ist (Values).23

c_ls_service_nameudfSERVICENAMENOTEXIST

The Service name does not exist(Values).24

c_ls_spread_nameudfSPREADNAMENOTEXISTThe Spread name does not exist(Values).25

c_ls_worksheet1_nameudfWORKSHEET1NAMENOTEXIST

The Worksheet1 name does not exist(Values).26

c_ls_worksheet2_nameudfWORKSHEET2NAMENOTEXIST

The Worksheet2 name does not exist(Values).27

c_ls_capacityrule_name

udfCAPACITYRULENAMENOTEXIST

The Capacity name does not exist(Values).28

c_ls_userrule_nameudfUSERRULENAMENOTEXIST

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

c_ls_icon_nameudfICONNAMENOTEXISTThe Icon name does not exist (Val-ues).30

c_ls_boundary_nameudfBOUNDARYNAMENOTEXIST

The Boundary name does not exist(Values).31

c_ls_lineitemdetail_name

udfLINEITEMDETAILNAMENOTEXIST

The Line Item Detail name does notexist (Values).33

c_ls_objective_nameudfOBJECTIVENAMENOTEXIST

The Objective name does not exist(Values).35

c_ls_metric_nameudfMETRICNAMENOTEXISTThe Metric name does not exist (Val-ues).36

2013-07-2949

Data Loader

Constant Names

Description



c_ls_employee_nameudfEMPLOYEENAMENOTEXIST

The Employee name does not exist(Values).38

c_ls_dtcostobject1_name

udfDTCOSTOBJECT1NAMENOTEXIST

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













c_ls_property_name_not_exist

udfPROPERTYNAMENOTEXIST

The Property name does not exist(Properties).50

c_ls_dim_name_not_exist

udfDIMENSIONNAMENOTEXIST

The dimension name does not exist(Properties).51

c_ls_dim_item_name_not_exist

udfDIMENSIONITEMNAMENOTEXIST

The dimension item name does notexist (Properties).52

c_ls_default_alias_not_exist

udfDEFAULTALIASNOTEXIST

The default alias does not exist (Alias).53

c_ls_reserved_nameudfRESERVEDNAMEThe item name is a software reservedname.54

c_ls_attrib_parent_not_exist

udfATTRIBUTEPARENTNOTEXIST

The attribute mapping parent does notexist (attribute mappings).55

c_ls_attrib_child_not_exist

udfATTRIBUTECHILDNOTEXIST

The dimension item name does notexist (attribute mappings)56

c_ls_structure_not_allowed

udfSTRUCTURENOTALLOWED

The dimension does not allow hierar-chical structures (Currency andBoundary)

57

c_ls_invalid_consol_type

udfCONSOLTYPENOTEXISTThe consolidation type is not valid.59

2013-07-2950

Data Loader

Constant Names

Description



c_ls_version_period_locked

udfVERSIONPERIODLOCKED

The version/period combination hasbeen locked (Values).60

c_ls_component_nameudfComponentNameNOTEXIST

Component does not exist in themodel.61

c_ls_delete_matching_keys

udfUNDELETEMATCHINGKEYS

For flagging records to delete (Proper-ties).70

c_ls_measure_nameudfMEASURENAMENOTEXIST

The Measure name does not exist(Values).85

c_ls_DataNotAllowedAtGrDC01

udfDATANOTALLOWEDATGROUPDC01()

Data not allowed at Detail Cost object186













c_ls_DisallowZeroValue

udfDISALLOWZEROVALUE

Record containing a zero value cannotbe loaded. Not a valid action. Thisprimarily applies to the ExternalActivity Cost Object UnitRate table.

91

c_ls_NotHVactivityDriver

udfNOTHVACTIVITYDRIVER

The Transactional Costing detail vol-ume data cannot be loaded againstan Activity Driver that is not markedas a Transactional Costing ActivityDriver.

92

c_ls_BOMMakupCo1udfBOMMAKEUPCO1The Default Bill Of Materials MakeupCost Object 1 item must exist as a leaflevel item, not a group level item.

93

2013-07-2951

Data Loader

Constant Names

Description



c_ls_BOMMakupCompudfBOMMAKEUPCOMPThe Default Bill Of Materials Makeupcomponent item must exist as a leaflevel item, not a group level item.

94

c_ls_NotExistAsDefaultBOM

udfNOTEXISTASDEFAULTBOM

Any Version and Period based Bill OfMaterials Makeup must already existas a Default Bill Of Materials Makeup.

95

c_ls_AResourceDriver_Name

udfARESOURCEDRIVERNAMENOTEXIST

The Actual Resource Driver item doesnot exist in the model.110

c_ls_TargetRespCenter_Name

udfTARGETRESPCENTERNAMENOTEXIST

The Target Responsibility Center itemdoes not exist in the model.111

c_ls_TargetActivity_Name

udfTARGETACTIVITYNAMENOTEXIST

The Target Activity item does not existin the model.112

c_ls_LIType_InCorrectudfLINEITEMTYPENOTCORRECT

The Line Item type for Cost ObjectAssignments does not exist in themodel.

113

c_ls_CO1Type_InCorrect

udfCOSTOBJECTTYPENOTCORRECT

The Cost Object type for Assignmentsis not set correctly.114

c_ls_COASS_not_existudfCOSTOBJECTASSNOTEXIST

The Cost Object for Assignment doesnot exist.115

c_ls_LIASS_not_existudfLINEITEMACTIVITYASSNOTEXIST

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

c_ls_AD1Name_not_exist

udfACTIVITYDRIVER1NAMENOTEXIST

Activity Driver 1 does not exist in themodel for the current Cost ObjectDriver.

120




121




122




123

2013-07-2952

Data Loader

Constant Names

Description






124

c_ls_VOLRespcenter1_not_valid

udfVOLRESPCENTER1NAMEINCORRECT

The specified type for Volume Respon-sibility Center 1 is incorrect. (0 - All, 1- Parent, 2 - Current, 3007 - RCUnassigned)

125




126




127




128




129

c_ls_DrOr1_not_validudfDRIVERORDER1NAMENOTVALID

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









2013-07-2953

Data Loader

5.5.3 Data Loader Error Codes

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

Description

Error Code

OracleMicrosoft SQLServer

When calling a procedure/package, a model identifier has been suppliedthat is not valid.2000150001

When calling a procedure/package, a load identifier has been suppliedthat is not valid.2000250002

When calling a procedure/package, a user identifier has been passedthat is not valid.2000350003

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

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

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

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

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

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

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

The supplied version name (version_name) does not exist as a defaultalias.2011250112

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

The supplied version period table name (table_name) does not exist inthe lookup table.2011450114

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

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

Remove all set incorrectly.2011750117

Unsupported name (name).2011850118

2013-07-2954

Data Loader

Maintenance

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

The Database Administrator (DBA) is typically responsible for the maintenance of the databases andensuring 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, toensure a robust environment for your development project and migration to a production environment.

6.1 Restoring the Database

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

To restore the system from the backup files, perform the following steps: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 databaserestore procedures.

4. When the database is restored successfully, execute the EPO_RESET_SESSIONS stored procedureon the database server(s).This procedure does not require any additional parameters.The procedure deletes any records that may exist in the EPO_SESSION_INFO table, effectivelyclosing 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 areproduced.

5. Inform the users that the system is available.

2013-07-2955

Maintenance

6.2 Data Files and Disk Space

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

Table fragmentation can be effectively managed through systematic rebuilding of the indexes andstatistics inherent within the database. Database file fragmentation however, requires file systemdefragmentation.

6.2.1 “Autogrow” Setting

The DBA is responsible for setting the initial size for a tablespace, and how much to autogrow a tableby. Your system may benefit from adjustments to the default “autogrow” setting.The following problemscould 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 localconditions.

6.3 Rebuilding Database Indexes and Statistics

All of the tables within the database are strategically indexed to maximize performance. These indexesneed 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 areregularly 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 youcan find several examples of rebuild scripts that can be applied to your environment.

Note:Autostatistical generation is set to “on” by default in a Microsoft SQL database. We recommend thatthis remains configured to the default setting.

2013-07-2956

Maintenance

Example: Microsoft SQL Server Rebuild Indexes Script

The following script is an example Microsoft SQL Server script that may be used for regular rebuildingof 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.

DECLARE @TableName sysnameDECLARE @indid intDECLARE cur_tblfetch CURSOR FOR

SELECT 'dbo.' + table_name FROM information_schema.tablesWHERE table_type = 'base table'OPEN cur_tblfetchFETCH NEXT FROM cur_tblfetch INTO @TableNameWHILE @@FETCH_STATUS = 0

BEGINDECLARE cur_indfetch CURSOR FOR

SELECT indid FROM sysindexesWHERE id = OBJECT_ID ( @TableName) and keycnt > 0OPEN cur_indfetchFETCH NEXT FROM cur_indfetch INTO @indidWHILE @@FETCH_STATUS = 0BEGIN

SELECT 'Defragmenting index_id = ' + convert(char(3),@indid) + 'of the ' + rtrim(@TableName) + 'table'

IF @indid <> 255 DBCC INDEXDEFRAG (0, @TableName, @indid)FETCH NEXT FROM cur_indfetch INTO @indidEND

CLOSE cur_indfetchDEALLOCATE cur_indfetchFETCH NEXT FROM cur_tblfetch INTO @TableName

ENDCLOSE cur_tblfetchDEALLOCATE cur_tblfetch

Example: Oracle Rebuild Indexes Script

This is an example re-index script that may be implemented on any system. The script needs to beexecuted 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 ON

COLUMN 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.OUTDECLARE

CURSOR CUR_INDEX_LIST ISSELECT OBJECT_NAME, CREATED, LAST_DDL_TIMEFROM USER_OBJECTSWHERE OBJECT_TYPE = 'INDEX'

2013-07-2957

Maintenance

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_LISTLOOP

DBMS_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';

EXECUTE IMMEDIATE(l_DDL_CMD);

SELECT LAST_DDL_TIMEINTO l_last_DDL_timeFROM 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 THENBEGIN

DBMS_OUTPUT.PUT_LINE(SQLCODE);DBMS_OUTPUT.PUT_LINE(SQLERRM);

END;

WHEN others THENBEGIN


END;END;/

SPOOL OUT

Example: Oracle Rebuild Statistics Script

The integrated DBMS_STATS package that is bundled with Oracle databases is a powerful series ofinternal measures that controls how well your Oracle database performs and provides statistics forthe entire database. Keeping the database statistics up to date is vital, especially before and after thedata loading process, as it assists in minimizing the load and calculate processes. If your data loadprocess is using Data Bridge, it is recommended that the database statistics are kept properlymaintained 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.

2013-07-2958

Maintenance

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 ONCOLUMN 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.OUT

DECLARECURSOR CUR_TAB_LIST IS

SELECT 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_LISTLOOP

DBMS_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')||' (lastanalyzed)');

DBMS_STATS.gather_table_stats( ownname =>'&&SCHEMA_OWNER',

tabname => REC_TAB_LIST.TABLE_NAME,estimate_percent => 30,cascade => TRUE

);SELECT last_analyzedINTO 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 THENBEGIN


END;WHEN others THENBEGIN


END;END;/

SPOOL OUT

2013-07-2959

Maintenance

6.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 byCPU overheads, depending on the architecture deployed in your installation. Below are variousconsiderations that should be taken into account, and you should also consult the Microsoftdocumentation 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.• 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.

2013-07-2960

Maintenance

• Tables with clustered indexes need only the indexes to be compressed as the clustered index iseffectively 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.

Example: Table 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)

Example: Index 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 Topics• Rebuilding Database Indexes and Statistics

6.5 Data Loader Parallel Processing Scripts

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

The scripts provided in the installation folder are as follows:• PCM_100_SQL\SUPPORT\MSSQLParallelQuery_ON.SQL

2013-07-2961

Maintenance

• PCM_100_SQL\SUPPORT\MSSQLParallelQuery_OFF.SQL

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

Example: MSSQLParallelQuery_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

Example: MSSQLParallelQuery_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

6.6 Log Tables

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

These tables need to be monitored regularly. If they become too large, they must be archived anddeleted. 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)

2013-07-2962

Maintenance

Database Tables

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

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

Table 7-1: Generic Field Type Definitions

Use this table to look up field types and sizes for a specific database system.

OracleMicrosoft SQL ServerGeneric Field Type

SizeField TypeSizeField Type

22Number4IntActivity Driver Identifier

22Number4IntAudit Identifier

1Char1CharChild Member Identifier

22Number4IntCombination Identifier

22Number4IntConsolidation Type Identifier

7Date8DatetimeDate

22Number(38,10)NumericDate Value

22Number4IntIdentifier

256Varchar2256NvarcharIndex Identifier

22Number4IntMember Identifier

256Varchar2256NvarcharMember Name

4000Clob16TextMemo

4000Clob16NtextNMemo

22Number4IntOrder Identifier

2013-07-2963

Database Tables

OracleMicrosoft SQL ServerGeneric Field Type

SizeField TypeSizeField Type

VariouslengthsVarchar2Various

lengthsNvarcharOther Text

22Number4IntStatus Value

22Number(38,10)NumericValue

Note:Most of the Microsoft SQL Server database tables contain an Ident field that is populated by MicrosoftSQL Server with an automatically generated unique identifier value. The same tables in an Oracledatabase do not contain this field, and therefore the Ident field is not documented in this guide.

7.1 About Data Loader Tables

Data Loading MethodsData 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, sofor identification purposes, some of the Data Loader tables contain identically named fields to thosecontained in Data Bridge tables. In this section, these fields are denoted by an asterisk (*) for informationonly.

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 fieldto 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 relevantfields listed in the table also have one of these numbers next to the field description to emphasize thatthe 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 TablesAll tables include a model identifier, that may be attained via the EPO_MODELS table. Model creationcan only be achieved by using the Model Builder application. In addition, most tables include a loadidentifier, which must also be unique. A load identifier is stored in the PP_FASTLOAD table and a newidentifier must be created using the fastload procedure functions.

2013-07-2964

Database Tables

Some types of Data Loader tables contain a LOADSTATUS field. This determines the status of the actualload record. All newly loaded records should be assigned a value of 1 (or 70 for property and valuetables), 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 successfullyprocessed. This field exists in the following tables:• All structural tables• All value tables

Example: EPO_MODELS Table

DescriptionAllow NullsTypeField Name

Unique ID number relating to themodel

NoIdentifierID (Key)

Refers to the type of model. Validoptions are:• 1 - Profitability and Costing

model• 4 - Objectives and Metrics model• 8 - Transactional Costing model• 16 - Bill of Materials model

NoIdentifierMODELTYPE

Name of modelYesMemberName

MODELNAME

Memo text for the modelYesOther TextMEMO

Next available EPO code for modelNoIdentifierNEXTUNIQUEID

Not currently usedNoStatus Val-ue

MODELSYNC

Current status of model. Valid op-tions are:• 0 - model disabled• 1 - model enabled

YesStatus Val-ue

MODELSTATUS

User ID of last user to amend modelNoIdentifierAUDITUSERID

Date of last amendment to modelNoDateDATEALTERED

Related Topics• PPLOAD_ACTIVITYDRIVERVALUE Activity Driver Value

2013-07-2965

Database Tables

7.1.1 Management Tables

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

7.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:


ID number for the modelNoIdentifierMODELID

ID number for the loadNoIdentifierLOADID

ID number for the configurationNoIdentifierCONFIGID

Value of the configuration IDNoIdentifierVALUE

7.1.1.2 EPO_ERRORLOG

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


2013-07-2966

Database Tables



Error codeNoIdentifierERRCODE

Error messageNoOther TextERRMSG

DescriptionNoOther TextDESCRIPTION

Date createdNoDateCREATED_ON

User ID of last user to amend recordNoIdentifierAUDITUSERID

7.1.1.3 PPHV_LOG

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




ID log number for the rowNoIdentifierID


Date enteredNoDateDATEENTERED

7.1.1.4 PPLOAD_LOG

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

The structure is defined in the table below:

2013-07-2967

Database Tables




ID log number for the rowNoIdentifierID


Date enteredNoDateDATEENTERED

7.1.2 Structural Tables

The loading procedures can load four types of structural data; dimension, alias, property andassignments. The parent child data and alias data each reside in their own table(s) for every singledimension 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

2013-07-2968

Database Tables

• WORKSHEET1• WORKSHEET2• 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.

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

7.1.2.1 PPLOAD_#_DH

Table: PPLOAD_#_DH

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

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

DescriptionAllows NullsTypeField Name



Default Alias name of itemNoMemberName

PARENTNAME*

Default Alias name of itemNoMemberName

CHILDNAME*

2013-07-2969

Database Tables

DescriptionAllows NullsTypeField Name

CHILDSORT parameter - this deter-mines the order in which dimension-al items appear within a grouping ina hierarchy.

NoIdentifierCHILDSORT

Attribute flag - this determines thetype of dimensional item that is be-ing loaded. Valid values are:• 10 - Create a main hierarchy• 12 - Define the attribute assign-

ments• 15 - Build an attribute hierarchyTo understand how to apply thesevalues correctly, read the section onbuilding hierarchies in the SAPBusinessObjects Profitability andCost Management Data Bridge UserGuide.

NoIdentifierATTRIBUTEFLAG*

Consolidation type - this is the typeof consolidation. Valid values include(~, +, -, OR, AND, NOR). To under-stand how to apply these valuescorrectly, read the section on build-ing hierarchies in the SAP Busines-sObjects Profitability and Cost Man-agement Data Bridge User Guide.

NoMemberName

CONSOLIDATIONTYPE*

Load status (Default 1)NoStatus ValueLOADSTATUS

For internal use only (Default 0) -This traps a special case where anitem appears only as a parent, andhence this is the root node. It isadded under the top level item in thisparticular scenario.

NoIdentifierISROOTNODE

(Default current date/time)YesDateDATESTAMP

7.1.2.2 PPLOAD_#_AL

Table: PPLOAD_#_AL

The purpose of these tables is to hold Alias data.

2013-07-2970

Database Tables

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




User defined Alias name. This is thename of the data alias, and by de-fault is stored in the EPO_DATA_ALIAS table.

NoMemberName

DATAALIASNAME*

Item name under Data Alias. This isthe actual name of the alias beingloaded, and validation occursagainst this item.

NoMemberName

ALIAS*

Default Alias name. This is the nameof the default alias, which is storedagainst a language id (LANGID) of0 in the schema. This is required toperform the lookup to return the ex-isting internal EPO code for the de-fault alias, so the new alias can bestored against the supplied dataalias name.

NoMemberName

DEFAULTALIAS*

Load status (Default 1)NoStatus ValueLOADSTATUS


7.1.2.3 EPOLOAD_PROPERTY

Table: EPOLOAD_PROPERTY

The purpose of this table is to hold Property data.

2013-07-2971

Database Tables




Name of the property itemNoOther TextNAME

Default property item valueNoOther TextDEFAULTVALUE

Load status (Default 1 or 70)NoStatus ValueLOADSTATUS


7.1.2.4 EPOLOAD_PROPERTYITEM

Table: EPOLOAD_PROPERTYITEM

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




Name of the property itemNoMemberName

NAME

Dimension typeNoMemberName

DIMENSION

Name of dimension itemNoMemberName

ITEMNAME

Property item valueNoOther TextVALUE



7.1.2.5 Assignment Tables

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

2013-07-2972

Database Tables

7.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




Name of the VersionNoMemberName

VERSIONNAME*

Name of the PeriodNoMemberName

PERIODNAME*

Name of the Responsibility CenterNoMemberName

RESPCENTERNAME*

Name of the ActivityNoMemberName

ACTIVITYNAME *

Name of the Resource DriverNoMemberName

RESOURCEDRIVERNAME*

Name of the Activity Allocation Driv-er

NoMemberName

ARESOURCEDRIVERNAME *

Name of the Target ResponsibilityCenter

NoMemberName

TARGETRESPCENTERNAME *

Name of the Target ActivityNoMemberName

TARGETACTIVITYNAME *



7.1.2.5.2 PPLOAD_ASSRESPCENTERACTIVITY Responsibility Centers Activities Assignment

Table: PPLOAD_ASSRESPCENTERACTIVITY

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

2013-07-2973

Database Tables





RESPCENTERNAME*


ACTIVITYNAME *



7.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

Restriction:Cost Object Drivers must be loaded before Cost Object Assignments. This means that data must existin the PP_COSTOBJECTDRIVER table before the Cost Object Assignments can be loaded into thePP_COSTOBJECTASSIGNMENT table.





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*

Name of the Line Item Activity orService (1)

NoMemberName

LINEITEMACTIVITYNAME *

Name of the Line Item, Activity, orService Type (1)

NoMemberName

LINEITEMACTIVITYTYPENAME*

Name of the Cost Object (Cost Ob-ject 1 - 5) (2)

NoMemberName

COSTOBJECTNAME *

2013-07-2974

Database Tables


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

NoMemberName

COSTOBJECTTYPENAME *



7.1.2.5.4 PPLOAD_COSTOBJECTDRIVER Cost Object Driver

Table: PPLOAD_COSTOBJECTDRIVER

This single load table is responsible for writing information to the following table:1. PP_COSTOBJITEM2. PP_COSTOBJECTDRIVER3. PP_HVCOSTOBJECTDRIVER

Restriction:Cost Object Drivers must be loaded before Cost Object Assignments. This means that data must existin the PP_COSTOBJECTDRIVER table before the Cost Object Assignments can be loaded into thePP_COSTOBJECTASSIGNMENT table.





VERSIONNAME


PERIODNAME


RESPCENTERNAME*

Name of the Line Item, Activity orService (1)

NoMemberName

LINEITEMACTIVITYNAME*

Line Items, Activities, or Services (1)NoMemberName

LINEITEMACTIVITYTYPENAME*

Name of the Activity Driver for CostObject 1 (2)

NoMemberName

ACTIVITYDRIVER1NAME*


NoMemberName



NoMemberName


2013-07-2975

Database Tables



NoMemberName



NoMemberName


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

NoActivity Driv-er Identifier

VOLUMERESPCENTER1TYPE*













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

NoOrder Identifi-er

ORDER1*


NoOrder Identifi-er

ORDER2*


NoOrder Identifi-er

ORDER3*


NoOrder Identifi-er

ORDER4*


NoOrder Identifi-er

ORDER5*

Name of the Transaction ActivityDriver (for Transactional Costingmodels only) (3)

YesMemberName

HVACTIVITYDRIVERNAME*



7.1.2.5.5 PPLOAD_LINEITEMDIRECT_ACTIVITY Line Item Direct Activity Overrides

Table: PPLOAD_LINEITEMDIRECT_ACTIVITY

2013-07-2976

Database Tables

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





VERSIONNAME *


PERIODNAME *


RESPCENTERNAME *

Name of the Line ItemNoMemberName

LINEITEMNAME *

Name of the ActivityYesMemberName

ACTIVITYNAME *



7.1.2.5.6 PPLOAD_LINEITEMRESOURCEDRIVER Resource Drivers Line Items Assignment

Table: PPLOAD_LINEITEMRESOURCEDRIVER

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





VERSIONNAME *


PERIODNAME *


RESPCENTERNAME*


LINEITEMNAME *

2013-07-2977

Database Tables


Name of the Line Item Activity TypeYesMemberName

RESOURCEDRIVERNAME *



7.1.2.5.7 PPLOAD_SERVICERESOURCEDRIVER Resource Drivers Services Assignment

Table: PPLOAD_SERVICERESOURCEDRIVER

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





VERSIONNAME *


PERIODNAME *


RESPCENTERNAME*

Name of the ServiceNoMemberName

SERVICENAME*

Name of the Resource DriverYesMemberName

RESOURCEDRIVERNAME*



7.1.2.5.8 PPLOAD_SERVICEDIRECT_ACTIVITY Direct Services Assignment Overrides

Table: PPLOAD_SERVICEDIRECT_ACTIVITY

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

2013-07-2978

Database Tables





VERSIONNAME *


PERIODNAME *


RESPCENTERNAME *


SERVICENAME *

Name of the Direct ActivityYesMemberName

ACTIVITYNAME *



7.1.2.5.9 PPLOAD_RESPCENTERSERVICE Services Responsibility Centers

Table: PPLOAD_RESPCENTERSERVICE

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





RESPCENTERNAME *


SERVICENAME *



7.1.2.5.10 OMLOAD_ASSMETRICEMPLOYEE Metric Employees Assignment

Table: OMLOAD_ASSMETRICEMPLOYEE

2013-07-2979

Database Tables

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




Name of the MetricNoMemberName

METRICNAME*

Name of the EmployeeNoMemberName

EMPLOYEENAME*



7.1.2.5.11 OMLOAD_ASSMETRICRESPCENTER Metric Responsibility Centers Assignment

Table: OMLOAD_ASSMETRICRESPCENTER

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





METRICNAME *


RESPCENTERNAME *



7.1.2.5.12 OMLOAD_ASSOBJECTIVEEMPLOYEE Objectives Employees Assignment

Table: OMLOAD_ASSOBJECTIVEEMPLOYEE

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

2013-07-2980

Database Tables




Name of the ObjectiveNoMemberName

OBJECTIVENAME *


EMPLOYEENAME *



7.1.2.5.13 OMLOAD_ASSOBJECTIVELOBJECTIVE Objectives Linked Objectives Assignment

Table: OMLOAD_ASSOBJECTIVELOBJECTIVE

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





OBJECTIVENAME*

Name of the Linked ObjectiveNoMemberName

LINKEDOBJECTIVENAME*



7.1.2.5.14 OMLOAD_ASSOBJECTIVEMETRIC Objectives Metrics Assignment

Table: OMLOAD_ASSOBJECTIVEMETRIC

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

2013-07-2981

Database Tables





OBJECTIVENAME*


METRICNAME*



7.1.2.5.15 OMLOAD_ASSOBJECTIVERESPCENTER Objectives Responsibility CentersAssignment

Table: OMLOAD_ASSOBJECTIVERESPCENTER

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





OBJECTIVENAME*


RESPCENTERNAME *



7.1.2.5.16 OMLOAD_OVRMETRICEMPLOYEE Metric Employees Assignment Override

Table: OMLOAD_OVRMETRICEMPLOYEE

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

2013-07-2982

Database Tables





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*


METRICNAME*

Name of Cost Object 1 (Object 1)NoMemberName

COSTOBJECT1NAME*


COSTOBJECT2NAME*


EMPLOYEENAME*



7.1.2.5.17 OMLOAD_OVROBJECTIVEEMPLOYEE Objectives Employees Assignment Override

Table: OMLOAD_OVROBJECTIVEEMPLOYEE

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





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*

2013-07-2983

Database Tables



OBJECTIVENAME*


COSTOBJECT1NAME*


COSTOBJECT2NAME*


EMPLOYEENAME*



7.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, forexample, the item does not already exist in the software schema, then the reason for the failure isrecorded in the LOADSTATUS field of the given record, and the record is not loaded into the model. Fora list of LOADSTATUS values, refer to the section on Exception Messages.

Note:Before being processed, records have a LOADSTATUS value of 1, and if successfully processed havea value of 9.

Related Topics• Data Loader Error Codes

7.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_ACTIVITYDRIVERDELTA

2013-07-2984

Database Tables

3. PP_ACTIVITYDRIVERTARGET

The load table structure is defined as follows:





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*

Name of the Activity DriverNoMemberName

ACTIVITYDRIVERNAME*

Name of Cost Object 1NoMemberName

COSTOBJECT1NAME*


COSTOBJECT2NAME*


COSTOBJECT3NAME*


COSTOBJECT4NAME*


COSTOBJECT5NAME*

Activity Driver value (1)YesValueVALUE*

Activity Driver delta value (2)YesValueDELTAVALUE*

Activity Driver target value (3)YesValueTARGETVALUE*



7.1.3.2 PPLOAD_BOMMAKEUP Bill of Materials Makeup

Table: PPLOAD_BOMMAKEUP

2013-07-2985

Database Tables

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





VERSIONNAME*


PERIODNAME*


COSTOBJECT1NAME*

Name of the product/sub-prod-uct/component that is the part

NoMemberName

COMPONENTNAME*

Name of a unit of measure itemNoMemberName

CURRENCYNAME*

The component makeup volume forthe product (Cost Object 1) (1)

YesValueVOLUME*



7.1.3.3 PPLOAD_BOMPRODUCTION Bill of Materials Production

Table: PPLOAD_BOMPRODUCTION

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





VERSIONNAME*


PERIODNAME*

2013-07-2986

Database Tables



COSTOBJECT1NAME*

Name of a Currency itemNoMemberName

CURRENCYNAME*

The component production volume(1)

YesValueVALUE*



7.1.3.4 PPLOAD_BOMUNITSSOLD Bill of Materials Units Sold

Table: PPLOAD_BOMUNITSSOLD

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





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*


COSTOBJECT1NAME*


COSTOBJECT2NAME*


COSTOBJECT3NAME*


COSTOBJECT4NAME*

2013-07-2987

Database Tables



COSTOBJECT5NAME*


CURRENCYNAME*

The product/sub-assembly units soldvalue (1)

YesValueVALUE*



7.1.3.5 PPLOAD_CURRENCYRATES Currency Rate

Table: PPLOAD_CURRENCYRATES

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





VERSIONNAME*


PERIODNAME*

Name of the Currency itemNoMemberName

CURRENCYNAME*

Currency rate (1)YesValueRATE*



7.1.3.6 PPLOAD_DEFAULTBOMMAKEUP Bill of Materials Default Makeup

2013-07-2988

Database Tables

Table: PPLOAD_DEFAULTBOMMAKEUP

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





COSTOBJECT1NAME*

Name of the product/sub-prod-uct/component that is the part

NoMemberName

COMPONENTNAME*


CURRENCYNAME*

The component makeup volume forthe product (Cost Object 1) (1)

YesValueVOLUME*



7.1.3.7 PPLOAD_EMPLOYEERDS Employee Resource Driver Split

Table: PPLOAD_EMPLOYEERDS

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





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*

2013-07-2989

Database Tables


Name of an EmployeeNoMemberName

EMPLOYEENAME*


RESOURCEDRIVERNAME*

Name of an ActivityNoMemberName

ACTIVITYNAME*

EmployeeResourceDriverSplit (1)NoValueVALUE*



7.1.3.8 PPLOAD_EXTERNALACTIVITYVALUE External Activity Value

Table: PPLOAD_EXTERNALACTIVITYVALUE

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






VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*

Name of an Activity DriverNoMemberName

ACTIVITYNAME*

Name of a Line ItemNoMemberName

LINEITEMNAME*


CURRENCYNAME*

2013-07-2990

Database Tables


External activity value (1)NoValueVALUE*

External fixed valueNoValueFIXEDVALUE*



7.1.3.9 PPLOAD_EXTERNALBOMUNITRATE Bill of Materials External Unit Rate

Table: PPLOAD_EXTERNALBOMUNITRATE

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





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*


LINEITEMNAME*


ACTIVITYNAME*


COSTOBJECT1NAME*


CURRENCYNAME*

2013-07-2991

Database Tables


Bill of Materials external unit ratevalue (1)

YesValueVALUE*



7.1.3.10 PPLOAD_EXTERNALCOSTOBJECTVALUE External Cost Object Value

Table: PPLOAD_EXTERNALCOSTOBJECTVALUE

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






VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*


ACTIVITYDRIVERNAME*


LINEITEMNAME*


COSTOBJECT1NAME*


COSTOBJECT2NAME*


COSTOBJECT3NAME*


COSTOBJECT4NAME*

2013-07-2992

Database Tables



COSTOBJECT5NAME*


CURRENCYNAME*

External Cost Object value (1)NoValueVALUE*

External fixed Cost Object value *NoValueFIXEDVALUE*



7.1.3.11 PPLOAD_HVACTIVITYDRIVERVOLUME Activity Driver Volume

Table: PPLOAD_HVACTIVITYDRIVERVOLUME

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






VERSIONNAME*


PERIODNAME*


RESPCENTERNAME

Name of Activity DriverNoMemberName

ACTIVITYDRIVERNAME*

Name of Detail Cost Object 1NoMemberName

DETAILCOSTOBJECT1NAME*



2013-07-2993

Database Tables








Activity Driver volume (1)YesValueVALUE*



7.1.3.12 PPLOAD_HVEXTACTCOUNITRATE External Activity Cost Object Unit Rate

Table: PPLOAD_HVEXTACTCOUNITRATE

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






VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*


ACTIVITYNAME*


ACTIVITYDRIVERNAME*


COSTOBJECT1NAME*

2013-07-2994

Database Tables



COSTOBJECT2NAME*


COSTOBJECT3NAME*


COSTOBJECT4NAME*


COSTOBJECT5NAME*

Unit Rate valueNoValueUNITRATE*

Fixed Unit Rate valueNoValueFIXEDUNITRATE*



7.1.3.13 PPLOAD_LINEITEMDETAILVALUE Line Item Detail Value

Table: PPLOAD_LINEITEMDETAILVALUE

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





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*

Name of a Line Item detailNoMemberName

LINEITEMDETAILNAME*


LINEITEMNAME*

2013-07-2995

Database Tables



CURRENCYNAME*

Line Item detail value (1)YesValueVALUE*



Note:The Data Bridge export table contains an additional field called LineItemdetailValueNC which isused internally to store values that are not currency specific.

7.1.3.14 PPLOAD_LINEITEMFIXEDVALUE Line Item Fixed Value

Table: PPLOAD_LINEITEMFIXEDVALUE

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

The load table is defined as follows:





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*


LINEITEMNAME*


CURRENCYNAME*

2013-07-2996

Database Tables


Fixed Line Item value (1)YesValueVALUE*



7.1.3.15 PPLOAD_LINEITEMVALUE Line Item Value Data

Table: PPLOAD_LINEITEMVALUE

This single load table is responsible for writing information to the following tables:1. PP_LINEITEMVALUE2. PP_LINEITEMDELTA






VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*


LINEITEMNAME*


CURRENCYNAME*

Line Item value (1)YesValueVALUE*

2013-07-2997

Database Tables


Line Item delta value (2)YesValueDELTAVALUE*



Note:Data Bridge export contains an additional field called LineItemCalculatedFixedValue which iscalculated internally and hence is not available for import.

7.1.3.16 PPLOAD_LINEITEMVARIABLE Line Item Variable

Table: PPLOAD_LINEITEMVARIABLE

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






VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*


LINEITEMNAME*

2013-07-2998

Database Tables


Line Item variability (1)YesValueVALUE*



7.1.3.17 PPLOAD_RESOURCEDRIVERSPLIT Resource Driver Split

Table: PPLOAD_RESOURCEDRIVERSPLIT

This single load table is responsible for writing information to the following tables:1. PP_RESOURCEDRIVERSPLIT2. PP_RESOURCEDRIVERDSPLIT3. PP_RESOURCEDRIVERTARSPLIT





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*


RESOURCEDRIVERNAME*


ACTIVITYNAME*

Resource Driver Split (1)YesValueSPLIT*

Resource Driver delta Split (2)YesValueDELTASPLIT*

2013-07-2999

Database Tables


Resource Driver target Split (3)YesValueTARGETSPLIT*



Note:The original Data Bridge table contains the percentage value ResourceDriverPctSplit that iscalculated, and as a result is not implemented.

7.1.3.18 PPLOAD_RESOURCEDRIVERVALUE Resource Driver Value

Table: PPLOAD_RESOURCEDRIVERVALUE

This single load table is responsible for writing information to the following tables:1. PP_RESOURCEDRIVERVALUE2. PP_RESOURCEDRIVERDELTA3. PP_RESOURCEDRIVERTARGET





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*


RESOURCEDRIVERNAME*

Resource Driver value (1)YesValueVALUE*

Resource Driver delta value (2)YesValueDELTAVALUE*

2013-07-29100

Database Tables


Resource Driver target value (3)YesValueTARGETVALUE*



7.1.3.19 PPLOAD_REVENUE Revenue

Table: PPLOAD_REVENUE

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





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*

Name of the Revenue TypeNoMemberName

REVENUETYPENAME*


COSTOBJECT1NAME*


COSTOBJECT2NAME*


COSTOBJECT3NAME*


COSTOBJECT4NAME*


COSTOBJECT5NAME*


CURRENCYNAME*

2013-07-29101

Database Tables


Unit Price value (1)YesValueUNITPRICE*

Units Sold value (1)YesValueUNITSSOLD*

Revenue (1)YesValueVALUE*



7.1.3.20 PPLOAD_SERVICEDRIVERVALUE Service Driver Value

Table: PPLOAD_SERVICEDRIVERVALUE

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

This single load table is responsible for writing information to the following tables:1. PP_SERVICEDRIVERVALUE2. PP_SERVICEDRIVERDELTA3. PP_SERVICEDRIVERTARGET





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*

Name of a ServiceNoMemberName

SERVICENAME*

Service Driver value (1)YesValueVALUE*

Service Driver delta value (2)YesValueDELTAVALUE*

2013-07-29102

Database Tables


Service Driver target value (3)YesValueTARGETVALUE*



7.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.

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





VERSIONNAME*


PERIODNAME*


SERVICENAME*


CURRENCYNAME*

Variable Service factor (1)YesValueVARIABLEFACTOR*

Fixed Unit Rate value (1)YesValueFIXEDUNITRATE*



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

2013-07-29103

Database Tables

7.1.3.22 PPLOAD_SPREADVALUE Spread Value

Table: PPLOAD_SPREADVALUE

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





VERSIONNAME*


PERIODNAME*

Name of the SpreadNoMemberName

SPREADNAME*

Spread value (1)YesValueVALUE*

Load status(Default 1 or 70)NoStatus ValueLOADSTATUS


7.1.3.23 PPLOAD_WORKSHEETVALUE Work Sheet Value

Table: PPLOAD_WORKSHEETVALUE

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

2013-07-29104

Database Tables





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*

Name of Work Sheet 1NoMemberName

WORKSHEET1NAME*

Name of Work Sheet 2NoMemberName

WORKSHEET2NAME*

Work Sheet value (1)YesValueVALUE*



7.1.3.24 OMLOAD_BOUNDARYINFO Boundary info

Table: OMLOAD_BOUNDARYINFO

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


ID number for thte modelNoIdentifierMODELID


Name of the Boundary Group (1)NoMemberName

GROUPBOUNDARYNAME*

Name of the BoundaryNoMemberName

BOUNDARYNAME*

Name of an IconNoMemberName

ICONNAME*

Range colorNoIdentifierRANGECOLOR*

2013-07-29105

Database Tables


Data colorNoIdentifierDATACOLOR*



7.1.3.25 OMLOAD_EMPLOYEEBOUNDARY Employee boundary

Table: OMLOAD_EMPLOYEEBOUNDARY

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





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*


EMPLOYEENAME*


COSTOBJECT1NAME*


COSTOBJECT2NAME*


COSTOBJECT3NAME


COSTOBJECT4NAME


COSTOBJECT5NAME


BOUNDARYNAME*

2013-07-29106

Database Tables


Name of a MeasureNoMemberName

MEASURENAME*

MetricBoundaryValue(1)NoValueVALUE*



7.1.3.26 OMLOAD_EMPLOYEEB Employee Boundary Measure

Table: OMLOAD_EMPLOYEEB

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





EMPLOYEENAME*


BOUNDARYNAME*

Name of a MeasureNoMemberName

MEASURENAME*



7.1.3.27 OMLOAD_ICONVALUE Icon Value

Table: OMLOAD_ICONVALUE

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

2013-07-29107

Database Tables


ID number for modelNoIdentifierMODELID

ID number for loadNoIdentifierLOADID

Name of an IconNoMemberName

ICONNAME

Property (1)YesOther TextCATEGORY

Icon value (encoded)YesNMemoVALUE



7.1.3.28 OMLOAD_METRICACTUAL Metric Actual Value

Table: OMLOAD_METRICACTUAL

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





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*


METRICNAME*


COSTOBJECT1NAME*


COSTOBJECT2NAME*


CURRENCYNAME*

2013-07-29108

Database Tables


Metric actual value (1)NoValueVALUE*



7.1.3.29 OMLOAD_METRICADJUSTMENT Metric Actual Adjustment Value

Table: OMLOAD_METRICADJUSTMENT

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





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*

Name of a MetricNoMemberName

METRICNAME*


COSTOBJECT1NAME*


COSTOBJECT2NAME*


CURRENCYNAME*

2013-07-29109

Database Tables


Metric actual adjustment value (1)NoValueVALUE*



7.1.3.30 OMLOAD_METRICADJUSTTARGET Metric Target Adjustment Value

Table: OMLOAD_METRICADJUSTTARGET

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





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*

Name of a MetricNoMemberName

METRICNAME*


COSTOBJECT1NAME*


COSTOBJECT2NAME*


CURRENCYNAME*

2013-07-29110

Database Tables


Metric Target adjustment value (1)NoValueVALUE*



7.1.3.31 OMLOAD_METRICB Metric Boundary Measure

Table: OMLOAD_METRICB

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





METRICNAME*


BOUNDARYNAME*

ID of table field e.g. MetricActualBoundaryValueID or MetricPercentBoundaryValueID

NoMemberName

MEASURENAME*



7.1.3.32 OMLOAD_METRICBASEPOINT Metric Base Point Value

Table: OMLOAD_METRICBASEPOINT

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

2013-07-29111

Database Tables





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*


METRICNAME*


COSTOBJECT1NAME*


COSTOBJECT2NAME*


CURRENCYNAME*

Metric basepoint value (1)NoValueVALUE*



7.1.3.33 OMLOAD_METRICBOUNDARY Metric Boundary Value

Table: OMLOAD_METRICBOUNDARY

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

2013-07-29112

Database Tables





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*


METRICNAME*


COSTOBJECT1NAME*


COSTOBJECT2NAME*


BOUNDARYNAME*

ID of table field e.g. MetricActualBoundaryValueID or MetricPercentBoundaryValueID

NoMemberName

MEASURENAME*

Value (1)NoValueVALUE*



7.1.3.34 OMLOAD_METRICTARGET Metric Target Value

Table: OMLOAD_METRICTARGET

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

2013-07-29113

Database Tables





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*


METRICNAME*


COSTOBJECT1NAME*


COSTOBJECT2NAME*


CURRENCYNAME*

Metric Target value (1)NoValueVALUE*



7.1.3.35 OMLOAD_OBJECTIVEACTUAL Objective Actual Value

Table: OMLOAD_OBJECTIVEACTUAL

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

2013-07-29114

Database Tables





VERSIONNAME*


PERIODNAME*

Name of the Responsibility CcenterNoMemberName

RESPCENTERNAME*


OBJECTIVENAME*


COSTOBJECT1NAME*


COSTOBJECT2NAME*

Objective actual value (1)NoValueVALUE*



7.1.3.36 OMLOAD_OBJECTIVEADJUSTMENT Object Actual Adjustment Value

Table: OMLOAD_OBJECTIVEADJUSTMENT

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





VERSIONNAME*


PERIODNAME*

2013-07-29115

Database Tables



RESPCENTERNAME*


OBJECTIVENAME*


COSTOBJECT1NAME*


COSTOBJECT2NAME*

Objective actual adjustment value(1)

NoValueVALUE*



7.1.3.37 OMLOAD_OBJECTIVEJUSTTARGET Objective Target Adjustment Value

Table: OMLOAD_OBJECTIVEADJUSTTARGET

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





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*


OBJECTIVENAME*


COSTOBJECT1NAME*

2013-07-29116

Database Tables



COSTOBJECT2NAME*

Objective Target adjustment value(1)

NoValueVALUE*



7.1.3.38 OMLOAD_OBJECTIVEB Objective Boundary Measure

Table: OMLOAD_OBJECTIVEB

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





OBJECTIVENAME*


BOUNDARYNAME*

ID of table field e.g. ObjectiveActualBoundaryValueID or ObjectivePercentBoundaryValueID

NoMemberName

MEASURENAME*



7.1.3.39 OMLOAD_OBJECTIVEBASEPOINT Objective Base Point Value

Table: OMLOAD_OBJECTIVEBASEPOINT

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

2013-07-29117

Database Tables

1. OM_OBJECTIVEBASEPOINT





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*


OBJECTIVENAME*


COSTOBJECT1NAME*


COSTOBJECT2NAME*

Objective basepoint value (1)NoValueVALUE*



7.1.3.40 OMLOAD_OBJECTIVEBOUNDARY Objective Boundary Value

Table: OMLOAD_OBJECTIVEBOUNDARY

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





VERSIONNAME*


PERIODNAME*

2013-07-29118

Database Tables



RESPCENTERNAME*


OBJECTIVENAME*


COSTOBJECT1NAME*


COSTOBJECT2NAME*


BOUNDARYNAME*

ID of table field e.g. ObjectiveActualBoundaryValueID or ObjectivePercentBoundaryValueID

NoMemberName

MEASURENAME*

Value (1)NoValueVALUE*



7.1.3.41 OMLOAD_OBJECTIVETARGET Objective Target Value

Table: OMLOAD_OBJECTIVETARGET

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





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*

2013-07-29119

Database Tables



OBJECTIVENAME*


COSTOBJECT1NAME*


COSTOBJECT2NAME*

Objective Target value (1)NoValueVALUE*

Load status (Default 1 or 70NoStatus ValueLOADSTATUS


7.1.3.42 OMLOAD_OBJECTIVEWEIGHTING Objective Weighting Value

Table: OMLOAD_OBJECTIVEWEIGHTING

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





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*


OBJECTIVENAME*

Name of the linked ObjectiveNoMemberName

LINKEDOBJECTIVE*


COSTOBJECT1NAME*


COSTOBJECT2NAME*

2013-07-29120

Database Tables


Objective weighting value (1)NoValueWEIGHTING*



7.1.3.43 OMLOAD_OBJMETRICWEIGHTING Objective Metric weighting value

Table: OMLOAD_OBJMETRICWEIGHTING

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





VERSIONNAME*


PERIODNAME*


RESPCENTERNAME*


OBJECTIVENAME*


METRICNAME*


COSTOBJECT1NAME*


COSTOBJECT2NAME*

2013-07-29121

Database Tables


Objective Metric weighting value (1)NoValueWEIGHTING*



7.2 About Results Tables

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

The layout details for dimension tables are referred to from within the results tables. The dimensiondata 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 theprefix PPR_, followed by the type of result the table holds. The Objectives and Metrics results tablesare prefixed by OMR_.

Example:

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

Note:The results tables are not indexed in a new installation or upgrade of version 10. If the\PCM_100_SQL\SUPPORT\Sample\MSSQLCreateResultIndexandPrimaryKeys.SQL script isrun to apply indexes and keys to the results tables, there may be a noticeable decrease in speed whenmodel 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 ViewsA set of views are also available to allow the default alias dimension item names to be viewed in theresults, rather than the EPO Codes.

Tip:If 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 LangID of the relevant dimension table, which in turn links in to the relevant results table.

Related Topics• Results Views

2013-07-29122

Database Tables

7.2.1 Results Tables

7.2.1.1 PPR_ACTCOSTOBJECTVALUE

Table: PPR_ACTCOSTOBJECTVALUE

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


ID number for the model (links toEPO_MODELS)

NoIdentifierMODELID

ID number for the export (links toEPO_USEREXPORTLOG)

NoIdentifierEXPORTID

ID number for the Version (links toPP_VERSION_NAME)

NoMemberIdentifier

VERSIONID

ID number for the Period (links toPP_PERIOD_NAME)

NoMemberIdentifier

PERIODID

ID number for an Activity (links toPP_ACTIVITY_NAME)

NoMemberIdentifier

ACTIVITYID

ID number for Cost Object 1 (linksto PP_COSTOBJECT1_NAME)

NoMemberIdentifier

COSTOBJECT1ID


NoMemberIdentifier

COSTOBJECT2ID


NoMemberIdentifier

COSTOBJECT3ID


NoMemberIdentifier

COSTOBJECT4ID


NoMemberIdentifier

COSTOBJECT5ID

2013-07-29123

Database Tables


Activity Cost Object valueNoValueVALUE

Fixed Activity Cost Object valueNoValueFIXEDVALUE

Variable activity cost object valueNoValueVARIABLEVALUE

7.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).



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID

ID number for the ResponsibilityCenter (links to PP_RESPCENTER_NAME)

NoMemberIdentifier

RESPCENTERID

ID Int for the Line Item (links toPP_LINEITEM_NAME)

NoMemberIdentifier

LINEITEMID

ID Int for the Activity (links toPP_ACTIVITY_NAME)

NoMemberIdentifier

ACTIVITYID

2013-07-29124

Database Tables


Activity Line Item valueNoValueVALUE

Fixed Activity Line Item valueNoValueFIXEDVALUE

Variable Activity Line Item valueNoValueVARIABLEVALUE

7.2.1.3 PPR_ACTIVITYVALUE

Table: PPR_ACTIVITYVALUE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID

ID number for the Line Item (links toPP_LINEITEM_NAME)

NoMemberIdentifier

LINEITEMID

ID number for the Activity (links toPP_ACTIVITY_NAME)

NoMemberIdentifier

ACTIVITYID

ID number for the Resource Driver(links to PP_RESOURCEDRIVER_NAME)

NoMemberIdentifier

RESOURCEDRIVERID

Activity valueNoValueVALUE

2013-07-29125

Database Tables


Fixed Activity valueNoValueFIXEDVALUE

Variable Activity valueNoValueVARIABLEVALUE

Activity Unit Rate valueNoValueUNITRATE

7.2.1.4 PPR_ACTREASSIGNSPLITVALUE

Table: PPR_ACTREASSIGNSPLITVALUE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

ACTIVITYID


NoMemberIdentifier

TARGETRESPCENTERID


NoMemberIdentifier

TARGETACTIVITYID

Activity reassignment split valueNoValueVALUE

2013-07-29126

Database Tables


Activity reassignment post valueNoValuePOSTVALUE

Activity reassignment in valueNoValueINVALUE

Activity reassignment out valueNoValueOUTVALUE

7.2.1.5 PPR_APRIMARYACTIVITYDRIVER

Table: PPR_APRIMARYACTIVITYDRIVER

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



NoIdentifierMODELID



ID number for the Version (links toPP_VERSIONNAME)

NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

LINEITEMID


NoMemberIdentifier

ACTIVITYID

2013-07-29127

Database Tables


ID number for the Activity Driver(links to PP_ACTIVITYDRIVER_NAME)

NoMemberIdentifier

ACTIVITYDRIVERID

Activity primary Activity Driver vol-ume

NoValueVOLUME

Activity primary Activity Driver unitrate

NoValueUNITRATE

7.2.1.6 PPR_BOMRESULT

Table: PPR_BOMRESULT

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

LINEITEMID


NoMemberIdentifier

ACTIVITYID

ID number of Cost Object 1NoMemberIdentifier

COSTOBJECT1ID

ID number of the Component for theProduct/Part

NoMemberIdentifier

COMPONENTID

2013-07-29128

Database Tables


The accumulated makeup volumeof a component in the product

NoValueCOMPONENTVOLUME

The unit rate value of the componentNoValueCOMPONENTUNITRATE

The fixed unit rate value of thecomponent

NoValueCOMPONENTFIXEDUNITRATE

The external unit rate value of thecomponent

NoValueCOMPONENTEXTERNALUNITRATE

The accumulated component unitrates of the product. This is calculat-ed as: PRODUCTUNITRATE = (COMPONENTUNITRATE +COMPONENTEXTERNALUNITRATE ) * COMPONENTVOLUME

NoValuePRODUCTUNITRATE

The accumulated component fixedunit rates of the product. This is cal-culated as: PRODUCTFIXEDUNITRATE = COMPONENTFIXEDUNITRATE * COMPONENTVOLUME

NoValuePRODUCTFIXEDUNITRATE

7.2.1.7 PPR_BOMUNITRATE

Table: PPR_BOMUNITRATE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID

2013-07-29129

Database Tables



NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

LINEITEMID


NoMemberIdentifier

ACTIVITYID


COSTOBJECT1ID

The calculated value of the Bill ofMaterials activity cost divided by theBill of Materials production volume.

NoValueVALUE

The calculated value of the Bill ofMaterials fixed activity cost dividedby the Bill of Materials productionvolume.

NoValueFIXEDVALUE

7.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 MaterialsMakeup volumes.



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID

2013-07-29130

Database Tables



COSTOBJECT1ID

ID number of the component for theproduct/part

NoMemberIdentifier

COMPONENTID

The component makeup volume forthe product (Cost Object 1)

NoValueVOLUME

7.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.



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID

ID number of Cost Object 1 (theproduct)

NoMemberIdentifier

COSTOBJECT1ID

The component production volumeNoValueVALUE

7.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.

2013-07-29131

Database Tables



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID

ID number for the Cost Object 1 (theproduct - links to PP_COSTOBJECT1_NAME)

NoMemberIdentifier

COSTOBJECT1ID


NoMemberIdentifier

COSTOBJECT2ID


NoMemberIdentifier

COSTOBJECT3ID


NoMemberIdentifier

COSTOBJECT4ID


NoMemberIdentifier

COSTOBJECT5ID

The product/sub-assembly units soldvalue

NoValueVALUE

7.2.1.11 PPR_CONTRIBUTION

Table: PPR_CONTRIBUTION

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

2013-07-29132

Database Tables



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

COSTOBJECT1ID


NoMemberIdentifier

COSTOBJECT2ID

ID numbr for Cost Object 3 (links toPP_COSTOBJECT3_NAME)

NoMemberIdentifier

COSTOBJECT3ID


NoMemberIdentifier

COSTOBJECT4ID


NoMemberIdentifier

COSTOBJECT5ID

Contribution valueNoValueCONTRIBUTION

7.2.1.12 PPR_COSTOBJECTVALUE

Table:PPR_COSTOBJECTVALUE

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

2013-07-29133

Database Tables



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

LINEIITEMID


NoMemberIdentifier

ACTIVITYID


NoMemberIdentifier

COSTOBJECT1ID


NoMemberIdentifier

COSTOBJECT2ID


NoMemberIdentifier

COSTOBJECT3ID


NoMemberIdentifier

COSTOBJECT4ID


NoMemberIdentifier

COSTOBJECT5ID

Cost Object valueNoValueVALUE

Fixed Cost Object valueNoValueFIXEDVALUE

Variable Cost Object valueNoValueVARIABLEVALUE

7.2.1.13 PPR_DCOSTOBJECTVALUE

Table: PPR_DCOSTOBJECTVALUE

2013-07-29134

Database Tables

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).



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

LINEITEMID


NoMemberIdentifier

COSTOBJECT1ID


NoMemberIdentifier

COSTOBJECT2ID


NoMemberIdentifier

COSTOBJECT3ID


NoMemberIdentifier

COSTOBJECT4ID


NoMemberIdentifier

COSTOBJECT5ID

Direct Cost Object valueNoValueVALUE

Fixed direct Cost Object valueNoValueFIXEDVALUE

Variable direct Cost Object valueNoValueVARIABLEVALUE

7.2.1.14 PPR_#DIMENSION_NAME#_BRIDGE

Table: PPR_#DIMENSION_NAME#_BRIDGE

2013-07-29135

Database Tables

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

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

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

Restriction:The functionality to report on SAP BusinessObjects Profitability and Cost Management hierarchicaldata by using this table is currently not available in the software.



NoIdentifierMODELID



ID number for the Dimension (linksto PP_DIMENSION_NAME)

NoMemberIdentifier

DIMENSIONID

ID number for hierarchies within adimension, including attribute hierar-chies.

Note:There must always be a main hierar-chy in a dimension and its DIMENSIONHIERARCHYID is always 0.

NoIdentifierDIMENSIONHIERARCHYID

Position of the dimension item in thehierarchy

NoIdentifierDIMENSIONLEVELID

Internal dimension item identifierNoIdentifierNODEID

Internal dimension identifier for theChild item

NoIdentifierCHILDNODEID

Name of the node itemNoMemberName

NODENAME

Child node nameNoMemberName

CHILDNODENAME

The NODEID leaf item in hierarchyNoIdentifierNODEISLEAF

2013-07-29136

Database Tables


The CHILDNODEID leaf item in hier-archy

NoIdentifierCHILDNODEISLEAF

Index to represent the position of thenode in the hierarchy

NoIndex Identifi-er

NODEINDEX

Child index to represent the positionof the node in the hierarchy

NoIndex Identifi-er

CHILDNODEINDEX

Original Dimension Level ID (SeeNote below)

NoIdentifierORIGINALDIMENSIONLEVELID

Determines original flattened dimen-sion item

NoStatus ValueISBALANCED

Note:In SAP BusinessObjects Profitability and Cost Management, dimensions in the Main and Attributehierarchies can contain multiple hierarchies that can be unbalanced or of varying depths. As part of theExport to Database function, the SAP BusinessObjects Profitability and Cost Management middle tieranalyses all the hierarchies contained within a given dimension for a particular export, to determinewhich is the deepest. All hierarchies are then vertically flattened to the maximum depth for reportingpurposes.

7.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 querythe results of hierarchical data contained within SAP BusinessObjects Profitability and Cost Managementdimensions for reporting and analysis.

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

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

Restriction:The functionality to report on SAP BusinessObjects Profitability and Cost Management hierarchicaldata by using this table is currently not available in the software.

2013-07-29137

Database Tables



NoIdentifierMODELID




NoMemberIdentifier

DIMENSIONID




Position of the dimension item in thehierarchy

NoIdentifierDIMENSIONlEVELID

Internal dimension item identifierNoIdentifierNODEID

Internal dimension identifier for theparent item

NoIdentifierPARENTNODEID

Name of the node itemNoMemberName

NODENAME

Parent node nameNoMemberName

PARENTNODENAME

The NODEID leaf item in hierarchyNoIdentifierNODEISLEAF

Index to represent the position of thenode in the hierarchy

NoIndex Identifi-er

NODEINDEX

Parent index to represent the posi-tion of the node in the hierarchy

NoIndex Identifi-er

PARENTNODEINDEX

Original Dimension Level ID (SeeNote below)

NoIdentifierORIGINALDIMENSIONLEVELID

Determines original flattened dimen-sion item

NoStatus ValueISBALANCED

Note:In SAP BusinessObjects Profitability and Cost Management, dimensions in the Main and Attributehierarchies can contain multiple hierarchies that can be unbalanced or of varying depths. As part of theExport to Database function, the SAP BusinessObjects Profitability and Cost Management middle tieranalyses all the hierarchies contained within a given dimension for a particular export, to determine

2013-07-29138

Database Tables

which is the deepest. All hierarchies are then vertically flattened to the maximum depth for reportingpurposes.

7.2.1.16 PPR_DPRIMARYACTIVITYDRIVER

Table: PPR_DPRIMARYACTIVITYDRIVER

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

LINEITEMID

ID number for the Activity (links toPP_ACTIVITYDRIVER_NAME)

NoMemberIdentifier

ACTIVITYDRIVERID

Direct primary Activity Driver volumeNoValueVOLUME

Direct primary Activity Driver unitrate

NoValueUNITRATE

7.2.1.17 PPR_DSERVICECOSTOBJECTVALUE

Table: PPR_DSERVICECOSTOBJECTVALUE

2013-07-29139

Database Tables

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID

ID number for the Service item (linksto PP_SERVICE_NAME)

NoMemberIdentifier

SERVICEID


NoMemberIdentifier

COSTOBJECT1ID


NoMemberIdentifier

COSTOBJECT2ID


NoMemberIdentifier

COSTOBJECT3ID


NoMemberIdentifier

COSTOBJECT4ID


NoMemberIdentifier

COSTOBJECT5ID

Direct Service Cost Object valueNoValueVALUE

7.2.1.18 PPR_DSPRIMARYACTIVITYDRIVER

Table: PPR_DSPRIMARYACTIVITYDRIVER

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

2013-07-29140

Database Tables



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

SERVICEID


NoMemberIdentifier

ACTIVITYDRIVERID

Direct Service primary Activity Drivervalue

NoValueVOLUME

Direct Service primary Activity Driverunit rate

NoValueUNITRATE

7.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.

2013-07-29141

Database Tables



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

ACTIVITYID


NoMemberIdentifier

LINEITEMID

ID number for a Currency item (linksto PP_CURRENCY_NAME)

NoMemberIdentifier

CURRENCYID

External Activity valueNoValueEXTERNALACTIVITYVALUE

Fixed external Activity valueNoValueEXTERNALACTIVITYFIXEDVALUE

7.2.1.20 PPR_EXTERNALCOSTOBJECTVALUE

Table: PPR_EXTERNALCOSTOBJECTVALUE

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

2013-07-29142

Database Tables



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

ACTIVITYID

ID number for Line Item (links toPP_LINEITEM_NAME)

NoMemberIdentifier

LINEITEMID


NoMemberIdentifier

COSTOBJECT1ID


NoMemberIdentifier

COSTOBJECT2ID


NoMemberIdentifier

COSTOBJECT3ID


NoMemberIdentifier

COSTOBJECT4ID


NoMemberIdentifier

COSTOBJECT5ID

External Cost Object valueNoValueEXTERNALCOSTOBJECTVALUE

Fixed external Cost Object valueNoValueEXTERNALCOSTOBJECTFIXEDVALUE

7.2.1.21 PPR_HVACTIVITYDRIVERMAPPING

Table: PPR_HVACTIVITYDRIVERMAPPING

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

2013-07-29143

Database Tables



NoIdentifierMODELID


NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID

ID number for the Activity driver(links to PP_ACTIVITYDRIVER_NAME)

NoMemberIdentifier

ACTIVITYDRIVERID

ID number for the Detail Cost Object1 (links to PP_DTCOSTOBJECT1ID)

NoMemberIdentifier

DETAILCOSTOBJECT1ID

ID number for Cost Object 2 (linksto PP_DTCOSTOBJECT2ID)

NoMemberIdentifier

DETAILCOSTOBJECT2ID


NoMemberIdentifier

DETAILCOSTOBJECT3ID


NoMemberIdentifier

DETAILCOSTOBJECT4ID


NoMemberIdentifier

DETAILCOSTOBJECT5ID


NoMemberIdentifier

COSTOBJECT1ID


NoMemberIdentifier

COSTOBJECT2ID


NoMemberIdentifier

COSTOBJECT3ID

2013-07-29144

Database Tables



NoMemberIdentifier

COSTOBJECT4ID


NoMemberIdentifier

COSTOBJECT5ID

Activity Driver volumeYesValueACTIVITYDRIVERVOLUME

7.2.1.22 PPR_HVBREAKDOWN

Table: PPR_HVBREAKDOWN

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



NoIdentifierMODELID


NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID

Links to the PPR_HVBREAKDOWNDETAILCOST table

NoIdentifierHVLOOKUPID


NoMemberIdentifier

RESPCENTERID

2013-07-29145

Database Tables


ID number for an Activity (links toPP_ACTIVITY_NAME)

NoMemberIdentifier

ACTIVITYID

Sum of the unit rateNoValueFACTOR

Sum of the fixed unit rateNoValueFIXEDFACTOR

7.2.1.23 PPR_HVBREAKDOWNDETAILCOST

Table: PPR_HVBREAKDOWNDETAILCOST

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



NoIdentifierMODELID


NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID

The Responsibility Center ID for thetransaction part of the cost

NoMemberIdentifier

TRANSACTIONALRESPCENTERID

Links to the PPR_HVBREAKDOWN ta-ble


ID number for Detailed Cost Object1 (links to PP_DETAILCOSTOBJECT1_NAME)

NoMemberIdentifier

DETAILCOSTOBJECT1ID


NoMemberIdentifier

DETAILCOSTOBJECT2ID


NoMemberIdentifier

DETAILCOSTOBJECT3ID

2013-07-29146

Database Tables



NoMemberIdentifier

DETAILCOSTOBJECT4ID


NoMemberIdentifier

DETAILCOSTOBJECT5ID

Sum of the original input volumemultiplied by the calculated unit ratefrom the PPR_HVUNITRATE table

NoValueVALUE

Sum of the original input volumemultiplied by the calculated fixed unitrate from the PPR_HVUNITRATE ta-ble

NoValueFIXEDVALUE

7.2.1.24 PPR_HVDETAILCOST

Table: PPR_HVDETAILCOST

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



NoIdentifierMODELID


NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID

The Responsibility Center ID for thetransaction part of the cost

NoMemberIdentifier

TRANSACTIONALRESPCENTERID


NoMemberIdentifier

ACTIVITYID

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

NoMemberIdentifier

DETAILCOSTOBJECT1ID

2013-07-29147

Database Tables



NoMemberIdentifier

DETAILCOSTOBJECT2ID


NoMemberIdentifier

DETAILCOSTOBJECT3ID


NoMemberIdentifier

DETAILCOSTOBJECT4ID


NoMemberIdentifier

DETAILCOSTOBJECT5ID

Detail cost valueNoValueVALUE

Detail cost fixed valueNoValueFIXEDVALUE

7.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 tocreate the detail costs.



NoIdentifierMODELID


NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

ACTIVITYID

ID number for the Activity (links toPP_LINEITEM_NAME)

NoMemberIdentifier

LINEITEMID

ID number for the Activity Driv-er(links to PP_ACTIVITYDRIVER_NAME)

NoMemberIdentifier

ACTIVITYDRIVERID

2013-07-29148

Database Tables



NoMemberIdentifier

COSTOBJECT1ID


NoMemberIdentifier

COSTOBJECT2ID


NoMemberIdentifier

COSTOBJECT3ID


NoMemberIdentifier

COSTOBJECT4ID


NoMemberIdentifier

COSTOBJECT5ID

Links to the PPR_HVBREAKDOWN andPPR_HVBREAKDOWNDETAILCOSTtables


Line item activity unit rate valueNoValueUNITRATE

Line item activity fixed unit rate valueYesValueFIXEDUNITRATE

7.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.



NoIdentifierMODELID


NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

ACTIVITYID

2013-07-29149

Database Tables


ID number for the Activity Driv-er(links to PP_ACTIVITYDRIVER_NAME)

NoMemberIdentifier

ACTIVITYDRIVERID


NoMemberIdentifier

COSTOBJECT1ID


NoMemberIdentifier

COSTOBJECT2ID


NoMemberIdentifier

COSTOBJECT3ID


NoMemberIdentifier

COSTOBJECT4ID


NoMemberIdentifier

COSTOBJECT5ID

Links to the PPR_HVBREAKDOWN andPPR_HVBREAKDOWNDETAILCOSTtables


Unit Rate valueNoValueUNITRATE

Fixed Unit Rate valueYesValueFIXEDUNITRATE

7.2.1.27 PPR_LICOSTOBJECTVALUE

Table: PPR_LICOSTOBJECTVALUE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID

2013-07-29150

Database Tables



NoMemberIdentifier

LINEITEMID


NoMemberIdentifier

COSTOBJECT1ID


NoMemberIdentifier

COSTOBJECT2ID


NoMemberIdentifier

COSTOBJECT3ID


NoMemberIdentifier

COSTOBJECT4ID


NoMemberIdentifier

COSTOBJECT5ID

Line Item Cost Object valueNoValueVALUE

Fixed Line Item Cost Object valueNoValueFIXEDVALUE

Variable Line Item Cost Object valueNoValueVARIABLEVALUE

7.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 querythe results of hierarchical data contained within Profitability and Cost Management dimensions forreporting and analysis. Reporting is achieved by using external reporting tools such as SAPBusinessObjects Web Intelligence to consume universe files. The table contains data about the numberof levels that are present in the hierarchy of a dimension, which can contain up to a maximum of threelevels.

Restriction:The functionality to report on Profitability and Cost Management hierarchical data by using this table iscurrently not available in the software (version 10.0 Support Package 01).

2013-07-29151

Database Tables



NoIdentifierMODELID




NoMemberIdentifier

DIMENSIONID




Position of the dimension item in thehierarchy.

NoIdentifierDIMENSIONLEVELID

Additional indicator of the positionof a dimension in a hierarchy, usedfor reporting purposes.

NoIdentifierLVL

Textual description of a dimensionlevel

NoLevel de-scription

DESCRIPTION

7.2.1.29 PPR_POSTREASSIGNLINEITEMVALUE

Table: PPR_POSTREASSIGNLINEITEMVALUE

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

2013-07-29152

Database Tables



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

LINEITEMID


NoMemberIdentifier

ACTIVITYID

Post re-assigned Activity Line Itemvalue

NoValueVALUE

Fixed component of the post re-as-signed Activity Line Item value

NoValueFIXEDVALUE

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

NoValueVARIABLEVALUE

7.2.1.30 PPR_RBACTIVITYDRIVERVALUE

Table: PPR_RBACTIVITYDRIVERVALUE

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

2013-07-29153

Database Tables



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

ACTIVITYDRIVERID


NoMemberIdentifier

COSTOBJECT1ID


NoMemberIdentifier

COSTOBJECT2ID


NoMemberIdentifier

COSTOBJECT3ID


NoMemberIdentifier

COSTOBJECT4ID


NoMemberIdentifier

COSTOBEJCT5ID

Activity Driver valueNoValueVALUE

7.2.1.31 PPR_RBCURRENCYRATES

Table: PPR_RBCURRENCYRATES

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

2013-07-29154

Database Tables



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID

ID number for a Currency item (linksto PP_CURRENCY_NAME)

NoMemberIdentifier

CURRENCYID

Currency rateNoValueRATE

7.2.1.32 PPR_RBEMPLOYEERDS

Table: PPR_RBEMPLOYEERDS

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID

ID number for the Employee (linksto PP_EMPLOYEE_NAME)

NoMemberIdentifier

EMPLOYEEID

2013-07-29155

Database Tables



NoMemberIdentifier

RESOURCEDRIVERID


NoMemberIdentifier

ACTIVITYID

Employee Resource Driver Splitvalue

NoValueVALUE

7.2.1.33 PPR_RBHVEXTACTCOUNITRATE

Table: PPR_RBHVEXTACTCOUNITRATE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

ACTIVITYID

ID number for Activity Driver (linksto PP_ACTIVITYDRIVER_NAME )

NoMemberIdentifier

ACTIVITYDRIVERID


NoMemberIdentifier

COSTOBJECT1ID


NoMemberIdentifier

COSTOBJECT2ID

2013-07-29156

Database Tables



NoMemberIdentifier

COSTOBJECT3ID


NoMemberIdentifier

COSTOBJECT4ID


NoMemberIdentifier

COSTOBJECT5ID

External Unit RateNoValueUNITRATE

Fixed Unit RateNoValueFIXEDUNITRATE

7.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.



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

LINEITEMID

2013-07-29157

Database Tables



NoMemberIdentifier

ACTIVITYID


COSTOBJECT1ID

The Bill of Materials external unitrate value

NoValueVALUE

7.2.1.35 PPR_RBLINEITEMDETAILVALUE

Table: PPR_RBLINEITEMDETAILVALUE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID

ID number for Period (links toPP_PERIOD_NAME)

NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID

2013-07-29158

Database Tables


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

NoMemberIdentifier

LINEITEMDETAILID


NoMemberIdentifier

LINEITEMID

Line Item Detail valueNoValueVALUE

7.2.1.36 PPR_RBLINEITEMFIXEDVALUE

Table: PPR_RBLINEITEMFIXEDVALUE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

LINEITEMID

Fixed Line Item valueNoValueFIXEDVALUE

7.2.1.37 PPR_RBLINEITEMVALUE

2013-07-29159

Database Tables

Table: PPR_RBLINEITEMVALUE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

LINEITEMID

Line Item valueNoValueVALUE

Fixed Line Item valueNoValueFIXEDVALUE

Variable Line Item valueNoValueVARIABLEVALUE

7.2.1.38 PPR_RBLINEITEMVARVALUE

Table: PPR_RBLINEITEMVARVALUE

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

2013-07-29160

Database Tables



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

LINEITEMID

Line Item Variability valueNoValueVARIABILITY

7.2.1.39 PPR_RBRESOURCEDRIVERSPLIT

Table: PPR_RBRESOURCEDRIVERSPLIT

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID

2013-07-29161

Database Tables



NoMemberIdentifier

RESOURCECENTERID


NoMemberIdentifier

ACTIVITYID

Resource Driver split valueNoValueVALUE

Resource Driver percentage splitvalue

NoValuePCT_VALUE

7.2.1.40 PPR_RBRESOURCEDRIVERVALUE

Table: PPR_RBRESOURCEDRIVERVALUE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID

2013-07-29162

Database Tables



NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

RESOURCEDRIVERID

Resource Driver valueNoValueVALUE

7.2.1.41 PPR_RBREVENUE

Table: PPR_RBREVENUE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID

ID number for a Revenue Type (linksto PP_REVENUETYPE_NAME)

NoMemberIdentifier

REVENUETYPEID


NoMemberIdentifier

COSTOBJECT1ID


NoMemberIdentifier

COSTOBJECT2ID


NoMemberIdentifier

COSTOBJECT3ID

2013-07-29163

Database Tables



NoMemberIdentifier

COSTOBJECT4ID


NoMemberIdentifier

COSTOBJECT5ID

Unit Price valueNoValueUNITPRICE

Units Sold valueNoValueUNITSSOLD

Revenue valueNoValueREVENUE

7.2.1.42 PPR_RBSERVICEDRIVERVALUE

Table: PPR_RBSERVICEDRIVERVALUE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID

2013-07-29164

Database Tables



NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

SERVICEID

Service Driver valueNoValueVALUE

7.2.1.43 PPR_RBSERVICEFACTOR

Table: PPR_RBSERVICEFACTOR

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

SERVICEID

2013-07-29165

Database Tables


Variable Factor valueNoValueVARIABLEFACTOR

Fixed Unit Rate valueNoValueFIXEDUNITRATE


7.2.1.44 PPR_RBSPREADVALUE

Table: PPR_RBSPREADVALUE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID

ID number for the Spread (linksPP_SPREAD_NAME)

NoMemberIdentifier

SPREADID

Spread valueNoValueVALUE

7.2.1.45 PPR_RBWORKSHEETVALUE

Table: PPR_RBWORKSHEETVALUE

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

2013-07-29166

Database Tables



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID

ID number for Work Sheet 1 (linksto PP_WORKSHEET1_NAME)

NoMemberIdentifier

WORKSHEET1ID

ID number for Work Sheet 2 (linksto PP_WORKSHEET2_NAME)

NoMemberIdentifier

WORKSHEET2ID

Worksheet item valueNoValueVALUE

7.2.1.46 PPR_REASSACTLINEITEMVALUE

Table: PPR_REASSACTLINEITEMVALUE

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


ID number for he model (links toEPO_MODELS)

NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID

2013-07-29167

Database Tables



NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

LINEITEMID


NoMemberIdentifier

TARGETRESPCENTERID


NoMemberIdentifier

TARGETACTIVITYID

Reassigned Activity Line Item valueNoValueVALUE

7.2.1.47 PPR_REASSACTSERVICEVALUE

Table: PPR_REASSACTSERVICEVALUE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID

ID number for the Line Item (links toPP_SERVICE_NAME)

NoMemberIdentifier

SERVICEID

2013-07-29168

Database Tables



NoMemberIdentifier

TARGETRESPCENTERID


NoMemberIdentifier

TARGETACTIVITYID

Reassigned Activity Service valueNoValueVALUE

7.2.1.48 PPR_REASSIGNTRACE

Table: PPR_REASSIGNTRACE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

ACTIVITYID


NoMemberIdentifier

LINEITEMID


NoMemberIdentifier

TARGETRESPCENTERID


NoMemberIdentifier

TARGETACTIVITYID

2013-07-29169

Database Tables


Reassigned traceback in valueNoValueINVALUE

Reassigned traceback out valueNoValueOUTVALUE

Reassigned traceback final valueNoValueFINALVALUE

Reassigned traceback move valueNoValueMOVEVALUE

7.2.1.49 PPR_SERVICEACTIVITYVALUE

Table: PPR_SERVICEACTIVITYVALUE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

SERVICEID


NoMemberIdentifier

ACTIVITYID

2013-07-29170

Database Tables



NoMemberIdentifier

RESOURCEDRIVERID

Service Activity valueNoValueVALUE

Service Activity Unit Rate valueNoValueUNITRATE

7.2.1.50 PPR_SERVICECOSTOBJECTVALUE

Table: PPR_SERVICECOSTOBJECTVALUE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

SERVICEID


NoMemberIdentifier

ACTIVITYID


NoMemberIdentifier

COSTOBJECT1ID


NoMemberIdentifier

COSTOBJECT2ID


NoMemberIdentifier

COSTOBJECT3ID

2013-07-29171

Database Tables



NoMemberIdentifier

COSTOBJECT4ID


NoMemberIdentifier

COSTOBJECT5ID

Service Cost Object valueNoValueVALUE

7.2.1.51 PPR_SERVICEVALUE

Table: PPR_SERVICEVALUE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

SERVICEID

Service Cost valueNoValueCOST

Service Income valueNoValueINCOME

7.2.1.52 PPR_SCOSTOBJECTVALUE

2013-07-29172

Database Tables

Table: PPR_SCOSTOBJECTVALUE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

LINEITEMID


NoMemberIdentifier

COSTOBJECT1ID


NoMemberIdentifier

COSTOBJECT2ID


NoMemberIdentifier

COSTOBJECT3ID


NoMemberIdentifier

COSTOBJECT4ID


NoMemberIdentifier

COSTOBJECT5ID

Cost Object valueNoValueVALUE

Fixed Cost Object valueNoValueFIXEDVALUE

Variable Cost Object valueNoValueVARIABLEVALUE

7.2.1.53 PPR_SOURCEACTLINEITEMVALUE

Table: PPR_SOURCEACTLINEITEMVALUE

2013-07-29173

Database Tables

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

LINEITEMID


NoMemberIdentifier

TARGETRESPCENTERID


NoMemberIdentifier

TARGETACTIVITYID

Source Activity Line Item valueNoValueVALUE

Fixed source Activity Line Item valueNoValueFIXEDVALUE

Variable source Activity Line Itemvalue

NoValueVARIABLEVALUE

7.2.1.54 PPR_SPRIMARYACTIVITYDRIVER

Table: PPR_SPRIMARYACTIVITYDRIVER

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

2013-07-29174

Database Tables



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

SERVICEID


NoMemberIdentifier

ACTIVITYID


NoMemberIdentifier

ACTIVITYDRIVERID

Services primary Activity Driver val-ue

NoValueVOLUME


7.2.1.55 PPR_SUMACTIVITYVALUE

Table: PPR_SUMACTIVITYVALUE

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

2013-07-29175

Database Tables



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

ACTIVITYID

Summary Activity valueNoValueVALUE

Fixed summary Activity valueNoValueFIXEDVALUE

Variable summary Activity valueNoValueVARIABLEVALUE

7.2.1.56 PPR_SUMCOSTOBJECTVALUE

Table: PPR_SUMCOSTOBJECTVALUE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID

2013-07-29176

Database Tables



NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

COSTOBJECT1ID


NoMemberIdentifier

COSTOBJECT2ID


NoMemberIdentifier

COSTOBJECT3ID


NoMemberIdentifier

COSTOBJECT4ID


NoMemberIdentifier

COSTOBJECT5ID

Summary Cost Object valueNoValueVALUE

Fixed summary Cost Object valueNoValueFIXEDVALUE

Variable summary Cost Object valueNoValueVARIABLEVALUE

7.2.1.57 PPR_SUMMARYMOVEMENTVALUE

Table: PPR_SUMMARYMOVEMENTVALUE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID

2013-07-29177

Database Tables



NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

ACTIVITYID


NoMemberIdentifier

TARGETRESPCENTERID


NoMemberIdentifier

TARGETACTIVITYID

Summary movement valueNoValueVALUE

7.2.1.58 PPR_SUMSERVICEACTIVITYVALUE

Table: PPR_SUMSERVICEACTIVITYVALUE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID

2013-07-29178

Database Tables



NoMemberIdentifier

SERVICEID


NoMemberIdentifier

ACTIVITYID

Summary Service Activity valueNoValueVALUE

7.2.1.59 PPR_TARGETCOSTOBJECTVALUE

Table: PPR_TARGETCOSTOBJECTVALUE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID


NoMemberIdentifier

ACTIVITYID


NoMemberIdentifier

TARGETRESPCENTERID


NoMemberIdentifier

TARGETACTIVITYID


NoMemberIdentifier

COSTOBJECT1ID

2013-07-29179

Database Tables



NoMemberIdentifier

COSTOBJECT2ID


NoMemberIdentifier

COSTOBJECT3ID


NoMemberIdentifier

COSTOBJECT4ID


NoMemberIdentifier

COSTOBJECT5ID

Target Cost Object valueNoValueVALUE

7.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.



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

COSTOBJECT1ID


NoMemberIdentifier

COSTOBJECT2ID


NoMemberIdentifier

COSTOBJECT3ID


NoMemberIdentifier

COSTOBJECT4ID

2013-07-29180

Database Tables



NoMemberIdentifier

COSTOBJECT5ID

Total Cost Object valueNoValueVALUE

Fixed total Cost Object valueNoValueFIXEDVALUE

Variable total Cost Object valueNoValueVARIABLEVALUE

7.2.1.61 PPR_TRACEBACKVALUE

Table: PPR_TRACEBACKVALUE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID

ID number for the Activity (links toPP_LINEITEM_NAME)

NoMemberIdentifier

LINEITEMID


NoMemberIdentifier

TARGETRESPCENTERID

ID number for Activity (links toPP_ACTIVITY_NAME)

NoMemberIdentifier

TARGETACTIVITYID


NoMemberIdentifier

COSTOBJECT1ID

2013-07-29181

Database Tables



NoMemberIdentifier

COSTOBJECT2ID


NoMemberIdentifier

COSTOBJECT3ID


NoMemberIdentifier

COSTOBJECT4ID


NoMemberIdentifier

COSTOBJECT5ID

Traceback valueNoValueVALUE

Fixed traceback valueNoValueFIXEDVALUE

Variable traceback valueNoValueVARIABLEVALUE

7.2.1.62 OMR_EMPLOYEERESULTVALUE

Table: OMR_EMPLOYEERESULTVALUE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID

ID number for the Employee (linksto PP_EMPLOYEE_NAME)

NoMemberIdentifier

EMPLOYEEID

2013-07-29182

Database Tables



NoMemberIdentifier

COSTOBJECT1ID


NoMemberIdentifier

COSTOBJECT2ID

Employee result valueNoValueRESULTVALUE

Employee result IconNoValueRESULTICON

Employee result Range colorNoValueRESULTRANGECOLOR

Employee result Data colorNoValueRESULTDATACOLOR

7.2.1.63 OMR_METRICRESULTVALUE

Table: OMR_METRICRESULTVALUE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID

ID number of the Metric (links toPP_METRIC_NAME)

NoMemberIdentifier

METRICID


COSTOBJECT1ID


COSTOBJECT2ID

Metric total actual valueNoValueTOTALACTUALVALUE

2013-07-29183

Database Tables


Metric total target valueNoValueTOTALTARGETVALUE

Metric total actual IconNoValueTOTALACTUALICON

Metric total actual Range colorNoValueTOTALACTUALRANGECOLOR

Metric total actual data colorNoValueTOTALACTUALDATACOLOR

Metric variance valueNoValueVARIANCEVALUE

Metric achievement valueNoValueACHIEVEMENTVALUE

Metric achievement IconNoValueACHIEVEMENTICON

Metric achievement Range colorNoValueACHIEVEMENTRANGECOLOR

Metric achievement data colorNoValueACHIEVEMENTDATACOLOR

7.2.1.64 OMR_OBJECTIVERESULTVALUE

Table: OMR_OBJECTIVERESULTVALUE

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



NoIdentifierMODELID




NoMemberIdentifier

VERSIONID


NoMemberIdentifier

PERIODID


NoMemberIdentifier

RESPCENTERID

ID number of the Objective (links toPP_OBJECTIVES_NAME)

NoMemberIdentifier

OBJECTIVEID


COSTOBJECT1ID

2013-07-29184

Database Tables



COSTOBJECT2ID

Objective total actual valueNoValueTOTALACTUALVALUE

Objective total target valueNoValueTOTALTARGETVALUE

Objective achievement valueNoValueACHIEVEMENTVALUE

Objective linked result valueNoValueLINKEDRESULTVALUE

Objective Metric results valueNoValueMETRICRESULTSVALUE

Objective result valueNoValueRESULTVALUE

Objective total actual IconNoValueTOTALACTUALICON

Objective total actual Range colorNoValueTOTALACTUALRANGECOLOR

Objective total actual Data colorNoValueTOTALACTUALDATACOLOR

Objective result IconNoValueRESULTICON

Objective result Range colorNoValueRRSULTRANGECOLOR

Objective result Data colorNoValueRESULTDATACOLOR

Objective achievement IconNoValueACHIEVEMENTICON

Objective achievement Range colorNoValueACHIEVEMENTRANGECOLOR

Objective achievement Data colorNoValueACHIEVEMENTDATACOLOR

Objective Metric achievement IconNoValueMETRICACHIEVEMENTICON

Objective Metric achievement Rangecolor

NoValueMETRICACHIEVEMENTRANGECOLOR

Objective Metric achievement Datacolor

NoValueMETRICACHIEVEMENTDATACOLOR

Objective linked result IconNoValueLINKEDRESULTICON

Objective linked result Range colorNoValueLINKEDRESULTRANGECOLOR

Objective linked result Data colorNoValueLINKEDRESULTDATACOLOR

7.2.2 Dimension Tables

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

2013-07-29185

Database Tables


Unique ID relating to dimension itemNoIdentifierID (Key)

Language ID relating to data aliasNoIdentifierLANGID (Key)

ID number of modelNoIdentifierMODELID (Key)

Name of the dimension itemYesMemberName

NAME

Memo text for a dimension itemYesOther TextMEMO

Number of times the dimension itemhas been amended

NoAudit Identifi-er

CHANGEREVISION

User ID of last user to amend themodel

NoIdentifierAUDITUSERID

Date of last amendment to themodel

NoDateDATEALTERED

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

2013-07-29186

Database Tables

7.2.3 Results Views

A set of views are available to provide a more user friendly view of the results tables. The views usethe EPO Codes in the PPR_ and OMR_ results tables and join to the relevant dimension tables to displaythe default alias dimension item names for the associated calculated values. The names for standardviews 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 noteat the end of this topic.)

Additionally, for each view there are further equivalent views available that can be used in differentcircumstances as appropriate:• The “SM” view is available for Microsoft SQL Server databases. This executes a different structured

query plan with a merged join, which may return results more efficiently. The view name is constructedby adding a suffix of “SM” to the name. For example, VPPR_COSTOBJECTVALUE has an equivalentview called VPPR_COSTOBJECTVALUESM.

• The “BW” views have the column names shortened and the dimension item names shortened to 32characters. These views can be used for systems that have naming conventions with characterrestrictions. They have been added to the product to simplify the integration of results into SAPNetweaver® Business Warehouse through DBConnect. The view name is constructed by replacingthe prefix of “V” with “BW”. For example, VPPR_COSTOBJECTVALUE has an equivalent view calledBWPPR_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 volumeof data. Because each SAP BusinessObjects Profitability and Cost Management implementation isunique, we do not recommend a specific view, but suggest that each view type is tested to determinewhich one works the most efficiently in your particular environment.

Tip:Custom views can be written if an alias other than the default is required. This can be achieved bylinking in the EPO_DATA_ALIAS table. The alias table ID can be linked to the Lang ID of the relevantdimension table, which in turn links to the relevant results table.

Note:Exceptions 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

2013-07-29187

Database Tables

• View names for ppr_postreassignlineitemvalue:• vppr_postrelineitemvalue• vppr_postrelineitemvaluesm• bwppr_postrelineitemvalue

Related Topics• About Results Tables

7.2.4 Exporting Results

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

7.2.4.1 Export to Database

When an Export to Database is performed, each export of calculated results to the database has anexport ID associated with it, which groups the data for different report types that may be required. Froma 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 areeach given a separate export ID. If either set of data needs to be replaced, then the data can bere-exported with the same ID.

7.3 About Audit Tables

A set of tables is provided to hold auditing data. These tables, are created when running the initial tablebuild scripts, and each are associated with an equivalent table in the database that supports the softwareapplication. They fall into two categories; those that record alterations to data tables in the softwareframework, 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 arefundamental to the auditing process.

The table below provides a description for these fields:

2013-07-29188

Database Tables

Field Name

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

AUDITID

This is the second field in most audit records. Within each audit table, it identifiesthe alteration that was made to the equivalent database table that supports thesoftware 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.

Note:When a record is deleted, the existing audit records relating to the deletion candi-date are updated with user and date in the DELETEUSERID and DELETEDATEfields.

OPERATIONID

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, dataalias and rules.

• PP_AU_ - The Profitability and Costing, Bill of Materials and Transactional Costing audit tables areprefixed 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.

Note:Audit is switched on/off for core framework tables via the "Configuration Wizard". The user who performsthe 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 "ConfigurationWizard" first as a user who is a member of the DBO group, then a second time as the restricted user.

7.3.1 Framework Audit Tables

2013-07-29189

Database Tables

7.3.1.1 EPO_AU_BOOKS

Table: EPO_AU_BOOKS

This table contains audit data for EPO_BOOKS table.


Unique ID number relating to audititem

NoIdentifierAUDITID (Key)

ID number relating to type of auditoperation

NoIdentifierOPERATIONID

ID number for the bookNoIdentifierID


ID number for the parent bookNoIdentifierPARENTID

ID number for the security recordNoIdentifierSECURITYID

User ID of the last user to amendrecord


Date of the last amendment torecord

NoDateDATEALTERED

User ID of the user who deletedrecord

YesIdentifierDELETEUSERID

Date of deletedYesDateDELETEDATE

7.3.1.2 EPO_AU_BOOK_PROPERTY

Table: EPO_AU_BOOK_PROPERTY

This table contains audit data for EPO_BOOK_PROPERTY table.

2013-07-29190

Database Tables


Unique ID relating to audit itemNoIdentifierAUDITID (Key)





CategoryYesOther TextCATEGORY

ValueYesNMemoVALUE




NoDateDATEALTERED



Date deletedYesDateDELETEDATE

7.3.1.3 EPO_AU_BOOK_NAME

Table: EPO_AU_BOOK_NAME

This table contains audit data for EPO_BOOK_NAME table.


Unique ID relating toaudit itemNoIdentifierAUDITID (Key)





ID number for the languageNoIdentifierLANGID

Name of the bookYesOther TextNAME



2013-07-29191

Database Tables



NoDateDATEALTERED




7.3.1.4 EPO_AU_BOOK_INFO

Table: EPO_AU_BOOK_INFO

This table contains the audit data for the EPO_BOOK_INFO table.


Unique ID number relating to theaudit item






Book typeNoIdentifierBOOKTYPE

XML representation of the bookYesNMemoXML

User ID of the last user to amendthe record



NoDateDATEALTERED

User ID of the user who deleted therecord



7.3.1.5 EPO_AU_CELLMEMO

2013-07-29192

Database Tables

Table: EPO_AU_CELLMEMO

This table contains audit data for EPO_AU_CELLMEMO table.







ID of table fieldNoIdentifierTABLEFIELDID

String containing unique IDs for di-mension items making up key setfor a value

NoOther TextREFERENCE

Memo text for the modelNoMemoMEMO

Number of times the item has beenamended

NoAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED




7.3.1.6 EPO_AU_CURRENCY_PROPERTY

Table: EPO_AU_CURRENCY_PROPERTY

This table contains audit data for EPO_CURRENCY_PROPERTY table.

2013-07-29193

Database Tables






Name of the Currency itemNoMemberName

NAME

ID number for the Currency itemitem

NoIdentifierID

Currency formattingYesOther TextVALUE




NoDateDATEALTERED




7.3.1.7 EPO_AU_DATA_ALIAS

Table: EPO_AU_DATA_ALIAS

This table contains audit data for EPO_DATA_ALIAS table.






ID number for the Data AliasNoIdentifierID

Name of the Data AliasNoMemberName

NAME


NoAudit Identifi-er

CHANGEREVISION

2013-07-29194

Database Tables





NoDateDATEALTERED




7.3.1.8 EPO_AU_DEFAULT_BOOK

Table: EPO_AU_DEFAULT_BOOK

This table contains audit data for EPO_DEFAULT_BOOK table.








ID number for the user groupNoIdentifierGROUPID


Date of last amendment to recordNoDateDATEALTERED

User ID of user who deleted recordYesIdentifierDELETEUSERID


7.3.1.9 EPO_AU_DIMENSION_AT

Table: EPO_AU_DIMENSION_AT

2013-07-29195

Database Tables

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


Unique ID number relating toaudititem




ID number for the DimensionNoIdentifierDIMENSIONID

ID number for the ModelNoIdentifierMODELID

ID number for the Attribute itemNoIdentifierID

ID number for the parent AttributeNoIdentifierPARENTATTRIBID

Consolidation typeNoIdentifierCONSOLTYPE

CHILDSORT parameterNoOrder Identifi-er

CHILDSORT


NoIdentifierCHANGEREVISION

LATEST parameterYesOrder Identifi-er

LATEST




NoDateDATEALTERED




7.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 thesoftware, each dimension has its own name table. Changes to all of these are recorded through thisaudit table.

2013-07-29196

Database Tables








ID number for the Dimension itemNoIdentifierID


Name of the Dimension itemNoMemberName

NAME


LATEST




NoDateDATEALTERED




7.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 thesoftware, each dimension has its own rules table. Changes to all of these are recorded through thisaudit table.

2013-07-29197

Database Tables






ID number for the dimension itemNoIdentifierDIMENSIONID

ID number for the ruleNoIdentifierID


Rule numberNoIdentifierRULENUMBER

WIZARD number parameterNoIdentifierWIZARDNUMBER

Rule scriptYesNMemoRULETEXT


NoAudit Identifi-er

CHANGEREVISION

Rule descriptionYesOther TextRULEDESC


LATEST




NoDateDATEALTERED




7.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, eachdimension has its own table. Changes to all of these are recorded through this audit table.

2013-07-29198

Database Tables







ID number for the modelYesIdentifierMODELID


ID number for the parent itemNoIdentifierPARENTID


Consolidation typeNoConsolida-tion TypeIdentifier

CONSOLTYPE

Attribute typeYesOther TextATTRIBUTEINFO

CHILDSORT parameterNoOrder Identifi-er

CHILDSORT

Dimension item statusNoMemberIdentifier

ITEMSTATUS


NoAudit Identifi-er

CHANGEREVISION


LATEST




NoDateDATEALTERED




7.3.1.13 EPO_AU_DV_INFO

Table: EPO_AU_DV_INFO

2013-07-29199

Database Tables

This table contains audit data for EPO_DV_INFO table.






ID number for the layoutNoIdentifierID

Model typeNoIdentifierAPP_TYPE

ID number for the model that layoutoriginates from

NoIdentifierSRC_MODEL_ID

Name of the layoutNoOther TextVIEW_NAME



Date of the last amendment torecordNoDateDATEALTERED




7.3.1.14 EPO_AU_GROUP_INFO

Table: EPO_AU_GROUP_INFO

This table contains audit data for EPO_GROUP_INFO table.







Group categoryYesOther TextCATEGORY

Group valueYesNMemoVALUE



2013-07-29200

Database Tables



NoDateDATEALTERED




7.3.1.15 EPO_AU_GROUP_ROOT

Table: EPO_AU_GROUP_ROOT

This table contains audit data for EPO_GROUP_ROOT table.








ID number for the DimensionNoIdentifierDIMID





NoDateDATEALTERED




7.3.1.16 EPO_AU_GROUPS

2013-07-29201

Database Tables

Table: EPO_AU_GROUPS

This table contains audit data for EPO_GROUPS table.






ID of the user groupYesIdentifierID

Name of the user groupYesOther TextNAME




NoDateDATEALTERED




7.3.1.17 EPO_AU_METADATA_VERSION

Table: EPO_AU_METADATA_VERSION

This table contains audit data for EPO_METADATA_VERSION table.






Major release numberYesIdentifierMAJOR

Minor release numberYesIdentifierMINOR

Patch numberYesIdentifierPATCH



2013-07-29202

Database Tables



NoDateDATEALTERED




7.3.1.18 EPO_AU_MODEL_GROUPS

Table: EPO_AU_MODEL_GROUPS

This table contains audit data for EPO_MODEL_GROUPS table.











NoDateDATEALTERED




7.3.1.19 EPO_AU_MODEL_PARTITION

Table: EPO_AU_MODEL_PARTITION

This table contains audit data for EPO_MODEL_PARTITION table.

2013-07-29203

Database Tables







ID number for the VersionYesMemberIdentifier

VERSIONID

ID number for the PeriodYesMemberIdentifier

PERIODID

ID number for the ResponsibilityCenter

YesMemberIdentifier

RESPCENTERID

Partition precedenceYesIdentifierPRECEDENCE

Partition numberYesIdentifierPARTITION

Server nameYesOther TextSERVER




NoDateDATEALTERED




7.3.1.20 EPO_AU_MODEL_PROPERTY

Table: EPO_AU_MODEL_PROPERTY

This table contains audit data for EPO_MODEL_PROPERTY table.

2013-07-29204

Database Tables







ID number for the propertyNoIdentifierID

Name of the propertyNoOther TextNAME

Default property item valueNoOther TextDEFAULTVALUE




NoDateDATEALTERED




7.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.







ID number for the propertyNoIdentifierPROPERTYID

ID number for the Dimension itemNoIdentifierDIMENSIONITEMID

Property valueNoOther TextVALUE



2013-07-29205

Database Tables



NoDateDATEALTERED




7.3.1.22 EPO_AU_MODEL_SERVERS

Table: EPO_AU_MODEL_SERVERS

This table contains audit data for EPO_MODEL_SERVERS table.







Server nameNoOther TextSERVER




NoDateDATEALTERED




7.3.1.23 EPO_AU_MODELS

Table: EPO_AU_MODELS

This table contains audit data for EPO_MODELS table.

2013-07-29206

Database Tables


Unique ID relating to audit itemNoIdentifierAUDITID (Key)

ID relating to type of audit operationNoIdentifierOPERATIONID

ID number for the modelNoIdentifierID

Model typeNoIdentifierMODELTYPE

Name of the modelNoOther TextMODELNAME


Next available EPO code for themodel

YesIdentifierNEXTUNIQUEID

MODELSYNC parameterYesIdentifierMODELSYNC

Model statusNoIdentifierMODELSTATUS




NoDateDATEALTERED




7.3.1.24 EPO_AU_REPORTS

Table: EPO_AU_REPORTS

This table contains audit data for EPO_REPORTS table.






ID number for the reportYesIdentifierREPORT_ID

Name of the reportYesOther TextNAME

ID number of the security recordYesIdentifierSECURITY_ID

2013-07-29207

Database Tables





NoDateDATEALTERED




7.3.1.25 EPO_AU_SECURITY

Table: EPO_AU_SECURITY

This table contains audit data for EPO_SECURITY table.







ID number for the security recordNoIdentifierID

Security typeYesIdentifierSECURITYTYPE



2013-07-29208

Database Tables



NoDateDATEALTERED




7.3.1.26 EPO_AU_SECURITY_INFO

Table: EPO_AU_SECURITY_INFO

This table contains audit data for EPO_SECURITY_INFO table.









Security contextYesIdentifierSECURITYCONTEXT




NoDateDATEALTERED




7.3.1.27 EPO_AU_SECURITY_NAME

2013-07-29209

Database Tables

Table: EPO_AU_SECURITY_NAME

This table contains audit data for EPO_SECURITY_NAME table.






ID number for the security recordNoIdentifierID



Security nameYesOther TextNAME



YesAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED




7.3.1.28 EPO_AU_SERVERS

Table: EPO_AU_SERVERS

This table contains audit data for EPO_SERVERS table.

2013-07-29210

Database Tables






Name of the serverNoOther TextSERVER

ID number for the componentNoIdentifierCOMPONENT_ID




NoDateDATEALTERED




7.3.1.29 EPO_AU_USER_GROUP

Table: EPO_AU_USER_GROUP

This table contains audit data for the EPO_USER_GROUP table.







ID number for the userNoIdentifierUSERID



2013-07-29211

Database Tables



NoDateDATEALTERED




7.3.1.30 EPO_AU_USER_INFO

Table: EPO_AU_USER_INFO

This table contains audit data for EPO_USER_INFO table.






ID number of the userNoIdentifierUSERID

User categoryYesOther TextCATEGORY

ValueYesNMemoVALUE




NoDateDATEALTERED




7.3.1.31 EPO_AU_USERS

Table: EPO_AU_USERS

2013-07-29212

Database Tables

This table contains audit data for EPO_USERS table.


Unique ID number relating toaudititem




ID number for the userNoIdentifierID

Name of the userYesOther TextUSERNAME

User passwordYesOther TextPASSWORD

User statusYesIdentifierSTATUS




NoDateDATEALTERED




7.3.1.32 EPO_AUDIT_MESSAGES

Table: EPO_AUDIT_MESSAGES

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


ID of Audit table procedureNoIdentifierID (Key)


Message stringYesOther TextMESSAGE

7.3.1.33 EPO_AUDITLOG

2013-07-29213

Database Tables

Table: EPO_AUDITLOG

This table describes changes made to auditing.




ID number for the audit messageNoIdentifierMESSAGEID

Free text reason for auditing changeYesOther TextDESCRIPTION




NoDateDATEALTERED

7.3.2 Assignment Audit Tables

7.3.2.1 PP_AU_ACTIVITYREASSIGN

Table: PP_AU_ACTIVITYREASSIGN

This table contains audit data for PP_ACTIVITYREASSIGN table.







ID number for the VersionNoMemberIdentifier

VERSIONID

ID number for the PeriodNoMemberIdentifier

PERIODID

2013-07-29214

Database Tables



NoMemberIdentifier

RESPCENTERID

ID number for the ActivityNoMemberIdentifier

ACTIVITYID

ID number for the Resource Driverfor reassignment

NoMemberIdentifier

RESOURCEDRIVERID

ID number for the Resource Driverfor allocation

NoMemberIdentifier

ARESOURCEDRIVERID

ID number for the Target Responsi-bility Center

NoMemberIdentifier

TARGETRESPCENTERID

ID number for the Target ActivityNoMemberIdentifier

TARGETACTIVITYID


NoAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED




7.3.2.2 PP_AU_ASSRESPCENTERACTIVITY

Table: PP_AU_ASSRESPCENTERACTIVITY

This table contains audit data for PP_ASSRESPCENTERACTIVITY table.

2013-07-29215

Database Tables








NoMemberIdentifier

RESPCENTERID


ACTIVITYID


NoAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED




7.3.2.3 PP_AU_COSTOBJECTASSIGNMENT

Table: PP_AU_COSTOBJECTASSIGNMENT

This table contains audit data for PP_COSTOBJECTASSIGNMENT table.







ID number for the Cost Object as-signment

NoMemberIdentifier

COSTOBJID

2013-07-29216

Database Tables


ID number for the Cost ObjectNoMemberIdentifier

COSTOBJECTID

Cost Object type i.e Activity, LineItem or Service

NoMemberIdentifier

COTYPE


NoAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED




7.3.2.4 PP_AU_COSTOBJECTDRIVER

Table: PP_AU_COSTOBJECTDRIVER

This table contains audit data for PP_COSTOBJECTDRIVER table.







ID number for the Cost Object as-signment

NoMemberIdentifier

COSTOBJID

ID number for the Activity DriverNoMemberIdentifier

ACTIVITYDRIVERID

Location of the Activity Driver val-ues. (0 – All, 1 – Parent, Current,3007 – RC Unassigned)


VOLUMERESPCENTERTYPE

Cost Object type i.e Activity, LineItem or Service

NoIdentifierCOTYPE

2013-07-29217

Database Tables


Numeric order in which the ActivityDriver is applied (for example, firstis 1 and second is 2)

NoOrder Identifi-er

DRIVERORDER


NoAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED




7.3.2.5 PP_AU_COSTOBJITEM

Table: PP_AU_COSTOBJITEM

This table contains audit data for PP_COSTOBJITEM table.








ID

ID number for the Activity Line Itemcombination

NoCombinationIdentifier

LIACTID

Activity Line Item typeNoMemberIdentifier

LIACTTYPE


VERSIONID


PERIODID

2013-07-29218

Database Tables



NoMemberIdentifier

RESPCENTERID


NoAudit Identifi-er

CHANGEREVISION



NoDateDATEALTERED




7.3.2.6 PP_AU_LINEITEMDIRECT_ACTIVITY

Table: PP_AU_LINEITEMDIRECT_ACTIVITY

This table contains audit data for PP_LINEITEMDIRECT_ACTIVITY table.








VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID

ID number for the Line ItemNoMemberIdentifier

LINEITEMID

ID number for the Direct ActivityNoMemberIdentifier

ACTIVITYID

2013-07-29219

Database Tables



NoAudit Identifi-er

CHANGEREVISION


NoMemberIdentifier

AUDITUSERID

Date of the last amendment to therecord

NoDatetimeDATEALTERED


YesMemberIdentifier

DELETEUSERID

Date deletedYesDatetimeDELETEDATE

7.3.2.7 PP_AU_LINEITEMRESOURCEDRIVER

Table: PP_AU_LINEITEMRESOURCEDRIVER

This table contains audit data for PP_LINEITEMRESOURCEDRIVER table.







ID number for the VersionYesMemberIdentifier

VERSIONID

ID number for the PeriodYesMemberIdentifier

PERIODID


YesMemberIdentifier

RESPCENTERID

ID number for the Line ItemYesMemberIdentifier

LINEITEMID

ID number for the Resource DriverYesMemberIdentifier

RESOURCEDRIVERID



CHANGEREVISION

2013-07-29220

Database Tables



YesIdentifierAUDITUSERID


YesDateDATEALTERED




7.3.2.8 PP_AU_SERVICERESOURCEDRIVER

Table: PP_AU_SERVICERESOURCEDRIVER

This table contains audit data for the PP_SERVICERESOURCEDRIVER table.








VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID

ID number for the ServiceNoMemberIdentifier

SERVICEID

ID number for the Resource Driverassigned to the Service

NoMemberIdentifier

RESOURCEDRIVERID


NoAudit Identifi-er

CHANGEREVISION



2013-07-29221

Database Tables



NoDateDATEALTERED




7.3.2.9 PP_AU_SERVICEDIRECT_ACTIVITY

Table: PP_AU_SERVICEDIRECT_ACTIVITY

This table contains audit data for PP_SERVICEDIRECT_ACTIVITY table.








VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID

ID number for the Service assigneddirectly to an Activity

NoMemberIdentifier

SERVICEID


ACTIVITYID


NoAudit Identifi-er

CHANGEREVISION



2013-07-29222

Database Tables



NoDateDATEALTERED




7.3.2.10 PP_AU_RESPCENTERSERVICE

Table: PP_AU_RESPCENTERSERVICE

This table contains audit data for PP_RESPCENTERSERVICE table.








NoMemberIdentifier

RESPCENTERID


SERVICEID




NoDateDATEALTERED




7.3.2.11 OM_AU_ASSMETRICRESPCENTER

2013-07-29223

Database Tables

Table: OM_AU_ASSMETRICRESPCENTER

This table contains audit data for OM_ASSMETRICRESPCENTER table.



NoIdentifierAUDITID




ID number for the MetricNoMemberIdentifier

METRICID


NoMemberIdentifier

RESPCENTERID


NoAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED


NoIdentifierDELETEUSERID


7.3.2.12 OM_AU_ASSOBJECTIVEINITIATIVE

Table: OM_AU_ASSOBJECTIVEINITIATIVE

This table contains the audit data for the OM_ASSOBJECTIVEINITIATIVE table.

2013-07-29224

Database Tables



NoIdentifierAUDITID




ID number for the ObjectiveNoMemberIdentifier

OBJECTIVEID

ID number for the InitiativeNoMemberIdentifier

INITIATIVEID


NoAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED




7.3.2.13 OM_AU_ASSOBJECTIVELOBJECTIVE

Table: OM_AU_ASSOBJECTIVELOBJECTIVE

This table contains audit data for the OM_ASSOBJECTIVELOBJECTIVE table.



NoIdentifierAUDITID





OBJECTIVEID

2013-07-29225

Database Tables


ID number for the linked ObjectiveNoMemberIdentifier

LINKEDOBJECTIVEID


NoAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED




7.3.2.14 OM_AU_ASSOBJECTIVEMETRIC

Table: OM_AU_ASSOBJECTIVEMETRIC

This table contains the audit data for the OM_ASSOBJECTIVEMETRIC table.


Unique ID relating to the audit itemNoIdentifierAUDITID


ID of the ModelNoIdentifierMODELID

ID of the ObjectiveNoMemberIdentifier

OBJECTIVEID

ID of the MetricNoMemberIdentifier

METRICID

The number of times the item hasbeen amended

NoAudit Identifi-er

CHANGEREVISION



2013-07-29226

Database Tables



NoDateDATEALTERED




7.3.2.15 OM_AU_ASSOBJECTIVERESPCENTER

Table: OM_AU_ASSOBJECTIVERESPCENTER

This table contains the audit data for the OM_ASSOBJECTIVERESPCENTER table.


Unique ID relating to the audit itemNoIdentifierAUDITID


ID of the ModelNoIdentifierMODELID

ID of the ObjectiveNoMemberIdentifier

OBJECTIVEID

ID of the Responsibility CenterNoMemberIdentifier

RESPCENTERID


NoAudit Identifi-er

CHANGEREVISION



2013-07-29227

Database Tables



NoDateDATEALTERED




7.3.3 Value Audit Tables

7.3.3.1 PP_AU_ACTIVITYDRIVERDELTA

Table: PP_AU_ACTIVITYDRIVERDELTA

This table contains audit data for PP_ACTIVITYDRIVERDELTA table.








VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID


ACTIVITYDRIVERID

ID number for Cost Object 1NoMemberIdentifier

COSTOBJECT1ID

2013-07-29228

Database Tables



COSTOBJECT2ID


COSTOBJECT3ID


COSTOBJECT4ID


COSTOBJECT5ID

Activity Driver Delta valueNoValueACTIVITYDRIVERVALUE


NoAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED




7.3.3.2 PP_AU_ACTIVITYDRIVERTARGET

Table: PP_AU_ACTIVITYDRIVERTARGET

This table contains audit data for PP_ACTIVITYDRIVERTARGET table.








VERSIONID

2013-07-29229

Database Tables



PERIODID


NoMemberIdentifier

RESPCENTERID


ACTIVITYDRIVERID


COSTOBJECT1ID


COSTOBJECT2ID


COSTOBJECT3ID


COSTOBJECT4ID


COSTOBJECT5ID

Activity Driver Target valueNoValueACTIVITYDRIVERVALUE


NoAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED




7.3.3.3 PP_AU_ACTIVITYDRIVERVALUE

Table: PP_AU_ACTIVITYDRIVERVALUE

This table contains audit data for PP_ACTIVITYDRIVERVALUE table.

2013-07-29230

Database Tables








VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID


ACTIVITYDRIVERID


COSTOBJECT1ID


COSTOBJECT2ID


COSTOBJECT3ID


COSTOBJECT4ID


COSTOBJECT5ID

Activity Driver valueNoValueACTIVITYDRIVERVALUE


NoAudit Identifi-er

CHANGEREVISION



2013-07-29231

Database Tables



NoDateDATEALTERED




7.3.3.4 PP_AU_BOMMAKEUP

Table: PP_AU_BOMMAKEUP

This table contains audit data for PP_BOMMAKEUP table.






ID number for the modelNoMemberIdentifier

MODELID


VERSIONID


PERIODID


COSTOBJECT1ID

ID number for the Component thatis part of the product

NoMemberIdentifier

COMPONENTID

ID number for the Currency itemNoMemberIdentifier

CURRENCYID

YesValueVOLUME


NoAudit Identifi-er

CHANGEREVISION



2013-07-29232

Database Tables



NoDateDATEALTERED




7.3.3.5 PP_AU_BOMPRODUCTION

Table: PP_AU_BOMPRODUCTION

This table contains audit data for PP_BOMPRODUCTION table.






ID number for the modelNoMemberIdentifier

MODELID


VERSIONID


PERIODID


COSTOBJECT1ID


CURRENCYID

YesValueVALUE


NoAudit Identifi-er

CHANGEREVISION



2013-07-29233

Database Tables



NoDateDATEALTERED




7.3.3.6 PP_AU_BOMUNITSSOLD

Table: PP_AU_BOMUNITSSOLD

This table contains audit data for PP_BOMUNITSSOLD table.








VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID


COSTOBJECT1ID


COSTOBJECT2ID


COSTOBJECT3ID


COSTOBJECT4ID


COSTOBJECT5ID

2013-07-29234

Database Tables



CURRENCYID

YesValueVALUE


NoAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED




7.3.3.7 PP_AU_CURRENCYRATES

Table: PP_AU_CURRENCYRATES

This table contains audit data for PP_CURRENCYRATES table.






ID number for themodelNoIdentifierMODELID


VERSIONID


PERIODID

ID number for a Currency itemNoMemberIdentifier

CURRENCYID

Currency rateNoValueRATE


NoAudit Identifi-er

CHANGEREVISION

2013-07-29235

Database Tables





NoDateDATEALTERED




7.3.3.8 PP_AU_DAVERSION

Table: PP_AU_DAVERSION

This table contains audit data for PP_DAVERSION table.







ID number for the Driver AnalysisVersion

NoMemberIdentifier

VERSIONID

ID number for the Source VersionNoMemberIdentifier

REFVERSIONID


NoAudit Identifi-er

CHANGEREVISION



2013-07-29236

Database Tables



NoDateDATEALTERED




7.3.3.9 PP_AU_DEFAULTBOMMAKEUP

Table: PP_AU_DEFAULTBOMMAKEUP

This table contains audit data for PP_DEFAULTBOMMAKEUP table.








COSTOBJECT1ID

ID number for the Component thatis part of the product

NoMemberIdentifier

COMPONENTID

ID number for the Bill Of MaterialsMakeup

NoMemberIdentifier

BOMMAKEUPID


CURRENCYID

YesValueVOLUME


NoAudit Identifi-er

CHANGEREVISION



2013-07-29237

Database Tables



NoDateDATEALTERED




7.3.3.10 PP_AU_EXTERNALBOMUNITRATE

Table: PP_AU_EXTERNALBOMUNITRATE

This table contains audit data for PP_EXTERNALBOMUNITRATE table.








NoMemberIdentifier

VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID

ID number for Direct ActivityNoMemberIdentifier

ACTIVITYID


LINEITEMID


COSTOBJECT1ID


CURRENCYID

YesValueVALUE

2013-07-29238

Database Tables



NoAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED




7.3.3.11 PP_AU_HVACTIVITYDRIVERVOLUME

Table: PP_AU_HVACTIVITYDRIVERVOLUME

This table holds the audit data for the PP_HVACTIVITYDRIVERVOLUME table.



NoIdentifierAUDITID





VERSIONID


PERIODID


ACTIVITYDRIVERID

ID number for the Detail Cost Object1

NoMemberIdentifier

DETAILCOSTOBJECT1ID


NoMemberIdentifier

DETAILCOSTOBJECT2ID


NoMemberIdentifier

DETAILCOSTOBJECT3ID

2013-07-29239

Database Tables



NoMemberIdentifier

DETAILCOSTOBJECT4ID


NoMemberIdentifier

DETAILCOSTOBJECT5ID

Activity Driver volumeYesValueACTIVITYDRIVERVOLUME



CHANGEREVISION




NoDateDATEALTERED




7.3.3.12 PP_AU_HVCOSTOBJECTDRIVER

Table: PP_AU_HVCOSTOBJECTDRIVER

This table holds the audit data for the PP_HVCOSTOBJECTDRIVER table.



NoIdentifierAUDITID





COSTOBJID


ACTIVITYDRIVERID



CHANGEREVISION

2013-07-29240

Database Tables





NoDateDATEALTERED




7.3.3.13 PP_AU_HVEXTACTCOUNITRATE

Table: PP_AU_HVEXTACTCOUNITRATE

This table contains audit data for the PP_HVEXTACTCOUNITRATE table.








NoMemberIdentifier

VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID


ACTIVITYID


ACTIVITYDRIVERID


COSTOBJECT1ID


COSTOBJECT2ID

2013-07-29241

Database Tables



COSTOBJECT3ID


COSTOBJECT4ID


COSTOBJECT5ID




NoAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED




7.3.3.14 PP_AU_EMPLOYEERDS

Table: PP_AU_EMPLOYEERDS

This table contains the audit data for the PP_EMPLOYEERDS table.








VERSIONID


PERIODID

2013-07-29242

Database Tables



NoMemberIdentifier

RESPCENTERID

ID number for the EmployeeNoMemberIdentifier

EMPLOYEEID

ID number for the Resource DriverNoMemberIdentifier

RESOURCEDRIVERID


ACTIVITYID

The value of the SplitNoValueVALUE


NoAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED




7.3.3.15 PP_AU_EXTERNALACTIVITYVALUE

Table: PP_AU_EXTERNALACTIVITYVALUE

This table contains audit data for PP_EXTERNALACTIVITYVALUE table.








NoMemberIdentifier

VERSIONID

2013-07-29243

Database Tables



PERIODID


NoMemberIdentifier

RESPCENTERID

ID number for the Direct ActivityNoMemberIdentifier

ACTIVITYID


LINEITEMID


CURRENCYID

External Activity valueYesValueEXTERNALACTIVITYVALUE

Fixed external Activity valueYesValueEXTERNALACTIVITYFIXEDVALUE


NoAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED




7.3.3.16 PP_AU_EXTERNALCOSTOBJECTVALUE

Table: PP_AU_EXTERNALCOSTOBJECTVALUE

This table contains audit data for PP_EXTERNALCOSTOBJECTVALUE table.

2013-07-29244

Database Tables








NoMemberIdentifier

VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID


ACTIVITYID


LINEITEMID


COSTOBJECT1ID


COSTOBJECT2ID


COSTOBJECT3ID


COSTOBJECT4ID


COSTOBJECT5ID


CURRENCYID

External Cost Object valueYesValueEXTERNALCOSTOBJECTVALUE

Fixed external Cost Object valueYesValueEXTERNALCOSTOBJECTFIXEDVALUE


NoAudit Identifi-er

CHANGEREVISION



2013-07-29245

Database Tables



NoDateDATEALTERED




7.3.3.17 PP_AU_LINEITEMDELTA

Table: PP_AU_LINEITEMDELTA

This table contains audit data for PP_LINEITEMDELTA table.








VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID


LINEITEMID


CURRENCYID

Delta value of the Line ItemNoValueLINEITEMVALUE


NoAudit Identifi-er

CHANGEREVISION



2013-07-29246

Database Tables



NoDateDATEALTERED




7.3.3.18 PP_AU_LINEITEMDETAILVALUE

Table: PP_AU_LINEITEMDETAILVALUE

This table contains audit data for PP_LINEITEMDETAILVALUE table.








VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID

ID number for the Line Item Detailitem

NoMemberIdentifier

LINEITEMDETAILID


LINEITEMID


CURRENCYID

Line Item Detail valueNoValueVALUE


NoAudit Identifi-er

CHANGEREVISION

2013-07-29247

Database Tables





NoDateDATEALTERED




7.3.3.19 PP_AU_LINEITEMFIXEDVALUE

Table: PP_AU_LINEITEMFIXEDVALUE

This table contains audit data for PP_LINEITEMFIXEDVALUE table.








VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID


LINEITEMID


CURRENCYID

Fixed Line Item valueNoValueVALUE


NoAudit Identifi-er

CHANGEREVISION

2013-07-29248

Database Tables





NoDateDATEALTERED




7.3.3.20 PP_AU_LINEITEMVALUE

Table: PP_AU_LINEITEMVALUE

This table contains the audit data for the PP_LINEITEMVALUE table.








VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID


LINEITEMID


CURRENCYID

Line Item valueNoNumericLINEITEMVALUE


NoAudit Identifi-er

CHANGEREVISION

2013-07-29249

Database Tables





NoDateDATEALTERED




7.3.3.21 PP_AU_LINEITEMVARVALUE

Table: PP_AU_LINEITEMVARVALUE

This table contains audit data for PP_LINEITEMVARVALUE table.








VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID


LINEITEMID

Variable Line Item valueNoValueVALUE


NoAudit Identifi-er

CHANGEREVISION



2013-07-29250

Database Tables



NoDateDATEALTERED



Date deletionYesDateDELETEDATE

7.3.3.22 PP_AU_LOCKRESULTS

Table: PP_AU_LOCKRESULTS

This table contains audit data for PP_LOCKRESULTS table.







ID number for the locked VersionNoMemberIdentifier

VERSIONID

ID number for the locked PeriodNoMemberIdentifier

PERIODID


NoMemberIdentifier

CHANGEREVISION



2013-07-29251

Database Tables



NoDateDATEALTERED




7.3.3.23 PP_AU_METADATA_VERSION

Table: PP_AU_METADATA_VERSION

This table contains audit data for PP_METADATA_VERSION table.






Major release numberNoIdentifierMAJOR

Minor release numberNoIdentifierMINOR

Patch numberNoIdentifierPATCH




NoDateDATEALTERED




7.3.3.24 PP_AU_RESOURCEDRIVERDELTA

Table: PP_AU_RESOURCEDRIVERDELTA

2013-07-29252

Database Tables








VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID


RESOURCEDRIVERID

Resource Driver Delta valueNoValueRESOURCEDRIVERVALUE


NoAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED



Date of deletionYesDateDELETEDATE

7.3.3.25 PP_AU_RESOURCEDRIVERDSPLIT

This table contains audit data for PP_RESOURCEDRIVERDSPLIT table.

2013-07-29253

Database Tables








VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID


RESOURCEDRIVERID


ACTIVITYID

Activity Resource Driver Delta Splitvalue

NoValueRESOURCEDRIVERVALUE


NoAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED




7.3.3.26 PP_AU_RESOURCEDRIVERSPLIT

Table: PP_AU_RESOURCEDRIVERSPLIT

This table contains audit data for PP_RESOURCEDRIVERSPLIT table.

2013-07-29254

Database Tables








VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID


RESOURCEDRIVERID


ACTIVITYID

Activity Resource Driver Split valueNoValueRESOURCEDRIVERVALUE


NoAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED




7.3.3.27 PP_AU_RESOURCEDRIVERTARGET

Table: PP_AU_RESOURCEDRIVERTARGET

This table contains audit data for PP_RESOURCEDRIVERTARGET table.

2013-07-29255

Database Tables








VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID


RESOURCEDRIVERID

Resource Driver Target valueNoNumericRESOURCEDRIVERVALUE


NoAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED




7.3.3.28 PP_AU_RESOURCEDRIVERTARSPLIT

Table: PP_AU_RESOURCEDRIVERTARSPLIT

This table contains the audit data for the PP_RESOURCEDRIVERTARSPLIT table.

2013-07-29256

Database Tables


Unique ID relating to the audit itemNoIdentifierAUDITID (Key)


ID of a ModelNoIdentifierMODELID

ID of a VersionNoMemberIdentifier

VERSIONID

ID of a PeriodNoMemberIdentifier

PERIODID

ID of a Responsibility CenterNoMemberIdentifier

RESPCENTERID

ID of a Resource DriverNoMemberIdentifier

RESOURCEDRIVERID

ID of an ActivityNoMemberIdentifier

ACTIVITYID

Resource Driver Target Split Valuefor the Activity

NoValueRESOURCEDRIVERVALUE


NoAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED



Date of deletionYesDateDELETEDATE

7.3.3.29 PP_AU_RESOURCEDRIVERVALUE

Table: PP_AU_RESOURCEDRIVERVALUE

This table contains audit data for PP_RESOURCEDRIVERVALUE table.

2013-07-29257

Database Tables







ID number for VersionNoMemberIdentifier

VERSIONID

ID number for PeriodNoMemberIdentifier

PERIODID

ID number for Responsibility CenterNoMemberIdentifier

RESPCENTERID

ID number for Resource DriverNoMemberIdentifier

RESOURCEDRIVERID

Resource Driver valueNoValueRESOURCEDRIVERVALUE

Number of times item has beenamended

NoAudit Identifi-er

CHANGEREVISION





7.3.3.30 PP_AU_REVENUE

Table: PP_AU_REVENUE

This table contains audit data for the PP_REVENUE table.

2013-07-29258

Database Tables








VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID

ID number for the Revenue TypeNoMemberIdentifier

REVENUETYPEID


COSTOBJECT1ID


COSTOBJECT2ID


COSTOBJECT3ID


COSTOBJECT4ID


COSTOBJECT5ID


CURRENCYID

Unit Price valueNoValueUNIT_PRICE

Units Sold valueNoValueUNITS_SOLD

Revenue item valueNoValueREVENUE


NoAudit Identifi-er

CHANGEREVISION



2013-07-29259

Database Tables



NoDateDATEALTERED




7.3.3.31 PP_AU_SERVICEDRIVERDELTA

Table: PP_AU_SERVICEDRIVERDELTA

This table contains audit data for PP_SERVICEDRIVERDELTA table.








VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID


SERVICEID

Service Driver Delta valueNoValueSERVICEDRIVERVALUE


NoAudit Identifi-er

CHANGEREVISION



2013-07-29260

Database Tables



NoDateDATEALTERED




7.3.3.32 PP_AU_SERVICEDRIVERTARGET

Table: PP_AU_SERVICEDRIVERTARGET

This table contains audit data for PP_SERVICEDRIVERTARGET table.








VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID


SERVICEID

Service Driver Target valueNoValueSERVICEDRIVERVALUE


NoAudit Identifi-er

CHANGEREVISION



2013-07-29261

Database Tables



NoDateDATEALTERED




7.3.3.33 PP_AU_SERVICEDRIVERVALUE

Table: PP_AU_SERVICEDRIVERVALUE

This table contains audit data for the PP_SERVICEDRIVERVALUE table.








VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID


SERVICEID

Service Driver valueNoNumericSERVICEDRIVERVALUE


NoAudit Identifi-er

CHANGEREVISION



2013-07-29262

Database Tables



NoDateDATEALTERED




7.3.3.34 PP_AU_SERVICEFACTOR

Table: PP_AU_SERVICEFACTOR

This table contains audit data for the PP_SERVICEFACTOR table.








VERSIONID


PERIODID


SERVICEID


CURRENCYID

Variable Factor valueNoValueVARIABLEFACTOR


Number of times the item has beenthe amended

NoAudit Identifi-er

CHANGEREVISION



2013-07-29263

Database Tables



NoDateDATEALTERED




7.3.3.35 PP_AU_SPREADVALUE

Table: PP_AU_SPREADVALUE

This table contains audit data for the PP_SPREADVALUE table.






ID number relating the modelNoIdentifierMODELID

ID number relating the VersionNoMemberIdentifier

VERSIONID

ID number relating the PeriodNoMemberIdentifier

PERIODID

ID number for the SpreadNoMemberIdentifier

SPREADID

Spread valueNoValueSPREADVALUE


NoAudit Identifi-er

CHANGEREVISION



2013-07-29264

Database Tables



NoDateDATEALTERED




7.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_SUBSTITUTIONStable.




ID number relating to the type ofaudit operation



ID number for the LanguageNoIdentifierLANGID

ID number for the substitute itemNoIdentifierID

Substitute nameYesOther TextSUBSTITUTION



2013-07-29265

Database Tables



NoDateDATEALTERED




7.3.3.37 PP_AU_USER_RULE

Table: PP_AU_USER_RULE

This table contains audit data for the PP_USER_RULE table.







Rule scriptYesNMemoRULETEXT



CHANGEREVISION

Rule descriptionYesOther TextRULEDESC


YesIdentifierAUDITUSERID

2013-07-29266

Database Tables



YesDateDATEALTERED




7.3.3.38 PP_AU_WORKSHEETVALUE

Table: PP_AU_WORKSHEETVALUE

This table contains audit data for the PP_WORKSHEETVALUE table.








VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID

ID number for Work Sheet 1NoMemberIdentifier

WORKSHEET1ID

ID number for Work Sheet 2NoMemberIdentifier

WORKSHEET2ID

Value of Work Sheet array itemNoValueWORKSHEETVALUE


NoAudit Identifi-er

CHANGEREVISION



2013-07-29267

Database Tables



NoDateDATEALTERED




7.3.3.39 OM_AU_BOUNDARYINFO

Table: OM_AU_BOUNDARYINFO

This table contains audit data for the OM_BOUNDARYINFO table.



NoIdentifierAUDITID




ID number for the Group BoundaryNoMemberIdentifier

GROUPBOUNDARYID

ID number for the BoundaryNoMemberIdentifier

BOUNDARYID

ID number for the IconNoMemberIdentifier

ICONID

Range colorNoIdentifierRANGECOLOR

Data colorNoIdentifierDATACOLOR


NoAudit Identifi-er

CHANGEREVISION



2013-07-29268

Database Tables



NoDateDATEALTERED




7.3.3.40 OM_AU_EMPLOYEEB

Table: OM_AU_EMPLOYEEB

This table contains the audit data for the OM_AU_EMPLOYEEB table.



NoIdentifierAUDITID




ID number for EmployeeNoMemberIdentifier

EMPLOYEEID

ID number for BoundaryNoMemberIdentifier

BOUNDARYID

ID number for measureNoMemberIdentifier

MEASUREID


NoAudit Identifi-er

CHANGEREVISION


2013-07-29269

Database Tables





7.3.3.41 OM_AU_EMPLOYEEBOUNDARY

Table: OM_AU_EMPLOYEEBOUNDARY

This table contains the audit data for the OM_AU_EMPLOYEEBOUNDARY table.



NoIdentifierAUDITID





VERSIONID


PERIODID


RESPCENTERID

ID number for EmployeeNoMemberIdentifier

EMPLOYEEID


COSTOBJECT1ID


COSTOBJECT2ID


BOUNDARYID

ID number for MeasureNoMemberIdentifier

MEASUREID

Employee Boundary valueNoValueVALUE

2013-07-29270

Database Tables



NoAudit Identifi-er

CHANGEREVISION



User ID of user who deleted recordNoIdentifierDELETEUSERID


7.3.3.42 OM_AU_ICONVALUE

Table: OM_AU_ICONVALUE

This table contains audit data for OM_ICONVALUE table.



NoIdentifierAUDITID




ID number for IconNoMemberIdentifier

ICONID

Icon propertyYesOther TextCATEGORY

An icon value (encoded)YesNMemoVALUE

number of times item has beenamended

NoAudit Identifi-er

CHANGEREVISION


2013-07-29271

Database Tables





7.3.3.43 OM_AU_INITIATIVE_DETAIL

Table: OM_AU_INITIATIVE_DETAIL

This table contains the audit data for the OM_INITIATIVE_DETAIL table.



NoIdentifierAUDITID




ID number for the InitiativeNoMemberIdentifier

INITIATIVEID

Initiative nameNoOther TextSHORTDESCRIPTION

Initiative descriptionNoNMemoLONGDESCRIPTION

Internal system date for the calcula-tion of new initiatives

NoDate ValueAREFERENCE

User ID of the user who created theinitiative

NoIdentifierCREATEUSERID

User name of the user who lastamended the initiative

NoOther TextLASTMODIFIEDNAME


NoAudit Identifi-er

CHANGEREVISION



2013-07-29272

Database Tables



NoDateDATEALTERED




7.3.3.44 OM_AU_METRICACTUAL

Table: OM_AU_METRICACTUAL

This table contains audit data for OM_METRICACTUAL table.



NoIdentifierAUDITID





VERSIONID


PERIODID


RESPCENTERID

ID number for MetricNoMemberIdentifier

METRICID


COSTOBJECT1ID


COSTOBJECT2ID

ID number for CurrencyNoMemberIdentifier

CURRENCYID

Metric valueNoValueVALUE

2013-07-29273

Database Tables



NoAudit Identifi-er

CHANGEREVISION





7.3.3.45 OM_AU_METRICADJUSTMENT

Table: OM_AU_METRICADJUSTMENT

This table contains audit data for the OM_METRICADJUSTMENT table.



NoIdentifierAUDITID





VERSIONID


PERIODID


RESPCENTERID


METRICID


COSTOBJECT1ID


COSTOBJECT2ID


CURRENCYID

2013-07-29274

Database Tables


Metric adjustment valueNoNumericVALUE


NoAudit Identifi-er

CHANGEREVISION





7.3.3.46 OM_AU_METRICADJUSTTARGET

Table: OM_AU_METRICADJUSTTARGET

This table contains audit data for OM_METRICADJUSTTARGET table.



NoIdentifierAUDITID





VERSIONID


PERIODID


RESPCENTERID


METRICID


COSTOBJECT1ID


COSTOBJECT2ID

2013-07-29275

Database Tables



CURRENCYID

Metric Adjustment Target valueNoValueVALUE


NoAudit Identifi-er

CHANGEREVISION





7.3.3.47 OM_AU_METRICB

Table: OM_AU_METRICB

This table contains audit data for the OM_METRICB table.



NoIdentifierAUDITID





METRICID


BOUNDARYID


MEASUREID


NoAudit Identifi-er

CHANGEREVISION


2013-07-29276

Database Tables





7.3.3.48 OM_AU_METRICBASEPOINT

Table: OM_AU_METRICBASEPOINT

This table contains audit data for the OM_METRICBASEPOINT table.



NoIdentifierAUDITID





VERSIONID


PERIODID


RESPCENTERID


METRICID


COSTOBJECT1ID


COSTOBJECT2ID


CURRENCYID

Metric basepoint valueNoValueVALUE


NoAudit Identifi-er

CHANGEREVISION

2013-07-29277

Database Tables






7.3.3.49 OM_AU_METRICBOUNDARY

Table: OM_AU_METRICBOUNDARY

This table contains audit data for the OM_METRICBOUNDARY table.



NoIdentifierAUDITID





VERSIONID


PERIODID


RESPCENTERID


METRICID


COSTOBJECT1ID


COSTOBJECT2ID


BOUNDARYID


MEASUREID

2013-07-29278

Database Tables


Metric Boundary valueNoValueVALUE


NoAudit Identifi-er

CHANGEREVISION





7.3.3.50 OM_AU_METRICTARGET

Table: OM_AU_METRICTARGET

This table contains audit data for the OM_METRICTARGET table.



NoIdentifierAUDITID





VERSIONID


PERIODID


RESPCENTERID


METRICID


COSTOBJECT1ID


COSTOBJECT2ID

2013-07-29279

Database Tables



CURRENCYID

Metric Target valueNoValueVALUE


NoAudit Identifi-er

CHANGEREVISION





7.3.3.51 OM_AU_OBJECTIVEACTUAL

Table: OM_AU_OBJECTIVEACTUAL

This table contains audit data for OM_OBJECTIVEACTUAL table.



NoIdentifierAUDITID





VERSIONID


PERIODID


RESPCENTERID

ID number for ObjectiveNoMemberIdentifier

OBJECTIVEID


COSTOBJECT1ID

2013-07-29280

Database Tables



COSTOBJECT2ID

Objective Actual valueNoValueVALUE


NoAudit Identifi-er

CHANGEREVISION





7.3.3.52 OM_AU_OBJECTIVEADJUSTMENT

Table: OM_AU_OBJECTIVEADJUSTMENT

This table contains audit data for the OM_OBJECTIVEADJUSTMENT table.



NoIdentifierAUDITID





VERSIONID


PERIODID


RESPCENTERID


OBJECTIVEID


COSTOBJECT1ID

2013-07-29281

Database Tables



COSTOBJECT2ID

Objective Adjustment valueNoValueVALUE


NoAudit Identifi-er

CHANGEREVISION





7.3.3.53 OM_AU_OBJECTIVEADJUSTTARGET

Table: OM_AU_OBJECTIVEADJUSTTARGET

This table contains audit data for the OM_OBJECTIVEADJUSTTARGET table.



NoIdentifierAUDITID





VERSIONID


PERIODID


RESPCENTERID


OBJECTIVEID


COSTOBJECT1ID

2013-07-29282

Database Tables



COSTOBJECT2ID

Objective Adjustment Target valueNoValueVALUE


NoAudit Identifi-er

CHANGEREVISION





7.3.3.54 OM_AU_OBJECTIVEB

Table: OM_AU_OBJECTIVEB

This table contains audit data for the OM_OBJECTIVEB table.



NoIdentifierAUDITID





OBJECTIVEID


BOUNDARYID


MEASUREID


NoAudit Identifi-er

CHANGEREVISION


2013-07-29283

Database Tables





7.3.3.55 OM_AU_OBJECTIVEBASEPOINT

Table: OM_AU_OBJECTIVEBASEPOINT

This table contains audit data for the OM_OBJECTIVEBASEPOINT table.



NoIdentifierAUDITID





VERSIONID


PERIODID


RESPCENTERID


OBJECTIVEID


COSTOBJECT1ID


COSTOBJECT2ID

Objective basepoint valueNoValueVALUE


NoAudit Identifi-er

CHANGEREVISION


2013-07-29284

Database Tables




Date of deletedYesDateDELETEDATE

7.3.3.56 OM_AU_OBJECTIVEBOUNDARY

Table: OM_AU_OBJECTIVEBOUNDARY

This table contains audit data for the OM_OBJECTIVEBOUNDARY table.



NoIdentifierAUDITID





VERSIONID


PERIODID


RESPCENTERID


OBJECTIVEID


COSTOBJECT1ID


COSTOBJECT2ID


BOUNDARYID


MEASUREID

Objective Boundary valueNoValueVALUE

2013-07-29285

Database Tables



NoAudit Identifi-er

CHANGEREVISION





7.3.3.57 OM_AU_OBJECTIVEMETRICWEIGHTING

Table: OM_AU_OBJECTIVEMETRICWEIGHTING

This table contains audit data for the OM_OBJECTIVEMETRICWEIGHTING table.



NoIdentifierAUDITID





VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID


OBJECTIVEID

ID number for the MetricNoMemberIdentifier

METRICID


COSTOBJECT1ID


COSTOBJECT2ID

2013-07-29286

Database Tables


Objective Metric Weighting valueNoValueWEIGHTING


NoAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED




7.3.3.58 OM_AU_OBJECTIVETARGET

Table: OM_AU_OBJECTIVETARGET

This table contains audit data for the OM_OBJECTIVETARGET table.



NoIdentifierAUDITID





VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID


OBJECTIVEID


COSTOBJECT1ID

2013-07-29287

Database Tables



COSTOBJECT2ID

Objective Target valueNoValueVALUE


NoAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED




7.3.3.59 OM_AU_OBJECTIVEWEIGHTING

Table: OM_AU_OBJECTIVEWEIGHTING

This table contains audit data for the OM_OBJECTIVEWEIGHTING table.



NoIdentifierAUDITID





VERSIONID


PERIODID


NoMemberIdentifier

RESPCENTERID


OBJECTIVEID

2013-07-29288

Database Tables


ID number for the linked ObjectiveNoMemberIdentifier

LINKEDOBJECTIVEID


COSTOBJECT1ID


COSTOBJECT2ID

Weighting valueNoValueWEIGHTING


NoAudit Identifi-er

CHANGEREVISION




NoDateDATEALTERED




2013-07-29289

Database Tables

2013-07-29290

Database Tables

More Information

LocationInformation Resource

http://www.sap.comSAP BusinessObjects product infor-mation

Navigate to http://help.sap.com/businessobjects and on the "SAP Busi-nessObjects Overview" side panel click All Products.

You can access the most up-to-date documentation covering all SAPBusinessObjects products and their deployment at the SAP Help Portal.You can download PDF versions or installable HTML libraries.

Certain guides are stored on the SAP Service Marketplace and are notavailable from the SAP Help Portal. These guides are listed on the HelpPortal accompanied by a link to the SAP Service Marketplace. Customerswith a maintenance agreement have an authorized user ID to accessthis site. To obtain an ID, contact your customer support representative.

SAP Help Portal

http://service.sap.com/bosap-support > Documentation• Installation guides: https://service.sap.com/bosap-instguides• Release notes: http://service.sap.com/releasenotes

The SAP Service Marketplace stores certain installation guides, upgradeand migration guides, deployment guides, release notes and SupportedPlatforms documents. Customers with a maintenance agreement havean authorized user ID to access this site. Contact your customer supportrepresentative to obtain an ID. If you are redirected to the SAP ServiceMarketplace from the SAP Help Portal, use the menu in the navigationpane on the left to locate the category containing the documentation youwant to access.

SAP Service Marketplace

https://cw.sdn.sap.com/cw/community/docupedia

Docupedia provides additional documentation resources, a collaborativeauthoring environment, and an interactive feedback channel.

Docupedia

https://boc.sdn.sap.com/

https://www.sdn.sap.com/irj/sdn/businessobjects-sdklibraryDeveloper resources

2013-07-29291

More Information

http://www.sap.com

http://help.sap.com/businessobjects

http://service.sap.com/bosap-support

https://service.sap.com/bosap-instguides

http://service.sap.com/releasenotes

https://cw.sdn.sap.com/cw/community/docupedia

https://boc.sdn.sap.com/

https://www.sdn.sap.com/irj/sdn/businessobjects-sdklibrary

LocationInformation Resource

https://www.sdn.sap.com/irj/boc/businessobjects-articles

These articles were formerly known as technical papers.SAP BusinessObjects articles onthe SAP Community Network

https://service.sap.com/notes

These notes were formerly known as Knowledge Base articles.Notes

https://www.sdn.sap.com/irj/scn/forumsForums on the SAP CommunityNetwork

http://www.sap.com/services/education

From traditional classroom learning to targeted e-learning seminars, wecan offer a training package to suit your learning needs and preferredlearning style.

Training


The SAP Support Portal contains information about Customer Supportprograms and services. It also has links to a wide range of technical in-formation and downloads. Customers with a maintenance agreementhave an authorized user ID to access this site. To obtain an ID, contactyour customer support representative.

Online customer support

http://www.sap.com/services/bysubject/businessobjectsconsulting

Consultants can accompany you from the initial analysis stage to thedelivery of your deployment project. Expertise is available in topics suchas relational and multidimensional databases, connectivity, databasedesign tools, and customized embedding technology.

Consulting

2013-07-29292

More Information

https://www.sdn.sap.com/irj/boc/businessobjects-articles

https://service.sap.com/notes

https://www.sdn.sap.com/irj/scn/forums

http://www.sap.com/services/education


http://www.sap.com/services/bysubject/businessobjectsconsulting

IndexA

About Results TablesExporting Results 188

Activities ReassignmentPPLOAD_COSTOBJECTASSIGNMENT

73Activity Driver Volume

PPLOAD_HVACTIVITYDRIVERVOLUME93

Alias Data LoadEPO_DATA_ALIAS 33OMLOAD_#_AL 33pkgPP_#_ALIAS 33PP_#_NAME 33PPLOAD_#_AL 33

Alias Procedures and Packages 31Assignment Load 36Assignment Procedures and Packages

35Audit Tables

About 188autogrow 56Automatic Model Refresh 43

B

Bill of Materials Default Makeup 89Bill of Materials External Unit Rate 91Bill of Materials Makeup 85Bill of Materials Production

PPLOAD_BOMPRODUCTION 86Bill of Materials Units Sold

PPLOAD_BOMUNITSSOLD 87Boundary info

OMLOAD_BOUNDARYINFO 105

C

Core tables 11Cost Object Assignment

PP_COSTOBJECTASSIGNMENT74

PP_COSTOBJITEM 74Cost Object Driver Assignment

PP_COSTOBJECTDRIVER 75PP_COSTOBJITEM 75PP_HVCOSTOBJECTDRIVER 75

Currency RatePPLOAD_CURRENCYRATES 88

D

Data LoaderAbout 19Assignment Tables 72Follow-up Activities 44Management Tables 66Structural Tables 68

Data Loader Completion Checks 44Data Loader Error Codes 54Data Loader Management Tables

EPO_DBCONFIG 66EPO_ERRORLOG 66PPHV_LOG 67PPLOAD_LOG 67

Data Loader Parallel ProcessingScripts 61

Data Loader Parameters 22Data Loader Preparation 19Data Loader Structural Tables

EPOLOAD_PROPERTY 71EPOLOAD_PROPERTYITEM 72PPLOAD_#_AL 70PPLOAD_#_DH 69

Data Loader TablesAbout 64

Database Administrator's GuideAbout 9

Database Setup Scripts 12Dimension Data load 30Dimension Procedures and Packages

29Dimension Tables 185Disk Space Maintenance

Data File Maintenance 56

E

Employee boundaryOMLOAD_EMPLOYEEBOUNDARY

106Employee Boundary Measure

OMLOAD_EMPLOYEEB 107Employee Resource Driver Split

PPLOAD_EMPLOYEERDS 89EPO_AU_BOOK_INFO 192EPO_AU_BOOK_NAME 191EPO_AU_BOOK_PROPERTY 190EPO_AU_BOOKS 190, 276, 277EPO_AU_CELLMEMO 193

EPO_AU_CURRENCY_PROPERTY193

EPO_AU_DATA_ALIAS 194EPO_AU_DEFAULT_BOOK 195EPO_AU_DIMENSION_AT 195EPO_AU_DIMENSION_NAME 196EPO_AU_DIMENSION_RULE 197EPO_AU_DIMENSION_STRUCTURE

198EPO_AU_DV_INFO 199EPO_AU_GROUP_INFO 200EPO_AU_GROUP_ROOT 201EPO_AU_GROUPS 202EPO_AU_METADATA_VERSION 202EPO_AU_MODEL_GROUPS 203EPO_AU_MODEL_PARTITION 203EPO_AU_MODEL_PROPERTY 204EPO_AU_MODEL_PROPERTY_VALUE

205EPO_AU_MODEL_SERVERS 206EPO_AU_MODELS 206EPO_AU_REPORTS 207EPO_AU_SECURITY 208EPO_AU_SECURITY_INFO 209EPO_AU_SECURITY_NAME 210EPO_AU_SERVERS 210EPO_AU_USER_GROUP 211EPO_AU_USER_INFO 212EPO_AU_USERS 212EPO_AUDIT_MESSAGES 213EPO_AUDITLOG 214EPOACCESS 16Execute Data Loader Routines

PP_EXECUTEDLROUTINES 42Exporting Results

Export to Database 188ExportToLoad 43External activity cost object unit rate

PPLOAD_HVEXTACTCOUNITRATE94

External Activity ValuePPLOAD

_EXTERNALACTIVITYVALUE90

External Cost Object ValuePPLOAD_EXTERNALCOSTOBJECTVALUE

92

G

Generating a Load Identifier 19

2013-07-29293

H

History of Changes 5

I

Icon ValueOMLOAD_ICONVALUE 107

Indexes and Statistics 56

L

Line item detail valuePPLOAD_LINEITEMDETAILVALUE

95Line Item Direct Activity Overrides

PPLOAD_LINEITEMDIRECT_ACTIVITY76

Line item fixed valuePPLOAD_LINEITEMFIXEDVALUE

96Line item value data

PP_LINEITEMDELTA 97PPLOAD_LINEITEMVALUE 97

Line Item VariablePPLOAD_LINEITEMVARIABLE 98

Load Log TablePPLOAD_LOG 47

LOADSTATUS Constant Names 47LOADSTATUS Field Values 47Log Maintenance 62

M

Metric actual adjustment valueOMLOAD_METRICADJUSTMENT

109Metric Actual Value

OMLOAD_METRICACTUAL 108Metric base point value

OMLOAD_METRICBASEPOINT111

Metric Boundary MeasureOMLOAD_METRICB 111

Metric boundary valueOMLOAD_METRICBOUNDARY

112Metric target adjustment value

OMLOAD_METRICADJUSTTARGET110

Metric target valueOMLOAD_METRICTARGET 113

Metrics Employees AssignmentOverride ValueOMLOAD_OVRMETRICEMPLOYEE

82Metrics Employees Assignment Value

OMLOAD_ASSMETRICEMPLOYEE79

Metrics Responsibility CentersAssignment ValueOMLOAD_ASSMETRICRESPCENTER

80Microsoft SQL Server

Pre-installation Tasks 12Setting up a New Database 15

MSSQLParallelQuery_OFF.SQL 61MSSQLParallelQuery_ON.SQL 61

O

Objective actual adjustment valueOMLOAD_OBJECTIVEADJUSTMENT

115Objective Actual Value

OMLOAD_OBJECTIVEACTUAL114

Objective Base Point ValueOMLOAD_OBJECTIVEBASEPOINT

117Objective boundary measure

OMLOAD_OBJECTIVEB 117Objective boundary value

OMLOAD_OBJECTIVEBOUNDARY118

Objective Metric Weighting ValueOMLOAD_OBJMETRICWEIGHTING

121Objective target adjustment value

OMLOAD_OBJECTIVEJUSTTARGET116

Objective target valueOMLOAD_OBJECTIVETARGET

119Objective weighting value

OMLOAD_OBJECTIVEWEIGHTING120

Objectives Employees AssignmentOverride ValueOMLOAD_OVROBJECTIVEEMPLOYEE

83Objectives Employees Assignment

ValueOMLOAD_OBJMETRICWEIGHTING

80

Objectives Linked Objectives AssignmentValueOMLOAD_ASSOBJECTIVELOBJECTIVE

81Objectives Metrics Assignment Value

OMLOAD_ASSOBJECTIVEMETRIC81

Objectives Responsibility CentersAssignment ValueOMLOAD_ASSOBJECTIVERESPCENTER

82OM_AU_ASSMETRICRESPCENTER

224OM_AU_ASSOBJECTIVEINITIATIVE

224OM_AU_ASSOBJECTIVELOBJECTIVE

225OM_AU_ASSOBJECTIVEMETRIC 226OM_AU_ASSOBJECTIVERESPCENTER

227OM_AU_BOUNDARYINFO 268OM_AU_EMPLOYEEB 269OM_AU_EMPLOYEEBOUNDARY 270OM_AU_ICONVALUE 271OM_AU_INITIATIVE_DETAIL 272OM_AU_METRICACTUAL 273OM_AU_METRICADJUSTMENT 274OM_AU_METRICADJUSTTARGET

275OM_AU_METRICBOUNDARY 278OM_AU_METRICTARGET 279OM_AU_OBJECTIVEACTUAL 280OM_AU_OBJECTIVEADJUSTMENT

281OM_AU_OBJECTIVEADJUSTTARGET

282OM_AU_OBJECTIVEB 283OM_AU_OBJECTIVEBASEPOINT 284OM_AU_OBJECTIVEBOUNDARY 285OM_AU_OBJECTIVEMETRICWEIGHTING

286OM_AU_OBJECTIVETARGET 287OM_AU_OBJECTIVEWEIGHTING 288OMR_EMPLOYEERESULTVALUE

182OMR_METRICRESULTVALUE 183OMR_OBJECTIVERESULTVALUE

184Oracle

Database Preparation 13Pre-installation Tasks 13Setting up a New Database 17Tablespace and User Creation 14Tablespace Setup and User Rights

13

2013-07-29294

Index

P

Performing a Data Load 40PP_AU_ACTIVITYDRIVERDELTA 228PP_AU_ACTIVITYDRIVERTARGET

229PP_AU_ACTIVITYDRIVERVALUE 230PP_AU_ACTIVITYREASSIGN 214PP_AU_ASSRESPCENTERACTIVITY

215PP_AU_BOMMAKEUP 232PP_AU_BOMPRODUCTION 233PP_AU_BOMUNITSSOLD 234PP_AU_COSTOBJECTASSIGNMENT

216PP_AU_COSTOBJECTDRIVER 217PP_AU_COSTOBJITEM 218PP_AU_CURRENCYRATES 235PP_AU_DAVERSION 236PP_AU_DEFAULTBOMMAKEUP 237PP_AU_EMPLOYEERDS 242PP_AU_EXTERNALACTIVITYVALUE

243PP_AU_EXTERNALBOMUNITRATE

238PP_AU_EXTERNALCOSTOBJECTVALUE

244PP_AU_HVACTIVITYDRIVERVOLUME

239PP_AU_HVCOSTOBJECTDRIVER

240PP_AU_HVEXTACTCOUNITRATE

241PP_AU_LINEITEMDELTA 246PP_AU_LINEITEMDETAILVALUE 247PP_AU_LINEITEMDIRECT_ACTIVITY

219PP_AU_LINEITEMFIXEDVALUE 248PP_AU_LINEITEMRESOURCEDRIVER

220PP_AU_LINEITEMVALUE 249PP_AU_LINEITEMVARVALUE 250PP_AU_LOCKRESULTS 251PP_AU_METADATA_VERSION 252PP_AU_RESOURCEDRIVERDELTA

252PP_AU_RESOURCEDRIVERDSPLIT

253PP_AU_RESOURCEDRIVERSPLIT

254PP_AU_RESOURCEDRIVERTARGET

255PP_AU_RESOURCEDRIVERTARSPLIT

256PP_AU_RESOURCEDRIVERVALUE

257

PP_AU_RESPCENTERSERVICE 223PP_AU_REVENUE 258PP_AU_SERVICEDIRECT_ACTIVITY

222PP_AU_SERVICEDRIVERDELTA 260PP_AU_SERVICEDRIVERTARGET

261PP_AU_SERVICEDRIVERVALUE 262PP_AU_SERVICEFACTOR 263PP_AU_SERVICERESOURCEDRIVER

221PP_AU_SPREADVALUE 264PP_AU_SUBSTITUTIONS 265PP_AU_USER_RULE 266PP_AU_WORKSHEETVALUE 267PPLOAD_#_DH 30PPLOAD_ACTIVITYDRIVERVALUE

Activity Driver Value 84PPLOAD_BOMMAKEUP 85PPLOAD_DEFAULTBOMMAKEUP 89PPLOAD_EXTERNALBOMUNITRATE

91PPR_#DIMENSION_NAME#_BRIDGE

135PPR_#DIMENSION_NAME#_NODEITEMS

137PPR_ACTCOSTOBJECTVALUE 123PPR_ACTIVITYLINEITEMVALUE 124PPR_ACTIVITYVALUE 125PPR_ACTREASSIGNSPLITVALUE

126PPR_APRIMARYACTIVITYDRIVER

127PPR_BOMRESULT 128PPR_BOMUNITRATE 129PPR_CONTRIBUTION 132PPR_COSTOBJECTVALUE 133PPR_DCOSTOBJECTVALUE 134PPR_DPRIMARYACTIVITYDRIVER

139PPR_DSERVICECOSTOBJECTVALUE

139PPR_DSPRIMARYACTIVITYDRIVER

140PPR_EXTERNALACTIVITYVALUE

141PPR_EXTERNALCOSTOBJECTVALUE

142PPR_HVACTIVITYDRIVERMAPPING

143PPR_HVBREAKDOWN 145PPR_HVBREAKDOWNDETAILCOST

146PPR_HVDETAILCOST 147PPR_HVLIUNITRATE 148PPR_HVUNITRATE 149

PPR_LICOSTOBJECTVALUE 150PPR_NODE_LEVEL 151PPR_POSTREASSIGNLINEITEMVALUE

152PPR_RBACTIVITYDRIVERVALUE153PPR_RBBOMMAKEUP 130PPR_RBBOMPRODUCTION 131PPR_RBBOMUNITSSOLD 131PPR_RBCURRENCYRATES 154PPR_RBEMPLOYEERDS 155PPR_RBEXTERNALBOMUNITRATE

157PPR_RBHVEXTACTCOUNITRATE

156PPR_RBLINEITEMDETAILVALUE 158PPR_RBLINEITEMFIXEDVALUE 159PPR_RBLINEITEMVALUE 160PPR_RBLINEITEMVARVALUE 160PPR_RBRESOURCEDRIVERSPLIT

161PPR_RBRESOURCEDRIVERVALUE

162PPR_RBREVENUE 163PPR_RBSERVICEDRIVERVALUE 164PPR_RBSERVICEFACTOR 165PPR_RBSPREADVALUE 166PPR_RBWORKSHEETVALUE 166PPR_REASSACTLINEITEMVALUE

167PPR_REASSACTSERVICEVALUE

168PPR_REASSIGNTRACE 169PPR_SCOSTOBJECTVALUE 172PPR_SERVICEACTIVITYVALUE 170PPR_SERVICECOSTOBJECTVALUE

171PPR_SERVICEVALUE 172PPR_SOURCEACTLINEITEMVALUE

173PPR_SPRIMARYACTIVITYDRIVER

174PPR_SUMACTIVITYVALUE 175PPR_SUMCOSTOBJECTVALUE 176PPR_SUMMARYMOVEMENTVALUE

177PPR_SUMSERVICEACTIVITYVALUE

178PPR_TARGETCOSTOBJECTVALUE

179PPR_TOTCOSTOBJECTVAULE 180PPR_TRACEBACKVALUE 181Property Data Load 34Property Item Value Data Load 34Property Procedures and Packages 34

2013-07-29295

Index

R

Resource Driver SplitPPLOAD_RESOURCEDRIVERSPLIT

99Resource Driver Value

PPLOAD_RESOURCEDRIVERVALUE100

Resource Drivers Line ItemsAssignment 77

Resource Drivers Services AssignmentPPLOAD_SERVICERESOURCEDRIVER

78Responsibility Centers Activities

AssignmentPPLOAD_ASSRESPCENTERACTIVITY

73Restoring the Database 55Restrictions 11Results Tables

About 122Results Views 187

RevenuePPLOAD_REVENUE 101

Running Data Loader Remotely 20

S

Service Driver ValuePPLOAD_SERVICEDRIVERVALUE

102Service Factor

PPLOAD_SERVICEFACTOR 103Services Resource Drivers Assignment

OverridesPPLOAD_SERVICEDIRECT_ACTIVITY

78Services Responsibility Centers

PP_RESPCENTERSERVICE 79Spread Value

PPLOAD_SPREADVALUE 104Stage Table Management 45

Structural Procedures and Packages29

Supported Versions 11

T

Transforming Data from an ExistingModel 43

Troubleshooting Data Loader 46

V

Value Data Load 40Value Procedures and Packages 37Value Tables 84

W

Work Sheet ValuePPLOAD_WORKSHEETVALUE

104

2013-07-29296

Index

Pcm 10 Database En

Documents

Transcript of Pcm 10 Database En