Results for “fwk_tbx_project_details”

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

Overview

The AK.FWK_TBX_PROJECT_DETAILS table is a repository table within the Oracle E-Business Suite Common Modules (AK) schema. It stores task-level project definition detail used by the Oracle Application Framework (OAF) development toolset, commonly referred to as the "Toolbox" (TBX). The table holds the individual task rows that make up a project definition, including task numbering, naming, scheduling, and task typing information that supports project-based configuration and lifecycle workflows in the EBS framework layer.

The table is owned by the AK schema and carries a status of VALID in supported releases, including 12.1.1 and 12.2.2. It contains fourteen documented columns and is exposed through an Online Documentation & ETRM (Electronic Technical Reference Manual) entry, with a primary key defined on the dependent surrogate column TASK_ID.

From a heuristic Data Vault modelling perspective, FWK_TBX_PROJECT_DETAILS is classified as a standalone entity. Where a Data Vault architecture is being considered, this object is best represented as a satellite or standalone hub table, since it does not participate in a strong multi-parent relationship pattern visible in the mined foreign key structure. The single documented foreign key is directed outward to PA_TOP_TASKS_IT, which suggests this table behaves as a detail/child object rather than a conformed dimension.

Key Information Stored

The table’s primary key is TASK_ID, which is the surrogate identifier and the basis of the unique index FWK_TBX_PROJECT_DETAILS_PK. Because TASK_ID is generated as a numeric surrogate rather than derived from business data, it is not treated as a business key candidate; it is the technical row identifier.

• PROJECT_ID — the project context to which each task row belongs.
• TOP_TASK_ID — the parent or "top task" reference; documented as a foreign key column pointing to PA_TOP_TASKS_IT, linking the framework task back to the Project Accounting top task structure.
• TASK_ID — the surrogate primary key (TASK_ID in FWK_TBX_PROJECT_DETAILS_PK).
• TASK_NUMBER — the business-readable ordinal or reference number for the task.
• TASK_NAME — the descriptive label for the task.
• START_FROM — the effective start date for the task definition.
• END_TO — the effective end date for the task definition.
• TASK_TYPE — the classification of the task, used to distinguish behaviour or usage of the task row.
• TEXT_RIGHT — the trailing free-text or alignment field associated with the task.
• LAST_UPDATE_DATE — the standard Who column tracking the last modification timestamp.
• LAST_UPDATED_BY — the standard Who column identifying the user who last updated the row.
• CREATION_DATE — the standard Who column recording row creation.
• CREATED_BY — the standard Who column identifying the creating user.
• LAST_UPDATE_LOGIN — the standard Who column recording the login session of the last update.

Common Use Cases and Queries

This table is typically queried during framework diagnostics, task generation validation, and reconciliation against Project Accounting top tasks. A common pattern counts tasks per project:

SELECT PROJECT_ID, COUNT(*) FROM AK.FWK_TBX_PROJECT_DETAILS GROUP BY PROJECT_ID;

Another frequent requirement is retrieving the descriptive task rows and joining to the parent top task:

SELECT t.TASK_ID, t.TASK_NUMBER, t.TASK_NAME, t.START_FROM, t.END_TO, p.TOP_TASK_ID FROM AK.FWK_TBX_PROJECT_DETAILS t, PA_TOP_TASKS_IT p WHERE t.TOP_TASK_ID = p.TOP_TASK_ID;

Reporting scenarios include auditing Who columns for change tracking, driving date-range filters between START_FROM and END_TO, and grouping task rows by TASK_TYPE to evaluate distribution by task category. Because TASK_ID is unique, individual task rows can be retrieved directly by primary key.

Related Objects

• PA_TOP_TASKS_IT — the directly referenced foreign key parent via TOP_TASK_ID.
• FWK_TBX_PROJECT_DETAILS_PK — the unique index enforcing uniqueness on TASK_ID.
• AK schema tables — other Toolbox framework tables in the same schema, which commonly share PROJECT_ID and TASK_ID logic.
• OAF (Oracle Application Framework) runtime configuration views — consume task definitions for page and function behaviour.