Results for “source_object_id”

50+ results




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

Overview

The view OKX_CTR_ASSOCIATIONS_V is a reporting and integration object owned by the APPS schema within the Oracle E-Business Suite (OKX — Contracts Integration product). Its documented purpose is to present counter group associations to inventory items. In the architecture of Oracle Contracts Integration, a "counter group" is a logical grouping of counters — numeric, monetary, or date-based attributes that accumulate against a contract or contract line. The OKX_CTR_ASSOCIATIONS_V view exposes the linkage between these counter groups and the source objects (typically inventory items) with which they are associated, allowing downstream reporting, form queries, and programmatic integration to retrieve association data through a stable, read-only interface rather than querying the transactional base table directly. The object is documented as VALID and is available in the Oracle EBS 12.1.1 and 12.2.2 releases referenced by the ETRM metadata.

Underlying Base Objects

The view is defined as a simple projection over a single base object:

  • CS_CTR_ASSOCIATIONS — referenced through a synonym. The view text selects directly from this synonym with no joins, unions, or aggregation, so the view is a one-to-one passthrough of the underlying rows.

Because there are no joins, the cardinality of the view matches that of CS_CTR_ASSOCIATIONS exactly. The base table stores the persistent relationship between counter groups and their associated source objects; the view simply renames the surrogate key column (ASSOCIATION_ID becomes CTR_ASSOCIATION_ID) and exposes a restricted column list. This design keeps the public interface narrow and shields callers from columns that may be added to or changed on the base table over time.

Key Columns

The view exposes three columns, as documented:

  • CTR_ASSOCIATION_ID — The unique surrogate identifier for each association record. It is sourced from CS_CTR_ASSOCIATIONS.ASSOCIATION_ID and serves as the primary lookup key for a specific counter group–source object pairing.
  • COUNTER_GROUP_ID — The foreign key identifying the counter group that is being associated. This value points into the counter group definition, allowing the caller to resolve the group's name, type, and behavior.
  • SOURCE_OBJECT_ID — The identifier of the object being associated, documented as the inventory item. In practice this is the inventory item's identifier within the applicable source object context, enabling the counter group to be tied to specific items.

Common Use Cases and Queries

Typical usage centers on resolving which counter groups are attached to which inventory items during contract setup, order capture, or reporting. A straightforward retrieval by counter group is shown below:

  • List all associations for a given counter group:
    SELECT ctr_association_id, counter_group_id, source_object_id FROM okx_ctr_associations_v WHERE counter_group_id = :p_counter_group_id;
  • Find the counter groups associated with a specific inventory item:
    SELECT counter_group_id, ctr_association_id FROM okx_ctr_associations_v WHERE source_object_id = :p_item_id;
  • Validate that an association exists before processing:
    SELECT COUNT(*) FROM okx_ctr_associations_v WHERE counter_group_id = :p_group AND source_object_id = :p_item;

Because the view performs no joins, these queries are inexpensive and can be embedded in concurrent programs, OAF/Forms LOVs, or integration extracts. Joins to counter group definition tables and item master views should be added by the caller as required to enrich the result set.