oracle business analytics warehouse data model reference version 7.9.5

Oracle

Business Analytics Warehouse

Data Model Reference Version 7.9.5

The Oracle Business Analytics Warehouse Data Model Reference comprises three distinct pieces:

The Oracle Business Analytics Warehouse Naming Conventions and Domain Values Guide, Version 7.9.5

The star schema diagrams The table and column descriptions

Oracle Business Analytics WarehouseNaming Conventions and Domain Values Guide

Version 7.9.5

E12088-01

May 2008

Oracle Business Analytics Warehouse Naming Conventions and Domain Values Guide Version 7.9.5.

E12088-01

Copyright 2008, Oracle. All rights reserved.

The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.

The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.

Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.

iii

Contents

Preface ................................................................................................................................................................. vAudience....................................................................................................................................................... viDocumentation Accessibility ..................................................................................................................... viRelated Documents ..................................................................................................................................... viConventions ................................................................................................................................................. vi

1 What's New in This Release1.1 What's New in Oracle Business Analytics Warehouse Naming Conventions and Domain

Values Guide, Version 7.9.5 1-1

2 Oracle Business Analytics Warehouse Naming Conventions2.1 Naming Conventions for Oracle Business Analytics Warehouse Tables ........................... 2-12.2 Table Types for Oracle Business Analytics Warehouse ........................................................ 2-22.2.1 Staging Tables in Oracle Business Analytics Warehouse .............................................. 2-32.2.2 Fact Tables in Oracle Business Analytics Warehouse .................................................... 2-32.2.3 Aggregate Tables in Oracle Business Analytics Warehouse ......................................... 2-32.2.4 Dimension Tables in Oracle Business Analytics Warehouse ........................................ 2-32.2.5 Dimension Class Tables in Oracle Business Analytics Warehouse.............................. 2-32.2.6 Dimensional Tables With Business Role-Based Flags .................................................... 2-42.2.7 Subset Dimension Tables in Oracle Business Analytics Warehouse............................ 2-42.2.8 Mini-Dimension Tables in Oracle Business Analytics Warehouse .............................. 2-42.2.9 Hierarchy Tables in Oracle Business Analytics Warehouse.......................................... 2-52.2.10 Helper Tables in Oracle Business Analytics Warehouse ............................................... 2-52.3 Internal Tables in Oracle Business Analytics Warehouse..................................................... 2-52.4 Standard Column Prefixes in Oracle Business Analytics Warehouse................................. 2-72.5 Standard Column Suffixes in Oracle Business Analytics Warehouse................................. 2-72.6 System Columns in Oracle Business Analytics Warehouse Tables..................................... 2-72.7 Currency Codes for Related System Columns ....................................................................... 2-82.8 Code Pairs for Related System Columns................................................................................. 2-92.9 Data Security Design in Oracle Business Analytics Warehouse .......................................... 2-92.10 Oracle Business Analytics Warehouse Primary Data Values............................................ 2-102.11 Supported List of Values in Oracle Business Analytics Warehouse ................................ 2-102.11.1 Data Sourced from Siebel Transactional Databases .................................................... 2-102.11.2 Data Sourced from Non-Siebel Sources......................................................................... 2-112.12 Oracle Business Analytics Warehouse Currency Conversion........................................... 2-11

iv

3 Oracle Business Analytics Warehouse Domain Values3.1 Overview of Domain Values ..................................................................................................... 3-13.2 W_BUSN_LOCATION_D Domain Values ............................................................................. 3-23.3 W_CHNL_TYPE_D Domain Values ........................................................................................ 3-23.4 W_DAY_D (and Other Calendar Tables) Domain Values.................................................... 3-33.5 W_EMPLOYMENT_D Domain Values ................................................................................... 3-43.6 W_EMPLOYEE_D Domain Values .......................................................................................... 3-53.7 W_EVENT_TYPE_D Domain Values ...................................................................................... 3-63.7.1 Contact Center Events in the W_EVENT_TYPE_D Table ............................................. 3-63.7.2 HR Events in the W_EVENT_TYPE_D Table .................................................................. 3-73.8 W_EXPENSE_F Domain Values ............................................................................................... 3-83.9 W_GL_ACCOUNT_D Domain Values.................................................................................... 3-93.10 W_HR_POSITION_D Domain Values.................................................................................. 3-113.11 W_JOB_D Domain Values ...................................................................................................... 3-113.12 W_MVMNT_TYPE_D Domain Values................................................................................. 3-123.13 W_PAYMENT_METHOD_D Domain Values..................................................................... 3-123.14 W_PAY_TYPE_D Domain Values......................................................................................... 3-133.15 W_PERSON_D Domain Values............................................................................................. 3-133.16 W_PRODUCT_XACT_F Domain Values ............................................................................. 3-133.17 W_PRODUCT_D Domain Values ......................................................................................... 3-143.18 W_REASON_D Domain Values ............................................................................................ 3-143.19 W_STATUS_D Domain Values.............................................................................................. 3-143.20 W_XACT_TYPE_D Domain Values ...................................................................................... 3-18

Index

vPreface

Oracle Business Intelligence Applications Fusion Edition (Oracle BI Applications) are comprehensive prebuilt solutions that deliver pervasive intelligence across an organization, empowering users at all levels with the key information they need to maximize effectiveness. Oracle BI Applications are built on Oracle Business Intelligence Suite Enterprise Edition, a comprehensive next-generation BI and analytics platform.

Oracle BI Applications includes the following application families:

Oracle Financial Analytics Fusion Edition

Oracle Human Resources Analytics Fusion Edition

Oracle Supply Chain and Order Management Analytics Fusion Edition

Oracle Procurement and Spend Analytics Fusion Edition

Oracle Sales Analytics Fusion Edition

Oracle Service Analytics Fusion Edition

Oracle Contact Center Telephony Analytics Fusion Edition

Oracle Marketing Analytics Fusion Edition

Oracle Partner Analytics Fusion Edition

Oracle Pricing Analytics Fusion Edition

The Oracle Business Analytics Warehouse Naming Conventions and Domain Values Guide contains information about the data structures in the Oracle Business Analytics Warehouse that store data for reporting purposes. The information provided includes data modeling concepts, nomenclature, table and column descriptions, and star schema diagrams.

Oracle recommends reading the Oracle Business Intelligence Applications Fusion Edition Release Notes before installing, using, or upgrading Oracle Business Intelligence Applications. The Oracle Business Intelligence Applications Fusion Edition Release Notes are available:

On the Oracle Business Intelligence Applications CD-ROM.

On the Oracle Technology Network at http://www.oracle.com/technology/documentation/bi_apps.html (to register for a free account on the Oracle Technology Network, go to http://www.oracle.com/technology/about/index.html).

vi

AudienceThis document is intended for data warehouse administrators and ETL developers and operators.

Documentation AccessibilityOur goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at

http://www.oracle.com/accessibility

Accessibility of Code Examples in DocumentationScreen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in DocumentationThis documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

TTY Access to Oracle Support ServicesOracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.

