Search Results customer_key




Overview
Explore in AI Chat

Overview

APPS.AMS_TAR_ORGANIZATION_V is an Oracle E-Business Suite 12.1.1 / 12.2.2 view owned by the APPS schema that presents organization-based list entries from the Oracle Marketing (AMS) module in a denormalized, reporting-friendly shape. It is a "TAR" (Target Audience Registry) view: a presentation layer used by Oracle Marketing list management, list entry selection, and audience segmentation functionality. The view filters the underlying list entries stack so that only rows whose source system type equals the literal value AMS_ORGANIZATION are returned, meaning it exposes organization (party) records that have been enrolled onto marketing lists rather than persons, contacts, or other source objects.

Because it joins out to customer/party attributes such as DUNS number, fiscal code, SIC code, and tax identifiers, the view is commonly consumed for downstream reporting, data extraction, and integration into external campaign management or master data systems. The presence of LIST_ENTRY_SOURCE_SYSTEM_ID and related source system columns reflects the fact that organizations may originate from multiple source systems; the view itself is restricted to one organization source type and therefore does not enumerate cross-source deduplication.

Underlying Base Objects

The documented view definition references exactly one base object: the synonym AMS_LIST_ENTRIES. All columns projected by the view (with the exception of aliased customer attributes) are selected directly from AMS_LIST_ENTRIES, and no joins are visible in the documented view text. This is significant: the aliased columns such as COL1–COL6 and CUSTOMER_NAME are already resolved within AMS_LIST_ENTRIES (or its own underlying layer) as stored attribute columns rather than being joined at view-execution time.

  • AMS_LIST_ENTRIES — the sole documented base object, exposed via a synonym in the APPS schema.
  • The view applies a hard-coded predicate WHERE LIST_ENTRY_SOURCE_SYSTEM_TYPE = 'AMS_ORGANIZATION', so it is effectively a filtered projection.

Key Columns

Common Use Cases and Queries

Typical uses include auditing organization membership on marketing lists, extracting organization demographics for external systems, and verifying source system population. A representative query:

  • SELECT list_header_id, list_entry_id, party_id, organization_name, duns_number, list_entry_source_system_id, enabled_flag FROM apps.ams_tar_organization_v WHERE enabled_flag = 'Y';
  • Reporting by source system: group by LIST_ENTRY_SOURCE_SYSTEM_ID to reconcile organizations loaded from differing upstream systems.
  • Data quality checks on duplicate, random, and control-group flags before campaign execution.