Results for “code_ind_flag”

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

Overview

AMS_COND_STRUCT_RESTRICT_VALUE is an Oracle E-Business Suite table owned by the AMS (Marketing) schema. It stores the restricted list-of-values (LOV) entries associated with a query template condition in the Audience Workbench. When a marketer builds a query template condition that limits a selection attribute to a specific set of allowed values, the individual included or excluded values are persisted as rows in this table. The table therefore acts as the detail store beneath the higher-level condition structure definition.

From a heuristic Data Vault modeling perspective, this object is best classified as a satellite. It carries descriptive attributes (the code value, inclusion indicator, and audit columns) attached to a parent condition structure business key, plus its own surrogate identifier. It is not a pure hub because it introduces no independent business concept, and it is not a link because it resolves no many-to-many relationship between two distinct hubs. This classification is a modeling suggestion derived from the foreign-key topology, not a documented ETRM designation.

Key Information Stored

The table contains 17 documented columns. The most significant are listed below.

• COND_STRUCT_RESTRICT_ID — the surrogate primary key, backed by the unique index AMS_CONDITION_RESTRICT_PK. It uniquely identifies each restricted-value row.
• QUERY_COND_DISP_STRUCT_ID — the linkage to the parent query condition display structure; this is the de facto business key relating each restricted value to its owning condition.
• CODE — the actual restricted LOV value or code captured for the condition.
• INCLUDED_FLAG — indicates whether the code is included in or excluded from the condition's result set.
• CODE_IND_FLAG — a discriminator flag describing the nature or type of the stored code.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OA Framework to detect concurrent updates.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant data segregation.
• ZD_EDITION_NAME — the edition marker used by Oracle's online patching (Edition-Based Redefinition) infrastructure; it participates in the unique index AMS_COND_STRUCT_RESTRICT_U1 alongside COND_STRUCT_RESTRICT_ID.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard EBS who-columns providing creation and audit history.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — the standard concurrent program context columns, recording which program populated or last updated the row.

The unique index AMS_COND_STRUCT_RESTRICT_U1 on (COND_STRUCT_RESTRICT_ID, ZD_EDITION_NAME) is the principal business-key candidate, combining the surrogate identifier with the edition to support Online Patching in 12.2.2.

Common Use Cases and Queries

Because this table drives Audience Workbench condition behavior, it is most commonly interrogated during troubleshooting and reconciliation of list-building queries. Typical activities include identifying why a condition returns (or omits) particular values, auditing which values a marketer has explicitly restricted, and verifying that seeded templates reference valid LOV codes.

A representative query retrieves all restricted values for a condition:

• SELECT COND_STRUCT_RESTRICT_ID, CODE, INCLUDED_FLAG, CODE_IND_FLAG FROM AMS.AMS_COND_STRUCT_RESTRICT_VALUE WHERE QUERY_COND_DISP_STRUCT_ID = :condition_id;

To audit who created or changed restrictions, join the who-columns to FND_USER:

• SELECT r.CODE, r.INCLUDED_FLAG, u.USER_NAME, r.LAST_UPDATE_DATE FROM AMS.AMS_COND_STRUCT_RESTRICT_VALUE r, FND_USER u WHERE r.LAST_UPDATED_BY = u.USER_ID AND r.QUERY_COND_DISP_STRUCT_ID = :condition_id;

Reporting use cases include measuring the number of inclusive versus exclusive values per condition, detecting conditions with no restrictions, and migrating condition definitions between environments by extracting CODE and INCLUDED_FLAG rows alongside their parent structures.

Related Objects

The documented foreign-key relationship connects this table to the following core object, and several related tables in the Audience Workbench schema are significant through the shared condition identifier.

• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID; governs which security group owns each restricted value.
• AMS_COND_STRUCT_RESTRICT — the parent condition-restriction header; joined on the shared COND_STRUCT_RESTRICT_ID business identifier.
• AMS_QUERY_COND_DISP_STRUCT — the query condition display structure referenced by QUERY_COND_DISP_STRUCT_ID, defining the condition to which restricted values belong.
• AMS_CONDITION_STRUCTURE — the broader condition-structure definition that owns the query condition display structure.
• FND_USER — joined through CREATED_BY and LAST_UPDATED_BY for audit reporting.
• FND_CONCURRENT_REQUESTS / FND_CONCURRENT_PROGRAMS — joined through REQUEST_ID and PROGRAM_ID for program-context traceability.

These objects together form the persistence layer through which Audience Workbench renders, evaluates, and audits query template conditions and their restricted value lists.