DMR_BIApplications7964

Oracle Business Analytics Warehouse Data Model

Reference Version 7.9.6.4

The Oracle Business Analytics Warehouse Data Model Reference is made up of three distinct pieces: The Oracle Business Intelligence Applications Naming Conventions and Domain Values

Guide, Version 7.9.6.4 The star schema diagrams The table and column descriptions

Oracle Business Intelligence ApplicationsNaming Conventions and Domain Values Guide

Release 7.9.6.4

E35829-01

November 2012Explains the naming conventions and domain values for the Oracle Business Analytics Warehouse, including table types, system columns, column prefixes, and currency codes.

Oracle Business Intelligence Applications Naming Conventions and Domain Values Guide, Release 7.9.6.4

E35829-01

Copyright 2006, 2012, Oracle and/or its affiliates. All rights reserved.

Primary Author: Jill Arehart

Contributing Author: Sam Myers

Contributors: Oracle Business Intelligence development, product management, and quality assurance teams.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

iii

Contents

Preface ................................................................................................................................................................ viiAudience..................................................................................................................................................... viiiDocumentation Accessibility ................................................................................................................... viiiRelated Documents ................................................................................................................................... viiiConventions ................................................................................................................................................. ix

1 What's New in This Release1.1 What's New in Oracle Business Analytics Warehouse Data Model Reference

Release 7.9.6.3 .............................................................................................................................. 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-42.2.3 Aggregate Tables in Oracle Business Analytics Warehouse ......................................... 2-42.2.4 Dimension Tables in Oracle Business Analytics Warehouse ........................................ 2-42.2.5 Dimension Class Tables in Oracle Business Analytics Warehouse.............................. 2-42.2.6 Dimension Tables With Business Role-Based Flags ....................................................... 2-42.2.7 Mini-Dimension Tables in Oracle Business Analytics Warehouse .............................. 2-52.2.8 Hierarchy Tables in Oracle Business Analytics Warehouse.......................................... 2-52.2.9 Helper Tables in Oracle Business Analytics Warehouse ............................................... 2-52.3 Internal Tables in Oracle Business Analytics Warehouse..................................................... 2-62.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-82.7 Currency Codes for Related System Columns ....................................................................... 2-92.8 Code Pairs for Related System Columns.............................................................................. 2-102.9 Oracle Business Analytics Warehouse Primary Data Values............................................ 2-102.10 Supported List of Values in Oracle Business Analytics Warehouse ................................ 2-102.10.1 Data Sourced from Siebel Transactional Databases .................................................... 2-102.10.2 Data Sourced from Non-Siebel Sources......................................................................... 2-112.11 Oracle Business Analytics Warehouse Currency Conversion........................................... 2-11

iv

3 Oracle Business Analytics Warehouse Domain Values3.1 Overview of Domain Values ..................................................................................................... 3-23.2 W_BUSN_LOCATION_D Domain Values ............................................................................. 3-23.3 W_CHNL_TYPE_D Domain Values ........................................................................................ 3-23.4 W_CODE_D Domain Values .................................................................................................... 3-33.5 W_DAY_D (and Other Calendar Tables) Domain Values.................................................... 3-43.6 W_EMPLOYMENT_D Domain Values ................................................................................... 3-53.7 W_EMPLOYEE_D Domain Values .......................................................................................... 3-63.8 W_EVENT_TYPE_D Domain Values ...................................................................................... 3-73.8.1 Contact Center Events in the W_EVENT_TYPE_D Table ............................................. 3-73.8.2 HR Events in the W_EVENT_TYPE_D Table .................................................................. 3-83.9 W_EXPENSE_F Domain Values ............................................................................................... 3-93.10 W_GL_ACCOUNT_D Domain Values................................................................................. 3-103.11 W_HR_POSITION_D Domain Values.................................................................................. 3-143.12 W_JOB_D Domain Values ...................................................................................................... 3-153.13 W_JOB_RQSTN_D Domain Values ...................................................................................... 3-163.14 W_MKTG_LEAD_D Domain Values ................................................................................... 3-163.15 W_MVMNT_TYPE_D Domain Values................................................................................. 3-173.16 W_PAYMENT_METHOD_D Domain Values..................................................................... 3-173.17 W_PAY_TYPE_D Domain Values......................................................................................... 3-183.18 W_PERSON_D Domain Values............................................................................................. 3-183.19 W_PRODUCT_XACT_F Domain Values ............................................................................. 3-193.20 W_PRODUCT_D Domain Values ......................................................................................... 3-193.21 W_RCRTMNT_EVENT_TYPE_D Domain Values ............................................................. 3-193.22 W_RCRTMNT_SOURCE_D Domain Values ...................................................................... 3-223.23 W_REASON_D Domain Values ............................................................................................ 3-233.24 W_STATUS_D Domain Values.............................................................................................. 3-233.24.1 Contact Center Telephone Analytics Status Domain Values ..................................... 3-243.24.2 Accounting Document Status Domain Values for Financial Analytics .................... 3-243.24.3 Vacancy Status Domain Values for Human Resource Performance Analytics ....... 3-243.24.4 Recruitment Status Domain Values for Human Resource

