Search Results get_work_class_rec

Overview

HZ_PERSON_INFO_V2PUB is a public PL/SQL API package owned by the APPS schema in Oracle E-Business Suite, classified as a public (PUB) API within Oracle Trading Community Architecture (TCA). It exposes programmatic interfaces for maintaining person-related entities associated with a party record — specifically language proficiency, citizenship, education, employment history, work classification, and personal interests. The package is documented under product code HZ, with a business entity designation of HZ_PERSON, and its reference documentation resides in the Oracle Trading Community Architecture Technical Implementation Guide (120hztig.pdf). The header comment identifies this as version 120.11, dated August 17, 2006, with the source file ARH2PISS.pls.

The package defines several PL/SQL record types — person_language_rec_type, citizenship_rec_type, education_rec_type, and employment_history_rec_type — that structure the data passed into and out of the API calls. These record types mirror the underlying TCA tables and include standard audit attributes such as created_by_module, application_id, and status.

Key Procedures and Functions

The package documents 18 public procedures and functions organized into paired create/update operations plus a retrieval function for each entity type:

• Person Language: CREATE_PERSON_LANGUAGE, UPDATE_PERSON_LANGUAGE, GET_PERSON_LANGUAGE_REC — maintain language use, native and primary language flags, and proficiency levels for reading, speaking, writing, and spoken comprehension.
• Citizenship: CREATE_CITIZENSHIP, UPDATE_CITIZENSHIP, GET_CITIZENSHIP_REC — manage citizenship records including country, recognition and disownment dates, and supporting documentation references.
• Education: CREATE_EDUCATION, UPDATE_EDUCATION, GET_EDUCATION_REC — capture degree information, course major, school attended, attendance dates, and school type.
• Employment History: CREATE_EMPLOYMENT_HISTORY, UPDATE_EMPLOYMENT_HISTORY, GET_EMPLOYMENT_HISTORY_REC — record prior and current employment details for a person party.
• Work Class: CREATE_WORK_CLASS, UPDATE_WORK_CLASS, GET_WORK_CLASS_REC — maintain work classification data.
• Person Interest: CREATE_PERSON_INTEREST, UPDATE_PERSON_INTEREST, GET_PERSON_INTEREST_REC — manage personal interest records.

The typical invocation pattern is standard for TCA V2 public APIs: the create and update procedures accept a record structure and return a newly generated or affected identifier, while the get functions return a fully populated record for a supplied primary key.

Tables Accessed

The package operates against the following tables through APPS synonyms:

• HZ_PERSON_LANGUAGE — stores language proficiency records for a party.
• HZ_CITIZENSHIP — stores citizenship records linked to a person party.
• HZ_EDUCATION — stores educational background records.
• HZ_EMPLOYMENT_HISTORY — stores employment history records.
• HZ_WORK_CLASS — stores work classification data.
• HZ_PERSON_INTEREST — stores personal interest records.
• HZ_PARTIES — the master party entity table; the person entity records maintained here are anchored to a party_id foreign key that references HZ_PARTIES.

Each child table is keyed by a surrogate identifier (for example, citizenship_id or education_id) and carries a party_id reference to the parent party record.

Usage Notes

HZ_PERSON_INFO_V2PUB is typically invoked from Oracle Forms, concurrent programs, and custom PL/SQL integrations that need to create or maintain person-level attributes in TCA without direct DML against the base tables. Using the public API ensures that TCA internal logic, including identifier generation and audit column population via created_by_module and application_id, is consistently applied.

Because the package is referenced by 11 other packages, changes to its behavior can have cascading effects; it should be treated as a shared infrastructure component. Callers must supply the party identifier for the target person and handle the API return status conventions used across TCA public APIs. Direct table manipulation is not recommended, as it bypasses the validation and audit semantics embedded in these procedures. The API is documented as active, indicating continued support across Oracle EBS 12.1.1 and 12.2.2 release lines.