Results for “ff_route_parameters_uk2”

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

Overview

HR.FF_ROUTE_PARAMETERS is a seed data table in the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 schema, registered under FND Design Data as FF.FF_ROUTE_PARAMETERS. It holds the definitions of parameters that can be passed into a FastFormula route, together with the positional sequence in which each parameter is consumed by the route text. These parameters effectively restrict and filter the number of rows returned by a route, so they act as the binding contract between a route definition and the data set it processes. The table resides in the APPS_TS_SEED tablespace and has a status of VALID.

From a Data Vault modeling perspective, the heuristic classification is satellite-leaning. Because the table carries descriptive attributes (DATA_TYPE, PARAMETER_NAME, SEQUENCE_NO) that describe a parent business entity (the route) and are qualified by a foreign key to FF_ROUTES, it is best viewed as a descriptive satellite of the route hub rather than an independent hub or a link.

Key Information Stored

Only the following documented columns are noteworthy:

• ROUTE_PARAMETER_ID — numeric surrogate primary key (FF_ROUTE_PARAMETERS_PK) uniquely identifying each parameter definition.
• ROUTE_ID — foreign key to FF_ROUTES identifying the owning route; also part of business-key unique indexes.
• DATA_TYPE — a single-character code designating the parameter type: N for number, T for text, D for date.
• PARAMETER_NAME — a 40-character descriptive name (documented as "for information only"); it does not drive route behavior.
• SEQUENCE_NO — numeric position of the parameter as used in the route text, which must match the positional order expected by the route.

Two unique business-key candidates are documented: FF_ROUTE_PARAMETERS_UK2 (ROUTE_ID, SEQUENCE_NO) guarantees no two parameters occupy the same slot within a route, and FF_ROUTE_PARAMETERS_UK3 (PARAMETER_NAME, ROUTE_ID) enforces unique names within a route. In the 12.2.2 physical schema, all three unique indexes include ZD_EDITION_NAME, reflecting edition-based redefinition support.

Common Use Cases and Queries

Typical use cases include listing all parameters for a given route, verifying sequence continuity, and auditing which routes require numeric or date inputs. The standard query template is:

• SELECT ROUTE_PARAMETER_ID, ROUTE_ID, DATA_TYPE, PARAMETER_NAME, SEQUENCE_NO FROM HR.FF_ROUTE_PARAMETERS;
• Filter by owner route: ... WHERE ROUTE_ID = :route_id ORDER BY SEQUENCE_NO;
• Type inventory: ... WHERE DATA_TYPE = 'N';
• Join to route metadata: SELECT r.ROUTE_NAME, p.PARAMETER_NAME, p.DATA_TYPE, p.SEQUENCE_NO FROM FF_ROUTES r, FF_ROUTE_PARAMETERS p WHERE r.ROUTE_ID = p.ROUTE_ID ORDER BY r.ROUTE_NAME, p.SEQUENCE_NO;

These queries support FastFormula route troubleshooting, upgrade validation of seeded routes, and impact analysis before modifying or decommissioning a route.

Related Objects

• HR.FF_ROUTES — parent table; FF_ROUTE_PARAMETERS.ROUTE_ID references FF_ROUTES.
• HR.FF_ROUTE_PARAMETER_VALUES — child table; FF_ROUTE_PARAMETER_VALUES.ROUTE_PARAMETER_ID references this table's primary key.
• HR.HR_S_ROUTE_PARAMETERS — shadow/seed variant referencing ROUTE_PARAMETER_ID.
• HR.HR_S_ROUTE_PARAMETER_VALUES — shadow variant of the values table, likewise referencing ROUTE_PARAMETER_ID.
• Database triggers FF_ROUTE_PARAMETERS_BRI and FF_ROUTE_PARAMETERS_BRUD — row-level triggers enforcing insert and update/delete logic.

Together these objects form the route-parameter subsystem used by the FastFormula engine within Oracle HRMS.