Search Results ams_media_type




Overview
Explore in AI Chat

Overview

APPS.AMS_CUSTOM_SETUP_SCR_V is an Oracle E-Business Suite view in the Advanced Marketing (AMS) product family. It consolidates descriptive attributes of custom setups — the configurable objects used within campaign, event, and media execution — and enriches them with decoded lookup meanings and media names. The view sits in the reporting and integration layer rather than the transaction layer: it performs no data manipulation, exposes no DML capability, and serves primarily as a denormalized read model for forms, concurrent programs, and custom reports.

The suffix _SCR_V indicates a screen-oriented view, meaning it was designed to feed a specific AMS setup screen or its supporting LOV/validation logic, but it is equally usable as a standalone query surface. Its central reporting value is that it resolves three code columns — OBJECT_TYPE, ACTIVITY_TYPE_CODE, and MEDIA_ID — into human-readable values, sparing report authors from writing their own lookup joins. In 12.1.1 and 12.2.2 the object resides in the APPS schema and follows standard EBS view conventions: WHO audit columns are carried through, and multilingual meaning resolution is delegated to the underlying VL views.

Underlying Base Objects

The view is defined over three documented objects: AMS_CUSTOM_SETUPS_VL, AMS_LOOKUPS (referenced twice), and AMS_MEDIA_VL. All three are themselves views, not base tables, so the effective query depth is greater than the object list suggests.

  • AMS_CUSTOM_SETUPS_VL — the driving object, supplying the custom setup rows together with creation, audit, and versioning attributes. The VL suffix indicates a translated view, exposing language-specific name and description columns.
  • AMS_LOOKUPS (alias B) — joined on LOOKUP_TYPE = 'AMS_SYS_ARC_QUALIFIER' against OBJECT_TYPE. This is an inner join, so a custom setup appears only when its object type matches a valid, enabled lookup code in that set.
  • AMS_MEDIA_VL (alias C) — outer-joined on MEDIA_ID, supplying MEDIA_NAME. The (+) operator preserves setups that carry no media reference.
  • AMS_LOOKUPS (alias D) — a second, independent reference to AMS_LOOKUPS, outer-joined on LOOKUP_TYPE (+) = 'AMS_MEDIA_TYPE' against ACTIVITY_TYPE_CODE. This decodes the activity type as a media type classification.

Key Columns

  • CUSTOM_SETUP_ID — primary identifier for the custom setup record.
  • SETUP_NAME, DESCRIPTION — translated descriptive fields from AMS_CUSTOM_SETUPS_VL.
  • OBJECT_TYPE and B.MEANING — the raw setup object type and its decoded meaning from the AMS_SYS_ARC_QUALIFIER lookup set. These two columns are always populated together given the inner join.
  • ACTIVITY_TYPE_CODE and D.MEANING — the activity classification and its decoded AMS_MEDIA_TYPE meaning. Both are nullable because of the outer join.
  • MEDIA_ID / MEDIA_NAME — the associated media record and its translated name; both are nullable for setups with no media.
  • ENABLED_FLAG — indicates whether the setup is active and selectable.
  • ALLOW_ESSENTIAL_GROUPING — controls whether essential grouping is permitted for the setup.
  • SOURCE_CODE_SUFFIX — source qualification suffix, used in code generation and matching logic.
  • OBJECT_VERSION_NUMBER — optimistic locking value maintained by the AMS framework.
  • APPLICATION_ID — owning application discriminator.
  • CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

The most frequent use is a filtered listing of active custom setups for a given media type, which is the pattern implied by a search on ams_media_type:

SELECT custom_setup_id, setup_name, object_type, meaning,
       activity_type_code, media_id, media_name
FROM   apps.ams_custom_setup_scr_v
WHERE  enabled_flag = 'Y'
AND    meaning IS NOT NULL;

A second common pattern retrieves the decoded classifications for a single setup, useful when validating configuration during implementation:

SELECT setup_name, object_type, b_meaning, activity_type_code,
       media_name, source_code_suffix, object_version_number
FROM   apps.ams_custom_setup_scr_v
WHERE  custom_setup_id = :p_custom_setup_id;

A third pattern inventories media coverage, identifying setups that reference no media:

SELECT media_name, COUNT(*) setup_count
FROM   apps.ams_custom_setup_scr_v
GROUP  BY media_name
ORDER  BY setup_count DESC;

Because the view decodes classifications inline, it is well suited to ad hoc analysis, ETL extraction, and Oracle Reports or XML Publisher data templates. Queries should always qualify the view with the APPS schema and respect operating unit or application security only where the calling program requires it, since the view itself carries no security predicates.