Results for “tab_page_name”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PQH_TXN_CATEGORY_ATTRIBUTES is an HR-schema table belonging to the Public Sector HR (PQH) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The ETRM description defines it as the "intersection entity between transaction category and table attributes." In practical terms, it acts as the configuration bridge that binds a defined transaction category to the specific table columns and value sets that a routing configuration exposes. Each row answers the question: for this transaction category and this table route, which attribute (column) is available, how is it displayed, and how is it validated?
Because the table stores dependent descriptive detail keyed to parent entities rather than defining those entities itself, the mined Data Vault classification is satellite-leaning. Treated as a modeling suggestion, this means the row should be understood as an attribute-bearing record attached to a transaction category hub and an attribute hub, rather than as an independent business concept. The grain is one row per transaction category attribute enabled for a given routing and edition.
Key Information Stored
The table carries 20 documented columns, of which the most consequential are listed below.
- TXN_CATEGORY_ATTRIBUTE_ID — surrogate primary key, enforced by PQH_TXN_CATEGORY_ATTRIBUTES_PK.
- TRANSACTION_CATEGORY_ID — foreign key to PQH_TRANSACTION_CATEGORIES; identifies the owning category.
- ATTRIBUTE_ID — foreign key to PQH_ATTRIBUTES; identifies the underlying column or field definition.
- TRANSACTION_TABLE_ROUTE_ID — foreign key to PQH_TABLE_ROUTE; ties the attribute to a specific routing destination.
- VALUE_SET_ID — foreign key to FRM_PART_VALUE_SETS; supplies the list of values used to validate or default the attribute.
- FORM_COLUMN_NAME and TAB_PAGE_NAME — the OAF form column and tab page on which the attribute is rendered.
- SELECT_FLAG, IDENTIFIER_FLAG, LIST_IDENTIFYING_FLAG, and MEMBER_IDENTIFYING_FLAG — behavioural switches controlling selection eligibility and identifying status.
- REFRESH_FLAG and VALUE_STYLE_CD — refresh behaviour and value presentation style.
- OBJECT_VERSION_NUMBER — optimistic locking for concurrent updates.
- ZD_EDITION_NAME — editioning discriminator; the unique index PQH_TXN_CATEGORY_ATTRIBUTES_PK covers TXN_CATEGORY_ATTRIBUTE_ID together with ZD_EDITION_NAME, making this pair the effective business-key candidate in the 12.2.2 editioned data model.
- Standard Who columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE) provide audit history.
Common Use Cases and Queries
The primary use case is diagnosing why a field appears, or fails to appear, on a Public Sector transaction page. A configuration query joining the category and attribute parents reveals the enabled attribute set:
- Attribute inventory by category: SELECT a.FORM_COLUMN_NAME, a.TAB_PAGE_NAME, a.SELECT_FLAG FROM PQH_TXN_CATEGORY_ATTRIBUTES a, PQH_TRANSACTION_CATEGORIES c WHERE a.TRANSACTION_CATEGORY_ID = c.TRANSACTION_CATEGORY_ID AND c.TRANSACTION_CATEGORY_ID = :p_category.
- Value set validation review: join VALUE_SET_ID to FRM_PART_VALUE_SETS to confirm the LOV supplying each attribute.
- Routing audit: join TRANSACTION_TABLE_ROUTE_ID to PQH_TABLE_ROUTE to verify the attribute is attached to the intended table route.
- Impact analysis: query the dependent children (PQH_COPY_ENTITY_TXNS, PQH_SPECIAL_ATTRIBUTES, PQH_FR_STAT_SITUATION_RULES) before retiring or re-pointing an attribute row.
Reporting extracts should filter on ZD_EDITION_NAME to avoid duplicating editioned rows.
Related Objects
- PQH_TRANSACTION_CATEGORIES — parent via TRANSACTION_CATEGORY_ID.
- PQH_ATTRIBUTES — parent via ATTRIBUTE_ID.
- PQH_TABLE_ROUTE — parent via TRANSACTION_TABLE_ROUTE_ID.
- FRM_PART_VALUE_SETS — parent via VALUE_SET_ID.
- PQH_COPY_ENTITY_TXNS — child keyed by TXN_CATEGORY_ATTRIBUTE_ID.
- PQH_SPECIAL_ATTRIBUTES — child keyed by TXN_CATEGORY_ATTRIBUTE_ID.
- PQH_FR_STAT_SITUATION_RULES — child keyed by TXN_CATEGORY_ATTRIBUTE_ID.
-
Intersection entity between transaction category and table attributes
-
Definition of form tab page for configurable forms
-
View: HR_FORM_TAB_PAGES_VL 12.2.2
Translated view of HR_FORM_TAB_PAGES_B and HR_FORM_TAB_PAGES_TL
APPS.HR_FORM_TAB_PAGES_VL·↳ HR_FORM_TAB_PAGES_B·↳ HR_FORM_TAB_PAGES_TL·Explore PER module →
-
Definition of form tab page for configurable forms
-
Intersection entity between transaction category and table attributes
-
View: HR_FORM_TAB_PAGES_VL 12.1.1
Translated view of HR_FORM_TAB_PAGES_B and HR_FORM_TAB_PAGES_TL
APPS.HR_FORM_TAB_PAGES_VL·↳ HR_FORM_TAB_PAGES_B·↳ HR_FORM_TAB_PAGES_TL·Explore PER module →
-
View: HR_FORM_TAB_PAGES 12.2.2
View of tab page definitions and translated properties
APPS.HR_FORM_TAB_PAGES·↳ HR_FORM_TAB_PAGES_B·↳ HR_FORM_TAB_PAGES_VL·↳ HR_TAB_PAGE_PROPERTIES_VL·Explore PER module →
-
View: HR_FORM_TAB_PAGES 12.1.1
View of tab page definitions and translated properties
APPS.HR_FORM_TAB_PAGES·↳ HR_FORM_TAB_PAGES_B·↳ HR_FORM_TAB_PAGES_VL·↳ HR_TAB_PAGE_PROPERTIES_VL·Explore PER module →
-
PACKAGE: APPS.HR_FTP_SHD 12.1.1
-
PACKAGE: APPS.HR_FTP_SHD 12.2.2
-
PACKAGE: APPS.HR_FTP_INS 12.2.2
-
PACKAGE: APPS.HR_FTP_UPD 12.1.1
-
PACKAGE: APPS.HR_FTP_INS 12.1.1
-
PACKAGE: APPS.HR_FTP_UPD 12.2.2
-
VIEW: APPS.HR_FORM_TAB_PAGES 12.1.1
-
APPS.HR_TMPLT SQL Statements 12.2.2
-
VIEW: APPS.HR_FORM_TAB_PAGES 12.2.2
-
APPS.HR_TMPLT SQL Statements 12.1.1