Search Results check_parent_existence

Overview

APPS.IGS_FI_PARTY_VENDRS_PKG is a table-handler PL/SQL package body maintained in the APPS schema that encapsulates DML operations against the IGS_FI_PARTY_VENDRS table, which stores the association between a trading party (HZ_PARTIES) and its corresponding supplier (vendor and vendor site) identity within Oracle Financials for the Higher Education / Student Systems (IGS) product family. The package follows the standard Oracle EBS client-extension table-handler pattern generated for the IGS schema, in which each table handler exposes a uniform set of procedures for insert, update, delete, lock, primary-key validation, and pre-DML processing, while delegating error handling and row-reference management to shared utilities.

The package body carries a header of $Header: IGSSIC8B.pls 115.1 2003/02/25 ..., authored on 20-FEB-2003, indicating it was originally written against an early release of the IGS data model and has since been maintained in the standard APPS naming convention with the _PKG suffix. It is classified in ETRM as an API of type OTHER, meaning it is not a fully public, supported business API but rather an internal table-handler used by generated forms and other IGS packages.

Key Procedures and Functions

The package body documents six procedures and functions, each serving a specific role in the DML lifecycle:

• INSERT_ROW — Inserts a new party-vendor association row into IGS_FI_PARTY_VENDRS. It initialises the new-reference record, invokes set_column_values with an INSERT action, and delegates the actual DML and audit-column population to the shared client-extension routines.
• UPDATE_ROW — Updates an existing association row. It re-reads the current row into the old-references record, applies the new column values while preserving creation_date and created_by from the original row, and performs the update.
• DELETE_ROW — Removes an association row identified by rowid, after validating that the row still exists.
• LOCK_ROW — Acquires a row-level lock on the target row, typically used by the generated form to prevent concurrent modification before an update or delete.
• GET_PK_FOR_VALIDATION — Returns the primary-key columns for a given row so that the calling form or package can validate the existence and identity of the record (this is the routine most closely related to the user's search term check_parent_existence).
• BEFORE_DML — A pre-DML hook invoked before insert, update, or delete to enforce mandatory-column and referential-integrity checks, including verification that the referenced HZ_PARTIES parent record exists.

Tables Accessed

The package references two documented tables through APPS synonyms:

• IGS_FI_PARTY_VENDRS — The base table. All insert, update, delete, and lock operations target this table, and the package declares old_references and new_references anchored to its %ROWTYPE.
• HZ_PARTIES — The parent party table in Oracle Trading Community Architecture (TCA). It is referenced for existence and referential-integrity validation, confirming that a party_id supplied to the package corresponds to a real party before the association row is written.

Usage Notes

IGS_FI_PARTY_VENDRS_PKG is invoked principally by the generated Oracle Forms UI that maintains the party-vendor association for IGS financials, and it is referenced by one other package in the APPS schema (the counterpart that performs dependent DML or cascading operations). It is also callable from custom PL/SQL that needs to create or maintain supplier links for student-related parties. Because the package is classified as OTHER rather than a supported public API, customisations should treat it as an internal implementation detail and prefer invocations through the generated form or through the supported TCA/vendor APIs where possible. The check_parent_existence behaviour referenced in user searches is implemented through the BEFORE_DML and GET_PK_FOR_VALIDATION routines, which ensure the parent HZ_PARTIES record is present before any association row is persisted.