Performance Analytics ..................................................................................................... 3-253.24.5 Loyalty Member Status Domain Values for Loyalty Analytics ................................. 3-263.24.6 Purchase Approval Status Domain Values for Procurement and

Spend Analytics ................................................................................................................ 3-263.24.7 Purchase Cycle Status Domain Values for Procurement and Spend Analytics ...... 3-263.24.8 AP Invoice Payment Status Domain Values for Procurement and

Spend Analytics ................................................................................................................ 3-273.24.9 AP Invoice Approval Status Domain Values for Procurement and

Spend Analytics ................................................................................................................ 3-283.24.10 Requisition Cycle Status Domain Values for Procurement and

Spend Analytics ................................................................................................................ 3-283.24.11 Expense Status Domain Values for Procurement and Spend Analytics................... 3-293.24.12 Status Dimension Class Domain Values for Order Management and

Fulfillment Analytics........................................................................................................ 3-303.24.13 Project Status Domain Values for Project Analytics .................................................... 3-323.24.14 Transfer Status Domain Values for Project Analytics ................................................. 3-32

v3.24.15 Revenue Status Domain Values for Project Analytics................................................. 3-323.24.16 Invoice Status Domain Values for Project Analytics ................................................... 3-353.24.17 Marketing Lead Status Domain Values for Marketing Analytics ............................. 3-353.24.18 Learning Enrollment Status Domain Values for Human

Resource Performance Analytics.................................................................................... 3-353.25 W_XACT_SOURCE_D Domain Values................................................................................ 3-363.26 W_XACT_TYPE_D Domain Values ...................................................................................... 3-373.27 W_WRKFC_EVENT_TYPE_D Domain Values................................................................... 3-48

Index

vii

Preface

Oracle Business Intelligence Applications are comprehensive prebuilt solutions that deliver pervasive intelligence across an organization, empowering users at all levels from front line operational users to senior management with the key information they need to maximize effectiveness. Intuitive and role-based, these solutions transform and integrate data from a range of enterprise sources, including Siebel, Oracle, PeopleSoft, JD Edwards, and corporate data warehouses into actionable insight that enables more effective actions, decisions, and processes.

Oracle BI Applications includes the following:

Oracle Contact Center Telephony Analytics

Oracle Financial Analytics

Oracle Manufacturing Analytics

Oracle Enterprise Asset Management Analytics

Oracle Human Resources Analytics

Oracle Loyalty Analytics

Oracle Marketing Analytics

Oracle Pharma Marketing Analytics

Oracle Pharma Sales Analytics

Oracle Price Analytics

Oracle Procurement and Spend Analytics

Oracle Project Analytics

Oracle Sales Analytics

Oracle Service Analytics

Oracle Supply Chain and Order Management Analytics

For more details on the applications included in this release of Oracle BI Applications, see the Oracle Business Intelligence Applications Licensing and Packaging Guide. This guide is included in the Oracle Business Intelligence Media Pack. Also, see System Requirements and Supported Platforms for Oracle Business Intelligence Applications, available on the documentation library for this release at http://www.oracle.com/technology/documentation/bi_apps.html.

The Oracle Business Intelligence Applications Naming Conventions and Domain Values Guide contains information about the data structures in the Oracle Business Analytics

viii

Warehouse that store data for reporting purposes. The information provided includes table and column descriptions.

Oracle recommends reading the Oracle Business Intelligence Applications Release Notes before installing, using, or upgrading Oracle BI Applications. The most current version of the Oracle Business Intelligence Applications Release Notes is available on the Oracle Technology Network at http://www.oracle.com/technetwork/middleware/bi-foundation/documentation/bi-apps-098545.html. To register for a free account on the Oracle Technology Network, go to http://www.oracle.com/technetwork/index.html.

AudienceThis document is intended for BI managers and implementers of Oracle BI Applications.

Documentation AccessibilityFor information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle SupportOracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

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

Oracle Business Intelligence Applications Release Notes

System Requirements and Supported Platforms for Oracle Business Intelligence Applications

Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users

