Search Results csi_counter_derived_filters




Overview

CSI_COUNTER_DERIVED_FILTERS is a table within the CSI (Install Base) product schema in Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. As documented in the ETRM metadata, the table "holds the counter filters data," meaning it stores the filter definitions applied to installation base counters. Counters in Oracle CSI are used to track measurable usage or condition values on installed assets — for example meter readings or cycle counts — and derived filters constrain or refine how those counter values are evaluated, aggregated, or selected during processing.

The table is classified as VALID and resides in the CSI schema with 35 documented columns. From a heuristic Data Vault modeling perspective, the mined FK structure suggests this object behaves as a standalone entity rather than a dependent satellite or a pure link. This classification is a modeling suggestion only; it reflects the absence of inbound dependencies within the provided relationship metadata, not a definitive architectural role.

Key Information Stored

The physical schema is anchored by a surrogate primary key, CSI_COUNTER_DERIVED_FILTERS_PK, defined on COUNTER_DERIVED_FILTER_ID. A unique index, CSI_CTR_DERIVED_FILTERS_U01, also exists on COUNTER_DERIVED_FILTER_ID, confirming it as the strongest business-key candidate documented for the table.

  • COUNTER_DERIVED_FILTER_ID — primary key and unique business-key candidate identifying each filter row.
  • COUNTER_ID — associates the filter with a specific counter definition.
  • SEQ_NO — ordering sequence for evaluating filter conditions.
  • COUNTER_PROPERTY_ID — identifies the counter property being tested by the filter.
  • RELATIONAL_OPERATOR — comparison operator (for example, equals, greater than) applied to the property.
  • RIGHT_VALUE — the literal or constant operand on the right side of the comparison.
  • LEFT_PARENT and RIGHT_PARENT — parenthetical grouping markers that express nested boolean logic.
  • LOGICAL_OPERATOR — boolean connector (AND/OR) between successive filter clauses.
  • START_DATE_ACTIVE and END_DATE_ACTIVE — effective-dating range governing when the filter is active.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the EBS framework.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant data segregation.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) columns.
  • MIGRATED_FLAG — indicates whether the row was migrated from a legacy source.

Common Use Cases and Queries

Typical usage centers on retrieving the active filter rules for a given counter so that application logic or reporting can evaluate counter readings against them. A common pattern filters by counter and effective date:

SELECT counter_derived_filter_id, seq_no, counter_property_id,
relational_operator, right_value, logical_operator
FROM csi.csi_counter_derived_filters
WHERE counter_id = :p_counter_id
AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);

Reporting scenarios include auditing which counters carry derived filters, verifying the effective-date coverage of filter definitions, and tracing migrated rows via MIGRATED_FLAG. Because SECURITY_GROUP_ID is populated, queries executed under multiple operating units or security contexts should join or filter against FND_SECURITY_GROUPS to respect data segregation. Ordered evaluation of the filter expression relies on SEQ_NO together with the parenthetical columns.

Related Objects

  • FND_SECURITY_GROUPS — referenced by the SECURITY_GROUP_ID foreign key, providing the security group definition for each row.
  • CSI_COUNTERS (COUNTER_ID) — the parent counter definition that each filter row qualifies; joins on COUNTER_ID.
  • CSI_COUNTER_PROPERTIES (COUNTER_PROPERTY_ID) — supplies the property metadata tested by the filter.
  • CSI_COUNTER_DERIVED_FILTERS_PK / CSI_CTR_DERIVED_FILTERS_U01 — the primary key constraint and unique index enforcing row identity.
  • CSI Install Base APIs — the public counter and counter-filter APIs that read and maintain these filter definitions at runtime.