Search Results mnhd website
The AMS.AMS_ACT_CONTACT_POINTS
table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 is a critical data structure within the Oracle Marketing (AMS) module, designed to store and manage contact point information for activities and campaigns. This table serves as a junction between marketing activities and contact details, enabling organizations to track communication channels, preferences, and interaction histories for targeted marketing efforts. Below is a detailed analysis of its purpose, structure, and integration within Oracle EBS.
Purpose and Functional Overview
TheAMS_ACT_CONTACT_POINTS
table acts as a repository for contact points associated with marketing activities, such as campaigns, events, or lead engagements. It links activity records (AMS_ACTIVITIES
) with contact information (AMS_CONTACT_POINTS
), ensuring that marketing teams can maintain a centralized view of customer interactions across multiple channels (email, phone, social media, etc.). This table supports key marketing operations, including segmentation, campaign execution, and response tracking.
Table Structure and Key Columns
The table's schema includes columns that define relationships, contact methods, and metadata. Key columns include:- ACT_CONTACT_POINT_ID: Primary key, uniquely identifying each contact point record.
- ACTIVITY_ID: Foreign key referencing
AMS_ACTIVITIES
, linking to the associated marketing activity. - CONTACT_POINT_ID: Foreign key referencing
AMS_CONTACT_POINTS
, identifying the contact method (e.g., email address or phone number). - STATUS_CODE: Indicates the status of the contact point (e.g., ACTIVE, INACTIVE).
- USAGE_TYPE: Specifies the purpose (e.g., PRIMARY, SECONDARY) of the contact point in the activity.
- CREATION_DATE and LAST_UPDATE_DATE: Audit columns tracking record creation and modification timestamps.
Integration with Oracle EBS Modules
The table integrates with several EBS modules:- Marketing (AMS): Core to campaign management, enabling activity-specific contact tracking.
- CRM: Shares data with
HZ_CONTACT_POINTS
(Trading Community Architecture) for unified customer profiles. - Sales: Supports lead and opportunity management by linking contact points to sales activities.
Technical Considerations
- Indexing: Optimized for queries on
ACTIVITY_ID
andCONTACT_POINT_ID
to enhance join performance. - Data Volume: Can grow significantly in high-activity environments; partitioning may be required for scalability.
- Security: Access is controlled via Oracle EBS responsibilities and grants, often restricted to marketing roles.
Customization and Extensions
Organizations may extend the table's functionality by:- Adding custom columns via descriptive flexfields (DFFs) to capture industry-specific attributes.
- Creating triggers or workflows to automate contact point validation or updates.
Conclusion
TheAMS.AMS_ACT_CONTACT_POINTS
table is a foundational component of Oracle Marketing, bridging activities and customer interactions. Its design ensures efficient data management, supports complex marketing workflows, and aligns with broader EBS integration patterns. Proper utilization of this table enhances campaign precision, customer engagement, and reporting accuracy in Oracle EBS 12.1.1 and 12.2.2 environments.
-
Lookup Type: AMS_CONTACT_POINT_TYPE
12.2.2
product: AMS - Marketing , meaning: Contact Point Type , description: Contact Point type ,
-
APPS.IBY_FD_EXTRACT_GEN_PVT dependencies on HZ_FORMAT_PHONE_V2PUB
12.2.2
-
Lookup Type: AMS_CONTACT_POINT_TYPE
12.1.1
product: AMS - Marketing , meaning: Contact Point Type , description: Contact Point type ,
-
APPS.IBY_FD_EXTRACT_GEN_PVT dependencies on HZ_FORMAT_PHONE_V2PUB
12.1.1
-
Index of locally available sites:
12.2.2
-
Index of locally available sites:
12.1.1
-
Oops!...
12.1.1
-
VIEW: APPS.AMS_CAMPAIGN_SCHEDULES_B1_DFV
12.1.1
owner:APPS, object_type:VIEW, object_name:AMS_CAMPAIGN_SCHEDULES_B1_DFV, status:VALID,
-
APPS.IBY_FD_EXTRACT_GEN_PVT dependencies on DUAL
12.1.1
-
Oops!...
12.2.2
-
VIEW: APPS.AMS_CAMPAIGN_SCHEDULES_B1_DFV
12.2.2
owner:APPS, object_type:VIEW, object_name:AMS_CAMPAIGN_SCHEDULES_B1_DFV, status:VALID,
-
APPS.IBY_FD_EXTRACT_GEN_PVT dependencies on DUAL
12.2.2
-
TABLE: AMS.AMS_ACT_CONTACT_POINTS
12.1.1
owner:AMS, object_type:TABLE, fnd_design_data:AMS.AMS_ACT_CONTACT_POINTS, object_name:AMS_ACT_CONTACT_POINTS, status:VALID,
-
TABLE: PON.PON_SUPPLIER_PROVIDERS
12.1.1
owner:PON, object_type:TABLE, fnd_design_data:PON.PON_SUPPLIER_PROVIDERS, object_name:PON_SUPPLIER_PROVIDERS, status:VALID,
-
TABLE: PON.PON_SUPPLIER_PROVIDERS
12.2.2
owner:PON, object_type:TABLE, fnd_design_data:PON.PON_SUPPLIER_PROVIDERS, object_name:PON_SUPPLIER_PROVIDERS, status:VALID,
-
TABLE: AMS.AMS_ACT_CONTACT_POINTS
12.2.2
owner:AMS, object_type:TABLE, fnd_design_data:AMS.AMS_ACT_CONTACT_POINTS, object_name:AMS_ACT_CONTACT_POINTS, status:VALID,
-
APPS.HZ_ELOCATION_PKG dependencies on FND_PROFILE
12.2.2
-
APPS.HZ_ELOCATION_PKG dependencies on HZ_GEOCODE_PKG
12.2.2
-
APPS.HZ_ELOCATION_PKG dependencies on HZ_GEOCODE_PKG
12.1.1
-
APPS.HZ_ELOCATION_PKG dependencies on FND_PROFILE
12.1.1
-
TABLE: CSD.CSD_RECALL_HEADERS_B
12.2.2
owner:CSD, object_type:TABLE, fnd_design_data:CSD.CSD_RECALL_HEADERS_B, object_name:CSD_RECALL_HEADERS_B, status:VALID,
-
VIEW: APPS.OKC_ARTICLES_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:OKC.OKC_ARTICLES_V, object_name:OKC_ARTICLES_V, status:VALID,
-
TABLE: OKC.OKC_ARTICLE_VERSIONS
12.1.1
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_ARTICLE_VERSIONS, object_name:OKC_ARTICLE_VERSIONS, status:VALID,
-
VIEW: APPS.OKC_ARTICLES_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:OKC.OKC_ARTICLES_V, object_name:OKC_ARTICLES_V, status:VALID,
-
VIEW: APPS.CSD_RECALL_HEADERS_VL
12.2.2
owner:APPS, object_type:VIEW, object_name:CSD_RECALL_HEADERS_VL, status:VALID,
-
TABLE: OKC.OKC_ARTICLE_VERSIONS
12.2.2
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_ARTICLE_VERSIONS, object_name:OKC_ARTICLE_VERSIONS, status:VALID,
-
TABLE: AR.AR_CMGT_BANK_REF_DATA
12.2.2
owner:AR, object_type:TABLE, fnd_design_data:AR.AR_CMGT_BANK_REF_DATA, object_name:AR_CMGT_BANK_REF_DATA, status:VALID,
-
TABLE: AR.AR_CMGT_BANK_REF_DATA
12.1.1
owner:AR, object_type:TABLE, fnd_design_data:AR.AR_CMGT_BANK_REF_DATA, object_name:AR_CMGT_BANK_REF_DATA, status:VALID,
-
APPS.PON_WF_UTL_PKG dependencies on FND_LOG
12.2.2
-
APPS.PON_WF_UTL_PKG dependencies on FND_LOG
12.1.1
-
TABLE: OKC.OKC_ART_INTERFACE_ALL
12.1.1
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_ART_INTERFACE_ALL, object_name:OKC_ART_INTERFACE_ALL, status:VALID,
-
TABLE: OKC.OKC_ART_INTERFACE_ALL
12.2.2
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_ART_INTERFACE_ALL, object_name:OKC_ART_INTERFACE_ALL, status:VALID,
-
TABLE: AR.AR_CMGT_GUARANTOR_DATA
12.2.2
owner:AR, object_type:TABLE, fnd_design_data:AR.AR_CMGT_GUARANTOR_DATA, object_name:AR_CMGT_GUARANTOR_DATA, status:VALID,
-
TABLE: DDR.DDR_I_ORG_BSNS_UNIT
12.1.1
owner:DDR, object_type:TABLE, object_name:DDR_I_ORG_BSNS_UNIT, status:VALID,
-
TABLE: AR.AR_CMGT_GUARANTOR_DATA
12.1.1
owner:AR, object_type:TABLE, fnd_design_data:AR.AR_CMGT_GUARANTOR_DATA, object_name:AR_CMGT_GUARANTOR_DATA, status:VALID,
-
TABLE: DDR.DDR_E_ORG_BSNS_UNIT
12.1.1
owner:DDR, object_type:TABLE, object_name:DDR_E_ORG_BSNS_UNIT, status:VALID,
-
TABLE: DDR.DDR_I_ORG_BSNS_UNIT
12.2.2
owner:DDR, object_type:TABLE, object_name:DDR_I_ORG_BSNS_UNIT, status:VALID,
-
TABLE: DDR.DDR_E_ORG_BSNS_UNIT
12.2.2
owner:DDR, object_type:TABLE, object_name:DDR_E_ORG_BSNS_UNIT, status:VALID,
-
PACKAGE: APPS.PER_TASKS_IN_CHECKLIST_API
12.1.1
-
PACKAGE: APPS.PER_TASKS_IN_CHECKLIST_API
12.2.2
-
PACKAGE: APPS.PER_ALLOCATED_TASK_API
12.1.1
-
PACKAGE: APPS.PER_ALLOCATED_TASK_API
12.2.2
-
APPS.IBY_FD_EXTRACT_GEN_PVT SQL Statements
12.1.1
-
APPS.IBY_FD_EXTRACT_GEN_PVT SQL Statements
12.2.2
-
PACKAGE BODY: APPS.PON_WF_UTL_PKG
12.1.1
-
PACKAGE BODY: APPS.PON_WF_UTL_PKG
12.2.2
-
APPS.HZ_GEOCODE_PKG dependencies on HZ_UTILITY_V2PUB
12.1.1
-
APPS.HZ_GEOCODE_PKG dependencies on HZ_UTILITY_V2PUB
12.2.2
-
PACKAGE: APPS.ETRM_STATIC
12.1.1
-
PACKAGE: APPS.ETRM_STATIC
12.2.2