Results for “ams_lt_org_profiles_v”

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

Overview

AMS_LT_ORG_PROFILES_V is a data source view owned by the APPS schema in Oracle E-Business Suite, registered under the AMS (Marketing) product family. It is documented as a "Data Source view based on hz_organization_profiles," which places it in the class of objects that Oracle Marketing and its lead-to-opportunity components use to expose trading-community and organization-profile attributes to reporting, list generation, and integration consumers. Because the object is a view rather than a table, it stores no data of its own; it presents a stable, read-only projection of organization profile information that Marketing, Sales, and related modules can query without directly binding to the underlying TCA (Trading Community Architecture) table.

The view is reported as VALID in the ETRM metadata under both Oracle EBS 12.1.1 and 12.2.2. Its name follows the AMS naming convention for source views joined to marketing lists and campaign segmentation operations, where a "_V" suffix denotes a view used as a data source rather than a base entity.

Underlying Base Objects

The documented base object is HZ_ORGANIZATION_PROFILES, exposed to the APPS schema through a synonym. HZ_ORGANIZATION_PROFILES is the TCA table that stores organization-level profile attributes for parties of type organization. The view is defined as a direct, single-table projection over this object: the SELECT list references columns from the aliased table HOP (for HZ_ORGANIZATION_PROFILES) with no joins, unions, or subqueries. Consequently, row cardinality, key structure, and data types of the view are identical to those of the base table, and all profile columns are drawn from a single organization profile row identified by PARTY_ID.

Because the view is a simple pass-through projection, no data transformation, filtering, or denormalization is applied. Changes written to HZ_ORGANIZATION_PROFILES become visible through the view in the same session subject to normal read-consistency rules.

Key Columns

The view exposes a broad set of firmographic, credit, and ownership attributes used for business-to-business marketing and customer profiling. Notable columns include:

• PARTY_ID — primary identifier linking the profile to the TCA party record.
• CEO_NAME, CEO_TITLE, PRINCIPAL_NAME, PRINCIPAL_TITLE — key contact and officer attributes; PRINCIPAL_TITLE is the title of the organization's principal officer and is a frequently referenced attribute for lead qualification.
• ORGANIZATION_TYPE, CORPORATION_CLASS, LEGAL_STATUS, BUSINESS_SCOPE, YEAR_ESTABLISHED, INCORP_YEAR — firmographic classification and establishment data.
• SIC_CODE, SIC_CODE_TYPE, LINE_OF_BUSINESS, LOCAL_ACTIVITY_CODE, LOCAL_ACTIVITY_CODE_TYPE — industry and activity coding.
• EMPLOYEES_TOTAL, TOTAL_EMPLOYEES_TEXT, TOTAL_EMPLOYEES_IND, TOTAL_EMP_EST_IND, TOTAL_EMP_MIN_IND, EMP_AT_PRIMARY_ADR — sizing attributes and their estimation indicators.
• OWNERSHIP FLAGS: PUBLIC_PRIVATE_OWNERSHIP_FLAG, MINORITY_OWNED_IND, MINORITY_OWNED_TYPE, WOMAN_OWNED_IND, DISADV_8A_IND, SMALL_BUS_IND, OOB_IND, IMPORT_IND, EXPORT_IND.
• Credit and risk columns such as CREDIT_SCORE, CREDIT_SCORE_CLASS, CREDIT_SCORE_NATL_PERCENTILE, CREDIT_SCORE_INCD_DEFAULT, CREDIT_SCORE_AGE, CREDIT_SCORE_DATE, FAILURE_SCORE, GLOBAL_FAILURE_SCORE, DB_RATING, PAYDEX_SCORE, MAXIMUM_CREDIT_RECOMMENDATION, and MAXIMUM_CREDIT_CURRENCY_CODE.
• Financial signals: CURR_FY_POTENTIAL_REVENUE, NEXT_FY_POTENTIAL_REVENUE, FISCAL_YEAREND_MONTH.
• DEBARMENT_IND, DEBARMENTS_COUNT, DEBARMENTS_DATE and ENQUIRY_DUNS for compliance and identification.

Common Use Cases and Queries

AMS_LT_ORG_PROFILES_V supports marketing list building, account segmentation, and profile enrichment in AMS workflows. The following queries illustrate typical access patterns.

• Retrieving officer information for a party:

SELECT party_id, principal_name, principal_title, ceo_name, ceo_title FROM apps.ams_lt_org_profiles_v WHERE party_id = :p_party_id;

• Identifying organizations by title or classification:

SELECT party_id, principal_title, organization_type, line_of_business FROM apps.ams_lt_org_profiles_v WHERE UPPER(principal_title) LIKE '%CFO%' AND organization_type = 'CORPORATION';

• Segmenting by credit and size for targeted campaigns:

SELECT party_id, credit_score_class, credit_score, employees_total FROM apps.ams_lt_org_profiles_v WHERE small_bus_ind = 'Y' AND credit_score_class IN ('A','B');

Because the view is unfiltered, tenants must apply their own WHERE predicates for performance and data security, and joins to TCA tables such as HZ_PARTIES (on PARTY_ID) are required to obtain organization names and addresses not carried in the profile projection.