Results for “ff_route_parameters”

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

Overview

FF_ROUTE_PARAMETERS is a FastFormula (FF) configuration table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It defines the parameters that can be passed to a ROUTE to restrict the number of rows returned by that ROUTE. Within the FastFormula architecture, a ROUTE is a database-driven mechanism for retrieving rows from a source table or view, applying SQL-style selection criteria, and feeding the results to a formula. The parameters recorded in FF_ROUTE_PARAMETERS act as the declared inputs (bind-style variables) that a caller may supply when executing a route, allowing the same route definition to return a reduced, filtered row set rather than the full result.

From a Data Vault modeling perspective, the heuristic classification of this table is satellite-leaning. This is a modeling suggestion only: the table hangs off the parent route entity (FF_ROUTES) via a foreign key and carries descriptive, route-specific attributes rather than functioning as an independent hub. It occupies a supporting, descriptive role relative to the route definition, which is consistent with satellite behavior.

Key Information Stored

Each row in FF_ROUTE_PARAMETERS represents one parameter that may be passed to a route. The most significant documented columns are:

• ROUTE_PARAMETER_ID — the surrogate primary key (FF_ROUTE_PARAMETERS_PK), uniquely identifying each parameter definition.
• ROUTE_ID — foreign key to FF_ROUTES, tying the parameter to the route that consumes it.
• PARAMETER_NAME — the name by which the parameter is referenced; part of the business-key candidate FF_ROUTE_PARAMETERS_UK3 (PARAMETER_NAME, ROUTE_ID, ZD_EDITION_NAME).
• SEQUENCE_NO — the ordinal position of the parameter within the route; part of the business-key candidate FF_ROUTE_PARAMETERS_UK2 (ROUTE_ID, SEQUENCE_NO, ZD_EDITION_NAME).
• DATA_TYPE — the datatype governing the parameter's accepted values.
• ZD_EDITION_NAME — the editioning column introduced by EBS 12.2's online patching architecture, included in all three unique indexes to keep definitions isolated by edition.

The surrogate ROUTE_PARAMETER_ID should be distinguished from the business-key candidates FF_ROUTE_PARAMETERS_UK2 and FF_ROUTE_PARAMETERS_UK3, which enforce uniqueness of a parameter name and its sequence position within a given route. The documented physical schema contains six columns in total.

Common Use Cases and Queries

Typical usage centers on inspecting and validating route definitions before troubleshooting FastFormula behavior. Common scenarios include enumerating the parameters available to a specific route, verifying sequence ordering, and confirming datatype definitions.

• List parameters for a given route:

  SELECT p.route_parameter_id, p.route_id, p.parameter_name,
         p.data_type, p.sequence_no
  FROM   hr.ff_route_parameters p
  WHERE  p.route_id = :route_id
  ORDER  BY p.sequence_no;

• Join to the parent route to identify which routes expose a named parameter:

  SELECT r.route_id, r.NAME, p.parameter_name
  FROM   hr.ff_route_parameters p, hr.ff_routes r
  WHERE  p.route_id = r.route_id
  AND    p.parameter_name = :param_name;

• Inspect the values supplied for those parameters via the child table:

  SELECT v.route_parameter_id, v.*
  FROM   hr.ff_route_parameter_values v
  WHERE  v.route_parameter_id = :route_parameter_id;

Reporting and migration activities also rely on this table to document which routes are parameterized, aiding impact analysis when routes are edited or cloned. All queries should be aware of the ZD_EDITION_NAME column when run under 12.2 online patching.

Related Objects

The following objects are most significant to FF_ROUTE_PARAMETERS, based on the documented FK/PK relationships:

• FF_ROUTES — parent definition; joined on FF_ROUTE_PARAMETERS.ROUTE_ID = FF_ROUTES.ROUTE_ID.
• FF_ROUTE_PARAMETER_VALUES — child table holding actual parameter values; joined on ROUTE_PARAMETER_ID.
• HR_S_ROUTE_PARAMETERS — editioning/seed synonym-style companion referencing ROUTE_PARAMETER_ID.
• HR_S_ROUTE_PARAMETER_VALUES — companion values object referencing ROUTE_PARAMETER_ID.

Together these objects form the route-parameterization chain: the route, its declared parameters, and the values bound to those parameters at execution.