Results for “hxc_bld_blk_info_types”

50+ results




Overview
Explore in AI Chat

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

Overview

The HXC_BLD_BLK_INFO_TYPES table, owned by the HXC schema (Time and Labor Engine), defines the catalogue of build block information types used by Oracle E-Business Suite time collection and rules processing. Within the Time and Labor Engine, a "build block" is a logical grouping of information elements that the rules engine assembles when constructing timecards, applying time rules, and preparing records for payroll or project costing. This table acts as the master registry that classifies each such information type, binding it to a legislative context and a descriptive flexfield definition, and controlling whether the type may appear multiple times within a single build block.

From a Data Vault modelling perspective, the metadata's heuristic classification places this object as hub-leaning. This classification suggests that BLD_BLK_INFO_TYPE_ID functions as a durable business key that anchors references from multiple dependent tables, with the descriptive attributes acting in a satellite capacity. Analysts designing a warehouse layer over EBS should treat this table as a reference or dimension hub rather than a transaction-bearing entity.

Key Information Stored

The table contains 42 documented columns in the 12.2.2 physical schema. The most significant include:

  • BLD_BLK_INFO_TYPE_ID — the surrogate primary key, enforced by the unique index HXC_BUILD_BLK_INFO_TYPES_PK. This is the single documented business-key candidate and the value returned when users search on "bld_blk_info_type_id."
  • LEGISLATION_CODE — identifies the legislative or country context in which the information type is valid, enabling jurisdiction-specific build block configurations.
  • DESCRIPTIVE_FLEXFIELD_NAME — names the descriptive flexfield that supplies the additional, context-dependent attributes captured for each information type.
  • BLD_BLK_INFO_TYPE — the functional classification value describing the nature of the information block.
  • MULTIPLE_OCCURENCES_FLAG — a control flag indicating whether the information type may appear more than once within a build block.
  • OBJECT_VERSION_NUMBER — the optimistic locking column used by the EBS framework during concurrent updates.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns tracking record provenance and last modification.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — the descriptive flexfield segments supporting installation-specific extensions without schema change.

Common Use Cases and Queries

Typical reporting and integration scenarios resolve the identifier to its descriptive definition, or enumerate all information types valid for a given legislation. A representative join retrieves usage rows with their parent definitions:

  • SELECT t.BLD_BLK_INFO_TYPE_ID, t.BLD_BLK_INFO_TYPE, t.LEGISLATION_CODE, u.* FROM hxc.hxc_bld_blk_info_types t, hxc.hxc_bld_blk_info_type_usages u WHERE t.bld_blk_info_type_id = u.bld_blk_info_type_id;
  • Filtering by LEGISLATION_CODE to list the information types applicable to a country or legislative regime.
  • Querying MULTIPLE_OCCURENCES_FLAG to audit which types permit repeated entry within a build block.
  • Reading ATTRIBUTE_CATEGORY and the ATTRIBUTE1–30 columns to expose flexfield-driven custom attributes in downstream extracts.

Related Objects

The table is referenced by several dependent objects through the BLD_BLK_INFO_TYPE_ID column:

Together these relationships make HXC_BLD_BLK_INFO_TYPES the central reference point for time attribute definition and mapping within the Time and Labor Engine.