Results for “bld_blk_info_type_usage_id”

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

Overview

HXC_BLD_BLK_INFO_TYPE_USAGES is a table in the HXC schema, owned by the Time and Labor Engine product within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is "Build Block Information Type Usages." The table records the association between building block categories and the information types available to them within the Time and Labor configuration model. Building blocks in Oracle Time and Labor are reusable rule containers used to assemble time calculation, validation, and accrual logic. This table governs which information types are consumed by a given building block category, forming part of the metadata that drives how timecards and time entry pages are rendered and validated.

The ETRM metadata assigns a heuristic Data Vault classification of satellite-leaning to this object. Under that modeling suggestion, the table behaves as a descriptive satellite attached to a parent hub represented by HXC_BLD_BLK_INFO_TYPES. Its primary key is a surrogate identifier rather than a natural business key, and its single documented foreign key points upward to the information types table, which is consistent with a satellite capturing attribute detail about a parent entity.

Key Information Stored

The documented physical schema contains nine columns for the 12.2.2 release.

• BLD_BLK_INFO_TYPE_USAGE_ID — the surrogate primary key, enforced by unique index HXC_BLD_BLK_INFO_TYPE_USAGE_PK. This is the only documented business-key candidate; no alternate unique index is recorded.
• BLD_BLK_INFO_TYPE_ID — the foreign key column referencing HXC_BLD_BLK_INFO_TYPES. It identifies which information type is being associated with the usage record.
• BUILDING_BLOCK_CATEGORY — the category value that scopes the usage, determining the building block context in which the referenced information type applies.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Application Object Library to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns capturing creation and modification provenance and the login context of the last change.

The combination of BLD_BLK_INFO_TYPE_ID and BUILDING_BLOCK_CATEGORY carries the substantive business meaning, while the surrogate key exists primarily for referential integrity and row-level identification.

Common Use Cases and Queries

Typical usage centers on configuration validation and diagnostics. Administrators investigating why a given information type is or is not available to a building block category can query this table directly. A common pattern joins the usage rows back to the parent information type table:

• SELECT u.BLD_BLK_INFO_TYPE_USAGE_ID, u.BUILDING_BLOCK_CATEGORY, u.BLD_BLK_INFO_TYPE_ID, t.NAME FROM HXC_BLD_BLK_INFO_TYPE_USAGES u, HXC_BLD_BLK_INFO_TYPES t WHERE u.BLD_BLK_INFO_TYPE_ID = t.BLD_BLK_INFO_TYPE_ID;
• Filtering by BUILDING_BLOCK_CATEGORY to list every information type consumed by a specific category.
• Counting usages per information type to identify orphaned or heavily reused definitions ahead of a configuration migration.
• Auditing LAST_UPDATED_BY and LAST_UPDATE_DATE to attribute configuration drift to a specific user and date.

Because the table is configuration metadata rather than transactional timecard data, reporting volumes are low and queries are typically ad hoc or part of pre-upgrade and setup verification scripts.

Related Objects

The most significant relationship is the documented foreign key from HXC_BLD_BLK_INFO_TYPE_USAGES.BLD_BLK_INFO_TYPE_ID to HXC_BLD_BLK_INFO_TYPES. That parent table supplies the information type definition referenced by each usage row and is the natural join partner for any descriptive query.

Beyond that relationship, the table participates in the broader HXC building block and information type model. Applications built on the Time and Labor Engine use the API layer supplied by the product rather than writing to this table directly, so configuration changes should flow through the supported HXC setup interfaces. The standard WHO audit columns also tie rows to FND_USER through CREATED_BY and LAST_UPDATED_BY for audit reconstruction. Any dependent objects not represented in the supplied ETRM extract should be confirmed against the deployment's data dictionary before being relied upon.