Results for “event_source_code”

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

Overview

AMS_EVENT_MAPPING_V is a valid database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the AMS (Marketing) product family and, as its product description states, returns event mapping information. The view provides a convenient, denormalized projection of marketing import staging data in which positional staging columns (COL1 through COL175 and beyond) are surfaced under business-meaningful aliases such as EVENT_SOURCE_CODE, REGISTRATION_SOURCE_TYPE, and ATTENDANCE_FLAG.

Functionally, the view serves as a mapping layer between the generic, position-based structure of the AMS import interface tables and the semantic field names expected by downstream registration, event attendance, and marketing analytics reporting. Because the underlying staging tables store values in numbered generic columns, this view is the recommended access point for any reporting or integration logic that requires a stable column name. It is commonly used in attendance reconciliation, registration load monitoring, and marketing event effectiveness reporting.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects as synonyms:

• AMS_IMP_LIST_HEADERS_ALL (SYNONYM) — the import list header that groups a batch of imported registration records.
• AMS_IMP_SOURCE_LINES (SYNONYM) — the import source line table that holds each staged registration record.

The view text selects from the source line table (aliased S) and exposes its keys, audit columns, and load-status columns, then maps the generic COL1, COL2, COL3, and so on to descriptive aliases. For example, S.COL3 is exposed as ATTENDANCE_FLAG, S.COL175 as WAITLISTED_FLAG, S.COL4 as CANCELLATION_FLAG, and S.COL5 as CANCELLATION_REASON_CODE. The import header identifier (IMPORT_LIST_HEADER_ID) links each line back to AMS_IMP_LIST_HEADERS_ALL, allowing batch-level reporting to be joined across both base objects.

Key Columns

• IMPORT_SOURCE_LINE_ID — primary identifier for a staged registration line.
• IMPORT_LIST_HEADER_ID — foreign key to the import list header, enabling batch grouping.
• IMPORT_SUCCESSFUL_FLAG / LOAD_STATUS — indicate whether the line imported successfully and its processing state.
• EVENT_SOURCE_CODE (COL1) — source code identifying the originating event or campaign.
• REGISTRATION_SOURCE_TYPE (COL2) — classification of the registration source.
• ATTENDANCE_FLAG (COL3) — indicates whether the registrant attended; this is the column most relevant to the search term "attendance_flag". It is central to attendance tracking and no-show analysis.
• WAITLISTED_FLAG (COL175) — indicates whether the registrant was placed on a waitlist.
• CANCELLATION_FLAG (COL4) and CANCELLATION_REASON_CODE (COL5) — record cancellation status and reason.
• Regional and demographic attributes — REG_PARTY_ID, REG_PARTY_NAME, REG_FIRST_NAME, REG_LAST_NAME, REG_EMAIL_ADDRESS, REG_JOB_TITLE, REG_CITY, REG_COUNTRY, and similar columns carry the registrant profile for segmentation and analysis.

Common Use Cases and Queries

Typical scenarios include reconciling attendance outcomes after an event, auditing unsuccessful imports, and analyzing registration demographics by source. Because ATTENDANCE_FLAG is a direct staging alias, it is frequently filtered or aggregated in these queries.

Sample query — attendance summary by event source:

• SELECT EVENT_SOURCE_CODE, ATTENDANCE_FLAG, COUNT(*) FROM APPS.AMS_EVENT_MAPPING_V GROUP BY EVENT_SOURCE_CODE, ATTENDANCE_FLAG;

Sample query — failed or pending imports within a batch:

• SELECT IMPORT_LIST_HEADER_ID, IMPORT_SOURCE_LINE_ID, LOAD_STATUS, IMPORT_SUCCESSFUL_FLAG FROM APPS.AMS_EVENT_MAPPING_V WHERE IMPORT_SUCCESSFUL_FLAG = 'N';

Sample query — registrant attendance with contact details:

• SELECT REG_PARTY_NAME, REG_EMAIL_ADDRESS, ATTENDANCE_FLAG, CANCELLATION_FLAG FROM APPS.AMS_EVENT_MAPPING_V WHERE ATTENDANCE_FLAG = 'Y';

Note that AMS_EVENT_MAPPING_V is a read-only reporting view over the staging interface; it does not enforce referential integrity and reflects the raw staged state of the import tables, so production interface processing should always be validated against the post-import marketing entities.