Results for “hr_s_route_parameters”

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

Overview

HR_S_ROUTE_PARAMETERS is a Human Resources (PER) module table in the Oracle E-Business Suite database, owned by the HR schema. The ETRM metadata classifies it as a "Retrofitted" object, meaning it was introduced or re-registered into the ETRM inventory during an upgrade or retrofit exercise rather than being delivered as a first-class documented entity in the original product data model. Its functional purpose is to hold parameter definitions used by HR routing and transaction-routing configurations, allowing a given route to declare the named parameters it accepts, along with their data types and ordering.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is standalone. This suggests the table behaves as an independent reference or configuration entity rather than a pure hub, link, or satellite, although modeling it as a small reference hub keyed on ROUTE_PARAMETER_ID is a reasonable design suggestion. In EBS 12.1.1 and 12.2.2 the physical definition is consistent: five columns in the HR schema, with the table marked VALID.

Key Information Stored

The documented physical schema contains five columns. The most significant are:

• ROUTE_PARAMETER_ID — the surrogate primary key for the table. It uniquely identifies each parameter definition row and is the column referenced by the foreign-key relationship to FF_ROUTE_PARAMETERS.
• ROUTE_ID — identifies the route (or routing configuration) to which the parameter belongs. This is the principal business-key candidate, since a parameter is only meaningful in the context of its owning route.
• PARAMETER_NAME — the human-readable name of the parameter exposed by the route. Together with ROUTE_ID it forms the natural business key that users and configuration tools recognize.
• DATA_TYPE — the declared data type of the parameter value (for example, character, number, or date semantics), governing validation and interpretation.
• SEQUENCE_NO — the ordinal position of the parameter within the route, controlling display and processing order.

No unique index definitions beyond the primary-key and business-key candidates are documented in the ETRM excerpt.

Common Use Cases and Queries

Typical scenarios involve inspecting or maintaining the parameter set for a given routing configuration, validating that a route exposes the parameters expected by downstream logic, and joining parameter metadata to the broader routing model.

• List all parameters for a specific route, in processing order:
  SELECT route_parameter_id, parameter_name, data_type, sequence_no FROM hr.hr_s_route_parameters WHERE route_id = :p_route_id ORDER BY sequence_no;
• Find routes that define a parameter of a given name:
  SELECT route_id, parameter_name, data_type FROM hr.hr_s_route_parameters WHERE parameter_name = :p_name;
• Trace the link into the referenced parameter framework:
  SELECT rp.route_parameter_id, rp.parameter_name, fr.* FROM hr.hr_s_route_parameters rp, hr.ff_route_parameters fr WHERE rp.route_parameter_id = fr.route_parameter_id;
• Reporting use cases: configuration listings for audit, data-migration validation comparing expected versus configured parameters per route, and discovery queries enumerating all distinct parameter names and data types in use.

Related Objects

The following objects are most significant in relation to HR_S_ROUTE_PARAMETERS:

• FF_ROUTE_PARAMETERS — referenced by HR_S_ROUTE_PARAMETERS via ROUTE_PARAMETER_ID; the primary foreign-key relationship documented for this table.
• HR_S_ROUTES / FF_ROUTES — the route definitions to which ROUTE_ID conceptually belongs; likely holding the master routing records.
• FF_ROUTE_ROUTES — supporting the routing configuration structure associated with FF_ROUTE_PARAMETERS.
• HR_S_ROUTE_STEPS — steps within a route that consume the parameters defined here.
• HR_S_ROUTE_PARAM_VALUES (where present) — runtime or instance values supplied for the declared parameters.
• HR_LOOKUPS — repository of lookup codes commonly referenced for PARAMETER_NAME and DATA_TYPE validation.

Because the ETRM entry is marked Retrofitted and exposes only the single documented foreign key, additional dependencies should be confirmed against the live data dictionary before relying on them in custom reporting or interfaces.