Search Results psb_attribute_types

Overview

PSB.PSB_ATTRIBUTE_TYPES is a configuration table within the Public Sector Budgeting (PSB) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. The ETRM metadata describes it as the "assignment table details of attribute types" — in practice, it is the master reference that defines and classifies the attribute types available to the budgeting attribute framework. Each row establishes one attribute type and, critically, supplies the metadata-driven SQL fragments (select column, select table, select key, and where clause) that the PSB engine uses to dynamically resolve attribute values at runtime. Rather than storing transaction-level attribute data itself, this table governs how such data is retrieved, linked, and validated.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. This suggests a modeling approach in which PSB_ATTRIBUTE_TYPES functions effectively as a reference or "hub-like" table: it carries its own primary key, has no upward foreign keys to other tables, and is referenced by dependent tables. Analysts building a vault-style model should treat it as a reusable reference row source rather than as a transactional entity or a link table.

Key Information Stored

The table is documented with 14 physical columns in the 12.1.1 schema. The most significant are:

• ATTRIBUTE_TYPE_ID — the surrogate primary key, enforced by the constraint PSB_ATTRIBUTE_TYPES_PK and mirrored by the unique index PSB_ATTRIBUTE_TYPES_U1. This is also the business-key candidate documented for the table.
• ATTRIBUTE_TYPE and NAME — the type code and the user-facing description of the attribute type.
• SELECT_COLUMN, SELECT_TABLE, SELECT_KEY, SELECT_WHERE — the dynamic query components that tell the PSB engine which column, table, key, and filter to apply when resolving attribute values.
• LINK_KEY and LINK_TYPE — control how the resolved attribute is joined or related to the budget line being processed.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard Oracle EBS WHO columns recording audit and creation history.

Because the retrieval behavior is data-driven, changes to these SQL fragment columns directly alter how dependent attributes are populated, making them high-impact configuration fields.

Common Use Cases and Queries

Typical uses include auditing the configured attribute types, diagnosing why an attribute value failed to resolve, and documenting the metadata-driven select logic for a given type.

-- List all defined attribute types
SELECT attribute_type_id, attribute_type, name
FROM   psb.psb_attribute_types
ORDER  BY attribute_type;

-- Inspect the dynamic resolution logic for a type
SELECT attribute_type, select_table, select_column,
       select_key, select_where, link_key, link_type
FROM   psb.psb_attribute_types
WHERE  attribute_type = :type_code;

Reporting scenarios frequently join this table to PSB_ATTRIBUTES to enumerate the attributes assigned under each type, and to identify recently modified configurations using LAST_UPDATE_DATE and LAST_UPDATED_BY.

Related Objects

The FK data identifies the primary dependent object, and standard PSB framework tables provide additional related context:

• PSB_ATTRIBUTES — the key dependent table; joins via PSB_ATTRIBUTES.ATTRIBUTE_TYPE_ID = PSB_ATTRIBUTE_TYPES.ATTRIBUTE_TYPE_ID.
• PSB_ATTRIBUTE_TYPES_PK and PSB_ATTRIBUTE_TYPES_U1 — the primary key constraint and unique index on ATTRIBUTE_TYPE_ID.
• PSB budgeting attribute and worksheet definition tables that consume attribute metadata during budget entry and reporting.
• Standard Oracle EBS WHO/audit lookup views used to resolve LAST_UPDATED_BY and CREATED_BY to application users.

Because the table is classified as standalone, it should be treated as a controlled reference source; all maintenance should preserve the integrity of the SQL fragment columns, since dependent PSB processing relies directly on them.