Results for “csc_prof_category_lookups_v”

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

Overview

CSC_PROF_CATEGORY_LOOKUPS_V is an APPS-owned database view within the Oracle E-Business Suite Customer Care (CSC) product family. It is classified as a reporting and reference view, presenting a denormalized, human-readable projection of profile group category data combined with its corresponding lookup definitions. In EBS 12.1.1 and 12.2.2, views of this type are commonly consumed by concurrent programs, Oracle Reports outputs, OA Framework pages, and integration extracts that require descriptive category labels rather than raw lookup codes.

The view joins two documented base objects to produce a single row per profile group category, resolved against the CSC_PROF_CATEGORIES lookup type. Because it encapsulates the join logic, the view abstracts referential lookups from downstream consumers, ensuring that applications querying CSC_PROF_CATEGORY_LOOKUPS_V receive the decoded meaning without needing direct knowledge of the lookup table structure or the specific lookup type string.

Underlying Base Objects

According to ETRM metadata for 12.2.2, the view is defined over two referenced objects:

• CSC_PROF_GROUP_CATEGORIES (documented as a SYNONYM) — the primary driver table, storing profile group category assignments including the group identifier, category code, and sequence.
• CSC_LOOKUPS (documented as a VIEW) — the lookup reference object supplying the descriptive meaning for each category code.

The view text confirms this relationship: it selects from CSC_PROF_GROUP_CATEGORIES alias CPGC and CSC_LOOKUPS alias LK, applying the join condition CPGC.CATEGORY_CODE = LK.LOOKUP_CODE restricted by LK.LOOKUP_TYPE = 'CSC_PROF_CATEGORIES'. This constraint ensures that only lookup values belonging to the profile categories lookup type participate in the join, preventing cross-type contamination.

Key Columns

The view exposes six columns, each carrying specific semantic weight:

• ROW_ID — the ROWID of the underlying CSC_PROF_GROUP_CATEGORIES row, useful as a unique row handle for update or delete operations performed through the view.
• GROUP_CATEGORY_ID — the surrogate primary key identifying each profile group category record.
• GROUP_ID — the foreign key identifying the parent profile group to which the category belongs.
• CATEGORY_CODE — the stored lookup code representing the category. This is the column most frequently targeted when users search for "category_code."
• CATEGORY_SEQUENCE — the ordinal position controlling display or processing order of categories within a group.
• MEANING — the decoded, user-facing description retrieved from CSC_LOOKUPS for the matching category code.

Common Use Cases and Queries

Typical reporting scenarios include listing all categories for a given profile group with their descriptive meanings, generating ordered category listings for UI display, and validating that category codes have valid lookup definitions. A representative query retrieving categories for a specific group is:

• SELECT group_category_id, group_id, category_code, category_sequence, meaning FROM apps.csc_prof_category_lookups_v WHERE group_id = :p_group_id ORDER BY category_sequence;
• SELECT category_code, meaning FROM apps.csc_prof_category_lookups_v WHERE category_code = :p_category_code; — to resolve a specific code's meaning.
• SELECT group_id, COUNT(*) FROM apps.csc_prof_category_lookups_v GROUP BY group_id; — to summarize category counts per group.

Because the view resolves meanings inline, it eliminates the need for downstream joins to CSC_LOOKUPS and enforces consistent lookup type filtering. Developers building custom reports or interfaces against Customer Care profile configuration should query this view rather than reconstructing the join manually, ensuring alignment with Oracle's supported access path.