Search Results survey_cycle_id




Overview
Explore in AI Chat

Overview

The IES_SVY_SUMMARY_STATS table is a transactional data object owned by the IES schema, which supports the Scripting module in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It stores aggregated statistical snapshots of survey deployment activity, capturing response counts, error totals, and lifecycle status indicators for each combination of survey, survey cycle, and deployment. In this capacity the table functions as a denormalized summary repository that complements the more granular survey response and deployment records maintained elsewhere in the IES schema.

The ETRM metadata classifies this object heuristically as a link in a Data Vault model. This classification reflects the composite three-part key — SURVEY_ID, SURVEY_CYCLE_ID, and SURVEY_DEPLOYMENT_ID — which resolves the many-to-many relationships between surveys, their scheduled cycles, and their operational deployments. The table effectively records the intersection of these three business entities along with the measured statistics accumulated against that intersection.

Key Information Stored

The table contains 22 documented columns. The most significant include:

The surrogate primary key is the composite of the three identifier columns. Business-key candidates are implicit in that same composite, since the natural uniqueness of a summary record is defined by which survey, cycle, and deployment it describes.

Common Use Cases and Queries

The table is most often queried for survey performance dashboards, response-rate reporting, and deployment health monitoring. Typical access patterns include retrieving the latest summary for an active deployment, aggregating response rates across cycles, and identifying deployments with elevated error or abandonment counts.

  • Reporting on response rates: compare TOTAL_NO_RESPONSES_RECD against TOTAL_NO_SENT grouped by SURVEY_ID.
  • Monitoring operational quality: filter on TOTAL_NO_ERRORS, TOTAL_ABANDONED, or TOTAL_ABORTED exceeding thresholds.
  • Status tracking: join DEPLOYMENT_STATUS and SURVEY_STATUS to the master survey tables to report outstanding or closed deployments.
  • Temporal analysis: use REFRESH_DATE to identify stale summaries that require recalculation.

A representative query joins the table to IES_SVY_SURVEYS_ALL on SURVEY_ID and filters on DEPLOYMENT_STATUS to produce a current status report. Applications should scope queries by SECURITY_GROUP_ID to respect multi-tenant security, and exclude rows where F_DELETEDFLAG is set.

Related Objects

The following objects are directly connected through the documented foreign key and primary key relationships:

  • IES_SVY_SURVEYS_ALL — referenced via SURVEY_ID; holds the survey definition master data.
  • IES_SVY_CYCLES_ALL — referenced via SURVEY_CYCLE_ID; defines the scheduling cycle for each survey.
  • IES_SVY_DEPLYMENTS_ALL — referenced via SURVEY_DEPLOYMENT_ID; holds the operational deployment record.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; enforces the EBS multi-tenant security model.
  • IES_SVY_SUMMARY_STATS_PK — the primary key constraint enforcing uniqueness of the composite identifier.

Because the table depends on three master tables, any deletion or status change in a survey, cycle, or deployment record can directly affect the integrity and interpretation of the summary statistics stored here.