Results for “get_flex_info”

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

Overview

APPS.HXC_TIME_CATEGORY_UTILS_PKG is a utility package within the Oracle E-Business Suite Time and Labor module (HXC schema). It provides the underlying engine that resolves, evaluates, and totals time categories and their associated building blocks, flexfield segments, and value sets. Time categories in Time and Labor define how timecard entries are classified, validated, and mapped to payroll or project attributes. This package supplies the programmatic logic for interpreting those categories — determining which value sets apply, how components are evaluated, and how hours are aggregated against a given timecard or period.

The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking session rather than the definer, and it is heavily reused: it is referenced by 26 other packages across the Time and Labor schema. It sits beneath the user-facing timecard forms and feeds downstream processing such as payroll transfer and project costing.

Key Procedures and Functions

• MAPPING_COMPONENT_STRING / ALTERNATE_NAME_STRING — Resolve component or alias mappings into display/derivation strings used when interpreting category definitions.
• INITIALISE_TIME_CATEGORY — Loads and caches time category metadata, including the backward-compatibility structures declared at the top of the package (r_time_category, r_seg_info, r_context).
• GET_TIME_CATEGORY_ID, GET_FLEX_INFO, GET_FLEX_VALUE, GET_VALUE_SET_SQL — Lookup helpers that retrieve category identifiers, descriptive flexfield segment details, individual flex values, and generated SQL for a value set.
• EVALUATE_TIME_CATEGORY — Evaluates a time category against the applicable components and value sets to determine whether entries satisfy the category definition.
• CATEGORY_TIMECARD_HRS, CATEGORY_TIMECARD_HRS_IND, CATEGORY_DETAIL_HRS, CATEGORY_APP_PERIOD_TC_HRS — Aggregation functions that total hours for a category at the timecard, detail, or application-period level. CATEGORY_TIMECARD_HRS_IND returns an indicator-style result and is the object most directly associated with the category_timecard_hrs_ind search term.
• SUM_TC_BB_OK_HRS, CHK_TC_BB_OK — Sum hours for timecard building blocks and validate whether a building block is acceptable for the category; the package global g_tc_bb_not_ok_string accumulates failure detail.
• INSERT_TIME_CATEGORY_COMP_SQL, UPDATE_TIME_CATEGORY_COMP_SQL, DELETE_TIME_CATEGORY_COMP_SQL — Maintain the component SQL stored for a time category.
• PUSH_TIMECARD, PUSH_ATTRIBUTES, PROCESS_TC_TIMECARD — Drive population of timecard attributes and the processing of timecard data against category definitions.

Tables Accessed

• HXC_TIME_CATEGORIES — Master category definitions, including the time_sql retrieved by the csr_get_time_sql cursor.
• HXC_TIME_CATEGORY_COMPS / HXC_TIME_CATEGORY_COMP_SQL — Category components and their generated SQL, read and maintained by the component-SQL procedures.
• HXC_TIME_ATTRIBUTES / HXC_TIME_BUILDING_BLOCKS — Attribute values and building block data used during category evaluation and hour summation.
• FND_DESCR_FLEX_COLUMN_USAGES, FND_FLEX_VALUE_SETS, FND_FLEX_VALIDATION_TABLES, FND_COLUMNS — Flexfield segment usages, value set definitions, validation rules, and column metadata underpinning GET_FLEX_INFO and GET_VALUE_SET_SQL.
• HXC_ALIAS_DEFINITIONS, HXC_ALIAS_TYPES, HXC_ALIAS_TYPE_COMPONENTS, HXC_ALIAS_VALUES, HXC_BLD_BLK_INFO_TYPES, HXC_LATEST_DETAILS — Alias resolution and building-block classifications used by the mapping and evaluation routines.

Usage Notes

The package is not intended for direct end-user invocation. It is called programmatically from Time and Labor timecard forms, from concurrent programs that process timecards or transfer time to downstream modules, and from the 26 dependent packages that build on its category-evaluation and hour-aggregation routines. The CATEGORY_TIMECARD_HRS_IND and related hour functions are typically reached through these internal callers rather than through a public API.

Because it is compiled AUTHID CURRENT_USER and relies on APPS synonyms, any custom code calling it must run in a session with the appropriate APPS privileges. Implementations extending Time and Labor should treat this package as an internal utility: reference it only where a supported calling package does not already expose the required behaviour, and avoid direct DML against the underlying HXC and FND tables it manages.