Results for “create_contact”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

HR_CONTACT_REL_API is a public PL/SQL package in the APPS schema that maintains contact relationship information between two people in the Oracle E-Business Suite database. It belongs to the Human Resources (PER) product family and is classified as a public API, meaning it is supported for direct invocation by external and customer-written code subject to the licensing terms stated in its header.

The package exists to formalize and centralize the creation, maintenance, and removal of the contact relationships that link an employee or person of record to their designated contacts. Rather than allowing direct DML against the underlying contact relationship tables, the API enforces the business rules, validation logic, and date-tracking conventions that Oracle EBS requires, ensuring that person records and their relationship rows remain consistent across the HR schema. It is a focused, narrowly scoped API with three documented entry points and a clear dependency footprint on the core person and contact relationship entities.

Key Procedures and Functions

The package exposes three documented procedures, each covering one stage of the contact relationship lifecycle:

• CREATE_CONTACT — Creates the first contact relationship between two people and, where necessary, the contact person record itself. According to the documented behavior, the person for whom the relationship is being created must already exist, while the contact need not; if the contact person identifier is not supplied, a person record is created using details derived from the parameters of the call. The procedure supports a validation-only mode so that all checks can be performed without modifying the database. On success, either the new contact person is created and the relationship established, or the relationship is created between two existing people. On failure, no contact person or relationship is persisted and an error is raised. The API is licensed for use with Human Resources. The documentation notes that it creates the first contact relationship, implying that subsequent or additional relationships are handled through the companion update procedure.
• UPDATE_CONTACT_RELATIONSHIP — Maintains the details of an existing contact relationship, including its effective dating and associated attributes. It is the supported mechanism for amending a relationship after initial creation, preserving the integrity and audit characteristics of the underlying rows.
• DELETE_CONTACT_RELATIONSHIP — Removes a contact relationship. This procedure provides the controlled, supported route for ending a relationship rather than issuing direct deletes against the contact relationship data.

Consistent with the documented design, each of these entry points is expected to honor the standard EBS API conventions, including validation-only processing, effective date handling, and the raising of errors on failure so that the transaction can be rolled back cleanly.

Tables Accessed

The package operates against two core HR tables, resolved through APPS synonyms:

• PER_ALL_PEOPLE_F — The primary person datastore. CREATE_CONTACT reads from this table to confirm that the person of record exists and writes to it when a new contact person must be created because no contact person identifier was supplied. UPDATE_CONTACT_RELATIONSHIP and DELETE_CONTACT_RELATIONSHIP interact with it only insofar as the relationship's person references must remain valid.
• PER_CONTACT_RELATIONSHIPS — The table that physically stores the relationship between the primary person and the contact person. This is the principal target of all three procedures: rows are inserted on creation, modified on update, and removed on deletion, subject to the effective-dating conventions applied by the API.

Usage Notes

HR_CONTACT_REL_API is typically invoked from the Human Resources contact and personal information forms, from concurrent programs that load or migrate personal data, and from custom PL/SQL extensions that need to establish contact relationships during onboarding, data conversion, or integration scenarios. The reference to the search term "[email protected]" reflects the common use case of recording an external contact's e-mail address alongside the person details derived during CREATE_CONTACT.

Because the package is classified as a public API and is referenced by fourteen other packages, customizations should call it rather than performing direct DML on PER_CONTACT_RELATIONSHIPS. Callers should always supply the validation-only flag first during development, wrap invocations in a savepoint or transaction boundary, and expect an error to be raised on failure, in which case no person or relationship record is left behind. Effective dates passed at creation must be consistent with the existing person record's date-tracked history.