Results for “interest_theater_flag”

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

Overview

AMS_DM_PERINT_STG is a staging table owned by the AMS (Marketing) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a container for the interest and hobby attributes associated with a party (customer, prospect, or contact), and it supplies the interest-related detail rows that are later consolidated into AMS_DM_DRV_STG. The table is populated and consumed by the mining collection pack within Oracle Marketing's data mining and list-generation framework. As a staging object, its contents are transient by design: records are loaded, processed, and typically purged or refreshed during each mining run rather than retained as permanent master data.

The documented physical schema (ETRM 12.2.2) shows ten columns, with PARTY_ID serving as the single-column primary key (AMS_DM_PERINT_STG_PK). The metadata classifies the object heuristically as standalone under Data Vault modeling conventions, meaning no foreign key relationships were mined from the schema. This suggests that, if modeled in a Data Vault warehouse, the table would most naturally be treated as a satellite keyed to a party hub rather than as a link or independent hub, since its payload is descriptive interest flags attached to a single business entity.

Key Information Stored

The table is narrow and flag-oriented. The most significant columns are:

• PARTY_ID — The primary key and the business-key candidate. It identifies the party whose interests are being staged. Because it is the sole column of AMS_DM_PERINT_STG_PK, each party appears at most once per staging cycle.
• INTEREST_ART_FLAG — Indicates a demonstrated or declared interest in art.
• INTEREST_BOOKS_FLAG — Indicates interest in books or reading.
• INTEREST_MOVIES_FLAG — Indicates interest in movies or film.
• INTEREST_MUSIC_FLAG — Indicates interest in music.
• INTEREST_THEATER_FLAG — Indicates interest in theater or performing arts.
• INTEREST_TRAVEL_FLAG — Indicates interest in travel.
• INTEREST_DRINK_FLAG — Indicates interest in beverages or drinking-related activity.
• INTEREST_SMOKE_FLAG — Indicates smoking-related interest or preference.
• INTEREST_OTHER_FLAG — Captures miscellaneous interests not covered by the specific category flags.

There is no documented surrogate key beyond PARTY_ID; the interest flags act as descriptive payload rather than as identifiers. Consequently, the table behaves as a party-keyed attribute set rather than a transactional or historical record.

Common Use Cases and Queries

The primary use case is audience segmentation. Marketers combine these interest flags with the driver staging table to build targeted lists. A typical query might count parties by interest:

• Segment extraction: SELECT party_id FROM ams_dm_perint_stg WHERE interest_music_flag = 'Y' AND interest_travel_flag = 'Y';
• Aggregate profiling: SELECT COUNT(*) FROM ams_dm_perint_stg WHERE interest_books_flag = 'Y';
• Join to drivers: SELECT d.party_id, p.interest_movies_flag FROM ams_dm_drv_stg d JOIN ams_dm_perint_stg p ON d.party_id = p.party_id;

Reporting use cases include campaign response analysis, list quality assessment, and pre-mining data validation. Because the table is a staging object, queries should account for the possibility of partial or stale loads.

Related Objects

• AMS_DM_DRV_STG — The principal dependent staging table; it references the interest detail rows contained here, joined on PARTY_ID.
• AMS_DM_PERINT_STG_PK — The primary key constraint enforcing uniqueness on PARTY_ID.
• HZ_PARTIES — The party master table supplying the PARTY_ID values staged here.
• HZ_CUST_ACCOUNTS — Customer account records linked through the party model for downstream segmentation.
• Mining collection pack concurrent programs — The AMS processes that load, transform, and purge this staging table.

Because no foreign keys were documented, referential integrity to these objects is maintained procedurally by the mining collection pack rather than by database constraints.