Results for “event_food_available_flag”

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

Overview

AS_PROMOTIONS_ALL is a Sales Foundation table owned by the OSM schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It defines promotions, campaigns, mail blitzes, call blitzes, and events at the transaction level, acting as the central header table for the Sales Foundation promotional subsystem. Each row captures a single promotional object together with its cost, reach, collateral, and event scheduling attributes.

A data vault classification heuristic mined from the foreign key structure identifies this table as a hub. Modelers should treat it as a hub because it holds a surrogate primary key (PROMOTION_ID) plus natural business keys (CODE, ORG_ID), while descriptive and transactional attributes could be separated into satellites. This is a modeling suggestion, not a physical fact.

Key Information Stored

The table contains 97 documented columns. The most significant are:

• PROMOTION_ID — the surrogate primary key (index AS_PROMOTIONS_PK); also appears in unique index AS_PROMOTIONS_U1.
• CODE and ORG_ID — the composite business key enforced by unique index AS_PROMOTIONS_U2.
• NAME, TYPE, STATUS, and ENABLED_FLAG — describe identity, categorization, and lifecycle state of the promotion; TYPE and NAME form the AS_PROMOTIONS_UK2 unique constraint.
• CURRENCY_CODE — the currency of promotion cost fields; foreign key to FND_CURRENCIES.
• EXPECTED_PROMOTION_COST, EXPECTED_NUM_OF_RESPONSES, EXPECTED_REACH — planning metrics.
• ACTUAL_PROMOTION_COST, ACTUAL_NUM_OF_RESPONSES — post-execution actuals for comparison reporting.
• EVENT_NAME_ID, EVENT_FACILITY_ID, EVENT_FAC_ROOM_ID, EVENT_FAC_STAFF_ID — event-planning attribution, linking to event name, facility, room, and staff definitions.
• EVENT_START_DATE, EVENT_END_DATE, CALL_START_DATE, CALL_END_DATE, AD_RUN_DATE_START, AD_RUN_DATE_END — scheduling windows for events, calls, and advertising.
• COLLATERAL_INVENTORY_ITEM_ID and COLLATERAL_ORGANIZATION_ID — the inventory item and organization supplying collateral.
• OWNER_PERSON_ID and ASSIGN_PERSON_ID — owner and assignee of the promotion.
• The ATTRIBUTE1 through ATTRIBUTE15 flexfield columns, plus ATTRIBUTE_CATEGORY, and the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE).

Common Use Cases and Queries

Because the table stores header-level promotion data, it commonly drives promotion status reports, budget versus actual cost analysis, event calendars, and collateral fulfillment.

A simple lookup by business key:

• SELECT promotion_id, name, status, event_start_date FROM as_promotions_all WHERE code = :code AND org_id = :org_id;

Cost-versus-response analysis by status:

• SELECT status, SUM(expected_promotion_cost) expected_cost, SUM(actual_promotion_cost) actual_cost, SUM(expected_num_of_responses) expected_responses, SUM(actual_num_of_responses) actual_responses FROM as_promotions_all WHERE org_id = :org_id GROUP BY status;

Event scheduling window:

• SELECT promotion_id, name, event_start_date, event_end_date FROM as_promotions_all WHERE event_start_date BETWEEN :from_date AND :to_date ORDER BY event_start_date;

Because the table is a hub, reporting queries frequently join satellites and links, such as AS_PROMOTION_SCRIPTS for scripting and AS_EVENT_ENROLLMENTS_ALL for enrollment counts.

Related Objects

The table participates in a dense relational graph. Significant related objects include:

• AS_EVENT_ENROLLMENTS_ALL — joined on EVENT_ID or SOURCE_PROMOTION_ID to PROMOTION_ID; tracks event attendees.
• AS_PROMOTION_SCRIPTS — joined on SCRIPT_ID and PROMOTION_ID; holds scripts associated with the promotion or event.
• AS_COLLATERAL_REQ_ALL — references the promotion through LIST_ID, MAIL_BLITZ_ID, and LETTER_ID.
• AS_COLLATERAL_CAT_ALL — joined on PROMOTION_ID to categorize collateral.
• AS_PROMOTION_RELATIONSHIPS — links promotions via PARENT_PROMOTION_ID and CHILD_PROMOTION_ID.
• AS_EVENT_FACILITIES_ALL, AS_EVENT_FAC_ROOMS, AS_EVENT_FAC_STAFF, and AS_EVENT_NAMES_ALL — referenced through the event-related foreign keys.
• FND_CURRENCIES and MTL_SYSTEM_ITEMS_B — validation lookups through CURRENCY_CODE and COLLATERAL_INVENTORY_ITEM_ID.
• AS_LIST_ENTRIES, AS_SCRIPT_QUESTIONS, AS_SCRIPT_ANSWER_ACTIONS_ALL, and AS_SCRIPT_PRE_DEFINED_ANSWERS — depend on the promotion or script identifiers for list and question management.