Search Results update_party_records

Overview

IRC_PARTY_PERSON_UTL is an Oracle E-Business Suite iRecruitment utility package owned by the APPS schema. Its purpose is to maintain the personal and party-level records that iRecruitment relies upon when a candidate, employee, or external party registers, updates a profile, or is otherwise processed through the recruitment lifecycle. The package header carries the identifier irptpeul.pkh 120.0, dated 2005, indicating that it is an older but retained component of the iRecruitment data model. It is declared with AUTHID CURRENT_USER, so its SQL and PL/SQL statements execute with the privileges of the calling schema rather than as a definer-rights package.

The "party person" naming reflects the Oracle Trading Community Architecture (TCA) foundation: the procedures propagate and reconcile attribute changes across the HZ_PARTIES and HZ_PERSON_PROFILES entities alongside the person records maintained in the HR/PER tables. In practical terms, the package serves as the maintenance layer that keeps iRecruitment party records consistent with the underlying person data model.

Key Procedures and Functions

ETRM documents two public procedures in this package:

• UPDATE_PARTY_RECORDS — Accepts a p_mode parameter defaulting to the string 'BASIC'. This procedure performs the synchronous maintenance of party and person records. The mode argument allows the caller to select the scope or depth of the update, with BASIC representing the default processing path.
• UPDATE_PARTY_CONC — The concurrent-program entry point. It exposes the standard Oracle concurrent manager signature with errbuf and retcode OUT parameters, allowing the procedure to be registered and executed as a concurrent program and to report success or failure back to the concurrent manager.

No other functions or procedures are documented for this package. Note that the object the user searched for, update_party_conc, corresponds to the concurrent wrapper procedure UPDATE_PARTY_CONC described above. Parameter lists beyond those shown in the package header are not enumerated in the available metadata and should not be assumed.

Tables Accessed

The documented table references span the TCA, HR, and iRecruitment data models:

• TCA/person tables — HZ_PARTIES and HZ_PERSON_PROFILES, the core party and person profile entities that the update procedures reconcile.
• HR person tables — PER_ALL_PEOPLE_F, PER_ADDRESSES, PER_COMPETENCE_ELEMENTS, and PER_ESTABLISHMENT_ATTENDANCES, providing the person, address, competency, and establishment data that feed the party records.
• Organization and user tables — HR_ORGANIZATION_INFORMATION and FND_USER, used to resolve the organization and application user context.
• iRecruitment tables — IRC_DOCUMENTS, IRC_JOB_BASKET_ITEMS, IRC_NOTIFICATION_PREFERENCES and IRC_NOTIFICATION_PREFS_S, IRC_SEARCH_CRITERIA and IRC_SEARCH_CRITERIA_S, and IRC_VACANCY_CONSIDERATIONS, covering documents, job baskets, notification preferences, saved search criteria, and vacancy consideration records tied to the party.

Usage Notes

Because UPDATE_PARTY_CONC conforms to the concurrent manager calling convention, it is most likely registered as a concurrent program and scheduled by administrators rather than called interactively. UPDATE_PARTY_RECORDS is the callable API for synchronous updates and may be invoked from iRecruitment forms, from other PL/SQL routines, or from custom code where an immediate party data refresh is required. The package is referenced by zero other packages according to the metadata, so it operates largely as a leaf-level maintenance utility rather than as a shared internal API. Customizations should call the documented procedures only, respect the default 'BASIC' mode unless a supported alternative is confirmed, and be aware that the AUTHID CURRENT_USER declaration means the executing user must hold the necessary privileges on the referenced tables.