Search Results get_uk_for_validation

Overview

IGR_INQUIRY_LINES_PKG is an Oracle E-Business Suite PL/SQL package that belongs to the Oracle iRecruitment (IGR) product family and is owned by the APPS schema. In EBS 12.1.1 and 12.2.2 it supports the media and inquiry handling layer of iRecruitment, specifically the maintenance of inquiry lines that link a person (candidate) to an enquiry application. The line records act as the bridge between the raw inquiry application header stored in IGR_I_APPL_ALL and the underlying sales lead line structures used to track recruitment interest and demand.

The package is classified in ETRM as an OTHER API rather than a public, supported interface. This distinction is important: it carries no formal API commitment, and Oracle treats it as an internal implementation unit whose signatures may change without notice. It is documented with three procedures — INSERT_ROW, UPDATE_ROW, and GET_UK_FOR_VALIDATION. The header comment, dated 2003 and versioned at 120.1, reflects its origin during the initial iRecruitment development cycle, while the object remains present in the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

• INSERT_ROW — Handles the DML insert logic for an inquiry line. Before writing the row, it resolves the parent sales lead by querying IGR_I_APPL_ALL for the sales_lead_id matching the supplied person and enquiry application number. It also declares typed structures from AS_UTILITY_PUB and AS_SALES_LEADS_PUB, indicating that the insert can propagate data into the sales lead line tables as part of the same operation.
• UPDATE_ROW — Encapsulates the update DML for an existing inquiry line record, allowing attribute changes on a line previously created through INSERT_ROW.
• GET_UK_FOR_VAILIDATION (GET_UK_FOR_VALIDATION) — A uniqueness-check helper that validates whether an inquiry line already exists for a given person, enquiry application number, product category, and product category set. It returns a Boolean result used by INSERT_ROW to decide whether to proceed with the insert or raise the IGS_GE_RECORD_ALREADY_EXISTS message via FND_MESSAGE.

A representative call from INSERT_ROW passes x_person_id, x_enquiry_appl_number, x_product_category_id, and x_product_category_set_id to GET_UK_FOR_VALIDATION and, when the check succeeds, loads the IGS message name and pushes it onto the IGS_GE_MSG_STACK message stack.

Tables Accessed

• IGR_I_APPL_ALL — The inquiry application header table. The package reads person_id and enquiry_appl_number and uses them to retrieve the sales_lead_id through the cur_sales_lead_id cursor.
• IGR_I_A_LINES — The inquiry application lines table that stores the line-level detail the package inserts and updates. Column sales_lead_line_id is anchored to this table through an %TYPE declaration.
• AS_SALES_LEAD_LINES — The sales lead line table accessed through APPS synonyms. The package references the AS_SALES_LEADS_PUB row types, indicating it writes or reconciles corresponding sales lead line records when an inquiry line is created.

Usage Notes

Because IGR_INQUIRY_LINES_PKG is classified as OTHER, it is not intended for direct invocation from external or custom code. It is normally called from within the iRecruitment inquiry and media handling flows, where Oracle Forms or internal iRecruitment packages pass inquiry line data for persistence. Concurrent programs are not the typical entry point; the procedures are procedural building blocks invoked during interactive or batch business transactions.

The presence of FND_MESSAGE and IGS_GE_MSG_STACK calls means callers should expect standard EBS message-stack behavior, including x_ret_status, x_msg_data, and x_msg_count outputs. Customizations should favor supported iRecruitment APIs and avoid binding directly to this package, since its header and procedure signatures are not covered by Oracle's API compatibility guarantees. The package is referenced by one other package, confirming its role as a subordinate utility within the IGR schema rather than a top-level interface.