Search Results pea_object_version_number

Overview

HRU_JP_CREATE_EDUC_ADD is a Japanese-localization view owned by the APPS schema in Oracle E-Business Suite, classified under the PER (Human Resources) product family. In both 12.1.1 and 12.2.2 the view is reported with a VALID status and is documented in ETRM as a placeholder-style construct rather than a true reporting data source.

The defining characteristic of this view is that every column is projected as a literal NULL. Columns such as HIRE_DATE, PERSON_ID, ASSIGNMENT_ID, PER_OBJECT_VERSION_NUMBER, PEA_DATE_FROM and REQUEST_ID carry no data — they exist only to publish a stable column signature. The view is therefore best understood as a structural stub used by the Japanese HR localization layer, most likely consulted during concurrent-program validation or as a compile-time dependency so that dependent objects resolve against a known column list.

The user search term pea_object_version_number maps directly to the PEA_OBJECT_VERSION_NUMBER column exposed here, alongside the related PER_OBJECT_VERSION_NUMBER, ASG_OBJECT_VERSION_NUMBER and APL_OBJECT_VERSION_NUMBER columns. These object version columns are the standard Oracle HRMS optimistic-locking tokens used to detect concurrent modification of person, assignment, applicant and assignment-extra-attribute records.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the view references exactly one base object: the DUAL synonym. This confirms the observation above — there is no join to PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, PER_PERSON_EXTRA_INFO or any other HRMS table. Because DUAL supplies a single synthetic row and all projections are NULL, the view returns exactly one row of nulls regardless of the underlying HR data.

Architecturally this places the view outside the normal HRMS date-tracked model. It relates to the real Japanese HR education/additional-information functionality only by naming convention and column shape, not by data lineage. Any expectation that querying it returns live HR records is incorrect.

Key Columns

• PER_OBJECT_VERSION_NUMBER / ASG_OBJECT_VERSION_NUMBER / APL_OBJECT_VERSION_NUMBER / PEA_OBJECT_VERSION_NUMBER — Optimistic-locking version tokens for the person, assignment, applicant and assignment-extra-info entities respectively. PEA_OBJECT_VERSION_NUMBER is the column returned by the user's search.
• PERSON_ID, ASSIGNMENT_ID, APPLICATION_ID — Primary and foreign key identifiers for the HR entities referenced by the localization screen.
• PEA_COMMENTS, PEA_DATE_FROM, PEA_DATE_TO — Descriptive and effective-dating columns for Japanese additional assignment information.
• LAST_NAME_KANA, FIRST_NAME_KANA, PREVIOUS_LAST_NAME_KANA — Phonetic (kana) name columns specific to Japanese localization.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Standard concurrent-manager audit columns.
• PER_ATTRIBUTE1 through PER_ATTRIBUTE30 — Descriptive flexfield segments carried for the person entity.

All of the above are defined but always NULL at runtime.

Common Use Cases and Queries

Because the view is a null-projection stub over DUAL, it should not be used as a reporting source. Typical usage is diagnostic: verifying that the object exists and is valid in the APPS schema, or inspecting its column signature when troubleshooting a dependent object that fails to compile.

To confirm presence and validity:

SELECT object_name, object_type, status
FROM   all_objects
WHERE  object_name = 'HRU_JP_CREATE_EDUC_ADD';

To inspect the exposed columns, including the object version token sought:

SELECT column_name, data_type, nullable
FROM   all_tab_columns
WHERE  table_name = 'HRU_JP_CREATE_EDUC_ADD'
ORDER  BY column_id;

To confirm that no data is returned (the expected result):

SELECT pea_object_version_number, person_id, assignment_id
FROM   apps.hru_jp_create_educ_add;

For genuine Japanese HR education and additional-information reporting, query the underlying HRMS base tables or the functional Japanese localization views instead. HRU_JP_CREATE_EDUC_ADD should be treated strictly as a structural placeholder that guarantees the PEA_OBJECT_VERSION_NUMBER and its sibling version columns remain resolvable across 12.1.1 and 12.2.2.