Search Results survey_name

Overview

The IES_SVY_SURVEYS_V view is a reporting and integration artifact within the Oracle E-Business Suite (EBS) IES – Scripting product family, owned by the APPS schema and marked VALID in the ETRM catalog for releases 12.1.1 and 12.2.2. It exposes survey definition header data managed by the Scripting engine, which is used to build and administer interactive scripts, questionnaires, and survey instruments consumed by Oracle Advanced Outbound and related telephony/agent-facing modules.

The view functions as a read-oriented projection over the survey master entity. Rather than requiring external consumers to reference the multi-organization base table directly, it provides a stable, singular name that can be granted to reporting users, embedded in concurrent program queries, or invoked through Oracle Reports, BI Publisher, and OBIEE integration layers. Because it resolves to the survey header only, it does not itself carry question, response, or answer detail; those reside in sibling child objects linked by SURVEY_ID. The user search term "survey_id" aligns precisely with the primary business key this view publishes.

Underlying Base Objects

The documented definition is a straightforward single-source SELECT over IES_SVY_SURVEYS_ALL, which is exposed through a SYNONYM in the APPS schema. No joins, unions, or analytical clauses are present in the documented view text. Column names are carried through unchanged, and no filtering predicate is applied, so the view returns the full row population of the underlying table.

• IES_SVY_SURVEYS_ALL — the multi-organization (ORG_ID-enabled) survey header table and the sole documented base object.
• APPS.IES_SVY_SURVEYS_V — the APPS-owned view layered on top, inheriting owner and grants from the base table.
• The _ALL suffix confirms the base table is partitioned by operating unit, so callers must supply or inherit the correct ORG_ID context in multi-org environments.

Because the view is a thin pass-through, referential integrity, value-set validation, and WHO-column population are governed entirely by the base table and its underlying Concurrent Program / EBS runtime conventions. Any DML attempted against the view is subject to the updatability rules of the single-table join, though in practice the view is intended for read access.

Key Columns

• SURVEY_ID — the surrogate primary key uniquely identifying each survey definition; the principal foreign key referenced by question, response, and answer tables.
• SURVEY_NAME — the user-visible survey or script name presented in administrative and reporting interfaces.
• SURVEY_DESCRIPTION — free-text description of the survey's purpose.
• SURVEY_STATUS_CODE — lifecycle state of the survey (for example, active versus inactive), driving whether the instrument is available for execution.
• DSCRIPT_ID — identifier of the associated script definition, tying the survey to its Scripting framework object.
• F_DELETEDFLAG — soft-delete indicator; rows are logically removed rather than physically purged, so queries typically filter on this flag.
• ORG_ID — operating unit identifier supporting Multi-Org Access Control and row-level security.
• OBJECT_VERSION_NUMBER — optimistic locking token used by the entity's business object layer.
• CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — standard WHO audit columns.
• SECURITY_GROUP_ID — security grouping reference used by the Scripting security model.

Common Use Cases and Queries

Typical usage centers on survey inventory reporting, validation of configured instruments, and integration lookups that resolve a survey name to its internal identifier before traversing to question-level tables.

• Listing all active surveys for a given operating unit.
• Resolving a survey name into its SURVEY_ID for downstream joins.
• Auditing creation and last-modification activity on survey definitions.

Representative SQL:

SELECT survey_id, survey_name, survey_status_code, org_id
FROM apps.ies_svy_surveys_v
WHERE f_deletedflag = 'N' AND org_id = :p_org_id
ORDER BY survey_name;

SELECT survey_id
FROM apps.ies_svy_surveys_v
WHERE survey_name = :p_survey_name AND f_deletedflag = 'N';

Consumers should qualify the view with the APPS schema, include the ORG_ID predicate where multi-org security applies, and filter F_DELETEDFLAG to exclude logically removed definitions.