Results for “ams_custom_setup_attr_bk”

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

Overview

AMS_CUSTOM_SETUP_ATTR_BK is a Marketing (AMS) module table in Oracle EBS 12.1.1 and 12.2.2 that stores attribute-level definition metadata for custom setup entities. The "_BK" suffix designates it as a backup or staging-tier table within the AMS custom setup framework, holding the attribute records that describe how individual fields behave in a custom setup — including display ordering, mandatory status, cue card visibility, and report availability. The table is populated and maintained by the AMS setup infrastructure and is used to drive dynamic attribute behavior at runtime.

Heuristic Data Vault classification (mined from the FK structure) suggests this object is a satellite. It carries descriptive, changing attributes about a parent setup entity and references parent hubs/links — AMS_CUSTOM_SETUP_ATTR, AMS_CUSTOM_SETUPS_B, and FND_SECURITY_GROUPS — through foreign keys. Treating it as a satellite in a data-vault model would separate its descriptive payload from the parent setup business keys. The table is standalone in the sense that no other documented table holds a foreign key back to it.

Key Information Stored

The documented physical schema holds 22 columns. The most significant are:

• SETUP_ATTRIBUTE_ID — Surrogate primary key identifying each attribute record; also a foreign key to AMS_CUSTOM_SETUP_ATTR.
• CUSTOM_SETUP_ID — Foreign key to AMS_CUSTOM_SETUPS_B, linking the attribute to its parent custom setup definition.
• OBJECT_ATTRIBUTE — The underlying object attribute name this setup attribute maps to.
• DISPLAY_SEQUENCE_NO and PARENT_DISPLAY_SEQUENCE — Control ordering of attributes in the UI, including nested/hierarchical presentation.
• ATTR_MANDATORY_FLAG — Indicates whether the attribute is required during setup entry.
• ATTR_AVAILABLE_FLAG — Indicates whether the attribute is exposed/available for use.
• SHOW_IN_CUE_CARD and SHOW_IN_REPORT — Visibility flags governing cue card and report rendering.
• FUNCTION_NAME and PARENT_FUNCTION_NAME — The function context in which the attribute is presented and its parent context.
• PARENT_SETUP_ATTRIBUTE — Reference to a parent attribute for hierarchical setups.
• RELATED_AK_ATTRIBUTE — The associated alternate-key attribute used for value derivation or matching.
• COPY_ALLOWED_FLAG — Whether the attribute value may be copied when duplicating a setup.
• ESSENTIAL_SEQ_NUM — Sequencing for essential attributes surfaced in guided setup.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enabling Multi-Org/security-group filtering.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the AMS framework to detect concurrent updates.

Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — are also present for audit tracking.

Common Use Cases and Queries

Typical use cases include reviewing which attributes are mandatory for a given custom setup, auditing cue card and report visibility, and reconciling backup/staging attribute rows against the live AMS_CUSTOM_SETUP_ATTR table.

• List mandatory attributes for a setup:

  SELECT a.SETUP_ATTRIBUTE_ID, a.OBJECT_ATTRIBUTE, a.DISPLAY_SEQUENCE_NO
  FROM AMS.AMS_CUSTOM_SETUP_ATTR_BK a
  WHERE a.CUSTOM_SETUP_ID = :setup_id
    AND a.ATTR_MANDATORY_FLAG = 'Y'
  ORDER BY a.DISPLAY_SEQUENCE_NO;

• Cue card / report configuration report:

  SELECT OBJECT_ATTRIBUTE, SHOW_IN_CUE_CARD, SHOW_IN_REPORT
  FROM AMS.AMS_CUSTOM_SETUP_ATTR_BK
  WHERE CUSTOM_SETUP_ID = :setup_id;

• Joining to the parent setup definition via AMS_CUSTOM_SETUPS_B on CUSTOM_SETUP_ID to resolve setup names, and to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to resolve security context.

Reporting use cases include setup configuration audits, migration validation between environments, and comparison of backup rows to current attribute definitions ahead of an upgrade.

Related Objects

The following objects are most significant to this table, based on documented FK relationships:

• AMS_CUSTOM_SETUP_ATTR — Parent attribute definition table; joined on SETUP_ATTRIBUTE_ID.
• AMS_CUSTOM_SETUPS_B — Parent custom setup base table; joined on CUSTOM_SETUP_ID.
• FND_SECURITY_GROUPS — Security group reference; joined on SECURITY_GROUP_ID.
• AMS_CUSTOM_SETUPS_TL — Translation table for setup names/descriptions, typically joined via CUSTOM_SETUP_ID for reporting.
• AMS_CUSTOM_SETUP_VALUES — Holds actual captured setup values that reference these attribute definitions.
• FND_FUNCTION / FND_FORM_FUNCTIONS — Resolve FUNCTION_NAME and PARENT_FUNCTION_NAME to application function context.
• AMS setup APIs used to create and maintain custom setups, which drive inserts and updates into this table as part of the setup lifecycle.