Search Results class_category_desc

Overview

AST_PARTY_CLASSIFICATION_V is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data as AST.AST_PARTY_CLASSIFICATION_V. Its status is VALID in both 12.1.1 and 12.2.2. The view exists primarily to simplify forms coding within the Asset (AST) module, presenting party classification assignments in a denormalized, user-friendly form. Classification assignments associate a party record with a class category and a specific class code, and the view resolves the raw codes into their descriptive meanings for direct display on Oracle Forms screens.

Because the view is designated Oracle Internal Use Only, Oracle does not support direct customer access to its data except through standard Oracle Applications programs. The view type is explicitly described as a supplementary view used to simplify forms coding, with an accompanying warning that Oracle does not recommend querying or altering data through it and that its definition may change dramatically in subsequent minor or major releases. Consequently, the view should be treated as a reporting and diagnostic convenience rather than a stable integration interface.

Underlying Base Objects

The ETRM documentation lists four referenced base objects: AR_LOOKUPS (VIEW), AR_LOOKUP_TYPES (VIEW), HZ_CLASS_CATEGORIES (SYNONYM), and HZ_CODE_ASSIGNMENTS (SYNONYM). The HZ_CODE_ASSIGNMENTS synonym points to the base table storing individual code assignment rows, keyed by CODE_ASSIGNMENT_ID and linked to an owner table and owner record through OWNER_TABLE_NAME and OWNER_TABLE_ID. The HZ_CLASS_CATEGORIES synonym supplies the class category definitions, including the CLASS_CATEGORY code and its descriptive CLASS_CATEGORY_DESC. The AR_LOOKUPS and AR_LOOKUP_TYPES views provide the lookup-based resolution of class codes to their meanings, which is reflected in CLASS_CODE_MEANING. In combination, these objects allow the view to join assignment records to their category and code definitions without requiring the calling form or report to navigate the underlying normalized structure.

Key Columns

• CODE_ASSIGNMENT_ID — Numeric primary identifier for the classification assignment row (length 15).
• OWNER_TABLE_NAME / OWNER_TABLE_ID — Identify the entity to which the classification applies and its primary key value.
• CLASS_CATEGORY — The class category code (length 30) drawn from HZ_CLASS_CATEGORIES.
• CLASS_CATEGORY_DESC — The descriptive text for the category (length 80). This column directly answers searches such as "class_category_desc" and is the human-readable label displayed on forms.
• CLASS_CODE / CLASS_CODE_MEANING — The assigned class code and its resolved meaning (lengths 30 and 80 respectively), sourced via AR_LOOKUPS.
• PRIMARY_FLAG — Indicates whether the assignment is the primary classification for the party.
• IMPORTANCE_RANKING / RANK — Ordering attributes (length 240 for importance ranking text; RANK is numeric).
• START_DATE_ACTIVE / END_DATE_ACTIVE / STATUS — Effective dating and status controls for the assignment.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE, LAST_UPDATED_BY, plus OBJECT_VERSION_NUMBER, CREATED_BY_MODULE, and APPLICATION_ID.

Common Use Cases and Queries

Typical use cases include diagnosing classification assignments for a party, validating that a category description is correctly resolving, and producing ad hoc reports of active classifications. A representative query follows:

SELECT code_assignment_id, owner_table_name, owner_table_id, class_category, class_category_desc, class_code, class_code_meaning, primary_flag, status, start_date_active, end_date_active FROM apps.ast_party_classification_v WHERE class_category_desc LIKE '%CUSTOMER%' AND status = 'A' ORDER BY importance_ranking;

Additional scenarios include joining the view to a party table on OWNER_TABLE_ID to enrich party extracts, and filtering on PRIMARY_FLAG to isolate the principal classification. Given the internal-use designation and the volatility warning, any such query should be treated as diagnostic and re-validated after upgrades.