Search Results survey_assoc_id

Overview

AMW_SURVEY_ASSOCS is a table belonging to the AMW – Internal Controls Manager product family within Oracle E-Business Suite, documented across releases 12.1.1 and 12.2.2. The object is classified in the ETRM metadata as obsolete, meaning Oracle no longer actively develops or supports it in current EBS deployments, though its definition remains catalogued for historical and upgrade reference. As its description indicates, the table stores details of the association between a survey and an assessment, functioning as a cross-reference container that links survey constructs to the assessment or deployment activities against which they are evaluated.

The documented physical schema in release 12.1.1 lists the owner as AMW with twelve columns. Notably, the metadata states that the object is not implemented in the current database, and therefore no live data segments or indexes should be expected in a standard installation. From a Data Vault modeling perspective, the heuristic classification supplied with the metadata identifies AMW_SURVEY_ASSOCS as standalone. This should be treated as a modeling suggestion rather than a definitive design: because the table carries both a surrogate identifier and multiple foreign-key-like references to survey, cycle, and deployment entities, it exhibits the characteristics of a link table rather than a pure hub or satellite. Implementers reconstructing the model should evaluate it as a candidate link bridging survey and assessment domains.

Key Information Stored

The primary key of the table is enforced through AMW_SURVEY_ASSOCS_PK, defined on the SURVEY_ASSOC_ID column. This surrogate key uniquely identifies each association record and is the value most often referenced when users search for survey_assoc_id. Surrounding the primary key are the standard EBS WHO columns that audit record lifecycle: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER, the latter supporting optimistic locking during concurrent updates.

The business content of the row is carried by the association payload columns. OBJECT_ID and OBJECT_TYPE identify the generic target of the association, allowing the table to point at heterogeneous assessment objects. IES_SURVEY_ID, IES_CYCLE_ID, and IES_DEPLOYMENT_ID anchor the row to the survey definition, the assessment cycle, and the specific deployment instance respectively. Together these three identifiers form the natural business-key candidates that determine which survey is associated with which assessment context; a unique index on this combination would be the logical enforcement point in a production design, although the documented metadata records only the primary key constraint.

Common Use Cases and Queries

Because the table is documented as obsolete and unimplemented, the primary use cases are historical reporting, data migration analysis, and upgrade impact assessment rather than day-to-day transaction processing. A typical investigative query retrieves all association rows for a given survey and cycle:

• SELECT survey_assoc_id, object_id, object_type, ies_survey_id, ies_cycle_id, ies_deployment_id FROM amw_survey_assocs WHERE ies_survey_id = :survey_id AND ies_cycle_id = :cycle_id;
• Reverse lookup by generic object: filter on OBJECT_TYPE and OBJECT_ID to determine which surveys were associated with a particular assessment object.
• Audit trail extraction: select the WHO columns to determine when associations were created or last modified, useful when reconciling legacy Internal Controls Manager data during migration.
• Deployment scoping: group by IES_DEPLOYMENT_ID to count associations per deployment for capacity or reconciliation reporting.

When the table is absent—as the metadata indicates for the current database—queries should be guarded by checks against ALL_TABLES before execution, and migration scripts should treat its contents as optional.

Related Objects

The metadata identifies AMW_SURVEY_ASSOCS as standalone from a foreign-key perspective, so no enforced FK relationships are documented. Conceptually, however, the following objects are the most significant counterparts:

• AMW_SURVEYS (referenced via IES_SURVEY_ID) — the survey definition being associated.
• AMW_CYCLES (referenced via IES_CYCLE_ID) — the assessment cycle governing the evaluation period.
• AMW_DEPLOYMENTS (referenced via IES_DEPLOYMENT_ID) — the deployment instance in which the survey runs.
• The generic assessment entity identified by OBJECT_TYPE and OBJECT_ID, resolved dynamically rather than through a declared constraint.
• AMW_SURVEY_ASSOCS_PK — the primary key constraint object itself, defined on SURVEY_ASSOC_ID.

Because no foreign keys are enforced, referential integrity for these relationships must be validated manually during data analysis and migration.