Search Results fa_system_controls_pk

Overview

FA.FA_SYSTEM_CONTROLS is a standalone configuration table in the Oracle Assets (OFA) module of Oracle E-Business Suite, holding system-wide control values that govern asset processing for an entire Oracle Assets installation. Unlike operational tables that store transactions or asset records, this table functions as a singleton control record — the metadata documents a single-row primary key composed of COMPANY_NAME, which effectively anchors the control values to one company (and therefore one ledger/book context via the associated GL_APPLICATION_ID and FA_APPLICATION_ID). Every depreciation run, mass addition, and asset numbering event consults these controls as defaults, making the table a foundational reference point rather than a transactional one.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone — the table neither participates as a hub nor as a link, and its COMPANY_NAME primary key behaves more like a natural business key than a surrogate identifier. In a Data Vault design this would typically suggest a small reference or satellite-style entity capturing configuration state rather than an associative structure.

Key Information Stored

The most operationally significant columns include the following. The primary key is COMPANY_NAME (documented as FA_SYSTEM_CONTROLS_PK), serving as both the surrogate and business identifier for the control row.

• DATE_PLACED_IN_SERVICE — default in-service date applied to new assets when not otherwise supplied.
• INITIAL_ASSET_ID — starting value for automatic asset number generation.
• GL_APPLICATION_ID and FA_APPLICATION_ID — application identifiers linking the controls to General Ledger and Assets installations.
• LOCATION_FLEX_STRUCTURE, CATEGORY_FLEX_STRUCTURE, ASSET_KEY_FLEX_STRUCTURE, GROUP_FLEX_STRUCTURE, SUPER_GROUP_FLEX_STRUCTURE — key flexfield structure identifiers that define the segment configurations used for locations, categories, asset keys, and grouping.
• LAST_MASS_ADDITIONS and LAST_MASS_ADDITIONS_POST — timestamps for the most recent mass addition run and posting, used for reconciliation and audit trails.
• USE_CUSTOM_ASSET_NUMBERS_FLAG and CUA_INHERITANCE_FLAG — flags controlling asset numbering behavior and custom (user-defined) asset inheritance.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS WHO columns for audit tracking.
• ATTRIBUTE_CATEGORY_CODE and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield (DFF) segment columns for extensible, client-specific configuration data.

Common Use Cases and Queries

Typical reporting and troubleshooting scenarios include verifying the default in-service date, confirming flexfield structure assignments, or auditing the last mass addition posting. A representative query to inspect controls is:

SELECT COMPANY_NAME, DATE_PLACED_IN_SERVICE, INITIAL_ASSET_ID, USE_CUSTOM_ASSET_NUMBERS_FLAG, LAST_MASS_ADDITIONS_POST FROM FA.FA_SYSTEM_CONTROLS;

Because of the singleton design, applications and reports frequently join this row to asset data to supply defaults or to validate that flexfield structures align with the structures assigned on asset records. Auditors often query LAST_MASS_ADDITIONS and LAST_MASS_ADDITIONS_POST to confirm that period-end mass additions were posted before depreciation close.

Related Objects

The metadata classifies this table as standalone with no foreign keys, so dependents are inferred from function rather than documented FK columns. Significant related objects include:

• FA_ADDITIONS — asset records that inherit default in-service dates and numbering rules.
• FA_BOOK_CONTROLS — book-level controls that complement system-wide controls and share flexfield structure references.
• FA_MASS_ADDITIONS — mass addition transactions validated against the last-post timestamps.
• FA_CATEGORIES — categories referenced by CATEGORY_FLEX_STRUCTURE.
• FA_LOCATIONS — locations governed by LOCATION_FLEX_STRUCTURE.
• The Assets setup forms and concurrent programs (e.g., mass additions, depreciation) that read these controls at runtime.