Results for “fte_ptrk_params”

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

Overview

FTE_PTRK_PARAMS is a Transportation Execution (FTE) module table in Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. As its description states, it stores tracking parameter information — configuration rows that define how shipment, container, or delivery tracking pages behave within the FTE tracking UI. Each row associates a tracking parameter with a parent page and, optionally, a runtime token. This separation of configuration data from page and token definitions allows transportation planners to tailor tracking screens without code changes.

The documented schema comprises 12 columns, with FTE_PTRK_PARAMS_U1 on PARAM_ID serving as the unique business-key index. The Data Vault classification mined from the FK structure is standalone, meaning this should be modeled as an independent hub or reference table rather than as a link or satellite. The single foreign key, FTE_PTRK_PARAMS.TOKEN_ID → PRP_TOKENS_B, indicates a lightweight reference to the token master, while the absence of child FKs across the ETRM model confirms the table's role as a leaf-level configuration store.

Key Information Stored

The most significant columns are:

• PARAM_ID — the surrogate primary key and the column indexed by FTE_PTRK_PARAMS_U1; it uniquely identifies each tracking parameter row.
• PAGE_ID — identifies the tracking page (FTE_PTRK_PAGES) to which the parameter belongs; it establishes the parent-child grouping of parameters on a screen.
• PARAM_NAME — the display or programmatic name of the parameter.
• STATIC_VALUE — a literal value bound to the parameter when no dynamic token is used.
• TOKEN_ID — the foreign key to PRP_TOKENS_B; when populated, the parameter resolves dynamically from the referenced token rather than STATIC_VALUE.
• SEQUENCE_NUMBER — controls the ordering in which parameters appear or evaluate.
• FLAG — a status/control indicator for the parameter.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit columns, populated via the WHO columns mechanism.

Together, PARAM_ID and TOKEN_ID define the resolution logic: static value or token-derived value, ordered by SEQUENCE_NUMBER within a PAGE_ID.

Common Use Cases and Queries

Typical usage includes auditing page configuration, troubleshooting why a tracking field renders incorrectly, and cloning parameters between environments. A representative query joining parameters to the token master:

• SELECT p.PAGE_ID, p.PARAM_ID, p.PARAM_NAME, p.STATIC_VALUE, p.SEQUENCE_NUMBER, t.TOKEN_NAME FROM FTE.FTE_PTRK_PARAMS p, FTE.PRP_TOKENS_B t WHERE p.TOKEN_ID = t.TOKEN_ID(+) ORDER BY p.PAGE_ID, p.SEQUENCE_NUMBER;
• Reporting which parameters rely on dynamic tokens: SELECT * FROM FTE.FTE_PTRK_PARAMS WHERE TOKEN_ID IS NOT NULL;
• Detecting duplicates or misconfigured ordering: SELECT PAGE_ID, PARAM_NAME, COUNT(*) FROM FTE.FTE_PTRK_PARAMS GROUP BY PAGE_ID, PARAM_NAME HAVING COUNT(*) > 1;

Because the table is configuration data, changes are usually made through the FTE setup UI rather than direct DML; direct inserts risk invalid PAGE_ID or TOKEN_ID references and should be treated as a last resort.

Related Objects

The most significant related objects are:

• PRP_TOKENS_B — the token master referenced by TOKEN_ID; the primary join for resolving dynamic parameter values.
• FTE_PTRK_PAGES — the parent page definition table linked via PAGE_ID; parameters are scoped to a page.
• PRP_TOKENS_TL — the translated token names for reporting token-based parameters.
• FTE tracking APIs — the FTE tracking page query and tracking parameter resolution routines that consume FTE_PTRK_PARAMS at runtime.
• FTE_LOOKUPS — FTE lookup types that supply valid values for FLAG or status-related configuration.

In practice, PRP_TOKENS_B and the page table are the two objects most frequently joined to FTE_PTRK_PARAMS in both diagnostic queries and reporting extracts.