Search Results class_code_meaning

Overview

AST_PARTY_CLASSIFICATION_V is a read-only reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the AST (TeleSales) product module. It presents party-level classification assignments — records that associate a classification category and class code with a specific party record — in a denormalized, presentation-ready form. The view surfaces the code assignment identifier exposed in the user's search term, code_assignment_id, which is the primary key of the underlying assignment row in HZ_CODE_ASSIGNMENTS.

In EBS 12.1.1 and 12.2.2, the view functions as a semantic layer over the Oracle Trading Community Architecture (TCA) classification tables. Instead of requiring callers to resolve lookup meanings, category descriptions, and owner table filtering manually, the view pre-joins the assignment records to their category and lookup definitions and constrains the result set to party-owned assignments only (OWNER_TABLE_NAME = 'HZ_PARTIES'). This makes it suitable for TeleSales screens, concurrent reporting, and integration extracts that need human-readable classification data.

Underlying Base Objects

The view is defined over four documented objects:

• HZ_CODE_ASSIGNMENTS (synonym) — the driving table, aliased COD, holding the classification assignment rows keyed by CODE_ASSIGNMENT_ID.
• HZ_CLASS_CATEGORIES (synonym) — aliased CAT, joined on CLASS_CATEGORY to supply category metadata.
• AR_LOOKUPS (view) — aliased LKUP, joined on LOOKUP_CODE and LOOKUP_TYPE to resolve the class code meaning.
• AR_LOOKUP_TYPES (view) — aliased TYPE, outer-joined ((+)) on LOOKUP_TYPE to supply the category description.

The inner joins on AR_LOOKUPS and HZ_CLASS_CATEGORIES mean that assignments with no matching lookup or category are excluded; only the description join to AR_LOOKUP_TYPES is outer, so a missing type description does not suppress a row.

Key Columns

• CODE_ASSIGNMENT_ID — unique identifier of the classification assignment; the principal key used in joins and by-key lookups.
• OWNER_TABLE_NAME / OWNER_TABLE_ID — identify the owning entity; the view hard-codes HZ_PARTIES with the party identifier in the ID column.
• CLASS_CATEGORY / CLASS_CATEGORY_DESC — the category code and its description from AR_LOOKUP_TYPES.
• CLASS_CODE / CLASS_CODE_MEANING — the assigned class value and its translated meaning from AR_LOOKUPS.
• PRIMARY_FLAG, IMPORTANCE_RANKING, RANK — indicate whether a classification is primary and provide ordering/priority for multiple codes in a category.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating window for the assignment.
• STATUS and standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) plus APPLICATION_ID and CREATED_BY_MODULE for auditing and origin tracking.

Common Use Cases and Queries

Typical uses include retrieving all classifications for a party, listing primary classifications only, and joining to other TCA party views for reporting. Because the view filters to HZ_PARTIES, it is safe to treat OWNER_TABLE_ID as a party ID.

• All classifications for a party:

SELECT code_assignment_id, class_category,
       class_category_desc, class_code,
       class_code_meaning, primary_flag
FROM   apps.ast_party_classification_v
WHERE  owner_table_id = :p_party_id
ORDER BY class_category, importance_ranking;

• Primary classifications only:

SELECT owner_table_id, class_category, class_code_meaning
FROM   apps.ast_party_classification_v
WHERE  primary_flag = 'Y'
AND    SYSDATE BETWEEN start_date_active
                   AND NVL(end_date_active, SYSDATE + 1);

• Resolution by code assignment ID:

SELECT owner_table_id, class_category, class_code
FROM   apps.ast_party_classification_v
WHERE  code_assignment_id = :p_code_assignment_id;

Callers should note the view is not intended for direct DML; updates belong to the HZ_CODE_ASSIGNMENTS base table through TCA APIs.