Oracle Business Intelligence Applications Configuration Guide for Informatica PowerCenter Users

Oracle Business Intelligence Applications Upgrade Guide for Informatica PowerCenter Users

Oracle Business Intelligence Applications Security Guide

ConventionsThe following text conventions are used in this document:

ix

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.6.4 of the software.

1.1 What's New in Oracle Business Intelligence Applications Naming Conventions and Domain Values Guide Release 7.9.6.4

This guide includes the following changes:

Domain values were added to the W_MVMNT_TYPE_D section. See W_MVMNT_TYPE_D Domain Values for more information.

Kanban Card Status domain values were added to the W_STATUS_D section. See Kanban Card Status Domain Values for more information.

Asset Status domain values for Enterprise Asset Management were added to the W_STATUS_D section. See Asset Status Domain Values for Enterprise Asset Management for more information.

Work Order Status domain values for Process Manufacturing were added to the W_STATUS_D section. See Work Order Status Domain Values for Process Manufacturing Analytics for more information.

Work Order Status domain values for Enterprise Discrete Manufacturing and Enterprise Asset Management were added to the W_STATUS_D section. See Work Order Status Domain Values for Enterprise Discrete Manufacturing and Enterprise Asset Management Analytics for more information.

Work Order Types in Enterprise Asset Management Analytics was added to the W_XACT_TYPE_D section. See Work Order Types in Enterprise Asset Management Analytics for more information.

Failure Cause Codes in Enterprise Asset Management Analytics was added to the W_XACT_TYPE_D section. See Failure Cause Codes in Enterprise Asset Management Analytics for more information.

Cost Elements in Enterprise Asset Management Analytics was added to the W_XACT_TYPE_D section. See Cost Elements in Enterprise Asset Management Analytics for more information.

Errorcode in Kanban Analytics was added to the W_XACT_TYPE_D section. See Errorcodes in Kanban Analytics for more information.

Cost Elements in Process Manufacturing Analytics was added to the W_XACT_TYPE_D section. See Cost Elements in Process Manufacturing Analytics for more information.

What's New in Oracle Business Intelligence Applications Naming Conventions and Domain Values Guide Release 7.9.6.4

1-2 Oracle Business Intelligence Applications Naming Conventions and Domain Values Guide

Cost Elements in Discrete Manufacturing Analytics was added to the W_XACT_TYPE_D section. See Cost Elements in Discrete Manufacturing Analytics for more information.

Plan Order Types in Discrete Manufacturing Analytics was added to the W_XACT_TYPE_D section. See Plan Order Types in Discrete Manufacturing Analytics for more information.

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, "Oracle Business Analytics Warehouse Primary Data Values"

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

Section 2.11, "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

WS_= Staging

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_DEL = Delete_DH = Dimension Hierarchy_DHL = Dimension Helper_DHLS = Staging for Dimension Helper_DHS = Staging for Dimension Hierarchy_DS = Staging for Dimension_F = Fact_FS = Staging for Fact_G, _GS, _S = Internal_H = Helper_M = Map Dimension_MD = Mini Dimension_PE = Primary Extract_PS = Persisted Staging_TMP = Pre-staging temporary table_UD = Unbounded Dimension_WS = Staging for Usage Accelerator

Table 22 Table Types Used by the Oracle Business Analytics Warehouse

Table Type Description

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

Dimension tables (_D) Star analysis dimensions.

Delete tables (_DEL) Tables that store IDs of the entities that were physically deleted from the source system and should be flagged as deleted from the data warehouse.

Note that there are two types of delete tables: _DEL and _PE. For more information about the _PE table type, see the following Primary extract tables (_PE) row.

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)

Staging tables for storing M:M relationships between two joining dimension tables.

Staging for Dimension Hierarchy (_DHS)

Staging tables for storing the hierarchy structures of dimensions that have not been through the final extract-transform-load (ETL) transformations.

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

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

Fact Staging tables (_FS) Staging tables used to hold the metrics being analyzed by dimensions that have 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.

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

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.

Primary extract tables (_PE) Tables that are used to support the soft delete feature. The table includes all the primary key columns (integration ID column) from the source system. When a delete event happens, the full extract from the source compares the data previously extracted in the primary extract table to determine if a physical deletion was done in the Siebel application. The soft delete feature is disabled by default. Therefore, the primary extract tables are not populated until you enable the soft delete feature.

Persisted staging tables (_PS) Tables that source multiple data extracts from the same source table.

These tables perform some common transformations required by multiple target objects. They also simplify the source object to a form that is consumable by the warehouse needed for multiple target objects. These tables are never truncated during the life of the data warehouse. These are truncated only during full load, and therefore, persist the data throughout.

