Search Results cs_ctr_formula_bvars_u1

Overview

CS_CTR_FORMULA_BVARS is a table in the Customer Care (CS) schema of Oracle E-Business Suite. Its name indicates that it is intended to hold bind variable definitions used by counter formulas: the BIND_VAR_NAME column stores the formula reference (bind variable) name, and the surrounding columns associate those references with counters and with the inventory items or counters into which they are mapped. It therefore belongs to the telephony and counter configuration area of Oracle Advanced Support / Customer Care, where counters evaluate arithmetic expressions against measured usage data.

Two points of caution are documented in the ETRM metadata. First, the object's own dictionary comment states that the table is not used, so no seeded application logic in Release 12.1.1 or 12.2.2 reads or writes it during normal processing. Second, the table is classified by heuristic analysis of its foreign key structure as a link table — a modeling suggestion rather than a certified fact. That classification is consistent with its shape: it resolves many-to-many relationships between counters and bind variables, and additionally carries surrogate foreign keys to inventory items and to a second counter, which are typical of a link or association entity.

Key Information Stored

The table contains 29 documented columns. The most significant are:

• CTR_FORMULA_BVAR_ID — NUMBER primary key. It is also the single column of the unique index CS_CTR_FORMULA_BVARS_U1, making it the surrogate identifier and the business-key candidate recognized by the dictionary.
• COUNTER_ID — NUMBER. Identifies the counter to which the formula reference belongs; the leading column of the non-unique index CS_CTR_FORMULA_BVARS_U2.
• BIND_VAR_NAME — VARCHAR2(15). The formula reference (bind variable) name; the second column of CS_CTR_FORMULA_BVARS_U2, so the index supports lookups by counter and variable name together.
• MAPPED_INV_ITEM_ID — NUMBER. The inventory item to which the formula reference resolves.
• MAPPED_COUNTER_ID — NUMBER. The counter to which the formula reference resolves.
• READING_TYPE — documented column used to qualify the nature of the reading associated with the variable.
• OBJECT_VERSION_NUMBER — NUMBER. Sequential value used for optimistic database locking control.
• SECURITY_GROUP_ID — NUMBER. Security group partitioning column, referenced against FND_SECURITY_GROUPS.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — the standard WHO audit columns.
• ATTRIBUTE1 through ATTRIBUTE15 — VARCHAR2(150) descriptive flexfield segments.
• CONTEXT — VARCHAR2(240), the descriptive flexfield structure name qualifying which attribute segments are populated.

Common Use Cases and Queries

Because the table is documented as not used, practical work with CS_CTR_FORMULA_BVARS is almost always investigative: confirming that no custom or third-party code depends on it before archiving or purging, or auditing residual rows left by legacy releases. Typical queries include counting rows and checking for orphaned references:

• Row census and recency: SELECT COUNT(*), MAX(last_update_date) FROM cs.cs_ctr_formula_bvars;
• Variables per counter: SELECT counter_id, bind_var_name, mapped_inv_item_id, mapped_counter_id FROM cs.cs_ctr_formula_bvars ORDER BY counter_id, bind_var_name;
• Orphan detection against the parent counter table: SELECT b.ctr_formula_bvar_id FROM cs.cs_ctr_formula_bvars b WHERE NOT EXISTS (SELECT 1 FROM cs.cs_counters c WHERE c.counter_id = b.counter_id);
• Security group validation: SELECT b.security_group_id, COUNT(*) FROM cs.cs_ctr_formula_bvars b GROUP BY b.security_group_id;

All queries should be executed with the CS or APPS schema and, given the table's status, used for diagnostic rather than functional reporting purposes.

Related Objects

The following objects are the most significant dependencies, drawn from the documented foreign keys and indexes:

• CS.CS_COUNTERS — referenced twice, by COUNTER_ID (the owning counter) and by MAPPED_COUNTER_ID (the resolved counter).
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for row-level security partitioning.
• CS_CTR_FORMULA_BVARS_U1 — unique index on CTR_FORMULA_BVAR_ID; the primary key constraint CS_CTR_FORMULA_BVARS_PK is enforced through it.
• CS_CTR_FORMULA_BVARS_U2 — non-unique index on (COUNTER_ID, BIND_VAR_NAME), supporting counter-scoped variable lookups.
• INV.MTL_SYSTEM_ITEMS — logically related through MAPPED_INV_ITEM_ID, though no enforced foreign key is documented.
• Formula and counter configuration tables in the CS schema — the functional parents implied by COUNTER_ID; any custom extension reading BIND_VAR_NAME should be reviewed before relying on this table.