Search Results fnd_building_block_objects_pk

Overview

FND_BUILDING_BLOCK_OBJECTS is an Applications DBA (AD) repository table that records the individual database objects which collectively comprise a building block. In the Oracle EBS 12.1.1 and 12.2.2 architectures, building blocks (ADR, ARU, and other patchable container abstractions) group related tables, views, and sequences so that the AutoPatch and AD utilities can reason about a patchable unit rather than a loose collection of objects. This table is the association layer that binds each building block to its member objects.

The ETRM metadata flags this object as Not implemented in this database, meaning it is not installed or populated in every EBS instance; its presence and contents depend on the AD configuration. From a Data Vault modeling perspective, the heuristic classification mined from the FK structure is link. This is consistent with the table's role: it resolves a many-to-many relationship between building blocks and the database objects they contain, and it carries no descriptive attributes of its own beyond the association keys.

Key Information Stored

The table is intentionally narrow. Its documented columns are the composite primary key members and the foreign key columns that establish membership:

• APPLICATION_ID — identifies the application context of the building block; part of the primary key and FK to FND_BUILDING_BLOCKS.
• BUILDING_BLOCK_ID — the surrogate identifier of the parent building block; part of the PK and FK to FND_BUILDING_BLOCKS.
• OBJECT_TYPE — discriminates the kind of member object (for example TABLE, VIEW, or SEQUENCE); part of the PK.
• OBJECT_APPLICATION_ID — the owning application of the referenced object; part of the PK and the shared FK column used against FND_TABLES, FND_SEQUENCES, and FND_VIEWS.
• OBJECT_ID — the identifier of the member object within its type-specific repository; part of the PK and the second column of the shared FK.

The composite primary key FND_BUILDING_BLOCK_OBJECTS_PK spans (APPLICATION_ID, BUILDING_BLOCK_ID, OBJECT_TYPE, OBJECT_APPLICATION_ID, OBJECT_ID). There is no separate single-column surrogate key; the natural business key is the full composite, and uniqueness is enforced by that primary key rather than a distinct unique index. Because the object reference is polymorphic — the same (OBJECT_APPLICATION_ID, OBJECT_ID) pair can point at a table, a view, or a sequence — the OBJECT_TYPE column disambiguates which FK target is authoritative for a given row.

Common Use Cases and Queries

The primary use case is impact analysis: determining which building block owns a given table, view, or sequence before applying or backing out a patch. A typical query joins to FND_BUILDING_BLOCKS to resolve the block name and then filters by the referenced object:

• List all objects in a building block: SELECT OBJECT_TYPE, OBJECT_APPLICATION_ID, OBJECT_ID FROM FND_BUILDING_BLOCK_OBJECTS WHERE BUILDING_BLOCK_ID = :bb AND APPLICATION_ID = :app;
• Find the owning block for a known object: filter on OBJECT_TYPE, OBJECT_APPLICATION_ID, and OBJECT_ID and join back to FND_BUILDING_BLOCKS.
• Inventory by object class: GROUP BY OBJECT_TYPE to count tables versus views versus sequences per block.
• Sequence-specific reporting: the user's search for "fnd_sequences" maps directly to the FK path from this table to FND_SEQUENCES, so joins on (OBJECT_APPLICATION_ID, OBJECT_ID) with OBJECT_TYPE = 'SEQUENCE' enumerate sequences packaged in each block.

Because the table is not implemented in all databases, queries should be guarded to tolerate a missing or empty result set in environments where AD metadata is not staged.

Related Objects

The FK structure documented in the ETRM metadata identifies the following significant dependencies:

• FND_BUILDING_BLOCKS — parent table joined on APPLICATION_ID and BUILDING_BLOCK_ID; supplies the block definition.
• FND_TABLES — referenced via OBJECT_APPLICATION_ID and OBJECT_ID for table-type members.
• FND_SEQUENCES — referenced via OBJECT_APPLICATION_ID and OBJECT_ID for sequence-type members; directly relevant to the "fnd_sequences" search.
• FND_VIEWS — referenced via OBJECT_APPLICATION_ID and OBJECT_ID for view-type members.

Together these form the AD building-block object map, and they are the objects most commonly joined when resolving block membership or performing patch-impact reporting.