Pre-staging temporary table (_TMP) Source-specific tables used as part of the ETL processes to conform the data to fit the universal staging tables (table types _DS and _FS). These tables contain intermediate results that are created as part of the conforming process.

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

Staging tables for Usage Accelerator (_WS)

Tables containing the necessary columns for the ETL transformations.

Table 22 (Cont.) Table Types Used by the Oracle Business Analytics WarehouseTable Type Description



also as interface tables between the transactional database sources and data warehouse target tables.

2.2.2 Fact Tables in Oracle Business Analytics WarehouseA fact table in the Oracle Business Analytics Warehouse has a surrogate key only if the records in the fact table need to be updated or if the fact table has an aggregate table on top of it. 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-demand 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 are 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. The table 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 Dimension 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 a Human Resources (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 (for example, W_EMPLOYEE_D) 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 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 23 lists the mini-dimension tables in the Oracle Business Analytics Warehouse.

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

Table 23 Mini-Dimension Tables in Oracle Business Analytics WarehouseTable 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

W_QUOTE_MD Parent W_RESPONSE_D

W_SRVREQ_MD Parent W_RESPONSE_D

Internal Tables in Oracle Business Analytics Warehouse


At times there is a requirement to query facts related to the children of a given parent in the dimension by specifying only 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 Oracle Data Warehouse Administration Console (DAC). These tables are described in Table 24.

Note: Tables located in the transactional database are used only by Siebel source systems.

Table 24 Oracle Business Analytics Warehouse Internal Tables

Name 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

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

W_UOM_CONVERSION_G

Stores a list of From and To UOM codes and their conversion rates.

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

Standard Column Suffixes in Oracle Business Analytics Warehouse


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

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

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 Standard Column PrefixPrefix Description In Table Types

W_ Domain value columns _D, _F

Table 26 Standard Column Suffixes

Suffix Description In Table Types_CD, _CD_I, _CODE

Code field. _D, _DS, _FS, _G, _GS

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

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

System Columns in Oracle Business Analytics Warehouse Tables


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 27 lists system columns used in dimension tables. Table 27 lists system columns used in fact tables.

_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

_ID _ID columns are used in _FS tables. They correspond to the _WID columns of the corresponding _F table.

_FS

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

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.



Table 26 (Cont.) Standard Column SuffixesSuffix Description In Table Types

Currency Codes for Related System Columns


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


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 used in an Application Service Provider (ASP)/Software as a Service (SaaS) model.

X_CUSTOM Column used as a generic field for customer extensions.

Table 28 Currency Codes for Related System ColumnsSystem Column DescriptionDOC_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.

GRP_CURR_CODE The primary 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.

GLOBAL1_EXCHANGE_RATE

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


Currency conversion rate from the document currency code to the GLOBAL1 currency code.


Currency conversion rate from document currency code to the GLOBAL2 currency code.

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

Code Pairs for Related System Columns


2.8 Code Pairs for Related System ColumnsTable 29 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 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.10 Supported List of Values in Oracle Business Analytics WarehouseThis section discusses list of values usage in Oracle Business Analytics Warehouse.

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

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

Oracle Business Analytics Warehouse Currency Conversion


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.10.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.11 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 entity in which the transaction occurred.

Global currency. The Oracle Business Analytics Warehouse stores up to three group currencies configured using the Oracle Business Intelligence Data Warehouse Administration Console. 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_CODE_D Domain Values"

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

Section 3.6, "W_EMPLOYMENT_D Domain Values"

Section 3.7, "W_EMPLOYEE_D Domain Values"

Section 3.8, "W_EVENT_TYPE_D Domain Values"

Section 3.9, "W_EXPENSE_F Domain Values"

Section 3.10, "W_GL_ACCOUNT_D Domain Values"

Section 3.11, "W_HR_POSITION_D Domain Values"

Section 3.12, "W_JOB_D Domain Values"

Section 3.13, "W_JOB_RQSTN_D Domain Values"

Section 3.14, "W_MKTG_LEAD_D Domain Values"

Section 3.15, "W_MVMNT_TYPE_D Domain Values"

Section 3.16, "W_PAYMENT_METHOD_D Domain Values"

Section 3.17, "W_PAY_TYPE_D Domain Values"

Section 3.18, "W_PERSON_D Domain Values"

Section 3.19, "W_PRODUCT_XACT_F Domain Values"

Section 3.20, "W_PRODUCT_D Domain Values"

Section 3.21, "W_RCRTMNT_EVENT_TYPE_D Domain Values"

Section 3.22, "W_RCRTMNT_SOURCE_D Domain Values"

Section 3.23, "W_REASON_D Domain Values"

Section 3.24, "W_STATUS_D Domain Values"

Overview of Domain Values


Section 3.25, "W_XACT_SOURCE_D Domain Values"

Section 3.26, "W_XACT_TYPE_D Domain Values"

Section 3.27, "W_WRKFC_EVENT_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.

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 guide 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 SourceCNTCT_CNTR Contact Center

LocationContact 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

W_CODE_D 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_CODE_D Domain ValuesTable 34 lists the Project Type Class Code domain values for Project Analytics.

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_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 RelationshipsW_CHTY_GRP_CODE W_CHTY_SUBG_CODE W_INBOUND_TYPE_FLG

CALL 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

W_DAY_D (and Other Calendar Tables) Domain Values


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

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 35 lists the calendar tables and the columns in those tables that take on the domain values listed above.

Table 34 Project Type Class Code Domain Values for Project AnalyticsW_PROJECT_TYPE_CLASS_CODE

W_PROJECT_TYPE_CLASS_DESC Source

INDIRECT Project type class of indirect project

Oracle EBS, PeopleSoft

CAPITAL Project type class of capital project


CONTRACT Project type class of contract project


Table 35 Calendar Columns and TablesCalendar Table Name Column Name Values SourceW_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_EMPLOYMENT_D Domain Values


3.6 W_EMPLOYMENT_D Domain ValuesThis dimension contains the attributes for employment.

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

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

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

Table 36 Employee Category Domain Value (W_EMPLOYMENT_D)W_EMPLOYEE_CAT_CODE

W_EMPLOYEE_CAT_DESC

W_EMPLOYEE_SUB_CAT_CODE

W_EMPLOYEE_SUB_CAT_DESC Source

EMPLOYEE Employee EMPLOYEE_REGULAR

Regular Employee Oracle EBS, PeopleSoft

EMPLOYEE Employee EMPLOYEE_EXPATRIATE

Expatriate Oracle EBS, PeopleSoft

EMPLOYEE Employee EMPLOYEE_TEMP Temporary Employee Oracle EBS, PeopleSoft

CONTIGENT Contigent Worker CONTIGENT_TEMP Agency/Temp Oracle EBS, PeopleSoft

CONTIGENT Contigent Worker CONTIGENT_CONTIGENT

Contractor Oracle EBS, PeopleSoft

CONTIGENT Contigent Worker CONTIGENT_CONTRACTOR

Contractor Oracle EBS, PeopleSoft

CONTIGENT Contigent Worker CONTIGENT_INTERN

Intern Oracle EBS, PeopleSoft

CONTIGENT Contigent Worker CONTIGENT_TRAINEE

Trainee Oracle EBS, PeopleSoft

NONWORKER Non Worker NONWORKER Non Worker Oracle EBS, PeopleSoft

Table 37 Exempt Flag Domain Value (W_EMPLOYMENT_D)W_EXEMPT_FLG Source

N Oracle EBS, PeopleSoft

Table 35 (Cont.) Calendar Columns and TablesCalendar Table Name Column Name Values Source

W_EMPLOYEE_D Domain Values


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

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

Table 310 lists the values for the Regular Temporary domain value for W_EMPLOYMENT_D.

3.7 W_EMPLOYEE_D Domain ValuesTable 311 contains all the attributes associated with employees of an organization. It lists the Gender Group Code domain values for the Employees dimension table.

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

Y Oracle EBS, PeopleSoft

Table 38 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 39 Full Time Flag Domain Value (W_EMPLOYMENT_D)W_FULL_TIME_FLG SourceN Oracle EBS, PeopleSoft


Table 310 Regular Temporary Domain Value (W_EMPLOYMENT_D)W_REG_TEMP_CODE W-REG_TEMP_DESC Source

REG Regular Oracle EBS, PeopleSoft

TEMP Temporary Oracle EBS, PeopleSoft

Table 311 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

Table 312 Ethnic Group Code Domain Value Description (W_EMPLOYEE_D)W_ETHNIC_GRP W_ETHNIC_GRP_DESC Source

1 White (Not Hispanic or Latino) Oracle EBS, PeopleSoft

Table 37 (Cont.) Exempt Flag Domain Value (W_EMPLOYMENT_D)W_EXEMPT_FLG Source

W_EVENT_TYPE_D Domain Values


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

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

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.

2 Black or African American (Not Hispanic or Latino)


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)


