Search Results fnd_building_block_objects

Overview

The FND_BUILDING_BLOCK_OBJECTS table is a core metadata repository within the Oracle E-Business Suite Applications DBA (AD) module. It serves as a central catalog, defining the relationship between logical application components, known as "building blocks," and the specific physical database objects that comprise them. A building block represents a reusable unit of functionality or data, such as a setup entity or a transaction entity. This table's primary role is to enable the Oracle Applications technology stack to manage dependencies, perform impact analysis, and support patching and upgrade processes by understanding which database objects (like tables, sequences, and views) belong to which logical component. The provided metadata indicates this specific object is "Not implemented in this database," which is a common ETRM notation for tables that are part of the core data model but may not be populated or actively used in standard installations, often reserved for internal Oracle development or specific administrative tools.

Key Information Stored

The table's structure is designed to link a building block to its constituent objects through a composite primary key. The key columns are APPLICATION_ID and BUILDING_BLOCK_ID, which together identify the specific building block from the FND_BUILDING_BLOCKS table. The remaining primary key columns, OBJECT_TYPE, OBJECT_APPLICATION_ID, and OBJECT_ID, uniquely identify the associated database object. The OBJECT_TYPE would classify the object (e.g., 'TABLE', 'SEQUENCE', 'VIEW'), while OBJECT_APPLICATION_ID and OBJECT_ID form a foreign key to the corresponding object's metadata table, such as FND_TABLES, FND_SEQUENCES, or FND_VIEWS. This design allows a single building block to be associated with multiple objects of various types.

Common Use Cases and Queries

While direct operational use by customers is rare due to its metadata nature, this table is critical for system management. A primary use case is determining all database objects impacted by a change to a specific application component. For instance, if a consultant needs to understand what sequences are associated with a particular building block—perhaps relevant to a user searching for "fnd_sequences"—a query could join these tables. The foreign key relationship to FND_SEQUENCES, as documented, is key for this analysis.

Sample Query: Find sequences for a building block.
SELECT fbb.building_block_name, fs.sequence_name
FROM fnd_building_block_objects fbbo,
fnd_building_blocks fbb,
fnd_sequences fs
WHERE fbbo.application_id = fbb.application_id
AND fbbo.building_block_id = fbb.building_block_id
AND fbbo.object_application_id = fs.application_id
AND fbbo.object_id = fs.sequence_id
AND fbbo.object_type = 'SEQUENCE'
AND fbb.building_block_name = '&BLOCK_NAME';

Related Objects

As defined by its foreign keys, FND_BUILDING_BLOCK_OBJECTS has direct dependencies on several fundamental Application Object Library tables. The parent building block definition is stored in FND_BUILDING_BLOCKS. The specific database objects it references are cataloged in FND_TABLES, FND_SEQUENCES, and FND_VIEWS. This network of relationships situates FND_BUILDING_BLOCK_OBJECTS as a junction table within the broader E-Business Suite technical architecture, connecting high-level application logic with low-level database implementation details. Its existence supports the modularity and maintainability of the entire Oracle Applications system.