Results for “as_promotions”

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

Overview

The AS_PROMOTIONS view is a multi-org reporting object within the Oracle E-Business Suite AS – Sales Foundation product family. It exposes promotion master data maintained through the Sales Foundation promotions functionality, which supports marketing and sales promotion planning, budgeting, collateral management, event coordination, and call/mail blitz execution. The view is a filtered and organization-aware presentation of the underlying promotions data, restricting and standardizing columns so that downstream reports, concurrent programs, and integration interfaces can query promotions without directly accessing the base table.

Its multi-org designation is significant. The defining predicate applies an ORG_ID filter (typically NVL(ORG_ID, ...) as shown in the view text), which means the result set is scoped to the operating unit or organization context of the session. Consequently, the view behaves as an operational reporting and integration surface rather than a global administrative listing.

Underlying Base Objects

Per the ETRM metadata, no base objects are separately documented for this view. The view text itself, however, establishes a direct dependency on AS_PROMOTIONS_ALL, the underlying multi-org base table that stores all organizations’ promotion records. Every column projected by AS_PROMOTIONS is drawn from AS_PROMOTIONS_ALL; the view adds the ORG_ID predicate and exposes the resulting rows as the organization-scoped promotion set.

Because the sourcing table is an _ALL table, it contains promotions across all operating units, and the view’s ORG_ID filter is what isolates the relevant organization. The metadata notes that the view is “Not implemented in this database,” indicating that in some environments or documentation sets the object exists as a definition but is not instantiated for direct use.

Key Columns

The view exposes an extensive promotion attribute set. Identity and audit columns include PROMOTION_ID (primary identifier), CODE, NAME, and the standard WHO columns (LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and so on).

Organizational and status attributes include ORG_ID, ENABLED_FLAG, STATUS, COUNTRY, LANGUAGE, CURRENCY_CODE, PUBLIC_FLAG, PRIORITY, and owner/assignee references (OWNER_PERSON_ID, ASSIGN_PERSON_ID).

Financial and response measures include EXPECTED_PROMOTION_COST, ACTUAL_PROMOTION_COST, EXPECTED_NUM_OF_RESPONSES, ACTUAL_NUM_OF_RESPONSES, and EXPECTED_REACH. Advertising and collateral attributes include AD_RUN_DATE_START, AD_RUN_DATE_END, AD_AGENCY_NAME, AD_MEDIA_TYPE, and the COLLATERAL_* group.

Event columns are directly relevant to the user’s search term. The event group includes EVENT_NAME_ID, EVENT_START_DATE, EVENT_START_TIME, EVENT_END_DATE, EVENT_END_TIME, EVENT_REG_TIME, EVENT_ENROLLMENT_FEE, EVENT_MAX_ATTENDEES, and EVENT_NUM_REGISTERED. EVENT_END_DATE supplies the calendar date on which a promotional event concludes, complementing EVENT_END_TIME for precise scheduling.

Common Use Cases and Queries

The most common usage is reporting on promotions and their scheduled events within a single operating unit. For example, to identify events ending in a period:

• SELECT promotion_id, name, event_start_date, event_end_date FROM as_promotions WHERE event_end_date BETWEEN :p_start AND :p_end ORDER BY event_end_date;
• SELECT promotion_id, code, name, actual_promotion_cost, expected_promotion_cost FROM as_promotions WHERE enabled_flag = 'Y';
• SELECT promotion_id, name, event_end_date, event_num_registered, event_max_atteNdees FROM as_promotions WHERE event_end_date >= SYSDATE;

Additional scenarios include budget-versus-actual cost analysis, collateral availability checks, and integration extracts feeding external marketing systems. Because ORG_ID filtering is applied by the view, reports inherit the session’s organization context; users requiring cross-organization data must query AS_PROMOTIONS_ALL directly or run the view with the appropriate multi-org initialization.