Results for “hr_s_route_parameter_values”

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

Overview

HR_S_ROUTE_PARAMETER_VALUES is a table owned by the HR schema in Oracle E-Business Suite, belonging to the PER (Human Resources) product family. The object carries a VALID status in the ETRM repository and is documented as "Retrofitted," indicating it forms part of the standard Oracle HRMS data model that was re-implemented or migrated into the current schema definition rather than being created anew. In functional terms, the table stores the concrete values assigned to routing parameters that govern how HR self-service transactions, approvals, and workflow-driven processes are directed through the routing engine.

The ETRM metadata classifies this object heuristically as a standalone Data Vault entity. This classification is a modeling suggestion rather than a physical constraint: the table contains no downstream dependents within the documented relationship set, which is consistent with satellite-style behavior, where the table would act as a descriptive satellite attached to the parameter and entity hubs it references. It is not a hub or link in its own right, since its identity is derived from the combination of a route parameter and a user entity rather than from an independent business key.

Key Information Stored

The documented physical schema for release 12.2.2 comprises eight columns. The most functionally significant are the following:

• ROUTE_PARAMETER_ID — Foreign key to FF_ROUTE_PARAMETERS, identifying which routing parameter definition the stored value belongs to. This column forms half of the natural composite identity of a row.
• USER_ENTITY_ID — Foreign key to FF_USER_ENTITIES, identifying the user entity or entity instance to which the parameter value applies. Together with ROUTE_PARAMETER_ID, this constitutes the business-key candidate for uniqueness.
• VALUE — The actual parameter value stored for the given route parameter and user entity combination. This is the payload column and the primary target of most application reads.
• LAST_UPDATE_DATE — Timestamp of the most recent modification, used by concurrent programs and audit reports for incremental processing.
• LAST_UPDATED_BY — The application user who performed the last update.
• LAST_UPDATE_LOGIN — The login session associated with the last update, useful for forensic tracing.
• CREATED_BY — The user who originally inserted the row.
• CREATION_DATE — The insertion timestamp.

The metadata does not document an explicit surrogate primary key column separate from the two foreign keys; the effective row identity is the ROUTE_PARAMETER_ID and USER_ENTITY_ID pair. The WHO columns follow standard EBS conventions and carry no business meaning beyond audit tracking.

Common Use Cases and Queries

The principal use case is resolving how a transaction should be routed for a specific parameter and entity. A typical query joins the parameter definition to retrieve descriptive context alongside the stored value:

• Retrieve all values for a given parameter: SELECT p.parameter_name, v.user_entity_id, v.value FROM hr.hr_s_route_parameter_values v, hr.ff_route_parameters p WHERE v.route_parameter_id = p.route_parameter_id;
• Audit recently changed rows: filter on LAST_UPDATE_DATE greater than a cutoff and join LAST_UPDATED_BY to FND_USER for user names.
• Reconcile routing configuration: compare stored values against expected defaults to detect drift during a clone or upgrade.
• Reporting on parameter coverage: aggregate counts of distinct USER_ENTITY_ID per ROUTE_PARAMETER_ID to identify entity types missing configuration.

Because the table is described as retrofitted, direct DML is not recommended. Changes should flow through the supported HRMS setup and routing APIs so that the parameter and entity relationships remain consistent.

Related Objects

The documented foreign keys establish two direct parent relationships, and additional EBS objects interact with the table through the routing engine. The significant related objects are:

• FF_ROUTE_PARAMETERS — joined via ROUTE_PARAMETER_ID; defines the parameter itself.
• FF_USER_ENTITIES — joined via USER_ENTITY_ID; defines the entity to which the value applies.
• FF_ROUTES and FF_ROUTE_PARAMETER_USAGES — define routing structures that consume these parameter values.
• FND_USER — referenced through the WHO audit columns for user identification.
• HR_S_ROUTE_PARAMETERS_VL and related HRMS routing views — provide the queryable, translation-enabled presentation layer over the same routing configuration.

Together these objects form the routing configuration layer of the PER product, with HR_S_ROUTE_PARAMETER_VALUES supplying the concrete, entity-specific values that drive that routing behavior.