Results for “locvenue_use_id”

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

Overview

The view APPS.IGS_PE_LOCVENUE_USE_V belongs to the IGS (Student System) product family within Oracle E-Business Suite, and is valid in both 12.1.1 and 12.2.2. It presents location-venue usage records together with their decoded lookup meaning, joining the base transaction table IGS_PE_LOCVENUE_USE to the Oracle Application Object Library lookup repository FND_LOOKUP_VALUES. Its primary reporting and integration role is to expose the site-use classification of a location or venue in a human-readable form, translating the raw SITE_USE_CODE into its descriptive MEANING for a given runtime language. This makes the view a convenient source for concurrent programs, OAF pages, BI Publisher reports, and interface extracts that need venue usage information without replicating the lookup decoding logic.

Underlying Base Objects

The view is defined over two documented objects joined in its SELECT text:

• IGS_PE_LOCVENUE_USE (aliased PLV) — the base entity table holding location-venue usage rows, including the site-use code, location value, and active indicator.
• FND_LOOKUP_VALUES (aliased LK) — the standard lookup values table from which the meaning of each code is derived.

The join is governed by four predicates. First, PLV.SITE_USE_CODE = LK.LOOKUP_CODE links each usage row to its lookup definition. Second, the lookup type is restricted with LK.LOOKUP_TYPE = 'PARTY_SITE_USE_CODE', which is precisely the lookup that corresponds to the term the user searched for. Third, the language is bound to the session with LK.LANGUAGE = USERENV('LANG'), ensuring the returned meaning matches the user's runtime language. Fourth, the lookup is scoped with LK.VIEW_APPLICATION_ID = 222 and LK.SECURITY_GROUP_ID = 0, tying the lookup set to the IGS application and the standard security group. Because the view is a pure decode-and-project construct, it carries no independent storage; all persistence remains in the base table.

Key Columns

• ROW_ID — the row identifier of the underlying IGS_PE_LOCVENUE_USE record.
• LOCVENUE_USE_ID — primary key of the location-venue usage entity.
• LOC_VENUE_ADDR_ID — foreign reference to the associated location or venue address.
• SITE_USE_CODE — the raw site-use classification code, and the value keyed to the PARTY_SITE_USE_CODE lookup.
• LOCATION — the descriptive location value carried on the base record.
• ACTIVE_IND — flag indicating whether the usage record is currently active.
• MEANING — the decoded, language-sensitive description of SITE_USE_CODE, sourced from FND_LOOKUP_VALUES.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle who-columns for audit and change tracking.

Common Use Cases and Queries

A frequent requirement is listing active venue usages with their decoded site-use meaning:

• SELECT locvenue_use_id, site_use_code, meaning, location FROM igs_pe_locvenue_use_v WHERE active_ind = 'Y';

To filter by a specific classification, query on the decoded meaning or the raw code:

• SELECT locvenue_use_id, site_use_code, meaning FROM igs_pe_locvenue_use_v WHERE site_use_code = :p_site_use_code;

Because MEANING is resolved against USERENV('LANG'), the same query returns localized descriptions in each user's session language, which suits multilingual reports and integration payloads. The view also serves as a validation source for LOVs and interface extracts that must present PARTY_SITE_USE_CODE values already resolved to their display text.