Search Results per_assignment_info_types




Overview
Explore in AI Chat

Overview

PER_ASSIGNMENT_INFO_TYPES is an HR schema table in Oracle E-Business Suite 12.1.1 and 12.2.2 that defines the catalog of extra information types which may be stored against an assignment record. It is a setup or reference table: each row describes one category of supplemental assignment data (for example, a specific descriptive flexfield-style attribute group) that the application may then capture for a given assignment. The table itself holds no transactional assignment data; it holds the metadata that governs what supplemental information is permitted, and how that information behaves.

Within the PER (Human Resources) product, this table acts as the authoritative list of assignment-level information types. Downstream transactional values are stored in PER_ASSIGNMENT_EXTRA_INFO, which references a valid INFORMATION_TYPE. The documented relationship structure — a single primary key on INFORMATION_TYPE with PER_ASSIGNMENT_EXTRA_INFO pointing to it — suggests a hub-leaning Data Vault classification. In a dimensional or Data Vault model, this table would typically be modeled as a reference or hub entity, while the dependent extra-info table would function as a satellite or link capturing occurrence-level detail.

Key Information Stored

The table is documented with 16 columns. The most significant are:

  • INFORMATION_TYPE — the primary identifier and business key of each information type. It forms the leading column of the primary key PER_ASSIGNMENT_INFO_TYPES_PK and of the unique index PER_ASSIGNMENT_INFO_TYPES_PK (INFORMATION_TYPE, ZD_EDITION_NAME).
  • ZD_EDITION_NAME — the editioning column introduced with the 12.2 online patching architecture (E-Business Suite Editioning). Combined with INFORMATION_TYPE it forms the unique business key. In 12.1.1 this concept does not exist, so cross-release queries must account for its presence only in 12.2.x.
  • ACTIVE_INACTIVE_FLAG — indicates whether the information type is currently active and therefore selectable when capturing assignment data.
  • MULTIPLE_OCCURENCES_FLAG — governs whether multiple occurrences of the information type may be recorded against a single assignment.
  • DESCRIPTION — the user-facing name or description of the information type.
  • LEGISLATION_CODE — ties the information type to a specific legislative/regulatory context, enabling country-specific assignment information.

The remaining columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) are the standard concurrent-program audit columns, while LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY, and OBJECT_VERSION_NUMBER support the WHO-column auditing and optimistic locking conventions used throughout EBS.

Common Use Cases and Queries

Typical usage includes validating which assignment information types are active, driving LOVs on assignment entry forms, and generating listings of available supplemental assignment attributes. A simple active-types query is:

SELECT information_type, description, legislation_code
FROM   hr.per_assignment_info_types
WHERE  active_inactive_flag = 'Y';

To identify which information types are actually in use against assignments, join to the dependent detail table:

SELECT t.information_type, t.description, COUNT(e.*)
FROM   hr.per_assignment_info_types t,
       hr.per_assignment_extra_info e
WHERE  e.information_type = t.information_type
GROUP  BY t.information_type, t.description;

Reporting scenarios include auditing which information types are enabled per legislation, and reconciling setup between environments by comparing rows across instances. On 12.2.x, queries intended to run in a specific edition should filter on ZD_EDITION_NAME.

Related Objects

The most significant dependent object is PER_ASSIGNMENT_EXTRA_INFO, which stores the actual extra-information values and references this table via PER_ASSIGNMENT_EXTRA_INFO.INFORMATION_TYPE. Other relevant objects include the PER assignment base tables PER_ALL_ASSIGNMENTS_F and PER_ASSIGNMENTS_F, which the extra information augments; the associated API layer in the HR/POS packages used to validate and write assignment extra information; and the standard concurrent-program audit objects referenced by REQUEST_ID and PROGRAM_ID. Because this is a reference table, its chief dependency is inbound: applications and descriptive information setups look up valid INFORMATION_TYPE values before allowing assignment data to be captured.