Results for “hr_location_info_types”

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

Overview

HR_LOCATION_INFO_TYPES is a Human Resources (PER) reference table that defines the catalog of extra information attributes that may be captured against a Location in Oracle E-Business Suite. Its ETRM description states that it holds the "types of extra information that may be held against a Location." In effect, it is the definitional or setup layer of the location flexfield-style extra information framework: rather than storing the values themselves, it specifies which descriptive attributes exist, whether they are currently usable, whether more than one value may be recorded, and the legislative context in which they apply.

The table is owned by the HR schema and is documented as VALID in both the 12.1.1 and 12.2.2 releases. The physical schema documented in ETRM 12.2.2 records sixteen columns. Under the heuristic Data Vault classification mined from the foreign-key structure, HR_LOCATION_INFO_TYPES is characterized as hub-leaning. This classification is a modeling suggestion only: the table behaves as a durable, business-key-driven entity whose primary identifier is referenced by dependent tables, rather than as a transactional satellite or an associative link.

Key Information Stored

The documented primary key, HR_LOCATION_INFO_TYPES_PK, is defined over INFORMATION_TYPE (with ZD_EDITION_NAME in the 12.2.2 edition-aware unique index). INFORMATION_TYPE is therefore both the surrogate/primary identifier and the business-key candidate for this table — the value that dependent records carry to identify which information type they describe.

The most significant descriptive and control columns are:

• INFORMATION_TYPE — the primary key and business identifier of the information type.
• DESCRIPTION — the user-facing name of the extra information attribute.
• ACTIVE_INACTIVE_FLAG — controls whether the information type is available for use against locations.
• MULTIPLE_OCCURENCES_FLAG — indicates whether more than one value may be held for the type against a single location.
• LEGISLATION_CODE — restricts the information type to a specific legislative/regulatory context.
• ZD_EDITION_NAME — the editioning column supporting Online Patching and edition-based redefinition in 12.2.2.
• OBJECT_VERSION_NUMBER — the optimistic locking token used by the HR APIs and forms.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit Who columns.
• CREATED_BY, CREATION_DATE — standard creation audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program / DML context columns identifying the request that last updated the row.

Common Use Cases and Queries

Typical usage includes listing the available location extra information types for setup validation, driving LOVs for the Location Extra Information form, and joining the active definitions to the actual data rows in HR_LOCATION_EXTRA_INFO for reporting.

Querying active, legislatively appropriate information types: SELECT information_type, description FROM hr.hr_location_info_types WHERE active_inactive_flag = 'Y';

Joining definitions to stored values for a location: SELECT t.description, e.location_id, e.information_type FROM hr.hr_location_info_types t, hr.hr_location_extra_info e WHERE e.information_type = t.information_type AND e.location_id = :p_location_id;

Filtering by legislation: SELECT information_type, description FROM hr.hr_location_info_types WHERE legislation_code = :p_legislation_code AND active_inactive_flag = 'Y';

Because the table is a setup/reference object, it is frequently reported alongside HR_LOCATIONS and HR_LOCATION_EXTRA_INFO in extracts and data-conversion validation scripts.

Related Objects

• HR_LOCATION_EXTRA_INFO — the dependent child table; join column HR_LOCATION_EXTRA_INFO.INFORMATION_TYPE references HR_LOCATION_INFO_TYPES.INFORMATION_TYPE. This is the documented foreign key relationship.
• HR_LOCATIONS — the parent location entity whose extra information is governed by these types (through the extra-information records).
• HR_LOCATION_INFO_TYPES_PK — the documented primary key / unique index on INFORMATION_TYPE (and ZD_EDITION_NAME), the authoritative business key.
• HR_LOCATION_EXTRA_INFO APIs and forms, such as the Location Extra Information maintenance UI, which read this table to render and validate available types.
• HR_LOCATIONS_ALL and related location views, used in conjunction with this table in reporting joins.

These relationships confirm the hub-leaning role of HR_LOCATION_INFO_TYPES as the stable definitional entity that subordinate extra-information records reference.