Search Results g_phone




Overview

IGS_OR_PHONES_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified as an "OTHER" API object within the public package family. Its business purpose is to manage telephone and telex contact point records for parties, contacts, and organizations governed by the Oracle Higher Education / Student System (IGS) module and the Trading Community Architecture (TCA). The package wraps the Oracle Customer Data Hub contact point public APIs — specifically HZ_CONTACT_POINT_V2PUB, adopted as part of the V2API uptake recorded in the source header — so that IGS applications can create, maintain, and remove phone contact points in a controlled, error-aware manner rather than issuing direct insert, update, and delete statements against the underlying TCA tables.

The source header shows a lineage of maintenance patches spanning 2002 and 2003. Notable milestones include removal of the obsolete Get_Level and Check_Primary procedures (Bug 2225917), elimination of the Customer_Id, Address_Id, and Contact_Id parameters from the insert and update routines, propagation of all HZ error messages so that more than one error can be surfaced (Bug 2338473), the switch from HZ_CONTACT_POINT_PUB to HZ_CONTACT_POINT_V2PUB (Bug 2466674), removal of hard-coded g_gen values (Bug 2730137), and signature changes required by the OVN work (Bug 2730137 and 30-APR-2003 revisions).

Key Procedures and Functions

The ETRM metadata documents three executable procedures, all of which act on contact point data:

  • INSERT_ROW — Creates a new phone or telex contact point record. It validates and formats the supplied contact point data and invokes the V2 contact point API to persist the row in the TCA tables.
  • UPDATE_ROW — Modifies an existing contact point record, allowing corrections to phone number, purpose, or related attributes. As documented in the change history, the created_by_module assignment was commented out in this call per Bug 2676422.
  • DELETE_ROW — Removes a contact point record. Deletion is typically logical in TCA, with the API managing the denormalized and history tables.
  • get_error_msg — A private helper function that iterates over the FND message stack using FND_MSG_PUB.Get and concatenates all pending messages into a single string, ensuring callers receive complete diagnostic output rather than only the first error. Package constants g_parties ('HZ_PARTIES'), g_tlx ('TLX'), and the searched-for g_phone ('PHONE') classify the contact point type being processed.

Tables Accessed

The documented table references reach through APPS synonyms to the TCA contact point model:

  • HZ_CONTACT_POINTS — The primary table holding contact point records for parties, including phone, telex, email, and similar types. This package reads and writes rows here for phone and telex contact points.
  • HZ_CONTACT_POINTS_S — The intersection or secondary entity table associated with contact points, maintained in step with the primary table when records are inserted, updated, or deleted.
  • DUAL — Used for single-row queries such as sequence retrieval or constant evaluation.

In practice the package does not manipulate HZ_CONTACT_POINTS directly; those tables are touched indirectly through the HZ_CONTACT_POINT_V2PUB API, which performs the physical DML on the package's behalf.

Usage Notes

IGS_OR_PHONES_PKG is invoked from CUSTOM code, oracle forms, and other PL/SQL packages within the IGS or TCA integration layer that need to maintain phone contact points for students, applicants, organizations, or their contacts. The ETRM metadata records that the package is referenced by one other package, indicating it is consumed as a utility by a higher-level IGS routine rather than called directly by end users. Because it exposes only insert, update, and delete operations and no query capability, read access to phone data is handled elsewhere. The get_error_msg helper should be called after any API failure to retrieve the full concatenated message stack; the package deliberately preserves multiple HZ errors, so callers should display or log the entire returned string. No concurrent program or form is registered directly against the package.