Results for “igs_pe_src_types”

39 results




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

Overview

IGS_PE_SRC_TYPES is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGS — Student System product family. Its documented description is "Person source types." The view exposes the catalogue of person (prospect, applicant, or student) source types used to classify how a person first entered the institution's recruiting and admissions pipeline — for example, a web enquiry, a recruitment fair, a referral, or an agency submission. In EBS 12.1.1 and 12.2.2 the object is listed with a status of VALID and is deployed in the standard APPS schema alongside the underlying IGS_PE_SRC_TYPES_ALL table.

The view is significant because it applies a Multi-Org (organization) security predicate at runtime. Rather than exposing every source-type definition across all operating units, it filters rows to the operating unit implied by the session's CLIENT_INFO value. This makes it suitable for institution-facing reports, LOV (list of values) queries, and integrations that must respect the active organization context without the developer having to write the operating-unit predicate by hand.

Underlying Base Objects

Although the ETRM metadata records no referenced base objects, the documented view text makes the dependency explicit. The view is defined over a single base table:

  • IGS_PE_SRC_TYPES_ALL — the multi-org ("_ALL") table that stores the source-type setup rows for every operating unit. All columns exposed by the view map one-to-one to columns of this table, with no joins to other IGS tables.

The WHERE clause is the standard EBS Multi-Org filter pattern: it compares the base table's ORG_ID against the current operating unit derived from USERENV('CLIENT_INFO'), using the NVL/DECODE construction and a sentinel value of -99. Rows whose ORG_ID matches the active operating unit are returned; the sentinel supports globally defined (org-independent) rows. Because the view is a thin projection, any change made to the setup table — end-dating a source type, adding a new enquiry source, or changing a funnel status — is immediately visible through the view.

Key Columns

The view exposes 21 columns. The most relevant for reporting and integration are:

Common Use Cases and Queries

Typical scenarios include validating source-type values in prospect and applicant interfaces, populating LOVs on enquiry forms, and reconciling recruiting activity by source.

SELECT source_type, description
FROM   igs_pe_src_types
WHERE  closed_ind = 'N'
ORDER BY source_type;
SELECT source_type_id,
       source_type,
       description,
       admission_cat,
       person_type_code,
       funnel_status,
       enquiry_source_type
FROM   igs_pe_src_types
WHERE  org_id = :p_org_id;

SELECT COUNT(*) AS active_source_types
FROM   igs_pe_src_types
WHERE  closed_ind = 'N';

Because the Multi-Org predicate is embedded in the view definition, queries inherit operating-unit security automatically in EBS 12.1.1 and 12.2.2; developers must therefore set the correct operating-unit context (via FND_CLIENT_INFO) before running reports that depend on this view.