Results for “per_position_info_types”

50+ results




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

Overview

PER_POSITION_INFO_TYPES is a Human Resources (PER) configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2 that defines the catalog of extra information types available for association with positions. It functions as a reference or lookup entity: rather than holding position-specific descriptive data itself, it declares which categories of supplemental information may be captured against a position, and the rules under which that information is entered. Downstream transactional data is held in PER_POSITION_EXTRA_INFO, which references this table through its INFORMATION_TYPE foreign key.

From a Data Vault modeling perspective, the mined relationship structure classifies this object as hub-leaning. Its role is that of a durable business entity keyed by information type, with descriptive and control attributes absorbed into the same structure rather than fully normalized into a separate satellite. This classification is a heuristic suggestion drawn from foreign key topology and should be treated as a modeling guideline, not a functional definition.

Key Information Stored

The table is documented with sixteen columns in the ETRM 12.2.2 physical schema. The most significant are:

  • INFORMATION_TYPE — the primary business identifier and the sole column of the PER_POSITION_INFO_TYPES_PK unique index in the base (non-editioned) definition; it is also the target of the foreign key from PER_POSITION_EXTRA_INFO. This is the value positions are tagged with.
  • ACTIVE_INACTIVE_FLAG — controls whether the information type remains available for selection when users enter position extra information.
  • MULTIPLE_OCCURENCES_FLAG — governs whether more than one value of this information type may be recorded for a single position.
  • DESCRIPTION — the user-facing name or explanation of the information type.
  • LEGISLATION_CODE — scopes the information type to a specific legislative or country context.
  • OBJECT_VERSION_NUMBER — supports optimistic locking for concurrent updates.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the standard EBS WHO audit columns.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns recording the request that created or modified the row.
  • ZD_EDITION_NAME — the editioning attribute appearing in the 12.2.2 unique index PER_POSITION_INFO_TYPES_PK (INFORMATION_TYPE, ZD_EDITION_NAME); it is absent from the 12.1.1 definition and is central to how the table behaves under online patching.

No separate surrogate key is documented; INFORMATION_TYPE is the business-key candidate, with ZD_EDITION_NAME acting as the edition discriminator in 12.2.2.

Common Use Cases and Queries

Typical uses include reporting all active position information types for a given legislation, validating configuration before loading position data, and joining configuration to captured values for a position audit report. A representative query joining the catalog to the transaction table:

  • SELECT pit.INFORMATION_TYPE, pit.DESCRIPTION, pit.MULTIPLE_OCCURENCES_FLAG, pei.POSITION_ID, pei.INFORMATION_TYPE value FROM PER_POSITION_INFO_TYPES pit, PER_POSITION_EXTRA_INFO pei WHERE pit.INFORMATION_TYPE = pei.INFORMATION_TYPE AND pit.ACTIVE_INACTIVE_FLAG = 'Y' AND pit.LEGISLATION_CODE = :p_legislation;
  • SELECT INFORMATION_TYPE, DESCRIPTION, ACTIVE_INACTIVE_FLAG FROM PER_POSITION_INFO_TYPES WHERE ACTIVE_INACTIVE_FLAG = 'Y' ORDER BY DESCRIPTION;

In 12.2.2 online patching environments, queries must respect the editioning view; ZD_EDITION_NAME filters are applied by the editioning layer rather than written explicitly by end users.

Related Objects

  • PER_POSITION_EXTRA_INFO — the principal dependent table; its INFORMATION_TYPE column carries the foreign key to PER_POSITION_INFO_TYPES.INFORMATION_TYPE.
  • PER_POSITION_INFO_TYPES_PK — the primary key unique index (INFORMATION_TYPE in 12.1.1; INFORMATION_TYPE plus ZD_EDITION_NAME in 12.2.2).
  • PER_POSITIONS — the parent position entity whose extra information is governed by these types.
  • FND_LOOKUP_VALUES — commonly used alongside for related validation lookups (active/inactive flags, legislation).
  • HR_LOOKUPS — the HR lookup repository referenced by legislation and similar coded values.
  • Position extra information entry pages in the PER module consume this catalog at runtime to render available fields and enforce the multiple-occurrence rule.