Results for “rei_attribute_category”

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

Overview

GHR_PA_REQUEST_EXTRA_INFO is a table owned by the HR schema within the Oracle E-Business Suite product GHR — US Federal Human Resources. Its documented purpose is to store additional information based on information types, functioning as an extension mechanism for the parent personnel action request records held in GHR_PA_REQUESTS. Rather than hard-coding each possible data element onto the main request header, the application models extensible, information-type-specific detail in this child table, allowing the same request to carry different attribute sets depending on the category of supplemental data being captured.

From a data modeling perspective, the metadata’s heuristic Data Vault classification identifies this object as a link. That classification is a suggestion rather than a normative statement: the table’s structure — a surrogate primary key plus foreign keys to two distinct parent entities (the personnel action request and the information type definition) — is characteristic of a link-style association that connects a request to its information type context while carrying descriptive payload. Analysts designing a Data Vault or dimensional representation of this subject area should treat GHR_PA_REQUEST_EXTRA_INFO as the bridge between requests and information type definitions, with the attribute and information columns acting as dependent descriptive data.

Key Information Stored

The table contains 65 documented columns. The most operationally significant are described below; the remainder are largely the generic descriptive flexfield, who-columns, and concurrency-control fields that follow standard Oracle EBS conventions.

• PA_REQUEST_EXTRA_INFO_ID — the surrogate primary key, defined by the unique index GHR_PA_REQUEST_EXTRA_INFO_PK. This is the single documented business-key candidate for uniqueness within the table.
• PA_REQUEST_ID — foreign key to GHR_PA_REQUESTS, identifying the personnel action request to which this supplemental record belongs.
• INFORMATION_TYPE — foreign key to GHR_PA_REQUEST_INFO_TYPES, defining the type classification that governs how the remaining columns are interpreted.
• REI_ATTRIBUTE_CATEGORY and REI_ATTRIBUTE1 through REI_ATTRIBUTE20 — a descriptive flexfield segment set that stores information-type-dependent attribute values in a generic, normalized fashion.
• REI_INFORMATION_CATEGORY and REI_INFORMATION1 through REI_INFORMATION30 — a second, larger generic information segment set providing additional per-type data storage.
• OBJECT_VERSION_NUMBER — the standard optimistic-locking column used by the Oracle Application Framework (OAF) and related UI layers to detect concurrent updates.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — the standard concurrent program context columns that record which concurrent request created or last modified the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the standard audit who-columns maintained automatically by the EBS framework.

Common Use Cases and Queries

Typical reporting and integration scenarios retrieve the supplemental detail for a given personnel action request, or aggregate all supplemental records for a particular information type. A straightforward join pattern is:

• Joining GHR_PA_REQUESTS to GHR_PA_REQUEST_EXTRA_INFO on PA_REQUEST_ID to produce a complete request picture with its supplemental information.
• Joining to GHR_PA_REQUEST_INFO_TYPES on INFORMATION_TYPE to resolve the human-readable name and definition of the information type governing the record.
• Filtering on INFORMATION_TYPE to extract only the attribute population relevant to a specific business process.
• Correlating REQUEST_ID and PROGRAM_ID with concurrent program definitions to trace how a row was populated.
• Auditing changes over time using LAST_UPDATE_DATE, LAST_UPDATED_BY, and CREATION_DATE for SOX or federal compliance reporting.

Because the attribute and information segments are generic, any extraction should always be conditioned by INFORMATION_TYPE; the meaning of REI_INFORMATION1 or REI_ATTRIBUTE3 is defined by the information type, not by the column itself.

Related Objects

• GHR_PA_REQUESTS — parent table; joined on GHR_PA_REQUEST_EXTRA_INFO.PA_REQUEST_ID = GHR_PA_REQUESTS.PA_REQUEST_ID.
• GHR_PA_REQUEST_INFO_TYPES — lookup table defining valid information types; joined on GHR_PA_REQUEST_EXTRA_INFO.INFORMATION_TYPE = GHR_PA_REQUEST_INFO_TYPES.INFORMATION_TYPE.
• GHR_PA_REQUEST_EXTRA_INFO_PK — the unique index on PA_REQUEST_EXTRA_INFO_ID that enforces row uniqueness and supports primary key lookups.
• FND_CONCURRENT_REQUESTS — referenced indirectly via REQUEST_ID and PROGRAM_APPLICATION_ID / PROGRAM_ID for concurrent program traceability.
• FND_APPLICATION and FND_CONCURRENT_PROGRAMS — standard joins for resolving PROGRAM_APPLICATION_ID and PROGRAM_ID to meaningful program names.
• PER_ALL_PEOPLE_F — commonly joined through the request’s subject person for federal HR reporting across personnel action requests and their supplemental detail.

Together these relationships position GHR_PA_REQUEST_EXTRA_INFO as the extensible detail layer of the personnel action request model in Oracle EBS Federal Human Resources, supporting both transactional data entry and downstream reporting against information-type-specific attributes.