Results for “setup_attribute_id”

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

Overview

AMS.AMS_CUSTOM_SETUP_ATTR is a Marketing (AMS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the individual setup attributes belonging to a custom setup definition. Where AMS_CUSTOM_SETUPS_B holds the header-level definition of a user-defined or extensible marketing setup, AMS_CUSTOM_SETUP_ATTR holds the granular rows that describe each attribute participating in that setup: which object attribute is presented, whether it is mandatory or available, its display ordering, its cue-card and report visibility, and its parent/child grouping behavior. The table therefore acts as the attribute-level extension of the custom setup framework and is a core dependency for setups that drive marketing object configuration and UI behavior.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is satellite-leaning. AMS_CUSTOM_SETUP_ATTR is best treated as a descriptive satellite attached to the AMS_CUSTOM_SETUPS_B hub: it carries the descriptive, non-key context of a custom setup, keyed by its own surrogate identifier and linked back to the parent setup. It is not a pure hub or link, so it should generally not be used as a standalone integration point.

Key Information Stored

The table contains 23 documented columns in the 12.2.2 physical schema. The most significant include:

• SETUP_ATTRIBUTE_ID — the surrogate primary key, enforced by AMS_CUSTOM_SETUP_ATTR_PK. This is also the leading column of unique index AMS_CUSTOM_SETUP_ATTR_U1.
• CUSTOM_SETUP_ID — foreign key to AMS_CUSTOM_SETUPS_B, identifying the parent custom setup; leading column of unique index AMS_CUSTOM_SETUP_ATTR_U2.
• OBJECT_ATTRIBUTE — the business attribute being configured; combined with CUSTOM_SETUP_ID in U2, this forms the primary business-key candidate.
• DISPLAY_SEQUENCE_NO, PARENT_DISPLAY_SEQUENCE — control ordering of the attribute and its parent group in the setup UI.
• ATTR_MANDATORY_FLAG, ATTR_AVAILABLE_FLAG, COPY_ALLOWED_FLAG — flags governing whether the attribute is required, selectable, and copyable.
• SHOW_IN_CUE_CARD, SHOW_IN_REPORT — control presentation in cue cards and reporting output.
• FUNCTION_NAME, PARENT_FUNCTION_NAME — function-level context governing where the attribute appears.
• PARENT_SETUP_ATTRIBUTE — enables hierarchical grouping of attributes.
• RELATED_AK_ATTRIBUTE, ESSENTIAL_SEQ_NUM — relate the attribute to alternate-key attributes and essential sequencing.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing Multi-Org security.
• ZD_EDITION_NAME — the editioning column supporting Online Patching (adopted in 12.2.2); it participates in both U1 and U2. Audit columns include LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

Typical usage covers configuration review, attribute-availability reporting, and migration validation. To list all attributes of a setup:

SELECT a.setup_attribute_id, a.object_attribute, a.display_sequence_no, a.attr_mandatory_flag, a.attr_available_flag FROM ams.ams_custom_setup_attr a WHERE a.custom_setup_id = :p_setup_id ORDER BY a.display_sequence_no;

To join attributes to their parent setup and identify ordering within a security group, join AMS_CUSTOM_SETUP_ATTR to AMS_CUSTOM_SETUPS_B on CUSTOM_SETUP_ID and filter by SECURITY_GROUP_ID. Common reporting scenarios include auditing which attributes are mandatory, which appear in cue cards or reports, and which attributes allow copy during setup replication. Because ZD_EDITION_NAME participates in both unique indexes, edition-aware queries should constrain by the active edition when reconciling patched environments.

Related Objects

• AMS_CUSTOM_SETUPS_B — the parent setup header; joined via AMS_CUSTOM_SETUP_ATTR.CUSTOM_SETUP_ID = AMS_CUSTOM_SETUPS_B.CUSTOM_SETUP_ID.
• AMS_CUSTOM_SETUP_ATTR_BK — the backup table referencing AMS_CUSTOM_SETUP_ATTR via SETUP_ATTRIBUTE_ID.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for Multi-Org security context.
• AMS_CUSTOM_SETUPS_TL — translated setup names, linked through the parent setup for display purposes.
• FND_FUNCTION / FND_FORM_FUNCTIONS — functional context referenced by FUNCTION_NAME and PARENT_FUNCTION_NAME.

Together these objects define and expose the custom setup attribute framework within the AMS Marketing module.