Search Results using_object_type_meaning




Overview
Explore in AI Chat

Overview

APPS.AMS_ACT_CAMPAIGNS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It is registered in Oracle's ETRM (E-Business Suite Technical Reference Manual) with FND Design Data identifier AMS.AMS_ACT_CAMPAIGNS_V and holds a status of VALID. The view belongs to the Oracle Marketing (AMS) product family and presents campaign information joined to the general object-association model used throughout the Marketing and Trade Management modules.

Rather than exposing a single base table, the view consolidates campaign header attributes supplied by the AMS_CAMPAIGNS_V view with association rows stored in AMS_OBJECT_ASSOCIATIONS, resolving lookup meanings through AMS_LOOKUPS. This design allows reporting and integration consumers to retrieve a campaign together with the objects that reference or are referenced by it in a single query. The object is flagged "Oracle Internal Use Only" in ETRM; Oracle Corporation does not support direct access to this data except from standard Oracle Applications programs, so any external use should be treated as an unsupported extension.

Underlying Base Objects

The ETRM dependency listing documents the following referenced objects:

  • AMS_CAMPAIGNS_V (VIEW) — supplies the campaign header attributes, including campaign identifier, name, purpose, owner, and the start and end dates.
  • AMS_LOOKUPS (VIEW) — provides the meaning values exposed by the USAGE_TYPE_MEANING, MASTER_OBJECT_TYPE_MEANING, USING_OBJECT_TYPE_MEANING, and CAMPAIGN_PURPOSE columns, translating stored lookup codes into user-facing descriptions.
  • AMS_OBJECT_ASSOCIATIONS (SYNONYM) — the association model that links a master object to a using object; the view surfaces each association row together with its campaign context.
  • AMS_UTILITY_PVT (PACKAGE) — a Marketing utility package invoked by the view definition, typically for lookup resolution and type-conversion logic embedded in the view SQL.

ETRM records that AMS_ACT_CAMPAIGNS_V is not referenced by any other database object, so it is a leaf-level reporting view rather than a building block for further definitions.

Key Columns

  • OBJECT_ASSOCIATION_ID — unique identifier of the underlying association record.
  • USAGE_TYPE / USAGE_TYPE_MEANING — the usage classification of the association and its decoded display value (30 and 80 characters respectively).
  • MASTER_OBJECT_ID / MASTER_OBJECT_TYPE / MASTER_OBJECT_TYPE_MEANING — the owning side of the association and its decoded type.
  • USING_OBJECT_ID / USING_OBJECT_TYPE / USING_OBJECT_TYPE_MEANING — the referencing side of the association and its decoded type.
  • CAMPAIGN_ID / CAMPAIGN_NAME — the campaign identifier and its descriptive name (up to 240 characters).
  • CAMPAIGN_PURPOSE_CODE / CAMPAIGN_PURPOSE — the campaign purpose lookup code (the column targeted by the search term "campaign_purpose_code") and the decoded purpose text (up to 4000 characters).
  • CAMPAIGN_OWNER — the owner of the campaign, stored as a numeric identifier (typically referencing a resource or user).
  • CAMPAIGN_START_DATE / CAMPAIGN_END_DATE — the effective date range of the campaign.
  • OBJECT_VERSION_NUMBER — optimistic locking / concurrency control column maintained by the Marketing framework.

Common Use Cases and Queries

A typical requirement is to report campaigns together with the objects associated to them, filtered by campaign purpose. For example:

  • Filter by purpose code:

    SELECT campaign_id, campaign_name, campaign_purpose_code,
       campaign_purpose, campaign_start_date, campaign_end_date
FROM   apps.ams_act_campaigns_v
WHERE  campaign_purpose_code = '&purpose_code';

  • List associations for a specific campaign:

    SELECT object_association_id, usage_type_meaning,
       master_object_type_meaning, using_object_type_meaning
FROM   apps.ams_act_campaigns_v
WHERE  campaign_id = :campaign_id;

  • Report active campaigns by date range:

    SELECT campaign_id, campaign_name, campaign_owner
FROM   apps.ams_act_campaigns_v
WHERE  TRUNC(SYSDATE) BETWEEN campaign_start_date AND campaign_end_date;

Because the view is documented as Oracle Internal Use Only and is not referenced by other database objects, consumers should prefer supported Marketing APIs or concurrent programs for production integration, reserving direct queries for controlled reporting scenarios.