Search Results init_fnd_debug




Overview
Explore in AI Chat

Overview

ICX_POR_TRACK_VALIDATE_JOB_S is an Oracle E-Business Suite PL/SQL package owned by the APPS schema. It belongs to the Oracle iProcurement / Internet Procurement (ICX) module and forms part of the supplier punchout and catalog content loading infrastructure used by the Purchasing and iProcurement product family. The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking schema rather than the definer, a convention common to shared loader utilities in EBS.

The package manages the lifecycle of validation jobs that parse and load supplier-provided catalog or punchout files into Oracle. Each job records progress through a series of status transitions, tracks counts of successfully loaded and failed records for items, prices, and headers, and optionally emits debug and log information to the FND logging framework. In effect, it is the bookkeeping and diagnostics layer behind the iProcurement catalog loader, providing controlled entry points for job creation, deletion, status updates, and debug instrumentation rather than embodying the bulk of the parsing logic itself.

Key Procedures and Functions

  • UPDATE_JOB_STATUS — A procedure that updates the status of an existing validation job (identified by job number), and records the cumulative counts of loaded and failed items, prices, and headers along with the acting user. This is the primary mechanism by which batch processing reports progress and completion back to the job tracking tables.
  • CREATE_JOB — A function returning a job number. It registers a new loader job, capturing supplier identity, supplier and exchange file names, host IP address, exchange operator, job type, and a maximum-failed-lines threshold that governs when a job should be aborted or flagged.
  • DELETE_JOB — A function returning a status string that removes a job and its associated tracking identity from the system.
  • SET_DEBUG_CHANNEL — A procedure accepting a debug channel indicator (defaulting to 0) that toggles runtime diagnostics for the session.
  • INIT_FND_DEBUG — A procedure accepting a request ID that initializes the Oracle FND debug/logging context for the job run. This is the object commonly referenced when users search for "init_fnd_debug".
  • LOG — A procedure that writes a message, with a default log type of 'LOADER', into the FND log message repository.

The package additionally declares global state: a boolean debug channel flag, a global request ID, and a module name constant ('ICX.PLSQL.LOADER.').

Tables Accessed

  • ICX_POR_BATCH_JOBS — The primary job header table, written by job creation and status update operations.
  • ICX_POR_BATCH_JOBS_S — A shadow/sequence-support table associated with batch job records.
  • ICX_POR_FAILED_LINES — Stores individual lines that failed during loading, enabling the failed-count reporting used by UPDATE_JOB_STATUS.
  • ICX_POR_FAILED_LINE_MESSAGES — Stores the detailed error messages associated with failed lines.

Usage Notes

This package is normally invoked from the iProcurement catalog and punchout loader concurrent programs, where a batch process calls CREATE_JOB at the outset, INIT_FND_DEBUG to enable FND logging, and LOG for diagnostic output, then repeatedly calls UPDATE_JOB_STATUS as processing proceeds. Because it is documented as referenced by zero other packages, it is a top-level entry point rather than a shared utility called by other PL/SQL APIs. Customizations that need to query or update loader job state should call these documented procedures directly rather than manipulating ICX_POR_BATCH_JOBS and the failure tables in isolation, since the package enforces the expected job-status conventions and failure bookkeeping.