Results for “per_info_type_security”

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

Overview

PER_INFO_TYPE_SECURITY is a Human Resources (PER) product table residing in the HR schema of Oracle E-Business Suite. It functions as a cross-reference (intersection) table that links Oracle EBS responsibilities to the information types those responsibilities are permitted to access or maintain. In effect, it is the configuration store for "information type security," the mechanism that determines which extra information types (EITs) or predefined information types a user sees in self-service and professional forms based on the responsibility under which the session is running.

When a user opens a person record, the application resolves the active responsibility, reads the rows in PER_INFO_TYPE_SECURITY, and filters the available information types accordingly. This makes the table a central control point for restricting or exposing HR data by responsibility rather than by user or role alone. The ETRM relationship metadata classifies this object heuristically as standalone within a Data Vault model. In practice, however, its business purpose is that of a link table joining responsibility and information type; a modeling suggestion would be to treat it as a link (or at minimum a many-to-many resolution table) rather than an independent hub.

Key Information Stored

The table contains twelve documented columns. The most significant are summarized below.

• PER_INFO_TYPE_SECURITY_ID — surrogate primary key, uniquely identifying each row and enforced by the PER_INFO_TYPE_SECURITY_PK constraint.
• APPLICATION_ID — identifies the Oracle application that owns the information type; part of the unique business key.
• RESPONSIBILITY_ID — the responsibility to which the security restriction applies; part of the unique business key and the principal join to FND_RESPONSIBILITY.
• INFO_TYPE_TABLE_NAME — the underlying table or view name on which the information type is based; part of the unique business key.
• INFORMATION_TYPE — the code or name of the information type being secured; part of the unique business key.
• OBJECT_VERSION_NUMBER — optimistic locking column used to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO (audit) columns recording the last modification.
• CREATED_BY, CREATION_DATE — standard WHO columns recording row creation.
• ZD_EDITION_NAME — editioning column introduced for Oracle's Edition-Based Redefinition (EBR), enabling online patching in Release 12.2.

The surrogate key is PER_INFO_TYPE_SECURITY_ID, while the business-key candidate is the combination of APPLICATION_ID, RESPONSIBILITY_ID, INFO_TYPE_TABLE_NAME, and INFORMATION_TYPE (plus ZD_EDITION_NAME under EBR), enforced by the PER_INFO_TYPE_SECURITY_UK unique index.

Common Use Cases and Queries

Administrators and technical consultants typically query this table to audit or troubleshoot responsibility-based information type exposure, most often when a self-service user cannot see an expected EIT.

• List all information types secured for a given responsibility:

  SELECT responsibility_id, application_id, info_type_table_name, information_type
  FROM   hr.per_info_type_security
  WHERE  responsibility_id = :resp_id;

• Identify which responsibilities can access a specific information type:

  SELECT responsibility_id
  FROM   hr.per_info_type_security
  WHERE  information_type = :info_type_code;

• Detect duplicate or missing configuration by joining to FND_RESPONSIBILITY to confirm the responsibility is valid and active.

Reporting use cases include security audits for SOX compliance, migration checks when responsibilities are cloned between environments, and troubleshooting EIT visibility during a 12.1.1 to 12.2.2 upgrade. Because ZD_EDITION_NAME is part of the unique key, queries should filter on the appropriate edition when run in an EBR-enabled Release 12.2 environment.

Related Objects

• FND_RESPONSIBILITY — joined on RESPONSIBILITY_ID to resolve responsibility names and application context.
• FND_APPLICATION — joined on APPLICATION_ID to resolve the owning application for the information type.
• PER_INFO_TYPE_USAGES and PER_INFO_TYPES — define the information types whose visibility this table governs.
• PER_EIT_CATEGORIES / EIT definitions — the extra information type metadata that INFO_TYPE_TABLE_NAME ultimately references.
• FND_RESPONSIBILITY_VL — the translatable view commonly used in listings and reports.
• PER_PERSON_TYPES — related HR setup objects whose display may also be filtered by responsibility through the same security framework.

All objects should be accessed with appropriate HR schema privileges, and any writes should respect the WHO audit columns and the OBJECT_VERSION_NUMBER optimistic-locking convention.