Results for “fnd_building_blocks”

6 results




Overview
Explore in AI Chat

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

Overview

FND_BUILDING_BLOCKS is an Applications DBA (AD) repository table that stores the definition of building blocks used during Oracle E-Business Suite installation, patching, and upgrade operations. A building block represents a logical grouping of application objects that the AD utilities (such as AutoPatch and the Rapid Install/upgrade drivers) treat as a single deployable unit. The table resides in the APPLSYSPUB/APPLSYS schema tier and is consulted by the AD layer to determine which objects belong to which block, thereby governing how patches are applied and how the file system and database are synchronized during an upgrade.

From a Data Vault modeling perspective, the metadata heuristic classifies FND_BUILDING_BLOCKS as satellite-leaning. This classification is suggested because the table functions primarily as a descriptive container reached from a parent application hub (FND_APPLICATION) and read by downstream consumer tables rather than acting as a pure hub of independent business entities. It is best treated as a satellite of the application context, holding descriptive attributes keyed by APPLICATION_ID and BUILDING_BLOCK_ID.

Key Information Stored

The table's structure is deliberately narrow, its integrity enforced through three primary keys and a foreign key to the application registry.

  • APPLICATION_ID — Identifies the owning Oracle application (for example, FND, GL, or AP) as registered in FND_APPLICATION. It is the leading column of all three keys and scopes every building block to a single application.
  • BUILDING_BLOCK_ID — The surrogate identifier for an individual building block. Combined with APPLICATION_ID it forms the primary key FND_BUILDING_BLOCKS_PK.
  • BUILDING_BLOCK_NAME — The descriptive, human-readable name of the block. Together with APPLICATION_ID it forms unique key FND_BUILDING_BLOCKS_UK1, making it a business-key candidate.
  • BUILDING_BLOCK_SHORTNAME — The abbreviated identifier (building_block_shortname) used internally by AD utilities to reference the block compactly. With APPLICATION_ID it forms unique key FND_BUILDING_BLOCKS_UK2, so it is a second business-key candidate and the natural lookup token for scripts and diagnostics.

Columns beyond these are implementation details and are not documented in the ETRM metadata. Note the explicit statement that the object is "Not implemented in this database," meaning the table may be absent or empty in a given environment and should not be relied upon as a populated reporting source.

Common Use Cases and Queries

Because FND_BUILDING_BLOCKS drives AD processing rather than end-user transactions, its use cases center on patch analysis, upgrade diagnostics, and metadata reconciliation.

Looking up a block by the shortname is the most direct query:

  • SELECT application_id, building_block_id, building_block_name FROM fnd_building_blocks WHERE building_block_shortname = :shortname;
  • Resolving the application context by joining to FND_APPLICATION on APPLICATION_ID to translate numeric IDs into application short names.
  • Enumerating all blocks for an application of interest to scope an upgrade plan.
  • Joining to FND_BUILDING_BLOCK_OBJECTS to list the objects each block contains, supporting impact analysis before applying a patch.
  • Detecting orphaned or duplicate business keys by counting occurrences of BUILDING_BLOCK_SHORTNAME or BUILDING_BLOCK_NAME within an application.

These queries are typically run by DBAs and upgrade engineers, not by functional users, and are most valuable during pre-upgrade validation and post-patch verification.

Related Objects

The documented foreign key relationships define the table's immediate neighborhood.

  • FND_APPLICATION — Referenced through FND_BUILDING_BLOCKS.APPLICATION_ID; supplies the owning application definition and is the parent hub for the satellite relationship.
  • FND_BUILDING_BLOCK_OBJECTS — The primary dependent table; its APPLICATION_ID and BUILDING_BLOCK_ID columns reference this table, mapping each block to the individual application objects it contains. This is the most significant downstream consumer of the building block definition.
  • AD utility objects — Patches and upgrade drivers that read building block definitions to sequence object deployment, referenced indirectly rather than through formal constraints.

Together these objects form a compact dependency cluster in which FND_BUILDING_BLOCKS acts as the descriptive link between an application and the constituent objects deployed under it.