Results for “fv_transmission_formats”

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

Overview

FV_TRANSMISSION_FORMATS is a reference (setup) table within the Oracle E-Business Suite Federal Financials (FV) module. It stores the master list of transmission formats supported by the Fund Balance with Treasury (FBWT) Import Process. Each row defines a distinct format in which Treasury transmission data can be received and parsed, providing the lookup framework that drives how inbound FBWT files are interpreted, validated, and loaded into the subsystem.

From a Data Vault modeling perspective, the metadata's heuristic classification places this object as hub-leaning. This is consistent with its behavior as a stable, uniquely-keyed business entity registry whose rows are referenced by dependent transactional data. Modelers would typically represent it as a hub keyed on the transmission format business concept, with descriptive attributes optionally separated into a satellite. The documented description confirms its role: it exists exclusively to enumerate the transmission formats recognized by the import process.

Key Information Stored

The metadata documents the following structural elements. The clearly named and authoritative column is:

• TRANSMISSION_FORMAT_ID — The surrogate primary key for the table, enforced through the FV_TRANSMISSION_FORMATS_PK constraint. It uniquely identifies each supported transmission format and is the value propagated to child tables as a foreign key.

Additional descriptive columns (for example, a format name, code, or descriptive text) are implied by the table's purpose as a format registry, but the supplied metadata does not enumerate them, so they are not asserted here. The primary key column is the sole documented business identifier: no separate unique index or alternate business key is specified in the metadata beyond the PK constraint. Deployments should confirm the presence of a user-facing format name or code column before relying on a natural key.

The metadata notes the table is flagged "Not implemented in this database," indicating that in the referenced environment the object definition was not present, though the logical model and constraints are documented.

Common Use Cases and Queries

Typical uses of this table center on decoding and validating the transmission format associated with imported FBWT records. Reporting queries frequently join it to FV_TRANSMISSION_RECORDS to translate the stored format identifier into a human-readable description. Representative patterns include:

• Listing all supported formats for setup or administrative review: SELECT transmission_format_id FROM fv_transmission_formats;
• Counting records per transmission format to audit import volume by source format, joining FV_TRANSMISSION_RECORDS on the shared TRANSMISSION_FORMAT_ID.
• Validating referential integrity by identifying transmission records whose TRANSMISSION_FORMAT_ID has no matching parent row.

Because the table is a reference list, its cardinality is low and its primary value is as a dimension or lookup in joins against the larger transmission record set.

Related Objects

The documented foreign key relationships identify the objects that depend on this table. The most significant related object is:

• FV_TRANSMISSION_RECORDS — The primary dependent table. It carries a foreign key, FV_TRANSMISSION_RECORDS.TRANSMISSION_FORMAT_ID, which references FV_TRANSMISSION_FORMATS. This is the table that stores the actual inbound Treasury transmission data associated with each format. The documented FK column is TRANSMISSION_FORMAT_ID.

Beyond this relationship, the provided metadata does not enumerate additional referencing views, APIs, or tables. The Fund Balance with Treasury Import Process is the functional consumer that reads this format registry while processing files, and FV_TRANSMISSION_RECORDS is the sole documented child object. Deployments should verify any supplemental lookup views or concurrent program parameters that reference FV_TRANSMISSION_FORMATS in their specific environment.