Results for “cs_cp_contracts_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CS_CP_CONTRACTS_V is a documented Oracle E-Business Suite view owned by the APPS schema and delivered as part of the CS (Service) product family. The view exposes information regarding counter groups used within the Service module. Despite the broader naming convention implied by the "CONTRACTS" token in its object name, the ETRM-documented definition of this view is narrow and specific: it returns counter group identification and descriptive attributes. The view presents the columns COUNTER_GROUP_ID, NAME, and DESCRIPTION, drawn directly from the CS_COUNTER_GROUPS source. Its reported status in ETRM is VALID, indicating that it is a supported, compiled database object within the 12.1.1 and 12.2.2 environments.

In the context of Oracle EBS reporting and integration, this view functions as a simplified, presentation-layer access point over counter group metadata. Consumers searching for counter_group_id are typically attempting to resolve the numeric identifier of a counter group into a human-readable name, or to join counter group identifiers held on transactional or setup tables back to meaningful descriptions. Because the view is APPS-owned, it is queryable from custom reports, concurrent programs, BI Publisher data models, and interface programs without requiring direct grants to the underlying table, provided the calling responsibility has the appropriate privileges.

Underlying Base Objects

The ETRM documentation records a single referenced base object for this view: CS_COUNTER_GROUPS, exposed in the APPS schema as a SYNONYM. The view text is documented as:

• SELECT COUNTER_GROUP_ID, NAME, DESCRIPTION FROM CS_COUNTER_GROUPS

This is a straightforward projection with no joins, filters, aggregation, or expressions. Consequently, the view carries no additional business logic beyond column exposure; row counts and predicate pushdown behaviour are effectively identical to querying the synonym directly. The relationship is therefore one-to-one: each row in CS_COUNTER_GROUPS appears as one row in CS_CP_CONTRACTS_V. Any change to the base counter group definition table is immediately reflected in the view, as no materialization or snapshot mechanism is involved.

Key Columns

• COUNTER_GROUP_ID — The primary identifier for a counter group. This numeric key is the column most frequently referenced in searches and is the value used in foreign-key relationships elsewhere in the Service schema.
• NAME — The user-defined or seeded name of the counter group, providing the readable label used in setup forms, lists of values, and operational reporting.
• DESCRIPTION — Free-text descriptive detail attached to the counter group, useful for disambiguating similarly named groups in reporting output.

No lookup, status, or date-effective columns are documented for this view. Consumers requiring additional attributes must query the base object or related counter setup tables directly.

Common Use Cases and Queries

The principal use case is resolving counter group identifiers obtained from counter readings, service contracts, or installed base records into readable labels. A typical reporting query joins the view to a fact or detail table carrying COUNTER_GROUP_ID.

• List all counter groups: SELECT counter_group_id, name, description FROM cs_cp_contracts_v ORDER BY name;
• Resolve a specific identifier: SELECT name, description FROM cs_cp_contracts_v WHERE counter_group_id = :p_group_id;
• Join to detail data: SELECT d.counter_group_id, v.name, COUNT(*) FROM cs_counter_readings d, cs_cp_contracts_v v WHERE d.counter_group_id = v.counter_group_id GROUP BY d.counter_group_id, v.name;

These patterns are appropriate for custom concurrent programs, ad hoc SQL*Plus extracts, and BI Publisher datasets. Because the view is thin, no performance penalty relative to the synonym is expected; standard indexing on COUNTER_GROUP_ID in the base object governs access paths.