Results for “ams_p_org_profiles_v”

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

Overview

AMS_P_ORG_PROFILES_V is a public view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AMS (Marketing) product family. Its documented purpose is to return an organization profile for a given organization, primarily to support list generation within Oracle Marketing and related campaign and audience-building functions. The view is marked VALID in the ETRM reference for releases 12.1.1 and 12.2.2, and its definition is intentionally denormalized: it exposes a single wide row per organization profile, combining identity, demographic, credit, and attribute columns into one convenient projection. Because it is a view rather than a table, consumers gain read-only access to profile data without needing to navigate the many foreign keys and lookup structures present in the underlying model.

Underlying Base Objects

Per the documented metadata, AMS_P_ORG_PROFILES_V is defined over HZ_ORGANIZATION_PROFILES, accessed through a synonym in the APPS schema. HZ_ORGANIZATION_PROFILES is the Trading Community Architecture (TCA) table that stores organization-level profile information, including firmographics, credit data, and classification attributes. The view selects from this base object and aliases ORGANIZATION_PROFILE_ID to AMS_ORG_PROFILE_ID, which aligns the TCA primary key with the naming convention expected by the AMS list-generation code. No joins to other tables are documented in the excerpted view text; the projection is drawn from the single base table, though a PARTY_ID column is carried forward to link the profile back to the HZ_PARTIES record representing the organization.

Key Columns

The view exposes several logical groupings of columns:

• Identity: AMS_ORG_PROFILE_ID (aliased from ORGANIZATION_PROFILE_ID), PARTY_ID, ORGANIZATION_NAME, and KNOWN_AS.
• Descriptive attributes: ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20, plus the parallel GLOBAL_ATTRIBUTE_CATEGORY and GLOBAL_ATTRIBUTE1–GLOBAL_ATTRIBUTE20 flexfields.
• Firmographics: LEGAL_STATUS, CONTROL_YR, YEAR_ESTABLISHED, EMPLOYEES_TOTAL, TOTAL_EMPLOYEES_TEXT, ORGANIZATION_TYPE, CORPORATION_CLASS, and INCORP_YEAR.
• Classification indicators: HQ_BRANCH_IND, BRANCH_FLAG, OOB_IND, IMPORT_IND, EXPORT_IND, MINORITY_OWNED_IND, WOMAN_OWNED_IND, DISADV_8A_IND, SMALL_BUS_IND, PARENT_SUB_IND, PUBLIC_PRIVATE_OWNERSHIP_FLAG, and INTERNAL_FLAG — the latter being the flag commonly used to separate internal organizations from external ones.
• Credit and risk: FAILURE_SCORE, FAILURE_SCORE_NATL_PERCENTILE, FAILURE_SCORE_OVERRIDE_CODE, GLOBAL_FAILURE_SCORE, DB_RATING, CREDIT_SCORE, PAYDEX_SCORE, and HIGH_CREDIT/AVG_HIGH_CREDIT.
• Contact and other data: BEST_TIME_CONTACT_BEGIN/END, PREF_FUNCTIONAL_CURRENCY, LOCAL_BUS_IDEN_TYPE, LOCAL_BUS_IDENTIFIER, and TOTAL_PAYMENTS.

Common Use Cases and Queries

Because the view is used for list generation, the most common pattern is to filter organizations by one or more classification or firmographic criteria before feeding them into a Marketing list. A typical query selecting internal organizations is:

• SELECT ams_org_profile_id, party_id, organization_name FROM apps.ams_p_org_profiles_v WHERE internal_flag = 'Y';

Other frequent scenarios include segmenting by size or ownership, for example filtering on EMPLOYEES_TOTAL or minority-owned indicators, and enriching campaign target lists with credit ratings for B2B collections or risk-driven outreach. Analysts also join the view to HZ_PARTIES on PARTY_ID or to HZ_CUST_ACCOUNTS when a customer context is required. Because the underlying table is TCA-based, query performance benefits from indexed access on PARTY_ID, and applications should treat the view strictly as read-only.