Search Results fv_system_parameters




Overview
Explore in AI Chat

Overview

FV_SYSTEM_PARAMETERS is a configuration table owned by the FV schema within the Oracle E-Business Suite Federal Financials (FV) product. Its documented purpose is to store Federal System parameters — the setup-level flags, attribute mappings, and option controls that govern how the Federal Financials module captures, classifies, and reports financial transactions. Because these parameters drive Treasury reporting (FACTS I, FACTS II, GTAS) and feeder subsystem processing, the table acts as a central control record for the module rather than a transactional table.

The table contains 24 documented columns and is exposed as FV.FV_SYSTEM_PARAMETERS with primary key constraint FV_SYSTEM_PARAMETERS_PK, declared on LAST_UPDATE_DATE. The ETRM data vault classification heuristic labels this object a standalone entity with no mined foreign key relationships. As a modeling suggestion, a standalone EBS configuration table of this type is best treated as a satellite-style reference object: it holds descriptive attributes describing a single configuration state rather than participating in hub/link relationships. It is not a hub, since it has no natural business key exposed to dependent tables, and not a link, since it resolves no many-to-many association.

Key Information Stored

The documented columns fall into three functional groups: standard audit columns, Federal reporting attribute mappings, and processing option switchers. The most significant documented columns are:

No unique business-key index beyond the primary key constraint is documented. Surrogate identification therefore rests on the constraint name FV_SYSTEM_PARAMETERS_PK, while the various *_OPTION and *_ATTRIBUTE columns behave as configuration business fields rather than candidate keys.

Common Use Cases and Queries

Typical uses center on validating Federal reporting configuration before running Treasury extract programs and on documenting the active attribute mappings for audit purposes.

  • Parameter review: SELECT * FROM fv.fv_system_parameters; — confirms which options and attribute mappings are active.
  • Change auditing: filter on the audit columns to identify recent setup changes: SELECT last_updated_by, last_update_date FROM fv.fv_system_parameters WHERE last_update_date > SYSDATE - 30;
  • Report readiness checks: verify that FACTS II mappings (FACTSII_PUB_LAW_CODE_ATTRIBUTE, FACTSII_ADVANCE_TYPE_ATTRIBUTE, FACTSII_TR_MAIN_ACCT_ATTRIBUTE, FACTSII_TR_DEPT_ID_ATTRIBUTE) and the GTAS_CUSTOMER_ATTRIBUTE are populated before initiating GTAS or FACTS extract processes.
  • Date segment validation: inspect REQ_DATE_SEG, PUR_ORDER_DATE_SEG, and REC_TRXN_DATE_SEG to confirm which date segments drive procurement and receiving transaction dating.
  • Option dependency tracing: query ETC_OPTION, EBD_OPTION, and ARAP_OPTION to determine whether dependent interface programs should execute.
  • Reporting reproduction: join attribute mapping columns to descriptive flexfield definitions to reconstruct how FACTS I/II and GTAS attributes were derived at a point in time.

Related Objects

The ETRM metadata classifies FV_SYSTEM_PARAMETERS as standalone, with no documented foreign key relationships. As a configuration table it is referenced logically rather than via FK constraints, so relationship determination relies on knowledge of the Federal Financials data model. Significant related objects include:

  • FACTS I / FACTS II extract and reporting programs — consume the FACTSI_* and FACTSII_* attribute mapping columns.
  • GTAS reporting processes — read GTAS_CUSTOMER_ATTRIBUTE during Treasury symbol derivation.
  • FV subsystem options and Federal setup forms — the UI layer that writes ETC_OPTION, EBD_OPTION, and ARAP_OPTION.
  • Report 2209 processing — depends on REP_2209_ATTRIBUTE.
  • Prior-year adjustment (PYA) and AR reclassification routines — depend on PYA_INVOICE_ATTRIBUTE and AR_RECLASS_ATTRIBUTE.
  • SF 224 (Statement of Transactions) reporting — depends on SF224_ACCOMPLISH_DATE.
  • Standard EBS WHO audit columns (FND_USER via CREATED_BY / LAST_UPDATED_BY) — for user-level change attribution.

Because the FK relationship data is empty, the FV_SYSTEM_PARAMETERS_PK constraint on LAST_UPDATE_DATE should be treated as the only documented database-level relationship anchor; all other associations are application-level dependencies rather than enforced constraints.