Results for “create_contact_extra_info”
26 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The APPS.HR_CONTACT_EXTRA_INFO_SWI package body is a server-side wrapper interface (SWI) within the Oracle E-Business Suite Human Resources (PER) module. It provides a programmatic, PL/SQL-based entry point for maintaining extra information records associated with contacts held in the HR schema. In the Oracle EBS data model, contacts are stored through the contact relationship entity, and each contact may carry one or more sets of user-defined "extra information" — flexible, descriptive attributes driven by the DFF (Descriptive Flexfield) architecture. The _SWI suffix denotes that the package is not the primary business logic engine; rather, it is a thin wrapper that validates incoming arguments and delegates persistence to the underlying HR contact extra information APIs.
The package is owned by APPS and is classified as OTHER in the ETRM registry. Its header comment ($Header: pereiswi.pkb 120.0.12000000.1) indicates the file shares the naming lineage with the PER extra information SWI family, and that it is marked noship, meaning it is not an object that should be shipped as a standalone patch unit but is delivered as part of the installed product library. The package is a public, callable API surface intended for integration and extension scenarios rather than end-user interaction.
Key Procedures and Functions
ETRM documents three procedures for this package, each corresponding to one of the standard DML operations on a contact's extra information record:
- CREATE_CONTACT_EXTRA_INFO — Creates a new contact extra information row. The signature (as seen in the source excerpt) accepts a validation flag (
p_validate), the primary keyp_contact_extra_info_id, anp_effective_date, the owningp_contact_relationship_id, anp_information_type, a category (p_cei_information_category), and a block of twenty-eight genericp_cei_informationNattributes. The many flexfield segments are the standard mechanism by which Oracle EBS exposes Descriptive Flexfield columns. Thep_validateparameter permits a caller to exercise all validation logic in a rollback-only mode before committing. - UPDATE_CONTACT_EXTRA_INFO — Modifies an existing contact extra information record, again keyed by the extra information identifier and contact relationship, with the same flexfield segment parameters so that callers can change individual descriptive attributes.
- DELETE_CONTACT_EXTRA_INFO — Removes a contact extra information record, typically identified by its primary key, thereby removing the descriptive data attached to a contact relationship.
All three procedures follow the EBS API convention of returning errors through the standard fnd_api.g_ret_sts messaging channel rather than propagating raw exceptions to the caller.
Tables Accessed
The ETRM extract for this package does not enumerate any direct table references through APPS synonyms. In practice, the wrapper operates on the HR contact extra information table family (the PER_CONTACT_EXTRA_INFO structure and its associated flexfield views), with the underlying _API layer performing the actual inserts, updates, and deletes. Because the SWI is a validation and delegation layer, the absence of documented table references is consistent with its design: it does not issue DML directly but relies on the base HR contact extra information API to write the PER_CONTACT_EXTRA_INFO row and its DFF segment values.
Usage Notes
The package is invoked from custom PL/SQL integration code, Oracle Forms personalizations, or concurrent programs that need to attach or maintain contact extra information without going through the HR user interface. A caller should always pass a valid p_contact_relationship_id and a correct p_effective_date, since date-tracked records are validated against the contact relationship's effective period. Setting p_validate to a non-zero value performs all checks without committing, which is useful in test harnesses and pre-flight routines. ETRM records zero packages referencing this object, indicating it sits near the top of the HR contact API call stack and is not itself consumed by other shipped packages. Because the object is flagged noship, it must be treated as part of the installed Oracle HR library and not modified; customers requiring additional contact extra information behavior should wrap this package rather than alter it.