Search Results fund_source_name




Overview
Explore in AI Chat

Overview

APPS.AMS_EVENT_HEADERS_V is a reporting view in the Oracle E-Business Suite Marketing (AMS) module that exposes event header records at the "MAIN" event level. It consolidates core event attributes with decoded lookup meanings, user status names, and language descriptions, making it suitable for operational reporting, integration extracts, and ad hoc queries without requiring callers to join multiple lookup and status tables manually.

The view is defined with an event-level filter (EVH.EVENT_LEVEL='MAIN'), so only top-level events are returned; child or sub-events are excluded. This makes the view a convenient single source for event master data used in marketing calendars, registration reporting, and financial tracking against events.

Underlying Base Objects

The view is defined over four documented base objects:

The joins to lookups, user statuses, and languages are inner or outer joins as shown, with outer joins applied where codes may be null (lookups and language). The inner join to AMS_USER_STATUSES_VL requires a valid USER_STATUS_ID for each returned row.

Key Columns

Identity and descriptive columns include ROW_ID, EVENT_HEADER_ID, EVENT_HEADER_NAME, EVENT_MKTG_MESSAGE, DESCRIPTION, and OBJECT_VERSION_NUMBER. Audit columns include CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Classification columns include EVENT_LEVEL, APPLICATION_ID, EVENT_TYPE_CODE with the decoded EVENT_TYPE, ACTIVE_FLAG, PRIVATE_FLAG, GLOBAL_FLAG, EVENT_STANDALONE_FLAG, and SOURCE_CODE. Status handling is represented by USER_STATUS_ID, its decoded NAME, SYSTEM_STATUS_CODE, and LAST_STATUS_DATE.

In response to the search term "fund_source_name," note that the view exposes FUND_SOURCE_TYPE_CODE, FUND_SOURCE_ID, and an aliased column producing FUND_SOURCE_NAME — defined in the view text as EVH.FUND_SOURCE_TYPE_CODE FUND_SOURCE_NAME. Importantly, this alias returns the fund source type code value, not a decoded descriptive name from a lookup join. Related funding columns include FUND_AMOUNT_TC, FUND_AMOUNT_FC, CURRENCY_CODE_TC, and CURRENCY_CODE_FC.

Scheduling and logistics columns include DAY_OF_EVENT, AGENDA_START_TIME, AGENDA_END_TIME, DURATION, DURATION_UOM_CODE, ACTIVE_FROM_DATE, and ACTIVE_TO_DATE. Registration columns include REG_REQUIRED_FLAG, REG_INVITED_ONLY_FLAG, REG_MAXIMUM_CAPACITY, REG_MINIMUM_CAPACITY, REG_CHARGE_FLAG, and REG_INVITED_ONLY_FLAG. Financial and organizational columns include FORECASTED_REVENUE, ACTUAL_REVENUE, FORECASTED_COST, ACTUAL_COST, ORGANIZATION_ID, INVENTORY_ITEM_ID, COUNTRY_CODE, and BUSINESS_UNIT_ID.

Common Use Cases and Queries

Typical uses include listing active main events, reconciling event funding, and feeding event data into downstream analytics. A simple listing query follows:

  • SELECT event_header_id, event_header_name, event_type, name AS status, fund_source_name, fund_amount_tc FROM apps.ams_event_headers_v WHERE active_flag = 'Y';
  • SELECT event_header_name, fund_source_id, fund_source_name, fund_amount_tc, currency_code_tc FROM apps.ams_event_headers_v WHERE fund_source_id IS NOT NULL; — useful to inspect funding attribution.
  • SELECT event_header_name, nls_language, business_unit_id, forecasted_revenue, actual_revenue FROM apps.ams_event_headers_v WHERE start_period_name = :period; — period-based financial comparison.

When a decoded fund source description is required, join FUND_SOURCE_ID or FUND_SOURCE_TYPE_CODE to the appropriate lookup view, since FUND_SOURCE_NAME here carries the type code value. All queries should be schema-qualified with APPS and follow site security and MOAC policies via BUSINESS_UNIT_ID or ORGANIZATION_ID filters.