Results for “hxc_approval_comps_v”

38 results




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

Overview

HXC_APPROVAL_COMPS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, defined within the HXC (Time and Labor Engine) product family. It exposes configuration data for approval components, which are the discrete rule elements that make up an approval style in Oracle Time and Labor and related modules. Each row represents a single approval component that governs how a timecard, time entry, or time-related transaction is routed, assigned, or automatically processed. The view is validated and available in both 12.1.1 and 12.2.2.

Because the view consolidates descriptive names, lookup meanings, time category details, recipient information, and workflow attributes into a denormalized, business-friendly result set, it is suitable for reporting, data migration validation, and integration extracts. It is the principal interface through which functional consultants and technical developers inspect how approval styles are composed without joining the underlying transactional configuration tables directly.

Underlying Base Objects

HXC_APPROVAL_COMPS_V is defined as a UNION of two SELECT statements. The primary base tables are HXC_APPROVAL_COMPS (the approval component definitions) joined to HXC_APPROVAL_STYLES (the parent style), HXC_TIME_RECIPIENTS, HXC_TIME_CATEGORIES, HR_STANDARD_LOOKUPS, and PER_PEOPLE_X. The second branch of the UNION additionally joins PER_PEOPLE_X to resolve a recipient person full name where an approval mechanism identifier points to a specific person. Supporting objects referenced by the definition include the HR_GENERAL package (used to evaluate the HR_GENERAL.END_OF_TIME sentinel), HR_STANDARD_LOOKUPS for the HXC_APPROVAL_MECHANISM lookup type under application_id 809, PER_PEOPLE_X for person names, and FF_FORMULAS_F / FF_FORMULA_TYPES and HR_PERSON_NAME / HR_SECURITY / WF_ACTIVITIES_VL for recipient extension and workflow context. All joins to HXC_TIME_RECIPIENTS, HXC_TIME_CATEGORIES, and HR_STANDARD_LOOKUPS are outer joins, so components are retained even when these lookups are absent.

Key Columns

Common Use Cases and Queries

Typical use cases include auditing approval style composition, validating that a PROJECT_MANAGER mechanism is configured for project-driven time entry, and extracting configuration for migration. A representative query listing all approval components for a mechanism is:

SELECT approval_style_id, name, approval_mechanism, meaning, approval_order, time_category_name FROM hxc_approval_comps_v WHERE approval_mechanism = 'PROJECT_MANAGER' ORDER BY approval_style_id, approval_order;

To inspect recipient-resolved components, query rows where approval_mechanism_id is not null and return the resolved persons alongside the style. Because the view joins HR_SECURITY and PER_PEOPLE_X, results adhere to the caller's HR security profile, so reporting responsibility affects visible rows. For migration, the WHO columns and object version number support change detection and reconciliation.