Search Results right_value




Overview

CSI_COUNTER_DER_FILTERS_V is a reporting and integration view owned by the APPS schema within the CSI — Install Base product of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. The view exposes counter derived filter definitions used by the Install Base counter engine. Counter derived filters define the conditional expressions applied when derived counters are calculated across installed base assets. Each filter row represents a single predicate component — a left operand, a relational operator, and a right operand — combined through logical operators to form a larger Boolean expression.

The view functions predominantly as a read-only presentation layer over the base filter entity, enriching each filter row with the descriptive counter name. Because the object carries the _V suffix and is documented in ETRM as a VIEW with VALID status, it is intended for queries and integration extracts rather than direct DML. Typical consumers include custom reports, diagnostics, and interface programs that must resolve how a derived counter is evaluated without navigating the underlying tables and their translation-enabled property view directly.

Underlying Base Objects

Per the documented ETRM metadata, CSI_COUNTER_DERIVED_FILTERS_V is defined over two base objects:

  • CSI_COUNTER_DERIVED_FILTERS (referenced as a SYNONYM in APPS) — the primary transactional entity holding each filter condition, its sequencing, operands, operators, date-effective range, descriptive flexfield attributes, and standard WHO columns. It supplies the majority of the view's columns.
  • CSI_COUNTER_PROPERTIES_VL (VIEW) — the translated counter properties view, joined to supply the counter's display name through CCPV.NAME. This is a _VL view, so the name returned is language-sensitive.

The join between the two objects is an outer join on COUNTER_PROPERTY_ID (CCDF.COUNTER_PROPERTY_ID = CCPV.COUNTER_PROPERTY_ID(+)), meaning filter rows are retained even when no matching counter property translation exists. The view therefore preserves all derived filter definitions while optionally decorating them with counter property naming.

Key Columns

Common Use Cases and Queries

The view is commonly queried to reconstruct the Boolean logic of a derived counter, to audit filter definitions by effective date, and to extract counter logic for migration or documentation. A representative query joining the view back to the base entity and filtering on the requested attribute is:

  • Retrieve all filters for a counter, ordered for evaluation: SELECT counter_derived_filter_id, counter_name, seq_no, left_parent, relational_operator, right_value, right_parent, logical_operator FROM csi_counter_der_filters_v WHERE counter_id = :p_counter_id ORDER BY seq_no;
  • Audit active filters as of a date: SELECT * FROM csi_counter_der_filters_v WHERE SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);
  • Isolate rows with right-side grouping: SELECT counter_derived_filter_id, right_parent, logical_operator FROM csi_counter_der_filters_v WHERE right_parent IS NOT NULL;
  • Report counter names alongside filter expressions: SELECT counter_name, seq_no, relational_operator, right_value FROM csi_counter_der_filters_v WHERE migrated_flag = 'N';

Because COUNTER_NAME derives through an outer join, queries requiring a guaranteed counter name should add a filter such as counter_name IS NOT NULL or join explicitly to CSI_COUNTER_PROPERTIES_VL. When the requested attribute "right_parent" is absent for a row, the null value indicates that the right operand is not parenthesized independently, which is significant when reconstructing nested expressions from the flat filter rows.