Search Results get_mappingvalue_sum
Overview
The APPS.HXC_INTEGRATION_LAYER_V2_GRP package body is a Time and Labor (OTL / HXC schema) integration wrapper that belongs to the Oracle E-Business Suite HRMS family. Within Oracle EBS 12.1.1 and 12.2.2, it functions as a thin façade over the core mapping utility package HXC_MAPPING_UTILITIES. Its primary business purpose is to expose the mapping-sum retrieval logic so that upstream integration processes—such as Time Store entry, retrieval, and payroll costing flows—can resolve and aggregate field-level mapping values without directly coupling to the base utility package. The "_GRP" classification indicates a group or gateway package whose role is to aggregate and forward calls rather than implement business logic itself. The header comment ($Header: hxcintegrationv2.pkb 120.0 2005/05/29 ...) confirms it is a long-standing component of the OTL integration layer, unchanged in structure across the 12.1.1 and 12.2.2 releases.
Key Procedures and Functions
The package body documents a single program unit:
- GET_MAPPINGVALUE_SUM — A
NUMBER-returning function that accepts a primary build-block information type and field name, plus up to four additional optional selector sets (each comprising a build-block information type, field name, and field value), together with a status and resource identifier. Internally it declares a locall_return NUMBER, invokesHXC_MAPPING_UTILITIES.get_mappingvalue_sumusing named parameter notation, and returns the resulting aggregate.
The signature supports up to five mapping criteria, allowing callers to sum mapping values that are filtered by multiple build-block/field/value combinations. The optional parameters beyond the first pair default to null, so the function degrades gracefully to a single-criterion lookup. No independent computation occurs inside this body; it is purely a delegation layer.
Tables Accessed
The ETRM metadata records no direct table references through APPS synonyms for this package body. All data access is indirect: the actual reads occur inside HXC_MAPPING_UTILITIES, which resolves rows from the OTL mapping and build-block information tables (such as the mapping definition and build-block info type/value structures). Because the wrapper performs no SQL of its own, it contributes no direct read or write footprint against the EBS data model. Consumers relying on this package should treat table access as governed entirely by the underlying utility package.
Usage Notes
The package is referenced by one other package, confirming its role as a shared callable within the OTL integration stack. It is typically invoked from custom PL/SQL that needs to reuse the standard OTL mapping-sum logic—for example, when deriving aggregated time attributes during Time Store integration or when extending Time and Labor configuration. It is not associated with a user-facing form or concurrent program of its own; instead, it is called programmatically by the integration layer and by custom extensions that require mapping-value aggregation with multiple filter criteria. Because it delegates to HXC_MAPPING_UTILITIES, any mapping rule changes maintained through the OTL setup are automatically reflected without modification to this wrapper. The p_status and p_resource_id parameters allow resource-scoped evaluation, making the function suitable for per-resource processing loops in batch or online integrations.
-
PACKAGE BODY: APPS.HXC_INTEGRATION_LAYER_V2_GRP
12.1.1
-
PACKAGE: APPS.HXC_INTEGRATION_LAYER_V2_GRP
12.1.1
-
PACKAGE: APPS.HXC_INTEGRATION_LAYER_V2_GRP
12.2.2
-
PACKAGE BODY: APPS.HXC_INTEGRATION_LAYER_V2_GRP
12.2.2
-
PACKAGE: APPS.HXC_INTEGRATION_LAYER_V1_GRP
12.1.1
-
PACKAGE BODY: APPS.PO_HXC_INTERFACE_PVT
12.1.1
-
PACKAGE: APPS.HXC_INTEGRATION_LAYER_V1_GRP
12.2.2
-
PACKAGE BODY: APPS.PO_HXC_INTERFACE_PVT
12.2.2
-
PACKAGE: APPS.HXC_MAPPING_UTILITIES
12.1.1
-
PACKAGE: APPS.HXC_MAPPING_UTILITIES
12.2.2
-
PACKAGE BODY: APPS.HXC_INTEGRATION_LAYER_V1_GRP
12.2.2
-
PACKAGE BODY: APPS.HXC_INTEGRATION_LAYER_V1_GRP
12.1.1
-
APPS.PO_HXC_INTERFACE_PVT dependencies on PO_DEBUG
12.1.1
-
APPS.HXC_INTEGRATION_LAYER_V2_GRP dependencies on HXC_INTEGRATION_LAYER_V2_GRP
12.1.1
-
APPS.HXC_INTEGRATION_LAYER_V2_GRP dependencies on HXC_INTEGRATION_LAYER_V2_GRP
12.2.2
-
APPS.HXC_INTEGRATION_LAYER_V1_GRP dependencies on HXC_MAPPING_UTILITIES
12.2.2
-
APPS.HXC_INTEGRATION_LAYER_V2_GRP dependencies on HXC_MAPPING_UTILITIES
12.1.1
-
APPS.HXC_INTEGRATION_LAYER_V2_GRP dependencies on HXC_MAPPING_UTILITIES
12.2.2
-
APPS.PO_HXC_INTERFACE_PVT dependencies on PO_DEBUG
12.2.2
-
APPS.HXC_INTEGRATION_LAYER_V1_GRP dependencies on HXC_MAPPING_UTILITIES
12.1.1
-
PACKAGE BODY: APPS.HXC_MAPPING_UTILITIES
12.1.1
-
PACKAGE BODY: APPS.HXC_MAPPING_UTILITIES
12.2.2
-
APPS.HXC_MAPPING_UTILITIES dependencies on HXC_MAPPING_UTILITIES
12.2.2
-
APPS.HXC_MAPPING_UTILITIES dependencies on HXC_MAPPING_UTILITIES
12.1.1
-
APPS.HXC_MAPPING_UTILITIES dependencies on HR_UTILITY
12.2.2
-
APPS.HXC_MAPPING_UTILITIES dependencies on HR_UTILITY
12.1.1
-
APPS.RCV_HXT_GRP dependencies on FND_GLOBAL
12.1.1
-
APPS.RCV_HXT_GRP dependencies on FND_GLOBAL
12.2.2
-
PACKAGE BODY: APPS.RCV_HXT_GRP
12.1.1
-
PACKAGE BODY: APPS.RCV_HXT_GRP
12.2.2