Search Results pse_pk

Overview

PA_STRUCTURE_TYPES is a table within the PA (Projects) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. According to the ETRM repository, the object holds user-defined Structure Types and carries a documented status of VALID, but its description explicitly qualifies it as being reserved "for future use." In practice this means the table exists as part of the delivered Projects schema, is fully defined at the database level, and participates in the referential model, yet is not a primary transactional driver of standard project setup flows in the current release.

From a dimensional modeling perspective, the mined relationship data classifies PA_STRUCTURE_TYPES heuristically as a standalone object. This should be read as a modeling suggestion rather than a definitive Data Vault assignment: although the table enforces a foreign key outward to BOM_STRUCTURE_TYPES_B, no documented child objects reference it, which suggests that a hub-style treatment for STRUCTURE_TYPE_ID — potentially combined with a satellite for the descriptive and attribute columns — would be reasonable until additional dependents are confirmed.

Key Information Stored

The documented physical schema comprises 26 columns under the PA owner. The most significant are the following.

• STRUCTURE_TYPE_ID — the surrogate identifier for each structure type, and the leading column of the primary key (PSE_PK) as well as of unique index PA_STRUCTURE_TYPES_U1. This is the column most likely to appear as a foreign key in any dependent object.
• STRUCTURE_TYPE — the business-facing name or code of the structure type. It is the leading column of unique index PA_STRUCTURE_TYPES_U2, making it a business-key candidate alongside the edition discriminator.
• STRUCTURE_TYPE_CLASS_CODE — classifies the structure type. It anchors PA_STRUCTURE_TYPES_U3 and functions as the third documented business-key candidate. Because it is a code rather than an ID, expected values and meanings should be validated against the underlying lookup before being reported on.
• RECORD_VERSION_NUMBER — supports optimistic locking and row versioning, allowing concurrent updates to be detected reliably.
• Standard WHO audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN record the insert and most recent modification context for each row and are the standard basis for audit and lineage reporting.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the DFF (descriptive flexfield) segment set. These are only meaningful when the descriptive flexfield is configured and populated for this table; otherwise they remain null.
• ZD_EDITION_NAME — the editioning discriminator. It participates in all three unique indexes (U1, U2, and U3) as the trailing column, so uniqueness is scoped by edition. Any ad-hoc uniqueness check or key-based lookup must include this column to be edition-correct under the 12.2.x editioning architecture.

Common Use Cases and Queries

Because the object is designated for future use, the most common practical scenarios are inventory and impact analysis rather than day-to-day reporting. Typical patterns include checking for populated rows before assuming the structure type feature is active, environment comparison between instances, and tracing the foreign key path back to BOM_STRUCTURE_TYPES_B.

• Confirming whether the table contains data: SELECT COUNT(*) FROM pa.pa_structure_types;
• Listing valid, unique business keys per edition: SELECT structure_type_id, structure_type, structure_type_class_code, zd_edition_name FROM pa.pa_structure_types ORDER BY structure_type_id;
• Resolving the parent structure type through the documented foreign key: SELECT p.structure_type_id, p.structure_type, b.structure_type_name FROM pa.pa_structure_types p, bom.bom_structure_types_b b WHERE p.structure_type_id = b.structure_type_id;
• Detecting DFF usage: filter on attribute_category IS NOT NULL to determine whether the descriptive flexfield has been configured for this object.
• Audit extraction: select CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and RECORD_VERSION_NUMBER for change-tracking reports.

Related Objects

The documented referential footprint of this table is deliberately narrow.

• BOM_STRUCTURE_TYPES_B — the sole documented foreign key target, joined on STRUCTURE_TYPE_ID. This is the primary dependency to inspect when validating that a PA structure type points at a valid BOM structure type.
• PA_STRUCTURE_TYPES_U1, U2, U3 — the unique indexes on (STRUCTURE_TYPE_ID, ZD_EDITION_NAME), (STRUCTURE_TYPE, ZD_EDITION_NAME), and (STRUCTURE_TYPE_CLASS_CODE, ZD_EDITION_NAME) respectively. These are not separate tables but define the uniqueness contract that any ETL or interface must respect.
• PSE_PK — the primary key constraint over the structure type identifier, and the anchor for any future foreign key created by a dependent object.

No child tables, views, or public APIs referencing PA_STRUCTURE_TYPES are documented in the available metadata. Consequently, integration and interface design should treat the table as an upstream or leaf object until a dependent is formally identified.