Search Results group_description




Overview
Explore in AI Chat

Overview

APPS.CST_CIMP_GROUP_ID is a Cost Management (CST) interface view in Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It presents a consolidated, de-duplicated list of cost interface group identifiers that are currently eligible for processing by the Cost Interface Manager (CIM) concurrent programs. Rather than exposing transactional cost lines, the view acts as a driver or lookup layer: it answers the question "which interface group IDs have pending work that is ready to be picked up?" by scanning the four cost interface tables used by the Cost Management open interfaces.

Its functional role is closely tied to the column the user searched for, GROUP_DESCRIPTION. Because the view returns both the character-formatted group ID and its human-readable description, it supplies the context needed for parameter lists of CIM processes (for example, the "Cost Interface Group ID" parameter of the Cost Interface Manager and related cost import programs) and for diagnostic reports that let users identify which staged cost data belongs to which logical batch. In this sense it is a control/selection view rather than a data-entry or transactional view.

Underlying Base Objects

The view is owned by APPS and is defined over four interface synonyms, each mapping to a Cost Management interface table:

The view issues a UNION over four SELECT statements, one per table, each projecting TO_CHAR(group_id), group_description, and a literal discriminator value (1, 2, or 3). The discriminator distinguishes the source table: 1 maps to the item cost detail interface, 2 to the resource costs interface, and 3 to both the department overheads and resource overheads interfaces. Each branch applies identical filter predicates: GROUP_ID IS NOT NULL, PROCESS_FLAG = 1, and ERROR_FLAG IS NULL. Consequently only groups flagged for processing and free of errors are surfaced.

Key Columns

  • TO_CHAR(GROUP_ID) — the interface group identifier rendered as a character string. Group IDs tie together the individual interface rows that belong to one logical cost upload or batch, so all rows sharing a group ID are processed as a unit by the Cost Interface Manager. Returning it as a string normalizes the presentation across tables and simplifies use in parameter lists and report predicates.
  • GROUP_DESCRIPTION — the descriptive label recorded on the interface rows for that group, providing the user-facing identity of the batch. This is the column referenced by the "group_description" search and is what allows users to recognize and select a group without knowing its numeric ID.
  • Literal discriminator (1, 2, or 3) — an unnamed third column indicating which source interface the row originated from. It is useful for segmentation and for determining whether a group contains item, resource, or overhead cost data.

Common Use Cases and Queries

Typical usage includes populating selection lists and validating the group before invoking Cost Interface Manager processing, and troubleshooting which source interface is contributing to a pending batch. A simple listing query is:

  • SELECT TO_CHAR(group_id), group_description, 1 FROM CST_ITEM_CST_DTLS_INTERFACE WHERE group_id IS NOT NULL AND process_flag = 1 AND error_flag IS NULL UNION SELECT TO_CHAR(group_id), group_description, 2 FROM CST_RESOURCE_COSTS_INTERFACE WHERE group_id IS NOT NULL AND process_flag = 1 AND error_flag IS NULL UNION SELECT TO_CHAR(group_id), group_description, 3 FROM CST_DEPT_OVERHEADS_INTERFACE WHERE group_id IS NOT NULL AND process_flag = 1 AND error_flag IS NULL UNION SELECT TO_CHAR(group_id), group_description, 3 FROM CST_RES_OVERHEADS_INTERFACE WHERE group_id IS NOT NULL AND process_flag = 1 AND error_flag IS NULL;

Because it is a UNION and not a UNION ALL, duplicate group IDs arising where the same group spans multiple interface tables are collapsed automatically. A common refinement is SELECT DISTINCT group_id, group_description FROM apps.cst_cimp_group_id ORDER BY group_description for a clean pick-list. Practitioners also join this view back to the four interface tables on group_id to inspect individual ready-to-process rows, and filter on the discriminator when isolating, for example, only resource cost groups.