Search Results ams_object_attributes




Overview

The AMS_OBJECT_ATTRIBUTES table is a historical data object within the Oracle E-Business Suite (EBS) Marketing (AMS) module. According to the official ETRM documentation, this table is explicitly marked as obsoleted and is no longer in use in versions 12.1.1 and 12.2.2. Its original purpose was to store attribute data associated with various marketing objects, such as campaigns and events, likely serving as a flexible extension mechanism for custom data points. Its current status indicates that its functionality has been superseded by other architectural components or tables within the AMS schema, and it should be considered a legacy artifact for reference only during data migration or historical analysis.

Key Information Stored

While the detailed column list is not provided in the excerpt, the documented primary and foreign key relationships reveal its core structural elements. The primary key column is OBJECT_ATTRIBUTE_ID, which uniquely identified each attribute record. The table was designed to link to several major marketing entities via the OBJECT_ID column, which served as a foreign key to campaign, event header, and event offer tables. Furthermore, the CUSTOM_SETUP_ID column established a relationship with the AMS_CUSTOM_SETUPS_B table, suggesting the attributes were potentially governed by configurable setup definitions. This structure implies the table stored records linking an object (campaign, event) to specific attribute values, with the attribute definitions themselves likely managed elsewhere.

Common Use Cases and Queries

Given the table's obsolete status, there are no active operational or reporting use cases in a standard EBS 12.1.1 or 12.2.2 environment. Its sole contemporary relevance is for technical consultants or DBAs performing historical data audits or managing legacy data cleanup projects. Sample queries would be strictly diagnostic, such as identifying any residual data that may require archiving before a table purge. A typical check would be a simple SELECT COUNT(*) FROM apps.AMS_OBJECT_ATTRIBUTES. Any joins, such as linking to campaign tables via OBJECT_ID, would only be for understanding old data relationships and should not be incorporated into new development, interfaces, or reports.

Related Objects

The ETRM metadata documents specific foreign key relationships for this table. AMS_OBJECT_ATTRIBUTES references the following core marketing tables, indicating the scope of objects it once described:

  • AMS_CAMPAIGNS_ALL_B: Via the OBJECT_ID column. This linked attributes to campaign master records.
  • AMS_EVENT_HEADERS_ALL_B: Via the OBJECT_ID column. This linked attributes to event master records.
  • AMS_EVENT_OFFERS_ALL_B: Via the OBJECT_ID column. This linked attributes to specific event offers.
  • AMS_CUSTOM_SETUPS_B: Via the CUSTOM_SETUP_ID column. This linked the attribute instance to its configuration setup.

These relationships confirm the table's role as a central, flexible attribute store for multiple marketing object types, a pattern that has since been deprecated in favor of more standardized extension methods within Oracle EBS.