7 Hispanic or Latino Oracle EBS, PeopleSoft

8 Two or more Races (Not Hispanic or Latino)


999 Not Specified Oracle EBS, PeopleSoft

Table 313 Veteran Status Code Domain Value (W_EMPLOYEE_D)W_VETERAN_STATUS_CODE W_VETERAN_STATUS_DESC Source1 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

Table 312 (Cont.) Ethnic Group Code Domain Value Description (W_EMPLOYEE_D)W_ETHNIC_GRP W_ETHNIC_GRP_DESC Source

W_EVENT_TYPE_D Domain Values


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 314 lists the relevant domain value columns in the W_EVENT_TYPE_D table, the possible values, and the relationship among them.

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

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

Table 314 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


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 315 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.9 W_EXPENSE_F Domain ValuesW_EXPENSE_F is used to capture all expense related data that is submitted through an expense report. Table 316 lists the relevant domain values.

Table 315 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 316 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 Oracle EBS, PeopleSoft, Universal Source

RECIEPT_FLG N No Oracle EBS, PeopleSoft, Universal Source

RECIEPT_FLG V Verified Oracle EBS, PeopleSoft

W_GL_ACCOUNT_D Domain Values


3.10 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 317 lists the domain values for W_GL_ACCOUNT_D for Financial Analytics.

