Search Results get_contact_relationship_tt

Overview

HR_PROCESS_CONTACT_SS is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the contact management flow within Oracle HRMS. It is classified as an "OTHER" API in the ETRM repository and is primarily associated with the contact creation, update, and end-dating user interface flow. The package coordinates the business logic behind processing contact relationship transactions, including validation, persistence, and invocation of the underlying public contact APIs. It relies on the HR_API_TRANSACTION_STEPS and HR_API_TRANSACTION_VALUES framework, which suggests it operates as a server-side controller that either processes transaction payloads directly or hands them to the standard PER contact APIs for execution. The package carries the AUTHID CURRENT_USER directive, meaning it executes with the privileges of the calling user rather than as definer-rights code. This design ties the package to session-level context and reinforces its role as an internal helper for the contacts UI rather than a freely callable public API.

Key Procedures and Functions

The documented procedures and functions span the full lifecycle of a contact relationship change.

• GET_CONTACT_RELATIONSHIP_TT, GET_CONTACT_FROM_TT, GET_CONTACT_REGIONS_STATUS_TT — retrieve transaction data saved earlier in the current transaction, typically when a user navigates back from a Review page to an Update page.
• UPDATE_CONTACT_RELATIONSHIP, CREATE_CONTACT_TT, END_CONTACT_RELATIONSHIP — perform the core create, update, and end-date operations on contact relationship records.
• PROCESS_API and PROCESS_END_API — orchestrate the transaction processing, with PROCESS_END_API specifically handling the end-dating of a contact relationship.
• PROCESS_CREATE_CONTACT_API, CALL_CONTACT_API — wrap and invoke the standard PER contact APIs.
• IS_ADDRESS_UPDATED, IS_REC_CHANGED, IS_CON_REC_CHANGED, IS_CONTACT_ADDED — status and change-detection functions used to determine whether data has been modified.
• SAVE_FOR_LATER_VALIDATION, DELETE_TRANSACTION_STEPS, UPDATE_OBJECT_VERSION, VALIDATE_REL_START_DATE — handle transaction persistence, cleanup, concurrency control, and date validation.
• CHECK_NI_UNIQUE, GET_EMRG_REL_ID — enforce uniqueness constraints and retrieve emergency relationship identifiers.

Tables Accessed

• PER_CONTACT_RELATIONSHIPS — the primary table holding contact relationship records.
• PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F — person and assignment data for the contact and related party.
• PER_ADDRESSES — address information referenced during contact updates.
• PER_PERIODS_OF_SERVICE — periods of service linked to the relationship.
• BEN_LER_F — legal entity/employer records.
• HR_API_TRANSACTION_STEPS and HR_API_TRANSACTION_VALUES — transaction framework tables used to stage and process API payloads.
• WF_ACTIVITY_ATTR_VALUES — workflow attribute values, consistent with the package's use of workflow item type and item key context.
• HR_COMMENTS and PLITBLM — supplementary storage for comments and PL/SQL table data.

Usage Notes

Given the documented process_end_api interest, this package is most relevant to the contact end-dating workflow. It is typically invoked indirectly from Oracle Forms or OAF-based pages in the HRMS contacts responsibility, not called directly by end users. Custom code should treat these routines as internal helpers rather than a supported public API; direct invocation risks bypassing validation and transaction management. The two dependent packages referencing it should also be reviewed before customizing. Because the source header dates from 2006 (version 120.3), the package is stable across 12.1.1 and 12.2.2, though the table-driven transaction model means behavior depends on correctly populated HR_API_TRANSACTION_STEPS/VALUES rows.