Search Results source_object_name

Overview

CS_CTR_ASSOCIATIONS_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the Service (CS) product family and is documented in ETRM as the "Counter group associations view." Its purpose is to expose the relationship between counter groups maintained in Oracle Service and the inventory items that serve as the source objects for those counters, resolving the raw foreign key identifier stored on the association record into human-readable item segments and descriptions.

The view is a reporting and integration surface rather than a transactional entry point. It presents the same attributes as the underlying association entity while adding two denormalized columns derived from the item master. Because it performs the item lookup internally, it is well suited to concurrent programs, Discoverer workbooks, OBIEE extracts, and inbound interface verification routines that must display or validate which inventory item a counter group is associated with. The view is defined as VALID and conforms to the standard EBS audit column convention (WHO columns, DFF attributes, and OBJECT_VERSION_NUMBER for optimistic locking).

Underlying Base Objects

The view is defined over three documented base objects:

• CS_CTR_ASSOCIATIONS (synonym to the APPS base table) — the driving table, aliased A, holding counter association rows keyed by CTR_ASSOCIATION_ID and linked to a counter group through COUNTER_GROUP_ID.
• MTL_SYSTEM_ITEMS_KFV (synonym) — the key flexfield item view, aliased B, supplying the CONCATENATED_SEGMENTS and DESCRIPTION used for the SOURCE_OBJECT_NAME and SOURCE_OBJECT_DESCRIPTION columns.
• CS_STD (package) — the Service standards package, whose function CS_STD.GET_ITEM_VALDN_ORGZN_ID is invoked in the join predicate to supply the validation organization for the item flexfield.

The join between A and B is an outer join on SOURCE_OBJECT_ID = INVENTORY_ITEM_ID, with the organization restriction applied on the B side. Because the item side is outer-joined and its organization is resolved dynamically at runtime through CS_STD, association rows whose source item cannot be resolved in the current validation organization still appear in the result set with null name and description values. The view also selects A.ROWID to support row-level addressing and updates performed through the view.

Key Columns

• CTR_ASSOCIATION_ID — primary identifier of the counter-to-object association record.
• COUNTER_GROUP_ID — foreign key to the counter group that owns the association.
• SOURCE_OBJECT_ID — the raw inventory item identifier stored on the association record.
• SOURCE_OBJECT_NAME — the concatenated flexfield segments of the item (B.CONCATENATED_SEGMENTS), which is the column most frequently referenced when users search by item name.
• SOURCE_OBJECT_DESCRIPTION — the item description from the item master.
• ROW_ID — the base table ROWID, exposed for row-level operations.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, plus OBJECT_VERSION_NUMBER for concurrent update control.
• ATTRIBUTE1 through ATTRIBUTE15 and CONTEXT — descriptive flexfield columns carried through from the base table for extensibility.

Common Use Cases and Queries

Typical usage includes listing all item associations for a given counter group, reconciling counter group configuration after a migration, and driving reports that must show the item number instead of an internal identifier. The following query retrieves the associated items for a specific counter group:

• SELECT ctr_association_id, counter_group_id, source_object_id, source_object_name, source_object_description FROM cs_ctr_associations_v WHERE counter_group_id = :p_counter_group_id ORDER BY source_object_name;
• SELECT counter_group_id, COUNT(*) FROM cs_ctr_associations_v WHERE source_object_name IS NULL GROUP BY counter_group_id; — identifies associations whose source item does not resolve to the current validation organization, a frequent finding during item organization setup reviews.
• SELECT ctr_association_id, source_object_name, last_update_date, last_updated_by FROM cs_ctr_associations_v WHERE last_update_date >= :p_since; — supports incremental auditing of configuration changes.

Queries should filter on counter_group_id or source_object_id where possible to leverage the base table indexes; unrestricted scans force evaluation of the CS_STD item validation organization for every row.