Table 318 lists the domain values for W_GL_ACCOUNT_D for Commercial Financial Analytics.

Table 319 lists the domain values for W_GL_ACCOUNT_D for U.S. Federal Financial Analytics.

Table 317 W_GL_ACCOUNT_D Domain Values for Financial AnalyticsGL_ACCOUNT_CAT_CODE FIN_STMT_ITEM_CODE GROUP_ACCT_NUM Description SourceBS AP AP Accounts Payables Oracle EBS,

PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

BS AR AR Accounts Receivable Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

BS OTHERS ACC DEPCN Accrued Depreciation

Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

BS OTHERS ACC LIAB Accrued Liabilities Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

BS OTHERS CASH Cash Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

BS OTHERS CMMN STOCK Common Stock Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

BS OTHERS FG INV Finished Goods Inventory


BS OTHERS GOODWILL Goodwill Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World



BS OTHERS LT DEBT Lt Debt Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

BS OTHERS OTHER ASSET Other Asset Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

BS OTHERS OTHER CA Other Current Asset Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

BS OTHERS OTHER CL Other Current Liability


BS OTHERS OTHER EQUITY Other Equity Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

BS OTHERS OTHER LIAB Other Liability Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

BS OTHERS PPE Ppe Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

BS OTHERS PREF STOCK Preferred Stock Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

BS OTHERS PURCH Purch Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

BS OTHERS RET EARNING Retained Earning Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

BS OTHERS RM CONS Rm Cons Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

Table 317 (Cont.) W_GL_ACCOUNT_D Domain Values for Financial AnalyticsGL_ACCOUNT_CAT_CODE FIN_STMT_ITEM_CODE GROUP_ACCT_NUM Description Source



BS OTHERS RM INV Raw Material Inventory


BS OTHERS ST BORR St Borr Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

BS OTHERS WIP INV Wip Inv Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

PL COGS COGS Cost Of Goods Sold Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

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, JD Edwards EnterpriseOne, JD Edwards World

PL OTHERS EMP SUPP Employee Support And Cafeteria Expenses


PL OTHERS FREIGHT Freight Expenses Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

PL OTHERS GEN PAYROLL General Admin And Other Payroll





PL OTHERS INC TAX Income Tax Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

PL OTHERS INT EXP Interest Exp Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

PL OTHERS MKTG PAYROLL Marketing Payroll Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

PL OTHERS OTHER INC Other Income Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

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, JD Edwards EnterpriseOne, JD Edwards World

PL OTHERS R&D PAYROLL R&D Payroll Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

PL OTHERS SLS PAYROLL Sales Payroll Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World


W_HR_POSITION_D Domain Values


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

PL OTHERS VARIANCE EXP Product Variance Expenses


PL REVENUE REVENUE Sales Revenue Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

PL TAX TAX Tax Items Oracle EBS, PeopleSoft, JD Edwards EnterpriseOne, JD Edwards World

Table 318 W_GL_ACCOUNT_D Domain Values for Commercial Financial AnalyticsGL_ACCOUNT_CAT_CODE

FIN_STMT_ITEM_CODE GROUP_ACCT_NUM Description Source

BS REVENUE DEFERRED REVENUE

Deferred Revenue Oracle EBS

Table 319 W_GL_ACCOUNT_D Domain Values for U.S. Federal Financial AnalyticsGL_ACCOUNT_CAT_CODE

FIN_STMT_ITEM_CODE GROUP_ACCT_NUM Description Source

