Search Results class_category_group

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

Overview

FII_PARTY_MKT_CLASS_TYPE_V is a Financial Intelligence (FII) database view owned by the APPS schema. It exposes a filtered, translated list of Trading Community Architecture (TCA) party classification categories — the "class categories" that act as marketing and reporting classification types for parties (organizations and persons). Its distinguishing feature is that it returns the descriptive meaning of each class category in the language of the current session, rather than only the internal lookup code.

The view is a supporting lookup source for FII reporting and integration components that need to present party classification values in a user-readable form. Because marketing and segmentation reports frequently group or filter parties by classification category, this view centralizes the join logic between the classification metadata, its descriptive translation, and the registered usage of the category, so that downstream queries and concurrent programs do not have to reproduce it.

Note: the user's search term, hz_class_category_uses, maps directly to the underlying table HZ_CLASS_CATEGORY_USES, which this view relies on in its second UNION ALL branch.

Underlying Base Objects

The view is defined over the following TCA and Oracle Application Object Library (FND) tables:

• HZ_CLASS_CATEGORIES — The registration of each class category, including the multi-parent and multi-assign flags that control eligibility.
• FND_LOOKUP_TYPES_TL — The translated lookup type definitions, joined on LOOKUP_TYPE = CLASS_CATEGORY, VIEW_APPLICATION_ID = 222 (Oracle Customers / TCA), and LANGUAGE = USERENV('LANG').
• HZ_CLASS_CODE_RELATIONS — Used in a NOT EXISTS-style subquery to exclude categories with an active class code relation at the current date.
• HZ_CODE_ASSIGNMENTS — Used both to restrict the view to categories assigned to the ORG_GROUP class code group and to exclude categories already assigned through the assignment mechanism.
• HZ_CLASS_CATEGORY_USES — Inspected via ADDITIONAL_WHERE_CLAUSE and OWNER_TABLE (='HZ_PARTIES') to determine whether a category is intended for organization or person parties. The DECODE / LIKE logic matches '%PARTY_TYPE%ORGANIZATION%' for the ORG_GROUP branch and '%PARTY_TYPE%PERSON%' for the PERSON_GROUP branch, also allowing NULL or 'WHERE 1=1' clauses.

The view is the UNION ALL of two branches: the first returns ORG_GROUP-registered categories from HZ_CODE_ASSIGNMENTS, and the second derives the equivalent set from the HZ_CLASS_CATEGORY_USES usage definitions. Across both branches, only categories where ALLOW_MULTI_PARENT_FLAG = 'N' and ALLOW_MULTI_ASSIGN_FLAG = 'N' are exposed, and only those in the ORG_GROUP scope.

Key Columns

• CLASS_CATEGORY — The internal lookup/code value identifying the party class category (for example, a marketing segment or classification type). Joins to HZ_CLASS_CATEGORIES.CLASS_CATEGORY and, by extension, to subclass assignments.
• MEANING — The translated display name of the class category from FND_LOOKUP_TYPES_TL for the session language, suitable for report labels and LOVs.

The view intentionally projects only these two columns, keeping the interface narrow for use in lookup queries and value sets.

Common Use Cases and Queries

Typical uses include driving a user-facing list of valid party class categories, or resolving codes to meanings for customer segmentation reports. A representative query:

• SELECT CLASS_CATEGORY, MEANING FROM FII_PARTY_MKT_CLASS_TYPE_V ORDER BY MEANING;
• Joining resolved meanings to party classifications: SELECT pc.party_id, v.meaning FROM hz_party_classifications pc, FII_PARTY_MKT_CLASS_TYPE_V v WHERE pc.class_category = v.class_category;
• Filtering for organization-scoped categories: SELECT meaning FROM FII_PARTY_MKT_CLASS_TYPE_V WHERE class_category IN (SELECT owner_table_key_1 FROM hz_code_assignments WHERE class_category='CLASS_CATEGORY_GROUP' AND class_code='ORG_GROUP');

Because the view filters out categories with active class code relations and multi-assign capability, it is best used where a single, unambiguous category per party is required.