Results for “display_program”

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

Overview

AMS_IBA_POSTINGS_B is the base (non-translated) table in the Oracle E-Business Suite Marketing (AMS) module that stores definitional information for iStore/iMarketing postings. A "posting" represents an online advertising or content placement, such as a banner, promotional block, or sponsored tile, that is presented to a customer or affiliate within a Web store or campaign. The table holds the descriptive, scheduling, presentation, and billing attributes needed to render a posting and to account for impressions and chargebacks.

The table is owned by the AMS schema, has a documented status of VALID, and contains 42 columns in the 12.2.2 physical schema. It is the parent of a translated table, AMS_IBA_POSTINGS_TL, which carries the language-specific text for the same POSTING_ID. From a Data Vault modeling perspective, the mined foreign-key structure classifies this object as hub-leaning: POSTING_ID behaves as a durable business key around which descriptive satellites and relationships (for example, campaign associations) are organized. This classification is a heuristic suggestion, not a product-supplied designation; the table itself is a normal, third-normal-form OLTP structure.

Key Information Stored

The primary key is POSTING_ID, enforced by the unique index AMS_IBA_POSTINGS_B U1 and the constraint AMS_IBA_POSTINGS_B_PK. POSTING_ID is the surrogate key that links the base table to its translation table and to the campaign-posting relationship. Notable columns include:

• POSTING_ID — surrogate primary key and business-key candidate; joins to AMS_IBA_POSTINGS_TL and AMS_IBA_CAMP_POSTINGS.
• POSTING_TYPE and CAMPAIGN_TYPE — classify the posting and the associated campaign context.
• AVAILABLE_ON_OBJECT_TYPE and AVAILABLE_ON_OBJECT_ID — identify the host object (for example, a store or section) on which the posting may appear.
• DISPLAY_RULE_ID — foreign key to AMS_IBA_DISPLAY_RULES, governing how and when the posting is rendered.
• EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — define the posting's active scheduling window.
• IMPRESSION_COUNT and MAX_IMPRESSION_COUNT — track realized and permitted impression volume.
• CHARGEBACK_AMOUNT, CHARGEBACK_AMOUNT_CURR_CODE, and CHARGEBACK_UOM — billing basis for the posting.
• PRESENTATION_URL, CONTENT_SITE, DISPLAY_PROGRAM, and AFFILIATE_STYLE_SHEET — presentation targets and styling.
• POSTING_WIDTH and POSTING_HEIGHT — physical dimensions of the rendered posting.
• ORG_ID, ENABLED_FLAG, STATUS_CODE, and SECURITY_GROUP_ID — multi-org, activation, lifecycle, and access control attributes.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS.
• SEGMENT_OVERRIDE_FLAG and MAX_CAMPAIGNS — targeting and eligibility controls.

Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) and program columns (PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) are also present for concurrency control and diagnostics.

Common Use Cases and Queries

Typical scenarios include reporting on active postings, auditing impression utilization, reconciling chargebacks, and troubleshooting why a posting does not appear.

SELECT p.posting_id, t.posting_name, p.status_code,
       p.effective_start_date, p.effective_end_date,
       p.impression_count, p.max_impression_count
FROM   ams.ams_iba_postings_b p,
       ams.ams_iba_postings_tl t
WHERE  p.posting_id = t.posting_id
AND    t.language = USERENV('LANG')
AND    p.enabled_flag = 'Y'
AND    sysdate BETWEEN p.effective_start_date AND p.effective_end_date;

A second common pattern joins campaign associations to determine which postings belong to which campaign:

SELECT c.campaign_id, p.posting_id, p.posting_type
FROM   ams.ams_iba_postings_b p,
       ams.ams_iba_camp_postings c
WHERE  p.posting_id = c.posting_id;

Related Objects

• AMS_IBA_POSTINGS_TL — translated table joined on POSTING_ID; supplies language-specific posting text.
• AMS_IBA_CAMP_POSTINGS — associates postings with campaigns via POSTING_ID.
• AMS_IBA_DISPLAY_RULES — referenced through DISPLAY_RULE_ID.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID.

These relationships define the core posting model: a base definition, its translations, its campaign assignments, and the display and security rules that control its use.