BS OTHERS UNAPPORTIONED AUTH

UNAPPORTIONED AUTHORITY

Oracle EBS

BS OTHERS APPORTIONMENT APPORTIONMENT Oracle EBS

BS OTHERS ALLOTMENT ALLOTMENT Oracle EBS

BS OTHERS COMMITMENT COMMITMENT Oracle EBS

BS OTHERS OBLIGATION OBLIGATION Oracle EBS

BS OTHERS EXPENDITURE EXPENDITURE Oracle EBS

BS OTHERS ANT RES ANTICIPATED RESOURCES

Oracle EBS

BS OTHERS APPROP RELZ APPROPRIATIONS REALIZED

Oracle EBS

BS OTHERS CONT AUTH CONTRACT AUTHORITY

Oracle EBS

BS OTHERS BORR AUTH BORROWING AUTHORITY

Oracle EBS

BS OTHERS OTHER RES OTHER RESOURCES Oracle EBS


W_JOB_D Domain Values


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

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

3.12 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 322 lists the FLSA Status Code domain values for W_JOB_D.

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

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


Table 321 Exempt Flag Domain Value (W_HR_POSITION_D)W_EXEMPT_FLG SourceN Oracle EBS, PeopleSoft


Table 322 FLSA_STAT_CODE (FLSA Status Code) Domain Value (W_JOB_D)W_FLSA_STAT_CODE W_FLSA_STAT_DESC SourceExempt Exempt Oracle EBS, PeopleSoft

Non Exempt Non Exempt Oracle EBS, PeopleSoft

Unknown Unknown Oracle EBS, PeopleSoft

Table 323 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

W_JOB_RQSTN_D Domain Values


3.13 W_JOB_RQSTN_D Domain ValuesThis section describes the Job Requisition domain values in the W_JOB_RQSTN_D table that are used in Human Resource Performance Analytics.

Table 324 lists the Status Code domain values for W_JOB_RQSTN_D.

Table lists the Category Code domain values for W_JOB_RQSTN_D.

3.14 W_MKTG_LEAD_D Domain Values W_MKTG_LEAD_D is used to maintain information on Marketing Lead Quality and Marketing Lead Outcome. Marketing Lead Status is stored in W_STATUS_D. Table 326 lists the Marketing Lead Quality domain values.

10 Executive/Senior Level Officials and Managers


999 No EEO Reporting Oracle EBS, PeopleSoft

Table 324 Status Code Domain Values (W_JOB_RQSTN_D)W_STATUS_CODE W_STATUS_DESC SourceAPPROVED Job requisition request is approved. Oracle EBS, PeopleSoft

CANCELLED Job requisition is cancelled before it is approved.


FILLED Job requisition is filled when all openings for a job requisition are filled.


REJECTED Job requisition is rejected. Oracle EBS, PeopleSoft

DRAFT Job requisition is being drafted. Oracle EBS, PeopleSoft

HOLD Job requisition is on hold. Oracle EBS, PeopleSoft

OPEN Job requisition is open while candidate sourcing, interviews, and offers take place.


UNDER REVIEW Job requisition request is submitted to management for review.


OTHER Other statuses. Oracle EBS, PeopleSoft

Table 325 Category Code Domain Values (W_JOB_RQSTN_D)W_CATEGORY_CODE W_CATEGORY_DESC Source

STANDARD Standard Job requisition Oracle EBS, PeopleSoft

ONGOING Ongoing/Continuous Job requisition Oracle EBS, PeopleSoft

Table 326 Marketing Lead Quality Domain ValuesW_QUALITY_CODE W_QUALITY_DESC Source1-Excellent Excellent Siebel CRM

2-Very High Very High Siebel CRM

Table 323 (Cont.) W_EEO_JOB_CAT_CODE (EEO Job Category Code) Domain Value (W_JOB_D)W_EEO_JOB_CAT_CODE W_EEO_JOB_CAT_DESC Source

W_PAYMENT_METHOD_D Domain Values


3.15 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 327 lists the values for the Movement Type domain value for W_MVMNT_TYPE_D.

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

3-High High Siebel CRM

4-Fair Fair Siebel CRM

5-Poor Poor Siebel CRM

Table 327 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

COMPLETION RETURN

COMPLETION RETURN

Oracle EBS

COMPLETION COMPLETION Oracle EBS

SCRAP SCRAP Oracle EBS

SCRAP RETURN

SCRAP RETURN OracleEBS

Table 328 W_PAYMENT_METHOD_D (Method Dimension Table) Domain Values


W_PAYMENT_METHOD_CODE

