Search Results update_contact_extra_info




Overview
Explore in AI Chat

Overview

The APPS.HR_CONTACT_EXTRA_INFO_API package body provides the supported programmatic interface for maintaining descriptive, flexfield-based "extra information" attached to contact relationships within Oracle Human Resources (Oracle EBS 12.1.1 and 12.2.2). Contact extra information stores user-defined attributes for a person or organization contact — for example, additional identifiers, classifications, or customer-specific data captured through a descriptive flexfield structure. This package encapsulates the DML logic that underlies the Contact Extra Information form, ensuring that inserts, updates, and deletions to the underlying PER_CONTACT_EXTRA_INFO_F table are performed with correct validation, effective-dating, and date-tracked business-group behavior. It is classified as an API in the ETRM repository, meaning it is the sanctioned entry point for external or internal code that must create, change, or remove contact extra information records rather than writing to the table directly. The package is referenced by seven other packages, indicating that it is embedded within broader HR person and contact maintenance flows.

Key Procedures and Functions

  • CREATE_CONTACT_EXTRA_INFO — Inserts a new contact extra information row against a specified contact relationship. The procedure accepts an effective date, a contact relationship identifier, an information type, an information category, and up to twenty-four generic p_cei_information segment parameters. These generic arguments correspond positionally to the segments defined on the descriptive flexfield structure mapped to contact extra information. A p_validate flag allows the caller to execute the routine in validation-only mode, confirming that the supplied data would be accepted without committing the row. This is the procedure most commonly sought when developers search for "create_contact_extra_info".
  • UPDATE_CONTACT_EXTRA_INFO — Modifies an existing contact extra information record. It follows the same effective-dating and flexfield segment conventions as the create procedure, applying changes to the target row identified by the contact relationship and information type.
  • DELETE_CONTACT_EXTRA_INFO — Removes a contact extra information record, either by physical deletion or through the date-tracked end-dating mechanism, depending on how the underlying date-tracked entity is configured.

Tables Accessed

  • PER_CONTACT_EXTRA_INFO_F — The base (date-tracked _F) table that stores contact extra information records. The package reads and writes this table through the APPS synonym. Because the table is date-tracked, the API manages the effective start and end dates of each row, allowing historical versions of contact extra information to be retained and queried. The p_effective_date parameter passed into each procedure determines the date context for insert, update, or delete operations.

Usage Notes

This API is typically invoked from the Contact Extra Information form within Oracle HRMS, from concurrent programs that bulk-load or migrate contact data, and from custom PL/SQL code that must maintain contact extra information in a supported manner. Because the underlying entity is date-tracked, callers should always supply a meaningful effective date and should exercise the p_validate parameter during development to verify that flexfield segment values pass the descriptive flexfield validation before committing. Direct DML against PER_CONTACT_EXTRA_INFO_F is discouraged; using this package preserves the validation and date-tracking semantics expected by the rest of Oracle HR. When calling from custom code, the flexfield segment parameters must be populated in the order defined by the descriptive flexfield structure for the relevant information type, as the parameters are position-based rather than name-based.