Search Results chk_location_codes_crit

Overview

PQP_GB_PSI_LOCATION_CODES is an Oracle EBS package body owned by the APPS schema and is classified under the ETRM documentation as type OTHER. It belongs to the PQP product family, which governs statutory and legislative reporting, and its GB prefix indicates that it addresses United Kingdom localization requirements. Specifically, the package supports PSI (Payment Summary Information) location-code processing, providing the infrastructure that validates, extracts, and post-processes United Kingdom location code data used in statutory returns. The package is a body-only unit, with its source stored alongside the specification, and it is not referenced by any other documented packages, indicating that it is invoked directly rather than through a shared PL/SQL API layer.

A significant portion of the body is dedicated to a reusable debugging framework. The package declares a private exception, hr_application_error, initialized against HR_APPLICATION_ERROR (-20001), and a global variable g_nested_level initialized from pqp_utilities.g_nested_level. These constructs underpin the trace instrumentation used throughout the package's business procedures.

Key Procedures and Functions

The documented procedures fall into two functional groups: debugging utilities and location-code business logic.

• DEBUG — Wrapper that forwards a trace message and trace location to pqp_utilities.DEBUG, providing a single instrumentation point for the package.
• DEBUG_ENTER — Checks the package debug flag and, when tracing is enabled, activates hr_utility.trace_on with the REQID pipe name when the nested utility level is zero, then delegates to pqp_utilities.debug_enter. It records entry into a procedure for trace purposes.
• DEBUG_EXIT — Companion to DEBUG_ENTER; gated by the debug flag, it records exit from a procedure so that trace output is properly bracketed.
• DEBUG_OTHERS — Handles the OTHERS exception branch for debug-relevant error reporting, ensuring unexpected errors are captured in the trace stream.
• CHK_LOCATION_CODES_CRIT — Validates location codes against the criteria required by the PSI reporting process, identifying records that fail statutory validation rules.
• LOCATION_EXTRACT_MAIN — The principal extraction routine, assembling the location code data set required for United Kingdom statutory reporting from the underlying HR location tables.
• LOCATION_CODES_POST_PROCESSING — Performs post-extraction processing, applying any final transformations, derivations, or reconciliation logic before the extracted location codes are consumed by downstream reporting.

With respect to the user's search term, clear_cache, no procedure or function of that name is documented in this package. The package contains no cache-management routine, and the term does not appear in the procedures listed above. Callers seeking cache clearing behaviour should look to pqp_utilities or other PQP packages rather than to PQP_GB_PSI_LOCATION_CODES.

Tables Accessed

The package accesses two documented tables through APPS synonyms:

• HR_LOCATIONS_ALL — The core Oracle HRMS location table storing address and location definitions. The extract and validation routines read from it to obtain the set of locations relevant to PSI location-code reporting.
• HR_LOCATION_EXTRA_INFO — The descriptive flexfield-style extension table carrying additional location attributes. It is used to retrieve the supplementary location code information needed for statutory extraction and validation.

Both tables are read within the location-code business logic; the ETRM documentation does not indicate that this package inserts, updates, or deletes rows in either table.

Usage Notes

PQP_GB_PSI_LOCATION_CODES is designed to be invoked during the preparation of United Kingdom PSI statutory returns. It is typically called from concurrent programs or reporting drivers within the PQP/GB localization flow, which supply the run context and drive the extract, validation, and post-processing sequence. Because the package is referenced by no other documented packages, custom code that requires its functionality must call it explicitly rather than relying on a higher-level API.

The debugging procedures operate only when the package-level debug flag and pqp_utilities.g_nested_level conditions are satisfied, so production executions run without trace overhead unless debug is deliberately enabled. On EBS 12.1.1 and 12.2.2 the package remains a body-only unit with no documented cache-clearing entry point.