Search Results hxc_bld_blk_info_types

Overview

The HXC_BLD_BLK_INFO_TYPES table is a core metadata repository within the Oracle E-Business Suite Time and Labor (HXC) engine. It functions as the master definition table for all types of supplementary information that can be attached to a timecard building block. A building block is the fundamental unit of time entry, such as a day, an hour, or a specific time period. This table defines the categories of descriptive data—like project numbers, task details, absence reasons, or custom attributes—that can be associated with these blocks to fully describe the work or absence being recorded. Its role is to provide a controlled, reusable catalog of information types that ensure data consistency and integrity across the timecard creation and processing lifecycle.

Key Information Stored

While the provided ETRM metadata does not list all columns, the structure centers on the primary key and descriptive attributes. The critical column is BLD_BLK_INFO_TYPE_ID, a unique system-generated identifier for each information type definition. Other typical columns in such a metadata table would include a NAME or MEANING column for the display name of the information type (e.g., "Project," "Expense Type"), a DESCRIPTION, and columns controlling its usage and validation, such as whether it is mandatory, its data type (number, date, character), and possibly a reference to a lookup type for predefined values. The table essentially stores the blueprint for what additional data can be captured on a timecard beyond the basic start and stop times.

Common Use Cases and Queries

This table is primarily referenced for configuration analysis, data validation, and troubleshooting integration points. Common scenarios include identifying all available information types for reporting or to understand timecard composition, and tracing which information types are assigned to specific time attributes or layouts. A frequent query involves joining with its related usage table to see the assignment of these types. For example:

• To list all defined information types: SELECT bld_blk_info_type_id, name FROM hxc_bld_blk_info_types WHERE SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE);
• To find where a specific information type is used: SELECT u.* FROM hxc_bld_blk_info_types t, hxc_bld_blk_info_type_usages u WHERE t.bld_blk_info_type_id = u.bld_blk_info_type_id AND t.name = 'PROJECT_NUMBER';

Related Objects

The HXC_BLD_BLK_INFO_TYPES table maintains critical referential integrity with other Time and Labor tables, as documented by its foreign key relationships. The primary key (BLD_BLK_INFO_TYPE_ID) is referenced by:

• HXC_BLD_BLK_INFO_TYPE_USAGES: This table defines the specific contexts or timecard layouts where an information type is applicable. The join column is HXC_BLD_BLK_INFO_TYPE_USAGES.BLD_BLK_INFO_TYPE_ID.
• HXC_MAPPING_COMPONENTS: This table is used in the process of mapping and importing time data from external systems. It references the information type to map external data elements to the correct internal Time and Labor attributes. The join column is HXC_MAPPING_COMPONENTS.BLD_BLK_INFO_TYPE_ID.

These relationships underscore the table's role as a source of valid values for configuring timecard data collection and integration mappings.