Results for “fv_facts_rt7_codes_u2”

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

Overview

FV.FV_FACTS_RT7_CODES is a base table in the Oracle E-Business Suite Financials (FV) schema that stores the authorization code definitions used by FACTS II (Financial Accounting and Cost Tracking System) reporting for federal agencies. The table acts as the master reference list of RT7 authorization codes, capturing each code's borrowing source, authority type, and descriptive text, scoped by set of books. It is the parent object for code-to-account mappings and for individual authorization transactions, meaning that every authorization line recorded in the subledger must resolve to a row in this table through the RT7_CODE_ID identifier.

In Data Vault modeling terms, FV_FACTS_RT7_CODES is best classified as a hub. The heuristic classification derived from the foreign key structure is "standalone," reflecting that no foreign keys point outward from this table. It carries its own surrogate key (RT7_CODE_ID) and a pair of natural business keys (SET_OF_BOOKS_ID combined with RT7_CODE), with the descriptive attributes (borrowing source, authority type, description) behaving as hub-adjacent reference data.

Key Information Stored

The table is defined with 28 columns. The most significant are:

• RT7_CODE_ID — the unique, system-generated surrogate primary key (FV_FACTS_RT7_CODES_PK) and the column referenced by all dependent tables.
• SET_OF_BOOKS_ID — the set of books (ledger) identifier that scopes the code; combined with RT7_CODE it forms the unique business key FV_FACTS_RT7_CODES_U1.
• RT7_CODE — the user-facing authorization code, the primary business identifier for lookups and reporting.
• RT7_BORROWING_SOURCE — the borrowing source associated with the authorization code.
• RT7_AUTHORITY_TYPE — the authority type classification for the code.
• RT7_CODE_DESCRIPTION — an 80-character transaction type description used in reporting and inquiry screens.
• FACTSII_EDIT_CODE — the FACTS II edit rule code applied to transactions using this authorization code.

The remaining columns are the standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and fifteen descriptive flexfield segments (ATTRIBUTE_CATEGORY plus ATTRIBUTE1 through ATTRIBUTE15). The unique indexes FV_FACTS_RT7_CODES_U1 (SET_OF_BOOKS_ID, RT7_CODE) and FV_FACTS_RT7_CODES_U2 (RT7_CODE_ID) both reside in APPS_TS_TX_IDX; the table data resides in APPS_TS_TX_DATA with a PCT Free of 10.

Common Use Cases and Queries

Typical usage centers on validating and reporting authorization codes. A common validation pattern resolves a code to its surrogate key for downstream joins:

• Lookup by business key: SELECT rt7_code_id, rt7_code_description, rt7_authority_type FROM fv_facts_rt7_codes WHERE set_of_books_id = :sob AND rt7_code = :code;
• Join to account mappings: SELECT c.rt7_code, a.account_id FROM fv_facts_rt7_codes c, fv_facts_rt7_accounts a WHERE c.rt7_code_id = a.rt7_code_id AND c.set_of_books_id = :sob;
• Reconcile activity: aggregate authorizations in FV_FACTS_AUTHORIZATIONS grouped by RT7_CODE_ID, then join back to this table for descriptive reporting.

Reporting extracts for FACTS II submissions frequently query this table to produce code listings per ledger, and interfaces loading external authorization data must observe both unique indexes to avoid duplicate key errors.

Related Objects

Two tables are documented as referencing FV_FACTS_RT7_CODES through the RT7_CODE_ID foreign key, and both are significant dependencies:

• FV.FV_FACTS_RT7_ACCOUNTS — joins on RT7_CODE_ID and provides the code-to-account relationship referenced in the object description.
• FV.FV_FACTS_AUTHORIZATIONS — joins on RT7_CODE_ID and stores the authorization transactions that consume these codes.

In addition, the FND Design Data entry FV.FV_FACTS_RT7_CODES governs the registration of the object within the application dictionary, and the descriptive flexfield segments imply a configured DFF definition attached to the table for site-specific extensions.