Results for “fte_ptrk_sources”

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

Overview

FTE_PTRK_SOURCES is a Transportation Execution (FTE) module table in the Oracle E-Business Suite that stores tracking type information. It defines the source metadata used by the Oracle Transportation Execution tracking infrastructure to interpret and resolve tracking tokens — the runtime placeholders that appear on transportation documents and are substituted with operational data such as carrier, shipment, trip, or delivery values. The table is valid and owned by the FTE schema in both Oracle EBS 12.1.1 and 12.2.2. It is documented in ETRM as a standalone table with 16 columns and a single unique index.

Heuristic Data Vault classification mined from the foreign-key structure identifies this object as standalone. In Data Vault modeling terms, that suggests the table behaves as a self-contained reference or configuration entity rather than as a hub, link, or satellite. Its single foreign key to PRP_TOKENS_B (a Product Reporting/PRP tokens base table) nonetheless gives it a reference relationship with the shared token definition framework, so it may be treated as a satellite or reference table surrounding the token hub when a Data Vault view is desired.

Key Information Stored

The table is keyed by a composite unique index, FTE_PTRK_SOURCES_U1, defined on (OWNER_APPLICATION_ID, TOKEN_ID). These two columns constitute the business-key candidate. TOKEN_ID also forms a foreign key to FTE_PTRK_SOURCES.TOKEN_ID → PRP_TOKENS_B, tying each tracking source row to a shared token definition.

• OWNER_APPLICATION_ID — identifies the owning application context; part of the unique business key.
• TOKEN_ID — the referenced token identifier; foreign key to PRP_TOKENS_B and second component of the unique key.
• TOKEN_NAME — the human-readable name of the tracking token/type.
• PAGE_GRANULARITY — indicates the page or document granularity at which the token source applies.
• SOURCE_TABLE — the database table from which tracking values are retrieved.
• SOURCE_COLUMN — the specific column in SOURCE_TABLE that supplies the token value.
• KEY_COLUMN1 through KEY_COLUMN5 — up to five key columns used to join or filter the source table when resolving the tracking value.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO columns capturing audit and concurrency information.

Common Use Cases and Queries

Typical usage centers on diagnosing tracking token resolution, validating source mappings, and reporting on configured tracking types.

• Listing all tracking sources for an application context: SELECT TOKEN_ID, TOKEN_NAME, SOURCE_TABLE, SOURCE_COLUMN FROM FTE.FTE_PTRK_SOURCES WHERE OWNER_APPLICATION_ID = :app_id;
• Joining to token definitions to resolve names: SELECT s.TOKEN_NAME, t.* FROM FTE.FTE_PTRK_SOURCES s, FTE.PRP_TOKENS_B t WHERE s.TOKEN_ID = t.TOKEN_ID;
• Tracing which physical table/column supplies a token for debugging missing or incorrect substitution on a transportation document.
• Auditing configuration changes over time via CREATION_DATE and LAST_UPDATE_DATE.
• Reporting on tokens whose key-column mappings span KEY_COLUMN1..KEY_COLUMN5, to understand multi-key source lookups.

Related Objects

• PRP_TOKENS_B — referenced via FTE_PTRK_SOURCES.TOKEN_ID → PRP_TOKENS_B.TOKEN_ID; the primary token master.
• FTE_PTRK_SOURCES_U1 — unique index on (OWNER_APPLICATION_ID, TOKEN_ID), enforcing business-key uniqueness.
• FTE schema token/tracking tables — other FTE objects that consume tracking token definitions resolved through this table.
• PRP token translation/base tables — related PRP objects that, with PRP_TOKENS_B, complete the token definition model.

Because the object is classified as standalone, downstream dependencies are limited; most relationships are driven by the PRP_TOKENS_B foreign key rather than by inbound foreign keys from other tables.