Results for “coordinator_id”

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

Overview

AMS_AGENDAS_B is the base (non-translatable) table within the Oracle E-Business Suite Marketing (AMS) module that stores agenda information for events, including the tracks and sessions that compose an event program. It resides in the AMS schema and is marked VALID in the 12.1.1 / 12.2.2 data dictionary. The table holds 36 documented columns and is the master record for agenda scheduling, room assignment, and coordinator responsibility, while translated descriptive text is stored separately in AMS_AGENDAS_TL.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table carries a single surrogate primary key plus multiple outbound references to independent business entities such as parties, venues, offers, and setup types, which is characteristic of a descriptive satellite attached to core event/venue hubs rather than a standalone hub or a pure link.

Key Information Stored

• AGENDA_ID — Surrogate primary key, enforced by AMS_AGENDAS_B_PK and also defined by the unique index AMS_AGENDAS_B_U1. This is the business-key candidate used for all downstream joins.
• COORDINATOR_ID — References HZ_PARTIES; identifies the party responsible for the agenda item.
• PARENT_ID and PARENT_TYPE — Reference AMS_EVENT_OFFERS_ALL_B; establish parentage between an agenda and its owning offer or track.
• ROOM_ID — References AMS_VENUES_B; specifies the physical venue room for the session.
• SETUP_TYPE_ID — References AMS_SETUP_TYPES; defines the room setup configuration (theater, classroom, and similar).
• TIMEZONE_ID — References HZ_TIMEZONES; governs the interpretation of scheduled times.
• START_DATE_TIME and END_DATE_TIME — The scheduled start and end timestamps for the agenda item.
• AGENDA_TYPE — Classifies the record, distinguishing track-level from session-level agenda entries.
• ACTIVE_FLAG and DEFAULT_TRACK_FLAG — Status and default-track indicators controlling visibility and default selection behavior.
• SECURITY_GROUP_ID — References FND_SECURITY_GROUPS; enforces multi-org security and access partitioning.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Forms/ADF layer during concurrent updates.
• Standard WHO columns — LAST_UPDATE_DATE, CREATION_DATE, LAST_UPDATED_BY, CREATED_BY, LAST_UPDATE_LOGIN, and APPLICATION_ID provide audit and ownership tracking.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield (DFF) storage for customer-defined attributes.

The remaining columns follow standard EBS audit conventions. The translated short and long descriptions are maintained in AMS_AGENDAS_TL and joined on AGENDA_ID.

Common Use Cases and Queries

Agenda data is queried for event scheduling reports, room utilization analysis, and coordinator workload dashboards. A typical join retrieves the descriptive text alongside the base record:

SELECT b.agenda_id, t.name, b.start_date_time, b.end_date_time
FROM   ams.ams_agendas_b b,
       ams.ams_agendas_tl t
WHERE  b.agenda_id = t.agenda_id
AND    t.language = USERENV('LANG')
AND    b.active_flag = 'Y';

Room and setup reporting joins AMS_VENUES_B on ROOM_ID and AMS_SETUP_TYPES on SETUP_TYPE_ID to produce venue calendars. Coordinator roll-ups join HZ_PARTIES on COORDINATOR_ID. Hierarchy queries use the PARENT_ID / PARENT_TYPE pair against AMS_EVENT_OFFERS_ALL_B to walk track-to-session relationships. Security-filtered extracts must include SECURITY_GROUP_ID to respect MOAC partitioning.

Related Objects

• AMS_AGENDAS_TL — Translatable child table; joins on AMS_AGENDAS_TL.AGENDA_ID = AMS_AGENDAS_B.AGENDA_ID.
• HZ_PARTIES — Joined on COORDINATOR_ID to resolve the responsible party.
• AMS_EVENT_OFFERS_ALL_B — Joined on PARENT_ID to link the agenda to its offer or parent track.
• AMS_VENUES_B — Joined on ROOM_ID for venue and room information.
• AMS_SETUP_TYPES — Joined on SETUP_TYPE_ID for room setup definitions.
• HZ_TIMEZONES — Joined on TIMEZONE_ID to resolve scheduling time zones.
• FND_SECURITY_GROUPS — Joined on SECURITY_GROUP_ID for multi-org security filtering.

These relationships make AMS_AGENDAS_B a central integration point for event program management within the AMS Marketing module.