Results for “igs_co_addr_type”

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

Overview

The view IGS_CO_ADDR_TYPE is a reporting and integration object belonging to the IGS — Student System product family in Oracle E-Business Suite. It exposes a filtered, decoded list of address type lookup values used within the Student System's party and address management model. Rather than storing data of its own, the view presents a formatted projection of Oracle's standard lookup infrastructure, translating internal lookup codes and enabled flags into a business-friendly result set suitable for display, validation, and downstream integration.

A defining characteristic of this object is its status. As reflected in the ETRM documentation, IGS_CO_ADDR_TYPE is marked as Obsolete and is documented as Not implemented in this database. Consequently, it has no owner and no documented referenced base objects in the 12.2.2 metadata. This indicates that the view is a legacy artifact associated with the deprecated IGS Student System, and that in a standard 12.1.1 or 12.2.2 installation the definition may be absent entirely. Any reliance on this object should therefore be treated as a migration or remediation concern rather than a supported integration point.

Underlying Base Objects

Although the metadata records no referenced base objects, the documented view text establishes that IGS_CO_ADDR_TYPE is defined over a single underlying base object: FND_LOOKUP_VALUES, the core Oracle Application Object Library table that stores all extensible lookup codes and their translations across applications.

The relationship to FND_LOOKUP_VALUES is highly selective. The view does not expose the entire lookup table; it restricts results to rows where LOOKUP_TYPE = 'PARTY_SITE_USE_CODE', VIEW_APPLICATION_ID = 222, SECURITY_GROUP_ID = 0, and the language matches the current session language via USERENV('LANG'). The application filter (222) ties the rows to the owning application context, while the security group and language predicates confine output to the active, user-facing lookup set. In effect, the view is a constrained, application-specific slice of a shared reference data table.

Key Columns

The view exposes three derived columns, each produced through aliasing or DECODE logic:

• ADDR_TYPE — Sourced from LOOKUP_CODE. This is the stored, coded identifier for the address type (for example, a site-use code representing home, mailing, or work address categories). It is the value typically used in joins and programmatic comparisons.
• DESCRIPTION — Sourced from MEANING. This is the translatable, human-readable label presented to end users. Because the view filters on the session language, DESCRIPTION reflects the appropriate language-specific meaning.
• CLOSED_IND — Derived from a DECODE on ENABLED_FLAG. The logic inverts the enabled flag: an enabled lookup ('Y') yields 'N', and a disabled lookup ('N') yields 'Y'. The column therefore signals whether the address type has been closed (disabled) for use, with 'Y' indicating closed and 'N' indicating open. This inversion is a key behavioral detail, since the underlying flag semantics are reversed in the output.

Common Use Cases and Queries

In legacy IGS deployments, this view supported Student System screens and concurrent programs that needed a clean list of address types with a human-readable description and an open/closed indicator. Typical usage included populating address-type list of values, driving validation logic, and feeding integration extracts in which downstream systems expected a decoded rather than coded representation.

A representative query retrieves only active address types, exploiting the CLOSED_IND convention:

• SELECT addr_type, description FROM igs_co_addr_type WHERE closed_ind = 'N' ORDER BY description;
• SELECT addr_type, description, closed_ind FROM igs_co_addr_type ORDER BY 1;
• SELECT addr_type FROM igs_co_addr_type WHERE addr_type = :p_addr_type; — for validation lookups.

Because the object is obsolete and may not exist, the recommended replacement is to query FND_LOOKUP_VALUES directly with an equivalent predicate on LOOKUP_TYPE = 'PARTY_SITE_USE_CODE', reproducing the language and application filters and applying the same enabled-flag inversion in the select list. This preserves behavior while removing dependency on a non-implemented, unsupported artifact.