Search Results cs_qm_function_filters




Overview
Explore in AI Chat

Overview

CS_QM_FUNCTION_FILTERS is a Service (CS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the relationship between functions and filters. It acts as a junction table that maps Oracle Forms functions — registered in the FND_FORM_FUNCTIONS dictionary — to filter definitions maintained in CS_QM_FILTERS. In the Service module this enables function-level control over which records, folders, or quality-management query contexts are visible to a given responsibility or form function, supporting the folder and query-management framework used by Service agents and administrators.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table carries its own surrogate primary key, CS_QM_FUNCTION_FILTERS_PK on FUNCTION_FILTER_ID, alongside descriptive columns such as SEEDED_FLAG, ACTIVE_FLAG, and the administrative WHO columns. Because it also references two parent entities, FILTER_ID and FUNCTION_ID, it behaves partly as an associative link, but the presence of descriptive and auditable attributes leans toward satellite treatment.

Key Information Stored

The dominant column is FUNCTION_FILTER_ID, the surrogate primary key that uniquely identifies each function-to-filter mapping row. Business-key uniqueness is documented through CS_QM_FUNCTION_FILTERS_UK, defined over FILTER_ID and FUNCTION_ID, and through the unique index CS_QM_FUNCTION_FILTERS_U1 (FUNCTION_FILTER_ID, ZD_EDITION_NAME) introduced with editioning in 12.2. The FILTER_ID column is a foreign key to CS_QM_FILTERS, and FUNCTION_ID is a foreign key to FND_FORM_FUNCTIONS.

  • FUNCTION_FILTER_ID — surrogate primary key for each mapping row.
  • FILTER_ID — reference to the parent filter definition in CS_QM_FILTERS.
  • FUNCTION_ID — reference to the application function in FND_FORM_FUNCTIONS.
  • FUNCTION_NAME — denormalized function name used for display and reporting.
  • COLUMN_NAME and COLUMN_DATATYPE — the target column and its datatype that the filter constrains.
  • SEEDED_FLAG — indicates whether the row was seeded by Oracle as opposed to user-created.
  • ACTIVE_FLAG — controls whether the function-filter association is currently in effect.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/BC4J middle tier.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
  • ZD_EDITION_NAME — editioning support column present in 12.2.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include identifying which filters are attached to a form function, determining active seeded mappings, and validating that every custom function has an appropriate filter association after a patch or upgrade. A representative query joins the mapping table to both parent tables:

  • SELECT fff.function_filter_id, fff.function_name, qf.filter_name, fff.active_flag, fff.seeded_flag FROM cs.cs_qm_function_filters fff, cs.cs_qm_filters qf, applsys.fnd_form_functions ffn WHERE fff.filter_id = qf.filter_id AND fff.function_id = ffn.function_id;
  • Inventory of active mappings: filter on ACTIVE_FLAG = 'Y' and order by FUNCTION_NAME.
  • Seed-data audit: count rows grouped by SEEDED_FLAG to distinguish Oracle-delivered rows from customer extensions.
  • Upgrade verification: left-outer join FND_FORM_FUNCTIONS with this table to find functions lacking a filter mapping.

Related Objects

The table participates in a small but important object cluster within the Service query-management framework.

  • CS_QM_FILTERS — parent table referenced through FILTER_ID; holds the filter definitions themselves.
  • FND_FORM_FUNCTIONS — application dictionary parent referenced through FUNCTION_ID; defines the registered form function.
  • CS_QM_FOLDER_FILTERS — child table that references FUNCTION_FILTER_ID, extending the mapping into the folder-filter context.
  • CS_QM_FUNCTION_FILTERS_PK / _UK / _U1 — the primary key constraint, business-key unique constraint, and edition-aware unique index that enforce integrity.
  • FND_FORM_FUNCTIONS_VL and related FND views — commonly joined for user-facing function names in reporting.

Because the table is owned by CS and seeded as part of the Service module, changes should ordinarily be made through supported configuration and concurrent programs rather than direct DML, preserving the WHO audit columns and the seeded flag semantics.