Search Results get_mapping_value




Overview
Explore in AI Chat

Overview

HXC_MAPPING_UTILITIES is a public PL/SQL package body in the APPS schema that supports the Oracle E-Business Suite Time and Labor (formerly OTM) mapping infrastructure. Its central responsibility is to resolve mapping values: given a set of mapping identifiers, timebuilding block context, and date information, it derives and returns the value that a configured mapping should produce for a timecard time building block. It is a companion to the mapping definition and mapping component tables that define how time attributes are transformed into values consumed by retrieval and deposit processes.

The package also validates the freshness of mapping and building block configuration. Caching and change-detection routines allow callers to avoid re-deriving or re-applying mappings when neither the mapping definition nor the underlying time data has changed. The header comments confirm the package has been maintained through release 12.1.0 (hxcmputl.pkb 120.7.12010000.3), and the same object is documented in the 12.2.2 ETRM metadata, indicating continuity across the 12.1.1 and 12.2.2 code lines.

Key Procedures and Functions

  • GET_MAPPING_VALUE — the flagship function users search for; returns the resolved value produced by a mapping for a given time building block or attribute context. It is the primary entry point for consumers needing a single mapped result.
  • GET_MAPPINGVALUE_SUM — returns an aggregated (summed) mapping value, used where numeric attribute mappings must be accumulated across multiple components or building blocks rather than returned as a single scalar.
  • GET_DAY_DATE — resolves the start or stop date of a day-level (non-RANGE) time building block by walking to its parent. Visible in the packaged cursor where it supplies the effective start_time and stop_time for blocks whose type is not 'RANGE'.
  • CHK_MAPPING_CHANGED — determines whether a mapping definition has changed since a previously recorded state, enabling conditional re-derivation of mapped values.
  • CHK_BLD_BLK_CHANGED — determines whether a time building block has changed, used to invalidate cached mapping results for that block.
  • CHK_MAPPING_EXISTS — verifies that a mapping is configured, allowing callers to bypass mapping logic when no definition is present.
  • ATTRIBUTE_COLUMN — maps a time attribute to its corresponding column or storage location, supporting dynamic attribute handling within the mapping engine.

Tables Accessed

The package operates over the Time and Labor mapping data model. It reads HXC_MAPPINGS, HXC_MAPPING_COMPONENTS, and HXC_MAPPING_COMP_USAGES to obtain mapping definitions and their component composition. HXC_TIME_ATTRIBUTES and HXC_TIME_ATTRIBUTE_USAGES provide the time attribute definitions and their usage context. HXC_TIME_BUILDING_BLOCKS is the principal transactional source, filtered in the packaged cursor on the maximum OBJECT_VERSION_NUMBER, scope, type, start/stop times, measure, date_to, and comment text. HXC_BLD_BLK_INFO_TYPES and HXC_BLD_BLK_INFO_TYPE_USAGES supply building block information type configuration. FND_PRODUCT_INSTALLATIONS is consulted to confirm the owning product installation. HXC_DEPOSIT_PROCESSES and HXC_RETRIEVAL_PROCESSES provide the deposit and retrieval process context in which mapped values are consumed. PLITBLM appears in the reference list as the PL/SQL table and index-by table type facility used internally.

Usage Notes

HXC_MAPPING_UTILITIES is invoked indirectly rather than through a user-facing form. It is called by retrieval and deposit processing logic and by other Time and Labor packages; the ETRM metadata records that it is referenced by 4 other packages, with GET_MAPPING_VALUE and GET_MAPPINGVALUE_SUM forming the public contract those callers depend on. Custom code extending Time and Labor mapping behavior should call GET_MAPPING_VALUE with the appropriate identifiers rather than querying the mapping tables directly, thereby honoring the change-detection and existence checks (CHK_MAPPING_CHANGED, CHK_BLD_BLK_CHANGED, CHK_MAPPING_EXISTS). The package is executed within the APPS schema under standard EBS database privileges, and its cached or change-aware results should be treated as valid only for the installation and process context established by FND_PRODUCT_INSTALLATIONS and the deposit/retrieval process records.