Search Results interest_status




Overview
Explore in AI Chat

Overview

AS_INTEREST_STATUSES_ACTIVE_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AS (Sales Foundation) product family. As its name and the ETRM description ("Active interest statuses view") indicate, the view exposes the subset of interest status definitions that are currently enabled, joined to their lookup translations. In ETRM terminology, an "interest" represents a party's involvement in a lead, opportunity, or sales-related entity, and the interest status describes the stage or disposition of that involvement — for example active, inactive, converted, or closed. The view therefore serves as the canonical, user-friendly source for the set of interest statuses that may legitimately be assigned to an interest record at any given time.

Because it filters on ENABLED_FLAG = 'Y' and resolves the lookup meaning and description, the view is appropriate for LOV-style queries, reporting, validation logic, and integration extract routines that must avoid obsolete or disabled statuses. It is registered as VALID in the ETRM repository for both 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over two documented base objects referenced in the ETRM metadata:

  • AS_INTEREST_STATUSES (exposed as a SYNONYM) — the transactional definition table holding interest type identifiers, interest status codes, audit columns, and the ENABLED_FLAG that qualifies a status as active.
  • AS_LOOKUPS (exposed as a VIEW over the FND lookup infrastructure) — supplies the lookup MEANING and DESCRIPTION for lookup type 'INTEREST_STATUS'.

The join is an inner join on INTEREST_STATUS_CODE = ASLKP.LOOKUP_CODE, constrained by ASLKP.LOOKUP_TYPE = 'INTEREST_STATUS' and ISTAT.ENABLED_FLAG = 'Y'. Consequently, only statuses that are both enabled in AS_INTEREST_STATUSES and present in the seeded 'INTEREST_STATUS' lookup set are returned. A status defined in the base table but missing from the lookup type will not appear.

Key Columns

  • INTEREST_TYPE_ID — identifier of the interest type to which the status applies; supports statuses scoped per interest type.
  • INTEREST_STATUS_CODE — the internal code used for storage and foreign-key references.
  • INTEREST_STATUS — the translatable lookup MEANING, suitable for display in reports and user interfaces.
  • DESCRIPTION — the lookup description providing additional context for the status.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns inherited from the base table, useful for change tracking and data lineage.

Common Use Cases and Queries

Typical scenarios include populating status LOVs in custom forms or OAF pages, building ETRM reports of assignable statuses, and validating inbound status codes during data migration or interface loads.

Listing all active statuses with their display text:

  • SELECT interest_type_id, interest_status_code, interest_status, description FROM apps.as_interest_statuses_active_v ORDER BY interest_status;

Restricting to a specific interest type:

  • SELECT interest_status_code, interest_status FROM apps.as_interest_statuses_active_v WHERE interest_type_id = :p_interest_type_id;

Validating that a supplied code is active before assignment:

  • SELECT COUNT(*) FROM apps.as_interest_statuses_active_v WHERE interest_status_code = :p_code AND interest_type_id = :p_type_id;

Because the view already enforces the enabled and lookup constraints, querying it directly avoids duplicating that logic in downstream SQL and ensures consistency across ETRM reporting and integration routines.