Related DocumentsFor more information, see the following documents in the Oracle Business Intelligence Applications Release 7.9.5 documentation set (available at http://www.oracle.com/technology/documentation/bi_apps.html):

Oracle Business Intelligence Applications Fusion Edition Release Notes

System Requirements and Supported Platforms for Oracle Business Intelligence Applications Fusion Edition

Oracle Business Intelligence Applications Fusion Edition Installation and Configuration Guide

Oracle Business Intelligence Infrastructure Installation and Configuration Guide

Oracle Business Intelligence Applications Fusion Edition Upgrade Guide

ConventionsThe following text conventions are used in this document:

vii

Convention Meaningboldface Boldface type indicates graphical user interface elements associated

with an action, or terms defined in text or the glossary.

italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1What's New in This Release 1-1

1What's New in This Release

This section lists changes described in this version of the documentation to support release 7.9.5 of the software.

1.1 What's New in Oracle Business Analytics Warehouse Naming Conventions and Domain Values Guide, Version 7.9.5

This guide includes the following changes:

The names of some of the Oracle BI Applications were updated in Chapter 3, "Oracle Business Analytics Warehouse Domain Values."

The domain values were updated in Chapter 3, "Oracle Business Analytics Warehouse Domain Values."

What's New in Oracle Business Analytics Warehouse Naming Conventions and Domain Values Guide, Version 7.9.5

1-2 Naming Conventions and Domain Values Guide

2Oracle Business Analytics Warehouse Naming Conventions 2-1

2Oracle Business Analytics WarehouseNaming Conventions

This chapter includes information on the types of tables and columns in the Oracle Business Analytics Warehouse, including the naming conventions used.

This chapter contains the following topics:

Section 2.1, "Naming Conventions for Oracle Business Analytics Warehouse Tables"

Section 2.2, "Table Types for Oracle Business Analytics Warehouse"

Section 2.3, "Internal Tables in Oracle Business Analytics Warehouse"

Section 2.4, "Standard Column Prefixes in Oracle Business Analytics Warehouse"

Section 2.5, "Standard Column Suffixes in Oracle Business Analytics Warehouse"

Section 2.6, "System Columns in Oracle Business Analytics Warehouse Tables"

Section 2.7, "Currency Codes for Related System Columns"

Section 2.8, "Code Pairs for Related System Columns"

Section 2.9, "Data Security Design in Oracle Business Analytics Warehouse"

Section 2.10, "Oracle Business Analytics Warehouse Primary Data Values"

Section 2.11, "Supported List of Values in Oracle Business Analytics Warehouse"

Section 2.12, "Oracle Business Analytics Warehouse Currency Conversion"

2.1 Naming Conventions for Oracle Business Analytics Warehouse Tables

Oracle Business Analytics Warehouse tables use a three-part naming convention: PREFIX_NAME_SUFFIX, as shown in Table 21.

Table 21 Naming Conventions for Oracle Business Analytics Data Warehouse TablesPart Meaning Table TypePREFIX Shows Oracle Business

Analytics-specific data warehouse application tables.

W_ = Warehouse

NAME Unique table name. All tables.

Table Types for Oracle Business Analytics Warehouse


2.2 Table Types for Oracle Business Analytics WarehouseTable 22 lists the types of tables used by the Oracle Business Analytics Warehouse.

SUFFIX Indicates the table type. _A = Aggregate_D = Dimension_DS = Staging for dimension_DH = Dimension Hierarchy_DHL = Dimension Helper Table_DHLS = Staging for Dimension Helper_F = Fact_FS = Staging for Fact_G, _GS, _S = Internal Table_H Helper table_M = Map dimension_MD = Mini dimension_UD = Unbounded dimension_TMP = Pre staging temporary table

Table 22 Table Types Used by the Oracle Business Analytics WarehouseTable Type Description

Aggregate tables (_A) Contain summed (aggregated) data.

Dimension tables (_D) Star analysis dimensions.

Staging tables for Dimension (_DS) Tables used to hold dimension information that have not been through the final ETL transformations.

Staging tables for Usage Accelerator (WS_)

Tables containing the necessary columns for the ETL transformations.

Dimension Hierarchy tables (_DH) Tables that store the dimension's hierarchical structure.

Dimension Helper tables (_DHL) Tables that store M:M relationships between two joining dimension tables.

Staging tables for Dimension Helper (_DHLS)

Tables used to hold dimension helper information that has not been through the final ETL transformations.

Fact tables (_F) Contain the information being analyzed by dimensions.

Fact Staging tables (_FS) Tables used to hold fact information that has not been through the final ETL transformations.

Internal tables (_G, _GS, _S) Internal tables are used primarily by ETL mappings for data transformation and controlling ETL runs.

Helper tables (_H) Helper tables are inserted between the fact and dimension tables to support a many-to-many (M:M) relationship between fact and dimension records.

Map dimension tables (_M) Tables that store cross-referencing mappings between the external data ID and the internal ID.

Mini dimension tables (_MD) Include combinations of the most queried attributes of their parent dimensions. The database joins these small tables to the fact tables.

Unbounded dimension tables Tables containing information that is not bounded in transactional database data but should be treated as bounded data in the Oracle Business Analytics Warehouse.

Table 21 (Cont.) Naming Conventions for Oracle Business Analytics Data Warehouse Part Meaning Table Type


Oracle Business Analytics Warehouse Naming Conventions 2-3

2.2.1 Staging Tables in Oracle Business Analytics WarehouseStaging tables are used primarily to stage incremental data from the transactional database. When the ETL process runs, staging tables are truncated before they are populated with change capture data. During the initial full ETL load, these staging tables hold the entire source data set for a defined period of history, but they hold only a much smaller volume during subsequent refresh ETL runs.

This staging data (list of values translations, computations, currency conversions) is transformed and loaded to the dimension and fact staging tables. These tables are typically tagged as _DS or _FS. The staging tables for the Usage Accelerator are tagged as WS_.

The staging table structure is independent of source data structures and resembles the structure of data warehouse tables. This resemblance allows staging tables to be used also as interface tables between the transactional database sources and data warehouse target tables.

2.2.2 Fact Tables in Oracle Business Analytics WarehouseEach fact table contains a unique numeric key (ROW_WID) that is generated during the load process. This key is used to join a fact table with its corresponding extension table. Each fact table also contains one or more numeric foreign key columns to link it to various dimension tables.

2.2.3 Aggregate Tables in Oracle Business Analytics WarehouseOne of the main uses of a data warehouse is to sum up fact data with respect to a given dimension, for example, by date or by sales region. Performing this summation on the fly is resource-intensive, and slows down response time. The Oracle Business Analytics Warehouse precalculates some of these sums and stores the information in aggregate tables. In the Oracle Business Analytics Warehouse, the aggregate tables have been suffixed with _A.

2.2.4 Dimension Tables in Oracle Business Analytics WarehouseThe unique numeric key (ROW_WID) for each dimension table is generated during the load process. This key is used to join each dimension table with its corresponding fact table or tables. It is also used to join the dimension with any associated hierarchy table or extension table. The ROW_WID columns in the Oracle Business Analytics Warehouse tables are numeric. In every dimension table, the ROW_WID value of zero is reserved for Unspecified. If one or more dimensions for a given record in a fact table is unspecified, the corresponding key fields in that record are set to zero.

2.2.5 Dimension Class Tables in Oracle Business Analytics WarehouseA class table is a single physical table that can store multiple logical entities that have similar business attributes. Various logical dimensions are separated by a separator column, such as, type or category. W_XACT_TYPE_D is an example of a dimension class table. Different transaction types, such as, sales order types, sales invoice types, purchase order types, and so on, can be housed in the same physical table.

You can add additional transaction types to an existing physical table and so reduce the effort of designing and maintaining new physical tables. However, while doing so, you should consider that attributes specific to a particular logical dimension cannot be defined in this physical table. Also, if a particular logical dimension has a large



number of records, it might be a good design practice to define a separate physical table for that particular logical entity.

2.2.6 Dimensional Tables With Business Role-Based FlagsThis design approach is used when the entity is logically the same but participates as different roles in the business process. As an example, an employee could participate in an HR business process as an employee, in the sales process as a sales representative, in the receivables process as a collector, and in the purchase process as a buyer. However, the employee is still the same. For such logical entities, flags have been provided in the corresponding physical table to describe the record's participation in business as different roles. While configuring the presentation layer, the same physical table can be used as a specific logical entity by flag-based filters. For example, if a particular star schema requires Buyer as a dimension, the Employee table can be used with a filter where the Buyer flag is set to Y.

2.2.7 Subset Dimension Tables in Oracle Business Analytics WarehouseThe Oracle Business Analytics Warehouse contains subset dimension tables, which are extracted from dimension tables using a filter on a particular attribute of the parent dimension table. In other words, the subset dimension tables contain all the columns of the parent dimension table. Subset dimension tables are primarily used in conjunction with aggregate tables.

Table 23 lists the subset dimension tables in the Oracle Business Analytics Warehouse.

2.2.8 Mini-Dimension Tables in Oracle Business Analytics WarehouseMini-dimension tables include combinations of the most queried attributes of their parent dimensions. They improve query performance because the database does not need to join the fact tables to the big parent dimensions but can join these small tables to the fact tables instead.

Table 24 lists the mini-dimension tables in the Oracle Business Analytics Warehouse.

Table 23 Subset Dimension Tables in Oracle Business Analytics Warehouse

Table Name SubsetW_COMPETITOR_D Competitor Organizations

W_PROD_LN_D Product Line

W_IND_VERT_D Industry Vertical

W_CTRY_REGN_D Country Region

W_PRG_PROGRAM_D Programs

W_PRG_CAMP_D Campaigns

Table 24 Mini-Dimension Tables in Oracle Business Analytics Warehouse

Table Name Parent Dimension

W_RESPONSE_MD Parent W_RESPONSE_D

W_AGREE_MD Parent W_RESPONSE_D

W_ASSET_MD Parent W_RESPONSE_D

W_OPTY_MD Parent W_RESPONSE_D

W_ORDER_MD Parent W_RESPONSE_D

Internal Tables in Oracle Business Analytics Warehouse


2.2.9 Hierarchy Tables in Oracle Business Analytics WarehouseSome dimension tables have hierarchies into which each record rolls. This hierarchy information is stored in a separate table, with one record for each record in the corresponding dimension table. This information allows users to drill up and down through the hierarchy in reports.

There are two types of hierarchies in the Oracle Business Analytics Warehouse: a structured hierarchy in which there are fixed levels, and a hierarchy with parent-child relationships. Structured hierarchies are simple to model, since each child has a fixed number of parents and a child cannot be a parent. The second hierarchy, with unstructured parent-child relationships is difficult to model because each child record can potentially be a parent and the number of levels of parent-child relationships is not fixed. Hierarchy tables have a suffix of _DH.

2.2.10 Helper Tables in Oracle Business Analytics WarehouseHelper tables are used by the Oracle Business Analytics Warehouse to solve complex problems that cannot be resolved by simple dimensional schemas.

In a typical dimensional schema, fact records join to dimension records with a many-to-one relationship. To support a many-to-many relationship between fact and dimension records, a helper table is inserted between the fact and dimension tables.

The helper table can have multiple records for each fact and dimension key combination. This allows queries to retrieve facts for any given dimension value. It should be noted that any aggregation of fact records over a set of dimension values might contain overlaps (due to a many-to-many relationship) and can result in double counting.

At times there is a requirement to query facts related to the children of a given parent in the dimension by only specifying the parent value (example: manager's sales fact that includes sales facts of the manager's subordinates). In this situation, one helper table containing multiple records for each parent-child dimension key combination is inserted between the fact and the dimension. This allows queries to be run for all subordinates by specifying only the parent in the dimension.

2.3 Internal Tables in Oracle Business Analytics WarehouseInternal tables are used primarily by ETL (extract-transform-load) mappings for data transformation and for controlling ETL runs. These tables are not queried by end users and are not directly managed by the Data Warehouse Administration Console (DAC). These tables are described in Table 25.

W_QUOTE_MD Parent W_RESPONSE_D

W_SRVREQ_MD Parent W_RESPONSE_D

Table 25 Oracle Business Analytics Warehouse Internal TablesName Purpose Location

W_PARAM_G Stores parameters and defaults that are used in ETL processes.

Data warehouse

W_DUAL_G Used to generate records for the Day dimension. Data warehouse

Table 24 (Cont.) Mini-Dimension Tables in Oracle Business Analytics WarehouseTable Name Parent Dimension

Internal Tables in Oracle Business Analytics Warehouse


W_ETL_RUN_S Stores a record for every ETL run with a status of Running when the ETL is running and Completed when the ETL finishes successfully.

Data warehouse

W_COSTLST_G Stores cost lists. Data warehouse

W_EXCH_RATE_G Stores exchange rates. Data warehouse

W_LOV_G Stores lists of values in a way that translations can be done effectively using SQL.

Data warehouse

W_LST_OF_VAL_G Stores the list of values. A temporary table that is built during every ETL run and used to populate W_LOV_D.

Data warehouse

W_LOV_EXCPT_G Stores the list of values for the LOV types in which the ETL process finds exceptions.

Data warehouse

S_ETL_COSTLST Mirror table of W_COST_LST_G. Used by real-time Analytics processes.

Transactional database

S_ETL_EXCH_RATE Mirror table of W_COST_LST_G. Used by real-time Analytics processes.


S_ETL_CTRYREGN Mirror table of W_EXCH_RATE_G. Used by real-time Analytics processes.


S_ETL_CURR_RUN Stores the last ETL run date for which forecasts were extracted and the current ETL run date when forecasts are being extracted.


S_ETL_RUN Mirror table of W_ETL_RUN_S. Transactional database

S_ETL_TIME_DAY A seeded table. The date from this table is extracted and loaded into W_TIME_DAY_D. Also used by real-time Analytics processes.


S_ETL_DAY Mirror table of W_DAY_D. Used by real-time Analytics processes.


S_ETL_ERRHLP A seeded table. Stores the error messages displayed in exception reports.


S_ETL_ERRLOG Stores exceptions. Transactional database

S_ETL_INDUS_VER A seeded table. Stores the vertical for every SIC industry code. This table is used to load W_INDUSTRY_D and also used in real-time Analytics processes.


S_ETL_LOV Mirror table of W_LOV_D. Used by real-time Analytics processes.


S_ETL_PARAM Mirror table of W_PARAM_G. Used to extract and convert exchange rates to the data warehouse's currency.


S_ETL_PRD_ATTR Stores all possible attributes for a given product. Transactional database

S_ETL_PRD_REL Stores class inheritance of a product. Transactional database

Table 25 (Cont.) Oracle Business Analytics Warehouse Internal TablesName Purpose Location

System Columns in Oracle Business Analytics Warehouse Tables


2.4 Standard Column Prefixes in Oracle Business Analytics WarehouseThe Oracle Business Analytics Warehouse uses a standard prefix to indicate fields that must contain specific values, as shown in Table 26.

2.5 Standard Column Suffixes in Oracle Business Analytics WarehouseThe Oracle Business Analytics Warehouse uses suffixes to indicate fields that must contain specific values, as shown in Table 27.

2.6 System Columns in Oracle Business Analytics Warehouse TablesOracle Business Analytics Warehouse tables contain system fields. These system fields are populated automatically and should not be modified by the user. Table 28 lists system columns used in dimension tables. Table 28 lists system columns used in fact tables.

Table 26 Standard Column PrefixPrefix Description In Table Types

W_ Domain value columns _D

Table 27 Standard Column SuffixesSuffix Description In Table Types_CD Code field. _D, _DS, _FS, _G, _GS

_DT Date field. _D, _DS, _FS, _G, _DHL, _DHLS

_I Language Independent Code.

In the transactional database, list of value (LOV) information is stored with both language-independent and display values. A Language Independent Code column references the language-independent LOV, which may be different from the displayed value in both the transactional system and the data warehouse.

_D, _MD

_FLG Indicator or Flag. _D, _DHL, _DS, _FS, _F, _G, _DHLS

_WID Identifier generated by Oracle BI linking dimension and fact tables, except for ROW_WID.

_F, _A, _DHL

_NAME Name corresponding to the code column (columns ending with _CODE)

_D, _F, _A

_DESC Long Description corresponding to the code column (columns ending with _CODE)

_D, _F, _A

Table 28 System Columns Used in Fact TablesSystem Column Description

ROW_WID Surrogate key to identify a record uniquely.

CREATED_BY_WID Foreign key to the W_USER_D dimension that specifies the user who created the record in the source system.

CHANGED_BY_WID Foreign key to the W_USER_D dimension that specifies the user who last modified the record in the source system.

Currency Codes for Related System Columns


2.7 Currency Codes for Related System ColumnsTable 29 lists the currency codes for related system columns.

CREATED_ON_DT The date and time when the record was initially created in the source system.

CHANGED_ON_DT The date and time when the record was last modified in the source system.

AUX1_CHANGED_ON_DT System field. This column identifies the last modified date and time of the auxiliary table's record that acts as a source for the current table.




DELETE_FLG This flag indicates the deletion status of the record in the source system. A value of Y indicates the record is deleted from the source system and logically deleted from the data warehouse. A value of N indicates that the record is active.

W_INSERT_DT Stores the date on which the record was inserted in the data warehouse table.

W_UPDATE_DT Stores the date on which the record was last updated in the data warehouse table.

DATASOURCE_NUM_ID Unique identifier of the source system from which data was extracted. In order to be able to trace the data back to its source, it is recommended that you define separate unique source IDs for each of your different source instances.

ETL_PROC_WID System field. This column is the unique identifier for the specific ETL process used to create or update this data.

INTEGRATION_ID Unique identifier of a dimension or fact entity in its source system. In case of composite keys, the value in this column can consist of concatenated parts.

TENANT_ID Unique identifier for a tenant in a multi-tenant environment. This column is typically be used in an Application Service Provider (ASP)/Software As a Service (SOAS) model.

X_CUSTOM Column used as a generic field for customer extensions.

Table 29 Currency Codes for Related System ColumnsSystem Column Description

DOC_CURR_CODE Code for the currency in which the document was created in the source system.

LOC_CURR_CODE Usually the reporting currency code for the financial company in which the document was created.

Table 28 (Cont.) System Columns Used in Fact TablesSystem Column Description

Data Security Design in Oracle Business Analytics Warehouse


2.8 Code Pairs for Related System ColumnsTable 210 lists the code pairs for related system columns. The code pair fields can be generated in the warehouse or sourced from the source tables.

2.9 Data Security Design in Oracle Business Analytics WarehouseThe Oracle Business Analytics Warehouse maintains ten security groups, which are assigned dynamically to every user at the session level. Each security group has a set of filters associated with it that determines the data each user is allowed to see. A user is assigned a security group through the Authorization initialization block.

The data security design has the following features:

Drill down. The user can drill down on a particular position in the position hierarchy to slice the data by the next position level in the hierarchy. For example, if the initial report is defined as:

select Top Level Position, Revenue from RevenueStar

then by drilling down on a value of MyPosition in the TopLevelPosition hierarchy, the report will become:

Select Level8 Position, Revenue, where TopLevelPosition = 'MyPosition'

Personalized reports. Users at different levels of the Position hierarchy can use the same Position-based reports but with each user seeing the data corresponding to his or her level. In such reports, Position is a dynamic column.

For example, if a report is defined as:

GRP_CURR_CODE The primary group reporting currency code for the group of companies or organizations in which the document was created.

GRP1_CURR_CODE Secondary Group reporting Currency code for the group of companies or organizations in which the document was created.

GRP2_CURR_CODE Secondary Group reporting Currency code for the group of companies or organizations in which the document was created.

LOC_EXCHANGE_RATE Currency conversion rate from the document currency code to the local currency code.

GRP1_EXCHANGE_RATE Currency conversion rate from the document currency code to the primary group currency code.

GRP2_EXCHANGE_RATE Currency conversion rate from the document currency code to the Group (GRP1) currency code.

GRP2_EXCHANGE_RATE Currency conversion rate from document currency code to the Group (GRP2) currency code.

Table 210 Code Pairs for Related System ColumnsField Description

CODE field A coded alphanumeric value that defines a possible value for a data element.

NAME field A short name that describes the code.

DESC field A long description for the code.

Table 29 (Cont.) Currency Codes for Related System ColumnsSystem Column Description

Oracle Business Analytics Warehouse Primary Data Values


select Position, Revenue from RevenueStar

the logical query for the user at the top level of the hierarchy will be:

select Top Level Position, Revenue from RevenueStar

The logical query for the user at the next level of the hierarchy will be:

select Level8 Position, Revenue from RevenueStar

CURRENT Position hierarchy columns. Position hierarchy columns with the prefix CURRENT contain the Current Position hierarchy at any point of time. This feature allows users to see the same data associated with the employee holding the Current Employee position at the time the report runs. This type of Analysis is called As Is.

Additional Position hierarchy columns. The columns EMP_LOGIN and EMPLOYEE_FULL_NAME are used at every level of the Position hierarchy to store additional information about an employee holding a particular position. In the Logical layer, the Employee path and Position path are two drill down paths under the Position hierarchy that allow the user to drill down on a position to see all positions under it. It also allows an employee to see all the employees reporting to him or her.

2.10 Oracle Business Analytics Warehouse Primary Data ValuesThe Oracle Business Analytics Warehouse performs many analyses on multi-value data fields such as Industry, Competitor, and Sales Representative. An opportunity could have multiple values of these three fields associated with it.

For example, several of your sales representatives could be working on an opportunity that has an account belonging to several different industries. In such situations, the Oracle Business Analytics Warehouse considers only the Primary Competitor, Primary Sales Representative, and Primary Industry fields.

While this limits the analysis you can perform with Oracle Business Analytics Warehouse, it also eliminates potential double counting problems. For example, if five sales representatives working on an opportunity were attributed with its closed revenue, the Oracle Business Analytics Warehouse would report five times as much revenue as was actually involved with that opportunity.

There are a few important exceptions to this rule. The Person star supports a many-to-many relationship between Contacts and Accounts. Therefore, when querying the Person star on both Accounts and Contacts, every combination of Account and Contact is returned. The Opportunity-Competitor star supports a many-to-many relationship between Opportunities and Competitor Accounts, and the Campaign-Opportunity star supports a many-to-many relationship between Campaigns and Opportunities. In other stars, however, querying returns only the primary account for a given contact. \

2.11 Supported List of Values in Oracle Business Analytics WarehouseThis section discusses list of values usage in Oracle Business Analytics Warehouse.

2.11.1 Data Sourced from Siebel Transactional DatabasesFor data sourced from Siebel transactional databases, the List of Values dimension table stores the various lists of values used in the Siebel transactional database. The

Oracle Business Analytics Warehouse Currency Conversion


different value sets are distinguished by different values in the TYPE column. The Name column contains the language-independent value and the VAL column contains the corresponding language-specific value. The Oracle Business Analytics Warehouse only supports List of Values that have unique TYPE and VAL and unique TYPE and NAME for a particular language. SUB_TYPES are not accounted for. Every row in this dimension table uses a unique ROW_WID key to join it with fact tables.

Some values are available in different languages and the translated values are available to the user in his or her own language. The transactional database also keeps a language-independent string in the list of value tables.

Special attribute columns in dimension tables hold information coming from source fields in the transactional database that use lists of values. For each such attribute column, there exists a corresponding column with a name ending in _I. These columns hold the language-independent string for the corresponding language-dependent column. The language-dependent columns can be used in reports so that end users can see the data in their own language. The language-independent columns can be used in filtering WHERE clauses so that the query need not be translated for every language.

The lists of values are initially extracted into the W_LST_OF_VAL_G table and are loaded from there into the LOV dimension table.

The W_LST_OF_VAL_G table is purged and recreated during ETL loads, both full and incremental. The W_LOV_D dimension table is modified incrementally during refresh loads.

2.11.2 Data Sourced from Non-Siebel SourcesFor data sourced from non-Siebel transactional databases, the codes and their descriptions are converted to domain values. For a description of the supported domain values, see Chapter 3, "Oracle Business Analytics Warehouse Domain Values".

2.12 Oracle Business Analytics Warehouse Currency ConversionThe Oracle Business Analytics Warehouse supports the following currency types:

Document currency. The currency in which the transaction was done and the related document created.

Local currency. The accounting currency of the legal company in which the transaction occurred.

Group currency. The Oracle Business Analytics Warehouse stores up to three group currencies. These need to be preconfigured so as to allow global reporting by the different currencies. The exchange rates are stored in the table W_EXCH_RATE_G.

Oracle Business Analytics Warehouse Currency Conversion


3Oracle Business Analytics Warehouse Domain Values 3-1

3Oracle Business Analytics WarehouseDomain Values

This chapter provides a description of the domain values used by the Oracle Business Analytics Warehouse tables as well as the table columns that use domain values.

This section includes the following topics:

Section 3.1, "Overview of Domain Values"

Section 3.2, "W_BUSN_LOCATION_D Domain Values"

Section 3.3, "W_CHNL_TYPE_D Domain Values"

Section 3.4, "W_DAY_D (and Other Calendar Tables) Domain Values"

Section 3.5, "W_EMPLOYMENT_D Domain Values"

Section 3.6, "W_EMPLOYEE_D Domain Values"

Section 3.7, "W_EVENT_TYPE_D Domain Values"

Section 3.8, "W_EXPENSE_F Domain Values"

Section 3.9, "W_GL_ACCOUNT_D Domain Values"

Section 3.10, "W_HR_POSITION_D Domain Values"

Section 3.11, "W_JOB_D Domain Values"

Section 3.12, "W_MVMNT_TYPE_D Domain Values"

Section 3.13, "W_PAYMENT_METHOD_D Domain Values"

Section 3.14, "W_PAY_TYPE_D Domain Values"

Section 3.15, "W_PERSON_D Domain Values"

Section 3.16, "W_PRODUCT_XACT_F Domain Values"

Section 3.17, "W_PRODUCT_D Domain Values"

Section 3.18, "W_REASON_D Domain Values"

Section 3.19, "W_STATUS_D Domain Values"

Section 3.20, "W_XACT_TYPE_D Domain Values"

3.1 Overview of Domain ValuesDomain values are a set of distinct values used to calculate prepackaged metrics. These values are provided by Oracle Business Analytics Warehouse to allow you to create metric calculations independent of source system values.

W_BUSN_LOCATION_D Domain Values


This chapter provides a list of domain values used by Oracle Business Analytics Warehouse tables as well as the table columns that use domain values. The domain values provided in this appendix are by no means exhaustive. As you map particular source data to domain values, you may find that your source data does not map to one of the prepackaged domain values. You can add more domain values, but keep in mind that metric calculations may be affected.

3.2 W_BUSN_LOCATION_D Domain ValuesThis dimension table has a record for each business location.

Table 31 lists the domain values for the Business Locations dimension class table.

3.3 W_CHNL_TYPE_D Domain ValuesThe Channel Types dimension covers the methods by which contact paths are established between the customer and your organization. Channel type refers to any communication media that is used to broadcast messages or offers. This table stores different kinds of communication paths through a specific medium. Examples of channel types include direct mail or newspapers through print media, email through Web media, and Internet advertisements through Web media. This table can also store information about sales channels and servicing channels used by organizations. Sales channel examples include both direct and indirect channels used by an organization. This table also stores information about whether services provided to the customer were done through internal channels or through external (third party) channels.

Table 31 W_BUSN_LOCATION_D (Business Locations Dimension Class Table) Domain Values

BUSN_LOC_TYPE Business Name Description Source

CNTCT_CNTR Contact Center Location

Contact Center Location

Universal

COMPANY Company Location Company Location Oracle EBS, PeopleSoft

EMP_LOC Employee Location Employee Location Oracle EBS

LOADING_LOC Loading Location Loading Location SAP R/3

PLANT Plant Location Plant Location Oracle EBS, PeopleSoft

RECIPIENT_LOC Recipient Location Recipient Location Oracle EBS

SALES_OFFICE Sales Office Location Sales Office Location SAP R/3

SHIPPING_LOC Shipping Location Shipping Location SAP R/3

STORAGE_LOC Storage Location Storage Location Oracle EBS

Table 32 W_CHNL_TYPE_D (Channel Types Dimension Table) Domain ValuesField Value Domain Value Domain Value Business Name

W_CHTY_GRP_CODE CALL Call

W_CHTY_GRP_CODE CHAT Chat

W_CHTY_GRP_CODE EMAIL Email

W_CHTY_GRP_CODE DIRECT Direct

W_CHTY_GRP_CODE INDIRECT Indirect

W_DAY_D (and Other Calendar Tables) Domain Values

Oracle Business Analytics Warehouse Domain Values 3-3

Table 33 lists the relationship among W_CHTY_GRP_CODE, W_CHTY_SUBG_CODE, and W_INBOUND_TYPE_FLG.

3.4 W_DAY_D (and Other Calendar Tables) Domain ValuesAll the calendar tables in the Oracle Business Analytics Warehouse contain one or more columns to indicate the relationship between a record and the current system date (period). Each row will have one of four values for these columns:

Previous. Indicates that when compared to the system date (period), this row belongs to the immediate prior period.

Current. Indicates that when compared to the system date (period), this row belongs to the current period.

W_CHTY_GRP_CODE SALES_CHANNEL Sales Channel

W_INBOUND_TYPE_ FLG Y Direction - Inbound

W_INBOUND_TYPE_ FLG N Direction - Outbound

W_INBOUND_TYPE_ FLG X Direction - Undefined

W_CHTY_SUBG_ CODE AUTOMATIC Call - Automatic

W_CHTY_SUBG_ CODE IVR Call - Interactive voice response

W_CHTY_SUBG_ CODE MANUAL Call - Manual (Direction - Inbound/Outbound)

W_CHTY_SUBG_ CODE PARTNER Indirect - Partner (Direction - Undefined)

W_CHTY_SUBG_CODE RESELLER Indirect - Reseller (Direction - Undefined)

W_CHTY_SUBG_ CODE VAR Indirect - Value Added Reseller (Direction - Undefined)

Table 33 W_CHNL_TYPE_D Domain Value Relationships

W_CHTY_GRP_CODE W_CHTY_SUBG_CODE W_INBOUND_TYPE_FLGCALL AUTOMATIC N

CALL IVR Y

CALL MANUAL Y

CALL MANUAL N

CHAT Y

CHAT N

EMAIL Y

EMAIL N

INDIRECT PARTNER X

INDIRECT RESELLER X

INDIRECT VAR X

Table 32 (Cont.) W_CHNL_TYPE_D (Channel Types Dimension Table) Domain ValuesField Value Domain Value Domain Value Business Name

W_EMPLOYMENT_D Domain Values


Next. Indicates that when compared to the system date (period), this row belongs to the immediate next period.

?. This is the default value. It applies to all records whose relation to the system date (period) is none of the above.

These columns are updated whenever the incremental ETL process runs. Table 34 lists the calendar tables and the columns in those tables that take on the domain values listed above.

3.5 W_EMPLOYMENT_D Domain ValuesThis dimension contains the attributes for employment.

Table 35 lists the values for the Employee Category domain value for W_EMPLOYMENT_D.

Table 34 Calendar Columns and TablesCalendar Table Name Column Name Values Source

W_DAY_D W_CURRENT_CAL_DAY_CODE Previous, Current, Next, ? All

W_DAY_D W_CURRENT_CAL_MONTH_CODE Previous, Current, Next, ? All

W_DAY_D W_CURRENT_CAL_QTR_CODE Previous, Current, Next, ? All

W_DAY_D W_CURRENT_CAL_WEEK_CODE Previous, Current, Next, ? All

W_DAY_D W_CURRENT_CAL_YEAR_CODE Previous, Current, Next, ? All

W_DAY_D W_CURRENT_FSCL_MONTH_CODE Previous, Current, Next, ? All

W_DAY_D W_CURRENT_FSCL_QTR_CODE Previous, Current, Next, ? All

W_DAY_D W_CURRENT_FSCL_WEEK_CODE Previous, Current, Next, ? All

W_DAY_D W_CURRENT_FSCL_YEAR_CODE Previous, Current, Next, ? All

W_FSCL_WEEK_D W_CURRENT_FSCL_WEEK_CODE Previous, Current, Next, ? All

W_FSCL_WEEK_D W_CURRENT_FSCL_YEAR_CODE Previous, Current, Next, ? All

W_FSCL_MONTH_D W_CURRENT_FSCL_MONTH_CODE Previous, Current, Next, ? All

W_FSCL_MONTH_D W_CURRENT_FSCL_QTR_CODE Previous, Current, Next, ? All

W_FSCL_MONTH_D W_CURRENT_FSCL_YEAR_CODE Previous, Current, Next, ? All

W_FSCL_QTR_D W_CURRENT_FSCL_QTR_CODE Previous, Current, Next, ? All

W_FSCL_QTR_D W_CURRENT_FSCL_YEAR_CODE Previous, Current, Next, ? All

W_FSCL_YEAR_D W_CURRENT_FSCL_YEAR_CODE Previous, Current, Next, ? All

W_WEEK_D W_CURRENT_CAL_WEEK_CODE Previous, Current, Next, ? All

W_WEEK_D W_CURRENT_CAL_YEAR_CODE Previous, Current, Next, ? All

W_MONTH_D W_CURRENT_CAL_MONTH_CODE Previous, Current, Next, ? All

W_MONTH_D W_CURRENT_CAL_QTR_CODE Previous, Current, Next, ? All

W_MONTH_D W_CURRENT_CAL_YEAR_CODE Previous, Current, Next, ? All

W_QTR_D W_CURRENT_CAL_QTR_CODE Previous, Current, Next, ? All

W_QTR_D W_CURRENT_CAL_YEAR_CODE Previous, Current, Next, ? All

W_YEAR_D W_CURRENT_CAL_YEAR_CODE Previous, Current, Next, ? All

W_EMPLOYEE_D Domain Values


Table 36 lists the values for the Exempt Flag domain value for W_EMPLOYMENT_D.

Table 37 lists the values for the Employment Status domain value for W_EMPLOYMENT_D.

Table 38 lists the values for the Full Time Flag domain value for W_EMPLOYMENT_D.

3.6 W_EMPLOYEE_D Domain ValuesThis table contains all the attributes associated with employees of an organization.

Table 39 lists the Gender Group Code domain values for the Employees dimension table.

Table 35 Employee Category Domain Value (W_EMPLOYMENT_D)W_EMPLOYEE_CAT_CODE W_EMPLOYEE_CAT_DESC SourceCONTRACTOR CONTRACTOR Oracle EBS, PeopleSoft

DIRECT DIRECT Oracle EBS, PeopleSoft

INDIRECT INDIRECT Oracle EBS, PeopleSoft

OTHER OTHER Oracle EBS, PeopleSoft

REGULAR REGULAR Oracle EBS, PeopleSoft

TEMPORARY TEMPORARY Oracle EBS, PeopleSoft

Table 36 Exempt Flag Domain Value (W_EMPLOYMENT_D)W_EXEMPT_FLG SourceN Oracle EBS, PeopleSoft

Y Oracle EBS, PeopleSoft

Table 37 Employment Status Domain Value (W_EMPLOYMENT_D)W_EMPLOYMENT_STAT_CODE

W_EMPLOYMENT_STAT_DESC Source

A Active Oracle EBS, PeopleSoft

I Inactive Oracle EBS, PeopleSoft

Table 38 Full Time Flag Domain Value (W_EMPLOYMENT_D)W_FULL_TIME_FLG SourceN Oracle EBS, PeopleSoft


Table 39 Gender Group Code Domain Value Description (W_EMPLOYEE_D)W_SEX_MF_CODE W_SEX_MF_DESC Source

M Male Oracle EBS, PeopleSoft, Siebel

F Female Oracle EBS, PeopleSoft, Siebel

U Unknown Oracle EBS, PeopleSoft, Siebel

W_EVENT_TYPE_D Domain Values


Table 310 lists the Ethnic Group Code domain values for the Employees dimension table.

Table 311 lists the Veteran Status Code domain values for the Employees dimension table.

3.7 W_EVENT_TYPE_D Domain ValuesThe Event Types (W_EVENT_TYPE_D) dimension contains the possible event types for any activity that could take place. Oracle Business Analytics Warehouse prepackages certain event types, which you cannot customize. You must add customized event types using the category OTHERS.

3.7.1 Contact Center Events in the W_EVENT_TYPE_D TableThis section describes the domain values in the W_EVENT_TYPE_D table that are used in Contact Center Telephony Analytics. This module makes use of four different event classes:

REP ACTIVITY. This event class is used to mark the events supplied through the Universal adapter as Contact Representative Activities. These events are mapped into the Contact Rep Activity Type dimension.

CONTACT. This event class is used to mark the events supplied through the Universal adapter as Contact types. These events are mapped into the Call Type dimension.

Table 310 Ethnic Group Code Domain Value Description (W_EMPLOYEE_D)W_ETHNIC_GRP W_ETHNIC_GRP_DESC Source1 White (Not Hispanic or Latino) Oracle EBS, PeopleSoft

2 Black or African American (Not Hispanic or Latino)

Oracle EBS, PeopleSoft

3 Asian (Not Hispanic or Latino) Oracle EBS, PeopleSoft

4 American Indian or Alaskan Native (Not Hispanic or Latino)


5 Native Hawaiian or Other Pacific Islander (Not Hispanic or Latino)


6 Hispanic or Latino Oracle EBS, PeopleSoft

7 Two or more Races (Not Hispanic or Latino)


999 Not Specified Oracle EBS, PeopleSoft

Table 311 Veteran Status Code Domain Value (W_EMPLOYEE_D)W_VETERAN_STATUS_CODE W_VETERAN_STATUS_DESC Source

1 Special Disabled Veterans Oracle EBS, PeopleSoft

2 Vietnam Era Veterans Oracle EBS, PeopleSoft

3 Other Protected Veterans Oracle EBS, PeopleSoft

4 Newly Separated Veterans Oracle EBS, PeopleSoft

5 Not a Veteran Oracle EBS, PeopleSoft

W_EVENT_TYPE_D Domain Values


INTRA_CALL. This event class is used to mark the events supplied through the Universal adapter as Intra Call (or ACD) events. These are not exposed in any dimension; however, you can use them for Intra Call activity analysis.

AFTER CALL WORK (ACW) ACTIVITY. This event class is used to mark the events supplied through the Universal adapter as After Call Work events. These events are mapped into the Contact Rep ACW Activity Type dimension.

Table 312 lists the relevant domain value columns in the W_EVENT_TYPE_D table, the possible values, and the relationship among them.

3.7.2 HR Events in the W_EVENT_TYPE_D TableThis section provides further information about HR Event domain values for the W_EVENT_TYPE_D table. To better understand how domain values are used in the W_EVENT_TYPE_D table, examine the following sample scenario for HR events. Your source system tracks many different types of events, some of which involve the employee life cycle events, such as, hire, promotion, termination, leave of absence, and so on. In order to build particular reports, Oracle Business Analytics Warehouse prepackages some domain values for the different event types specific to HR. It is highly recommended that you map all applicable events to the set of domain values provided for the Event Group Code column (W_EVENT_GRP_CODE). Doing so will ensure that the prepackaged reports encompass all applicable events, and, thus, are accurate.

Table 312 Contact Center Events in W_EVENT_TYPE_D

W_EVENT_CLASS W_EVENT_GRP_CODE W_EVENT_SUBG_CODEDomain Value Business Name Source

REPACTIVITY ABSENT FROM WORK ACTUAL Contact rep absent from work

Universal

REPACTIVITY ABSENT FROM WORK SCHEDULED Contact rep scheduled absence

Universal

REPACTIVITY BREAK ACTUAL Contact rep on break Universal

REPACTIVITY BREAK SCHEDULED Contact rep scheduled break

Universal

REPACTIVITY PRESENT TO WORK ACTUAL Contact rep present to work

Universal

REPACTIVITY PRESENT TO WORK SCHEDULED Contact rep scheduled to work

Universal

REPACTIVITY LOGIN ACTUAL Contact rep logged in Universal

REPACTIVITY LOGIN SCHEDULED Contact rep scheduled to log in

Universal

CONTACT COMPLAINT SCHEDULED Contact type Universal

CONTACT COLLECTION SCHEDULED Contact type Universal

CONTACT PRODUCT INQUIRY SCHEDULED Contact type Universal

CONTACT SERVICE INQUIRY SCHEDULED Contact type Universal

CONTACT CAMPAIGN RESPONSE SCHEDULED Contact type Universal

INTRA_CALL CAMPAIGN RESPONSE SCHEDULED ACD or Intra Call Activity type

Universal

ACWACTIVITY CAMPAIGN RESPONSE SCHEDULED After Call Work Activity type

Universal

W_EXPENSE_F Domain Values


Some HR events should be mapped to a domain value for the Event Category Code column (EVENT_CAT_CODE). Any event classified as a TERMINATE for the Event Group Code column (W_EVENT_GRP_CODE) needs to be classified as VOLUNTARY or INVOLUNTARY for the Event Sub Group Code column (IA_EVENT_SUBG_CODE).

In addition, Oracle Business Analytics Warehouse requires that you map your events into the Event Reason Code column (W_EVENT_REASON_CODE), whenever applicable. The Event Reason Code denotes the reason for the Event Group Code. For example, an employee gets terminated. Thus, you would map this source information to the Event Group Code's domain value TERMINATE. If the employee left the company voluntarily, then the Event Sub Group Code column (IA_EVENT_SUBG_CODE) would take the value VOLUNTARY, and if the reason to leave was that the employee was not satisfied, then you would map this reason to the W_EVENT_REASON_CODE's domain value as DISSATISFIED.

Table 313 lists the HR domain values relationship among the IA_EVENT_GRP_CODE, IA_EVENT_SUBG_CODE, and the IA_EVENT_REASON_CODE for Human Resources Analytics.

3.8 W_EXPENSE_F Domain ValuesW_EXPENSE_F is used to capture all expense related data that is submitted through an expense report. Table 314 lists the relevant domain values.

Table 313 Event Types Domain Value Relationships for Human Resources Analytics

W_EVENT_GRP_CODE IA_EVENT_SUBG_CODE W_EVENT_REASON_CODE ROW_TYPE

HIR OTHER OTHER SIEBEL_SUPPLIED

PRO OTHER OTHER SIEBEL_SUPPLIED

REH OTHER OTHER SIEBEL_SUPPLIED

RETIRE OTHER OTHER SIEBEL_SUPPLIED

TERMINATE VOLUNTARY DISSATISFIED SIEBEL_SUPPLIED

TERMINATE VOLUNTARY OTHER SIEBEL_SUPPLIED

TERMINATE INVOLUNTARY OTHER SIEBEL_SUPPLIED

TERMINATE OTHER OTHER SIEBEL_SUPPLIED

OTHER OTHER OTHER SIEBEL_SUPPLIED

Table 314 W_EXPENSE_F (Expense Fact Table) Domain Values

Field Value Domain ValueDomain Value Business Name Source

PREF_MERCHANT_FLAG Y Yes Universal Source

PREF_MERCHANT_FLAG N No Universal Source

CUST_BILLABLE_FLG Y Yes Universal Source

CUST_BILLABLE_FLG N No Universal Source

RECIEPT_FLG Y Yes Universal Source

RECIEPT_FLG N No Universal Source

W_GL_ACCOUNT_D Domain Values


3.9 W_GL_ACCOUNT_D Domain ValuesW_GL_ACCOUNT stores all the general ledger accounts associated with any organization. It contains the general ledger accounts attributes and hierarchy attributes. It also keeps the financial statement item code which determines the nature of account (that is revenue, AP, AR, and so on.).

Table 315 lists the domain values relationships for W_GL_ACCOUNT_D for Financial Analytics.

Table 315 W_GL_ACCOUNT_D Domain ValuesGL_ACCOUNT_CAT_CODE FIN_STMT_ITEM_CODE GROUP_ACCT_NUM Description SourceBS AP AP Accounts Payables Oracle EBS,

PeopleSoft

BS AR AR Accounts Receivable Oracle EBS, PeopleSoft

BS OTHERS ACC DEPCN Accrued Depreciation


BS OTHERS ACC LIAB Accrued Liabilities Oracle EBS, PeopleSoft

BS OTHERS CASH Cash Oracle EBS, PeopleSoft

BS OTHERS CMMN STOCK Common Stock Oracle EBS, PeopleSoft

BS OTHERS FG INV Finished Goods Inventory


BS OTHERS GOODWILL Goodwill Oracle EBS, PeopleSoft

BS OTHERS LT DEBT Lt Debt Oracle EBS, PeopleSoft

BS OTHERS OTHER ASSET Other Asset Oracle EBS, PeopleSoft

BS OTHERS OTHER CA Other Current Asset Oracle EBS, PeopleSoft

BS OTHERS OTHER CL Other Current Liability


BS OTHERS OTHER EQUITY Other Equity Oracle EBS, PeopleSoft

BS OTHERS OTHER LIAB Other Liability Oracle EBS, PeopleSoft

BS OTHERS PPE Ppe Oracle EBS, PeopleSoft

BS OTHERS PREF STOCK Preferred Stock Oracle EBS, PeopleSoft

BS OTHERS PURCH Purch Oracle EBS, PeopleSoft

BS OTHERS RET EARNING Retained Earning Oracle EBS, PeopleSoft

BS OTHERS RM CONS Rm Cons Oracle EBS, PeopleSoft

W_GL_ACCOUNT_D Domain Values


BS OTHERS RM INV Raw Material Inventory


BS OTHERS ST BORR St Borr Oracle EBS, PeopleSoft

BS OTHERS WIP INV Wip Inv Oracle EBS, PeopleSoft

PL COGS COGS Cost Of Goods Sold Oracle EBS, PeopleSoft

PL OTHERS CONT EXP Contracting Expenses


PL OTHERS DEPCN Depreciation Expenses


PL OTHERS EMP BENFT Employee Benefits Related Expenses


PL OTHERS EMP OVERTIME Employee Overtime Oracle EBS, PeopleSoft

PL OTHERS EMP SUPP Employee Support And Cafeteria Expenses


PL OTHERS FREIGHT Freight Expenses Oracle EBS, PeopleSoft

PL OTHERS GEN PAYROLL General Admin And Other Payroll


PL OTHERS INC TAX Income Tax Oracle EBS, PeopleSoft

PL OTHERS INT EXP Interest Exp Oracle EBS, PeopleSoft

PL OTHERS MKTG PAYROLL Marketing Payroll Oracle EBS, PeopleSoft

PL OTHERS OTHER INC Other Income Oracle EBS, PeopleSoft

PL OTHERS OTHER MKTG EXP Other Marketing Expenses


PL OTHERS OTHER OPER EXP Other Operating Expenses


PL OTHERS OTHER R&D EXP Other R&D Expenses


PL OTHERS OTHER SLS EXP Other Sales Expenses


PL OTHERS PPAID EXP Prepaid Expenses Oracle EBS, PeopleSoft

PL OTHERS R&D PAYROLL R&D Payroll Oracle EBS, PeopleSoft

PL OTHERS SLS PAYROLL Sales Payroll Oracle EBS, PeopleSoft

Table 315 (Cont.) W_GL_ACCOUNT_D Domain ValuesGL_ACCOUNT_CAT_CODE FIN_STMT_ITEM_CODE GROUP_ACCT_NUM Description Source

W_JOB_D Domain Values


3.10 W_HR_POSITION_D Domain ValuesW_HR_POSITION_D tracks all the positions in an organization. Position in the current model has a one-to-one relationship to an employee.

Table 316 lists the values for the W_ACTIVE_POSITION_FLG domain value for W_HR_POSITION_D.

Table 317 lists the values for the W_EXEMPT_FLG domain value for W_HR_POSITION_D.

3.11 W_JOB_D Domain ValuesW_JOB_D describes different jobs (not positions) in an organization and also is used for EEO reporting. For example, Manager is a job, as opposed to Senior Manager Sales Western Region San Jose Office, which is a position.

Table 318 lists the FLSA Status Code domain values for W_JOB_D.

Table 319 lists the EEO Job Category Code domain values for the W_JOB_D.

PL OTHERS VARIANCE EXP Product Variance Expenses


PL REVENUE REVENUE Sales Revenue Oracle EBS, PeopleSoft

PL TAX TAX Tax Items Oracle EBS, PeopleSoft

Table 316 W_ACTIVE_POSITION_FLG Domain Value (W_HR_POSITION_D)W_ACTIVE_POSITION_FLG SourceN Oracle EBS, PeopleSoft


Table 317 Exempt Flag Domain Value (W_HR_POSITION_D)W_EXEMPT_FLG Source

N Oracle EBS, PeopleSoft


Table 318 FLSA_STAT_CODE (FLSA Status Code) Domain Value (W_JOB_D)W_FLSA_STAT_CODE W_FLSA_STAT_DESC Source

Exempt Exempt Oracle EBS, PeopleSoft

Non Exempt Non Exempt Oracle EBS, PeopleSoft

Unknown Unknown Oracle EBS, PeopleSoft

Table 315 (Cont.) W_GL_ACCOUNT_D Domain ValuesGL_ACCOUNT_CAT_CODE FIN_STMT_ITEM_CODE GROUP_ACCT_NUM Description Source

W_MVMNT_TYPE_D Domain Values


3.12 W_MVMNT_TYPE_D Domain ValuesW_MVMNT_TYPE_D is used to maintain information on all inventory movement types handled by business organizations. The Movement Type domain value is used to identify vendor returns and customer returns. Other types of movement types are not currently classified.

Table 320 lists the values for the Movement Type domain value for W_MVMNT_TYPE_D.

3.13 W_PAYMENT_METHOD_D Domain ValuesW_PAYMENT_METHOD_D covers the payment methods. Example of payment methods include Cash, Check, and Credit Card.

Table 319 W_EEO_JOB_CAT_CODE (EEO Job Category Code) Domain Value (W_JOB_D)W_EEO_JOB_CAT_CODE W_EEO_JOB_CAT_DESC Source1 First/Mid Level Officials and

ManagersOracle EBS, PeopleSoft

2 Professionals Oracle EBS, PeopleSoft

3 Technicians Oracle EBS, PeopleSoft

4 Sales Workers Oracle EBS, PeopleSoft

5 Administrative Support Workers


6 Craft Workers Oracle EBS, PeopleSoft

7 Operatives Oracle EBS, PeopleSoft

8 Laborers and Helpers Oracle EBS, PeopleSoft

9 Service Workers Oracle EBS, PeopleSoft

10 Executive/Senior Level Officials and Managers


999 No EEO Reporting Oracle EBS, PeopleSoft

Table 320 Movement Type Domain Values (W_MVMNT_TYPE_D)W_MVMNT_TYPE_CODE W_MVMNT_TYPE_DESC Source

OTHERS OTHERS Oracle EBS

VENDOR RETURN VENDOR_RETURN Oracle EBS

CUSTOMER RETURN CUSTOMER RETURN Oracle EBS

Table 321 W_PAYMENT_METHOD_D (Method Dimension Table) Domain Values


W_PAYMENT_METHOD_CODE Cash Cash Oracle EBS

W_PAYMENT_METHOD_CODE Check Check Oracle EBS

W_PAYMENT_METHOD_CODE Credit Card Credit Card Oracle EBS

W_PRODUCT_XACT_F Domain Values


3.14 W_PAY_TYPE_D Domain ValuesThe Pay Types dimension table (W_PAY_TYPE_D) defines various types of compensation or deductions. It can include all types of entries which appear on a pay stub.

Table 322 lists the values for the Pay Type flag domain value for W_PAY_TYPE_D.

Table 323 lists the values for the Pay Type Group Code domain value for the W_PAY_TYPE_D table.

3.15 W_PERSON_D Domain ValuesW_PERSON_D is the ERP and CRM contacts dimension table in the Oracle Business Analytics Warehouse. Table 324 lists the relevant domain values.

3.16 W_PRODUCT_XACT_F Domain ValuesTable 325 lists the Product Transactions (W_PRODUCT_XACT_F) debit or credit indicator domain values.

Table 322 W_PAY_TYPE_FLG Domain Value (W_PAY_TYPE_D)W_PAY_TYPE_FLG Source

C Oracle EBS, PeopleSoft

D Oracle EBS, PeopleSoft

Table 323 Pay Type Group Code Domain Value (W_PAY_TYPE_D)W_PAY_TYPE_GRP_CODE W_PAY_TYPE_GRP_DESC SourceBONUS BONUS Oracle EBS, PeopleSoft

DEDUCTIONS DEDUCTIONS Oracle EBS, PeopleSoft

OTHER OTHER Oracle EBS, PeopleSoft

OTHER_DEDUCTIONS OTHER_DEDUCTIONS Oracle EBS, PeopleSoft

OTHER_EARNINGS OTHER_EARNINGS Oracle EBS, PeopleSoft

OVERTIME OVERTIME Oracle EBS, PeopleSoft

REGULAR REGULAR Oracle EBS, PeopleSoft

TAXES TAXES Oracle EBS, PeopleSoft

TOTAL_GROSS TOTAL_GROSS Oracle EBS, PeopleSoft

TOTAL_DEDUCTIONS TOTAL_DEDUCTIONS Oracle EBS, PeopleSoft

TOTAL_TAXES TOTAL_TAXES Oracle EBS, PeopleSoft

NET_PAY NET_PAY Oracle EBS, PeopleSoft

Table 324 W_PERSON_D table Domain ValueField Value Domain Value Domain Value Business Name SourceCONTACT_TYPE ERP_CONTACT ERP Contact Person Oracle EBS

CONTACT_TYPE CONTACT Contact Siebel

CONTACT_TYPE PROSPECT Prospect Siebel

W_PRODUCT_D Domain Values


3.17 W_PRODUCT_D Domain ValuesW_PRODUCT_D is the Product dimension master table. It contains the basic information and essential details of all products within the organization. Table 326 lists the relevant domain values.

3.18 W_REASON_D Domain ValuesAny action or status change can have one or more reasons associated with it. The W_REASON_D table stores the various reasons associated with various states or activities, for example, account closure reason, product failure reason, claim approval/denial reasons, termination reasons, and customer contact reasons. This table has the ability to store associated information with a reason and categorize them accordingly. In the Oracle Business Analytics Warehouse, this table is identified as a class table. Table 327 lists the relevant domain values.

3.19 W_STATUS_D Domain ValuesThe Status table (W_STATUS_D) is used for tracking attributes associated with statuses of purchase orders, requisitions, shipments, inventory, customer cases, contact statuses, and other documents. There could be several classes of statuses, such as order status, requisition status, schedule status, document status, case status, call status, and

Table 325 W_PROD_XACT_F (Product Transactions) Domain ValuesDEBIT_CREDIT_IND Business Name Description SourceC Credit Indicates a Credit

TransactionOracle EBS

D Debit Indicates a Debit Transaction

Oracle EBS

Table 326 W_PRODUCT_D (Products Dimension Table) Domain Value


MAKE_BUY_IND B Buy Oracle EBS

MAKE_BUY_IND M Make Oracle EBS

Table 327 W_REASON_D (Reasons Dimension Table) Domain Values


W_REASON_CLASS OPPORTUNITY_ REASON Opportunity reason Universal Source

W_REASON_CLASS OPPORTUNITY_ STATUS_REASON

Opportunity status reason

Universal Source

W_REASON_CLASS OPPORTUNITY_ CHANGE_REASON

Opportunity change reason

Universal Source

W_REASON_CLASS QUOTA_CHANGE_REASON Quota change reason Universal Source

W_REASON_CLASS CONTACT Contact Reason Universal Source

W_REASON_CLASS CONTACT_TRANSFER Contact Transfer Reason Universal Source

W_STATUS_D Domain Values


so on. Depending on the class of transactions, the table can have different categories of values. The status class is identified by the column status type.

Table 328 lists the Status domain values for Contact Center Telephony Analytics.

Table 329 lists the Accounting Document domain values for the Status dimension class table for Financial Analytics.

Table 330 lists the Purchase Cycle domain values for the Status dimension class table for Supply Chain and Order Management Analytics.

Table 328 Contact Center Domain Value (W_STATUS_D)W_STATUS_CLASS W_STATUS_CODE Source

CONTACT ABANDONED Universal Source

CONTACTS HANGUP Universal Source

CONTACT RELEASE Universal Source

CONTACT DISCONNECTED Universal Source

Table 329 Accounting Document Domain Value (W_STATUS_D)W_STATUS_CODE W_SUBSTATUS_CODE STATUS_CODE

POSTED OPEN~POSTED OPEN

UNPOSTED CLEARED~UNPOSTED CLEARED

POSTED CLEARED~POSTED CLEARED

POSTED POSTED CLEARED

UNPOSTED OPEN~UNPOSTED OPEN

UNPOSTED UNPOSTED OPEN

Table 330 Purchase Cycle Domain Values (W_STATUS_D)W_STATUS_CLASS W__STATUS_CODE W_SUBSTATUS_CODE SourcePURCH_CYCLE CLOSED CLOSED Oracle EBS

PURCH_CYCLE INVOICED INVOICED Oracle EBS

PURCH_CYCLE OPEN OPEN Oracle EBS

PURCH_CYCLE ON HOLD ON HOLD Oracle EBS

PURCH_CYCLE CANCELLED CANCELLED Oracle EBS

PURCH_CYCLE OTHER OTHER Oracle EBS

PURCH_CYCLE COMPLETED COMPLETED Oracle EBS

PURCH_CYCLE CLOSED CANCELLED Oracle EBS

PURCH_CYCLE INVOICED CANCELLED Oracle EBS

PURCH_CYCLE OPEN CANCELLED Oracle EBS

PURCH_CYCLE ON HOLD CANCELLED Oracle EBS

PURCH_CYCLE CLOSED CANCELLED Oracle EBS

PURCH_CYCLE COMPLETED CANCELLED Oracle EBS



Table 331 lists the Purchase Approval domain values for the Status dimension class table for Supply Chain and Order Management Analytics.

Table 332 lists the Expense Status domain values for the Status dimension class table for Supply Chain and Order Management Analytics.

Table 333 lists the domain values for the Status dimension class table for Supply Chain and Order Management Analytics.

Table 331 Purchase Approval Domain Values (W_STATUS_D)W_STATUS_CLASS W_STATUS_CODE SourcePURCH_APPROVAL COMPOSING Oracle EBS

PURCH_APPROVAL PENDING APPROVAL Oracle EBS

PURCH_APPROVAL APPROVED Oracle EBS

PURCH_APPROVAL REJECTED Oracle EBS

PURCH_APPROVAL CANCELLED Oracle EBS

PURCH_APPROVAL OTHER Oracle EBS

Table 332 Expense Status Domain Values (W_STATUS_D)W_STATUS_CLASS W_STATUS_CODE SourceEXPENSE_STATUS Approved Universal Source

EXPENSE_STATUS Submitted Universal Source

EXPENSE_STATUS Denied Universal Source

EXPENSE_STATUS Request for more information Universal Source

EXPENSE_STATUS Composing Universal Source

EXPENSE_STATUS Withdrawn Universal Source

Table 333 Status Domain Values (W_STATUS_D)W_STATUS_CLASS W_STATUS_CODE W_STATUS DESC SourceCUSTOMER_STATUS DORMANT DORMANT Oracle EBS

CUSTOMER_STATUS LOST LOST Oracle EBS

CUSTOMER_STATUS NEW NEW Oracle EBS

CUSTOMER_STATUS RECENT RECENT Oracle EBS

CUSTOMER_STATUS UNKNOWN UNKNOWN Oracle EBS

FULFILLMENT_STATUS

ORDER BOOKED ORDER BOOKED Oracle EBS

FULFILLMENT_STATUS

ORDER ENTERED ORDER ENTERED Oracle EBS

FULFILLMENT_STATUS

ORDER FULLY CANCELLED


Oracle EBS

FULFILLMENT_STATUS

ORDER FULLY PICKED ORDER FULLY PICKED Oracle EBS

FULFILLMENT_STATUS

ORDER FULLY SCHEDULED

ORDER FULLY SCHEDULED

Oracle EBS



FULFILLMENT_STATUS

ORDER FULLY SHIPPED ORDER FULLY SHIPPED

Oracle EBS

FULFILLMENT_STATUS

ORDER PARTIALLY CANCELLED

ORDER PARTIAL CANCELLED

Oracle EBS

FULFILLMENT_STATUS

ORDER PARTIALLY PICKED

ORDER PARTIAL PICKED

Oracle EBS

FULFILLMENT_STATUS

ORDER PARTIALLY SCHEDULED

ORDER PARTIAL SCHEDULED

Oracle EBS

FULFILLMENT_STATUS

ORDER PARTIALLY SHIPPED

ORDER PARTIAL SHIPPED

Oracle EBS

FULFILLMENT_STATUS

ORDER NOT ELIGIBLE ORDER NOT ELIGIBLE FOR SHIPPING

Oracle EBS

INVOICE_STATUS ORDER FULLY INVOICED

ORDER FULLY INVOICED

Oracle EBS

INVOICE_STATUS ORDER NOT INVOICED ORDER NOT INVOICED

Oracle EBS

INVOICE_STATUS ORDER PAID ORDER PAID Oracle EBS

INVOICE_STATUS ORDER PARTIALLY INVOICED

ORDER PARTIALLY INVOICED

Oracle EBS

INVOICE_STATUS ORDER NOT ELIGIBLE ORDER NOT ELIGIBLE FOR INVOICING

Oracle EBS

INVOICE_STATUS ORDER FULLY CANCELLED


Oracle EBS

SALES_INVOICE_PROCESS

Cancelled Cancelled Oracle EBS


Completed Completed Oracle EBS


Open Open Oracle EBS


Pending Pending Oracle EBS

SALES_ORDER_PROCESS

Being Processed Being Processed Oracle EBS

SALES_ORDER_PROCESS

Blocked Blocked Oracle EBS

SALES_ORDER_PROCESS

Booked Booked Oracle EBS

SALES_ORDER_PROCESS


SALES_ORDER_PROCESS

Closed Closed Oracle EBS

SALES_ORDER_PROCESS

Entered Entered Oracle EBS

SALES_PICKING_PROCESS


Table 333 (Cont.) Status Domain Values (W_STATUS_D)W_STATUS_CLASS W_STATUS_CODE W_STATUS DESC Source

W_XACT_TYPE_D Domain Values


3.20 W_XACT_TYPE_D Domain ValuesW_XACT_TYPE_D defines various transaction types as they are defined in the domain and client value lists.

Table 334 lists the hierarchical relationship among W_XACT_TYPE_CODE and W_XACT_SUBTYPE_CODE for the Purchase Order transaction type (XACT_CODE=PURCH_ORDERS).

Table 335 and Table 336 lists the domain values of W_XACT_TYPE_CODE (Measure Basis) and W_XACT_TYPE_CODE1 (Buying Type) for the purchase order line type transaction type (XACT_CODE= PO_LINE_TYPE). A purchase order line type in the source can have any name, but it is measured either by amount or quantity (W_XACT_TYPE_CODE). A purchase order line type can also indicate what is being procured


Fully Picked Fully Picked Oracle EBS


Fully Shipped Fully Shipped Oracle EBS


Not Relevant Not Relevant Oracle EBS


Not Yet Picked Not yet picked Oracle EBS


Back Ordered Back Ordered


Purged Purged

SALES_SCHEDULE_PROCESS

Blocked Blocked Oracle EBS




Closed Closed Oracle EBS


Entered Entered Oracle EBS


Not Valid Not Valid Oracle EBS

Table 334 Purchase Order Transaction Type Domain Values (W_XACT_TYPE_D)W_XACT_TYPE_CODE

W_XACT_SUBTYPE_CODE Description Source

AGREEMENT No value Agreement Oracle EBS

ORDER COMPLEXWORK_ACTUAL

Order, Actual Complex Work Procurement

Oracle EBS

ORDER COMPLEXWORK_FINANCING

Order, Financing Complex Work Procurement

Oracle EBS

ORDER No value Order, Regular Oracle EBS

Table 333 (Cont.) Status Domain Values (W_STATUS_D)W_STATUS_CLASS W_STATUS_CODE W_STATUS DESC Source



(W_XACT_TYPE_CODE1). These two values do not necessarily have a hierarchical relationship.

Table 337 lists various other transaction types (XACT_CODE) in Supply Chain and Order Management Analytics. The list also shows the transaction type code domain values (W_XACT_TYPE_CODE) for each transaction type.

Table 338 lists the relationship among XACT_CAT_CODE, XACT_CODE, W_XACT_TYPE_CODE, and W_XACT_SUBTYPE_CODE for the Transaction Types dimension class table for Financial Analytics.

Table 335 PO Line Type Transaction Type, Measure Basis Domain Values (W_XACT_TYPE_D)W_XACT_TYPE_CODE Description Source

AMOUNT Amount Oracle EBS

QUANTITY Quantity Oracle EBS

Table 336 PO Line Type Transaction Type, Buying Type Domain Values (W_XACT_TYPE_D)W_XACT_TYPE_CODE1 Description SourceSERVICES Services based purchases Oracle EBS

TEMP LABOR Temporary labor based purchases

Oracle EBS

GOODS Goods based purchases Oracle EBS

Table 337 Other Transaction Type Domain Values for Supply Chain and Order Management Analytics

XACT_CODEW_XACT_TYPE_CODE Description Source

PO_PAYMENT_TYPE ADVANCE Advance Pay Item Oracle EBS

PO_PAYMENT_TYPE DELIVERY Delivery Pay Item Oracle EBS

PO_PAYMENT_TYPE LUMPSUM Lump Sum Pay Item Oracle EBS

PO_PAYMENT_TYPE MILESTONE Milestone Pay Item Oracle EBS

PO_PAYMENT_TYPE RATE Rate Type Pay Item Oracle EBS

PO_PAYMENT_TYPE BLANKET Blanket Release Shipment

Oracle EBS

PO_PAYMENT_TYPE PREPAYMENT Prepayment Oracle EBS

PO_PAYMENT_TYPE SCHEDULED Scheduled Release Shipment

Oracle EBS

PO_PAYMENT_TYPE STANDARD Standard Shipment Oracle EBS

PURCH_ORDER_CI CONSIGNED Consigned PO Oracle EBS

PURCH_ORDER_CI CONSIGNED-CONSUMED

Consumption Advice Oracle EBS

PURCH_ORDER_CI REGULAR Regular Oracle EBS

PURCH_RCPTS RECEIVE Receive Oracle EBS

PURCH_RQLNS REQUISITION Requisition Oracle EBS



Table 338 Transaction Types Dimension Class Table for Financial Analytics

XACT_CAT_CODE XACT_CODE W_XACT_TYPE_CODEW_XACT_SUBTYPE_CODE Description Source

ACCT_DOC RECEIVABLE ORIGINAL INVOICE Invoice Oracle EBS, PeopleSoft

ACCT_DOC RECEIVABLE ORIGINAL CR MEMO Credit Memo Oracle EBS, PeopleSoft

ACCT_DOC RECEIVABLE ORIGINAL DR MEMO Debit Memo Oracle EBS, PeopleSoft

ACCT_DOC RECEIVABLE ORIGINAL OTHER Other type of Receivable Transaction


ACCT_DOC RECEIVABLE PAYMENT PAYMENT Cash Payment Oracle EBS, PeopleSoft

ACCT_DOC RECEIVABLE APPLICATION CASH APPLICATION

Cash Application


ACCT_DOC RECEIVABLE APPLICATION CR MEMO APPLICATION

Credit Memo Application


ACCT_DOC RECEIVABLE APPLICATION ADJUSTMENT APPLICATION

Adjustments Oracle EBS, PeopleSoft

ACCT_DOC RECEIVABLE DISTRIBUTION DISTRIBUTION All distributions


ACCT_DOC RECEIVABLE DIFFERENCE GL DIFF ADJ Difference from GL Journal


ACCT_DOC RECEIVABLE MANUAL GL MANUAL ADJ GL Journal Manual Entry


ACCT_DOC PAYABLE ORIGINAL INVOICE Invoice Oracle EBS, PeopleSoft

ACCT_DOC PAYABLE ORIGINAL CR MEMO Credit Memo Oracle EBS, PeopleSoft

ACCT_DOC PAYABLE ORIGINAL DR MEMO Debit Memo Oracle EBS, PeopleSoft

ACCT_DOC PAYABLE ORIGINAL OTHER Other type of Payable Transaction


ACCT_DOC PAYABLE DISTRIBUTION OTHER Invoice Distribution




ACCT_DOC PAYABLE APPLICATION APPLICATION Invoice Payment


ACCT_DOC PAYABLE DIFFERENCE GL DIFF ADJ Difference from GL Journal


ACCT_DOC PAYABLE MANUAL GL MANUAL ADJ GL Journal Manual Entry


ACCT_DOC REVENUE ORIGINAL INVOICE Invoice Oracle EBS

ACCT_DOC REVENUE ORIGINAL CR MEMO Credit Memo Oracle EBS

ACCT_DOC REVENUE ORIGINAL DR MEMO Debit Memo Oracle EBS

ACCT_DOC REVENUE ORIGINAL OTHER Other type of Revenue Transaction

Oracle EBS

ACCT_DOC REVENUE DIFFERENCE GL DIFF ADJ Difference from GL Journal

Oracle EBS

ACCT_DOC REVENUE MANUAL GL MANUAL ADJ GL Journal Manual Entry

Oracle EBS

ACCT_DOC COGS ORIGINAL DELIVERY Delivery Oracle EBS

ACCT_DOC COGS ORIGINAL RETURN Return Oracle EBS

ACCT_DOC COGS DIFFERENCE GL DIFF ADJ Difference from GL Journal

Oracle EBS

ACCT_DOC COGS MANUAL GL MANUAL ADJ GL Journal Manual Entry

Oracle EBS

ACCT_DOC DEFERRED REVENUE

ORIGINAL INVOICE Invoice Oracle EBS


ORIGINAL CR MEMO Credit Memo Oracle EBS


ORIGINAL DR MEMO Debit Memo Oracle EBS


ORIGINAL OTHER Other type of Receivable Transaction

Oracle EBS


DIFFERENCE GL DIFF ADJ Difference from GL Journal

Oracle EBS


MANUAL GL MANUAL ADJ GL Journal Manual Entry

Oracle EBS

Table 338 (Cont.) Transaction Types Dimension Class Table for Financial Analytics

XACT_CAT_CODE XACT_CODE W_XACT_TYPE_CODEW_XACT_SUBTYPE_CODE Description Source



ACCT_DOC DEFERRED COGS

ORIGINAL DELIVERY Delivery Oracle EBS


DIFFERENCE GL DIFF ADJ Difference from GL Journal

Oracle EBS


MANUAL GL MANUAL ADJ GL Journal Manual Entry

Oracle EBS

ACCT_DOC PROD_COSTLNS

MARKETING MARKETING SALARIES

Marketing Salaries

Universal Source


MARKETING ADVERTISEMENT Advertisement Universal Source


oracle business analytics warehouse data model reference version 7.9.5

Documents

government rights programs

oracle parkway

oracle usa

commercial computer

domain values guide

extent applicable

safe use

united states government