Results for “activity_resource_id”

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

Overview

AMS_ACT_RESOURCES is a Marketing (AMS) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, owned by the AMS schema. It stores the business parties associated with a specific marketing activity, such as an event, seminar, or campaign offer. In practice, the table acts as the assignment and participation repository that links an activity or event to the resources — typically parties, contacts, or roles — that are used by, or otherwise engaged with, that activity. Each row represents one activity-resource association, capturing the resource identity, the source of the usage relationship, and the role semantics through which the resource participates.

Heuristic Data Vault classification mined from the foreign key structure identifies this object as a link. This is consistent with its design: it sits between the marketing activity/event entities and the resource and status entities, resolving many-to-many relationships rather than acting as a durable descriptive hub or a slowly changing satellite. As a modeling suggestion, AMS_ACT_RESOURCES serves as a junction table with transactional and effectiveness-dated attributes attached.

Key Information Stored

The table contains 34 documented columns. The most significant are:

• ACTIVITY_RESOURCE_ID — the surrogate primary key (constraint AMS_ACT_RESOURCES_PK), also documented as unique index AMS_ACT_RESOURCES_U1. It uniquely identifies each activity-resource association.
• ACT_RESOURCE_USED_BY_ID — the identifier of the activity or event by which the resource is used. This is the business-key candidate column in unique index AMS_ACT_RESOURCES_UK1, along with RESOURCE_ID and ARC_ACT_RESOURCE_USED_BY.
• ARC_ACT_RESOURCE_USED_BY — discriminator indicating which parent entity the ACT_RESOURCE_USED_BY_ID value refers to, allowing the same column to point to either event headers or event offers.
• RESOURCE_ID — the resource (business party/contact) assigned to the activity, sourced from JTF_RS_RESOURCE_EXTNS.
• ROLE_RELATE_ID and ROLE_CD — the relationship and role code defining how the resource participates in the activity.
• USER_STATUS_ID and SYSTEM_STATUS_CODE — the user-defined and system status of the resource assignment.
• START_DATE_TIME and END_DATE_TIME — the effective period during which the resource association is active.
• DESCRIPTION and the ATTRIBUTE_CATEGORY / ATTRIBUTE1–15 flexfield columns — descriptive text and descriptive flexfield data.
• Standard WHO and concurrency columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER, and SECURITY_GROUP_ID.

Common Use Cases and Queries

Typical usage includes event staffing reports, campaign participant rosters, and resource-utilization analysis across activities. Analysts join AMS_ACT_RESOURCES to event headers and event offers via ACT_RESOURCE_USED_BY_ID, resolving the parent with ARC_ACT_RESOURCE_USED_BY, and to party records via RESOURCE_ID.

• List active resources for an event: SELECT r.RESOURCE_ID, r.ROLE_CD FROM AMS.AMS_ACT_RESOURCES r WHERE r.ACT_RESOURCE_USED_BY_ID = :event_id AND (r.END_DATE_TIME IS NULL OR r.END_DATE_TIME > SYSDATE);
• Join to event headers: ... FROM AMS_ACT_RESOURCES r JOIN AMS_EVENT_HEADERS_ALL_B h ON r.ACT_RESOURCE_USED_BY_ID = h.EVENT_HEADER_ID
• Join to resource master: ... JOIN JTF_RS_RESOURCE_EXTNS x ON r.RESOURCE_ID = x.RESOURCE_ID
• Filter by status: resolve USER_STATUS_ID against AMS_USER_STATUSES_B, or use SYSTEM_STATUS_CODE directly.

Related Objects

• AMS_EVENT_HEADERS_ALL_B — joined on ACT_RESOURCE_USED_BY_ID; supplies event context.
• AMS_EVENT_OFFERS_ALL_B — joined on ACT_RESOURCE_USED_BY_ID; supplies offer context.
• JTF_RS_RESOURCE_EXTNS — joined on RESOURCE_ID; the resource/party master.
• AMS_USER_STATUSES_B — joined on USER_STATUS_ID; user-defined status lookup.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; multi-org security context.