Results for “position_code”

2 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FWK_TBX_EMPLOYEES is a table owned by the AK schema (Common Modules – AK) in Oracle E-Business Suite 12.1.1 and 12.2.2. It is a demonstration or framework table used by the Oracle Application Framework (OAF) "Toolbox" (TBX) sample application, which Oracle ships to illustrate standard OAF development patterns such as master-detail pages, search-and-result regions, and validation against lookup data. The table stores a roster of employee records with personal, organizational, and compensation attributes, and is populated with seeded sample rows shipped as part of the framework tutorial schema.

From a data modeling perspective, the ETRM metadata classifies this object heuristically as standalone under the Data Vault scheme. In Data Vault terms, this would suggest treating FWK_TBX_EMPLOYEES as a hub-like entity whose business key is EMPLOYEE_ID, with the remaining descriptive attributes behaving as satellite payload. Because the table carries only one outgoing foreign key, it does not participate in a classic link construct, so the standalone designation remains an appropriate modeling suggestion. Note that this table is intended for training and demonstration purposes and is not part of the production transactional data model of any Oracle EBS module.

Key Information Stored

The documented physical schema for 12.2.2 shows 33 columns, with FWK_TBX_EMPLOYEES_PK defined on EMPLOYEE_ID as the single-column unique index. The most significant columns are:

  • EMPLOYEE_ID — the surrogate primary key and the sole unique-index business-key candidate. It also carries the foreign key relationship to PSB_EMPLOYEES.EMPLOYEE_ID.
  • TITLE, FIRST_NAME, MIDDLE_NAMES, LAST_NAME, FULL_NAME — the employee's name components and honorific/title. FULL_NAME typically holds the concatenated display name used in OAF result tables.
  • EMAIL_ADDRESS — the contact e-mail address associated with the employee record.
  • MANAGER_ID — a self-referencing or external reference to the employee's manager, enabling hierarchical reporting in the sample application.
  • POSITION_CODE — a lookup-style code indicating the employee's role or job classification.
  • SALARY — the numeric compensation value stored for the employee.
  • START_DATE, END_DATE — effective dating for the employment record, supporting date-effective queries in the tutorial pages.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard EBS WHO columns that track row audit information.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) columns, reserved for client-specific extensions.

The presence of the DFF columns and the WHO audit columns confirms that the table was designed to conform to EBS table conventions, even though its primary purpose is illustrative.

Common Use Cases and Queries

The table is primarily referenced when developers build or extend OAF pages in the Toolbox sample application. Typical queries include lookups by primary key, name searches, and manager-based rollups. A simple retrieval by key follows:

  • SELECT employee_id, full_name, email_address, position_code FROM ak.fwk_tbx_employees WHERE employee_id = :p_employee_id;
  • SELECT employee_id, full_name, salary FROM ak.fwk_tbx_employees WHERE last_name LIKE :p_search || '%' ORDER BY last_name;
  • SELECT e.full_name, m.full_name AS manager_name FROM ak.fwk_tbx_employees e LEFT JOIN ak.fwk_tbx_employees m ON e.manager_id = m.employee_id;

Reporting use cases usually involve the OAF sample dashboards, where the table drives result-table regions and simple salary or headcount summaries. Because the table is seeded rather than transactional, it is rarely joined to production HR tables in customer solutions, though the FK to PSB_EMPLOYEES can be used in lab exercises to demonstrate multi-table joins.

Related Objects

The documented FK relationship links FWK_TBX_EMPLOYEES.EMPLOYEE_ID to PSB_EMPLOYEES.EMPLOYEE_ID; PSB_EMPLOYEES is therefore the principal parent object to consider when joining. Other objects that typically interact with this table in the Toolbox framework include:

  • PSB_EMPLOYEES — the referenced parent via EMPLOYEE_ID, providing the broader employee record used in OAF demos.
  • FWK_TBX_EMPLOYEES_PK — the primary-key index that guarantees uniqueness of EMPLOYEE_ID and is used by all row-level access paths.
  • AK schema OAF Toolbox views and pages — the web-tier Java and XML page definitions that bind to this table for the sample Search and Detail pages.
  • AK lookup / flexfield objects — any lookup types referenced by POSITION_CODE and the ATTRIBUTE_CATEGORY DFF, which resolve codes stored in this table to their displayed meanings.

In EBS 12.2.2 the table is validated and available under the AK schema; in 12.1.1 it is likewise present as part of the same framework. Because it is a demonstration object, it should be treated as read-only reference content rather than a target for custom data entry.