Search Results chk_application_id




Overview

The PL/SQL package body APPS.HR_FWN_BUS belongs to the Oracle E-Business Suite Human Resources (HR) family of APIs and is classified under the ETRM metadata as an OTHER API type. It is a component of the HR Forms Window (FWN) infrastructure, whose responsibility is to resolve form-and-window context for HR-related Oracle Forms windows, most notably the FND_FORM window used by Oracle Applications Forms. The package supplies the business logic layer that supports the HR Forms Window region, mapping a form window identifier to the legislation code and security group context that governs how HR data is displayed and validated. The "chk_application_id" search term that led to this object reflects a common developer interest in how the package associates an application identifier with a form window — an association ultimately derived from the FND_APPLICATION and FND_FORM synonym views. The source header (hrfwnrhi.pkb 115.4, dated 2002) indicates the package has been stable across many releases, including Oracle EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

  • SET_SECURITY_GROUP_ID — Establishes the security group context associated with a given form window identifier. In the documented body this procedure is implemented as a stub (it performs no business-group lookup), reflecting the design assumption that no business group context is applicable for the HR form window being rendered.
  • RETURN_LEGITATION_CODE — Returns the legislation code for the supplied form window identifier. In the documented implementation the function explicitly returns a null legislation code, because legislation context is not available at the form-canvas level.
  • INSERT_VALIDATE — Performs row-level validation logic invoked before an insert operation on the HR form window entity.
  • UPDATE_VALIDATE — Performs row-level validation logic invoked before an update operation on the HR form window entity.
  • DELETE_VALIDATE — Performs row-level validation logic invoked before a delete operation on the HR form window entity.

The two context-related routines (SET_SECURITY_GROUP_ID and RETURN_LEGITATION_CODE) rely on the private globals g_legislation_code and g_form_window_id, which are reserved exclusively for use by the legislation-code lookup function.

Tables Accessed

The documented ETRM metadata lists two tables accessed through APPS synonyms:

  • FND_APPLICATION — Read to resolve the application to which a given form window belongs. This is the table most closely tied to the chk_application_id lookup, since it maps application short names and identifiers to the form definitions in use.
  • FND_FORM — Read to obtain the form definition, including its form window metadata, that the HR Forms Window package validates against.

The remaining validation routines (INSERT/UPDATE/DELETE_VALIDATE) operate on the HR form-window entity rows implied by the HR Forms Window data model, but the ETRM metadata records only the two FND_* tables as explicit references.

Usage Notes

HR_FWN_BUS is invoked automatically by the Oracle Forms layer whenever an HR form window is opened, queried, or committed, rather than being called directly by end users. The package is referenced by four other packages in the EBS schema, indicating it forms a shared context utility for HR Forms Window processing. Because the security-group and legislation routines are implemented as stub behaviors, deployments that require actual legislation or business-group filtering must layer that logic in a separate HR Global (HRG) package or a local extension. Customizations should never modify this seeded package; instead, developers should use the standard Forms personalization or CUSTOM library hooks and treat the validation routines as read-only integration points.