Results for “wf_item_id”

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

Overview

AMS_TCOP_REQUESTS is a table in the AMS (Marketing) schema of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It stores requests that need to be scheduled so that fatigue rules can be applied to outbound marketing activities. In the Oracle Marketing (OAM) and TeleSales/Collections context, "TCOP" relates to the treatment and control of outbound communications, and this table acts as the transactional register of scheduling requests that drive fatigue-rule enforcement — that is, rules that limit how frequently a given customer or contact may be targeted within a defined period.

Under a heuristic Data Vault classification mined from its foreign-key structure, this object is satellite-leaning. It is modeled as a descriptive satellite attached to a scheduling parent (AMS_CAMPAIGN_SCHEDULES_B), carrying attributes about each request (dates, status, workflow linkage) rather than serving as a pure hub of business keys or a link between multiple hubs. This classification should be treated as a modeling suggestion rather than a normative EBS definition.

Key Information Stored

The table documents 13 columns. The most significant are summarized below.

• REQUEST_ID — The surrogate primary key, enforced by index AMS_TCOP_REQUESTS_PK and also by unique index AMS_TCOP_REQUESTS_U1. This is the value commonly sought under the alias key name "ams_tcop_requests_pk".
• SCHEDULE_ID — Foreign key to AMS_CAMPAIGN_SCHEDULES_B and the column behind unique index AMS_TCOP_REQUESTS_U2. It ties the request to the campaign schedule to which fatigue rules are to be applied, making it the primary business-key candidate alongside REQUEST_ID.
• REQUEST_DATE — The date on which the scheduling request was raised.
• STATUS — The processing state of the request (for example, pending, processed, or completed).
• COMPLETION_DATE — The date the request finished processing.
• WF_ITEM_TYPE and WF_ITEM_ID — The workflow item type and identifier linking the request to an Oracle Workflow process instance; WF_ITEM_ID references GML_BATCH_SO_WORKFLOW.
• SECURITY_GROUP_ID — The operating-unit/security grouping column, foreign key to FND_SECURITY_GROUPS, used to partition data visibility.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit ("WHO") columns recording insert and update accountability.

Common Use Cases and Queries

Typical scenarios include monitoring outstanding fatigue-rule scheduling requests, reconciling completed requests against the campaigns they serve, and diagnosing workflow failures. A frequent lookup resolves a request by its primary key:

• SELECT request_id, schedule_id, status, request_date FROM ams.ams_tcop_requests WHERE request_id = :p_request_id;
• Reporting requests by status and date range: SELECT status, COUNT(*) FROM ams.ams_tcop_requests WHERE request_date BETWEEN :from_date AND :to_date GROUP BY status;
• Joining to the schedule parent to enrich reporting: SELECT r.request_id, s.* FROM ams.ams_tcop_requests r JOIN ams.ams_campaign_schedules_b s ON s.schedule_id = r.schedule_id;
• Identifying stalled workflow-linked requests using WF_ITEM_ID and STATUS for operational troubleshooting.

Because SECURITY_GROUP_ID governs visibility, reports should honor the caller's security profile.

Related Objects

• AMS_CAMPAIGN_SCHEDULES_B — Parent of AMS_TCOP_REQUESTS via SCHEDULE_ID; defines the campaign schedule to which fatigue rules apply.
• GML_BATCH_SO_WORKFLOW — Referenced by WF_ITEM_ID; carries the workflow execution associated with the request.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID; controls data security partition.
• AMS_TCOP_REQUESTS_PK / _U1 / _U2 — The primary and unique indexes that enforce request and schedule key integrity.
• Oracle Workflow (WF_ITEMS / WF_ITEM_ACTIVITY_STATUS) — Implied by WF_ITEM_TYPE and WF_ITEM_ID for process tracking.

Collectively, these relationships position AMS_TCOP_REQUESTS as the control point between campaign scheduling and workflow-driven fatigue-rule execution.