Results for “ams_tcop_preview”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
AMS_TCOP_PREVIEW is an Oracle Marketing (AMS) package body owned by the APPS schema that supports the "Traffic Cop" preview and fatigue-checking engine within Oracle E-Business Suite. Traffic Cop is the component of the Advanced Marketing / campaign management module that evaluates prospective campaign audience lists against contact-policy and fatigue rules before a campaign schedule is executed. The package allows marketers to simulate the result of a schedule run — determining which contacts would actually be selected, which would be suppressed by global or channel-level contact limits, and how many days or periods must elapse before a party may be contacted again — without committing the actual schedule execution.
The package body declares a large set of global variables and nested-table types used to cache intermediate preview state in memory, including party lists, fatigue-by-party and fatigue-by-schedule lists, preview start and end dates, global and channel maximum-contact counters, and global and channel no-of-days values. It also exposes an FND_LOG-based debug logging utility (write_debug_message) gated by runtime log level, which is consistent with the diagnostic instrumentation typical of AMS scheduling code delivered in EBS 12.1.1 and 12.2.2. The header comment identifies the source revision as amsvtcpb.pls 120.14, indicating a long-maintained component of the marketing scheduling stack.
The package is classified as API classification OTHER, and it is referenced by zero other packages in the documented metadata, confirming it is a top-level utility rather than a shared library.
Key Procedures and Functions
- REFRESH — Recomputes or repopulates the preview contact and fatigue results for the current preview request, reading the traffic-cop rule setup and schedule context and writing refreshed preview rows.
- FORCE_REFRESH — Performs the same recomputation as REFRESH but bypasses any caching or short-circuit logic, forcing a full regeneration of preview data even where results may already exist.
- PREVIEW_FATIGUE — Evaluates fatigue rules for the preview population, determining which parties are suppressed because they have been contacted too recently under global or channel-level contact limits and no-of-days thresholds.
- REGENERATE_PREVIEW — Rebuilds the complete preview result set for a preview request, coordinating contact selection and fatigue evaluation.
- REGENERATE_PREVIEW_DAYS — Regenerates the preview for a specific date or day range within the preview window, supporting day-by-day reconciliation of the projected schedule.
Tables Accessed
The package works primarily against the AMS_TCOP_PRVW_* tables, which hold its own output: AMS_TCOP_PRVW_CONTACTS and its _S sequence-backed counterpart store previewed contacts; AMS_TCOP_PRVW_FATIGUE and AMS_TCOP_PRVW_FATIGUE_S store fatigue evaluation results; and AMS_TCOP_PRVW_FTG_BY, AMS_TCOP_PRVW_FTG_BY_S, and AMS_TCOP_PRVW_FTG_DTLS hold fatigue-by-party/schedule breakdowns and detail lines. Configuration and input data are read from AMS_TCOP_FR_PERIODS_B and AMS_TCOP_FR_RULES_SETUP (fatigue rule periods and rule setup), AMS_TCOP_CONTACTS (actual contact history used as the fatigue baseline), AMS_CAMPAIGN_SCHEDULES_B, AMS_ACT_LISTS, AMS_LIST_HEADERS_ALL, and AMS_LIST_ENTRIES (schedule, activity list, and list membership). WF_EVENT_T is referenced for workflow event integration. All access is via APPS synonyms.
Usage Notes
AMS_TCOP_PREVIEW is invoked internally by the marketing scheduling and Traffic Cop preview flows — typically from the campaign schedule preview UI in Oracle Marketing and from the concurrent programs that execute preview and regeneration processing. It is not a general-purpose public API and is not referenced by other PL/SQL packages. Customizations should avoid calling it directly; instead, use the supported schedule preview functionality, and treat the AMS_TCOP_PRVW_* tables as transient preview output. Debug output can be enabled through FND_LOG runtime level settings.
-
SYNONYM: APPS.AMS_ACT_LISTS 12.1.1
-
SYNONYM: APPS.AMS_ACT_LISTS 12.2.2
-
12.1.1 DBA Data 12.1.1
-
SYNONYM: APPS.WF_EVENT_T 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
TYPE: APPS.WF_EVENT_T 12.1.1
-
VIEW: APPS.AMS_CAMPAIGNS_VL 12.1.1
-
VIEW: APPS.AMS_CAMPAIGNS_VL 12.2.2