CASH Cash Oracle EBS, JD Edwards EnterpriseOne, JD Edwards World, PeopleSoft


CHECK Check Oracle EBS, JD Edwards EnterpriseOne, JD Edwards World, PeopleSoft


CREDIT CARD Credit Card Oracle EBS, JD Edwards EnterpriseOne, JD Edwards World, PeopleSoft

Table 326 (Cont.) Marketing Lead Quality Domain ValuesW_QUALITY_CODE W_QUALITY_DESC Source

W_PAY_TYPE_D Domain Values


3.17 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 329 lists the values for the Pay Type flag domain value for W_PAY_TYPE_D.

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


ELECTRONIC Electronic Oracle EBS, JD Edwards EnterpriseOne, JD Edwards World


DRAFT Draft JD Edwards EnterpriseOne, JD Edwards World


OTHER Other Oracle EBS, PeopleSoft


UNKNOWN Unknown JD Edwards EnterpriseOne, JD Edwards World

Table 329 W_PAY_TYPE_FLG Domain Value (W_PAY_TYPE_D)W_PAY_TYPE_FLG SourceC Oracle EBS, PeopleSoft

D Oracle EBS, PeopleSoft

Table 330 Pay Type Group Code Domain Value (W_PAY_TYPE_D)W_PAY_TYPE_GRP_CODE W_PAY_TYPE_GRP_DESC Source

BONUS 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 328 (Cont.) W_PAYMENT_METHOD_D (Method Dimension Table) Domain Values


W_RCRTMNT_EVENT_TYPE_D Domain Values


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

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

3.20 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 333 lists the relevant domain values.

3.21 W_RCRTMNT_EVENT_TYPE_D Domain ValuesThis section describes the Recruitment Event Type domain values in the W_RCRTMNT_EVENT_TYPE_D table that are used in Human Resource Performance Analytics.

Table 334 lists the Event Code domain values for W_RCRTMNT_EVENT_TYPE_D.

Table 331 W_PERSON_D table Domain ValueField Value Domain Value Domain Value Business Name Source

CONTACT_TYPE ERP_CONTACT ERP Contact Person Oracle EBS

CONTACT_TYPE CONTACT Contact Siebel

CONTACT_TYPE PROSPECT Prospect Siebel

Table 332 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 333 W_PRODUCT_D (Products Dimension Table) Domain Value


MAKE_BUY_IND B Buy Oracle EBS, JD Edwards EnterpriseOne, JD Edwards World

MAKE_BUY_IND M Make Oracle EBS, JD Edwards EnterpriseOne, JD Edwards World

Table 334 Event Code Domain Values (W_RCRTMNT_EVENT_TYPE_D)W_EVENT_CODE W_EVENT_DESC SourceRQSTN_DRAFTED Requisition Drafted Oracle EBS, PeopleSoft

W_RCRTMNT_EVENT_TYPE_D Domain Values


Table 335 lists the Stage Code and Sub Stage Code domain values for W_RCRTMNT_EVENT_TYPE_D.

RQSTN_APPROVAL_PENDING

Requisition Approval Pending Oracle EBS, PeopleSoft

RQSTN_APPROVAL_DENIED

Requisition Approval Denied Oracle EBS, PeopleSoft

RQSTN_OPEN Requisition Opened Oracle EBS, PeopleSoft

RQSTN_HOLD Requisition on Hold Oracle EBS, PeopleSoft

RQSTN_FILLED_CLOSED Requisition Filled or Closed Oracle EBS, PeopleSoft

RQSTN_CANCELLED Requisition Cancelled Oracle EBS, PeopleSoft

APPLICATION_RECEIVED Application Received Oracle EBS, PeopleSoft

ASSESSMENT_START Assessment Start Oracle EBS, PeopleSoft

ASSESSMENT_INTERVIEW Interview Oracle EBS, PeopleSoft

ASSESSMENT_INTERVIEW2 Second Interview Oracle EBS, PeopleSoft

OFFER_EXTENDED Offer extended Oracle EBS, PeopleSoft

OFFER_ACCEPTED Offer accepted Oracle EBS, PeopleSoft

APPLICATION_TERMINATED

Application Terminated Oracle EBS, PeopleSoft

HIRE Hire Oracle EBS, PeopleSoft

EMP_PERF_REVIEW First Appraisal / Review Oracle EBS, PeopleSoft

EMP_TRANSFER Transferred prior to completing first period of work band


EMP_TERMINATED Terminated prior to completing first period of work band

Oracle EBS, Pe

Date post:	26-Nov-2015
Category:	Documents
Upload:	jaguarkuppu
View:	1,407 times
Download:	59 times