Search Results get_fk_igs_ca_inst_all

Overview

IGF_AP_PERSON_MATCH_PKG is a PL/SQL package owned by the APPS schema within Oracle E-Business Suite, declared with AUTHID CURRENT_USER so that it executes with the privileges of the invoking session. It belongs to the Oracle Grants/Proposals family of objects (the IGF namespace), and specifically supports the person match entity used during sponsor and applicant processing. The package encapsulates the standard Oracle Forms server-side DML and validation logic for the IGF_AP_PERSON_MATCH entity, exposing a stable API surface so that forms, concurrent programs, and dependent packages can insert, update, lock, and delete person match records without direct table manipulation. The business purpose is to record and maintain the association between a person (typically an applicant or sponsor contact, identified by css_id and si_id) and a calendar instance reference, together with the run date and record status that drive the match cycle. The package is classified as OTHER in the ETRM metadata and is referenced by five other packages, confirming that it acts as a shared lower-level API rather than a top-level user-facing component.

Key Procedures and Functions

The package exposes eight documented programs. The DML procedures follow the Oracle Forms-generated pattern used throughout EBS:

• INSERT_ROW — Creates a new person match record. It accepts the ROWID and primary key (apm_id) as IN OUT NOCOPY parameters so the caller receives the generated values, along with the descriptive columns and a x_mode flag defaulting to 'R'.
• ADD_ROW — Companion to INSERT_ROW for the Forms "add" operation, taking the same attribute set and returning the row identifier and key.
• UPDATE_ROW — Modifies an existing record identified by its ROWID and key columns, again honoring the x_mode default.
• LOCK_ROW — Acquires a row-level lock using the ROWID and key columns to support Forms optimistic locking before an update.
• DELETE_ROW — Removes the person match record identified by the supplied ROWID.
• GET_PK_FOR_VALIDATION — Boolean function that verifies the primary key apm_id exists; used by Forms validation triggers.
• GET_FK_IGS_CA_INST_ALL — Validates the foreign key relationship against the IGS_CA_INST_ALL calendar instance table using x_cal_type and x_sequence_number. This is the program surfaced by the search term "get_fk_igs_ca_inst_all", and it confirms the person match record is anchored to a valid calendar instance.
• BEFORE_DML — Central pre-DML hook that normalizes and validates the full attribute set (apm_id, css_id, si_id, record_type, date_run, ci_cal_type, ci_sequence_number, record_status) prior to insert, update, or delete. Documented parameters are defaulted to NULL.

Tables Accessed

The package operates against the base table IGF_AP_PERSON_MATCH_ALL, the partitioned/synonym base table holding the person match rows authored by the API, and IGF_AP_PERSON_MATCH_ALL_S, the corresponding sequence or shadow object used to supply generated primary key values. DUAL is referenced for scalar evaluations. All access occurs through APPS synonyms, in line with EBS standards. Validating against IGS_CA_INST_ALL via GET_FK_IGS_CA_INST_ALL guarantees that each person match is tied to an existing calendar instance identified by calendar type and sequence number.

Usage Notes

This package is normally invoked indirectly. Oracle Forms modules for person match maintenance call the DML procedures from block-level triggers and the validation function from key and pre-record triggers. Concurrent programs and batch person match processes invoke the same API to load or refresh match records, relying on BEFORE_DML for consistent validation. Custom code should never write to IGF_AP_PERSON_MATCH_ALL directly; it should call INSERT_ROW, UPDATE_ROW, LOCK_ROW, or DELETE_ROW, and use GET_FK_IGS_CA_INST_ALL when the calendar instance reference requires explicit validation. Because the package is declared AUTHID CURRENT_USER, callers must hold the necessary object privileges to the underlying APPS synonyms.