Search Results ams_act_qa_checks_pk

Overview

AMS_ACT_QA_CHECKS is a table in the AMS (Oracle Marketing) schema that stores the quality assurance checks configured to run against a given marketing activity. Within Oracle EBS 12.1.1 and 12.2.2, this object acts as the configuration backbone for the Activity Quality Assurance framework, which validates that a marketing activity satisfies predefined business rules before it is allowed to progress through its lifecycle (for example, before it can be launched, approved, or transitioned to a downstream status). Each row represents a single QA check definition, binding a check function or package to a specific activity context and status-order rule.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this table as satellite-leaning. It carries descriptive and behavioral attributes (warning flags, enabled flags, status codes, function and package names) that describe a business key defined elsewhere, rather than acting as a pure hub or link. This is a modeling suggestion only; the table itself is a standard 12.x EBS transactional configuration entity.

Key Information Stored

The table contains 16 documented columns. Its surrogate primary key is ACTIVITY_QA_CHECK_ID, enforced by the unique index AMS_ACT_QA_CHECKS_PK. A second unique index, AMS_ACT_QA_CHECKS_U2, defines the business-key candidate as the combination of ACTIVITY_QA_CHECK_FOR_ID, ARC_ACTIVITY_QA_CHECK_FOR, and FUNCTION_NAME, which together identify a unique check within its activity context.

• ACTIVITY_QA_CHECK_ID — Surrogate primary key; unique system-generated identifier for each QA check row.
• ACTIVITY_QA_CHECK_FOR_ID — Foreign key to AMS_STATUS_ORDER_RULES, indicating the status-order rule the check belongs to; part of the business-key candidate.
• ARC_ACTIVITY_QA_CHECK_FOR — Code qualifying the check's activity context; part of the unique business key.
• FUNCTION_NAME — Name of the PL/SQL function invoked to perform the check; part of the unique business key.
• PACKAGE_NAME — PL/SQL package housing the check logic.
• ENABLED_FLAG — Indicates whether the QA check is currently active.
• WARNING_ONLY_FLAG — Determines whether a failed check produces only a warning rather than a hard error.
• STATUS_CODE — Status classification of the check row.
• DESCRIPTION — Human-readable description of the check's purpose.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS supporting multi-org/security partitioning.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the 12.2.x framework.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / CREATION_DATE / CREATED_BY / LAST_UPDATE_LOGIN — Standard EBS WHO-column audit trail.

Common Use Cases and Queries

Typical scenarios include auditing which QA checks are active for a marketing activity, diagnosing why an activity failed a validation step, and reporting on checks configured as warning-only versus blocking. A representative query joining the foreign key to the status-order rule table:

• SELECT q.ACTIVITY_QA_CHECK_ID, q.PACKAGE_NAME, q.FUNCTION_NAME, q.ENABLED_FLAG, q.WARNING_ONLY_FLAG FROM AMS.AMS_ACT_QA_CHECKS q WHERE q.ACTIVITY_QA_CHECK_FOR_ID = :rule_id AND q.ENABLED_FLAG = 'Y';
• SELECT q.FUNCTION_NAME, q.DESCRIPTION, r.* FROM AMS.AMS_ACT_QA_CHECKS q, AMS.AMS_STATUS_ORDER_RULES r WHERE q.ACTIVITY_QA_CHECK_FOR_ID = r.STATUS_ORDER_RULE_ID;
• Reporting on checks with WARNING_ONLY_FLAG = 'N' to identify hard-blocking validations across all activities.
• Filtering by SECURITY_GROUP_ID for multi-org scoped administration.

Related Objects

The following objects are the most significant relationships for this table based on documented FK structure:

• AMS_STATUS_ORDER_RULES — Referenced via ACTIVITY_QA_CHECKS.ACTIVITY_QA_CHECK_FOR_ID; defines the status-order rule each QA check is bound to.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for security partitioning.
• AMS_ACT_QA_CHECKS_PK / AMS_ACT_QA_CHECKS_U1 / AMS_ACT_QA_CHECKS_U2 — Primary and unique indexes enforcing key integrity.
• Activity and campaign parent entities in the AMS schema that consume the QA framework indirectly through the status-order rules.