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
- ROW_ID — the ROWID of the underlying HXC_APPROVAL_COMPS row, used as a stable identifier.
- APPROVAL_COMP_ID — primary key of the approval component.
- APPROVAL_STYLE_ID / NAME — identifier and descriptive name of the parent approval style.
- APPROVAL_MECHANISM / MEANING — the mechanism code (for example HR_SUPERVISOR, AUTO_APPROVE, ORG_TIMEKEEPER, ENTRY_LEVEL_APPROVAL, or PROJECT_MANAGER) and its translated lookup meaning.
- APPROVAL_MECHANISM_ID — a person or recipient identifier; the first UNION branch filters this column to NULL, while the second branch resolves the corresponding person via PER_PEOPLE_X.FULL_NAME.
- TIME_RECIPIENT_ID / NAME — the time recipient associated with the component.
- TIME_CATEGORY_ID / TIME_CATEGORY_NAME — the optional time category narrowing the component's applicability.
- APPROVAL_ORDER — sequence in which components are evaluated within the style.
- START_DATE / END_DATE — effective dating, with END_OF_TIME converted to NULL.
- WF_ITEM_TYPE / WF_NAME — the workflow item type and process name used for routing.
- PARENT_COMP_ID / PARENT_COMP_OVN — hierarchical parent component and its object version number.
- RUN_RECIPIENT_EXTENSIONS and the standard WHO columns (OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN).
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.
-
View: HXC_APPROVAL_COMPS_V 12.2.2
APPS.HXC_APPROVAL_COMPS_V·↳ FF_FORMULAS_F·↳ FF_FORMULA_TYPES·↳ HR_GENERAL·Explore HXC module →
-
View: HXC_APPROVAL_COMPS_V 12.1.1
APPS.HXC_APPROVAL_COMPS_V·↳ FF_FORMULAS_F·↳ FF_FORMULA_TYPES·↳ HR_GENERAL·Explore HXC module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
VIEW: APPS.WF_ACTIVITIES_VL 12.2.2
-
VIEW: APPS.WF_ACTIVITIES_VL 12.1.1
-
VIEW: APPS.PER_PEOPLE_X 12.2.2
-
VIEW: APPS.PER_PEOPLE_X 12.1.1
-
SYNONYM: APPS.FF_FORMULAS_F 12.2.2
-
SYNONYM: APPS.FF_FORMULAS_F 12.1.1
-
eTRM - HXC Tables and Views 12.1.1
Transaction Details Archive
-
eTRM - HXC Tables and Views 12.2.2
Used in Generic Upgrade
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - HXC Tables and Views 12.1.1
Transaction Details Archive
-
eTRM - HXC Tables and Views 12.2.2
Used in Generic Upgrade
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
eTRM - FND Tables and Views 12.2.2
No longer used
-
eTRM - FND Tables and Views 12.1.1
No longer used
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
eTRM - FND Tables and Views 12.2.2
No longer used
-
eTRM - FND Tables and Views 12.1.1
No longer used