Results for “context_name”

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

Overview

PER_INFO_TYPES_V is an APPS-owned database view within the Oracle E-Business Suite Human Resources (PER) product family. Its documented purpose in Oracle ETRM is to support the user interface, meaning it exists primarily as a lookup and enumeration mechanism rather than as a transactional or analytical object in its own right. The view consolidates the "information type" definitions that are scattered across the many descriptive flexfield contexts configured throughout Oracle HRMS and related modules.

In EBS, information types (also called "extra information types" or EITs) are the mechanism by which administrators extend standard HR entities — people, assignments, positions, jobs, locations, contacts, and others — with customer-specific attributes. Each information type is stored as a row in a dedicated base table per entity, keyed by information type name and legislation. PER_INFO_TYPES_V provides a single, unified projection of the active information types across all of these tables, which is why it is well suited to supporting LOVs, flexfield context validation, and administrative setup screens.

Because the view filters each branch on ACTIVE_INACTIVE_FLAG = 'Y', it exposes only currently enabled information types. This makes it a reliable source for validation logic and for any reporting requirement that needs to confirm a given information type is still in use.

Underlying Base Objects

The documented view text defines PER_INFO_TYPES_V as a series of UNION operations over ten base information-type tables, each of which is exposed in APPS through a synonym:

• PER_PEOPLE_INFO_TYPES — person-level information types
• PER_POSITION_INFO_TYPES — position-level information types
• PER_ASSIGNMENT_INFO_TYPES — assignment-level information types
• HR_LOCATION_INFO_TYPES — location-level information types
• PER_JOB_INFO_TYPES — job-level information types
• GHR_PA_REQUEST_INFO_TYPES — public-sector/PA request information types
• PAY_ELEMENT_TYPE_INFO_TYPES — payroll element type information types
• PER_PREV_JOB_INFO_TYPES — previous job information types
• PER_CONTACT_INFO_TYPES — contact information types
• PQH_ROLE_INFO_TYPES — role information types (Public Sector/HR Foundation)

ETRM also lists additional referenced base objects used by the broader information-type framework, including BEN_ABR_INFO_TYPES, BEN_ELP_INFO_TYPES, BEN_LER_INFO_TYPES, BEN_OPT_INFO_TYPES, BEN_PGM_INFO_TYPES, BEN_PL_INFO_TYPES, PQP_VEH_ALLOC_INFO_TYPES and PQP_VEH_REPOS_INFO_TYPES (Benefits and Payroll/Vehicle), together with the FND_DESCR_FLEX_CONTEXTS_VL view and the HR_DOCUMENT_TYPES_V view, and the HR_API package. Each UNION branch contributes a literal string identifying the originating table, the information type name, and the legislation code.

Key Columns

• TABLE_NAME — A literal identifier naming the source information-type table for the row (for example, 'PER_PEOPLE_INFO_TYPES'). It indicates which HR entity the information type applies to and is the principal row discriminator in the UNION.
• INFORMATION_TYPE — The name of the information type (EIT) as defined in the source table. This is the value users select when attaching extra information to a record.
• LEGISLATION_CODE — The legislation (country) under which the information type is available. A null or specific value here determines whether the EIT applies globally or only to a particular legislative context.

Common Use Cases and Queries

Typical use is to enumerate the active information types available for a given entity, to drive selection lists, or to validate configuration during upgrades and audits.

List all active information types for people:

• SELECT information_type, legislation_code FROM per_info_types_v WHERE table_name = 'PER_PEOPLE_INFO_TYPES';

Count active information types per source entity:

• SELECT table_name, COUNT(*) FROM per_info_types_v GROUP BY table_name ORDER BY 1;

Find a specific EIT and the entity it belongs to:

• SELECT table_name, legislation_code FROM per_info_types_v WHERE information_type = 'MY_EIT_NAME';

Because the view joins only lightweight master tables and applies an active-flag filter, queries against it are inexpensive and safe for interactive reporting. It should not be used for transactional reporting, since it carries no effective dates or assignment-specific data.